bss network doctor formulas 2007

BSS Network Doctor Formulas

DN98619493 © Nokia Corporation 1 (440)Issue 3-2 en Nokia Proprietary and Confidential


The information in this documentation is subject to change without notice and describes onlythe product defined in the introduction of this documentation. This documentation is intendedfor the use of Nokia's customers only for the purposes of the agreement under which thedocumentation is submitted, and no part of it may be reproduced or transmitted in any form ormeans without the prior written permission of Nokia. The documentation has been prepared tobe used by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia welcomes customer comments as part of the process ofcontinuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity,or performance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However, Nokiahas made all reasonable efforts to ensure that the instructions contained in the documentationare adequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.

Nokia's liability for any errors in the documentation is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation orthe information in it.

This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

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

Copyright © Nokia Corporation 2007. All rights reserved.

2 (440) © Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 3-2en

Contents

Contents 3

List of tables 5

List of figures 6

1 About this manual 411.1 Summary of changes 421.2 What you need to know first 431.3 Where to find more 431.4 Typographic conventions 441.4.1 Text styles 441.5 Terms and concepts 451.5.1 Abbreviations 451.5.2 Terms 46

2 BSS counter formulas 492.1 Additional GPRS channels (ach) 492.2 Multislot (msl) 522.3 Temporary block flow (tbf) 582.4 Logical link control (llc) 782.5 Radio link control (rlc) 802.6 Frame relay (frl) 1152.7 HSCSD (hsd) 1192.8 Dynamic Abis Pool (dap) 1202.9 Random access (rach) 1262.10 SDCCH drop failures (sd) 1282.10.1 SDCCH drop counters 1302.10.2 Problems with the SDCCH drop counters 1322.11 SDCCH drop ratio (sdr) 1332.12 Setup success ratio (cssr) 1352.13 TCH drop failures 1352.13.1 TCH drop call counters 1352.13.2 Drop call ratio 1382.13.3 Drop-out ratio 1382.13.4 Problems with the drop call counters 1392.14 Drop call failures (dcf) 1392.15 TCH drop call % (dcr) 1402.16 Adaptive Multirate (amr) 1612.17 Position based services (pbs) 1622.18 Handover (ho) 1642.19 Handover failure % (hfr) 1832.20 Handover success % (hsr) 2182.21 Handover failures (hof) 2232.22 Interference (itf) 2282.23 Congestion (cngt) 2302.24 Queuing (que) 2322.25 Blocking (blck) 235



2.26 Traffic (trf) 2482.27 Traffic directions 3372.27.1 Mobile originated calls (moc) 3372.27.2 Mobile terminated calls (mtc) 3392.28 Paging (pgn) 3412.29 Short message service (sms) 3452.30 Directed retry (dr) 3462.31 Availability (ava) 3482.32 Unavailability (uav) 3742.33 Location updates (lu) 3802.34 LU success % (lsr) 3812.35 Emergency call (ec) 3812.36 Emergency call success % (ecs) 3822.37 Call re-establishment (re) 3822.38 Call re-establishment success % (res) 3832.39 Quality 3832.39.1 Downlink quality (dlq) 3832.39.2 Uplink quality (ulq) 3872.40 Downlink and uplink level 3922.40.1 Downlink level (dll) 3922.40.2 Uplink level (ull) 3922.41 Power (pwr) 3932.42 Level (lev) 3932.43 Distance (dis) 3952.44 Link balance, power, level (lb) 3962.45 Call success (csf) 3992.46 Configuration (cnf) 4192.47 Wireless priority service (wps) 4202.48 DFCA 4212.49 NCCR 4242.50 Packet flow context (pfc) 4292.51 Quality control action (qca) 4312.52 Gb over IP (gbip) 437

Index 439


List of tables

Table 1. Text styles in this document 44

Table 2. Abbreviations 45

Table 3. Terms used in this document 46

Table 4. SDCCH Drop Counters 131

Table 5. TCH drop call counters 136



List of figures

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

Figure 2. Additional GPRS channel use (ach_1a) 50

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

Figure 4. Additional GPRS channels seized, S9PS (ach_3) 51

Figure 5. Additional GPRS channels seized (ach_3a) 51

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

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

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

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

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

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

Figure 12. Ratio of unreserved GPRS DL TSL requests, S9PS (msl_6) 53

Figure 13. UL multislot allocations, S9PS (msl_9) 54

Figure 14. UL multislot allocations (msl_9a) 54

Figure 15. DL multislot allocations, S9PS (msl_10) 54

Figure 16. DL multislot allocations (msl_10a) 55

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

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

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

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

Figure 21. UL multislot allocation %, S9PS (msl_15a) 56

Figure 22. DL multislot allocation %, S9PS (msl_16a) 57

Figure 23. UL multislot requests, S9PS (msl_17) 57

Figure 24. UL multislot requests (msl_17a) 57

Figure 25. DL multislot requests, S9PS (msl_18) 57

Figure 26. DL multislot requests (msl_18a) 58

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

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

Figure 29. Average UL TBF duration, S9PS (tbf_5) 59


Figure 30. Average UL TBF duration, S9PS (tbf_5a) 59

Figure 31. Average DL TBF duration, S9PS (tbf_6a) 59

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

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

Figure 34. UL mlslot allocation blocking, S9PS (tbf_15) 60

Figure 35. UL mlslot allocation blocking (tbf_15a) 61

Figure 36. DL mlslot allocation blocking, S9PS (tbf_16) 61

Figure 37. DL mlslot allocation blocking (tbf_16a) 61

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

Figure 39. UL TBF releases due to CS traffic % (tbf_19a) 62

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

Figure 41. DL TBF releases due to CS traffic % (tbf_20a) 63

Figure 42. UL drops per 10 Kbytes, MS lost, S9PS (tbf_27a) 63

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

Figure 44. UL drops per 10 Kbytes, MS lost, S10.5PS (tbf_27c) 64

Figure 45. UL drops per 10 kbytes, MS lost (tbf_27d) 65

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

Figure 47. DL drops per 10 Kbytes, MS lost, S9PS (tbf_28b) 66

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

Figure 49. DL drops per 10 kbytes, MS lost (tbf_28d) 67

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

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

Figure 52. UL TBF reallocation attempts, S9PS (tbf_31) 68

Figure 53. DL TBF reallocation attempts, S9PS (tbf_32) 68

Figure 54. TBF success % S9PS (tbf_34) 69

Figure 55. TBF success %, S10.5PS (tbf_34a) 70

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

Figure 57. Share of UL TBF releases due to flush (tbf_35a) 70

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

Figure 59. Share of DL TBF releases due to flush (tbf_36a) 71

Figure 60. Average UL TBF per timeslot, S9PS (tbf_37b) 71



Figure 61. Average UL TBFper timeslot, S9PS (tbf_37c) 72

Figure 62. Average UL TBF per timeslot (tbf_37d) 72

Figure 63. Average DL TBF per timeslot, S9PS (tbf_38b) 72

Figure 64. Average DL TBFper timeslot, S9PS (tbf_38c) 72

Figure 65. Average DL TBF per timeslot (tbf_38d) 73

Figure 66. UL GPRS TBF establishments, S10.5PS (tbf_41) 73

Figure 67. DL GPRS TBF establishments, S10.5PS (tbf_42) 73

Figure 68. Normal TBF release ratio DL, to UL, S10.5PS (tbf_44) 74

Figure 69. Average UL TBF per timeslot, Area, S9PS (tbf_47) 74

Figure 70. Average UL TBF per timeslot (tbf_47a) 74

Figure 71. Average DL TBF per timeslot, Area, S9PS (tbf_48) 75

Figure 72. Average DL TBF per timeslot (tbf_48a) 75

Figure 73. Usage ratio of EDGE resources used for UL GPRS TBFs (tbf_57) 75

Figure 74. Usage ratio of EDGE resources used for UL GPRS TBFs (tbf_57a) 76

Figure 75. Usage ratio of EDGE resources used for DL GPRS TBFs (tbf_58) 76

Figure 76. Usage ratio of EDGE resources used for DL GPRS TBFs (tbf_58a) 76

Figure 77. Usage ratio of GPRS resources used for UL EDGE TBFs (tbf_59) 77

Figure 78. Usage ratio of GPRS resources used for DL EDGE TBFs (tbf_60) 77

Figure 79. Ratio of signaling TBFs from all created UL TBFs (tbf_61) 77

Figure 80. DL signaling TBFs usage ratio (tbf_62) 78

Figure 81. UL Flush pr Minute (tbf_63) 78

Figure 82. DL Flush pr Minute (tbf_64) 78

Figure 83. Expired LLC frames % DL, S9PS (llc_1) 79

Figure 84. Discarded UL LLC frames, NSE unavailability %, S9PS (llc_2) 79

Figure 85. Ratio of discarded UL LLC frames, NSE unavailability (llc_2a) 79

Figure 86. Volume weighted LLC throughput (llc_3) 80

Figure 87. Volume weighted LLC throughput (llc_3a) 80

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

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

Figure 90. Ack. CS1 RLC DL block error rate, S9PS (rlc_3a) 81

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


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

Figure 93. UL CS1 RLC data share, S9PS (rlc_6a) 82

Figure 94. UL CS1 ack RLC data share, S9PS (rlc_6b) 82

Figure 95. UL CS1 unack RLC data share, S9PS (rlc_6c) 82

Figure 96. UL CS1 ack RLC data share (rlc_6e) 83

Figure 97. UL CS1 unack RLC data share (rlc_6f) 83

Figure 98. UL CS2 RLC data share, S9PS (rlc_7a) 84

Figure 99. UL CS2 RLC data share (rlc_7b) 84

Figure 100. DL CS1 RLC data share, S9PS (rlc_8a) 84

Figure 101. DL CS1 ack RLC data share, S9PS (rlc_8b) 85

Figure 102. DL CS1 ack RLC data share (rlc_8e) 85

Figure 103. DL CS1 unack RLC data share (rlc_8f) 86

Figure 104. DL CS1 unack RLC data share, S9PS (rlc_8c) 86

Figure 105. DL CS2 RLC data share, S9PS (rlc_9a) 86

Figure 106. DL CS2 RLC data share ( rlc_9b) 87

Figure 107. UL CS1 RLC block error rate, S9PS (rlc_10a) 88

Figure 108. UL CS1 RLC block error rate, S9PS (rlc_10b) 89

Figure 109. UL CS1 ACK RLC block error rate, S9PS (rlc_10c) 89

Figure 110. UL CS1 ACK RLC block error rate, S9PS (rlc_10d) 89

Figure 111. UL CS1 ACK RLC block error rate, S11.5 (rlc_10e) 90

Figure 112. UL CS2 ARLC block error rate, S9PS (rlc_11a) 90

Figure 113. UL CS2 RLC block error rate, S9PS (rlc_11b) 91

Figure 114. UL CS2 ACK RLC block error rate, S9PS (rlc_11c) 91

Figure 115. UL CS2 ACK RLC block error rate, S10.5PS(rlc_11d) 92

Figure 116. UL CS2 ACK RLC block error rate, S10.5PS (rlc_11e) 92

Figure 117. UL CS2 ACK RLC block error rate, S11.5 (rlc_11f) 92

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

Figure 119. DL CS1 ACK RLC block error rate, S9PS (rlc_12a) 93

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

Figure 121. UL RLC blocks, S9PS (rlc_14) 93

Figure 122. UL RLC blocks (rlc_14a) 94



Figure 123. DL RLC blocks, S9PS (rlc_15) 94

Figure 124. DL RLC blocks (rlc_15a) 94

Figure 125. UL ACK EGPRS block error ratio S10.5PS (rlc_18) 95

Figure 126. DL ACK EGPRS block error ratio S10.5PS (rlc_19) 95

Figure 127. UL ACK EGPRS block error ratio MCS-n, S10.5PS (rlc_20) 95

Figure 128. UL ACK EGPRS block error ratio MCS-n (rlc_20b) 96

Figure 129. UL ACK EGPRS block error ratio MCS-n (rlc_20c) 96

Figure 130. DL ACK EGPRS block error ratio MCS-n, S10.5PS (rlc_21) 97

Figure 131. UL ACK RLC data share MCS-n, S10.5PS (rlc_22) 97

Figure 132. UL UNACK RLC data share MCS-n, S10.5PS (rlc_23) 98

Figure 133. DL ACK RLC data share MCS-n, S10.5PS (rlc_24) 98

Figure 134. DL UNACK RLC data share MCS-n, S10.5PS (rlc_25) 98

Figure 135. UL CS3 retransmission ratio (rlc_27) 99

Figure 136. DL CS3 retransmission ratio (rlc_28) 99

Figure 137. UL CS4 retransmission ratio (rlc_29) 99

Figure 138. DL CS4 retransmission ratio (rlc_30) 100

Figure 139. Ratio of UL CS2 ack blocks (rlc_32) 100

Figure 140. Ratio of DL CS2 ack blocks (rlc_33) 101





Figure 145. GMSK RLC data block share, S10.5PS (rlc_39) 103

Figure 146. GMSK RLC data share, S10.5PS (rlc_41) 103

Figure 147. GPRS UL ACK RLC data share, S10.5PS (rlc_42) 104

Figure 148. GPRS UL ACK RLC data share (rlc_42a) 104

Figure 149. GPRS UL UNACK RLC data share, S10.5PS (rlc_43) 105

Figure 150. GPRS UL UNACK RLC data share (rlc_43a) 105

Figure 151. GPRS DL ACK RLC data share, S10.5PS (rlc_44) 106

Figure 152. GPRS DL ACK RLC data share (rlc_44a) 107

Figure 153. GPRS DL UNACK RLC data share, S10.5PS (rlc_45) 107


Figure 154. GPRS DL UNACK RLC data share (rlc_45a) 108

Figure 155. EGPRS UL ACK RLC data share, S10.5PS (rlc_46) 108

Figure 156. EGPRS UL ACK RLC data share (rlc_46a) 109

Figure 157. EGPRS UL UNACK RLC data share, S10.5PS (rlc_47) 110

Figure 158. EGPRS UL UNACK RLC data share (rlc_47a) 110

Figure 159. EGPRS DL ACK RLC data share, S10.5PS (rlc_48) 111

Figure 160. EGPRS DL ACK RLC data share (rlc_48a) 112

Figure 161. EGPRS DL UNACK RLC data share, S10.5PS (rlc_49) 112

Figure 162. EGPRS DL UNACK RLC data share (rlc_49a) 113

Figure 163. Ratio of UL CS1 (GPRS_ack) (rlc_54b) 114

Figure 164. Ratio of DL CS1 (GPRS_ack) (rlc_55b) 114

Figure 165. EGPRS UL block error ratio (rlc_60) 114

Figure 166. GMSK modulation used in DL (rlc_61) 115

Figure 167. Kbytes in sent frames, S9PS (frl_1) 115

Figure 168. Kbytes in received frames, S9PS (frl_2) 116

Figure 169. ‘Wrong check seq.’ errors per Mbyte, S9PS (frl_3) 116

Figure 170. ‘Other’ errors per Mbyte, S9PS (frl_4) 116

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

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

Figure 173. Maximum sent load %, S9PS (frl_7) 117

Figure 174. Maximum received load %, S9PS (frl_8) 118

Figure 175. Sent frames, S9PS (frl_9) 118

Figure 176. Received frames, S9PS (frl_10) 118

Figure 177. Discarded sent frames, S9PS (frl_11) 119

Figure 178. Discarded received frames, S9PS (frl_12) 119

Figure 179. Discarded bytes, UL NS-VC congestion S9PS (frl_13a) 119

Figure 180. Throughput ratio, S7HS (hsd_15) 120

Figure 181. Bps traffic share, S7HS (hsd_49) 120

Figure 182. Bps traffic share, S7HS (hsd_50) 120

Figure 183. Average usage of DL Dynamic Abis Pool, S10.5PS (dap_1a) 121

Figure 184. Average usage of UL Dynamic Abis Pool, S10.5PS (dap_2a) 121



Figure 185. Average usage of UL Dynamic Abis Pool (dap_2b) 121

Figure 186. Average Available PCM Sub-TSL, S10.5PS (dap_3) 122

Figure 187. Inadequate EDAP resources in DL limited by EDAP size (dap_7a) 123

Figure 188. Inadequate EDAP resources in DL (dap_7b) 123

Figure 189. No EDAP resources in UL due to too small EDAP pool size (dap_8c) 124

Figure 190. Sum(UL_No_Resource_minutes)/Sum(UL GPRS payload_Gbyte + ULEGPRS payload_Gbyte) (dap_9) 125

Figure 191. Inadequate EDAP resources in UL limited by PCU (dap_10) 126

Figure 192. Average RACH slot, S1 (rach_1) 126

Figure 193. Peak RACH load, average, S1 (rach_2) 126

Figure 194. Peak RACH load %, S1 (rach_3) 127

Figure 195. Average RACH load %, S1 (rach_4) 127

Figure 196. Average RACH busy, S1 (rach_5) 127

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

Figure 198. Total RACH rejection ratio, S7 (rach_7) 128

Figure 199. Ghosts detected on SDCCH and other failures, S1 (sd_1) 129

Figure 200. Ghosts detected on SDCCH and other failures, S1 (sd_1a) 129

Figure 201. Ghosts detected on SDCCH and other failures (sd_1b) 130

Figure 202. SDCCH drop %, S3 (sdr_1a) 134

Figure 203. SDCCH drop %, abis fail excluded, S3 (sdr_2) 134

Figure 204. Illegal establishment cause % (sdr_3b) 134

Figure 205. SDCCH drop ratio without timer T3101 expiry % (sdr_4) 135

Figure 206. SDCCH, TCH setup success %, S4 (cssr_2) 135

Figure 207. TCH drop calls in HO, S2 (dcf_2) 139

Figure 208. TCH drop calls in BSC outgoing HO, S3 (dcf_3) 139

Figure 209. TCH drop calls in intra-cell HO, S3 (dcf_4) 140

Figure 210. TCH drop calls in intra BSC HO, S3 (dcf_6) 140

Figure 211. Drop calls in BSC incoming HO, S3 (dcf_7) 140

Figure 212. TCH drop calls in HO, S7 (dcf_11) 140

Figure 213. TCH drop call %, area, S3 (dcr_3c) 141

Figure 214. TCH drop call %, area, real, after re-establishment S3 (dcr_3f) 143


Figure 215. TCH drop call %, area, real, before re-establishment, S3 (dcr_3g) 144

Figure 216. TCH drop call %, area, real, after re-establishment, S7 (dcr_3h) 144

Figure 217. TCH drop call %, area, real, before re-establishment, S3 (dcr_3i) 145

Figure 218. TCH drop call %, area, real, after re-establishment, S7 (dcr_3j) 147

Figure 219. TCH drop-out %, BTS level, before call re-establishment, S3(dcr_4c) 148

Figure 220. TCH drop-out %, BTS level, before call re-establishment, S3(dcr_4d) 148

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

Figure 222. TCH drop-out %, BTS level, before call re-establishment, S7(dcr_4f) 150

Figure 223. TCH drop-out ratio, before call re-establishment (dcr_4g) 150

Figure 224. TCH drop call (dropped conversation) %, BSC level, S4 (dcr_5) 151

Figure 225. . . TCH dropped conversation %, area, re-establishment considered, S7(dcr_5b) 152

Figure 226. . TCH drop call %, after TCH assignment, without RE, area level, S10.5(dcr_8c) 152

Figure 227.TCH drop call %, after TCH assignment, with RE, area level, S10.5(dcr_8e) 153

Figure 228. TCH drop call %, S11 (dcr_8h) 153

Figure 229. Drops per erlang, before re-establishment, S4 (dcr_10) 154

Figure 230. Drops per erlang, after re-establishment, S4 (dcr_10a) 154

Figure 231. Drops per erlang, after re-establishment, S7 (dcr_10b) 155

Figure 232. Drops per erlang, before re-establishment (dcr_10c) 156

Figure 233. Drops per erlang, after re-establishment (dcr_10d) 156

Figure 234. TCH Rf loss in HO - ratio, IUO (dcr_14) 156

Figure 235. Transcoder failure ratio, FR (dcr_16) 157

Figure 236. Transcoder failure ratio, EFR (dcr_17) 157

Figure 237. Transcoder failure ratio, HR (dcr_18) 157

Figure 238. Transcoder failure ratio, AMR FR (dcr_19) 157

Figure 239. Transcoder failure ratio, AMR HR (dcr_20) 158

Figure 240. Transcoder failure ratio (dcr_21) 158



Figure 241. Call failures share of transcoder failures (dcr_22) 158

Figure 242. HO target share of transcoder failures (dcr_23) 158

Figure 243. HO source share of transcoder failures (dcr_24) 159

Figure 244. Transcoder failures (dcr_25) 159

Figure 245. TCH drop call %, before re-establishment (dcr_31) 160

Figure 246. TCH drop call %, after re-establishment (dcr_32) 161

Figure 247. Codec set upgrade attempts, S10 (amr_1) 161

Figure 248. Codec set downgrade attempts, S10 (amr_2) 161

Figure 249. Codec set upgrade failure ratio, S10 (amr_3) 162

Figure 250. Codec set downgrade failure ratio, S10 (amr_4) 162

Figure 251. Failure ratio of location calculations for external LCS clients, S10(pbs_1a) 162

Figure 252. Failure ratio of location calculations for emergency calls, S10(pbs_2a) 162

Figure 253. Failure ratio of E-OTD location calculations, S10 (pbs_3) 163

Figure 254. Failure ratio of E-OTD location calculations, S10 (pbs_3a) 163

Figure 255. Failure ratio of location calculations for MS, S10 (pbs_4a) 163

Figure 256. Failure ratio of location calculations for operator, S10 (pbs_5a) 163

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

Figure 258. Failure ratio of location calculations using stand-alone GPS, S10(pbs_6a) 164

Figure 259. Unspecified LCS requests, S10 (pbs_8) 164

Figure 260. Return from super TRXs to regular TRX, S4 (ho_1) 164

Figure 261. HO attempts from regular TRXs to super, S4 (ho_2) 165

Figure 262. HO attempts from super to regular, S4 (ho_3) 165

Figure 263. Share of HO attempts from super to regular due to DL quality, S4(ho_4) 165

Figure 264. Share of HO attempts from super to regular due to DL interference, S4(ho_5) 165

Figure 265. Share of HO attempts from super to regular due to UL interference, S4(ho_6) 166

Figure 266. Share of HO attempts from super to regular due to bad C/I, S4(ho_7) 166


Figure 267. MSC incoming HO attempts (ho_8) 166

Figure 268. MSC outgoing HO attempts (ho_9) 166

Figure 269. BSC incoming HO attempts (ho_10) 167

Figure 270. BSC outgoing HO attempts (ho_11) 167

Figure 271. Intra-cell HO attempts, S6 (ho_12a) 167

Figure 272. HO attempts, S3 (ho_13a) 167

Figure 273. HO attempts, outgoing and intra-cell, S5 (ho_13b) 168

Figure 274. HO attempts, outgoing and intra-cell, S3 (ho_13e) 168

Figure 275. HO attempts, outgoing and intra-cell, S9 (ho_13g) 169

Figure 276. HO attempts, S11.5 (ho_13h) 170

Figure 277. TCH requests for HO (ho_14a) 170

Figure 278. TCH requests for HO (ho_14b) 170

Figure 279. TCH seizures for HO (ho_15) 170

Figure 280. TCH-TCH HO attempts (ho_16) 171

Figure 281. SDCCH-TCH HO attempts (ho_17) 171

Figure 282. SDCCH-SDCCH HO attempts (ho_18) 171

Figure 283. TCH-TCH HO successes (ho_19) 172

Figure 284. SDCCH-TCH HO successes (ho_20) 172

Figure 285. SDCCH-SDCCH HO successes (ho_21) 172

Figure 286. MSC controlled HO attempts (ho_22) 172

Figure 287. BSC controlled HO attempts (ho_23) 173

Figure 288. Intra-cell HO attempts (ho_24) 173

Figure 289. MSC controlled HO successes (ho_25) 173

Figure 290. BSC controlled HO successes (ho_26) 174

Figure 291. Intra-cell HO successes (ho_27) 174

Figure 292. MSC incoming HO successes (ho_28) 174

Figure 293. MSC outgoing HO successes (ho_29) 174

Figure 294. BSC incoming HO successes (ho_30) 175

Figure 295. BSC outgoing HO successes (ho_31) 175

Figure 296. Incoming HO success (ho_32) 175

Figure 297. Outgoing HO successes (ho_33) 175



Figure 298. Outgoing HO attempts (ho_34) 176

Figure 299. Incoming HO attempts (ho_35) 176

Figure 300. Outgoing SDCCH-SDCCH HO attempts (ho_36) 176

Figure 301. Incoming SDCCH-SDCCH HO attempts (ho_37) 176

Figure 302. Outgoing SDCCH-TCH HO attempts (ho_38) 177

Figure 303. Incoming SDCCH-TCH HO attempts (ho_39) 177

Figure 304. Outgoing TCH-TCH HO attempts (ho_40) 177

Figure 305. Incoming TCH-TCH HO attempts (ho_41) 177

Figure 306. Outgoing SDCCH-SDCCH HO success (ho_42) 178

Figure 307. Incoming SDCCH-SDCCH HO success (ho_43) 178

Figure 308. Outgoing SDCCH-TCH HO success (ho_44) 178

Figure 309. Incoming SDCCH-TCH HO success (ho_45) 178

Figure 310. Outgoing TCH-TCH HO success (ho_46) 179

Figure 311. Incoming TCH-TCH HO success (ho_47) 179

Figure 312. Intra-cell HO share (ho_48) 179

Figure 313. MSC controlled incoming HO attempts (ho_49) 179

Figure 314. IBHO attempts (ho_50a) 180

Figure 315. Total IBHO attempts to default ANEs (ho_51) 180

Figure 316. Share of IBHO attempts to GSM ANEs (ho_52a) 181

Figure 317. Share of IBHO attempts to UTRAN ANEs (ho_53a) 181

Figure 318. Share of default ANE IBHO attempts for GSM ANE (ho_54) 182

Figure 319. Share of default ANE IBHO attempts for UTRAN ANE (ho_55) 182

Figure 320. GPRS triggered handovers (ho_61) 182

Figure 321. ALL ANE IBHO attempts (ho_62) 183

Figure 322. Share of ALL ANE IBHO attempts to GSM (ho_63) 183

Figure 323. Share of ALL ANE IBHO attempts to UTRAN (ho_64) 183

Figure 324. Total HO failure %, S1 (hfr_1) 184

Figure 325. Total HO failure %, S1 (hfr_2) 185

Figure 326. Total HO failure ratio (hfr_2a) 186

Figure 327. Intra-cell HO failure share, S1 (hfr_3a) 187

Figure 328. Intra-cell HO failure share, S1 (hfr_3b) 187


Figure 329. Intra-cell HO failure share, S1 (hfr_3c) 187

Figure 330. Intra-cell HO failure share, S1 (hfr_3d) 188

Figure 331. Incoming MSC ctrl HO failure %, S1 (hfr_4) 188

Figure 332. Incoming MSC ctrl HO failure share, S1 (hfr_4a) 189

Figure 333. Incoming MSC ctrl HO failure share, S1 (hfr_4b) 189

Figure 334. Incoming MSC ctrl HO failure share, S1 (hfr_4c) 189

Figure 335. Incoming MSC ctrl HO failure share, S1 (hfr_4d) 190

Figure 336. Outgoing MSC ctrl HO failure ratio %, S1 (hfr_5) 190

Figure 337. Outgoing MSC ctrl HO failure share %, S1 (hfr_5a) 191

Figure 338. Outgoing MSC ctrl HO failure share %, S1 (hfr_5b) 191

Figure 339. Outgoing MSC ctrl HO failure share %, S1 (hfr_5c) 191

Figure 340. Outgoing MSC ctrl HO failure share %, S1 (hfr_5d) 192

Figure 341. Incoming BSC ctrl HO failure %, S1 (hfr_6) 192

Figure 342. Incoming BSC ctrl HO failure share %, S1 (hfr_6a) 193

Figure 343. Incoming BSC ctrl HO failure %, S1 (hfr_6b) 193

Figure 344. Incoming BSC ctrl HO failure share %, S1 (hfr_6c) 193

Figure 345. Incoming BSC ctrl HO failure %, S1 (hfr_6d) 194

Figure 346. Outgoing BSC ctrl HO failure share, S1 (hfr_7) 194

Figure 347. Outgoing BSC ctrl HO failure share, S1 (hfr_7a) 195

Figure 348. Outgoing BSC ctrl HO failure share, S1 (hfr_7b) 195

Figure 349. Outgoing BSC ctrl HO failure share, S1 (hfr_7c) 195

Figure 350. Outgoing BSC ctrl HO failure share, S1 (hfr_7d) 196

Figure 351. Internal inter HO failure %, S4 (hfr_8) 196

Figure 352. Internal intra HO failure %, S4 (hfr_9) 196

Figure 353. External source HO failure %, S4 (hfr_10) 197

Figure 354. HO failure % from super to regular, S4 (hfr_12) 197

Figure 355. HO failure % from regular to super, S4 (hfr_13) 197

Figure 356. Share of HO failures from regular to super due to return, S4 (hfr_14) 197

Figure 357. Share of HO failures from regular to super due to MS lost, S4(hfr_15) 198

Figure 358. Share of HO failures from regular to super due to another cause, S4(hfr_16) 198



Figure 359. Share of HO failures from super to regular due to return, S4 (hfr_17) 198

Figure 360. Share of HO failures from super to regular due to MS lost, S4(hfr_18) 199

Figure 361. Share of HO failures from super to regular due to another cause, S4(hfr_19) 199

Figure 362. SDCCH-SDCCH HO failure %, S2 (hfr_20) 200

Figure 363. SDCCH-TCH HO failure %, S2 (hfr_21) 200

Figure 364. TCH-TCH HO failure %, S2 (hfr_22) 200

Figure 365. SDCCH-SDCCH incoming HO failure %, S2 (hfr_23) 201

Figure 366. SDCCH-SDCCH outgoing HO failure ratio, S2 (hfr_24) 201

Figure 367. SDCCH-TCH incoming HO failure %, S2 (hfr_25) 201

Figure 368. SDCCH-TCH outgoing HO failure %, S2 (hfr_26) 201

Figure 369. TCH-TCH incoming HO failure %, S2 (hfr_27) 202

Figure 370. TCH-TCH outgoing HO failure %, S2 (hfr_28) 202

Figure 371. MSC ctrl HO failure %, blocking (hfr_29) 202

Figure 372. MSC ctrl HO failure %, not allowed (hfr_30) 202

Figure 373. MSC ctrl HO failure %, return to old (hfr_31) 203

Figure 374. MSC ctrl HO failure %, call clear (hfr_32) 203

Figure 375. MSC ctrl HO failure %, end HO (hfr_33) 203

Figure 376. MSC ctrl HO failure %, end HO BSS (hfr_34) 203

Figure 377. MSC ctrl HO failure %, wrong A interface (hfr_35) 204

Figure 378. MSC ctrl HO failure %, adjacent cell error (hfr_36) 204

Figure 379. BSC ctrl HO failure %, blocking (hfr_37) 204

Figure 380. BSC ctrl HO failure %, not allowed (hfr_38) 205

Figure 381. BSC ctrl HO failure %, return to old (hfr_39) 205

Figure 382. BSC ctrl HO failure %, call clear (hfr_40) 205

Figure 383. BSC ctrl HO failure %, end HO (hfr_41) 205

Figure 384. BSC ctrl HO failure %, end HO BSS (hfr_42) 206

Figure 385. BSC ctrl HO failure %, wrong A interface (hfr_43) 206

Figure 386. BSC ctrl HO drop call % (hfr_44) 206

Figure 387. Intra-cell HO failure %, cell_fail_lack (hfr_45) 206

Figure 388. Intra-cell HO failure %, not allowed (hfr_46) 207


Figure 389. Intra-cell HO failure %, return to old (hfr_47) 207

Figure 390. Intra-cell HO failure %, call clear (hfr_48) 207

Figure 391. Intra-cell HO failure %, MS lost (hfr_49) 207

Figure 392. Intra-cell HO failure %, BSS problem (hfr_50) 208

Figure 393. Intra-cell HO failure %, drop call (hfr_51) 208

Figure 394. HO failure % to adjacent cell (hfr_52) 208

Figure 395. HO failure % from adjacent cell (hfr_53) 208

Figure 396. HO failure %, blocking excluded (hfr_54a) 209

Figure 397. HO failure % due to radio interface blocking (hfr_55) 209

Figure 398. Intra-cell HO failure %, wrong A interface (hfr_56) 210

Figure 399. Intra-cell HO failure % (hfr_57) 210

Figure 400. HO failures to target cell, S6 (hfr_58) 210

Figure 401. HO failures from target cell, S6 (hfr_59) 211

Figure 402. HO drop ratio (hfr_68) 211

Figure 403. HO drop ratio (hfr_68a) 212

Figure 404. HO failures to target WCDMA cell, S10.5 (hfr_69) 212

Figure 405. HO failures from target WCDMA cell, S10.5 (hfr_70) 213

Figure 406. Intra-Segment SDCCH-SDCCH HO failure ratio from BCCH to non-BCCH layer, BSC level, S10.5 (hfr_71) 213

Figure 407. IIntra-segment SDCCH-SDCCH HO failure ratio between BTS types,BSC level, S10.5 (hfr_72) 213

Figure 408. Intra-segment TCH-TCH HO failure ratio between bands (due to load),BSC level, S10.5 (hfr_73) 214

Figure 409. Intra-segment TCH-TCH HO failure ratio between bands (due to downlinksignal level), BSC level, S10.5 (hfr_74) 214

Figure 410. Intra-segment TCH-TCH HO failure ratio between BTS types (due toload), BSC level, S10.5 (hfr_75) 215

Figure 411. IBHO failure ratio for default GSM ANE (hfr_76) 215

Figure 412. IBHO failure ratio for default UTRAN ANE (hfr_77) 215

Figure 413. IBHO failure ratio to GSM ANEs (hfr_78a) 216

Figure 414. IBHO failure ratio to UTRAN ANEs (hfr_79a) 216

Figure 415. IBHO failure ratio for GSM ANEx (hfr_83) 217

Figure 416. IBHO failure ratio for UTRAN ANEx (hfr_84) 217



Figure 417. IBHO ALL ANE failure ratio to GSM (hfr_85) 217

Figure 418. IBHO ALL ANE failure ratio to UTRAN (hfr_86) 218

Figure 419. MSC controlled outgoing SDCCH-SDCCH HO success %, S1(hsr_1) 218

Figure 420. MSC controlled outgoing SDCCH-TCH HO success %, S1 (hsr_2) 218

Figure 421. MSC controlled outgoing TCH-TCH HO success %, S1 (hsr_3) 218

Figure 422. BSC controlled outgoing SDCCH-SDCCH HO success %, S1(hsr_4) 219

Figure 423. BSC controlled outgoing SDCCH-TCH HO success %, S1 (hsr_5) 219

Figure 424. BSC controlled outgoing TCH-TCH HO success %, S1 (hsr_6) 219

Figure 425. Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_7) 219

Figure 426. Intra-cell SDCCH-TCH HO success %, S1 (hsr_8) 220

Figure 427. Intra-cell TCH-TCH HO success %, S1 (hsr_9) 220

Figure 428. MSC controlled incoming SDCCH-SDCCH HO success %, S1(hsr_10) 220

Figure 429. MSC controlled incoming SDCCH-TCH HO success %, S1 (hsr_11) 220

Figure 430. MSC controlled incoming TCH-TCH HO success %, S1 (hsr_12) 221

Figure 431. BSC controlled incoming SDCCH-SDCCH HO success %, S1(hsr_13) 221

Figure 432. BSC controlled incoming SDCCH-TCH HO success %, S1 (hsr_14) 221

Figure 433. BSC controlled incoming TCH-TCH HO success %, S1 (hsr_15) 221

Figure 434. BSC controlled incoming HO success %, S1 (hsr_16) 222

Figure 435. MSC controlled incoming HO success %, S1 (hsr_17) 222

Figure 436. Incoming HO success %, S1 (hsr_18) 222

Figure 437. Outgoing HO success %, S1 (hsr_19) 222

Figure 438. Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_20) 223

Figure 439. Intra-cell SDCCH-TCH HO success %, S1 (hsr_21) 223

Figure 440. Intra-cell TCH-TCH HO success %, S1 (hsr_22) 223

Figure 441. Outgoing HO failures due to lack of resources (hof_1) 223

Figure 442. Incoming HO failures due to lack of resources (hof_2) 224

Figure 443. TCH HO failures when return to old channel was successful (hof_3) 224

Figure 444. SDCCH HO failures when return to old channel was successful(hof_4) 224


Figure 445. MSC incoming HO failures (hof_5) 224

Figure 446. MSC outgoing HO failures (hof_6) 225

Figure 447. MSC outgoing HO failures (hof_6a) 225

Figure 448. BSC incoming HO failures (hof_7) 225

Figure 449. BSC incoming HO failures (hof_7a) 225

Figure 450. BSC outgoing HO failures (hof_8) 226

Figure 451. BSC outgoing HO failures (hof_8a) 226

Figure 452. Intra-cell HO failures (hof_9) 226

Figure 453. Intra-cell HO failures (hof_9a) 226

Figure 454. Intra-cell HO failures (hof_9b) 227

Figure 455. Failed outgoing HO, return to old (hof_10) 227

Figure 456. Outgoing HO failures (hof_12) 227

Figure 457. Intra-cell HO failure, return to old channel (hof_13) 227

Figure 458. Intra-cell HO failure, drop call (hof_14) 227

Figure 459. Incoming HO failures (hof_15) 228

Figure 460. UL interference, BTS level, S1 (itf_1) 228

Figure 461. Idle TSL percentage of time in band X, TRX level, IUO, S4 (itf_2) 229

Figure 462. UL interference from IUO, TRX level, S4 (itf_3) 229

Figure 463. UL interference from Power Control, TRX level, S6 (itf_4) 230

Figure 464. TCH congestion time, S1 (cngt_1) 230

Figure 465. SDCCH congestion time, S1 (cngt_2) 230

Figure 466. FTCH time congestion % (cngt_3) 230

Figure 467. FTCH time congestion % (cngt_3a) 231

Figure 468. FTCH time congestion ratio (cngt_3b) 231

Figure 469. HTCH time congestion % (cngt_4) 231

Figure 470. HTCH time congestion % (cngt_4a) 231

Figure 471. HTCH time congestion ratio (cngt_4b) 232

Figure 472. Queued, served TCH call requests % (que_1a) 232

Figure 473. Queued, served TCH HO requests % (que_2) 232

Figure 474. Queued, served TCH HO requests % (que_2a) 233

Figure 475. Successful queued TCH requests (que_3) 233



Figure 476. Successful non-queued TCH requests (que_4) 233

Figure 477. Successful queued TCH HO requests (que_5) 233

Figure 478. Successful non-queued TCH HO requests (que_6) 234

Figure 479. Non-queued, served TCH call requests % (que_7) 234

Figure 480. Non-queued, served TCH HO requests % (que_8) 234

Figure 481. Non-queued, served TCH HO requests % (que_8a) 234

Figure 482. TCH raw blocking, S1 (blck_1) 235

Figure 483. SDCCH blocking %, S1 (blck_5) 235

Figure 484. SDCCH real blocking %, S1 (blck_5a) 235

Figure 485. TCH raw blocking % on super TRXs, S4 (blck_6) 236

Figure 486. TCH raw blocking % on regular TRXs, S4 (blck_7) 236

Figure 487. TCH call blocking, before DR, S2 (blck_8) 236

Figure 488. TCH call blocking %, DR compensated, S2 (blck_8b) 237

Figure 489. TCH call blocking %, DR and DAC compensated, EFR excluded, S5(blck_8d) 238

Figure 490. TCH call blocking %, DR compensated, EFR excluded S11.5(blck_8f) 239

Figure 491. TCH call blocking %, S11.5 (blck_8g) 240

Figure 492. TCH call blocking, DR compensated, EFR excluded (blck_8h) 240

Figure 493. Blocked calls, S5 (blck_9b) 241

Figure 494. Blocked calls, S5 (blck_9c) 241

Figure 495. Blocked calls, S11.5 (blck_9d) 242

Figure 496. Blocked TCH HOs, S2 (blck_10a) 242

Figure 497. Blocked TCH HOs, S5 (blck_10b) 242

Figure 498. TCH HO blocking, S2 (blck_11a) 242

Figure 499. TCH HO blocking without Q, S2 (blck_11b) 243

Figure 500. TCH HO blocking, S5 (blck_11c) 243

Figure 501. Blocked incoming and internal HO, S2 (blck_12) 243

Figure 502. Blocked incoming and internal HO, S2 (blck_12a) 244

Figure 503. AG blocking, S1 (blck_13) 244

Figure 504. FCS blocking, S5 (blck_14) 244

Figure 505. Blocked SDCCH seizure attempts, S5 (blck_15) 244


Figure 506. HO blocking % (blck_16a) 245

Figure 507. Handover blocking % (blck_16b) 245

Figure 508. Blocked FACCH call setup TCH requests (blck_18) 245

Figure 509. Handover blocking to target cell (blck_19) 246

Figure 510. Handover blocking from target cell (blck_20) 246

Figure 511. NACK ratio of p-immediate assignment, S9PS (blck_21) 246

Figure 512. NACK ratio of p-immediate assignment requests (blck_21b) 247

Figure 513. Territory upgrade rejection %, S9PS (blck_22) 247

Figure 514. Handover blocking to target WCDMA cell, S10.5 (blck_27) 247

Figure 515. Handover blocking from target WCDMA cell, S10.5 (blck_28) 248

Figure 516. TCH denied for Call request, Ratio, S10 (blck_29) 248

Figure 517. TCH traffic sum, S1 (trf_1) 249

Figure 518. TCH traffic sum, S1 (trf_1a) 249

Figure 519. TCH traffic sum of normal TRXs, S1 (trf_1b) 250

Figure 520. TCH traffic sum of extended TRXs, S1 (trf_1c) 250

Figure 521. Average call length, S1 (trf_2b) 250

Figure 522. Average call length, S1 (trf_2d) 251

Figure 523. CS territory usage, S1 (trf_3) 251

Figure 524. FTCH usage, S5 (trf_3b) 252

Figure 525. Average SDCCH holding time, S1 (trf_4) 252

Figure 526. Average FTCH holding time, S1 (trf_5) 252

Figure 527. TCH seizures for new call (call bids), S1 (trf_6) 253

Figure 528. SDCCH usage %, S1 (trf_7b) 253

Figure 529. SDCCH usage %, S1 (trf_7c) 253

Figure 530. TCH traffic absorption on super, S4 (trf_8) 254

Figure 531. TCH traffic absorption on super, S4 (trf_8a) 254

Figure 532. Average cell TCH traffic from IUO, S4 (trf_9) 254

Figure 533. Cell TCH traffic from IUO, S4 (trf_9a) 255

Figure 534. Super TRX TCH traffic, S4 (trf_10) 255

Figure 535. Sum of super TRX TCH traffic, S4 (trf_10a) 255

Figure 536. Average SDCCH traffic, erlang, S2 (trf_11) 256



Figure 537. Average SDCCH traffic, erlang, S2 (trf_11b) 256

Figure 538. Average TCH traffic, erlang, S2 (trf_12) 256

Figure 539. Average TCH traffic, erlang, S2 (trf_12a) 256

Figure 540. Average CS traffic, erlang, S2 (trf_12b) 257

Figure 541. Average CS traffic per BTS (trf_12d) 257

Figure 542. Handover/call % (trf_13b) 258

Figure 543. Intra-cell handover/call % (trf_13c) 258

Figure 544. HO / call % (trf_13d) 258

Figure 545. Handover/call % (trf_13e) 259

Figure 546. IUO, average TCH seizure length on super TRXs, S4 (trf_14b) 259

Figure 547. IUO, average TCH seizure length on regular TRXs, S4 (trf_15b) 260

Figure 548. Average TRX traffic, IUO, S4 (trf_16) 260

Figure 549. Average TRX TCH seizure length, IUO, S4 (trf_17) 260

Figure 550. Average TRX TCH seizure length, IUO, S4 (trf_17a) 260

Figure 551. Average TRX TCH seizure length, IUO, S4 (trf_17b) 260

Figure 552. TCH requests for a new call, S3 (trf_18) 261

Figure 553. TCH requests for a new call, S3 (trf_18a) 261

Figure 554. Peak busy TCH (trf_19) 261

Figure 555. Average unit load (trf_20) 261

Figure 556. Call time difference between TRXs, S4 (trf_21) 262

Figure 557. Call time difference between TRXs, S4 (trf_21a) 263

Figure 558. Number of mobiles located in a cell, BSC (trf_23a) 263

Figure 559. Total TCH seizure time (call time in seconds) (trf_24b) 264

Figure 560. Total TCH seizure time (call time in hours) (trf_24c) 264

Figure 561. SDCCH true seizures (trf_25) 265

Figure 562. SDCCH true seizures, S7 (trf_25a) 265

Figure 563. SDCCH true seizures for call and SS (trf_26) 265

Figure 564. SDCCH true seizures for call, SMS, SS (trf_27) 265

Figure 565. Peak busy SDCCH seizures (trf_28) 266

Figure 566. IUO layer usage % (trf_29) 266

Figure 567. SDCCH seizures (trf_30) 266


Figure 568. Call time (minutes) from p_nbsc_res_avail (trf_32) 266

Figure 569. Non-AMR call time from p_nbsc_rx_qual (trf_32a) 267

Figure 570. Call time from p_nbsc_rx_statistics (trf_32b) 267

Figure 571. SDCCH HO seizure % out of SDCCH seizure attempts (trf_33) 268

Figure 572. SDCCH assignment % out of SDCCH seizure attempts (trf_34) 268

Figure 573. TCH HO seizure % out of TCH HO seizure request (trf_35) 268

Figure 574. TCH norm seizure % out of TCH call request (trf_36) 268

Figure 575. TCH normal seizure % out of TCH call requests (trf_36a) 269

Figure 576. TCH FCS seizure % out of TCH FCS attempts (trf_37) 269

Figure 577. TTCH FCS (due to SDCCH congestion) seizure % out of SDCCH seizureattempts (trf_38) 269

Figure 578. TCH seizures for new calls (trf_39) 269

Figure 579. TCH seizures for new calls (trf_39a) 270

Figure 580. HTCH usage, S5 (trf_40) 270

Figure 581. MOC rate, S6 (trf_41) 270

Figure 582. MTC rate, S6 (trf_42) 271

Figure 583. TCH single band subscriber holding time, S6 (trf_43) 271

Figure 584. TCH dual band subscriber holding time, S6 (trf_44) 271

Figure 585. Share of single band traffic (trf_47) 271

Figure 586. Share of dual band traffic (trf_48) 272

Figure 587. Call retries due to A interface pool mismatch (trf_49) 272

Figure 588. HO retries due to A interface pool mismatch (trf_50) 272

Figure 589. TCH single band subscribers’ share of holding time, S6 (trf_51) 272

Figure 590. TCH dual band subscribers’ share of holding time, S6 (trf_52) 273

Figure 591. Calls started as FACCH call setup (trf_53) 273

Figure 592. SDCCH seizures (trf_54) 273

Figure 593. TCH normal seizures (trf_55) 273

Figure 594. Total FTCH seizure time (trf_56) 274

Figure 595. Total HTCH seizure time (trf_57) 274

Figure 596. Average TCH hold time for HSCSD, S7 (trf_58) 274

Figure 597. Average number of HSCSD users, S7HS (trf_60) 274



Figure 598. Total HSCSD TCH seizure time (call time, hours), S7HS (trf_61) 275

Figure 599. . . . . . . . . . . . . .Average upgrade pending time for HSCSD (trf_62) 275

Figure 600. . . . . . . . Average upgrade pending time due to congestion (trf_63) 275

Figure 601. . . . . . . . . . . . . Total reporting time of ph1 and ph2 mobiles (trf_64) 275

Figure 602. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Total TCH seizures (trf_65) 276

Figure 603. . . . . . . . . . . . . . . . .Net UL data traffic per timeslot, S9PS (trf_69a) 276

Figure 604. Net DL data traffic per timeslot, S9PS (trf_70a) 276

Figure 605. Average UL throughput per allocated timeslot, S9PS (trf_72b) 277

Figure 606. Average effective UL throughput per used tsl, S9PS (trf_72d) 278

Figure 607. Average effective UL throughput per used TSL, S10PS (trf_72f) 279

Figure 608. Average effective UL throughput per used TSL, S10PS (trf_72h) 280

Figure 609. . . . . Average DL throughput per allocated timeslot, S9PS (trf_73b) 281

Figure 610. Average effective DL throughput per used timeslot, S9PS (trf_73d) 281

Figure 611. Average effective DL throughput per used timeslot, S10PS (trf_73f) 282

Figure 612. Average effective DL throughput per used TSL, S10PS (trf_73g) 283

Figure 613. Total RLC data, S9PS (trf_74) 284

Figure 614. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Total RLC data, S9PS (trf_74a) 284

Figure 615. Total GPRS RLC data, S9PS (trf_74b) 284

Figure 616. Total GPRS RLC data (trf_74c) 285

Figure 617. . . . . . . . . . . . . . . . . . .GPRS territory UL utilisation, S9PS (trf_76b) 286

Figure 618. GPRS territory DL utilisation, S9PS (trf_77a) 287

Figure 619. UL GPRS traffic, S9PS (trf_78a) 287

Figure 620. UL PS traffic (trf_78c) 288

Figure 621. DL GPRS traffic, S9PS (trf_79a) 289

Figure 622. DL PS traffic (trf_79c) 289

Figure 623. TCH free margin, S9PS (trf_81) 290

Figure 624. Normal TCH usage % for CS (trf_83a) 290

Figure 625. Normal TCH usage ratio for CS (trf_83b) 290

Figure 626. TCH usage % for PS, S9PS (trf_84a) 291

Figure 627. Normal TCH usage % for PS, S9PS (trf_84b) 291

Figure 628. Total TCH usage % for CS, S9PS (trf_85) 291


Figure 629. Total TCH usage % for CS and PS, S9PS (trf_85b) 291

Figure 630. Total TCH usage ratio for CS and PS (trf_85d) 292

Figure 631. Free TCH %, S9PS (trf_86a) 292

Figure 632. Free TCH %, S10.5PS (trf_86c) 292

Figure 633. Total TCH % for PS (trf_87b) 293

Figure 634. Total TCH % for PS (trf_87c) 293

Figure 635. Total TCH % for dedicated PS, S9PS (trf_88b) 294

Figure 636. Total TCH % for dedicated PS, S9PS (trf_88c) 294

Figure 637. Average total UL throughput per used timeslot, S9PS (trf_89) 295

Figure 638. Average total UL throughput per used TSL, S10PS (trf_89a) 296

Figure 639. Average total DL throughput per used timeslot, S9PS (trf_90) 297

Figure 640. Average total DL throughput per used timeslot, S10PS (trf_90a) 298

Figure 641. SDCCH true seizures for call (trf_91) 298

Figure 642. Average HSCSD subchannel traffic, S7HS (trf_92) 298

Figure 643. Voice calls on SDCCH, S1 (trf_93) 298

Figure 644. TCH traffic, S1 (trf_94) 299

Figure 645. GPRS traffic sum, S9PS (trf_95a) 299

Figure 646. PS territory utilisation, S10.5PS (trf_96b) 301

Figure 647. Average CS traffic, normal TRXs, erlang, S2 (trf_97) 301

Figure 648. Average CS traffic, extended TRXs S2 (trf_98) 302

Figure 649. Average HSCSD traffic, normal TRXs, S7HS (trf_99) 302

Figure 650. Average HSCSD traffic, extended TRXs, S7HS (trf_100) 302

Figure 651. Average HTCH traffic, normal TRXs, S7HS (trf_102) 302

Figure 652. Average HTCH traffic, extended TRXs, S7HS (trf_103) 303

Figure 653. Average HSCSD main channel traffic, normal TRXs, S7HS (trf_104) 303

Figure 654. Average HSCSD main channel traffic, extended TRXs, S7HS(trf_105) 303

Figure 655. Average FTCH single traffic, normal TRXs, S7HS (trf_107) 303

Figure 656. Average FTCH single traffic, extended TRXs, S7HS (trf_108) 304

Figure 657. Peak busy TCH on normal TRXs (trf_109) 304

Figure 658. Peak busy TCH on normal TRXs (trf_110) 304



Figure 659. Normal TCH usage % for CS (trf_111) 304

Figure 660. Normal TCH usage ratio for CS, normal TRX (trf_111b) 305

Figure 661. Normal TCH usage % for CS (trf_112) 305

Figure 662. Normal TCH usage ratio for CS, extended TRXs (trf_112a) 305

Figure 663. CS call samples, non-AMR call (trf_113) 306

Figure 664. CS call samples, non-AMR call (trf_113a) 306

Figure 665. CS call samples, AMR call (trf_114) 306

Figure 666. CS call samples, AMR call (trf_114a) 307

Figure 667. TCH traffic time, non-AMR calls (trf_115) 307

Figure 668. TCH traffic time, non-AMR calls (trf_115a) 308

Figure 669. TCH traffic time, AMR calls (trf_116) 308

Figure 670. TCH traffic time, FR AMR calls (trf_117) 308

Figure 671. TCH traffic time, HR AMR calls (trf_118) 309

Figure 672. TCH traffic time, HR AMR calls (trf_118a) 309

Figure 673. TCH traffic time, all calls (trf_119) 309

Figure 674. TCH traffic share of non-AMR calls (trf_120) 310

Figure 675. TCH traffic share of non-AMR calls (trf_120a) 310

Figure 676. TCH traffic share of FR AMR calls (trf_121) 310

Figure 677. TCH traffic share of HR AMR calls (trf_122) 310

Figure 678. TCH traffic share of HR AMR calls (trf_122a) 310

Figure 679. Average effective UL timeslot throughput per TBF, S10PS (trf_123) 311

Figure 680. Average effective DL timeslot throughput per TBF, S10PS (trf_124) 312

Figure 681. MS specific flowrate (trf_125) 312

Figure 682. Total RLC payload data (Kbytes), MCS-n, S10.5PS (trf_131) 313

Figure 683. UL RLC data MCS-n, S10.5PS (trf_140) 313

Figure 684. DL RLC data MCS-n, S10.5PS (trf_141) 314

Figure 685. Normal TCH usage % for EGPRS, S10.5PS (trf_160) 314

Figure 686. UL EGPRS traffic, S10.5PS (trf_161) 315

Figure 687. UL EGPRS traffic (trf_161g) 315

Figure 688. UL EGPRS traffic (trf_161h) 316

Figure 689. DL EGPRS traffic, S10.5PS (trf_162) 317


Figure 690. DL EGPRS traffic (trf_162d) 317

Figure 691. DL EGPRS traffic (trf_162e) 318

Figure 692. DL EGPRS traffic (trf_162f) 319

Figure 693. Average SDCCH traffic, Area, S1 (trf_168) 319

Figure 694. Average SDCCH hold time, S10.5 (trf_169) 320

Figure 695. Average CS traffic, extended TRXs (trf_170) 320

Figure 696. Average FTCH hold time, S11.5 (trf_172) 320

Figure 697. Average FTCH single traffic, S7 (trf_192) 321

Figure 698. Average HTCH traffic, Area S7HS (trf_193) 321

Figure 699. Average HSCSD main channel traffic, Area S7HS (trf_194) 321

Figure 700. Average HSCSD subchannel traffic, Area S7HS (trf_195) 322

Figure 701. Total TCH seizure time (call time, hours), Area, (trf_196) 322

Figure 702. Normal TCH usage % for CS, Area, (trf_197) 322

Figure 703. Normal TCH usage % for PS, Area, S10.5PS (trf_198) 323

Figure 704. Normal TCH usage % for EGPRS, S10.5 (trf_199) 323

Figure 705. . . . . . . . . . . . . . . . . . . . . . . . . . . . Free TCH %, S10.5PS (trf_200) 323

Figure 706. GPRS territory utilisation, Area, S9PS (trf_201) 324

Figure 707. GPRS territory utilisation (trf_201a) 325

Figure 708. Average CS traffic, normal TRXs, erlang, Area, S2 (trf_202) 326

Figure 709. UL GPRS traffic (trf_205b) 326

Figure 710. DL GPRS traffic in EGPRS BTS (trf_208b) 327

Figure 711. GPRS UL Payload Data (trf_212c) 327

Figure 712. GPRS DL Payload Data (trf_213c) 328

Figure 713. EGPRS UL payload data (trf_214a) 328

Figure 714. EGPRS DL payload data (trf_215a) 329

Figure 715. Average GPRS UL LLC throughput (trf_216) 329

Figure 716. Average GPRS DL LLC throughput (trf_217) 329

Figure 717. Average EGPRS UL LLC throughput (trf_218) 330

Figure 718. Average EGPRS DL LLC throughput (trf_219) 330

Figure 719. Total LLC data volume (trf_220) 331

Figure 720. Share of GPRS UL in total LLC data volume (trf_225) 331



Figure 721. Share of GPRS DL in total LLC data volume (trf_226) 331

Figure 722. Share of EGPRS UL in total LLC data volume (trf_227) 332

Figure 723. Share of EGPRS DL in total LLC data volume (trf_228) 332

Figure 724. LLC data volume for TRECn (trf_229) 332

Figure 725. Share of TRECn in total LLC data volume (trf_230) 333

Figure 726. Average effective ACK GPRS UL throughput per used TSL(trf_233c) 334

Figure 727. Average effective ACK EGPRS UL throughput per used TSL(trf_234) 334

Figure 728. Average effective ACK GPRS DL throughput per used TSL(trf_235b) 335

Figure 729. PS traffic (trf_237b) 337

Figure 730. Average UL PS traffic (trf_238) 337

Figure 731. Average DL PS traffic (trf_239) 337

Figure 732. SDCCH seizures for MO calls, S2 (moc_1) 337

Figure 733. Successful MO speech calls, S3 (moc_2) 338

Figure 734. Successful MO data calls, S3 (moc_3) 338

Figure 735. MO call success ratio, S6 (moc_4) 338

Figure 736. MO speech call attempts, S3 (moc_5) 339

Figure 737. MO call bids, S2 (moc_6) 339

Figure 738. SDCCH seizures for MT calls, S2 (mtc_1) 339

Figure 739. Successful MT speech calls (mtc_2) 340

Figure 740. Successful MT data calls, S3 (mtc_3) 340

Figure 741. MT call success ratio, S6 (mtc_4) 340

Figure 742. MT speech call attempts (mtc_5) 340

Figure 743. MT call attempts, S2 (mtc_6) 341

Figure 744. Number of paging messages sent, S2 (pgn_1) 341

Figure 745. Paging buffer size average, S1 (pgn_2) 342

Figure 746. Average paging buffer space, S1 (pgn_3) 342

Figure 747. Average free space of paging GSM buffer area, S1 (pgn_3a) 342

Figure 748. Paging success ratio, S1 (pgn_4) 343

Figure 749. . . . . . . Average paging buffer air interface occupancy, S7 (pgn_5) 343


Figure 750. Average paging buffer Gb occupancy, S7PS (pgn_6) 343

Figure 751. Average air interface DRX buffer load, due to paging, S7 (pgn_7) 343

Figure 752. Average air interface DRX buffer load, due to DRX AG, S7 (pgn_8) 344

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

Figure 754. Average free space of paging GPRS buffer area, S9 (pgn_10) 344

Figure 755. Average paging buffer Gb occupancy, S7PS (pgn_11) 345

Figure 756. SMS establishment failure % (sms_1) 345

Figure 757. SMS TCH establishment failure % (sms_2) 345

Figure 758. SMS SDCCH establishment failure % (sms_3) 346

Figure 759. SMS establishment attempts (sms_4) 346

Figure 760. SMS SDCCH establishment attempts (sms_5) 346

Figure 761. SMS TCH establishment attempts (sms_6) 346

Figure 762. DR, outgoing attempts, S3 (dr_1) 346

Figure 763. DR attempts, S3 (dr_1a) 347

Figure 764. DR, incoming attempts, S3 (dr_2) 347

Figure 765. DR, outgoing success to another cell, S3 (dr_3) 347

Figure 766. DR, incoming success from another cell, S3 (dr_4) 347

Figure 767. DR, intra-cell successful HO, S3 (dr_5) 348

Figure 768. % of new calls successfully handed over to another cell by DR, S3(dr_6) 348

Figure 769. DR, outgoing to another cell, failed, S3 (dr_7) 348

Figure 770. DR, intra-cell failed, S3 (dr_8) 348

Figure 771. TCH availability %, S4 (ava_1a) 349

Figure 772. TCH availability %, S9 (ava_1c) 349

Figure 773. TCH availability %, S9 (ava_1d) 350

Figure 774. TCH availability %, S9 (ava_1e) 350

Figure 775. TCH availability ratio (ava_1g) 351

Figure 776. Average available TCH, S1 (ava_2) 351

Figure 777. Average available SDCCH, S1 (ava_3) 351

Figure 778. SDCCH availability %, S4 (ava_4) 352

Figure 779. SDCCH availability %, S4 (ava_4a) 352



Figure 780. Average available FTCH in area, S1 (ava_5) 352

Figure 781. DMR availability %, S6 (ava_6) 353

Figure 782. DN2 availability %, S6 (ava_7) 353

Figure 783. TRU availability %, S6 (ava_8) 353

Figure 784. Average defined HTCH, S1 (ava_9) 353

Figure 785. SC ET availability %, S7 (ava_10) 354

Figure 786. BSC ET availability %, S7 (ava_11) 354

Figure 787. SC TCSM availability %, S7 (ava_12) 354

Figure 788. BSC TCSM availability %, S7 (ava_13) 354

Figure 789. TRE availability %, S6 (ava_14) 355

Figure 790. Average CS territory, S9 (ava_15) 355

Figure 791. Average PS territory, S9PS (ava_16a) 356

Figure 792. Average PS territory (ava_16b) 356

Figure 793. Average available dedicated GPRS channels, S9PS (ava_17) 357

Figure 794. Average available dedicated GPRS channels, S9PS (ava_17a) 357

Figure 795. TRE-SEL availability %, S6 (ava_20) 357

Figure 796. Number of timeslots available for CS traffic, S9 (ava_21) 358

Figure 797. Number of timeslots available for CS traffic on normal TRXs, S9(ava_21a) 358

Figure 798. Number of HR timeslots available, S9 (ava_22) 358

Figure 799. Number of HR timeslots available, S9 (ava_22a) 359

Figure 800. Number of FR timeslots available, S9 (ava_23) 359

Figure 801. Number of FR timeslots available, S9 (ava_23a) 359

Figure 802. Number of dual timeslots available, S9 (ava_24) 359

Figure 803. Number of dual timeslots available, S9 (ava_24a) 360

Figure 804. Average number of available TCH timeslots, S9 (ava_25a) 360

Figure 805. Number of available TCH timeslots, PS and CS common, S9(ava_26) 360

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

Figure 807. Average CS TCH in normal TRXs, S9 (ava_28) 361

Figure 808. Average CS TCH in normal TRXs, S9 (ava_28a) 362


Figure 809. Average available CS TCH in extended TRXs, S9 (ava_29) 362

Figure 810. Number of HR tsls available, normal TRXs, S9 (ava_30) 362

Figure 811. Number of HR tsls available, extended TRXs S9 (ava_31) 363

Figure 812. Number of FR timeslots available, normal TRXs, S9 (ava_32) 363

Figure 813. Number of FR timeslots available, extended TRXs, S9 (ava_33) 364

Figure 814. Number of dual timeslots available, normal TRXs, S9 (ava_34) 364

Figure 815. Number of dual timeslots available, extended TRXs, S9 (ava_35) 364

Figure 816. GPRS enable time %, S10 (ava_36) 364

Figure 817. Number of HR TSLs available, extended TRXs, Area, S9 (ava_37) 365

Figure 818. Number of FR TSLs available, extended TRXs, Area, S9 (ava_38) 365

Figure 819. Average number of available TCH TSLs, Area, S9 (ava_39) 366

Figure 820. Number of dual TSLs available, extended TRXs, Area, S9 (ava_40) 366

Figure 821. Number of dual TSLs available, normal TRXs, Area, S9 (ava_41) 367

Figure 822. Number of HR TSLs available, normal TRXs, Area, S9 (ava_42) 367

Figure 823. Number of FR TSLs available, normal TRXs, Area, S9 (ava_43) 368

Figure 824. Number of FR TSLs available, normal TRXs (ava_43a) 368

Figure 825. Average PS territory, Area, S9PS (ava_44) 369

Figure 826. Average available SDCCH, Area, S1 (ava_45) 369

Figure 827. Average available SDCCH 369

Figure 828. Average available SDCCH, normal TRX, Area, S1 (ava_48) 369

Figure 829. Average available SDCCH, extended TRX, Area, S1 (ava_49) 370

Figure 830. Number of available TCH TSLs, PS and CS common, Area S9(ava_50) 370

Figure 831. Average available dedicated GPRS channels, Area S9PS (ava_51) 370

Figure 832. Average CS TCH in normal TRXs, Area S9 (ava_52) 371

Figure 833. Average available CS TCH in extended TRXs, Area S9 (ava_53) 371

Figure 834. TCH availability %, Area, S9 (ava_55) 372

Figure 835. TCH availability % (ava_55b) 372

Figure 836. Average defined HTCH (ava_58) 372

Figure 837. Average defined FTCH (ava_59) 373

Figure 838. Number of TSLs available for CS traffic on normal TRXs, Area, S9(ava_62) 373



Figure 839. SDCCH availability %, Area S4 (ava_63a) 373

Figure 840. Data service availability ratio (ava_68) 374

Figure 841. Average unavailable TSL per BTS, S1 (uav_1) 375

Figure 842. Average unavailable TSL per BTS, S1 (uav_1a) 375

Figure 843. Average unavailable TSL per BTS, S1 (uav_1b) 375

Figure 844. Total outage time (uav_2) 375

Figure 845. Number of outages (uav_3) 376

Figure 846. Share of unavailability due to user (uav_4) 376

Figure 847. Share of unavailability due to internal reasons (uav_5) 376

Figure 848. Share of unavailability due to external reasons (uav_6) 377

Figure 849. TRX unavailability time due to user (uav_7) 377

Figure 850. TRX unavailability time due to internal reasons (uav_8) 377

Figure 851. TRX unavailability time due to external reasons (uav_9) 377

Figure 852. Average unavailable SDCCH, S5 (uav_10) 378

Figure 853. Average unavailable TCH, S5 (uav_11a) 378

Figure 854. Average bearer unavailability, S9PS (uav_12) 378

Figure 855. Average unavailable TCH on normal TRXs, S5 (uav_13) 378

Figure 856. Average unavailable TCH on extended TRXs, S5 (uav_14) 379

Figure 857. Average unavailable TCH on normal TRXs, Area, S5 (uav_15) 379

Figure 858. Average unavailable TCH on extended TRXs, Area, S5 (uav_16) 379

Figure 859. Average unavailable TCH, Area, S5 (uav_17) 379

Figure 860. Average unavailable SDCCH, normal TRX, Area level S5 (uav_20) 380

Figure 861. Average unavailable SDCCH, extended TRX, Area level S5(uav_21) 380

Figure 862. Average unavailable SDCCH (uav_22) 380

Figure 863. Number of LU attempts, S1 (lu_1) 380

Figure 864. Average of LU attempts per hour, S1 (lu_2) 381

Figure 865. Number of LU attempts, S1 (lu_3) 381

Figure 866. LU success %, S6 (lsr_2) 381

Figure 867. Emergency calls, S6 (ec_1) 382

Figure 868. Emergency call success %, S6 (ecs_1) 382


Figure 869. Call re-establishment attempts, S6 (re_1) 382

Figure 870. Call re-establishments, S6 (re_2) 382

Figure 871. Call re-establishment success %, S6 (res_1) 383

Figure 872. DL BER, S1 (dlq_1) 383

Figure 873. DL cumulative quality % in class X, S1 (dlq_2) 384

Figure 874. DL cumulative quality % in class X, S1 (dlq_2a) 384

Figure 875. DL quality %, FER based, S10 (dlq_3) 384

Figure 876. DL cumulative quality % in class X, HR AMR, S10 (dlq_4) 385

Figure 877. DL cumulative quality % in class X, FR AMR, S10 (dlq_5) 385

Figure 878. DL cumulative quality % in class X,S10 (dlq_6) 386

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

Figure 880. DL quality 0-5 %, FR, FER based, S10 (dlq_8) 386

Figure 881. DL quality 0-5 % EFR, FER based, S10 (dlq_9) 387

Figure 882. DL quality 0-5 % AMR HR, FER based, S10 (dlq_10) 387

Figure 883. DL quality 0-5 % AMR FR, FER based, S10 (dlq_11) 387

Figure 884. UL BER, S1 (ulq_1) 387

Figure 885. UL cumulative quality % in class X, S1 (ulq_2) 388

Figure 886. UL cumulative quality % in class X, S1 (ulq_2a) 388

Figure 887. UL quality %, FER based, S10 (ulq_3) 389

Figure 888. UL cumulative quality % in class X, HR AMR, S10 (ulq_4) 389

Figure 889. UL cumulative quality % in class X, FR AMR, S10 (ulq_5) 389

Figure 890. UL cumulative quality % in class X, non-AMR S10 (ulq_6) 390

Figure 891. UL quality 0-5 %, HR, FER based, S10 (ulq_7) 390

Figure 892. UL quality 0-5 %, FR, FER based, S10 (ulq_8) 391

Figure 893. UL quality 0-5 % EFR, FER based, S10 (ulq_9) 391

Figure 894. UL quality 0-5 % AMR HR, FER based, S10 (ulq_10) 391

Figure 895. UL quality 0-5 % AMR FR, FER based, S10 (ulq_11) 392

Figure 896. Share % per range, S4 (dll_1) 392

Figure 897. Sorting factor for undefined adjacent cell, S4 (dll_2) 392

Figure 898. Share % per range, S4 (ull_1) 393

Figure 899. Average MS power, S2 (pwr_1) 393



Figure 900. Average MS power, S2 (pwr_1b) 393

Figure 901. Average BS power, S2 (pwr_2) 393

Figure 902. Average DL signal strength, S2 (lev_1) 394

Figure 903. Average DL signal strength, S2 (lev_1a) 394

Figure 904. Average UL signal strength, S2 (lev_2) 394

Figure 905. Average UL signal strength, S2 (lev_2a) 394

Figure 906. Average MS-BS distance (dis_1) 395

Figure 907. Average MS-BS distance (dis_1a) 395

Figure 908. MS-BS distance class upper range (dis_3a) 396

Figure 909. Link balance, S1 (lb_1) 396

Figure 910. Share in acceptance range, S4 (lb_2) 396

Figure 911. Share in normal, S4 (lb_3) 396

Figure 912. Share in MS limited, S4 (lb_4) 397

Figure 913. Share in BS limited, S4 (lb_5) 397

Figure 914. Share in maximum power, S4 (lb_6) 397

Figure 915. Average MS power attenuation, S2 (lb_7) 397

Figure 916. Average MS power, S2 (lb_7b) 398

Figure 917. Average UL signal strength, S2 (lb_9) 398

Figure 918. Average DL signal strength, S2 (lb_10) 398

Figure 919. Average MS power attenuation, S2 (lb_11) 398

Figure 920. Average BS power attenuation, S2 (lb_12) 399

Figure 921. Average link imbalance, S2 (lb_13) 399

Figure 922. SDCCH access probability, before FCS (csf_1) 399

Figure 923. SDCCH access probability (csf_1a) 400

Figure 924. SDCCH success ratio (csf_2a) 401

Figure 925. SDCCH success ratio, area (csf_2e) 401

Figure 926. SDCCH success ratio, BTS, S6 (csf_2g) 402

Figure 927. SDCCH success ratio, BTS (csf_2i) 403

Figure 928. SDCCH success ratio (csf_2k) 404

Figure 929. SDCCH success ratio, area (csf_2m) 405

Figure 930. SDCCH success ratio, BTS (csf_2n) 406


Figure 931. SDCCH success ratio, area, S10.5 (csf_2o) 407

Figure 932. TCH access probability without DR (csf_3a) 407

Figure 933. TCH access probability without DR and Q (csf_3b) 408

Figure 934. TCH access probability without Q (csf_3c) 408

Figure 935. TCH access probability, real (csf_3d) 409

Figure 936. TCH access probability without DR (csf_3i) 409

Figure 937. TCH access probability without DR and Q (csf_3j) 409

Figure 938. TCH access probability, real (csf_3k) 410

Figure 939. TCH access probability, real (csf_3l) 410

Figure 940. TCH access probability without DR and Q (csf_3m) 411

Figure 941. TCH access probability, real, S11.5 (csf_3o) 411

Figure 942. TCH access probability, S11.5 (csf_3p) 411

Figure 943. TCH success ratio, area, before call re-establisment (csf_4o) 412

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

Figure 945. TCH success ratio, BTS, before call re-establisment (csf_4q) 413

Figure 946. TCH success ratio, BTS, after call re-establishment (csf_4r) 414

Figure 947. TCH success ratio, BTS, after call re-establishment (csf_4t) 415

Figure 948. TCH success ratio, area, before call re-establishment, S7(csf_4u) 415

Figure 949. TCH success ratio, area, after call re-establishment, S7 (csf_4v) 416

Figure 950. TCH success ratio, BTS, after call re-establishment (csf_4x) 417

Figure 951. TCH success ratio, BTS, before call re-establishment (csf_4y) 417

Figure 952. Activation related SDCCH access probability, S7, (csf_12) 418

Figure 953. SDCCH call success probability, S10.5 (csf_13a) 418

Figure 954. TCH success ratio, before call re-establishment (csf_41) 419

Figure 955. TCH success ratio, after call re-establishment (csf_42) 419

Figure 956. Reuse pattern (cnf_1) 420

Figure 957. Reuse pattern, S1 (cnf_2) 420

Figure 958. Average successful queuing time for WPS user, S11 (wps_1) 420

Figure 959. Average occupied FTCHs for WPS user, S11 (wps_2) 420

Figure 960. Average occupied HTCHs for WPS user, S11 (wps_3) 421

Figure 961. Average BSC - BSC delay, S11 (dfca_1) 421



Figure 962. Total DFCA assignment requests, S11 (dfca_2) 421

Figure 963. DFCA assignment success ratio, S11 (dfca_3) 422

Figure 964. Most optimal DFCA assignment success ratio, S11 (dfca_4) 422

Figure 965. Total soft-blocked DFCA assignments, S11 (dfca_5) 422

Figure 966. DFCA soft-blocking ratio, S11 (dfca_6) 423

Figure 967. DFCA soft-blocking ratio for C/I reason, S11 (dfca_7) 423

Figure 968. DFCA soft-blocking ratio for C/N reason, S11 (dfca_8) 423

Figure 969. Total number of DFCA channel assignments, S11 (dfca_9) 424

Figure 970. Peak BSC - BSC delay (dfca_10) 424

Figure 971. Total NCCR attempts (nccr_1) 425

Figure 972. Total NCCR setup failures (nccr_2) 425

Figure 973. NCCR setup failure ratio (nccr_3) 425

Figure 974. Total started NCCRs (nccr_4) 426

Figure 975. Total failed NCCRs (nccr_5) 426

Figure 976. Share of failed NCCRs returned to old cell (nccr_6) 426

Figure 977. Share of started NCCRs for GPRS MS due to power budget in totalNCCRs (nccr_7) 427

Figure 978. Share of started NCCRs for EGPRS MS due to power budget in totalNCCRs (nccr_8) 427

Figure 979. Share of started NCCRs due to ISNCCR service in total NCCRs(nccr_9) 427

Figure 980. Share of started NCCRs due to ISNCCR coverage in total NCCRs(nccr_10) 428

Figure 981. Share of started NCCRs due quality control in total NCCRs(nccr_11) 428

Figure 982. Number of network controlled cell reselections compared to data amount(nccr_12) 428

Figure 983. Successful NCCRs ratio (nccr_13) 429

Figure 984. Average duration of successful NCCRs (nccr_14) 429

Figure 985. Average duration of successful NCCRs (nccr_14a) 429

Figure 986. PFC creation success ratio (pfc_1) 430

Figure 987. PFC transfer failure ratio (pfc_8) 430

Figure 988. Share of abnormal PFC releases (pfc_11) 430


Figure 989. Number of successful PFC creations (pfc_13) 431

Figure 990. Total started quality control actions (qca_1) 431

Figure 991. Total started TBF reallocation (qca_2) 431

Figure 992. Total started NCCRs (qca_3) 432

Figure 993. Total started PFC Modify (qca_4) 432

Figure 994. Total started PFC delete (qca_5) 432

Figure 995. Share of TBF reallocations in total started QC actions (qca_6) 433

Figure 996. Share of NCCRs in total started QC actions (qca_7) 433

Figure 997. Share of PFC modifications in total started QC actions (qca_8) 433

Figure 998. Share of PFC deletion in total started QC actions (qca_9) 433

Figure 999. Share of started TBF reallocations due to throughput (qca_10) 434

Figure 1000. Share of started TBF reallocations due to BLER (qca_11) 434

Figure 1001. Share of started TBF reallocations due to RB bitrate (qca_12) 434

Figure 1002. Share of started NCCRs due to throughput (qca_13) 434

Figure 1003. Share of started NCCRs due to BLER (qca_14) 435

Figure 1004. Share of started NCCRs due to RB bitrate (qca_15) 435

Figure 1005. Share of started PFC modification due to throughput (qca_16) 435

Figure 1006. Share of started PFC modification due to BLER (qca_17) 435

Figure 1007. Share of started PFC modification due to RB bitrate (qca_18) 436

Figure 1008. Share of started PFC deletion due to throughput (qca_19) 436

Figure 1009. Share of started PFC deletion due to BLER (qca_20) 436

Figure 1010. Share of started PFC deletion due to RB bitrate (qca_21) 436

Figure 1011. Ratio of discarded received packets (gbip_1) 437


About this manual

Note

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

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

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

The information contained in this document relates to BSS Network Doctorsoftware version 4.1.2 and Nokia NetAct release OSS4. This version of BSSNetwork Doctor offers compatibility with BSC version S11.5 measurements.This document should not be used with any other versions of the Nokia NetActor Nokia BSC software.

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

This chapter covers the following topics:

• Summary of changes

• What you need to know first

• Where to find more

• Typographic conventions

• Concepts and terminology



1.1 Summary of changes

In this Change Delivery OSS_CD_1470

As a result of fault corrections made to BSS Network Doctor software version4.1.2, the following changes have been made to this document:

New formulas

• AVA

- ava_52; an alternative formula added

• LLC

- llc_3a

• MSL

- msl_9a, msl_10a, msl_17a, msl_18a

• NCCR

- nccr_14a

• TBF

- tbf_15a, tbf_16a

In the previous Change Delivery OSS_CD_1010

As a result of the changes made to BSS Network Doctor software from version4.0.2 to 4.0.3, the following changes have been made into this document:

New formulas

• AVA

- ava_68

• DAP

- dap_7a, dap_7b, dap_8c, dap_9, and dap_10

• HFR

- hfr_2a

• LLC

- llc_2a and llc_3


About this manual

• RLC

- rlc_6e, rlc_6f, rlc_7b, rlc_8f, rlc_8e, rlc_9b, rlc_14a, rlc_15a,rlc_20b, rlc_20c, rlc_27, rlc_28, rlc_29, rlc_30, rlc_32, rlc_33,rlc_34, rlc_35, rlc_36, rlc_37, rlc_42a, rlc_43a, rlc_44a, rlc_45a,rlc_46a, rlc_47a, rlc_48a, rlc_49a, rlc_54b, rlc_55b, and rlc_60

• TBF

- tbf_27d, tbf_28d, tbf_57a, tbf_58a, tbf_63, and tbf_64

• TRF

- trf_74c, trf_111b, trf_112a, trf_113a, trf_114a, trf_115a, trf_120a,trf_122a, trf_161h, trf_162e, trf_162f, trf_170, trf_201a, trf_205b,trf_212c, trf_213c, trf_214a, trf_233c, trf_234, trf_235b, andtrf_237b

1.2 What you need to know first

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

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

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

1.3 Where to find more

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

Other BSS Network Doctor documents

• Administering BSS Network Doctor, DN98619369, for systemadministrator’s tasks related to running BSS Network Doctor.

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

OSS NED library documents

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



Other Nokia documents

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

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

1.4 Typographic conventions

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

1.4.1 Text styles

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

Table 1. Text styles in this document

Style Explanation

Initial Upper-caseLettering

Application names

Italicised text Emphasis

State, status or mode

Courier File and directory names

Names of database tables

Parameters

User names

System output

User input

UPPER-CASELETTERING

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

Bold text User interface components

Initial Upper-caseLettering in Italics

Referenced documents

Referenced sections and chapters within a document

<bracketed text> Variable user input


About this manual

1.5 Terms and concepts

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

1.5.1 Abbreviations

Table 2. Abbreviations

Abbreviation Explanation

AG Access Grant

AMR Adaptive Multirate

BCCH Broadcast Control Channel

BCF Base Control Function

BER Bit Error Ratio

BSC Base Station Controller

BSS Base Station Subsystem

BTS Base Transceiver Station

CI Cell Identity

DL Downlink

DR Directed Retry

FCS Frame Check Sequence

GPRS General Packet Radio Service

HO Handover

HSCSD High Speed Circuit Switched Data

IUO Intelligent Underlay Overlay

KPI Key Performance Indicator

LU Location Update

MML Man-machine Language

MOC Mobile Originated Call

MR Maintenance Region

MS Mobile Station

MSC Mobile Services Switching Centre

OMC Operation and Maintenance Centre



1.5.2 Terms

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

PBS Position Based Services

PI Performance Indicator

PLMN Public Land Mobile Network

PM Performance Management

RACH Random Access Control Channel

SDCCH Stand Alone Dedicated Control Channel

SMS Short Message Service

SQL Standard Query Language

SS Supplementary Service

TCH Traffic Channel

TR Trunk Reservation

TRX Transceiver

TSL Timeslot

UL Uplink

Table 2. Abbreviations (Continued)

Abbreviation Explanation

Table 3. Terms used in this document

Term Explanation

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

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

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

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


About this manual

For any other terms, refer to Glossary, DN9763965.

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

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

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

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

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

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

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

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

SQL*Plus An interactive program for accessing the database.

Stand-alone Dedicated ControlChannel (SDCCH)

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

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

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

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

Table 3. Terms used in this document (Continued)

Term Explanation


BSS counter formulas

Note

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

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

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

2.1 Additional GPRS channels (ach)

Additional GPRS channel use, S9PS (ach_1)

Use: BTS level, especially BH values can be used for adjusting theCDEF parameter.

Example: If the value equals to one, on average one additional timeslothas been used for GPRS. If the situation continues, it indicatesa need to extend the default or the dedicated territory.

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

Experiences on use: ach_1 is included in ava_16.

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



----------------------------------------------------------- =period duration

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

Counters from table(s):p_nbsc_res_avail

Unit: timeslot

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

Additional GPRS channel use (ach_1a)

Use: Used on Segment/Area level, especially BH values can beused for adjusting the CDEF parameter.

Example: If the value equals to one, on average one additional timeslothas been used for GPRS. If the situation continues, it indicatesthe need to extend the default or dedicated territory.

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

Experiences on use: ach_1 is included in ava_16.

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

total hold time of all additional GPRS ch. seizures (sec)----------------------------------------------------------- =total segment time over the area

sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100---------------------------------------(count(distinct period_duration)count(distinct period_start_time) *60)

Counters from table(s):a = p_nbsc_res_avail

Figure 2. Additional GPRS channel use (ach_1a)

Average additional GPRS channel hold time, S9PS (ach_2)

Use: If the value is high, more default area is needed.

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

sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100



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

Counters from table(s):p_nbsc_res_availUnit: sec

Figure 3. 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 (acase of territory downgrade).

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

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


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

Additional GPRS channels seized (ach_3a)

Use: Indicates how many times an additional channel has beenreleased (a case of territory downgrade).

Known problems: Shows slightly incorrect values in the case of an extendedcell.

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

Counters from table(s):a= p_nbsc_res_avail

Figure 5. Additional GPRS channels seized (ach_3a)

Total additional GPRS channel hold time, S9PS (ach_4)

Use: How many times an additional channel has been released (acase of territory downgrade).

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

sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100

Counters from table(s):



p_nbsc_res_availUnit: sec

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

2.2 Multislot (msl)

Distribution of UL multislot requests, S9PS (msl_1)

Use: Indicates the share of a multislot request type to all multislotrequests.

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

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

req_X_TSL_UL = one of the componentsof the denominator.

Counters from table(s):p_nbsc_packet_control_unit

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

Distribution of DL multislot requests, S9PS (msl_2)


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

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

req_X_TSL_UL = one of the components of the denominator.


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

Distribution of UL multislot allocations, S9PS (msl_3)


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

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

req_X_TSL_UL = one of the components of the denominator.




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

Distribution of DL multislot allocations, S9PS (msl_4)


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

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

req_X_TSL_DL = one of the components of the denominator.


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

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


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

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


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

Ratio of unreserved GPRS DL TSL requests, S9PS (msl_6)


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

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


Figure 12. Ratio of unreserved GPRS DL TSL requests, S9PS (msl_6)



UL multislot allocations, S9PS (msl_9)

Use: Total number of multislot allocations in UL.

sum(alloc_1_TSL_UL+ alloc_2_TSL_UL+ alloc_3_TSL_UL

+ alloc_4_TSL_UL+ alloc_5_8_TSL_UL)


Figure 13. UL multislot allocations, S9PS (msl_9)

UL multislot allocations (msl_9a)

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_TSL_UL+ alloc_6_TSL_UL+ alloc_7_TSL_UL+ alloc_8_TSL_UL)


Figure 14. UL multislot allocations (msl_9a)

DL multislot allocations, S9PS (msl_10)

Use: Total number of multislot allocations in DL.

sum(alloc_1_TSL_DL+ alloc_2_TSL_DL+ alloc_3_TSL_DL

+ alloc_4_TSL_DL+ alloc_5_8_TSL_DL)


Figure 15. DL multislot allocations, S9PS (msl_10)

DL multislot allocations (msl_10a)

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_TSL_DL+ alloc_6_TSL_DL+ alloc_7_TSL_DL+ alloc_8_TSL_DL)


Figure 16. DL multislot allocations (msl_10a)

Average number of allocated timeslots, UL S9PS (msl_11)

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


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

Average number of allocated timeslots, DL S9PS (msl_12)

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


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

Average number of requested UL timeslots, S9PS (msl_13)

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

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


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



Average number of requested DL timeslots, S9PS (msl_14)

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

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


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

UL multislot allocation %, S9PS (msl_15a)

Use: Indicates how well the requested multislots could beallocated.

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

100* average allocated tsl / average requested tsl % =

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

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

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


Figure 21. UL multislot allocation %, S9PS (msl_15a)

DL multislot allocation %, S9PS (msl_16a)

Use: Indicates how well the requested multislots could beallocated.

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

100* average allocated tsl / average requested tsl % =

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

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

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




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

UL multislot requests, S9PS (msl_17)

Use: Total number of multislot requests in UL.



Figure 23. UL multislot requests, S9PS (msl_17)

UL multislot requests (msl_17a)

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_TSL_UL+req_6_TSL_UL+req_7_TSL_UL+req_8_TSL_UL)


Figure 24. UL multislot requests (msl_17a)

DL multislot requests, S9PS (msl_18)

Use: Total number of multislot requests in DL.



Figure 25. DL multislot requests, S9PS (msl_18)

DL multislot requests (msl_18a)

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_TSL_DL+req_6_TSL_DL+req_7_TSL_DL+req_8_TSL_DL)


Figure 26. DL multislot requests (msl_18a)

2.3 Temporary block flow (tbf)

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

Use: Indicates the average number of LLC data blocks pernormally released TBF.

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


Figure 27. 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 pernormally released TBF.

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


Unit: second

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

Average UL TBF duration, S9PS (tbf_5)

Known problems: The unit has changed to 10 ms in BSC CD 1.2. After thattbf_5a is needed.

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




Unit: second

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


Unit: second

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

Average DL TBF duration, S9PS (tbf_6a)

Use: Counted from the normally released TBFs.Known problems: Contains part of TBF establishment delays.

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


Unit: second

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

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

sum(ave_dur_ul_tbf_unack_mode_sum/100)-------------------------------------sum(ave_dur_ul_tbf_unack_mode_den)


Unit: second

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



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

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


Unit: second

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

UL mlslot allocation blocking, S9PS (tbf_15)

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

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

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



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

UL mlslot allocation blocking (tbf_15a)

Use: If the blocking is met regularly, there is need either to expandthe territory (CS traffic low) or TCH capacity (CS traffichigh).


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_TSL_UL + req_6_TSL_UL + req_7_TSL_UL + req_8_TSL_UL)




Figure 35. UL mlslot allocation blocking (tbf_15a)

DL mlslot allocation blocking, S9PS (tbf_16)

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


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



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

DL mlslot allocation blocking (tbf_16a)

Use: If the blocking is met regularly, there is need either to expandthe territory (CS traffic low) or TCH capacity (CS traffichigh).


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_TSL_DL + req_6_TSL_DL + req_7_TSL_DL + req_8_TSL_DL)


Figure 37. DL mlslot allocation blocking (tbf_16a)



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

Use: In GPRS the CS takes priority over the radio interfaceresources outside the dedicated territory. This KPI indicatesthe impact of CS traffic on PS (TBF drops) when radiointerface capacity (TCH) is not sufficient and CS traffic takesthe capacity from PS traffic by force.

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

sum(Nbr_of_UL_TBF)


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

UL TBF releases due to CS traffic % (tbf_19a)


sum(UL_TBF_rel_due_CSW_traffic)100*----------------------------------------------------------------------------% sum(Nbr_of_UL_TBF-UL_TBF_Establishment_Failed-UL_EGPRS_TBF_REL_DUE_NO_RESP)


Figure 39. UL TBF releases due to CS traffic % (tbf_19a)

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


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

sum(Nbr_of_DL_TBF)


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



DL TBF releases due to CS traffic % (tbf_20a)

Use: In GPRS the CS takes priority over the radio interfaceresources outside the dedicated territory. This KPI indicatesthe impact of CS traffic on PS (TBF drops) when the capacityof radio interface (TCH) is not sufficient and CS traffic takesthe capacity from PS traffic by force.

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

sum(Nbr_of_DL_TBF-DL_TBF_Establishment_Failed-DL_EGPRS_TBF_REL_DUE_NO_RESP)


Figure 41. DL TBF releases due to CS traffic % (tbf_20a)

UL drops per 10 Kbytes, MS lost, S9PS (tbf_27a)

Use: This KPI tries to build something similar that we are used toseeing in the CS side to indicate the bad radio conditions thataffect the connection i.e. drops in ratio to volume.

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

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


Figure 42. UL drops per 10 Kbytes, MS lost, S9PS (tbf_27a)

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

Use: This KPI tries to build something similar that we are used toseeing in the CS side to indicate the bad radio conditions thataffect the connection i.e. drops in ratio to volume.



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

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


Unit: drops per 10Kbytes

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

UL drops per 10 Kbytes, MS lost, S10.5PS (tbf_27c)

Use: To indicate the bad radio conditions that affect the connectioni.e. drops in ratio to volume.

Known problems: 1) Slow cell reselections (flushes) can increment thenumerator.2) Combining TBF related information (numerator) to RLCblock information (numerator) causes problems, because thebehaviour of TBFs is quite independent of the RLC blocks(TBF length varies strongly).

sum(UL_TBF_rel_due_no_resp_MS)------------------------------------------------------------(sum(rlc_data_blocks_ul_cs1*20 + rlc_data_blocks_ul_cs2*30 )

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

Where xx = (UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE)

Counters from table(s):p_nbsc_packet_control_unitp_nbsc_coding_scheme


Figure 44. UL drops per 10 Kbytes, MS lost, S10.5PS (tbf_27c)



UL drops per 10 kbytes, MS lost (tbf_27d)

Description: UL TBF drops per 10 kbytes.Use: To indicate the bad radio conditions that affect the

connection, which means drops in ratio to volume.Known problems: 1) Slow cell reselections (flushes) can increment the

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

sum(a.UL_TBF_rel_due_no_resp_MS)---------------------------------sum(a.rlc_data_blocks_ul_cs1*20

+ a.rlc_data_blocks_ul_cs2*30+ sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148+ sum over MCS-11 (xx)*36+ sum over MCS-12 (xx)*50)/ 10240

Where xx = (b.UL_RLC_BLOCKS_IN_ACK_MODE + b.UL_RLC_BLOCKS_IN_UNACK_MODE)

Counters from table(s):a = p_nbsc_packet_control_unitb = p_nbsc_coding_scheme

Unit: Numbers

Figure 45. UL drops per 10 kbytes, MS lost (tbf_27d)

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

Use: See tbf_27bKnown problems: 1) Slow cell reselections (flushes) can increment the

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

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




p_nbsc_packet_control_unit

Unit: Numbers

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

DL drops per 10 Kbytes, MS lost, S9PS (tbf_28b)

Use: See tbf_27b.Known problems: 1) Slow cell reselections (flushes) can increment the

numerator.2) Combining TBF related info (numerator) to RLC blockinfo (numerator) causes problems because the behaviour ofTBFs is quite independent of the RLC blocks (TBF lengthvaries strongly).3) In S10 the EGPRS modulation coding scheme countershave to be added to the denominator.

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


Unit: Drops per 10Kbytes

Figure 47. DL drops per 10 Kbytes, MS lost, S9PS (tbf_28b)

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

Use: See tbf_27b.Known problems: 1) Slow cell reselections (flushes) can increment the

numerator.2) Combining TBF related info (numerator) to RLC blockinfo (numerator) causes problems because the behaviour ofTBFs is quite independent of the RLC blocks (TBF lengthvaries strongly).

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

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

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

Where yy = (DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE)



Counters from table(s):p_nbsc_packet_control_unitp_nbsc_coding_schemes


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

DL drops per 10 kbytes, MS lost (tbf_28d)

Description: DL TBF drops per 10kbytesUse: Indicates the bad radio conditions that affect the connection,

which means drops in ratio to volume.Known problems: 1) Slow cell reselections (flushes) can increment the

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

sum(a.DL_TBF_rel_due_no_resp_MS)----------------------------------------sum(a.rlc_data_blocks_dl_cs1*20

+ a.rlc_data_blocks_dl_cs2*30+ sum over MCS-1 (yy)* 22+ sum over MCS-2 (yy)* 28+ sum over MCS-3 (yy)* 37+ sum over MCS-4 (yy)* 44+ sum over MCS-5 (yy)* 56+ sum over MCS-6 (yy)* 74+ sum over MCS-7 (yy/2)*112+ sum over MCS-8 (yy/2)*136+ sum over MCS-9 (xx/2)*148+ sum over MCS-11 (xx)*36+ sum over MCS-12 (xx)*50)/ 10240

Where yy = (b.DL_RLC_BLOCKS_IN_ACK_MODE + b.DL_RLC_BLOCKS_IN_UNACK_MODE)


Unit: Numbers

Figure 49. DL drops per 10 kbytes, MS lost (tbf_28d)

UL TBF reallocation failure ratio, S9PS (tbf_29)

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

sum(UL_TBF_RE_ALLOCATIONS + UL_TBF_REALLOC_FAILS)




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


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

UL TBF reallocation attempts, S9PS (tbf_31)

sum(UL_TBF_RE_ALLOCATIONS + UL_TBF_REALLOC_FAILS)


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

DL TBF reallocation attempts, S9PS (tbf_32)

sum(DL_TBF_RE_ALLOCATIONS + DL_TBF_REALLOC_FAILS)


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

TBF success % S9PS (tbf_34)

Use: Also called ‘TBF retainability’.This KPI is used to measure the quality of the radio interfacefor TBF sessions. The KPI measures purely the retainabilityof TBFs and is not dependent on interfaces and NEs outsideBSS.

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

100 - TBF failure % =



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

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

- releases due to flush releases due to suspend

sum(NBR_OF_UL_TBF + NBR_OF_DL_TBF ;TBF establishments- decode(AVE_DUR_UL_TBF_SUM,0,0,AVE_DUR_UL_TBF_DEN)- decode(AVE_DUR_DL_TBF_SUM,0,0,AVE_DUR_DL_TBF_DEN)- UL_TBF_REL_DUE_TO_FLUSH - DL_TBF_REL_DUE_TO_FLUSH- UL_TBF_REL_DUE_TO_SUSPEND - DL_TBF_REL_DUE_TO_SUSPEND)

100 - 100 * ----------------------------------------------------------- %sum(NBR_OF_UL_TBF + NBR_OF_DL_TBF

- UL_TBF_REL_DUE_TO_FLUSH - DL_TBF_REL_DUE_TO_FLUSH- UL_TBF_REL_DUE_TO_SUSPEND - DL_TBF_REL_DUE_TO_SUSPEND)


Figure 54. TBF success % S9PS (tbf_34)

TBF success %, S10.5PS (tbf_34a)

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

Known problems: Not usable on BTS level when common BCCH is used,because TBF can start in one BTS of a segment and end inanother.

100 - TBF failure % =

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

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

- releases due to flush - releases due to suspend

sum(NBR_OF_UL_TBF+ NBR_OF_DL_TBF- UL_TBF_Establishment_Failed - DL_TBF_Establishment_Failed- UL_EGPRS_TBF_REL_DUE_NO_RESP - DL_EGPRS_TBF_REL_DUE_NO_RESP

;TBF establishments- decode(AVE_DUR_UL_TBF_SUM,0,0,AVE_DUR_UL_TBF_DEN)- decode(AVE_DUR_DL_TBF_SUM,0,0,AVE_DUR_DL_TBF_DEN)- UL_TBF_REL_DUE_TO_FLUSH-DL_TBF_REL_DUE_TO_FLUSH- UL_TBF_REL_DUE_TO_SUSPEND-DL_TBF_REL_DUE_TO_SUSPEND)

100 - 100 * --------------------------------------------------------------- %sum(NBR_OF_UL_TBF+NBR_OF_DL_TBF

- UL_TBF_Establishment_Failed- DL_TBF_Establishment_Failed- UL_EGPRS_TBF_REL_DUE_NO_RESP- DL_EGPRS_TBF_REL_DUE_NO_RESP- UL_TBF_REL_DUE_TO_FLUSH-DL_TBF_REL_DUE_TO_FLUSH- UL_TBF_REL_DUE_TO_SUSPEND-DL_TBF_REL_DUE_TO_SUSPEND)




Figure 55. TBF success %, S10.5PS (tbf_34a)

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

Use: This KPI indicates that there is mobility from this cell to othercells by cell reselection. Cell reselection affects thethroughput.

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

sum(Nbr_of_UL_TBF)


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

Share of UL TBF releases due to flush (tbf_35a)


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

sum(Nbr_of_UL_TBF-UL_TBF_Establishment_Failed-UL_EGPRS_TBF_REL_DUE_NO_RESP)


Figure 57. Share of UL TBF releases due to flush (tbf_35a)

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


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

sum(Nbr_of_DL_TBF)


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



Share of DL TBF releases due to flush (tbf_36a)


Note: Some abnormal releases are not shown in any release counters(those are included in establishment), but there is no impact tothis formula.

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

sum(Nbr_of_DL_TBF-DL_TBF_Establishment_Failed-DL_EGPRS_TBF_REL_DUE_NO_RESP)


Figure 59. Share of DL TBF releases due to flush (tbf_36a)

Average UL TBF per timeslot, S9PS (tbf_37b)

Use: Indicates how many UL TBFs on average there are pertimeslot.

sum(aver_tbfs_per_tsl_ul_sum)--------------------------------------sum(aver_tbfs_per_tsl_ul_den)


Figure 60. Average UL TBF per timeslot, S9PS (tbf_37b)

Average UL TBF per timeslot, S9PS (tbf_37c)

Use: Indicates how many UL TBFs there are on average pertimeslot.

Known problems: 1. When updating AVE_TBFS_PER_TSL counters, allTSLs of a territory are counted. This means thataver_tbfs_per_tsl_ul_sum may have a value below 1.When there is more traffic, for example all TSLs of aterritory are in use, the problem does not occur. Newcounters will be available in S11.5 (tbf_37d).

2. Another problem with the current counters is that alsoidle TBFs are considered, as updating is based on theterritory timeslot allocation situation, not on thescheduling situation. This problem is corrected inS10.5.

sum(aver_tbfs_per_tsl_ul_sum)--------------------------------------sum(aver_tbfs_per_tsl_ul_den) * 100




Figure 61. Average UL TBFper timeslot, S9PS (tbf_37c)

Average UL TBF per timeslot (tbf_37d)


sum(ave_ul_tbfs_per_used_tsl)-----------------------------------sum(aver_tbfs_per_tsl_ul_den) * 100


Figure 62. Average UL TBF per timeslot (tbf_37d)

Average DL TBF per timeslot, S9PS (tbf_38b)

Use: Indicates how many DL TBFs on average there are pertimeslot.

sum(aver_tbfs_per_tsl_dl_sum)-------------------------------------sum(aver_tbfs_per_tsl_dl_den)


Figure 63. Average DL TBF per timeslot, S9PS (tbf_38b)

Average DL TBF per timeslot, S9PS (tbf_38c)

Use: Indicates how many DL TBFs there are on average pertimeslot.

Known problems: The implementation of the counters is wrong. Correctionpending.

sum(aver_tbfs_per_tsl_dl_sum)----------------------------------------sum(aver_tbfs_per_tsl_dl_den) * 100


Figure 64. Average DL TBFper timeslot, S9PS (tbf_38c)



Average DL TBF per timeslot (tbf_38d)


sum(ave_dl_tbfs_per_used_tsl)-----------------------------------sum(aver_tbfs_per_tsl_dl_den) * 100


Figure 65. Average DL TBF per timeslot (tbf_38d)

UL GPRS TBF establishments, S10.5PS (tbf_41)

Use: Indicates only GPRS TBF establishments. EGPRSestablishments are not counted.

Sum (NBR_OF_UL_TBF - EGPRS_TBFS_UL)


Unit: Numbers

Figure 66. UL GPRS TBF establishments, S10.5PS (tbf_41)

DL GPRS TBF establishments, S10.5PS (tbf_42)

Use: Indicates only GPRS TBF establishments. EGPRSestablishments are not counted.

Sum (NBR_OF_DL_TBF - EGPRS_TBFS_DL)


Unit: Numbers

Figure 67. DL GPRS TBF establishments, S10.5PS (tbf_42)

Normal TBF release ratio, DL to UL, S10.5PS (tbf_44)

Use: Ratio of normally released TBFs in DL to UL. To detect therelative activity in DL compared to UL, used in findingsleeping GPRS cells.

(100*(AVE_DUR_DL_TBF_DEN/AVE_DUR_UL_TBF_DEN))




Unit: %

Figure 68. Normal TBF release ratio DL, to UL, S10.5PS (tbf_44)

Average UL TBF per timeslot, Area, S9PS (tbf_47)



sum(aver_tbfs_per_tsl_ul_sum)-----------------------------------------------------------------------avg(aver_tbfs_per_tsl_ul_den) * 100 * count(distinct period_start_time)


Figure 69. Average UL TBF per timeslot, Area, S9PS (tbf_47)

Average UL TBF per timeslot (tbf_47a)


sum(ave_ul_tbfs_per_used_tsl)-----------------------------------------------------------------------avg(aver_tbfs_per_tsl_ul_den) * 100 * count(distinct period_start_time)


Unit = Number

Figure 70. Average UL TBF per timeslot (tbf_47a)

Average DL TBF per timeslot, Area, S9PS (tbf_48)



sum(aver_tbfs_per_tsl_dl_sum)-----------------------------------------------------------------------avg(aver_tbfs_per_tsl_dl_den) * 100 * count(distinct period_start_time)




Figure 71. Average DL TBF per timeslot, Area, S9PS (tbf_48)

Average DL TBF per timeslot (tbf_48a)


sum(ave_dl_tbfs_per_used_tsl)-----------------------------------------------------------------------avg(aver_tbfs_per_tsl_dl_den) * 100 * count(distinct period_start_time)


Unit = Number

Figure 72. Average DL TBF per timeslot (tbf_48a)

Usage ratio of EDGE resources used for UL GPRS TBFs (tbf_57)

Description: Share of UL GPRS TBF allocations done in EGPRS territorybecause of congestion in GPRS area.

sum(ul_gprs_tbf_in_egprs_terr)100 * --------------------- ----------- %

sum(nbr_of_ul_tbf- egprs_tbfs_ul)


Figure 73. Usage ratio of EDGE resources used for UL GPRS TBFs (tbf_57)

Usage ratio of EDGE resources used for UL GPRS TBFs (tbf_57a)

Description: Share of UL GPRS TBF allocations done in EGPRS territorybecause of congestion in GPRS area (or non-existence of pureGPRS territory).

sum(ul_gprs_tbf_in_egprs_terr)100 * ---------------------------------------------

sum((REQ_1_TSL_UL - REQ_1_TSL_UL_FOR_EGPRS_MS)+ (REQ_2_TSL_UL - REQ_2_TSL_UL_FOR_EGPRS_MS)+ (REQ_3_TSL_UL - REQ_3_TSL_UL_FOR_EGPRS_MS)+ (REQ_4_TSL_UL - REQ_4_TSL_UL_FOR_EGPRS_MS)+ (REQ_5_TSL_UL - REQ_5_TSL_UL_FOR_EGPRS_MS)+ (REQ_6_TSL_UL - REQ_6_TSL_UL_FOR_EGPRS_MS)+ (REQ_7_TSL_UL - REQ_7_TSL_UL_FOR_EGPRS_MS)+ (REQ_8_TSL_UL - REQ_8_TSL_UL_FOR_EGPRS_MS))




Unit: %

Figure 74. Usage ratio of EDGE resources used for UL GPRS TBFs (tbf_57a)

Usage ratio of EDGE resources used for DL GPRS TBFs (tbf_58)

Description: Share of DL GPRS TBF allocations done in EGPRS territorybecause of congestion in GPRS area.

sum(dl_gprs_tbf_in_egprs_terr)100 * ------------------------------------ %

sum(nbr_of_dl_tbf - egprs_tbfs_dl)


Figure 75. Usage ratio of EDGE resources used for DL GPRS TBFs (tbf_58)

Usage ratio of EDGE resources used for DL GPRS TBFs (tbf_58a)

Description: Share of DL GPRS TBF allocations done in EGPRS territorybecause of congestion in GPRS area (or non-existence of pureGPRS territory).

sum(DL_gprs_tbf_in_egprs_terr)100 * ----------------------------------------------

sum((REQ_1_TSL_DL - REQ_1_TSL_DL_FOR_EGPRS_MS)+ (REQ_2_TSL_DL - REQ_2_TSL_DL_FOR_EGPRS_MS)+ (REQ_3_TSL_DL - REQ_3_TSL_DL_FOR_EGPRS_MS)+ (REQ_4_TSL_DL - REQ_4_TSL_DL_FOR_EGPRS_MS)+ (REQ_5_TSL_DL - REQ_5_TSL_DL_FOR_EGPRS_MS)+ (REQ_6_TSL_DL - REQ_6_TSL_DL_FOR_EGPRS_MS)+ (REQ_7_TSL_DL - REQ_7_TSL_DL_FOR_EGPRS_MS)+ (REQ_8_TSL_DL - REQ_8_TSL_DL_FOR_EGPRS_MS))


Unit: %

Figure 76. Usage ratio of EDGE resources used for DL GPRS TBFs (tbf_58a)

Usage ratio of GPRS resources used for UL EDGE TBFs (tbf_59)

Description: Share of UL GPRS TBF allocations done for EGPRS requestin GPRS territory because of congestion in EGPRS area.

sum(ul_gprs_tbf_for_egprs_req)100 * ------------------------------- %

sum(req_1_tsl_ul_for_egprs_ms+ req_2_tsl_ul_for_egprs_ms+ req_3_tsl_ul_for_egprs_ms+ req_4_tsl_ul_for_egprs_ms



+ req_5_tsl_ul_for_egprs_ms+ req_6_tsl_ul_for_egprs_ms+ req_7_tsl_ul_for_egprs_ms+ req_8_tsl_ul_for_egprs_ms)


Figure 77. Usage ratio of GPRS resources used for UL EDGE TBFs (tbf_59)

Usage ratio of GPRS resources used for DL EDGE TBFs (tbf_60)

Description: Share of DL GPRS TBF allocations done for EGPRS requestin GPRS territory because of congestion in EGPRS area.

sum(dl_gprs_tbf_for_egprs_req)100 * ------------------------------- %

sum(req_1_tsl_dl_for_egprs_ms+ req_2_tsl_dl_for_egprs_ms+ req_3_tsl_dl_for_egprs_ms+ req_4_tsl_dl_for_egprs_ms+ req_5_tsl_dl_for_egprs_ms+ req_6_tsl_dl_for_egprs_ms+ req_7_tsl_dl_for_egprs_ms+ req_8_tsl_dl_for_egprs_ms)


Figure 78. Usage ratio of GPRS resources used for DL EDGE TBFs (tbf_60)

Ratio of signaling TBFs from all created UL TBFs (tbf_61)

Description: Ratio of signaling TBFs from all created UL TBFsUse: Indicates how much signalling TBFs are from all UL TBFs.

sum(ul_tbf_for_signalling)100* -------------------------------------------- %

sum(ul_tbf_for_signalling + ul_tbf_for_data)


Figure 79. Ratio of signaling TBFs from all created UL TBFs (tbf_61)

DL signaling TBFs usage ratio (tbf_62)

Description: Ratio of signaling TBFs from all created DL TBFs.Use: Indicates how big a percentage there are signalling TBFs from

all DL TBFs.

sum(dl_tbf_for_signalling)100* -------------------------------------------- %

sum(dl_tbf_for_signalling + dl_tbf_for_data)




Figure 80. DL signaling TBFs usage ratio (tbf_62)

UL Flush pr Minute (tbf_63)

Use: Indicates how many TBFs are interrupted by cell reselectionsper "TBF minute". Indicates the level of subscriber mobility.

60 * 100 * UL_TBF_REL_DUE_TO_FLUSH/AVE_DUR_UL_TBF_SUM


Unit: Number/min

Figure 81. UL Flush pr Minute (tbf_63)

DL Flush pr Minute (tbf_64)

Use: Indicates how many TBFs are interrupted by cell reselectionsper "TBF minute". Indicates the level of subscriber mobility.RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS

60 * 100 * DL_TBF_REL_DUE_TO_FLUSH/AVE_DUR_DL_TBF_SUM


Unit: Number/min

Figure 82. DL Flush pr Minute (tbf_64)

2.4 Logical link control (llc)

Expired LLC frames % DL, S9PS (llc_1)

Use: Ratio of expired LLC frames to all frames. Indicatesthroughput problems in SGSN or in the network under it. Thelifetime of the packets is set by SGSN and that may expirealready in SGSN. If a packet is sent to PCU, the remaininglifetime is the time when it should be sent further in PCU. Ifthe lifetime expires, the packet is discarded.

sum(disc_llc_blocks_due_to_exp)100 * ------------------------------------------------------- %

sum(ave_dl_llc_per_tbf_sum+ disc_llc_blocks_due_to_exp)




Figure 83. Expired LLC frames % DL, S9PS (llc_1)

Discarded UL LLC frames, NSE unavailability %, S9PS (llc_2)

Use: Ratio of discarded LLC bytes to UL RLC data bytes. Bytesdiscarded due to unavailable NSE which may mean problemsin the Gb interface.

sum(disc_UL_LLC_data)100 * --------------------------------------------------------- %

sum(RLC_data_blocks_UL_CS1*20 +RLC_data_blocks_UL_CS2*30)


Figure 84. Discarded UL LLC frames, NSE unavailability %, S9PS (llc_2)

Ratio of discarded UL LLC frames, NSE unavailability (llc_2a)

Use: Ratio of discarded LLC bytes to UL RLC data bytes. Bytesdiscarded due to unavailable NSE which may mean problemsin the Gb interface.

sum(a.disc_UL_LLC_data)100 * --------------------------------------------------------------

sum(a.RLC_data_blocks_UL_CS1*20 + a.RLC_data_blocks_UL_CS2*30+ sum over MCS-11 (xx)*36 + sum over MCS-12 (xx)*50+ sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148

Where xx = (b.UL_RLC_BLOCKS_IN_ACK_MODE + b.UL_RLC_BLOCKS_IN_UNACK_MODE)


Unit: %

Figure 85. Ratio of discarded UL LLC frames, NSE unavailability (llc_2a)



Volume weighted LLC throughput (llc_3)

Use: Indicates the average of successfully transferred kilobits persecond when at least one of the following two conditions ismet: 1. TBF duration is longer than four seconds or 2. LLCbytes are more than 1560.END RELEASE: S11.5

sum(spare072109) * 8---------------------sum(spare072110) * 10


Unit: kbps

Figure 86. Volume weighted LLC throughput (llc_3)

Volume weighted LLC throughput (llc_3a)

Use: Indicates the average of successfully transferred kilobits persecond when at least one of the following two conditions ismet: 1. TBF duration is longer than four seconds or 2. LLCbytes are more than 1560.

sum(AVG_VOL_WGHT_LLC_TROUGHPUT_NUM) * 8------------------------------------------sum(AVG_VOL_WGHT_LLC_TROUGHPUT_DEN) * 10


Unit: kbps

Figure 87. Volume weighted LLC throughput (llc_3a)

2.5 Radio link control (rlc)

Ack. CS1 RLC blocks UL, S9PS (rlc_1)

Use: Number of UL blocks in RLC ack mode using CS1.Retransmission is not included.

sum(RLC_DATA_BLOCKS_UL_CS1 - RLC_DATA_BLOCKS_UL_UNACK)


Figure 88. 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 89. 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 90. 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 91. 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 92. Ack. CS1 RLC UL block error rate), S9PS (rlc_5a)



UL CS1 RLC data share, S9PS (rlc_6a)

Use: Indicates how big a share as a percentage UL CS1 datacomprises out of all RLC payload data.

sum(RLC_data_blocks_UL_CS1*20)100 * ----------------------------------------------------------%

sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30+ RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30)


Unit: %

Figure 93. UL CS1 RLC data share, S9PS (rlc_6a)

UL CS1 ack RLC data share, S9PS (rlc_6b)

Use: Indicates how big a share as a percentage UL CS1 ack datacomprises out of all RLC payload data.

sum(RLC_data_blocks_UL_CS1-RLC_data_blocks_UL_UNACK)*20100 * ----------------------------------------------------------%



Unit: %

Figure 94. UL CS1 ack RLC data share, S9PS (rlc_6b)

UL CS1 unack RLC data share, S9PS (rlc_6c)

Use: Indicates how big a share as a percentage DL CS1 unack datacomprises out of all RLC payload data.

sum(RLC_data_blocks_UL_UNACK)*20100 * ----------------------------------------------------------%



Figure 95. UL CS1 unack RLC data share, S9PS (rlc_6c)

UL CS1 ack RLC data share (rlc_6e)

Use: Indicates how big a share as a percentage UL CS1 ack datacomprises out of all RLC payload data.



sum(a.RLC_data_blocks_UL_CS1- a.RLC_data_blocks_UL_UNACK)*20

100 * ----------------------------------sum(a.RLC_data_blocks_UL_CS1*20

+ a.RLC_data_blocks_UL_CS2*30+ a.RLC_data_blocks_DL_CS1*20+ a.RLC_data_blocks_DL_CS2*30+ sum over MCS-11 (xx)*36+ sum over MCS-12 (xx)*50)

Where xx=(b.UL_RLC_BLOCKS_IN_ACK_MODE + b.UL_RLC_BLOCKS_IN_UNACK_MODE+ b.DL_RLC_BLOCKS_IN_ACK_MODE + b.DL_RLC_BLOCKS_IN_UNACK_MODE)


Unit: %

Figure 96. UL CS1 ack RLC data share (rlc_6e)

UL CS1 unack RLC data share (rlc_6f)

Use: Indicates how big a share as a percentage UL CS1 unack datacomprises out of all RLC payload data.

sum(a.RLC_data_blocks_UL_UNACK*20)100 * ----------------------------------

sum(a.RLC_data_blocks_UL_CS1*20+ a.RLC_data_blocks_UL_CS2*30+ a.RLC_data_blocks_DL_CS1*20+ a.RLC_data_blocks_DL_CS2*30+ sum over MCS-11 (xx)*36+ sum over MCS-12 (xx)*50)



Unit: %

Figure 97. UL CS1 unack RLC data share (rlc_6f)

UL CS2 RLC data share, S9PS (rlc_7a)


sum(RLC_data_blocks_UL_CS2*30)100 * ----------------------------------------------------------%





Unit: %

Figure 98. UL CS2 RLC data share, S9PS (rlc_7a)

UL CS2 RLC data share (rlc_7b)


sum(a.RLC_data_blocks_UL_CS2*30)100 * --------------------------------




Unit: %

Figure 99. UL CS2 RLC data share (rlc_7b)

DL CS1 RLC data share, S9PS (rlc_8a)

Use: Indicates how big a share as a percentage DL CS1 datacomprises out of all RLC payload data.

sum(RLC_data_blocks_DL_CS1*20)100 * ----------------------------------------------------------%



Unit: %

Figure 100. DL CS1 RLC data share, S9PS (rlc_8a)

DL CS1 ack RLC data share, S9PS (rlc_8b)

Use: Indicates how big a share as a percentage DL CS1 ack datacomprises out of all RLC payload data.

sum(RLC_data_blocks_DL_CS1 - RLC_data_blocks_DL_UNACK)*20100 * ----------------------------------------------------------%

sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30



+ RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30)


Unit: %

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

DL CS1 ack RLC data share (rlc_8e)

Use: Indicates how big a share as a percentage DL CS1 ack datacomprises out of all RLC payload data.

sum(a.RLC_data_blocks_DL_CS1- a.RLC_data_blocks_DL_UNACK)*20

100 * ----------------------------------sum(a.RLC_data_blocks_UL_CS1*20

+ a.RLC_data_blocks_UL_CS2*30+ a.RLC_data_blocks_DL_CS1*20+ a.RLC_data_blocks_DL_CS2*30+ sum over MCS-11 (xx)*36+ sum over MCS-12 (xx)*50)



Unit: %

Figure 102. DL CS1 ack RLC data share (rlc_8e)

DL CS1 unack RLC data share (rlc_8f)


sum(a.RLC_data_blocks_DL_UNACK)*20100 * -----------------------------------






Unit: %

Figure 103. DL CS1 unack RLC data share (rlc_8f)

DL CS1 unack RLC data share, S9PS (rlc_8c)


sum(RLC_data_blocks_DL_UNACK)*20100 * ---------------------------------------------------------- %

sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30+ RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30)


Unit: %

Figure 104. DL CS1 unack RLC data share, S9PS (rlc_8c)

DL CS2 RLC data share, S9PS (rlc_9a)


sum(RLC_data_blocks_DL_CS2*30)100 * ----------------------------------------------------------%

sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30+ RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30)


Unit: %

Figure 105. DL CS2 RLC data share, S9PS (rlc_9a)

DL CS2 RLC data share (rlc_9b)


sum(a.RLC_data_blocks_DL_CS2*30)100 * --------------------------------






Unit: %

Figure 106. DL CS2 RLC data share ( rlc_9b)

UL CS1 RLC block error rate, S9PS (rlc_10a)

Use: High BLER means worse radio interface conditions.Known problems: 1) The number of ignored RLC data blocks in uplink due to

BSN being in acknowledged mode should be subtracted butthere is no counter for this specifically for CS1 There is onlyone counter for CS1 and CS2 which is marked as counter xxin the formula.2) Does not show correctly if there is unack mode used.(rlc_data_blocks_ul_cs1 contains both ack and unack)

Experiences on use: UL block error rate (BLER) is normally higher than DLBLER. There can be several reasons to this:1) There is UL power control while full power is used in DL.The UL PC parameters may have been set too aggressively.2) UL BLER includes uplink as well as downlinktransmission problems (the MS needs to decode the USFcorrectly before transmitting).3) When the MS stops responding during an UL TBF (e.g. dueto a cell change), a number of ‘bad frames’ is received by thePCU before it detects that the radio contact has been lost.These bad frames increase the counters c072070 or c072071,and thus the UL BLER.4) Also when resources are allocated for an UL TBF duringone phase access, but the MS does not respond, bad frames arereceived. Such an allocation without any blocks may occur,for example, if the MS has sent the channel request more thanonce during the access, or if there is a collision, i.e. thenetwork initiates DL TBF establishment at the same time, theMS reacts on that and ignores the UL TBF.

sum(bad_frame_ind_UL_CS1)100 * -------------------------------------------------%

sum(rlc_data_blocks_UL_CS1+ bad_frame_ind_UL_CS1+xx)

xx = RLC CS1 blocks ignored due to incorrect BSN (missing counter approximated)

sum(rlc_data_blocks_ul_cs1)= ------------------------------- *sum(ignor_rlc_data_bl_ul_due_bsn)

sum(rlc_data_blocks_ul_cs1+ rlc_data_blocks_ul_cs2)




Unit: %

Figure 107. UL CS1 RLC block error rate, S9PS (rlc_10a)

UL CS1 ACK RLC block error rate, S9PS (rlc_10b)


BSN being in acknowledged mode should be subtracted butthere is no counter for this specifically for CS1 There is onlyone counter for CS1 and CS2 which is marked as counter xxin the formula.2) Does not show correctly if there is unack mode used.(rlc_data_blocks_ul_cs1 contains both ack and unack)

Experiences on use: UL block error rate (BLER) is normally higher than DLBLER. There can be several reasons to this:1) There is UL power control while full power is used in DL.The UL PC parameters may have been set too aggressively.2) UL BLER includes uplink as well as downlinktransmission problems (the MS needs to decode the USFcorrectly before transmitting).3) When the MS stops responding during an UL TBF (e.g. dueto a cell change), a number of ’bad frames’ is received by thePCU before it detects that the radio contact has been lost.These bad frames increase the counters c072070 or c072071,and thus the UL BLER.4) Also when resources are allocated for an UL TBF duringone phase access, but the MS does not respond, bad frames arereceived. Such an allocation without any blocks may occur,for example, if the MS has sent the channel request more thanonce during the access, or if there is a collision, i.e. thenetwork initiates DL TBF establishment at the same time, theMS reacts on that and ignores the UL TBF.

sum(bad_frame_ind_UL_CS1)100 * --------------------------------------------------------------------%

sum(rlc_data_blocks_UL_CS1- rlc_data_blocks_UL_unack !ack CS1 data blocks+ bad_frame_ind_UL_CS1+ xx !RLC CS1 blocks ignored due to incorrect BSN (estimate)

where

xx =

sum(rlc_data_blocks_ul_cs1- rlc_data_blocks_UL_unack)

xx= ----------------------------- *sum(ignor_rlc_data_bl_ul_due_bsn)sum(rlc_data_blocks_ul_cs1

- rlc_data_blocks_UL_unack+ rlc_data_blocks_ul_cs2)




Figure 108. UL CS1 RLC block error rate, S9PS (rlc_10b)

UL CS1 ACK RLC block error rate, S9PS (rlc_10c)

Use: High BLER means worse radio interface conditions.Known problems: 1)

SPARE72107=RETRA_RLC_DATA_BLOCKS_UL_CS1.The spare counter will be replaced by an official counter lateron.2) Impact of "Ignore due to BSN" not considered.3) See also rlc_10b.

Experiences on use: See rlc_10a.

sum(SPARE072107)100 * -----------------------------------------%

sum(rlc_data_blocks_UL_CS1)


Figure 109. UL CS1 ACK RLC block error rate, S9PS (rlc_10c)

UL CS1 ACK RLC block error rate, S9PS (rlc_10d)


SPARE72107=RETRA_RLC_DATA_BLOCKS_UL_CS1.An official counter will replace the spare counter later on.2) Impact of "Ignore due to BSN" not considered.3) See also rlc_10b.

sum(SPARE072107)100 * ------------------------------------------ %

sum(rlc_data_blocks_UL_CS1 + SPARE072107)


Figure 110. UL CS1 ACK RLC block error rate, S9PS (rlc_10d)

UL CS1 ACK RLC block error rate, S11.5 (rlc_10e)

Description: Block Error Rate (BLER) for UL CS1 ACK RLC BlocksUse: High BLER means worse radio interface conditions.



Known problems: 1) Impact of "Ignore due to BSN" not considered.2) See also rlc_10b.

sum(retra_data_blocks_ul_cs1)100 * ------------------------------------ %

sum(rlc_data_blocks_UL_CS1+ retra_data_blocks_ul_cs1)


Figure 111. UL CS1 ACK RLC block error rate, S11.5 (rlc_10e)

UL CS2 ARLC block error rate, S9PS (rlc_11a)


BSN being in acknowledged mode should be subtracted butthere is no counter for this specifically for CS2. There is onlyone counter for CS1 and CS2 the estimated value of which iscounted as xx below.2) Does not work if unack mode is used, too.

Experiences on use: See rlc_10a.

sum(bad_frame_ind_ul_cs2)100 * -------------------------------------------------%

sum(rlc_data_blocks_ul_cs2+ bad_frame_ind_ul_cs2+ xx)

xx = RLC CS2 blocks ignored due to incorrect BSN (missing counter approximated)

sum(rlc_data_blocks_ul_cs2)= -----------------------------------------------------* sum(ignor_rlc_data_bl_ul_due_bsn)

sum(rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2)


Figure 112. UL CS2 ARLC block error rate, S9PS (rlc_11a)

UL CS2 ACK RLC block error rate, S9PS (rlc_11b)

Use: High BLER means worse radio interface conditions.Known problems: 1) The number of ignored RLC data blocks in downlink due

to BSN being in acknowledged mode should be subtracted butthere is no counter for this separately for CS2. There is onlyone counter for CS1 and CS2, the estimated value of which iscounted as xx below.

Experience on use: See rlc_10a

sum(bad_frame_ind_ul_cs2)



100 * ---------------------------------------------- %sum(rlc_data_blocks_ul_cs2

- rlc_data_blocks_UL_unack ! CS2 ack blocks+ bad_frame_ind_ul_cs2+ xx ! RLC CS2 blocks ignored due to incorrect BSN (estimated))

where

sum(rlc_data_blocks_ul_cs2)xx = ------------------------------ *sum(ignor_rlc_data_bl_ul_due_bsn)

sum(rlc_data_blocks_ul_cs1--rlc_data_blocks_UL_unack+rlc_data_blocks_ul_cs2)


Figure 113. UL CS2 RLC block error rate, S9PS (rlc_11b)

UL CS2 ACK RLC block error rate, S9PS (rlc_11c)


BSN being in acknowledged mode should be subtracted butthere is no counter for this separately for CS2. There is onlyone counter for CS1 and CS2, the estimated value of which iscounted as xx below.

Experiences on use: See rlc_10b.

sum(bad_frame_ind_ul_cs2)100 * ----------------------------------------------------------------- %

sum(rlc_data_blocks_ul_cs2 + bad_frame_ind_ul_cs2+ xx) ! RLC CS2 blocks ignored due to incorrect BSN estimated

where

sum(rlc_data_blocks_ul_cs2)xx = ----------------------------- *sum(ignor_rlc_data_bl_ul_due_bsn)

sum(rlc_data_blocks_ul_cs1- rlc_data_blocks_UL_unack+ rlc_data_blocks_ul_cs2)


Figure 114. UL CS2 ACK RLC block error rate, S9PS (rlc_11c)

UL CS2 ACK RLC block error rate, S10.5PS (rlc_11d)

Use: High BLER means worse radio interface conditions.Known problems: 1)SPARE72108=RETRA_RLC_DATA_BLOCKS_UL_CS.

The spare counter will be replaced by an official counter lateron.2) Impact of blocks “Ignored due to BSN” not covered.

Experience on use: See rlc_10b.



sum(SPARE072108)100 * -------------------------------------------%

sum(rlc_data_blocks_ul_cs2)


Figure 115. UL CS2 ACK RLC block error rate, S10.5PS(rlc_11d)

UL CS2 ACK RLC block error rate, S10.5PS (rlc_11e)


SPARE72108=RETRA_RLC_DATA_BLOCKS_UL_CS2.An official counter will replace the spare counter later on.2) Impact of blocks "Ignored due to BSN" not covered.

Experience on use: See rlc_10b.

sum(SPARE072108)100 * ------------------------------------------ %

sum(SPARE072108 + rlc_data_blocks_ul_cs2)


Figure 116. UL CS2 ACK RLC block error rate, S10.5PS (rlc_11e)

UL CS2 ACK RLC block error rate, S11.5 (rlc_11f)

Use: High BLER means worse radio interface conditions.Known problems: 1) Impact of blocks "Ignore due to BSN" not covered.

2) See rlc_10b.

sum(retra_data_blocks_ul_cs2)100 * ------------------------------------- %

sum(retra_data_blocks_ul_cs2+ rlc_data_blocks_ul_cs2)


Figure 117. UL CS2 ACK RLC block error rate, S11.5 (rlc_11f)

DL CS1 RLC block error rate, S9PS (rlc_12)

Use: High BLER means worse radio interface conditions.Known problems: Does not work if the unack mode is used, too.

sum(retra_rlc_data_blocks_dl_cs1)100 * ---------------------------------------------------------- %

sum(rlc_data_blocks_dl_cs1 + retra_rlc_data_blocks_dl_cs1)




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

DL CS1 ACK RLC block error rate, S9PS (rlc_12a)

Use: High BLER means worse radio interface conditions.

sum(retra_rlc_data_blocks_dl_cs1)100 * --------------------------------------------------------------- %

sum(rlc_data_blocks_dl_cs1 - rlc_data_blocks_dl_unack ; ack CS1+ retra_rlc_data_blocks_dl_cs1)


Figure 119. DL CS1 ACK RLC block error rate, S9PS (rlc_12a)

DL CS2 RLC block error rate, S9PS (rlc_13)

Use: High BLER means worse radio interface conditions.

sum(retra_rlc_data_blocks_dl_cs1)100 * --------------------------------------------------------------- %

sum(rlc_data_blocks_dl_cs1 - rlc_data_blocks_dl_unack ; ack CS1+ retra_rlc_data_blocks_dl_cs1)


Figure 120. 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+ bad_frame_ind_ul_cs2 + bad_frame_ind_ul_unack+ ignor_rlc_data_bl_ul_due_bsn)


Figure 121. UL RLC blocks, S9PS (rlc_14)

UL RLC blocks (rlc_14a)

Use: Total UL data volume as the number of RLC blocks.



sum(a.rlc_data_blocks_ul_cs1 + a.rlc_data_blocks_ul_cs2+a.rlc_mac_cntrl_blocks_ul + a.bad_frame_ind_ul_cs1+a.bad_frame_ind_ul_cs2 + a.bad_frame_ind_ul_unack+a.ignor_rlc_data_bl_ul_due_bsn)+sum over MCS-11..12 (b.ul_rlc_blocks_in_ack_mode + b.ul_rlc_blocks_in_unack_mode

+b.bad_rlc_valid_hdr_ul_unack + b.bad_rlc_bad_hdr_ul_unack+b.bad_rlc_valid_hdr_ul_ack + b.bad_rlc_bad_hdr_ul_ack)

+sum over MCS-1..9 (b.ul_rlc_blocks_in_ack_mode + b.ul_rlc_blocks_in_unack_mode+b.bad_rlc_valid_hdr_ul_unack + b.bad_rlc_bad_hdr_ul_unack+b.bad_rlc_valid_hdr_ul_ack + b.bad_rlc_bad_hdr_ul_ack)


Unit: Numbers

Figure 122. UL RLC blocks (rlc_14a)

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)


Unit: Numbers

Figure 123. DL RLC blocks, S9PS (rlc_15)

DL RLC blocks (rlc_15a)

Use: Total DL data volume as the number of RLC blocks.

sum(a.rlc_data_blocks_dl_cs1 + a.rlc_data_blocks_dl_cs2+ a.rlc_mac_cntrl_blocks_dl + a.retra_rlc_data_blocks_dl_cs1+ a.retra_rlc_data_blocks_dl_cs2)+ sum over MCS-11..12(b.dl_rlc_blocks_in_ack_mode + b.dl_rlc_blocks_in_unack_mode

+ b.retrans_rlc_data_blocks_dl)+ sum over MCS-1..9(b.dl_rlc_blocks_in_ack_mode + b.dl_rlc_blocks_in_unack_mode

+ b.retrans_rlc_data_blocks_dl)


Unit: Numbers

Figure 124. DL RLC blocks (rlc_15a)



UL ACK EGPRS block error ratio S10.5PS (rlc_18)

Use: Ratio of retransmitted UL blocks to all blocks sent in EGPRScoding schemes.

Sum over MCS1 to 9 (RETRANS_RLC_DATA_BLOCKS_UL)100 * --------------------------------------------------------------------------

Sum over MCS1 to 9 (UL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_UL)

Counters from table(s):p_nbsc_coding_scheme

Unit: %

Figure 125. UL ACK EGPRS block error ratio S10.5PS (rlc_18)

DL ACK EGPRS block error ratio S10.5PS (rlc_19)

Use: Ratio of retransmitted DL blocks to all blocks sent in EGPRScoding schemes.

Sum over MCS1 to 9 (RETRANS_RLC_DATA_BLOCKS_DL)100 * --------------------------------------------------------------------------

Sum over MCS1 to 9 (DL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_DL)


Unit: %

Figure 126. DL ACK EGPRS block error ratio S10.5PS (rlc_19)

UL ACK EGPRS block error ratio MCS-n, S10.5PS (rlc_20)

Use: Used for UL ACK EGPRS block error ratio of any MCS 1 to9.

Sum over MCSn (RETRANS_RLC_DATA_BLOCKS_UL)100 * ----------------------------------------------------------------------

Sum over MCSn (UL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_UL)

where n can be from 1 to 9


Unit: %

Figure 127. UL ACK EGPRS block error ratio MCS-n, S10.5PS (rlc_20)

UL ACK EGPRS block error ratio MCS-n (rlc_20b)

Description: UL ACK EGPRS block error ratio MCSn.



Use: Used for UL ACK EGPRS block error ratio of any MCS fromMCS 1 to 9.

Sum over MCS-n (RETRANS_RLC_DATA_BLOCKS_UL)100 * -----------------------------------------------------------------------

Sum over MCS-n (UL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_UL)

where n can be from 1 to 9.Counters from table(s):p_nbsc_coding_scheme

Unit: %

Figure 128. UL ACK EGPRS block error ratio MCS-n (rlc_20b)

UL ACK EGPRS block error ratio MCS-n (rlc_20c)

Description: UL ACK EGPRS block error ratio MCSn.Use: Used to for UL ACK EGPRS block error ratio of any MCS

from MCS 1 to 9.

Sum over MCS-n (b.RETRANS_RLC_DATA_BLOCKS_UL)100 * -----------------------------------------------------------

Sum over MCS-n (b.UL_RLC_BLOCKS_IN_ACK_MODE- [ignor rlc data bl ul due bsn mcs n ack]+ b.RETRANS_RLC_DATA_BLOCKS_UL)

where n can be from 1 to 9.

[ignor rlc data bl ul due bsn egprs] =

trf_204aa.ignor_rlc_data_bl_ul_due_bsn * ------------------

trf_203 + trf_204a

[ignor rlc data bl ul due bsn egprs ack] =

[ignor rlc data bl ul sum over MCS1-9 (b.UL_RLC_Blocks_In_Ack_Mode)* ----------------------------------------------

ul due bsn egprs] sum over MCS1-9 (b.UL_RLC_Blocks_In_Ack_Mode+ b.UL_RLC_Blocks_In_Unack_Mode)

[ignor rlc data bl ul due bsn mcs n ack] =

[ignor rlc data bl sum over MCSn (b.UL_RLC_Blocks_In_Ack_Mode)* --------------------------------------------

ul due bsn egprs ack] sum over MCS1-9 (b.UL_RLC_Blocks_In_Ack_Mode)


Unit: %

Figure 129. UL ACK EGPRS block error ratio MCS-n (rlc_20c)



DL ACK EGPRS block error ratio MCS-n, S10.5PS (rlc_21)

Use: For DL ACK EGPRS block error ratio of any MCS 1 to 9.

Sum over MCSn (RETRANS_RLC_DATA_BLOCKS_DL)100 * ----------------------------------------------------------------------

Sum over MCSn (DL_RLC_BLOCKS_IN_ACK_MODE + RETRANS_RLC_DATA_BLOCKS_DL)



Unit: %

Figure 130. DL ACK EGPRS block error ratio MCS-n, S10.5PS (rlc_21)

UL ACK RLC data share MCS-n, S10.5PS (rlc_22)

Use: Indicates how big a share as a percentage UL ACK RLC datacomprises out of all RLC payload data.

Sum over MCS-n (UL_RLC_BLOCKS_IN_ACK_MODE)100* --------------------------------------------

Sum over MCS-n (UL_RLC_BLOCKS_IN_ACK_MODE+ UL_RLC_BLOCKS_IN_UNACK_MODE+ DL_RLC_BLOCKS_IN_ACK_MODE+ DL_RLC_BLOCKS_IN_UNACK_MODE)



Unit: %

Figure 131. UL ACK RLC data share MCS-n, S10.5PS (rlc_22)

UL UNACK RLC data share MCS-n, S10.5PS (rlc_23)

Use: Indicates how big a share as a percentage UL UNACK RLCdata comprises out of all RLC payload data.

Sum over MCS-n (UL_RLC_BLOCKS_IN_UNACK_MODE)100* ----------------------------------------------






Unit: %

Figure 132. UL UNACK RLC data share MCS-n, S10.5PS (rlc_23)

DL ACK RLC data share MCS-n, S10.5PS (rlc_24)

Use: Indicates how big a share as a percentage DL ACK RLC datacomprises out of all RLC payload data.

Sum over MCS-n (DL_RLC_BLOCKS_IN_ACK_MODE)100* --------------------------------------------

Sum over MCS-n (UL_RLC_BLOCKS_IN_ACK_MODE+ UL_RLC_BLOCKS_IN_UNACK_MODE+ DL_RLC_BLOCKS_IN_ACK_MODE++ DL_RLC_BLOCKS_IN_UNACK_MODE)



Unit: %

Figure 133. DL ACK RLC data share MCS-n, S10.5PS (rlc_24)

DL UNACK RLC data share MCS-n, S10.5PS (rlc_25)

Use: Indicates how big a share as a percentage DL UNACK RLCdata comprises out of all RLC payload data.

Sum over MCS-n (DL_RLC_BLOCKS_IN_UNACK_MODE)100* ----------------------------------------------




Unit: %

Figure 134. DL UNACK RLC data share MCS-n, S10.5PS (rlc_25)

UL CS3 retransmission ratio (rlc_27)

Description: Retransmission ratio for UL CS3 ACK RLC blocks.Use: High retransmission ratio means worse radio interface

conditions.

Sum over MCS-11(retrans_rlc_data_blocks_ul)



100 * --------------------------------------------------Sum over MCS-11(retrans_rlc_data_blocks_ul

+ ul_rlc_blocks_in_ack_mode)


Unit: %

Figure 135. UL CS3 retransmission ratio (rlc_27)

DL CS3 retransmission ratio (rlc_28)

Description: Retransmission ratio for DL CS3 ACK RLC blocks.Use: High retransmission ratio means worse radio interface

conditions.

Sum over MCS-11(retrans_rlc_data_blocks_dl)100 * --------------------------------------------------

Sum over MCS-11(retrans_rlc_data_blocks_dl+ dl_rlc_blocks_in_ack_mode)


Unit: %

Figure 136. DL CS3 retransmission ratio (rlc_28)

UL CS4 retransmission ratio (rlc_29)

Description: Retransmission ratio for UL CS4 ACK RLC blocks.Use: High retransmission ratio means worse radio interface

conditions.

Sum over MCS-12(retrans_rlc_data_blocks_ul)100 * --------------------------------------------------

Sum over MCS-12(retrans_rlc_data_blocks_ul+ ul_rlc_blocks_in_ack_mode)


Unit: %

Figure 137. UL CS4 retransmission ratio (rlc_29)

DL CS4 retransmission ratio (rlc_30)

Description: Retransmission ratio for DL CS4 ACK RLC blocks.Use: High retransmission ratio means worse radio interface

conditions.



Sum over MCS-12(retrans_rlc_data_blocks_dl)100 * --------------------------------------------------

Sum over MCS-12(retrans_rlc_data_blocks_dl+ dl_rlc_blocks_in_ack_mode)


Unit: %

Figure 138. DL CS4 retransmission ratio (rlc_30)

Ratio of UL CS2 ack blocks (rlc_32)

Use: Indicates the ratio of UL CS2 ack data blocks out of all GPRSUL ack data blocks.

Known problems: The formula assumes that all GRPS unack RLC traffic isusing CS1. With PCU2, GPRS unack RLC traffic can useCS1-4. If there is a significant amount of GRPS unack RLCtraffic with CS2, the values given by the formula will be toohigh.

sum(a.RLC_data_blocks_UL_CS2)100 * ------------------------------------------------------

sum(a.RLC_data_blocks_UL_CS1- a.RLC_data_blocks_UL_unack

+ a.RLC_data_blocks_UL_CS2)+ sum over MCS-11..12 (b.UL_RLC_BLOCKS_IN_ACK_MODE)


Unit: %

Figure 139. Ratio of UL CS2 ack blocks (rlc_32)

Ratio of DL CS2 ack blocks (rlc_33)

Use: Indicates the ratio of DL CS2 ack data blocks comprised outof all GPRS DL ack data blocks.

Known problems: The formula assumes that all GRPS unack RLC traffic isusing CS1. With PCU2, GPRS unack RLC traffic can useCS1-4. If there is a significant amount of GRPS unack RLCtraffic with CS2, the values given by the formula will be toohigh.

sum(a.RLC_data_blocks_DL_CS2)100 * --------------------------------------------------

sum(a.RLC_data_blocks_DL_CS1- a.RLC_data_blocks_DL_unack

+ a.RLC_data_blocks_DL_CS2)+ sum over MCS-11..12 (b.DL_RLC_BLOCKS_IN_ACK_MODE)




a = p_nbsc_packet_control_unitb = p_nbsc_coding_scheme

Unit: %

Figure 140. Ratio of DL CS2 ack blocks (rlc_33)


Use: Indicates the ratio of UL CS3 ack data blocks comprised outof all GPRS UL ack data blocks.

sum over MCS-11(b.UL_RLC_BLOCKS_IN_ACK_MODE)100 * --------------------------------------------------

sum(a.RLC_data_blocks_UL_CS1- a.RLC_data_blocks_UL_unack+ a.RLC_data_blocks_UL_CS2+ sum over MCS-11..12 (b.UL_RLC_BLOCKS_IN_ACK_MODE)


Unit: %




sum over MCS-11(b.DL_RLC_BLOCKS_IN_ACK_MODE)100 * ------------------------------------------------------

sum(a.RLC_data_blocks_DL_CS1- a.RLC_data_blocks_DL_unack+ a.RLC_data_blocks_DL_CS2+ sum over MCS-11..12 (b.DL_RLC_BLOCKS_IN_ACK_MODE)


Unit: %



Use: Indicates the ratio of UL CS4 ack data blocks comprised outof all GPRS UL ack data blocks.

sum over MCS-12(b.UL_RLC_BLOCKS_IN_ACK_MODE)100 * ------------------------------------------------------

sum(a.RLC_data_blocks_UL_CS1



- a.RLC_data_blocks_UL_unack+ a.RLC_data_blocks_UL_CS2+ sum over MCS-11..12 (b.UL_RLC_BLOCKS_IN_ACK_MODE)


Unit: %




sum over MCS-12(b.DL_RLC_BLOCKS_IN_ACK_MODE)100 * --------------------------------------------------

sum(a.RLC_data_blocks_DL_CS1- a.RLC_data_blocks_DL_unack+ a.RLC_data_blocks_DL_CS2+ sum over MCS-11..12 (b.DL_RLC_BLOCKS_IN_ACK_MODE)


Unit: %


GMSK RLC data block share, S10.5PS (rlc_39)

Use: Share of RLC blocks with MCS1..4 out of all used MCSs.

Sum over MCS 1..4 (UL_RLC_BLOCKS_IN_ACK_MODE +RETRANS_RLC_DATA_BLOCKS_UL +BAD_RLC_VALID_HDR_UL_UNACK +UL_RLC_BLOCKS_IN_UNACK_MODE +DL_RLC_BLOCKS_IN_ACK_MODE +RETRANS_RLC_DATA_BLOCKS_DL +DL_RLC_BLOCKS_IN_UNACK_MODE)------------------------------- * 100Sum over MCS 1..9 (UL_RLC_BLOCKS_IN_ACK_MODE +RETRANS_RLC_DATA_BLOCKS_UL +BAD_RLC_VALID_HDR_UL_UNACK +UL_RLC_BLOCKS_IN_UNACK_MODE +DL_RLC_BLOCKS_IN_ACK_MODE +RETRANS_RLC_DATA_BLOCKS_DL +DL_RLC_BLOCKS_IN_UNACK_MODE)




Unit: %

Figure 145. GMSK RLC data block share, S10.5PS (rlc_39)

GMSK RLC data share, S10.5PS (rlc_41)

Use: Share of RLC data bytes with MCS1..4 out of all used MCSs.

(sum over MCS-1 (xx)* 22+sum over MCS-2 (xx)* 28+sum over MCS-3 (xx)* 37+sum over MCS-4 (xx)* 44)

------------------------------ * 100(sum over MCS-1 (xx)*30+sum over MCS-2 (xx)*36+sum over MCS-3 (xx)*45+sum over MCS-4 (xx)*52+sum over MCS-5 (xx)*63+sum over MCS-6 (xx)*81+sum over MCS-7 (xx/2)*123+sum over MCS-8 (xx/2)*147+sum over MCS-9 (xx/2)*159)

where xx =UL_RLC_BLOCKS_IN_ACK_MODE +RETRANS_RLC_DATA_BLOCKS_UL +BAD_RLC_VALID_HDR_UL_UNACK +UL_RLC_BLOCKS_IN_UNACK_MODE +DL_RLC_BLOCKS_IN_ACK_MODE +RETRANS_RLC_DATA_BLOCKS_DL +DL_RLC_BLOCKS_IN_UNACK_MODE


Unit: %

Figure 146. GMSK RLC data share, S10.5PS (rlc_41)

GPRS UL ACK RLC data share, S10.5PS (rlc_42)

Use: Share of GPRS UL ACK RLC data in data for total data.

sum(RLC_data_blocks_UL_CS1 - RLC_data_blocks_UL_UNACK)*20+ sum(RLC_data_blocks_UL_CS2*30

100 * ------------------------------------------------------------ %sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30

+ RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30)+( sum over MCS-1 (xx)* 22

+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148)

Where xx=



(UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE+ DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE)


Unit: %

Figure 147. GPRS UL ACK RLC data share, S10.5PS (rlc_42)

GPRS UL ACK RLC data share (rlc_42a)

Description: Share of GPRS UL ACK RLC data in data for total data.Known problems: The double-counting of pre-emptive UL retransmissions has

not been taken into account.

sum(a.RLC_data_blocks_UL_CS1 - a.RLC_data_blocks_UL_UNACK)*20+ sum(a.RLC_data_blocks_UL_CS2)*30+ sum over MCS-11(b.UL_RLC_BLOCKS_IN_ACK_MODE)*36+ sum over MCS-12(b.UL_RLC_BLOCKS_IN_ACK_MODE)*50

100 * ---------------------------------------------------------------sum(a.RLC_data_blocks_UL_CS1*20 + a.RLC_data_blocks_UL_CS2*30

+ a.RLC_data_blocks_DL_CS1*20 + a.RLC_data_blocks_DL_CS2*30)+ sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148+ sum over MCS-11 (xx)*36+ sum over MCS-12 (xx)*50

Where xx=b.UL_RLC_BLOCKS_IN_ACK_MODE + b.UL_RLC_BLOCKS_IN_UNACK_MODE

+ b.DL_RLC_BLOCKS_IN_ACK_MODE + b.DL_RLC_BLOCKS_IN_UNACK_MODE


Unit: %

Figure 148. GPRS UL ACK RLC data share (rlc_42a)

GPRS UL UNACK RLC data share, S10.5PS (rlc_43)

Use: Share of GPRS UL UNACK RLC data in data for total data.

sum(RLC_data_blocks_UL_UNACK)*20100 * ----------------------------------------------------------%

sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30+ RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30)+( sum over MCS-1 (xx)* 22

+ sum over MCS-2 (xx)* 28



+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148)

Where xx=(UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE

+ DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE)


Unit: %

Figure 149. GPRS UL UNACK RLC data share, S10.5PS (rlc_43)

GPRS UL UNACK RLC data share (rlc_43a)

Description: Share of GPRS UL UNACK RLC data in data for total data.Known problems: The double-counting of pre-emptive UL retransmissions has


sum(a.RLC_data_blocks_UL_UNACK)*20+ sum over MCS-11(b.UL_RLC_BLOCKS_IN_UNACK_MODE)*36+ sum over MCS-12(b.UL_RLC_BLOCKS_IN_UNACK_MODE)*50

100 * --------------------------------------------------------------sum(a.RLC_data_blocks_UL_CS1*20 + a.RLC_data_blocks_UL_CS2*30





Unit: %

Figure 150. GPRS UL UNACK RLC data share (rlc_43a)



GPRS DL ACK RLC data share, S10.5PS (rlc_44)

Use: Share of GPRS DL ACK RLC data in data for total data.

sum(RLC_data_blocks_DL_CS1-RLC_data_blocks_DL_UNACK)*20+ sum(RLC_data_blocks_DL_CS2*30

100 * ----------------------------------------------------------%sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30+ RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30)+( sum over MCS-1 (xx)* 22





Unit: %

Figure 151. GPRS DL ACK RLC data share, S10.5PS (rlc_44)

GPRS DL ACK RLC data share (rlc_44a)

Description: Share of GPRS DL ACK RLC data in data for total data.Known problems: The double-counting of pre-emptive UL retransmissions has


sum(a.RLC_data_blocks_DL_CS1 - a.RLC_data_blocks_DL_UNACK)*20+ sum(a.RLC_data_blocks_DL_CS2)*30+ sum over MCS-11(b.DL_RLC_BLOCKS_IN_ACK_MODE)*36+ sum over MCS-12(b.DL_RLC_BLOCKS_IN_ACK_MODE)*50








a = p_nbsc_packet_control_unitb = p_nbsc_coding_scheme

Unit: %

Figure 152. GPRS DL ACK RLC data share (rlc_44a)

GPRS DL UNACK RLC data share, S10.5PS (rlc_45)

Use: Share of GPRS DL UNACK RLC data in data for total data.

sum(RLC_data_blocks_DL_UNACK)*20100 * ----------------------------------------------------------%

sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30+ RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30)+( sum over MCS-1 (xx)* 22




Counters from table(s):p_nbsc_packet_control_unitp_nbsc_coding_schemeUnit: %

Figure 153. GPRS DL UNACK RLC data share, S10.5PS (rlc_45)

GPRS DL UNACK RLC data share (rlc_45a)

Description: Share of GPRS DL UNACK RLC data in data for total data.Known problems: The double-counting of pre-emptive UL retransmissions has


sum(a.RLC_data_blocks_DL_UNACK)*20+ sum over MCS-11(b.DL_RLC_BLOCKS_IN_UNACK_MODE)*36+ sum over MCS-12(b.DL_RLC_BLOCKS_IN_UNACK_MODE)*50

100 * ----------------------------------------------------------sum(a.RLC_data_blocks_UL_CS1*20 + a.RLC_data_blocks_UL_CS2*30

+ a.RLC_data_blocks_DL_CS1*20 + a.RLC_data_blocks_DL_CS2*30)+ sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148+ sum over MCS-11 (xx)*36



+ sum over MCS-12 (xx)*50




Unit: %

Figure 154. GPRS DL UNACK RLC data share (rlc_45a)

EGPRS UL ACK RLC data share, S10.5PS (rlc_46)

Use: Share of EGPRS UL ACK RLC data in total data.

( sum over MCS-1 (yy)* 22+ sum over MCS-2 (yy)* 28+ sum over MCS-3 (yy)* 37+ sum over MCS-4 (yy)* 44+ sum over MCS-5 (yy)* 56+ sum over MCS-6 (yy)* 74+ sum over MCS-7 (yy/2)*112+ sum over MCS-8 (yy/2)*136+ sum over MCS-9 (yy/2)*148)

100 * ----------------------------------------------------------%sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30

+ RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30)+( sum over MCS-1 (xx)* 22




Where yy= UL_RLC_BLOCKS_IN_ACK_MODECounters from table(s):p_nbsc_packet_control_unitp_nbsc_coding_scheme

Unit: %

Figure 155. EGPRS UL ACK RLC data share, S10.5PS (rlc_46)

EGPRS UL ACK RLC data share (rlc_46a)

Description: Share of EGPRS UL ACK RLC data in total data.Known problems: The double-counting of pre-emptive UL retransmissions has




sum over MCS-1 (yy)* 22+ sum over MCS-2 (yy)* 28+ sum over MCS-3 (yy)* 37+ sum over MCS-4 (yy)* 44+ sum over MCS-5 (yy)* 56+ sum over MCS-6 (yy)* 74+ sum over MCS-7 (yy/2)*112+ sum over MCS-8 (yy/2)*136+ sum over MCS-9 (yy/2)*148





Where yy= b.UL_RLC_BLOCKS_IN_ACK_MODE


Unit: %

Figure 156. EGPRS UL ACK RLC data share (rlc_46a)

EGPRS UL UNACK RLC data share, S10.5PS (rlc_47)

Use: Share of EGPRS UL UNACK RLC data in total data.


100 * ---------------------------------------------------------- %sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30

+ RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30)+( sum over MCS-1 (xx)* 22




Where xx=(UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE+ DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE)

Where yy= UL_RLC_BLOCKS_IN_UNACK_MODECounters from table(s):p_nbsc_packet_control_unitp_nbsc_coding_schemeUnit: %

Figure 157. EGPRS UL UNACK RLC data share, S10.5PS (rlc_47)

EGPRS UL UNACK RLC data share (rlc_47a)

Description: Share of EGPRS UL UNACK RLC data in total data.Known problems: The double-counting of pre-emptive UL retransmissions has







Where yy= b.UL_RLC_BLOCKS_IN_UNACK_MODE


Unit: %

Figure 158. EGPRS UL UNACK RLC data share (rlc_47a)



EGPRS DL ACK RLC data share, S10.5PS (rlc_48)

Use: Share of EGPRS DL ACK RLC data in total data.







Where yy= DL_RLC_BLOCKS_IN_ACK_MODE


Unit: %

Figure 159. EGPRS DL ACK RLC data share, S10.5PS (rlc_48)

EGPRS DL ACK RLC data share (rlc_48a)

Description: Share of EGPRS DL ACK RLC data in total data.Known problems: The double-counting of pre-emptive UL retransmissions has



100 * -----------------------------------------------------------------sum(a.RLC_data_blocks_UL_CS1*20 + a.RLC_data_blocks_UL_CS2*30+ a.RLC_data_blocks_DL_CS1*20 + a.RLC_data_blocks_DL_CS2*30)+ sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44



+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148+ sum over MCS-11 (xx)*36+ sum over MCS-12 (xx)*50



Where yy= b.DL_RLC_BLOCKS_IN_ACK_MODE


Unit: %

Figure 160. EGPRS DL ACK RLC data share (rlc_48a)

EGPRS DL UNACK RLC data share, S10.5PS (rlc_49)

Use: Share of EGPRS DL UNACK RLC data in total data.







Where yy= DL_RLC_BLOCKS_IN_UNACK_MODE


Unit: %

Figure 161. EGPRS DL UNACK RLC data share, S10.5PS (rlc_49)



EGPRS DL UNACK RLC data share (rlc_49a)

Description: Share of EGPRS DL UNACK RLC data in total data.Known problems: The double-counting of pre-emptive UL retransmissions has







Where yy= b.DL_RLC_BLOCKS_IN_UNACK_MODE


Unit: %

Figure 162. EGPRS DL UNACK RLC data share (rlc_49a)

Ratio of UL CS1 (GPRS_ack) (rlc_54b)

Description: Ratio of UL CS1 (GPRS, ack)Use: The formula is used to monitor the quality of radio link by

looking at coding scheme distribution for UL and DLseparately.

Known problems: GPRS link adaptation may not be used in all the cells. Theformula assumes that all GPRS unack RLC traffic is usingCS1. With PCU2, GPRS unack RLC traffic can use CS1-4. Ifthere is a significant amount of GPRS unack RLC traffic withCS2, the values given by the formula will be too low.

sum(a.RLC_Data_Blocks_UL_CS1 - a.RLC_Data_Blocks_UL_Unack)100 * -----------------------------------------------------------

sum(a.RLC_data_blocks_UL_CS1 - a.RLC_Data_Blocks_UL_Unack+ a.RLC_data_blocks_UL_CS2)



+ sum over MCS-11..12(b.UL_RLC_BLOCKS_IN_ACK_MODE)


Unit: %

Figure 163. Ratio of UL CS1 (GPRS_ack) (rlc_54b)

Ratio of DL CS1 (GPRS_ack) (rlc_55b)

Description: Ratio of DL CS1 (GPRS, ack)Use: This formula is used for monitoring the quality of radio link

by looking at coding scheme distribution for UL and DLseparately.

Known problems: GPRS link adaptation may not be used in all the cells.Formula assumes that all GRPS unack RLC traffic is usingCS1. With PCU2, GPRS unack RLC traffic can use CS1-4. Ifthere is a significant amount of GRPS unack RLC traffic withCS2, the values given by the formula will be too low.

sum(a.RLC_Data_Blocks_DL_CS1 - a.RLC_Data_Blocks_DL_Unack)100 * -----------------------------------------------------------

sum(a.RLC_data_blocks_DL_CS1 - a. RLC_Data_Blocks_DL_Unack+ a.RLC_data_blocks_DL_CS2)+ sum over MCS-11..12(b.DL_RLC_BLOCKS_IN_ACK_MODE)


Unit: %

Figure 164. Ratio of DL CS1 (GPRS_ack) (rlc_55b)

EGPRS UL block error ratio (rlc_60)

Description: This formula shows BLER of EGPRS connection in UL.Use: To measure the quality of the uplink EGPRS radio link.

Sum over MCS-n (BAD_RLC_VALID_HDR_UL_ACK + BAD_RLC_VALID_HDR_UL_UNACK)100 * --------------------------------------------------------------------------

Sum over MCS-n (BAD_RLC_VALID_HDR_UL_ACK + BAD_RLC_VALID_HDR_UL_UNACK+ UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE)

where n can be from 1 to 9Counters from table(s):p_nbsc_coding_scheme

Unit: %

Figure 165. EGPRS UL block error ratio (rlc_60)



GMSK modulation used in DL (rlc_61)

Description: This formula shows how many times GMSK modulation isused in DL instead of 8PSK modulation (normally 8PSKoffers better performance).

Use: When an uplink GPRS TBF uses the same timeslots as adownlink EDGE TBF, the EDGE TBF is forced to use GMSKmodulation. The number of forced modulation methodchanges are shown with this formula.

a.DL_8PSK_TO_GMSK_DUE_UL_GPRS----------------------------------------------------sum over mcs1...9 of (b.dl_rlc_blocks_in_ack_mode

+ b.dl_rlc_blocks_in_unack_mode)


Unit: Number

Figure 166. GMSK modulation used in DL (rlc_61)

2.6 Frame relay (frl)

Kbytes in sent frames, S9PS (frl_1)

Use: Total data volume over all DLCI. Frame relay signalling isdelivered in DLCI 0, so counters do not include thesemessages. This KPI includes NS and BSSGP signalling whichmeans that the counters start to get pegged when these layershave been created.

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

Unit: Kbyte

Figure 167. Kbytes in sent frames, S9PS (frl_1)



Kbytes in received frames, S9PS (frl_2)

Use: Total data volume over all DLCI. Frame relay signalling isdelivered in DLCI 0, so counters do not include thesemessages. This KPI includes NS and BSSGP signalling whichmeans that the counters start to get pegged when these layershave been created.

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_relayUnit: Kbyte

Figure 168. Kbytes in received frames, S9PS (frl_2)

’Wrong check seq.’ errors per Mbyte, S9PS (frl_3)

Use: Quality indicator of the HDLC layer.

sum(FRMS_WRONG_CHECK_SEQ_)1000 * ---------------------------------------------

sum(DLCI_1_BYTES_REC + DLCI_1_BYTES_DISC_REC+ DLCI_2_BYTES_REC + DLCI_2_BYTES_DISC_REC+ DLCI_3_BYTES_REC + DLCI_3_BYTES_DISC_REC+ DLCI_4_BYTES_REC + DLCI_4_BYTES_DISC_REC+ DLCI_5_BYTES_REC + DLCI_5_BYTES_DISC_REC)

Counters from table(s):p_nbsc_frame_relayUnit: errors per Mbyte

Figure 169. ‘Wrong check seq.’ errors per Mbyte, S9PS (frl_3)

‘Other’ errors per Mbyte, S9PS (frl_4)

Use: Quality indicator of the HDLC layer.

sum(OTHER_FRAME_ERROR)1000 * ---------------------------------------------

sum(DLCI_1_BYTES_REC + DLCI_1_BYTES_DISC_REC+ DLCI_2_BYTES_REC + DLCI_2_BYTES_DISC_REC+ DLCI_3_BYTES_REC + DLCI_3_BYTES_DISC_REC+ DLCI_4_BYTES_REC + DLCI_4_BYTES_DISC_REC+ DLCI_5_BYTES_REC + DLCI_5_BYTES_DISC_REC)

Counters from table(s):p_nbsc_frame_relayUnit: errors per Mbyte

Figure 170. ‘Other’ errors per Mbyte, S9PS (frl_4)



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)


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

Bytes in discarded received frames, S9PS (frl_6)

sum(dlci_1_bytes_disc_rec+dlci_2_bytes_disc_rec+dlci_3_bytes_disc_rec+dlci_4_bytes_disc_rec+dlci_5_bytes_disc_rec)


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

Maximum sent load %, S9PS (frl_7)

Use: Indicates the load % of the frame relay bearer for outgoingdata to SGSN.

Known problems: The access rate is taken from configuration data andrepresents only the current setting. This may cause errorswhen used in historical perspective if the settings have beenchanged.

max per bearer_id(8*(dlci_1_bytes_sent

+ dlci_2_bytes_sent+ dlci_3_bytes_sent+ dlci_4_bytes_sent+ dlci_5_bytes_sent)/(period_duration*60))

100 * ------------------------------------------------ %sum per frbc over all unlocked child nsvc

(c_nsvc.committed_info_rate*16);

frbc object_instance = bearer_id in p_nbsc_frame_relay


Figure 173. Maximum sent load %, S9PS (frl_7)



Maximum received load %, S9PS (frl_8)

Use: Indicates the load % of the frame relay bearer for incomingdata from SGSN.

Known problems: The access rate is taken from configuration data andrepresents only the current setting. This may cause errorswhen used in historical perspective if the settings have beenchanged.

max per bearer_id(8*(dlci_1_bytes_rec

+ dlci_2_bytes_rec+ dlci_3_bytes_rec+ dlci_4_bytes_rec+ dlci_5_bytes_rec)/(period_duration*60))

100 * ------------------------------------------------ %sum per frbc over all unlocked child nsvc(c_nsvc.committed_info_rate*16);

frbc object_instance = bearer_id in p_nbsc_frame_relay


Figure 174. Maximum received load %, S9PS (frl_8)

Sent frames, S9PS (frl_9)

sum(dlci_1_sent_frms+dlci_2_sent_frms+dlci_3_sent_frms+dlci_4_sent_frms+dlci_5_sent_frms)


Figure 175. Sent frames, S9PS (frl_9)

Received frames, S9PS (frl_10)

sum(dlci_1_rec_frms+dlci_2_rec_frms+dlci_3_rec_frms+dlci_4_rec_frms+dlci_5_rec_frms)


Figure 176. Received frames, S9PS (frl_10)



Discarded sent frames, S9PS (frl_11)

sum(dlci_1_disc_sent_frms+dlci_2_disc_sent_frms+dlci_3_disc_sent_frms+dlci_4_disc_sent_frms+dlci_5_disc_sent_frms)


Figure 177. Discarded sent frames, S9PS (frl_11)

Discarded received frames, S9PS (frl_12)

sum(dlci_1_disc_rec_frms+dlci_2_disc_rec_frms+dlci_3_disc_rec_frms+dlci_4_disc_rec_frms+dlci_5_disc_rec_frms)


Figure 178. Discarded received frames, S9PS (frl_12)

Discarded bytes, UL NS-VC congestion S9PS (frl_13a)

sum(dlci_1_disc_ul_ns_udata+dlci_2_disc_ul_ns_udata+dlci_3_disc_ul_ns_udata+dlci_4_disc_ul_ns_udata+dlci_5_disc_ul_ns_udata)

Counters from table(s):p_nbsc_frame_relayUnit: bytes

Figure 179. Discarded bytes, UL NS-VC congestion S9PS (frl_13a)

2.7 HSCSD (hsd)

Throughput ratio, S7HS (hsd_15)

Use: Indicates the percentage of the offered data that is put through.

Sum(96*(ONE_TCH_SEIZ_TIME_9600 + TWO_TCH_SEIZ_TIME_9600+ THREE_TCH_SEIZ_TIME_9600 + FOUR_TCH_SEIZ_TIME_9600)

+ 144*(ONE_TCH_SEIZ_TIME_14400 + TWO_TCH_SEIZ_TIME_14400



+ THREE_TCH_SEIZ_TIME_14400 + FOUR_TCH_SEIZ_TIME_14400))100*-------------------------------------------------------------------- %

Sum(96*(ONE_TCH_REQ_TIME_9600 + TWO_TCH_REQ_TIME_9600+ THREE_TCH_REQ_TIME_9600 + FOUR_TCH_REQ_TIME_9600)

+144*(ONE_TCH_REQ_TIME_14400 + TWO_TCH_REQ_TIME_14400+ THREE_TCH_REQ_TIME_14400 + FOUR_TCH_REQ_TIME_14400))

Figure 180. Throughput ratio, S7HS (hsd_15)

Bps traffic share, S7HS (hsd_49)

Use: Indicates the share of 9600 bps traffic out of all traffic.

Sum(ONE_TCH_SEIZ_TIME_9600+TWO_TCH_SEIZ_TIME_9600+THREE_TCH_SEIZ_TIME_9600+FOUR_TCH_SEIZ_TIME_9600)

100*------------------------------------------------------------ %Sum(ONE_TCH_SEIZ_TIME_9600+TWO_TCH_SEIZ_TIME_9600

+THREE_TCH_SEIZ_TIME_9600+FOUR_TCH_SEIZ_TIME_9600+ONE_TCH_SEIZ_TIME_14400+TWO_TCH_SEIZ_TIME_14400+THREE_TCH_SEIZ_TIME_14400+FOUR_TCH_SEIZ_TIME_14400)

Figure 181. Bps traffic share, S7HS (hsd_49)

Bps traffic share, S7HS (hsd_50)

Use: Indicates the share of share of 14400 bps traffic out of alltraffic.

Sum(ONE_TCH_SEIZ_TIME_14400+TWO_TCH_SEIZ_TIME_14400+THREE_TCH_SEIZ_TIME_14400+FOUR_TCH_SEIZ_TIME_14400)

100*------------------------------------------------------------- %Sum(ONE_TCH_SEIZ_TIME_9600+TWO_TCH_SEIZ_TIME_9600

+THREE_TCH_SEIZ_TIME_9600+FOUR_TCH_SEIZ_TIME_9600+ONE_TCH_SEIZ_TIME_14400+TWO_TCH_SEIZ_TIME_14400+THREE_TCH_SEIZ_TIME_14400+FOUR_TCH_SEIZ_TIME_14400)

Figure 182. Bps traffic share, S7HS (hsd_50)

2.8 Dynamic Abis Pool (dap)

Average usage of DL Dynamic Abis Pool, S10.5PS (dap_1a)

Description: Percentage of Average usage of DL Dynamic Abis Pool fromthe total amount of subTSLs in DL EDAP.

Use: Indicates the usage of pool resources.Known Problems: There may be EDAP allocations only in one direction at a

time. This may lower the averages, and most probably thevalues in both directions are smaller than actual percentageaverages. Separate counters are needed for both 76000 and76003 in DL and UL. This fix is in future plans.



Sum(AVERAGE_DL_EDAP_USAGE_SUM)100 * ------------------------------

Sum(TOTAL_PCM_SUBTSLS_IN_EDAP)

Counters from table(s):p_nbsc_dynamic_abis

Unit: %

Figure 183. Average usage of DL Dynamic Abis Pool, S10.5PS (dap_1a)

Average usage of UL Dynamic Abis Pool, S10.5PS (dap_2a)

Description: Percentage of Average usage of UL Dynamic Abis Pool fromthe total amount of subTSLs in UL EDAP.

Use: Indicates the usage of pool resources.Known problems: There may be EDAP allocations only in one direction at a

time. This may lower the averages, and most probably thevalues in both directions are smaller than actual percentageaverages. Separate counters are needed for both 76000 and76003 in DL and UL. This fix is in future plans.

Sum(AVERAGE_UL_EDAP_USAGE_SUM)100 * ------------------------------

Sum(TOTAL_PCM_SUBTSLS_IN_EDAP)


Unit: %

Figure 184. Average usage of UL Dynamic Abis Pool, S10.5PS (dap_2a)

Average usage of UL Dynamic Abis Pool (dap_2b)

Description: Percentage of average usage of UL Dynamic Abis Pool fromthe total amount of subTSLs in UL EDAP.

Use: Indicates the usage of pool resources.

sum(average_ul_edap_usage_sum)100 * ---------------------------------- %

sum(tot_nbr_of_pcm_sts_in_edap_ul)


Unit: %

Figure 185. Average usage of UL Dynamic Abis Pool (dap_2b)



Average Available PCM Sub-TSL, S10.5PS (dap_3)

Use: Average available amount of sub-TSLs in EDAP. Indicatestotal sub-TSLs in EDAP.

Sum(TOTAL_PCM_SUBTSLS_IN_EDAP)-------------------------------Sum(AVERAGE_EDAP_USAGE_DEN)


Unit: sub-TSLs

Figure 186. Average Available PCM Sub-TSL, S10.5PS (dap_3)

Inadequate EDAP resources in DL limited by EDAP size (dap_7a)

Description: Time per gigabytes when adequacy of requested EDAPresources cannot be granted for a scheduled DL TBF in BTSswhere EGPRS is enabled. Effects of PCU limitationconsidered.

Use: Indicates the time per gigabytes when the available DL EDAPresources are inadequate because of EDAP size.The formula may not give correct values if:1) The object aggregation level is smaller than BSC level, and2) One or more BTSs in the area has more than one dynamicabis pool connected.

(Sum(DL_Indadeq_Time_minutes)/Sum(DL GPRS payload_Gbyte + DL EGPRS payload_Gbyte)

=

sum( a.dl_tbfs_with_inadeq_edap_res - a.dl_mcs_limited_by_pcu) / (50 * 60)--------------------------------------------------------------------------sum over BTS with EGENA = Y( b.rlc_data_blocks_dl_cs1 *20+ b.rlc_data_blocks_dl_cs2 *30+ sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148+ sum over MCS-11(xx)*36+ sum over MCS-12(xx)*50

) / (1024*1024*1024)

where xx = (c.dl_rlc_blocks_in_ack_mode + c.dl_rlc_blocks_in_unack_mode)

Counters from table(s):a = p_nbsc_dynamic_abisb = p_nbsc_packet_control_unitc = p_nbsc_coding_scheme



Unit: min/GB

Figure 187. Inadequate EDAP resources in DL limited by EDAP size (dap_7a)

Inadequate EDAP resources in DL (dap_7b)

Description: Time per gigabytes when adequacy of requested EDAPresources cannot be granted for a scheduled DL TBF in BTSswhere EGPRS is enabled.

Use: Indicates the time per gigabytes when the available DL EDAPresources are inadequate.

Note: This formula is not "PCU2 compatible", because CS3 & CS4are not included.The formula may not give correct values if:1) The object aggregation level is smaller than BSC level, and2) One or more BTSs in the area has more than one dynamicabis pool connected

Sum(DL_Indadeq_Time_minutes)/Sum(DL GPRS payload_Gbyte+DL EGPRS payload_Gbyte)

=

sum( a.dl_tbfs_with_inadeq_edap_res) / (50 * 60)-------------------------------------------------sum over BTS with EGENA = Y( rlc_data_blocks_dl_cs1 *20+ rlc_data_blocks_dl_cs2 *30+ sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148

) / (1024*1024*1024)where xx = (dl_rlc_blocks_in_ack_mode + dl_rlc_blocks_in_unack_mode)


Unit: min/GB

Figure 188. Inadequate EDAP resources in DL (dap_7b)

No EDAP resources in UL due to too small EDAP pool size (dap_8c)

Description: Time per gigabytes when the requested UL TBF cannot beserviced due to too small EDAP pool size in BTSs whereEGPRS is enabled.



Use: Indicates UL congestion time per gigabytes of EDAPresources available limited by the EDAP pool size.The formula may not give correct values if:1) The object aggregation level is smaller than BSC level, and2) One or more BTSs in the area has more than one dynamicabis pool connected

Sum(UL_No_Resource_minutes)/Sum(UL GPRS payload_Gbyte + UL EGPRS payload_Gbyte)

=

sum(a.ul_tbfs_without_edap_res - a.ul_mcs_limited_by_pcu) / (50 * 60)------------------------------------------------------------------------sum over BTS with EGENA = Y( b.rlc_data_blocks_ul_cs1 *20+ b.rlc_data_blocks_ul_cs2 *30+ sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148+ sum over MCS-11(xx)*36+ sum over MCS-12(xx)*50

) / (1024*1024*1024)where xx = (c.ul_rlc_blocks_in_ack_mode + c.ul_rlc_blocks_in_unack_mode)


Unit: min/GB

Figure 189. No EDAP resources in UL due to too small EDAP pool size (dap_8c)

Sum(UL_No_Resource_minutes)/Sum(UL GPRS payload_Gbyte + ULEGPRS payload_Gbyte) (dap_9)

Description: Time per gigabytes when adequacy of requested EDAPresources cannot be granted for a scheduled DL TBF in BTSswhere EGPRS is enabled. Only PCU limitations areconsidered.

Use: Indicates the time per gigabytes when the available DL EDAPresources are inadequate because of PCU capacity.The formula may not give correct values if:1) The object aggregation level is smaller than BSC level, and2) One or more BTSs in the area have more than one dynamicabis pool connected

Sum (DL_Indadeq_Time_minutes)/Sum (DL GPRS payload_Gbyte + DL EGPRS payload_Gbyte)

=



sum(a.dl_mcs_limited_by_pcu) / (50 * 60)--------------------------------------------------------------------------sum over BTS with EGENA = Y( b.rlc_data_blocks_dl_cs1 *20+ b.rlc_data_blocks_dl_cs2 *30+ sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148+ sum over MCS-11(xx)*36+ sum over MCS-12(xx)*50

) / (1024*1024*1024)where xx = (c.dl_rlc_blocks_in_ack_mode + c.dl_rlc_blocks_in_unack_mode)


Unit: min/GB

Figure 190. Sum(UL_No_Resource_minutes)/Sum(UL GPRS payload_Gbyte +UL EGPRS payload_Gbyte) (dap_9)

Inadequate EDAP resources in UL limited by PCU (dap_10)

Description: Time per gigabytes when adequacy of requested EDAPresources cannot be granted for a scheduled UL TBF in BTSswhere EGPRS is enabled. Only PCU limitations areconsidered.

Use: Indicates the time per gigabytes when the available UL EDAPresources are inadequate because of PCU capacity.The formula may not give correct values if:1) The object aggregation level is smaller than BSC level, and2) One or more BTSs in the area have more than one dynamicabis pool connected.

Sum (UL_Indadeq_Time_minutes)/Sum (UL GPRS payload_Gbyte + UL EGPRS payload_Gbyte)

=

sum(a.ul_mcs_limited_by_pcu) / (50 * 60)--------------------------------------------------------------------------sum over BTS with EGENA = Y( b.rlc_data_blocks_ul_cs1 *20+ b.rlc_data_blocks_ul_cs2 *30+ sum over MCS-1 (xx)* 22+ sum over MCS-2 (xx)* 28+ sum over MCS-3 (xx)* 37+ sum over MCS-4 (xx)* 44+ sum over MCS-5 (xx)* 56+ sum over MCS-6 (xx)* 74+ sum over MCS-7 (xx/2)*112+ sum over MCS-8 (xx/2)*136+ sum over MCS-9 (xx/2)*148



+ sum over MCS-11(xx)*36+ sum over MCS-12(xx)*50

) / (1024*1024*1024)

where xx = (c.ul_rlc_blocks_in_ack_mode + c.ul_rlc_blocks_in_unack_mode)


Unit: min/GB

Figure 191. Inadequate EDAP resources in UL limited by PCU (dap_10)

2.9 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 onthe BTS configuration which does not often change.

avg(ave_rach_slot/res_acc_denom1)

Counters from table(s):p_nbsc_res_access

Figure 192. Average RACH slot, S1 (rach_1)

Peak RACH load, average, S1 (rach_2)

Use: Indicates the absolute peak value during a measurementperiod. Correlates strongly with UL interference.

Experiences on use: High values may suggest that MSs have problems inaccessing the BTS. High values do not mean high load onSDCCH because SDCCH is needed only if the RACH passesthe detection in BTS.

Known problems: The peak value does not indicate yet how many times therehave been other peaks during the measurement period.

Open questions: How serious the high values really are from the MS point ofview?

avg(peak_rach_load)


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



Peak RACH load %, S1 (rach_3)

Use: This PI indicates how close to full capacity the peak use ofRACH has been during the measurement period.

Experiences on use: It is quite normal that the momentary (peak) load can behigh. Average RACH load is a more meaningful indicator.

max(peak_rach_load)100 * ---------------------------------- %

max(ave_rach_busy/res_acc_denom1)


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

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

avg(ave_rach_busy/res_acc_denom3)100 * ------------------------------------ %

avg(ave_rach_slot/res_acc_denom1)


Figure 195. 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 ‘average RACH slot’ (rach_1)there probably are access problems and MS users get, moreoften than usual, 3 beeps when trying to start calls.

avg(ave_rach_busy/res_acc_denom3)


Figure 196. 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 theghosts have legal establishment cause and get further toSDCCH.Note that the actual ghost filtering is in BTS.

sum(ghost_ccch_res - rej_seiz_att_due_dist)


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

Total RACH rejection ratio, S7 (rach_7)

Use: Ratio of all RACH rejections to total number of channelrequired messages received.Note that the counter ghost_ccch_res contains both ghosts andrejections due to distance checking. The latter one is anoptional feature of BSC.

sum(ghost_ccch_res - rej_seiz_att_due_dist; illegal establ. cause+ bcsu_overload_lower_limit+ bcsu_overload_upper_limit+ bcsu_overload_deleted_rach)

100 * --------------------------------------------------------------------- %sum(ch_req_msg_rec)


Figure 198. Total RACH rejection ratio, S7 (rach_7)

2.10 SDCCH drop failures (sd)

Ghosts detected on SDCCH and other failures, S1 (sd_1)

Use: This part of ghost RACH accesses comprises:- ghosts which have an occasionally valid establishmentcause. These should comprise statistically 5/8 of all ghosts inGSM phase 1. Another 3/8 of ghosts are detected alreadybefore SDCCH based on some invalid establishment cause. InGSM2 the ratio 5/8 and 3/8 is no longer valid.- multiple seizures of SDCCH.

Known problems: This counter includes also IMSI detaches which do not havea counter of their own.

sum(a.sdcch_assign)- sum(b.succ_seiz_term+ b.succ_seiz_orig



+ b.sdcch_loc_upd+ b.succ_emerg_call+ b.sdcch_call_re_est)

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_res_access

Figure 199. Ghosts detected on SDCCH and other failures, S1 (sd_1)

Ghosts detected on SDCCH and other failures, S1 (sd_1a)

Use: This part of ghost RACH accesses comprises:- ghosts which have an occasionally valid establishmentcause. These should comprise statistically 5/8 of all ghosts inGSM phase 1. Another 3/8 of ghosts are detected alreadybefore SDCCH based on some invalid establishment cause. InGSM2 the ratio 5/8 and 3/8 is no longer valid.- multiple seizures of SDCCH.


sum(a.sdcch_assign)- sum(b.succ_seiz_term

+ b.succ_seiz_orig+ b.sdcch_loc_upd+ b.sdcch_emerg_call+ b.sdcch_call_re_est+ imsi_detach_sdcch)


Figure 200. Ghosts detected on SDCCH and other failures, S1 (sd_1a)

Ghosts detected on SDCCH and other failures (sd_1b)

Use: This part of ghost RACH accesses comprises:- ghosts which have an occasionally valid establishmentcause. These should comprise statistically 5/8 of all ghosts inGSM phase 1. Another 3/8 of ghosts are detected alreadybefore SDCCH, based on some invalid establishment cause.In GSM2 the ratio 5/8 and 3/8 is no longer valid.- multiple seizures of SDCCH .


sum(a.sdcch_assign)- sum(b.succ_seiz_term

+ b.succ_seiz_orig+ b.sdcch_loc_upd+ b.sdcch_emerg_call



+ b.sdcch_call_re_est+ imsi_detach_sdcch+b.succ_seiz_supplem_serv)


Unit: number

Figure 201. Ghosts detected on SDCCH and other failures (sd_1b)

2.10.1 SDCCH drop counters

SDCCH drop calls are counted as the sum of the following counters:



Table 4. SDCCH Drop Counters

ID Name Description

1003 SDCCH_RADIO_FAIL A coverage problem, for example

• MS moves out from timing advance

Common in connection with coverage problems.

Triggered also if the MS user clears the call in the SDCCHphase.

1004 SDCCH_RF_OLD_HO Transactions have ended due to an old channel failure in HO.

For instance, a failure in Directed Retry drops the call andtriggers this counter in the source cell.

1075 SDCCH_ABIS_FAIL_CALL Transactions have ended due to Abis problems. Missingchannel activation ack or if no indication of call establishmenthas been received. Augmented when the BSC receives anEstablish indication the contents of which are corrupted, ormore commonly when a timer (T3101, default 3 sec) expireswhile waiting for the Establish indication. The Establishindication is the first message sent from the BTS to the BSCafter the MS has successfully accessed the SDCCH.

• Ghost seizures which accidentally have a validestablishment cause and are detected on SDCCH,increment this counter.

• Multiple SDCCH seizures may cause these failures. If theMS has to send multiple random accesses for a call orlocation update, it is possible that there will be multiplereservations of SDCCH for one mobile naturally the mobilecan use only one of these and the rest will eventually timeout and result in sdcch_abis_fail_call. Onereason for multiple SDCCH seizures can be DLinterference.

• Too short frequency&BSIC reuse distance may cause HOburst from one cell to be interpreted as RACH bursts inanother cell causing false SDCCH seizures. This reasonmay be suspected if there are short, 2 - 3 second peakswith high blocking rate on SDCCH.

• A more rare yet possible reason are failing LUs.

1076 SDCCH_ABIS_FAIL_OLD Same as above but when trying to return back to the oldchannel in HO.

1078 SDCCH_A_IF_FAIL_CALL Transactions have ended due to A interface problems. A highvalue can be related to IMSI detaches (in S3).

See #1 for all possible causes. SDCCH observation may beused to diagnose the cause on cell level. If this occurs in theentire network or BSS areas, use Clear Code measurementfor cause analysis.



To see what DX causes can trigger the counters above, see #2.

2.10.2 Problems with the SDCCH drop counters

Phantoms affect SDCCH_abis_fail_*

SDCCH drop ratio counts the ratio of all SDCCH failures to SDCCH seizures.Normally most of the seizures are caused because of phantoms which are countedas SDCCH_abis_fail_call and SDCCH_abis_fail_old. In practice, thelatter case does not practically occur because SDCCH handovers are usually notused and particularly because phantoms do not perform handover.

1079 SDCCH_A_IF_FAIL_OLD Same as above but when trying to return back to the oldchannel in HO.

1035 SDCCH_LAPD_FAIL Transactions have ended due to LAPD problems (a call is lostwhen LAPD goes down).

TRX/TSL is blocked with cause lapd_fail due to a signallinglink fault or a PCM fault.

Even if it occurs, the share is normally very low because thesituation is transient.

1036 SDCCH_BTS_FAIL Transactions have ended due to BTS problems. A call is lostwhen TRX/TSL is blocked with cause bts_fail due to FUor CU or BCF fault or BTS or BCF reset.


1038 SDCCH_BCSU_RESET Transactions have ended due to BSCU reset (calls are lostwhen BSCU is reset).


1037 SDCCH_USER_ACT Transactions have ended due to user actions. A timeslot orTRX is locked by the user via the Top-level User Interface orBSC MML.


1039 SDCCH_NETW_ACT Transactions have ended due to a change in the radio networkconfiguration (BCCH swap to another TRX) initiated by theBSC. The cause for the configuration change fails or locallyblocked BCCH TRX.


Table 4. SDCCH Drop Counters (Continued)

ID Name Description



The percentage of SDCCH_abis_fail_call used to be very high in a low trafficnetwork (even tens of per cent) whereas in a high traffic network the percentagesettled down to around 18-20 per cent. In BTS B9, BTS RACH detection wasimproved, and figures well under 10 per cent are now typical.

A interface blocking not shown

SDCCH failures do not include A interface blocking. In A interface blocking, anMSC clears the call without a request from a BSC. The failure is not in the BSCwhere the principle has been that MSC failures are not counted. Yet from an MSuser’s point of view, A interface blocking ends up in a failed call attempt. Youcan detect A interface blocking from the NSS statistics for circuit groups.

2.11 SDCCH drop ratio (sdr)

SDCCH drop %, S3 (sdr_1a)

Use: To follow up the performance of SDCCH from a technicalpoint of view.

Experiences on use: 1) High SDCCH drop rates usually result from ghostaccesses. A BTS decodes them from environmental orbackground noise and filters out most of them. However, allof them cannot be filtered out and the RACH request is passedon to the BSC for processing and for the allocation of aSDCCH channel.The counter ghost_ccch_res (3030) is updated each time achannel required is rejected because of an invalidestablishment cause. In GSM ph.1 there exist altogether eightestablishment causes, three of which are undefined as invalid,for example,resulting in that this counter shows only 3/8 of allthe ghost accesses the BTS has decoded. For the rest, aSDCCH is allocated and this will result insdcch_abis_fail_call failure. Because of ghost attemptsthe SDCCH drop ratio is high with low traffic. As the amountof call attempts increases, the influence of ghosts becomessmaller and the drop ratio approaches its real value.2) The rate of ghosts coming to SDCCH dropped when BTSB9 with improved ghost filtering was taken into use.

Known problems: In SDCCH failure counters it is not possible to separate LUand call seizures.

sum(sdcch_radio_fail+sdcch_rf_old_ho+sdcch_user_act+sdcch_bcsu_reset+sdcch_netw_act+sdcch_abis_fail_call+sdcch_abis_fail_old+sdcch_bts_fail+sdcch_lapd_fail+sdcch_a_if_fail_call+sdcch_a_if_fail_old)

100 * ------------------------------------------------------------------------ %sum(sdcch_assign+sdcch_ho_seiz)



Counters from table(s):p_nbsc_traffic

Figure 202. SDCCH drop %, S3 (sdr_1a)

SDCCH drop %, abis fail excluded, S3 (sdr_2)

Known problems: SDCCH_ABIS_CALL does not necessarily refer to ghosts butalso, for example, to failing location updates.

sum(sdcch_radio_fail+sdcch_rf_old_ho+sdcch_user_act+sdcch_bcsu_reset+sdcch_netw_act +sdcch_bts_fail+sdcch_lapd_fail+sdcch_a_if_fail_call+sdcch_a_if_fail_old)

100 * ------------------------------------------------------------------- %sum(sdcch_assign+sdcch_ho_seiz)

- sum(sdcch_abis_fail_call+sdcch_abis_fail_old)


Figure 203. SDCCH drop %, abis fail excluded, S3 (sdr_2)

Illegal establishment cause % (sdr_3b)

Use: This PI gives you the number of ghost accesses which try toseize SDCCH but are rejected before seizing SDCCH due toan illegal establishment cause.

sum(a.ghost_CCCH_res-a.rej_seiz_att_due_dist)100 * ------------------------------------------------- %

sum(b.sdcch_assign+b.sdcch_ho_seiz)%

Counters from table(s):a = p_nbsc_res_accessb = p_nbsc_traffic

Figure 204. Illegal establishment cause % (sdr_3b)

SDCCH drop ratio without timer T3101 expiry % (sdr_4)

Use: This PI shows the ratio of dropped SDCCH withoutconsidering the drops caused by timer T3101. See sdr_1a.

Known problems: See sdr_1a.

sum(a.sdcch_radio_fail+ a.sdcch_rf_old_ho+ a.sdcch_user_act+ a.sdcch_bcsu_reset++ a.sdcch_netw_act+ a.sdcch_abis_fail_call+ a.sdcch_abis_fail_old+ a.sdcch_bts_fail+ a.sdcch_lapd_fail+ a.sdcch_a_if_fail_call



+ a.sdcch_a_if_fail_old- b. T3101_EXPIRED)

100 * -------------------------------- %sum(sdcch_assign+sdcch_ho_seiz)

a = p_nbsc_trafficb = p_nbsc_service

Counters from table(s):p_nbsc_trafficp_nbsc_service

Figure 205. SDCCH drop ratio without timer T3101 expiry % (sdr_4)

2.12 Setup success ratio (cssr)

SDCCH, TCH setup success %, S4 (cssr_2)

Use: This PI shows the setup success ratio, including SDCCH andTCH. It works also in the case of DR.Possible fault cases:- faulty DSP in BTS TRX

Experiences on use: Fits for general quality monitoring. Values between 2.5 and4%, for example.

Known problems: ’B no answer’ is also counted as a successful call.Includes also SMSs and LUs which do not use TCH at all.This causes problems in special cases when there are manyLUs but few calls. The problems in calls are hidden by a greatnumber of LUs which receive SDCCH successfully.

Troubleshooting: You can use SDCCH and TCH observations to see which oneis failing. However, note that this is a time-consuming task.

sum(call_setup_failure)100* ( 1 - ----------------------------------------) %

sum(setup_succ+call_setup_failure)

Counters from table(s):p_nbsc_service

Figure 206. SDCCH, TCH setup success %, S4 (cssr_2)

2.13 TCH drop failures

2.13.1 TCH drop call counters

TCH drop calls are counted as the sum of the following counters:



Table 5. TCH drop call counters

ID Name Description

1011 TCH_RADIO_FAIL • Radio link timeout

• Release indication from MS

• MS moves out from timing advance

• TCH assignment failure where an Establish Indication hasbeen received but Assignment Complete has not beenreceived

This counter is typical in connection with coverage problems. Thisfailure type is usually the dominating one.

1014 TCH_RF_OLD_HO Same as above but when trying to return to the old channel in HO.

1084 TCH_ABIS_FAIL_CALL • missing ack of channel activation

• missing establishment indication

• reception of error indication

• corruption of messages

• measurement results no longer received from BTS

• excessive timing advance

• missing HO detection

• T3107 (assignment completely missing) expiry

• T3109 expiry. As in this case the drop happens in the releasephase, the MS user cannot see the situation as a drop call.

The BTS suffering from this failure can be faulty or their TCH TRXsuffers from bad interference (TCH assignment fails).

See #1 for all possible causes that trigger this counter.

If FACCH call setup is used, we may expect that we start to seeghost seizures incrementing this counter because the signallingtries to use SDCCH instead of TCH.

1085 TCH_ABIS_FAIL_OLD Same as above but when trying to return to the old channel in HO.

1087 TCH_A_IF_FAIL_CALL • A clear command from the MSC during the call setup phasebefore the assignment from MS is complete

• Abnormal clear received due to A-interface (reset circuit,SCCP clear). For example, a BSU reset in MSC makes MSCsend a "reset circuit" message.

There have been cases where the MSC of another vendor in inter-MSC handovers has caused high values even though thehandovers have been successful.

See #1 for all possible causes that trigger this counter.



1088 TCH_A_IF_FAIL_OLD Same as above but when trying to return to the old channel in HO.

Can be updated when GSM timer T8 expires in the source BSCduring an external handover.

1029 TCH_TR_FAIL • Transcoder failure during a call attempt

This counter is updated only when BTS sends a "connectionfailure" with cause "remote trascoder failure" and the call isreleased due to this.

If this failure is related to a transcoder, you can see its share to behigh for one BSC. Another possibility is that the problem lies in aBTS. Also interruptions of the transmission may cause this failure(alarms may be filtered out in a BSC or OMC to reduce thenumber of alarms due to disturbance).

In analysing the problem, you may find it helpful to check thepattern over a longer period of time.

In S6 the portion of this failure has decreased due toimprovements in transcoders.

1030 TCH_TR_FAIL_OLD Same as above but when trying to return to the old channel in HO.

1046 TCH_LAPD_FAIL TRX is blocked due to a LAPD failure (signalling link failure orPCM failure).

Even if it occurs, the share is very small because only ongoingcalls are dropped when the LAPD fails.

1047 TCH_BTS_FAIL TRX is blocked by a BTS failure.

(FU fault, CU fault, BTS reset, BCF reset, CU and FU fault, BCFfault).

Even if it occurs, the share is very small because only ongoingcalls are dropped when a BTS fails.

1049 TCH_BCSU_RESET TRX is blocked by BCSU reset.

Even if it occurs, the share is very small because only ongoingcalls are dropped when BCSU resets.

Table 5. TCH drop call counters (Continued)

ID Name Description



To see what DX causes can trigger the counters above, see #2.

The problem especially with failure classes Abis and Aif is that they are triggeredby many different causes. To analyse the case in question, TCH observations maybe used. As there are limitations on how to set the observations, the analysis ismore time-consuming.

If the problem is not cell specific but related to the entire network or BSS areas,you can also use the Clear Code measurement.

*_OLD counters are related to the handover situation when returning to the oldchannel fails causing a call to drop. Thus, these counters reflect the amount of calldrops in handovers.

2.13.2 Drop call ratio

Drop call ratio is counted as the ratio of the sum of the above named counters toall TCH seizures for a new call. This ratio is used in reports for network ormaintenance region level. See dcr_3*.

2.13.3 Drop-out ratio

Drop-out ratio is counted as the ratio of the sum of the above named counters toall TCH seizures. This ratio is used on cell level reports where the concept of callis not applicable.

1048 TCH_USER_ACT Busy TSL or TRX blocked by MML command (blocked by user).

Even if it occurs, the share is very small because only ongoingcalls are dropped when the blocking command is given.

1050 TCH_NETW_ACT TRX is blocked by a fault leading to reconfiguration (blocked by thesystem).

Even if occurs, the share is very small because only ongoing callsare dropped when reconfiguration is executed.

1081 TCH_ACT_FAIL_CALL Channel activation nack received.

Table 5. TCH drop call counters (Continued)

ID Name Description



2.13.4 Problems with the drop call counters

TCH Tr, Abis failures

These failures can contain also situations when timer T3109 (8 to 15 s, default 12s) expires in a BSC in the call release phase while waiting for the Releaseindication. With BTS software 6.0 these were seen as TC failures, whereas sinceBTS software 6.1 they have been Abis failures. The MS user does not see thesefailures as real drop calls.

If you detect a high ratio of TC or Abis failures, check the BTS release and thetimer.

TCH_A_IF_OLD high

There have been cases when this counter has been showing high values whileanother vendor’s MSC has cleared the call with the cause CLR_CMD in the case ofa successful inter-MSC HO.

2.14 Drop call failures (dcf)

TCH drop calls in HO, S2 (dcf_2)

Open questions: Claims of cases when the TCH_A_IF_OLD has not been a dropcall have been made.

sum(tch_rf_old_ho+ tch_abis_fail_old+tch_a_if_fail_old+tch_tr_fail_old)


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

TCH drop calls in BSC outgoing HO, S3 (dcf_3)

Known problems: Accuracy is not good.

sum(bsc_o_drop_calls)

Counters from table(s):p_nbsc_ho

Figure 208. TCH drop calls in BSC outgoing HO, S3 (dcf_3)

TCH drop calls in intra-cell HO, S3 (dcf_4)


sum(cell_drop_calls)




Figure 209. TCH drop calls in intra-cell HO, S3 (dcf_4)

TCH drop calls in intra-BSC HO, S3 (dcf_6)

Known problems: Use on the BTS level. On the area level causes doublecounting. Accuracy is not good.

sum(bsc_i_drop_calls+bsc_o_drop_calls+cell_drop_calls)


Figure 210. TCH drop calls in intra BSC HO, S3 (dcf_6)

Drop calls in BSC incoming HO, S3 (dcf_7)


sum(bsc_i_drop_calls)


Figure 211. Drop calls in BSC incoming HO, S3 (dcf_7)

TCH drop calls in HO, S7 (dcf_11)

Known problems: On the area level causes double counting. Accuracy is notgood.

sum(msc_o_call_drop_ho+bsc_i_drop_calls+bsc_o_drop_calls+cell_drop_calls)


Figure 212. TCH drop calls in HO, S7 (dcf_11)

2.15 TCH drop call % (dcr)

TCH drop call %, area, S3 (dcr_3c)

Use: Used on the area level.Experiences on use: See dcr_3. The best value reported for area: 2.3



Known problems: 1) Some failures in release phase are included in this formula(tch_abis_fail_call) but are, in fact, not perceived as drop callsby the MS user.2) tch_norm_seiz does not mean that the MS is on TCH. Itmeans that TCH has been successfully seized. Some mobilesnever appear to the TCH because2a) the call is cleared by user (probability is higher if callsetup takes a long time, and thus DR and queuing canincrease this share) or2b) the mobile fails or2c) something else goes wrong.3) TCH failure counters are not triggered if call is cleared bypre-emption (1st priority call requested to be established, allTCH seized, lower priority calls on) whereas p_nbsc-service.dropped_call is triggered.

sum(tch_radio_fail+ tch_rf_old_ho+ tch_abis_fail_call+ tch_abis_fail_old+ tch_a_if_fail_call+ tch_a_if_fail_old+ tch_tr_fail+ tch_tr_fail_old+ tch_lapd_fail+ tch_bts_fail+ tch_user_act+ tch_bcsu_reset+ tch_netw_act+ tch_act_fail_call)

100 * ------------------------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)

+ sum(c.msc_i_sdcch_tch + c.bsc_i_sdcch_tch) ;(calls started via DR)+ sum(a.tch_seiz_due_sdcch_con) ;calls started as FACCH call setup

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_res_accessc = p_nbsc_ho

Figure 213. TCH drop call %, area, S3 (dcr_3c)

TCH drop call %, area, real, after re-establishment, S3 (dcr_3f)

Use: Used on the area level.



Experiences on use: See dcr_3g. Call re-establishments can markedly improvethe drop call ratio (for example, from 2.5 to 2.0%). Since thisis an improvement from the MS user’s point of view, thisfigure suits better to management reports.In good networks where optimisation has been done alreadyfor two to three years, values have been around 2 to 3 per cent(and in networks in which no optimisation has been done yetthe values remain even above 10 per cent. A value of 5 percent is achievable in many networks despite their bad initialcoverage planning. Interference also raises the figure. Becareful when setting the target values since the factors(whether caused by the customer or Nokia) can be time-consuming and expensive to prove.If used on the cell level, the values can be even over 100 percent if a cell takes handovers in but then drops them.

Known problems: 1) See dcr_3g.2) It is assumed that call re-establishments happen on TCH. Infact they may happen also on SDCCH.3) The counters used to compensate re-establishments are theones that indicate re-establishment attempts, not thesuccessful re-establishments. In S7/T11 re-establishments canbe considered accurately (see dcr_3j).4) On cell level it can happen that the call is re-established ina different cell than where it was dropped, resulting ininaccuracy.

100 - csf_4p =

sum(a.tch_radio_fail+ a.tch_rf_old_ho+ a.tch_abis_fail_call+ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)

- sum(b.sdcch_call_re_est + b.tch_call_re_est) ;call re-establ.100 * ------------------------------------------------------------------- %

sum(a.tch_norm_seiz) ;calls started directly in the cell+ sum(c.msc_i_sdcch_tch

+ c.bsc_i_sdcch_tch+ c.cell_sdcch_tch) ;DR calls

+ sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls- sum(b.sdcch_call_re_est+b.tch_call_re_est) ;call re-establ.

Counters from table(s):a = p_nbsc_traffic



b = p_nbsc_res_accessc = p_nbsc_ho

Figure 214. TCH drop call %, area, real, after re-establishment S3 (dcr_3f)

TCH drop call %, area, real, before re-establishment, S3 (dcr_3g)

Use: Used on the area level.Experiences on use: In good networks where optimisation has been done already

for two to three years, values have been around 2 to 3 per cent(and in networks in which no optimisation has been done yet,the values remain even above 10 per cent). A value of 5 percent is achievable in many networks despite their bad initialcoverage planning.Interference also raises the figure.Be careful when setting the target values since the factors(whether caused by the customer or Nokia) can be time-consuming and expensive to prove.If used on cell level, the values can be even over 100 per centif a cell takes HOs in but then drops them.

Known problems: Some failures in the release phase are included in this formula(tch_abis_fail_call) but are, in fact, not perceived asdrop calls by the MS user.tch_norm_seiz does not mean that the MS is on TCH. Itmeans that TCH has been successfully seized. Some mobilesnever appear to the TCH because:• the call is cleared by the user (probability is higher if

call setup takes a long time, and thus DR and queuingcan increase this share) or

• the mobile fails or• something else goes wrong.TCH failure counters are not triggered if a call is cleared bypre-emption (1st priority call requested to be established, allTCH seized, lower priority calls on) whereas p_nbsc-service_dropped_call is triggered.

sum(tch_radio_fail+ tch_rf_old_ho+ tch_abis_fail_call+ tch_abis_fail_old+ tch_a_if_fail_call+ tch_a_if_fail_old+ tch_tr_fail+ tch_tr_fail_old+ tch_lapd_fail+ tch_bts_fail+ tch_user_act+ tch_bcsu_reset+ tch_netw_act+ tch_act_fail_call)

100 * ------------------------------------------------------------------ %sum(a.tch_norm_seiz) ;(normal calls)

+ sum(c.msc_i_sdcch_tch



+ c.bsc_i_sdcch_tch+ c.cell_sdcch_tch) ;(DR calls)

+ sum(a.tch_seiz_due_sdcch_con) ;calls started as FACCH call setup

Counters from table(s):a = p_nbsc_trafficc = p_nbsc_ho

Figure 215. TCH drop call %, area, real, before re-establishment, S3 (dcr_3g)

TCH drop call %, area, real, after re-establishment, S7 (dcr_3h)

Use: Used on the area level.Experiences on use: See dcr_3. Call re-establishments can markedly improve

the drop call ratio (for example, from 2.5 to 2.0%). Since thisis an improvement from the MS user’s point of view, thisfigure suits better to management reports.

Known problems: See dcr_3g. It is assumed that call re-establishments occuron TCH. In fact they may occur also on SDCCH.

sum(tch_radio_fail+ tch_rf_old_ho+ tch_abis_fail_call+ tch_abis_fail_old+ tch_a_if_fail_call+ tch_a_if_fail_old+ tch_tr_fail+ tch_tr_fail_old+ tch_lapd_fail+ tch_bts_fail+ tch_user_act+ tch_bcsu_reset+ tch_netw_act+ tch_act_fail_call

- sum(b.tch_re_est_assign) ;(call re-establishments)100 * ------------------------------------------------------------------- %

sum(a.tch_norm_seiz) ;(normal calls)+ sum(c.msc_i_sdcch_tch


+ sum(a.tch_seiz_due_sdcch_con) ;calls started as FACCH call setup- sum(b.tch_re_est_assign) ;(call re-establishments)

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_servicec = p_nbsc_ho

Figure 216. TCH drop call %, area, real, after re-establishment, S7 (dcr_3h)

TCH drop call %, area, real, before re-establishment S3 (dcr_3i)

Use: Used on the area level.This KPI indicates how many calls are dropped after TCHseizure.



Experiences on use: In good networks where optimisation has been done alreadyfor two to three years, values have been around 2 to 3 per cent(and in networks in which no optimisation has been done yetthe values remain even above 10 per cent. A value of 5 percent is achievable in many networks despite their bad initialcoverage planning. Interference also raises the figure. Becareful when setting the target values since the factors(whether caused by the customer or Nokia) can be time-consuming and expensive to prove.If used on cell level, the values can be even over 100 per centif a cell takes HOs in but then drops them.

Known problems: 1) Some failures in release phase are included in this formula(tch_abis_fail_call) but are, in fact, not perceived asdrop calls by the MS user.2) tch_norm_seiz does not mean that the MS is on TCH. Itmeans that TCH has been successfully seized. Some mobilesnever appear to the TCH because2a) the call is cleared by the user (probability is higher if callsetup takes a long time, and thus DR and queuing canincrease this share) or2b) the mobile fails or2c) something else goes wrong.3) TCH failure counters are not triggered if a call is cleared bypre-emption (1st priority call requested to be established, allTCH seized, lower priority calls on), whereas p_nbsc-service.dropped_call is triggered.

100-csf_4u =

sum(a.tch_radio_fail+ a.tch_rf_old_ho+ a.tch_abis_fail_call++ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)

100 * ----------------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)

+ sum(c.msc_i_sdcch_tch+ c.bsc_i_sdcch_tch+ c.cell_sdcch_tch) ;(DR calls)

- sum(a.tch_succ_seiz_for_dir_acc ) ;ref.2+ sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls


Figure 217. TCH drop call %, area, real, before re-establishment, S3 (dcr_3i)



Ref.2. Compensation is needed, since in case of Direct Access to super reuse TRXthe tch_norm_seiz is triggered in parallel with cell_sdcch_tch.

TCH drop call %, area, real, after re-establishment, S7 (dcr_3j)

Use: On the area level.Experiences on use: In good networks where optimisation has been done already

for two to three years, values are around 2 to 3 per cent. Innetworks in which no optimisation has been done yet thevalues are even as high as 10 per cent. A value of 5 per cent isachievable in many networks despite their bad initialcoverage planning.The values in the best networks are below 1.5%.Interference also raises the figure.Be careful when you give promises concerning quality sincethe factors (whether caused by the customer or Nokia) can betime-consuming and expensive to prove.If used on cell level, the values can be even over 100 per centif a cell takes handovers in but then drops them.Call re-establishments can markedly improve the drop callratio (for example, from 2.3 to 2.0 %). Since this is animprovement from the MS user's point of view, this figuresuits better to management reports.The biggest reason for having low figures usually is in basicnetwork planning. If coverage is not adequate, this KPI cannotshow good values.

Known problems: 1) Some failures in the release phase are included in thisformula (tch_abis_fail_call) but are, in fact, notperceived as drop calls by the MS user.2) tch_norm_seiz does not mean that the MS is on TCH.It means that TCH has been successfully seized. Somemobiles never appear to the TCH because2a) the call is cleared by user (probability is higher if callsetup takes a long time, and thus DR and queuing canincrease this share) or2b) the mobile fails or2c) something else goes wrong3) TCH failure counters are not triggered if call is cleared bypre-emption (first priority call requested to be established, allTCH seized, lower priority calls on) whereas p_nbsc-service.dropped_call is triggered.4) It is assumed that call re-establishments happen on TCH. Infact they may happen also on SDCCH.5) On the cell level it can happen that the call is re-establishedin a different cell than it was dropped resulting in inaccuracy.

100-csf_4v =

sum(a.tch_radio_fail+ a.tch_rf_old_ho+ a.tch_abis_fail_call



+ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)

- sum(b.tch_re_est_assign) ;call re-establishments100 * ----------------------------------------------------------- %



- sum(a.tch_succ_seiz_for_dir_acc) ;ref.1+ sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls- sum(b.tch_re_est_assign) ;call re-establishments


Figure 218. TCH drop call %, area, real, after re-establishment, S7 (dcr_3j)


TCH drop-out %, BTS level, before call re-establishment, S3 (dcr_4c)

Use: Used on the BTS level. To rank cells by the share of TCH dropcall failures per TCH seizure (normal or HO). Intra-cell HOexcluded which is meaningful in the case of IUO, forexample.

Known problems: See dcr_3g.


100 * ----------------------------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)


+ sum(a.tch_seiz_due_sdcch_con) ;(FACCH call setup calls)+ sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) ;(TCH-TCH HO from other cells)




a = p_nbsc_trafficc = p_nbsc_ho

Figure 219. TCH drop-out %, BTS level, before call re-establishment, S3(dcr_4c)

TCH drop-out %, BTS level, before call re-establishment, S3 (dcr_4d)

Use: Used on the BTS level. To rank cells by the share of TCH dropcall failures per TCH seizure (normal or HO). Intra-cell HO isexcluded, which is meaningful in the case of IUO. Inter-cellHOs are counted only as a net value.



100 * ------------------------------------------------------------ %sum(a.tch_norm_seiz) ;(normal calls)


+ sum(a.tch_seiz_due_sdcch_con) ;(FACCH call setup calls)+ sum(c.msc_i_tch_tch + c.bsc_i_tch_tch)- sum(c.msc_o_tch_tch

+ c.bsc_o_tch_tch) ;(TCH-TCH HO net in from other cells)


Figure 220. TCH drop-out %, BTS level, before call re-establishment, S3(dcr_4d)

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

Use: Used on the BTS level. To rank cells by the share of TCH dropcall failures per TCH seizure (normal or HO). Intra-cell HO isexcluded, which is meaningful in the case of IUO, forexample.


100 - csf_4y =

sum(a.tch_radio_fail+ a.tch_rf_old_ho



+ a.tch_abis_fail_call+ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)

100 * ------------------------------------------------------ %sum(a.tch_norm_seiz) ;(normal calls)

+ sum(c.msc_i_sdcch_tch+ c.bsc_i_sdcch_tch+ c.cell sdcch_tch) ;(DR calls)

- sum(a.tch_succ_seiz_for_dir_acc ) ;ref.2+ sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls+ sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) ;(TCH-TCH HO from other cells)


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


TCH drop-out %, BTS level, before call re-establishment, S7 (dcr_4f)

Use: Used on the BTS level. To rank cells by the share of TCH dropcall failures per TCH seizure (normal or HO). Intra-cell HO isexcluded, which is meaningful in the case of IUO. Inter-cellHOs are counted only as a net value.



100 * ------------------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)


- sum(a.tch_succ_seiz_for_dir_acc) ;ref.2+ sum(a.tch_seiz_due_sdcch_con) ;(FACCH call setup calls)+ sum(c.msc_i_tch_tch + c.bsc_i_tch_tch)- sum(c.msc_o_tch_tch





Ref.2. Compensation is needed, since in case of Direct Access to super reuseTRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch.

Figure 222. TCH drop-out %, BTS level, before call re-establishment, S7 (dcr_4f)

TCH drop-out ratio, before call re-establishment (dcr_4g)

Use: Used on the BTS level to rank cells by the share of TCH dropcall failures per TCH seizure (normal or HO). Intra-cell HO isexcluded, which is meaningful in the case of IUO. Inter-cellHOs are counted only as a net value.

sum(a.tch_radio_fail+ a.tch_rf_old_ho+(a.tch_abis_fail_call - b.spare002072) ;Ref 1+ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)

100 * ------------------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)


- sum(a.tch_succ_seiz_for_dir_acc) ;ref.2+ sum(a.tch_seiz_due_sdcch_con) ;(FACCH call setup calls)+ sum(c.msc_i_tch_tch + c.bsc_i_tch_tch)- sum(c.msc_o_tch_tch


Counters from table(s):a = p_nbsc_trafficb = p_nbsc_res_availc = p_nbsc_ho

Ref 1; The spare counter (2072) used to compensate the counter001084TCH_ABIS_FAIL_CALLthat is updated faultily after activation of FACCHRef.2. Compensation needed since in case of Direct Access to super reuse TRXthetch_norm_seiz is triggered in parallel with cell_sdcch_tch.

Figure 223. TCH drop-out ratio, before call re-establishment (dcr_4g)



TCH drop call (dropped conversation) %, BSC level, S4 (dcr_5)

Use: Used on the area level. Tells the ratio of calls dropped whileA and B are talking, that is after conn_ack.Theoretically should always be less than dcr_3f or dcr_3g.Results from networks 2 to 6 %.

Known problems: 1) Does not work on the BTS level (handovers). Accurate onthe BSC and PLMN levels after a bug was corrected.2) If call re-establishment is active and occurs, theconver_started is triggered once and dropped_callsonly once. After the first call re-establishment thedropped_calls counter is no longer incremented in this callno matter if the call stays or drops. This means that in this caseseen from counters, the call looks like a dropped call. In fact,from the MS user’s point of view it is impossible to knowwhether it was dropped or not (does callre_establishment save the call or not).3) Subscriber clear during HO is counted as a dropped call.4) Due to an error in the mapping table also blocking in thecase of an external HO has been counted as a dropped call.5) External HOs (inter BSC handovers) trigger theconver_started counter in a target cell. Therefore onnetwork level the ratio does not correctly illustrate thedropped conversation ratio from the MS’s point of view.

sum(dropped_calls)100 * -------------------- %

sum(conver_started)


Figure 224. TCH drop call (dropped conversation) %, BSC level, S4 (dcr_5)

TCH dropped conversation %, area, re-establishment considered, S7(dcr_5b)

Use: Used on the area level. Tells the ratio of calls dropped whileA and B are talking, that is after conn_ack. Inter BSChandovers are subtracted in the denominator because theytrigger conver_started. Compensation is 100% true onlyif the area has no inter-BSC handovers from outside the area.Theoretically should always be less than dcr_3f or dcr_3g.

Known problems: See dcr_5.1) conver_started is not triggered for call re-establishments.dropped_calls is triggered once for the first re-establishment. After that setup_failure is triggered if thecall is a dropped call.



If the call is ’saved’ by re-establishment multiple times,setup_failure will be triggered several times accordingly.2) Drop call by pre-emption (1st priority call request to beestablished, all TCHs seized, lower priority calls on) triggersdropped_calls. Therefore this counter does not indicateonly technical drops.

sum(b.dropped_calls) - sum(tch_re_est_release)100 * -------------------------------------------------- %

sum(b.conver_started) - sum(a.msc_i_tch_tch)

Counters from table(s):a = p_nbsc_hob = p_nbsc_service

Figure 225. TCH dropped conversation %, area, re-establishment considered,S7 (dcr_5b)

TCH drop call %, after TCH assignment, without RE, area level, S10.5(dcr_8c)

Use: This formula is developed to better match with the formulasof other vendors. It does not consider the impact of the call re-establishment.

Known problems: 1) The formula is not reliable on hourly level because assignsand releases can happen in different measurement periods. Inthe worst case this can cause a negative value.2) Not good for BTS level because the denominator countsonly started new calls (there can be a lot of handovers in, too).3) The following bugs that affect the formula have beencorrected in S9:3a) Counter TCH_NORM_RELEASE (c57035) is notupdated if during the call there has been a MSC controlled HOwith cause 'pre-emption' or 'traffic'.3b) TCH_NEW_CALL_ASSIGN (c57033) is not updated inthe case of MSC controlled SDCCH-TCH HO with cause'pre-emption' or 'traffic'.

Drops after TCH assignment100 * ------------------------------ % =

TCH assignments for new calls

sum(spare057044)100 * ------------------------ %

sum(tch_new_call_assign)


Figure 226. TCH drop call %, after TCH assignment, without RE, area level, S10.5 (dcr_8c)



TCH drop call %, after TCH assignment, with RE, area level, S10.5 (dcr_8e)

Description: TCH drop call%, after TCH assignment, considering re-establishments.

Use: This formula is developed to better match with the formulasof other vendors.

Known problems: See dcr_8c.

Drops after TCH assignment considering re-establishments100 * -------------------------------------------------------- % =


sum(spare057044 - tch_re_est_release)100 * ------------------------------------- %



Figure 227. TCH drop call %, after TCH assignment, with RE, area level, S10.5(dcr_8e)

TCH drop call %, S11 (dcr_8h)

Description: TCH drop call %, after TCH assignment, without consideringre-establishments.

Use: This formula is developed to better match with the formulasof other vendors (Ericsson and Motorola). It considers theimpact of the call re-establishment.

Known problems: See dcr_8c.

Drops after TCH assignment considering re-establishments100 * -------------------------------------------------------- % =


sum(drop_after_tch_assign - TCH_RE_EST_ASSIGN)100 * ----------------------------------------------- %



Unit:%

Figure 228. TCH drop call %, S11 (dcr_8h)

Drops per erlang, before re-establishment, S4 (dcr_10)

Use: Used on the area and BTS level.Known problems: Works for the 60 min period.

Drops-------------------------- =Traffic (Erlang hours sum)




---------------------------------------------------------------sum(b.ave_busy_tch/b.res_av_denom14) / (60/avg(period_duration))

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_res_avail

Figure 229. Drops per erlang, before re-establishment, S4 (dcr_10)

Drops per erlang, after re-establishment, S4 (dcr_10a)


The counters used to compensate re-establishments are theones that indicate re-establishment attempts, not thesuccessful re-establishments.

Drops- re-establishments-------------------------- =Traffic (Erlang hours sum)


- sum(c.sdcch_call_re_est + c.tch_call_re_est) ;call re-establishments-------------------------------------------------------------------------

sum(b.ave_busy_tch/b.res_av_denom14) / (60/avg(period_duration))

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_res_availc = p_nbsc_res_access

Figure 230. Drops per erlang, after re-establishment, S4 (dcr_10a)



Drops per erlang, after re-establishment, S7 (dcr_10b)


Drops - re-establishments-------------------------- =Traffic (Erlang hours sum)


- sum(c.tch_re_est_assign) ;call re-establishments--------------------------------------------------------------------

sum(b.ave_busy_tch/b.res_av_denom14) / (60/avg(b.period_duration))

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_res_availc = p_nbsc_service

Figure 231. Drops per erlang, after re-establishment, S7 (dcr_10b)

Drops per erlang, before re-establishment (dcr_10c)

Use: Used on the area and BTS level.

Drops-------------------------- =Traffic (Erlang hours sum)

sum(a.tch_radio_fail+ a.tch_rf_old_ho+(a.tch_abis_fail_call - b.spare002072); Ref 1+ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)

---------------------------------------------------------------sum(b.ave_busy_tch/b.res_av_denom14) / (60/avg(period_duration))

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_res_avail



Ref 1; The spare counter (2072) used to compensate the counter001084 TCH_ABIS_FAIL_CALLthat is updated faultily after activation of FACCH

Figure 232. Drops per erlang, before re-establishment (dcr_10c)

Drops per erlang, after re-establishment (dcr_10d)

Use: Used on the area and BTS level.

Drops - re-establishments-------------------------- =Traffic (Erlang hours sum)

sum(a.tch_radio_fail+ a.tch_rf_old_ho+(a.tch_abis_fail_call - b.spare002072); Ref 1+ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)- sum(c.tch_re_est_assign) ;call re-establishments

--------------------------------------------------------------------sum(b.ave_busy_tch/b.res_av_denom14) / (60/avg(b.period_duration))

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_res_availc = p_nbsc_service

Ref 1; The spare counter (2072) used to compensate the counter001084 TCH_ABIS_FAIL_CALL that is updated faultily after activation of FACCH

Figure 233. Drops per erlang, after re-establishment (dcr_10d)

TCH Rf loss in HO - ratio, IUO (dcr_14)

sum(TCH_FAIL_CALL_HO)100 * ---------------------- %

sum(tch_succ_seiz)

Counters from table(s):p_nbsc_underlay

Figure 234. TCH Rf loss in HO - ratio, IUO (dcr_14)



Transcoder failure ratio, FR (dcr_16)

sum(TCH_ENDED_DUE_TRANSC_FR_RATE1)100 * ---------------------------------- %

sum(TCH_FULL_SEIZ_SPEECH_VER1)


Figure 235. Transcoder failure ratio, FR (dcr_16)

Transcoder failure ratio, EFR (dcr_17)




Figure 236. Transcoder failure ratio, EFR (dcr_17)

Transcoder failure ratio, HR (dcr_18)

sum(TCH_ENDED_DUE_TRANSC_HR_RATE1)100 * ---------------------------------- %

sum(TCH_HALF_SEIZ_SPEECH_VER1)


Figure 237. Transcoder failure ratio, HR (dcr_18)

Transcoder failure ratio, AMR FR (dcr_19)




Figure 238. Transcoder failure ratio, AMR FR (dcr_19)

Transcoder failure ratio, AMR HR (dcr_20)

sum(TCH_ENDED_DUE_TRANSC_HR_RATE3)100 * ---------------------------------- %

sum(TCH_HALF_SEIZ_SPEECH_VER3)




Figure 239. Transcoder failure ratio, AMR HR (dcr_20)

Transcoder failure ratio (dcr_21)

sum(TCH_ENDED_DUE_TRANSC_FR_RATE1+TCH_ENDED_DUE_TRANSC_HR_RATE1+TCH_ENDED_DUE_TRANSC_FR_RATE2+TCH_ENDED_DUE_TRANSC_FR_RATE3+TCH_ENDED_DUE_TRANSC_HR_RATE3")

100 * ----------------------------------------------------------------- %sum(TCH_FULL_SEIZ_SPEECH_VER1+TCH_HALF_SEIZ_SPEECH_VER1

+TCH_FULL_SEIZ_SPEECH_VER2+TCH_FULL_SEIZ_SPEECH_VER3+TCH_HALF_SEIZ_SPEECH_VER3)


Figure 240. Transcoder failure ratio (dcr_21)

Call failures share of transcoder failures (dcr_22)

Use: Indicates the percentage of transcoding failures during TCHseizure for a call. These are call drops.

Sum(TCH_TR_FAIL)100 * ------------------------------------------------ %

sum(TCH_TR_FAIL+TCH_TR_FAIL_OLD+TCH_TR_FAIL_NEW)


Figure 241. Call failures share of transcoder failures (dcr_22)

HO target share of transcoder failures (dcr_23)

Use: Indicates the percentage of transcoding failures in the targetcell during TCH seizure for HO. These are not call drops.

Sum(TCH_TR_FAIL_NEW)100 * ------------------------------------------------ %



Figure 242. HO target share of transcoder failures (dcr_23)



HO source share of transcoder failures (dcr_24)

Use: Indicates as a percentage the transcoding failures that happenin the source cell in HO when MS fails to return to the old celland a call drops.

Sum(TCH_TR_FAIL_OLD)100 * ------------------------------------------------ %



Figure 243. HO source share of transcoder failures (dcr_24)

Transcoder failures (dcr_25)



Figure 244. Transcoder failures (dcr_25)

TCH drop call %, before re-establishment (dcr_31)

Use: Used on the area level. This KPI indicates how much calls aredropped after a TCH seizure.

Experiences on use: In good networks where optimisation has been done alreadyfor two to three years, values have been around 2 to 3 per cent.In networks in which no optimisation has been done yet thevalues remain even above 10%. A value of 5% is achievablein many networks despite of their bad initial coverageplanning. Interference also raises the figure. Be careful when setting the target values since the factors(whether caused by the customer or Nokia) can be time-consuming and expensive to prove. If used on cell level, thevalues can be even over 100 per cent if a cell takes HOs in butthen drops them.

100-csf_41 =

sum(a.tch_radio_fail+ a.tch_rf_old_ho+(a.tch_abis_fail_call - b.spare002072); Ref 1+ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act+ a.tch_bcsu_reset



+ a.tch_netw_act+ a.tch_act_fail_call)

100 * ----------------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)




Ref 1; The spare counter (2072) used to compensate the counter001084 TCH_ABIS_FAIL_CALL that is updated faultily after activation of FACCHRef.2. Compensation needed since in case of Direct Access to super reuseTRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch.

Figure 245. TCH drop call %, before re-establishment (dcr_31)

TCH drop call %, after re-establishment (dcr_32)

Use: Used on the area level.Experiences on use: In good networks where optimisation has been done

already for two to three years, values are around 2 to 3 percent. In networks in which no optimisation has been done yetthe values are even as high as 10 per cent. A value of 5% isachievable in many networks despite their bad initialcoverage planning. The values in the best networks are below1.5%. Interference also raises the figure.If used on the cell level, the values can be even over 100% ifa cell takes handovers in but then drops them. Call re-establishments can markedly improve the drop call ratio (forexample, from 2.3 to 2.0%). Since this is an improvementfrom the MS users point of view, this figure suits better tomanagement reports. The biggest reason for having lowfigures usually is in basic network planning. If coverage is notadequate this KPI cannot show good values.

Known problems: There might be some problems with tch_norm_size if used onBTS level and the BTS is part of the multisegment.

100-csf_42 =

sum(a.tch_radio_fail+ a.tch_rf_old_ho+(a.tch_abis_fail_call - d.spare002072) ;Ref 1+ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act



+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)

- sum(b.tch_re_est_assign) ;call re-establishments100 * ----------------------------------------------------------- %




Counters from table(s):a = p_nbsc_trafficb = p_nbsc_servicec = p_nbsc_hod = p_nbsc_res_avail

Ref 1; The spare counter (2072) used to compensate the counter 001084TCH_ABIS_FAIL_CALL that is updated faultily after activation of FACCHRef.2; Compensation needed since in case of Direct Access to super reuseTRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch.

Figure 246. TCH drop call %, after re-establishment (dcr_32)

2.16 Adaptive Multirate (amr)

Codec set upgrade attempts, S10 (amr_1)

Sum(SUCC_AMR_CODEC_SET_UPGR+UNSUCC_AMR_CODEC_SET_UPGR)


Figure 247. Codec set upgrade attempts, S10 (amr_1)

Codec set downgrade attempts, S10 (amr_2)

Sum(SUCC_AMR_CODEC_SET_DOWNGR+UNSUCC_AMR_CODEC_SET_DOWNGR)


Figure 248. Codec set downgrade attempts, S10 (amr_2)

Codec set upgrade failure ratio, S10 (amr_3)

Sum(UNSUCC_AMR_CODEC_SET_UPGR)100 * ------------------------------------------------------ %

Sum(SUCC_AMR_CODEC_SET_UPGR+UNSUCC_AMR_CODEC_SET_UPGR)




Figure 249. Codec set upgrade failure ratio, S10 (amr_3)

Codec set downgrade failure ratio, S10 (amr_4)

Sum(UNSUCC_AMR_CODEC_SET_DOWNGR)100 * ---------------------------------------------------------- %

Sum(SUCC_AMR_CODEC_SET_DOWNGR+UNSUCC_AMR_CODEC_SET_DOWNGR)


Figure 250. Codec set downgrade failure ratio, S10 (amr_4)

2.17 Position based services (pbs)

Failure ratio of location calculations for external LCS clients, S10 (pbs_1a)

Sum(SUCC_LOC_CALC_BY_LCS_REQ)100 - 100*--------------------------------- %

Sum(NBR_OF_LOC_REQ_FROM_LCS)

Counters from table(s):p_nbsc_pbs

Figure 251. Failure ratio of location calculations for external LCS clients, S10(pbs_1a)

Failure ratio of location calculations for emergency calls, S10 (pbs_2a)

Sum(SUCC_LOC_CALC_EMERGENCY)100 - 100*------------------------------- %

Sum(NBR_OF_LOC_REQ_EMERGENCY)


Figure 252. Failure ratio of location calculations for emergency calls, S10(pbs_2a)

Failure ratio of E-OTD location calculations, S10 (pbs_3)

Sum(SUCC_LOC_CALC_E_OTD)100 - 100 * --------------------------------------------------- %



Sum(NBR_OF_E_OTD_CALCULATIONS + SUCC_LOC_CALC_E_OTD)


Figure 253. Failure ratio of E-OTD location calculations, S10 (pbs_3)

Failure ratio of E-OTD location calculations, S10 (pbs_3a)

Sum(SUCC_LOC_CALC_E_OTD)100 - 100*------------------------------- %

Sum(NBR_OF_E_OTD_CALCULATIONS)


Figure 254. Failure ratio of E-OTD location calculations, S10 (pbs_3a)

Failure ratio of location calculations for MS, S10 (pbs_4a)

Sum(SUCC_LOC_CALC_BY_MS_REQ)100 - 100*------------------------------- %

Sum(NBR_OF_LOC_REQ_FROM_MS)


Figure 255. Failure ratio of location calculations for MS, S10 (pbs_4a)

Failure ratio of location calculations for operator, S10 (pbs_5a)

Sum(SUCC_LOC_CALC_BY_OPER_REQ)100 - 100*-------------------------------- %

Sum(NBR_OF_LOC_REQ_FROM_OPER)


Figure 256. Failure ratio of location calculations for operator, S10 (pbs_5a)

Failure ratio of location calculations using stand-alone GPS, S10 (pbs_6)

Sum(SUCC_LOC_CALC_STAND_ALONE_GPS)100 - 100 * ----------------------------------------------------------------- %

Sum(NBR_LOC_CALC_STAND_ALONE_GPS + SUCC_LOC_CALC_STAND_ALONE_GPS)




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

Failure ratio of location calculations using stand-alone GPS, S10 (pbs_6a)

Sum(SUCC_LOC_CALC_STAND_ALONE_GPS)100 - 100*-------------------------------------%

Sum(NBR_LOC_CALC_STAND_ALONE_GPS)


Figure 258. Failure ratio of location calculations using stand-alone GPS, S10(pbs_6a)

Unspecified LCS requests, S10 (pbs_8)

Use: Indicates the requests for which the client type is unspecified.

Sum(NBR_OF_LOC_REQ_FROM_LCS-NBR_OF_LOC_REQ_EMERGENCY-NBR_OF_LOC_REQ_FROM_MS-NBR_OF_LOC_REQ_FROM_OPER)


Figure 259. Unspecified LCS requests, S10 (pbs_8)

2.18 Handover (ho)

Return from super TRXs to regular TRX, S4 (ho_1)

sum(ho_succ_to_reg_freq)100 * -------------------------- %

sum(ho_succ_from_reg_freq)


Figure 260. Return from super TRXs to regular TRX, S4 (ho_1)



HO attempts from regular TRXs to super, S4 (ho_2)

sum(ho_att_from_reg_freq)


Figure 261. HO attempts from regular TRXs to super, S4 (ho_2)

HO attempts from super to regular, S4 (ho_3)

sum(ho_att_to_reg_freq)


Figure 262. HO attempts from super to regular, S4 (ho_3)

Share of HO attempts from super to regular due to DL quality, S4 (ho_4)

sum(att_from_super_dl_qual)100 * -------------------------------------------------- %

sum(att_from_super_dl_qual + att_from_super_dl_if+att_from_super_ul_if + att_from_super_bad_ci)


Figure 263. Share of HO attempts from super to regular due to DL quality, S4(ho_4)

Share of HO attempts from super to regular due to DL interference, S4(ho_5)

sum(att_from_super_dl_if)100 * -------------------------------------------------- %



Figure 264. Share of HO attempts from super to regular due to DL interference,S4 (ho_5)



Share of HO attempts from super to regular due to UL interference, S4(ho_6)

sum(att_from_super_ul_if)100 * -------------------------------------------------- %



Figure 265. Share of HO attempts from super to regular due to UL interference,S4 (ho_6)

Share of HO attempts from super to regular due to bad C/I, S4 (ho_7)

sum(att_from_super_bad_ci)100 * -------------------------------------------------- %



Figure 266. Share of HO attempts from super to regular due to bad C/I, S4(ho_7)

MSC incoming HO attempts (ho_8)

sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch_at)


Figure 267. MSC incoming HO attempts (ho_8)

MSC outgoing HO attempts (ho_9)

sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at)


Figure 268. MSC outgoing HO attempts (ho_9)

BSC incoming HO attempts (ho_10)

sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at)




Figure 269. BSC incoming HO attempts (ho_10)

BSC outgoing HO attempts (ho_11)

sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at)


Figure 270. BSC outgoing HO attempts (ho_11)

Intra-cell HO attempts, S6 (ho_12a)

Known problems: Segment related problems: This KPI does not work on BTSlevel if the BTS is part of a multi-segment. The reason is thatan HO attempt counter is triggered for a master BTS (BCCHBTS) first. If the HO is successful then the attempt counter isupdated for the BTS in question. This problem occurs if theHO is unsuccessful. If this is the case, the attempt counterremains in master BTS and is not updated for the BTS thatcaused the HO failure.

sum(cell_tch_tch_at+cell_sdcch_at+cell_sdcch_tch_at)


Unit: Numbers

Figure 271. Intra-cell HO attempts, S6 (ho_12a)

HO attempts, S3 (ho_13a)

sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at + msc_i_sdcch_at)+ sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at)+ sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at + bsc_i_sdcch_at)+ sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at)+ sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at)


Unit: Numbers

Figure 272. HO attempts, S3 (ho_13a)



HO attempts, outgoing and intra-cell, S5 (ho_13b)

sum(cause_up_qual+ cause_up_level+ cause_down_qual+ cause_down_lev+ cause_distance+ cause_msc_invoc+ cause_intfer_up+ cause_intfer_dwn+ cause_umbr+ cause_pbdgt+ cause_omc+ cause_ch_adm+ cause_traffic+ cause_dir_retry+ cause_pre_emption+ cause_field_drop+ cause_low_distance+ cause_bad_CI+ cause_good_CI+ ho_due_slow_mov_ms)


Unit: Numbers

Figure 273. HO attempts, outgoing and intra-cell, S5 (ho_13b)

HO attempts, outgoing and intra-cell, S3 (ho_13e)

sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at)+ sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at)+ sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at)


Unit: Numbers

Figure 274. HO attempts, outgoing and intra-cell, S3 (ho_13e)

HO attempts, outgoing and intra-cell, S9, (ho_13g)

Sum(cause_up_qual+ cause_up_level+ cause_down_qual+ cause_down_lev+ cause_distance+ cause_msc_invoc+ cause_intfer_up+ cause_intfer_dwn+ cause_umbr+ cause_pbdgt+ cause_omc+ cause_traffic+ cause_dir_retry



+ cause_pre_emption+ cause_field_drop+ cause_low_distance+ cause_bad_CI+ cause_good_CI+ ho_due_slow_mov_ms+ ho_due_ms_slow_speed ; new S5,S6,S7 causes+ ho_due_ms_high_speed+ ho_att_due_switch_circ_pool+ ho_att_due_erfd+ ho_att_due_to_bsc_contr_trho.; new S8,S9 causes+ ho_att_due_to_dadlb+ ho_att_due_to_gprs+ ho_att_due_to_hscsd)


Unit: Number

Figure 275. HO attempts, outgoing and intra-cell, S9 (ho_13g)

HO attempts, S11.5 (ho_13h)

Sum(cause_up_qual+ cause_up_level+ cause_down_qual+ cause_down_lev+ cause_distance+ cause_msc_invoc+ cause_intfer_up+ cause_intfer_dwn+ cause_umbr+ cause_pbdgt+ cause_omc+ cause_dir_retry+ cause_pre_emption+ cause_field_drop+ cause_low_distance+ cause_bad_CI+ cause_good_CI+ ho_due_slow_mov_ms+ ho_due_ms_slow_speed ; new S5,S6,S7 causes+ ho_due_ms_high_speed+ ho_att_due_switch_circ_pool+ ho_att_due_erfd+ ho_att_due_to_bsc_contr_trho.; new S8,S9 causes+ ho_att_due_to_dadlb+ ho_att_due_to_gprs+ ho_att_due_to_hscsd+ ho_att_due_bad_super_rxlev+ ho_att_due_good_regular_rxlev+ ho_att_due_direct_access+ ho_attempt_interband_due_level+ ho_attempt_due_to_isho+ ho_att_due_intersys_direct_acc+ ho_att_for_amr_to_hr+ ho_att_for_amr_to_fr+ ho_att_inter_band_sdcch+ ho_att_inter_band_tch+ ho_att_inter_bts_type_sdcch+ ho_att_inter_bts_type_tch )




p_nbsc_ho

Unit: Numbers

Figure 276. HO attempts, S11.5 (ho_13h)

TCH requests for HO (ho_14a)

sum(tch_req-tch_call_req-tch_fast_req)


Unit: Number

Figure 277. TCH requests for HO (ho_14a)

TCH requests for HO (ho_14b)

Note: When you are using IUO, you can see that the number of TCHrequests due to HO attempts goes up (even tenfold).

sum(a.tch_req-a.tch_call_req-tch_fast_req)-sum(b.bsc_i_unsucc_a_int_circ_type+b.msc_controlled_in_ho

+b.ho_unsucc_a_int_circ_type)

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_ho

Unit: Number

Figure 278. TCH requests for HO (ho_14b)

TCH seizures for HO (ho_15)

sum(tch_ho_seiz)


Unit: Numbers

Figure 279. TCH seizures for HO (ho_15)

TCH-TCH HO attempts (ho_16)

Use: Used on the BTS level. If used on the area level, it wouldresult in double counting of inter-cell HOs.



sum( msc_o_tch_tch_at + msc_i_tch_tch_at+ bsc_o_tch_tch_at + bsc_i_tch_tch_at+ cell_tch_tch_at)


Unit: Numbers

Figure 280. TCH-TCH HO attempts (ho_16)

SDCCH-TCH HO attempts (ho_17)


sum( msc_o_sdcch_tch_at + msc_i_sdcch_tch_at+ bsc_o_sdcch_tch_at + bsc_i_sdcch_tch_at+ cell_sdcch_tch_at)


Unit: Numbers

Figure 281. SDCCH-TCH HO attempts (ho_17)

SDCCH-SDCCH HO attempts (ho_18)


sum( msc_o_sdcch_at + msc_i_sdcch_at+ bsc_o_sdcch_at + bsc_i_sdcch_at+ cell_sdcch_at)


Unit: Numbers

Figure 282. SDCCH-SDCCH HO attempts (ho_18)

TCH-TCH HO success (ho_19)


sum( msc_o_tch_tch + msc_i_tch_tch+ bsc_o_tch_tch + bsc_i_tch_tch+ cell_tch_tch)




Unit: Numbers

Figure 283. TCH-TCH HO successes (ho_19)

SDCCH-TCH HO success (ho_20)


sum( msc_o_sdcch_tch + msc_i_sdcch_tch+ bsc_o_sdcch_tch + bsc_i_sdcch_tch+ cell_sdcch_tch)


Unit: Numbers

Figure 284. SDCCH-TCH HO successes (ho_20)

SDCCH-SDCCH HO success (ho_21)


sum( msc_o_sdcch + msc_i_sdcch+ bsc_o_sdcch + bsc_i_sdcch+ cell_sdcch)


Unit: Numbers

Figure 285. SDCCH-SDCCH HO successes (ho_21)

MSC controlled HO attempts (ho_22)


sum( msc_o_tch_tch_at + msc_i_tch_tch_at+ msc_o_sdcch_tch_at + msc_i_sdcch_tch_at+ msc_o_sdcch_at + msc_i_sdcch_at)


Unit: Numbers

Figure 286. MSC controlled HO attempts (ho_22)



BSC controlled HO attempts (ho_23)


sum( bsc_o_tch_tch_at + bsc_i_tch_tch_at+ bsc_o_sdcch_tch_at + bsc_i_sdcch_tch_at+ bsc_o_sdcch_at + bsc_i_sdcch_at)


Unit: Numbers

Figure 287. BSC controlled HO attempts (ho_23)

Intra-cell HO attempts (ho_24)

sum(cell_tch_tch_at+ cell_sdcch_tch_at+ cell_sdcch_at)


Unit: Numbers

Figure 288. Intra-cell HO attempts (ho_24)

MSC controlled HO success (ho_25)


sum( msc_o_tch_tch + msc_i_tch_tch+ msc_o_sdcch_tch + msc_i_sdcch_tch+ msc_o_sdcch_ + msc_i_sdcch)


Unit: Numbers

Figure 289. MSC controlled HO successes (ho_25)

BSC controlled HO success (ho_26)


sum( bsc_o_tch_tch + bsc_i_tch_tch+ bsc_o_sdcch_tch + bsc_i_sdcch_tch+ bsc_o_sdcch + bsc_i_sdcch)




Unit: Numbers

Figure 290. BSC controlled HO successes (ho_26)

Intra-cell HO success (ho_27)

sum(cell_tch_tch + cell_sdcch_tch + cell_sdcch)


Unit: Numbers

Figure 291. Intra-cell HO successes (ho_27)

MSC incoming HO success (ho_28)

sum(msc_i_tch_tch+msc_i_sdcch_tch+msc_i_sdcch)


Unit: Numbers

Figure 292. MSC incoming HO successes (ho_28)

MSC outgoing HO success (ho_29)

sum(msc_o_tch_tch+msc_o_sdcch_tch+msc_o_sdcch)


Unit: Numbers

Figure 293. MSC outgoing HO successes (ho_29)

BSC incoming HO success (ho_30)

sum(bsc_i_tch_tch+bsc_i_sdcch_tch+bsc_i_sdcch)




Unit: Numbers

Figure 294. BSC incoming HO successes (ho_30)

BSC outgoing HO success (ho_31)

sum(bsc_o_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch)


Unit: Numbers

Figure 295. BSC outgoing HO successes (ho_31)

Incoming HO success (ho_32)

sum(msc_i_succ_ho+bsc_i_succ_ho)


Unit: Numbers

Figure 296. Incoming HO success (ho_32)

Outgoing HO success (ho_33)

sum(msc_o_succ_ho+ bsc_o_succ_ho)


Unit: Numbers

Figure 297. Outgoing HO successes (ho_33)

Outgoing HO attempts (ho_34)

sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at+bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at)




Unit: Numbers

Figure 298. Outgoing HO attempts (ho_34)

Incoming HO attempts (ho_35)

sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at + msc_i_sdcch_at+bsc_i_tch_tch_at + bsc_i_sdcch_tch_at + bsc_i_sdcch_at)


Unit: Numbers

Figure 299. Incoming HO attempts (ho_35)

Outgoing SDCCH-SDCCH HO attempts (ho_36)

sum(msc_o_sdcch_at+bsc_o_sdcch_at)


Unit: Numbers

Figure 300. Outgoing SDCCH-SDCCH HO attempts (ho_36)

Incoming SDCCH-SDCCH HO attempts (ho_37)

sum(msc_i_sdcch_at+bsc_i_sdcch_at)


Unit: Numbers

Figure 301. Incoming SDCCH-SDCCH HO attempts (ho_37)

Outgoing SDCCH-TCH HO attempts (ho_38)

sum(msc_o_sdcch_tch_at+bsc_o_sdcch_tch_at)




Unit: Numbers

Figure 302. Outgoing SDCCH-TCH HO attempts (ho_38)

Incoming SDCCH-TCH HO attempts (ho_39)

sum(msc_i_sdcch_tch_at+bsc_i_sdcch_tch_at)


Unit: Numbers

Figure 303. Incoming SDCCH-TCH HO attempts (ho_39)

Outgoing TCH-TCH HO attempts (ho_40)

sum(msc_o_tch_tch_at+bsc_o_tch_tch_at)


Unit: Numbers

Figure 304. Outgoing TCH-TCH HO attempts (ho_40)

Incoming TCH-TCH HO attempts (ho_41)

sum(msc_i_tch_tch_at+bsc_i_tch_tch_at)


Unit: Numbers

Figure 305. Incoming TCH-TCH HO attempts (ho_41)

Outgoing SDCCH-SDCCH HO success (ho_42)

sum(msc_o_sdcch+bsc_o_sdcch)




Unit: Numbers

Figure 306. Outgoing SDCCH-SDCCH HO success (ho_42)

Incoming SDCCH-SDCCH HO success (ho_43)

sum(msc_i_sdcch+bsc_i_sdcch)


Unit: Numbers

Figure 307. Incoming SDCCH-SDCCH HO success (ho_43)

Outgoing SDCCH-TCH HO success (ho_44)

sum(msc_o_sdcch_tch+bsc_o_sdcch_tch)


Unit: Numbers

Figure 308. Outgoing SDCCH-TCH HO success (ho_44)

Incoming SDCCH-TCH HO success (ho_45)

sum(msc_i_sdcch tch+bsc_i_sdcch_tch)


Unit: Numbers

Figure 309. Incoming SDCCH-TCH HO success (ho_45)

Outgoing TCH-TCH HO success (ho_46)

sum(msc_o_tch_tch+bsc_o_tch_tch)




Unit: Numbers

Figure 310. Outgoing TCH-TCH HO success (ho_46)

Incoming TCH-TCH HO success (ho_47)

sum(msc_i_tch_tch+bsc_i_tch_tch)


Unit: Numbers

Figure 311. Incoming TCH-TCH HO success (ho_47)

Intra-cell HO share (ho_48)

Segment related problems: Does not work on BTS level if the BTS is part of amulti-segment. The reason is that an HO attempt counter istriggered for a master BTS (BCCH BTS) first. If the HO issuccessful then the attempt counter is updated for the BTS inquestion. The problem occurs if the HO is unsuccessful. Inthis case, the attempt counter remains in master BTS and isnot updated for the BTS that caused the HO failure.

Known problem: ISHO attempts are not taken into account. Use ho_48ainstead.

sum(cell_sdcch_tch_at + cell_tch_tch_at + cell_sdcch_at)100 * ------------------------------------------------------------

sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at + msc_i_sdcch_at+ msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at+ bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at+ bsc_i_tch_tch_at + bsc_i_sdcch_tch_at + bsc_i_sdcch_at+ cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at)


Figure 312. Intra-cell HO share (ho_48)

MSC controlled incoming HO attempts (ho_49)

sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at + msc_i_sdcch_at)


Figure 313. MSC controlled incoming HO attempts (ho_49)



IBHO attempts (ho_50a)

Use: Total number of IBHO attempts. Sum of IBHO attempts to'Default ANE', 'ALL ANE' and 'ANEs 1…10'

sum(IBHO_ATT_TO_GSM_ALL+ IBHO_ATT_TO_UTRAN_ALL+ IBHO_ATT_TO_GSM_DEFAULT_ANE+ IBHO_ATT_TO_UTRAN_DEFAULT_ANE+ IBHO_ATT_TO_GSM_ANE1+ IBHO_ATT_TO_GSM_ANE2+ IBHO_ATT_TO_GSM_ANE3+ IBHO_ATT_TO_GSM_ANE4+ IBHO_ATT_TO_GSM_ANE5+ IBHO_ATT_TO_GSM_ANE6+ IBHO_ATT_TO_GSM_ANE7+ IBHO_ATT_TO_GSM_ANE8+ IBHO_ATT_TO_GSM_ANE9+ IBHO_ATT_TO_GSM_ANE10+ IBHO_ATT_TO_UTRAN_ANE1+ IBHO_ATT_TO_UTRAN_ANE2+ IBHO_ATT_TO_UTRAN_ANE3+ IBHO_ATT_TO_UTRAN_ANE4+ IBHO_ATT_TO_UTRAN_ANE5+ IBHO_ATT_TO_UTRAN_ANE6+ IBHO_ATT_TO_UTRAN_ANE7+ IBHO_ATT_TO_UTRAN_ANE8+ IBHO_ATT_TO_UTRAN_ANE9+ IBHO_ATT_TO_UTRAN_ANE10)

Counters from table(s):P_NBSC_IMSI_HO

Unit: Numbers

Figure 314. IBHO attempts (ho_50a)

Total IBHO attempts to default ANEs (ho_51)

Use: Total number of IBHOs to default ANEs.

sum(IBHO_ATT_TO_GSM_DEFAULT_ANE + IBHO_ATT_TO_UTRAN_DEFAULT_ANE)


Unit: Numbers

Figure 315. Total IBHO attempts to default ANEs (ho_51)

Share of IBHO attempts to GSM ANEs (ho_52a)

Use: Share of IBHO attempts to GSM ANEs is the ratio betweenall GSM IBHO attempts and total IBHOs. IBHO attempts to'Default ANE', 'ALL ANE' and 'ANEs 1…10'makes the total.

sum(IBHO_ATT_TO_GSM_ALL+ IBHO_ATT_TO_GSM_DEFAULT_ANE+ IBHO_ATT_TO_GSM_ANE1



+ IBHO_ATT_TO_GSM_ANE2+ IBHO_ATT_TO_GSM_ANE3+ IBHO_ATT_TO_GSM_ANE4+ IBHO_ATT_TO_GSM_ANE5+ IBHO_ATT_TO_GSM_ANE6+ IBHO_ATT_TO_GSM_ANE7+ IBHO_ATT_TO_GSM_ANE8+ IBHO_ATT_TO_GSM_ANE9+ IBHO_ATT_TO_GSM_ANE10)

100 * -------------------------------ho_50a


Unit: %

Figure 316. Share of IBHO attempts to GSM ANEs (ho_52a)

Share of IBHO attempts to UTRAN ANEs (ho_53a)

Use: Share of IBHO attempts to UTRAN ANEs is the ratiobetween all UTRAN IBHO attempts and total IBHOs. IBHOattempts to 'Default ANE', 'ALL ANE' and 'ANEs1…10'makes the total.

sum(IBHO_ATT_TO_UTRAN_ALL+ IBHO_ATT_TO_UTRAN_DEFAULT_ANE+ IBHO_ATT_TO_UTRAN_ANE1+ IBHO_ATT_TO_UTRAN_ANE2+ IBHO_ATT_TO_UTRAN_ANE3+ IBHO_ATT_TO_UTRAN_ANE4+ IBHO_ATT_TO_UTRAN_ANE5+ IBHO_ATT_TO_UTRAN_ANE6+ IBHO_ATT_TO_UTRAN_ANE7+ IBHO_ATT_TO_UTRAN_ANE8+ IBHO_ATT_TO_UTRAN_ANE9+ IBHO_ATT_TO_UTRAN_ANE10)

100 * -------------------------------------ho_50a


Unit: %

Figure 317. Share of IBHO attempts to UTRAN ANEs (ho_53a)

Share of default ANE IBHO attempts for GSM ANE (ho_54)

Use: To compare the number of GSM IBHO attempts to sum ofIBHO attempts to GSM and UTRAN (in default ANE IBHOcase).

sum(IBHO_ATT_TO_GSM_DEFAULT_ANE)100 * ----------------------------------------------------------------





Unit: %

Figure 318. Share of default ANE IBHO attempts for GSM ANE (ho_54)

Share of default ANE IBHO attempts for UTRAN ANE (ho_55)

Use: To compare the number of UTRAN IBHO attempts to sum ofIBHO attempts to GSM and UTRAN (in default ANE IBHOcase).

sum(IBHO_ATT_TO_UTRAN_DEFAULT_ANE)100 * ---------------------------------------------------------------



Unit: %

Figure 319. Share of default ANE IBHO attempts for UTRAN ANE (ho_55)

GPRS triggered handovers (ho_61)

Use: Number of GPRS triggered handovers that a voice user canexpect per minute.

Nbr of GPRS-triggered handovers------------------------------- =voice talk time

sum(a.ho_att_due_to_gprs)--------------------------------------------------------sum(period_duration * b.ave_busy_tch / b.res_av_denom14)

Counters from table(s):a = P_NBSC_HOb = P_NBSC_RES_AVAIL

Unit: Number

Figure 320. GPRS triggered handovers (ho_61)

ALL ANE IBHO attempts (ho_62)

Use: Total Number of ALL ANE IBHOs. ALL ANE IBHOcounters are triggered if a subscriber has access to allneighbouring networks (UTRAN and/or GSM) to makeIBHO.



sum(IBHO_ATT_TO_GSM_ALL + IBHO_ATT_TO_UTRAN_ALL)


Unit: Number

Figure 321. ALL ANE IBHO attempts (ho_62)

Share of ALL ANE IBHO attempts to GSM (ho_63)

Use: Defines how many (%) of ALL ANE IBHO attempts aretargeted to GSM network.

sum(IBHO_ATT_TO_GSM_ALL)100 * ------------------------------------------------ %



Unit: %

Figure 322. Share of ALL ANE IBHO attempts to GSM (ho_63)

Share of ALL ANE IBHO attempts to UTRAN (ho_64)

Use: Defines how many (%) of ALL ANE IBHO attempts aretargeted to UTRAN network.

sum(IBHO_ATT_TO_UTRAN_ALL)100 * ------------------------------------------------ %



Unit: %

Figure 323. Share of ALL ANE IBHO attempts to UTRAN (ho_64)

2.19 Handover failure % (hfr)

Total HO failure %, S1 (hfr_1)

Use: Works best on the BTS level, but is usable on both the areaand the cell level.



Experiences on use: In a good network the value can be less than 3 per cent,whereas in a very bad network values higher than 15 per centmay occur. When IUO is used, this formula shows high valuesdue to highly failing intra-cell handovers between layers incongested cells.

Known problems: This formula emphasises the non-intra-cell handovers sincethey are counted twice. This causes no problems on the celllevel, whereas on the area level problems may occur.Blocking is included. Blocking makes this indicator showhigh values especially in the case of IUO, but it does notnecessarily mean that there are problems.

HO failures100 * --------------- %

HO attempts

HO attempts - successful HOs= 100 * ------------------------------- %

HO attempts

successful HOs= 100 * (1- -------------- ) %

HO attempts

sum(msc_i_succ_ho+msc_o_succ_ho+bsc_i_succ_ho+bsc_o_succ_ho+cell_succ_ho)

= 100 * (1- -------------------------------------------------------------------)%sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch_at+

msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at+bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at+bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at+cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at)


Unit: %

Figure 324. Total HO failure %, S1 (hfr_1)

Total HO failure %, S1 (hfr_2)

Use: Used on the area or network level.Experiences on use: In a network gave the result of 8 % instead of 7 % of hfr_1.

In a good network the value can be less than 3 per cent, whilein a very bad network values higher than 15 per cent mayoccur.If Directed Retry is enabled, the MS may, when congestion ofthe source cell SDCCH occurs, be moved from the best cell toa worse one. Then the MS tries to make a handover back butfails if the first cell is still congested. This leads toincrementation of the HO failure ratio.Common reasons for a handover to fail:- incorrect parameter settings of adjacencies- badly defined neighbours (UL coverage becomes a problem)



- UL coverage in general. Cell imbalanced.- TCH blocking in the target cell- UL interference (target BTS never gets the HO access)

Known problems: Blocking is included. Blocking makes this indicator showhigh values especially in the case of IUO, but it does notnecessarily mean that there are some technical problems.Calls that are cleared by the MS user during the HO processincrement the attempt counters but cannot be compensated inthe numerator. (XX2)HO that is interrupted due to another procedure (e.g.assignment) increments the attempt counters but cannot becompensated in the numerator.(XX3)

HO failures100* --------------- %

HO attempts

HO attempts - successful HOs= 100 * --------------------------------- %

HO attempts

successful HOs= 100 * (1- -------------- ) %

HO attempts

sum(msc_o_succ_ho + bsc_o_succ_ho + cell_succ_ho) + XX2+ XX3= 100 * (1- -------------------------------------------------------------------)%

sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at+bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at+cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at)


Unit: %

Figure 325. Total HO failure %, S1 (hfr_2)

Total HO failure ratio (hfr_2a)

Use: Used on the area or network level. However, this formula doesnot work on BTS level if BTS is part of SEG with severalBTSs and there are HOs from other cells. The reason is thatthe incoming HO from another cell triggers the incoming HOattempt counter in the master BTS but the HO success countercan be triggered in another BTS. This is the case only if theHO is unsuccessful.



Experiences on use: In a network the formula gave the result of 8 % instead of 7% of hfr_1. In a good network the value can be less than 3 percent, while in a very bad network values higher than 15 percent may occur.- If Directed Retry is enabled, the MS may, when congestionof the source cell SDCCH occurs, be moved from the best cellto a worse one. Then the MS tries to make a handover backbut fails if the first cell is still congested. This leads toincrementation of the HO failure ratio.Common reasons for a handover to fail:- incorrect parameter settings of adjacencies- badly defined neighbours (UL coverage becomes a problem)- UL coverage generally. Cell imbalanced.- TCH blocking in the target cell- UL interference (target BTS never gets the HO access)RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS

Known problems: Blocking is included. Blocking makes this indicator showhigh values especially in the case of IUO, but it does notnecessarily mean that there are some technical problems.

HO attempts - successful HOs100 * ---------------------------------

HO attempts

successful HOs= 100 * (1- -------------- )

HO attempts

sum(a.msc_o_succ_ho + a.bsc_o_succ_ho + a.cell_succ_ho)100 * (1- -----------------------------------------------------------)

sum(b.msc_o_ho_cmd + b.bsc_o_ho_cmd_assgn + b.bts_ho_assgn)

Counters from table(s):a = p_nbsc_hob = p_nbsc_traffic

Unit: %

Figure 326. Total HO failure ratio (hfr_2a)

Intra-cell HO failure share, S1 (hfr_3a)

Use: Used on the BTS level. The results are equal to hfr_3c.Intra-cell HO failures

100* (--------------------------------------) %All HO attempts

sum(cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch-at)-sum(cell_succ_ho)

= 100* (--------------------------------------------------------------) %sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at + msc_i_sdcch_at)

+ sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at)+ sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at + bsc_i_sdcch_at)+ sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at)



+ sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at)


Figure 327. Intra-cell HO failure share, S1 (hfr_3a)

Intra-cell HO failure share, S1 (hfr_3b)

Use: Used on the area or network level. The results are equal tohfr_3d.

Intra-cell HO failures100* (--------------------------------------) %

All HO attempts

sum(cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch-at)-sum(cell_succ_ho)

= 100* (--------------------------------------------------------------) %sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at+ msc_i_sdcch_at)

+ sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at+ msc_o_sdcch_at)+ sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at+ bsc_i_sdcch_at)+ sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at+ bsc_o_sdcch_at)+ sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at)


Unit: %

Figure 328. Intra-cell HO failure share, S1 (hfr_3b)

Intra-cell HO failure share, S1 (hfr_3c)

Use: Used on the BTS level. The results are equal to hfr_3a.


All HO attempts

sum(cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at)-sum(cell_tch_tch+cell_sdcch_tch+cell_sdcch)




Unit: %

Figure 329. Intra-cell HO failure share, S1 (hfr_3c)



Intra-cell HO failure share, S1 (hfr_3d)

Use: On the area or network level. The results are equal to hfr_3b.


All HO attempts

sum(cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at)-sum(cell_tch_tch+cell_sdcch_tch+cell_sdcch)

= 100* (--------------------------------------------------------------) %sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at+ msc_o_sdcch_at)

+ sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at+ bsc_o_sdcch_at)+ sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at)


Unit: %

Figure 330. Intra-cell HO failure share, S1 (hfr_3d)

Incoming MSC ctrl HO failure %, S1 (hfr_4)

MSC controlled incoming HO successes100* (1- --------------------------------------) %

MSC controlled incoming HO attempts

sum(msc_i_tch_tch+msc_i_sdcch_tch+msc_i_sdcch)= 100* (1- -----------------------------------------------------------) %



Unit: %

Figure 331. Incoming MSC ctrl HO failure %, S1 (hfr_4)

Incoming MSC ctrl HO failure share, S1 (hfr_4a)

Use: Used on the BTS level. The results are equivalent to hfr_4c.

MSC controlled incoming HO failures100* (--------------------------------------) %

All HO attempts

sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch-at)-sum(msc_i_succ_ho)






Unit: %

Figure 332. Incoming MSC ctrl HO failure share, S1 (hfr_4a)

Incoming MSC ctrl HO failure share, S1 (hfr_4b)



All HO incoming attempts

sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch-at)-sum(msc_i_succ_ho)


+ sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at+ bsc_i_sdcch_at)+ sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at)


Unit: %

Figure 333. Incoming MSC ctrl HO failure share, S1 (hfr_4b)

Incoming MSC ctrl HO failure share, S1 (hfr_4c)



All HO attempts

sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch_at)- sum(msc_i_tch_tch+msc_i_sdcch_tch+msc_i_sdcch)




Unit: %

Figure 334. Incoming MSC ctrl HO failure share, S1 (hfr_4c)



Incoming MSC ctrl HO failure share, S1 (hfr_4d)

Use: Used on the area or network level. The results are equal tohfr_4b.


All HO incoming attempts

sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch_at)- sum(msc_i_tch_tch+msc_i_sdcch_tch+msc_i_sdcch)




Unit: %

Figure 335. Incoming MSC ctrl HO failure share, S1 (hfr_4d)

Outgoing MSC ctrl HO failure ratio %, S1 (hfr_5)

sum(msc_o_tch_tch+msc_o_sdcch_tch+msc_o_sdcch)100 - 100 * ------------------------------------------------------------ %

sum(nvl(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at,0)


Unit: %

Figure 336. Outgoing MSC ctrl HO failure ratio %, S1 (hfr_5)

Outgoing MSC ctrl HO failure share %, S1 (hfr_5a)

Use: Used on the BTS level. The results are equal to hfr_5c.

MSC controlled outgoing HO failures100* (--------------------------------------) %

All HO attempts

sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch-at)-sum(msc_o_succ_ho)






Unit: %

Figure 337. Outgoing MSC ctrl HO failure share %, S1 (hfr_5a)

Outgoing MSC ctrl HO failure share %, S1 (hfr_5b)



All HO outgoing attempts

sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch-at)-sum(msc_o_succ_ho)




Unit: %

Figure 338. Outgoing MSC ctrl HO failure share %, S1 (hfr_5b)

Outgoing MSC ctrl HO failure share %, S1 (hfr_5c)



All HO attempts

sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at)- sum(msc_o_tch_tch+msc_o_sdcch_tch+msc_o_sdcch)




Unit: %

Figure 339. Outgoing MSC ctrl HO failure share %, S1 (hfr_5c)



Outgoing MSC ctrl HO failure share %, S1 (hfr_5d)



All HO outgoing attempts





Unit: %

Figure 340. Outgoing MSC ctrl HO failure share %, S1 (hfr_5d)

Incoming BSC ctrl HO failure %, S1 (hfr_6)

BSC controlled incoming HO successes100* (1- --------------------------------------) %

BSC controlled incoming HO attempts

sum(bsc_i_tch_tch+bsc_i_sdcch_tch+bsc_i_sdcch)= 100* (1- ------------------------------------------------------------) %

sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at)


Unit: %

Figure 341. Incoming BSC ctrl HO failure %, S1 (hfr_6)

Incoming BSC ctrl HO failure share %, S1 (hfr_6a)


BSC controlled incoming HO failures100* (--------------------------------------) %

All HO attempts

sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch-at)-sum(bsc_i_succ_ho)






Unit: %

Figure 342. Incoming BSC ctrl HO failure share %, S1 (hfr_6a)

Incoming BSC ctrl HO failure %, S1 (hfr_6b)

Use: Use on the area or network level. The results are equal tohfr_6d.


All incoming HO attempts

sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch-at)-sum(bsc_i_succ_ho)




Unit: %

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

Incoming BSC ctrl HO failure share %, S1 (hfr_6c)



All HO attempts

sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at)-sum(bsc_i_tch_tch+bsc_i_sdcch_tch+bsc_i_sdcch)




Unit: %

Figure 344. Incoming BSC ctrl HO failure share %, S1 (hfr_6c)



Incoming BSC ctrl HO failure %, S1 (hfr_6d)



All incoming HO attempts

sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at)-sum(bsc_i_tch_tch+bsc_i_sdcch_tch+bsc_i_sdcch)




Unit: %

Figure 345. Incoming BSC ctrl HO failure %, S1 (hfr_6d)

Outgoing BSC ctrl HO failure share, S1 (hfr_7)

BSC controlled outgoing HO successes100* (1- --------------------------------------) %

BSC controlled outgoing HO attempts

sum(bsc_o_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch)= 100* (1- ------------------------------------------------------------) %

sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at)


Unit: %

Figure 346. Outgoing BSC ctrl HO failure share, S1 (hfr_7)

Outgoing BSC ctrl HO failure share, S1 (hfr_7a)


BSC controlled outgoing HO failures100* (--------------------------------------) %

All HO attempts

sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch-at)-sum(bsc_o_succ_ho)






Unit: %

Figure 347. Outgoing BSC ctrl HO failure share, S1 (hfr_7a)

Outgoing BSC ctrl HO failure share, S1 (hfr_7b)



All HO attempts

sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch-at)-sum(bsc_o_succ_ho)




Unit: %

Figure 348. Outgoing BSC ctrl HO failure share, S1 (hfr_7b)

Outgoing BSC ctrl HO failure share, S1 (hfr_7c)



All HO attempts

sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at)-sum(bsc_o_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch)




Unit: %

Figure 349. Outgoing BSC ctrl HO failure share, S1 (hfr_7c)

Outgoing BSC ctrl HO failure share, S1 (hfr_7d)

Use: On the area or PLMN level. The results are equal to hfr_7b.




All HO attempts

sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at)-sum(bsc_o_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch)




Unit: %

Figure 350. Outgoing BSC ctrl HO failure share, S1 (hfr_7d)

Internal inter HO failure %, S4 (hfr_8)

sum(int_inter_ho_source_fail)100* (-----------------------------------------------) %

sum(int_inter_ho_source_fail+int_inter_ho_succ)


Unit: %

Figure 351. Internal inter HO failure %, S4 (hfr_8)

Internal intra HO failure %, S4 (hfr_9)

sum(int_intra_ho_source_fail)100* (-----------------------------------------------) %

sum(int_intra_ho_source_fail+int_intra_ho_succ)


Unit: %

Figure 352. Internal intra HO failure %, S4 (hfr_9)

External source HO failure %, S4 (hfr_10)

sum(ext_ho_source_fail)100* (-----------------------------------------------) %

sum(ext_ho_source_fail+ ext_ho_source_succ)




Unit: %

Figure 353. External source HO failure %, S4 (hfr_10)

HO failure % from super to regular, S4 (hfr_12)

Use: Ratio of all other failures than ’blocked’ to all HO attemptsfrom super to regular TRX.

sum(ho_fail_to_reg_due_ret+ ho_fail_to_reg_ms_lost+ ho_fail_to_reg_freq)100* (-------------------------------------------------------------------------) %

sum(ho_att_to_reg_freq)


Unit: %

Figure 354. HO failure % from super to regular, S4 (hfr_12)

HO failure % from regular to super, S4 (hfr_13)

sum(ho_fail_from_reg_due_ret+ho_fail_from_reg_ms_lost+ho_fail_from_reg_freq)100*(------------------------------------------------------------------------) %

sum(ho_att_from_reg_freq)


Unit: %

Figure 355. HO failure % from regular to super, S4 (hfr_13)

Share of HO failures from regular to super due to return, S4 (hfr_14)

sum(ho_fail_from_reg_due_ret)100* (------------------------------------------------------------------------) %

sum(ho_fail_from_reg_due_ret+ho_fail_from_reg_ms_lost+ho_fail_from_reg_freq)


Unit: %

Figure 356. Share of HO failures from regular to super due to return, S4 (hfr_14)



Share of HO failures from regular to super due to MS lost, S4 (hfr_15)

Use: Ratio of ’MS Lost’ failures to all HO attempts (blocked HOsexcluded) in HOs from regular to super TRX.

sum(ho_fail_from_reg_ms_lost)100* (--------------------------------------------------------------------------)%

sum(ho_fail_from_reg_due_ret+ ho_fail_from_reg_ms_lost+ ho_fail_from_reg_freq)


Unit: %

Figure 357. Share of HO failures from regular to super due to MS lost, S4(hfr_15)

Share of HO failures from regular to super due to another cause, S4 (hfr_16)

Use: Ratio of any other HO failures than ’return’ and ’MS lost’ toall HO attempts (blocked HOs excluded) in HOs from regularto super TRX.

sum(ho_fail_from_reg_freq)100* (--------------------------------------------------------------------------) %

sum(ho_fail_from_reg_due_ret+ ho_fail_from_reg_ms_lost+ ho_fail_from_reg_freq)


Unit: %

Figure 358. Share of HO failures from regular to super due to another cause, S4(hfr_16)

Share of HO failures from super to regular due to return, S4 (hfr_17)

Use: Ratio of ’return’ HO failures to all HO attempts (blocked HOsexcluded) in HOs from super to regular TRX.

sum(ho_fail_to_reg_due_ret)100* (--------------------------------------------------------------------------) %

sum(ho_fail_to_reg_due_ret+ ho_fail_to_reg_ms_lost+ ho_fail_to_reg_freq)


Unit: %

Figure 359. Share of HO failures from super to regular due to return, S4 (hfr_17)



Share of HO failures from super to regular due to MS lost, S4 (hfr_18)

Use: Ratio of ’MS lost’ HO failures to all HO attempts (blockedHOs excluded) in HOs from super to regular TRX.

sum(ho_fail_to_reg_ms_lost)100* (--------------------------------------------------------------------------) %

sum(ho_fail_to_reg_due_ret+ ho_fail_to_reg_ms_lost+ ho_fail_to_reg_freq)


Unit: %

Figure 360. Share of HO failures from super to regular due to MS lost, S4(hfr_18)

Share of HO failures from super to regular due to another cause, S4 (hfr_19)

Experiences on use: Includes HO failures due to any other reason than ’return’and ’MS lost’.

Use: Ratio of ’Other cause’ HO failures to all HO attempts(blocked HOs excluded) in HOs from super to regular TRX.

sum(ho_fail_to_reg_freq)100*(-----------------------------------------------------------------------) %

sum(ho_fail_to_reg_due_ret+ho_fail_to_reg_ms_lost+ho_fail_to_reg_freq)


Unit: %

Figure 361. Share of HO failures from super to regular due to another cause, S4(hfr_19)

SDCCH-SDCCH HO failure %, S2 (hfr_20)

Experiences on use: It is better to look at MSC and BSC controlled handoverseparately.

sum(msc_i_sdcch+ msc_o_sdcch+ bsc_i_sdcch+ bsc_o_sdcch+ cell_sdcch)

-sum(msc_i_sdcch_at + msc_o_sdcch_at+ bsc_i_sdcch_at + bsc_o_sdcch_at+ cell_sdcch_at)

100* (----------------------------------------------) %sum(msc_i_sdcch_at + msc_o_sdcch_at

+ bsc_i_sdcch_at + bsc_o_sdcch_at+ cell_sdcch_at)




Unit: %

Figure 362. SDCCH-SDCCH HO failure %, S2 (hfr_20)

SDCCH-TCH HO failure %, S2 (hfr_21)

Use: These are Directed Retry.

sum(msc_i_sdcch_tch+ msc_o_sdcch_tch+ bsc_i_sdcch_tch+ bsc_o_sdcch_tch+ cell_sdcch_tch)

- sum(msc_i_sdcch_tch_at + msc_o_sdcch_tch_at+ bsc_i_sdcch_tch_at + bsc_o_sdcch_tch_at+ cell_sdcch_tch_at)

100* (-----------------------------------------------------) %sum(msc_i_sdcch_tch_at + msc_o_sdcch_tch_at

+ bsc_i_sdcch_tch_at + bsc_o_sdcch_tch_at+ cell_sdcch_tch_at)


Unit: %

Figure 363. SDCCH-TCH HO failure %, S2 (hfr_21)

TCH-TCH HO failure %, S2 (hfr_22)

sum(msc_i_tch_tch+ msc_o_tch_tch+ bsc_i_tch_tch+ bsc_o_tch_tch+ cell_tch_tch)

-sum(msc_i_tch_tch_at + msc_o_tch_tch_at+ bsc_i_tch_tch_at + bsc_o_tch_tch_at+ cell_tch_tch_at)

100* (--------------------------------------------------) %sum(msc_i_tch_tch_at + msc_o_tch_tch_at

+ bsc_i_tch_tch_at + bsc_o_tch_tch_at+ cell_tch_tch_at)


Unit: %

Figure 364. TCH-TCH HO failure %, S2 (hfr_22)

SDCCH-SDCCH incoming HO failure %, S2 (hfr_23)

sum(msc_i_sdcch_at+ bsc_i_sdcch_at) - sum(msc_i_sdcch + bsc_i_sdcch)100* ------------------------------------------------------------------------- %

sum(msc_i_sdcch_at+ bsc_i_sdcch_at)




Unit: %

Figure 365. SDCCH-SDCCH incoming HO failure %, S2 (hfr_23)

SDCCH-SDCCH outgoing HO failure ratio, S2 (hfr_24)

sum(msc_o_sdcch_at+ bsc_o_sdcch_at) - sum(msc_o_sdcch + bsc_o_sdcch)100* ------------------------------------------------------------------------ %

sum(msc_o_sdcch_at+ bsc_o_sdcch_at)


Unit: %

Figure 366. SDCCH-SDCCH outgoing HO failure ratio, S2 (hfr_24)

SDCCH-TCH incoming HO failure %, S2 (hfr_25)

sum(msc_i_sdcch_tch_at+ bsc_i_sdcch_tch_at)-sum(msc_i_sdcch_tch + bsc_i_sdcch_tch)

100* (------------------------------------------------) %sum(msc_i_sdcch_tch_at+ bsc_i_sdcch_tch_at)


Unit: %

Figure 367. SDCCH-TCH incoming HO failure %, S2 (hfr_25)

SDCCH-TCH outgoing HO failure %, S2 (hfr_26)

sum(msc_o_sdcch_tch_at+ bsc_o_sdcch_tch_at)-sum(msc_o_sdcch_tch + bsc_o_sdcch_tch)

100* ----------------------------------------------- %sum(msc_o_sdcch_tch_at+ bsc_o_sdcch_tch_at)


Unit: %

Figure 368. SDCCH-TCH outgoing HO failure %, S2 (hfr_26)

TCH-TCH incoming HO failure %, S2 (hfr_27)

sum(msc_i_tch_tch_at+ bsc_i_tch_tch_at) - sum(msc_i_tch_tch + bsc_i_tch_tch)



100* --------------------------------------------------------------------------- %sum(msc_i_tch_tch_at+ bsc_i_tch_tch_at)


Unit: %

Figure 369. TCH-TCH incoming HO failure %, S2 (hfr_27)

TCH-TCH outgoing HO failure %, S2 (hfr_28)

sum(msc_o_tch_tch_at+ bsc_o_tch_tch_at) - sum(msc_o_tch_tch + bsc_o_tch_tch)100* --------------------------------------------------------------------------- %

sum(msc_o_tch_tch_at+ bsc_o_tch_tch_at)


Unit: %

Figure 370. TCH-TCH outgoing HO failure %, S2 (hfr_28)

MSC ctrl HO failure %, blocking (hfr_29)

msc_o_fail_lack100* ------------------------------------------------------ %

msc_o_sdcch_at + msc_o_sdcch_tch_at + msc_o_tch_tch_at


Unit: %

Figure 371. MSC ctrl HO failure %, blocking (hfr_29)

MSC ctrl HO failure %, not allowed (hfr_30)

msc_o_not_allwd100* ------------------------------------------------------ %



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



MSC ctrl HO failure %, return to old (hfr_31)

msc_o_fail_ret100* ------------------------------------------------------ %



Unit: %

Figure 373. MSC ctrl HO failure %, return to old (hfr_31)

MSC ctrl HO failure %, call clear (hfr_32)

msc_o_call_clr100* ------------------------------------------------------ %



Unit: %

Figure 374. MSC ctrl HO failure %, call clear (hfr_32)

MSC ctrl HO failure %, end HO (hfr_33)

msc_o_end_of_ho100* ------------------------------------------------------ %



Unit: %

Figure 375. MSC ctrl HO failure %, end HO (hfr_33)

MSC ctrl HO failure %, end HO BSS (hfr_34)

msc_o_end_ho_bss100* ------------------------------------------------------ %



Unit: %

Figure 376. MSC ctrl HO failure %, end HO BSS (hfr_34)



MSC ctrl HO failure %, wrong A interface (hfr_35)

Use: Relates to the congestion of A-interface pool resourcesdetected by BSC.

msc_controlled_out_ho100* ------------------------------------------------------ %



Unit: %

Figure 377. MSC ctrl HO failure %, wrong A interface (hfr_35)

MSC ctrl HO failure %, adjacent cell error (hfr_36)

msc_o_adj_cell_id_err_c100* ------------------------------------------------------ %



Unit: %

Figure 378. MSC ctrl HO failure %, adjacent cell error (hfr_36)

BSC ctrl HO failure %, blocking (hfr_37)

bsc_o_fail_lack100* ------------------------------------------------------ %

bsc_o_sdcch_at + bsc_o_sdcch_tch_at + bsc_o_tch_tch_at


Unit: %

Figure 379. BSC ctrl HO failure %, blocking (hfr_37)

BSC ctrl HO failure %, not allowed (hfr_38)

bsc_o_not_allwd100* ------------------------------------------------------ %





Unit: %

Figure 380. BSC ctrl HO failure %, not allowed (hfr_38)

BSC ctrl HO failure %, return to old (hfr_39)

bsc_o_fail_ret100* ------------------------------------------------------ %



Unit: %

Figure 381. BSC ctrl HO failure %, return to old (hfr_39)

BSC ctrl HO failure %, call clear (hfr_40)

bsc_o_call_clr100* ------------------------------------------------------ %



Unit: %

Figure 382. BSC ctrl HO failure %, call clear (hfr_40)

BSC ctrl HO failure %, end HO (hfr_41)

bsc_o_end_of_ho100* ------------------------------------------------------ %



Unit: %

Figure 383. BSC ctrl HO failure %, end HO (hfr_41)

BSC ctrl HO failure %, end HO BSS (hfr_42)

bsc_o_end_ho_bss100* ------------------------------------------------------ %





Unit: %

Figure 384. BSC ctrl HO failure %, end HO BSS (hfr_42)

BSC ctrl HO failure %, wrong A interface (hfr_43)


bsc_o_unsucc_a_int_circ_type100* ------------------------------------------------------ %



Unit: %

Figure 385. BSC ctrl HO failure %, wrong A interface (hfr_43)

BSC ctrl HO drop call % (hfr_44)

bsc_o_drop_calls100* ------------------------------------------------------ %



Unit: %

Figure 386. BSC ctrl HO drop call % (hfr_44)

Intra-cell HO failure %, cell_fail_lack (hfr_45)

cell_fail_lack100* --------------------------------------------------- %

cell_sdcch_at + cell_sdcch_tch_at + cell_tch_tch_at


Unit: %

Figure 387. Intra-cell HO failure %, cell_fail_lack (hfr_45)



Intra-cell HO failure %, not allowed (hfr_46)

cell_not_allwd100* --------------------------------------------------- %



Unit: %

Figure 388. Intra-cell HO failure %, not allowed (hfr_46)

Intra-cell HO failure %, return to old (hfr_47)

cell_fail_ret100* --------------------------------------------------- %



Unit: %

Figure 389. Intra-cell HO failure %, return to old (hfr_47)

Intra-cell HO failure %, call clear (hfr_48)

cell_call_clr100* --------------------------------------------------- %



Unit: %

Figure 390. Intra-cell HO failure %, call clear (hfr_48)

Intra-cell HO failure %, MS lost (hfr_49)

cell_fail_move100* --------------------------------------------------- %



Unit: %

Figure 391. Intra-cell HO failure %, MS lost (hfr_49)



Intra-cell HO failure %, BSS problem (hfr_50)

cell_fail_bss100* --------------------------------------------------- %



Unit: %

Figure 392. Intra-cell HO failure %, BSS problem (hfr_50)

Intra-cell HO failure %, drop call (hfr_51)

cell_drop_calls100* --------------------------------------------------- %



Unit: %

Figure 393. Intra-cell HO failure %, drop call (hfr_51)

HO failure % to adjacent cell (hfr_52)

sum(ho_att_to_adj - ho_succ_to_adj)100* ----------------------------------- %

sum(ho_att_to_adj)

Counters from table(s):p _nbsc_ho_adj

Unit: %

Figure 394. HO failure % to adjacent cell (hfr_52)

HO failure % from adjacent cell (hfr_53)

sum(ho_att_from_adj - ho_succ_from_adj)100* --------------------------------------- %

sum(ho_att_from_adj)

Counters from table(s):p _nbsc_ho_adj

Unit: %

Figure 395. HO failure % from adjacent cell (hfr_53)



HO failure %, blocking excluded (hfr_54a)


/* all HO attempts */sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at

+bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at+cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at)

/*successful handovers */-sum(msc_o_succ_ho +bsc_o_succ_ho+cell_succ_ho)

/* handovers failing due to blocking */-sum(msc_o_fail_lack+bsc_o_fail_lack+cell_fail_lack)

100 * ------------------------------------------------------%/* all HO attempts */sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at




Unit: %

Figure 396. HO failure %, blocking excluded (hfr_54a)

HO failure % due to radio interface blocking (hfr_55)


/* handovers failing due to blocking */sum(msc_o_fail_lack+bsc_o_fail_lack+cell_fail_lack)

100 * -------------------------------------------------------- %/* all HO attempts */sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at



Unit: %

Figure 397. HO failure % due to radio interface blocking (hfr_55)

Intra-cell HO failure %, wrong A interface (hfr_56)


sum(ho_unsucc_a_int_circ_type)100 x -------------------------------------------------------- %

sum(cell_sdcch_at + cell_sdcch_tch_at + cell_tch_tch_at)




Unit: %

Figure 398. Intra-cell HO failure %, wrong A interface (hfr_56)

Intra-cell HO failure % (hfr_57)

Intra-cell HO successes100* (1- -------------------------) %

Intra-cell HO attempts

sum(cell_tch_tch + cell_sdcch_tch+ cell_sdcch)= 100* (1- ---------------------------------------------------------------) %

sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at)


Unit: %

Figure 399. Intra-cell HO failure % (hfr_57)

HO failures to target cell, S6 (hfr_58)

Use: On the adjacency level. Gives the failure % of the real (nonblocked) HO attempts.

Known problems: Not accurate because of:1) Calls that are cleared by MS user during the HO process.The ho_att_to_adj counter is incremented and cannot becompensated in the numerator.2) HO that is interrupted due to another procedure (e.g.assignment) increments attempt counters but cannot becompensated in the numerator.

sum(ho_att_to_adj-ho_succ_to_adj-ho_fail_res_to_adj)100* -------------------------------------------------------- %

sum(ho_att_to_adj- ho_fail_res_to_adj)

Counters from table(s):p_nbsc_ho_adj

Unit: %

Figure 400. HO failures to target cell, S6 (hfr_58)

HO failures from target cell, S6 (hfr_59)

Use: Used on the adjacency level. Gives failure % of the real(unblocked) HO attempts.



Known problems: Not accurate because of:1) Calls that are cleared by MS user during the HO process.The ho_att_to_adj counter is incremented and cannot becompensated in the numerator.2) HO that is interrupted due to other procedure (for exampleassignment) increments attempt counters but cannot becompensated in the numerator.

sum(ho_att_from_adj-ho_succ_from_adj-ho_fail_res_from_adj)100* ----------------------------------------------------------- %

sum(ho_att_from-adj- ho_fail_res_from_adj)


Unit: %

Figure 401. HO failures from target cell, S6 (hfr_59)

HO drop ratio (hfr_68)

Use: Defines how big a share of the started handovers is dropped.Indicates the quality of the handovers.

Sum(bsc_o_drop_calls+msc_o_call_drop_ho +cell_drop_calls)100* --------------------------------------------------------- %

/* all HO attempts */sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at


/* handovers failing due to blocking */-sum(msc_o_fail_lack+bsc_o_fail_lack+cell_fail_lack)/* handovers failing due to not allowed */

-sum(msc_o_not_allwd+bsc_o_not_allwd+cell_not_allwd)/* wrong Aif circuit type */

-sum(bsc_o_unsucc_a_int_circ_type+msc_controlled_out_ho+ho_unsucc_a_int_circ_type

)


Unit: %

Figure 402. HO drop ratio (hfr_68)

HO drop ratio (hfr_68a)

Use: Defines how big a share of the started handovers is dropped.Indicates the quality of the handovers.



Segment related problems: Does not work on BTS level if the BTS is part of amultisegment. A reason for this is that an attempt countertriggers for a target BTS only if the handover is successful. Inthe case of a handover failure, the attempt counter triggersonly for the master BTS.

Sum(bsc_o_drop_calls+msc_o_call_drop_ho +cell_drop_calls)100* --------------------------------------------------------- %

/* all HO attempts */sum(msc_o_ho_cmd + bsc_o_ho_cmd_assgn + bts_ho_assgn)/* handovers failing due to blocking */

-sum(msc_o_fail_lack+bsc_o_fail_lack+cell_fail_lack)/* handovers failing due to not allowed */

-sum(msc_o_not_allwd+bsc_o_not_allwd+cell_not_allwd)/* wrong Aif circuit type */

-sum(bsc_o_unsucc_a_int_circ_type+msc_controlled_out_ho+ho_unsucc_a_int_circ_type )


Unit: %

Figure 403. HO drop ratio (hfr_68a)

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

Use: Gives the failure percentage of the non-blocked HO attempts.

sum(ho_att_wcdma_ran_cell-ho_succ_wcdma_ran_cell-ho_fail_due_res_wcdma_ran)

100 * ------------------------------- %sum(ho_att_wcdma_ran_cell

- ho_fail_due_res_wcdma_ran)

Counters from table(s):p_nbsc_utran_ho_adj_cell

Unit: %

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

HO failures from target WCDMA cell, S10.5 (hfr_70)

Use: Gives the failure percentage of the non-blocked HO attempts.

sum(ho_att_from_wcdma_ran-ho_succ_from_wcdma_ran-ho_fail_due_res_wcdma_ran_cell)

100 * ------------------------------------ %sum(ho_att_from_wcdma_ran

-ho_fail_due_res_wcdma_ran_cell)




Unit: %

Figure 405. HO failures from target WCDMA cell, S10.5 (hfr_70)

Intra-Segment SDCCH-SDCCH HO failure ratio from BCCH to non-BCCH layer, BSC level, S10.5 (hfr_71)

Use: Gives intra-segment SDCCH-SDCCH HO failure ratio fromBCCH to non-BCCH layer.

Known problems: Timing difference in two measurements.

sum(b.INTRA_INTER_BAND_SDCCH_HANDOVER)100 - 100* -------------------------------------- %

sum(a.HO_ATT_INTER_BAND_SDCCH)

a = p_nbsc_hob = p_nbsc_cc_pm

Counters from table(s):p_nbsc_hop_nbsc_cc_pm

Unit: %

Figure 406. Intra-Segment SDCCH-SDCCH HO failure ratio from BCCH to non-BCCH layer, BSC level, S10.5 (hfr_71)

Intra-segment SDCCH-SDCCH HO failure ratio between BTS types, BSClevel, S10.5 (hfr_72)

Use: Gives intra-segment SDCCH-SDCCH HO failure ratiobetween BTS types.

Known problems: See hfr_71.

sum(b.INTRA_INTER_BTS_TYPE_TCH)100 - 100* -------------------------------------- %

sum(a.HO_ATT_INTER_BTS_TYPE_TCH)



Unit: %

Figure 407. IIntra-segment SDCCH-SDCCH HO failure ratio between BTStypes, BSC level, S10.5 (hfr_72)



Intra-segment TCH-TCH HO failure ratio between bands (due to load), BSClevel, S10.5 (hfr_73)

Use: Gives intra-segment TCH-TCH HO failure ratio betweenbands (due to load reason).


sum(b.INTRA_INTER_BAND_TCH)100 - 100* -------------------------------------- %

sum(a.HO_ATT_INTER_BAND_TCH)


Counters from table(s):p_nbsc_ho p_nbsc_cc_pm

Figure 408. Intra-segment TCH-TCH HO failure ratio between bands (due toload), BSC level, S10.5 (hfr_73)

Intra-segment TCH-TCH HO failure ratio between bands (due to downlinksignal level), BSC level, S10.5 (hfr_74)

Use: Gives intra-segment TCH-TCH HO failure ratio betweenbands (due to downlink signal level).


sum(b.INTRA_INTER_BAND_DUE_LEV)100 - 100* -------------------------------------- %

sum(a.HO_ATTEMPT_INTERBAND_DUE_LEVEL)



Unit: %

Figure 409. Intra-segment TCH-TCH HO failure ratio between bands (due todownlink signal level), BSC level, S10.5 (hfr_74)

Intra-segment TCH-TCH HO failure ratio between BTS types (due to load),BSC level, S10.5 (hfr_75)

Use: Gives intra-segment TCH-TCH HO failure ratio betweenBTS types (due to load).


sum(b.INTRA_INTER_BTS_TYPE_TCH)100 - 100* -------------------------------------- %

sum(a.HO_ATT_INTER_BTS_TYPE_TCH)

a = p_nbsc_ho



b = p_nbsc_cc_pm


Unit: %

Figure 410. Intra-segment TCH-TCH HO failure ratio between BTS types (due toload), BSC level, S10.5 (hfr_75)

IBHO failure ratio for default GSM ANE (hfr_76)

Use: To compare how GSM to GSM IBHOs perform.

sum(IBHO_UNS_TO_GSM_DEFAULT_ANE)100 * -------------------------------- %

sum(IBHO_ATT_TO_GSM_DEFAULT_ANE)

Unit: %Counters from table(s):P_NBSC_IMSI_HO

Figure 411. IBHO failure ratio for default GSM ANE (hfr_76)

IBHO failure ratio for default UTRAN ANE (hfr_77)

Use: To compare how GSM to UTRAN IBHOs perform.

sum(IBHO_UNS_TO_UTRAN_DEFAULT_ANE)100 * ---------------------------------- %

sum(IBHO_ATT_TO_UTRAN_DEFAULT_ANE)


Unit: %

Figure 412. IBHO failure ratio for default UTRAN ANE (hfr_77)

IBHO failure ratio to GSM ANEs (hfr_78a)

Use: IBHO failure ratio for all GSM ANEs. It shows theunsuccessful GSM IBHOs compared to total IBHOs.

sum(IBHO_UNS_TO_GSM_ALL + IBHO_UNS_TO_GSM_DEFAULT_ANE + IBHO_UNS_TO_GSM_ANE1+ IBHO_UNS_TO_GSM_ANE2 + IBHO_UNS_TO_GSM_ANE3 + IBHO_UNS_TO_GSM_ANE4+ IBHO_UNS_TO_GSM_ANE5 + IBHO_UNS_TO_GSM_ANE6 + IBHO_UNS_TO_GSM_ANE7+ IBHO_UNS_TO_GSM_ANE8 + IBHO_UNS_TO_GSM_ANE9 + IBHO_UNS_TO_GSM_ANE10)

100 * ------------------------------------------------------------- %sum(IBHO_ATT_TO_GSM_ALL + IBHO_ATT_TO_GSM_DEFAULT_ANE + IBHO_ATT_TO_GSM_ANE1

+ IBHO_ATT_TO_GSM_ANE2 + IBHO_ATT_TO_GSM_ANE3 + IBHO_ATT_TO_GSM_ANE4+ IBHO_ATT_TO_GSM_ANE5 + IBHO_ATT_TO_GSM_ANE6 + IBHO_ATT_TO_GSM_ANE7+ IBHO_ATT_TO_GSM_ANE8 + IBHO_ATT_TO_GSM_ANE9 + IBHO_ATT_TO_GSM_ANE10)




Unit: %

Figure 413. IBHO failure ratio to GSM ANEs (hfr_78a)

IBHO failure ratio to UTRAN ANEs (hfr_79a)

Use: IBHO failure ratio for all UTRAN ANEs. It shows theunsuccessful UTRAN IBHOs compared to total IBHOs.

sum(IBHO_UNS_TO_UTRAN_ALL+ IBHO_UNS_TO_UTRAN_DEFAULT_ANE+ IBHO_UNS_TO_UTRAN_ANE1+ IBHO_UNS_TO_UTRAN_ANE2+ IBHO_UNS_TO_UTRAN_ANE3+ IBHO_UNS_TO_UTRAN_ANE4+ IBHO_UNS_TO_UTRAN_ANE5+ IBHO_UNS_TO_UTRAN_ANE6+ IBHO_UNS_TO_UTRAN_ANE7+ IBHO_UNS_TO_UTRAN_ANE8+ IBHO_UNS_TO_UTRAN_ANE9+ IBHO_UNS_TO_UTRAN_ANE10)

100 * ------------------------------------- %sum(IBHO_ATT_TO_UTRAN_ALL

+ IBHO_ATT_TO_UTRAN_DEFAULT_ANE+ IBHO_ATT_TO_UTRAN_ANE1+ IBHO_ATT_TO_UTRAN_ANE2+ IBHO_ATT_TO_UTRAN_ANE3+ IBHO_ATT_TO_UTRAN_ANE4+ IBHO_ATT_TO_UTRAN_ANE5+ IBHO_ATT_TO_UTRAN_ANE6+ IBHO_ATT_TO_UTRAN_ANE7+ IBHO_ATT_TO_UTRAN_ANE8+ IBHO_ATT_TO_UTRAN_ANE9+ IBHO_ATT_TO_UTRAN_ANE10)


Unit: %

Figure 414. IBHO failure ratio to UTRAN ANEs (hfr_79a)

IBHO failure ratio for GSM ANEx (hfr_83)

Use: Share of unsuccessful GSM ANE IBHOs.

sum(IBHO_UNS_TO_GSM_ANEx)100 * ------------------------- %

sum(IBHO_ATT_TO_GSM_ANEx)

Where x = ANE1..10




Unit: %

Figure 415. IBHO failure ratio for GSM ANEx (hfr_83)

IBHO failure ratio for UTRAN ANEx (hfr_84)

Use: Share of unsuccessful UTRAN ANE IBHOs.

sum(IBHO_UNS_TO_UTRAN_ANEx)100 * --------------------------- %

sum(IBHO_ATT_TO_UTRAN_ANEx)

Where x = ANE1..10


Unit: %

Figure 416. IBHO failure ratio for UTRAN ANEx (hfr_84)

IBHO ALL ANE failure ratio to GSM (hfr_85)

Use: Defines the ratio of unsuccessful ALL ANE IBHO attempts toGSM network.

sum(IBHO_UNS_TO_GSM_ALL)100 * ------------------------ %

sum(IBHO_ATT_TO_GSM_ALL)


Unit: %

Figure 417. IBHO ALL ANE failure ratio to GSM (hfr_85)

IBHO ALL ANE failure ratio to UTRAN (hfr_86)

Use: Defines the ratio of unsuccessful ALL ANE IBHO attempts toUTRAN network.

sum(IBHO_UNS_TO_UTRAN_ALL)100 * -------------------------- %

sum(IBHO_ATT_TO_UTRAN_ALL)




Unit: %

Figure 418. IBHO ALL ANE failure ratio to UTRAN (hfr_86)

2.20 Handover success % (hsr)

MSC controlled outgoing SDCCH-SDCCH HO success %, S1 (hsr_1)

sum(msc_o_sdcch)100 * ------------------- %

sum(msc_o_sdcch_at)


Figure 419. MSC controlled outgoing SDCCH-SDCCH HO success %, S1(hsr_1)

MSC controlled outgoing SDCCH-TCH HO success %, S1 (hsr_2)

sum(msc_o_sdcch_tch)100 * ----------------------- %

sum(msc_o_sdcch_tch_at)


Figure 420. MSC controlled outgoing SDCCH-TCH HO success %, S1 (hsr_2)

MSC controlled outgoing TCH-TCH HO success %, S1 (hsr_3)

sum(msc_o_tch_tch)100 * ----------------------- %

sum(msc_o_tch_tch_at)


Figure 421. MSC controlled outgoing TCH-TCH HO success %, S1 (hsr_3)

BSC controlled outgoing SDCCH-SDCCH HO success %, S1 (hsr_4)

sum(bsc_o_sdcch)100 * ------------------- %

sum(bsc_o_sdcch_at)




Figure 422. BSC controlled outgoing SDCCH-SDCCH HO success %, S1(hsr_4)

BSC controlled outgoing SDCCH-TCH HO success %, S1 (hsr_5)

sum(bsc_o_sdcch_tch)100 * ----------------------- %

sum(bsc_o_sdcch_tch_at)


Figure 423. BSC controlled outgoing SDCCH-TCH HO success %, S1 (hsr_5)

BSC controlled outgoing TCH-TCH HO success %, S1 (hsr_6)

sum(bsc_o_tch_tch)100 * --------------------- %

sum(bsc_o_tch_tch_at)


Figure 424. BSC controlled outgoing TCH-TCH HO success %, S1 (hsr_6)

Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_7)

sum(cell_sdcch)100 * ------------------- %

sum(cell_sdcch_at)


Figure 425. Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_7)

Intra-cell SDCCH-TCH HO success %, S1 (hsr_8)

sum(cell_sdcch_tch)100 * --------------------- %

sum(cell_sdcch_tch_at)




Figure 426. Intra-cell SDCCH-TCH HO success %, S1 (hsr_8)

Intra-cell TCH-TCH HO success %, S1 (hsr_9)

sum(cell_tch_tch)100 * --------------------- %

sum(cell_tch_tch_at)


Figure 427. Intra-cell TCH-TCH HO success %, S1 (hsr_9)

MSC controlled incoming SDCCH-SDCCH HO success %, S1 (hsr_10)

sum(msc_i_sdcch)100 * --------------------- %

sum(msc_i_sdcch_at)


Figure 428. MSC controlled incoming SDCCH-SDCCH HO success %, S1(hsr_10)

MSC controlled incoming SDCCH-TCH HO success %, S1 (hsr_11)

sum(msc_i_sdcch_tch)100 * --------------------- %

sum(msc_i_sdcch_tch_at)


Figure 429. MSC controlled incoming SDCCH-TCH HO success %, S1 (hsr_11)

MSC controlled incoming TCH-TCH HO success %, S1 (hsr_12)

sum(msc_i_tch_tch)100 * --------------------- %

sum(msc_i_tch_tch_at)




Figure 430. MSC controlled incoming TCH-TCH HO success %, S1 (hsr_12)

BSC controlled incoming SDCCH-SDCCH HO success %, S1 (hsr_13)

sum(bsc_i_sdcch)100 * --------------------- %

sum(bsc_i_sdcch_at)


Figure 431. BSC controlled incoming SDCCH-SDCCH HO success %, S1(hsr_13)

BSC controlled incoming SDCCH-TCH HO success %, S1 (hsr_14)

sum(bsc_i_sdcch_tch)100 * ----------------------- %

sum(bsc_i_sdcch_tch_at)


Figure 432. BSC controlled incoming SDCCH-TCH HO success %, S1 (hsr_14)

BSC controlled incoming TCH-TCH HO success %, S1 (hsr_15)

sum(bsc_i_tch_tch)100 * --------------------- %

sum(bsc_i_tch_tch_at)


Figure 433. BSC controlled incoming TCH-TCH HO success %, S1 (hsr_15)

BSC controlled incoming HO success %, S1 (hsr_16)

sum(bsc_i_succ_ho)100 * ------------------------------------------------------- %

sum(bsc_i_sdcch_at+bsc_i_sdcch_tch_at+bsc_i_tch_tch_at)




Figure 434. BSC controlled incoming HO success %, S1 (hsr_16)

MSC controlled incoming HO success %, S1 (hsr_17)

sum(msc_i_succ_ho)100 * ------------------------------------------------------- %



Figure 435. MSC controlled incoming HO success %, S1 (hsr_17)

Incoming HO success %, S1 (hsr_18)

sum(msc_i_tch_tch+bsc_i_tch_tch)100 * --------------------------------------- %

sum(msc_i_tch_tch_at +bsc_i_tch_tch_at)


Figure 436. Incoming HO success %, S1 (hsr_18)

Outgoing HO success %, S1 (hsr_19)

sum(msc_o_tch_tch+bsc_o_tch_tch)100 * --------------------------------------- %

sum(msc_o_tch_tch_at +bsc_o_tch_tch_at)


Figure 437. Outgoing HO success %, S1 (hsr_19)

Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_20)

sum(cell_sdcch)100 * ------------------ %

sum(cell_sdcch_at)




Figure 438. Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_20)

Intra-cell SDCCH-TCH HO success %, S1 (hsr_21)

sum(cell_sdcch_tch)100 * --------------------- %

sum(cell_sdcch_tch_at)


Figure 439. Intra-cell SDCCH-TCH HO success %, S1 (hsr_21)

Intra-cell TCH-TCH HO success %, S1 (hsr_22)

sum(cell_tch_tch)100 * --------------------- %

sum(cell_tch_tch_at)


Figure 440. Intra-cell TCH-TCH HO success %, S1 (hsr_22)

2.21 Handover failures (hof)

Outgoing HO failures due to lack of resources (hof_1)

sum(BSC_o_fail_lack+MSC_o_fail_lack)


Figure 441. Outgoing HO failures due to lack of resources (hof_1)

Incoming HO failures due to lack of resources (hof_2)

sum(BSC_i_fail_lack+MSC_i_fail_lack)




Figure 442. Incoming HO failures due to lack of resources (hof_2)

TCH HO failures when return to old channel was successful (hof_3)

Known problems: Due to the mapping of different causes the accuracy may bepoor.

HOs failed in going to new channel - HOs failed to return to old channel

= sum(tch_rf_new_ho + tch_abis_fail_new + tch_a_if_fail_new + tch_tr_fail_new)- sum(tch_rf_old_ho + tch_abis_fail_old + tch_a_if_fail_old + tch_tr_fail_old)


Figure 443. TCH HO failures when return to old channel was successful (hof_3)

SDCCH HO failures when return to old channel was successful (hof_4)

Known problems: Due to the mapping of different causes the accuracy may bepoor.

HOs failed in going to new channel - HOs failed to return to old channel

= sum(sdcch_rf_new_ho+sdcch_abis_fail_new+sdccha_if_fail_new+sdcch_tr_fail_new)-sum(sdcch_rf_old_ho+sdcch_abis_fail_old+sdccha_if_fail_old+sdcch_tr_fail_old)


Figure 444. SDCCH HO failures when return to old channel was successful(hof_4)

MSC incoming HO failures (hof_5)

HO attempts - successful HO

= sum(msc_i_tch_tch_at+msc_i_tch_tch_at+msc_i_sdcch_at- msc_i_tch_tch+msc_i_sdcch_tch+msc_i_sdcch)


Figure 445. MSC incoming HO failures (hof_5)



MSC outgoing HO failures (hof_6)



Figure 446. MSC outgoing HO failures (hof_6)

MSC outgoing HO failures (hof_6a)

sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at)- sum(msc_o_succ_ho)


Figure 447. MSC outgoing HO failures (hof_6a)

BSC incoming HO failures (hof_7)

sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at + bsc_i_sdcch_at)- sum(bsc_i_tch_tch + bsc_i_sdcch_tch + bsc_i_sdcch)


Figure 448. BSC incoming HO failures (hof_7)

BSC incoming HO failures (hof_7a)

sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at + bsc_i_sdcch_at-bsc_i_succ_ho)


Figure 449. BSC incoming HO failures (hof_7a)

BSC outgoing HO failures (hof_8)

sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at)- sum(bsc_o_tch_tch + bsc_o_sdcch_tch + bsc_o_sdcch)




Figure 450. BSC outgoing HO failures (hof_8)

BSC outgoing HO failures (hof_8a)

sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at- bsc_o_succ_ho)


Figure 451. BSC outgoing HO failures (hof_8a)

Intra-cell HO failures (hof_9)

sum(cell_tch_tch_at + cell_sdcch_at - cell_tch_tch + cell_sdcch)


Figure 452. Intra-cell HO failures (hof_9)

Intra-cell HO failures (hof_9a)

sum(cell_tch_tch_at + cell_sdcch_at+ cell_sdcch_tch-cell_tch_tch - cell_sdcch-cell_sdcch_tch)


Figure 453. Intra-cell HO failures (hof_9a)

Intra-cell HO failures (hof_9b)

Segment related problems: Does not work on BTS level if the BTS is part of amultisegment. A reason for this is that an attempt countertriggers for a target BTS only if the handover is successful. Inthe case of a handover failure, the attempt counter triggersonly for the master BTS.

sum(cell_tch_tch_at + cell_sdcch_at+ cell_sdcch_tch_at - cell_tch_tch - cell_sdcch - cell_sdcch_tch)




Unit: number

Figure 454. Intra-cell HO failures (hof_9b)

Failed outgoing HO, return to old (hof_10)

sum(msc_o_fail_ret + bsc_o_fail_ret)


Figure 455. Failed outgoing HO, return to old (hof_10)

Outgoing HO failures (hof_12)

Outgoing HO attempts - Outgoing HO successes

=sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at + msc_o_sdcch_at

+ bsc_o_tch_tch_at + bsc_o_sdcch_tch_at + bsc_o_sdcch_at)- sum(msc_o_succ_ho + bsc_o_succ_ho)


Figure 456. Outgoing HO failures (hof_12)

Intra-cell HO failure, return to old channel (hof_13)

sum(cell_fail_ret)


Figure 457. Intra-cell HO failure, return to old channel (hof_13)

Intra-cell HO failure, drop call (hof_14)

sum(cell_drop_calls)


Figure 458. Intra-cell HO failure, drop call (hof_14)



Incoming HO failures (hof_15)

Incoming HO attempts - Incoming HO successes

=sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at + msc_i_sdcch_at

+ bsc_i_tch_tch_at + bsc_i_sdcch_tch_at + bsc_i_sdcch_at)- sum(msc_i_succ_ho + bsc_i_succ_ho)


Figure 459. Incoming HO failures (hof_15)

2.22 Interference (itf)

UL interference, BTS level, S1 (itf_1)

Use: UL interference is measured as the time-out of the lowestband (band 0 in BSC terminology). Band 0 is defined byboundaries 0 and 1 which are BTS parameters. Boundary 0 isfixed, whereas boundary 1 can be set.

Experiences on use: UL interference alone is not a reliable quality factor if IUOis used. In IUO cells the UL interference can be high but thequality is still good.

Known problems: This formula is on the BTS level, whereas the interferenceproblems are met on the frequency (TRX) level. This meansthat the accuracy is not good if there is more than one TRX ina cell.If band 1 is defined as exceptionally wide, it becomes difficultto see the interference.

sum(ave_idle_f_TCH_1/res_av_denom4)100 x (1- ------------------------------------- ) %

sum(ave_idle_f_TCH_1/res_av_denom4+ ave_idle_f_TCH_2/res_av_denom5+ ave_idle_f_TCH_3/res_av_denom6+ ave_idle_f_TCH_4/res_av_denom7+ ave_idle_f_TCH_5/res_av_denom8)


Figure 460. UL interference, BTS level, S1 (itf_1)

Idle TSL percentage of time in band X, TRX level, IUO, S4 (itf_2)

Experiences on use: In IUO cells the UL interference can show high values butthe UL quality is still excellent. The bigger the values are inbands towards band 5, the worse the interference.



sum(ave_full_tch_ifX)100 x (----------------------- ) %

sum(ave_full_tch_if1+ ave_full_tch_if2+ ave_full_tch_if3+ ave_full_tch_if4+ ave_full_tch_if5)


Figure 461. Idle TSL percentage of time in band X, TRX level, IUO, S4 (itf_2)

UL interference from IUO, TRX level, S4 (itf_3)

Experiences on use: UL interference alone is not a reliable quality factor if IUOis used. In IUO cells the UL interference can be high but thequality is still good.

Known problems: There are more than one TRX in a cell.

sum(ave_full_tch_if1)100 x (1 - ----------------------- ) %

sum(ave_full_tch_if1+ ave_full_tch_if2+ ave_full_tch_if3+ ave_full_tch_if4+ ave_full_tch_if5)


Figure 462. UL interference from IUO, TRX level, S4 (itf_3)

UL interference from Power Control, TRX level, S6 (itf_4)

Use: BTS reports the interference of each TCH as a band number(0-4, where 0 is the lowest and band boundaries are defined ascell parameters). BSC sums up the band numbers(ave_sum_idle_ch_interf) as well as the number ofTCHs reported (ave_sum_idle_tch_per_trx), and fromthese figures an average interference band (0-4) can becalculated. Average interference is shifted by 1 (+1) tocomply with band numbers 1-5.

Experiences on use: Shows null value on the TRX level if the TRX is completelyin the GPRS territory, and on BTS level if all TRXs arecompletely in the GPRS territory, respectively.

sum(ave_sum_idle_ch_interf)--------------------------------sum(ave_sum_idle_tch_per_trx)+1



Counters from table(s):p_nbsc_power

Figure 463. UL interference from Power Control, TRX level, S6 (itf_4)

2.23 Congestion (cngt)

TCH congestion time, S1 (cngt_1)

Experiences on use: Useful to follow on the area level. Should give higher valuesthan SDCCH congestion.

sum(tch_cong_time/100)

Counters from table(s):p_nbsc_res_availunit: second

Figure 464. TCH congestion time, S1 (cngt_1)

SDCCH congestion time, S1 (cngt_2)

Experiences on use: Useful to follow on the area level. Should give smallervalues than TCH congestion.

sum(sdcch_cong_time/100)

Counters from table(s):p_nbsc_res_availunit: second

Figure 465. SDCCH congestion time, S1 (cngt_2)

FTCH time congestion % (cngt_3)

sum(tch_fr_radio_congestion_time)100 * ----------------------------------------- %

sum(period_duration*ave_tch_busy_full/60)


Figure 466. FTCH time congestion % (cngt_3)

FTCH time congestion % (cngt_3a)

sum(tch_fr_radio_congestion_time/100)



100 * ----------------------------------------- %sum(period_duration*ave_tch_busy_full*60)


Figure 467. FTCH time congestion % (cngt_3a)

FTCH time congestion ratio (cngt_3b)

sum(tch_fr_radio_congestion_time/100)100 * ----------------------------------------- %

sum(period_duration)


Unit:%

Figure 468. FTCH time congestion ratio (cngt_3b)

HTCH time congestion % (cngt_4)

sum(tch_hr_radio_congestion_time)100 * ----------------------------------------- %

sum(period_duration*ave_tch_busy_half/60)


Unit:%

Figure 469. HTCH time congestion % (cngt_4)

HTCH time congestion % (cngt_4a)

sum(tch_hr_radio_congestion_time/100)100 * ----------------------------------------- %

sum(period_duration*ave_tch_busy_half*60)


Unit:%

Figure 470. HTCH time congestion % (cngt_4a)

HTCH time congestion ratio (cngt_4b)

sum(tch_hr_radio_congestion_time/100)



100 * ----------------------------------------- %sum(period_duration)


Unit: %

Figure 471. HTCH time congestion ratio (cngt_4b)

2.24 Queuing (que)

Queued, served TCH call requests % (que_1a)

Use: Indicates the quota of TCH call requests seizing the TCHsuccessfully after queuing.

Known problems: tch_qd_call_att is triggered but unsrv_qd_call_attis not if the call is lost for some other reason (e.g. MS userhangs) before the queuing timer expires.The impact of this depends on queuing time and cellparameter Directed Retry Time Limit Min.

sum( tch_qd_call_att - removal_from_que_due_to_dr - unsrv_qd_call_att)100* ---------------------------------------------------------------------- %

sum(tch_call_req)


Figure 472. Queued, served TCH call requests % (que_1a)

Queued, served TCH HO requests % (que_2)

Known problems: tch_qd_ho_att is triggered but unsrv_qd_ho_att is notif a call for some reason is lost (the MS user is hanging, forexample) before the queuing timer expires.

sum(tch_qd_ho_att-unsrv_qd_ho_att)100* ------------------------------------------------- %

sum(tch_request-tch_call_req-tch_fast_req)


Figure 473. Queued, served TCH HO requests % (que_2)



Queued, served TCH HO requests % (que_2a)

Known problems: tch_qd_ho_att is triggered but unsrv_qd_ho_att is notif a call for some reason is lost (the MS user is hanging, forexample) before the queuing timer expires.

sum(a. tch_qd_ho_att-a.unsrv_qd_ho_att)100* ------------------------------------------------- %

sum(a.tch_request-a.tch_call_req-a.tch_fast_req)- Sum(b.bsc_i_unsucc_a_int_circ_type+b.msc_controlled_in_ho



Figure 474. Queued, served TCH HO requests % (que_2a)

Successful queued TCH requests (que_3)

sum(tch_qd_call_att-unsrv_qd_call_att)


Figure 475. Successful queued TCH requests (que_3)

Successful non-queued TCH requests (que_4)

sum(tch_norm_seiz)-sum(tch_qd_call_att-unsrv_qd_call_att)


Figure 476. Successful non-queued TCH requests (que_4)

Successful queued TCH HO requests (que_5)

sum(tch_qd_ho_att-unsrv_qd_ho_att)


Figure 477. Successful queued TCH HO requests (que_5)

Successful non-queued TCH HO requests (que_6)

sum(tch_ho_seiz) -sum(tch_qd_ho_att-unsrv_qd_ho_att)




Figure 478. Successful non-queued TCH HO requests (que_6)

Non-queued, served TCH call requests % (que_7)

Use: Indicates the quota of TCH call requests seizing the TCHsuccessfully straight without queuing. DR is excluded (itsimpact is seen in dr_3).

sum(tch_norm_seiz - (tch_qd_call_att - unsrv_qd_call_att))100 * ---------------------------------------------------------- %

sum(tch_call_req)


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

Non-queued, served TCH HO requests % (que_8)

sum(tch_ho_seiz-(tch_qd_ho_att-unsrv_qd_ho_att))100 * ------------------------------------------------- %



Figure 480. Non-queued, served TCH HO requests % (que_8)

Non-queued, served TCH HO requests % (que_8a)

Known problems: See que_2.

sum(a.tch_ho_seiz-(a.tch_qd_ho_att-a.unsrv_qd_ho_att))100 * -------------------------------------------------------- %

sum(a.tch_request-a.tch_call_req-a.tch_fast_req)- Sum(b.bsc_i_unsucc_a_int_circ_type+b.msc_controlled_in_ho



Figure 481. Non-queued, served TCH HO requests % (que_8a)



2.25 Blocking (blck)

TCH raw blocking, S1 (blck_1)

Experiences on use: Was earlier (before blck_8a) widely used on the cell andthe area level.

Known problems: This PI does not take Directed Retry into consideration.Rather, it shows only raw blocking including also HOs.Blocked HOs are normally not so serious because there arealternatives to go to. Blocked new calls can be lost calls ifDirected Retry is not in use.

sum(tch_req_rej_lack)100 * --------------------- %

sum(tch_request)


Figure 482. TCH raw blocking, S1 (blck_1)

SDCCH blocking %, S1 (blck_5)

Known problems: See csf_1.

100-csf_1 =

sum(SDCCH_busy_att)100 * -------------------- %

sum(SDCCH_seiz_att)


Figure 483. SDCCH blocking %, S1 (blck_5)

SDCCH real blocking %, S1 (blck_5a)

Known problems: See csf_1a.

100_csf_1a =

sum(SDCCH_busy_att - tch_seiz_due_sdcch_con)100 * -------------------------------------------- %

sum(SDCCH_seiz_att)


Figure 484. SDCCH real blocking %, S1 (blck_5a)



TCH raw blocking % on super TRXs, S4 (blck_6)

Use: TCH blocking % on super TRXs.Note: Cannot be calculated by a simple SQL*Plus statement.

sum over super TRXs (tch_req_rej_lack)100 * ----------------------------------------- %

sum over super TRXs (tch_request)


Figure 485. TCH raw blocking % on super TRXs, S4 (blck_6)

TCH raw blocking % on regular TRXs, S4 (blck_7)

Use: TCH Blocking % on regular layer.Note: Cannot be calculated by a simple SQL*Plus statement.

sum over regular TRX (tch_req_rej_lack)100 * ----------------------------------------- %

sum over regular TRX (tch_request)


Figure 486. TCH raw blocking % on regular TRXs, S4 (blck_7)

TCH call blocking, before DR, S2 (blck_8)

Experiences on use: Shows the blocking if DR is not used.

TCH call req. rejected due to lack of res. or routed by DR to another cell100* ------------------------------------------------------------------------ % =

all TCH call requests

sum(tch_call_req-tch_norm_seiz)100* -------------------------------- %

sum(tch_call_req)


Figure 487. TCH call blocking, before DR, S2 (blck_8)

TCH call blocking %, DR compensated, S2 (blck_8b)

Use: On the cell level should appear in the busiest cells. The cellneeds an urgent capacity extension or has lost part of capacitydue to a fault.It is the blocking rate that the customer will notice when theyare driving in the mobile environment caused by the lack ofradio resources. It is therefore one of the most critical KPIs.



Experiences on use: On the area level there is not yet a target value to give(except that 0% is the best). On the cell level, for example, 2%blocking on Busy Hour has been used as a criterion for design.

Known problems: 1) This blocking also shows situations when it is caused by afault in the BTS - not only pure blocking caused by hightraffic.2) NOTE: If Trunk Reservation is used, HO and Call blockingcannot be counted precisely (there is only one counter for thecase of Trunk Reservation Invocation Refused).3) The ratio can show too high values in the following case:TCH assignment fails if the requested channel type is notfound in the A-interface circuit pool. In this casetch_norm_seiz is not triggered but tch_call_req is, i.e.this attempt in blck_8b is considered a blocked call.Anyhow, BSC requests the MSC to change the A-if circuitpool. MSC can then decide if there is another assignmentrequest or call clear (clear_command).The second request may again fail or succeed. In BSC theTCH_REJ_DUE_REQ_CH_A_IF_CRC counter is triggeredevery time the channel request fails due to the above-mentioned reason.If Nokia MSC is used, there can only be one retry. Withanother vendor’s MSC there can be multiple retrys.The actual situation when this can be met is if EFR (enhancedfull rate) codec is the primary choice but- the selected A-if circuit supports only Full Rate- there are free circuits supporting EFR in the A interface.

TCH call requests rejected due to lack of res. or saved by DR- successful DR

100* ------------------------------------------------------------------------- % =all TCH call requests

sum(a.tch_call_req-a.tch_norm_seiz)- sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch+b.cell_sdcch_tch)

100* ---------------------------------------------------------- %sum(a.tch_call_req)


Figure 488. TCH call blocking %, DR compensated, S2 (blck_8b)

TCH call blocking %, DR and DAC compensated, EFR excluded, S5(blck_8d)

Use: Applicable on area or BTS level.Queuing and Directed Retry are the BSS features that canreduce blocking.



It is the failed call attempts that the MS user will notice,caused by the lack of radio resources. It is therefore one of themost critical KPIs.On the cell level may appear in the busiest cells. The cellneeds an urgent capacity extension or has lost part of capacitydue to a fault. An MS user will usually hear three beep toneswhen the call is rejected due to blocking.

Experiences on use: On the area level there is not yet a target value to give(except that the trend should be towards a smaller value, 0%being the best). On the cell level, for example, 2% blockingon Busy Hour has been used as a criterion for design. ThisKPI can be followed statistically, for example, as the numberof cells in which the value exceeds the given threshold.

Known problems: 1) Note that if Trunk Reservation is used, HO and Callblocking cannot be counted precisely, i.e. there is only onecounter for the case of Trunk Reservation Invocation Refused.2) If dadlb_start_due_exceeded_load is triggered andthe DADLB handover fails, the counter tch_call_req willbe triggered twice. This problem will be corrected in S10.3) The formula counts also the following case of a blockedcall: a call is cleared from the other end between call requestand TCH seizure. Note that queuing prolongs this time andthus the probability of a call to be cleared.

100 - csf_3l =

sum(a.tch_call_req - a.tch_norm_seiz)- sum(b.msc_o_sdcch_tch + b.bsc_o_sdcch_tch + b.cell_sdcch_tch); DR calls+ sum(a.tch_succ_seiz_for_dir_acc) ;ref.2- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion

-(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool handover failures+ b.msc_controlled_in_ho+ b.ho_unsucc_a_int_circ_type))

100 * -------------------------------------------------------------------------- %sum(a.tch_call_req)

- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion-(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool handover failures+ b.msc_controlled_in_ho+ b.ho_unsucc_a_int_circ_type))


Figure 489. TCH call blocking %, DR and DAC compensated, EFR excluded, S5(blck_8d)

Ref.2. Compensation needed since in case of Direct Access to super reuse TRXthe tch_norm_seiz is triggered in parallel with cell_sdcch_tch.



TCH call blocking %, DR compensated, EFR excluded S11.5 (blck_8f)

Use: Applicable on area level (and BTS level only if BTS is notpart of a multi-BTS segment). When DADL/B is in use, callsetup is a little slower and it is usually observed that asubscriber might disconnect the call in those cases (while thecall is in Phase 3, call setup). In BSS S11, SPARE001149 iscounting such instances and those are considered normal andreduced from the numerator so that it is not consideredblocked. For more background information, see blck_8e.

Segment related problems: Does not work on BTS level if a segment of severalBTSs is used.

100 - csf_3o =

sum(a.tch_call_req- a.tch_norm_seiz- a.SPARE001149)

- sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch+ b.cell_sdcch_tch) ; DR calls

+ sum(a.tch_succ_seiz_for_dir_acc) ; ref.2- sum(a.SPARE001191 ; ref.3

100 * -------------------------------------------------------------------------- %sum(a.tch_call_req)

- sum(a.SPARE001191) ; Aif type mismatch or congestion


Ref.2. Compensation needed since in the case of Direct Access to super reuse TRXthe tch_norm_seiz is triggered in parallel with the cell_sdcch_tch.Ref.3. Aif type mismatch or congestion)

Unit: %

Figure 490. TCH call blocking %, DR compensated, EFR excluded S11.5(blck_8f)

TCH call blocking %, S11.5 (blck_8g)

Use: Applicable on area level (and BTS level only if BTS is notpart of multi BTS segment). When DADL/B is in use, callsetup is little slower (takes longer) and it is usually observedthat subscriber might disconnect the call in those cases (whilecall is in Phase 3, call setup). For more backgroundinformation, see blck_8e and blck_8f.

Known problems: Does not work on BTS level if BTS is part of SEG withseveral BTSs.

100 - csf_3p =

sum(a.tch_call_req- a.tch_norm_seiz- a.calls_ended_user_dadlb_setup)

- sum(b.msc_o_sdcch_tch



+ b.bsc_o_sdcch_tch+ b.cell_sdcch_tch) ; DR calls

+ sum(a.tch_succ_seiz_for_dir_acc) ; ref.2- sum(a.a_if_crc_mismatch_call_setup; ref.3

100 * -------------------------------------------------------------------------- %sum(a.tch_call_req)

- sum(a.a_if_crc_mismatch_call_setup) ; Aif type mismatch or congestion


Ref.2. Compensation needed since in the case of Direct Access to super reuse TRXthe tch_norm_seiz is triggered in parallel with the cell_sdcch_tch.Ref.3. Aif type mismatch or congestion

Unit: %

Figure 491. TCH call blocking %, S11.5 (blck_8g)

TCH call blocking, DR compensated, EFR excluded (blck_8h)

Use: Applicable on BTS level even the BTS is part of multi-BTSsegment. When DADL/B is in use, call setup is a little slower(takes longer) and it is usually observed that a subscribermight disconnect the call in those cases (while the call is inPhase 3, call setup).

Note: This version is usable only in S11 with the CDxx. For S11.5,use blck_8i.

sum(spare001192- spare001193)

100 * ---------------- %sum(spare001192)


Figure 492. TCH call blocking, DR compensated, EFR excluded (blck_8h)

Blocked calls, S5 (blck_9b)

Use: Shows also situations when blocking is caused by a fault inthe BTS - not only blocking caused purely by high traffic.

TCH call req. rejected due to lack of res. or routed by DR to another cell- successful DR- Rejections due to Aif circuit mismatch

sum(a.tch_call_req-a.tch_norm_seiz)- sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch);inter-cell DR- sum(b.cell_sdcch_tch); intra-cell DR in IUO- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion

-(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool handover failures+b.msc_controlled_in_ho+b.ho_unsucc_a_int_circ_type))




Figure 493. Blocked calls, S5 (blck_9b)

Blocked calls, S5 (blck_9c)



sum(a.tch_call_req-a.tch_norm_seiz)- sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch);inter-cell DR- sum(b.cell_sdcch_tch); intra-cell DR in IUO+ sum(a.succ_tch_seiz_for_dir_acc) ;ref.2- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion

-(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool handover failures+b.msc_controlled_in_ho+b.ho_unsucc_a_int_circ_type))



Figure 494. Blocked calls, S5 (blck_9c)

Blocked calls, S11.5 (blck_9d)



sum(a.tch_call_req- a.tch_norm_seiz- a.calls_ended_user_dadlb_setup)

- sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch+ b.cell_sdcch_tch) ; DR calls

+ sum(a.tch_succ_seiz_for_dir_acc) ; ref.2- sum(a.a_if_crc_mismatch_call_setup;


Unit: number



Ref.2. Compensation needed since in the case of Direct Access to super reuse TRXthe tch_norm_seiz is triggered in parallel with cell_sdcch_tch.

Figure 495. Blocked calls, S11.5 (blck_9d)

Blocked TCH HOs, S2 (blck_10a)

Use: Replaces blck_10.

sum(tch_request-tch_call_req - tch_fast_req-tch_ho_seiz)


Figure 496. Blocked TCH HOs, S2 (blck_10a)

Blocked TCH HOs, S5 (blck_10b)

Use: Replaces blck_10a.

sum(a.tch_request - a.tch_call_req - a.tch_fast_req - a.tch_ho_seiz)-sum(b.bsc_i_unsucc_a_int_circ_type + b.msc_controlled_in_ho

+ b.ho_unsucc_a_int_circ_type)


Figure 497. Blocked TCH HOs, S5 (blck_10b)

TCH HO blocking, S2 (blck_11a)

Known problems: 1) Shows also the situations when blocking is caused by afault in the BTS - not only blocking caused purely by hightraffic.2) Note that if Trunk Reservation is used, HO and Callblocking cannot be counted precisely (there is only onecounter for the case of Trunk Reservation InvocationRefused).

sum(tch_request-tch_call_req-tch_fast_req-tch_ho_seiz)100 * ------------------------------------------------------- %



Figure 498. TCH HO blocking, S2 (blck_11a)



TCH HO blocking without Q, S2 (blck_11b)

Use: Shows TCH HO blocking if queuing was not in use.Known problems: See que_2 (factor XX1).

sum(tch_request - tch_call_req - tch_fast_req - tch_ho_seiz)+ sum(tch_qd_ho_att - XX1-unserv_qd_ho_att)

100 * ------------------------------------------------------------- %sum(tch_request - tch_call_req - tch_fast_req)


Figure 499. TCH HO blocking without Q, S2 (blck_11b)

TCH HO blocking, S5 (blck_11c)

Known problems: 1) Shows also the situations when blocking is caused by afault in the BTS - not only blocking caused purely by hightraffic.2) Note that if Trunk Reservation is used, HO and Callblocking cannot be counted precisely (there is only onecounter for the case of Trunk Reservation InvocationRefused).

sum(a.tch_request-a.tch_call_req-a.tch_fast_req-a.tch_ho_seiz)-sum(b.bsc_i_unsucc_a_int_circ_type+b.msc_controlled_in_ho

+b.ho_unsucc_a_int_circ_type)100 * -------------------------------------------------------------- %

sum(a.tch_request-a.tch_call_req-a.tch_fast_req)-sum(b.bsc_i_unsucc_a_int_circ_type+b.msc_controlled_in_ho



Figure 500. TCH HO blocking, S5 (blck_11c)

Blocked incoming and internal HO, S2 (blck_12)

Use: Usable with S4 and earlier.

sum(msc_i_fail_lack + bsc_i_fail_lack + cell_fail_lack)


Figure 501. Blocked incoming and internal HO, S2 (blck_12)

Blocked incoming and internal HO, S2 (blck_12a)

Use: Used on the area level with S5 and S6.



sum(msc_i_fail_lack + bsc_i_fail_lack + cell_fail_lack+ bsc_i_unsucc_a_int_circ_type+ msc_controlled_in_ho+ ho_unsucc_a_int_circ_type)


Figure 502. Blocked incoming and internal HO, S2 (blck_12a)

AG blocking, S1 (blck_13)

Use: A BSC sends to a BTS an immediate assignment orimmediate assignment rejected commands. If the AccessGrant (AG) buffer in the BTS is full, it will respond with adelete indication. Thus, the ratio of delete indications to thesum of immediate assignment and immediate assignmentrejected describes the AG blocking. After receiving the deleteindication message the BSC releases the SDCCH.

100 * sum(del_ind_msg_rec)/ sum(imm_assgn_rej+imm_assgn_sent)


Figure 503. AG blocking, S1 (blck_13)

FCS blocking, S5 (blck_14)

sum(tch_seiz_att_due_sdcch_con - tch_seiz_due_sdcch_con)100 * --------------------------------------------------- %

sum(tch_seiz_att_due_sdcch_con %)


Figure 504. FCS blocking, S5 (blck_14)

Blocked SDCCH seizure attempts, S5 (blck_15)

All blocked - seizures to FACCH setup sum(sdcch_busy_att- tch_seiz_due_sdcch_con)


Figure 505. Blocked SDCCH seizure attempts, S5 (blck_15)



HO blocking % (blck_16a)

Use: Used on the area level with S4 or earlier.


100 * --------------------------------------------------------/* all HO attempts */sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at



Figure 506. HO blocking % (blck_16a)

Handover blocking % (blck_16b)

Use: Used on the area level with S5 and S6.Known problems: If the required channel type (e.g. Full Rate) is not available in

intra-cell handover, then ho_unsucc_a_int_circ_type istriggered, but the same channel may be seized successfullyafter changing the handover for external (A interface circuitchanges).

/* handovers failing due to blocking */sum(msc_i_fail_lack+bsc_i_fail_lack + cell_fail_lack+

+bsc_i_unsucc_a_int_circ_type+msc_i_unsucc_a_int_circ_type+ho_unsucc_a_int_circ_type)

100 * -------------------------------------------------------------- %/* all HO attempts */sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at



Figure 507. Handover blocking % (blck_16b)

Abis link blocking (blck_17)

There is no counter but an alarm: 2720 ’Telecom Link Overload’.

Blocked FACCH call setup TCH requests (blck_18)

sum(tch_seiz_att_due_sdcch_con - tch_seiz_due_sdcch_con)


Figure 508. Blocked FACCH call setup TCH requests (blck_18)



Handover blocking to target cell (blck_19)

sum(ho_fail_res_to_adj)100 * ---------------------- %

sum(ho_att_to_adj)


Figure 509. Handover blocking to target cell (blck_19)

Handover blocking from target cell (blck_20)

sum(ho_fail_res_from_adj)100 * ------------------------- %

sum(ho_att_from_adj)


Figure 510. Handover blocking from target cell (blck_20)

NACK ratio of p-immediate assignment, S9PS (blck_21)

Use: A negative acknowledgement (NACK) is sent from BTS toBSC after all AGCH messages that are deleted from TRXbuffers due to:- buffer overflow- maximum lead-time expiry- expired starting timeThe AGCH messages are ordered by BSC to beacknowledged. The negative acknowledgement is sentimmediately after the message has been deleted.

sum(packet_immed_ass_nack_msg)100 * ---------------------------------------------------- %

sum(packet_immed_ass_msg + packet_immed_ass_rej_msg)


Figure 511. NACK ratio of p-immediate assignment, S9PS (blck_21)

NACK ratio of p-immediate assignment requests (blck_21b)

Use: A negative acknowledgement (NACK) is sent from BTS toBSC after all AGCH messages which are deleted from TRXbuffers due to- buffer overflow



- maximum lead-time expiry- expired starting timeand which are ordered by BSC to be acknowledged. Thenegative acknowledgement is sent immediately after themessage has been deleted.

sum(packet_immed_ass_nack_msg)100 * --------------------------------------------------------- %

sum(packet_immed_ass_ack_msg + packet_immed_ass_nack_msg)


Figure 512. NACK ratio of p-immediate assignment requests (blck_21b)

Territory upgrade rejection %, S9PS (blck_22)

Use: Indicates the lack of resources to upgrade the GPRS territory.

sum(gprs_ter_ug_rej_due_csw_tr+gprs_ter_ug_rej_due_lack_psw+gprs_ter_ug_rej_due_lack_pcu)

100 * --------------------------------- %sum(gprs_ter_upgrd_req)


Figure 513. Territory upgrade rejection %, S9PS (blck_22)

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

sum(ho_fail_due_res_wcdma_ran)100 * ------------------------------

sum(ho_att_wcdma_ran_cell)


Unit: %

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

Handover blocking from target WCDMA cell, S10.5 (blck_28)

sum(ho_fail_due_res_wcdma_ran_cell)100 * -----------------------------------

sum(ho_att_from_wcdma_ran)




Unit: %

Figure 515. Handover blocking from target WCDMA cell, S10.5 (blck_28)

TCH denied for Call request, Ratio, S10 (blck_29)

Use: To indicate end user experience of TCH denied for new calls.Failures during call setup are not considered.

Description: Attempts that fail to get TCH after the call setup phase.Sum (a.tch_call_req + a.tch_fast_req)

- Sum (c.tch_re_est_assign + c.tch_new_call_assign)- Sum (a.tch_rej_due_req_ch_a_if_crc; Aif type mismatch or congestion

-(b.bsc_i_unsucc_a_int_circ_type; Aif circuit pool handover failures+ b.msc_controlled_in_ho+ b.ho_unsucc_a_int_circ_type))

100* ----------------------------------------------------------------------- %Sum (a.tch_call_req + a.tch_fast_req)

- Sum (a.tch_rej_due_req_ch_a_if_crc; Aif type mismatch or congestion-(b.bsc_i_unsucc_a_int_circ_type; Aif circuit pool handover failures+ b.msc_controlled_in_ho+ b.ho_unsucc_a_int_circ_type))

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_hoc = p_nbsc_service

Unit: %

Figure 516. TCH denied for Call request, Ratio, S10 (blck_29)

2.26 Traffic (trf)

TCH traffic sum, S1 (trf_1)

Experiences on use: If counted over one hour, erlang is shown. Counting erlangsover a longer period requires that the erlang values per hourare first counted and then averaged.



Note

Known problems: 1) Shows slightly different values (around 3 % higheraccording to one study) than if counted from an MSC. Thereason for this is that in a BSC one call holds two TCHs for ashort period in HOs.2) The sampling period is 20 s, which means that during theperiod of one hour the number of used TCHs are checked 180times. This method is not accurate if we think about shortseizures and low traffic, but statistically the results have beensatisfactory.3) Does not show calls going to voice mail.

The result represents technical traffic, not charged traffic because counting isstarted when BSC seizes TCH. Includes some of signalling, ringing and speech.

sum(ave_busy_tch)-------------------sum(res_av_denom14)

Counters from table(s):p_nbsc_res_availUnit: Erlang hours if the measurement period is 1 hour.

Figure 517. TCH traffic sum, S1 (trf_1)

TCH traffic sum, S1 (trf_1a)

Note: See trf_1.

sum_over_area(sum_over_BTS(ave_busy_tch)/ sum_over_BTS(res_av_denom14)

)


Figure 518. TCH traffic sum, S1 (trf_1a)

TCH traffic sum of normal TRXs, S1 (trf_1b)

Use: On BTS and area level.Known problems: See trf_1.Note: See trf_1.

sum(decode(trx_type,0,ave_busy_tch) / decode(trx_type,0,res_av_denom14))




p_nbsc_res_availUnit: Erlang hours if measurement period is 1 hour.

Figure 519. TCH traffic sum of normal TRXs, S1 (trf_1b)

TCH traffic sum of extended TRXs, S1 (trf_1c)

Use: On BTS and area level.Known problems: See trf_1.Note: See trf_1.

sum(decode(trx_type,1,ave_busy_tch) / decode(trx_type,1,res_av_denom14))

Counters from table(s):p_nbsc_res_availUnit: Erlang hours if measurement period is 1 hour.

Figure 520. TCH traffic sum of extended TRXs, S1 (trf_1c)

Average call length, S1 (trf_2b)

Use: When used on the area level this PI gives an idea about thebehaviour of the MS users.

Note: In the numerator (a.ave_busy_tch / a.res_av_denom14)represents technical traffic, not charged traffic becausecounting is started when BSC seizes TCH. Includes somesignalling, ringing and speech. The denominator includes alsounanswered calls.

total TCH use time nbr of seconds in meas.period * average busy TCH------------------- = -------------------------------------------------number of calls number of calls

sum(period_duration*60* a.ave_busy_tch / a.res_av_denom14)= -------------------------------------------------------------------------

sum(b.tch_norm_seiz) ;normal calls+ sum(c.msc_o_sdcch_tch+ c.bsc_o_sdcch_tch + c.cell_sdcch_tch) ;DR calls+ sum(b.tch_seiz_due_sdcch_con) ; FACCH call setup calls

Counters from table(s):a = p_nbsc_res_availb = p_bsc_trafficc = p_nbsc_ho

Figure 521. Average call length, S1 (trf_2b)

Average call length, S1 (trf_2d)

Use: On the area level gives you an idea about the behaviour of theMS users.



Note: In the numerator ( a.ave_busy_tch /a.res_av_denom14) represents technical traffic, notcharged traffic, because counting is started when BSC seizesTCH. Includes some of signalling, ringing and speech.In the denominator there are also calls that are not answered.The numerator counts both the A and B side in MS-MS calls,thus duplicating call time.

total TCH use time nbr of seconds in meas.period * average busy TCH------------------- = -------------------------------------------------

number of calls number of calls

sum(period_duration*60* a.ave_busy_tch / a.res_av_denom14)= ----------------------------------------------------------

sum(b.tch_norm_seiz) ;normal calls+ sum(msc_i_sdcch_tch+ bsc_i_sdcch_tch + cell_sdcch_tch); DR calls+ sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls

Counters from table(s):a = p_nbsc_res_availb = p_bsc_trafficc = p_nbsc_ho

Figure 522. Average call length, S1 (trf_2d)

CS territory usage, S1 (trf_3)

Use: On the area level gives you an idea of how well the capacityis used. Usable after S4 if half rate is not used. The formuladoes not comprise to the GPRS timeslots (PDTCH).

Known problems: When GPRS is used, the CS territory size (denominator) canchange according to the traffic needs and therefore theindicator is not consistent.

used TCH100 * ----------------------- %

available TCH

sum(ave_busy_tch/res_av_denom14)= 100 * -------------------------------------------- %

sum(ave_avail_full_TCH/res_av_denom2)


Figure 523. CS territory usage, S1 (trf_3)

FTCH usage, S5 (trf_3b)

Use: On the area level gives you an idea of how well the capacityis used. Use with S5 or later.

Known problems: When GPRS is used, the CS territory size (denominator) canchange according to the traffic needs and therefore theindicator is not consistent.



sum(ave_tch_busy_full)= 100 * -------------------------------------------- %

sum(ave_avail_full_TCH/res_av_denom2)


Figure 524. FTCH usage, S5 (trf_3b)

Average SDCCH holding time, S1 (trf_4)

Note: For area (or segment) level, first use the formula for all theBTSs and then sum this formula over all underlying BTSs,keeping in mind the note above.

Use: The holding time may change due to modification of thetimers or perhaps software. This time is part of the call setuptime.

Experiences on use: The counters receive the value of zero if the BTS is locked.Typically the values range from 2 to 3 seconds but over 4seconds with satellite Abis.

sum(ave_sdcch_hold_tim)------------------------ secsum(res_av_denom16)*100


Figure 525. Average SDCCH holding time, S1 (trf_4)

Average FTCH holding time, S1 (trf_5)

Use: The holding time may change due to modification of thetimers or perhaps software. You can use this PI to follow theimpact of the modifications.

Experiences on use: The counters receive the value of zero if the BTS is locked.The value is highly dependent on the number of handoversthat, again, are dependent on the network plan.

sum(ave_ftch_hold_tim)------------------------ secsum(res_av_denom17)*100


Figure 526. Average FTCH holding time, S1 (trf_5)



TCH seizures for new call (call bids), S1 (trf_6)

Use: The seizures of TCH for a new call (i.e. not HO, not DR, notFCS).

sum(p_nbsc_traffic.tch_norm_seiz)


Figure 527. TCH seizures for new call (call bids), S1 (trf_6)

SDCCH usage %, S1 (trf_7b)

Experiences on use: Dynamic SDCCH allocation can add SDCCH capacitydynamically and therefore make the counting of SDCCHusage % obsolete.

total SDCCH hold time in seconds100 * --------------------------------------------------- %

average total nbr of SDCCH * period duration in seconds

sum(SDCCH_SEIZURES)*avg(a.ave_sdcch_hold_tim/a.res_av_denom16/100)= 100 * ----------------------------------------------------- %

sum((a.ave_sdcch_sub/a.res_av_denom3 + a.ave_non_avail_sdcch)* a.period duration*60)

where SDCCH_SEIZURES = (b.sdcch_assign+b.sdcch_ho_seiz+b.tch_seiz_due_sdcch_con)

Counters from table(s):a = p_nbsc_res_availb = p_nbsc_traffic

Figure 528. SDCCH usage %, S1 (trf_7b)

SDCCH usage %, S1 (trf_7c)

Known problems: SDCCH seizures are very short to be counted using 20 ssampling time.

sum(period_duration*ave_busy_sdcch/res_av_denom15)100 * ------------------------------------------------------------------------ %

sum((ave_sdcch_sub/res_av_denom3+ave_non_avail_sdcch)*period_duration)

Figure 529. SDCCH usage %, S1 (trf_7c)

TCH traffic absorption on super, S4 (trf_8)

Note: Cannot be calculated by a simple SQL*Plus statement.



1. First, count the traffic per a TRX.

avg(ave_busy_tch)

2. Then, label the TRXs to super or regular (TRX is a super TRX if HOrelated counters for this TRX show the value of zero). Sum up the trafficfor super TRXs and for all TRXs and calculate their ratio.

traffic (super)100 x --------------- %

traffic (all)


Figure 530. TCH traffic absorption on super, S4 (trf_8)

TCH traffic absorption on super, S4 (trf_8a)

Use: IUONote: Cannot be calculated by a simple SQL*Plus statement.

sum over BTS (avg per each super TRX (ave_busy_tch))100 x ---------------------------------------------------- %

sum over BTS (avg per each TRX (ave_busy_tch))


Figure 531. TCH traffic absorption on super, S4 (trf_8a)

Average cell TCH traffic from IUO, S4 (trf_9)


1. First, count the traffic per a TRX and per hour:

avg(ave_busy_tch)

2. Then, sum up the traffic over the period and divide it by the number ofhours in the period.

sum traffic of all TRXs100 x ------------------------ %

hours


Figure 532. Average cell TCH traffic from IUO, S4 (trf_9)



Cell TCH traffic from IUO, S4 (trf_9a)


sum over BTS (avg per each TRX (ave_busy_tch))


Figure 533. Cell TCH traffic from IUO, S4 (trf_9a)

Super TRX TCH traffic, S4 (trf_10)


1. First, count the traffic per a TRX and per hour:

avg(ave_busy_tch)

2. Then, sum it up over the periodfor super TRXs and divide it by the number of hours in the period:

traffic (super)100 x --------------- 100%

hours


Figure 534. Super TRX TCH traffic, S4 (trf_10)

Sum of super TRX TCH traffic, S4 (trf_10a)


sum over BTS (avg per each super TRX (ave_busy_tch))


Figure 535. Sum of super TRX TCH traffic, S4 (trf_10a)

Average SDCCH traffic, erlang, S2 (trf_11)

Known problems: SDCCH seizures are too short to be counted by using 20 ssampling time.

sum of traffic sum(ave_busy_sdcch / res_av_denom15)--------------- = --------------------------------------nbr of records count(*)




Figure 536. Average SDCCH traffic, erlang, S2 (trf_11)

Average SDCCH traffic, erlang, S2 (trf_11b)

Known problems: SDCCH seizures are too short to be counted by using 20 ssampling if traffic is low (less than 0.5 Erl).

Note: On BTS level. For area (or segment) level, first use theformula for all the BTSs and then sum this formula over allunderlying BTSs.

sum(ave_busy_sdcch) / sum(res_av_denom15)


Figure 537. Average SDCCH traffic, erlang, S2 (trf_11b)

Average TCH traffic, erlang, S2 (trf_12)

sum of traffic sum(ave_busy_tch / res_av_denom14)--------------- = --------------------------------------nbr of records count(*)


Figure 538. Average TCH traffic, erlang, S2 (trf_12)

Average TCH traffic, erlang, S2 (trf_12a)

Note: Gives the same results as trf_12. On BTS level. For area (orsegment) level, first use the formula for all the BTSs and thensum this formula over all underlying BTSs.

avg(ave_busy_tch / res_av_denom14)


Unit: Erlang

Figure 539. Average TCH traffic, erlang, S2 (trf_12a)



Average CS traffic, erlang, S2 (trf_12b)

Use: This is a speech (circuit switched) traffic indicator. Speechtraffic is a basic indicator needed to see how much TCHcapacity is consumed. When the traffic increases without theincrease of the capacity, the probability of blocking increases.The relationship between traffic, capacity and blocking isdescribed for speech traffic in the formula known as Erlang B.This KPI includes all types of CS traffic (single TCH,HSCSD).

Known problems: If extended cells are used, the value is correct only when usedon BTS/trx_type level.

sum(ave_busy_tch) / sum(res_av_denom14)


Unit: erlang

Figure 540. Average CS traffic, erlang, S2 (trf_12b)

Average CS traffic per BTS (trf_12d)

Use: This is a speech (circuit switched) traffic indicator. Speechtraffic is a basic indicator needed to see how much TCHcapacity is consumed. When the traffic increases without theincrease of capacity, the probability of blocking increases.The relationship between traffic, capacity and blocking isdescribed for speech traffic in the formula known as Erlang B.This KPI includes all types of CS traffic (single TCH,HSCSD).

trf_97a ; CS traffic on normal TRXs+ trf_98a ; CS traffic on extended TRXs

Figure 541. Average CS traffic per BTS (trf_12d)

Handover/call % (trf_13b)

Use: Indicates how stationary or mobile the traffic is. The biggerthe number, the more mobile is the traffic. Using this KPI,cells with stationary traffic can be found. This is largelydependent on how much the coverage areas overlap.

Known problems: Includes also intra-cell handovers that are not so directlyrelated to mobility.

sum(a.tch_ho_seiz)100 * ------------------------------------------------------------------ %

sum(a.tch_norm_seiz) ;(normal calls)+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch) ;(DR inter-cell calls)



+ sum(c.cell_sdcch_tch) ;(DR intra-cell calls in IOU, optional feature for S6)+ sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup


Figure 542. Handover/call % (trf_13b)

Intra-cell handover/call % (trf_13c)

Use: Usually illustrates the impact of interference in a non-IUOnetwork.

Known problems: See trf_13b.

sum(c.cell_tch_tch)100 * ------------------------------------------------------------------ %

sum(a.tch_norm_seiz) ;(normal calls)+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch) ;(DR inter-cell calls)+ sum(c.cell_sdcch_tch) ;(DR intra-cell calls in IOU, optional feature for S6)+ sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup


Figure 543. Intra-cell handover/call % (trf_13c)

HO / call % (trf_13d)

Use: Indicates how stationary or mobile the traffic is. The biggerthe number, the more mobile is the traffic. By using this KPIcells with stationary traffic can be found. This is largelydependent on how much the coverage areas overlap. It isusable for non-IUO network.The use of this KPI depends on factors like cell size and calllength.

Known problems: Includes also intra-cell HOs that are not so directly related tomobility.

sum(a.tch_ho_seiz)- sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch) ;(DR inter-cell calls)- sum(c.cell_sdcch_tch) ;(DR intra-cell calls in IOU, optional feature for S6)

100 * ------------------------------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)

+ sum(c.msc_i_sdcch_tch +c.bsc_i_sdcch_tch) ;(DR inter-cell calls)+ sum(c.cell_sdcch_tch) ;(DR intra-cell calls in IOU, optional feature for S6)+ sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup


Figure 544. HO / call % (trf_13d)



Handover/ call % (trf_13e)

Use: Indicates how stationary or mobile the traffic is: the bigger thenumber, the more mobile is the traffic. Using this KPI, cellswith stationary traffic can be found.This is largely dependent on how much the coverage areasoverlap.Usable for a non-IUO network.Intra-cell HOs are not included as they are not directly relatedto mobility.

sum(a.tch_ho_seiz)- sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch) ;(DR inter-cell calls)- sum(c.cell_sdcch_tch) ;(DR intra-cell calls in IOU, optional feature for S6)- sum(c.cell_tch_tch) ;(Intra cell HOs)

100 * ------------------------------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)

+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch) ;(DR inter-cell calls)+ sum(c.cell_sdcch_tch) ;(DR intra-cell calls in IOU, optional feature for S6)+ sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup


Figure 545. Handover/call % (trf_13e)

IUO, average TCH seizure length on super TRXs, S4 (trf_14b)

call time/tch seizures = average period duration * average traffic / tch seizures

avg of BTS (avg of TRX (period_duration))*60 ! Avg.call time in seconds*sum of BTS (sum of super TRX(ave_busy_tch))

= ------------------------------------------------------ secsum of BTS( sum of super TRX(tch_succ_seiz))


Figure 546. IUO, average TCH seizure length on super TRXs, S4 (trf_14b)

IUO, average TCH seizure length on regular TRXs, S4 (trf_15b)

call time/tch seizures = average period duration * average traffic / tch seizures

avg of BTS (avg of TRX (period_duration))*60*sum of BTS (sum of regular TRX(avg_trx_traf))

= ------------------------------------------------------ secsum of BTS( sum of regular TRX(tch_succ_seiz))




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

Average TRX traffic, IUO, S4 (trf_16)

avg(ave_busy_tch)


Figure 548. Average TRX traffic, IUO, S4 (trf_16)

Average TRX TCH seizure length, IUO, S4 (trf_17)

count(*) avg(ave_busy_tch)*3600-------------------------------

sum(tch_succ_seiz)


Figure 549. Average TRX TCH seizure length, IUO, S4 (trf_17)

Average TRX TCH seizure length, IUO, S4 (trf_17a)

count(*) avg(ave_busy_tch)* period_duration*60-----------------------------------------------

sum(tch_succ_seiz)


Figure 550. Average TRX TCH seizure length, IUO, S4 (trf_17a)

Average TRX TCH seizure length, IUO, S4 (trf_17b)

sum(ave_busy_tch* period_duration*60)-----------------------------------------------

sum(tch_succ_seiz)

Counters from table(s):p_nbsc_underlayUnit: second

Figure 551. Average TRX TCH seizure length, IUO, S4 (trf_17b)



TCH requests for a new call, S3 (trf_18)

Known problems: A interface pool circuit type mismatch related retries areincluded.

sum(tch_call_req)


Figure 552. TCH requests for a new call, S3 (trf_18)

TCH requests for a new call, S3 (trf_18a)

sum(a.tch_call_req)- sum(a.tch_rej_due_req_ch_a_if_crc)- (b.bsc_i_unsucc_a_int_circ_type+b.msc_controlled_in_ho



Figure 553. TCH requests for a new call, S3 (trf_18a)

Peak busy TCH (trf_19)

Use: This PI is an important traffic load indicator on the cell level.By following the development of this indicator and reactingproactively, blocking can be avoided in cells where the trafficgrows smoothly.

max(peak_busy_tch)


Figure 554. Peak busy TCH (trf_19)

Average unit load (trf_20)

sum(load_rate)/sum(load_denom1)

Counters from table(s):p_nbsc_load

Figure 555. Average unit load (trf_20)



Call time difference between TRXs, S4 (trf_21)

Use: This PI shows as a percentage how much bigger the traffic ofthe busiest TRX of a BTS is compared to the least busy TRXof the same BTS.

100 * (max_call_samples - min_call_samples)/min_call_samples

wheremax_call_samples are the call samples of the busiest TRX of a BTS:max((ul_calls + dl_calls)/2)andmin_call_samples are the call samples of the least busy TRX of a BTS:min((ul_calls + dl_calls)/2)

ul_calls =sum(freq_ul_qual0+ freq_ul_qual1+ freq_ul_qual2+ freq_ul_qual3+ freq_ul_qual4+ freq_ul_qual5+ freq_ul_qual6+ freq_ul_qual7)

dl_calls=sum(freq_dl_qual0+ freq_dl_qual1+ freq_dl_qual2+ freq_dl_qual3+ freq_dl_qual4+ freq_dl_qual5+ freq_dl_qual6+ freq_dl_qual7)

Counters from table(s):p_nbsc_rx_qual

Figure 556. Call time difference between TRXs, S4 (trf_21)

Call time difference between TRXs, S4 (trf_21a)

Use: Shows how many times bigger the traffic of the busiest TRXof a BTS is compared to the least busy TRX of the same BTS.

max_call_samples/min_call_samples

wheremax_call_samples are the call samples of the busiest TRX of a BTS:max((ul_calls + dl_calls)/2)andmin_call_samples are the call samples of the least busy TRX of a BTS:min((ul_calls + dl_calls)/2)

ul_calls=sum(freq_ul_qual0+ freq_ul_qual1+ freq_ul_qual2+ freq_ul_qual3+ freq_ul_qual4+ freq_ul_qual5+ freq_ul_qual6+ freq_ul_qual7)



dl_calls=sum(freq_dl_qual0

+ freq_dl_qual1+ freq_dl_qual2+ freq_dl_qual3+ freq_dl_qual4+ freq_dl_qual5+ freq_dl_qual6+ freq_dl_qual7)


Figure 557. Call time difference between TRXs, S4 (trf_21a)

Number of mobiles located in a cell, BSC (trf_23a)

Use: If counted over an area, it could be possible to derive a KPIcalled ’Call minutes per MS’ from this formula.If used over a cell, it can give you an idea about how potentialthe cell is, for example.

How many times periodic LU has been sent = PLUS

How many times one MS sends a periodic LU in a time period =count_of_periods * period_duration/LU_period

X = number of MS

==>

X* count_of_periods * period_duration/LU_period = number ofperiodic updates (PLUS)

==> X = PLUS * LU_period/ (count_of_periods *period_duration)

sum(a.sdcch_loc_upd-nbr of incom.HO from other LA) * 0.1*b.timer_periodic_update_ms-------------------------------------------------------------------------------

count(*).a.period_duration/60

Counters from table(s):a = p_nbsc_res_accessb = c_bts

Figure 558. Number of mobiles located in a cell, BSC (trf_23a)



Note

The sum of incoming handovers from other location areas has to be counted fromp_nbsc_ho_adj using the LA info from the c_bts table.

* b.timer_periodic_update_ms and a.period_duration should be ofthe same unit, minutes for example.

Total TCH seizure time (call time in seconds) (trf_24b)

Note: The sampling takes place every 20 seconds. ave_busy_tchcounts cumulatively the number of busy TCHs.res_av_denom14 counts the number of samples taken.This is not pure conversation time but TCH seizure time. InHO there are two TCHs seized for a short time simultaneouslyand both may be counted if both seizures take place at thesampling moment.

sum(period_duration*60*ave_busy_tch/res_av_denom14)

Counters from table(s):p_nbsc_res_availunit: seconds

Figure 559. Total TCH seizure time (call time in seconds) (trf_24b)

Total TCH seizure time (call time in hours) (trf_24c)

Note: 1. See trf_24b.2. On BTS level. For area (or segment) level, first use theformula for all the BTSs and then sum this formula over allunderlying BTSs.

sum(period_duration*ave_busy_tch/res_av_denom14/60)

Counters from table(s):p_nbsc_res_availunit: erlang hour

Figure 560. Total TCH seizure time (call time in hours) (trf_24c)

SDCCH true seizures (trf_25)

Known problems: There is no counter for IMSI detaches until in release S7.

sum(succ_seiz_term+succ_seiz_orig+sdcch_call_re_est+sdcch_emerg_call+sdcch_loc_upd)




Figure 561. SDCCH true seizures (trf_25)

SDCCH true seizures, S7 (trf_25a)

Known problems: There is no counter for supplemetary service requests until inrelease S9.

sum(succ_seiz_term+succ_seiz_orig+sdcch_call_re_est+sdcch_emerg_call+sdcch_loc_upd+imsi_detach_sdcch)


Figure 562. SDCCH true seizures, S7 (trf_25a)

SDCCH true seizures for call and SS (trf_26)

Known problems: Supplementary services cannot be separated currently on thecell level.

sum(succ_seiz_term+succ_seiz_orig+sdcch_call_re_est+sdcch_emerg_call- succ_sdcch_sms_est- unsucc_sdcch_sms_est)


Figure 563. SDCCH true seizures for call and SS (trf_26)

SDCCH true seizures for call, SMS, SS (trf_27)

Known problems: Supplementary services cannot be separated.

sum(succ_seiz_term+succ_seiz_orig+sdcch_call_re_est+sdcch_emerg_call)


Figure 564. SDCCH true seizures for call, SMS, SS (trf_27)

Peak busy SDCCH seizures (trf_28)

Use: The peak value of SDCCH usage is needed for preventivecapacity monitoring on the cell level.

max(peak_busy_sdcch)




Figure 565. Peak busy SDCCH seizures (trf_28)

IUO layer usage % (trf_29)

Use: Counted for overlay TRXs or underlay TRXs.sum(ave_busy_tch)

100 * -------------------------- %sum(ave_full_tch_if1

+ ave_full_tch_if2+ ave_full_tch_if3+ ave_full_tch_if4+ ave_full_tch_if5)

+ sum(ave_busy_tch)


Figure 566. IUO layer usage % (trf_29)

SDCCH seizures (trf_30)

Use: This figure tells the number of all events that have seizedSDCCH.

sum(sdcch_assign+sdcch_ho_seiz)


Figure 567. SDCCH seizures (trf_30)

Call time (minutes) from p_nbsc_res_avail (trf_32)

sum(period_duration * ave_busy_tch/res_av_denom14)

Counters from table(s):p_nbsc_res_availunit = minute

Figure 568. Call time (minutes) from p_nbsc_res_avail (trf_32)



Non-AMR call time from p_nbsc_rx_qual (trf_32a)

Known problems: In a high load situation (OMU link) it is possible that all calltime is not measured. In other words, call time can show alower value than it has in reality.Also, in the beginning of a call and in handover, two samplesare lost, showing a shorter time than in reality.

0.48*sum(freq_ul_qual0

+ freq_ul_qual1+ freq_ul_qual2+ freq_ul_qual3+ freq_ul_qual4+ freq_ul_qual5+ freq_ul_qual6+ freq_ul_qual7)

/60

Counters from table(s):p_nbsc_rx_qualunit = minutes

Figure 569. Non-AMR call time from p_nbsc_rx_qual (trf_32a)

Call time from p_nbsc_rx_statistics (trf_32b)

Known problems: In a high load situation it is possible that all call time is notmeasured. In other words, call time can show a lower valuethan it has in reality.

0.48*sum(freq_ul_qual0

+ freq_ul_qual1+ freq_ul_qual2+ freq_ul_qual3+ freq_ul_qual4+ freq_ul_qual5+ freq_ul_qual6+ freq_ul_qual7)

/60

Counters from table(s):p_nbsc_rx_statisticsunit = minutes

Figure 570. Call time from p_nbsc_rx_statistics (trf_32b)

SDCCH HO seizure % out of SDCCH seizure attempts (trf_33)

sum(sdcch_ho_seiz)100 * -------------------- %

sum(sdcch_seiz_att)




Figure 571. SDCCH HO seizure % out of SDCCH seizure attempts (trf_33)

SDCCH assignment % out of SDCCH seizure attempts (trf_34)

Formula:sum(sdcch_assign)

100 * -------------------- %sum(sdcch_seiz_att )


Figure 572. SDCCH assignment % out of SDCCH seizure attempts (trf_34)

TCH HO seizure % out of TCH HO seizure request (trf_35)

sum(tch_ho_seiz100 * ---------------------------------------------- %

sum(tch_request - tch_call_req - tch_fast_req)


Figure 573. TCH HO seizure % out of TCH HO seizure request (trf_35)

TCH norm seizure % out of TCH call request (trf_36)

sum(tch_norm_seiz)100 * --------------------------- %

sum(tch_call_req)


Figure 574. TCH norm seizure % out of TCH call request (trf_36)

TCH normal seizure % out of TCH call requests (trf_36a)

sum(tch_norm_seiz)-sum(tch_succ_seiz_for_dir_acc); ref.1

100 * --------------------------------------- %sum(tch_call_req)




Figure 575. TCH normal seizure % out of TCH call requests (trf_36a)

Ref.1 tch_norm_seiz is triggered also in case of DAC.

TCH FCS seizure % out of TCH FCS attempts (trf_37)

sum(tch_seiz_due_sdcch_con)100 * ----------------------------------- %

sum(tch_seiz_att_due_sdcch_con)


Figure 576. TCH FCS seizure % out of TCH FCS attempts (trf_37)

TCH FCS (due to SDCCH congestion) seizure % out of SDCCH seizureattempts (trf_38)

Use: Indicates the percentage of SDCCH seizures saved byFACCH call setup.

sum(tch_seiz_due_sdcch_con)100 * ----------------------------------- %

sum(sdcch_seiz_att)


Figure 577. TTCH FCS (due to SDCCH congestion) seizure % out of SDCCHseizure attempts (trf_38)

TCH seizures for new calls (trf_39)

sum(a.tch_norm_seiz) ;(normal calls)+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch) ;(DR inter-cell calls)+ sum(c.cell_sdcch_tch) ;(DR intra-cell calls in IOU, optional feature for S6)+ sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup


Figure 578. TCH seizures for new calls (trf_39)



TCH seizures for new calls (trf_39a)

sum(a.tch_norm_seiz) ;(normal calls)- sum(a.succ_tch_seiz_for_dir_acc); ref.2+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch) ;(DR inter-cell calls)+ sum(c.cell_sdcch_tch) ;(DR intra-cell calls in IOU)+ sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup


Figure 579. TCH seizures for new calls (trf_39a)


HTCH usage, S5 (trf_40)

Use: On the area level gives you an idea of how well the capacityis used. Use with S5 or a later version.

sum(ave_tch_busy_halfl)= 100 * ----------------------------- %

sum(ave_tch_avail_half)


Figure 580. HTCH usage, S5 (trf_40)

MOC rate, S6 (trf_41)

Known problems: Do not include SMS, SS ==> Better accuracy for speech callsthan if 3012 and 3013 were used.If SDCCH were congested and FACCH used for SMS (SS?),also SMS and SS get included.

tch_moc_seiz_att100 * ------------------------------------ %

tch_moc_seiz_att + tch_mtc_seiz_att


Figure 581. MOC rate, S6 (trf_41)



MTC rate, S6 (trf_42)

Known problems: Do not include SMS, SS ==> Better accuracy for speech callsthan if 3012 and 3013 were used.If SDCCH were congested and FACCH used for SMS (SS?)then also SMS and SS are included.

tch_moc_seiz_att100 * ------------------------------------ %

tch_moc_seiz_att + tch_mtc_seiz_att


Figure 582. MTC rate, S6 (trf_42)

TCH single band subscriber holding time, S6 (trf_43)

0.48* sum(tch_single_band_hold_time)

Counters from table(s):p_nbsc_dual_bandUnit: second

Figure 583. TCH single band subscriber holding time, S6 (trf_43)

TCH dual band subscriber holding time, S6 (trf_44)

0.48* sum(tch_dual_band_hold_time)

Unit: secondCounters from table(s):p_nbsc_dual_band

Figure 584. TCH dual band subscriber holding time, S6 (trf_44)

Share of single band traffic (trf_47)

sum(tch_single_band_hold_time)100* -------------------------------------------------------- %

sum(tch_single_band_hold_time + tch_dual_band_hold_time)

Counters from table(s):p_nbsc_dual_band.

Figure 585. Share of single band traffic (trf_47)



Share of dual band traffic (trf_48)

sum(tch_dual_band_hold_time)100* -------------------------------------------------------- %

sum(tch_single_band_hold_time + tch_dual_band_hold_time)


Figure 586. Share of dual band traffic (trf_48)

Call retries due to A interface pool mismatch (trf_49)

Use: Compensation of the blocking caused by the A interfacecircuit pool mismatch.

Aif type mismatch or congestion - Aif circuit pool handover failure =

a.tch_rej_due_req_ch_a_if_crc- (b.bsc_i_unsucc_a_int_circ_type+ b.msc_controlled_in_ho+ b.ho_unsucc_a_int_circ_type)


Figure 587. Call retries due to A interface pool mismatch (trf_49)

HO retries due to A interface pool mismatch (trf_50)

Use: Compensation of blocking caused by the A interface circuitpool mismatch.

Sum(bsc_i_unsucc_a_int_circ_type+ msc_controlled_in_ho+ ho_unsucc_a_int_circ_type)


Figure 588. HO retries due to A interface pool mismatch (trf_50)

TCH single band subscribers’ share of holding time, S6 (trf_51)

sum(tch_single_band_hold_time)100 * ------------------------------------------------------ %

sum(tch_single_band_hold_time+tch_dual_band_hold_time)


Figure 589. TCH single band subscribers’ share of holding time, S6 (trf_51)



TCH dual band subscribers’ share of holding time, S6 (trf_52)

sum(tch_dual_band_hold_time)100 * ------------------------------------------------------ %

sum(tch_single_band_hold_time+tch_dual_band_hold_time)

Unit: secondCounters from table(s):p_nbsc_dual_band

Figure 590. TCH dual band subscribers’ share of holding time, S6 (trf_52)

Calls started as FACCH call setup (trf_53)

Use: If there is SDCCH congestion and dynamic SDCCHallocation is not capable of allocating more SDCCH, thesignalling can take place on TCH if there is free capacity, anda call can be established.

sum(tch_seiz_att_due_sdcch_con)

Counters from table(s):p_nbsc_trafficUnit: second

Figure 591. Calls started as FACCH call setup (trf_53)

SDCCH seizures (trf_54)

sum(sdcch_assign+sdcch_ho_seiz)


Figure 592. SDCCH seizures (trf_54)

TCH normal seizures (trf_55)

sum(tch_norm_seiz)-sum(tch_succ_seiz_for_dir_acc); ref.1


Figure 593. TCH normal seizures (trf_55)

Ref.1 The counter tch_norm_seiz is triggered also in the case of DAC.



Total FTCH seizure time (trf_56)

sum(period_duration*ave_tch_busy_full/60)

Counters from table(s):p_nbsc_res_availunit = hour

Figure 594. Total FTCH seizure time (trf_56)

Total HTCH seizure time (trf_57)

sum(period_duration*ave_tch_busy_half/60)


Figure 595. Total HTCH seizure time (trf_57)

Average TCH hold time for HSCSD, S7 (trf_58)

Use: The numerator counts the cumulative sum of the TCH holdingtimes for HSCSD. The numerator is the number of HSCSDTCH releases.

Known problems: Incorrect if extended TRXs are used and not counted onBTS/trx_type level.

sum(ave_tch_hold_time_hscsd_numer)----------------------------------- secsum(ave_tch_hold_time_hscsd_denom)*100


Figure 596. Average TCH hold time for HSCSD, S7 (trf_58)

Average number of HSCSD users, S7HS (trf_60)

sum(ave_hscsd_users_numer)--------------------------sum(ave_hscsd_users_denom)


Figure 597. Average number of HSCSD users, S7HS (trf_60)



Total HSCSD TCH seizure time (call time, hours), S7HS (trf_61)

period_duration * ave_busy_tch_hscsd_numersum(-------------------------------------------)

ave_busy_tch_hscsd_denom/60


Figure 598. Total HSCSD TCH seizure time (call time, hours), S7HS (trf_61)

Average upgrade pending time for HSCSD (trf_62)

sum(ave_pend_time_numer)----------------------------sum(ave_pend_time_denom)*100

Counters from table(s):p_nbsc_high_speed_dataUnit: sec

Figure 599. Average upgrade pending time for HSCSD (trf_62)

Average upgrade pending time due to congestion (trf_63)

sum(ave_pend_time_due_cong_numer)---------------------------------------sum(ave_pend_time_due_cong_denom)*100

Counters from table(s):p_nbsc_high_speed_dataUnit: sec

Figure 600. Average upgrade pending time due to congestion (trf_63)

Total reporting time of ph1 and ph2 mobiles (trf_64)

sum(rep_time_by_ph_1_ms + rep_time_by_ph_2_ms)*0,46/60

Counters from table(s):p_nbsc_ms_capabilityUnit: min

Figure 601. Total reporting time of ph1 and ph2 mobiles (trf_64)

Total TCH seizures (trf_65)

sum(tch_reserv_by_mslot_cl_1_ms + ... + tch_reserv_by_mslot_cl_18_ms



+tch_reserv_by_mslot_incap_ms)

Counters from table(s):p_nbsc_ms_capability

Figure 602. Total TCH seizures (trf_65)

Net UL data traffic per timeslot, S9PS (trf_69a)

Use: Gives an idea of how effectively the GPRS timeslots are used.

data in kilobits------------------------------------------------------- =total time * average number of GPRS timeslots

sum(a.RLC_data_blocks_UL_CS1*20+a.RLC_data_blocks_UL_CS2*30)* 8/1000-------------------------------------------------------------------------------sum(b.period_duration*60)*sum(b.ave_GPRS_channels_sum)/sum(b.ave_GPRS_channels_den)

Counters from table(s):a = p_nbsc_packet_control_unitb = p_nbsc_res_availUnit: kbit/sec/tsl

Figure 603. Net UL data traffic per timeslot, S9PS (trf_69a)

Net DL data traffic per timeslot, S9PS (trf_70a)

Use: Gives an idea of how effectively the GPRS timeslots are used.

data in kilobits------------------------------------------------------- =total time * average number of GPRS timeslots

sum(a.RLC_data_blocks_DL_CS1*20+a.RLC_data_blocks_DL_CS2*30)* 8/1000-------------------------------------------------------------------------------sum(b.period_duration*60)*sum(b.ave_GPRS_channels_sum)/sum(b.ave_GPRS_channels_den)

Counters from table(s):a= p_nbsc_packet_control_unitb = p_nbsc_res_availUnit: kbit/sec/tsl

Figure 604. Net DL data traffic per timeslot, S9PS (trf_70a)

Average UL throughput per allocated timeslot, S9PS (trf_72b)

Use: Indicates the net data rate per allocated channel. The lower thevalue the more loaded is the GPRS territory and the lessservice the MS users receive.The numerator does not contain the RLC header bytes (2)neither the MAC header (1) because the aim is to count datavolume from the user’s point of view.



Known problems: 1) The formula works after S9 CD1.2, seeave_dur_UL_TBF_sum.2) The number of TBFs (MS) sharing the same timeslotsvaries.3) The data blocks of abnormally released TBFs and TBFsthat are not yet released during the measurement periodincrease the amount of data during the period, but are nottaken into account in the duration counters, i.e. they do notincrease the total duration of TBF4) Another inaccuracy is the ‘average allocated tsl’. Now eachallocation in the formula is of equal weight. To be correct,each allocation should be weighted by its duration.5) After S9 BSC CD 4.0, the ‘Delayed TBF release’modification in PCU adds the TBF holding time and thusmakes this KPI show smaller values.

data in kilobits/ TBF total time---------------------------------------- =average allocated tsl

(sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30)* 8/1000----------------------------------------------------------------------

sum(Ave_dur_UL_TBF_sum/100)----------------------------------------------------------------------

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


Unit: kbit/sec/tsl

Figure 605. Average UL throughput per allocated timeslot, S9PS (trf_72b)

Average effective UL throughput per used tsl, S9PS (trf_72d)

Use: Indicates net data rate per used timeslot. The lower the valuethe more loaded is the GPRS territory and the less service theMS users receive.The numerator does not contain the RLC header bytes neitherdoes the MAC header because the aim is to count data volumefrom as close to the user’s point of view as possible.The denominator is built on the fact that one timeslot cancarry 50 RLC blocks per second.



Known problems: 1) The numerator is not yet pure user data but as close to thatas we can see from BSC counters.2) Note that this KPI has correlation with DL data becauserlc_mac_cntrl_blocks_ul gets triggered for each PacketDownlink ACK/NACK. If the DL retransmissions get morefrequent (radio interface quality worse or polling parametershave been modified) the polling becomes more frequent andtherefore rlc_mac_cntrl_blocks_ul gets triggered more often.This leads to a situation where the effective UL throughputseems to get worse even though nothing really has changed inUL.

UL payload data in (kbytes)---------------------------------------- =UL time for data transfer (sec)

sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30)*8 /1000--------------------------------------------------------------------sum(rlc_data_blocks_ul_cs1+ rlc_data_blocks_ul_cs2+ rlc_mac_cntrl_blocks_ul+ BAD_FRAME_IND_UL_CS1+ BAD_FRAME_IND_UL_CS2+ BAD_FRAME_IND_UL_UNACK+ IGNOR_RLC_DATA_BL_UL_DUE_BSN) /50

Counters from table(s):p_nbsc_packet_control_unitunit: Kbps / tsl

Figure 606. Average effective UL throughput per used tsl, S9PS (trf_72d)

Average effective UL throughput per used timeslot, S10PS (trf_72f)

Use: Indicates the net data rate per used timeslot. The lower thevalue the more loaded is the GPRS territory and the lessservice the MS users receive.The numerator does not contain the RLC header bytes neitherdoes the MAC header because the aim is to count data volumefrom as close to the user’s point of view as possible.The denominator is built on the fact that one timeslot cancarry 50 RLC blocks per second.

Known problems: The numerator is not yet pure user data but as close to that aswe can see from BSC counters.

UL payload data in (kilobits)-------------------------------- =UL time for data transfer (sec)

sum(a.RLC_data_blocks_UL_CS1*20 + a.RLC_data_blocks_UL_CS2*30)*8 /1000+(sum over MCS-1 (xx)*22+sum over MCS-2 (xx)*28+sum over MCS-3 (xx)*37+sum over MCS-4 (xx)*44+sum over MCS-5 (xx)*56+sum over MCS-6 (xx)*74+



sum over MCS-7 (xx)*56+sum over MCS-8 (xx)*68+sum over MCS-9 (xx)*74)*8/1000

------------------------------------------------------------------------sum(a.rlc_data_blocks_ul_cs1

+ a.rlc_data_blocks_ul_cs2+ a.rlc_mac_cntrl_blocks_ul+ a.BAD_FRAME_IND_UL_CS1+ a.BAD_FRAME_IND_UL_CS2+ a.BAD_FRAME_IND_UL_UNACK+ a.IGNOR_RLC_DATA_BL_UL_DUE_BSN) /50+ sum over MSC1?6 of (yy)/50+ sum over MSC7?9 of (yy)/2 /50

wherexx = b.ul_rlc_blocks_in_ack_mode + b.ul_rlc_blocks_in_unack_modeyy =b.ul_rlc_blocks_in_ack_mode

+b.retrans_rlc_data_blocks_ul+b.bad_rlc_valid_hdr_ul_unack+b.ul_rlc_blocks_in_unack_mode


Figure 607. Average effective UL throughput per used TSL, S10PS (trf_72f)

Average effective UL throughput per used TSL, S10PS (trf_72h)

Use: Indicates the net data rate per used timeslot. The lower thevalue the more loaded is the GPRS territory and the lessservice the MS users receive.The numerator does not contain the RLC header bytes neitherthe does the MAC header because the aim is to count datavolume from the user's point of view as close as possible.The denominator is build on the fact that one timeslot cancarry 50 RLC blocks per second.

Known problems: The numerator is not yet pure user data but as close to that aswe can see from BSC counters.

UL payload data in (kilobits)---------------------------------------- =UL time for data transfer (sec)

sum(a.RLC_data_blocks_UL_CS1*20+a.RLC_data_blocks_UL_CS2*30)*8 /1000+(sum over MCS-1 (xx)*22+sum over MCS-2 (xx)*28+sum over MCS-3 (xx)*37+sum over MCS-4 (xx)*44+sum over MCS-5 (xx)*56+sum over MCS-6 (xx)*74+sum over MCS-7 (xx)*56+sum over MCS-8 (xx)*68+sum over MCS-9 (xx)*74)*8/1000--------------------------------------------------------------------sum(a.rlc_data_blocks_ul_cs1

+ a.rlc_data_blocks_ul_cs2+ a.BAD_FRAME_IND_UL_CS1



+ a.BAD_FRAME_IND_UL_CS2+ a.BAD_FRAME_IND_UL_UNACK+ a.IGNOR_RLC_DATA_BL_UL_DUE_BSN) /50

+sum over MSC1...6 of (yy)/50+sum over MSC7...9 of (yy)/2 /50

wherexx = b.ul_rlc_blocks_in_ack_mode

+ b.ul_rlc_blocks_in_unack_modeyy = b.ul_rlc_blocks_in_ack_mode

+ b.retrans_rlc_data_blocks_ul+ b.bad_rlc_valid_hdr_ul_unack+ b.ul_rlc_blocks_in_unack_mode

Counters from table(s):a=p_nbsc_packet_control_unitb=p_nbsc_coding_scheme

Figure 608. Average effective UL throughput per used TSL, S10PS (trf_72h)

Average DL throughput per allocated timeslot, S9PS (trf_73b)

Use: Indicates the net data rate per allocated channel. The lower thevalue the more loaded the GPRS territory and the less servicethe MS users receive.The numerator does not contain the RLC header bytes (2)neither the MAC header (1) because the aim is to count datavolume from the user’s point of view.

Known problems: 1)The formula works after S9 CD1.2, seeave_dur_UL_TBF_sum.2) Number of TBFs (MS) sharing the same timeslot varies.3) Abnormally released TBFs as well as TBFs that are not yetreleased during the measurement period . The data blocks ofthose increase the amount of data during the period, but theyare not taken into account in the duration counters, i.e. they donot increase the total duration of TBFs. This situation occurswhen TBF completion ratio tbf_26a shows a low value.4) Another inaccuracy is the 'average allocated tsl'. Now eachallocation in the formula has equal weight. To be correct, eachallocation should be weighed by it’s duration.5) After S9 BSC CD 4.0, the 'Delayed TBF release'modification in PCU adds the TBF holding time andtherefore causes this KPI to show smaller values.

data in kilobits/ TBF total time----------------------------------- =average allocated tsl

(sum(RLC_data_blocks_DL_CS1*20+ RLC_data_blocks_DL_CS2*30)* 8/1000

------------------------------------------sum(Ave_dur_DL_TBF_sum/100 )

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


Unit: kbit/sec/tsl

Figure 609. Average DL throughput per allocated timeslot, S9PS (trf_73b)

Average effective DL throughput per used timeslot, S9PS (trf_73d)

Use: Indicates the net data rate per used timeslot. The lower thevalue the more loaded is the GPRS territory and the lessservice the MS users receive.The numerator does not contain the RLC header bytes neitherthe MAC header because the aim is to count data volume fromthe user’s point of view as close as possible.The denominator is built on the fact that one timeslot cancarry 50 RLC blocks per second.

Known problems: 1) The numerator is not yet pure user data but as close to thatas we can see from BSC counters.2) Retransmitted blocks due to other reasons than NACK arenot counted in any of the RLC counters. In DL direction theseretransmissions occur when the TBF release is delayed.3) If there is only one TBF on a timeslot, for example, someRLC blocks can be retransmitted before an ACK is received.These blocks are not counted in any of the RLC counters.4) Counter rlc_mac_cntrl_blocks_dl also containsdummy blocks until CD.6.1.

DL ’payload’ data in (kilobit)---------------------------------------- =DL time for data transfer (sec)

sum(RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30)*8 /1000-----------------------------------------------------------------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) /50


Unit: Kbps / tsl

Figure 610. Average effective DL throughput per used timeslot, S9PS (trf_73d)



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

Use: Indicates the net data rate per used timeslot. The lower thevalue the more loaded is the GPRS territory and the lessservice the MS users receive.The numerator does not contain the RLC header bytes neitherdoes the MAC header, because the aim is to count datavolume from as close to the user’s point of view as possible.

Known problems: 1) The numerator is not yet pure user data but as close to thatas we can see from BSC counters.2) Retransmitted blocks due to other reasons than NACK arenot counted in any of the RLC-counters. In DL direction theseretransmissions occur when the TBF release is delayed.3) If there is only one TBF on a timeslot, for example, someRLC blocks can be retransmitted before an ACK is received.These blocks are not counted in any of the RLC counters.

DL payload data in (kbytes)---------------------------------- =DL time for data transfer (sec)

sum(a.RLC_data_blocks_DL_CS1*20 + a.RLC_data_blocks_DL_CS2*30)*8 /1024+(sum over MCS-1 (xx)*22+sum over MCS-2 (xx)*28+sum over MCS-3 (xx)*37+sum over MCS-4 (xx)*44+sum over MCS-5 (xx)*56+sum over MCS-6 (xx)*74+sum over MCS-7 (xx)*56+sum over MCS-8 (xx)*68+sum over MCS-9 (xx)*74)*8/1024

----------------------------------------------------------------------sum(a.rlc_data_blocks_dl_cs1

+ a.rlc_data_blocks_dl_cs2+ a.rlc_mac_cntrl_blocks_dl - a.dummy_dl_mac_blocks_sent+ a.RETRA_RLC_DATA_BLOCKS_DL_CS1+ a.RETRA_RLC_DATA_BLOCKS_DL_CS2) /50+ sum over msc1...6 of (yy)/50+ sum over msc7...9 of (yy)/2/50

wherexx = b.dl_rlc_blocks_in_ack_mode + b.dl_rlc_blocks_in_unack_modeyy =b.dl_rlc_blocks_in_ack_mode

+b.retrans_rlc_data_blocks_dl+b.dl_rlc_blocks_in_unack_mode


Unit: kbit/sec/tsl

Figure 611. Average effective DL throughput per used timeslot, S10PS (trf_73f)



Average effective DL throughput per used TSL, S10PS (trf_73g)

Use: Indicates the net data rate per used timeslot. The lower thevalue the more loaded is the GPRS territory and the lessservice the MS users receive. The numerator does not containthe RLC header bytes neither the does the MAC headerbecause the aim is to count data volume from the user's pointof view as close as possible

Known problems: 1) The numerator is not yet pure user data but as close to thatas we can see from BSC counters.2) Retransmitted blocks due to other reasons than NACK arenot counted in any of the RLC-counters. In DL direction theseretransmissions occur when the TBF release is delayed.3) If there is only one TBF on a timeslot, for example, someRLC blocks can be retransmitted before an ACK is received.These blocks are not counted in any of the RLC counters.

DL payload data in (kilobits)---------------------------------------- =DL time for data transfer (sec)

sum(a.RLC_data_blocks_DL_CS1*20+ a.RLC_data_blocks_DL_CS2*30)*8 /1000

+ (sum over MCS-1 (xx)*22++ sum over MCS-2 (xx)*28++ sum over MCS-3 (xx)*37++ sum over MCS-4 (xx)*44++ sum over MCS-5 (xx)*56++ sum over MCS-6 (xx)*74++ sum over MCS-7 (xx)*56++ sum over MCS-8 (xx)*68++ sum over MCS-9 (xx)*74)*8/1000

---------------------------------------------sum(a.rlc_data_blocks_dl_cs1

+ a.rlc_data_blocks_dl_cs2+ a.RETRA_RLC_DATA_BLOCKS_DL_CS1+ a.RETRA_RLC_DATA_BLOCKS_DL_CS2) /50

+ sum over msc1…6 of (yy)/50+ sum over msc7…9 of (yy)/2/50

wherexx = b.dl_rlc_blocks_in_ack_mode

+ b.dl_rlc_blocks_in_unack_modeyy = b.dl_rlc_blocks_in_ack_mode

+ b.retrans_rlc_data_blocks_dl+ b.dl_rlc_blocks_in_unack_mode


Unit: kbit/sec/tsl

Figure 612. Average effective DL throughput per used TSL, S10PS (trf_73g)

Total RLC data, S9PS (trf_74)

Use: Indicates the total amount of data transmitted as CS1 or CS2blocks, UL or DL.



(sum(RLC_data_blocks_UL_CS1*23 + RLC_data_blocks_UL_CS2*33+ RLC_data_blocks_DL_CS1*23 + RLC_data_blocks_DL_CS2*33) /1000


Unit: kbyte

Figure 613. Total RLC data, S9PS (trf_74)

Total RLC data, S9PS (trf_74a)

Use: Indicates the total amount of data (both ack and unack modes)transmitted as CS1 or CS2 blocks. UL or DL. MAC blocksand RLC header bytes are excluded in order to get as close aspossible to the payload data.

Known problems: The divisor should be 1024 for Kbytes.

(sum(RLC_data_blocks_UL_CS1*20+RLC_data_blocks_UL_CS2*30+ RLC_data_blocks_DL_CS1*20+RLC_data_blocks_DL_CS2*30) /1000


Unit: kbyte

Figure 614. Total RLC data, S9PS (trf_74a)

Total GPRS RLC data, S9PS (trf_74b)

Use: Indicates the total amount of data (both ack and unack modes)transmitted as CS1 or CS2 blocks. UL or DL. MAC blocksand RLC header bytes are excluded in order to get as close aspossible to the payload data.

(sum(RLC_data_blocks_UL_CS1*20 + RLC_data_blocks_UL_CS2*30+ RLC_data_blocks_DL_CS1*20 + RLC_data_blocks_DL_CS2*30) /1024

Counters from table(s):p_nbsc_packet_control_unitUnit: kbyte

Figure 615. Total GPRS RLC data, S9PS (trf_74b)

Total GPRS RLC data (trf_74c)

Use: Indicates the total amount of data (both ack and unack modes)transmitted as CS1..CS4 blocks. UL or DL. MAC blocks andRLC header bytes are excluded in order to get as close to thepayload data as possible.

sum(



a.RLC_data_blocks_UL_CS1*20+ a.RLC_data_blocks_UL_CS2*30+ a.RLC_data_blocks_DL_CS1*20+ a.RLC_data_blocks_DL_CS2*30+ sum over MCS-11 (b.dl_rlc_blocks_in_ack_mode+ b.dl_rlc_blocks_in_unack_mode+ b.ul_rlc_blocks_in_ack_mode+ b.ul_rlc_blocks_in_unack_mode)*36+ sum over MCS-12 (b.dl_rlc_blocks_in_ack_mode+ b.dl_rlc_blocks_in_unack_mode+ b.ul_rlc_blocks_in_ack_mode+ b.ul_rlc_blocks_in_unack_mode)*50 )

/1024


Unit: kB

Figure 616. Total GPRS RLC data (trf_74c)

GPRS territory UL utilisation, S9PS (trf_76b)

Use: Most useful on BTS level. Used as BH (CS+PS) trendtogether with CS traffic, total TCH capacity and PS territorysize.Indicates how big a portion of the GPRS territory has beenused. When the utilisation % increases, the throughput rateperceived by the user reduces. This KPI is the way to estimatethe throughput rate reduction.If the utilisation % is high, increasing the CDEF parametersetting (when CS traffic is low) or adding a new TRX (whenCS traffic is high) should be considered.UL and DL should be looked at the same time and the higherone of those used in dimensioning together with CS traffictrf_12b and PS territory ava_16.

Note: The denominator varies depending on the traffic situation(downgrade of territory) and therefore this KPI has no linearcorrelation with the traffic. See ava_15.

Target level: Choosing the acceptable level is a QoS issue. For example,60% utilisation would give about 70% of the maximum rateachieved.

Data blocks transmitted in UL100* ------------------------------------------------------------ % =

(available GPRS channel time in sec)* (nbr of blocks per sec)

100*(DL blocks transmitted / DL block transmission capacity) % =

sum(rlc_data_blocks_ul_cs1+ rlc_data_blocks_ul_cs2+ rlc_mac_cntrl_blocks_ul+ BAD_FRAME_IND_UL_CS1+ BAD_FRAME_IND_UL_CS2+ BAD_FRAME_IND_UL_UNACK+ IGNOR_RLC_DATA_BL_UL_DUE_BSN)



100* -------------------------------------------------------------- %sum(a.ave_gprs_channels_sum/sum(a.ave_gprs_channels_den)

*sum(a.period_duration*60)*50

Counters from table(s):a = p_nbsc_res_availb = p_nbsc_packet_control_unit

Figure 617. GPRS territory UL utilisation, S9PS (trf_76b)

GPRS territory DL utilisation, S9PS (trf_77a)

Use: Most useful on BTS level. Used as BH (CS+PS) trendtogether with CS traffic, total TCH capacity and PS territorysize.Indicates how big a portion of the GPRS territory has beenused. When the utilisation % increases, the throughput rateperceived by the user reduces. This KPI is the way to estimatethe throughput rate reduction.If the utilisation % is high, increasing the CDEF parametersetting (when CS traffic is low) or adding a new TRX (whenCS traffic is high) should be considered.UL and DL should be looked at the same time and the higherone of those used in dimensioning together with CS traffictrf_12b and PS territory ava_16.


Known problems: Dummy blocks on DL make this PI show too high a value(fixed in CD6.0: RLC_MAC_cntrl_blocks does not containdummy blocks any more).


Data blocks transmitted in DL and UL100* ------------------------------------------------------------ % =


100*(DL blocks transmitted / DL block transmission capacity) % =

sum(+ b.RLC_data_blocks_DL_CS1+ b.RLC_data_blocks_DL_CS2+ b.RLC_MAC_cntrl_blocks_DL+ b.retra_RLC_data_blocks_DL_CS1+ b.retra_RLC_data_blocks_DL_CS2)

100* --------------------------------------------------------------- %sum(a.ave_gprs_channels_sum/sum(a.ave_gprs_channels_den)

*sum(a.period_duration*60)*50




a = p_nbsc_res_availb = p_nbsc_packet_control_unit

Figure 618. GPRS territory DL utilisation, S9PS (trf_77a)

UL GPRS traffic, S9PS (trf_78a)

Use: Indicates the amount of resources (timeslots) the GPRS trafficdata consumes on average during the period. This informationis useful, for example, in forecasting the need for capacityextension.

Known problems: The value is optimistic because the time needed for TBFestablishment and release is not included. The delayed TBFrelease that was taken into use in a CD of S9 also adds theactual usage of the TCH but cannot be considered in thisformula. These make the value seem smaller.

Actual UL data throughput (blocks)---------------------------------------------- =max. nbr of blocks during measurement period

sum(rlc_data_blocks_ul_cs1+ rlc_data_blocks_ul_cs2+ rlc_mac_cntrl_blocks_ul+ BAD_FRAME_IND_UL_CS1+ BAD_FRAME_IND_UL_CS2+ BAD_FRAME_IND_UL_UNACK+ IGNOR_RLC_DATA_BL_UL_DUE_BSN)

-----------------------------------sum(period_duration*60)*50


Unit: tsl (or erlang)

Figure 619. UL GPRS traffic, S9PS (trf_78a)

UL PS traffic (trf_78c)

Use: Indicates the amount of resources (timeslots) the GPRS trafficdata consumes on average during the period. This informationis useful, for example, in forecasting the need for capacityextension.

Known problems: The value is optimistic because the time needed for TBFestablishment and release is not included. The delayed TBFrelease that was taken into use in a CD of S9 also adds theactual usage of the TCH but cannot be considered in thisformula. These make the value seem smaller.

Actual UL data throughput (blocks)------------------------------------------------------------- =nbr of blocks equivalent to 1 tsl full use in each BTS of area



sum(a.rlc_data_blocks_ul_cs1+ a.rlc_data_blocks_ul_cs2+ a.rlc_mac_cntrl_blocks_ul+ a.bad_frame_ind_ul_cs1+ a.bad_frame_ind_ul_cs2+ a.bad_frame_ind_ul_unack+ a.ignor_rlc_data_bl_ul_due_bsn)

+sum over MCS1..6 of(b.ul_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_ul+

b.bad_rlc_valid_hdr_ul_unack+b.ul_rlc_blocks_in_unack_mode)+sum over MCS7..9 of(b.ul_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_ul+b.bad_rlc_valid_hdr_ul_unack+b.ul_rlc_blocks_in_unack_mode)/2---------------------------------------------------sum(period_duration*60)*50 ; 50 blocks /sec /tsl

Counters from table(s):a=p_nbsc_packet_control_unitb= p_nbsc_coding_scheme

Figure 620. UL PS traffic (trf_78c)

DL GPRS traffic, S9PS (trf_79a)

Use: Indicates the amount of resources (timelots) the GPRS trafficdata consumes. This information is useful, for example, inforecasting the need for capacity extension.

Known problems: 1) The MS can send an UL data block only if it has receivedits USF in the preceding DL block. If the network has nothingelse to send, it will send a Packet DL Dummy Control Blockto carry the USF. These dummy blocks are included in thisKPI until CD6.1 and make it show bigger values.2) Transferred DL blocks, whose corresponding element inthe transmit window V(B) has the value PENDING ACK, arenot counted to any of the counters.3) The time needed for TBF establishment and release is notincluded. Also the delayed TBF release that was taken intouse in a CD of S9 adds the actual usage of the TCH but cannotbe considered in this formula. These make the value seemsmaller.

Actual DLdata throughput (blocks)---------------------------------------------- =max. nbr of blocks during measurement period

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)

----------------------------------sum(period_duration*60)*50




p_nbsc_packet_control_unitUnit: timeslot or erlang

Figure 621. DL GPRS traffic, S9PS (trf_79a)

DL PS traffic (trf_79c)

Use: Indicates the amount of resources (timeslots) the GPRS trafficdata consumes. This information is useful, for example, inforecasting the need for capacity extension.

Known problems: 1) The MS can send an UL data block only if it has receivedits USF in the preceding DL block. If the network has nothingelse to send it will send a Packet DL Dummy Control Blockto carry the USF. These dummy blocks are included in thisKPI and make it show bigger values. In S10 there is a newcounter for the dummy blocks and it can be subtracted fromthe numerator.2) Transferred DL blocks, whose corresponding element inthe transmit window V(B) has the value PENDING ACK, arenot counted to any of the counters3) The time needed for TBF establishment and release is notincluded. Also the delayed TBF release that was taken intouse in a CD of S9 adds the actual usage of the TCH but cannotbe considered in this formula. These make the value seemsmaller.

Actual DL data throughput (blocks)--------------------------------------------------------------- =nbr of blocks equivalent to 1 tsl full use in each BTS of area

sum(a.rlc_data_blocks_dl_cs1+ a.rlc_data_blocks_dl_cs2+ a.rlc_mac_cntrl_blocks_dl+ a.RETRA_RLC_DATA_BLOCKS_DL_CS1+ a.RETRA_RLC_DATA_BLOCKS_DL_CS2)

+sum over MCS1..6 of(b.dl_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_dl+b.dl_rlc_blocks_in_unack_mode)+sum over mcs7..9 ofb.dl_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_dl+

+ b.dl_rlc_blocks_in_unack_mode)/2---------------------------------------------------------sum(period_duration*60)*50 ;50 blocks /sec /tsl

Counters from table(s):A=p_nbsc_packet_control_unitB=p_nsbc_coding_scheme

Figure 622. DL PS traffic (trf_79c)

TCH free margin, S9PS (trf_81)

Use: Indicates the average number of free TCH timeslots.



Known problems: 1) DL MAC blocks contain dummy blocks.2) Transferred DL blocks, whose corresponding element inthe transmit window V(B) has the value PENDING ACK, arenot counted to any of the counters.

Capacity available for CSW + dedicated PSW capacity - CSW traffic - PSW DL trafficava_15+ava_16-trf_12b-trf_79a

Counters from table(s):p_nbsc_res_availp_nbsc_packet_control_unit

Figure 623. TCH free margin, S9PS (trf_81)

Normal TCH usage % for CS (trf_83a)

Use: Indicates how many % of the total available normal TCHcapacity has been used for CS traffic on average. Used fortrend analysis.

Capacity used by CS traffic / total normal TCH capacity

trf_97= 100* ------------- %

ava_28+ava_16a

Figure 624. Normal TCH usage % for CS (trf_83a)

Normal TCH usage ratio for CS (trf_83b)

Use: Indicates how many per cent of the total available normalTCH capacity has been used for CS traffic on average. ThisKPI is used for trend analysis.

Capacity used by CS traffic / total normal TCH capacity

trf_97= 100 * ----------------- %

ava_28a + ava_16b

Figure 625. Normal TCH usage ratio for CS (trf_83b)

TCH usage % for PS, S9PS(trf_84a)

Use: Indicates how many % of the total available TCH capacity hasbeen used for PS traffic on average.

Known problems: 1) See the problems of trf_79a.2) For the absolute peak value there is no counter availableunlike for CS traffic.

Capacity used by PS traffic / total TCH capacity



trf_79a= 100* --------------- %

ava_15+ava_16

Figure 626. TCH usage % for PS, S9PS (trf_84a)

Normal TCH usage % for PS, S9PS (trf_84b)

Use: Indicates how many % of the total available normal TCHcapacity has been used for PS traffic on average. Used fortrend analysis.

trf_95= 100* ------------- %

ava_28+ava_16a

Figure 627. Normal TCH usage % for PS, S9PS (trf_84b)

Total TCH usage % for CS, S9PS(trf_85)

Use: Indicates how many % the of total TCH capacity has beenused for PS traffic.

Known problems: It is assumed that DL PS traffic is always greater than UL PStraffic.

Capacity used by CS and PS traffic / total TCH capacity

trf_12b +trf_79a= 100* --------------- %

ava_15+ava_16

Figure 628. Total TCH usage % for CS, S9PS (trf_85)

Total TCH usage % for CS and PS, S9PS (trf_85b)

Use: Indicates how many % of the total TCH capacity has beenused for PS traffic.



trf_12b +trf_95= 100* --------------- %

ava_25a

Figure 629. Total TCH usage % for CS and PS, S9PS (trf_85b)



Total TCH usage ratio for CS and PS (trf_85d)

Description: Indicates the percentage of the TCH use of combined CS andPS traffic.

Use: Indicates how many per cent of the total TCH capacity hasbeen used for PS traffic.



trf_12b + trf_159= 100 * ----------------- %

ava_25a

Figure 630. Total TCH usage ratio for CS and PS (trf_85d)

Free TCH %, S9PS (trf_86a)

Use: Most useful on BTS level in context with trf_83 and trf_84aKnown problems: Because the measurement period usually is 60min, the value

can not be used for spotting momentary problems but trends.

100- TCH usage % for CS - TCH usage % for PS= 100 - trf_83-trf_84a

Figure 631. Free TCH %, S9PS (trf_86a)

Free TCH %, S10.5PS (trf_86c)

Use: Most useful on BTS level in connection with trf_83a, trf_84cand trf_160. The combined (PS+CS traffic) value trend can beused for dimensioning.Indicates how many % of the total available RCH capacity hasnot been used on average. If free TCH percentage approaches0 the MS users start to experience call blocking and/orslowing down of (E)GPRS throughput.

Known problems: Because the measurement period usually is 60 minutes, thevalue can not be used for spotting momentary problems butonly the trend.

100 - TCH usage % for CS - TCH usage % for GPRS - TCH usage % for EGPRS= 100 - trf_83a - trf_84b - trf_160

Unit: %

Figure 632. Free TCH %, S10.5PS (trf_86c)



Total TCH % for PS (trf_87b)

Use: Indicates how many % of the total available normal TRXTCH capacity has been allocated for the PS territory,including additional channels.If there are now upgrades or downgrades, this value should bequite close to the value of parameter CDEF. Some differencecomes from granularity when the CDEF value is converted totimeslots in BSC.The denominator does not contain extended TRXs becausethey are not GPRS capable and are not included in theconversion of CDEF to timeslots.

Capacity allocated for PS territory-------------------------------------total TCH capacity of normal TRXs

ava_16a= 100* --------------- %

ava_28+ava_16a

Figure 633. Total TCH % for PS (trf_87b)

Total TCH % for PS (trf_87c)

Use: Indicates how many % of the total available normal TRXTCH capacity has been allocated for the PS territory,including additional channels.If there are now upgrades or downgrades, this value should bequite close to the value of parameter CDEF. Some differencecomes from granularity when the CDEF value is converted totimeslots in BSC.The denominator does not contain extended TRXs becausethey are not GPRS capable and are not included in theconversion of CDEF to timeslots.

Capacity allocated for PS territory-------------------------------------total TCH capacity of normal TRXs

ava_16a= 100 * --------------- %

ava_28a+ava_16b

Unit:%

Figure 634. Total TCH % for PS (trf_87c)



Total TCH % for dedicated PS, S9PS (trf_88b)

Use: Indicates how many % of the total normal TRX TCH capacityhas been allocated for the dedicated PS territory. This valueshould be quite close to the value of the CDED parameter.Some difference comes from granularity when the CDEDvalue is converted to timeslots in BSC.The denominator does not contain extended TRXs becausethey are not GPRS capable and are not included in theconversion of CDED to timeslots.

Capacity allocated for dedicated PS territory---------------------------------------------

total TCH capacity of normal TRXs

ava_17a= 100* --------------- %

ava_28+ava_16a

Unit: %

Figure 635. Total TCH % for dedicated PS, S9PS (trf_88b)

Total TCH % for dedicated PS, S9PS (trf_88c)

Use: Indicates how many % of the total normal TRX TCH capacityhas been allocated for the dedicated PS territory. This valueshould be quite close to the value of the CDED parameter.Some difference comes from granularity when the CDEDvalue is converted to timeslots in BSC.The denominator does not contain extended TRXs becausethey are not GPRS capable and are not included in theconversion of CDED to timeslots.

Capacity allocated for dedicated PS territory---------------------------------------------

total TCH capacity of normal TRXs

ava_17a= 100* --------------- %

ava_28a+ava_16b

Unit:%

Figure 636. Total TCH % for dedicated PS, S9PS (trf_88c)

Average total UL throughput per used timeslot, S9PS (trf_89]

Use: Indicates the total data rate per used timeslot. This figure isaffected by the coding scheme selected by the link adaptation.

Known problems: IGNOR_RLC_DATA_BL_UL_DUE_BSN is not only CS1(23 octets) but can also be CS2 (33). The share between CS1and CS2 has to be approximated.



All UL data (kilobit)---------------------------------- =time used for UL data transfer (sec)

( sum(rlc_data_blocks_ul_cs1 *23+ rlc_data_blocks_ul_cs2 *33+ rlc_mac_cntrl_blocks_ul *23+ BAD_FRAME_IND_UL_CS1*23+ BAD_FRAME_IND_UL_UNACK*23+ BAD_FRAME_IND_UL_CS2* 33)

+ ignor_rlc_data_bl_ul_due_bsn_CS1_aprx*23+ ignor_rlc_data_bl_ul_due_bsn_CS2_aprx *33

)*8/1000-----------------------------------------------sum(period_duration)*60* trf_78a

where

ignor_rlc_data_bl_ul_due_bsn_CS1_aprx =RLC CS1 blocks ignored due to incorrect BSN (missing counter approximated) =

sum(rlc_data_blocks_ul_cs1-rlc_data_blocks_UL_unack)-------------------------------------------------*sum(ignor_rlc_data_bl_ul_due_bsn)

sum(rlc_data_blocks_ul_cs1-rlc_data_blocks_UL_unack+rlc_data_blocks_ul_cs2)

ignor_rlc_data_bl_ul_due_bsn_CS2_aprx =RLC CS2 blocks ignored due to incorrect BSN (missing counter approximated)=

sum(rlc_data_blocks_ul_cs2)------------------------------------------------------*sum(ignor_rlc_data_bl_ul_due_bsn)

sum(rlc_data_blocks_ul_cs1-rlc_data_blocks_UL_unack+rlc_data_blocks_ul_cs2)


unit: kbps / tsl

Figure 637. Average total UL throughput per used timeslot, S9PS (trf_89)

Average total UL throughput per used TSL, S10PS (trf_89a)

Use: Indicates the total data rate per used timeslot. This figure isaffected by the coding scheme selected by the link adaptation.

Known problems: IGNOR_RLC_DATA_BL_UL_DUE_BSN is not only CS1(23 octets) but can also be CS2 (33). The share between CS1and CS2 has to be approximated.

All UL data (kilobits)------------------------------------ =time used for UL data transfer (sec)

sum(a.rlc_data_blocks_ul_cs1 *23+ a.rlc_data_blocks_ul_cs2 *33



+ a.rlc_mac_cntrl_blocks_ul *23+ a.BAD_FRAME_IND_UL_CS1*23+ a.BAD_FRAME_IND_UL_UNACK*23+ a.BAD_FRAME_IND_UL_CS2* 33+ a.ignor_rlc_data_bl_ul_due_bsn_CS1_aprx*23+ a.ignor_rlc_data_bl_ul_due_bsn_CS2_aprx *33

..+ )*8/1000+8*(sum over MCS-1 (xx)*30+

sum over MCS-2 (xx)*36+sum over MCS-3 (xx)*45+sum over MCS-4 (xx)*52+sum over MCS-5 (xx)*63+sum over MCS-6 (xx)*81+sum over MCS-7 (xx/2)*123+sum over MCS-8 (xx/2)*147+sum over MCS-9 (xx/2)*159)/1000

-----------------------------------------------sum(period_duration)*60* trf_78c

where1)ignor_rlc_data_bl_ul_due_bsn_CS1_aprx =RLC CS1 blocks ignored due to incorrect BSN (missing counter approximated) =

sum(rlc_data_blocks_ul_cs1- rlc_data_blocks_UL_unack)

------------------------------- *sum(ignor_rlc_data_bl_ul_due_bsn)sum(rlc_data_blocks_ul_cs1- rlc_data_blocks_UL_unack+ rlc_data_blocks_ul_cs2)


2)ignor_rlc_data_bl_ul_due_bsn_CS2_aprx =RLC CS2 blocks ignored due to incorrect BSN (missing counter approximated)=

sum(rlc_data_blocks_ul_cs2)------------------------------- *sum(ignor_rlc_data_bl_ul_due_bsn)sum(rlc_data_blocks_ul_cs1- rlc_data_blocks_UL_unack+ rlc_data_blocks_ul_cs2)

Counters from table(s):a=p_nbsc_packet_control_unit,b=p_nbsc_coding_scheme

3)xx = EGPRS UL RLC blocks =(b.ul_rlc_blocks_in_ack_mode + b.retrans_rlc_data_blocks_ul+b.bad_rlc_valid_hdr_ul_unack + b.ul_rlc_blocks_in_unack_mode)

Unit: kbps/tsl

Figure 638. Average total UL throughput per used TSL, S10PS (trf_89a)

Average total DL throughput per used timeslot, S9PS (trf_90)

Use: Indicates the total data rate per used timeslot.



Known problems: Counter rlc_mac_cntrl_blocks_dl also contains dummyblocks until CD6.1.

All DL data (kbits)---------------------------------- =time used for DL data transfer (sec)

sum(rlc_data_blocks_dl_cs1 *23+ rlc_data_blocks_dl_cs2 *33+ rlc_mac_cntrl_blocks_dl *23+ RETRA_RLC_DATA_BLOCKS_DL_CS1*23+ RETRA_RLC_DATA_BLOCKS_DL_CS2* 33)*8/1000

-----------------------------------------------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)/50


Unit: kbit/sec/tsl

Figure 639. Average total DL throughput per used timeslot, S9PS (trf_90)

Average total DL throughput per used timeslot, S10PS (trf_90a)

Use: Indicates the total data rate per used timeslot.Known problems: Dummy blocks are included. They can be subtracted in S10.

All GPRS DL data + all EGPRS DL data (kbits)-------------------------------------------- =time used for DL data transfer (sec)

sum(a.rlc_data_blocks_dl_cs1 *23+ a.rlc_data_blocks_dl_cs2 *33+ a.rlc_mac_cntrl_blocks_dl *23+ a.RETRA_RLC_DATA_BLOCKS_DL_CS1*23+ a.RETRA_RLC_DATA_BLOCKS_DL_CS2* 33)*8/1000+(sum over MCS-1 (xx)*30+sum over MCS-2 (xx)*36+sum over MCS-3 (xx)*45+sum over MCS-4 (xx)*52+sum over MCS-5 (xx)*63+sum over MCS-6 (xx)*81+sum over MCS-7 (xx/2)*123+sum over MCS-8 (xx/2)*147+sum over MCS-9 (xx/2)*159)*8/1000

-----------------------------------------------sum(period_duration)*60* trf_79c

Wherexx =(b.dl_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_dl+b.dl_rlc_blocks_in_unack_mode)

Counters from table(s):a = p_nbsc_packet_control_unit,b = p_nbsc_coding_scheme



Unit: kbps/tsl

Figure 640. Average total DL throughput per used timeslot, S10PS (trf_90a)

SDCCH true seizures for call (trf_91)

sum(succ_seiz_term+succ_seiz_orig+sdcch_call_re_est+sdcch_emerg_call- succ_sdcch_sms_est- unsucc_sdcch_sms_est-succ_seiz_supplem_serv)


Figure 641. SDCCH true seizures for call (trf_91)

Average HSCSD subchannel traffic, S7HS (trf_92)

HSCSD total traffic - HSCS main channel traffic =trf_59-trf-60 =

sum(ave_busy_tch_hscsd_numer)/sum(ave_busy_tch_hscsd_denom)-sum(ave_hscsd_users_numer)/sum(ave_hscsd_users_denom)-


Figure 642. Average HSCSD subchannel traffic, S7HS (trf_92)

Voice calls on SDCCH, S1 (trf_93)

sum(sdcch_emerg_call+succ_seiz_term+succ_seiz_orig-succ_sdcch_sms_est-unsucc_sdcch_sms_est)


Figure 643. Voice calls on SDCCH, S1 (trf_93)

TCH traffic, S1 (trf_94)

Use: Possible to use on the TRX level.

Call time / period duration =

sum(freq_ul_qual0+ freq_ul_qual1+ freq_ul_qual2+ freq_ul_qual3



+ freq_ul_qual4+ freq_ul_qual5+ freq_ul_qual6+ freq_ul_qual7)/60

0.48 * ------------------------sum(period_duration)

Unit: Erlang


Figure 644. TCH traffic, S1 (trf_94)

GPRS traffic sum, S9PS (trf_95a)

Use: Indicates the amount of resources (timeslots) the GPRS trafficdata consumes during the period on average. This informationis useful for example in forecasting the need for capacityextension.

Known problems: Timeslot usage caused by DL TBF release delay is notincluded and this makes the value seem optimistic.

Time used to transmit RLC blocks---------------------------------- =time available

sum(max of (rlc_data_blocks_ul_cs1

+ rlc_data_blocks_ul_cs2+ rlc_mac_cntrl_blocks_ul+ BAD_FRAME_IND_UL_CS1+ BAD_FRAME_IND_UL_CS2+ BAD_FRAME_IND_UL_UNACK+ IGNOR_RLC_DATA_BL_UL_DUE_BSN,

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

/50/3600


Unit: erlang hour

Figure 645. GPRS traffic sum, S9PS (trf_95a)

PS territory utilisation, S10.5PS (trf_96b)

Use: Used on BTS level. Indicates how big a portion of the PSterritory has been used. If the utilisation percentage is high,increasing the CDEF parameter setting should be considered.





Known problems: Dummy blocks on DL make this PI show too high a value(fixed in CD6.0: RLC_MAC_cntrl_blocks_DL does notcontain dummy blocks anymore).1) If there are very few timeslots in the GPRS territory, thisKPI can show a high value even if there is only one activeuser.2) The denominator is slightly incorrect if extended TRXswere used.

100*(RLC blocks transmitted / (block transmission capacity) % =

Data blocks transmitted # greater one chosen, DL or UL100* ------------------------------------------------------------- % =


sum(max of (

rlc_data_blocks_ul_cs1+ rlc_data_blocks_ul_cs2+ rlc_mac_cntrl_blocks_ul+ BAD_FRAME_IND_UL_CS1+ BAD_FRAME_IND_UL_CS2+ BAD_FRAME_IND_UL_UNACK+ IGNOR_RLC_DATA_BL_UL_DUE_BSN,+(

sum over MCS-1 (xx)+sum over MCS-2 (xx)+sum over MCS-3 (xx)+sum over MCS-4 (xx)+sum over MCS-5 (xx)+sum over MCS-6 (xx)+sum over MCS-7 (xx/2)+sum over MCS-8 (xx/2)+sum over MCS-9 (xx/2)),

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)+(

sum over MCS-1 (yy)+sum over MCS-2 (yy)+sum over MCS-3 (yy)+sum over MCS-4 (yy)+sum over MCS-5 (yy)+sum over MCS-6 (yy)+sum over MCS-7 (yy/2)+sum over MCS-8 (yy/2)+sum over MCS-9 (yy/2)

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

ava_16a *sum(a.period_duration*60)*50

Where xx=



c.(UL_RLC_BLOCKS_IN_ACK_MODE+RETRANS_RLC_DATA_BLOCKS_UL+BAD_RLCVALID_HDR_UL_UNACK+UL_RLC_BLOCKS_IN_UNACK_MODE)

yy=c.(DL_RLC_BLOCKS_IN_ACK_MODE+ RETRANS_RLC_DATA_BLOCKS_DL+ DL_RLC_BLOCKS_IN_UNACK_MODE)

Counters from table(s):a= p_nbsc_res_availb= p_nbsc_packet_control_unitc= p_nbsc_coding_scheme

Figure 646. PS territory utilisation, S10.5PS (trf_96b)

Average CS traffic, normal TRXs, erlang, S2 (trf_97)

Use: This is a speech (circuit switched) traffic indicator. Speechtraffic is a basic indicator needed to show how much TCHcapacity is used. When traffic increases without an increase incapacity, the probability of blocking increases. Therelationship between traffic, capacity and blocking for speechtraffic is described in the formula known as Erlang B.This KPI includes all types of CS traffic (single TCH,HSCSD) on normal TRXs.

sum(decode(trx_type,0,ave_busy_tch))-----------------------------------sum(decode(trx_type,0,res_av_denom14))


Unit: erlang

Figure 647. Average CS traffic, normal TRXs, erlang, S2 (trf_97)

Average CS traffic, extended TRXs S2 (trf_98)

Use: This is a speech (circuit switched) traffic indicator. Speechtraffic is a basic indicator needed to show how much TCHcapacity is used. When the traffic increases without increasein capacity, the probability of blocking grows.The relationship between traffic, capacity and blocking inspeech traffic is described in the formula known as Erlang B.This KPI includes all types of CS traffic (single TCH,HSCSD) on extended TRXs

sum(decode(trx_type,1,ave_busy_tch))-----------------------------------sum(decode(trx_type,1,res_av_denom14))




Unit: erlang

Figure 648. Average CS traffic, extended TRXs S2 (trf_98)

Average HSCSD traffic, normal TRXs, S7HS (trf_99)

Note: HSCSD uses FR.

sum(decode(trx_type,0,ave_busy_tch_hscsd_numer))------------------------------------------------sum(decode(trx_type,0,ave_busy_tch_hscsd_denom))


Unit: erlang

Figure 649. Average HSCSD traffic, normal TRXs, S7HS (trf_99)

Average HSCSD traffic, extended TRXs, S7HS (trf_100)


sum(decode(trx_type,1,ave_busy_tch_hscsd_numer))------------------------------------------------sum(decode(trx_type,1,ave_busy_tch_hscsd_denom))


Unit: erlang

Figure 650. Average HSCSD traffic, extended TRXs, S7HS (trf_100)

Average HTCH traffic, normal TRXs, S7HS (trf_102)

Use: Total of speech (circuit switched) in single timeslot half ratetraffic over normal TRXs

Avg(decode,trx_type,0,ave_tch_busy_half))

Unit: erlang

Figure 651. Average HTCH traffic, normal TRXs, S7HS (trf_102)



Average HTCH traffic, extended TRXs, S7HS (trf_103)

Use: Total of speech (circuit switched) in single timeslot half ratetraffic over extended TRXs

nvl(Avg(decode,trx_type,1,ave_tch_busy_half)),0)

Unit: erlang

Figure 652. Average HTCH traffic, extended TRXs, S7HS (trf_103)

Average HSCSD main channel traffic, normal TRXs, S7HS (trf_104)


sum(decode(trx_type,0,ave_hscsd_users_numer))--------------------------------------------sum(decode(trx_type,0,ave_hscsd_users_denom))


Figure 653. Average HSCSD main channel traffic, normal TRXs, S7HS (trf_104)

Average HSCSD main channel traffic, extended TRXs, S7HS (trf_105)


sum(decode(trx_type,0,ave_hscsd_users_numer))--------------------------------------------sum(decode(trx_type,0,ave_hscsd_users_denom))


Unit: erlang

Figure 654. Average HSCSD main channel traffic, extended TRXs, S7HS(trf_105)

Average FTCH single traffic, normal TRXs, S7HS (trf_107)

trf_97 ; all CS traffic on normal TRXs-trf_102 ; single HR traffic on normal TRXs-trf_99 ; all HSCSD (FR) traffic on normal TRXs

Unit: erlang

Figure 655. Average FTCH single traffic, normal TRXs, S7HS (trf_107)



Average FTCH single traffic, extended TRXs, S7HS (trf_108)

trf_98 ; all CS traffic on extended TRXs-trf_103 ; single HR traffic on extended TRXs-trf_100 ; all HSCSD (FR) traffic on extended TRXs

Unit: erlang

Figure 656. Average FTCH single traffic, extended TRXs, S7HS (trf_108)

Peak busy TCH on normal TRXs (trf_109)

Use: This PI is an important traffic load indicator on the cell level.By following this and reacting proactively, blocking can beavoided in cells in which the traffic grows smoothly.

max(decode(trx_type,0,peak_busy_tch))


Figure 657. Peak busy TCH on normal TRXs (trf_109)

Peak busy TCH on normal TRXs (trf_110)

Use: This PI is an important traffic load indicator on the cell level.By following this and reacting proactively, blocking can beavoided in cells in which the traffic grows smoothly.

max(decode(trx_type,1,peak_busy_tch))


Figure 658. Peak busy TCH on normal TRXs (trf_110)

Normal TCH usage % for CS (trf_111)

Use: Indicates how many % of the total normal TCH capacityavailable has been used for CS traffic on average.

trf_97= 100* ----------------------- %

ava_28+ava_16a-ava_17a

Figure 659. Normal TCH usage % for CS (trf_111)



Normal TCH usage ratio for CS, normal TRX (trf_111b)

Use: Indicates how many % of the total available TCH normalcapacity has been used for CS traffic on average.

trf_202= 100 * ---------------------------

ava_52 + ava_44 - ava_51

Unit: %

Figure 660. Normal TCH usage ratio for CS, normal TRX (trf_111b)

Normal TCH usage % for CS (trf_112)

Use: Indicates how many % of the total normal TCH capacityavailable has been used for CS traffic on average.

trf_98= 100* ------------ %

ava_29

Unit: %

Figure 661. Normal TCH usage % for CS (trf_112)

Normal TCH usage ratio for CS, extended TRXs (trf_112a)

Use: Indicates how many % of the total available TCH normalcapacity has been used for CS traffic on average.

trf_170= 100* ------------

ava_53

Unit: %

Figure 662. Normal TCH usage ratio for CS, extended TRXs (trf_112a)

CS call samples, non-AMR call (trf_113)

Use: Indicates how many call samples (sampling interval 480 ms)of non-AMR calls have been detected.

sum(nvl(FREQ_UL_QUAL0,0)+ + nvl(FREQ_UL_QUAL7,0)

-sum(nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0)

+ nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_2_UL_RXQUAL_7,0)+ nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_3_UL_RXQUAL_7,0)+ nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_4_UL_RXQUAL_7,0)

nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0)



+ nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_4_UL_RXQUAL_6,0)))

Figure 663. CS call samples, non-AMR call (trf_113)

CS call samples, non-AMR call (trf_113a)

Use: Indicates how many call samples (sampling interval 480 ms)of non-AMR calls have been detected.


-sum(nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0)

+ nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_2_UL_RXQUAL_7,0)+ nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_3_UL_RXQUAL_7,0)+ nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_4_UL_RXQUAL_7,0)

nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_4_UL_RXQUAL_7,0)

))


Unit: Numbers

Figure 664. CS call samples, non-AMR call (trf_113a)

CS call samples, AMR call (trf_114)

Use: Indicates TCH use (sampling interval 480 ms) for AMR calls.

sum(nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0)


nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0)

+ nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_4_UL_RXQUAL_6,0))

Figure 665. CS call samples, AMR call (trf_114)

CS call samples, AMR call (trf_114a)

Use: Indicates TCH use (sampling interval 480ms) for AMR calls.sum(

nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0)




nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_4_UL_RXQUAL_7,0)

)


Unit: Numbers

Figure 666. CS call samples, AMR call (trf_114a)

TCH traffic time, non-AMR calls (trf_115)

Use: Indicates TCH use (sampling interval 480 ms) for non-AMRcalls.



-sum(nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0)


nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_4_UL_RXQUAL_6,0)

)*0,48/3600

Unit: erlang hours

Figure 667. TCH traffic time, non-AMR calls (trf_115)

TCH traffic time, non-AMR calls (trf_115a)

Use: Indicates TCH use (sampling interval 480 ms) for non-AMRcalls.


-sum(nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0)


nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0)



+ nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_4_UL_RXQUAL_7,0))*0,48/3600


Unit: erlang hour

Figure 668. TCH traffic time, non-AMR calls (trf_115a)

TCH traffic time, AMR calls (trf_116)

Use: Indicates TCH use (sampling interval 480 ms) for AMR calls.Known problems: In a high load situation (OMU link) it is possible that all call

time is not measured. In other words, call time can show alower value than it has in reality.Also, in the beginning of a call and in handover, two samplesare lost, showing a shorter time than in reality.

trf_114*0,48/36000

Unit: erlang hour

Figure 669. TCH traffic time, AMR calls (trf_116)

TCH traffic time, FR AMR calls (trf_117)

Use: Indicates TCH use (sampling interval 480 ms) for full rateAMR.


,sum(nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0)


)*0,48/3600

Unit: erlang hours

Figure 670. TCH traffic time, FR AMR calls (trf_117)



TCH traffic time, HR AMR calls (trf_118)


Sum(nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0)

+ nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_4_UL_RXQUAL_6,0))

*0,48/3600

Unit: erlang hours

Figure 671. TCH traffic time, HR AMR calls (trf_118)

TCH traffic time, HR AMR calls (trf_118a)

Known problems: In a high load situation (OMU link) it is possible that all calltime is not measured. This means that the call time can showa lower value than it has in reality. Also, in the beginning of acall and in handover, two samples are lost, showing a shortertime than in reality.

Sum(nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0)

+ nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ .. + nvl(AMR_HR_MODE_4_UL_RXQUAL_7,0)

)*0,48/3600

Unit: erlang hours

Figure 672. TCH traffic time, HR AMR calls (trf_118a)

TCH traffic time, all calls (trf_119)


sum(nvl(FREQ_UL_QUAL0,0)+ .. + nvl(FREQ_UL_QUAL7,0))*0,48/3600

Unit: erlang hours

Figure 673. TCH traffic time, all calls (trf_119)



TCH traffic share of non-AMR calls (trf_120)

100*Trf_115/Trf_119

Unit: erlang hours

Figure 674. TCH traffic share of non-AMR calls (trf_120)

TCH traffic share of non-AMR calls (trf_120a)

100*trf_115a/trf_119

Unit: %

Figure 675. TCH traffic share of non-AMR calls (trf_120a)

TCH traffic share of FR AMR calls (trf_121)

100*Trf_117/Trf_119

Unit: erlang hours

Figure 676. TCH traffic share of FR AMR calls (trf_121)

TCH traffic share of HR AMR calls (trf_122)

100*Trf_118/Trf_119

Unit: erlang hours

Figure 677. TCH traffic share of HR AMR calls (trf_122)

TCH traffic share of HR AMR calls (trf_122a)

100*trf_118a/trf_119

Unit: %

Figure 678. TCH traffic share of HR AMR calls (trf_122a)



Average effective UL timeslot throughput per TBF, S10PS (trf_123)

Use; Indicates the net data rate per used timeslot and per TBF. Thelower, the value the more loaded is the GPRS territory and theless service the MS users receive.The numerator does not contain the RLC header bytes neitherdoes the MAC header because the aim is to count data volumefrom the user’s point of view as close as possible.

Known problems: 1) The numerator of trf_72d is not yet pure user data but asclose to that as we can see from BSC counters.2) See problems of the denominator.

UL payload data (kilobit) / UL time for data transfer (sec)------------------------------------------------------------- =

Avg UL TBF per tsl

trf_72d= ----------

tbf_37b


unit: Kbps / tsl/TBF

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

Average effective DL timeslot throughput per TBF, S10PS (trf_124)

Use; Indicates the net data rate per used timeslot and per TBF. Thelower the value, the more loaded is the GPRS territory and theless service the MS users receive.The numerator does not contain the RLC header bytes neitherthe MAC header because the aim is to count the data volumefrom the user point of view as close as possible.

Known problems: 1) The numerator of trf_73d is not yet pure user data but asclose as we can see from BSC counters.2) Retransmitted blocks due to other reasons than NACK arenot counted in any of the RLC counters. In DL direction theseretransmissions occur when TBF release is delayed.3) If there is, for example, only one TBF on a timeslot, someRLC blocks can be retransmitted before an ACK is received.These blocks are not counted in any of the RLC counters.4) Counter rlc_mac_cntrl_blocks_dl also containsdummy blocks until CD.6.1.5) See problems of the denominator.

DL payload data (kilobit) / DL time for data transfer (sec)------------------------------------------------------------- =

Avg DL TBF per tsl

trf_73d= --------



tbf_38b


unit: Kbps / tsl / TB

Figure 680. Average effective DL timeslot throughput per TBF, S10PS (trf_124)

MS specific flowrate (trf_125)

Use; This is the flowrate of LLC PDUs. It can be counted persegment and priority class.

8/1000 * ave_ms_bssgp_flow_rate_sum-----------------------------------ave_ms_bssgp_flow_rate_den

Counters from table(s):p_nbsc_qosUnit: kbit/sec

Figure 681. MS specific flowrate (trf_125)

Total RLC payload data (Kbytes), MCS-n, S10.5PS (trf_131)

Sum over MCS-n (UL_RLC_BLOCKS_IN_ACK_MODE +UL_RLC_BLOCKS_IN_UNACK_MODE +DL_RLC_BLOCKS_IN_ACK_MODE +DL_RLC_BLOCKS_IN_UNACK_MODE) * nn / 1024

where n can be from 1 to 9 and nn is the multiplier for each Coding Scheme,i.e. RLC Data Block payload in bytes.nn for each MCS:MCS-122MCS-228MCS-337MCS-444MCS-556MCS-674MCS-756MCS-868MCS-974)




Unit: Kbytes

Figure 682. Total RLC payload data (Kbytes), MCS-n, S10.5PS (trf_131)

UL RLC data MCS-n, S10.5PS (trf_140)

sum over MCS-n (xx) *nn / 1024

(where xx =UL_RLC_BLOCKS_IN_ACK_MODE +RETRANS_RLC_DATA_BLOCKS_UL +BAD_RLC_VALID_HDR_UL_UNACK +UL_RLC_BLOCKS_IN_UNACK_MODE)


(where nn is multiplier for each Coding Scheme, i.e. RLC Data Block payload in bytesnn for each MCS:MCS-1 22MCS-2 28MCS-3 37MCS-4 44MCS-5 56MCS-6 74MCS-7 56MCS-8 68MCS-9 74)


Figure 683. UL RLC data MCS-n, S10.5PS (trf_140)

DL RLC data MCS-n, S10.5PS (trf_141)

Use: DL RLC dData MCS1

sum over MCS-n (xx) * nn / 1024

where xx =(DL_RLC_BLOCKS_IN_ACK_MODE +RETRANS_RLC_DATA_BLOCKS_DL +DL_RLC_BLOCKS_IN_UNACK_MODE)


(where nn is multiplier for each Coding Scheme, i.e. RLC Data Block payload in bytesnn for each MCS:MCS-1 22MCS-2 28MCS-3 37MCS-4 44MCS-5 56MCS-6 74MCS-7 56MCS-8 68



MCS-9 74)


Unit: kbytes

Figure 684. DL RLC data MCS-n, S10.5PS (trf_141)

Normal TCH usage % for EGPRS, S10.5PS (trf_160)

Use: Indicates how many % of the total available normal TCHcapacity has been used for EGPRS traffic on average. Usedfor trend analysis.

Capacity used by EGPRS traffic------------------------------Total TCH normal capacity

trf_158= 100 * ---------------- %

ava_28 + ava_16aUnit: %

Figure 685. Normal TCH usage % for EGPRS, S10.5PS (trf_160)

UL EGPRS traffic, S10.5PS (trf_161)

Use: Indicates the amount of resources (timeslots) that the GPRStraffic data consumes on average during the period. Thisinformation is useful, for example, in forecasting the need toextend capacity.

Known problems: See trf_78c.

Actual UL data throughput (blocks)----------------------------------------------------------------- =Number of blocks equivalent to 1 tsl full use in each BTS of area

sum over MSC1-6 of( ul_rlc_blocks_in_ack_mode+ retrans_rlc_data_blocks_ul+ BAD_RLC_VALID_HDR_UL_ACK+ bad_rlc_valid_hdr_ul_unack+ ul_rlc_blocks_in_unack_mode)

+ sum over MSC7-9 of( ul_rlc_blocks_in_ack_mode+ retrans_rlc_data_blocks_ul+ BAD_RLC_VALID_HDR_UL_ACK+ bad_rlc_valid_hdr_ul_unack+ ul_rlc_blocks_in_unack_mode)/2

----------------------------------------------------------------------------------------

sum(period_duration*60)*50 ; 50 blocks /sec /tsl




Unit: tsl (or erlang)

Figure 686. UL EGPRS traffic, S10.5PS (trf_161)

UL EGPRS traffic (trf_161g)

Use: For area level, this formula should first be collected for allBTSs in the area and then the results should be summed up forthe area. Indicates the amount of resources (timeslots) that theEGPRS traffic data consumes on average during the period.This information is useful, for example, in forecasting theneed for capacity extension. 50 blocks /sec /tsl is used toestimate timeslots.

actual UL data throughput (blocks)--------------------------------------------------------------- =nbr of blocks equivalent to 1 tsl full use in each BTS of area

sum over MCS0..6 of( a.ul_rlc_blocks_in_ack_mode+ a.BAD_RLC_VALID_HDR_UL_ACK+ a.bad_rlc_valid_hdr_ul_unack+ a.ul_rlc_blocks_in_unack_mode+ a.bad_rlc_bad_hdr_ul_ack+ a.bad_rlc_bad_hdr_ul_unack)

+sum over MCS7..9 of( a.ul_rlc_blocks_in_ack_mode+ a.bad_rlc_bad_hdr_ul_ack+ a.bad_rlc_bad_hdr_ul_unack+ a.BAD_RLC_VALID_HDR_UL_ACK+ a.bad_rlc_valid_hdr_ul_unack+ a.ul_rlc_blocks_in_unack_mode)/2+ rlc_mac_cntrl_blocks_ul_egprs

----------------------------------------------------------------------------------avg(period_duration*60)*count( distinct period_start_time)*50 ;50 blocks /sec /tsl

Counters from table(s):a = p_nbsc_coding_schemeb = p_nbsc_packet_control_unit

rlc_mac_cntrl_blocks_ul_egprs =trf_204a

b.rlc_mac_cntrl_blocks_ul * -------------------trf_203 + trf_204a

Unit:TSL (or erlang)

Figure 687. UL EGPRS traffic (trf_161g)

UL EGPRS traffic (trf_161h)

Description: UL EGPRS traffic in Erlangs.



Use: For area level, this formula should first be collected for allBTSs in the area and then the results should be summed up forthe area. It indicates the amount of resources (timeslots) theEGPRS traffic data consumes on average during the period.This information is useful, for example, in forecasting theneed for capacity extension. 50 blocks /sec /tsl is used toestimate timeslots.RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS

actual UL data throughput (blocks)--------------------------------------------------------------- =nbr of blocks equivalent to 1 tsl full use in each BTS of area

sum over MCS0..6 of( a.ul_rlc_blocks_in_ack_mode+ a.BAD_RLC_VALID_HDR_UL_ACK+ a.bad_rlc_valid_hdr_ul_unack+ a.ul_rlc_blocks_in_unack_mode+ a.bad_rlc_bad_hdr_ul_ack+ a.bad_rlc_bad_hdr_ul_unack)

+sum over MCS7..9 of( a.ul_rlc_blocks_in_ack_mode+ a.bad_rlc_bad_hdr_ul_ack+ a.bad_rlc_bad_hdr_ul_unack+ a.BAD_RLC_VALID_HDR_UL_ACK+ a.bad_rlc_valid_hdr_ul_unack+ a.ul_rlc_blocks_in_unack_mode)/2+ egprs_ul_ctrl_blocks+ [ignor rlc radio bl ul due bsn egprs]

----------------------------------------------------------------------------------avg(period_duration*60)*count( distinct period_start_time)*50 ;50 blocks /sec /tsl

Counters from table(s):a = p_nbsc_coding_schemeb = p_nbsc_packet_control_unit

[ignor rlc radio bl ul due bsn egprs] =

trf_204ignor_rlc_data_bl_ul_due_bsn * X * ----------------

trf_203b + trf_204

Where X = 0.5 * A/(A+B) + 1 * B/(A+B)

A=sum over MCS7...9 of(a.ul_rlc_blocks_in_ack_mode+a.ul_rlc_blocks_in_unack_mode)B=sum over MCS1...6 of(a.ul_rlc_blocks_in_ack_mode+a.ul_rlc_blocks_in_unack_mode)

Unit: TSL(or erlang)

Figure 688. UL EGPRS traffic (trf_161h)

DL EGPRS traffic, S10.5PS (trf_162)

Use: Indicates the amount of resources (timeslots) the DL EGPRStraffic data consumes. This information is useful, for example,in forecasting the need to extend capacity.

Actual DL data throughput (blocks)----------------------------------------------------------------- =



Number of blocks equivalent to 1 tsl full use in each BTS of area

sum over msc1…6( dl_rlc_blocks_in_ack_mode+ retrans_rlc_data_blocks_dl+ dl_rlc_blocks_in_unack_mode)

+ sum over msc7…9 of( dl_rlc_blocks_in_ack_mode+ retrans_rlc_data_blocks_dl+ dl_rlc_blocks_in_unack_mode)/2

----------------------------------------------------sum(period_duration*60)*50 ;50 blocks /sec /tsl

Counters from table(s):p_nsbc_coding_scheme

Figure 689. DL EGPRS traffic, S10.5PS (trf_162)

DL EGPRS traffic (trf_162d)

Use: For area level, this formula should be first collected for allBTSs in an area and then results should be summed up for thearea. Indicates the amount of resources (timeslots) that the DLEGPRS traffic data consumes. This information is useful, forexample, in forecasting the need for capacity extension.

Known problems: RLC/MAC Control block counters are not available forEGPRS and estimation is used.

Actual DL data throughput (blocks)------------------------------------------------------------ =nbr of blocks equivalent to 1 tsl full use in each BTS of area

sum over mcs1..6 of (dl_rlc_blocks_in_ack_mode+retrans_rlc_data_blocks_dl+dl_rlc_blocks_in_unack_mode)

+ sum over mcs7..9 of (dl_rlc_blocks_in_ack_mode+retrans_rlc_data_blocks_dl+dl_rlc_blocks_in_unack_mode)/2

+ (rlc_mac_cntrl_blocks_ul - egprs_ul_ctrl_blocks)--------------------------------------------------sum(period_duration*60)*50 ;50 blocks /sec /tsl

Counters from table(s):p_nsbc_coding_scheme


Figure 690. DL EGPRS traffic (trf_162d)



DL EGPRS traffic (trf_162e)

Use: For area level, this formula should first be collected for allBTSs in the area and then the results should be summed up forthe area. The formula indicates the amount of resources(timeslots) consumed by DL EGPRS traffic. This informationis useful, for example, in forecasting the need for capacityextension.

Known problems: Counter rlc_mac_cntrl_blocks_dl calculates also GPRScontrol blocks but this formula is for EGPRS only, so thecounter rlc_mac_cntrl_blocks_dl is not needed at all becausein S11.5 there is a new counter egprs_dl_ctrl_blocks thatcalculates RLC/MAC control blocks sent to MS with EGPRSTBF.


Formula: (NetAct names)sum over mcs1..6 of (

a.dl_rlc_blocks_in_ack_mode+ a.retrans_rlc_data_blocks_dl+ a.dl_rlc_blocks_in_unack_mode)

+ sum over mcs7..9 of (a.dl_rlc_blocks_in_ack_mode+ a.retrans_rlc_data_blocks_dl+ a.dl_rlc_blocks_in_unack_mode)/2

+ (b.rlc_mac_cntrl_blocks_dl - b.egprs_dl_ctrl_blocks)--------------------------------------------------sum(b.period_duration*60)*50 ;50 blocks /sec /tsl

Counters from table(s):a = p_nsbc_coding_schemeb = p_nsbc_packet_control_unit


Figure 691. DL EGPRS traffic (trf_162e)

DL EGPRS traffic (trf_162f)

Use: For area level, this formula should first be collected for allBTSs in the area and then the results should be summed up forthe area. the formula indicates the amount of resources(timeslots) consumed by DL EGPRS traffic data. Thisinformation is useful, for example, in forecasting the need forcapacity extension.RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS


sum over mcs1..6 of (a.dl_rlc_blocks_in_ack_mode



+ a.retrans_rlc_data_blocks_dl+ a.dl_rlc_blocks_in_unack_mode)

+ sum over mcs7..9 of (a.dl_rlc_blocks_in_ack_mode+ a.retrans_rlc_data_blocks_dl+ a.dl_rlc_blocks_in_unack_mode)/2

+ (b.egprs_dl_ctrl_blocks)--------------------------------------------------sum(b.period_duration*60)*50 ;50 blocks /sec /tsl

Counters from table(s):a = p_nsbc_coding_schemeb = p_nsbc_packet_control_unit


Figure 692. DL EGPRS traffic (trf_162f)

Average SDCCH traffic, Area, S1 (trf_168)

Note: For area (or segment) level, first use the formula for all theBTSs and then sum this formula over all underlying BTSs,keeping in mind the note above.

SDCCH used time / period duration =

(sum(a.ave_sdcch_hold_tim) / (avg(a.res_av_denom16)* 100 * count( distinct period_start_time))

)* sum(b.sdcch_assign + b.sdcch_ho_seiz + b.tch_seiz_due_sdcch_con)------------------------------------------------------------------

sum(a.period_duration*60)

Counters from table(s):a = p_nbsc_res_availb = p_nbsc_traffic

Unit: Erlang

Figure 693. Average SDCCH traffic, Area, S1 (trf_168)

Average SDCCH hold time, S10.5 (trf_169)

Description: Average SDCCH hold time on area level.Use: The holding time may change due to modification of the

timers or perhaps software. This time is part of the call setuptime.

Experiences on use: The counters receive the value of zero if the BTS is locked.Typically the values range from 2 to 3 seconds and over 4seconds with satellite Abis.

sum(ave_sdcch_hold_tim)--------------------------------------------------------- secavg(res_av_denom16)*100*count(distinct period_start_time)




Unit: seconds

Figure 694. Average SDCCH hold time, S10.5 (trf_169)

Average CS traffic, extended TRXs (trf_170)

Use: This is a speech (circuit switched) traffic indicator. Speechtraffic is a basic indicator needed to see how much TCHcapacity is consumed. When the traffic increases without theincrease of the capacity, the probability of blocking grows.The relationship between traffic, capacity and blocking isdescribed for speech traffic in the formula known as Erlang B.This KPI includes all types of CS traffic (single TCH,HSCSD) on extended TRXs.

sum(decode(trx_type,1,ave_busy_tch))-----------------------------------avg(decode(trx_type,1,res_av_denom14)) * count(distinct period_start_time)


Unit: erlang

Figure 695. Average CS traffic, extended TRXs (trf_170)

Average FTCH hold time, S11.5 (trf_172)

Description: Average FTCH hold time on area levelUse: The holding time may change due to modification of the

timers or perhaps software. You can use this PI to follow theimpact of the modifications.

Experiences on use: The counters receive the value zero if the BTS is locked.The value is highly dependent on the number of handoversthat, again, are dependent on the network plan.

sum(ave_ftch_hold_tim)--------------------------------------------------------- secavg(res_av_denom17)*100*count(distinct period_start_time)


Unit: sec

Figure 696. Average FTCH hold time, S11.5 (trf_172)



Average FTCH single traffic, S7 (trf_192)

trf_189 ; FTCH single traffic on normal TRXs+ trf_190 ; FTCH single traffic on extended TRXs

Unit: erlang

Figure 697. Average FTCH single traffic, S7 (trf_192)

Average HTCH traffic, Area S7HS (trf_193)

Use: Total of speech (circuit switched) single timeslot half ratetraffic over normal and extended TRXs.

Note: On BTS level. For area (or segment) level, first use theformula for all the BTSs and then sum this formula over allunderlying BTSs.

trf_175 ; HTCH traffic, normal TRXs+ trf_176 ; HTCH traffic, extended TRXs

Unit: erlang

Figure 698. Average HTCH traffic, Area S7HS (trf_193)

Average HSCSD main channel traffic, Area S7HS (trf_194)

Use: On BTS level. For area (or segment) level, first use theformula for all the BTSs and then sum this formula over allunderlying BTSs.

trf_177 ; HSCSD main channel traffic, normal TRXs+ trf_178 ; HSCSD main channel traffic, extended TRXs


Unit: erlang

Figure 699. Average HSCSD main channel traffic, Area S7HS (trf_194)

Average HSCSD subchannel traffic, Area S7HS (trf_195)

Use: On BTS level. For area (or segment) level, first use theformula for all the BTSs and then sum this formula over allunderlying BTSs.


trf_188 ; HSCSD total traffic, normal TRXs+ trf_191 ; HSCSD total traffic, extended TRXs- trf_177 ; HSCSD main channel traffic, normal TRXs



- trf_178 ; HSCSD main channel traffic, extended TRXs


Unit: erlang

Figure 700. Average HSCSD subchannel traffic, Area S7HS (trf_195)

Total TCH seizure time (call time, hours), Area, (trf_196)

Note: 1. See trf_24b.

(sum(period_duration * ave_busy_tch)--------------------------------------------------------avg(res_av_denom14) * count (distinct period_start_time))/60


Unit = hour (Erlang hour)

Figure 701. Total TCH seizure time (call time, hours), Area, (trf_196)

Normal TCH usage % for CS, Area, (trf_197)

Use: Indicates how many % of the total available normal TCHcapacity has been used for CS traffic on average. Used fortrend analysis.

Capacity used by CS traffic----------------------------total normal TCH capacity

trf_202= 100 * ----------------- %

ava_52 + ava_44

Figure 702. Normal TCH usage % for CS, Area, (trf_197)

Normal TCH usage % for PS, Area, S10.5PS (trf_198)

Description: Percentage of TCH usage for GPRS and EGPRS.Use: Indicates how many % of the total available normal TCH

capacity has been used for PS traffic on average. Used fortrend analysis.

Capacity used by GPRS traffic / total TCH normal capacity

trf_95= 100 * ---------------- %

ava_52 + ava_44



Unit: %

Figure 703. Normal TCH usage % for PS, Area, S10.5PS (trf_198)

Normal TCH usage % for EGPRS, S10.5 (trf_199)

Use: Indicates how many % of the total available normal TCHcapacity has been used for EGPRS traffic on average. Usedfor trend analysis.

Capacity used by EGPRS traffic------------------------------Total TCH normal capacity

trf_158= 100 * ----------------- %

ava_52 + ava_44

Unit: %

Figure 704. Normal TCH usage % for EGPRS, S10.5 (trf_199)

Free TCH %, S10.5PS (trf_200)

Description: Percentage of free TCH capacity.Use: Most useful on BTS level in connection with trf_83 and

trf_84a. The combined (PS+CS traffic) BH value trend can beused for dimensioning.Indicates how many % of the total available TCH capacity hasnot been used on average. If free TCH % approaches 0 the MSusers start to experience call blocking and/or that GPRSthroughput slows down.

Known problems: Because the measurement period is usually 60 minutes, thevalue cannot be used for spotting momentary problems ratherthe trend only.

100 - TCH usage % for CS - TCH usage % for PS= 100 - trf_197 - trf_198Unit: %

Figure 705. Free TCH %, S10.5PS (trf_200)

GPRS territory utilisation, Area, S9PS (trf_201)

Use: Area level. Indicates how big a portion of the GPRS territoryhas been used.If the utilisation % is high, increasing the CDEF parametersetting should be considered.





Known problems: Dummy blocks on DL make this PI show too high a value(fixed in CD6.0: RLC_MAC_cntrl_blocks_DL does notcontain dummy blocks anymore).

Known problems: 1) If there are very few timeslots in the GPRS territory, thisKPI can show a high value even if there is only one activeuser.2) The denominator is slightly incorrect if extended TRXswere used.

100 *(RLC blocks transmitted / (block transmission capacity) % =

Data blocks transmitted # greater one chosen, DL or UL100 * ------------------------------------------------------------ % =

(available GPRS channel time in sec)* (nbr of blocks per sec)sum(max of (

b.rlc_data_blocks_ul_cs1+ b.rlc_data_blocks_ul_cs2+ b.rlc_mac_cntrl_blocks_ul+ b.BAD_FRAME_IND_UL_CS1+ b.BAD_FRAME_IND_UL_CS2+ b.BAD_FRAME_IND_UL_UNACK+ b.IGNOR_RLC_DATA_BL_UL_DUE_BSN

or b.rlc_data_blocks_dl_cs1+ b.rlc_data_blocks_dl_cs2+ b.rlc_mac_cntrl_blocks_dl+ b.RETRA_RLC_DATA_BLOCKS_DL_CS1+ b.RETRA_RLC_DATA_BLOCKS_DL_CS2))

100 * ------------------------------------------ %a.ava_44 * sum(a.period_duration*60)*50

Counters from table(s):a= p_nbsc_res_availb= p_nbsc_packet_control_unit

Figure 706. GPRS territory utilisation, Area, S9PS (trf_201)

GPRS territory utilisation (trf_201a)

Use: Used on area level. Indicates how big a portion of the GPRSterritory has been used. If the utilisation percentage is high,increasing the CDEF parameter setting should be considered.




Known problems: 1) If there are very few timeslots in the GPRS territory, thisKPI can show a high value even if there is only one activeuser.2) The denominator is slightly incorrect if extended TRXswere used.

100*(RLC blocks transmitted / (block transmission capacity) =

Data blocks transmitted # greater one chosen, DL or UL100* --------------------------------------------------- =


sum(max of (

b.rlc_data_blocks_ul_cs1+ b.rlc_data_blocks_ul_cs2+ b.rlc_mac_cntrl_blocks_ul+ b.BAD_FRAME_IND_UL_CS1+ b.BAD_FRAME_IND_UL_CS2+ b.BAD_FRAME_IND_UL_UNACK+ b.IGNOR_RLC_DATA_BL_UL_DUE_BSN+ sum over MCS-11..12 (c.ul_rlc_blocks_in_ack_mode

+ c.ul_rlc_blocks_in_unack_mode+ c.bad_rlc_valid_hdr_ul_unack+ c.bad_rlc_valid_hdr_ul_ack+ c.bad_rlc_bad_hdr_ul_ack),

b.rlc_data_blocks_dl_cs1+ b.rlc_data_blocks_dl_cs2+ b.rlc_mac_cntrl_blocks_dl+ b.RETRA_RLC_DATA_BLOCKS_DL_CS1+ b.RETRA_RLC_DATA_BLOCKS_DL_CS2+ sum over MCS-11..12 (c.dl_rlc_blocks_in_ack_mode

+ c.dl_rlc_blocks_in_unack_mode+ c.retrans_rlc_data_blocks_dl)

)100*-------------------------------------------------------------------

a.ava_44 *sum(a.period_duration*60)*50

Counters from table(s):a= p_nbsc_res_availb= p_nbsc_packet_control_unitc= p_nbsc_coding_scheme

Unit: %

Figure 707. GPRS territory utilisation (trf_201a)

Average CS traffic, normal TRXs, erlang, Area, S2 (trf_202)

Use: This is a speech (circuit switched) traffic indicator. Speechtraffic is a basic indicator needed to see how much TCHcapacity is consumed. When the traffic increases without theincrease of the capacity, the probability of blocking grows.The relationship between traffic, capacity and blocking isdescribed for speech traffic in the formula known as Erlang B.This KPI includes all types of CS traffic (single TCH,HSCSD) on normal TRXs.

sum(decode(trx_type,0,ave_busy_tch))



---------------------------------------------------------------------------avg(decode(trx_type,0, res_av_denom14)) * count(distinct period_start_time)


Unit: erlang

Figure 708. Average CS traffic, normal TRXs, erlang, Area, S2 (trf_202)

UL GPRS traffic (trf_205b)

Description: UL GPRS Traffic in ErlangsUse: Indicates the amount of resources (timeslots) the GPRS traffic

(excluding EDGE traffic) consumes on average during theperiod. This information is useful, for example, in forecastingthe need for capacity extension. 50 blocks /sec /tsl is used toestimate timeslots.

Actual UL data throughput (blocks)------------------------------------------------------------- =nbr of blocks equivalent to 1 tsl full use in each BTS of area

sum(a.rlc_data_blocks_ul_cs1+ a.rlc_data_blocks_ul_cs2+ a.bad_frame_ind_ul_cs1+ a.bad_frame_ind_ul_cs2+ a.bad_frame_ind_ul_unack+ sum over MCS-11..12 (b.ul_rlc_blocks_in_ack_mode

+ b.ul_rlc_blocks_in_unack_mode+ b.bad_rlc_valid_hdr_ul_unack+ b.bad_rlc_bad_hdr_ul_unack+ b.bad_rlc_valid_hdr_ul_ack+ b.bad_rlc_bad_hdr_ul_ack)

+ (a.rlc_mac_cntrl_blocks_ul - a.egprs_ul_ctrl_blocks)+ [ignor rlc data bl ul due bsn gprs])

----------------------------------------------------sum(period_duration*60)*50 ; 50 blocks /sec /tsl

[ignor rlc data bl ul due bsn gprs] =

trf_203ba.ignor_rlc_data_bl_ul_due_bsn * -----------------

trf_203b + trf_204



Figure 709. UL GPRS traffic (trf_205b)

DL GPRS traffic in EGPRS BTS (trf_208b)

Description: DL GPRS Traffic in Erlangs.



Use: Indicates the amount of resources (timeslots) that the GPRStraffic data in EGPRS capable BTS consumes on averageduring the period. This information is useful, for example, inforecasting the need for capacity extension. 50 blocks /sec /tslis used to estimate timeslots.

Actual DL data throughput (blocks)------------------------------------------------------------- =nbr of blocks equivalent to 1 tsl full use in each BTS of area

sum(a.rlc_data_blocks_dl_cs1+ a.rlc_data_blocks_dl_cs2+ a.retra_rlc_data_blocks_dl_cs1+ a.retra_rlc_data_blocks_dl_cs2)+ sum over MCS-11..12 (b.dl_rlc_blocks_in_ack_mode

+ b.dl_rlc_blocks_in_unack_mode+ b.retrans_rlc_data_blocks_dl)

+ (rlc_mac_cntrl_blocks_dl - egprs_dl_ctrl_blocks)------------------------------------------------------

sum(period_duration*60)*50; 50 blocks /sec /tsl



Figure 710. DL GPRS traffic in EGPRS BTS (trf_208b)

GPRS UL Payload Data (trf_212c)

Use: Indicates all GPRS payload data on UL.

All GPRS UL Payload data (kbytes) =

sum(a.rlc_data_blocks_ul_cs1 *20+ a.rlc_data_blocks_ul_cs2 *30+ sum over MCS-

11(b.ul_rlc_blocks_in_ack_mode+b.ul_rlc_blocks_in_unack_mode)*36 ;CS3+ sum over MCS-

12(b.ul_rlc_blocks_in_ack_mode+b.ul_rlc_blocks_in_unack_mode)*50 ;CS4)/1024


Unit: kB

Figure 711. GPRS UL Payload Data (trf_212c)

GPRS DL Payload Data (trf_213c)

Use: Indicates all GPRS Payload data on DL

All GPRS DL Payload data (kbytes) =



sum(a.rlc_data_blocks_dl_cs1 *20+ a.rlc_data_blocks_dl_cs2 *30+ sum over MCS-

11(b.dl_rlc_blocks_in_ack_mode+b.dl_rlc_blocks_in_unack_mode)*36 ;CS3+ sum over MCS-

12(b.dl_rlc_blocks_in_ack_mode+b.dl_rlc_blocks_in_unack_mode)*50 ;CS4)/1024


Figure 712. GPRS DL Payload Data (trf_213c)

EGPRS UL payload data (trf_214a)

Use: Indicates all EGPRS payload data on UL.RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS

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

) / 1024where xx = (UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE)


Unit: kB

Figure 713. EGPRS UL payload data (trf_214a)

EGPRS DL payload data (trf_215a)

Use: Indicates all EGPRS payload data on DL.RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS

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

) / 1024where xx = (DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE)




p_nbsc_coding_scheme

Figure 714. EGPRS DL payload data (trf_215a)

Average GPRS UL LLC throughput (trf_216)

Description: Average LLC Thoughput for GPRS UL. Note: PFC durationis counted for only the time when PFC is active (i.e. datatransfer ongoing). PFC Active Duration counters are in theunit of 10ms; therefore the multiplier of 100 is used.

Use: Best available indicator of user perceived data rate from BSCstatistics.

Sum(LLC_BYTES_UL- LLC_BYTES_UL_EGPRS) * 8 *100

----------------------------------Sum(PFC_ACTIVE_TIME_UL_SUM

- UL_ACT_PFC_DUR_FOR_EGPRS) * 1000

Counters from table(s):p_nbsc_eqos

Unit:kbps

Figure 715. Average GPRS UL LLC throughput (trf_216)

Average GPRS DL LLC throughput (trf_217)

Description: Average LLC Thoughput for GPRS DL. Note: PFC durationis counted for only the time when PFC is active (i.e. datatransfer ongoing). PFC Active Duration counters are in theunit of 10ms; therefore the multiplier of 100 is used.


Sum(LLC_BYTES_DL- LLC_BYTES_DL_EGPRS) * 8 * 100

------------------------------------Sum(PFC_ACTIVE_TIME_DL_SUM

- DL_ACT_PFC_DUR_FOR_EGPRS) * 1000

Counters from table(s):p_nbsc_eqosUnit: kbps

Figure 716. Average GPRS DL LLC throughput (trf_217)



Average EGPRS UL LLC throughput (trf_218)

Description: Average LLC Thoughput for EGPRS UL. Note: PFC durationis counted for only the time when PFC is active (i.e. datatransfer ongoing). PFC Active Duration counters are in theunit of 10ms; therefore the multiplier of 100 is used.


Sum(LLC_BYTES_UL_EGPRS) * 8 * 100------------------------------------Sum(UL_ACT_PFC_DUR_FOR_EGPRS) * 1000

Counters from table(s):p_nbsc_eqosUnit: kbps

Figure 717. Average EGPRS UL LLC throughput (trf_218)

Average EGPRS DL LLC throughput (trf_219)

Description: Average LLC Thoughput for EGPRS DL. Note: PFC durationis counted for only the time when PFC is active (i.e. datatransfer ongoing). PFC Active Duration counters are in theunit of 10ms; therefore the multiplier of 100 is used.


Sum(LLC_BYTES_DL_EGPRS) * 8 * 100------------------------------------Sum(DL_ACT_PFC_DUR_FOR_EGPRS) * 1000


Unit:kbps

Figure 718. Average EGPRS DL LLC throughput (trf_219)

Total LLC data volume (trf_220)

Description: Total transferred LLC data volume in UL and DL.

Sum(LLC_BYTES_UL + LLC_BYTES_DL)--------------------------------

1024




Unit:kB

Figure 719. Total LLC data volume (trf_220)

Share of GPRS UL in total LLC data volume (trf_225)

Use: Indicates the percentage of GPRS UL in total LLC datavolume.

trf_221-------- * 100trf_220


Unit: %

Figure 720. Share of GPRS UL in total LLC data volume (trf_225)

Share of GPRS DL in total LLC data volume (trf_226)

Use: Indicates the percentage of GPRS DL in total LLC datavolume.

trf_222-------- * 100trf_220


Unit: %

Figure 721. Share of GPRS DL in total LLC data volume (trf_226)

Share of EGPRS UL in total LLC data volume (trf_227)

Use: Indicates the percentage of EGPRS UL in total LLC datavolume.

trf_223-------- * 100trf_220




p_nbsc_eqosUnit: %

Figure 722. Share of EGPRS UL in total LLC data volume (trf_227)

Share of EGPRS DL in total LLC data volume (trf_228)

Use: Indicates the percentage of EGPRS DL in total LLC datavolume.

trf_224-------- * 100trf_220

Counters from table(s):p_nbsc_eqosUnit: %

Figure 723. Share of EGPRS DL in total LLC data volume (trf_228)

LLC data volume for TRECn (trf_229)

Description: Total transferred LLC data volume in UL and DL.Use: Indicates the total LLC data volume for TRECn.Note: Following is the mapping of TREC to TC_THP_PFI and ARP

columns in p_nbsc_eqos measurement.TREC 0 Background TC_THP_PFI=4 ARP=3TREC 1 Interactive THP3 TC_THP_PFI=3 ARP=3TREC 2 Interactive THP2 TC_THP_PFI=2 ARP=2TREC 3 Interactive THP1 TC_THP_PFI=1 ARP=1TREC 4 Streaming TC_THP_PFI=0 ARP=3TREC 5 Streaming TC_THP_PFI=0 ARP=2TREC 6 Streaming TC_THP_PFI=0 ARP=1Best-effort TC_THP_PFI=5Signalling TC_THP_PFI=6SMS TC_THP_PFI=7

Sum(LLC_BYTES_UL + LLC_BYTES_DL)--------------------------------

1024

where TC_THP_PFI = 0…7 AND ARP = 1…3


Unit: kB

Figure 724. LLC data volume for TRECn (trf_229)



Share of TRECn in total LLC data volume (trf_230)

Use: Share of TRECn in total transferred LLC data volume.

trf_229-------- * 100trf_220


Unit: %

Figure 725. Share of TRECn in total LLC data volume (trf_230)

Average effective ACK GPRS UL throughput per used TSL (trf_233c)

Use: Indicates the impact of radio link quality on net data rate perused timeslot considering retransmissions and coding schemeselection. The lower the value, the poorer the radio linkquality causing retransmissions and use of lower codingschemes. The numerator does not contain the RLC headerbytes, neither does the MAC header, because the aim is tocount data volume from the users point of view as close aspossible. The denominator is built on the fact that one timeslotcan carry 50 RLC blocks per second.RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS

Known problems: 1) The numerator is not yet pure user data but as close to thatas we can see from BSC counters.2) See rlc_10b for more details on counter update scenarios.3) See trf_72i for more information.4) The formula assumes that all GRPS unack RLC traffic isusing CS1. With PCU2, GPRS unack RLC traffic can useCS1-4. If there is a significant amount of GRPS unack RLCtraffic with CS2, the formula will give too high values

GPRS UL payload ACK data in (kilobits)----------------------------------------- =GPRS UL time for ACK data transfer (sec)

sum((a.rlc_data_blocks_ul_cs1- a.rlc_data_blocks_ul_unack)*20+ a.rlc_data_blocks_ul_cs2*30+ sum over MCS-11 (b.ul_rlc_blocks_in_ack_mode)*36+ sum over MCS-12 (b.ul_rlc_blocks_in_ack_mode)*50)*8 /1000

-----------------------------------------------------------------sum(a.rlc_data_blocks_ul_cs1

- a.rlc_data_blocks_ul_unack+ a.rlc_data_blocks_ul_cs2+ a.retra_data_blocks_ul_cs1+ a.retra_data_blocks_ul_cs2+ sum over MCS-11..12(b.ul_rlc_blocks_in_ack_mode

+ b.retrans_rlc_data_blocks_ul)) /50




Unit: kbps/TSL

Figure 726. Average effective ACK GPRS UL throughput per used TSL(trf_233c)

Average effective ACK EGPRS UL throughput per used TSL (trf_234)

Use: Indicates the impact of radio link quality on net data rate perused timeslot considering retransmissions and coding schemeselection. The lower the value the poorer the radio link qualitycausing retransmissions and use of lower coding schemes.The numerator does not contain the RLC header bytes neitherthe does the MAC header because the aim is to count datavolume from the users point of view as close as possible. Thedenominator is built on the fact that one timeslot can carry 50RLC blocks per second.RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS1) The numerator is not yet pure user data but as close to thatas we can see from BSC counters.2) See rlc_10b for more details on counter update scenarios.3) See trf_72i for more information.

EGPRS UL payload ACK data in (kilobits)--------------------------------------- =EGPRS UL time for ACK data transfer (sec)

(sum over MCS-1 (xx)*22+ sum over MCS-2 (xx)*28+ sum over MCS-3 (xx)*37+ sum over MCS-4 (xx)*44+ sum over MCS-5 (xx)*56+ sum over MCS-6 (xx)*74+ sum over MCS-7 (xx)*56+ sum over MCS-8 (xx)*68+ sum over MCS-9 (xx)*74)*8/1000---------------------------------------sum over MCS1..6 of (yy)/50+ sum over MCS7..9 of (yy)/2 /50

wherexx = b.ul_rlc_blocks_in_ack_modeyy = b.ul_rlc_blocks_in_ack_mode

+ b.retrans_rlc_data_blocks_ul


Unit: kbps/TSL

Figure 727. Average effective ACK EGPRS UL throughput per used TSL(trf_234)



Average effective ACK GPRS DL throughput per used TSL (trf_235b)

Use: Indicates the impact of radio link quality on net data rate perused timeslot considering retransmissions and coding schemeselection. The lower the value the poorer the radio link qualitycausing retransmissions and use of lower coding schemes.The numerator does not contain the RLC header bytes neitherthe does the MAC header because the aim is to count datavolume from the users point of view as close as possible. Thedenominator is built on the fact that one timeslot can carry 50RLC blocks per second. RECOMMENDED SUMMARYLEVELS: Area; SEG; BTS

Known problems: 1) The numerator is not yet pure user data but as close to thatas we can see from BSC counters.2) Retransmitted blocks due to other reasons than NACK arenot counted in any of the RLC-counters. In DL direction theseretransmissions occur when the TBF release is delayed.3) If there is only one TBF on a timeslot, for example, someRLC blocks can be retransmitted before an ACK is received.These blocks are not counted in any of the RLC counters.4) See trf_73h for more details.5) The formula assumes that all GRPS unack RLC traffic isusing CS1. With PCU2, GPRS unack RLC traffic can useCS1-4. If there is a significant amount of GRPS unack RLCtraffic with CS2, the formula will give too high values.

GPRS ACK DL payload data in (kilobits)---------------------------------------- =GPRS ACK DL time for data transfer (sec)

sum((a.rlc_data_blocks_dl_CS1- a.rlc_data_blocks_dl_unack)*20+ a.rlc_data_blocks_dl_CS2*30+ sum over MCS-11 (b.DL_RLC_BLOCKS_IN_ACK_MODE)*36+ sum over MCS-12 (b.DL_RLC_BLOCKS_IN_ACK_MODE)*50)*8 /1000

---------------------------------------------------------------sum (a.rlc_data_blocks_dl_cs1

- a.rlc_data_blocks_dl_unack+ a.rlc_data_blocks_dl_cs2+ RETRA_RLC_DATA_BLOCKS_DL_CS1+ RETRA_RLC_DATA_BLOCKS_DL_CS2+ sum over MCS-11..12(b.DL_RLC_BLOCKS_IN_ACK_MODE

+ b.RETRANS_RLC_DATA_BLOCKS_DL)) /50


Unit: kbps/TSL

Figure 728. Average effective ACK GPRS DL throughput per used TSL(trf_235b)



PS traffic (trf_237b)

Use: The formula is used to find out the maximum amount of PSdata traffic during a measurement period.RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS

PS Erlangs = max( UL PS Erlangs, DL PS Erlangs) =

Max((a.rlc_data_blocks_ul_cs1+ a.rlc_data_blocks_ul_cs2+ a.BAD_FRAME_IND_UL_CS1+ a.BAD_FRAME_IND_UL_CS2+ a.BAD_FRAME_IND_UL_UNACK+ a.rlc_mac_cntrl_blocks_ul+ a.ignor_rlc_data_bl_ul_due_bsn * X+ sum over MCS0..6 of (b.ul_rlc_blocks_in_ack_mode

+ b.ul_rlc_blocks_in_unack_mode+ b.bad_rlc_valid_hdr_ul_ack+ b.bad_rlc_valid_hdr_ul_unack+ b.bad_rlc_bad_hdr_ul_ack+ b.bad_rlc_bad_hdr_ul_unack)

+ sum over MCS7..9 of (b.ul_rlc_blocks_in_ack_mode+ b.ul_rlc_blocks_in_unack_mode+ b.bad_rlc_valid_hdr_ul_ack+ b.bad_rlc_valid_hdr_ul_unack+ b.bad_rlc_bad_hdr_ul_ack+ b.bad_rlc_bad_hdr_ul_unack)/2)

+ sum over MCS-11..12 of (b.ul_rlc_blocks_in_ack_mode+ b.bad_rlc_valid_hdr_ul_unack+ b.bad_rlc_valid_hdr_ul_ack+ b.bad_rlc_bad_hdr_ul_ack+ b.bad_rlc_bad_hdr_ul_unack+ b.ul_rlc_blocks_in_unack_mode)

--------------------------------------------------------------------------------,period_duration*60*50

(a.rlc_data_blocks_dl_cs1+ a.rlc_data_blocks_dl_cs2+ a.retra_rlc_data_blocks_dl_cs1+ a.retra_rlc_data_blocks_dl_cs2+ a.rlc_mac_cntrl_blocks_dl+ sum over mcs1..6 of (b.dl_rlc_blocks_in_ack_mode

+ b.dl_rlc_blocks_in_unack_mode+ b.retrans_rlc_data_blocks_dl)

+ sum over mcs7..9 of (b.dl_rlc_blocks_in_ack_mode+ b.dl_rlc_blocks_in_unack_mode+ b.retrans_rlc_data_blocks_dl)/2)

+ sum over MCS-11..12 of (b.dl_rlc_blocks_in_ack_mode+ b.dl_rlc_blocks_in_unack_mode+ b.retrans_rlc_data_blocks_dl))

--------------------------------------------------------------------------------period_duration*60*50)

Where X = 0.5 * A/(A+B) + 1 * B/(A+B)

A = sum over MCS7...9 of(b.ul_rlc_blocks_in_ack_mode + b.ul_rlc_blocks_in_unack_mode)B=(sum over MCS1...6 of(b.ul_rlc_blocks_in_ack_mode + b.ul_rlc_blocks_in_unack_mode))+ a.rlc_data_blocks_ul_cs1 + a.rlc_data_blocks_ul_cs2 + sum

over MCS-11..12 of (b.ul_rlc_blocks_in_ack_mode + b.ul_rlc_blocks_in_unack_mode)




Unit: Erlang

Figure 729. PS traffic (trf_237b)

Average UL PS traffic (trf_238)

Description: Average number of busy uplink GPRS channels.

ave_busy_gprs_ch_ul / ave_busy_gprs_ch_den


Unit: E

Figure 730. Average UL PS traffic (trf_238)

Average DL PS traffic (trf_239)

Description: Shows the average number of busy uplink GPRS channels.ave_busy_gprs_ch_dl / ave_busy_gprs_ch_den


Unit: E

Figure 731. Average DL PS traffic (trf_239)

2.27 Traffic directions

2.27.1 Mobile originated calls (moc)

SDCCH seizures for MO calls, S2 (moc_1)

Known problems: Includes supplementary services such as call divert.Includes SMS.

sum(succ_seiz_orig)


Figure 732. SDCCH seizures for MO calls, S2 (moc_1)



Note

Successful MO speech calls, S3 (moc_2)

Note: Triggered when a call is cleared. Excludes setup failures,TCH drops and TCH busy (congestion) cases.

Known problems: The measurement is on the BSC level.

sum(nbr_of_calls)where counter_id = 44

Counters from table(s):p_nbsc_cc_pm

Figure 733. Successful MO speech calls, S3 (moc_2)

Successful MO data calls, S3 (moc_3)

Note: See moc_2.Known problems: The measurement is on the BSC level.



Figure 734. Successful MO data calls, S3 (moc_3)

MO call success ratio, S6 (moc_4)

Note: See moc_2.Known problems: The measurement is on the BSC level.

MO call attempts are counted when MOCs are found on SDCCH. The numeratorexcludes setup failures, TCH drops and TCH busy (congestion) cases.

sum(nbr_of_calls) where counter_id = 44 /* MO call completed */100 * -----------------------------------------------------------------------

sum(nbr_of_calls) where counter_id = 38 /* MO call attempt */


Figure 735. MO call success ratio, S6 (moc_4)



MO speech call attempts, S3 (moc_5)

Note: Triggered when a call is cleared. Excludes setup failures,TCH drops and TCH busy (congestion) cases.

Known problems: The measurement is on the BSC level.



Figure 736. MO speech call attempts, S3 (moc_5)

MO call bids, S2 (moc_6)

Known problems: Includes supplementary services such as call divert.Includes SMS.

sum(succ_seiz_orig+tch_moc)


Figure 737. MO call bids, S2 (moc_6)

2.27.2 Mobile terminated calls (mtc)

SDCCH seizures for MT calls, S2 (mtc_1)

Known problems: Includes SMS. See also moc_2.

sum(succ_seiz_term)


Figure 738. SDCCH seizures for MT calls, S2 (mtc_1)

Successful MT speech calls (mtc_2)

Note: See moc_2.Known problems: See moc_2.





Figure 739. Successful MT speech calls (mtc_2)

Successful MT data calls, S3 (mtc_3)




Figure 740. Successful MT data calls, S3 (mtc_3)

MT call success ratio, S6 (mtc_4)

Note: MT call attempts are counted when MTCs are found onSDCCH. The numerator excludes setup failures, TCH dropsand TCH busy (congestion) cases.

Known problems: See moc_2.

sum(nbr_of_calls) where counter_id = 43 /* MT call completed */100 * -----------------------------------------------------------------------

sum(nbr_of_calls) where counter_id = 37 /* MT call attempt */


Figure 741. MT call success ratio, S6 (mtc_4)

MT speech call attempts (mtc_5)




Figure 742. MT speech call attempts (mtc_5)



MT call attempts, S2 (mtc_6)

Use: Total number of calls bids with establishment cause ’MT’.Known problems: Includes SMS.

sum(succ_seiz_term+tch_mtc)


Figure 743. MT call attempts, S2 (mtc_6)

2.28 Paging (pgn)

Number of paging messages sent, S2 (pgn_1)

Known problems: The number of repagings cannot be separated.

sum(paging_msg_sent)


Figure 744. Number of paging messages sent, S2 (pgn_1)

Paging buffer size average, S1 (pgn_2)

Use: To have an indication on how close to problems the BTS hasbeen.

Known problems: It is difficult to say when the problems start. Even if thecounter 3018 does not yet show the 0 value, there may havebeen the situation in one or some of the buffers that thecapacity has run out.

avg(min_paging_buf)


Parameters related:Number of Blocks for AGCH (AG): e.g. = 2Number of MultiFrames (MFR): e.g. = 6

Formulas related:Nbr of paging groups = (3-AG)*MFR ;if combined control channelNbr of paging groups = (9-AG)*MFR ;if non-combined control channel

Paging_Buffer_Size = free buffers (max 8) * Nbr of paging groups



Min Paging Buffer (counter 3018) = min(Paging_Buffer_Space). = min(Paging_Buffer_Size/2)

Figure 745. Paging buffer size average, S1 (pgn_2)

Paging Buffer Space is sent by BTS in the CCH_Load_Ind message to a BSCevery 30 s. A BSC sends current paging load as Paging_Buffer_Size to astatistical unit. The minimum value of this is recorded as counter 3018. If MinPaging Buffer (counter 3018) equals to zero, paging blocking has occurred.

Average paging buffer space, S1 (pgn_3)

Use: Average remaining free space for paging commands in GSMbuffer area (part of GPRS buffer area). When there are nopagings, this PI shows the capacity of the buffer.

Known problems: Incorrect if CCCH load ind interval has changed during theobservation period.

avg(ave_pch_load/res_acc_denom2)


Figure 746. Average paging buffer space, S1 (pgn_3)

Average free space of paging GSM buffer area, S1 (pgn_3a)

Use: Average remaining free space for paging commands in GSMbuffer area (part of GPRS buffer area). When there are nopagings this PI shows the capacity of the buffer.

sum(ave_pch_load)/sum(res_acc_denom2)


Figure 747. Average free space of paging GSM buffer area, S1 (pgn_3a)

Paging success ratio, S1 (pgn_4)

Known problems: Due to the very dynamic behaviour it seems that this formulais not useful.

sum over all BTS in LA (succ_seiz_term + tch_mtc)100* ------------------------------------------------------- %

sum over LA(paging_msg_sent) / sum over LA (count of BTS)




Figure 748. Paging success ratio, S1 (pgn_4)

Average paging buffer air interface occupancy, S7 (pgn_5)

sum(ave_paging_buffer_capa_numer)----------------------------------sum(ave_paging_buffer_capa_denom)


Figure 749. Average paging buffer air interface occupancy, S7 (pgn_5)

Average paging buffer Gb occupancy, S7PS (pgn_6)

sum(ave_paging_gb_buf_sum)---------------------------sum(ave_paging_gb_buf_den)


Figure 750. Average paging buffer Gb occupancy, S7PS (pgn_6)

Average air interface DRX buffer load, due to paging, S7 (pgn_7)

Use: The DRX buffer handles messages that are sent in the DRXcycle, i.e. pagings and DRX access grants. This counterdescribes the DRX buffer load resulting from pagingmessages.

sum(ave_paging_load_air_sum)---------------------------sum(ave_paging_load_air_den)


Figure 751. Average air interface DRX buffer load, due to paging, S7 (pgn_7)

Average air interface DRX buffer load, due to DRX AG, S7 (pgn_8)

Use: The DRX buffer handles messages that are sent in DRX cycle,i.e. pagings and DRX access grants. This counter describesDRX buffer load resulting from DRX AG messages (e.g. anImm.Ass.for DL TBF establishment.)



sum(ave_drx_agch_load_air_sum)-------------------------------sum(ave_drx_agch_load_air_den)


Figure 752. Average air interface DRX buffer load, due to DRX AG, S7 (pgn_8)

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

Use: The non-DRX buffer handles messages that are sentimmediately. This counter describes the non-DRX buffer loadresulting from non-DRX (i.e. immediate) access grants suchas CS Imm.Ass. and UL TBF (Imm.Ass. sent as an answer toRACH).

sum(ave_non_drx_agch_load_air_sum)-----------------------------------sum(ave_non_drx_agch_load_air_den)


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

Average free space of paging GPRS buffer area, S9 (pgn_10)

Use: Average remaining free space for paging commands in theGSM buffer area. When there are no pagings, this PI showsthe capacity of the GPRS buffer area.

sum(AVE_PCH_GB_LOAD_ON_CCCH_SUM)----------------------------------sum(AVE_PCH_GB_LOAD_ON_CCCH_DEN)


Figure 754. Average free space of paging GPRS buffer area, S9 (pgn_10)

Average paging buffer Gb occupancy, S7PS (pgn_11)

Use: Area or BTS level.

sum(ave_paging_gb_buf_sum)-------------------------------------------------------------avg(ave_paging_gb_buf_den) * count(distinct period_start_time)




Figure 755. Average paging buffer Gb occupancy, S7PS (pgn_11)

2.29 Short message service (sms)

SMS establishment failure % (sms_1)

100* unsuccessful SMS establishments / all SMS establishments =

sum(unsucc_TCH_sms_est+unsucc_SDCCH_sms_est)100* ------------------------------------------------------------------ %

sum(succ_TCH_sms_est+unsucc_TCH_sms_est+succ_SDCCH_sms_est+unsucc_SDCCH_sms_est)


Figure 756. SMS establishment failure % (sms_1)

SMS TCH establishment failure % (sms_2)

sum(unsucc_TCH_sms_est)100 * ------------------------------------------- %

sum(succ_TCH_sms_est+unsucc_TCH_sms_est)


Figure 757. SMS TCH establishment failure % (sms_2)

SMS SDCCH establishment failure % (sms_3)

Use: MOC: Instead of the sending SETUP message, the MS startsSMS by sending SABM with SAPI 3 to BTS, and a newestablishment indication is generated.MTC: Instead of the sending SETUP message, the MSC startsSMS by sending a CP DATA message to BSC and BSC sendsan ESTABLISH REQUEST to BTS, then MS answers by theUA message, and the ESTABLISH CONFIRM message isgenerated.SMS fails if the message data is corrupted, timer expires whenwaiting for an establishment confirmation, or if an errorindication or release indication is received.

sum(unsucc_sdcch_sms_est)100 * -------------------------------------------- %



sum(succ_sdcch_sms_est+unsucc_sdcch_sms_est)


Figure 758. SMS SDCCH establishment failure % (sms_3)

SMS establishment attempts (sms_4)

sum(succ_tch_sms_est+unsucc_tch_sms_est+succ_sdcch_sms_est+unsucc_sdcch_sms_est)


Figure 759. SMS establishment attempts (sms_4)

SMS SDCCH establishment attempts (sms_5)

sum(succ_sdcch_sms_est+unsucc_sdcch_sms_est)


Figure 760. SMS SDCCH establishment attempts (sms_5)

SMS TCH establishment attempts (sms_6)

sum(succ_TCH_sms_est+unsucc_TCH_sms_est)


Figure 761. SMS TCH establishment attempts (sms_6)

2.30 Directed retry (dr)

DR, outgoing attempts, S3 (dr_1)

sum(msc_o_sdcch_tch_at + bsc_o_sdcch_tch_at)


Figure 762. DR, outgoing attempts, S3 (dr_1)



DR attempts, S3 (dr_1a)

Use: Includes all DR cases (to another cell and intra-cell).

sum(cause_dir_retry)


Figure 763. DR attempts, S3 (dr_1a)

DR, incoming attempts, S3 (dr_2)

sum(msc_i_sdcch_tch_at + bsc_i_sdcch_tch_at)


Figure 764. DR, incoming attempts, S3 (dr_2)

DR, outgoing success to another cell, S3 (dr_3)

sum(msc_o_sdcch_tch + bsc_o_sdcch_tch)


Figure 765. DR, outgoing success to another cell, S3 (dr_3)

DR, incoming success from another cell, S3 (dr_4)

sum(msc_i_sdcch_tch + bsc_i_sdcch_tch)


Figure 766. DR, incoming success from another cell, S3 (dr_4)

DR, intra-cell successful HO, S3 (dr_5)

Use: Triggered by• S6 feature ’TCH assignment to super-reuse in IUO’• S7 feature ’Direct access to super-reuse TRX’

sum(cell_sdcch_tch)




Figure 767. DR, intra-cell successful HO, S3 (dr_5)

% of new calls successfully handed over to another cell by DR, S3 (dr_6)

sum(msc_o_sdcch_tch + bsc_o_sdcch_tch)100 * --------------------------------------

sum(tch_call_req)


Figure 768. % of new calls successfully handed over to another cell by DR, S3(dr_6)

DR, outgoing to another cell, failed, S3 (dr_7)

sum(msc_o_sdcch_tch_at + bsc_o_sdcch_tch_at- msc_o_sdcch_tch + bsc_o_sdcch_tch)


Figure 769. DR, outgoing to another cell, failed, S3 (dr_7)

DR, intra-cell failed, S3 (dr_8)

Use: Triggered by• S6 feature ’TCH assignment to super-reuse in IUO’• S7 feature ’Direct access to super-reuse TRX’

sum(cell_sdcch_tch_at- cell_sdcch_tch)


Figure 770. DR, intra-cell failed, S3 (dr_8)

2.31 Availability (ava)

TCH availability %, S4 (ava_1a)

Use: Failures (downtime) of TRXs cause loss of TCH and affectthis KPI.



Known problems: 1)If TRXs are locked and BTSs and BCFs are unlocked, theTCHs appear as unavailable. This means that both the systemand the user can affect this KPI and make it less useful.2)This PI does not take HTCH into consideration.

available TCH100 * ------------------ %

all TCH

sum(ave_avail_full_TCH/res_av_denom2)=100 * ------------------------------------------------------------ %

sum(ave_avail_full_TCH/res_av_denom2)+sum(ave_non_avail_TCH)


Figure 771. TCH availability %, S4 (ava_1a)

TCH availability %, S9 (ava_1c)


Known problems: 1) If TRXs are locked and BTSs and BCFs are unlocked, theTCHs appear as unavailable. This means that both the systemand the user can affect this KPI and make it less useful.2) The formula leaves out the timeslots reserved for GPRS.

available TCH100 * ------------------ %

all TCH

sum(ave_avail_TCH_sum/ave_avail_TCH_den)=100 * --------------------------------------------------------------- %

sum(ave_avail_TCH_sum/ave_avail_TCH_den)+sum(ave_non_avail_TCH)


Figure 772. TCH availability %, S9 (ava_1c)

TCH availability %, S9 (ava_1d)


Known problems: If TRXs are locked and BTSs and BCFs are unlocked, theTCHs appear as unavailable. This means that both the systemand the user can affect this KPI and make it less useful.

Note: This KPI has to be counted separately for extended andnormal area. Trx type: 0 = normal, 1 = extended.

available TCH100 * ------------------------- %

all TCH (traffic and GPRS)



sum(ave_avail_TCH_sum/ave_avail_TCH_den+ ave_GPRS_channels_sum/ave_GPRS_channels_den)

=100 * ---------------------------------------------------------------- %sum(ave_avail_TCH_sum/ave_avail_TCH_den

+ ave_GPRS_channels_sum/ave_GPRS_channels_den+ave_non_avail_TCH)


Figure 773. TCH availability %, S9 (ava_1d)

TCH availability %, S9 (ava_1e)




available TCH100 * -------------------------- %


ava_15 + ava_16b= 100 * ---------------------------- %

ava_15 + ava_16b + uav_11a


Figure 774. TCH availability %, S9 (ava_1e)

TCH availability ratio (ava_1g)


Known problems: If TRXs are locked and BTSs and BCFs are unlocked, theTCHs appear unavailable. This means that both the systemand the user can affect this KPI and make it less useful.

Note: The KPI has to be counted separately for extended and normalarea (trx_type: 0 = normal, 1 = extended).

available TCH100 * ------------------------- %


sum(ave_avail_TCH_sum/ave_avail_TCH_den+ ave_GPRS_channels_sum/ave_GPRS_channels_den)

=100 * ------------------------------------------------------------------ %sum(ave_avail_TCH_sum/ave_avail_TCH_den

+ ave_GPRS_channels_sum/ave_GPRS_channels_den



+ ave_non_avail_tch_timeslot/non_avail_tch_denom)


Unit: %

Figure 775. TCH availability ratio (ava_1g)

Average available TCH, S1 (ava_2)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, theTCHs appear as unavailable.

Note: 1. This KPI has to be counted separately for extended andnormal area (trx_type: 0 = normal, 1 = extended).2. For area (or segment) level, first use the formula for all theBTSs and then sum this formula over all underlying BTSs,keeping in mind the note above.

sum(ave_avail_full_TCH)-------------------------sum(res_av_denom2)


Figure 776. Average available TCH, S1 (ava_2)

Average available SDCCH, S1 (ava_3)

Note: 1)This KPI has to be counted separately for extended andnormal area (trx_type: 0 = normal, 1 = extended).2)For area (or segment) level, first use the formula for all theBTSs and then sum this formula over all underlying BTSs,keeping in mind the note above.

sum(ave_sdcch_sub)/sum(res_av_denom3)


Figure 777. Average available SDCCH, S1 (ava_3)

SDCCH availability %, S4 (ava_4)

Use: Indicates how big a share of all SDCCH resources has beenavailable for traffic. Failures (downtime) of TRX containingSDCCH affect this KPI.

Known problems: Affected by locked TRX under unlocked BCF and BTS.




sum(ave_sdcch_sub/res_av_denom3)100 * --------------------------------------------------------- %

sum(ave_sdcch_sub/res_av_denom3)+sum(ave_non_avail_sdcch)


Figure 778. SDCCH availability %, S4 (ava_4)

SDCCH availability %, S4 (ava_4a)

Use: Indicates how big a share of all SDCCH resources has beenavailable for traffic. Failures (downtime) of TRX containingSDCCH affect this KPI.

Known problems: Affected by locked TRX under unlocked BCF and BTS.Note: This KPI has to be counted separately for extended and

normal area. Trx type: 0 = normal, 1 = extended.ava_3

100 * ---------------- %ava_3 + uav_10


Figure 779. SDCCH availability %, S4 (ava_4a)

Average available FTCH in area, S1 (ava_5)

sum_over_area(

sum_over_BTS(ave_avail_full_TCH)/sum_over_BTS(res_av_denom2))


Figure 780. Average available FTCH in area, S1 (ava_5)

DMR availability %, S6 (ava_6)

sum(avail_time)100 * ---------------- %

sum(total_time)



Counters from table(s):p_nbsc_dmr

Figure 781. DMR availability %, S6 (ava_6)

DN2 availability %, S6 (ava_7)

sum(avail_time)100 * --------------- %

sum(total_time)

Counters from table(s):p_nbsc_dn2

Figure 782. DN2 availability %, S6 (ava_7)

TRU availability %, S6 (ava_8)

sum(avail_time)100 * --------------- %

sum(total_time)

Counters from table(s):p_nbsc_tru_bie

Figure 783. TRU availability %, S6 (ava_8)

Average defined HTCH, S1 (ava_9)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked,the TCHs appear as unavailable.

Avg(ave_tch_avail_half)


Figure 784. Average defined HTCH, S1 (ava_9)

SC ET availability %, S7 (ava_10)

sum(avail_time)100 * --------------- %

sum(total_time)



Counters from table(s):p_nbsc_et_bsc.

Figure 785. SC ET availability %, S7 (ava_10)

BSC ET availability %, S7 (ava_11)

sum(remote_avail_time)100 * --------------------- %

sum(remote_total_time)

Counters from table(s):p_nbsc_et_bsc.

Figure 786. BSC ET availability %, S7 (ava_11)

SC TCSM availability %, S7 (ava_12)

sum(avail_time)100 * --------------- %

sum(total_time)

Counters from table(s):p_nbsc_et_tcsm.

Figure 787. SC TCSM availability %, S7 (ava_12)

BSC TCSM availability %, S7 (ava_13)

sum(remote_avail_time)100 * --------------------- %

sum(remote_total_time)

Counters from table(s):p_nbsc_et_tcsm.

Figure 788. BSC TCSM availability %, S7 (ava_13)

TRE availability %, S6 (ava_14)

sum(avail_time)100 * --------------- %

sum(total_time)



Counters from table(s):p_nbsc_tre.

Figure 789. TRE availability %, S6 (ava_14)

Average CS territory, S9 (ava_15)

Use: Used on BTS level. It indicates the average number of TCHsavailable for circuit switched traffic (CS).For area (orsegment) level, first use the formula for all the BTSs and thensum this formula over all underlying BTSs.Note: This is not the same as the total capacity available forCS traffic, which is defined as ava_21. If CS traffic grows, thePS territory can diminish to what is defined as dedicatedterritory and give space for CS traffic.This figure is affected by:1)The settings of BTS-parameters CDEF and CDED2)Changes in capacity:a) TRX locked or unlocked by the operator. If TRXs arelocked and BTSs and BCFs are unlocked, the TCHs of thatTRX appear as unavailable.b) TRX disabled by BSC due to fatal faults.Upgrades and downgrades of territory by BSC according totraffic needs

Known problems: If extended cells are used, this KPI shows correct value onlyonly on the BTS/trx_type level

sum(ave_avail_TCH_sum)------------------------sum(ave_avail_TCH_den)


Unit: timeslots

Figure 790. Average CS territory, S9 (ava_15)

Average PS territory, S9PS (ava_16a)

Use: BTS level.Shows the actual average territory available for packetswitched (PS) traffic.The value can be used for tuning the CDEF parameter.This figure is affected by1) The settings of BTS parameters CDEF and CDED2)Changes of capacity



a) TRX locked or unlocked by the operator. If TRXs arelocked and BTSs and BCFs are unlocked, the TCHs of thatTRX appear as unavailable.b) TRX disabled by BSC due to fatal faults3) Upgrades and downgrades of territory by BSC according totraffic needs

Known problems: GPRS timeslots can only be in normal TRXs.

sum(decode(trx_type,0,ave_GPRS_channels_sum))----------------------------------------------sum(decode(trx_type,0,ave_GPRS_channels_den))


Unit: timeslot

Figure 791. Average PS territory, S9PS (ava_16a)

Average PS territory (ava_16b)

Use: BTS level. For area (or segment) level, first use the formulafor all the BTSs and then sum this formula over all underlyingBTSs.Shows the actual average territory available for packetswitched (PS) traffic.The value can be used for tuning the CDEF parameter.This figure is affected by1) The settings of BTS parameters CDEF and CDED2)Changes of capacitya) TRX locked or unlocked by the operator. If TRXs arelocked and BTSs and BCFs are unlocked, the TCHs of thatTRX appear as unavailable.b) TRX disabled by BSC due to fatal faults3) Upgrades and downgrades of territory by BSC according totraffic needs


sum(decode(trx_type,0,ave_GPRS_channels_sum))--------------------------------------------------------------------------------sum(decode(trx_type,0, decode(ave_GPRS_channels_sum,0,0,ave_GPRS_channels_den)))


Unit: timeslot

Figure 792. Average PS territory (ava_16b)



Average available dedicated GPRS channels, S9PS (ava_17)

Use: BTS level.Indicates the average number of channels available only fordedicated PS (GPRS) traffic. This capacity is allocated bysetting the parameter CDED. In the case that there are nodedicated GPRS channels, throughput is not guaranteed, if CStraffic needs all the capacity.

Known problems: If extended TRXs are used, the values are correct only if thereport is on the BTS/TRX type level.

sum(ave_permanent_GPRS_ch_sum)--------------------------------sum(ave_permanent_GPRS_ch_den)


Figure 793. Average available dedicated GPRS channels, S9PS (ava_17)

Average available dedicated GPRS channels, S9PS (ava_17a)

Use: BTS level. For area (or segment) level, first use the formulafor all the BTSs and then sum this formula over all underlyingBTSs.Indicates the average number of channels available only fordedicated PS (GPRS) traffic. This capacity is allocated bysetting the parameter CDED. In the case that there are nodedicated GPRS channels, throughput is not guaranteed, if CStraffic needs all the capacity.


sum(decode(trx_type,0,ave_permanent_GPRS_ch_sum))-------------------------------------------------sum(decode(trx_type,0,ave_permanent_GPRS_ch_den))


Figure 794. Average available dedicated GPRS channels, S9PS (ava_17a)

TRE-SEL availability %, S6 (ava_20)

sum(avail_time)100 * --------------- %

sum(total_time)

Counters from table(s):p_nbsc_tre_sel

Figure 795. TRE-SEL availability %, S6 (ava_20)



Number of timeslots available for CS traffic, S9 (ava_21)

Use: BTS levelThis KPI shows all the available timeslots that are notdedicated for PS (GPRS), i.e. that can be used by CS traffic.Note that this is not the same as CS territory, which is definedas ava_15.

Known problems: Incorrect if extended TRXs were used.sum(ave_avail_TCH_sum) sum(ave_GPRS_channels_sum) sum(ave_permanent_GPRS_ch_sum)--------------------- + -------------------------- - ------------------------------sum(ave_avail_TCH_den) sum(ave_GPRS_channels_den) sum(ave_permanent_GPRS_ch_den)


Figure 796. Number of timeslots available for CS traffic, S9 (ava_21)

Number of timeslots available for CS traffic on normal TRXs, S9 (ava_21a)

Use: Used on BTS levelThis formula contains all the available timeslots that are notdedicated for PS (GPRS), i.e. that can be used by CS traffic onnormal TRXs.

ava_28 ; Pure CS TCHs on normal TRXs+ava_16a-ava_17a ; dynamic part of PS territory

Figure 797. Number of timeslots available for CS traffic on normal TRXs, S9(ava_21a)

Number of HR timeslots available, S9 (ava_22)

Use: Average number of timeslots available for half rate trafficonly

Known problems: Incorrect values if extended TRXs were used.

Sum(ave_avail_TCH_sum)/sum(ave_avail_TCH_den)-sum(ave_avail_full_TCH)/sum(res_av_denom2)


Figure 798. Number of HR timeslots available, S9 (ava_22)

Number of HR timeslots available, S9 (ava_22a)

Use: Average number of timeslots available for half rate trafficonly



Known problems: Incorrect values if extended TRXs used.

ava_30+ava_31


Unit: timeslots

Figure 799. Number of HR timeslots available, S9 (ava_22a)

Number of FR timeslots available, S9 (ava_23)

Use: Average number of timeslots available for full rate traffic only

Sum(ave_avail_TCH_sum)/sum(ave_avail_TCH_den) - avg(ave_tch_avail_half)/2


Figure 800. Number of FR timeslots available, S9 (ava_23)

Number of FR timeslots available, S9 (ava_23a)

Use: Average number of timeslots available for full rate traffic only

ava_32 ; FR timeslots on normal TRXs+ ava_33 ; FR timeslots on extended TRXs


Figure 801. Number of FR timeslots available, S9 (ava_23a)

Number of dual timeslots available, S9 (ava_24)

Use: Average number of timeslots available for dual (half rate orfull rate) traffic

Known problems: Incorrect values if extended TRXs were used.

sum(ave_avail_full_TCH)/sum(res_av_denom2) + avg(ave_tch_avail_half)/2)- Sum(ave_avail_TCH_sum)/sum(ave_avail_TCH_den)


Figure 802. Number of dual timeslots available, S9 (ava_24)



Number of dual timeslots available, S9 (ava_24a)

Use: Average number of timeslots available for dual (half rate orfull rate) traffic

ava_34 ; dual timeslots on normal TRXs+ ava_35 ; dual timeslots on extended TRXs


Figure 803. Number of dual timeslots available, S9 (ava_24a)

Average number of available TCH timeslots, S9 (ava_25a)

Use: Used on BTS level. Average number of TCH timeslots (bothCS and PS) available.For area (or segment) level, first use theformula for all the BTSs and then sum this formula over allunderlying BTSs.

ava_31 ; HR timeslots on extended TRXs+ ava_33 ; FR timeslots on extended TRXs+ ava_35 ; dual timeslots on extended TRXs+ ava_30 ; HR timeslots on normal TRXs+ ava_32 ; FR timeslots on normal TRXs+ ava_34; ; Dual timeslots on normal TRXs+ ava_16a ; PS territory timeslots (always on normal TRXs))


Figure 804. Average number of available TCH timeslots, S9 (ava_25a)

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

Use: Average number of timeslots available both CS and PStraffic.These are part of PS (GPRS) territory but if CS trafficneeds they can be taken to CS call use (territory downgrade)automatically by BSC.

Known problems: If extended TRXs were used, the values are correct only if thereport is on the BTS/TRX_type level.

ava_16-ava_17

Figure 805. Number of available TCH timeslots, PS and CS common, S9(ava_26)



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

Use: Average number of timeslots available for both CS and PStraffic. These are part of PS (GPRS) territory but if CS trafficneeds they can be taken to CS call use (territory downgrade)automatically by BSC. For area (or segment) level, first usethe formula for all the BTSs and then sum this formula overall underlying BTSs.

ava_16a-ava_17a

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

Average CS TCH in normal TRXs, S9 (ava_28)

Use: BTS level. Indicates the average number of TCHs availablefor circuit switched traffic (CS) in normal TRXs. Thiscapacity can also be used for PS traffic if CS traffic is low.IfCS traffic grows, the PS territory can diminish to what isdefined as dedicated territory and give space for CStraffic.This figure is affected byThis figure is affected by1) The settings of BTS-parameters CDEF andCDED2) Changes of capacity:a) TRX locked or unlocked by the operator. If TRXs arelocked and BTSs and BCFs are unlocked, the TCHs of thatparticular TRX appear as unavailable.b) TRX disabled by BSC due to fatal faults.3) Upgrades and downgrades of territory by BSC according totraffic needs.

sum(decode(trx_type,0,ave_avail_TCH_sum))/sum(decode(trx_type,0,ave_avail_TCH_den))


Unit: timeslots

Figure 807. Average CS TCH in normal TRXs, S9 (ava_28)

Average CS TCH in normal TRXs, S9 (ava_28a)

Use: BTS level. Indicates the average number of TCHs availablefor circuit switched traffic (CS) in normal TRXs. Thiscapacity can also be used for PS traffic if CS traffic is low.IfCS traffic grows, the PS territory can diminish to what isdefined as dedicated territory and give space for CS traffic.This figure is affected by1) The settings of BTS-parameters CDEF andCDED



2) Changes of capacity:a) TRX locked or unlocked by the operator. If TRXs arelocked and BTSs and BCFs are unlocked, the TCHs of thatparticular TRX appear as unavailable.b) TRX disabled by BSC due to fatal faults.3) Upgrades and downgrades of territory by BSC according totraffic needs.

sum(decode(trx_type,0,ave_avail_TCH_sum))-------------------------------------------------------------------------sum(decode(trx_type,0, decode(ave_avail_TCH_sum,0,0, ave_avail_TCH_den)))


Unit: TSL

Figure 808. Average CS TCH in normal TRXs, S9 (ava_28a)

Average available CS TCH in extended TRXs, S9 (ava_29)

Use: BTS level. Indicates the average number of TCHs availablefor circuit switched traffic (CS) in extended TRXs. Thiscapacity cannot be used for PS traffic.

nvl(sum(decode(trx_type,1,ave_avail_TCH_sum))/sum(decode(trx_type,1,ave_avail_TCH_den)),1)


Unit: timeslots

Figure 809. Average available CS TCH in extended TRXs, S9 (ava_29)

Number of HR tsls available, normal TRXs, S9 (ava_30)

Use: Average number of timeslots available for half rate trafficonly. On BTS level. For area (or segment) level, first use theformula for all the BTSs and then sum this formula over allunderlying BTSs.

Sum(decode(trx_type,0,ave_avail_TCH_sum))/sum(decode(trx_type,0,ave_avail_TCH_den))-sum(decode(trx_type,0,ave_avail_full_TCH))/sum(decode(trx_type,0,res_av_denom2))


Figure 810. Number of HR tsls available, normal TRXs, S9 (ava_30)



Number of HR tsls available, extended TRXs S9 (ava_31)

Use: Average number of timeslots available on extended TRXs forfull rate traffic only.Used on the BTS level. If used on the area level, it shows theaverage over extended cells only. For area (or segment) level,first use the formula for all the BTSs and then sum thisformula over all underlying BTSs.

nvl(Sum(decode(trx_type,1,ave_avail_TCH_sum))/sum(decode(trx_type,1,ave_avail_TCH_den))

-sum(decode(trx_type,1,ave_avail_full_TCH))/sum(decode(trx_type,1,res_av_denom2)),0)


Figure 811. Number of HR tsls available, extended TRXs S9 (ava_31)

Number of FR timeslots available, normal TRXs, S9 (ava_32)

Use: Average number of timeslots available on normal TRXs forfull rate traffic only. On BTS level. For area (or segment)level, first use the formula for all the BTSs and then sum thisformula over all underlying BTSs.

sum(decode(trx_type,0,ave_avail_TCH_sum))-----------------------------------------sum(decode(trx_type,0,ave_avail_TCH_den))

avg(decode(trx_type,0,ave_tch_avail_half)- -----------------------------------------

2


Figure 812. Number of FR timeslots available, normal TRXs, S9 (ava_32)

Number of FR timeslots available, extended TRXs, S9 (ava_33)

Use: Average number of timeslots available on extended TRXs forfull rate traffic only.Used on the BTS level. If used on the area level, it shows theaverage over extended cells only. For area (or segment) level,first use the formula for all the BTSs and then sum thisformula over all underlying BTSs.

nvl(Sum(decode(trx_type,1,ave_avail_TCH_sum))/sum(decode(trx_type,1,ave_avail_TCH_den))

- avg(decode(trx_type,1,ave_tch_avail_half))/2,0)




Figure 813. Number of FR timeslots available, extended TRXs, S9 (ava_33)

Number of dual timeslots available, normal TRXs, S9 (ava_34)

Use: Average number of timeslots available for dual (half rate orfull rate) traffic. On BTS level. For area (or segment) level,first use the formula for all the BTSs and then sum thisformula over all underlying BTSs.

Figure 814. Number of dual timeslots available, normal TRXs, S9 (ava_34)

Number of dual timeslots available, extended TRXs, S9 (ava_35)

Use: Average number of timeslots available for dual (half rate orfull rate) traffic.Used on the BTS level. If used on the area level, it shows theaverage over extended cells only. For area (or segment) level,first use the formula for all the BTSs and then sum thisformula over all underlying BTSs.

nvl(sum(decode(trx_type,1,ave_avail_full_TCH))/sum(decode(trx_type,1,res_av_denom2))+ avg(decode(trx_type,1,ave_tch_avail_half))/2-Sum(decode(trx_type,1,ave_avail_TCH_sum))/sum(decode(trx_type,1,ave_avail_TCH_den)

),0)


Figure 815. Number of dual timeslots available, extended TRXs, S9 (ava_35)

GPRS enable time %, S10 (ava_36)

Use: To indicate the GPRS availability in time.

(100*(AVE_PCH_GB_LOAD_ON_CCCH_DEN / RES_ACC_DENOM1))


Unit: %

Figure 816. GPRS enable time %, S10 (ava_36)



Number of HR TSLs available, extended TRXs, Area, S9 (ava_37)

Use: Average number of timeslots available for half rate trafficonly. Used on the BTS level. If used on the area level, it showsthe average over extended cells only. For area (or segment)level, first use the formula for all the BTSs and then sum thisformula over all underlying BTSs.

nvl((

sum(decode(trx_type,1,ave_avail_TCH_sum))--------------------------------------------(avg(decode(trx_type,1,ave_avail_TCH_den))* count(distinct period_start_time))

)-

(sum(decode(trx_type,1,ave_avail_full_TCH))

--------------------------------------------(avg(decode(trx_type,1,res_av_denom2)* count(distinct period_start_time))

),0)


Figure 817. Number of HR TSLs available, extended TRXs, Area, S9 (ava_37)

Number of FR TSLs available, extended TRXs, Area, S9 (ava_38)

Use: Average number of timeslots available on extended TRXs forfull rate traffic only.

nvl(sum(decode(trx_type,1,ave_avail_TCH_sum))

--------------------------------------------(avg(decode(trx_type,1,ave_avail_TCH_den))* count(distinct period_start_time))

-sum(decode(trx_type,1,ave_tch_avail_half * RES_AV_DENOM1))

---------------------------------------------------------------(2 * avg(decode(trx_type,1,ave_avail_TCH_den))* count(distinct period_start_time))

,0)


Figure 818. Number of FR TSLs available, extended TRXs, Area, S9 (ava_38)

Average number of available TCH TSLs, Area, S9 (ava_39)

Use: Average number of TCH timeslots (both CS and PS)available.

(ava_37 ; HR timeslots on extended TRXs

+ ava_38 ; FR timeslots on extended TRXs



+ ava_40 ; Dual timeslots on extended TRXs+ ava_42 ; HR timeslots on normal TRXs+ ava_43 ; FR timeslots on normal TRXs+ ava_41 ; Dual timeslots on normal TRXs+ ava_44 ; PS territory timeslots (always on normal TRXs))


Unit: TSL

Figure 819. Average number of available TCH TSLs, Area, S9 (ava_39)

Number of dual TSLs available, extended TRXs, Area, S9 (ava_40)

Use: Average number of timeslots available for dual (half rate orfull rate) traffic.

nvl((

sum(decode(trx_type,1,ave_avail_full_TCH))--------------------------------------------(avg(decode(trx_type,1,res_av_denom2))* count(distinct period_start_time))

)+

(sum(decode(trx_type,1,ave_tch_avail_half * RES_AV_DENOM1))

---------------------------------------------------------------(2 * avg(decode(trx_type,1, RES_AV_DENOM1)))

)-

(sum(decode(trx_type,1,ave_avail_TCH_sum))

--------------------------------------------(avg(decode(trx_type,1,ave_avail_TCH_den))* count(distinct period_start_time))

),0)


Figure 820. Number of dual TSLs available, extended TRXs, Area, S9 (ava_40)

Number of dual TSLs available, normal TRXs, Area, S9 (ava_41)

Use: Average number of timeslots available for dual (half rate orfull rate) traffic.

nvl((

sum(decode(trx_type,0,ave_avail_full_TCH))--------------------------------------------(avg(decode(trx_type,0,res_av_denom2))* count(distinct period_start_time))

)+



(sum(decode(trx_type,0,ave_tch_avail_half * RES_AV_DENOM1))

--------------------------------------------------------------(2 * avg(decode(trx_type,0, RES_AV_DENOM1)))

)-


-------------------------------------------(avg(decode(trx_type,0,ave_avail_TCH_den))* count(distinct period_start_time))

),0)


Figure 821. Number of dual TSLs available, normal TRXs, Area, S9 (ava_41)

Number of HR TSLs available, normal TRXs, Area, S9 (ava_42)

Use: On the area level. Average number of timeslots available forhalf rate traffic only.


-------------------------------------------------------------------------------(avg(decode(trx_type,0,ave_avail_TCH_den))* count(distinct period_start_time))

)-(

sum(decode(trx_type,0,ave_avail_full_TCH))----------------------------------------------------------------------------(avg(decode(trx_type,0,res_av_denom2)) * count(distinct period_start_time))

)Counters from table(s):p_nbsc_res_avail

Figure 822. Number of HR TSLs available, normal TRXs, Area, S9 (ava_42)

Number of FR TSLs available, normal TRXs, Area, S9 (ava_43)

Use: Average number of timeslots available on normal TRXs forfull rate traffic only.


-------------------------------------------------------------------------------(avg(decode(trx_type,0,ave_avail_TCH_den)) * count(distinct period_start_time))

)-(

sum(decode(trx_type,0,ave_tch_avail_half * RES_AV_DENOM1))-------------------------------------------------------------------------------(2 * avg(decode(trx_type,0,RES_AV_DENOM1)) * count(distinct period_start_time))

)




Figure 823. Number of FR TSLs available, normal TRXs, Area, S9 (ava_43)

Number of FR TSLs available, normal TRXs (ava_43a)

Use: Shows the average number of timeslots available on normalTRXs for full rate traffic only.

sum(decode(trx_type,0,ave_avail_TCH_sum))------------------------------------------------------------------------------avg(decode(trx_type,0,ave_avail_TCH_den))*count(distinct period_start_time)

sum(decode(trx_type,0,ave_tch_avail_half*RES_AV_DENOM1))- ------------------------------------------------------------------------------2*avg(decode(trx_type,0,ave_avail_TCH_den))*count(distinct period_start_time)


Figure 824. Number of FR TSLs available, normal TRXs (ava_43a)

Average PS territory, Area, S9PS (ava_44)

Description: Average available GPRS Channels (territory).Use: Shows the actual average territory available for packet

switched (PS) traffic.The value can be used for tuning the CDEF parameter.This figure is affected by:1) The settings of BTS parameters CDEF and CDED2) Changes of capacity

a) TRX locked or unlocked by the operator. If TRXs arelocked and BTSs and BCFs are unlocked, the TCHs of thatTRX appear as unavailable.

b) TRX disabled by BSC due to fatal faults3) Upgrades and downgrades of territory by BSC according totraffic needs


sum(decode(trx_type,0,ave_GPRS_channels_sum))--------------------------------------------------------------------------------(avg(decode(trx_type,0, decode(ave_GPRS_channels_sum,0,0,ave_GPRS_channels_den)))* count(distinct period_start_time))

where ave_GPRS_channels_sum > 0




Unit: timeslots

Figure 825. Average PS territory, Area, S9PS (ava_44)

Average available SDCCH, Area, S1 (ava_45)

sum(ave_sdcch_sub)--------------------------------------------------------(avg(res_av_denom3) * count(distinct period_start_time))


Figure 826. Average available SDCCH, Area, S1 (ava_45)

Average available SDCCH (ava_45a)

Use: Used on area level.

ava_48 + ava_49


Unit: number

Figure 827. Average available SDCCH

Average available SDCCH, normal TRX, Area, S1 (ava_48)

sum(decode(trx_type,0,ave_sdcch_sub)------------------------------------------------------------------------avg(decode(trx_type,0,res_av_denom3) * count(distinct period_start_time)


Figure 828. Average available SDCCH, normal TRX, Area, S1 (ava_48)

Average available SDCCH, extended TRX, Area, S1 (ava_49)

sum(decode(trx_type,1,ave_sdcch_sub)------------------------------------------------------------------------avg(decode(trx_type,1,res_av_denom3) * count(distinct period_start_time)




Figure 829. Average available SDCCH, extended TRX, Area, S1 (ava_49)

Number of available TCH TSLs, PS and CS common, Area S9 (ava_50)

Use: Average number of timeslots available for both CS and PStraffic. These are part of PS (GPRS) territory but if CS trafficneeds, they can be taken to CS call use (territory downgrade)automatically by BSC.

ava_44 - ava_51

Figure 830. Number of available TCH TSLs, PS and CS common, Area S9(ava_50)

Average available dedicated GPRS channels, Area S9PS (ava_51)

Use: Indicates the average number of channels available only fordedicated PS (GPRS) traffic. This capacity is allocated bysetting the parameter CDED. In the case that there are nodedicated GPRS channels, throughput is not guaranteed, if CStraffic needs all the capacity.


sum(decode(trx_type,0,ave_permanent_GPRS_ch_sum))----------------------------------------------------------------------(avg(decode(trx_type,0,

decode(ave_permanent_GPRS_ch_sum,0,0,ave_permanent_GPRS_ch_den)))* count(distinct period_start_time)

where ave_permanent_GPRS_ch_sum > 0


Figure 831. Average available dedicated GPRS channels, Area S9PS (ava_51)

Average CS TCH in normal TRXs, Area S9 (ava_52)

Description: Average available TCHs for CS use in normal TRXs.Use: BTS level. Indicates the average number of TCHs available

for circuit switched traffic (CS) in normal TRXs. Thiscapacity can also be used for PS traffic if CS traffic is low.If CS traffic grows, the PS territory can diminish to what isdefined as dedicated territory and give space for CS traffic.This figure is affected by1) The settings of BTS parameters CDEF and CDED



2) Changes of capacitya) TRX locked or unlocked by the operator. If TRXs arelocked and BTSs and BCFs are unlocked, the TCHs of thatTRX appear as unavailable.b) TRX disabled by BSC due to fatal faults3) Upgrades and downgrades of territory by BSC according totraffic needs

sum(decode(trx_type,0,ave_avail_TCH_sum))--------------------------------------------------------avg(decode(trx_type,0,

decode(ave_avail_TCH_sum,0,0, ave_avail_TCH_den)))* count(dinstinct period_start_time)

where ave_GPRS_channels_sum > 0

OR (the same result also with the following formula)

nvl(sum(decode(trx_type,0,ave_avail_TCH_sum))--------------------------------------------------------(avg(decode(trx_type,0,ave_avail_TCH_den))

* count (distinct period_start_time)),1)


Unit: timeslots

Figure 832. Average CS TCH in normal TRXs, Area S9 (ava_52)

Average available CS TCH in extended TRXs, Area S9 (ava_53)

Use: BTS level. Indicates the average number of TCHs availablefor circuit switched traffic (CS) in extended TRXs. Thiscapacity cannot be used for PS traffic.

nvl(sum(decode(trx_type,1,ave_avail_TCH_sum))----------------------------------------------------------------------------------(avg(decode(trx_type,1,ave_avail_TCH_den)) * count (distinct period_start_time),1)


Unit: timeslots

Figure 833. Average available CS TCH in extended TRXs, Area S9 (ava_53)

TCH availability %, Area, S9 (ava_55)






available TCH100 * ------------------------- %


ava_54 + ava_44= 100 * --------------------------- %

ava_54 + ava_44 + uav_17


Figure 834. TCH availability %, Area, S9 (ava_55)

TCH availability % (ava_55b)




available TCH100 * ------------------------- %


ava_54 + ava_44= 100 * --------------------------- %

ava_54 + ava_44 + uav_17b


Figure 835. TCH availability % (ava_55b)

Average defined HTCH (ava_58)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked, theTCHs appear as unavailable

ava_56 + ava_57


Unit: number

Figure 836. Average defined HTCH (ava_58)



Average defined FTCH (ava_59)


ava_60 + ava_61


Unit:number

Figure 837. Average defined FTCH (ava_59)

Number of TSLs available for CS traffic on normal TRXs, Area, S9 (ava_62)

Use: This KPI shows all the available timeslots that are notdedicated for PS (GPRS), i.e. that can be used by CS traffic onnormal TRXs.

ava_52 ; Pure CS TCHs on normal TRXs+ ava_44 - ava_51 ; dynamic part of PS territory

Figure 838. Number of TSLs available for CS traffic on normal TRXs, Area, S9(ava_62)

SDCCH availability %, Area S4 (ava_63a)

Use: Indicates how big a share of all SDCCH resources has beenavailable for traffic. Failures (downtime) of TRX containingSDCCH affect this KPI. .

Known problems: Affected by locked TRX under unlocked BCF and BTS.

sum(ave_sdcch_sub)100 * -------------------------------------------- %

sum(ave_sdcch_sub)+nvl(sum(ave_non_avail_sdcch * RES_AV_DENOM1))

=ava_4

Counters from table(s): p_nbsc_res_avail

Figure 839. SDCCH availability %, Area S4 (ava_63a)

Data service availability ratio (ava_68)

Description: Data Service Availability gives the estimated percentage ofon-air GPRS-capable BTSs which are able to provide GPRSservice (not afflicted by Sleeping GPRS outages).



Known problems: In some situations a base station can generate an 11-bit RACHburst without a real mobile on a cell. This will cause TBFestablishments in BSC and also an increment ofpacket_ch_req counter. In bad radio conditions this amountcan be more than 100. The official statement is that thenumber of ghost packet channel request messages cannot begreater than 100 during one measurement period but it hasbeen noticed that this limit can be exceeded in somesituations. It is proposed that the limit used in this condition"packet_ch_req >= 100" shall be set (greater than 100) basedon the real network conditions. 100 is sufficient in manycases, however.

100 *

(1-(

ava_71--------------------------------count(*)where (a.packet_ch_req >= 100)

)*

1-(ava_72

---------------------------------------------------------------count(*)where ((b.ave_tch_busy_full + b.ave_tch_busy_half) >= 0.2) and

(b.ave_gprs_channels_sum > 0) and(c.tch_call_req > 10)

))

Counters from table(s):a = p_nbsc_packet_control_unitb = p_nbsc_res_availc = p_nbsc_service

Unit: %

Figure 840. Data service availability ratio (ava_68)

2.32 Unavailability (uav)

Average unavailable TSL per BTS, S1 (uav_1)

Use: For area (or segment) level, first use the formula for all theBTSs and then sum this formula over all underlying BTSs.


sum(ave_non_avail_tsl)/sum(res_av_denom1)




Figure 841. Average unavailable TSL per BTS, S1 (uav_1)

Average unavailable TSL per BTS, S1 (uav_1a)


avg(ave_non_avail_tsl/res_av_denom1)


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

Average unavailable TSL per BTS, S1 (uav_1b)


sum(ave_non_avail_tsl/res_av_denom1)------------------------------------

count(*)


Figure 843. Average unavailable TSL per BTS, S1 (uav_1b)

Total outage time (uav_2)

Known problems: It should be made possible to differentiate the reasons foroutage.

Note: Alarm number changed in S7 from 2567 to 7767

sum of BCCH missing alarm durations =

sum(cancel_time-alarm_time)*24*60

where probable_cause = 7767 /* BCCH missing alarm */

Counters from table(s):fx_alarmunit = minutes

Figure 844. Total outage time (uav_2)



Number of outages (uav_3)

Note: Alarm number changed in S7 from 2567 to 7767.

number of BCCH missing alarm starts =

count(alarm_start_time)

where probable_cause = 7767 /* BCCH missing alarm */

Counters from table(s):fx_alarm

Figure 845. Number of outages (uav_3)

Share of unavailability due to user (uav_4)

Experiences on use: Locked TRXs can make this PI show high values.Known problems: The measurement is made on the BSC level. The BTS level

cannot be seen.

sum(ave_non_avail_user)100 * -------------------------------------------------------------- %

sum(ave_non_avail_user + ave_non_avail_int + ave_non_avail_ext)

Counters from table(s):p_nbsc_trx_avail

Figure 846. Share of unavailability due to user (uav_4)

Share of unavailability due to internal reasons (uav_5)

Known problems: The measurement is made on the BSC level. The BTS levelcannot be seen. This includes, for example, also an electricitybreak which, in fact, is not a BTS fault.

sum(ave_non_avail_int)100 * -------------------------------------------------------------- %



Figure 847. Share of unavailability due to internal reasons (uav_5)

Share of unavailability due to external reasons (uav_6)

Known problems: The measurement is made on the BSC level. The BTS levelcannot be seen.

sum(ave_non_avail_ext)100 * -------------------------------------------------------------- %





Figure 848. Share of unavailability due to external reasons (uav_6)

TRX unavailability time due to user (uav_7)

Experiences on use: Locked TRXs can make this PI show high values.

sum(period_duration * ave_non_avail_user)


Figure 849. TRX unavailability time due to user (uav_7)

TRX unavailability time due to internal reasons (uav_8)

Known problems: This includes, for example, also an electricity break which, infact, is not a BTS fault.

sum(period_duration * ave_non_avail_int)


Figure 850. TRX unavailability time due to internal reasons (uav_8)

TRX unavailability time due to external reasons (uav_9)

sum(period_duration * ave_non_avail_ext)


Figure 851. TRX unavailability time due to external reasons (uav_9)

Average unavailable SDCCH, S5 (uav_10)

Note: 1)This KPI has to be counted separately for extended andnormal area (trx_type: 0=normal, 1=extended).2)For area (or segment) level, first use the formula for all theBTSs and then sum this formula over all underlying BTSs.

avg(ave_non_avail_sdcch)




Figure 852. Average unavailable SDCCH, S5 (uav_10)

Average unavailable TCH, S5 (uav_11a)

Use: On BTS level. For area (or segment) level, first use theformula for all the BTSs and then sum this formula over allunderlying BTSs

Known problems: Locked TRXs are counted as unavailable TCH

uav_13+uav_14

Figure 853. Average unavailable TCH, S5 (uav_11a)

Average bearer unavailability, S9PS (uav_12)

100*sum(time_bear_oper_unoper)/sum(period_duration*60)


Figure 854. Average bearer unavailability, S9PS (uav_12)

Average unavailable TCH on normal TRXs, S5 (uav_13)

Known problems: Locked TRXs are counted as unavailable TCH.Note: For area (or segment) level, first use the formula for all the

BTSs and then sum this formula over all underlying BTSs.

avg(decode(trx_type,0,ave_non_avail_tch))


Figure 855. Average unavailable TCH on normal TRXs, S5 (uav_13)

Average unavailable TCH on extended TRXs, S5 (uav_14)

Use: On the BTS level. If used on the area level, it shows theaverage over extended cells only.

Known problems: Locked TRXs are counted as unavailable TCH. For area (orsegment) level, first use the formula for all the BTSs and thensum this formula over all underlying BTSs.

nvl(avg(decode(trx_type,1,ave_non_avail_tch)),0)




Figure 856. Average unavailable TCH on extended TRXs, S5 (uav_14)

Average unavailable TCH on normal TRXs, Area, S5 (uav_15)

Known problems: Locked TRXs are counted as unavailable TCH.

sum(decode(trx_type,0,ave_non_avail_tch * RES_AV_DENOM1))-------------------------------------------------------------------------avg(decode(trx_type,0,RES_AV_DENOM1)) * count(distinct period_start_time)


Figure 857. Average unavailable TCH on normal TRXs, Area, S5 (uav_15)

Average unavailable TCH on extended TRXs, Area, S5 (uav_16)

Known problems: Locked TRXs are counted as unavailable TCH.

nvl(sum(decode(trx_type,1,ave_non_avail_tch * RES_AV_DENOM1)),0)-------------------------------------------------------------------------avg(decode(trx_type,1,RES_AV_DENOM1)) * count(distinct period_start_time)


Figure 858. Average unavailable TCH on extended TRXs, Area, S5 (uav_16)

Average unavailable TCH, Area, S5 (uav_17)

Use: Average unavailable TCH on Area level.Known problems: Locked TRXs are counted as unavailable TCH.

uav_15 + uav_16

Figure 859. Average unavailable TCH, Area, S5 (uav_17)

Average unavailable SDCCH, normal TRX, Area level S5 (uav_20)

nvl(sum(decode(trx_type,0,ave_non_avail_sdcch * RES_AV_DENOM1)),0)-------------------------------------------------------------------------avg(decode(trx_type,0,RES_AV_DENOM1)) * count(distinct period_start_time)




Unit:number

Figure 860. Average unavailable SDCCH, normal TRX, Area level S5 (uav_20)

Average unavailable SDCCH, extended TRX, Area level S5 (uav_21)

nvl(sum(decode(trx_type,1,ave_non_avail_sdcch * RES_AV_DENOM1)),0)-------------------------------------------------------------------------avg(decode(trx_type,1,RES_AV_DENOM1)) * count(distinct period_start_time)


Unit:number

Figure 861. Average unavailable SDCCH, extended TRX, Area level S5(uav_21)

Average unavailable SDCCH (uav_22)

uav_20 + uav_21


Unit:number

Figure 862. Average unavailable SDCCH (uav_22)

2.33 Location updates (lu)

Number of LU attempts, S1 (lu_1)

sum(sdcch_loc_upd)


Figure 863. Number of LU attempts, S1 (lu_1)

Average of LU attempts per hour, S1 (lu_2)

sum(sdcch_loc_upd)--------------------------------avg(period_duration)*count(*)/60




Figure 864. Average of LU attempts per hour, S1 (lu_2)

Number of LU attempts, S1 (lu_3)

sum(nbr_of_calls)where counter_id = 25 /* LU started */


Figure 865. Number of LU attempts, S1 (lu_3)

2.34 LU success % (lsr)

LU success %, S6 (lsr_2)

Use: Probable causes to make this KPI show bad values:interference, coverage, possibly MSC side problems.

Known problems: The measurement is made on the BSC level.The LU started (51025) is triggered from establish indication.Any problems prior to that cannot be seen. For example,interference prevents a mobile station from making a locationupdate.

Values: Good: >99% .

sum(nbr_of_calls) where counter_id = 26 /* LU completed */100 * -------------------------------------------------------------- %

sum(nbr_of_calls) where counter_id = 25 /* LU started */


Figure 866. LU success %, S6 (lsr_2)

2.35 Emergency call (ec)

Emergency calls, S6 (ec_1)

sum(nbr_of_calls)where counter_id = 35 /* Em.call started */




Figure 867. Emergency calls, S6 (ec_1)

2.36 Emergency call success % (ecs)

Emergency call success %, S6 (ecs_1)

sum(nbr_of_calls) where counter_id = 41 /* Em.call completed */100 * -----------------------------------------------------------------------

sum(nbr_of_calls) where counter_id = 35 /* Em.call started */


Figure 868. Emergency call success %, S6 (ecs_1)

2.37 Call re-establishment (re)

Call re-establishment attempts, S6 (re_1)

sum(nbr_of_calls)where counter_id = 36 /* Callreest. started */


Figure 869. Call re-establishment attempts, S6 (re_1)

Call re-establishments, S6 (re_2)

sum(sdcch_call_re_est+tch_call_re_est)


Figure 870. Call re-establishments, S6 (re_2)



2.38 Call re-establishment success % (res)

Call re-establishment success %, S6 (res_1)

sum(nbr_of_calls) where counter_id = 42 /* Call re-est. completed */100 * -----------------------------------------------------------------------

sum(nbr_of_calls) where counter_id = 36 /* Call re-est. started */


Figure 871. Call re-establishment success %, S6 (res_1)

2.39 Quality

2.39.1 Downlink quality (dlq)

DL BER, S1 (dlq_1)

Known problems: BER % is not a very easy entity for network planners.Measurement periods that have no period on TCH, havepower_denom5 = 0.

sum(ave_dl_sig_qual)------------------------ %sum(power_denom5)*100

Counters from table(s):p_nbsc_powerUnit = BER %

Figure 872. DL BER, S1 (dlq_1)

DL cumulative quality % in class X, S1 (dlq_2)

Use: This PI gives a cumulative percentage of call samples (AMR,non-AMR in classes 0 to X. X = 5 is normally used as aquality indicator. If X = 5 and this figure is 100 %, then theMS users obviously have not perceived any quality problems.

Known problems: If DL DTX is used, there is a shift to a worse quality %, but aMS does not perceive this.

sum(freq_dl_qual0 + ... + freq_dl_qualX)100 * --------------------------------------------- %

sum( freq_dl_qual0 + ... + freq_dl_qual7)




Figure 873. DL cumulative quality % in class X, S1 (dlq_2)

DL cumulative quality % in class X, S1 (dlq_2a)

Use: This PI gives a cumulative percentage of call samples inclasses 0 to X. X=5 is normally used as quality indicator. IfX=5 and this figure is 100 %, then the MS users obviouslyhave not perceived any quality problems.

sum(freq_dl_qual0 + ... + freq_dl_qualX)100 * --------------------------------------------- %

sum(freq_dl_qual0 + ... + freq_dl_qual7)

Counters from table(s):p_nbsc_rx_statistics

Figure 874. DL cumulative quality % in class X, S1 (dlq_2a)

DL quality %, FER based, S10 (dlq_3)

Use: The share (as a percentage) of call samples in FEP classes 0 to7.Classes are defined by boundaries B0 to B8. Boundaries 1 to7 can be set as a measurement parameter. Class 0 is betweenboundaries B0 (fixed 0%) and B1. Class 7 is betweenboundaries B7 and B8 (fixed 100%).

Note: In S10 all DL samples are estimated.

sum(NBR_OF_DL_FER_CL_X)100 * --------------------------------------------- %

sum(NBR_OF_DL_FER_CL_0++NBR_OF_DL_FER_CL_7)

Counters from table(s):p_nbsc_fer

Figure 875. DL quality %, FER based, S10 (dlq_3)

DL cumulative quality % in class X, HR AMR, S10 (dlq_4)

Use: This PI gives the cumulative percentage of call samples(downlink half rate AMR) in classes 0 to Z. Z = 5 is normallyused as a quality indicator.

sum(nvl(AMR_HR_MODE_1_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_1_DL_RXQUAL_Z,0)

+nvl(AMR_HR_MODE_2_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_2_DL_RXQUAL_Z,0)+nvl(AMR_HR_MODE_3_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_3_DL_RXQUAL_Z,0)+nvl(AMR_HR_MODE_4_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_4_DL_RXQUAL_Z,0))

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



sum(nvl(AMR_HR_MODE_1_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_1_DL_RXQUAL_7,0)

+nvl(AMR_HR_MODE_2_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_2_DL_RXQUAL_7,0)+nvl(AMR_HR_MODE_3_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_3_DL_RXQUAL_7,0)+nvl(AMR_HR_MODE_4_DL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_4_DL_RXQUAL_7,0))


Figure 876. DL cumulative quality % in class X, HR AMR, S10 (dlq_4)

DL cumulative quality % in class X, FR AMR, S10 (dlq_5)

Use: This PI gives the cumulative percentage of call samples(downlink full rate AMR) in classes 0 to Z. Z = 5 is normallyused as a quality indicator.

sum(nvl(AMR_FR_MODE_1_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_1_DL_RXQUAL_Z,0

+nvl(AMR_FR_MODE_2_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_2_DL_RXQUAL_Z,0+nvl(AMR_FR_MODE_3_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_3_DL_RXQUAL_Z,0+nvl(AMR_FR_MODE_4_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_4_DL_RXQUAL_Z,0)

100* -------------------------------------------------------------------------- %sum(

nvl(AMR_FR_MODE_1_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_1_DL_RXQUAL_7,0+nvl(AMR_FR_MODE_2_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_2_DL_RXQUAL_7,0+nvl(AMR_FR_MODE_3_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_3_DL_RXQUAL_7,0+nvl(AMR_FR_MODE_4_DL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_4_DL_RXQUAL_7,0)


Figure 877. DL cumulative quality % in class X, FR AMR, S10 (dlq_5)

DL cumulative quality % in class X, S10 (dlq_6)

Use: This PI gives the cumulative percentage of all call samples(AMR and non-AMR) in classes 0 to Z. Z = 5 is normally usedas a quality indicator. If Z = 5 and this figure is 100 %, the MSusers obviously have not perceived any quality problems.

sum(freq_dl_qual0 + ... + freq_dl_qualZ)-sum(

nvl(AMR_HR_MODE_1_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_1_DL_RXQUAL_Z,0)+ nvl(AMR_HR_MODE_2_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_2_DL_RXQUAL_Z,0)+ nvl(AMR_HR_MODE_3_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_3_DL_RXQUAL_Z,0)+ nvl(AMR_HR_MODE_4_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_4_DL_RXQUAL_Z,0))

-sum(nvl(AMR_FR_MODE_1_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_1_DL_RXQUAL_Z,0)

+ nvl(AMR_FR_MODE_2_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_2_DL_RXQUAL_Z,0)+ nvl(AMR_FR_MODE_3_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_3_DL_RXQUAL_Z,0)+ nvl(AMR_FR_MODE_4_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_4_DL_RXQUAL_Z,0)

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

sum(freq_dl_qual0 + ... + freq_dl_qual7)



-sum(nvl(AMR_HR_MODE_1_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_1_DL_RXQUAL_7,0)

+ nvl(AMR_HR_MODE_2_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_2_DL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_3_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_3_DL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_4_DL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_4_DL_RXQUAL_7,0))

-sum(nvl(AMR_FR_MODE_1_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_1_DL_RXQUAL_7,0)

+ nvl(AMR_FR_MODE_2_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_2_DL_RXQUAL_7,0)+ nvl(AMR_FR_MODE_3_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_3_DL_RXQUAL_7,0)+ nvl(AMR_FR_MODE_4_DL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_4_DL_RXQUAL_7,0)

)


Figure 878. DL cumulative quality % in class X,S10 (dlq_6)

DL quality 0-5 %, HR, FER based, S10 (dlq_7)

Use: FER based quality benchmark for half rate speech trafficchannel.

sum(NBR_OF_DL_FER_CL_0+ +NBR_OF_DL_FER_CL_5)100 * --------------------------------------------- %

sum(NBR_OF_DL_FER_CL_0+ +NBR_OF_DL_FER_CL_7)

codec_type = 1Counters from table(s):p_nbsc_fer

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

DL quality 0-5 %, FR, FER based, S10 (dlq_8)

Use: FER based quality benchmark for FR calls.




Figure 880. DL quality 0-5 %, FR, FER based, S10 (dlq_8)

DL quality 0-5 % EFR, FER based, S10 (dlq_9)







Figure 881. DL quality 0-5 % EFR, FER based, S10 (dlq_9)

DL quality 0-5 % AMR HR, FER based, S10 (dlq_10)

Use: FER based quality benchmark for AMR HR calls.



codec_type = 4..9Counters from table(s):p_nbsc_fer

Figure 882. DL quality 0-5 % AMR HR, FER based, S10 (dlq_10)

DL quality 0-5 % AMR FR, FER based, S10 (dlq_11)

Use: FER based quality benchmark for AMR FR calls.




Figure 883. DL quality 0-5 % AMR FR, FER based, S10 (dlq_11)

2.39.2 Uplink quality (ulq)

UL BER, S1 (ulq_1)

Known problems: BER % is not a very easy entity for network planners.Measurement periods that have no period on TCH, havepower_denom6 = 0.

sum(ave_ul_sig_qual)------------------------ %sum(power_denom6)*100


Figure 884. UL BER, S1 (ulq_1)



UL cumulative quality % in class X, S1 (ulq_2)

Use: This PI gives a cumulative percentage of call samples (nonAMR and AMR) in classes 0 to X. X=5 is normally used asquality indicator. If X=5 and this figure is 100 %, then the MSusers obviously have not perceived any quality problems.

Known problems: Investigations in late 1997 showed that UL DTX makes ULquality seem worse than it actually is. The impact was aboutone 1% unit (1% of samples more in classes 6 and 7). Wheninvestigated with field tests, no real degradation of qualitycould be found.

sum(freq_ul_qual0 + ... + freq_ul_qualX)100 * --------------------------------------------- %

sum(freq_ul_qual0 + ... + freq_ul_qual7)


Figure 885. UL cumulative quality % in class X, S1 (ulq_2)

UL cumulative quality % in class X, S1 (ulq_2a)

Use: This PI gives the cumulative percentage of call samples inclasses 0 to X.X = 5 is normally used as a quality indicator. IfX= 5 and this figure is 100 %, the MS users obviously havenot perceived any quality problems.

sum(freq_ul_qual0 + ... + freq_ul_qualX)100 * --------------------------------------------- %

sum(freq_ul_qual0 + ... + freq_ul_qual7)


Figure 886. UL cumulative quality % in class X, S1 (ulq_2a)

UL quality %, FER based, S10 (ulq_3)

Use: The share (as a percentage) of call samples in FER classes 0to 7.Classes are defined by boundaries B0 to B8. Boundaries 1 to7 can be set as a measurement parameter. Class 0 is betweenboundaries B0 (fixed 0%) and B1. Class 7 is betweenboundaries B7 and B8 (fixed 100%).

sum(NBR_OF_UL_FER_CL_X)100 * --------------------------------------------- %

sum(NBR_OF_UL_FER_CL_0++NBR_OF_UL_FER_CL_7)




Figure 887. UL quality %, FER based, S10 (ulq_3)

UL cumulative quality % in class X, HR AMR, S10 (ulq_4)

Use: This PI gives the cumulative percentage of call samples(uplink half rate AMR) in classes 0 to Z. Z = 5 is normallyused as a quality indicator.

sum(nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_1_UL_RXQUAL_Z,0)

+nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_2_UL_RXQUAL_Z,0)+nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_3_UL_RXQUAL_Z,0)+nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_4_UL_RXQUAL_Z,0))

100* ------------------------------------------------------------------------ %sum(

nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0)+nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0)+nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0)+nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_HR_MODE_4_UL_RXQUAL_7,0))


Figure 888. UL cumulative quality % in class X, HR AMR, S10 (ulq_4)

UL cumulative quality % in class X, FR AMR, S10 (ulq_5)

Use: This PI gives the cumulative percentage of call samples (fullrate AMR) in classes 0 to Z. Z = 5 is normally used as a qualityindicator.

sum(nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_1_UL_RXQUAL_Z,0

+nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_2_UL_RXQUAL_Z,0+nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_3_UL_RXQUAL_Z,0+nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_4_UL_RXQUAL_Z,0)

100* -------------------------------------------------------------------------- %sum(

nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0+nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_2_UL_RXQUAL_7,0+nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_3_UL_RXQUAL_7,0+nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0)+ + nvl(AMR_FR_MODE_4_UL_RXQUAL_7,0)


Figure 889. UL cumulative quality % in class X, FR AMR, S10 (ulq_5)



UL cumulative quality % in class X, non-AMR S10 (ulq_6)

Use: This PI gives a cumulative percentage of all call samples(AMR and non AMR) in classes 0 to Z. Z=5 is normally usedas quality indicator. If Z=5 and this figure is 100 %, then theMS users obviously have not perceived any quality problems.

Known problems: Investigations late 1997 showed that UL DTX makes ULquality to show worse. The impact was about one 1% unit (1%of samples more in classes 6 and 7). When investigated withfield tests no real degradiation of quality could be found.

sum(freq_ul_qual0 + ... + freq_ul_qualZ)-sum(

nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_1_UL_RXQUAL_Z,0)+ nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_2_UL_RXQUAL_Z,0)+ nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_3_UL_RXQUAL_Z,0)+ nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_4_UL_RXQUAL_Z,0)

)-sum(

nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_1_UL_RXQUAL_Z,0)+ nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_2_UL_RXQUAL_Z,0)+ nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_3_UL_RXQUAL_Z,0)+ nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_4_UL_RXQUAL_Z,0)

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

sum(freq_ul_qual0 + ... + freq_ul_qual7)-sum(

nvl(AMR_HR_MODE_1_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_1_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_2_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_2_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_3_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_3_UL_RXQUAL_7,0)+ nvl(AMR_HR_MODE_4_UL_RXQUAL_0,0) +...+ nvl(AMR_HR_MODE_4_UL_RXQUAL_7,0)

)-sum(

nvl(AMR_FR_MODE_1_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_1_UL_RXQUAL_7,0)+ nvl(AMR_FR_MODE_2_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_2_UL_RXQUAL_7,0)+ nvl(AMR_FR_MODE_3_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_3_UL_RXQUAL_7,0)+ nvl(AMR_FR_MODE_4_UL_RXQUAL_0,0) +...+ nvl(AMR_FR_MODE_4_UL_RXQUAL_7,0)

)


Figure 890. UL cumulative quality % in class X, non-AMR S10 (ulq_6)

UL quality 0-5 %, HR, FER based, S10 (ulq_7)

Use: FER based quality benchmark for HR calls.

sum(NBR_OF_UL_FER_CL_0+ +NBR_OF_UL_FER_CL_5)100 * --------------------------------------------- %

sum(NBR_OF_UL_FER_CL_0+ +NBR_OF_UL_FER_CL_7)


Figure 891. UL quality 0-5 %, HR, FER based, S10 (ulq_7)



UL quality 0-5 %, FR, FER based, S10 (ulq_8)





Figure 892. UL quality 0-5 %, FR, FER based, S10 (ulq_8)

UL quality 0-5 % EFR, FER based, S10 (ulq_9)

Use: FER based quality benchmark for EFR calls.




Figure 893. UL quality 0-5 % EFR, FER based, S10 (ulq_9)

UL quality 0-5 % AMR HR, FER based, S10 (ulq_10)

Use: FER based quality benchmark for AMR HR calls.




Figure 894. UL quality 0-5 % AMR HR, FER based, S10 (ulq_10)

UL quality 0-5 % AMR FR, FER based, S10 (ulq_11)

Use: FER based quality benchmark for AMR FR calls.



codec_type = 10..17




Figure 895. UL quality 0-5 % AMR FR, FER based, S10 (ulq_11)

2.40 Downlink and uplink level

2.40.1 Downlink level (dll)

Share % per range, S4 (dll_1)

sum over a range (class_upper_range)(freq_dl_qual0+freq_dl_qual1+freq_dl_qual2+freq_dl_qual3+freq_dl_qual4+freq_dl_qual5+freq_dl_qual6+freq_dl_qual7)

100 * ----------------------------------------------------------- %sum over all ranges

(freq_dl_qual0+freq_dl_qual1+freq_dl_qual2+freq_dl_qual3+freq_dl_qual4+freq_dl_qual5+freq_dl_qual6+freq_dl_qual7)


Figure 896. Share % per range, S4 (dll_1)

Sorting factor for undefined adjacent cell, S4 (dll_2)

Use: Helps to sort the list of undefined adjacent cells.

sum(ave_dl_sig_str)/1000

Counters from table(s):p_nbsc_undef_adj_cell

Figure 897. Sorting factor for undefined adjacent cell, S4 (dll_2)

2.40.2 Uplink level (ull)

Share % per range, S4 (ull_1)

sum over a range (class_upper_range)(freq_ul_qual0+freq_ul_qual1+freq_ul_qual2+freq_ul_qual3+freq_ul_qual4+freq_ul_qual5+freq_ul_qual6+freq_ul_qual7)

100 * ----------------------------------------------------------- %sum over all ranges

(freq_ul_qual0+freq_ul_qual1+freq_ul_qual2+freq_ul_qual3+freq_ul_qual4+freq_ul_qual5+freq_ul_qual6+freq_ul_qual7)




Figure 898. Share % per range, S4 (ull_1)

2.41 Power (pwr)

Average MS power, S2 (pwr_1)

max_power-2*sum(ave_ms_power)/sum(power_denom1)

max_power = 43 (GSM900) or max_power = 30 (GSM1800, GSM1900)


Figure 899. Average MS power, S2 (pwr_1)

Average MS power, S2 (pwr_1b)

Note: max_power = 43 (GSM900) or 30 (GSM1800, GSM1900)

decode(objects.frequency_band_in_use,0,43,30)-2*sum(ave_ms_power)/sum(power_denom1)


Figure 900. Average MS power, S2 (pwr_1b)

Average BS power, S2 (pwr_2)

max_power - 2*sum(ave_BS_power)/sum(power_denom2)

max_power depends on the TRX used.


Figure 901. Average BS power, S2 (pwr_2)

2.42 Level (lev)

Average DL signal strength, S2 (lev_1)

-110+sum(ave_dl_sig_str)/sum(power_denom3)




Figure 902. Average DL signal strength, S2 (lev_1)

Average DL signal strength, S2 (lev_1a)

decode(ave_dl_sig_str/power_denom3,0,’< -110’,63,’> -48’,(-110+(round(ave_dl_sig_str/power_denom3)-1))||’..’||(-110+round(ave_dl_sig_str/power_denom3)))


Figure 903. Average DL signal strength, S2 (lev_1a)

Average UL signal strength, S2 (lev_2)

-110+sum(ave_ul_sig_str)/sum(power_denom4)


Figure 904. Average UL signal strength, S2 (lev_2)

Average UL signal strength, S2 (lev_2a)

decode(ave_ul_sig_str/power_denom4,0,’< -110’,63,’> -48’,(-110+(round(ave_ul_sig_str/power_denom4)-1))||’..’||(-110+round(ave_ul_sig_str/power_denom4)))


Figure 905. Average UL signal strength, S2 (lev_2a)



2.43 Distance (dis)

Average MS-BS distance (dis_1)

avg(ave_ms_bs_dist)*550 meter


Figure 906. Average MS-BS distance (dis_1)

The condition below should be applied in order to filter out the hours that do nothave traffic and for that reason show 0:

peak_ms_bs_dist+ave_dl_sig_str +ave_ul_sig_str > 0

Average MS-BS distance (dis_1a)

Counted per BTS/trx-type

decode(trx_type,0, ave_ms_bs_dist*550/1000,1, ave_ms_bs_dist*550/1000 + c_bts.radius_extension)

Unit: km


Figure 907. Average MS-BS distance (dis_1a)

If counted using average, the condition below should be applied in order to filterout the hours that do not have traffic and for that reason show 0:

peak_ms_bs_dist+ave_dl_sig_str +ave_ul_sig_str > 0

MS-BS distance class upper range (dis_3a)

decode(trx_type,0, class_upper_range *550/1000,1, class_upper_range *550/1000 + c_bts.radius_extension)

Unit: km




Figure 908. MS-BS distance class upper range (dis_3a)

2.44 Link balance, power, level (lb)

Link balance, S1 (lb_1)

Known problems: Inaccurate.

avg(ave_dl_sig_str/power_denom3) - avg(ave_ul_sig_str/power_denom4)


Figure 909. Link balance, S1 (lb_1)

Share in acceptance range, S4 (lb_2)

Known problems: The usefulness of link balance measurement is questionable.

sum(normal+ms_limited+bs_limited+max_power){where class_sig_level <= upper threshold

and class_sig_level >= lower threshold }100 * ------------------------------------------------- %

sum(normal+ms_limited+bs_limited+max_power)

Counters from table(s):p_nbsc_link_balance

Figure 910. Share in acceptance range, S4 (lb_2)

Share in normal, S4 (lb_3)


sum(normal)100 * ------------------------------------------------- %



Figure 911. Share in normal, S4 (lb_3)

Share in MS limited, S4 (lb_4)




sum(ms_limited)100 * ------------------------------------------------- %



Figure 912. Share in MS limited, S4 (lb_4)

Share in BS limited, S4 (lb_5)


sum(bs_limited)100 * ------------------------------------------------- %



Figure 913. Share in BS limited, S4 (lb_5)

Share in maximum power, S4 (lb_6)


sum(max_power)100 * ------------------------------------------------- %



Figure 914. Share in maximum power, S4 (lb_6)

Average MS power attenuation, S2 (lb_7)

2*sum(ave_MS_power)/sum(power_denom1)

Counters from table(s):p_nbsc_powerUnit = dB

Figure 915. Average MS power attenuation, S2 (lb_7)

Average MS power, S2 (lb_7b)

avg(decode(o_bts.freq_band_in_use,0,43,1,30)-2*ave_MS_power/power_denom1




p_nbsc_powerUnit= dBm

Figure 916. Average MS power, S2 (lb_7b)

Average UL signal strength, S2 (lb_9)

Use: Values as defined by GSM 5.08. Values 0 to 63:0 = less than -110 dBm1 = -110 to -109 dBm3 = -109 to -108 dBm62 = -49 to -4863 = greater than -48

sum(ave_ul_sig_str)/sum(power_denom4)


Figure 917. Average UL signal strength, S2 (lb_9)

Average DL signal strength, S2 (lb_10)

Use: Values as defined by GSM 5.08. Values 0 to 63:0 = less than -110 dBm1 = -110 to -109 dBm3 = -109 to -108 dBm62 = -49 to -4863 = greater than -48

sum(ave_dl_sig_str)/sum(power_denom3)


Figure 918. Average DL signal strength, S2 (lb_10)

Average MS power attenuation, S2 (lb_11)

2*sum(ave_MS_power)/sum(power_denom1)

Counters from table(s):p_nbsc_powerUnit = dB

Figure 919. Average MS power attenuation, S2 (lb_11)



Average BS power attenuation, S2 (lb_12)

2*sum(ave_BS_power)/sum(power_denom2)

Counters from table(s): p_nbsc_powerUnit = dB

Figure 920. Average BS power attenuation, S2 (lb_12)

Average link imbalance, S2 (lb_13)

2*sum(ave_BS_power)/sum(power_denom2)+sum(ave_dl_sig_str)/sum(power_denom3)-2*sum(ave_MS_power)/sum(power_denom1)-sum(ave_ul_sig_str)/sum(power_denom4)


Unit = dB

Figure 921. Average link imbalance, S2 (lb_13)

2.45 Call success (csf)

SDCCH access probability, before FCS (csf_1)

Use: Gives the probability to access SDCCH without the effect ofFCS. Applicable for area and BTS level.

Known problems: 1) The momentary SDCCH blocking phenomenon is met insome networks.2) sdcch_busy_att triggered also in the case of HO attemptif there are no free SDCCH.

sdcch_busy_att100*(1- ---------------) %

sdcch_seiz_att


Figure 922. SDCCH access probability, before FCS (csf_1)

SDCCH access probability (csf_1a)

Use: Gives the probability to access SDCCH. Applicable for areaand BTS level. A low value means high traffic on SDCCH andlack of SDCCH resources, that is SDCCH blocking.



Experiences on use: The value should be kept very close to 100% in a networkwith traffic. -After S7 the Dynamic SDCCH Allocation can be used toprevent SDCCH congestion. -Before S7 the FACCH call setup could already be used toimprove this KPI.

Known problems: 1) The momentary SDCCH blocking phenomenon is met insome networks and if the traffic is low, this KPI can showlower values that, however, do not mean bad access to thenetwork perceived by the user.2) SDCCH_busy_att triggered also in the case of HO attemptif there are no free SDCCH.3) The formula does not separate calls from LU and other use.In some cases this would be needed (e.g. a train crossing LAboundary creates a high LU peak).

100-blck_5a =

sdcch_busy_att- tch_seiz_due_sdcch_con100-(100* ----------------------------------------) %

sdcch_seiz_att


Figure 923. SDCCH access probability (csf_1a)

SDCCH success ratio (csf_2a)

Experiences on use: The best values seen are around 98%.Known problems: The formula does not separate the SDCCH call seizures from

other seizures (such as LU). The failure rate in the case of acall or LU can greatly differ from one another, wherefore youcannot use this formula for SDCCH call success ratiocalculation.It is not exactly known how large a share ofsum(sdcch_abis_fail_call +sdcch_abis_fail_old) really are setup failures.

100 - non abis SDCCH drop ratio =

sum(sdcch_radio_fail+ sdcch_rf_old_ho+ sdcch_user_act+ sdcch_bcsu_reset+ sdcch_netw_act+ sdcch_bts_fail+ sdcch_lapd_fail+ sdcch_a_if_fail_call+ sdcch_a_if_fail_old)

100 - 100 * ------------------------------------------------------------ %sum(sdcch_assign + sdcch_ho_seiz)

- sum(sdcch_abis_fail_call + sdcch_abis_fail_old) ; phantoms




Figure 924. SDCCH success ratio (csf_2a)

SDCCH success ratio, area (csf_2e)

Use: Indicates how well the SDCCH phase is completed.Experiences on use: The best values seen are around 98%.Known problems: The formula does not separate the SDCCH call seizures from

other seizures (such as LU and SS). The failure rate in the caseof a call or for example LU can greatly differ from oneanother, wherefore you cannot use this formula for SDCCHcall success ratio calculation.

100 - SDCCH drop ratio =

sum(a.sdcch_radio_fail+ a.sdcch_rf_old_ho+ a.sdcch_user_act+ a.sdcch_bcsu_reset+ sdcch_netw_act+ a.sdcch_bts_fail+ a.sdcch_lapd_fail+ a.sdcch_a_if_fail_call+ a.sdcch_a_if_fail_old+ a.sdcch_abis_fail_old+(a.sdcch_abis_fail_call - C))

100 – 100 * ----------------------------------- %sum(b.succ_seiz_term

+ b.succ_seiz_orig+ b.sdcch_call_re_est+ b.sdcch_loc_upd+ b.imsi_detach_sdcch+ b.sdcch_emerg_call

C= part of sdcch_abis_fail_call that occurs before establishment indication =a.sdcch_assign - (b.succ_seiz_term

+ b.succ_seiz_orig+ b.sdcch_call_re_est+ b.sdcch_loc_upd+ b.imsi_detach_sdcch+ b.sdcch_emerg_call)


Figure 925. SDCCH success ratio, area (csf_2e)

SDCCH success ratio, BTS, S6 (csf_2g)

Use: BTS level.Experiences on use: Includes A interface blocking!



Note

Known problems: As consistency is a critical property in measurements, thecombining of three tables can lead into problems.

sum(a.tch_norm_seiz) ;(all TCH seiz.for new call)=100* -------------------------------------------------------------------- %

sum(b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_call_re_est+b.sdcch_emerg_call);(calls,sms, ss reqs)

- sum(b.succ_sdcch_sms_est+ b.unsucc_sdcch_sms_est) ;(sms attempts)

+ sum(c.msc_i_sdcch + c.bsc_i_sdcch ;(net SDCCH HO in)-c.msc_o_sdcch - c.bsc_o_sdcch) ;(unknown how big part calls

- sum(a.tch_call_req-a.tch_norm_seiz) ;(DR and air itf blocking)

- supplem.serv. requests ;(unknown factor)- call clears before TCH ;(unknown factor)- supplem.serv. requests ;(unknown factor)


Figure 926. SDCCH success ratio, BTS, S6 (csf_2g)

This formula includes also A interface blocking. If call re-establishment occursalready on SDCCH, the formula is not correct, but if it occurs on TCH, it iscorrect.

SDCCH success ratio, BTS (csf_2i)

Use: BTS level.Experiences on use: Includes A interface blocking!Known problems: 1) As consistency is a critical property in measurements, the

combining of three tables can lead into problems. Unknownfactors in the denominator make the values seem pessimistic2) The formula does not separate the SDCCH call seizuresfrom other seizures (such as LU and SS). The failure rate inthe case of a call or for example LU can greatly differ fromone another. For this reason you cannot use this formula forSDCCH call success ratio calculation.


sum(b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_call_re_est+b.sdcch_emerg_call);(calls,sms, ss reqs)


+ sum(c.msc_i_sdcch + c.bsc_i_sdcch ;(net SDCCH HO in)-c.msc_o_sdcch - c.bsc_o_sdcch) ;(unknown how big part calls

- sum(c.cell_sdcch_tch)+ sum(a.tch_succ_seiz_for_dir_acc);direct access related correction- sum(a.tch_call_req-a.tch_norm_seiz) ;(DR and air itf blocking)



Note

- supplem.serv. requests ;(unknown factor)- call clears before TCH ;(unknown factor)- supplem.serv. requests ;(unknown factor)


Figure 927. SDCCH success ratio, BTS (csf_2i)


SDCCH success ratio (csf_2k)

Use:Experiences on use: Includes A interface blocking.Known problems: As consistency is a critical property in measurements, the

binding of three tables can lead into problems. See problemsfrom csf_2j

Segment related problems: This KPI does not work on BTS level if a segmentof several BTSs is used.

sum(a.tch_norm_seiz) ;(all TCH seiz.for new call)= 100 * -------------------------------------------------------------------- %

sum(b.succ_seiz_term + b.succ_seiz_orig+ b.sdcch_call_re_est + b.sdcch_emerg_call) ;(calls,sms, ss reqs)


+ sum(c.msc_i_sdcch + c.bsc_i_sdcch ;(net SDCCH HO in)- c.msc_o_sdcch - c.bsc_o_sdcch) ;(unknown how big part calls

- sum(c.cell_sdcch_tch)+ sum(a.tch_succ_seiz_for_dir_acc) ; direct access related correction- sum(a.tch_call_req-a.tch_norm_seiz) ;(DR and air itf blocking)- sum(b.succ_seiz_supplem_serv) ;supplem.serv. requests (S9)- call clears before TCH ;(unknown factor)




Note

Unit: %

Figure 928. SDCCH success ratio (csf_2k)


SDCCH success ratio, area, S10.5 (csf_2m)

Use: Used on the area level.Experiences on use: The best values seen are around 95%. Includes A interface

blocking!Known problems: As consistency is a critical property in measurements, the

combining of three tables can lead into problems. Unknownfactors in the divisor make the values seem pessimistic.1) The calls are cleared before TCH can vary betweennetworks depending on the call setup time which, again, maydepend on the use of DR or queuing features. Other reasonscan be authentication fails, identity check fails and MOC callshaving wrong dialling, for example.2) This formula does not count correctly the situation whenthe first call or call re-establishment fails on SDCCH (MSnever comes to TCH).3) For the BTS area there is no way of knowing how muchSDCCH-SDCCH handovers take place across the area border.The net incoming amount of SDCCH handovers ends up in asuccessful case in TCH seizures but they are not seen in thenominator.4) For the BTS area there is no way of knowing how muchSDCCH-TCH (DR) handovers take place across the areaborder. The net incoming amount of SDCCH-TCH (DR)handovers ends up in a successful case in TCH seizures butthey are not seen in the nominator.5) LCS requests that are made on SDCCH (MS is idle)increment the denominator but not the numerator, thusmaking the ratio seem too pessimistic. A new counter isneeded to fix the formula for this.

(succ tch seiz) - (call re-establ.)100 * ------------------------------------------------------- %

(sdcch seizures for new calls) - (blocked calls)

sum(a.tch_norm_seiz) ;(all TCH seiz. for new call)- call re-establ. (unknown factor)

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



Note

sum(b.succ_seiz_term+ b.succ_seiz_orig+ b.sdcch_emerg_call+ b.sdcch_call_re_est+ b.call_assign_after_sms) ;(calls,sms, ss reqs)

- sum(b.succ_sdcch_sms_est + b.unsucc_sdcch_sms_est);(sms attempts)- sum(c.bsc_o_sdcch_tch - c.msc_o_sdcch_tch - c.cell_sdcch_tch) ; (DR)+ sum(a.tch_succ_seiz_for_dir_acc ) ; direct access- sum(b.succ_seiz_supplem_serv) ;(supplementary service requests, S9)- call clears before TCH (unknown factor)+ net impact of SDCCH-SDCCH HO on area(unknown factor)+ net incoming DR to area (unknown factor)


Figure 929. SDCCH success ratio, area (csf_2m)

This formula includes also A interface blocking. It works for call re-establishmentif the drop occurs on TCH. If the drop occurs on SDCCH and the call is re-established, there is double count in the divisor.

SDCCH success ratio, BTS, S10.5 (csf_2n)

Use: BTS level.Experiences on use: Includes A interface blocking!Known problems: As consistency is a critical property in measurements, the

combining of three tables can lead into problems. Unknownfactors in the divisor make the values seem pessimistic.1) The calls are cleared before TCH can vary betweennetworks depending on the call setup time which, again, maydepend on the use of DR or queuing features. Other possiblereasons are authentication fails, identity check fails and MOCcalls having wrong dialling, for example.2) This formula does not count correctly the situation wherethe first call or call re-establishment fails on SDCCH (MSnever comes to TCH).3) It is not known how much of SDCCH-SDCCH handoversare calls.4) LCS requests that are made on SDCCH (MS is idle)increment the denominator but not the numerator, thusmaking the ratio seem too pessimistic. A new counter isneeded to fix the formula for this.


sum(b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_call_re_est+b.sdcch_emerg_call



Note

+b.call_assign_after_sms) ;(calls,sms, ss reqs)- sum(b.succ_sdcch_sms_est

+ b.unsucc_sdcch_sms_est) ;(sms attempts)+ sum(c.msc_i_sdcch + c.bsc_i_sdcch ;(net SDCCH HO in)

-c.msc_o_sdcch - c.bsc_o_sdcch) ;(unknown how big part calls- sum(c.cell_sdcch_tch)+ sum(a.tch_succ_seiz_for_dir_acc); direct access related correction- sum(a.tch_call_req-a.tch_norm_seiz) ;(DR and air itf blocking)- sum(b.succ_seiz_supplem_serv) ;supplem.serv. requests (S9)- call clears before TCH ;(unknown factor)- supplem.serv. requests ;(unknown factor)


Figure 930. SDCCH success ratio, BTS (csf_2n)

Includes also A interface blocking. If call re-establishment occurs already onSDCCH, the frmula is not correct, but if it occurs on TCH, it is correct.

SDCCH success ratio, area, S10.5 (csf_2o)

Use: Area level.Experiences on use: The best values seen are around 95%. Includes A interface

blocking!Known problems: As consistency is a critical property in measurements, the

binding of three tables can lead into problems. Unknownfactors in the divisor make the values seem pessimistic.1) The calls cleared before TCH can vary between networksdepending on the call setup time which, again, may depend onthe use of DR or queuing features. Other reasons can beauthentication fails, identity check fails and MOC callshaving wrong dialling, for example.2) This formula does not count correctly the situation whenthe first call of call re-establishment fails on SDCCH (MSnever comes to TCH).4) For the BTS area there is no way knowing how muchSDCCH-TCH (DR) handovers take place across the areaborder. The net incoming amount of SDCCH-TCH (DR)handovers ends up in a successful case in TCH seizures butthey are not seen in the nominator.5) LCS requests that are made on SDCCH (MS is idle)increment the denominator but not the numerator, thusmaking the ratio seem too pessimistic. A new counter isneeded to fix the formula for this.

(successful tch seizures) - (call re-establ.)



Note

100 * ------------------------------------------------- %(sdcch seizures for new calls) - (blocked calls)

sum(a.tch_norm_seiz) ;(all TCH seiz. for new call)- call re-establ. ;(unknown factor)

= 100 * --------------------------------------------------------------------- %sum(b.succ_seiz_term

+ b.succ_seiz_orig+ b.sdcch_emerg_call+ b.sdcch_call_re_est+ b.call_assign_after_sms) ;(calls,sms, ss reqs)

- sum(b.succ_sdcch_sms_est + b.unsucc_sdcch_sms_est);(sms attempts)- sum(c.bsc_o_sdcch_tch + c.msc_o_sdcch_tch) ;(DR)+ sum(a.tch_succ_seiz_for_dir_acc ) ; direct access- sum(b.succ_seiz_supplem_serv) ;(supplementary service requests, S9)- call clears before TCH ;(unknown factor)+ net impact of SDCCH-SDCCH HO on area ;(unknown factor)+ net incoming DR to area ;(unknown factor)


Figure 931. SDCCH success ratio, area, S10.5 (csf_2o)

Includes also A interface blocking. Works for call re-establishment if the drop ison TCH. If the drop is on SDCCH and the call is re-established, then there isdouble count in the divisor.

TCH access probability without DR (csf_3a)

Use: This PI indicates what would be the blocking if DR was notused. When compared to csf_3, you can see, assuming thatDR is in use, the improvement that the DR has caused.

100-blck_8 =

sum(tch_call_req - tch_norm_seiz)100-100* -------------------------------- %

sum(tch_call_req)


Figure 932. TCH access probability without DR (csf_3a)



TCH access probability without DR and Q (csf_3b)

Use: This PI indicates what would be the TCH blocking if DR andqueuing were not used. When compared to csf_3a, you cansee, assuming that DR is in use, the improvement that the DRhas caused.

Known problems: See XX1.

sum(tch_call_req - tch_norm_seiz)+ sum(tch_qd_call_att - XX1 - unsrv_qd_call_att)

; calls succeeded via queuing100 - 100 * ------------------------------------------------- %

sum(tch_call_req)

Counters from table(s):p_nbsc_trafficXX1 = attempts taken from queue to DR (unknown)

Figure 933. TCH access probability without DR and Q (csf_3b)

TCH access probability without Q (csf_3c)

Use: This PI indicates what would be the blocking if queuing wasnot used (but DR is used).

sum(a.tch_call_req- a.tch_norm_seiz- b.msc_o_sdcch_tch- b.bsc_o_sdcch_tch)

+ sum(a.tch_qd_call_att- a.unsrv_qd_call_att) ;calls that succeeded via queuing

100 - 100 * ------------------------------------------------------------- %sum(a.tch_call_req)


Figure 934. TCH access probability without Q (csf_3c)

TCH access probability, real (csf_3d)

Use: This KPI is affected by the congestion on TCH.100 - blck_8b =

sum(a.tch_call_req - a.tch_norm_seiz)- sum(b.msc_o_sdcch_tch

+ b.bsc_o_sdcch_tch+ b.cell_sdcch_tch); DR calls

100 - 100 * ------------------------------------------ %sum(a.tch_call_req)




a = p_nbsc_trafficb = p_nbsc_ho

Figure 935. TCH access probability, real (csf_3d)

TCH access probability without DR (csf_3i)

Use: This PI indicates what would be the TCH blocking if DR wasnot used. When compared to csf_3a, you can see, assumingthat DR is in use, the improvement that the DR has caused.Does not contain the congestion of the A interface circuitpool.

sum(a.tch_call_req - a.tch_norm_seiz)- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion

-(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures+ b.msc_controlled_in_ho+ b.ho_unsucc_a_int_circ_type))

100 - 100 * ------------------------------------- %sum(a.tch_call_req)

- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion-(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures+ b.msc_controlled_in_ho+ b.ho_unsucc_a_int_circ_type))


Figure 936. TCH access probability without DR (csf_3i)

TCH access probability without DR and Q (csf_3j)

Use: This PI indicates what would be the TCH blocking if DR andqueuing were not used. When compared to csf_3a, you cansee, assuming that queuing is in use, the improvement that thequeuing has caused. Does not contain the congestion of the Ainterface circuit pool.

Known problems: See XX1.

sum(tch_call_req - tch_norm_seiz)+ sum(tch_qd_call_att-XX1-unsrv_qd_call_att) ;succ. calls via queuing- sum(tch_rej_due_req_ch_a_if_crc) ; Aif pool rejections

100-100*-------------------------------------------------------- %sum(tch_call_req)

- sum(tch_rej_due_req_ch_a_if_crc) ; Aif pool rejections

Counters from table(s):p_nbsc_trafficXX1 = attempts taken from queue to DR (unknown)

Figure 937. TCH access probability without DR and Q (csf_3j)



TCH access probability, real (csf_3k)

Use: This KPI is affected by the blocking on TCH.

100-blck_8c =

sum(a.tch_call_req-a.tch_norm_seiz)- sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch+b.cell_sdcch_tch); DR calls- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion

-(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures+b.msc_controlled_in_ho+b.ho_unsucc_a_int_circ_type))

100-100* ----------------------------------------------------------- %sum(a.tch_call_req)

- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion-(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures+b.msc_controlled_in_ho+b.ho_unsucc_a_int_circ_type))


Figure 938. TCH access probability, real (csf_3k)

TCH access probability, real (csf_3l)

Use: See blck_8d.Known problems: On cell level the formula is inaccurate in case of inter cell

direct access (BSS7057).

100-blck_8d =

sum(a.tch_call_req-a.tch_norm_seiz)- sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch+b.cell_sdcch_tch); DR calls+ sum(a.tch_succ_seiz_for_dir_acc) ;ref.2- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion

-(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures+b.msc_controlled_in_ho+b.ho_unsucc_a_int_circ_type))

100-100* ----------------------------------------------------------- %sum(a.tch_call_req)

- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion-(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures+b.msc_controlled_in_ho+b.ho_unsucc_a_int_circ_type))


Figure 939. TCH access probability, real (csf_3l)

Ref.2. Compensation needed since in case of Direct Access to super reuse TRXthe tch_norm_seiz is triggered in parallel with the cell_sdcch_tch.



TCH access probability without DR and Q (csf_3m)

Use: This PI indicates what would be the TCH blocking if DR andqueuing were not used. When compared to csf_3i, you cansee, assuming that queuing is in use, the improvement that thequeuing has caused. Does not contain the congestion of the Ainterface circuit pool.

Known problems: Inaccurate when the feature 'TCH assignment to super-reuseTRX in IUO' is applied. In this case tch_call_req andremoval_from_que_due_to_dr are triggered multipletimes if the target cell is congested and queuing is started butthe call is removed to normal DR.

sum(tch_call_req - tch_norm_seiz)+ sum(tch_qd_call_att

-removal_from_que_due_to_dr-unsrv_qd_call_att) ;succ. calls via queuing

- sum(tch_rej_due_req_ch_a_if_crc); Aif pool rejections100-100 * -------------------------------------------------------- %

sum(tch_call_req)- sum(tch_rej_due_req_ch_a_if_crc); Aif pool rejections


Figure 940. TCH access probability without DR and Q (csf_3m)

TCH access probability, real, S11.5 (csf_3o)

Use: See blck_8f.100 - blck_8f =

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_hoc = p_nbsc_service

Figure 941. TCH access probability, real, S11.5 (csf_3o)

TCH access probability, S11.5 (csf_3p)

Use: See blck_8g.

100 - blck_8g =


Figure 942. TCH access probability, S11.5 (csf_3p)



TCH success ratio, area, before call re-establisment (csf_4o)

Use: Used on the area level. The impact of call re-establishment isnot yet taken into account.



100 - 100 * ------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)


+ sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls


Figure 943. TCH success ratio, area, before call re-establisment (csf_4o)

TCH success ratio, area, after call re-establishment, S6 (csf_4p)

Use: Used on the area level.Known problems: 1) See dcr_3g.

2) It is assumed that call re-establishments happen on TCH. Infact they may happen also on SDCCH.3) The counters used to compensate re-establishments are theones that indicate re-establishment attempts, not thesuccessful re-establishments. In S7/T11 re-establishments canbe considered accurately (see csf_4v).4) On cell level it can happen that the call is re-established ina different cell than where it was dropped, which results ininaccuracy.

100 - dcr_3f =

sum(a.tch_radio_fail+ a.tch_rf_old_ho+ a.tch_abis_fail_call+ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail



+ a.tch_user_act+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)

- sum(b.sdcch_call_re_est + b.tch_call_re_est) ;call re-establ.100 - 100 * ------------------------------------------------------------------- %



+ sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls- sum(b.sdcch_call_re_est+b.tch_call_re_est) ;call re-establ.


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

TCH success ratio, BTS, before call re-establisment (csf_4q)

Use: Used on the BTS level.Known problems: See dcr_4c.

100 - dcr_4b =


100 - 100 * -------------------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)


+ sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls+ sum(c.msc_i_tch_tch+c.bsc_i_tch_tch) ;(TCH-TCH HO in)


Figure 945. TCH success ratio, BTS, before call re-establisment (csf_4q)

TCH success ratio, BTS, after call re-establishment (csf_4r)

Use: Used on the BTS level.Known problems: See dcr_3g.




- sum(b.sdcch_call_re_est + b.tch_call_re_est) ;call re-establ.100 - 100 * -------------------------------------------------------------------- %


+ c.bsc_i_sdcch_tch+ c.cell sdcch_tch) ;(DR calls)

+ sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls+ sum(c.msc_i_tch_tch

+ c.bsc_i_tch_tch) ;(TCH-TCH HO in)- sum(b.sdcch_call_re_est

+ b.tch_call_re_est) ;call re-establishments


Figure 946. TCH success ratio, BTS, after call re-establishment (csf_4r)

TCH success ratio, BTS, after call re-establishment (csf_4t)

Use: Used on the BTS level.Known problems: See dcr_3d.


- sum(b.tch_re_est_assign) ;call re-establishments100 - 100 * ----------------------------------------------------------- %


+ c.bsc_i_sdcch_tch+ c.cell sdcch_tch) ;(DR calls)

+ sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls+ sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) ;(TCH-TCH HO in)- sum(b.tch_re_est_assign) ;call re-establ.




a = p_nbsc_trafficb = p_nbsc_servicec = p_nbsc_ho

Figure 947. TCH success ratio, BTS, after call re-establishment (csf_4t)

TCH success ratio, area, before call re-establishment, S7(csf_4u)

Use: See dcr_3i.Known problems: See dcr_3g. The impact of call re-establishment is not yet

taken into account.

100 - dcr_3i =

sum(a.tch_radio_fail+ a.tch_rf_old_ho+ a.tch_abis_fail_call++ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)

100 - 100 * ---------------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)




Figure 948. TCH success ratio, area, before call re-establishment, S7(csf_4u)


TCH success ratio, area, after call re-establishment, S7 (csf_4v)

Use: On the area level. See dcr_3j.Known problems: 1) It is assumed that call re-establishments happen on TCH. In

fact they may happen also on SDCCH.2) On cell level it can happen that the call is re-established ina different cell than it was dropped and this causes inaccuracy.

100 - dcr_3j=

sum(a.tch_radio_fail



+ a.tch_rf_old_ho+ a.tch_abis_fail_call+ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)






Figure 949. TCH success ratio, area, after call re-establishment, S7 (csf_4v)


TCH success ratio, BTS, after call re-establishment (csf_4x)



- sum(b.tch_re_est_assign) ;call re-establishments100 - 100 * ---------------------------------------------------------------- %



- sum(a.tch_succ_seiz_for_dir_acc ) ;ref.2+ sum(a.tch_seiz_due_sdcch_con) ;FACCH call setup calls+ sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) ;(TCH-TCH HO in)- sum(b.tch_re_est_assign) ;call re-establishments




Figure 950. TCH success ratio, BTS, after call re-establishment (csf_4x)


TCH success ratio, BTS, before call re-establishment (csf_4y)


100 - dcr_4e=


100 - 100 * --------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)

+ sum(c.msc_i_sdcch_tch+ c.bsc_i_sdcch_tch+ c.cell sdcch_tch) ;(DR calls)

- sum(a.tch_succ_seiz_for_dir_acc ) ;ref.2+ sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls+ sum(c.msc_i_tch_tch + c.bsc_i_tch_tch) ;(TCH-TCH HO in)


Figure 951. TCH success ratio, BTS, before call re-establishment (csf_4y)


Activation related SDCCH access probability, S7, (csf_12)


sum(sdcch_assign + t3101_expired)100 * --------------------------------- %

sum(served_sdcch_req)




Figure 952. Activation related SDCCH access probability, S7, (csf_12)

SDCCH call success probability, S10.5 (csf_13a)


sum(a.tch_call_req)100 * ------------------------------ %

sum(c.call_assign_after_sms+ a.sdcch_new_call_assign+ b.sdcch_ho_call_assign+ a.sdcch_re_est_assign- a.sdcch_re_est_release- a.sdcch_sms_assign- a.sdcch_ho_rel.)

Counters from table(s):p_nbsc_service, a = source, b = targetc = p_nbsc_res_access

Figure 953. SDCCH call success probability, S10.5 (csf_13a)

TCH success ratio, before call re-establishment (csf_41)

Use: Used on the BTS level.100 - dcr_3k =

sum(a.tch_radio_fail+ a.tch_rf_old_ho+ (a.tch_abis_fail_call - b.spare002072); Ref 1+ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)

100 - 100 * ---------------------------------------------------------- %sum(a.tch_norm_seiz) ;(normal calls)




Unit: %

Ref 1; The spare counter (2072) used to compensate the counter



001084 TCH_ABIS_FAIL_CALLthat is updated faultily after activation of FACCHRef.2. Compensation needed since in case of Direct Access tosuper reuse TRX thetch_norm_seiz is triggered in parallel with cell_sdcch_tch.

Figure 954. TCH success ratio, before call re-establishment (csf_41)

TCH success ratio, after call re-establishment (csf_42)

Use: Used on the BTS level.

100 - dcr_3l=

sum(a.tch_radio_fail+ a.tch_rf_old_ho+ (a.tch_abis_fail_call - d.spare002072); Ref 1+ a.tch_abis_fail_old+ a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+ a.tch_tr_fail_old+ a.tch_lapd_fail+ a.tch_bts_fail+ a.tch_user_act+ a.tch_bcsu_reset+ a.tch_netw_act+ a.tch_act_fail_call)





Counters from table(s):a = p_nbsc_trafficb = p_nbsc_servicec = p_nbsc_hod = p_nbsc_res_avail

Ref 1; The spare counter (2072) used to compensate the counter001084 TCH_ABIS_FAIL_CALLthat is updated faultily after activation of FACCHRef.2. Compensation needed since in the case of Direct Access tosuper reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch.

Figure 955. TCH success ratio, after call re-establishment (csf_42)

2.46 Configuration (cnf)

Reuse pattern (cnf_1)

Experiences on use: For example, 30/3 = 10 means that the frequency can berepeated with 10 cells!The smaller the figure, the better the planning.



Known problems: This indicator can be counted from the Nokia NetAct only forthe latest moment (no history).

number of used frequencies------------------------average TRXs per cell

Figure 956. Reuse pattern (cnf_1)

The used frequency means that the TRX and its parents (BTS and BCF) areunlocked.

Reuse pattern, S1 (cnf_2)

Decode(Avg(trx_type),0,’normal’,1,’extended’,’mixed’)

Figure 957. Reuse pattern, S1 (cnf_2)

2.47 Wireless priority service (wps)

Average successful queuing time for WPS user, S11 (wps_1)

Use: Indicates the average successful queuing time for a WPS user.

Avg(AVE_SUCC_WPS_QUEUE_TIME/WPS_DENOMINATOR_3)Counters from table(s):p_nbsc_wps

Figure 958. Average successful queuing time for WPS user, S11 (wps_1)

Average occupied FTCHs for WPS user, S11 (wps_2)

Use: Indicates the average occupied FTCHs for a WPS user.

Avg(WPS_AVE_OCCU_FTCH_COUNT/WPS_DENOMINATOR_1)

Counters from table(s):p_nbsc_wps

Figure 959. Average occupied FTCHs for WPS user, S11 (wps_2)

Average occupied HTCHs for WPS user, S11 (wps_3)

Use: Indicates the average occupied HTCHs for a WPS user.

Avg(WPS_AVE_OCCU_HTCH_COUNT/WPS_DENOMINATOR_2)



Counters from table(s):p_nbsc_wps

Figure 960. Average occupied HTCHs for WPS user, S11 (wps_3)

2.48 DFCA

Average BSC - BSC delay, S11 (dfca_1)

Description: Average delay between Radio Resource Managers of theBSCs.

Use: Indicates the transmission of BSC (BTS) measurements toneighbouring BSCs.

BSC_BSC_DELAYavg (---------------------) x 100

BSC_BSC_DENOMINATOR1

Counters from table(s):p_nbsc_bsc_bsc

Unit: seconds

Figure 961. Average BSC - BSC delay, S11 (dfca_1)

Total DFCA assignment requests, S11 (dfca_2)

Use: Indicates the total number of DFCA requests.

Sum(SUCC_DFCA_ASS+ SOFT_BLOCKED_DFCA_ASS_DUETO_CI+ SOFT_BLOCKED_DFCA_ASS_DUETO_CN)

Counters from table(s):p_nbsc_dfca

Figure 962. Total DFCA assignment requests, S11 (dfca_2)

DFCA assignment success ratio, S11 (dfca_3)

Use: Indicates the ratio of successful DFCA assignments to theDFCA assignment requests. Note that soft-blocked DFCAassignment requests are put to normal channel searchprocedure.

Sum(SUCC_DFCA_ASS) ; total successful assignments100 * -----------------------

( dfca_2 ) ; total DFCA assignment requests




Unit: %

Figure 963. DFCA assignment success ratio, S11 (dfca_3)

Most optimal DFCA assignment success ratio, S11 (dfca_4)

Description: Success ratio of most optimal DFCA assignments.Use: Indicates the ratio of most optimal DFCA assignments to the

DFCA assignment requests.1. Due to high MCMU load it may not be possible to continuefinding the most optimal channel, and the best possiblechannel2. Soft-blocked DFCA assignment requests are put to thenormal channel search procedure.

Sum(SUCC_DFCA_ASS - SUCC_DFCA_ASS_HIGH_LOAD) ; most optimal assignments100 * ---------------------------------------------

( dfca_2 ) ; total DFCA assignments

Counters from table(s):p_nbsc_dfcaUnit: %

Figure 964. Most optimal DFCA assignment success ratio, S11 (dfca_4)

Total soft-blocked DFCA assignments, S11 (dfca_5)

Description: Soft-blocked DFCA assignmentsUse: Indicates the DFCA assignment requests that could not be

served through the DFCA channel assignment procedure andput to the normal channel assignment procedure.

Sum(SOFT_BLOCKED_DFCA_ASS_DUETO_CI + SOFT_BLOCKED_DFCA_ASS_DUETO_CN)


Figure 965. Total soft-blocked DFCA assignments, S11 (dfca_5)

DFCA soft-blocking ratio, S11 (dfca_6)

Description: Soft-blocking ratio of DFCA assignments.

( dfca_5 ) ; total soft-blocked DFCA assignment requests100 * -----------





p_nbsc_dfcaUnit: %

Figure 966. DFCA soft-blocking ratio, S11 (dfca_6)

DFCA soft-blocking ratio for C/I reason, S11 (dfca_7)

Description: Soft-blocking ratio of DFCA assignments due to C/I reasonalone.

Use: Indicates the ratio of only C/I reason soft-blocked DFCAassignment requests to total DFCA assignment requests.

Sum(SOFT_BLOCKED_DFCA_ASS_DUETO_CI)100 * ---------------------------------------------



Figure 967. DFCA soft-blocking ratio for C/I reason, S11 (dfca_7)

DFCA soft-blocking ratio for C/N reason, S11 (dfca_8)

Description: Soft-blocking ratio of DFCA assignments due to C/N reasonalone.

Use: Indicates the ratio of only C/N reason soft-blocked DFCAassignment requests to total DFCA assignment requests.

Sum(SOFT_BLOCKED_DFCA_ASS_DUETO_CN)100 * --------------------------------------------

( dfca_2 ) ; total dfca assignment requests


Figure 968. DFCA soft-blocking ratio for C/N reason, S11 (dfca_8)

Total number of DFCA channel assignments, S11 (dfca_9)

Use: A reference for indicating the share in each DFCA C/Iestimate.

Sum(DFCA_C_I_TG_UL+ DFCA_C_I_TG_1_UL+ DFCA_C_I_TG_2_UL+ DFCA_C_I_TG_3_UL+ DFCA_C_I_TG_4_UL+ DFCA_C_I_TG_5_UL+ DFCA_C_I_TG_6_UL+ DFCA_C_I_TG_7_UL+ DFCA_C_I_TG_8_UL+ DFCA_C_I_TG_9_UL+ DFCA_C_I_TG_10_UL



+ DFCA_C_I_TG_11_UL+ DFCA_C_I_TG_12_UL+ DFCA_C_I_TG_13_UL+ DFCA_C_I_TG_14_UL+ DFCA_C_I_TG_15_UL+ DFCA_C_I_TG_16_UL+ DFCA_C_I_TG_17_UL+ DFCA_C_I_TG_18_UL+ DFCA_C_I_TG_19_UL+ DFCA_C_I_TG_20_UL+ DFCA_C_I_TG_ABOVE_20_UL+ DFCA_C_I_TG_M_1_UL+ DFCA_C_I_TG_M_2_UL+ DFCA_C_I_TG_M_3_UL+ DFCA_C_I_TG_M_4_UL+ DFCA_C_I_TG_M_5_UL+ DFCA_C_I_TG_M_6_UL+ DFCA_C_I_TG_M_7_UL+ DFCA_C_I_TG_M_8_UL+ DFCA_C_I_TG_M_9_UL+ DFCA_C_I_TG_M_10_UL+ DFCA_C_I_TG_M_11_UL+ DFCA_C_I_TG_M_12_UL+ DFCA_C_I_TG_M_13_UL+ DFCA_C_I_TG_M_14_UL+ DFCA_C_I_TG_M_15_UL+ DFCA_C_I_TG_BELOW_M_15_UL)


Figure 969. Total number of DFCA channel assignments, S11 (dfca_9)

Peak BSC - BSC delay (dfca_10)

Description: Average delay between Radio Resource Managers of theBSCs.

Use: Indicates the peak delay in transmission of BSC (BTS)measurements to neighbouring BSCs.

max(BSC_BSC_PEAK_DELAY)*100

Counters from table(s):p_nbsc_bsc_bsc

Unit: seconds

Figure 970. Peak BSC - BSC delay (dfca_10)

2.49 NCCR

Total NCCR attempts (nccr_1)

Use: Total NCCR attempts include an attempt when any of NCCRtriggers is fulfilled.



Sum(a.NCCR_NOT_STARTED_DUE_AC+ b.NCCR_QC_TRIG_NO_GOOD_NEIG+ b.NCCR_SERV_ISNCCR_NO_GOOD_NEIG+ a.PCCO_TO_GPRS_MS_DUE_PWR_BDGT+ a.PCCO_TO_EGPRS_MS_DUE_PWR_BDGT+ a.PCCO_SENT_DUE_SERV_ISNCCR+ a.PCCO_SENT_DUE_COVERAGE_ISNCCR+ a.PCCO_SENT_DUE_QUAL_CTRL)

Counters from table(s):a = P_NBSC_CELL_RESELECTIONb = P_NBSC_PACKET_CONTROL_UNIT

Unit: Number

Figure 971. Total NCCR attempts (nccr_1)

Total NCCR setup failures (nccr_2)

Description: Total NCCR setup failures.

Sum (a.NCCR_NOT_STARTED_DUE_AC+ b.NCCR_QC_TRIG_NO_GOOD_NEIG+ b.NCCR_SERV_ISNCCR_NO_GOOD_NEIG)


Unit: Number

Figure 972. Total NCCR setup failures (nccr_2)

NCCR setup failure ratio (nccr_3)

Description: Ratio of failed NCCR attempts out of all attempts.

100 * (nccr_1 / nccr_2 )


Unit: %

Figure 973. NCCR setup failure ratio (nccr_3)

Total started NCCRs (nccr_4)

Description: Shows the total started NCCRs

sum(a.PCCO_TO_GPRS_MS_DUE_PWR_BDGT+ a.PCCO_TO_EGPRS_MS_DUE_PWR_BDGT+ a.PCCO_SENT_DUE_SERV_ISNCCR+ a.PCCO_SENT_DUE_COVERAGE_ISNCCR



+ a.PCCO_SENT_DUE_QUAL_CTRL)

Counters from table(s):a = P_NBSC_CELL_RESELECTION

Unit: Numbers

Figure 974. Total started NCCRs (nccr_4)

Total failed NCCRs (nccr_5)

Description: Total failed NCCRs

sum(+a.NCCR_FAIL_NO_RESPONSE+a.NCCR_FAIL_ASSIGNMENT_REJECT+a.NCCR_FAIL_ONGOING_CS_CONN+a.NCCR_FAIL_MS_STANDBY+a.NCCR_FAIL_OTHER_CAUSE+a.NCCR_FAIL_NO_FLUSH_IN_TIME)


Unit: Numbers

Figure 975. Total failed NCCRs (nccr_5)

Share of failed NCCRs returned to old cell (nccr_6)

Description: Share of failed NCCRs returned to old cell.

Sum(NCCR_SUCC_MS_RET_TO_OLD_CELL)100 * ---------------------------------

Sum(NCCR_SUCC_FLUSH_RECEIVED)


Unit: %

Figure 976. Share of failed NCCRs returned to old cell (nccr_6)

Share of started NCCRs for GPRS MS due to power budget in total NCCRs(nccr_7)

Description: Share of started NCCRs for GPRS MS due to power budget intotal NCCRs.

Sum(PCCO_TO_GPRS_MS_DUE_PWR_BDGT)100 * ---------------------------------

nccr_4




Unit: %

Figure 977. Share of started NCCRs for GPRS MS due to power budget in totalNCCRs (nccr_7)

Share of started NCCRs for EGPRS MS due to power budget in total NCCRs(nccr_8)

Description: Share of started NCCRs for EGPRS MS due to power budgetin total NCCRs.

Sum(PCCO_TO_EGPRS_MS_DUE_PWR_BDGT)100 * ----------------------------------

nccr_4


Unit: %

Figure 978. Share of started NCCRs for EGPRS MS due to power budget in totalNCCRs (nccr_8)

Share of started NCCRs due to ISNCCR service in total NCCRs (nccr_9)

Description: Share of started NCCRs due to service based criteria for Inter-System NCCR in total NCCRs.

Sum(PCCO_SENT_DUE_SERV_ISNCCR)100 * ------------------------------

nccr_4


Unit: %

Figure 979. Share of started NCCRs due to ISNCCR service in total NCCRs(nccr_9)

Share of started NCCRs due to ISNCCR coverage in total NCCRs (nccr_10)

Description: Share of started NCCRs due to coverage based criteria forInter-System NCCR in total NCCRs.

Sum(PCCO_SENT_DUE_COVERAGE_ISNCCR)100 * ----------------------------------

nccr_4




Unit: %

Figure 980. Share of started NCCRs due to ISNCCR coverage in total NCCRs(nccr_10)

Share of started NCCRs due quality control in total NCCRs (nccr_11)

Description: Share of started NCCRs due to quality control (QC) criteria intotal NCCRs.

Sum(PCCO_SENT_DUE_QUAL_CTRL)100 * ----------------------------

nccr_4


Unit: %

Figure 981. Share of started NCCRs due quality control in total NCCRs(nccr_11)

Number of network controlled cell reselections compared to data amount(nccr_12)

Description: Number of NCCRs per payload.

nccr_4--------------------------------------------------------(trf_213c+trf_212c+trf_215a+trf_214a)/(1024* 1024* 1024)

Counters from table(s):P_NBSC_CELL_RESELECTION

Unit: number

Figure 982. Number of network controlled cell reselections compared to dataamount (nccr_12)

Successful NCCRs ratio (nccr_13)

Description: Share of successful NCCRs.

nccr_succ_flush_received100 * ----------------------------

nccr_1




Unit: %

Figure 983. Successful NCCRs ratio (nccr_13)

Average duration of successful NCCRs (nccr_14)

Use: Indicates the average duration of successfully executedNCCR procedures.

ave_nccr_duration_sum * 100----------------------------nccr_succ_flush_received


Unit: s

Figure 984. Average duration of successful NCCRs (nccr_14)

Average duration of successful NCCRs (nccr_14a)

Use: Indicates the average duration of successfully executedNCCR procedures.

ave_nccr_duration_sum / 100----------------------------nccr_succ_flush_received

Counters from table(s):P_NBSC_CELL_RESELECTION

Unit: s

Figure 985. Average duration of successful NCCRs (nccr_14a)

2.50 Packet flow context (pfc)

PFC creation success ratio (pfc_1)

Description: Indicates the ratios of PFC creation attempts to thesuccessfully created PFCs.

Note: PFCs created with downgraded QoS are consideredsuccessful. PFC creation attempts are not duplicated insegment when downgraded QoS is downgraded.

Sum(NON_PREDEF_PFC_CREATE_SUCC+PREDEF_UL_PFC_CREATE_SUCC+PREDEF_DL_PFC_CREATE_SUCC)

100 * -------------------------------Sum(PFC_CREATE_ATTEMPT)



Counters from table(s):P_NBSC_EQOS

Unit: %

Figure 986. PFC creation success ratio (pfc_1)

PFC transfer failure ratio (pfc_8)

Description: Ratio of failed PFC Transfers.

Sum(PFC_TRANSF_FAIL_DUE_RADIO_RES+PFC_TRANSFER_FAIL_DUE_EDAP)

100 * ------------------------------------Sum(PFC_TRANSFER_STARTED)


Unit: %

Figure 987. PFC transfer failure ratio (pfc_8)

Share of abnormal PFC releases (pfc_11)

Description: Share of abnormal PFC relases to all PFC releases.

Sum(PFC_DELETE_DUE_ABNORMAL)100 * ----------------------------------

Sum(PFC_DELETE_DUE_ABNORMAL+PFC_DELETE_SGSN_REQ+PFC_DELETE_DUE_PFTIMER+PFC_DELETE_INTER_PCU_CELL_UPD)


Figure 988. Share of abnormal PFC releases (pfc_11)

Number of successful PFC creations (pfc_13)

Description: Total number of successfully created PFCs.

Sum(NON_PREDEF_PFC_CREATE_SUCC+ PREDEF_UL_PFC_CREATE_SUCC+ PREDEF_DL_PFC_CREATE_SUCC)




Unit: Numbers

Figure 989. Number of successful PFC creations (pfc_13)

2.51 Quality control action (qca)

Description: Total number of started quality control actions.

Total started quality control actions (qca_1)

Sum(QC_TBF_REALLOC_DUE_THROUGHPUT+QC_TBF_REALLOC_DUE_BLER+QC_TBF_REALLOC_DUE_RB_BITRATE+QC_NCCR_DUE_THROUGHPUT+QC_NCCR_DUE_BLER+QC_NCCR_DUE_RB_BITRATE+QC_PFC_MODIFY_DUE_THROUGHPUT+QC_PFC_MODIFY_DUE_BLER+QC_PFC_MODIFY_DUE_RB_BITRATE+QC_PFC_DELETE_DUE_THROUGHPUT+QC_PFC_DELETE_DUE_BLER+QC_PFC_DELETE_DUE_RB_BITRATE)


Unit: Numbers

Figure 990. Total started quality control actions (qca_1)

Total started TBF reallocation (qca_2)

Description: Total number of started TBF reallocations due to throughput,BLER or RB bitrate reasons.

Sum(QC_TBF_REALLOC_DUE_THROUGHPUT+QC_TBF_REALLOC_DUE_BLER+QC_TBF_REALLOC_DUE_RB_BITRATE)


Unit: Numbers

Figure 991. Total started TBF reallocation (qca_2)

Total started NCCRs (qca_3)

Description: Total number of started NCCRs due to Throughput, BLER orRB Bitrate reasons.



Sum(QC_NCCR_DUE_THROUGHPUT+QC_NCCR_DUE_BLER+QC_NCCR_DUE_RB_BITRATE)


Unit: Numbers

Figure 992. Total started NCCRs (qca_3)

Total started PFC Modify (qca_4)

Description: Total number of started PFC Modify due to throughput,BLER or RB bitrate reasons. PFC Modify means QualityControl function triggers PFC modification procedure withdowngraded ABQP.

Use: This KPI is relevant only for streaming and legacy streaming.

Sum(QC_PFC_MODIFY_DUE_THROUGHPUT+QC_PFC_MODIFY_DUE_BLER+QC_PFC_MODIFY_DUE_RB_BITRATE)


Unit: Numbers

Figure 993. Total started PFC Modify (qca_4)

Total started PFC delete (qca_5)

Description: Total number of started PFC Delete procedures due toThroughput, BLER or RB Bitrate reasons.

Use: This KPI is relevant only for Streaming and legacy Streaming.

Sum(QC_PFC_DELETE_DUE_THROUGHPUT+QC_PFC_DELETE_DUE_BLER+QC_PFC_DELETE_DUE_RB_BITRATE)


Unit: Numbers

Figure 994. Total started PFC delete (qca_5)

Share of TBF reallocations in total started QC actions (qca_6)

qca_2----- * 100qca_1




Unit: %

Figure 995. Share of TBF reallocations in total started QC actions (qca_6)

Share of NCCRs in total started QC actions (qca_7)

qca_3----- * 100qca_1


Unit: %

Figure 996. Share of NCCRs in total started QC actions (qca_7)

Share of PFC modifications in total started QC actions (qca_8)

qca_4----- * 100qca_1


Unit: %

Figure 997. Share of PFC modifications in total started QC actions (qca_8)

Share of PFC deletion in total started QC actions (qca_9)

qca_5----- * 100qca_1


Unit: %

Figure 998. Share of PFC deletion in total started QC actions (qca_9)

Share of started TBF reallocations due to throughput (qca_10)

Sum(QC_TBF_REALLOC_DUE_THROUGHPUT)



---------------------------------- * 100qca_2


Unit: %

Figure 999. Share of started TBF reallocations due to throughput (qca_10)

Share of started TBF reallocations due to BLER (qca_11)

Sum(QC_TBF_REALLOC_DUE_BLER)---------------------------- * 100

qca_2


Unit: %

Figure 1000. Share of started TBF reallocations due to BLER (qca_11)

Share of started TBF reallocations due to RB bitrate (qca_12)

Sum(QC_TBF_REALLOC_DUE_RB_BITRATE)---------------------------------- * 100

qca_2


Unit: %

Figure 1001. Share of started TBF reallocations due to RB bitrate (qca_12)

Share of started NCCRs due to throughput (qca_13)

Sum(QC_NCCR_DUE_THROUGHPUT)-------------------------- * 100

qca_3


Unit: %

Figure 1002. Share of started NCCRs due to throughput (qca_13)



Share of started NCCRs due to BLER (qca_14)

Sum(QC_NCCR_DUE_BLER)--------------------- * 100

qca_3


Unit: %

Figure 1003. Share of started NCCRs due to BLER (qca_14)

Share of started NCCRs due to RB bitrate (qca_15)

Sum(QC_NCCR_DUE_RB_BITRATE)--------------------------- * 100

qca_3


Unit: %

Figure 1004. Share of started NCCRs due to RB bitrate (qca_15)

Share of started PFC modification due to throughput (qca_16)

Sum(QC_PFC_MODIFY_DUE_THROUGHPUT)--------------------------------- * 100

qca_4


Unit: %

Figure 1005. Share of started PFC modification due to throughput (qca_16)

Share of started PFC modification due to BLER (qca_17)

Sum(QC_PFC_MODIFY_DUE_BLER)--------------------------- * 100

qca_4


Unit: %

Figure 1006. Share of started PFC modification due to BLER (qca_17)



Share of started PFC modification due to RB bitrate (qca_18)

Sum(QC_PFC_MODIFY_DUE_RB_BITRATE)--------------------------------- * 100

qca_4


Unit: %

Figure 1007. Share of started PFC modification due to RB bitrate (qca_18)

Share of started PFC deletion due to throughput (qca_19)

Sum(QC_PFC_DELETE_DUE_THROUGHPUT)--------------------------------- * 100

qca_5


Unit: %

Figure 1008. Share of started PFC deletion due to throughput (qca_19)

Share of started PFC deletion due to BLER (qca_20)

Sum(QC_PFC_DELETE_DUE_BLER)--------------------------- * 100

qca_5


Unit: %

Figure 1009. Share of started PFC deletion due to BLER (qca_20)

Share of started PFC deletion due to RB bitrate (qca_21)

Sum(QC_PFC_DELETE_DUE_RB_BITRATE)--------------------------------- * 100

qca_5


Unit: %

Figure 1010. Share of started PFC deletion due to RB bitrate (qca_21)



2.52 Gb over IP (gbip)

Ratio of discarded received packets (gbip_1)

Description: Ratio of discarded received packets to all received packets.

Sum(DISCARDED_RECEIVED_PACKETS)100 * ---------------------------------------------------------

Sum(NBR_OF_RCVD_DATA_PACKETS+NBR_OF_RCVD_SIGNAL_PACKETS)

Counters from table(s):P_NBSC_GB_OVER_IP

Unit: Numbers

Figure 1011. Ratio of discarded received packets (gbip_1)


bss network doctor formulas 2007

Documents