Wcdma rnc p6 kpi description

Ericsson Internal 1 (450)

Prepared (also subject responsible if other) No.

ESM/GB/A H.F. Soon; TEI/RFN S.Sestito, D.Mingione, 5/1553-FAF 102 358 Uen Approved Checked Date Rev Reference

EAB/GD/PP [Sebastian Schaplitz] 2008-06-09 A

WCDMA RNC P6 KPIs Description

Abstract

The purpose of this document is to provide a reference guideline to define and describe WCDMA RNC KPI related to UTRAN P6 release.

Delta information concerning new/removed/changed counters from P5 to P6 is included in this document into Note or KPI Description text fields.

This document is to be entirely considered for Ericsson internal use only.

Therefore the present document, as well as each of its single part or chapter, is not to be handed over to any external customer. Please refer to Reference list (chap. 13) for Customer Product Information documents available for external customer consultation.





Contents

1 Introduction........................................................................................12 1.1 Purpose of the document ..................................................................12 1.2 Important Remark..............................................................................12 2 Accessibility.......................................................................................13 2.1 Iu Signaling........................................................................................13 2.1.1 CS Iu Signaling Setup Success Rate ................................................13 2.1.2 PS Iu Signaling Setup Success Rate ................................................14 2.2 Overall Accessibility ..........................................................................15 2.2.1 Overall Accessibility Success Rate Speech ......................................15 2.2.2 Overall Accessibility Success Rate AMR-NB ....................................15 2.2.3 Overall Accessibility Success Rate AMR-WB ...................................16 2.2.4 Overall Accessibility Success Rate CS57 .........................................17 2.2.5 Overall Accessibility Success Rate CS64 .........................................18 2.2.6 Overall Accessibility Success Rate PS Streaming ............................19 2.2.7 Overall Accessibility Success Rate PS Streaming 128 .....................20 2.2.8 Overall Accessibility Success Rate PS Interactive ............................21 2.2.9 Overall Accessibility Success Rate PS Interactive DCH/FACH ........22 2.2.10 Overall Accessibility Success Rate PS Interactive HS......................23 2.2.11 Overall Accessibility Success Rate PS Interactive EUL....................24 2.2.12 Overall Accessibility Success Rate PS Streaming HS ......................24 2.3 Paging ...............................................................................................26 2.3.1 RNC Type 1 Paging Attempt Success Rate......................................26 2.3.2 RNC Type 2 Paging Attempts ...........................................................27 2.3.3 CN paging to UE in URA State..........................................................27 2.3.4 UTRAN Paging to UE in URA State ..................................................28 2.4 RRC Setup Complete........................................................................30 2.4.1 RRC Setup Success Rate .................................................................30 2.4.2 RRC Setup Success Rate CS ...........................................................31 2.4.3 RRC Setup Success Rate PS ...........................................................32 2.4.4 RRC Terminating Success Rate .......................................................33 2.4.5 RRC Terminating Success Rate CS..................................................35 2.4.6 RRC Terminating Success Rate PS..................................................36 2.4.7 RRC Terminating Call Percentage ....................................................37 2.4.8 RRC Terminating CS Call Percentage ..............................................38 2.4.9 RRC Terminating PS Call Percentage ..............................................39 2.5 RRC Establishment Causes..............................................................41 2.5.1 Low Priority Signaling Cause ............................................................41 2.5.2 Conversational Call RRC Establishment ...........................................41 2.5.3 Interactive and Background Call RRC Establishment .......................42 2.5.4 IRAT Cell Reselection Cause............................................................43 2.5.5 IRAT Cell Change Cause ..................................................................44 2.6 RRC Setup Failure Causes ...............................................................45 2.6.1 RRC Setup Module MP Load Control Failure....................................45 2.6.2 RRC Setup Admission Control Failure ..............................................45 2.6.3 RRC Setup Failure after Admission ..................................................47 2.6.4 RRC Setup Radio Failure..................................................................48 2.6.5 RRC Failures Admission CS .............................................................49





2.6.6 RRC Failures Admission PS..............................................................49 2.6.7 RL Failures due to Admission ...........................................................50 2.6.8 Total Failures after Admission...........................................................51 2.6.9 Request Denied due to Admission ....................................................52 2.6.10 RRC Request Denied due to License Capacity.................................53 2.6.11 CS RRC Request Denied due to License Capacity...........................53 2.6.12 PS RRC Request Denied due to License Capacity...........................54 2.6.13 CS RRC Request Blocked due to Node............................................55 2.6.14 PS RRC Request Blocked due to Node ............................................56 2.6.15 CS RRC Request Blocked due to TN................................................57 2.6.16 PS RRC Request Blocked due to TN................................................58 2.7 RAB Establishment ...........................................................................59 2.7.1 RAB Establishment Success Rate Speech .......................................59 2.7.2 RAB Establishment Success Rate AMR-NB .....................................60 2.7.3 RAB Establishment Success Rate AMR-WB ....................................61 2.7.4 RAB Establishment Success Rate CS57 ..........................................62 2.7.5 RAB Establishment Success Rate CS64 ..........................................63 2.7.6 RAB Establishment Success Rate PS Streaming .............................64 2.7.7 RAB Establishment Success Rate PS Streaming 128 ......................65 2.7.8 RAB Establishment Success Rate PS Interactive .............................66 2.7.9 RAB Establishment Success Rate PS Interactive DCH/FACH .........67 2.7.10 RAB Establishment Success Rate PS Interactive HS.......................69 2.7.11 RAB Establishment Success Rate PS Streaming HS .......................70 2.7.12 RAB Establishment Success Rate PS Interactive EUL.....................71 2.7.13 RAB Establishment Success Rate Emergency Call ..........................72 2.8 RAB Establishment Failure Causes ..................................................73 2.8.1 Invalid RAB Establishment Attempts.................................................73 2.8.2 UE Capability Limit RAB Establishment Failure ................................73 2.8.3 RAB Establishment Blocked due to TN Speech................................74 2.8.4 RAB Establishment Blocked due to TN CS57...................................75 2.8.5 RAB Establishment Blocked due to TN CS64...................................76 2.8.6 RAB Establishment Blocked due to TN PS Interactive Non HS........77 2.8.7 RAB Establishment Blocked due to TN PS Streaming Non HS ........77 2.8.8 RAB Establishment Blocked due to TN PS Interactive HS................78 2.8.9 RAB Establishment Blocked due to TN PS Streaming HS................79 2.8.10 RAB Establishment Blocked due to Node Speech............................80 2.8.11 RAB Establishment Blocked due to Node CS57 ...............................81 2.8.12 RAB Establishment Blocked due to Node CS64 ...............................82 2.8.13 RAB Establishment Blocked due to Node PS Interactive Non HS ....82 2.8.14 RAB Establishment Blocked due to Node PS Streaming Non HS ....83 2.8.15 RAB Establishment Blocked due to Node PS Interactive HS............84 2.8.16 RAB Establishment Blocked due to Node PS Streaming HS............85 2.8.17 RAB Establishment Blocked due to RN PS Streaming HS ...............86 2.9 Inter Frequency Load Sharing...........................................................87 2.9.1 IFLS Activity Rate..............................................................................87 2.9.2 IFLS Activity Rate CS........................................................................87 2.9.3 IFLS Activity Rate PS ........................................................................88 2.9.4 IFLS Return Rate ..............................................................................89 2.10 GSM Redirected RRC Connection Setup .........................................91 2.10.1 Directed Retry Activity Rate ..............................................................91 2.10.2 Directed Retry Success Rate ............................................................92





3 Availability .........................................................................................93 3.1 R99 Cell Unavailability ......................................................................93 3.2 HS Cell Unavailability ........................................................................94 3.3 EUL Cell Unavailability ......................................................................95 3.4 MBMS Cell Unavailability ..................................................................96 4 Retainability.......................................................................................97 4.1 RRC Drop Rate .................................................................................97 4.1.1 Overall RRC Drop Rate DCH ............................................................97 4.1.2 Overall RRC Drop Rate FACH ..........................................................98 4.1.3 RRC Drop Rate Speech ....................................................................99 4.1.4 RRC Drop Rate CS57 .....................................................................100 4.1.5 RRC Drop Rate CS64 .....................................................................101 4.1.6 RRC Drop Rate PS Streaming ........................................................102 4.1.7 RRC Drop Rate PS Streaming 128 .................................................103 4.1.8 RRC Drop Rate PS Interactive........................................................104 4.2 RAB Drop Rate................................................................................106 4.2.1 RAB Drop Rate Speech ..................................................................106 4.2.2 RAB Drop Rate AMR-NB ................................................................107 4.2.3 RAB Drop Rate AMR-WB................................................................108 4.2.4 RAB Drop Rate CS57......................................................................109 4.2.5 RAB Drop Rate CS64......................................................................110 4.2.6 RAB Drop Rate PS Streaming ........................................................111 4.2.7 RAB Drop Rate PS Streaming 128 .................................................112 4.2.8 RAB Drop Rate PS Interactive ........................................................113 4.2.9 RAB Drop Rate PS Interactive DCH/FACH.....................................114 4.2.10 RAB Drop Rate PS Interactive HS ..................................................116 4.2.11 RAB Drop Rate PS Streaming HS ..................................................117 4.2.12 RAB Drop Rate PS Interactive EUL ................................................118 4.2.13 RAB Drop Rate PS Interactive URA................................................119 4.3 Minutes per Drop.............................................................................120 4.3.1 Minutes per Drop Speech................................................................120 4.3.2 Minutes per Drop AMR-NB..............................................................121 4.3.3 Minutes per Drop AMR-WB.............................................................122 4.3.4 Minutes per Drop CS57...................................................................123 4.3.5 Minutes per Drop CS64...................................................................125 4.3.6 Minutes per Drop PS Streaming......................................................126 4.3.7 Minutes per Drop PS Streaming 128...............................................127 4.3.8 Minutes per Drop PS Interactive .....................................................129 4.3.9 Minutes per Drop PS DCH/FACH Data...........................................130 4.3.10 Minutes per Drop HS Data ..............................................................132 4.3.11 Minutes per Drop PS Streaming HS................................................133 4.3.12 Minutes per Drop EUL.....................................................................135 4.4 Average Holding Time.....................................................................137 4.4.1 Average Holding Time Speech........................................................137 4.4.2 Average Holding Time AMR-NB......................................................138 4.4.3 Average Holding Time AMR-WB.....................................................139 4.4.4 Average Holding Time CS57...........................................................140 4.4.5 Average Holding Time CS64...........................................................141 4.4.6 Average Holding Time PS Streaming..............................................142 4.4.7 Average Holding Time PS Streaming 128.......................................143 4.4.8 Average Holding Time Ps Interactive ..............................................145





4.4.9 Average Holding Time PS Interactive DCH/FACH..........................146 4.4.10 Average Holding Time PS Interactive HS .......................................148 4.4.11 Average Holding Time PS Streaming HS........................................149 4.4.12 Average Holding Time PS EUL .......................................................150 4.5 RAB Speech Drop Causes..............................................................152 4.5.1 Drop due to Soft Handover Action...................................................152 4.5.2 Drop due to Missing Neighbour.......................................................153 4.5.3 Drop due to UL Synchronization Lost..............................................154 4.5.4 Drop due to Congestion ..................................................................155 4.5.5 Drop due to IRAT Handover Lost ....................................................156 5 Integrity............................................................................................158 5.1 BLER ...............................................................................................158 5.1.1 RABs UL BLER ...............................................................................158 5.1.2 DCH BLER ......................................................................................159 5.1.3 RACH BLER....................................................................................159 5.1.4 EUL MAC-es PDU Delivery Failure Rate ........................................160 5.1.5 EUL HARQ Retransmission Rate PS Data .....................................162 5.1.6 EUL HARQ Retransmission Rate SRB ...........................................163 5.2 Packet Latency, Delay and Jitter .....................................................164 5.2.1 PS Interactive Latency ....................................................................164 5.2.2 R99 PS Interactive Latency.............................................................165 5.2.3 HS PS Interactive Latency ..............................................................166 5.2.4 HS PS Streaming Latency...............................................................167 5.2.5 HS EUL PS Interactive Latency ......................................................168 5.2.6 PS Interactive Delay........................................................................168 5.2.7 R99 PS Interactive Delay DL...........................................................169 5.2.8 HS PS Interactive Delay DL ............................................................170 5.2.9 HS EUL PS Interactive Delay..........................................................171 5.2.10 R99 PS Interactive Delay DL/UL .....................................................172 5.2.11 HS PS Interactive Delay UL ............................................................173 5.2.12 R99 PS Interactive Jitter..................................................................174 5.2.13 HS PS Interactive Jitter ...................................................................175 5.2.14 HS EUL Interactive Jitter .................................................................176 6 Channel Switching...........................................................................177 6.1 Channel Switching FACH-IDLE.......................................................177 6.1.1 Channel Switching FACH-IDLE Count ............................................177 6.2 Channel Switching Failure Rate ......................................................178 6.2.1 Channel Upswitch Failure Rate FACH-HS......................................178 6.2.2 Channel Switch Failure Rate FACH-URA .......................................178 6.2.3 Channel Switch Failure Rate URA-FACH .......................................179 6.2.4 Channel Upswitch Failure Rate DL Low Rate .................................180 6.2.5 Channel Upswitch Failure Rate UL Low Rate .................................181 6.2.6 Channel Upswitch Failure Rate DL Medium Rate ...........................182 6.2.7 Channel Upswitch Failure Rate UL Medium Rate ...........................183 6.2.8 Channel Upswitch Failure Rate DL High Rate ................................184 6.2.9 Channel Upswitch Failure Rate UL High Rate ................................185 6.2.10 Channel Upswitch Failure Rate DL HS ...........................................186 6.2.11 Channel Upswitch Failure Rate UL EUL .........................................187 6.2.12 Channel Downswitch Failure Rate ..................................................188 7 Traffic ..............................................................................................189 7.1 PS Throughput ................................................................................189





7.1.1 PS Data Average Throughput Net...................................................189 7.1.2 HS Data Average Throughput Net ..................................................190 7.1.3 PS Data Retransmission Rate.........................................................191 7.1.4 HS Data Retransmission Rate ........................................................192 7.1.5 PS Data Average User Throughput DL ...........................................193 7.1.6 PS Streaming 64 Average User Throughput DL .............................194 7.1.7 PS Streaming 128 Average User Throughput DL ...........................195 7.1.8 PS Streaming HS Average User Throughput DL ............................196 7.1.9 HS Data Average User Throughput DL...........................................197 7.1.10 PS Data Average User Throughput UL ...........................................197 7.1.11 PS Streaming 16 Average User Throughput UL .............................198 7.1.12 PS Streaming 32 Average User Throughput UL .............................199 7.1.13 PS Streaming 128 Average User Throughput UL ...........................200 7.1.14 EUL Data Average User Throughput UL.........................................201 7.1.15 PS Data Average Total Throughput DL...........................................202 7.1.16 HS Data Average Total Throughput DL ..........................................203 7.1.17 PS Data Average Total Throughput UL...........................................204 7.1.18 EUL Data Average Total Throughput UL ........................................205 7.1.19 PS Data RLC Net Throughput DL ...................................................206 7.1.20 PS Data RLC Net throughput UL ....................................................207 7.1.21 HS Data RLC Net Throughput DL ...................................................207 7.1.22 EUL Data RLC Net Throughput UL .................................................209 7.2 Cell Traffic .......................................................................................210 7.2.1 Cell Traffic Speech ..........................................................................210 7.2.2 Cell Traffic AMR ..............................................................................211 7.2.3 Cell Traffic AMR-WB .......................................................................212 7.2.4 Cell Traffic CS57 .............................................................................213 7.2.5 Cell Traffic CS64 .............................................................................214 7.2.6 Cell Traffic PS Streaming ................................................................215 7.2.7 Cell Traffic PS Streaming 128 .........................................................217 7.2.8 Cell Traffic Ps Interactive ................................................................218 7.2.9 Cell Traffic Ps Interactive DCH/FACH.............................................219 7.2.10 Cell Traffic PS HS ...........................................................................220 7.2.11 Cell Traffic PS Streaming HS ..........................................................221 7.2.12 Cell Traffic EUL ...............................................................................222 7.3 RNC Traffic......................................................................................224 7.3.1 RNC Traffic Speech ........................................................................224 7.3.2 RNC Traffic AMR-NB ......................................................................225 7.3.3 RNC Traffic AMR-WB......................................................................226 7.3.4 RNC Traffic CS57............................................................................227 7.3.5 RNC Traffic CS64............................................................................228 7.3.6 RNC Traffic Ps64 Stream................................................................229 7.3.7 RNC Traffic Ps128 Stream..............................................................230 7.3.8 RNC Traffic Ps Data........................................................................231 7.3.9 RNC Traffic Ps Data DCH/FACH ....................................................232 7.3.10 RNC Traffic HS................................................................................233 7.3.11 RNC Traffic Ps Streaming HS .........................................................234 7.3.12 RNC Traffic EUL..............................................................................235 7.4 Cell Traffic Volume ..........................................................................237 7.4.1 Cell Traffic Volume DL Speech .......................................................237 7.4.2 Cell Traffic Volume DL AMR-NB .....................................................237





7.4.3 Cell Traffic Volume DL AMR-WB ....................................................238 7.4.4 Cell Traffic Volume DL CS57 ..........................................................239 7.4.5 Cell Traffic Volume DL CS64 ..........................................................240 7.4.6 Cell Traffic Volume DL PS Streaming 16 ........................................241 7.4.7 Cell Traffic Volume DL PS Streaming 64 ........................................242 7.4.8 Cell Traffic Volume DL PS Streaming 128 ......................................242 7.4.9 Cell Traffic Volume DL PS Data DCH/FACH...................................243 7.4.10 Cell Traffic Volume DL PS Data HS ................................................244 7.4.11 Cell Traffic Volume DL PS Streaming HS .......................................245 7.4.12 Cell Traffic Volume DL MBMS PS Streaming 64.............................246 7.4.13 Cell Traffic Volume DL MBMS PS Streaming 128...........................247 7.4.14 Cell Traffic Volume DL MBMS PS Streaming 256...........................247 7.4.15 Cell Traffic Volume UL Speech .......................................................248 7.4.16 Cell Traffic Volume UL AMR-NB .....................................................249 7.4.17 Cell Traffic Volume UL AMR-WB ....................................................250 7.4.18 Cell Traffic Volume UL CS57 ..........................................................251 7.4.19 Cell Traffic Volume UL CS64 ..........................................................251 7.4.20 Cell Traffic Volume UL PS Streaming 16 ........................................252 7.4.21 Cell Traffic Volume UL PS Streaming 32 ........................................253 7.4.22 Cell Traffic Volume UL PS Streaming 128 ......................................254 7.4.23 Cell Traffic Volume UL PS Interactive DCH/FACH..........................255 7.4.24 Cell Traffic Volume UL PS Data EUL ..............................................256 7.5 RNC Traffic Volume ........................................................................258 7.5.1 RNC Traffic Volume DL Speech......................................................258 7.5.2 RNC Traffic Volume DL AMR-NB....................................................258 7.5.3 RNC Traffic Volume DL AMR-WB...................................................259 7.5.4 RNC Traffic Volume DL CS57.........................................................260 7.5.5 RNC Traffic Volume DL CS64.........................................................261 7.5.6 RNC Traffic Volume DL PS Streaming 16.......................................262 7.5.7 RNC Traffic Volume DL PS Streaming 64.......................................262 7.5.8 RNC Traffic Volume DL PS Streaming 128.....................................263 7.5.9 RNC Traffic Volume DL PS .............................................................264 7.5.10 RNC Traffic Volume DL Ps Data DCH/FACH..................................265 7.5.11 RNC Traffic Volume DL HS.............................................................266 7.5.12 RNC Traffic Volume UL Speech......................................................267 7.5.13 RNC Traffic Volume UL AMR-NB....................................................267 7.5.14 RNC Traffic Volume UL AMR-WB...................................................268 7.5.15 RNC Traffic Volume UL CS57.........................................................269 7.5.16 RNC Traffic Volume UL CS64.........................................................270 7.5.17 RNC Traffic Volume UL PS Streaming 16.......................................271 7.5.18 RNC Traffic Volume UL PS Streaming 32.......................................271 7.5.19 RNC Traffic Volume UL PS Streaming 128.....................................272 7.5.20 RNC Traffic Volume UL Ps Data .....................................................273 7.5.21 RNC Traffic Volume UL HS.............................................................274 7.5.22 RNC Traffic Volume UL EUL...........................................................275 8 Capacity ..........................................................................................277 8.1 Average Users.................................................................................277 8.1.1 Average Users Speech ...................................................................277 8.1.2 Average Users AMR-NB .................................................................278 8.1.3 Average Users AMR-WB.................................................................279 8.1.4 Average Users Cs Streaming Data .................................................280





8.1.5 Average Users Cs64 Data...............................................................280 8.1.6 Average Users Ps Stream 64..........................................................281 8.1.7 Average Users Ps128 Stream.........................................................282 8.1.8 Average Users Ps Data...................................................................283 8.1.9 Average Users Ps Data DCH/FACH ...............................................284 8.1.10 Average Users HS...........................................................................285 8.1.11 Average Users PS STREAM HS.....................................................286 8.1.12 Average Users EUL.........................................................................287 8.1.13 Average Users RRC Only ...............................................................288 8.1.14 Average Users URA ........................................................................289 8.2 Admission Control ...........................................................................290 8.2.1 Requests Denied due to Admission for RAB Speech......................290 8.2.2 Requests Denied due to Admission for RAB CS.............................291 8.2.3 Requests Denied due to Admission for RAB PS Streaming............292 8.2.4 Requests Denied due to Admission for RAB PS Streaming 128.....293 8.2.5 Requests Denied due to Admission for RAB PS Interactive ...........294 8.2.6 Requests Denied due to Admission for RAB PS Interactive

DCH/FACH......................................................................................295 8.2.7 Requests Denied due to Admission for RAB HS.............................296 8.2.8 Requests Denied due to Admission for EUL ...................................297 8.2.9 EUL Serving Cell Admission Reject ................................................298 8.2.10 EUL Non-serving Cell Admission Reject .........................................299 8.3 RAB Establishment Failure Causes ................................................300 8.3.1 UL ASE Limit Failure .......................................................................300 8.3.2 DL ASE Limit Failure .......................................................................301 8.3.3 Code Usage Failure ........................................................................302 8.3.4 Power Limit Failure..........................................................................303 8.3.5 SF Histogram Limit Failure..............................................................304 8.3.6 UL HW Limit Failure ........................................................................305 8.3.7 DL HW Limit Failure ........................................................................306 8.4 Congestion Control..........................................................................308 8.4.1 Congestion Time UL........................................................................308 8.4.2 Congestion Time DL........................................................................308 8.4.3 Congestion Time HS-DSCH............................................................309 8.4.4 Congestion Time IubLink Unavailable.............................................310 8.4.5 Congestion Time IubLink Congested DL.........................................311 8.4.6 Congestion Time MBMS .................................................................312 8.4.7 Congestion Control Triggered UL....................................................313 8.4.8 Congestion Control Triggered DL....................................................314 8.4.9 Release Cs Data Connection ..........................................................314 8.4.10 Downgraded PS Data Connections Cong .......................................315 8.4.11 Downgraded PS Data Connections Adm ........................................316 8.4.12 Downgraded PS Data Connections HO ..........................................317 8.4.13 Release Speech Connection...........................................................318 8.4.14 Congestion Soft Downswitch HS.....................................................318 8.4.15 Congestion Soft Downswitch EUL...................................................319 8.5 Traffic and Load ..............................................................................320 8.5.1 RNC Main Processor Load..............................................................320 8.5.2 RNC Main Processor Load Distribution...........................................320 9 Mobility Intra Frequency Handover .................................................322 9.1 Successful RL Addition ...................................................................322





9.1.1 Successful RL Addition Source Best Cell Speech...........................322 9.1.2 Successful RL Addition Source Best Cell CS64..............................323 9.1.3 Successful RL Addition Source Best Cell Packet Low ....................324 9.1.4 Successful RL Addition Source Best Cell Packet High ...................325 9.1.5 Successful RL Addition Source Best Cell Streaming ......................326 9.1.6 Successful RL Addition Source Best Cell Stand Alone ...................327 9.1.7 Successful RL Addition Target Cell .................................................328 9.2 Soft/Softer Handover Overhead ......................................................330 9.2.1 Soft/Softer Handover Overhead Speech.........................................330 9.2.2 Soft/Softer Handover Overhead AMR-NB.......................................331 9.2.3 Soft/Softer Handover Overhead AMR-WB ......................................331 9.2.4 Soft/Softer Handover Overhead CS Streaming Data ......................332 9.2.5 Soft/Softer Handover Overhead CS64 Data....................................333 9.2.6 Soft/Softer Handover Overhead PS64 Stream................................334 9.2.7 Soft/Softer Handover Overhead PS128 Stream..............................335 9.2.8 Soft/Softer Handover Overhead PS Data DCH/FACH ....................336 9.2.9 RL Soft/Softer Handover Overhead ................................................337 9.2.10 RL Soft Only Handover Overhead...................................................339 9.3 Cell Update......................................................................................341 9.3.1 Cell Update Success Rate ..............................................................341 9.4 URA Update ....................................................................................343 9.4.1 URA Update Success Rate .............................................................343 9.5 Core Network Hard Handover .........................................................344 9.5.1 CN Hard HO Outgoing Success Rate Speech ................................344 9.5.2 CN Hard HO Outgoing Success Rate CS Non-speech...................344 9.5.3 CN Hard HO Incoming Success Rate Speech ................................345 9.5.4 CN Hard HO CS Incoming Success Rate Non-speech...................346 10 Mobility IRAT Handover ..................................................................348 10.1 Compressed Mode ..........................................................................348 10.1.1 CM DL Activation Success Rate .....................................................348 10.1.2 CM UL Activation Success Rate .....................................................349 10.1.3 CM Alternative SC Usage ...............................................................350 10.1.4 CM Measurement Ratio ..................................................................351 10.1.5 Number of CM Users per Cell .........................................................352 10.2 CS IRAT HO....................................................................................354 10.2.1 IRAT HO Attempt Rate....................................................................354 10.2.2 CS IRAT HO Activity Rate...............................................................355 10.2.3 Relocation Preparation Failure Rate ...............................................356 10.2.4 CS IRAT HO Success Rate.............................................................357 10.2.5 CS IRAT Failure UE Rejection ........................................................358 10.2.6 CS IRAT HO Failure Physical Channel ...........................................359 10.2.7 CS IRAT HO Failure Not Physical Channel.....................................360 10.2.8 CS IRAT HO Failure UE Lost ..........................................................361 10.2.9 CS Incoming IRAT HO Success Rate .............................................363 10.2.10 CS Incoming IRAT HO Failure Rate due to Admission ...................364 10.3 PS IRAT ..........................................................................................365 10.3.1 PS IRAT (UMTS to GSM) Success Rate.........................................365 10.3.2 PS IRAT HO Failure Rate ...............................................................366 10.3.3 PS IRAT HO Incoming Success Rate .............................................366 10.3.4 PS IRAT HO Incoming Failure Rate................................................367 10.4 IRAT Cell Reselection .....................................................................369





10.4.1 IRAT Cell Reselection Success Rate ..............................................369 10.4.2 IRAT Cell Reselection Failure Rate due to Congestion...................370 10.5 Service Based Handover.................................................................371 10.5.1 Service Based HO Success Rate....................................................371 10.5.2 Service Based HO Percentage .......................................................372 10.5.3 Service Based HO Failure Rate ......................................................373 10.5.4 Service Based GSM HO Activity Rate.............................................374 10.5.5 Service Based GSM HO Success Rate...........................................375 11 Mobility Inter Frequency Handover .................................................376 11.1 Inter frequency Handover................................................................376 11.1.1 IF HO Radio Link Addition Failure...................................................376 11.1.2 IF HO Success Rate CS Speech ....................................................377 11.1.3 IF HO Success Rate CS64..............................................................378 11.1.4 IF HO Success Rate PS Interactive Less Than 64..........................379 11.1.5 IF HO Success Rate PS Interactive Greater Than 64.....................380 11.1.6 IF HO Success Rate Streaming ......................................................382 11.1.7 IF HO Failure Rate Speech .............................................................383 11.1.8 IF HO Failure Rate CS 64 ...............................................................384 11.1.9 IF HO Failure Rate PS Interactive Less Than 64 ............................385 11.1.10 IF HO Failure Rate PS Interactive Greater Than 64........................387 11.1.11 IF HO Failure Rate Streaming Other ...............................................388 11.2 Inter Frequency Hard HO ................................................................390 11.2.1 IF Hard HO HS Success Rate.........................................................390 11.2.2 IF Hard HO EUL Success Rate.......................................................391 11.2.3 IF Hard HO Hs Success Rate Incoming..........................................392 11.2.4 IF Hard HO Hs Success Rate Outgoing..........................................393 11.2.5 IF Hard HO Hs Failure Rate Incoming ............................................394 11.2.6 IF Hard HO Hs Failure Rate Outgoing ............................................395 11.2.7 IF Hard HO Eul Success Rate Incoming .........................................395 11.2.8 IF Hard HO Eul Success Rate Outgoing .........................................396 11.2.9 IF Hard HO EUL Failure Rate Incoming..........................................397 11.2.10 IF Hard HO Eul Failure Rate Outgoing............................................398 11.2.11 IF Hard HO PS Streaming Hs Success Rate Incoming...................399 11.2.12 IF Hard HO PS Streaming HS Success Rate Outgoing ..................400 11.2.13 IF Hard HO PS Streaming HS Failure Rate Incoming.....................401 11.2.14 IF Hard HO PS Streaming Hs Failure Rate Outgoing .....................402 12 Mobility HSDPA , EUL and PS Streaming HS.................................404 12.1 HSDPA Mobility...............................................................................404 12.1.1 HSDPA Cell Change SR .................................................................404 12.1.2 HSDPA to DCH Reconfiguration SR ...............................................405 12.2 EUL Mobility ....................................................................................407 12.2.1 EUL Cell Change SR.......................................................................407 12.2.2 EUL to DCH Reconfiguration SR ....................................................407 12.3 PS Streaming HS Mobility ...............................................................410 12.3.1 PS Streaming HS Cell Change SR .................................................410 12.3.2 PS Streaming HS to DCH Reconfiguration SR ...............................411 13 MBMS..............................................................................................413 13.1.1 Overall Accessibility Success Rate MBMS......................................413 13.1.2 Session Establishment Blocked due to TN MBMS..........................414 13.1.3 Session Drop Rate MBMS ..............................................................414 13.1.4 Cell Traffic MBMS ...........................................................................415





13.1.5 Successful Sessions MBMS............................................................416 13.1.6 MBMS Session Admission Failure ..................................................417 13.1.7 MBMS Average Session Throughput DL PS Streaming 64 ............418 13.1.8 MBMS Average Session Throughput DL PS Streaming 128 ..........419 13.1.9 MBMS Average Session Throughput DL PS Streaming 256 ..........420 14 Radio Resource Monitoring.............................................................421 14.1 Power ..............................................................................................421 14.1.1 UL Average RSSI ............................................................................421 14.1.2 UL Rssi Standard Deviation ............................................................421 14.2 Code Consumption..........................................................................423 14.2.1 DL Channelization Code Usage ......................................................423 14.2.2 DL Channelization Code usage Standard Deviation .......................423 14.3 Credit Consumption.........................................................................425 14.3.1 DL Credit Usage..............................................................................425 14.3.2 DL Credits Usage Standard Deviation ............................................425 14.3.3 DL Cedits Consumption Distribution ...............................................426 14.3.4 UL Credit Usage..............................................................................427 14.3.5 UL Credits Standard Deviation........................................................428 14.3.6 UL Cedits Consumption Distribution ...............................................429 14.4 ASE Consumption ...........................................................................431 14.4.1 DL Ase Usage .................................................................................431 14.4.2 UL Ase Usage .................................................................................432 14.5 Node Synchronization .....................................................................433 14.5.1 Out Of Sequence Frames UL..........................................................433 14.5.2 Dynamic Delay on Radio Network Layer.........................................433 14.5.3 Static Delay on Radio Network Layer..............................................434 14.6 Flow Controlled ...............................................................................436 14.6.1 HS Capacity Allocation Congestion Iub...........................................436 14.6.2 HS Capacity Allocation Congestion Iur ...........................................437 14.6.3 E-DCH Data Frame Lost Ratio........................................................438 14.6.4 E-DCH Flow Dynamic Delay Over Iub.............................................438 14.6.5 E-DCH Flow Dynamic Delay Over Iur .............................................440 15 UE Positioning.................................................................................442 15.1 Cell ID Positioning ...........................................................................442 15.1.1 Cell ID Positioning Success QoS Rate............................................442 15.1.2 Cell ID Positioning Failure QoS Rate ..............................................442 15.2 RTT Positioning...............................................................................444 15.2.1 RTT Positioning Success QoS Rate ...............................................444 15.2.2 RTT Positioning Failure QoS Rate ..................................................444 15.3 AGPS Positioning............................................................................446 15.3.1 AGPS Positioning Success QoS Rate ............................................446 15.3.2 AGPS Positioning Failure QoS Rate ...............................................446 16 Reference........................................................................................448 17 Appendix .........................................................................................449





1 Introduction

1.1 Purpose of the document

The purpose of this document is to provide a reference guideline to define and describe WCDMA RNC KPI related to UTRAN P6 release. Delta information concerning new/removed/changed counters from P5 to P6 is included in this document into Note or KPI Description text fields.

For every KPI, the following information is reported:

• Scope, Granularity, Time Resolution;

• Counters MO Class and Type;

• Metric of the formula;

• Description of the meaning of the formula;

• Description of the counters involved in the formula and triggering events;

• Eventual note about specific KPI inconsistency or applicability limitation.

Consequently, the document means to be a global reference for Service Delivery Information preparation for WRAN Performance Improvement, Network Audit/Benchmarking and Network Strategy Consulting projects on WCDMA P6 release.

1.2 Important Remark

This document is to be entirely considered for Ericsson internal use only.

Therefore the present document, as well as each of its single part or chapter, is not to be handed over to any external customer. Please refer to Reference list (chap. 13) for Customer Product Information documents available for external customer consultation.





2 Accessibility

2.1 Iu Signaling

2.1.1 CS Iu Signaling Setup Success Rate

KPI Name: IU_SIG_SUCC_RATE_CS RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PEG Target Value:

KPI Recommended Formula

⎟⎟⎠

⎞⎜⎜⎝

⎛temptCsstablishAtpmNoIuSigEccessCsstablishSupmNoIuSigE*100

Units: % Note: In P5, counters pmNoIuSigEstablishSuccessCs and

pmNoIuSigEstablishAttemptCs are introduced

KPI Description The KPI monitors the percentage of successfully Iu signaling connection setup towards the CS CN.

The signaling connection setup is triggered by the initial direct transfer message at call setup. The counter pmNoIuSigEstablishAttemptCs is pegged for the setup attempts towards the CS CN, whilst the counter pmNoIuSigEstablishSuccessCs is stepped once a SCCP connection is successfully setup. The KPI is calculated on a per RNC basis (the reference MO is RncFunction) and can be seen as an accessibility success rate for Iu control plane connection for CS RABs. Please note that it is possible to have two Iu control plane connections, one towards each CN.

The KPI can be multiplied by the RRC Success Rate and RAB success rate for a specific CS service to obtain the overall accessibility for that service (e.g. Speech or CS data).

The KPI can be aggregated with PS Iu Signaling Setup Success Rate (see following paragraph), providing the Total Iu Signaling Setup Success Rate.





2.1.2 PS Iu Signaling Setup Success Rate

KPI Name: IU_SIG_CONN_PS RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛temptPsstablishAtpmNoIuSigEccessPsstablishSupmNoIuSigE*100

Units: % Note: In P5, counters pmNoIuSigEstablishSuccessPs and

pmNoIuSigEstablishAttemptPs are introduced

KPI Description The KPI monitors the percentage of successfully Iu signaling connection setup towards the PS CN.

The signaling connection setup is triggered by the initial direct transfer message at call setup. The counter pmNoIuSigEstablishAttemptPs is pegged for the setup attempts towards the PS CN, whilst the counter pmNoIuSigEstablishSuccessPs is stepped once a SCCP connection is successfully setup. The KPI is calculated on a per RNC basis (the reference MO is RncFunction) and can be seen as an accessibility success rate for Iu control plane connection for PS RABs. Please note that it is possible to have two Iu control plane connections, one towards each CN.

The KPI can be multiplied by the RRC Success Rate and RAB success rate for a specific PS service to obtain the overall accessibility for that service (e.g. PS Interactive).

The KPI can be aggregated with CS Iu Signaling Setup Success Rate (see previous paragraph), providing the Total Iu Signaling Setup Success Rate.





2.2 Overall Accessibility

2.2.1 Overall Accessibility Success Rate Speech

KPI Name CSSR_SPEECH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

ryAttpmNoDirRet-mptSpeechablishAttepmNoRabEstessSpeechablishSuccpmNoRabEst

*nnCsaringRrcCopmNoLoadSh - CsConnectReqpmTotNoRrc

CsSuccConnectReqpmTotNoRrc

*100

Units: % Note: In P5, load sharing for CS has been introduced.

KPI Description This KPI is the indication of the accessibility rate for the Speech service. It can be seen as the product of two rates: “CS RRC Success Rate” and “RAB Establishment Success Rate Speech”. Please refer to respective KPIs sections for an exhaustive description of the formula and counters involved. In P5, the counter pmNoLoadSharingRrcConnCs has been introduced. This allows distinguishing load sharing events for CS RABs in case Load Sharing feature is enabled. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.2.2 Overall Accessibility Success Rate AMR-NB





KPI Name CSSR_AMRNB RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

mptAmrNbablishAttepmNoRabEstessAmrNbablishSuccpmNoRabEst



*100


KPI Description This KPI is the indication of the accessibility rate for the Amr service. It can be seen as the product of two rates: “CS RRC Success Rate” and “RAB Establishment Success Rate Amr”. Please refer to respective KPIs sections for an exhaustive description of the formula and counters involved. In P5, the counter pmNoLoadSharingRrcConnCs has been introduced. This allows distinguishing load sharing events for CS RABs in case Load Sharing feature is enabled. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.2.3 Overall Accessibility Success Rate AMR-WB

KPI Name CSSR_AMRWB RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour





Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

mptAmrWbablishAttepmNoRabEstessAmrWbablishSuccpmNoRabEst



*100

Units: % Note: In P6, Amr Wb service has been introduced.

KPI Description This KPI is the indication of the accessibility rate for the Amr WB service. It can be seen as the product of two rates: “CS RRC Success Rate” and “RAB Establishment Success Rate Amr WB”. Please refer to respective KPIs sections for an exhaustive description of the formula and counters involved. In P5, the counter pmNoLoadSharingRrcConnCs has been introduced. This allows distinguishing load sharing events for CS RABs in case Load Sharing feature is enabled. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.2.4 Overall Accessibility Success Rate CS57

KPI Name: CSSR_CS57 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

mptCs57ablishAttepmNoRabEstessCs57ablishSuccpmNoRabEst



*100


KPI Description This KPI is the indication of the accessibility rate for the CS57 services. It can be seen as the product of two rates: “CS RRC Success Rate” and “RAB Establishment Success Rate for CS57”. Please refer to respective KPIs sections for an exhaustive description of the formula and counters involved. In P5, the counter pmNoLoadSharingRrcConnCs has been introduced. This allows distinguishing load sharing events for CS RABs in case Load Sharing feature is enabled. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.2.5 Overall Accessibility Success Rate CS64

KPI Name: CSSR_CS64 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

mptCs64ablishAttepmNoRabEstessCs64ablishSuccpmNoRabEst



*100






KPI Description This KPI is the indication of the accessibility rate for the CS64 services. It can be seen as the product of two rates: “CS RRC Success Rate” and “RAB Establishment Success Rate for CS64”. Please refer to respective KPIs sections for an exhaustive description of the formula and counters involved. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.2.6 Overall Accessibility Success Rate PS Streaming

KPI Name: CSSR_ PSSTREAMING RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

treammptPacketSablishAttepmNoRabEsttreamessPacketSablishSuccpmNoRabEst

*nnPsaringRrcCopmNoLoadSh - PsConnectReqpmTotNoRrc

PsSuccConnectReqpmTotNoRrc

*100

Units: % Note: In P5, load sharing for PS has been introduced.

KPI Description This KPI is the indication of the accessibility rate for the PS Streaming services. It can be seen as the product of two rates: “PS RRC Success Rate” and “RAB Establishment Success Rate for PS64 Streaming”. Please refer to respective KPIs





sections for an exhaustive description of the formula and counters involved. In P5, the counter pmNoLoadSharingRrcConnPs has been introduced. This allows distinguishing load sharing events for PS RABs in case Load Sharing feature is enabled. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.2.7 Overall Accessibility Success Rate PS Streaming 128

KPI Name: CSSR_ PSSTREAMING128 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟

⎠

⎞

⎜⎜

⎝

⎛

⎟⎟

⎠

⎞

⎜⎜

⎝

⎛

tream128mptPacketSablishAttepmNoRabEsttream128essPacketSablishSuccpmNoRabEst


PsSuccConnectReqpmTotNoRrc

*100


KPI Description This KPI is the indication of the accessibility rate for the PS Streaming 128 services. It can be seen as the product of two rates: “PS RRC Success Rate” and “RAB Establishment Success Rate for PS128 Streaming”. Please refer to respective KPIs sections for an exhaustive description of the formula and counters involved. In P5, the counter pmNoLoadSharingRrcConnPs has been introduced. This allows distinguishing load sharing events for PS RABs in case Load Sharing feature is enabled.





This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.2.8 Overall Accessibility Success Rate PS Interactive

KPI Name: CSSR_PS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

nteractivemptPacketIablishAttepmNoRabEstnteractiveessPacketIablishSuccpmNoRabEst


PsSuccConnectReqpmTotNoRrc*100


KPI Description The above KPI evaluates the accessibility rate for the PS Data Interactive services, both R99 and HS. This KPI takes into account in the total amount of PS Data Interactive RAB attempts, all the contribution related to the PS data calls originated on R99 only, originated on HS cells and redirected to HS cells. It can be seen as the product of two rates: “PS RRC Success Rate” and “RAB Establishment Success Rate PS Interactive”. Please refer to respective KPIs sections for an exhaustive description of the formula and counters involved. In P5, the counter pmNoLoadSharingRrcConnPs has been introduced. This allows distinguishing load sharing events for PS RABs in case Load Sharing feature is enabled. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.





2.2.9 Overall Accessibility Success Rate PS Interactive DCH/FACH

KPI Name: CSSR_PS_NON_HS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Utran Cell Counters Type: PEG Target Value:


( )⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛++

⎟⎟⎠

⎞⎜⎜⎝

⎛

ntHsBest BlockTnPsIpmNoRabEst HsoReqDeniedpmNoOfNonH

tNonHsAttempPsInpmNoRabEst/ntNonHsSuccessPsIpmNoRabEst



Units: % Note: In P5, load sharing for PS has been introduced. The

counter pmNoRabEstBlockTnPsIntHsBest is available from P.5.0.17 release. In P6, new counter pmNoRabEstSuccessPsIntNonHs is introduced

KPI Description

The above KPI evaluates the accessibility rate for the PS Data Interactive services, only R99. This KPI takes into account in the total amount of PS Data Interactive RAB attempts all the contribution related to the PS data calls originated on R99 only. It can be seen as the product of two rates: “PS RRC Success Rate” and “RAB Establishment Success Rate PS DCH/FACH” which indicates the success rate of RAB establishments for PS R99 calls. Please refer to respective KPIs sections for an exhaustive description of the formula and counters involved. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.





2.2.10 Overall Accessibility Success Rate PS Interactive HS

KPI Name: CSSR_PSHS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Utran Cell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

HsnteractivemptPacketIablishAttepmNoRabEstHsnteractiveessPacketIablishSuccpmNoRabEst




KPI Description The above KPI evaluates the accessibility rate for the PS Data Interactive services, HSDPA only. This KPI takes into account in the total amount of PS Data Interactive RAB attempts all the contribution related to the PS data calls originated on HSDPA. Note that in PS HS RAB establishments attempts and success have been counted also relatively PS EUL RAB establishments ones. It can be seen as the product of three rates: It can be seen as the product of two rates: “PS RRC Success Rate” and RAB Establishment Success Rate PS HS, which indicates the success rate of RAB establishments for PS HS calls. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.





2.2.11 Overall Accessibility Success Rate PS Interactive EUL

KPI Name: CSSR_PSEUL RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Utran Cell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

EulnteractivemptPacketIablishAttepmNoRabEstEulnteractiveessPacketIablishSuccpmNoRabEst




KPI Description The above KPI evaluates the accessibility rate for the PS Data Interactive services, EUL only. This KPI takes into account in the total amount of PS Data Interactive RAB attempts all the contribution related to the PS data calls originated on EUL only. It can be seen as the product of three rates: It can be seen as the product of two rates: “PS RRC Success Rate” and RAB Establishment Success Rate PS EUL, which indicates the success rate of RAB establishments for PS EUL calls. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.2.12 Overall Accessibility Success Rate PS Streaming HS





KPI Name: CSSR_PSHS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Utran Cell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

treamHsAttemptPsSpmNoRabEsttreamHsSuccessPsSpmNoRabEst




In P6 new RAB PS Streaming HS had been introduced. Conters pmNoRabEstSuccessPsStreamHs and pmNoRabEstAttemptPsStreamHs stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The above KPI evaluates the accessibility rate for Number of successful RAB establishments for the PS Streaming RAB in an HS configuration. Reported on the serving HS-DSCH cell. It can be seen as the product of three rates: It can be seen as the product of two rates: “PS RRC Success Rate” and RAB Establishment Success Rate PS Streaming HS, which indicates the success rate of RAB establishments for PS Streaming HS calls. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.





2.3 Paging

2.3.1 RNC Type 1 Paging Attempt Success Rate

KPI Name: PAG_TYPE1_SR RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Paging, LocationArea, RoutingArea, UtranCell Counters Type: PEG Target Value:


⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

+

++

adCscardCmpLopmNoPageDi

RagingToldlepmCnInitPa

LagingToldlepmCnInitPa

+UegingToldlepmCnInitPa

anRejectedAttemptUtrpmNoPaging

-RagingToldlepmCnInitPa

LagingToldlepmCnInitPa

+UegingToldlepmCnInitPa

/*100

Units: % Note:

KPI Description This KPI is indicating the percentage of successful number of CN-initiated pages sent to idle mode UEs. The formula is just the rate between the number of paging successfully sent over the total number of attempts. In particular the pmCnInitPagingToIdleUe counter is increased when the RANAP paging message, without paging area ID, related to idle mode UEs is received by the RNC (Cs or PS pages). The pmCnInitPagingToIdleLa counter is increased when the RANAP Paging message, with specified CN identity and Location Area (Circuit switched pages), related to idle mode UEs is received by the RNC. The pmCnInitPagingToIdleRa counter is increased when the RANAP Paging message, with specified CN identity and Routing Area (Packet switched pages), related to idle mode UEs is received by the RNC. Note that RNC paging retransmissions in quick succession are not counted, only original page attempts and attempts (due to no response) are counted. These counters are increased respectively once per area RNC, per LA or per RA, for each received RANAP paging message. The counter pmNoPagingAttemptUtranRejected is stepped when an RRC Paging Type 1 message cannot be sent by UTRAN (due to very high number of pages, or due to not finding a queue position in the RNC for a paging request received from the CN for an Idle mode UE). Note that this counter can be stepped after the stepping of





the pmCnInitPagingToIdleUe, pmCnInitPagingToIdleUeRa or pmCnInitPagingToIdleUeLa counter. The pmNoPageDiscardCmpLoadC counter is increased whenever the Main Processor (MP) Load Control function indicates an overload situation in the central MP while the RNC is trying to process a paging request. Note that the overload situation is checked only for a paging to an Idle Mode UE.

2.3.2 RNC Type 2 Paging Attempts

KPI Name: PAG_TYPE2_ATTS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


nitDcchAttemptCnIpmNoPaging

Units: Note: Increased for all the cells in AS.

KPI Description This counter is indicating the number of CN-indicated pages sent on DCCH to connected mode UEs. The counter is increased for connected UEs when sending a RRC Paging Type 2 message. Note that the counter is increased for each cell included in the connection to the UE (can be up to 3 cells in an active set).

2.3.3 CN paging to UE in URA State

KPI Name: CN_PAG_URAUE RNC Sw Release: P6 Importance: High





Scope: Ura, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Ura Counters Type: PEG Target Value:


egingToUraUpmCnInitPa

Units: Note:

KPI Description This KPI provides the number of Cn initiated pages attempted for UEs in URA_PCH state. This counter is increased for every Cn initiated page attempted for UEs in URA_PCH state. This counter is only incremented in the SRNC.

2.3.4 UTRAN Paging to UE in URA State

KPI Name: UTRAN_PAG_URAUE RNC Sw Release: P6 Importance: High Scope: Ura, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Ura Counters Type: PEG Target Value:


raUetPagingToUpmUtranIni

Units: Note:

KPI Description Number of Utran initiated pages attempted for UEs in URA_PCH state. This counter is increased for every UTRAN initiated page attempted for UEs in





URA_PCH state. This counter is only incremented in the SRNC.





2.4 RRC Setup Complete

2.4.1 RRC Setup Success Rate

KPI Name: GLOBAL_RRCSUCCRATE RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

nnaringRrcCopmNoLoadSh - ConnectReqpmTotNoRrc

SuccConnectReqpmTotNoRrc*100

Units: % Note: Load Sharing has been included.

KPI Description This formula represents the percentage of successful RRC Connection Requests over the total number of RRC Connection Requests decreased by the number of diversions due to the Load Sharing feature during the establishments of RRC Connections, so that it is not counted as access failure on WCDMA RAN. As soon as an RRC Connection Request message is received by RNC from UE for any Establishment Cause, pmTotNoRrcConnectReq counter is triggered and if UE has selected another cell (frequency), due to Load Sharing feature, pmNoLoadSharingRrcConn counter is stepped when the RRC message RRC Connection Reject is sent to the UE. Then RNC asks permission both from RNC Main Processor (MP) load control and admission control functions. Having received permission to continue, allocates a DL channelization code and then starts to set up a connection towards the RBS. Also the UE is requested to setup an RRC connection with RRC Connection Setup message. Once NBAP Radio Link Restore Indication message and RRC Connection Setup Complete message have been received by RNC, then the RRC connection is considered to be successfully established. The counter pmTotNoRrcConnectReqSucc is now increased. Note that pmTotNoRrcConnectReq counter is always increased in the SRNC for the UE and it is increased once per connection, that is the subsequent retransmissions are not counted. This means that KPI is generating an indication of performance from the end user perspective. The end user is not aware of the UE





re-transmitting the RRC Connection Request message. Thus from the end user perspective a single connection attempt can involve one or more RRC Connection Request messages. In conclusion this KPI is based upon the single end user attempt rather than one or more UE attempts. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI may be used to identify cells which exhibit poor RRC connection performances as a result of insufficient resources (RNC runs MP load control and admission control) or hardware faults.

2.4.2 RRC Setup Success Rate CS

KPI Name: CS_RRCSUCCRATE RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

nnCsaringRrcCopmNoLoadSh - CsConnectReqpmTotNoRrc

CsSuccConnectReqpmTotNoRrc*100

Units: % Note: In P5, load sharing contribution for CS has been

introduced.

KPI Description This formula highlights the success rate of RRC Connection Requests for CS calls. Note that the total number of RRC Connection Requests CS is decreased by the number of diversions due to the Load Sharing feature during the establishments of RRC Connections. As soon as an RRC Connection Request message with Establishment Cause ’Originating Conversational Call’ or ’Terminating Conversational Call’ is





received by RNC from UE, pmTotNoRrcConnectReqCs counter is triggered and if UE has selected another cell (frequency), due to Load Sharing feature, pmNoLoadSharingRrcConnCs counter is stepped when the RRC message RRC Connection Reject is sent to the UE. The pmTotNoRrcConnectReqCsSucc is increased when an RRC Connection Setup Complete message is received following an attempt to setup an originating or terminating conversational call. Note that pmTotNoRrcConnectReqCs counter does not count repeated RRC connection requests. This means that KPI is generating an indication of performance from the end user perspective. The end user is not aware of the UE re-transmitting the RRC Connection Request message. Thus from the end user perspective a single connection attempt can involve one or more RRC Connection Request messages. In conclusion this KPI is based upon the single end user attempt rather than one or more UE attempts. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI is useful to identify cells which exhibit poor CS RRC connection performances.

2.4.3 RRC Setup Success Rate PS

KPI Name: PS_RRCSUCCRATE RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

nnPsaringRrcCopmNoLoadSh - PsConnectReqpmTotNoRrc


Units: % Note: In P5, load sharing contribution for PS has been

introduced.





KPI Description

This formula highlights the success rate of RRC Connection Requests for PS calls. Note that the total number of RRC Connection Requests PS is decreased by the number of diversions due to the Load Sharing feature during the establishments of RRC Connections. As soon as an RRC Connection Request message with Establishment Cause ‘Originating Interactive Call’, ’Terminating Interactive Call’, ’Originating Background Call’, ’Terminating Background Call’ or ’Originating Subscribed traffic call’ is received by RNC from UE, pmTotNoRrcConnectReqPs counter is triggered and if another cell (frequency) was selected by Load Sharing, pmNoLoadSharingRrcConnPs counter is stepped when the RRC message RRC Connection Reject is sent to the UE. The pmTotNoRrcConnectReqPsSucc is increased when an RRC Connection Setup Complete message is received following an attempt to setup an originating or terminating background or interactive call. Note that pmTotNoRrcConnectReqPs counter does not count repeated RRC connection requests. This means that KPI is generating an indication of performance from the end user perspective. The end user is not aware of the UE re-transmitting the RRC Connection Request message. Thus from the end user perspective a single connection attempt can involve one or more RRC Connection Request messages. In conclusion this KPI is based upon the single end user attempt rather than one or more UE attempts. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI is useful to identify cells which exhibit poor PS RRC connection performances.

2.4.4 RRC Terminating Success Rate

KPI Name: GLOBAL_RRCTERMSUCCRATE RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






⎟⎠⎞

⎜⎝⎛

tReqmRrcConnecpmTotNoTer

tReqSuccmRrcConnecpmTotNoTer*100

Units: % Note: Valid in case no IFLS is used

KPI Description This formula highlights the success rate of Terminating RRC Connection Requests for CS and PS calls. The counter pmTotNoTermRrcConnectReq is pegged in case of RRC connection requests with cause 'Terminating Conversational Call', 'Terminating Streaming Call', 'Terminating Interactive Call', 'Terminating Background Call', 'Terminating High Priority Signalling', 'Terminating Low Priority Signalling', or 'Terminating - cause unknown' (excluding subsequent retransmissions).The counter pmTotNoTermRrcConnectReqSucc is increased in case of Successful Terminating RRC connections with any of the causes that led to an increase of pmTotNoTermRrcConnectReq. In case Load Sharing is used, this formula is no longer valid. The reason is that once another cell (frequency) is selected for Load Sharing, the load sharing counters are pegged both for originating and terminating calls. This means that there is no direct way to distinguish originating or terminating calls (CS as well as PS calls) being redirected. There is no way to count for the number of terminating call attempt being redirected due to load sharing and consequently, the number of terminating calls effectively excluding load sharing events cannot be calculated. Note that pmTotNoTermRrcConnectReq counter does not count repeated RRC connection requests. This means that KPI is generating an indication of performance from the end user perspective. The end user is not aware of the UE re-transmitting the RRC Connection Request message. Thus from the end user perspective a single connection attempt can involve one or more RRC Connection Request messages. In conclusion this KPI is based upon the single end user attempt rather than one or more UE attempts. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.





2.4.5 RRC Terminating Success Rate CS

KPI Name: CS_RRCTERMSUCCRATE RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

tReqCsmRrcConnecpmTotNoTer

tReqCsSuccmRrcConnecpmTotNoTer*100


KPI Description This formula highlights the success rate of Terminating RRC Connection Requests for CS calls. The counter pmTotNoTermRrcConnectReqCs is pegged in case of RRC connection requests with cause 'Terminating Conversational Call' (excluding subsequent retransmissions).The counter pmTotNoTermRrcConnectReqCsSucc is pegged in case of successful RRC connections with cause 'Terminating Conversational Call' (excluding subsequent retransmissions). In case Load Sharing is used, this formula is no longer valid. The reason is that once another cell (frequency) is selected for Load Sharing, the load sharing counters are pegged both for originating and terminating CS calls. This means that there is no direct way to distinguish originating or terminating calls being redirected. There is no way to count for the number of terminating CS calls attempt being redirected due to load sharing and consequently, the number of terminating calls effectively attempted after load sharing cannot be calculated. Please note instead that the counter pmTotNoRrcConnectReqCs is pegged in case of originating as well as for terminating calls. This makes the load sharing events counted by pmNoLoadSharingRrcConnCs comparable with the number of RRC Connection Request for CS. Note that pmTotNoTermRrcConnectReqCs counter does not count repeated RRC





connection requests. This means that KPI is generating an indication of performance from the end user perspective. The end user is not aware of the UE re-transmitting the RRC Connection Request message. Thus from the end user perspective a single connection attempt can involve one or more RRC Connection Request messages. In conclusion this KPI is based upon the single end user attempt rather than one or more UE attempts. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.4.6 RRC Terminating Success Rate PS

KPI Name: PS_RRCTERMSUCCRATE RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

tReqPsmRrcConnecpmTotNoTer

tReqPsSuccmRrcConnecpmTotNoTer*100


KPI Description This formula highlights the success rate of Terminating RRC Connection Requests for CS calls. The counter pmTotNoTermRrcConnectReqPs is pegged in case of RRC connection requests with cause 'Terminating Interactive Call' or 'Terminating Background Call' (excluding subsequent retransmissions). The counter pmTotNoTermRrcConnectReqPsSucc is pegged in case of successful RRC connections with cause 'Terminating Interactive Call' or 'Terminating Background Call' (excluding subsequent retransmissions).





In case Load Sharing is used, this formula is no longer valid. The reason is that once another cell (frequency) is selected for Load Sharing, the load sharing counters are pegged both for originating and terminating PS calls. This means that there is no direct way to distinguish originating or terminating calls being redirected. There is no way to count for the number of terminating PS calls attempt being redirected due to load sharing and consequently, the number of terminating calls effectively attempted after load sharing cannot be calculated. Please note instead that the counter pmTotNoRrcConnectReqPs is pegged in case of originating as well as for terminating calls. This makes the load sharing events counted by pmNoLoadSharingRrcConnPs comparable with the number of RRC Connection Request for PS. Note that pmTotNoTermRrcConnectReqPs counter does not count repeated RRC connection requests. This means that KPI is generating an indication of performance from the end user perspective. The end user is not aware of the UE re-transmitting the RRC Connection Request message. Thus from the end user perspective a single connection attempt can involve one or more RRC Connection Request messages. In conclusion this KPI is based upon the single end user attempt rather than one or more UE attempts. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.4.7 RRC Terminating Call Percentage

KPI Name: GLOBAL_RRCTERM_PERC RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

ConnectReqpmTotNoRrc

tReqmRrcConnecpmTotNoTer*100





Units: % Note:

KPI Description This formula is the rate of Terminating RRC Connection Requests over the total amount of RRC Connection Requests. This percentage gives an indication of the amount of CS and PS incoming calls compared to the overall traffic (including signalling). Part of incoming calls are actually bounded within UTRAN (mobile-to-mobile calls), the rest is due to traffic incoming from other access technologies (e.g. GSM or fixed lines). The counter pmTotNoTermRrcConnectReq is pegged in case of RRC connection requests with cause 'Terminating Conversational Call', 'Terminating Streaming Call', 'Terminating Interactive Call', 'Terminating Background Call', 'Terminating High Priority Signalling', 'Terminating Low Priority Signalling', or 'Terminating - cause unknown' (excluding subsequent retransmissions). The counter pmTotNoRrcConnectReq is pegged as soon as an RRC Connection Request message is received by RNC from UE for ANY Establishment Cause. Note that pmTotNoTermRrcConnectReq counter does not count repeated RRC connection requests. This means that KPI is generating an indication of performance from the end user perspective. The end user is not aware of the UE re-transmitting the RRC Connection Request message. Thus from the end user perspective a single connection attempt can involve one or more RRC Connection Request messages. In conclusion this KPI is based upon the single end user attempt rather than one or more UE attempts. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.4.8 RRC Terminating CS Call Percentage

KPI Name: CS_RRCTERM_PERC RNC Sw Release: P6 Importance: Low Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






⎟⎠⎞

⎜⎝⎛

CsConnectReqpmTotNoRrc

tReqCsmRrcConnecpmTotNoTer*100

Units: % Note:

KPI Description This formula is the rate of Terminating RRC Connection Requests for CS calls over the total amount of RRC Connection Requests for CS (originating and terminating calls). This percentage gives an indication of the amount of CS incoming calls compared to the overall CS traffic. Part of incoming CS calls are actually bounded within UTRAN (mobile-to-mobile calls), the rest is due to traffic incoming from other access technologies (e.g. GSM or fixed lines). The counter pmTotNoTermRrcConnectReqCs is pegged in case of RRC connection requests with cause 'Terminating Conversational Call' (excluding subsequent retransmissions). The counter pmTotNoRrcConnectReqCs is increased when the RRC Connection Request message is received with Establishment Cause 'Originating Conversational Call' or 'Terminating Conversational Call'. Note that pmTotNoTermRrcConnectReqCs counter does not count repeated RRC connection requests. This means that KPI is generating an indication of performance from the end user perspective. The end user is not aware of the UE re-transmitting the RRC Connection Request message. Thus from the end user perspective a single connection attempt can involve one or more RRC Connection Request messages. In conclusion this KPI is based upon the single end user attempt rather than one or more UE attempts. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.4.9 RRC Terminating PS Call Percentage

KPI Name: PS_RRCTERM_PERC RNC Sw Release: P6 Importance: Low Scope: Cell, RNC Granularity: ROP – 15’





Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

PsConnectReqpmTotNoRrc

tReqPsmRrcConnecpmTotNoTer*100

Units: % Note:

KPI Description This formula is the rate of Terminating RRC Connection Requests for PS calls over the total amount of RRC Connection Requests for PS (originating and terminating calls). This percentage gives an indication of the amount of PS incoming calls compared to the overall PS traffic. Part of incoming PS calls are actually bounded within UTRAN (mobile-to-mobile calls), the rest is due to traffic incoming from other access technologies. The counter pmTotNoTermRrcConnectReqPs is pegged in case of RRC connection requests with cause 'Terminating interactive Call' or ‘Terminating background call’ (excluding subsequent retransmissions). The pmTotNoRrcConnectReqPs counter is increased when the RRC Connection Request message is received with Establishment Cause ’Originating Interactive Call’, ’Terminating Interactive Call’, ’Originating Background Call’, ’Terminating Background Call’, or ’Originating Subscribed Traffic Call’. Note that pmTotNoTermRrcConnectReqPs counter does not count repeated RRC connection requests. This means that KPI is generating an indication of performance from the end user perspective. The end user is not aware of the UE re-transmitting the RRC Connection Request message. Thus from the end user perspective a single connection attempt can involve one or more RRC Connection Request messages. In conclusion this KPI is based upon the single end user attempt rather than one or more UE attempts. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.





2.5 RRC Establishment Causes

2.5.1 Low Priority Signaling Cause

KPI Name: RRC_CONNECTIONS_SMS RNC Sw Release: P6 Importance: Low Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛


SmsConnectReqpmTotNoRrc*100

Units: % Note:

KPI Description This counter is indicating the percentage of RRC connection requests with Low Priority Signalling establishment cause over the total number of RRC connection requests. As soon as an RRC Connection Request message is received by RNC from UE for any Establishment Cause, pmTotNoRrcConnectReq counter is triggered, while the pmTotNoRrcConnectReqSms counter is stepped only when RRC Connection Request message is received by RNC from UE with an Establishment Cause of 'Originating Low Priority Signalling' or 'Terminating Low Priority Signalling'. Note that both counters are increased once per connection, that is the subsequent retransmissions are not counted.

2.5.2 Conversational Call RRC Establishment

KPI Name: RRC_CONNECTIONS_CS RNC Sw Release: P6 Importance: Low





Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛ConnectReqpmTotNoRrc

CsConnectReqpmTotNoRrc*100

Units: % Note:

KPI Description This counter is indicating the percentage of RRC connection requests with Conversational Call (originating or terminating) establishment cause over the total number of RRC connection requests. As soon as an RRC Connection Request message is received by RNC from UE for any Establishment Cause, pmTotNoRrcConnectReq counter is triggered, while the pmTotNoRrcConnectReqCs counter is stepped only when RRC Connection Request message is received by RNC from UE with an Establishment Cause of 'Originating Conversational Call' or 'Terminating Conversational Call’. Note that both counters are increased once per connection, that is the subsequent retransmissions are not counted.

2.5.3 Interactive and Background Call RRC Establishment

KPI Name: RRC_CONNECTIONS_PS RNC Sw Release: P6 Importance: Low Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






⎟⎟⎠

⎞⎜⎜⎝

⎛ConnectReqpmTotNoRrc

PsConnectReqpmTotNoRrc*100

Units: % Note:

KPI Description This counter is indicating the percentage of RRC connection requests with Interactive and Background Call (originating or terminating) establishment cause over the total number of RRC connection requests. As soon as an RRC Connection Request message is received by RNC from UE for any Establishment Cause, pmTotNoRrcConnectReq counter is triggered, while the pmTotNoRrcConnectReqPs counter is stepped only when RRC Connection Request message is received by RNC from UE with an Establishment Cause of 'Originating Interactive Call', 'Terminating Interactive Call’, 'Originating Background Call', 'Terminating Background Call’ or 'Originating Subscribed Traffic Call’. Note that both counters are increased once per connection, that is the subsequent retransmissions are not counted.

2.5.4 IRAT Cell Reselection Cause

KPI Name: RRC_CONNECTIONS_IRATCR RNC Sw Release: P6 Importance: Low Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛


selIratCellReConnectAttpmTotNoRrc*100

Units: % Note:

KPI Description This counter is indicating the percentage of RRC connection requests with IRAT Cell Reselection establishment cause over the total number of RRC connection





requests. As soon as an RRC Connection Request message is received by RNC from UE for any Establishment Cause, pmTotNoRrcConnectReq counter is triggered, while the pmTotNoRrcConnectAttIratCellResel counter is stepped only when RRC Connection Request message is received by RNC from UE with an Establishment Cause of 'Inter-RAT Cell Reselection’. Note that both counters are increased once per connection, that is the subsequent retransmissions are not counted.

2.5.5 IRAT Cell Change Cause

KPI Name: RRC_CONNECTIONS_IRATCC RNC Sw Release: P6 Importance: Low Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛


rIratCcOrdeConnectAttpmTotNoRrc*100

Units: % Note:

KPI Description This counter is indicating the percentage of RRC connection requests with IRAT Cell Change Order establishment cause over the total number of RRC connection requests. As soon as an RRC Connection Request message is received by RNC from UE for any Establishment Cause, pmTotNoRrcConnectReq counter is triggered, while the pmTotNoRrcConnectAttIratCcOrder counter is stepped only when RRC Connection Request message is received by RNC from UE with an Establishment Cause of 'Inter-RAT Cell Change Order’. Note that both counters are increased once per connection, that is the subsequent retransmissions are not counted.





2.6 RRC Setup Failure Causes

2.6.1 RRC Setup Module MP Load Control Failure

KPI Name: RRC_CONNECTIONS_REJ_PLOAD RNC Sw Release: P6 Importance: Low Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


CConnMpLoadpmNoRejRrc

Units: Event Note:

KPI Description The KPI highlights the number of rejected RRC connections due to module MP load control (includes incoming Inter-RAT CC). Then RNC asks permission both from RNC Main Processor (MP) load control and admission control functions. Having received permission to continue, allocates a DL channelization code and then starts to set up a connection towards the RBS. Also the UE is requested to setup an RRC connection with RRC Connection Setupmessage. Once NBAP Radio Link Restore Indication message and RRC Connection Setup Complete message have been received by RNC, then the RRC connection is considered to be successfully established. If RRC Connection Reject with rejection cause congestion (when the congestion cause has been indicated by internal load control) is sent, the pmNoRejRrcConnMpLoadC counter is increased. This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not successed Rrc connection requests, calculated as the difference between pmTotNoRrcConnReq and pmTotNoRrcConnReqSucc, therefore expressed as a rate.

2.6.2 RRC Setup Admission Control Failure





KPI Name: RRC_CONNECTIONS_DENIED_ADM RNC Sw Release: P6 Importance: Low Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


DeniedAdmpmNoRrcReq

Units: Event Note:

KPI Description The KPI highlights the number of rejected RRC connections due to Admission Control feature. RNC asks permission both from RNC Main Processor (MP) load control and admission control functions. Having received permission to continue, allocates a DL channelization code and then starts to set up a connection towards the RBS. Also the UE is requested to setup an RRC connection with RRC Connection Setupmessage. Once NBAP Radio Link Restore Indication message and RRC Connection Setup Complete message have been received by RNC, then the RRC connection is considered to be successfully established. The pmNoRrcReqDeniedAdm counter defines the number of RRC requests denied by admission control. It is stepped after denied admission after an RRC Connection Request with any cause value has been received. This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not successed Rrc connection requests, calculated as the difference between pmTotNoRrcConnReq and pmTotNoRrcConnReqSucc, therefore expressed as a rate. In case of Load Sharing, this counter is stepped also when a diversion, due to the LS feature, is redirected to the second layer. So the risk is to overestimate this rate when used to indicate eventual lack of radio resources. In this case the formula can be corrected as follows:

( )nnrningRrcCopmNoOfRetu cConnReqSucpmTotNoRrc -nn aringRrcCopmNoLoadSh - ConnReqpmTotNoRrcnnaringrrcCopmNoLoadSh - DeniedAdmpmNoRrcReq

+





2.6.3 RRC Setup Failure after Admission

KPI Name: RRC_CONNECTIONS_FAIL_AFT_ADM RNC Sw Release: P6 Importance: Low Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


DeniedAdmpmNoRrcReq - CConnMpLoadpmNoRejRrc - nnReqanRejRrcCopmTotNoUtr

Units: Note: New counter pmNoRrcReqDeniedAdm available

in P5.

KPI Description The KPI highlights the total number of rejected RRC connections after Admission Control feature. The pmTotNoUtranRejRrcConnReq counter is increased when a connection fails to be setup in RBS for one of the following reason: - RRC Connection Request is received and no internal UE identity is available in the RNC; - MP load control or Admission Control function does not grant permission to proceed; - any internal parameter retrieving or calculations fail; - a DL channelization code fails to be allocated. Note that this counter is never stepped if there is inter-frequency load-sharing. If RRC Connection Reject with rejection cause congestion (when the congestion cause has been indicated by internal load control) is sent, the pmNoRejRrcConnMpLoadC counter is increased. The pmNoRrcReqDeniedAdm counter defines the number of RRC requests denied by admission control. It is stepped after denied admission after an RRC Connection Request with any cause value has been received. This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not successed Rrc connection requests, calculated as the difference between pmTotNoRrcConnReq and pmTotNoRrcConnReqSucc, therefore expressed as a rate.





2.6.4 RRC Setup Radio Failure

KPI Name: RRC_CONNECTIONS_FAIL_RADIO RNC Sw Release: P6 Importance: Low Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


nnReqanRejRrcCopmTotNoUtr - SuccConnectReqpmTotNoRrc - ConnectReqpmTotNoRrc

Units: Note:

KPI Description The KPI highlights the total number of RRC connections failures due to Radio reasons. As soon as an RRC Connection Request message is received by RNC from UE for any Establishment Cause, pmTotNoRrcConnectReq counter is triggered. Then RNC asks permission both from RNC Main Processor (MP) load control and admission control functions. Having received permission to continue, allocates a DL channelization code and then starts to set up a connection towards the RBS. Also the UE is requested to setup an RRC connection with RRC Connection Setupmessage. Once NBAP Radio Link Restore Indication message and RRC Connection Setup Complete message have been received by RNC, then the RRC connection is considered to be successfully established. The counter pmTotNoRrcConnectReqSucc is now increased. If RRC Connection Reject with rejection cause congestion (when the congestion cause has been indicated by internal load control) is sent, the pmNoRejRrcConnMpLoadC counter is increased. The pmTotNoUtranRejRrcConnReq counter is increased when a connection fails to be setup in RBS for one of the following reason: - RRC Connection Request is received and no internal UE identity is available in the RNC; - MP load control or Admission Control function does not grant permission to proceed; - any internal parameter retrieving or calculations fail; - a DL channelization code fails to be allocated. Note that this counter is never stepped if there is inter-frequency load-sharing.





This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not successed Rrc connection requests, calculated as the difference between pmTotNoRrcConnReq and pmTotNoRrcConnReqSucc, therefore expressed as a rate.

2.6.5 RRC Failures Admission CS

KPI Name: ADMCONTROL_RRC_DEN_CS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


meqDeniedAdpmNoRrcCsR

Units: Note:

KPI Description This KPI is an indication of the limited accessibility for CS services caused by admission control. The counter pmNoRrcCsReqDeniedAdm is triggered when an RRC Connection Request with the cause; "Originating Conversational Call", "Terminating Conversational Call", or "Emergency call" is denied by Admission Control. This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not successed Rrc connection requests, calculated as the difference between pmTotNoRrcConnReqCs and pmTotNoRrcConnReqCsSucc, therefore expressed as a rate.

2.6.6 RRC Failures Admission PS

KPI Name: ADMCONTROL_RRC_DEN_PS RNC Sw Release: P6





Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


meqDeniedAdpmNoRrcPsR

Units: Note:

KPI Description This KPI is an indication of the limited accessibility for PS services caused by admission control. The counter pmNoRrcPsReqDeniedAdm is triggered after denied admission after an RRC Connection Request with any of the cause values: 'Originating Interactive Call', 'Terminating Interactive Call', 'Originating Background Call', 'Originating Subscribed Traffic Call' or 'Terminating Background Call' has been received. This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not successed Rrc connection requests, calculated as the difference between pmTotNoRrcConnReqPs and pmTotNoRrcConnReqPsSucc, therefore expressed as a rate.

2.6.7 RL Failures due to Admission

KPI Name: RL_DENIED_ADM RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






edAdmpmNoRlDeni

Units: Note:

KPI Description This KPI is an indication of the admission control denial during mobility. The counter pmNoRlDeniedAdm represents the number of Radio Link setup or Radio Link addition requests denied by admission control. It is triggered when an RL Setup Request or RL Addition Request is denied by Admission Control for either Soft and Softer Handover or Interfrequency Handover. It is incremented in the cell which represents the RL that was denied admission (i.e. the congested cell). This KPI can be computed on a per RNC basis as well as a per cell basis.

2.6.8 Total Failures after Admission

KPI Name: FAILURES_AFTER_ADM RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:

KPI Recommended Formula AfterAdmpmNoFailed

Units: Note:

KPI Description This KPI provides the number of Radio Resource Control (RRC) or Radio Access Bearer (RAB) establishment requests failed after being admitted by admission Control. The counter is increased if a function that has been granted admission for a UE fails after being admitted due to a problem in the RRC or RAB Setup procedure. Then the admission control function must be informed about the release of previously requested resources due to the failed procedure and this counter is increased. The counter is increased in the cell or cells where the UE is located.





This counter is stepped for all cells if UE is in macrodiversity. This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of Rrc connection requests (pmTotNoRrcConnReq) therefore expressed as a rate.

2.6.9 Request Denied due to Admission

KPI Name: ADMCONTROL_REQDEN RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


iedAdmpmNoReqDen

Units: Note:

KPI Description This KPI provides the number of RAB establishment and RRC requests denied due to admission. The counter is increased if admission control function denies admission to any UE in this cell. The reason for denial can be power, code utilization limits, ASE limit, or compressed mode limit reached. This counter is stepped only for one cell if the UE is in macrodiversity. The cell the counter is stepped for will be the first cell for which admission control denies access. The remaining cells will not be checked by admission control after admission is denied to a cell. Note that this counter is increased both in RRC Connection establishment and Radio Bearer setup phase. If a Radio Bearer setup for PS interactive is blocked before on DCH/HS and than on DCH/DCH, the counter is triggered only once. In case of Load Sharing, the counter is not stepped when a RCC connection is redirected on a second layer.





2.6.10 RRC Request Denied due to License Capacity

KPI Name: RRC_BLOCK_HW RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


ReqHwRrcConnectpmNoFailed

Units: Note: The counter pmNoFailedConnectReqHw has

been introduced in P6

KPI Description This KPI measures number of RRC requests denied by admission control due to insufficient licensed capacity in the RBS. The counter pmNoFailedRrcConnectReqHw is incremented by one when an RRC connection request with any cause value is denied by Admission Control due to insufficient licensed capacity in the RBS. This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not successed Rrc connection requests, calculated as the difference between pmTotNoRrcConnReq and pmTotNoRrcConnReqSucc, therefore expressed as a failure rate due to HW limitation.

2.6.11 CS RRC Request Denied due to License Capacity

KPI Name: RRC_BLOCK_HW_CS RNC Sw Release: P6 Importance: High Scope: Cell, RNC





Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


ReqHwCsRrcConnectpmNoFailed

Units: Note: The counter pmNoFailedConnectReqHwCs has


KPI Description This KPI measures number of CS calls denied by admission control due to insufficient licensed capacity in the RBS.

The counter pmNoFailedRrcConnectReqHwCs is incremented by one when an RRC connection request with cause 'Originating Conversational Call', 'Terminating Conversational Call' or 'emergency call' is denied by admission control due to insufficient licensed capacity in the RBS.

This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not success Rrc connection requests due to insufficient licensed capacity pmNoFailedRrcConnectReqHw, therefore expressed as a failure rate for CS RRC attempt due to hardware limitation.

This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not successed Rrc connection requests, calculated as the difference between pmTotNoRrcConnReqCs and pmTotNoRrcConnReqCsSucc, therefore expressed as a rate in CS RRC setup failure attempt.

2.6.12 PS RRC Request Denied due to License Capacity

KPI Name: RRC_BLOCK_HW_PS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG





Target Value:


ReqHwPsRrcConnectpmNoFailed

Units: Note: The counter pmNoFailedConnectReqHwPs has


KPI Description This KPI measures number of PS calls denied by admission control due to insufficient licensed capacity in the RBS.

The counter pmNoFailedRrcConnectReqHwPs is incremented by one when an RRC connection request with cause 'Originating Interactive Call', 'Terminating Interactive Call', 'Originating Background Call', 'Originating Subscribed Traffic Call' or 'Terminating Background Call' is denied by admission control due to insufficient licensed capacity in the RBS.

This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not success Rrc connection requests due to insufficient licensed capacity pmNoFailedRrcConnectReqHw, therefore expressed as a rate for PS RRC attempt due to hardware limitation.

This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not successed Rrc connection requests, calculated as the difference between pmTotNoRrcConnReqPs and pmTotNoRrcConnReqPsSucc, therefore expressed as a rate in PS RRC setup failure attempt.

2.6.13 CS RRC Request Blocked due to Node

KPI Name: RRC_BLOCK_NODE_CS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






odeCsnReqBlockNpmNoRrcCon

Units: Note: The counter pmNoRrcConnReqBlockNodeCs has


KPI Description This KPI measures number of RRC Connection Setup attempts for Circuit Switched calls that fail due to node blocking. The counter pmNoRrcConnReqBlockNodeCs is Incremented by one if the establishment of an RRC Connection Request with Establishment Cause = Originating/Terminating Conversational or Emergency, fails due to node blocking, i.e. node configuration error, node limitation or transport network layer service unavailability.. This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not success CS Rrc connection requests, calculated as the difference between pmTotNoRrcConnReqCs and pmTotNoRrcConnReqCsSucc, therefore expressed as a rate.

2.6.14 PS RRC Request Blocked due to Node

KPI Name: RRC_BLOCK_NODE_PS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


odePsnReqBlockNpmNoRrcCon

Units: Note: The counter pmNoRrcConnReqBlockNodePs has


KPI Description This KPI measures number of RRC Connection Setup attempts for Packet





Switched calls that fail due to node blocking. The counter pmNoRrcConnReqBlockNodePs is Incremented by one at the establishment of an RRC Connection Request with Establishment Cause = Originating/Terminating Interactive or Background or Originating Subscribed Traffic Call, fails due to node blocking, i.e. node configuration error, node limitation or transport network layer service unavailability.

This KPI can be computed on a per RNC basis as well as a per cell basis. It can be divided by the number of not success PS Rrc connection requests, calculated as the difference between pmTotNoRrcConnReqPs and pmTotNoRrcConnReqPsSucc, therefore expressed as a rate.

2.6.15 CS RRC Request Blocked due to TN

KPI Name: RRC _BLOCK_TN_CS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


nCsnReqBlockTpmNoRrcCon

Units: Note: The counter pmNoRrcConnReqBlockTnCs has

been introduced in P.5.0.17 release.

KPI Description This KPI provides the number of RRC Connection Setup attempts for Circuit Switched calls that fail due to Transport Network blocking, counted on the blocking cell. This counter is stepped if the establishment of an RRC Connection Request with Establishment Cause = Originating/Terminating Conversational or Emergency, fails due to congestion on the user plane (AAL2) or control plane (UniSaal or SCTP) of the transport network as a result of user dimensioned transport network resource shortages. This KPI can be divided by the number of not success CS Rrc connection requests,





calculated as the difference between pmTotNoRrcConnReqCs and pmTotNoRrcConnReqCsSucc, therefore expressed as a rate.

2.6.16 PS RRC Request Blocked due to TN

KPI Name: RRC _BLOCK_TN_PS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


nPsnReqBlockTpmNoRrcCon

Units: Note: The counter pmNoRrcConnReqBlockTnPs has

been introduced in P.5.0.17 release.

KPI Description This KPI provides the number of RRC Connection Setup attempts for Packet Switched calls that fail due to Transport Network blocking, counted on the blocking cell. This counters is stepped if the establishment of an RRC Connection Request with Establishment Cause = Originating/Terminating Interactive or Background or Originating Subscribed Traffic Call, fails due to congestion on the user plane (AAL2)or control plane (UniSaal or SCTP) of the transport network as a result of user dimensioned transport network resource shortages. This KPI can be divided by the number of not successed Rrc connection requests, calculated as the difference between pmTotNoRrcConnReqPs and pmTotNoRrcConnReqPsSucc, therefore expressed as a rate.





2.7 RAB Establishment

2.7.1 RAB Establishment Success Rate Speech

KPI Name: SPEECH_RABSUCCRATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

ryAttpmNoDirRet - mptSpeechablishAttepmNoRabEst

essSpeechablishSuccpmNoRabEst*100

Units: % Note: Direct retry contribution has been computed.

In P6, counters pmNoRabEstablishAttemptSpeech and pmNoRabEstablishSuccessSpeech stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

This formula indicates the success rate of RAB establishments for Speech calls. Note that the total number of attempts of RAB establishments is decreased by the number of attempts outgoing via inter RAT handover to GSM due to capacity reasons. The pmNoRabEstablishAttemptSpeech counter is increased just after successful RAB Speech Mapping, when a RANAP RAB Assignment Request message is received from the CN with Speech RABs to be setup or modified, while pmNoRabEstablishSuccessSpeech is increased after successful RAB Speech Establishment, after sending the RANAP RAB Assignment Response message to the CN. Both counters will only be incremented in the SRNC for the Best Cell. The pmNoDirRetryAtt counter is triggered when sending Relocation Required message (after Directed Retry to GSM was initiated). The counter is stepped for the cell where the RRC connection was established and will only be incremented in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When





computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. This formula can give some strange fluctuation about percentage values if calculated on cell level. This behaviour has not been observed on RNC level. The KPI is useful to identify cells which exhibit poor RAB Speech establishments’ performances.

2.7.2 RAB Establishment Success Rate AMR-NB

KPI Name: AMRNB_RABSUCCRATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

mptAmrNbablishAttepmNoRabEst

essAmrNbablishSuccpmNoRabEst*100

Units: % Note: In P6, counters pmNoRabEstablishAttemptAmrNb

and pmNoRabEstablishSuccessNb stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

This formula indicates the success rate of RAB establishments for Amr Narrow Band calls. Note that the total number of attempts of RAB establishments is decreased by the number of attempts outgoing via inter RAT handover to GSM due to capacity reasons. The pmNoRabEstablishAttemptAmrNb counter is incremented after successful AMR-NB RAB Mapping when a RANAP AMR-NB RAB Assignment Request message is received from the CN with AMR-NB RABs to be setup or modified. The counters shall be reported per single AMR-NB RAB state on Best Cell level for each AMR-NB RAB that is established. Note: This counter is only incremented in the SRNC. The pmNoRabEstablishAttemptAmrNb counter is increased after





successful AMR-NB RAB Establishment (on DCH) after sending the RANAP AMR-NB RAB Assignment Response message to the CN. This counter is only incremented in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI is useful to identify cells which exhibit poor RAB AMR-NB establishments’ performances.

2.7.3 RAB Establishment Success Rate AMR-WB

KPI Name: AMRWB_RABSUCCRATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

mptAmrWbablishAttepmNoRabEst

essAmrWbablishSuccpmNoRabEst*100

Units: % Note: In P6, AMR-WB service has been introduced.

In P6, counters pmNoRabEstablishAttemptAmrNb and pmNoRabEstablishSuccessNb stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

This formula indicates the success rate of RAB establishments for Amr Wide Band calls. Note that the total number of attempts of RAB establishments is decreased by the number of attempts outgoing via inter RAT handover to GSM due to capacity reasons. The pmNoRabEstablishAttemptAmrWb counter is incremented after successful





AMR-WB RAB Mapping when a RANAP AMR-WB RAB Assignment Request message is received from the CN with AMR-WB RABs to be setup or modified. The counters shall be reported per single AMR-WB RAB state on Best Cell level for each AMR-WB RAB that is established. Note: This counter is only incremented in the SRNC. The pmNoRabEstablishAttemptAmrWb counter is increased after successful AMR-WB RAB Establishment (on DCH) after sending the RANAP AMR-WB RAB Assignment Response message to the CN. This counter is only incremented in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI is useful to identify cells which exhibit poor RAB AMR-WB establishments’ performances.

2.7.4 RAB Establishment Success Rate CS57

KPI Name: CS57_RABSUCCRATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

mptCs57ablishAttepmNoRabEst

essCs57ablishSuccpmNoRabEst*100

Units: % Note: In P6, counters pmNoRabEstablishAttemptCs57

and pmNoRabEstablishSuccessCs57 stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

This formula indicates the success rate of RAB establishments for CS57 RAB.





The pmNoRabEstablishAttemptCs57 counter is increased just after successful RAB CS57 Mapping, when a RANAP RAB Assignment Request message is received from the CN with CS57 RAB to be setup or modified, while pmNoRabEstablishSuccessCs57 is increased after successful RAB CS57 Establishment, after sending the RANAP RAB Assignment Response message to the CN. Both counters will only be incremented in the SRNC for the Best Cell. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI is useful to identify cells which exhibit poor RAB establishments’ performances for CS57 RAB.

2.7.5 RAB Establishment Success Rate CS64

KPI Name: CS64_RABSUCCRATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

mptCs64ablishAttepmNoRabEst

essCs64ablishSuccpmNoRabEst*100


and pmNoRabEstablishSuccessCs64 stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

This formula indicates the success rate of RAB establishments for CS64 RAB. The pmNoRabEstablishAttemptCs64 counter is increased just after successful RAB CS64 Mapping, when a RANAP RAB Assignment Request message is received





from the CN with CS64 RAB to be setup or modified, while pmNoRabEstablishSuccessCs64 is increased after successful RAB CS64 Establishment, after sending the RANAP RAB Assignment Response message to the CN. Both counters will only be incremented in the SRNC for the Best Cell. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI is useful to identify cells which exhibit poor RAB establishments’ performances for CS64 RAB.

2.7.6 RAB Establishment Success Rate PS Streaming

KPI Name: PSSTREAMING_RABSUCCRATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

treammptPacketSablishAttepmNoRabEst

treamessPacketSablishSuccpmNoRabEst*100

Units: % Note: In P6, counters

pmNoRabEstablishAttemptPacketStream and pmNoRabEstablishSuccessPacketStream stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

This formula indicates the success rate of RAB establishments for PS Streaming. The pmNoRabEstablishAttemptPacketStream counter is increased just after successful RAB PS Streaming Mapping, when a RANAP RAB Assignment Request message is received from the CN with PS Streaming RAB to be setup or modified,





while pmNoRabEstablishSuccessPacketStream is increased after successful RAB PS Streaming Establishment, after sending the RANAP RAB Assignment Response message to the CN. Both counters will only be incremented in the SRNC for the Best Cell. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI is useful to identify cells which exhibit poor RAB establishments’ performances for PS Streaming RAB.

2.7.7 RAB Establishment Success Rate PS Streaming 128

KPI Name: PSSTREAMING128_RABSUCCRATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

tream128mptPacketSablishAttepmNoRabEst

tream128essPacketSablishSuccpmNoRabEst*100


pmNoRabEstablishAttemptPacketStream128 and pmNoRabEstablishSuccessPacketStream128 stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

This formula indicates the success rate of RAB establishments for PS Streaming128. The pmNoRabEstablishAttemptPacketStream128 counter is increased just after successful RAB PS Streaming128 Mapping, when a RANAP RAB Assignment





Request message is received from the CN with PS Streaming128 RAB to be setup or modified, while pmNoRabEstablishSuccessPacketStream128 is increased after successful RAB PS Streaming128 Establishment, after sending the RANAP RAB Assignment Response message to the CN. Both counters will only be incremented in the SRNC for the Best Cell. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI is useful to identify cells which exhibit poor RAB establishments’ performances for PS Streaming128 RAB.

2.7.8 RAB Establishment Success Rate PS Interactive

KPI Name: PS_RABSUCCRATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞⎜

⎝⎛

nteractivemptPacketIablishAttepmNoRabEstnteractiveessPacketIablishSuccpmNoRabEst

*100


pmNoRabEstablishAttemptPacketInteractive and pmNoRabEstablishSuccessPacketInteractive stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC.

The counter pmNoRabEstablishAttemptPacketInteractive stepped in the serving HS-DSCH cell if HS is enable





KPI Description This KPI defines the success rate of establishments for any RAB PS Interactive. Note that the total number of attempts of RAB establishments is decreased by the term HSHardHOFlow1. This number is the number of successful Hard HO outgoing diversions less the number of successful Hard HO incoming diversions. The pmNoRabEstablishAttemptPacketInteractive counter is increased just after successful RAB PS Data Interactive Mapping, when a RANAP RAB Assignment Request message is received from the CN with PS Data Interactive RABs to be setup or modified, while pmNoRabEstablishSuccessPacketInteractive is increased after successful RAB PS Data Interactive Establishment, after sending the RANAP RAB Assignment Responsemessage to the CN. Both counters will only be incremented on the Best Cell of the Active Set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI is useful to identify cells which exhibit poor RAB PS Data Interactive establishments’ performances.

2.7.9 RAB Establishment Success Rate PS Interactive DCH/FACH

KPI Name: PS_NON_HS_RABSUCCRATE RNC Sw Release: P5 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

+

+

ntHsBest BlockTnPsIpmNoRabEst

HsoReqDeniedpmNoOfNonH

tNonHsAttempPsInpmNoRabEst

/ntNonHsSuccessPsIpmNoRabEst*100

Units: % Note: The counter pmNoRabEstBlockTnPsIntHsBest

has been introduced in P.5.0.17 release.





In P6 new counters pmNoRabEstAttemptPsIntNonHs and pmNoRabEstSuccessPsIntNonHs introduced. Counters stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

This KPI defines the success rate of establishments for any RAB PS Interactive DCH/FACH. Note that the total number of success and attempts of RAB PS Interactive establishments is decreased by the respective terms of RAB HS PS Interactive establishments. Note also that the denominator is more increased by the total amount of the Rab Establishment Attempts for PS Int on HS where there are reattempts on NonHS. The cases that causes reattempts (after failure on HS) but are not included in those counters are: - failure to allocate DL Channelization Code - AAL2 setup failure due to Node blocking - RL Setup/Reconfiguration Failure received with cause value 'Node resources not available'.

The counter pmNoRabEstAttemptPsIntNonHs define the number of RAB establishment attempts for the PS Interactive RAB in a non-HS configuration (i.e. on DCH or FACH). Reported on the best cell in the active set. The counter is incremented by one when a RANAP RAB Assignment Request message is received from the CN with RABs to be set up or modified, after successful RAB mapping to PS Interactive. The counter is reported per single RAB state for each RAB that is attempted, on the best cell in the active set, only when the last reattempt is on a non-HS configuration (i.e. on DCH/DCH or RACH/FACH). The counter pmNoRabEstSuccessPsIntNonHs defined the number of successful RAB establishments for the PS Interactive RAB in a non-HS configuration (i.e. on DCH or FACH). Reported on the best cell in the active set. The counter is incremented by one after sending the RANAP RAB Assignment Response message to the CN, indicating a successful PS Interactive RAB establishment. The counter is reported per single RAB state for each RAB that is established, on the best cell in the active set, only if the last reattempt is on a non-HS configuration (i.e. on DCH/DCH or RACH/FACH).

This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI is useful to identify cells which exhibit poor establishments’ performances for RAB PS Data Interactive not including HS.





2.7.10 RAB Establishment Success Rate PS Interactive HS

KPI Name: PS_HS_RABSUCCRATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

HSnteractivemptPacketIablishAttepmNoRabEst

HsnteractiveessPacketIablishSuccpmNoRabEst*100


pmNoRabEstablishAttemptPacketInteractiveHs and pmNoRabEstablishSuccessPacketInteractiveHs stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC.

KPI Description

This formula indicates the success rate of establishments only for RAB HS PS Interactive. The counter pmNoRabEstablishAttemptPacketInteractiveHs is stepped for the selected Serving HS-DSCH cell at RAB establishment and before possible Inter-Frequency handover triggered by this cell selection. The counter pmNoRabEstablishSuccessPacketInteractiveHs is stepped for the selected Serving HS-DSCH cell at RAB establishment after the successfully transition SRB-DCH to PS Interactive 64/HS-HS-DSCH. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI is useful to identify cells which exhibit poor establishments’ performances only for RAB HS PS Data Interactive.





2.7.11 RAB Establishment Success Rate PS Streaming HS

KPI Name: PSSTR_HS_RABSUCCRATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

treamHSAttemptPsSpmNoRabEst

treamHsSuccessPsSpmNoRabEst*100

Units: % Note: In P6, counters pmNoRabEstAttemptPsStreamHs

and pmNoRabEstSuccessPsStreamHs stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC.

KPI Description

This formula indicates the success rate of establishments only for RAB HS PS Streaming. The counter pmNoRabEstAttemptPsStreamHs is stepped for the selected Serving HS-DSCH cell at RAB establishment and before possible Inter-Frequency handover triggered by this cell selection. The counter pmNoRabEstSuccessPsStreamHs is stepped for the selected Serving HS-DSCH cell at RAB establishment after the successfully transition SRB-DCH to Streaming PS/HS. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. The KPI is useful to identify cells which exhibit poor establishments’ performances only for RAB HS PS Streaming.





2.7.12 RAB Establishment Success Rate PS Interactive EUL

KPI Name: PS_EUL_RABSUCCRATE RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛EulnteractivemptPacketIablishAttepmNoRabEstEulnteractiveessPacketIablishSuccpmNoRabEst

*100


pmNoRabEstablishAttemptPacketInteractiveEul and pmNoRabEstablishSuccessPacketInteractiveEul stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC.

KPI Description

This KPI is an indication of accessibility for EUL calls, during the RAB establishment phase. The counter pmNoRabEstablishAttemptPacketInteractiveEul is the number of attempted RAB establishments for PS Interactive RAB mapped on E-DCH/ HSDPA. It is stepped for the suitable Serving E-DCH cell identified by the Serving E-DCH cell selection performed due to RAB establishment. The counter is triggered after reception of RAB Assignement Request and serving cell selection. The counter pmNoRabEstablishSuccessPacketInteractiveEul is the number of successful RAB establishments for PS Interactive RAB mapped on E-DCH/ HSDPA and it is stepped for the Serving E-DCH cell at successful RAB/RB combination transition to PS Interactive E-DCH/HS-DSCH due to RAB establishment. The counter is triggered after sending of RAB Assignment Response (successful). This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can





give poor performances.

2.7.13 RAB Establishment Success Rate Emergency Call

KPI Name: EC_RABSUCCRATE RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛mptlishEcAttepmRabEstabesslishEcSuccpmRabEstab

*100

Units: % Note: In P6, counters pmRabEstablishEcAttempt and

pmNoRabEstablishEcSuccess stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC.

KPI Description

This KPI is an indication of accessibility for Emergency call, during the RAB establishment phase. The counter pmRabEstablishEcAttempt is stepped when a RAB establishment is received for an Emergency Call. The counter pmRabEstablishEcSuccess is stepped after a successful RAB establishment for an Emergency Call This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.





2.8 RAB Establishment Failure Causes

2.8.1 Invalid RAB Establishment Attempts

KPI Name: INVALID_RAB_ATT RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction, UeRc Counters Type: PEG Target Value: KPI Recommended Formula

( ) [ ]⎟⎟

⎠

⎞

⎜⎜

⎝

⎛ ∑⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛+= =

sishAttemptdRabEstablpmNoInvali

780 iUeRcmptsablishAttepmNoRabEst

/sishAttemptdRabEstablpmNoInvali*100 i

Units: % Note: In P6, new RABs available are added. KPI Description This KPI highlights the percentage of invalid RAB establishments’ attempts over the total of RAB establishments’ attempts. The pmNoInvalidRabEstablishAttempts counter is increased if a RANAP RAB Assignment message is received for RABs to be setup/modified and the received QoS parameters cannot be mapped to a supported RAB type or if the data in the message contains a critical logical error. The pmNoRabEstablishAttempts counter is increased by 1 immediately after the RAB mapping has been completed successfully in the RNC for a RANAP RAB Assignment Request message received from either the PS or CS CN with RABs to be setup or modified. The counters shall be reported per single RAB state or Multi-RAB state on the RNC level, for each RAB that is established. Please note that only supported RABs will contribute to the overall sum.

2.8.2 UE Capability Limit RAB Establishment Failure

KPI Name: RAB_FAILURES_UECAP





RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction, UeRc Counters Type: PEG Target Value:


( ) [ ]⎟⎟

⎠

⎞

⎜⎜

⎝

⎛ ∑⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛+= =

sishAttemptdRabEstablpmNoInvali

780 iUeRcmptsablishAttepmNoRabEst

/ilityureUeCapabablishFailpmNoRabEst*100 i

Units: % Note: In P6, new RABs available are added.

KPI Description This KPI highlights the percentage of failed RAB establishments due to insufficient UE capabilities over the total of RAB establishments’ attempts. The pmNoRabEstablishFailureUeCapability counter is triggered when the Ue Capability check fails for the state to which it is established. The pmNoInvalidRabEstablishAttempts counter is increased if a RANAP RAB Assignment message is received for RABs to be setup/modified and the received QoS parameters cannot be mapped to a supported RAB type or if the data in the message contains a critical logical error. The pmNoRabEstablishAttempts counter is increased by 1 immediately after the RAB mapping has been completed successfully in the RNC for a RANAP RAB Assignment Request message received from either the PS or CS CN with RABs to be setup or modified. The counters shall be reported per single RAB state or Multi-RAB state on the RNC level, for each RAB that is established. Please note that only supported RABs will contribute to the overall sum.

2.8.3 RAB Establishment Blocked due to TN Speech

KPI Name: RAB_BLOCK_TN_SPEECH RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’







echBlockTnSpepmNoRabEst

Units: Note: The counter pmNoRabEstBlockTnSpeechBest

has been introduced in P.5.0.17 release for Best Cell measurement

KPI Description

This KPI provides the number of RAB establishment attempts for RAB Speech that are blocked due to TN congestion or TN failure, counted on the blocking cell. This counter is stepped when the establishment of a Speech RAB fails due to UNI-SAAL or AAl2 congestion, IP resource limitations or blocking as a result of user dimensioned transport network configured capacity. The counter is stepped for the best cell in the active set but only if the cell is in the SRNC. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as the difference between pmNoRabEstablishAttemptSpeech and pmNoRabEstalishSuccessSpeech, therefore expressed as a rate.

2.8.4 RAB Establishment Blocked due to TN CS57

KPI Name: RAB_BLOCK_TN_CS64 RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


7BlockTnCs5pmNoRabEst

Units:





Note: The counter is new in P6 A Best Cell counter is available by pmNoRabEstBlockTnCs57Best.

KPI Description

This KPI provides the number of RAB establishment attempts for RAB-type CS57 that are blocked due to TN congestion or TN failure, counted on the blocking cell. This counter is stepped when the establishment of a CS57 RAB fails due to UNI-SAAL or AAl2 congestion, IP resource limitations or blocking as a result of user dimensioned transport network configured capacity.The counter is stepped for the best cell in the active set but only if the cell is in the SRNC. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as the difference between pmNoRabEstablishAttemptCs57 and pmNoRabEstalishSuccessCs57, therefore expressed as a rate.

2.8.5 RAB Establishment Blocked due to TN CS64

KPI Name: RAB_BLOCK_TN_CS64 RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


4BlockTnCs6pmNoRabEst

Units: Note: The Best Cell measurement is available by

counter pmNoRabEstBlockTnCs64Best.

KPI Description This KPI provides the number of RAB establishment attempts for RAB-type CS64 that are blocked due to TN congestion or TN failure, counted on the blocking cell. This counter is stepped when the establishment of a CS64 RAB fails due to UNI-SAAL or AAl2 congestion, IP resource limitations or blocking as a result of user dimensioned transport network configured capacity.The counter is stepped for the best cell in the active set but only if the cell is in the SRNC.





This KPI can be divided by the number of not successed Rab establishment attempts, calculated as the difference between pmNoRabEstablishAttemptCs64 and pmNoRabEstalishSuccessCs64, therefore expressed as a rate.

2.8.6 RAB Establishment Blocked due to TN PS Interactive Non HS

KPI Name: RAB_BLOCK_TN_PSNONHS RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


ntNonHsBlockTnPsIpmNoRabEst


pmNoRabEstBlockTnPsIntNonHsBest

KPI Description This KPI provides the number of RAB establishment attempts for RAB-type PS Interactive that are blocked due to TN congestion or TN failure, counted on the blocking cell. The counter is stepped when the establishment of a PS Interactive (excluding HS) RAB fails due to UNI-SAAL or AAl2 congestion, IP resource limitations or blocking as a result of user dimensioned transport network configured capacity. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as following: (pmNoRabEstAttemptPacketInteractiveNonHs + pmNoOfNonHoReqDeniedHs + pmNoRabEstBlockTnPsIntHsBest – pmNoRabEstSuccessPacketInteractiveNonHs), therefore expressed as a rate.

2.8.7 RAB Establishment Blocked due to TN PS Streaming Non HS





KPI Name: RAB_BLOCK_TN_PSSTRNONHS RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


ttrNonHsBesBlockTnPsSpmNoRabEst

Units: Note: The blocking cell measurement is available by

pmNoRabEstBlockTnPsStrNonHs.

KPI Description This KPI provides the number of RAB establishment attempts for RAB-type PS Streaming that are blocked due to TN congestion or TN failure, counted on the best cell. The counter is stepped when the establishment of a PS Streaming (excluding HS) RAB fails due to UNI-SAAL or AAl2 congestion, IP resource limitations or blocking as a result of user dimensioned transport network configured capacity. This KPI can be divided by the number of not successed PS Streaming Rab establishment attempts, calculated as following: (pmNoRabEstablishAttemptPacketStream + pmNoRabEstablishAttemptPacketStream128 -pmNoRabEstablishSuccessPacketStream + pmNoRabEstablishSuccessPacketStream128), therefore expressed as a rate.

2.8.8 RAB Establishment Blocked due to TN PS Interactive HS

KPI Name: RAB_BLOCK_TN_PSHS RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG





Target Value:


ntHsBlockTnPsIpmNoRabEst


counter pmNoRabEstBlockTnPsIntHsBest.

KPI Description This KPI provides the number of RAB establishment attempts for RAB-type PS Interactive for HS that are blocked due to TN congestion or TN failure, counted on the best cell. The counter is stepped when the establishment of a PS Interactive RAB fails due to UNI-SAAL or AAl2 congestion, IP resource limitations or blocking as a result of user dimensioned transport network configured capacity. The counter is stepped for the best cell in the active set but only if the cell is in the SRNC. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as following: pmNoRabEstablishAttemptPacketInteractiveHs – pmNoRabEstablishSuccessPacketInteractiveHs, therefore expressed as a rate.

2.8.9 RAB Establishment Blocked due to TN PS Streaming HS

KPI Name: RAB_BLOCK_TN_PSSTRHS RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


trHsBlockTnPsSpmNoRabEst






counter pmNoRabEstBlockTnPsStreamHsBest has been introduced in P6 release.

KPI Description

This KPI provides the number of RAB establishment attempts for RAB-type PS Interactive for HS that are blocked due to TN congestion or TN failure, counted on the blocking cell. The counter is stepped when the establishment of a PS Interactive RAB fails due to UNI-SAAL or AAl2 congestion, IP resource limitations or blocking as a result of user dimensioned transport network configured capacity. The counter is stepped for the best cell in the active set but only if the cell is in the SRNC. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as following: pmNoRabEstablishAttemptPsStreamHs – pmNoRabEstablishSuccessPsStreamHs, therefore expressed as a rate.

2.8.10 RAB Establishment Blocked due to Node Speech

KPI Name: RAB_BLOCK_NODE_SPEECH RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


peechBlockNodeSpmNoRabEst

Units: Note: New in P6

The Best cell measurement is available by counter pmNoRabEstBlockNodeSpeechBest has been introduced in P6 release.

KPI Description

This KPI provides the number of RAB establishment attempts for RAB Speech that are blocked due to node congestion or node failure, counted on the blocking cell.





This counter is stepped when the establishment of a Speech RAB fails due to node configuration error, node limitation, or transport network layer service unavailability. The counter is stepped for the best cell in the active set but only if the cell is in the SRNC. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as the difference between pmNoRabEstablishAttemptSpeech and pmNoRabEstalishSuccessSpeech, therefore expressed as a rate.

2.8.11 RAB Establishment Blocked due to Node CS57

KPI Name: RAB_BLOCK_NODE_CS64 RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


s57BlockNodeCpmNoRabEst

Units: Note: Counter is new in P6

The Best Cell measurement is available by counter pmNoRabEstBlockNodeCs57Best has been introduced in P6 release.

KPI Description

This KPI provides the number of RAB establishment attempts for RAB-type CS57 that are blocked due to node congestion or node failure, counted on the blocking cell. This counter is stepped when the establishment of a CS57 RAB fails due to node configuration error, node limitation, or transport network layer service unavailability. The counter is stepped for the best cell in the active set but only if the cell is in the SRNC. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as the difference between pmNoRabEstablishAttemptCs57 and pmNoRabEstalishSuccessCs57, therefore expressed as a rate.





2.8.12 RAB Establishment Blocked due to Node CS64

KPI Name: RAB_BLOCK_NODE_CS64 RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


s64BlockNodeCpmNoRabEst


counter pmNoRabEstBlockNodeCs64Best has been introduced in P.5.0.17 release.

KPI Description

This KPI provides the number of RAB establishment attempts for RAB-type CS64 that are blocked due to node congestion or node failure, counted on the blocing cell. This counter is stepped when the establishment of a CS64 RAB fails due to configuration error, node limitation, or transport network layer service unavailability. The counter is stepped for the best cell in the active set but only if the cell is in the SRNC. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as the difference between pmNoRabEstablishAttemptCs64 and pmNoRabEstalishSuccessCs64, therefore expressed as a rate.

2.8.13 RAB Establishment Blocked due to Node PS Interactive Non HS

KPI Name: RAB_BLOCK_NODE_PSNONHS RNC Sw Release: P6 Importance: Medium





Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


ntNonHsBlkNodePsIpmNoRabEst

Units: Note: Counter is new in P6.

The Best Cell measurement is available by counter pmNoRabEstBlkNodePsIntNonHsBest has been introduced in P6 release.

KPI Description

This KPI provides the number of RAB establishment attempts for RAB-type PS Interactive that are blocked due to node congestion or node failure, counted on the blocking cell. The counter is stepped when the establishment of a PS Interactive (excluding HS) RAB fails due to configuration error, node limitation, or transport network layer service unavailability. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as following: (pmNoRabEstAttemptPsIntNonHs + pmNoOfNonHoReqDeniedHs + pmNoRabEstBlockTnPsIntHsBest – pmNoRabEstSuccessPsIntNonHs), therefore expressed as a rate.

2.8.14 RAB Establishment Blocked due to Node PS Streaming Non HS

KPI Name: RAB_BLOCK_NODE_PSSTRNONHS RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






trNonHsBlkNodePsSpmNoRabEst


The Best Cell measurement is available by counter pmNoRabEstBlkTnPsStrNonHsBest has been introduced in P6 release.

KPI Description

This KPI provides the number of RAB establishment attempts for RAB-type PS Streaming that are blocked due to congestion or node failure, counted on the blocking cell. The counter is stepped when the establishment of a PS Streaming (excluding HS) RAB fails due to configuration error, node limitation, or transport network layer service unavailability. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as following: (pmNoRabEstAttemptPacketInteractivenonHs + pmNoOfNonHoReqDeniedHs + pmNoRabEstBlockTnPsIntHsBest –pmNoRabEstSuccessPacketInteractiveNonHs), therefore expressed as a rate.

2.8.15 RAB Establishment Blocked due to Node PS Interactive HS

KPI Name: RAB_BLOCK_NODE_PSHS RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


sIntHsBlockNodePpmNoRabEst


The Best Cell measurement is available by counter pmNoRabEstBlockNodePsIntHsBest has been introduced in P6 release.





KPI Description This KPI provides the number of RAB establishment attempts for RAB-type PS Interactive for HS that are blocked due to congestion or node failure, counted on the blocking cell. The counter is stepped when the establishment of a PS Interactive RAB fails due to configuration error, node limitation, or transport network layer service unavailability. The counter is stepped for the best cell in the active set but only if the cell is in the SRNC. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as following: pmNoRabEstablishAttemptPacketInteractiveHs – pmNoRabEstablishSuccessPacketInteractiveHs, therefore expressed as a rate.

2.8.16 RAB Establishment Blocked due to Node PS Streaming HS

KPI Name: RAB_BLOCK_NODE_PSSTRHS RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


sStrHsBlockNodePpmNoRabEst


The Best Cell measurement is available by counter pmNoRabEstBlockNodePsStrHsBest has been introduced in P6 release.

KPI Description

This KPI provides the number of RAB establishment attempts for RAB-type PS Interactive for HS that are blocked due to congestion or node failure, counted on the blocking cell. The counter is stepped when the establishment of a PS Interactive RAB fails due to configuration error, node limitation, or transport network layer service unavailability.





The counter is stepped for the best cell in the active set but only if the cell is in the SRNC. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as following: pmNoRabEstablishAttemptPsStreamHs – pmNoRabEstablishSuccessPsStreamHs, therefore expressed as a rate.

2.8.17 RAB Establishment Blocked due to RN PS Streaming HS

KPI Name: RAB_BLOCK_RN_PSSTRHS RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


treamHsBlockRnPsSpmNoRabEst

Units: Note: The counter is new in P6

The best cell counter, pmNoRabEstBlockRnBestPsStreamHs is available for Best Cell.

KPI Description

This KPI provides the number of RAB establishment attempts for RAB-type streaming PS unknown HS that are blocked due to RN congestion or RN failure, counted on the congested cell. The counter is incremented by one when a target configuration is selected when reconfiguring the connection to add the new RAB, and the execution of the reconfiguration was blocked due to RN resources. The counter is stepped for the best cell in the active set but only if the cell is in the SRNC. This KPI can be divided by the number of not successed Rab establishment attempts, calculated as following: pmNoRabEstablishAttemptPsStreamHs – pmNoRabEstablishSuccessPsStreamHs, therefore expressed as a rate.





2.9 Inter Frequency Load Sharing

2.9.1 IFLS Activity Rate

KPI Name: IFLS_ACTIVITY RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛


nnaringRrcCopmNoLoadSh*100

Units: % Note:

KPI Description This formula indicates the percentage of connections redirected towards another UMTS carrier. As soon as an RRC Connection Request message is received by RNC from UE for any Establishment Cause, pmTotNoRrcConnectReq counter is triggered and if UE has selected another cell (frequency), due to Load Sharing feature, pmNoLoadSharingRrcConn counter is stepped when the RRC message RRC Connection Reject is sent to the UE. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.9.2 IFLS Activity Rate CS

KPI Name: IFLS_ACTIVITY_CS





RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

CsConnectReqpmTotNoRrc

nnCsaringRrcCopmNoLoadSh*100

Units: % Note:

KPI Description This formula indicates the percentage of RRC Connections for CS domain redirected towards another UMTS carrier. As soon as an RRC Connection Request message with Establishment Cause ’Originating Conversational Call’ or ’Terminating Conversational Call’ is received by RNC from UE, pmTotNoRrcConnectReqCs counter is triggered and if UE has selected another cell (frequency), due to Load Sharing feature, pmNoLoadSharingRrcConnCs counter is stepped when the RRC message RRC Connection Reject is sent to the UE. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.9.3 IFLS Activity Rate PS

KPI Name: IFLS_ACTIVITY_PS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell





Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

PsConnectReqpmTotNoRrc

nnPsaringRrcCopmNoLoadSh*100

Units: % Note:

KPI Description This formula indicates the percentage of RRC Connections for PS domain redirected towards another UMTS carrier. As soon as an RRC Connection Request message with Establishment Cause ‘Originating Interactive Call’, ’Terminating Interactive Call’, ’Originating Background Call’, ’Terminating Background Call’ or ’Originating Subscribed traffic call’ is received by RNC from UE, pmTotNoRrcConnectReqPs counter is triggered and if another cell (frequency) was selected by Load Sharing, pmNoLoadSharingRrcConnPs counter is stepped when the RRC message RRC Connection Reject is sent to the UE. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

2.9.4 IFLS Return Rate

KPI Name: IFLS_RETURN_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






⎟⎠⎞

⎜⎝⎛

nnaringRrcCopmNoLoadSh

nnrningRrcCopmNoOfRetu*100

Units: % Note:

KPI Description This formula indicates the percentage of RRC Connections returning to the original frequency, after having redirected to other one, over the total of Load Sharing redirected RRC Connections. pmNoLoadSharingRrcConn is a performance counter on cell level that shows the number of load sharing diversions during the establishment of RRC connections. If UE has selected another cell (frequency), due to Load Sharing feature, the counter is stepped when the RRC message RRC Connection Reject is sent to the UE. pmNoOfReturningRrcConn is stepped when the RNC detects an RRC connection attempt within 60 seconds of being redirected to another frequency, if that second attempt is made on the original frequency. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.





2.10 GSM Redirected RRC Connection Setup

2.10.1 Directed Retry Activity Rate

KPI Name: DR_ACTIVITY RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

mptSpeechablishAttepmNoRabEst

ryAttpmNoDirRet*100

Units: % Note: In P6, counter pmRabEstablishAttemptSpeech

stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC.

KPI Description

This KPI defines the percentage of Speech connections redirected towards GSM. It is just the ratio between the number of attempted outgoing inter RAT handover to GSM due to capacity reasons and the number of RAB Speech establishments attempts. The counter pmNoDirRetryAtt is triggered when sending Relocation Required (after Directed Retry to GSM was initiated).It is stepped for the cell where the RRC connection was established and in the SRNC. The counter pmNoRabEstablishAttemptSpeech is incremented after successful RAB Mapping when a RANAP RAB Assignment Request message is received from the CN with RABs to be setup or modified. The counters shall be reported per single RAB state on Best Cell level for each RAB that is established. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.





This KPI defines the activity rate for the redirection of speech calls to GSM and it is useful to understand if the origin WCDMA cell is overloaded.

2.10.2 Directed Retry Success Rate

KPI Name: DR_SUCC_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

ryAttpmNoDirRet

rySuccesspmNoDirRet*100

Units: % Note:

KPI Description This KPI defines the success rate of Directed Retry procedure. It’s the ratio between the total number of successful inter RAT handover to GSM (due to capacity reasons) over the total number of attempts. The pmNoDirRetrySuccess counter is increased when Iu Release Command is received with cause ’Normal release’ or ’Successful relocation’ (after Directed Retry to GSM was initiated). The counter pmNoDirRetryAtt is triggered when sending Relocation Required (after Directed Retry to GSM was initiated). Both counters are stepped for the cell where the RRC connection was established and in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances. This KPI defines is useful to understand if the IRAT blind HO towards a predefined target GSM neighbour cell from the origin WCDMA cell is working properly.





3 Availability

3.1 R99 Cell Unavailability

KPI Name: DOWNTIME_COMB RNC Sw Release: P5 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 24 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


[ ] ⎟⎠

⎞⎜⎝

⎛ +

Duration Timet Measuremen

timeManpmCellDown timeAutopmCellDown * 100

Units: % Note:

KPI Description The KPI defines the percentage of time during which the cell is in downtime state due to maintenance activity or to a system malfunction. The pmCellDowntimeAuto counter measures the length of time (in seconds) during which a cell is unavailable for service because, due to a fault, the system has set a cell or channel state to disable. This means that cell and/or channel Operation state = Disabled and the cell and/or channel Administration state = unlocked. The pmCellDowntimeMan counter measures the length of time (in seconds) during which a cell is unavailable for service because of Administration state being set to manual lock. This means that Administration state of the cell and/or channel = locked, regardless of the operational state of the cell or channel. If the observation period is 24 hours, the value Measurement Time Duration in seconds will be 24*3600 and the value of the counters for each 15 minutes will be aggregated over the 24 hour. The formula can be split obtaining two more different KPIs which consider singularly the auto contribution and the manual one.





3.2 HS Cell Unavailability

KPI Name: HSDOWNTIME_COMB RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 24 hour Counters MO Class: Hsdsch Counters Type: PEG Target Value:


[ ] ⎟⎠

⎞⎜⎝

⎛ +


meManpmHsDownti meAutopmHsDownti * 100

Units: % Note:

KPI Description The KPI defines the percentage of time during which the cell is in downtime state for HS service due to maintenance activity or to a system malfunction. The pmHsDowntimeAuto counter measures the amount of time (in seconds) during which the Hsdsch service in a cell is unavailable for service because, due to a fault, the system has set a cell or channel state (at least one of the MOs Hsdsch, UtranCell, Pch, Rach or Fach) to disable. This means that cell and/or any channels Operation state = Disabled and the cell and/or channel Administration state = unlocked. The pmHsDowntimeMan counter measures the amount of time (in seconds) during which the Hsdsch service in a cell is unavailable due to operation setting because the operator has locked at least one of the MOs Hsdsch, UtranCell, Pch, Rach or Fach. This means that cell and/or any channels Administration state = locked, regardless of the operational state of the cell or channel. So downtime value for a HS cell is always greater or at least equal to downtime value for the relative R99 cell. If the observation period is 24 hours, the value Measurement Time Duration in seconds will be 24*3600 and the value of the counters for each 15 minutes will be aggregated over the 24 hour. The formula can be split obtaining two more different KPIs which consider singularly the auto contribution and the manual one.





3.3 EUL Cell Unavailability

KPI Name: EULDOWNTIME_COMB RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 24 hour Counters MO Class: Eul Counters Type: PEG Target Value:


[ ] ⎟⎟⎠

⎞⎜⎜⎝

⎛ +


imeManpmEulDownt imeAutopmEulDownt * 100

Units: % Note: These counters is in MO class Eul

KPI Description The KPI defines the percentage of time during which the Eul service is in downtime state due to maintenance activity or to a system malfunction. The pmEulDowntimeAuto counter measures the amount of time (in seconds) the Eul service in the cell has been unavailable because the system has considered the cell as down, for example, at least one of the MOs Eul, Hsdsch, UtranCell, Pch, Rach or Fach has been disabled while all these MOs have been unlocked. The pmEulDowntimeMan counter measures the amount of time (in seconds) the Eul service in the cell has been unavailable due to operator setting, for example, the operator has locked at least one of the MOs Eul, Hsdsch, UtranCell, Pch, Rach or Fach. If the observation period is 24 hours, the value Measurement Time Duration in seconds will be 24*3600 and the value of the counters for each 15 minutes will be aggregated over the 24 hour. The formula can be split obtaining two more different KPIs which consider singularly the auto contribution and the manual one.





3.4 MBMS Cell Unavailability

KPI Name: MBMSDOWNTIME_COMB RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 24 hour Counters MO Class: MbmsCch Counters Type: PEG Target Value:


[ ] ⎟⎠

⎞⎜⎝

⎛ +


timeManpmMbmsDowntimeAutopmMbmsDown * 100

Units: % Note: In P6 MBMS has been introduced.

KPI Description The KPI defines the percentage of time during which the cell is in downtime state due to maintenance activity or to a system malfunction. The pmMbmsDowntimeAuto counter measures the length of time (in seconds) the MBMS service in the cell is unavailable due to the system has considered the cell as down. I.e. MbmsCch operational state is disabled, while all of the MbmsCch, UtranCell, Fach, Rach and Pch administrative states are unlocked.

The pmMbmsDowntimeMan counter measures the length of time (in seconds) the MbmsCch service in the cell is unavailable due to administrative state in any of the MOs MbmsCch, UtranCell, Fach, Rach or Pch is locked.

If the observation period is 24 hours, the value Measurement Time Duration in seconds will be 24*3600 and the value of the counters for each 15 minutes will be aggregated over the 24 hour. The formula can be split obtaining two more different KPIs which consider singularly the auto contribution and the manual one.





4 Retainability

4.1 RRC Drop Rate

4.1.1 Overall RRC Drop Rate DCH

KPI Name: RRC_DROPRATE_DCH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

tNormalhDisconnecpmNoCellDc

tAbnormhDisconnecpmNoCellDc/tAbnormhDisconnecpmNoCellDc*100

Units: % Note:

KPI Description The KPI defines the probability of loosing a RRC Connection already setup on Dedicated Channels. It is calculated as the ratio between abnormal disconnections from dedicated channels over the total number of disconnections from dedicated channels. The pmNoCellDchDisconnectNormal and the pmNoCellDchDisconnectAbnorm counters are stepped when releasing a UE Connection on a dedicated channel, and all Radio Links have been deleted in the RBS. In particular, they are only increased when an order is received from the Signaling Connection Handling function to release an RRC Connection from DCH or E-DCH due to a RRC Connection Release message relatively with “release cause” = ’normal event’ or ’user inactivity’ or ’Directed Signalling Connection Re-establishment’’ for the first one and anything except the previous causes for the second one. Both counters are stepped for the best cell in active set and are only incremented when all associated RABs (and the RRC Connection) are released. Therefore if releasing one RAB in a Multi-RAB scenario, these counters are not incremented. This KPI can be computed on a per RNC basis as well as a per cell basis. When





computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

4.1.2 Overall RRC Drop Rate FACH

KPI Name: RRC_DROPRATE_FACH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

ctNormalchDisconnepmNoCellFa

ctAbnormchDisconnepmNoCellFa/ctAbnormchDisconnepmNoCellFa*100

Units: % Note:

KPI Description The KPI defines the probability of loosing a RRC Connection already setup on common channels. It is calculated as the ratio between abnormal disconnections from common channels over the total number of disconnections from common channels. The pmNoCellFachDisconnectNormal and the pmNoCellFachDisconnectAbnorm counters are only increased while releasing any type of Connection on a common channel with an RRC Connection Release message relatively with “release cause” = ’normal event’ or ’user inactivity’ or ’Directed Signalling Connection Re-establishment’ for the first one and anything except the previous causes for the second one. All these counters will be only increased the first time the RRC Connection Release is sent to the UE. (The RNC may transmit several RRC messages to increase the probability of proper reception of the message by the UE). This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI





equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

4.1.3 RRC Drop Rate Speech

KPI Name: RRC_DROPRATE_SPEECH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

+ ormDchDiscAbnpmNoSpeech malDchDiscNorpmNoSpeech

ormDchDiscAbnpmNoSpeech*100

Units: % Note:

KPI Description The KPI defines the drop rate for RRC Connection with a CS Speech (12.2 kbps) Conversational RAB on dedicated channel. It is calculated as the rate between abnormal disconnections of a speech call over the total number of disconnections. Both counters are only increased for the best cell in active set and for the Speech RAB, that is the "conversational/speech 12.2 Kbps RAB". The pmNoSpeechDchDiscNormal and the pmNoSpeechDchDiscAbnorm counters are only increased when the RRC Connection is released with the RRC Connection Release command respectively with “release cause” equal to ’normal event’ or ’user inactivity’ or ’Directed Signaling Connection Re-establishment’ for the first one and anything but the just mentioned causes for the second one. In case of multi-RAB or multi signaling connection, the RRC Connection will remain after that the signaling connection or RAB to one CN have been released and therefore the counters shall not be increased. All these counters will be only increased the first time the RRC Connection Release is sent to the UE. (The RNC may transmit several RRC messages to increase the probability of proper reception of the message by the UE). This KPI can be computed on a per RNC basis as well as a per cell basis. When






4.1.4 RRC Drop Rate CS57

KPI Name: RRC_DROPRATE_CS57 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

bnormamDchDiscApmNoCsStre

ormalamDchDiscNpmNoCsStre/bnormamDchDiscApmNoCsStre*100

Units: % Note:

KPI Description The KPI defines the drop rate for RRC Connection with a CS Streaming Data RAB on dedicated channel. It is calculated as the rate between abnormal disconnections of a CS streaming Data call over the total number of CS streaming disconnections. The pmNoCsStreamDchDiscNormal and pmNoCsStreamDchDiscAbnorm counters are only increased when the RRC Connection, for a streaming 57.6 kbps call, is released with the RRC Connection Release command respectively with “release cause” equal to ’normal event ’ or ’user inactivity’ or ’Directed Signaling Connection Re-establishment’ for the first one and anything but the just mentioned causes for the second one. Both the counters are stepped for the best cell in active set. In case of multi-RAB or multi signaling connection, the RRC Connection will remain after that the signaling connection or RAB to one CN have been released and therefore the counters shall not be increased. These counters will be only increased the first time the RRC Connection Release is sent to the UE. (The RNC may transmit several RRC messages to increase the probability of proper reception of the message by the UE).





This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

4.1.5 RRC Drop Rate CS64

KPI Name: RRC_DROPRATE_CS64 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

mhDiscAbnorpmNoCs64Dc

lhDiscNormapmNoCs64Dc/mhDiscAbnorpmNoCs64Dc *100

Units: % Note:

KPI Description The KPI defines the drop rate for RRC Connection with a CS64 Data RAB on dedicated channel. It is calculated as the rate between abnormal disconnections of a CS64 Data call over the total number of CS64 data call disconnections. The pmNoCs64DchDiscNormal and pmNoCs64DchDiscAbnorm counters are only increased when the RRC Connection, for a conversational 64 kbps call, is released with the RRC Connection Release command respectively with “release cause” equal to ’normal event ’ or ’user inactivity’ or ’Directed Signaling Connection Re-establishment’ for the first one and anything but the just mentioned causes for the second one. All the counters are stepped for the best cell in active set. In case of multi-RAB or multi signaling connection, the RRC Connection will remain after that the signaling connection or RAB to one CN have been released and therefore the counters shall not be increased. All these counters will be only increased the first time the RRC Connection Release is sent to the UE. (The RNC may transmit several RRC messages to increase the probability of proper reception of the message by the UE).






4.1.6 RRC Drop Rate PS Streaming

KPI Name: RRC_DROPRATE_PSSTREAMING RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

DiscAbnormam64Ps8DchpmNoPsStre

DiscNormalam64Ps8DchpmNoPsStre/DiscAbnormam64Ps8DchpmNoPsStre*100

Units: % Note:

KPI Description The KPI defines the drop rate for RRC Connection with a PS64 Streaming RAB on dedicated channel. It is calculated as the rate between abnormal disconnections of a PS64 Streaming call over the total number of PS64 streaming disconnections. The pmNoPsStream64Ps8DchDiscNormal and pmNoPsStream64Ps8DchDiscAbnorm counters are only increased when the RRC Connection for a PS streaming 64 kbps + PS 8kbps multi-RAB is released with the RRC Connection Release command respectively with “release cause” equal to ’normal event’ or ’user inactivity’ or ’Directed Signaling Connection Re-establishment’ for the first one and anything but the just mentioned causes for the second one. Both the counters are stepped for the best cell in active set. The PS8 RAB is always released together with the PS Streaming RAB when in a multi-RAB. These counters will be only increased the first time the RRC Connection Release is sent to the UE. (The RNC may transmit several RRC messages to increase the probability of proper reception of the message by the UE).






4.1.7 RRC Drop Rate PS Streaming 128

KPI Name: RRC_DROPRATE_PSSTREAMING128 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

mhDiscAbnoram128Ps8DcpmNoPsStre

lhDiscNormaam128Ps8DcpmNoPsStre/mhDiscAbnoram128Ps8DcpmNoPsStre*100

Units: % Note:

KPI Description The KPI defines the drop rate for RRC Connection with a PS128 Streaming RAB on dedicated channel. It is calculated as the rate between abnormal disconnections of a PS128 Streaming call over the total number of PS128 Streaming call disconnections. The pmNoPsStream128Ps8DchDiscNormal and pmNoPsStream128Ps8DchDiscAbnorm counters are only increased when the RRC Connection for a PS streaming 128 + PS 8 kbps multi-RAB is released with the RRC Connection Release command respectively with “release cause” equal to ’normal event’ or ’user inactivity’ or ’Directed Signaling Connection Re-establishment’ for the first one and anything but the just mentioned causes for the second one. All the counters are stepped for the best cell in active set. The PS8 RAB is always released together with the PS Streaming RAB when in a multi-RAB. All these counters will be only increased the first time the RRC Connection Release is sent to the UE. (The RNC may transmit several RRC





messages to increase the probability of proper reception of the message by the UE). This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

4.1.8 RRC Drop Rate PS Interactive

KPI Name: RRC_DROPRATE_PS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

+ ormDchDiscAbnpmNoPacket malDchDiscNorpmNoPacket

ormDchDiscAbnpmNoPacket*100

Units: % Note:

KPI Description The KPI defines the drop rate for RRC Connection for all PS Interactive RABs (HS PS Interactive included) on dedicated channel. It is calculated as the rate between abnormal disconnections of a packet call over the total number of disconnections. The pmNoPacketDchDiscNormal and the pmNoPacketDchDiscAbnorm counters are only increased when the RRC Connection of a packet call is released with the RRC Connection Release command respectively with “release cause” equal to ’normal event’ or ’user inactivity’ or ’Directed Signaling Connection Re-establishment’ for the first one and anything but the just mentioned causes for the second one. Both counters are stepped for the best cell in active set. In case of multi-RAB or multi signaling connection, the RRC Connection will remain after that the signaling connection or RAB to one CN have been released and therefore the counters shall not be increased. All these counters will be only





increased the first time the RRC Connection Release is sent to the UE. (The RNC may transmit several RRC messages to increase the probability of proper reception of the message by the UE). This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





4.2 RAB Drop Rate

4.2.1 RAB Drop Rate Speech

KPI Name: DROPRATE_SPEECH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell, IurLink Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

+ SpeechRabReleasepmNoSystem Speech RabReleasepmNoNormal

SpeechRabReleasepmNoSystem*100

Units: % Note: In P6, counters pmNoSystemRabReleaseSpeech and

pmNoNormalRabReleaseSpeech stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the drop rate for RAB Speech. It can be seen as the ratio between all the abnormal RAB Speech releases over the total number of all the RAB Speech releases. The pmNoNormalRabReleaseSpeech and pmNoSystemRabReleaseSpeech counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. For UtranCell class these counters are incremented for the best cell in the Active Set in the SRNC. All the counters involved in the formula are available in two different MOs: UtranCell and IurLink. If an analysis of RAB Drop Rate at Iur level or RNC level is required (instead of Cell level), It’s possible to collect data related to these counters with MO “IurLink” or “UtranCell” respectively, and in the latter case aggregate them on all the cells belonging to the RNC. Note also that, in case of activation of AMR, in this formula are present all the releases of AMR code RABs.





When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

4.2.2 RAB Drop Rate AMR-NB

KPI Name: DROPRATE_AMRNB RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

+ AmrNbRabReleasepmNoSystem AmrNbRabReleasepmNoNormal

AmrNbRabReleasepmNoSystem*100

Units: % Note: In P6, counters pmNoSystemRabReleaseAmrNb and

pmNoNormalRabReleaseAmrNb stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the drop rate for RAB AMR-NB. It can be seen as the ratio between all the abnormal RAB AMR-NB releases over the total number of all the RAB AMR-NB releases. The pmNoNormalRabReleaseAmrNb and pmNoSystemRabReleaseAmrNb counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. Note: This counter is only incremented in the SRNC. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





4.2.3 RAB Drop Rate AMR-WB

KPI Name: DROPRATE_AMRWB RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

+ AmrWbRabReleasepmNoSystem AmrWbRabReleasepmNoNormal

AmrWbRabReleasepmNoSystem*100

Units: % Note: In P6, counters pmNoSystemRabReleaseAmrWb and

pmNoNormalRabReleaseAmrWb stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the drop rate for RAB AMR-NB. It can be seen as the ratio between all the abnormal RAB AMR-NB releases over the total number of all the RAB AMR-WB releases. The pmNoNormalRabReleaseAmrWb and pmNoSystemRabReleaseAmrWb counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. Note: This counter is only incremented in the SRNC. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





4.2.4 RAB Drop Rate CS57

KPI Name: DROPRATE_CS57 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell, IurLink Counters Type: PEG Target Value:


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

CsStreamRabReleasepmNoSystem

CsStreamRabReleasepmNoNormal/CsStreamRabReleasepmNoSystem*100

Units: % Note: In P6, counters pmNoSystemRabReleaseCsStream and

pmNoNormalRabReleaseCsStream stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the drop rate for RAB Cs Streaming Data. It can be seen as the ratio between all the abnormal RAB Cs Streaming releases over the total number of all the RAB Cs Streaming releases. The pmNoNormalRabReleaseCsStream and pmNoSystemRabReleaseCsStream and counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for streaming 57.6 kbps call RAB respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. All the counters involved in the formula are available in two different MOs: UtranCell and IurLink. If an analysis of Rab Drop Rate at Iur level or RNC level is required (instead of Cell level), It’s possible to collect data related to these counters with MO “IurLink” or “UtranCell” respectively, and in the latter case aggregate them on all the cells belonging to the RNC. For UtranCell MO, these counters are incremented for the best cell in the Active Set in the SRNC. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI






4.2.5 RAB Drop Rate CS64

KPI Name: DROPRATE_CS64 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell, IurLink Counters Type: PEG Target Value:


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

Cs64RabReleasepmNoSystem

Cs64RabReleasepmNoNormal/Cs64RabReleasepmNoSystem*100

Units: % Note: In P6, counters pmNoSystemRabReleaseCs64 and

pmNoNormalRabReleaseCs64 stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the drop rate for RAB CS64 Data. It can be seen as the ratio between all the abnormal RAB CS64 releases over the total number of all the RAB CS64 releases. The pmNoNormalRabReleaseCs64 and pmNoSystemRabReleaseCs64 counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for a conversational 64 kbps RAB, respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. All the counters involved in the formula are available in two different MOs: UtranCell and IurLink. If an analysis of Rab Drop Rate at Iur level or RNC level is required (instead of Cell level), It’s possible to collect data related to these counters with MO “IurLink” or “UtranCell” respectively, and in the latter case aggregate them on all the cells belonging to the RNC. For UtranCell MO, these counters are incremented for the best cell in the Active Set in the SRNC.





When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

4.2.6 RAB Drop Rate PS Streaming

KPI Name: DROPRATE_PSSTREAMING RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

amPacketStreRabReleasepmNoSystem

amPacketStreRabReleasepmNoNormal/amPacketStreRabReleasepmNoSystem*100

Units: % Note: In P6, counters pmNoSystemRabReleasePacketStream

and pmNoNormalRabReleasePacketStream stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the drop rate for RABs Ps Streaming 64. It can be seen as the ratio between all the abnormal RAB Ps Streaming 64 releases over the total number of all the RAB Ps Streaming 64 releases. The pmNoNormalRabReleasePacketStream and pmNoSystemRabReleasePacketStream counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for a PS streaming 64 kbps, respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. For UtranCell class, these counters are incremented for the best cell in the Active Set in the SRNC. Note that for IurLink class the counters pmNoNormalRabReleasePacketStream and pmNoSystemRabReleasePacketStream are defined, taking in count PS Streaming





Rabs at all rates. Therefore, It’s possible to use the same KPI on Iur level but only on the totality of PS Streaming Rabs 64+128. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

4.2.7 RAB Drop Rate PS Streaming 128

KPI Name: DROPRATE_PSSTREAMING128 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell, IurLink Counters Type: PEG Target Value:


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

am128PacketStreRabReleasepmNoSystem

am128PacketStreRabReleasepmNoNormal/am128PacketStreRabReleasepmNoSystem*100

Units: % Note: In P6, counters pmNoSystemRabReleasePacketStream128

and pmNoNormalRabReleasePacketStream128 stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the drop rate for RABs Ps128 Streaming. It can be seen as the ratio between all the abnormal RAB Ps Streaming 128 releases over the total number of all the RAB Ps Streaming 128 releases. The pmNoNormalRabReleasePacketStream128 and pmNoSystemRabReleasePacketStream128 counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for a PS streaming 128 RAB, respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. Note that for IurLink class the counters pmNoNormalRabReleasePacketStream and





pmNoSystemRabReleasePacketStream are defined, taking in count PS Streaming Rabs at all rates. Therefore, It’s possible to use the same KPI on Iur level but only on the totality of PS Streaming Rabs 64+128. For UtranCell class, these counters are incremented for the best cell in the Active Set in the SRNC. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

4.2.8 RAB Drop Rate PS Interactive

KPI Name DROPRATE_PS RNC Sw Release: P6 Importance: High Scope: Cell, Iur Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell, IurLink Counters Type: PEG Target Value:


⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

+

+

aSuccFachUrpmChSwitch

PacketUraRabReleasepmNoSystem

-PacketRabReleasepmNoSystem

PacketUraRabReleasepmNoNormal

-Packet RabReleasepmNoNormal

/PacketUraRabReleasepmNoSystem

-PacketRabReleasepmNoSystem*100

Units: % Note: In P6, counters pmNoSystemRabReleasePacket and

pmNoNormalRabReleasePacket stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the drop rate for all the PS RABs on Cell basis (all counters defined in MO class “UtranCell”). It can be seen as the ratio between all the abnormal RAB Ps releases over the total number of all the RAB Ps releases (including all the normal releases due to all the downswitchs from FACH state to URA). The pmNoNormalRabReleasePacket and pmNoSystemRabReleasePacket





counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for all PS RABs respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. The pmNoNormalRabReleasePacketUra counter represents the number of normal release of packet Rabs while on URA state. The pmNoSystemRabReleasePacketUra counter represents the number of system release of packet Rabs while on URA state. The pmChSwithSuccFachUra counter represents the number of successful channel downswitching attempts from CELL_FACH to URA_PCH. This counter is increased for every successful channel downswitching attempt from CELL_FACH to URA_PCH. It is possible to define the same KPI on the Iur, taking in count the same counters for MO “IurLink”, without considering the URA state (the counters pmNoNormalRabReleasePacketUra and pmNoSystemRabReleasePacketUra are not defined for the MO “IurLink”). The following formula can be used on IurLink:

( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

PacketRabReleasepmNoSystem

PacketRabReleasepmNoNormal/PacketRabReleasepmNoSystem*100


4.2.9 RAB Drop Rate PS Interactive DCH/FACH

KPI Name DROPRATE_PS_NON_HS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value: 1.5%






⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

+

+

−

+

schSuccessHpmDlUpswit

essFachHsSuccpmUpswitch

sRbReleaseHpmNoSystem


-Packet RabReleasepmNoSystem

sRbReleaseHpmNoNormal

-PacketUraRabReleasepmNoNormal


/




*100 -

Units: % Note: In P6, counters pmNoSystemRabReleasePacket and

pmNoNormalRabReleasePacket stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the drop rate for all the PS RABs only R99 on Cell basis (all counters defined in MO class “UtranCell”). It can be seen as the ratio between all the abnormal RAB PS DCH/FACH releases over the total number of all the RAB PS DCH/FACH releases (including all the normal releases due to all the upswitchs from DCH/FACH state to HS). The pmNoNormalRabReleasePacket and pmNoSystemRabReleasePacket counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for all PS RABs respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. The pmNoNormalRabReleasePacketUra counter represents the number of normal release of packet Rabs while on URA state. The pmNoSystemRabReleasePacketUra counter represents the number of system release of packet Rabs while on URA state. The pmNoSystemRbReleaseHs counter is stepped for the Serving HS-DSCH cell at RAB/RB combination transition from PS Interactive 64/HS (or 384/HS or EUL/HS) - HS-DSCH to SRB-DCH or to Idle mode due to the same reasons as for stepping the existing counter pmNoSystemRabReleasePacket. For UtranCell class, this counter is stepped for the Serving HS-DSCH cell. The same counter have not been released on Iur link levelThe pmNoNormalRbReleaseHs counter is only increased, at RAB/RB combination transition from PS Interactive 64/HS - HS-DSCH to SRB-DCH or to Idle mode, due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. The pmUpswitchFachHsSuccess counter provides the number of successful upswitches from FACH to any HS state. The counter is stepped for successful upswitch from CELL_FACH to a RB combination containing HS. The counter is only incremented in all cells of the active set. The pmDlUpswitchSuccessHs counter provides the number of successful DL upswitches to any HS state. The counter is stepped for





successful DL upswitch to a RB combination containing HS. The counter is only incremented in all cells of the active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

4.2.10 RAB Drop Rate PS Interactive HS

KPI Name DROPRATE_PS_HS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value: NA


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +


sRbReleaseHpmNoNormal/sRbReleaseHpmNoSystem*100

Units: % Note: In P6, counters pmNoSystemRbReleaseHs and

pmNoNormalRbReleaseHs stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the drop rate for RAB PS HSDPA on Cell basis (all counters defined in MO class “UtranCell”). It can be seen as the ratio between all the abnormal RAB PS HSDPA releases over the total number of all the RAB PS HSDPA releases. Note that in PS HS RAB releases have been counted also relatively PS EUL ones. Since HSDPA to DCH and HSDPA to FACH reconfigurations have to be considered in P5, this KPI can result not comparable with the values in P4. And due to the new channel switching strategy in P5, as calculated in the formula above, this KPI can give very high values. Therefore, for all these reasons, it’s highly recommended to use Minutes per Drop (or Drops Over Erl) formula for benchmark P4 to P5 figures and for meaningful KPIs values.






4.2.11 RAB Drop Rate PS Streaming HS

KPI Name DROPRATE_PSSTR_HS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value: NA


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

PsStreamHsRabReleasepmNoSystem

PsStreamHsRabReleasepmNoNormal/PsStreamHsRabReleasepmNoSystem*100

Units: % Note: In P6, counters pmNoSystemRabReleasePsStreamHs and

pmNoNormalRabReleasePsStreamHs stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC New counters in P6

KPI Description

The KPI defines the drop rate for RAB streaming PS unknown HS on Cell basis (all counters defined in MO class “UtranCell”). It can be seen as the ratio between all the abnormal RAB streaming PS unknown HS releases over the total number of all the RAB streaming PS unknown HS releases. Counter pmNoSystemRabReleasePsStreamHs incremented by one when a RANAP Iu Release Command or RAB Assignment Request message with "release cause" = anything except 'Normal Release', 'Successful Relocation', 'Resource Optimisation Relocation', 'User Inactivity' or 'release-due-to-UE-generated-signalling-connection-release' including a PS Streaming RAB on HS-DSCH. The counter is incremented for the best cell in the Active Set in the SRNC.

Counter pmNoNormalRabReleasePsStreamHs incremented by one when a





RANAP Iu Release Command or RAB Assignment Request message with "release cause" = 'Normal Release', 'Successful Relocation', 'Resource Optimisation Relocation', 'User Inactivity' or 'release-due-to-UE-generated-signalling-connection-release' including a PS Streaming RAB on HS-DSCH.

Both counted in best cell of Active Set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

4.2.12 RAB Drop Rate PS Interactive EUL

KPI Name DROPRATE_PS_EUL RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value: NA


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

ulRbReleaseEpmNoSystem

ulRbReleaseEpmNoNormal/ulRbReleaseEpmNoSystem*100

Units: % Note: In P6, counters pmNoSystemRbReleaseEul and

pmNoNormalRbReleaseEul stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the drop rate for RAB Eul on Cell basis (all counters defined in MO class “UtranCell”). It can be seen as the ratio between all the abnormal RAB EUL releases over the total number of all the RAB EUL releases. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can





give incorrect results.

4.2.13 RAB Drop Rate PS Interactive URA

KPI Name DROPRATE_PS_URA RNC Sw Release: P5 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value: NA


( ) ⎟⎟⎠

⎞⎜⎜⎝

⎛ +

acketUraRbReleasePpmNoSystem

acketUraRbReleasePpmNoNormal/acketUraRbReleasePpmNoSystem*100

Units: % Note:

KPI Description The KPI defines the drop rate for packet RABs on URA state on Cell basis (all counters defined in MO class “UtranCell”). It can be seen as the ratio between all the abnormal packet RABs releases on URA state over the total number of all the packet RABs releases on URA state. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





4.3 Minutes per Drop

4.3.1 Minutes per Drop Speech

KPI Name MPD_SPEECH RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


[ ] ⎟⎟⎠

⎞⎜⎜⎝

⎛SpeechRabReleasepmNoSystem

/ERL_SPEECH*utestTimeInMinMeasuremen

Units: Minutes Note: Counter stepped in SRNC, DRNC if

IurLink::srncPmReporting = ON in SRNC

KPI Description This formula gives the average time length (in minutes) between 2 consecutive drops of speech call. It can be seen also as the normalization of drop call over the total time a user is occupying a channel. This KPI is very useful to report real end user perception of drop call because it gives the idea how often a user is experiencing a drop call. A real useful way to monitor drop rate, even closer to the concept of drop rate, is the equivalent Drops per Erl Speech, calculated as:

⎟⎟⎠

⎞⎜⎜⎝

⎛ERL_SPEECH

Speech / RabReleasepmNoSystem

The ERL_SPEECH contribution represents all the traffic (in Erlangs) generated by the all the RABs Speech in the measured time. Please refer to the Traffic section for the description and the metric of this term. The pmNoSystemRabReleaseSpeech counter is only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech respectively with “release cause” = anything except ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For IurLink class, it is incremented for the IurLink representing the DRNC for the best cell in the active set. Note that, in





case of Multi RAB, are included all the releases from Multi RAB to only PS RAB and to Idle state. The KPI can be computed on RNC basis, using RNC_ERL_SPEECH (instead of ERL_SPEECH) which provides all the traffic (in Erlangs) generated by the all the RABs Speech in the measured time. This figure is calculated on RNC level with UeRc index related to Speech RAB. In this case, before computing the KPI, the counter pmNoSystemRabReleaseSpeech has to be aggregated on all the cells belonging to the RNC and on all Iur links from this RNC to neighboring RNCs, because the same counter has been defined on cell level and on Iur link level. During optimization activity and especially in case of parameter changes (i.e. in order to favorite or less IRAT handover), it is recommended to monitor this KPI since the absolute value of RAB or RRC Drop Call Rate can give a partial vision of the performances because it is not taking into consideration service time length (i.e. increasing or decreasing Speech on 3G call durations).

4.3.2 Minutes per Drop AMR-NB

KPI Name MPD_AMR RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


[ ] ⎟⎟⎠

⎞⎜⎜⎝

⎛AmrNbRabReleasepmNoSystem

ERL_AMRNB/*utestTimeInMinMeasuremen



KPI Description This formula gives the average time length (in minutes) between 2 consecutive drops of AMR-NB call. It can be seen also as the normalization of drop call over the total time a user is occupying a channel. This KPI is very useful to report real end user perception of drop call because it gives the idea how often a user is experiencing a drop call. A real useful way to monitor drop rate, even closer to the





concept of drop rate, is the equivalent Drops per Erl AMR, calculated as:

⎟⎟⎠

⎞⎜⎜⎝

⎛RNBTRAFFIC_AM

/ AmrNbRabReleasepmNoSystem

The ERL_AMRNB contribution represents all the traffic (in Erlangs) generated by the all the RABs AMR-NB in the measured time. Please refer to the Traffic section for the description and the metric of this term. The pmNoSystemRabReleaseAmrNb counter is only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB AMR-NB respectively with “release cause” = anything except ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. The KPI can be computed on RNC basis, using RNC_ERL_AMRNB (instead of ERL_AMRNB) which provides all the traffic (in Erlangs) generated by all the RABs AMR-NB in the measured time. This figure is calculated on RNC level with UeRc index related to AMR-NB RAB. In this case, before computing the KPI, the counter pmNoSystemRabReleaseAmrNb has to be aggregated on all the cells belonging to the RNC. During optimization activity and especially in case of parameter changes (i.e. in order to favorite or less IRAT handover), it is recommended to monitor this KPI since the absolute value of RAB or RRC Drop Call Rate can give a partial vision of the performances because it is not taking into consideration service time length (i.e. increasing or decreasing Speech on 3G call durations).

4.3.3 Minutes per Drop AMR-WB

KPI Name MPD_AMR RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


[ ] ⎟⎟⎠

⎞⎜⎜⎝

⎛AmrNbRabReleasepmNoSystem

ERL_AMRWB/*utestTimeInMinMeasuremen






IurLink::srncPmReporting = ON in SRNC. In P6 new RAB AMR-WB introduced.

KPI Description

This formula gives the average time length (in minutes) between 2 consecutive drops of AMR-WB call. It can be seen also as the normalization of drop call over the total time a user is occupying a channel. This KPI is very useful to report real end user perception of drop call because it gives the idea how often a user is experiencing a drop call. A real useful way to monitor drop rate, even closer to the concept of drop rate, is the equivalent Drops per Erl AMR-WB, calculated as:

⎟⎟⎠

⎞⎜⎜⎝

⎛ERL_AMRWB

/ AmrNbRabReleasepmNoSystem

The ERL_AMRWB contribution represents all the traffic (in Erlangs) generated by the all the RABs AMR-WB in the measured time. Please refer to the Traffic section for the description and the metric of this term. The pmNoSystemRabReleaseAmrNb counter is only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB AMR-WB respectively with “release cause” = anything except ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. The KPI can be computed on RNC basis, using RNC_ERL_AMRWB (instead of ERL_AMRWB) which provides all the traffic (in Erlangs) generated by all the RABs AMR-NB in the measured time. This figure is calculated on RNC level with UeRc index related to AMR-WB RAB. In this case, before computing the KPI, the counter pmNoSystemRabReleaseAmrWb has to be aggregated on all the cells belonging to the RNC. During optimization activity and especially in case of parameter changes (i.e. in order to favorite or less IRAT handover), it is recommended to monitor this KPI since the absolute value of RAB or RRC Drop Call Rate can give a partial vision of the performances because it is not taking into consideration service time length (i.e. increasing or decreasing Speech on 3G call durations).

4.3.4 Minutes per Drop CS57

KPI Name MPD_CS57 RNC Sw Release: P6 Importance: High





Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


[ ] ⎟⎟⎠

⎞⎜⎜⎝

⎛CsStreamRabReleasepmNoSystem

EAM_DATA /ERL_CS_STR*utestTimeInMinMeasuremen



KPI Description This formula gives the average time length (in minutes) between 2 consecutive drops of CS57 Streaming Data call. It can be seen also as the normalization of drop call over the total time a user is occupying a channel. This KPI is very useful to report real end user perception of drop call because it gives the idea how often a user is experiencing a drop call. A real useful way to monitor drop rate, even closer to the concept of drop rate, is the equivalent Drops per Erl CS57 Streaming Data, calculated as:

⎟⎟⎠

⎞⎜⎜⎝

⎛EAM_DATAERL_CS_STR

/ CsStreamRabReleasepmNoSystem

The ERL_CS_STREAM_DATA contribution represents all the traffic (in Erlangs) generated by the all the RABs CS57 Streaming in the measured time. Please refer to the Traffic section for the description and the metric of this term. The pmNoSystemRabReleaseCsStream counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for streaming 57.6 kbps call respectively with “release cause” = anything except ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For UtranCell class, this counter is incremented for the best cell in the Active Set in the SRNC. For IurLink class, it is incremented for the IurLink representing the DRNC for the best cell in the active set. The KPI can be computed on RNC basis, using RNC_ERL_CS_STREAM_DATA (instead of ERL_CS_STREAM_DATA) which provides all the traffic (in Erlangs) generated by the all the RABs CS57 in the measured time. This figure is calculated on RNC level with UeRc index related to CS57 RAB. In this case, before computing the KPI, the counter pmNoSystemRabReleaseCsStream has to be aggregated on all the cells belonging to the RNC and on all Iur links from this RNC to neighboring RNCs, because the same counter has been defined on cell level and on Iur link level.





During optimization activity and especially in case of parameter changes (i.e. in order to favorite or less up/down switch), it is recommended to monitor this KPI since the absolute value of RAB or RRC Drop Call Rate can give a partial vision of the performances because it is not taking into consideration service time length (i.e. increasing or decreasing PS Interactive section durations).

4.3.5 Minutes per Drop CS64

KPI Name MPD_CS64 RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


[ ] ⎟⎟⎠

⎞⎜⎜⎝

⎛Cs64RabReleasepmNoSystem

TA /ERL_CS64DA*utestTimeInMinMeasuremen



KPI Description This formula gives the average time length (in minutes) between 2 consecutive drops of CS64 Data call. It can be seen also as the normalization of drop call over the total time a user is occupying a channel. This KPI is very useful to report real end user perception of drop call because it gives the idea how often a user is experiencing a drop call. A real useful, even closer to the concept of drop rate, is the equivalent Drops per Erl CS64 Data, calculated as:

⎟⎟⎠

⎞⎜⎜⎝

⎛TAERL_CS64DA

/ Cs64RabReleasepmNoSystem

The ERL_CS64DATA contribution represents all the traffic (in Erlangs) generated by the all the RABs CS64 in the measured time. Please refer to the Traffic section for the description and the metric of this term. The pmNoSystemRabReleaseCs64 counters is only increased due to a RANAP Iu Release Command or RAB Assignment Request message for a conversational 64 kbps RAB Data respectively





with “release cause” = anything except ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For UtranCell class, this counter is incremented for the best cell in the Active Set in the SRNC. For IurLink class, it is incremented for the IurLink representing the DRNC for the best cell in the active set. The KPI can be computed on RNC basis, using RNC_ERL_CS64DATA (instead of ERL_CS64DATA) which provides all the traffic (in Erlangs) generated by the all the RABs CS64 in the measured time. This figure is calculated on RNC level with UeRc index related to CS64 RAB and to CS64+PS8 multiRAB. In this case, before computing the KPI, the counter pmNoSystemRabReleaseCs64 has to be aggregated on all the cells belonging to the RNC and on all Iur links from this RNC to neighboring RNCs, because the same counter has been defined on cell level and on Iur link level. During optimization activity and especially in case of parameter changes (i.e. in order to favorite or less up/down switch), it is recommended to monitor this KPI since the absolute value of RAB or RRC Drop Call Rate can give a partial vision of the performances because it is not taking into consideration service time length (i.e. increasing or decreasing PS Interactive section durations).

4.3.6 Minutes per Drop PS Streaming

KPI Name MPD_PSSTREAMING RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


[ ] ⎟⎟⎠

⎞⎜⎜⎝

⎛amPacketStreRabReleasepmNoSystem

/TREAMERL_PS64_S*utestTimeInMinMeasuremen



KPI Description





This formula gives the average time length (in minutes) between 2 consecutive drops of PS64 Streaming call. It can be seen also as the normalization of drop call over the total time a user is occupying a channel. This KPI is very useful to report real end user perception of drop call because it gives the idea how often a user is experiencing a drop call. A real useful way to monitor drop rate, even closer to the concept of drop rate, is the equivalent Drops per Erl PS64 Streaming, calculated as:

⎟⎟⎠

⎞⎜⎜⎝

⎛TREAMERL_PS64_S

/ amPacketStreRabReleasepmNoSystem

The ERL_PS64_STREAM contribution represents all the traffic (in Erlangs) generated by the all the RABs PS Streaming 64 in the measured time. Please refer to the Traffic section for the description and the metric of this term. The pmNoSystemRabReleasePacketStream counter is only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RABs PS64 Streaming respectively with “release cause” = anything except ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For UtranCell class, this counter is incremented for the best cell in the Active Set in the SRNC. For IurLink class, it is incremented for the IurLink representing the DRNC for the best cell in the active set. The KPI can be computed on RNC basis, using RNC_ERL_PS64_STREAM (instead of ERL_PS64_STREAM) which provides all the traffic (in Erlangs) generated by the all the RABs PS64 Streaming in the measured time. This figure is calculated on RNC level with UeRc index related to PS64 Streaming RAB. In this case, before computing the KPI, the counter pmNoSystemRabReleasePacketStream has to be aggregated on all the cells belonging to the RNC and on all Iur links from this RNC to neighboring RNCs, because the same counter has been defined on cell level and on Iur link level. During optimization activity and especially in case of parameter changes (i.e. in order to favorite or less up/down switch), it is recommended to monitor this KPI since the absolute value of RAB or RRC Drop Call Rate can give a partial vision of the performances because it is not taking into consideration service time length (i.e. increasing or decreasing PS Interactive section durations).

4.3.7 Minutes per Drop PS Streaming 128

KPI Name MPD_PSSTREAMING128 RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour







[ ] ⎟⎟⎠

⎞⎜⎜⎝

⎛am128PacketStreRabReleasepmNoSystem

/STREAMERL_PS128_*utestTimeInMinMeasuremen



KPI Description This formula gives the average time length (in minutes) between 2 consecutive drops of PS128 Streaming call. It can be seen also as the normalization of drop call over the total time a user is occupying a channel. This KPI is very useful to report real end user perception of drop call because it gives the idea how often a user is experiencing a drop call. A real useful way to monitor drop rate, even closer to the concept of drop rate, is the equivalent Drops per Erl PS128 Streaming, calculated as:

⎟⎟⎠

⎞⎜⎜⎝

⎛STREAMERL_PS128_

/ am128PacketStreRabReleasepmNoSystem

The ERL_PS128_STREAM contribution represents all the traffic (in Erlangs) generated by the all the RABs PS Streaming 128 in the measured time. Please refer to the Traffic section for the description and the metric of this term. The pmNoSystemRabReleasePacketStream128 counter is only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RABs PS128 Streaming respectively with “release cause” = anything except ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For UtranCell class, this counter is incremented for the best cell in the Active Set in the SRNC. For IurLink class, it is incremented for the IurLink representing the DRNC for the best cell in the active set. The KPI can be computed on RNC basis, using RNC_ERL_PS128_STREAM (instead of ERL_PS128_STREAM) which provides all the traffic (in Erlangs) generated by the all the RABs PS128 Streaming in the measured time. This figure is calculated on RNC level with UeRc index related to PS128 Streaming RAB. In this case, before computing the KPI, the counter pmNoSystemRabReleasePacketStream128 has to be aggregated on all the cells belonging to the RNC and on all Iur links from this RNC to neighboring RNCs, because the same counter has been defined on cell level and on Iur link level. During optimization activity and especially in case of parameter changes (i.e. in order to favorite or less up/down switch), it is recommended to monitor this KPI since the absolute value of RAB or RRC Drop Call Rate can give a partial vision of





the performances because it is not taking into consideration service time length (i.e. increasing or decreasing PS Interactive section durations).

4.3.8 Minutes per Drop PS Interactive

KPI Name MPD_PS RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


[ ]⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

PacketUra)RabReleasepmNoSystem

-PacketRabReleasepmNoSystem(

/ERL_PSDATA

*utestTimeInMinMeasuremen



KPI Description This formula gives the average time length (in minutes) between 2 consecutive drops of PS Interactive call, on cell basis with both involved counters defined for MO UtranCell). It can be seen also as the normalization of drop call over the total time a user is occupying a channel. This KPI is very useful to report real end user perception of drop call because it gives the idea how often a user is experiencing a drop call. A real useful way to monitor drop rate, even closer to the concept of drop rate, is the equivalent Drops per Erl PS Interactive, calculated as:

⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

ERL_PSDATA

/ PacketUra)RabReleasepmNoSystem


The ERL_PSDATA contribution represents all the traffic (in Erlangs) generated by the all the RABs PS Interactive in the measured time. Please refer to the Traffic section for the description and the metric of this term. The pmNoSystemRabReleasePacket counter is only increased due to a RANAP Iu





Release Command or RAB Assignment Request message for RABs PS Interactive respectively with “release cause” = anything except ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For UtranCell class, this counter is incremented for the best cell in the Active Set in the SRNC. For IurLink class, it is incremented for the IurLink representing the DRNC for the best cell in the active set. The counter pmNoSystemRabReleasePacketUra is not defined for IurLink class. Note that, in case of Multi RAB, are included all the releases from Multi RAB to only CS RAB and to Idle state. The KPI can be computed on RNC basis, using RNC_ERL_PSDATA (instead of ERL_PSDATA) which provides all the traffic (in Erlangs) generated by the all the RABs PS interactive in the measured time. This figure is calculated on RNC level with UeRc indexes related to Ps Interactive FACH, 64/64, 64/128, 64/384, 64/HS, 384/HS, EUL/HS, CS 12.2 + PS 64 MultiRAB, CS 12.2 + 64/HS MultiRAB, CS 12.2 + 384/HS MultiRAB, EUL/HS RAB. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. In this case, before computing the KPI, the counter pmNoSystemRabReleasePacket has to be aggregated on all the cells belonging to the RNC and on all Iur links from this RNC to neighboring RNCs (because the same counter has been defined on cell level and on Iur link level), while the counter pmNoSystemRabReleasePacketUra is only to be aggregated on all the cells belonging to the RNC since it is not defined for IurLink class. When releasing a HS RAB, pmNoSystemRabReleasePacket counter is stepped for the Serving HS-DCH cell. During optimization activity and especially in case of parameter changes (i.e. in order to favorite or less up/down switch), it is recommended to monitor this KPI since the absolute value of RAB or RRC Drop Call Rate can give a partial vision of the performances because it is not taking into consideration service time length (i.e. increasing or decreasing PS Interactive section durations).

4.3.9 Minutes per Drop PS DCH/FACH Data

KPI Name MPD_PS_NON_HS RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






[ ]⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

PacketUra)RabReleasepmNoSystem

-HsRbReleasepmNoSystem


_DCHFACH/ ERL_PSDATA




KPI Description This formula gives the average time length (in minutes) between 2 consecutive drops of PS DCH/FACH Interactive call, on cell basis with all counters involved in the formula defined for MO UtranCell). It can be seen also as the normalization of drop call over the total time a user is occupying a channel. This KPI is very useful to report real end user perception of drop call because it gives the idea how often a user is experiencing a drop call. A real useful way to monitor drop rate, even closer to the concept of drop rate, is the equivalent Drops per Erl PS DCH/FACH Interactive, calculated as:

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

_DCHFACHERL_PSDATA

/ PacketUra)RabReleasepmNoSystem

-HsRbReleasepmNoSystem


The ERL_PSDATA_DCHFACH contribution represents all the traffic (in Erlangs) generated by the all the RABs PS DCH/FACH Interactive in the measured time. Please refer to the Traffic section for the description and the metric of this term. The pmNoSystemRabReleasePacket counter is only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RABs PS Interactive respectively with “release cause” = anything except ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For UtranCell class, this counter is incremented for the best cell in the Active Set in the SRNC. For IurLink class, it is incremented for the IurLink representing the DRNC for the best cell in the active set. The pmNoSystemRbReleaseHs counter is stepped for the Serving HS-DSCH cell at RAB/RB combination transition from PS Interactive 64/HS (or 384/HS or EUL/HS) - HS-DSCH to SRB-DCH or to Idle mode due to the same reasons as for stepping the existing counter pmNoSystemRabReleasePacket. For UtranCell class, this counter is stepped for the Serving HS-DSCH cell. The same counter have not been released on Iur link level. In P5 Inter RNC mobility is supported through reconfiguration to R99 RAB if the network setting allows to do that (hsToDchTrigger.servHsChangeInterRnc=True). The pmNoSystemRabReleasePacketUra counter is stepped for Packet RABs on URA state, due to the same reason as for stepping pmNoSystemRabReleasePacket and it is not defined for IurLink class. Note that, in case of Multi RAB, are included all the releases from Multi RAB to only CS RAB and to Idle state.





The KPI can be computed on RNC basis, using RNC_ERL_PSDATA_DCHFACH (instead of ERL_PSDATA_DCHFACH) which provides all the traffic (in Erlangs) generated by the all the RABs PS DCH/FACH interactive in the measured time. This figure is calculated on RNC level with UeRc indexes related to Ps Interactive FACH, 64/64, 64/128, 64/384, 64/HS, 384/HS, EUL/HS, CS 12.2 + PS 64 MultiRAB, CS 12.2 + 64/HS MultiRAB, CS 12.2 + 384/HS MultiRAB, EUL/HS RAB. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. In this case, before computing the KPI, the counter pmNoSystemRabReleasePacket has to be aggregated on all the cells belonging to the RNC and on all Iur links from this RNC to neighboring RNCs (because the same counter has been defined on cell level and on Iur link level), while the counters pmNoSystemRabReleasePacketUra and pmNoSystemRbReleaseHs are only to be aggregated on all the cells belonging to the RNC since they are not defined for IurLink class. When releasing a HS RAB, pmNoSystemRabReleasePacket counter is stepped for the Serving HS-DCH cell. During optimization activity and especially in case of parameter changes (i.e. in order to favorite or less up/down switch), it is recommended to monitor this KPI since the absolute value of RAB or RRC Drop Call Rate can give a partial vision of the performances because it is not taking into consideration service time length (i.e. increasing or decreasing PS Interactive section durations).

4.3.10 Minutes per Drop HS Data

KPI Name MPD_PS_HS RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


[ ] ⎟⎟⎠

⎞⎜⎜⎝

⎛sRbReleaseHpmNoSystem

/ERL_HS*utestTimeInMinMeasuremen



KPI Description





This formula gives the average time length (in minutes) between 2 consecutive drops of HSDPA call on cell basis (both counters involved in the formula are defined for UtranCell class). It can be seen also as the normalization of drop call over the total time a user is occupying a channel. This KPI is very useful to report real end user perception of drop call because it gives the idea how often a user is experiencing a drop call. A real useful way to monitor drop rate, even closer to the concept of drop rate, is the equivalent Drops per Erl PS HS Data, calculated as:

⎟⎟⎠

⎞⎜⎜⎝

⎛ERL_HS

/ HsRbReleasepmNoSystem

The ERL_HS contribution represents all the traffic (in Erlangs) generated by the all the RABs HS Ps interactive in the measured time. Please refer to the Traffic section for the description and the metric of this term. The pmNoSystemRbReleaseHs counter is stepped for the Serving HS-DSCH cell at RAB/RB combination transition from PS Interactive 64/HS (or 384/HS or EUL/HS) - HS-DSCH to SRB-DCH or to Idle mode due to the same reasons as for stepping the existing counter pmNoSystemRabReleasePacket. For UtranCell class, this counter is stepped for the Serving HS-DSCH cell. The KPI can be computed on RNC basis, using RNC_ERL_HS (instead of ERL_HS) which provides all the traffic (in Erlangs) generated by the all the RABs PS interactive in the measured time. This figure is calculated on RNC level with UeRc indexes related to PS 64/HS, 384/HS, CS 12.2 + 64/HS MultiRAB, CS 12.2 + 384/HS MultiRAB, EUL/HS RAB. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. In this case the KPI is calculated on RNC level so the pmNoSystemRbReleaseHs counter has to be aggregated on all the cells belonging to this RNC.

4.3.11 Minutes per Drop PS Streaming HS

KPI Name MPD_PSSTR_HS RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






[ ] ⎟⎟⎠

⎞⎜⎜⎝

⎛)PsStreamHsRabReleasepmNoSystem(

/SERL_PSSTRH*utestTimeInMinMeasuremen

Units: Minutes Note: In P6 new RAB PS Streaming HS introduced.

Counter stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

This formula gives the average time length (in minutes) between 2 consecutive drops of PS Interactive call, on cell basis with both involved counters defined for MO UtranCell). It can be seen also as the normalization of drop call over the total time a user is occupying a channel. This KPI is very useful to report real end user perception of drop call because it gives the idea how often a user is experiencing a drop call. A real useful way to monitor drop rate, even closer to the concept of drop rate, is the equivalent Drops per Erl PS Streaming HS, calculated as:

⎟⎟⎠

⎞⎜⎜⎝

⎛SERL_PSSTRH

/ sStreamHs)PRabReleasepmNoSystem(

The ERL_PSDATA contribution represents all the traffic (in Erlangs) generated by the all the RABs PS Streaming HS in the measured time. Please refer to the Traffic section for the description and the metric of this term. The pmNoSystemRabReleasePsStreamHs counter is only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RABs PS Streaming Hs respectively with “release cause” = anything except ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For UtranCell class, this counter is incremented for the best cell in the Active Set in the SRNC. The KPI can be computed on RNC basis, using RNC_ERL_PSDATA (instead of ERL_PSDATA) which provides all the traffic (in Erlangs) generated by the all the RABs PS interactive in the measured time. This figure is calculated on RNC level with UeRc indexes related to Ps Interactive FACH, 64/64, 64/128, 64/384, 64/HS, 384/HS, EUL/HS, CS 12.2 + PS 64 MultiRAB, CS 12.2 + 64/HS MultiRAB, CS 12.2 + 384/HS MultiRAB, EUL/HS RAB. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. In this case, before computing the KPI, the counter pmNoSystemRabReleasePsSreamHst has to be aggregated on all the cells belonging to the. When releasing a HS RAB, pmNoSystemRabReleasePsStreamHs counter is stepped for the Serving HS-DCH cell. During optimization activity and especially in case of parameter changes (i.e. in order to favorite or less up/down switch), it is recommended to monitor this KPI since the absolute value of RAB or RRC Drop Call Rate can give a partial vision of the performances because it is not taking into consideration service time length (i.e. increasing or decreasing PS Interactive section durations).





4.3.12 Minutes per Drop EUL

KPI Name MPD_PS_EUL RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


[ ] ⎟⎟⎠

⎞⎜⎜⎝

⎛ulRbReleaseEpmNoSystem

/ERL_EUL*utestTimeInMinMeasuremen

Units: Minutes Note:

KPI Description This formula gives the average time length (in minutes) between 2 consecutive drops of EUL/HS calls on cell basis (both counters involved in the formula are defined for UtranCell class). It can be seen also as the normalization of drop call over the total time a user is occupying a EUL/HS PS RAB. A real useful way to monitor drop rate, even closer to the concept of drop rate, is the equivalent Drops per Erl PS EUL Data, calculated as:

⎟⎟⎠

⎞⎜⎜⎝

⎛ERL_EUL

/ EulRbReleasepmNoSystem

The ERL_EUL contribution represents all the traffic (in Erlangs) generated by the all the RABs Eul in the measured time. Please refer to the Traffic section for the description and the metric of this term. The pmNoSystemRbReleaseEul counter is the number of system initiated RAB releases for PS Interactive RAB mapped on E-DCH/ HSDPA. It is stepped for the Serving E-DCH cell for release of RAB/RB combination PS Interactive E-DCH/HS - HS-DSCH due to: RANAP Iu Release Command or RAB Assignment Request message with "release cause" = anything except 'Normal Release', 'Successful Relocation', 'Resource Optimisation Relocation', 'User Inactivity' or 'release-due-to-UE-generated- signalling-connection-release'. This counter is incremented for the Serving EUL/HS-DCH cell. The pmNoSystemRabReleasePacketUra counter is stepped for Packet RABs on URA state, due to the same reason as for stepping





pmNoSystemRabReleasePacket. Note: These counters are only incremented in the SRNC. The KPI can be computed on RNC basis, using RNC_ERL_EUL (instead of ERL_EUL) which provides all the traffic (in Erlangs) generated by the Ps Interactive RAB mapped to EUL/HS-DSCH in the measured time. This figure is calculated on RNC level with UeRc index related to EUL/HS RAB. In this case the KPI is calculated on RNC level so the pmNoSystemRbReleaseEul counter has to be aggregated on all the cells belonging to this RNC. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula.





4.4 Average Holding Time

4.4.1 Average Holding Time Speech

KPI Name AHT_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc, UtranCell Counters Type: PEG Target Value:


[ ]⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛ +

SpeechRabReleasepmNoSystem

Speech RabReleasepmNoNormal

/ ERL_SPEECH


Units: Minutes Note: In P6, new UeRc have been added. [Please refer to

Appendix]

KPI Description This formula gives the average time length (in minutes) the end user is utilizing a Speech service. It can be seen also as the normalization of any kind of releases over the total time a user is occupying a channel. It is also a very useful indication of end user behavior in terms of service time and of the traffic load in the network. Actually it can be also used as traffic monitoring KPI. The ERL_SPEECH contribution represents all the traffic (in Erlangs) generated by the all the RABs Speech in the measured time. This figure is calculated on Cell level with UeRc index related to Speech RAB. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. The pmNoNormalRabReleaseSpeech and pmNoSystemRabReleaseSpeech counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. For UtranCell class, these counters are incremented for the best cell in the Active Set in





the SRNC while, for IurLink class, they are incremented for the IurLink representing the DRNC for the best cell in the active set. Note that, in case of Multi RAB, in mentioned counters are included all the releases from Multi RAB to only PS RAB and to Idle state. This KPI can be calculated on RNC level, replacing in the formula ERL_SPEECH with RNC_ERL_SPEECH. In this case, all counters involved in the formula have to be aggregated on all the cells belonging to this RNC and on all Iur links from this RNC to neighboring RNCs, because the same counters have been defined on cell level and on Iur link level.

4.4.2 Average Holding Time AMR-NB

KPI Name AHT_AMRNB RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc, UtranCell Counters Type: PEG Target Value:


[ ]⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛ +

AmrNbRabReleasepmNoSystem

AmrNbRabReleasepmNoNormal

ERL_AMRNB/



KPI Description This formula gives the average time length (in minutes) the end user is utilizing an AMR-NB service. It can be seen also as the normalization of any kind of releases over the total time a user is occupying a channel. It is also a very useful indication of end user behavior in terms of service time and of the traffic load in the network. Actually it can be also used as traffic monitoring KPI. The ERL_AMRNB contribution represents all the traffic (in Erlangs) generated by the all the RABs AMR-NB in the measured time. This figure is calculated on Cell level with UeRc index related to AMR-NB RAB. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula.





The pmNoNormalRabReleaseAmrNb and pmNoSystemRabReleaseAmrNb counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB AMR-NB respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. These counters are defined for UtranCell class only, and are incremented for the best cell in the Active Set in the SRNC This KPI can be calculated on RNC level, replacing in the formula ERL_AMRNB with RNC_ERL_AMRNB. In this case, both counters involved in the formula have to be aggregated on all the cells belonging to this RNC.

4.4.3 Average Holding Time AMR-WB

KPI Name AHT_AMRWB RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc, UtranCell Counters Type: PEG Target Value:


[ ]⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛ +

AmrWbRabReleasepmNoSystem

AmrWbRabReleasepmNoNormal

ERL_AMRWB/



KPI Description This formula gives the average time length (in minutes) the end user is utilizing an AMR-NB service. It can be seen also as the normalization of any kind of releases over the total time a user is occupying a channel. It is also a very useful indication of end user behavior in terms of service time and of the traffic load in the network. Actually it can be also used as traffic monitoring KPI. The ERL_AMR-WB contribution represents all the traffic (in Erlangs) generated by





the all the RABs AMR-WB in the measured time. This figure is calculated on Cell level with UeRc index related to AMR-WB RAB. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. The pmNoNormalRabReleaseAmrWb and pmNoSystemRabReleaseAmrWb counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB AMR-WB respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. These counters are defined for UtranCell class only, and are incremented for the best cell in the Active Set in the SRNC This KPI can be calculated on RNC level, replacing in the formula ERL_AMRwB with RNC_ERL_AMRWB. In this case, both counters involved in the formula have to be aggregated on all the cells belonging to this RNC.

4.4.4 Average Holding Time CS57

KPI Name AHT_CS57 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc, UtranCell Counters Type: PEG Target Value:


[ ]⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛ +

CsStreamRabReleasepmNoSystem

CsStreamRabReleasepmNoNormal

EAM_DATA /ERL_CS_STR



KPI Description This formula gives the average time length (in minutes) the end user is utilizing Cs 57 Streaming Data service. It can be seen also as the normalization of any kind of releases over the total time a user is occupying a channel. It is also a very useful indication of end user behavior in terms of service time and of the traffic load in the





network. Actually it can be also used as traffic monitoring KPI. The ERL_CS_STREAM_DATA contribution represents all the traffic (in Erlangs) generated by the all the RABs CS57 in the measured time. This figure is calculated on Cell level with UeRc indexes related to CS57 RABs. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. The pmNoNormalRabReleaseCsStream and pmNoSystemRabReleaseCsStream counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for streaming 57.6 kbps call, respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. For UtranCell class, these counters are incremented for the best cell in the Active Set in the SRNC while, for IurLink class, they are incremented for the IurLink representing the DRNC for the best cell in the active set. This KPI can be calculated on RNC level, replacing in the formula ERL_CS_STREAM_DATA with RNC_ERL_CS_STREAM_DATA. In this case, all counters involved in the formula have to be aggregated on all the cells belonging to this RNC and on all Iur links from this RNC to neighboring RNCs, because the same counters have been defined on cell level and on Iur link level.

4.4.5 Average Holding Time CS64

KPI Name AHT_CS64 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc, UtranCell Counters Type: PEG Target Value:


[ ]⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛ +

4ReleaseCs6 RabpmNoSystem

4ReleaseCs6 RabpmNoNormal

TA / ERL_CS64DA


Units: Minutes





Note:

KPI Description This formula gives the average time length (in minutes) the end user is utilizing Cs Data service. It can be seen also as the normalization of any kind of releases over the total time a user is occupying a channel. It is also a very useful indication of end user behavior in terms of service time and of the traffic load in the network. Actually it can be also used as traffic monitoring KPI. The ERL_CS64DATA contribution represents all the traffic (in Erlangs) generated by the all the RABs CS64 in the measured time. This figure is calculated on Cell level with UeRc indexes related to CS64 RABs and to CS64+PS8 MultiRAB. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. The pmNoNormalRabReleaseCs64 and pmNoSystemRabReleaseCs64 counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for a conversational 64 kbps RAB, respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. For UtranCell class, these counters are incremented for the best cell in the Active Set in the SRNC while, for IurLink class, they are incremented for the IurLink representing the DRNC for the best cell in the active set. This KPI can be calculated on RNC basis, replacing in the formula ERL_CS64DATA with RNC_ERL_CS64DATA. In this case, before computing the KPI, all counters have to be aggregated on all the cells belonging to this RNC and on all Iur links from this RNC to neighboring RNCs, because the same counters have been defined on cell level and on Iur link level.

4.4.6 Average Holding Time PS Streaming

KPI Name AHT_PSSTREAMING RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc, UtranCell Counters Type: PEG Target Value:






[ ]⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛ +

amPacketStreRabReleasepmNoSystem

amPacketStreRabReleasepmNoNormal

/ TREAMERL_PS64_S



KPI Description This formula gives the average time length (in minutes) the end user is utilizing Ps Streaming 64 service. It can be seen also as the normalization of any kind of releases over the total time a user is occupying a channel. It is also a very useful indication of end user behavior in terms of service time and of the traffic load in the network. Actually it can be also used as traffic monitoring KPI. The ERL_PS64_STREAM contribution represents all the traffic (in Erlangs) generated by the all the RABs Ps Streaming 64 in the measured time. This figure is calculated on Cell level with UeRc indexes related to Ps Streaming 64. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. The pmNoNormalRabReleasePacketStream and pmNoSystemRabReleasePacketStream counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for a PS streaming 64 kbps RAB, respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. For UtranCell class, these counters are incremented for the best cell in the Active Set in the SRNC while, for IurLink class, they are incremented for the IurLink representing the DRNC for the best cell in the active set. This KPI can be also calculated on RNC basis, replacing ERL_PS64_STREAM with RNC_ERL_PS64_STREAM. In this case, before computing the KPI, bothcounters involved in the formula have to be aggregated on all the cells belonging to this RNC and on all Iur links from this RNC to neighboring RNCs, because the same counters have been defined on cell level and on Iur link level.

4.4.7 Average Holding Time PS Streaming 128

KPI Name AHT_PSSTREAMING128 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’





Time Resolution: 1 hour Counters MO Class: UeRc, UtranCell Counters Type: PEG Target Value:


[ ]⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛ +

am128PacketStreRabReleasepmNoSystem

am128PacketStreRabReleasepmNoNormal

/ STREAMERL_PS128_



KPI Description This formula gives the average time length (in minutes) the end user is utilizing Ps128 Streaming service. It can be seen also as the normalization of any kind of releases over the total time a user is occupying a channel. It is also a very useful indication of end user behavior in terms of service time and of the traffic load in the network. Actually it can be also used as traffic monitoring KPI. The ERL_PS128_STREAM contribution represents all the traffic (in Erlangs) generated by the all the RABs Ps Streaming 128 in the measured time. This figure is calculated on Cell level with UeRc indexes related to Ps Streaming 128. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. The pmNoNormalRabReleasePacketStream128 and pmNoSystemRabReleasePacketStream128 counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for a PS streaming 128 RAB, respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. For UtranCell class, these counters are incremented for the best cell in the Active Set in the SRNC while, for IurLink class, they are incremented for the IurLink representing the DRNC for the best cell in the active set. This KPI can be also calculated on RNC basis, replacing ERL_PS128_STREAM with RNC_ERL_PS128_STREAM. In this case, before computing the KPI, both counters involved in the formula have to be aggregated on all the cells belonging to this RNC and on all Iur links from this RNC to neighboring RNCs, because the same counters have been defined on cell level and on Iur link level.





4.4.8 Average Holding Time Ps Interactive

KPI Name AHT_PS RNC Sw Release: P5 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc, UtranCell Counters Type: PEG Target Value:


[ ]

⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜

⎝

⎛

+

+

aSuccFachUrpmChSwitch


-PacketRabReleasepmNoSystem

PacketUraRabReleasepmNoNormal


/ ERL_PSDATA


Units: Minutes Note: In P5, new UeRc types are counted in the

RNC_ERL_PSDATA formula: CS 12.2 + 64/HS (UeRc=19), CS 12.2 + 384/HS (UeRc=20), EUL/HS (UeRc=25)

KPI Description

This formula gives the average time length (in minutes) the end user is utilizing Ps Data service. It can be seen also as the normalization of any kind of releases over the total time a user is occupying a channel. It is also a very useful indication of end user behavior in terms of service time and of the traffic load in the network. Actually it can be also used as traffic monitoring KPI. The ERL_PSDATA contribution represents all the traffic (in Erlangs) generated by the all the RABs Ps Interactive, on cell basis, in the measured time. This figure is calculated on RNC level with UeRc indexes related to Ps Interactive FACH, 64/64, 64/128, 64/384, 64/HS, 384/HS, CS 12.2 + PS 64 MultiRAB, CS 12.2 + 64/HS MultiRAB, CS 12.2 + 384/HS MultiRAB, EUL/HS. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. The pmNoNormalRabReleasePacket and pmNoSystemRabReleasePacket counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for all PS RABs respectively with “release cause” =





’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. For UtranCell class, these counters are incremented for the best cell in the Active Set in the SRNC while, for IurLink class, they are incremented for the IurLink representing the DRNC for the best cell in the active set. When releasing a HS RAB, this counter is stepped for the Serving HS-DCH cell. Note that, in case of Multi RAB, in mentioned counters are included also the releases from Multi RAB to only Speech RAB. The pmNoSystemRabReleasePacketUra counter is stepped for Packet RABs on URA state, due to the same reason as for stepping pmNoSystemRabReleasePacket and it is not defined for IurLink class. The pmNoNormalRabReleasePacketUra counter is stepped for Packet RABs on URA state, due to the same reason as for stepping pmNoNormalRabReleasePacket and it is not defined for IurLink class. The pmChSwithSuccFachUra counter represents the number of successful channel downswitching attempts from CELL_FACH to URA_PCH. This counter is increased for every successful channel downswitching attempt from CELL_FACH to URA_PCH. This KPI can be calculated also on RNC level, replacing in the formula ERL_PSDATA with RNC_ERL_PSDATA. In this case, before computing the KPI, the pmNoSystemRabReleasePacket and pmNoNormalRabReleasePacket counters have to be aggregated on all the cells belonging to this RNC and on all Iur links from this RNC to neighboring RNCs, because the same counters have been defined on cell level and on Iur link level. The pmNoNormalRabReleasePacketUra and pmNosystemRabReleasePacketUra counters are only to be aggregated on all the cells belonging to the RNC since they are not defined for IurLink class.

4.4.9 Average Holding Time PS Interactive DCH/FACH

KPI Name AHT_PS_NON_HS RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc, UtranCell Counters Type: PEG Target Value:






[ ]

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+

−

+

schSuccessHpmDlUpswit





-PacketUraRabReleasepmNoNormal


/ A_DCHFACHERL_PS_DAT



KPI Description This formula gives the average time length (in minutes) the end user is utilizing Ps DCH/FACH Data service. It can be seen also as the normalization of any kind of releases over the total time a user is occupying a channel. It is also a very useful indication of end user behavior in terms of service time and of the traffic load in the network. Actually it can be also used as traffic monitoring KPI. The ERL_PSDATA_DCHFACH contribution represents all the traffic (in Erlangs) generated by the all the RABs Ps Interactive DCH/FACH in the measured time. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. The pmNoSystemRabReleasePacket counter is only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RABs PS Interactive respectively with “release cause” = anything except ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For UtranCell class, this counter is incremented for the best cell in the Active Set in the SRNC. For IurLink class, it is incremented for the IurLink representing the DRNC for the best cell in the active set. The pmNoSystemRbReleaseHs counter is stepped for the Serving HS-DSCH cell at RAB/RB combination transition from PS Interactive 64/HS (or 384/HS or EUL/HS) - HS-DSCH to SRB-DCH or to Idle mode due to the same reasons as for stepping the existing counter pmNoSystemRabReleasePacket. For UtranCell class, this counter is stepped for the Serving HS-DSCH cell. The same counter have not been released on Iur link level. In P5 Inter RNC mobility is supported through reconfiguration to R99 RAB if the network setting allows to do that (hsToDchTrigger.servHsChangeInterRnc=True). The pmNoSystemRabReleasePacketUra counter is stepped for Packet RABs on URA state, due to the same reason as for stepping pmNoSystemRabReleasePacket and it is not defined for IurLink class. Note that, in case of Multi RAB, are included all the releases from Multi RAB to only CS RAB and to Idle state. The pmNoNormalRabReleasePacket counter is only increased due to a RANAP Iu Release Command or RAB Assignment Request message for all PS RABs respectively with “release cause” = ’Normal Release’, ’Successful Relocation’,





’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ For UtranCell class, this counter are incremented for the best cell in the Active Set in the SRNC while, for IurLink class, it is incremented for the IurLink representing the DRNC for the best cell in the active set. When releasing a HS RAB, this counter is stepped for the Serving HS-DCH cell. Note that, in case of Multi RAB, in mentioned counters are included also the releases from Multi RAB to only Speech RAB. The pmNoNormalRbReleaseHs counter is only increased, at RAB/RB combination transition from PS Interactive 64/HS - HS-DSCH to SRB-DCH or to Idle mode, due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. The pmNoNormalRabReleasePacketUra counter is stepped for Packet RABs on URA state, due to the same reason as for stepping pmNoNormalRabReleasePacket and it is not defined for IurLink class. The pmDlUpswitchSuccessHs counter provides the number of successful DL upswitches to any HS state. The counter is stepped for successful DL upswitch to a RB combination containing HS. The counter is only incremented in all cells of the active set. This KPI can be calculated also on RNC level, replacing in the formula ERL_PSDATA_DCHFACH with RNC_ERL_PSDATA_DCHFACH. In this case, before computing the KPI, the pmNoSystemRabReleasePacket and pmNoNormalRabReleasePacket counters have to be aggregated on all the cells belonging to this RNC and on all Iur links from this RNC to neighboring RNCs, because the same counters have been defined on cell level and on Iur link level. The pmNoNormalRbReleaseHs, pmNosystemlRbReleaseHs, pmNoNormalRabReleasePacketUra and pmNosystemRabReleasePacketUra counters are only to be aggregated on all the cells belonging to the RNC since they are not defined for IurLink class.

4.4.10 Average Holding Time PS Interactive HS

KPI Name AHT_HS RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc, UtranCell Counters Type: PEG Target Value:






[ ]⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛ +



/ ERL_HS



KPI Description This formula gives the average time length (in minutes) the end user is utilizing Ps Data service. It can be seen also as the normalization of any kind of releases over the total time a user is occupying a channel. It is also a very useful indication of end user behavior in terms of service time and of the traffic load in the network. Actually it can be also used as traffic monitoring KPI. The ERL_HS contribution represents all the traffic (in Erlangs) generated by the all the RABs HS Ps Interactive in the measured time. This figure is calculated on Cell level with UeRc indexes related to Ps 64/HS, 384/HS, CS 12.2 + PS 64/HS MultiRAB, CS 122 + 384/HS MultiRAB, EUL/HS. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. The pmNoNormalRbReleaseHs and pmNoSystemRbReleaseHs counters are only increased, at RAB/RB combination transition from PS Interactive 64/HS - HS-DSCH to SRB-DCH or to Idle mode, due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. The counters are stepped for the Serving HS-DSCH cell. This KPI can be calculated on RNC level, replacing ERL_HS with RNC_ERL_HS. In this case, the pmNoNormalRbReleaseHs and pmNosystemlRbReleaseHs counters have to be aggregated only on all the cells belonging to this RNC since they are not defined for IurLink class.

4.4.11 Average Holding Time PS Streaming HS

KPI Name AHT_PSSTR_HS RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc, UtranCell







[ ]⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛ +

PsStreamHsRabReleasepmNoSystem

PsStreamHsRabReleasepmNoNormal

/ HSERL_PSSTR_



KPI Description This formula gives the average time length (in minutes) the end user is utilizing Ps Data service. It can be seen also as the normalization of any kind of releases over the total time a user is occupying a channel. It is also a very useful indication of end user behavior in terms of service time and of the traffic load in the network. Actually it can be also used as traffic monitoring KPI. The ERL_PSSTR_HS contribution represents all the traffic (in Erlangs) generated by the all the RABs Ps Streaming HS in the measured time. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. The pmNoNormalRabReleasePsStreamHs and pmNoSystemRabReleasePsStreamHs counters are only increased, at RAB/RB combination transition from PS Streaming HS HS-DSCH to SRB-DCH or to Idle mode, due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. The counters are stepped for the Serving HS-DSCH cell. This KPI can be calculated on RNC level, replacing ERL_HS with RNC_ERL_HS. In this case, the pmNoNormalRbReleaseHs and pmNosystemlRbReleaseHs counters have to be aggregated only on all the cells belonging to this RNC since they are not defined for IurLink class.

4.4.12 Average Holding Time PS EUL

KPI Name AHT_EUL RNC Sw Release: P6 Importance: Medium





Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc, UtranCell Counters Type: PEG Target Value:


[ ]⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛ +

ulRbReleaseEpmNoNormal

ulRbReleaseEpmNoSystem

/ ERL_EUL



KPI Description This formula gives the average time length (in minutes) the end user is utilizing EUL/HS RAB. It is a very useful indication of end user behavior in terms of service time and of the traffic load in the network. Actually it can be also used as traffic monitoring KPI. The ERL_EUL contribution represents all the traffic (in Erlangs) generated by the EUL/HS RAB in the measured time. This figure is calculated on RNC level with UeRc indexes related to EUL/HS RAB. Please refer to relative section in the chapter dedicated to Capacity for a deeper description of the KPI and all the counters involved in the formula. The pmNoSystemRbReleaseEul counter is the number of system initiated RAB releases for PS Interactive RAB mapped on E-DCH/ HSDPA. It is stepped for the Serving E-DCH cell for release of RAB/RB combination PS Interactive E-DCH/HS - HS-DSCH due to: RANAP Iu Release Command or RAB Assignment Request message with "release cause" = anything except 'Normal Release', 'Successful Relocation', 'Resource Optimisation Relocation', 'User Inactivity' or 'release-due-to-UE-generated- signalling-connection-release'. This counter is incremented for the Serving EUL/HS-DCH cell. This KPI can be calculated on RNC level, replacing ERL_EUL with RNC_ERL_EUL. In this case, all counters have to be aggregated on all the cells belonging to this RNC, before computing KPI.





4.5 RAB Speech Drop Causes

4.5.1 Drop due to Soft Handover Action

KPI Name DROPRATE_SOHO_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛


SpeechSoHopmNoSysRel*100

Units: % Note:

KPI Description The formula highlights the percentage of dropped Speech call due to Soft Handover action. It is calculated as the rate between the number of system disconnects of a speech call for this reason over the total number of releases. Network initiated call release of speech calls due to inability to include a non-valid or valid cell in the active set. The pmNoSysRelSpeechSoHo counter shall be incremented for the best cell in the active set prior to the call release. This counter is only incremented in the SRNC. The pmNoSystemRabReleaseSpeech counter is increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech with “release cause” other than: ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For UtranCell class, these counters are incremented for the best cell in the Active Set in the SRNC. Note that, in case of Multi RAB, in mentioned counters are included all the releases from Multi RAB to only PS RAB and to Idle state. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





4.5.2 Drop due to Missing Neighbour

KPI Name DROPRATE_MISSRELATION_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛


hbrSpeechNeigpmNoSysRel*100

Units: % Note:

KPI Description The formula highlights the percentage of dropped Speech call due to unknown measured cell (missing neighbour relation). It is calculated as the rate between the number of system disconnects of a speech call for this reason over the total number of releases. Network initiated call release of speech calls due to inability, for the mentioned reason, to include a non-valid or valid cell in the active set. The pmNoSysRelSpeechNeighbr counter shall be incremented for the best cell in the active set prior to the call release. This counter is only incremented in the SRNC. The pmNoSystemRabReleaseSpeech counter is increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech with “release cause” other than: ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For UtranCell class, these counters are incremented for the best cell in the Active Set in the SRNC. Note that, in case of Multi RAB, in mentioned counters are included all the releases from Multi RAB to only PS RAB and to Idle state. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





4.5.3 Drop due to UL Synchronization Lost

KPI Name DROPRATE_OUTOFSYNC_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛


nchSpeechUlSypmNoSysRel*100

Units: % Note:

KPI Description The formula highlights the percentage of dropped Speech call due to UL Synchronization Lost. It is calculated as the rate between the number of system disconnects of a speech call for this reason over the total number of releases. The pmNoSysRelSpeechULSynch counter is incremented if the timer dchRcLostT expires and the RAB type is a CS Conversational Speech 12.2 kbps RAB. This counter is only incremented in the SRNC. The pmNoSystemRabReleaseSpeech counter is increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech with “release cause” other than: ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For UtranCell class, these counters are incremented for the best cell in the Active Set in the SRNC. Note that, in case of Multi RAB, in mentioned counters are included all the releases from Multi RAB to only PS RAB and to Idle state. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





4.5.4 Drop due to Congestion

KPI Name DROPRATE_CONGESTION_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛


SpeechCongpmNoOfTerm*100

Units: % Note:

KPI Description The formula highlights the percentage of dropped Speech call due to Congestion. It is calculated as the rate between the number of system disconnects for speech call with this reason over the total number of releases. The pmNoOfTermSpeechCong counter is increased when a UE using the speech service is released due to cell congestion. The counter is increased in CRNC for non-drifting UEs for the one cell with congestion. The pmNoSystemRabReleaseSpeech counters is increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech with “release cause” other than: ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’. For UtranCell class, these counters are incremented for the best cell in the Active Set in the SRNC. Note that, in case of Multi RAB, in mentioned counters are included all the releases from Multi RAB to only PS RAB and to Idle state. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





4.5.5 Drop due to IRAT Handover Lost

KPI Name DROPRATE_IRATHO_SPEECH RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell, GsmRelation Counters Type: PEG Target Value:


( )SpeechRabReleasepmNoSystem/

tionechUeRejectIratHoSpepmNoFailOu

- ChFailldChNotPhyechReturnOtIratHoSpepmNoFailOu

- ailldChPhyChFechReturnOtIratHoSpepmNoFailOu

-Speech sOutIratHopmNoSucces

-ch IratHoSpeepmNoAttOut

*100

⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜

⎝

⎛

Units: % Note:

KPI Description The formula highlights the percentage of dropped Speech call due to IRAT Handover Lost. It is calculated as the rate between the IRAT HO failures leading to drop over the total number of releases. The pmNoAttOutIratHoSpeech and pmNoSuccessOutIratHoSpeech counters define respectively the number of attempted and successful outgoing (to GSM) inter-RAT handover. The first one is increased when RNC is received HANDOVER FROM UTRAN COMMAND while the second one when IU RELEASE COMMAND is received with cause ’Normal release’ or ’Successful relocation’. The pmNoFailOutIratHoSpeechReturnOldChPhyChFail, pmNoFailOutIratHoSpeechUeRejection and pmNoFailOutIratHoSpeechReturnOldChNotPhyChFail counters define the number of failed outgoing (to GSM) inter-RAT handover. The trigger is when "HANDOVER FROM UTRAN FAILURE" is received with inter-RAT handover failure cause= “Physical channel failure” for the first one, “Configuration unacceptable” for the second one or any other cause than “Physical channel failure” or “Configuration unacceptable” for the third one. All these counters will only be incremented for ’Conversational speech RAB’ for the best cell in the active set and in the SRNC.





Note that in this ratio, all contributions are increased on GsmRelation level. Therefore the KPI has to be aggregated first for all GSM relations defined for the same cell. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





5 Integrity

5.1 BLER

5.1.1 RABs UL BLER

KPI Name: UL_BLER_ RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


i]l[UeRctBlocksAcUpmTranspori]RccksAcUl[UeansportBlopmFaultyTr

*100=

=

Units: % Note: Calculate for every RABs associated to UeRc index

(i = 1… 78). UeRc count increased from 39 in P5 to 78 in P6

KPI Description The KPI defines the percentage of faulty UL transport blocks over the total of the valid received ones. This is not an absolute indicator of Channel Quality because these figures should match blerQualityTargetUl parameter values set in advance for each RAB in the RNC. If there is an inconsistency between counter values and parameter settings, this is an indication that Power Control algorithm is not working properly. After Macrodiversity Combining the number of faulty and received transport blocks are counted per Radio Connection Configuration for UL DCHs. Counting is based on the Cyclic Redundancy Check Indicator (CRCI) information. The pmFaultyTransportBlocksAcUl and pmTransportBlocksAcUl counters are respectively increased for each faulty and received UL data frame. This KPI can be computed only on RNC level since the counters involved in the formula are collected on a UeRc index basis, for each RABs. Please refer to the Appendix for UeRc index tables.





5.1.2 DCH BLER

KPI Name: BLER_DCH_CELL RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

ltBlocksBcUpmTranspor

cksBcUlansportBlopmFaultyTr*100

Units: % Note:

KPI Description The KPI defines the percentage of faulty UL transport blocks on DCH channel over the total of the valid received ones. Before Macrodiversity Combining the number of incorrect and valid transport blocks is counted for UL DCHs for each cell. Counting is based on the Cyclic Redundancy Check Indicator (CRCI) information. The pmFaultyTransportBlocksBcUl and pmTransportBlocksBcUl counters are respectively increased for each faulty and valid data frame. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

5.1.3 RACH BLER

KPI Name: BLER_RACH_CELL RNC Sw Release: P6 Importance: High Scope: Cell, RNC





Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Rach Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

tBlockspmTranspor

cksansportBlopmFaultyTr*100

Units: % Note:

KPI Description The KPI defines the percentage of faulty UL transport blocks on RACH channel over the total of the received ones. The pmFaultyTransportBlocks and pmTransportBlocks counters are respectively increased when faulty and successful RACH transport block detected at reception in the RNC. All the contributions from all active UEs using that particular RACH channel are counted. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

5.1.4 EUL MAC-es PDU Delivery Failure Rate

KPI Name: EUL_MACes_DEV_FR RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






( )

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

++

++

delivSrbPduTti10UnpmEulMaceseractivedelivPsIntPduTti10UnpmEulMaces

livSrbPduTti10DepmEulMacesactivelivPsInterPduTti10DepmEulMaces

delivSrbPduTti10UnpmEulMaceseractivedelivPsIntPduTti10UnpmEulMaces*100

Units: % Note:

KPI Description The multiple HARQ processes used for EUL transmission cannot in themselves ensure in-sequence delivery, as there is no interaction between the processes. In soft handover situations data is received independently in several RBSs and can therefore be received in the SRNC in a different order than transmitted. In addition, differences in Iub transport delay can cause out-of-sequence delivery to RLC. Hence, in-sequence delivery must be implemented on top of the MAC-e entity. The MAC-es entity in the SRNC has been defined to perform the following tasks: • Reordering • Duplicate removal • Macro diversity combining The proposed KPI evaluates the probability that the MAC-es layer (in RNC) cannot correctly handle MAC-es PDUs - both PS data and signalling - due to delays/problems in transmission. The counter pmEulMacesPduTti10UndelivPsInteractive represents the number of MAC-es PDUs which are undeliverable by MAC-es re-ordering entity to the disassembly entity. Undeliverable MAC-es PDUs are those that have not been received at expiry of a timer (t1eTimerUlTti10) and have a TSN (Transmission Sequence Number) smaller than the TSN that triggered the timer. The data shall be associated with the serving EUL cell. The counter pmEulMacesPduTti10DelivPsInteractive gives the number of MAC-es PDUs - corresponding to the PS interactive RB - which are delivered to the disassembly entity in MAC-es. It is pegged when the re-ordering entity delivers a MAC-es PDU carrying PS interactive data to MAC-d. The data shall be associated with the serving EUL cell. The counter pmEulMacesPduTti10UndelivSrb is the number of MAC-es PDUs, corresponding to the SRBs, which are undeliverable by MAC-es re-ordering. Undeliverable MAC-es PDUs are those that have not been received at expiry of a timer (t1eTimerUlTti10) and have a TSN (Transmission Sequence Number) smaller than the TSN that triggered the timer. The data shall be associated with the serving EUL cell. The counter pmEulMacesPduTti10DelivSrb is the number of MAC-es PDUs - corresponding to the SRBs - which are delivered to the disassembly entity in MAC-





es. It is pegged when the re-ordering entity delivers a MAC-es PDU carrying SRB data to MAC-d. The data shall be associated with the serving EUL cell.

5.1.5 EUL HARQ Retransmission Rate PS Data

KPI Name: EUL_HARQ_RETRAN_RATE_DATA RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PDF Target Value:


[ ][ ][ ]

[ ]⎟⎠

⎞⎜⎝

⎛

⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛+

+

∑=

=

4

1iivePsInteractransmTti10pmEulHarqT

4ivePsInteractransmTti10pmEulHarqT*33ivePsInteractransmTti10pmEulHarqT*2

2ivePsInteractransmTti10pmEulHarqT

i

i

Units: Note:

KPI Description The counter pmEulHarqTransmTti10PsInteractive is the number of HARQ transmissions attempted for the PS interactive RB when TTI = 10 ms. If the signalled number of HARQ retransmissions is 13, 14 or 15, the PDF counter shall not be incremented. The data shall be associated with the serving EUL cell. [1]: =1, [2]: =2, [3]: =3, [4]: >=4 The formula measures the retransmission rate of the PS Data carried over E-DCH. It can be used to evaluate possible limitation in the EUL data rate caused by too many retransmissions attempted over the air interface.





5.1.6 EUL HARQ Retransmission Rate SRB

KPI Name: EUL_HARQ_RETRAN_RATE_SRB RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PDF Target Value:


[ ][ ][ ]

[ ]⎟⎠

⎞⎜⎝

⎛

⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛+

+

∑=

=

4

1iSrbransmTti10pmEulHarqT

4SrbransmTti10pmEulHarqT*33SrbransmTti10pmEulHarqT*2

2SrbransmTti10pmEulHarqT

i

i

Units: Note:

KPI Description The counter pmEulHarqTransmTti10Srb is the number of HARQ transmissions attempted for the SRBs when TTI = 10 ms. If the signalled number of HARQ retransmissions is 13, 14 or 15, the PDF counter shall not be incremented. The data shall be associated with the serving EUL cell. [1]: =1, [2]: =2, [3]: =3, [4]: >=4 The formula measures the retransmission rate of the SRB carried over E-DCH. It can be used to evaluate possible problems over the air interface causing too many retransmissions between UE and RBS.





5.2 Packet Latency, Delay and Jitter

5.2.1 PS Interactive Latency

KPI Name: PS_INT_LATENCY RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PDF Target Value:


y[i]cketLatencpmSamplePa]tLatency[ipmSumPacke

Units: ms Note: New counters introduced in P6

KPI Description

The KPI measure the PS Interactive latency with respect to the Best Cell

Counter pmSumPacketLatency[i] sums all sample values recorded during a ROP for RAN SDU PS interactive packet latency with respect to the best cell. Incremented by the SDU latency for each SDU. Aggregation according to the following SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

Counter pmSamplePacketLatency[i] is number of samples recorded within the ROP period for pmSumPacketLatency. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x





5.2.2 R99 PS Interactive Latency

KPI Name: R99_PS_INT_LATENCY RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PDF Target Value:


y[i]hDchLatencpmSampleDc]hLatency[ipmSumDchDc


KPI Description

The KPI measure the R99 PS Interactive with DCH on both uplink and downlink latency with respect to the Best Cell

Counter pmSumDchDchLatency[i] sums all sample values recorded during a ROP for RAN SDU latency for PS Interactive with R99 DCH on both uplink and downlink with respect to the best cell. Incremented by the SDU latency for each SDU. Aggregation according to the following SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

Counter pmSampleDchDchLatency[i] is number of samples recorded within the ROP period for pmSumDchDchLatency. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x





5.2.3 HS PS Interactive Latency

KPI Name: HS_PS_INT_LATENCY RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PDF Target Value:


[i]DchLatencypmSampleHsLatency[i]pmSumHsDch


KPI Description

The KPI measure the PS Interactive with HS-DSCH on downlink and R99 DCH on uplink latency with respect to the Best Cell

Counter pmSumDchDchLatency[i] sums all sample values recorded during a ROP for RAN SDU latency for PS Interactive with HS-DSCH on downlink and R99 DCH on uplink with respect to the best cell. Incremented by the SDU latency for each SDU. Aggregation according to the following SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

Counter pmSampleHsDchLatency[i] is number of samples recorded within the ROP period for pmSumHsDchLatency. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x





5.2.4 HS PS Streaming Latency

KPI Name: HS_PS_STR_LATENCY RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PDF Target Value:


s[i]yOsStreamHcketLatencpmSamplePa]StreamHs[itLatencyPspmSumPacke


KPI Description

The KPI measure the RAN SDU PS Streaming HS packet latency with respect to the Best Cell

Counter pmSumPacketLatencyPsStreamHs [i] sums all sample values recorded during a ROP for RAN SDU PS Streaming HS packet latency with respect to the best cell. Incremented by the SDU latency for each SDU. Aggregation according to the following SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

Counter pmSamplePacketLatencyPsStreamHs[i] is number of samples recorded within the ROP period for pmSumPacketLatencyPsStreamHs. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x





5.2.5 HS EUL PS Interactive Latency

KPI Name: HS_EUL_PS_INT_LATENCY RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PDF Target Value:


[i]EulLatencypmSampleHsLatency[i]pmSumHsEul


KPI Description

The KPI measure the PS Interactive with HS-DSCH on downlink and EUL on uplink with respect to the Best Cell

Counter pmSumDchDchLatency[i] sums all sample values recorded during a ROP for RAN SDU latency for PS Interactive with HS-DSCH on downlink and EUL on uplink with respect to the best cell. Incremented by the SDU latency for each SDU. Aggregation according to the following SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

Counter pmSampleHsEulLatency[i] is number of samples recorded within the ROP period for pmSumHsEulLatency. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

5.2.6 PS Interactive Delay





KPI Name: PS_INT_DELAY RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PDF Target Value:


y[i]cketDlDelapmSamplePa]tDlDelay[ipmSumPacke


KPI Description

The KPI measure the PS Interactive delay with respect to the Best Cell

Counter pmSumPacketDlDelay[i] sums all sample values recorded during a ROP for RAN SDU PS interactive packet delay with respect to the best cell. Incremented by the SDU delay for each SDU. Aggregation according to the following SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

Counter pmSamplePacketDlDelay[i] is number of samples recorded within the ROP period for pmSumPacketDlDelay. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

5.2.7 R99 PS Interactive Delay DL

KPI Name: R99_PS_INT_DELAY_DL RNC Sw Release: P6 Importance: High Scope: RNC





Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PDF Target Value:


]hDlDelay[ipmSampleDcDelay[i]pmSumDchDl

Units: Ms Note: New counters introduced in P6

KPI Description

The KPI measure the R99 PS Interactive with DCH on downlink delay with respect to the Best Cell

Counter pmSumDchDlDelay[i] sums all sample values recorded during a ROP for RAN SDU delay for PS Interactive with R99 DCH on downlink with respect to the best cell. Incremented by the SDU delay for each SDU. Aggregation according to the following SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

Counter pmSampleDchDlDelay[i] is number of samples recorded within the ROP period for pmSumDchDlDelay. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

5.2.8 HS PS Interactive Delay DL

KPI Name: HS_PS_INT_LATENCY_DL RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction





Counters Type: PDF Target Value:


DlDelay[i]pmSampleHselay[i]pmSumHsDlD


KPI Description

The KPI measure the RAN SDU delay for HS-DSCH on downlink with respect to the Best Cell

Counter pmSumDchDchLatency[i] sums all sample values recorded during a ROP for RAN SDU delay for HS-DSCH on downlink with respect to the best cell. Incremented by the SDU delay for each SDU. Aggregation according to the following SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

Counter pmSampleHsDlDelay[i] is number of samples recorded within the ROP period for pmSumHsDlDelay. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

5.2.9 HS EUL PS Interactive Delay

KPI Name: HS_EUL_PS_INT_DELAY RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PDF Target Value:






lay[i]EulDlRcvDepmSampleHs[i]DlRcvDelaypmSumHsEul


KPI Description

The KPI measure the RAN SDU receive delay for PS Interactive with HS-DSCH on downlink and EUL on uplink with respect to the Best Cell

Counter pmSumHsEulDlRcvDelay[i] sums all sample values recorded during a ROP for RAN SDU receive delay for PS Interactive with HS-DSCH on downlink and EUL on uplink with respect to the best cell. Incremented by the SDU delay for each SDU. Aggregation according to the following SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

Counter pmSampleHsEulDlRcvDelay[i] is number of samples recorded within the ROP period for pmSumHsEulDlRcvDeley. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

5.2.10 R99 PS Interactive Delay DL/UL

KPI Name: R99_PS_INT_DELAY_DLUL RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PDF Target Value:






elay[i]hDchDlRcvDpmSampleDcy[i]hDlRcvDelapmSumDchDc


KPI Description

The KPI define RAN SDU receive delay for PS Interactive with R99 DCH on both downlink and uplink. with respect to the Best Cell

Counter pmSumDchDchDlRcvDelay[i] sums all sample values recorded during a ROP for RAN SDU receive delay for PS Interactive with R99 DCH on both downlink and uplink with respect to the best cell. Incremented by the SDU received delay for each SDU. Aggregation according to the following SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

Counter pmSampleDchDchDlRcvDelay[i] is number of samples recorded within the ROP period for pmSumDchDchDlRcvDelay. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

5.2.11 HS PS Interactive Delay UL

KPI Name: HS_PS_INT_DELAY_UL RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PDF Target Value:


lay[i]DchDlRcvDepmSampleHs[i]DlRcvDelaypmSumHsDch






KPI Description

The KPI measure the RAN SDU receive delay for PS Interactive with HS-DSCH on downlink and R99 DCH on uplink with respect to the Best Cell

Counter pmSumHsDchDlRcvDelay[i] sums all sample values recorded during a ROP for RAN SDU receive delay for PS Interactive with HS-DSCH on downlink and R99 DCH on uplink with respect to the best cell. Incremented by the SDU receive delay for each SDU. Aggregation according to the following SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

Counter pmSampleHsDchDlRcvDelay[i] is number of samples recorded within the ROP period for pmSumHsDchDlRcvDelay. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

[0] : 0 <= x < 100 (bytes) [1] : 100 <= x < 1000 [2] : 1000 <= x

5.2.12 R99 PS Interactive Jitter

KPI Name: R99_PS_INT_JIT RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: TrigACC, TrigSCAN Target Value:


hDchJitterpmSampleDchJitterpmSumDchDc

Units: ms





Note: New counters introduced in P6

KPI Description

The KPI measure the RAN SDU jitter for PS Interactive with R99 DCH on both uplink and downlink with respect to the Best Cell

Counter pmSumDchDchJitter sums all sample values recorded during a ROP for RAN SDU jitter for PS Interactive with R99 DCH on both uplink and downlink with respect to the best cell. Values are read periodically from an internal level counter and added to this counter. The level counter maintains the current RAN SDU jitter for PS Interactive with R99 DCH on both uplink and downlink.

Counter pmSampleDchDchJitter is number of samples recorded within the ROP period for pmSumDchDchJitter. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

5.2.13 HS PS Interactive Jitter

KPI Name: HS_PS_INT_JIT RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: TrigACC, TrigSCAN Target Value:


DchJitterpmSampleHsJitterpmSumHsDch


KPI Description

The KPI measure the RAN SDU jitter for PS Interactive with HS-DSCH on downlink and R99 DCH on uplink with respect to the Best Cell

Counter pmSumHsDchJitter sums all sample values recorded during a ROP for RAN SDU jitter for PS Interactive with HS-DSCH on downlink and R99 DCH on uplink with respect to the best cell. Values are read periodically from an internal





level counter and added to this counter. The level counter maintains the current RAN SDU jitter for PS Interactive with HS-DSCH on downlink and R99 DCH on uplink.

Counter pmSampleHsDchJitter is number of samples recorded within the ROP period for pmSumHsDchJitter. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:

5.2.14 HS EUL Interactive Jitter

KPI Name: HS_EUL_INT_JIT RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: TrigACC, TrigSCAN Target Value:


EulJitterpmSampleHsJitterpmSumHsEul


KPI Description

The KPI measure the RAN SDU jitter for PS Interactive with HS-DSCH on downlink and EUL on uplink with respect to the Best Cell

Counter pmSumHsEulJitter sums all sample values recorded during a ROP for RAN SDU jitter for PS Interactive with HS-DSCH on downlink and EUL on uplink with respect to the best cell. Values are read periodically from an internal level counter and added to this counter. The level counter maintains the current RAN SDU jitter for PS Interactive with HS-DSCH on downlink and EUL on uplink.

Counter pmSampleHsEulJitter is number of samples recorded within the ROP period for pmSumHsEulJitter. Incremented by one when the corresponding sum counter is incremented. Number of samples according to the respective SDU sizes:





6 Channel Switching

6.1 Channel Switching FACH-IDLE

6.1.1 Channel Switching FACH-IDLE Count

KPI Name: SWITCH_FACHIDLE_COUNT RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


FachIdlepmChSwitch

Units: % Note:

KPI Description This KPI evaluates number of attempted throughput-based channel switches from common channel (Cell_FACH) to idle (connection release).

The counter pmChSwitchFachIdle is incremented by one when a RANAP Iu Release Command or RAB Assignment Request message with Release cause 'User Inactivity' is received. The counter is incremented in the SRNC where the UE is located. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





6.2 Channel Switching Failure Rate

6.2.1 Channel Upswitch Failure Rate FACH-HS

KPI Name: USWITCH_FAILRATE_FACHHS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛−

mptFachHsAttepmUpswitchessFachHsSuccpmUpswitch1*100

Units: % Note:

KPI Description This KPI evaluates the probability that the transitions in UL between FACH and HSDPA fail due to admission control reject or failures during the channel switching procedure. The counter pmUpswitchFachHsAttempt is stepped for attempts to upswitch from CELL_FACH to a RB combination containing HS and is incremented in all cells of the active set. The counter pmUpswitchFachHsSuccess is stepped for successful upswitches from CELL_FACH to a RB combination containing HS. It is incremented in all cells of the active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

6.2.2 Channel Switch Failure Rate FACH-URA

KPI Name: SWITCH_FAILRATE_FACHURA RNC Sw Release: P6 Importance: Medium







⎟⎟⎠

⎞⎜⎜⎝

⎛−

hUraAttemptFacpmChSwitchaSuccFachUrpmChSwitch1*100

Units: % Note:

KPI Description This KPI evaluates the probability that the Downswitching transitions from FACH to URA state fail due to any reason. The counter pmChSwitchSuccFachUra provides the number of successful channel downswitching attempts from CELL_FACH to URA_PCH. This counter is increased for every successful channel downswitching attempt from CELL_FACH to URA_PCH. Note: This counter is only incremented in the SRNC. The counter pmChSwitchAttemptFachUra provides the number of channel downswitching attempts from CELL_FACH to URA_PCH. This counter is increased for every channel downswitching attempt from CELL_FACH to URA_PCH. Note: This counter is only incremented in the Serving Network Controller (SRNC). This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

6.2.3 Channel Switch Failure Rate URA-FACH

KPI Name: SWITCH_FAILRATE_URAFACH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell







⎟⎟⎠

⎞⎜⎜⎝

⎛−

FachAttemptUrapmChSwitchhSuccUraFacpmChSwitch1*100

Units: % Note:

KPI Description This KPI evaluates the probability that the transitions from URA to Cell_FACH state fail due to any reason. The pmChSwitchSuccUraFach provides the number of transitions succeeded from URA_PCH to Cell_FACH. This counter is increased for successful transition from URA_PCH to Cell_FACH. Note: This counter is only incremented in the SRNC. The counter pmChSwitchAttemptUraFach provides the number of transitions attempted from URA_PCH to Cell_FACH. This counter is increased for every transition attempted from URA_PCH to Cell_FACH. Note: This counter is only incremented in the Serving Network Controller (SRNC). This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

6.2.4 Channel Upswitch Failure Rate DL Low Rate

KPI Name: USWITCH_FAILRATE_DL_LOW RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛−

owchAttemptLpmDlUpswitowchSuccessLpmDlUpswit1*100





Units: % Note: Counters pmDlUpSwitchSuccessLow and

pmDlUpSwitchAttemptLow stepped in Best AS cell.

KPI Description This KPI evaluates the probability that the transitions in DL between FACH and CELL_DCH with DL rate up to 64 kbps fail due to admission control reject or failures during the channel switching procedure. The counter pmDlUpswitchAttemptLow is the number of attempted upswitches of DL rate from CELL_FACH to DL bit-rates less than or equal to 64 kbps. It is stepped for each SRNC cell in the AS in which admission is requested at DL up-switch of interactive PS RABs to bit-rates less than or equal to 64 kbps. The counter pmDlUpswitchSuccessLow is the number of successful DL upswitches of DL rate from CELL_FACH to DL bit-rates less than or equal to 64 kbps. It is stepped in each SRNC cell in the AS on reception of an RRC Radio Bearer Reconfiguration Complete message following DL up-switch of an Interactive PS RAB to bit-rates less than or equal to 64 kbps (not including up-switch to FACH from URA-PCH). This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

6.2.5 Channel Upswitch Failure Rate UL Low Rate

KPI Name: USWITCH_FAILRATE_UL_LOW RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛−

owchAttemptLpmUlUpswitowchSuccessLpmUlUpswit1*100

Units: %





Note: Counters pmUlUpSwitchSuccessLow and pmUlUpSwitchAttemptLow stepped in Best AS cell.

KPI Description

This KPI evaluates the probability that the transitions in DL between FACH and CELL_DCH with UL rate up to 64 kbps fail due to admission control reject or failures during the channel switching procedure. The counter pmUlUpswitchAttemptLow is the number of UL upswitch attempts to TrCH with UL rate <= 64 kbit/s (inc. FACH). The counter is stepped for UL upswitch attempts to a RB combination with a Trch with UL rate <= 64 kbit/s (incl. FACH). The counter is incremented in all cells of the active set. The counter pmUlUpswitchSuccessLow is the number of successful UL upswitches to Transport Channel (TrCh) with UL rate <= 64 kbit/s (inc. FACH). The counter is stepped for successful UL upswitches to a RB combination with a Trch with UL rate <= 64 kbit/s (inc. FACH)). The counter is incremented in all cells of the active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

6.2.6 Channel Upswitch Failure Rate DL Medium Rate

KPI Name: USWITCH_FAILRATE_DL_MEDIUM RNC Sw Release: P5 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛−

ediumchAttemptMpmDlUpswitediumchSuccessMpmDlUpswit1*100

Units: % Note: Counters pmDlUpSwitchSuccessMedium and

pmDlUpSwitchAttemptMedium stepped in Best AS cell.

KPI Description





This KPI evaluates the probability that the channel upswitching transitions due to throughput in DL CELL_DCH to CELL_DCH with DL target rate between 64 and 256 kbps fail due to admission control reject or failures during the channel switching procedure. The counter pmDlUpswitchAttemptMedium is the number of attempted DL up-switches to bit-rates higher than 64 kbps and less than or equal to 256 kbps. The counter pmDlUpswitchSuccessMedium is the number of successful DL up-switches to bit-rates higher than 64 kbps and less than or equal to 256 kbps. It is stepped in each SRNC cell in the active set on reception of an RRC Radio Bearer Reconfiguration Complete message following DL up-switch of an Interactive PS RAB to bit-rates higher than 64 kbps and less than or equal to 256 kbps. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

6.2.7 Channel Upswitch Failure Rate UL Medium Rate

KPI Name: USWITCH_FAILRATE_UL_MEDIUM RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛−

ediumchAttemptMpmUlUpswitediumchSuccessMpmUlUpswit1*100

Units: % Note: Counters pmUlUpSwitchSuccessMedium and

pmUlUpSwitchAttemptMedium stepped in Best AS cell.

KPI Description This KPI evaluates the probability that the channel upswitching transitions due to throughput in UL CELL_DCH to CELL_DCH with UL target rate between 64 and 256 kbps fail due to admission control reject or failures during the channel switching procedure.





The counter pmUlUpswitchAttemptMedium is the number of attempted DL up-switches to bit-rates higher than 64 kbps and less than or equal to 256 kbps. It is stepped for each SRNC cell in which admission is requested at DL up-switch of interactive Packet RAB to bit-rates higher than 64 kbps and less than or equal to 256 kbps. The counter pmUlUpswitchSuccessMedium is the number of successfull UL upswitches to TrCh with 64 Kbit/s< UL rate <256 Kbit/s. It is stepped in all cells in AS for successful UL upswitches to a Trch with a maximum rate higher than 64 kbit/s and less than 256 kbit/s. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

6.2.8 Channel Upswitch Failure Rate DL High Rate

KPI Name: USWITCH_FAILRATE_DL_HIGH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛−

ighchAttemptHpmDlUpswitighchSuccessHpmDlUpswit1*100

Units: % Note: Counters pmDlUpSwitchSuccessHigh and

pmDlUpSwitchAttemptHigh stepped in Best AS cell.

KPI Description This KPI evaluates the probability that the channel upswitching transitions due to throughput in DL CELL_DCH to CELL_DCH with DL target rate between higher than 256 kbps (not including HS), fail due to admission control reject or failures during the channel switching procedure. The counter pmDlUpswitchAttemptHigh is the number of attempted DL up-switches to bit-rates higher than 256 kbps (not including HS). It is stepped for each SRNC





cell in which admission is requested at DL up-switch of Interactive PS RAB to bit-rates higher than 256 kbps (not including HS). The counter pmDlUpswitchSuccessHigh is the number of successful DL up-switches to bit-rates higher than 256 kbps (not including HS). It is stepped in each SRNC cell in the active set on reception of an RRC Radio Bearer Reconfiguration Complete message following DL up-switch of an Interactive Packet RAB to bit-rates higher than 256 kbps (not including HS). This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

6.2.9 Channel Upswitch Failure Rate UL High Rate

KPI Name: USWITCH_FAILRATE_UL_HIGH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛−

ighchAttemptHpmUlUpswitighchSuccessHpmUlUpswit1*100

Units: % Note: Counters pmUlUpSwitchSuccessHigh and

pmUlUpSwitchAttemptHigh stepped in Best AS cell.

KPI Description This KPI evaluates the probability that the channel upswitching transitions due to throughput in UL CELL_DCH to CELL_DCH with UL target rate higher than or equal to 256 kbps (excluding EUL), fail due to admission control reject or failures during the channel switching procedure. The counter pmUlUpswitchAttemptHigh is the number of UL upswitch attempts to TrCH with UL rate >= 256 kbit/s. It is stepped for UL upswitch attempts to a RB combination with a Trch with UL rate >= 256 kbit/s (excluding EUL), in all cells of the active set. The counter pmUlUpswitchSuccessHigh is the number of successful





UL upswitches to TrCh with UL rate >= 256 kbit/s (excluding EUL). It is stepped for successfull UL upswitches to a RB combination with a Trch with UL rate >= 256 kbit/s, in all cells of the active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

6.2.10 Channel Upswitch Failure Rate DL HS

KPI Name: USWITCH_FAILRATE_DL_HS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛−

schAttemptHpmDlUpswitschSuccessHpmDlUpswit1*100

Units: % Note:

KPI Description This KPI evaluates the probability that the channel upswitching transitions due to throughput in DL from CELL_FACH or CELL_DCH R99 to any HS state, fail due to admission control reject or failures during the channel switching procedure. The counter pmDlUpswitchAttemptHs is the number of DL upswitch attempts to any HS state. It is stepped for DL attempt to upswitch to a RB combination containing HS and incremented in all cells of the active set. The counter pmDlUpswitchSuccessHs is the number of successful DL upswitches to any HS state. It is stepped for successful DL upswitch to a RB combination containing HS and incremented in all cells of the active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI






6.2.11 Channel Upswitch Failure Rate UL EUL

KPI Name: USWITCH_FAILRATE_UL_EUL RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛−

ulchAttemptEpmUlUpswitulchSuccessEpmUlUpswit1*100

Units: % Note:

KPI Description This KPI evaluates the probability that the channel upswitching transitions due to throughput in UL CELL_FACH or CELL_DCH (R99) to EUL to fail due to admission control reject or failures during the channel switching procedure. The counter pmUlUpswitchAttemptEul is the number of attempted up-switches, triggered by Ul user activity, to a target RB combination E-DCH/HSDPA. Stepped for the target cell. The counter shall be stepped when NBAP: RL SETUP REQUEST or RL RECONFIGURATION PREPARE is sent from the RNC. The counter pmUlUpswitchSuccessEul is the number successful up-switches, triggered by Ul user activity, to a target RB combination E-DCH/HSDPA. Stepped for the target cell. The counter shall be stepped when RRC: RB RECONFIGURATION COMPLETE is received by the RNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





6.2.12 Channel Downswitch Failure Rate

KPI Name: DSWITCH_FAILRATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛−

chAttemptpmDownSwitchSuccesspmDownSwit1*100

Units: % Note: Counters pmDownSwitchSuccess and

pmDownSwitchAttempt stepped in Best AS cell.

KPI Description This KPI evaluates the probability that the channel downswitch transitions fail during the channel switching procedure. The counter pmDownSwitchAttempt is the number of channel downswitching attempts (UL or DL). The counter includes switches CELL_DCH to CELL_DCH as well as channel type switches (CELL_DCH R99 to CELL_FACH and downswitch from E-DCH/HSDPA to RACH/FACH) on cell level. The counter is stepped in all cells in the active set. The counter pmDownSwitchSuccess is the number of successful channel downswitches (UL or DL). The counter includes switches between dedicated channels as well as channel type switches (CELL_DCH to CELL_FACH) and downswitch from E-DCH/HSDPA RB combination on cell level. The counter is stepped for successful channel downswitches (both DCH->DCH and DCH->FACH and E-DCH/HSDPA -> RACH/FACH) in all cells in the active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





7 Traffic

7.1 PS Throughput

7.1.1 PS Data Average Throughput Net

KPI Name: PS_TPUTAVERG RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PEG Target Value:


( )4321

4321*8nketDuratiopmTotalPacnketDuratiopmTotalPacnketDuratiopmTotalPacnketDuratiopmTotalPac

etDatapmSentPacketDatapmSentPacketDatapmSentPacketDatapmSentPack+++

+++

Units: Mbps Note: Unit of pmSentPacketData1 and pmSentPacketData2

counters has been changed from P5 to P6 (from bytes to kbytes=1000 bytes)

KPI Description

This formula defines the RLC throughput on RNC base, without taking into consideration retransmissions. It is evaluated as the rate between the sum (in bits) of the counters of the packet sent for all Interactive RABs and the accumulated time (in ms) that data has been transmitted in bursts. The pmSentPacketData1, pmSentPacketData2, pmSentPacketData3 and pmSentPacketData4 counters are increased when PS interactive/best effort user data is transmitted and the size of the data burst is relatively between 200 bytes and 1 Kbyte, between 1 Kbyte and 10 Kbytes, between 10 Kbytes and 100 Kbytes and over 100 Kbytes. The counter accumulates the number of bytes (for the first and the second one) and of Kbytes (for the third and the fourth one) transmitted excluding retransmissions. The pmTotalPacketDuration1, pmTotalPacketDuration2, pmTotalPacketDuration3 and pmTotalPacketDuration4 counters accumulate the time (in ms) the relative size of data burst was transmitted. The counters are related to a burst which may start in a different ROP than in which it is ended. The result of the counter is accounted for in the ROP in which the burst is ended. This KPI can be computed only at RNC level since the counters in the formula are defined in the RncFunction MO type.





7.1.2 HS Data Average Throughput Net

KPI Name: HS_TPUTAVERG RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PEG Target Value:


⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

+++

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

+++

4321

/

4321

*1000*8

nHsketDuratiopmTotalPacnHsketDuratiopmTotalPacnHsketDuratiopmTotalPacnHsketDuratiopmTotalPac

etDataHsspmSentPacketDataHspmSentPacketDataHspmSentPacketDataHspmSentPack

Units: Kbps Note: Unit of pmSentPacketDataHs1 and pmSentPacketDataHs2

counters have been changed from P5 to P6 (from bytes to kbytes=1000 bytes)

KPI Description

This formula defines the RLC throughput on RNC base, without taking into consideration retransmissions. It is evaluated as the rate between the sum (in bits) of the counters of the packet sent for all Interactive RABs mapped on HSDPA and the accumulated time (in ms) that data has been transmitted in bursts. The pmSentPacketDataHs1, pmSentPacketDataHs2, pmSentPacketDataHs3 and pmSentPacketDataHs4 counters are increased when PS interactive/best effort user data is transmitted over the HS-DSCH channel and the size of the data burst is relatively between 200 bytes and 1 Kbyte, between 1 Kbyte and 10 Kbytes, between 10 Kbytes and 100 Kbytes and over 100 Kbytes. The counters accumulate the number of bytes (first and second ones) and of Kbytes (third and fourth ones) transmitted excluding retransmissions. The pmTotalPacketDurationHs1, pmTotalPacketDurationHs2, pmTotalPacketDurationHs3 and pmTotalPacketDurationHs4 counters accumulate the time (in ms) the relative size of data burst was transmitted. The counters are related to a burst which may start in a different ROP than in which it is ended. The result of the counter is accounted for in the ROP in which the burst is ended. This KPI can be computed only at RNC level since the counters in the formula are defined in the RncFunction MO type.





7.1.3 PS Data Retransmission Rate

KPI Name: PS_RETRANSM_RATE RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PEG Target Value:


⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

+++

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

+++

4321

/

4Re3Re2Re1Re

*100

etDatapmSentPacketDatapmSentPacketDatapmSentPacketDatapmSentPack

transetDataInclpmSentPacktransetDataInclpmSentPacktransetDataInclpmSentPacktransetDataInclpmSentPack

Units: % Note: Unit of pmSentPacketDataInclRetrans1,

pmSentPacketDataInclRetrans2, pmSentPacketData1 and pmSentPacketData2 counters have been changed from P5 to P6 (from bytes to kbytes=1000 bytes)

KPI Description

This KPI estimates the aggregated retransmission rate for all PS interactive traffic on DCH/FACH. It is calculated as the rate between the sum (in bits) of the counters of the packet sent for all Interactive RABs, including retransmissions, and the ones, excluding retransmissions. It can be also as an indication of BLER in DL. The pmSentPacketData1, pmSentPacketDataInclRetrans1, pmSentPacketData2, pmSentPacketDataInclRetrans2, pmSentPacketData3, pmSentPacketDataInclRetrans3, pmSentPacketData4 and pmSentPacketDataInclRetrans4 counters are increased when PS interactive/best effort user data is transmitted and the size of the data burst is relatively between 200 bytes and 1 Kbyte, between 1 Kbyte and 10 Kbytes, between 10 Kbytes and 100 Kbytes and over 100 Kbytes. The counters accumulate the number of bytes (first to fourth) and Kbytes (fifth to eighth) transmitted, respectively excluding and including retransmissions. This KPI can be computed only at RNC level since the counters in the formula are defined in the RncFunction MO type.





7.1.4 HS Data Retransmission Rate

KPI Name: HS_RETRANSM_RATE RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: RncFunction Counters Type: PEG Target Value:


⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

+++

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

+++

4321

/

4Re3Re2Re1Re

*100

etDataHspmSentPacketDataHspmSentPacketDataHspmSentPacketDataHspmSentPack

transHsetDataInclpmSentPacktransHsetDataInclpmSentPacktransHsetDataInclpmSentPacktransHsetDataInclpmSentPack

Units: % Note: Unit of pmSentPacketDataHs1, pmSentPacketDataHs2

pmSentPacketDataInclRetransHs1 and pmSentPacketDataInclRetransHs2 counters have been changed from P5 to P6 (from bytes to kbytes=1000 bytes)

KPI Description

This KPI estimates the aggregated retransmission rate for all PS interactive traffic for HSDPA on RLC level. It is calculated as the rate between the sum (in bits) of the counters of the packet sent for all Interactive RABs mapped to HSDPA, including retransmissions, and the ones, excluding retransmissions. It can be also as an indication of BLER in DL. The pmSentPacketDataHs1, pmSentPacketDataInclRetransHs1, pmSentPacketDataHs2, pmSentPacketDataInclRetransHs2, pmSentPacketDataHs3, pmSentPacketDataInclRetransHs3, pmSentPacketDataHs4 and pmSentPacketDataInclRetransHs4 counters are increased when PS interactive/best effort user data is transmitted on HS-DSCH channels and the size of the data burst is relatively between 200 bytes and 1 Kbyte, between 1 Kbyte and 10 Kbytes, between 10 Kbytes and 100 Kbytes and over 100 Kbytes. The counter accumulates the number of bytes (first to fourth) and of Kbytes (fifth to eighth) transmitted, respectively excluding and including retransmissions. This KPI can be computed only at RNC level since the counters in the formula are defined in the RncFunction MO type.





7.1.5 PS Data Average User Throughput DL

KPI Name: PS_INT_USER_DL_THROUGH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: TrigACC, TrigSCAN Target Value:


rPacketThpchDlRlcUsepmSamplesDketThpRlcUserPacpmSumDchDl

Units: kbps Note: New counters pmSumDchDlRlcUserPacketThp and

pmSamplesDchDlRlcUserPacketThp introduced in P6 to replace removed pmSumActDlRlcUserPacketThp and pmSamplesActDlRlcUserPacketThp counters in P5

KPI Description

The formula evaluates the average user throughput for PS Data in DL (kbps). It includes user data, excluding retransmissions, padding bits, data PDU headers and RLC control PDU’s. Measured in the best cell in the active set.

The counter pmSumDchDlRlcUserPacketThp Values are read periodically from an internal level counter and added to this counter. The level counter maintains the current DL RLC throughput for PS Interactive on R99 DCH, including user data only. This counter is not incremented when the throughput is 0 kbps. For a multi-RAB combination containing more than one PS Interactive RB, this counter is incremented for only one of the R99 PS Interactive RBs in the combination. Sampling Rate: 0.5 seconds

The counter pmSamplesDchDlRlcUserPacketThp is the number of samples in pmSumDchDlRlcUserPacketThp (that is, pmSamplesDchDlRlcUserPacketThp = pmSamplesDchDlRlcUserPacketThp +1, whenever pmSumDchDlRlcUserPacketThp is to be updated). It is measured two times/second and incremented by one if pmSumDchDlRlcUserPacketThp > 0 for the same polling time duration.





7.1.6 PS Streaming 64 Average User Throughput DL

KPI Name: PSSTR_64_USER_DL_THROUGH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: TrigACC, TrigSCAN Target Value:


am64rThpPsStrechDlRlcUsepmSamplesDPsStream64RlcUserThppmSumDchDl

Units: kbps Note: New counters pmSumDchDlRlcUserThpPsStream64 and

pmSamplesDchDlRlcUserThpPsStream64 introduced in P6.

KPI Description The formula evaluates the average user DL RLC throughput for Streaming PS 64 kbps DCH, excluding retransmissions, padding bits, data PDU headers and RLC control PDU’s. Measured in the best cell in the active set.

The counter pmSumDchDlRlcUserThpPsStream64 values are read periodically from an internal level counter and added to this counter. The level counter maintains the current DL RLC throughput, excluding retransmissions, for Streaming PS 64 kbps DCH. This counter is not incremented when data volume = 0. Scampling Rate: 0.5 seconds

The counter pmSamplesDchDlRlcUserThpPsStrem64 is the number of samples in pmSumDchDlRlcUserThpPsStream64 (that is, pmSamplesDchDlRlcUserThpPsStream64 = pmSamplesDchDlRlcUserThpPsStream64 +1, whenever pmSumDchDlRlcUserThpPsStream64 is to be updated). It is measured two times/second and incremented by one if pmSumDchDlRlcUserThpPsStream64 > 0 for the same polling time duration.





7.1.7 PS Streaming 128 Average User Throughput DL

KPI Name: PSSTR_128_USER_DL_THROUGH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: TrigACC, TrigSCAN Target Value:


am128rThpPsStrechDlRlcUsepmSamplesD8PsStream12RlcUserThppmSumDchDl

Units: kbps Note: New counters pmSumDchDlRlcUserThpPsStream128 and

pmSamplesDchDlRlcUserThpPsStream128 introduced in P6.

KPI Description

The formula evaluates the average user DL RLC throughput for Streaming PS 128 kbps DCH, excluding retransmissions, padding bits, data PDU headers and RLC control PDU’s. Measured in the best cell in the active set.







7.1.8 PS Streaming HS Average User Throughput DL

KPI Name: PSSTR_HS_USER_DL_THROUGH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: TrigACC, TrigSCAN Target Value:


amHsrThpPsStrechDlRlcUsepmSamplesDPsStreamHsRlcUserThppmSumDchDl

Units: kbps Note: New counters pmSumDchDlRlcUserThpPsStreamHs and

pmSamplesDchDlRlcUserThpPsStreamHs introduced in P6.

KPI Description The formula evaluates the average user DL RLC throughput for Streaming HSDPA, excluding retransmissions, padding bits, data PDU headers and RLC control PDU’s. Measured in the HS serving cell.

The counter pmSumDchDlRlcUserThpPsStreamHs values are read periodically from an internal level counter and added to this counter. The level counter maintains the current DL RLC throughput, excluding retransmissions, for Streaming HSDPA. This counter is not incremented when data volume = 0. Scampling Rate: 0.5 seconds

The counter pmSamplesDchDlRlcUserThpPsStremHs is the number of samples in pmSumDchDlRlcUserThpPsStreamHs (that is, pmSamplesDchDlRlcUserThpPsStreamHs = pmSamplesDchDlRlcUserThpPsStreamHs +1, whenever pmSumDchDlRlcUserThpPsStreamHs is to be updated). It is measured two times/second and incremented by one if pmSumDchDlRlcUserThpPsStreamHs > 0 for the same polling time duration.





7.1.9 HS Data Average User Throughput DL

KPI Name: HS_INT_USER_DL_THROUGH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Hsdsch Counters Type: TrigACC, TrigSCAN Target Value:


cketThpsRlcUserPapmSamplesHThpUserPacketpmSumHsRlc

Units: kbps Note: Split new counters pmSumHslRlcUserPacketThp and

pmSamplesHsRlcUserPacketThp introduced in P6 to replace removed pmSumActUlRlcUserPacketThp and pmSamplesActUlRlcUserPacketThp counters in P5. new counter in MO class Hsdsch

KPI Description

The counter pmSumHslRlcUserPacketThp sums all sample values recorded during a ROP for HS-DSCH RLC throughput measurements, excluding retransmissions. Reported on the best cell in the active set.

Values are read periodically from an internal level counter and added to this counter. The level counter maintains the current HS-DSCH RLC throughput, excluding retransmissions. Sampling Rate: 0.1 seconds

The counter pmSamplesHsRlcUserPacketThp is the number of samples in pmSumHsRlcUserPacketThp (that is, pmSamplesHsRlcUserPacketThp = pmSamplesHsRlcUserPacketThp +1, whenever pmSumHsRlcUserPacketThp is to be updated, this means if no data is transmitted the counter is not incremented).

7.1.10 PS Data Average User Throughput UL

KPI Name: PS_INT_USER_UL_THROUGH RNC Sw Release: P6 Importance: Medium





Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: TrigACC, TrigSCAN Target Value:


rPacketThpchUlRlcUsepmSamplesDketThpRlcUserPacpmSumDchUl

Units: kbps Note: Split new counters pmSumDchUlRlcUserPacketThp and

pmSamplesDchUlRlcUserPacketThp introduced in P6 to replace removed pmSumActUlRlcUserPacketThp and pmSamplesActUlRlcUserPacketThp counters in P5

KPI Description

The formula evaluates the average user throughput for R99 PS Data in UL (kbps). It includes user data, excluding retransmissions, padding bits, data PDU headers and RLC control PDU’s. Measured in the best cell in the active set

The counter pmSumDchUlRlcUserPacketThp values are read periodically from an internal level counter and added to this counter. The level counter maintains the current UL RLC throughput for PS Interactive on R99 DCH, including user data only. This counter is not incremented when the throughput is 0 kbps. For a multi-RAB combination containing more than one PS Interactive RB, this counter is incremented for only one of the R99 PS Interactive RBs in the combination. Sampling Rate: 0.5 seconds

The counter pmSamplesDchUlRlcUserPacketThp is the number of samples in pmSumDchUlRlcUserPacketThp (that is, pmSamplesDchUlRlcUserPacketThp = pmSamplesDchUlRlcUserPacketThp +1, whenever pmSumDchUlRlcUserPacketThp is to be updated). It is measured two times/second and incremented by one if pmSumDchUlRlcUserPacketThp > 0 for the same polling time duration.

7.1.11 PS Streaming 16 Average User Throughput UL

KPI Name: PSSTR_16_USER_UL_THROUGH RNC Sw Release: P6 Importance: Medium





Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: TrigACC, TrigSCAN Target Value:



Units: kbps Note: New counters pmSumDchUlRlcUserThpPsStream16 and

pmSamplesDchUlRlcUserThpPsStream16 introduced in P6.

KPI Description The formula evaluates the average user UL RLC throughput for Streaming PS 16 kbps DCH, excluding retransmissions, padding bits, data PDU headers and RLC control PDU’s. Measured in the best cell in the active set.




KPI Name: PSSTR_32_USER_UL_THROUGH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’





Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: TrigACC, TrigSCAN Target Value:





KPI Description The formula evaluates the average user UL RLC throughput for Streaming PS 32 kbps DCH, excluding retransmissions, padding bits, data PDU headers and RLC control PDU’s. Measured in the best cell in the active set.




KPI Name: PSSTR_16_USER_UL_THROUGH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: TrigACC, TrigSCAN





Target Value:


am128rThpPsStrechDlRlcUsepmSamplesD8PsStream12RlcUserThppmSumDchDl



KPI Description

The formula evaluates the average user UL RLC throughput for Streaming PS 128 kbps DCH, excluding retransmissions, padding bits, data PDU headers and RLC control PDU’s. Measured in the best cell in the active set.



7.1.14 EUL Data Average User Throughput UL

KPI Name: EUL_INT_USER_UL_THROUGH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Eul Counters Type: TrigACC, TrigSCAN Target Value:






acketThpulRlcUserPpmSamplesEtThpcUserPackepmSumEulRl

Units: kbps Note: Split new counters pmSumEullRlcUserPacketThp and

pmSamplesEulRlcUserPacketThp introduced in P6 to replace removed pmSumActUlRlcUserPacketThp and pmSamplesActUlRlcUserPacketThp counters in P5. new counter in MO class Eul

KPI Description

The counter pmSumEullRlcUserPacketThp sums all sample values recorded during a ROP for EUL RLC throughput measurements, excluding retransmissions. Reported on the best cell in the active set.

Values are read periodically from an internal level counter and added to this counter. The level counter maintains the current EUL RLC throughput, excluding retransmissions. Sampling Rate: 0.1 seconds

The counter pmSamplesEulRlcUserPacketThp is the number of samples in pmSumEulRlcUserPacketThp (that is, pmSamplesEulRlcUserPacketThp = pmSamplesEulRlcUserPacketThp +1, whenever pmSumEulRlcUserPacketThp is to be updated, this means if no data is transmitted the counter is not incremented).

7.1.15 PS Data Average Total Throughput DL

KPI Name: PS_INT_TOTAL_DL_THROUGH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: TrigACC, TrigSCAN Target Value:


PacketThpchDlRlcTotpmSamplesDetThpRlcTotPackpmSumDchDl

Units: kbps Note: New counters pmSumDchDlRlcTotPacketThp and





pmSamplesDchDlRlcTotPacketThp introduced in P6 to replace removed pmSumDchDlRlcTotPacketThp and pmSamplesDchDlRlcTotPacketThp counters in P5

KPI Description

The formula evaluates the average total throughput for PS Data in DL (kbps). It includes user data, retransmissions, padding bits, data PDU headers and RLC control PDU’s. Measured in the best cell in the active set.

The counter pmSumDchDlRlcTotPacketThp Values are read periodically from an internal level counter and added to this counter. The level counter maintains the current DL RLC throughput for PS Interactive on R99 DCH. This counter is not incremented when the throughput is 0 kbps. For a multi-RAB combination containing more than one PS Interactive RB, this counter is incremented for only one of the R99 PS Interactive RBs in the combination.

The counter pmSamplesDchDlRlcTotPacketThp is the number of samples in pmSumDchDlRlcTotPacketThp (that is, pmSamplesDchDlRlcTotPacketThp = pmSamplesDchDlRlcTotPacketThp +1, whenever pmSumDchDlRlcTotPacketThp is to be updated). It s reported for one R99 DCH PS Interactive Radio Bearer (RB). It is measured two times/second. Incremented by one if pmSumDchDlRlcTotPacketThp > 0 for the same polling_time duration.

7.1.16 HS Data Average Total Throughput DL

KPI Name: HS_INT_TOTAL_DL_THROUGH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Hsdsch Counters Type: TrigACC, TrigSCAN Target Value:


ketThpsRlcTotPacpmSamplesHhpTotPacketTpmSumHsRlc

Units: kbps Note: Split new counters pmSumEulRlcTotPacketThp and

pmSamplesEulRlcTotPacketThp introduced in P6 to replace





removed pmSumActUlRlcTotPacketThp and pmSamplesActUlRlcTotPacketThp counters in P5. New counter in MO class Hsdsch

KPI Description

The counter pmSumHsRlcTotPacketThp sums all sample values recorded during a ROP for HS-DSCH RLC throughput measurements, including retransmissions.

Values are read periodically from an internal level counter and added to this counter. The level counter maintains the current HS-DSCH RLC throughput, including retransmissions.

The counter pmSamplesHsRlcTotPacketThp is the number of samples in pmSumHsRlcTotPacketThp (that is, pmSamplesHsRlcTotPacketThp = pmSamplesHsRlcTotPacketThp +1, whenever pmSumHsRlcTotPacketThp is to be updated, this means if no data is transmitted the counter is not incremented).

7.1.17 PS Data Average Total Throughput UL

KPI Name: PS_INT_TOTAL_UL_THROUGH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: TrigACC, TrigSCAN Target Value:


PacketThpchUlRlcTotpmSamplesDetThpRlcTotPackpmSumDchUl

Units: kbps Note: Split new counters pmSumDchUlRlcTotPacketThp and

pmSamplesDchUlRlcTotPacketThp introduced in P6 to replace removed pmSumActUlRlcTotPacketThp and pmSamplesActUlRlcTotPacketThp counters in P5

KPI Description

The formula evaluates the average total throughput for PS Data in UL (kbps). It includes user data, retransmissions, padding bits, data PDU headers and RLC control PDU’s. Measured in the best cell in the active set.





The counter pmSumDchUlRlcTotPacketThp values are read periodically from an internal level counter and added to this counter. The level counter maintains the current UL RLC throughput for PS Interactive on R99 DCH. This counter is not incremented when the throughput is 0 kbps. For a multi-RAB combination containing more than one PS Interactive RB, this counter is incremented for only one of the R99 PS Interactive RBs in the combination. Sampling Rate: 0.5 s The counter pmSamplesDchUlRlcTotPacketThp is the number of samples in pmSumDchUlRlcTotPacketThp (that is, pmSamplesDchUlRlcTotPacketThp = pmSamplesDchUlRlcTotPacketThp +1, whenever pmSumDchUlRlcTotPacketThp is to be updated, this means if no data is transmitted the counter is not incremented). It is reported for one R99 PS Interactive DCH Radio Bearer (RB), It is measured two times/second and incremented by one if pmSumDchUlRlcTotPacketThp > 0 for the same polling_time duration.

7.1.18 EUL Data Average Total Throughput UL

KPI Name: EUL_INT_TOTAL_UL_THROUGH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Eul Counters Type: TrigACC, TrigSCAN Target Value:


cketThpulRlcTotPapmSamplesEThpcTotPacketpmSumEulRl

Units: kbps Note: Split new counters pmSumEulRlcTotPacketThp and

pmSamplesEulRlcTotPacketThp introduced in P6 to replace removed pmSumActUlRlcTotPacketThp and pmSamplesActUlRlcTotPacketThp counters in P5. New counter in MO class Eul

KPI Description

The counter pmSumEulRlcTotPacketThp sums all sample values recorded during a ROP for EUL RLC throughput measurements, including retransmissions. Reported on the best cell in the active set. Sampling Rate: 0.1 seconds.





Values are read periodically from an internal level counter and added to this counter. The level counter maintains the current EUL RLC throughput, including retransmissions.

The counter pmSamplesEulRlcTotPacketThp is the number of samples in pmSumEulRlcTotPacketThp (that is, pmSamplesEulRlcTotPacketThp = pmSamplesEulRlcTotPacketThp +1, whenever pmSumEulRlcTotPacketThp is to be updated, this means if no data is transmitted the counter is not incremented).

7.1.19 PS Data RLC Net Throughput DL

KPI Name: PS_INT_RLC_DL_THROUGH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PDF Target Value:


ThpUserPacketpmDchDlRlc

Units: kbps Note: Spit new counter pmDchDlRlcUserPacketThp in P6 replace

removed pmDlRlcUserPacketThp counter in P5

KPI Description The counter pmDchDlRlcUserPacketThp reports DL RLC throughput for PS Interactive on R99 DCH, including user data but excluding retransmissions, padding bits, data PDU headers and RLC control PDU's. Reported on the best cell in the active set. Sampling Rate: 0.5 seconds. Values are read periodically from an internal level counter that maintains the current throughput. Incremented by one when a throughput sample is within its range

Reported according to the following intervals:

[0], 0 <= x < 5 (kbps) [1], 5 <= x < 20 [2], 20 <= x < 40 [3], 40 <= x < 60 ... [19], 360 <= x





7.1.20 PS Data RLC Net throughput UL

KPI Name: PS_INT_RLC_UL_THROUGH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PDF Target Value:


ThpUserPacketpmDchUlRlc

Units: kbps Note: Split new counter pmDchUlRlcUserPacketThp in P6 replace

removed pmUlRlcUserPacketThp counter in P5

KPI Description The counter pmDchUlRlcUserPacketThp reports UL RLC throughput for PS Interactive on R99 DCH, including user data but excluding retransmissions, padding bits, data PDU headers and RLC control PDU's. Reported on the best cell in the active set. Sampling Rate: 0.5 seconds. Values are read periodically from an internal level counter that maintains the current throughput. Incremented by one when a throughput sample is within its range


[0], 0 <= x < 5 (kbps) [1], 5 <= x < 20 [2], 20 <= x < 40 [3], 40 <= x < 60 ... [19], 360 <= x

7.1.21 HS Data RLC Net Throughput DL

KPI Name: HS_INT_RLC_DL_THROUGH RNC Sw Release: P6





Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Hsdsch Counters Type: PDF Target Value:

KPI Recommended Formula rPacketThppmHsRlcUse

Units: kbps Note: Split new counter pmHsDlRlcUserPacketThp in P6 replace

removed pmDlRlcUserPacketThp counter in P5. New counter is in MO class Hsdsch

KPI Description

The counter pmHsRlcUserPacketThp reports the HS-DSCH DL RLC throughput (user data), excluding retransmissions. Values are read periodically from an internal level counter that maintains the current throughput. Incremented by one when a throughput sample is within its range. Sampling Rate: 0.1 s


[0]: 0 <= x < 25 (kbps) [1]: 25 <= x < 50 [2]: 50 <= x < 100 [3]: 100 <= x < 200 ... [13]: 1100 <= x < 1200 [14]: 1200 <= x < 1400 ... [17]: 1800 <= x < 2000 [18]: 2000 <= x < 2500 [19]: 2500 <= x < 3000 ... [23]: 4500 <= x < 5000 [24]: 5000 <= x < 6000 [25]: 6000 <= x < 7000 [26]: 7000 <= x < 8000 [27]: 8000 <= x < 10000 [28]: 10000 <= x < 12000 [29]: 12000 <= x





7.1.22 EUL Data RLC Net Throughput UL

KPI Name: EUL_INT_RLC_UL_THROUGH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Eul Counters Type: PDF Target Value:


perPacketThpmEulRlcUs

Units: kbps Note: Split new counter pmEulRlcUserPacketThp in P6 replace

removed pmUlRlcUserPacketThp counter in P5. new counter is in MO class Eul.

KPI Description

The counter pmEulRlcUserPacketThp reports EUL RLC throughput (user data), excluding retransmissions. Reported on the best cell in the active set. Values are read periodically from an internal level counter that maintains the current throughput. Incremented by one when a throughput sample is within its range. Sampling Rate: 0.1 s


[0]: 0 <= x < 25 (kbps) [1]: 25 <= x < 50 [2]: 50 <= x < 100 [3]: 100 <= x < 200 ... [13]: 1100 <= x < 1200 [14]: 1200 <= x < 1400 ... [17]: 1800 <= x < 2000 [18]: 2000 <= x





7.2 Cell Traffic

7.2.1 Cell Traffic Speech

KPI Name: ERL_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


ablish estCs12EstpmSamplesB

sh s12EstablipmSumBestC

Units: Erl Note: In P6, new RABs contributes to the

TRAFFIC_SPEECH

In P6 counters pmSumBestCs12Establish and pmSamplesBestCs12Establish stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The formula defines the traffic value (in Erlangs), aggregated on cell level for RABs Speech (including MultiRab). It is calculated as the ratio between Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumBestCs12Establish counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the level counter being added to the pmSum counter. The level counter maintains a snapshot of the number of active speech 12.2 Kbit RABs at any given instant in time. The counter is maintained per Best Cell. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. It is also updated whenever the Best Cell changes without a change to the Radio Link configuration. The pmSamplesBestCs12Establish counter, as a Scan counter, provides the





number of samples collected by pmSumBestCs12Establish. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.2.2 Cell Traffic AMR

KPI Name: ERL_SPEECH_AMR RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


shRabEstabliestAmrpmSamplesBshRabEstablimrpmSumBestA




1220012200

79507950

59005900

47504750

+

++

Units: Erl Note: In P6 counters

pmSumBestAmrXXXXRabEstablish and pmSamplesBestAmrXXXXEstablish stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC. XXXX : 4750;5900;7950;12200

KPI Description

The formula defines the traffic value (in Erlangs), aggregated on cell level for AMR RABs. It is calculated as sum of the ratios between Accumulator counter and the Scan counter for each Amr Rab. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumBestAmr4750RabEstablish, pmSumBestAmr5900RabEstablish,





pmSumBestAmr7950RabEstablish and pmSumBestAmr12200RabEstablish counters provide the sum of all sample values recorded within ROP period for ‘Number of Speech AMRXXXX RABs established’, where XXXX is equal respectively to ‘4750’, ‘5900’, ‘7950’, ‘12200’. They are based on an internal ‘level’ counter, whose value is read every 5 seconds. The pmSamplesBestAmr4750RabEstablish, pmSamplesBestAmr5900RabEstablish, pmSamplesBestAmr7950RabEstablish and pmSamplesBestAmr12200RabEstablish counters provide the number of samples recorded within the ROP period for ‘Number of Speech AMRXXXX RABs established’, where XXXX is equal respectively to ‘4750’, ‘5900’, ‘7950’, ‘12200’. These counters are increased every time the corresponding Sum counter is increased. Note: This counter is only incremented in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.2.3 Cell Traffic AMR-WB

KPI Name: ERL_SPEECH_AMRWB RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


bEstablishestAmrWbRapmSamplesBablishmrWbRabEstpmSumBestA

Units: Erl Note: In P6 counters pmSumBestAmrWbRabEstablish

and pmSamplesBestAmrWbEstablish stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC. AMR-WB is new service RAB introduced in P6





KPI Description

The formula defines the traffic value (in Erlangs), aggregated on cell level for AMR-WB RABs. It is calculated as sum of the ratios between Accumulator counter and the Scan counter for each Amr Wb Rab. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumBestAmrWbRabEstablish counter provide the sum of all sample values recorded within ROP period for ‘Number of Speech AMR-WB RABs established’. They are based on an internal ‘level’ counter, whose value is read every 5 seconds. The pmSamplesBestAmrWbRabEstablish counter provide the number of samples recorded within the ROP period for ‘Number of Speech AMR-WB RABs established’. These counters are increased every time the corresponding Sum counter is increased. Note: This counter is only incremented in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.2.4 Cell Traffic CS57

KPI Name: ERL_CS57 RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


hh

EstablisestCs57RabpmSamplesB

bliss57RabEstapmSumBestC

Units: Erl Note: In P6 counters pmSumBestCs57RabEstablish

and pmSamplesBestCs57RabEstablish stepped in SRNC, DRNC if IurLink::srncPmReporting =





ON in SRNC

KPI Description The KPI defines the traffic value (in Erlangs), aggregated on cell level for RABs Cs57 (including MultiRab). It is calculated as the ratio between Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumBestCs57RabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of relatively ’Number of streaming 57.6 kbit CS RABs established’ and ’Number of streaming 57.6 kbit CS RABs established’. The counter is maintained per Best Cell. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. It is also updated whenever the Best Cell changes without a change to the Radio Link configuration. The pmSamplesBestCs57Establish counter, as a Scan counter, provides the number of samples collected by pmSumBestCs57Establish. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.2.5 Cell Traffic CS64

KPI Name: ERL_CS64 RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:






EstablishestCs64RabpmSamplesBblishs64RabEstapmSumBestC

Units: Erl Note: In P6 counters pmSumBestCs64RabEstablish

and pmSamplesBestCs64RabEstablish stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the traffic value (in Erlangs), aggregated on cell level, for RABs Cs64 (including MultiRab). It is calculated as the ratio between Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumBestCs64RabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of ’Number of PS Interactive + conversational 64 kbps CS multi-RABs established’, at any given instant in time. The counter is maintained per Best Cell. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. It is also updated whenever the Best Cell changes without a change to the Radio Link configuration. The pmSamplesBestCs64Establish counter, as a Scan counter, provides the number of samples collected by pmSumBestCs64Establish. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.2.6 Cell Traffic PS Streaming

KPI Name: ERL_PS_STREAM RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’





Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


blishPs8RabEstaestPsStr64pmSamplesB

habEstablissStr64Ps8RpmSumBestP


pmSumBestPsStr64Ps8RabEstablish and pmSamplesBestPsStr64Ps8RabEstablish stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the traffic value (in Erlangs), aggregated on cell level, for RABs PS64 Streaming. It is calculated as the ratio between Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumBestPsStr64Ps8RabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of the ’Number of PS Streaming 16/64 + Packet 8kbps PS multi-RABs established’ at any given instant in time. The counter is maintained per Best Cell. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. It is also updated whenever the Best Cell changes without a change to the Radio Link configuration. The pmSamplesBestPsStr64Ps8RabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumBestPsStr64Ps8RabEstablish. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.





7.2.7 Cell Traffic PS Streaming 128

KPI Name: ERL_PS_STREAM128 RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


ablish8Ps8RabEstestPsStr12pmSamplesB

shRabEstablisStr128Ps8pmSumBestP


pmSumBestPsStr128Ps8RabEstablish and pmSamplesBestPsStr128Ps8RabEstablish stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the traffic value (in Erlangs), aggregated on cell level, for RABs PS64 Streaming. It is calculated as the ratio between Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumBestPsStr128Ps8RabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of the ‘Number of PS Streaming 16/128 + Packet 8kbps PS multi-RABs’ at any given instant in time. The counter is maintained per Best Cell. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. It is also updated whenever the Best Cell changes without a change to the Radio Link configuration. The pmSamplesBestPsStr128Ps8RabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumBestPsStr128Ps8RabEstablish. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC





basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.2.8 Cell Traffic Ps Interactive

KPI Name: ERL_PS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC Target Value:


ishhRabEstablestPsHsAdcpmSamplesBEstablishsHsAdchRabpmSumBestP

bEstablishachPsIntRapmSamplesFablishsIntRabEstpmSumFachP

ishtRabEstablestDchPsInpmSamplesBEstablishchPsIntRabpmSumBestD

++


pmSumBestDchPsIntRabEstablish, pmSumBestPsHsAdchRabEstablish, pmSamplesBestPsHsAdchRabEstablish and pmSamplesBestDchPsIntRabEstablish stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the traffic value (in Erlangs), aggregated on cell level, for all PS Interactive RABs on FACH, DCH and A-DCH. It is calculated as the sum of the ratios between Accumulator counter and Scan counter for FACH, DCH and A-DCH. The accumulator counter is the sum of all sample values, collected every 5 seconds. The pmSumFachPsIntRabEstablish, pmSumBestDchPsIntRabEstablish and pmSumBestPsHsAdchRabEstablish counters are based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of relatively ’Number of PS RABs in state FACH





established’, ’Number of PS Interactive RABs established, regardless of rate’ and ’Number of A-DCHs established’, at any given instant in time. The counter is maintained per Best Cell. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. It is also updated whenever the Best Cell changes without a change to the Radio Link configuration. The pmSamplesFachPsIntRabEstablish, pmSamplesBestDchPsIntRabEstablish and pmSamplesBestPsHsAdchRabEstablish counters, as Scan counters, provide the number of samples collected by the corresponding Accumulator counter. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.2.9 Cell Traffic Ps Interactive DCH/FACH

KPI Name: ERL_PS_DCHFACH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:



ishtRabEstablestDchPsInpmSamplesBEstablishchPsIntRabpmSumBestD

+

Units: Erl Note: In P6 counters pmSumBestDchPsIntRabEstablish

and pmSamplesBestDchPsIntRabEstablish stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the traffic value (in Erlangs), aggregated on cell level for all PS





Interactive RABs on FACH and DCH. It is calculated as the sum of the ratios between Accumulator counter and Scan counter for FACH and DCH. The accumulator counter is the sum of all sample values, collected every 5 seconds. The pmSumFachPsIntRabEstablish and pmSumBestDchPsIntRabEstablish counters are based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of relatively ’Number of PS RABs in state FACH established’ and ’Number of PS Interactive RABs established, regardless of rate’ at any given instant in time. The counter is maintained per Best Cell. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. It is also updated whenever the Best Cell changes without a change to the Radio Link configuration. The pmSamplesBestDchPsIntRabEstablish and pmSamplesFachPsIntRabEstablish counters, as Scan counters, provide the number of samples collected by pmSumBestDchPsIntRabEstablish and pmSamplesFachPsIntRabEstablish respectively. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.2.10 Cell Traffic PS HS

KPI Name: ERL_PS_HS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


ishhRabEstablestPsHsAdcpmSamplesB

EstablishsHsAdchRabpmSumBestP






pmSumBestPsHsAdchRabEstablish and pmSamplesBestPsHsAdchRabEstablish stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the traffic value (in Erlangs), aggregated on cell level for RABs HS. It is calculated as the ratio between Accumulator counter and the Scan counter for HS Rabs. The accumulator counter is the sum of all sample values, collected every 5 seconds. The pmSumBestPsHsAdchRabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. That counter holds the value of the total number of A-DCH radio bearers established in a cell which are considered to be the best in their active set. The pmSumBestPsHsAdchRabEstablish counter, as a scan counter, provides the number of samples collected by pmSamplesBestPsHsAdchRabEstablish. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.2.11 Cell Traffic PS Streaming HS

KPI Name: ERL_PSSTR_HS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:






EsthmHsAdchRabestPsStreapmSamplesB

abEstsStreamHsRpmSumBestP

Units: Erl Note: In P6 counters pmSumBestPsStreamHsRabEst

and pmSamplesBestPsStreamHsRabEst stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the traffic value (in Erlangs), aggregated on cell level for RABs PS Streaming HS. It is calculated as the ratio between Accumulator counter and the Scan counter for PS Streaming HS Rabs. The accumulator counter is the sum of all sample values, collected every 5 seconds. The pmSumBestPsStreamHsRabEst counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. That counter holds the value of the total number of PS Streaming HS RAB established in a cell which are considered to be the best in their active set. The pmSumBestPsStreamHsRabEst counter, as a scan counter, provides the number of samples collected by pmSamplesBestPsStreamHsRabEst. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.2.12 Cell Traffic EUL

KPI Name: ERL_PS_EUL RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:






bEstablishestPsEulRapmSamplesB

ablish sEulRabEstpmSumBestP

Units: Erl Note: In P6 counters pmSumBestPsEulRabEstablish

and pmSamplesBestPsEulRabEstablish stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The formula defines the traffic value (in Erlangs), aggregated on cell level, for EUL/HS RAB. It is calculated as the ratio between Accumulator counter and the Scan counter for EUL Rabs. The pmSumBestPsEulRabEstablish counter is incremented for every E-DCH radio bearer established in this cell when it is the best cell, incremented every 5 seconds. The pmSamplesBestPsEulRabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumBestPsEulRabEstablish. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.





7.3 RNC Traffic

7.3.1 RNC Traffic Speech

KPI Name: RNC_ERL_SPEECH RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: ACC, SCAN Target Value:


[ ][ ]∑

=

=

i ii

UeRchabEstablispmSamplesR UeRctablishpmSumRabEs

Units: Erl Note: i = 2, 9, 10, 19, 20, 23, 24, 27,33, 34, 35, 36, 37,

38, 57, 58, 59, 60, 76, 77, 78. In P6, new RABs, have been added in the formula:

CS 12.2 + 64/HS (UeRc=19), CS 12.2 + 384/HS (UeRc=20), CS 12.2 + 2*64/HS (UeRc=57), CS 12.2 + 2*128/HS (UeRc=58), CS 12.2 + 2*384/HS (UeRc=59), CS 12.2 + 128/HS (UeRc=60), CS 12.2 + PS128/128 + PS 128/128 (UeRc=76), CS 12.2 + PS STR 16/HS = PS 8/HS (UeRc=77), CS 12.2 + PS STR 16/HS = PS 8/HS (UeRc=78)

Counters stepped in target configuration

KPI Description

The KPI defines the traffic value (in Erlangs), aggregated on RNC level for RABs Speech (including MultiRab). It is calculated as the ratio between Accumulator counter and the corresponding Scan counter. The accumulator counter is the sum of all sample values, collected every 30 seconds.





The pmSumRabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically from the level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter can be increased or decreased and is updated by RRC Connection Setup, RRC Connection Release, RAB Establishment, RAB Release, Channel Switching. Please refer to the appendix for the complete list of all UeRc indexes. The pmSamplesRabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumRabEstablish. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time. Note: the counters involved in the formula are stepped also at Iur level.

7.3.2 RNC Traffic AMR-NB

KPI Name: RNC_ERL_SPEECH_AMR RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: ACC, SCAN Target Value:


[ ][ ]∑

=

=

i ii


Units: Erl Note: i = 33, 34, 35.


KPI Description The KPI defines the traffic value (in Erlangs), aggregated on RNC level for RABs AMR (including MultiRab). It is calculated as the ratio between Accumulator counter and the corresponding Scan counter. The accumulator counter is the sum of all sample values, collected every 30 seconds.






7.3.3 RNC Traffic AMR-WB

KPI Name: RNC_ERL_SPEECH_AMR RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: ACC, SCAN Target Value:


[ ][ ]∑

=

=

i ii


Units: Erl Note: i = 40-45, 47-48, 50-51.

AMR-WB is new RABs introduced in P6 [Please refer to Appendix]


KPI Description The KPI defines the traffic value (in Erlangs), aggregated on RNC level for RABs AMR (including MultiRab).





It is calculated as the ratio between Accumulator counter and the corresponding Scan counter. The accumulator counter is the sum of all sample values, collected every 30 seconds. The pmSumRabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically from the level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter can be increased or decreased and is updated by RRC Connection Setup, RRC Connection Release, RAB Establishment, RAB Release, Channel Switching. Please refer to the appendix for the complete list of all UeRc indexes. The pmSamplesRabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumRabEstablish. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time. Note: the counters involved in the formula are stepped also at Iur level.

7.3.4 RNC Traffic CS57

KPI Name: RNC_ERL_CS57 RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: ACC Target Value:


[ ][ ]∑

=

=

i ii


Units: Erl Note: i = 8.


KPI Description The KPI defines the traffic value (in Erlangs), aggregated on RNC level, for RABs Cs57 (including MultiRab). It is calculated as the ratio between Accumulator





counter and the corresponding Scan counter. The accumulator counter is the sum of all sample values, collected every 30 seconds. The pmSumRabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically from the level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter can be increased or decreased and is updated by RRC Connection Setup, RRC Connection Release, RAB Establishment, RAB Release, Channel Switching. Please refer to the appendix for the complete list of all UeRc indexes. The pmSamplesRabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumRabEstablish. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time. Note: the counters involved in the formula are stepped also at Iur level.

7.3.5 RNC Traffic CS64

KPI Name: RNC_ERL_CS64 RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: ACC, SCAN Target Value:


[ ][ ]∑

=

=

i ii


Units: Erl Note: i = 3, 14.


KPI Description The KPI defines the traffic value (in Erlangs), aggregated on RNC level, for RABs Cs64 (including MultiRab). It is calculated as the ratio between Accumulator counter and the corresponding Scan counter. The accumulator counter is the sum





of all sample values, collected every 30 seconds. The pmSumRabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically from the level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter can be increased or decreased and is updated by RRC Connection Setup, RRC Connection Release, RAB Establishment, RAB Release, Channel Switching. Please refer to the appendix for the complete list of all UeRc indexes. The pmSamplesRabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumRabEstablish. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time. Note: the counters involved in the formula are stepped also at Iur level.

7.3.6 RNC Traffic Ps64 Stream

KPI Name: RNC_ERL_STREAMING RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: ACC, SCAN Target Value:


[ ][ ]∑

=

=

i ii


Units: Erl Note: i = 13.


KPI Description The KPI defines the traffic value (in Erlangs), aggregated on RNC level, for RABs PS64 Streaming. It is calculated as the ratio between Accumulator counter and the corresponding Scan counter. The accumulator counter is the sum of all sample values, collected every 30 seconds.






7.3.7 RNC Traffic Ps128 Stream

KPI Name: RNC_ERL_STREAMING128 RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: ACC, SCAN Target Value:


[ ][ ]∑

=

=

i ii


Units: Erl Note: i = 17, 22, 23, 24, 46, 49, 50


KPI Description The KPI defines the traffic value (in Erlangs), aggregated on RNC level, for RABs PS128 Streaming (including multiRabs). It is calculated as the ratio between Accumulator counter and the corresponding Scan counter. The accumulator counter is the sum of all sample values, collected every 30 seconds. The pmSumRabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically from the level counter. Each read





results in the actual value read from the level counter being added to the pmSum counter. The level counter can be increased or decreased and is updated by RRC Connection Setup, RRC Connection Release, RAB Establishment, RAB Release, Channel Switching. Please refer to the appendix for the complete list of all UeRc indexes. The pmSamplesRabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumRabEstablish. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time. Note: the counters involved in the formula are stepped also at Iur level.

7.3.8 RNC Traffic Ps Data

KPI Name: RNC_ERL_PS RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: ACC Target Value:


[ ][ ]∑

=

=

i ii


Units: Erl Note: i = 4-7,10,15-20,22-32,36-39,43-60,62,66-69,72-74,76-

78 In P6, new following RABs have been added for PS data [please refer to Appendix]

KPI Description

The KPI defines the traffic value (in Erlangs), aggregated on RNC level, for all PS Interactive RABs on FACH, DCH and A-DCH. It is calculated as the sum of the rates between Accumulator counter and the corresponding Scan counter. The accumulator counter is the sum of all sample values, collected every 30 seconds. The pmSumRabEstablish counter is based on an internal level counter which is





maintained by RNC. Values are read periodically from the level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter can be increased or decreased and is updated by RRC Connection Setup, RRC Connection Release, RAB Establishment, RAB Release, Channel Switching. Please refer to the appendix for the complete list of all UeRc indexes. The pmSamplesRabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumRabEstablish. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time. Note: the counters involved in the formula are stepped also at Iur level.

7.3.9 RNC Traffic Ps Data DCH/FACH

KPI Name: RNC_ERL_PS_DCHFACH RNC Sw Release: P5 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: ACC Target Value:


[ ][ ]∑

=

=

i ii


Units: Erl Note: i = 4-7, 10, 17-18, 22-24, 26-32, 36-39, 43-45, 49-51,

67-69, 74, 76

KPI Description

The KPI defines the traffic value (in Erlangs), aggregated on RNC level, for all PS Interactive RABs on FACH and DCH. It is calculated as the sum of the rates between Accumulator counter and the corresponding Scan counter. The accumulator counter is the sum of all sample values, collected every 30 seconds. The pmSumRabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically from the level counter. Each read






7.3.10 RNC Traffic HS

KPI Name: RNC_ERL_HS RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: ACC, SCAN Target Value:


[ ][ ]∑

=

=

i ii


Units: Erl Note: i = 15, 16, 19, 20, 25, 46-49, 52-60, 62, 72-73, 77-

78 In P6, additional RABs have been added [Please refer to Appendix]

KPI Description

The KPI defines the traffic value (in Erlangs), aggregated on RNC level, in the measurement time interval, for RABs HS. It is calculated as ratio Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 30 seconds. The pmSumRabEstablish counter is based on an internal level counter which is





maintained by RNC. Values are read periodically from the level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter can be increased or decreased and is updated by RRC Connection Setup, RRC Connection Release, RAB Establishment, RAB Release, Channel Switching. Please refer to the appendix for the complete list of all UeRc indexes. The pmSamplesRabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumRabEstablish. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time. Note: the counters involved in the formula are stepped also at Iur level.

7.3.11 RNC Traffic Ps Streaming HS

KPI Name: RNC_ERL_HS RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: ACC, SCAN Target Value:


[ ][ ]∑

=

=

i ii


Units: Erl Note: i = 46, 49, 72-73, 77-78

In P6, additional RABs have been added [Please refer to Appendix]

KPI Description

The KPI defines the traffic value (in Erlangs), aggregated on RNC level, in the measurement time interval, for RABs HS. It is calculated as ratio Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 30 seconds.






7.3.12 RNC Traffic EUL

KPI Name: RNC_ERL_EUL RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: ACC, SCAN Target Value:


[ ][ ]∑

=

=

i ii


Units: Erl Note: i = 25, 62

KPI Description The KPI defines the traffic value (in Erlangs), aggregated on RNC level, for EUL/HS RAB. It is calculated as the ratio between Accumulator counter and the corresponding Scan counter. The accumulator counter is the sum of all sample values, collected every 30 seconds. The pmSumRabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically from the level counter. Each read





7.4 Cell Traffic Volume

7.4.1 Cell Traffic Volume DL Speech

KPI Name: DLPAYLOAD_SPEECH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


2cVolumeCs1pmDlTraffi

Units: Kbits Note: The traffic counters (both in DL and UL) of each single-RAB (e.g.

Speech CS 12.2) are modified to sum all the traffic frames (separately in DL and UL) cumulated for all UeRc configurations which carries that RAB.

KPI Description

The formula defines the DL traffic volume, measured on cell level, for RABs Speech (including MultiRab). It is just the sum of relative counters within the ROP period. The pmDlTrafficVolumeCs12 counter define the traffic volume on downlink (DL) in Kb relatively for conversational/speech 12.2 Kbps CS RAB and for any MultiRAB combination where Speech CS 12.2 RAB is included, after macrodiversity. It is pegged every time a DL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.2 Cell Traffic Volume DL AMR-NB





KPI Name: DLPAYLOAD_AMRNB RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


7950cVolumeAmrpmDlTraffi5900cVolumeAmrpmDlTraffi4750cVolumeAmrpmDlTraffi ++

Units: Kbits Note:

KPI Description The formula defines the DL traffic volume, measured on cell level, for RABs AMR. It is just the sum of relative counters within the ROP period. The pmDlTrafficVolumeAm4750, pmDlTrafficVolumeAm5900 and pmDlTrafficVolumeAm7950 counters define the traffic volume on downlink (DL) in Kb relatively for speech AMR4750, AMR5900 and AMR7950 RABs. It is pegged every time a DL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.3 Cell Traffic Volume DL AMR-WB

KPI Name: DLPAYLOAD_AMRWB RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG





Target Value:


WbcVolumeAmrpmDlTraffi Units: Kbits Note: New RAB AMR-WB introduced in P6

KPI Description The formula defines the DL traffic volume, measured on cell level, for RABs AMR-WB after macro diversity. It is just the sum of relative counters within the ROP period. The counter pmDlTrafficVolumeAmWb defines the traffic volume on downlink (DL) in Kb relatively for speech AMR-WB RABs. It is pegged every time a DL data frame is sent. Payload traffic includes user data, Medium Access Control (MAC) and Radio Link Control (RLC) header information, and retransmissions are also counted as part of the traffic volume. Incremented when Iub / Iur data frame received after macro diversity This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.4 Cell Traffic Volume DL CS57

KPI Name: DLPAYLOAD_CS57 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:



Units: Kbits Note:





KPI Description The formula defines the DL traffic volume, measured on cell level for RABs Cs57. It is just the sum of relative counters within the ROP period. The pmDlTrafficVolumeCs57 counter defines the traffic volume on downlink (DL) in Kb relatively for streaming 57.6 Kbps CS RAB after macrodiversity. It is pegged every time a DL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.5 Cell Traffic Volume DL CS64

KPI Name: DLPAYLOAD_CS64 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:



Units: Kbits Note:

KPI Description The formula defines the DL traffic volume, measured on cell level for RABs Cs64. It is just the sum of relative counters within the ROP period. The pmDlTrafficVolumeCs64 counter defines the traffic volume on downlink (DL) in Kb for conversational 64 Kbps CS RAB after macrodiversity. It is pegged every time a DL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI





equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.6 Cell Traffic Volume DL PS Streaming 16

KPI Name: DLPAYLOAD_PSSTREAMING16 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


tr16cVolumePsSpmDlTraffi


PS Streaming 16) are modified to sum all the traffic frames (separately in DL and UL) cumulated for all UeRc configurations which carries that RAB.

KPI Description

The formula defines the DL traffic volume (in Kbits), measured on cell level, for RABs PS16 Streaming. It is just the sum of relative counters within the ROP period. The pmDlTrafficVolumePsStr16 counter defines the traffic volume on downlink (DL) in Kb after macrodiversity, relatively for PS Streaming 128/16 interactive/multi RABs. They are pegged every time a DL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.






KPI Name: DLPAYLOAD_PSSTREAMING RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:



Units: kbits Note:

KPI Description The formula defines the DL traffic volume (in Kbits), measured on cell level, for RABs PS64 Streaming. It is just the sum of relative counters within the ROP period. The pmDlTrafficVolumePsStr64 counter defines the traffic volume on downlink (DL) in Kb after macrodiversity, relatively for streaming 16/64 PS kbps + interactive/background 8/8 PS MultiRAB. They are pegged every time a DL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.


KPI Name: DLPAYLOAD_PSSTREAMING128 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour








Units: MBytes Note: The traffic counters (both in DL and UL) of each single-RAB (e.g.

PS Streaming) are modified to sum all the traffic frames (separately in DL and UL) cumulated for all UeRc configurations which carries that RAB.

KPI Description

The formula defines the DL traffic volume (in Kbits), measured on cell level, for RABs PS128 Streaming. It is just the sum of relative counters within the ROP period. The pmDlTrafficVolumePsStr128 counter defines the traffic volume on downlink (DL) in Kb after macrodiversity, relatively for PS Streaming 16/128 + interactive/background 8/8 PS MultiRAB. They are pegged every time a DL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.9 Cell Traffic Volume DL PS Data DCH/FACH

KPI Name: DLPAYLOAD_PS_NONHS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






6cVolumePs1pmDlTrafficVolumePs8pmDlTraffi48cVolumePs3pmDlTraffi

28cVolumePs1pmDlTraffi 4cVolumePs6pmDlTraffi ommon cVolumePsCpmDlTraffi

++

+++

Units: Kbits Note: In P6, counter pmDlTrafficVolumePs16 introduced with new RAB

interactive PS X/16 RAB. The traffic counters (both in DL and UL) for each single-RAB (e.g. PS Interactive) are modified to sum all the traffic frames (separately in DL and UL) cumulated for all UeRc configurations which carries that RAB.

KPI Description

The formula defines the DL traffic volume, measured on cell level, for all PS Interactive RABs on FACH and DCH. It is just the sum of relative counters within the ROP period. The pmDlTrafficVolumePsCommon, pmDlTrafficVolumePs64, pmDlTrafficVolumePs128, pmDlTrafficVolumePs384, pmDlTrafficVolumePs8 and pmDlTrafficVolumePs16 counters define the traffic volume on downlink (DL) in Kb - after macrodiversity - respectively for PS RAB on FACH/RACH, PS 64/64 RAB, PS 64/128 RAB, PS 64/384 RAB, Speech 12.2 Kbps CS + interactive or background 64/64 Kbps multi RAB, PS Streaming + PS 8/8 Interactive RABs, PS X/16 Interactive RABs. They are pegged every time a DL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.10 Cell Traffic Volume DL PS Data HS

KPI Name: DLPAYLOAD_PS_HS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






ntHscVolumePsIpmDlTraffi

Units: kbits Note:

KPI Description The formula defines the payload traffic in the downlink for UeRc configurations on HS-DSCH. Only PS Interactive traffic is included. Incremented when DL data is sent from RNC on HS. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.11 Cell Traffic Volume DL PS Streaming HS

KPI Name: DLPAYLOAD_PSSTR_HS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


trHscVolumePsSpmDlTraffi

Units: kbits Note:

KPI Description Payload traffic in the downlink for UeRc configurations which carries a Streaming PS DL Trch on HS-DSCH. Only PS Streaming traffic is included. ncremented when DL data is sent from the RNC on HS-DSCH.





This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.12 Cell Traffic Volume DL MBMS PS Streaming 64

KPI Name: DLPAYLOAD_MBMS64 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: MbmsCch Counters Type: PEG Target Value:


trMbms64cVolumePsSpmDlTraffi

Units: Kbits Note: In P6 MBMS service has been introduced.

KPI Description The formula defines the Payload traffic on Downlink for streaming PS MBMS 64.8 kbps. The counter pmDlTrafficVolumePsStrMbms64 is incremented every time a MBMS DL data frame is sent with the rate of 64 kbps. Payload includes user data, Medium Access Control (MAC) and Radio Link Control (RLC) header information. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.






KPI Name: DLPAYLOAD_MBMS128 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: MbmsCch Counters Type: PEG Target Value:






KPI Name: DLPAYLOAD_MBMS256 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: MbmsCch










7.4.15 Cell Traffic Volume UL Speech

KPI Name: ULPAYLOAD_SPEECH RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


2cVolumeCs1pmUlTraffi

Units: Kbits Note: The traffic counters (both in DL and UL) for each

single-RAB (e.g. Speech CS 12.2) are modified to sum all the traffic frames (separately in DL and





UL) cumulated for all UeRc configurations which carries that RAB.

KPI Description

The formula defines the UL traffic volume, measured on cell level, for RABs Speech (including MultiRAB). It is just the sum of relative counters within the ROP period. The pmUlTrafficVolumeCs12 counter defines the traffic volume on uplink (UL) in Kb relatively for conversational/speech 12.2 Kbps CS RAB and for any MultiRAB combination where Speech CS 12.2 RAB is included, before macrodiversity. It is pegged every time a UL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.16 Cell Traffic Volume UL AMR-NB

KPI Name: ULPAYLOAD_AMRNB RNC Sw Release: P5 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


7950cVolumeAmrpmUlTraffi5900cVolumeAmrpmUlTraffi4750cVolumeAmrpmUlTraffi ++

Units: Kbits Note:

KPI Description The formula defines the UL traffic volume, measured on cell level, for RABs AMR. It is just the sum of relative counters within the ROP period. The pmUlTrafficVolumeAm4750, pmUlTrafficVolumeAm5900 and pmUlTrafficVolumeAm7950 counters define the traffic volume on uplink (UL) in Kb





relatively for speech AMR4750, AMR5900 and AMR7950 RABs. It is pegged every time a UL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.17 Cell Traffic Volume UL AMR-WB

KPI Name: ULPAYLOAD_AMRWB RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


WbcVolumeAmrpmUlTraffi Units: Kbits Note: New RAB AMR-WB introduced in P6

KPI Description The formula defines the UL traffic volume, measured on cell level, for RABs AMR-WB after macro diversity. It is just the sum of relative counters within the ROP period. The counter pmUlTrafficVolumeAmWb defines the traffic volume on uplink (UL) in Kb relatively for speech AMR-WB RABs. It is pegged every time a UL data frame is sent. Payload traffic includes user data, Medium Access Control (MAC) and Radio Link Control (RLC) header information, and retransmissions are also counted as part of the traffic volume. Incremented when Iub / Iur data frame received after macro diversity This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.





7.4.18 Cell Traffic Volume UL CS57

KPI Name: ULPAYLOAD_CS57 RNC Sw Release: P5 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:



Units: Kbits Note:

KPI Description The formula defines the UL traffic volume, measured on cell level for RABs Cs57. It is just the sum of relative counters within the ROP period. The pmUlTrafficVolumeCs57 counter defines the traffic volume on Uplink (UL) in Kb relatively for streaming 57.6 Kbps CS RAB after macrodiversity. It is pegged every time a UL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.19 Cell Traffic Volume UL CS64

KPI Name: ULPAYLOAD_CS64 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’








Units: Kbits Note:

KPI Description The formula defines the UL traffic volume, measured on cell level for RABs Cs64. It is just the sum of relative counters within the ROP period. The pmUlTrafficVolumeCs64 counter defines the traffic volume on uplink (UL) in Kb for conversational 64 Kbps CS RAB after macrodiversity. It is pegged every time a UL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.20 Cell Traffic Volume UL PS Streaming 16

KPI Name: ULPAYLOAD_PSSTREAMING16 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


tr16cVolumePsSpmUlTraffi

Units: Kbits





Note: The traffic counters (both in DL and UL) of each single-RAB (e.g. PS Streaming 16) are modified to sum all the traffic frames (separately in DL and UL) cumulated for all UeRc configurations which carries that RAB.

KPI Description

The formula defines the UL traffic volume (in Kbits), measured on cell level, for RABs PS16 Streaming. It is just the sum of relative counters within the ROP period. The pmDlTrafficVolumePsStr16 counter defines the traffic volume on uplink (UL) in Kb after macrodiversity, relatively for PS Streaming 16 interactive/multi RABs. They are pegged every time a DL data frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.


KPI Name: ULPAYLOAD_PSSTREAMING RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:



Units: Kbits Note: In P6, new RAB PS Streaming 32 is introduced.

The traffic counters (both in DL and UL) of each single-RAB (e.g. PS Streaming) are modified to sum all the traffic frames (separately in DL and UL) cumulated for all UeRc configurations which carries that RAB.

KPI Description

The formula defines the UL traffic volume (in Kbits), measured on cell level, for





RABs PS64 Streaming. It is just the sum of relative counters within the ROP period. The pmUlTrafficVolumePsStr32 counter defines the payload traffic in the uplink before macro diversity for UeRc configurations which carries a Streaming PS UL Trch on 32 kbps DCH. Only PS Streaming traffic is included. Incremented when UL data is received in the RNC on 32DCH This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.


KPI Name: ULPAYLOAD_PSSTREAMING128 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:



Units: Kbits Note:

The traffic counters (both in DL and UL) of each single-RAB (e.g. PS Streaming) are modified to sum all the traffic frames (separately in DL and UL) cumulated for all UeRc configurations which carries that RAB.

KPI Description

The formula defines the UL traffic volume (in Kbits), measured on cell level, for RABs PS128 Streaming. It is just the sum of relative counters within the ROP period. The pmUlTrafficVolumePsStr128 counter defines the traffic volume on uplink (UL) in Kb after macrodiversity, relatively for PS Streaming 16/128 + interactive/background 8/8 PS MultiRAB. They are pegged every time a UL data





frame is sent. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.23 Cell Traffic Volume UL PS Interactive DCH/FACH

KPI Name: ULPAYLOAD_PS_NONHS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


6cVolumePs1pmUlTrafficVolumePs8pmUlTraffi 84cVolumePs3pmUlTraffi

28cVolumePs1pmUlTraffi 4cVolumePs6pmUlTraffi ommon cVolumePsCpmUlTraffi

++

+++

Units: Kbits Note: The traffic counters (both in DL and UL) for each single-RAB (e.g.


KPI Description

The formula defines the UL traffic volume, measured on cell level, for all PS Interactive RABs on FACH and DCH. It is just the sum of relative counters within the ROP period. The meaning of the counters included in the formula is reported. pmUlTrafficVolumePsCommon is the traffic volume on UL in Kbps for PS RAB on FACH/RACH. pmUlTrafficVolumePs64 is the payload traffic (kbits) in UL before macro diversity for UeRc configurations which carries an Interactive UL Trch with max rate equal to 64 kbit/s. Only PS Interactive traffic is included. pmUlTrafficVolumePs128 is the payload traffic (kbits) in UL before macro diversity for UeRc configurations which carries an Interactive UL Trch with max rate equal to 128 kbit/s. Only PS Interactive traffic is included. pmUlTrafficVolumePs384 is the





payload traffic (kbits) in UL before macro diversity for UeRc configurations which carries an Interactive UL Trch with max rate equal to 384 kbit/s. Only PS Interactive traffic is included. pmUlTrafficVolumePs8 and pmUlTrafficVolumePs16 is the payload traffic (kbits) in UL before macro diversity for UeRc configurations which carry an Interactive UL TrCH with a maximum bit rate equal to 8 kbit/s and 16 kbit/s respectively. Only the PS Interactive part of the traffic volume is measured. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.4.24 Cell Traffic Volume UL PS Data EUL

KPI Name: ULPAYLOAD_PS_EUL RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


ntEulcVolumePsIpmUlTraffi



KPI Description

The formula defines the UL traffic volume (in Kbits), measured on cell level, for RABs PS interactive EUL/HS. It is just the sum of relative counters within the ROP period. The pmUlTrafficVolumePsIntEul counter defines the payload traffic in the uplink for UeRc configurations on E-DCH. Only PS Interactive traffic is included. Incremented when UL data is received by the RNC on EUL





This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. For optimization purpose or for finer traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.





7.5 RNC Traffic Volume

7.5.1 RNC Traffic Volume DL Speech

KPI Name: RNC_DLPAYLOAD_SPEECH RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i

iUeRctBeforeSplifficVolumepmDlDchTra

Units: Kbits Note: i = 2, 9, 10, 19, 20, 23, 24, 27, 36, 37, 38, 57-60,

76-78. In P6 additional RAB combination introduced [Please refer to Appendix]

KPI Description

The formula defines the DL traffic volume (in GBytes), aggregated at RNC level, in the measurement time interval, for RABs Speech (including MultiRab). The pmDlDchTrafficVolumeBeforeSplit counter in the UeRc MO is counting traffic volume DL in Kb on dedicated channels (DCHs) (measured before diversity splitting). It is pegged every time a DL data frame is sent. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only at RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.5.2 RNC Traffic Volume DL AMR-NB

KPI Name: RNC_DLPAYLOAD_AMRNB





RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 33, 34, 35.

KPI Description The formula defines the DL traffic volume (in GBytes), aggregated at RNC level, in the measurement time interval, for RABs AMR-NB (including MultiRab). The pmDlDchTrafficVolumeBeforeSplit counter in the UeRc MO is counting traffic volume DL in Kb on dedicated channels (DCHs) (measured before diversity splitting). It is pegged every time a DL data frame is sent. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only at RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.5.3 RNC Traffic Volume DL AMR-WB

KPI Name: RNC_DLPAYLOAD_AMRWB RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:






[ ]∑ =i


Units: Kbits Note: i = 40-45, 47-48, 50-51.

In P6, AMR-WB RAB is introduced.

KPI Description The formula defines the DL traffic volume (in GBytes), aggregated at RNC level, in the measurement time interval, for RABs AMR-WB (including MultiRab). The pmDlDchTrafficVolumeBeforeSplit counter in the UeRc MO is counting traffic volume DL in Kb on dedicated channels (DCHs) (measured before diversity splitting). It is pegged every time a DL data frame is sent. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only at RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.5.4 RNC Traffic Volume DL CS57

KPI Name: RNC_DLPAYLOAD_CS57 RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 8.

KPI Description





The formula defines the DL traffic volume (in GBytes), aggregated up to RNC level, in the measurement time interval, for RABs CS 57.6 (including MultiRab). The pmDlDchTrafficVolumeBeforeSplit counter is counting traffic volume DL in Kb on dedicated channels (DCHs) (measured before diversity splitting). It is pegged every time a DL data frame is sent. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only at RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.5.5 RNC Traffic Volume DL CS64

KPI Name: RNC_DLPAYLOAD_CS64 RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 3, 14.

KPI Description The formula defines the DL traffic volume (in GBytes), aggregated up to RNC level, in the measurement time interval, for RABs CS 64 (including MultiRab). The pmDlDchTrafficVolumeBeforeSplit counter is counting traffic volume DL in Kb on dedicated channels (DCHs) (measured before diversity splitting). It is pegged every time a DL data frame is sent. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only at RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration





one RAB at the time.

7.5.6 RNC Traffic Volume DL PS Streaming 16

KPI Name: RNC_DLPAYLOAD_PSSTREAMING RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 22-23

KPI Description The formula defines the DL traffic volume (in Kbits), aggregated at RNC level, in the measurement time interval, for PS16 Streaming traffic. The pmDlDchTrafficVolumeBeforeSplit counter is counting traffic volume DL in Kb on dedicated channels (DCHs) (measured before diversity splitting). It is pegged every time a DL data frame is sent. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.


KPI Name: RNC_DLPAYLOAD_PSSTREAMING RNC Sw Release: P6 Importance: High





Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 13

KPI Description The formula defines the DL traffic volume (in Kbits), aggregated at RNC level, in the measurement time interval, for PS64 Streaming traffic. The pmDlDchTrafficVolumeBeforeSplit counter is counting traffic volume DL in Kb on dedicated channels (DCHs) (measured before diversity splitting). It is pegged every time a DL data frame is sent. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.


KPI Name: RNC_DLPAYLOAD_PSSTREAMING128 RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:






[ ]∑ =i



In P6 new RAB are introduced [Please refer to Appendix]

KPI Description

The formula defines the DL traffic volume (in Kbits), aggregated at RNC level, in the measurement time interval, for PS128 Streaming traffic. The pmDlDchTrafficVolumeBeforeSplit counter is counting traffic volume DL in Kb on dedicated channels (DCHs) (measured before diversity splitting). It is pegged every time a DL data frame is sent. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.5.9 RNC Traffic Volume DL PS

KPI Name: RNC_DLPAYLOAD_PS RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 4-7, 15-20, 22-32, 36-39, 43-62, 66-69, 72-74, 76-

78 In P6 new UeRc has been introduced. [Please refer to Appendix]





KPI Description

The formula defines the DL traffic volume (in Kbits), aggregated at RNC level, in the measurement time interval, for PS Interactive traffic. The pmDlDchTrafficVolumeBeforeSplit counter is counting traffic volume DL in Kb on dedicated channels (DCHs) (measured before diversity splitting). It is pegged every time a DL data frame is sent. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.5.10 RNC Traffic Volume DL Ps Data DCH/FACH

KPI Name: RNC_DLPAYLOAD_PS_NON_HS RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 4-7, 10, 15-20, 22-32, 36-39, 43-60, 62, 66-69, 72-

74, 76 In P6, new UeRc introduced [Please refer to Appendix]

KPI Description

The formula defines the DL traffic volume (in Kbits), aggregated at RNC level, in the measurement time interval, for PS Interactive on DCH and FACH traffic. The pmDlDchTrafficVolumeBeforeSplit counter is counting traffic volume DL in Kb on dedicated channels (DCHs) (measured before diversity splitting). It is pegged every time a DL data frame is sent. Please refer to the appendix for the complete





list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.5.11 RNC Traffic Volume DL HS

KPI Name: RNC_DLPAYLOAD_PS_HS RNC Sw Release: P5 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 15-16, 19-20, 25, 46-49, 52-60, 62, 66, 72-73, 77-

78 In P6, new UeRc have been introduced. [Please refer to Appendix]

KPI Description

The formula defines the DL traffic volume (in Kbits), aggregated at RNC level, in the measurement time interval, for HS traffic. The pmDlDchTrafficVolumeBeforeSplit counter is counting traffic volume DL in Kb on dedicated channels (DCHs) (measured before diversity splitting). It is pegged every time a DL data frame is sent. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.





7.5.12 RNC Traffic Volume UL Speech

KPI Name: RNC_ULPAYLOAD_SPEECH RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i

iUeRcAfterCombfficVolumepmUlDchTra

Units: Kbits Note: i = 2, 9, 10, 19, 20, 23, 24, 27, 36, 37, 38, 57-60,

76-78. In P6 additional RAB combination introduced [Please refer to Appendix]

KPI Description

The formula defines the UL traffic volume, aggregated at RNC level, in the measurement time interval, for RABs Speech (including MultiRab). The pmUlDchTrafficVolumeAfterComb counter is counting traffic volume UL in Kb on dedicated channels (DCHs) (measured after diversity combination). It is pegged every time a UL data frame is received. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.5.13 RNC Traffic Volume UL AMR-NB

KPI Name: RNC_ULPAYLOAD_AMRNB RNC Sw Release: P6 Importance: High Scope: RNC





Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i



KPI Description The formula defines the UL traffic volume, aggregated at RNC level, in the measurement time interval, for RABs AMR (including MultiRab). The pmUlDchTrafficVolumeAfterComb counter is counting traffic volume UL in Kb on dedicated channels (DCHs) (measured after diversity combination). It is pegged every time a UL data frame is received. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.5.14 RNC Traffic Volume UL AMR-WB

KPI Name: RNC_ULPAYLOAD_AMRWB RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i






Units: Kbits Note: i = 40-45, 47-48, 50-51.

In P6, AMR-WB RAB is introduced.

KPI Description The formula defines the UL traffic volume, aggregated at RNC level, in the measurement time interval, for RABs AMR (including MultiRab). The pmUlDchTrafficVolumeAfterComb counter is counting traffic volume UL in Kb on dedicated channels (DCHs) (measured after diversity combination). It is pegged every time a UL data frame is received. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.5.15 RNC Traffic Volume UL CS57

KPI Name: RNC_ULPAYLOAD_CS57 RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 8.

KPI Description The formula defines the UL traffic volume (in GBytes), aggregated at RNC level, in the measurement time interval, for RABs CS 57.6 (including MultiRab).





The pmUlDchTrafficVolumeAfterComb counter is counting traffic volume UL in Kb on dedicated channels (DCHs) (measured after diversity combination). It is pegged every time a UL data frame is received. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.5.16 RNC Traffic Volume UL CS64

KPI Name: RNC_ULPAYLOAD_CS64 RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 3, 14.

KPI Description The formula defines the UL traffic volume, aggregated at RNC level, in the measurement time interval, for RABs CS 64 data (including MultiRab). The pmUlDchTrafficVolumeAfterComb counter is counting traffic volume UL in Kb on dedicated channels (DCHs) (measured after diversity combination). It is pegged every time a UL data frame is received. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.





7.5.17 RNC Traffic Volume UL PS Streaming 16

KPI Name: RNC_ULPAYLOAD_PSTREAMING16 RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =

iiUeRcAfterCombfficVolumepmUlDchTra

Units: Kbits Note: i = 13,17, 72, 77

In P6 new UeRc introduced [Please refer Appendix]

KPI Description

The formula defines the UL traffic volume (in GBytes), aggregated at RNC level, in the measurement time interval, for PS16 Streaming traffic. The pmUlDchTrafficVolumeAfterComb counter is counting traffic volume UL in Kb on dedicated channels (DCHs) (measured after diversity combination). It is pegged every time a UL data frame is received. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.


KPI Name: RNC_ULPAYLOAD_PSTREAMING32 RNC Sw Release: P6 Importance: High





Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =


Units: Kbits Note: i = 72, 78

In P6 new UeRc introduced [Please refer Appendix]

KPI Description

The formula defines the UL traffic volume (in GBytes), aggregated at RNC level, in the measurement time interval, for PS32 Streaming traffic. The pmUlDchTrafficVolumeAfterComb counter is counting traffic volume UL in Kb on dedicated channels (DCHs) (measured after diversity combination). It is pegged every time a UL data frame is received. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.


KPI Name: RNC_ULPAYLOAD_PSSTREAMING128 RNC Sw Release: P5 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:






[ ]∑ =


Units: Kbits Note: i = 22, 23, 46,49.

In P6 new UeRc introduced. [Please refer to Appendix]

KPI Description

The formula defines the UL traffic volume, aggregated at RNC level, in the measurement time interval, for PS128 Streaming traffic. The pmUlDchTrafficVolumeAfterComb counter is counting traffic volume UL in Kb on dedicated channels (DCHs) (measured after diversity combination). It is pegged every time a UL data frame is received. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

7.5.20 RNC Traffic Volume UL Ps Data

KPI Name: RNC_ULPAYLOAD_PS RNC Sw Release: P5 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 4-7, 10, 15-20, 22-32, 36-39, 43-60, 62, 66-69, 72-74,

76-78





In P6, new UeRc introduced [Please refer to Appendix]

KPI Description

The formula defines the DL traffic volume (in GBytes), aggregated at RNC level, in the measurement time interval, for PS Interactive traffic. The pmUlDchTrafficVolumeAfterComb counter is counting traffic volume UL in Kb on dedicated channels (DCHs) (measured after diversity combination). It is pegged every time a UL data frame is received. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time. The formula is kept in P5 for backward compatibility to P4, but it does not include EUL, as the counter pmUlDchTrafficVolumeAfterComb is not stepped for EUL/HSDPA (UeRc=25).

7.5.21 RNC Traffic Volume UL HS

KPI Name: RNC_ULPAYLOAD_PS_HS RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 15-16,19-20,25,46-48,52-60,62,66,72-73,77-78

In P6, new UeRc introduced. [Please refer to Appendix]

KPI Description

The formula defines the UL traffic volume (in GBytes), aggregated at RNC level, in





the measurement time interval, for all PS Interactive RABs only on A-DCH. It is just the sum of relative counters within the ROP period. The pmUlDchTrafficVolumeAfterComb counter is counting traffic volume UL in Kb on dedicated channels (DCHs) (measured after diversity combination). It is pegged every time a UL data frame is received. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time. The formula is kept in P5 for backward compatibility to P4, but it does not include EUL, as the counter pmUlDchTrafficVolumeAfterComb is not stepped for EUL/HSDPA (UeRc=25).

7.5.22 RNC Traffic Volume UL EUL

KPI Name: RNC_ULPAYLOAD_PS_EUL RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UeRc Counters Type: PEG Target Value:


[ ]∑ =i


Units: Kbits Note: i = 25, 62

In P6, new UeRc introduced. [Please refer to Appendix]

KPI Description

The formula defines the UL traffic volume (in GBytes), aggregated at RNC level, in the measurement time interval, for all PS Interactive RABs only on A-DCH. It is just the sum of relative counters within the ROP period. The pmUlDchTrafficVolumeAfterComb counter is counting traffic volume UL in Kb





on dedicated channels (DCHs) (measured after diversity combination). It is pegged every time a UL data frame is received. Please refer to the appendix for the complete list of all UeRc indexes. Since all the counters composing the formula are collected on a per UeRc basis, this KPI can be computed only on RNC level. For optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time. The formula is kept in P5 for backward compatibility to P4, but it does not include EUL, as the counter pmUlDchTrafficVolumeAfterComb is not stepped for EUL/HSDPA (UeRc=25).





8 Capacity

8.1 Average Users

8.1.1 Average Users Speech

KPI Name: AVGNUMCONN_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


blish s12RabEstapmSamplesC

h abEstablispmSumCs12R

Units: Links Note: In P6, new RABs contributes to the

AVERAGE_USERS_SPEECH: CS 12.2+2*64/HSDPA (UeRc=57), CS 12.2+2*128/HSDPA (UeRc=58), CS 12.2+2*384/HSDPA (UeRc=59), CS 12.2+128/HSDPA (UeRc=60), CS 12.2+Str PS16/HS+PS8/HS(UeRc=77), CS 12.2+Str PS 32/HS+PS8/HS (UeRc=78).

In P6, counters stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC.

KPI Description

The formula defines the Average value of users aggregated on cell level for all RABs Speech (including MultiRab), not only for the Best cell in active set. It is calculated as the ratio between Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumCs12RabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the level counter being added to the





pmSum counter. The level counter maintains a snapshot of the number of active speech 12.2 Kbit RABs at any given instant in time. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. The pmSamplesCs12RabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumCs12RabEstablish.

8.1.2 Average Users AMR-NB

KPI Name: AVGNUMCONN_AMR_NB RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


shRabEstablimrpmSamplesAshRabEstablipmSumAmr




1220012200

79507950

59005900

47504750

+

++

Units: links Note: In P6, counters stepped in SRNC, DRNC if

IurLink::srncPmReporting = ON in SRNC.

KPI Description The formula defines the Average value of users aggregated on cell level for all AMR RABs, not only for the Best cell in active set. It is calculated as sum of the ratios between Accumulator counter and the Scan counter for each Amr Rab. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumAmr4750RabEstablish, pmSumAmr5900RabEstablish, pmSumAmr7950RabEstablish and pmSumAmr12200RabEstablish counters provide the sum of all sample values recorded within ROP period for ‘Number of Speech AMRXXXX RABs established’, where XXXX is equal respectively to ‘4750’, ‘5900’, ‘7950’, ‘12200’. They are based on an internal ‘level’ counter, whose value is read every 5 seconds. The pmSamplesAmr4750RabEstablish,





pmSamplesAmr5900RabEstablish, pmSamplesAmr7950RabEstablish and pmSamplesAmr12200RabEstablish counters provide the number of samples recorded within the ROP period for ‘Number of Speech AMRXXXX RABs established’, where XXXX is equal respectively to ‘4750’, ‘5900’, ‘7950’, ‘12200’. These counters are increased every time the corresponding Sum counter is increased.

8.1.3 Average Users AMR-WB

KPI Name: AVGNUMCONN_AMR_WB RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


ablishmrWbRabEstpmSamplesAshRabEstablipmSumAmrWb

Units: links Note: In P6, counters stepped in SRNC, DRNC if


KPI Description The formula defines the Average value of users aggregated on cell level for all AMR-WB RABs, not only for the Best cell in active set. It is calculated as sum of the ratios between Accumulator counter and the Scan counter for each Amr Rab. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumAmrWbRabEstablish counter provides the sum of all sample values recorded within ROP period for ‘Number of Speech AMR-WB RABs established’. It is based on an internal ‘level’ counter, whose value is read every 5 seconds. The pmSamplesAmrWbRabEstablish counter provides the number of samples recorded within the ROP period for ‘Number of Speech AMR-WB RABs established’. This counter is increased every time the corresponding Sum counter increased.





8.1.4 Average Users Cs Streaming Data

KPI Name: AVGNUMCONN _CS57 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


hh

bliss57RabEstapmSamplesC

abEstablispmSumCs57R

Units: Links Note: In P6, counters stepped in SRNC, DRNC if


KPI Description The formula defines the Average value of users aggregated on cell level for all RABs Cs57 (including MultiRab), not only for the Best cell in active set. It is calculated as the ratio between Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumCs57RabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of relatively ’Number of streaming 57.6 kbit CS RABs established’ and ’Number of streaming 57.6 kbit CS RABs established’. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. The pmSamplesCs57Establish counter, as a Scan counter, provides the number of samples collected by pmSumCs57Establish.

8.1.5 Average Users Cs64 Data

KPI Name: AVGNUMCONN _CS64 RNC Sw Release: P6





Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


blishs64RabEstapmSamplesChabEstablispmSumCs64R



KPI Description The formula defines the Average value of users aggregated on cell level for all RABs Cs64 (including MultiRab), not only for the Best cell in active set. It is calculated as the ratio between Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumCs64RabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of ’Number of PS Interactive + conversational 64 kbps CS multi-RABs established’, at any given instant in time. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. The pmSamplesCs64Establish counter, as a Scan counter, provides the number of samples collected by pmSumCs64Establish.

8.1.6 Average Users Ps Stream 64

KPI Name: AVGNUMCONN _STREAM RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour





Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


habEstablissStr64Ps8RpmSamplesP

tablish64Ps8RabEspmSumPsStr



KPI Description The formula defines the Average value of users aggregated on cell level for all RABs PS64 Streaming, not only for the best cell in Active Set. It is calculated as the ratio between Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumPsStr64Ps8RabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of the ’Number of PS Streaming 16/64 + Packet 8kbps PS multi-RABs established’ at any given instant in time. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. The pmSamplesPsStr64Ps8RabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumPsStr64Ps8RabEstablish.

8.1.7 Average Users Ps128 Stream

KPI Name: AVGNUMCONN _STREAM128 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:






shRabEstablisStr128Ps8pmSamplesP

stablish128Ps8RabEpmSumPsStr



KPI Description The formula defines the Average value of users aggregated on cell level for all RABs PS64 Streaming, not only for the best cell in Active Set. It is calculated as the ratio between Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumPsStr128Ps8RabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of the ‘Number of PS Streaming 16/128 + Packet 8kbps PS multi-RABs’ at any given instant in time. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. The pmSamplesPsStr128Ps8RabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumPsStr128Ps8RabEstablish.

8.1.8 Average Users Ps Data

KPI Name: AVGNUMCONN _PS RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC Target Value:






ablishsEulRabEstpmSamplesPshRabEstablipmSumPsEul

EstablishsHsAdchRabpmSamplesPblishdchRabEstapmSumPsHsA


vesInteractipmSamplesPeractivepmSumPsInt

+

++



KPI Description The formula defines the Average value of users aggregated on cell level for all PS Interactive RABs on FACH, DCH and A-DCH, not only for the best cell in Active Set. It is calculated as the sum of the ratios between Accumulator counter and Scan counter for FACH, DCH and A-DCH. The accumulator counter is the sum of all sample values, collected every 5 seconds. The pmSumFachPsIntRabEstablish, pmSumPsInteractive pmSumPsHsAdchRabEstablish and pmSumPsEulRabEstablish counters are based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of relatively ’Number of PS RABs in state FACH established’, ’Number of PS Interactive RABs established, regardless of rate’ ’Number of A-DCHs established’ and ‘Number of E-DCH RABs established’, at any given instant in time. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. It is also updated whenever the Best Cell changes without a change to the Radio Link configuration. The pmSamplesFachPsIntRabEstablish, pmSamplesPsInteractive pmSamplesPsHsAdchRabEstablish and pmSamplesPsEulRabEstablish counters, as Scan counters, provide the number of samples collected by the corresponding Accumulator counter.

8.1.9 Average Users Ps Data DCH/FACH

KPI Name: AVGNUMCONN _PS_NON_HS RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:







vesInteractipmSamplesPeractivepmSumPsInt

+

Units: Links Note: In P6, counters pmSumPsInteractive and

pmSamplesPsInteractive stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC.

KPI Description

The formula defines the Average value of users aggregated on cell level for all PS Interactive RABs on FACH and DCH, not only for the best cell in the Active Set. It is calculated as the sum of the ratios between Accumulator counter and Scan counter for FACH and DCH. The accumulator counter is the sum of all sample values, collected every 5 seconds. The pmSumFachPsIntRabEstablish and pmSumPsInteractive counters are based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of relatively ’Number of PS RABs in state FACH established’ and ’Number of PS Interactive RABs established, regardless of rate’ at any given instant in time. The level counter is updated by RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover, and Softer Handover, i.e. whenever the Radio Link configuration is changed. The pmSamplesPsInteractive and pmSamplesFachPsIntRabEstablish counters, as Scan counters, provide the number of samples collected by pmSumPsInteractive and pmSumFachPsIntRabEstablish respectively.

8.1.10 Average Users HS

KPI Name: AVGNUMCONN _HS RNC Sw Release: P5 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:






EstablishsHsAdchRabpmSamplesP

blishdchRabEstapmSumPsHsA



KPI Description The formula defines the Average value of users aggregated on cell level for all RABs HS, not only for the best cell in Active Set. It is calculated as the ratio between Accumulator counter and the Scan counter for HS Rabs. The accumulator counter is the sum of all sample values, collected every 5 seconds. The pmSumPsHsAdchRabEstablish counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The pmSumPsHsAdchRabEstablish counter, as a scan counter, provides the number of samples collected by pmSamplesPsHsAdchRabEstablish.

8.1.11 Average Users PS STREAM HS

KPI Name: AVGNUMCONN _PSSTRHS RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


abEstsStreamHsRpmSamplesP

teamHsRabEspmSumPsStr







KPI Description The formula defines the Average value of users aggregated on cell level for all RABs PS Streaming HS, not only for the best cell in Active Set. It is calculated as the ratio between Accumulator counter and the Scan counter for PS Streaming HS Rabs. The accumulator counter is the sum of all sample values, collected every 5 seconds. The pmSumPsStreamHsRabEst counter is based on an internal level counter which is maintained by RNC. Values are read periodically, every 5 seconds, from the internal level counter. Each read results in the actual value read from the level counter being added to the pmSum counter. The pmSumPsStreamHsRabEst counter, as a scan counter, provides the number of samples collected by pmSamplesPsStreamHsRabEst.

8.1.12 Average Users EUL

KPI Name: AVGNUMCONN _EUL RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


ablishsEulRabEstpmSamplesP

sh RabEstablipmSumPsEul



KPI Description The formula defines the Average value of users aggregated on cell level for all EUL/HS RAB, not only for the best cell in the Active Set. It is calculated as the ratio between Accumulator counter and the Scan counter for EUL Rabs. The pmSumPsEulRabEstablish counter is incremented for every E-DCH radio bearer established in this cell, incremented every 5 seconds. The pmSamplesPsEulRabEstablish counter, as a Scan counter, provides the number of samples collected by pmSumPsEulRabEstablish..





8.1.13 Average Users RRC Only

KPI Name: AVGNUMCONN_RRCONLY RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


blish rcOnlyEstapmSamplesR

h lyEstablispmSumRrcOn



KPI Description The formula defines the average RRC only connections which were active during a ROP period. It is calculated as the ratio between Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 30 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSumRrcOnlyEstablish counter provides a snapshot of the total number of currently active RRC only connection is recorded once every 30 seconds. This counter contains the sum of all the snapshot values taken in a ROP period added together. The condition is based on an internal level counter which is maintained by RNC. Values are read periodically, every 30 seconds, from the internal level counter. Each read results in the pmSamples counter being increased by one, and the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of the number of RRC only connections active at any given instant in time that is the counter can be decreased or increased. The level counter is updated by RRC Connection Setup, RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, Inter-frequency Handover, RAB Establishment, RAB Release, Soft Handover and Softer Handover. The pmSamplesRrcOnlyEstablish counter provides the number of samples recorded within the ROP period for number of active RRC-only connections. This counter is increased at every occasion when the corresponding sum counter is stepped.





8.1.14 Average Users URA

KPI Name: AVGNUMCONN_URA RNC Sw Release: P6 Importance: Medium Scope: Ura Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Ura Counters Type: ACC, SCAN Target Value:


abUrapmSamplesR

apmSumRabUr

Units: Links Note:

KPI Description The formula defines the the average number of PS RABs on FACH/RACH which were active during a ROP period. It is calculated as the ratio between Accumulator counter and the Scan counter. The accumulator counter is the sum of all sample values, collected every 5 seconds; the Scan counter provides the number of times the Accumulator has been incremented. The pmSamplesRabUra counter provides the number of samples recorded within the ROP period for number of PS Interactive RABs in URA_PCH, sampled once every 30 seconds. This counter is increased or decreased according to the number of samples recorded within the ROP period for number of PS Interactive RABs in URA_PCH, sampled once every 30th second. Note: This counter is only incremented in the SRNC. The pmSumRabUra counter provides the sum of all sample values recorded for number of PS Interactive RABs in URA_PCH, sampled once every 30 seconds. This counter is increased or decreased when measuring the number of PS Interactive RABs in URA_PCH changes, sampled once every 30th second. Note: This counter is only incremented in the SRNC. Note that the MO class of the counters above is Ura.





8.2 Admission Control

8.2.1 Requests Denied due to Admission for RAB Speech

KPI Name: NONHO_REQDEN_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

mptSpeechablishAttepmNoRabEst

SpeechoReqDeniedpmNoOfNonH*100

Units: % Note: In P6, counter pmNoRabEstablishAttemptSpeech

stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

Above KPI calculates the percentage of number of Speech RAB establishments rejected by admission control over the total of Speech RAB establishment attempts. The pmNoOfNonHoReqDeniedSpeech counter is increased in the cell where admission for RAB Establishments’ Speech is rejected. Note that the counter is not stepped when admission is rejected in a D-RNC and is applicable to all Speech RAB establishments including establishment on a Speech/Interactive multi RAB configuration. The pmNoRabEstablishAttemptSpeech counter is increased just after successful RAB Speech Mapping, when a RANAP RAB Assignment Request message is received from the CN with Speech RABs to be setup or modified: this counter will only be incremented in the SRNC for the Best Cell. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





8.2.2 Requests Denied due to Admission for RAB CS

KPI Name: NONHO_REQDEN_CS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

+ mptCs57ablishAttepmNoRabEst mptCs64ablishAttepmNoRabEst

CsoReqDeniedpmNoOfNonH*100


and pmNoRabEstablishAttemptCs57 stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

Above KPI calculates the percentage of number of CS RAB establishments rejected by admission control over the total of CS RAB establishment attempts. The pmNoOfNonHoReqDeniedCs counter is increased in the cell where admission for RAB Establishments’ CS data or streaming is rejected. Note that the counter is not stepped when admission is rejected in a D-RNC. The pmNoRabEstablishAttemptCs57 and pmNoRabEstablishAttemptCs64 counters are increased after successful RAB Speech Establishment, is increased just after successful RAB Cs57 and Cs64 Mapping, when a RANAP RAB Assignment Request message is received from the CN with CS RABs to be setup or modified. These counters will only be incremented in the SRNC for the Best Cell. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





8.2.3 Requests Denied due to Admission for RAB PS Streaming

KPI Name: NONHO_REQDEN_STREAM RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠

⎞⎜⎝

⎛treammptPacketSablishAttepmNoRabEst

gPsStreaminoReqDeniedpmNoOfNonH*100

Units: % Note: In P6, counter

pmNoRabEstablishAttemptPacketStream stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

Above KPI calculates the percentage of number of PS Streaming rejected by admission control over the total of PS Streaming attempt establishments. The pmNoOfNonHoReqDeniedPsStreaming counter is increased in the cell where admission for RAB Establishments’ PS Streaming is rejected. Note that the counter is not stepped when admission is rejected in a D-RNC. The pmNoRabEstablishAttemptPacketStream counter is increased just after successful PS Streaming RAB Mapping, when a RANAP RAB Assignment Request message is received from the CN with PS Streaming RABs to be setup or modified: this counter will only be incremented in the SRNC for the Best Cell. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





8.2.4 Requests Denied due to Admission for RAB PS Streaming 128

KPI Name: NONHO_REQDEN_STREAM128 RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

tream128mptPacketSablishAttepmNoRabEst

PsStr128oReqDeniedpmNoOfNonH*100


pmNoRabEstablishAttemptPacketStream128 stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

Above KPI calculates the percentage of number of PS Streaming 128 RAB establishments rejected by admission control over the total of PS Streaming 128 RAB establishment attempts. The pmNoOfNonHoReqDeniedPsStr128 counter is increased in the cell where admission for RAB Establishments’ PS Streaming 128 is rejected. Note that the counter is not stepped when admission is rejected in a D-RNC. The pmNoRabEstablishAttemptPacketStream128 counter is increased just after successful PS Streaming 128 RAB Mapping, when a RANAP RAB Assignment Request message is received from the CN with PS Streaming 128 RABs to be setup or modified: this counter will only be incremented in the SRNC for the Best Cell. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





8.2.5 Requests Denied due to Admission for RAB PS Interactive

KPI Name: NONHO_REQDEN_PS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

nteractivemptPacketIablishAttepmNoRabEst

eInteractivoReqDeniedpmNoOfNonH*100


pmNoRabEstablishAttemptPacketInteractive stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

Above KPI calculates the percentage of number of PS Interactive RAB establishments rejected by admission control over the total of PS Interactive RAB establishment attempts. The pmNoOfNonHoReqDeniedInteractive counter is increased in the cell where admission for RAB Establishments’ PS Interactive is rejected. Note that the counter is not stepped when admission is rejected in a D-RNC. The pmNoRabEstablishAttemptPacketInteractive counter is increased just after successful PS Interactive RAB Mapping, when a RANAP RAB Assignment Request message is received from the CN with PS Interactive RABs to be setup or modified: this counter will only be incremented in the SRNC for the Best Cell. Note that the pmNoOfNonHoReqDeniedInteractive counter is triggered twice when the RAB Establishment attempt for PS Interactive on HS and successive reattempt on DCH fail. For this reason, in order to investigate the RAB Establishments blocks, due to radio resources shortage, it’s recommended to check the DCH/FACH KPI that follows in this chapter. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can






8.2.6 Requests Denied due to Admission for RAB PS Interactive DCH/FACH

KPI Name: NONHO_REQDEN_PS_NON_HS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

+

+

⎟⎟

⎠

⎞

⎜⎜

⎝

⎛

ntHsBest BlockTnPsIpmNoRabEst

HsoReqDeniedpmNoOfNonH

iveNonHsetInteractAttempPackpmNoRabEst

/HsoReqDeniedpmNoOfNonH

- eInteractivoReqDeniedpmNoOfNonH*100

Units: % Note: In P6, counters pmNoRabEstAttemptPsIntNonHs


KPI Description

Above KPI calculates the percentage of number of PS Interactive RAB establishments rejected by admission control over the total of PS Interactive RAB establishment attempts. The pmNoOfNonHoReqDeniedInteractive counter is increased in the cell where admission for RAB Establishments’ PS Interactive is rejected. Note that the counter is not stepped when admission is rejected in a D-RNC. Note that the pmNoOfNonHoReqDeniedInteractive counter is triggered twice when the RAB Establishment attempt for PS Interactive on HS and successive reattempt on DCH fail. The pmNoOfNonHoReqDeniedHs counter is increased in the cell where admission for RAB Establishments’ HS Interactive is rejected. Note that the counter is not stepped when admission is rejected in a D-RNC.

The pmNoRabEstAttemptPsIntNonHs counter is increased by one when a RANAP RAB Assignment Request message is received from the CN with RABs to be set up or modified, after successful RAB mapping to PS Interactive. The counter is reported per single RAB state for each RAB that is attempted, on the best cell in the





active set, only when the last reattempt is on a non-HS configuration (i.e. on DCH/DCH or RACH/FACH): this counter will only be incremented in the SRNC for the Best Cell.

The pmNoOfNonHoReqDeniedHs counter provides the number of Interactive RAB establishments on a (High Speed) HS configuration rejected by admission control. The counter is increased in the cell where admission is rejected. Note: The counter is not stepped when admission is rejected in a DRNC cell. The pmNoRabEstBlockTnPsIntHsBest counter provides the number of RAB establishment attempts for RAB-type PS Interactive for HS that are blocked due to TN congestion or TN failure, counted on the best cell. This counter is stepped when the establishment of a PS Interactive RAB fails due to UNI-SAAL or AAl2 congestion, IP resource limitations or blocking as a result of user dimensioned transport network configured capacity. The counter is stepped for the best cell in the active set but only if the cell is in the SRNC.


8.2.7 Requests Denied due to Admission for RAB HS

KPI Name: NONHO_REQDEN_HS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

HsnteractivemptPacketIablishAttepmNoRabEst

HsoReqDeniedpmNoOfNonH*100


pmNoRabEstablishAttemptPackeInteractivetHs stepped in SRNC, DRNC if






KPI Description Above KPI calculates the percentage of number of HS RAB establishments rejected by admission control over the total of HS RAB establishment attempts. The pmNoOfNonHoReqDeniedHs counter is increased in the cell where admission for RAB Establishments’ HS Interactive is rejected. Note that the counter is not stepped when admission is rejected in a D-RNC. The pmNoRabEstablishAttemptPacketInteractiveHs counter is increased just after successful HS RAB Mapping, when a RANAP RAB Assignment Request message is received from the CN with HS RABs to be setup or modified: this counter will only be incremented in the SRNC for the Best Cell. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

8.2.8 Requests Denied due to Admission for EUL

KPI Name: NONHO_REQDEN_EUL RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

EulnteractivemptPacketIablishAttepmNoRabEst

EuloReqDeniedpmNoOfNonH*100


pmNoRabEstablishAttemptPacketInteractiveEul stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description





Above KPI calculates the percentage of number of PS RAB establishments mapped to EUL/HS-DSCH rejected by admission control over the total of EUL/HS-DSCH RAB establishment attempts. The counter pmNoOfNonHoReqDeniedEul is the number of admission requests denied at RAB establishment on E-DCH. The counter pmNoRabEstablishAttemptPacketInteractiveEul is the number of attempted RAB establishments for PS Interactive RAB mapped on E-DCH/ HSDPA. It is stepped for the suitable Serving E-DCH cell identified by the Serving E-DCH cell selection performed due to RAB establishment. The counter is triggered after reception of RAB Assignement Request and serving cell selection. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

8.2.9 EUL Serving Cell Admission Reject

KPI Name: EUL_SC_ADM_REJ RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


niedEulgCellReqDepmNoServin

Units: % Note:

KPI Description This KPI is an indication of accessibility for EUL/HS PS Interactive in case of EUL/HS PS RAB attempt in the cell selected to be the serving cell.

The counter pmNoServingCellReqDeniedEul is the number of admission requests denied when requesting the cell as serving cell because the number of E-DCH users is above the admission threshold. It is stepped at admission reject when requesting the cell as serving cell due to the number of E-DCH users is above the





admission threshold eulServingCellUsersAdm. The means of this policy it is possible to limit the number of simultaneous EUL scheduled users in a cell, preventing that many users have to share the available resources and get too low throughput.

This KPI is computed at cell level and can be used to fine tune the Utrancell parameter eulServingCellUsersAdm that limits the amount of EUL users admitted in case the cell is used as serving cell (recommended=4).

8.2.10 EUL Non-serving Cell Admission Reject

KPI Name: EUL_NSC_ADM_REJ RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


qDeniedEulvingCellRepmNoNonSer

Units: % Note:

KPI Description This KPI is an indication of accessibility for EUL/HS PS RAB during mobility.

The counter pmNoNonServingCellReqDeniedEul is the number of admission requests from EUL users in Soft Handover, denied when requesting the cell as non-serving cell because the number of E-DCH users is above the admission threshold eulNonServingCellUsersAdm. By means of this policy it is possible to limit the number of simultaneous non-serving EUL RLs in a cell, preventing that many EUL users occupy the UL HW shared with non-EUL users.

This KPI is computed at cell level and can be used to fine tune the Utrancell parameter eulNonServingCellUsersAdm that limits the amount of EUL users admitted in case the cell is used as serving cell (recommended=100).





8.3 RAB Establishment Failure Causes

8.3.1 UL ASE Limit Failure

KPI Name: REQDEN_ULASE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+

+

+

+

wBestmptLackDlHRabEstAttepmNoFailed

wBest mptLackUlHRabEstAttepmNoFailed

semptLackUlARabEstAttepmNoFailed

semptLackDlARabEstAttepmNoFailed

+ hnlCodemptLackDlCRabEstAttepmNoFailed

+wr mptLackDlPRabEstAttepmNoFailed

onnLimit mptExceedCRabEstAttepmNoFailed

/semptLackUlARabEstAttepmNoFailed*100

Units: % Note: In P5, counters for failures due to RBS HW are introduced.

KPI Description This KPI highlights the percentage of failed RAB establishments due to lack of UL ASE over the total of RAB establishment failures due to other reasons. The pmNoFailedRabEstAttemptLackUlAse, pmNoFailedRabEstAttemptLackDlAse, pmNoFailedRabEstAttemptLackDlChnlCode and pmNoFailedRabEstAttemptLackDlPwr, pmNoFailedRabEstAttemptLackUlHwBest, pmNoFailedRabEstAttemptLackDlHwBest counters are stepped when admission control fails with reject reason lack respectively of UL ASE, DL ASE, DL channelization codes, DL power, RBS UL HW and RBS DL HW. The pmNoFailedRabEstAttemptExceedConnLimit counter is stepped when admission control fails with reject reason value SF8, SF16, or SF32. The KPI can be computed per RNC basis as well as a per cell. When computing the RNC result, individual cell counters should be summed up to RNC before applying KPI calculation. This is in contrast to applying the KPI equation to each





cell and then averaging across the RNC. The latter can give incorrect results.

8.3.2 DL ASE Limit Failure

KPI Name: REQDEN_DLASE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+

+

+

+








/semptLackDlARabEstAttepmNoFailed*100

Units: % Note: In P5, counters for failures due to RBS HW are

introduced.

KPI Description This KPI highlights the percentage of failed RAB establishments due to lack of DL ASE over the total of RAB establishment failures due to other reasons. The pmNoFailedRabEstAttemptLackUlAse, pmNoFailedRabEstAttemptLackDlAse, pmNoFailedRabEstAttemptLackDlChnlCode, pmNoFailedRabEstAttemptLackDlPwr, pmNoFailedRabEstAttemptLackUlHwBest, pmNoFailedRabEstAttemptLackDlHwBest counters are stepped when admission control fails with reject reason lack respectively of UL ASE, DL ASE, DL channelization codes, DL power, RBS UL HW and RBS DL HW. The pmNoFailedRabEstAttemptExceedConnLimit counter is stepped when admission control fails with reject reason value SF8, SF16, or SF32. This KPI can be computed on a per RNC basis as well as a per cell basis. When






8.3.3 Code Usage Failure

KPI Name: REQDEN_CODES RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+

+

+

+








/hnlCodemptLackDlCRabEstAttepmNoFailed*100

Units: % Note: In P5 counters of HW failures are introduced.

KPI Description This KPI highlights the percentage of failed RAB establishments due to lack of DL Channelization codes over the total of RAB establishment failures due to other reasons. The pmNoFailedRabEstAttemptLackUlAse, pmNoFailedRabEstAttemptLackDlAse, pmNoFailedRabEstAttemptLackDlChnlCode, pmNoFailedRabEstAttemptLackDlPwr, pmNoFailedRabEstAttemptLackUlHwBest, pmNoFailedRabEstAttemptLackDlHwBest counters are stepped when admission control fails with reject reason lack respectively of UL ASE, DL ASE, DL channelization codes, DL power, RBS UL HW and RBS DL HW. The pmNoFailedRabEstAttemptExceedConnLimit counter is stepped when admission





control fails with reject reason value SF8, SF16, or SF32. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

8.3.4 Power Limit Failure

KPI Name: REQDEN_DLPOWER RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+

+

+

+








/wrmptLackDlPRabEstAttepmNoFailed*100


introduced.

KPI Description This KPI highlights the percentage of failed RAB establishments due to lack of DL power codes over the total of RAB establishment failures due to other reasons. The pmNoFailedRabEstAttemptLackUlAse, pmNoFailedRabEstAttemptLackDlAse, pmNoFailedRabEstAttemptLackDlChnlCode, pmNoFailedRabEstAttemptLackDlPwr, pmNoFailedRabEstAttemptLackUlHwBest, pmNoFailedRabEstAttemptLackDlHwBest counters are stepped when admission





control fails with reject reason lack respectively of UL ASE, DL ASE, DL channelization codes, DL power, RBS UL HW and RBS DL HW. The pmNoFailedRabEstAttemptExceedConnLimit counter is stepped when admission control fails with reject reason value SF8, SF16, or SF32. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

8.3.5 SF Histogram Limit Failure

KPI Name: REQDEN_SFHYST RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+

+

+

+








/onnLimitmptExceedCRabEstAttepmNoFailed*100

Units: % Note: In P5, failures due to RBS HW are introduced.

KPI Description This KPI highlights the percentage of failed RAB establishments due to exceeding the configured connection limit when allocating Spreading factor (‘SF Histogram’ in Admission Reject signal) over the total of RAB establishment failures due to other reasons.





The pmNoFailedRabEstAttemptLackUlAse, pmNoFailedRabEstAttemptLackDlAse, pmNoFailedRabEstAttemptLackDlChnlCode, pmNoFailedRabEstAttemptLackDlPwr, pmNoFailedRabEstAttemptLackUlHwBest, pmNoFailedRabEstAttemptLackDlHwBest counters are stepped when admission control fails with reject reason lack respectively of UL ASE, DL ASE, DL channelization codes, DL power, RBS UL HW and RBS DL HW. The pmNoFailedRabEstAttemptExceedConnLimit counter is stepped when admission control fails with reject reason value SF8, SF16, or SF32. This KPI can be computed per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

8.3.6 UL HW Limit Failure

KPI Name: REQDEN_ULHW RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+

+

+

+








/wBestmptLackUlHRabEstAttepmNoFailed*100


introduced.

KPI Description





This KPI highlights the percentage of failed RAB establishments due to exceeding the configured connection limit when allocating UL Hardware over the total of RAB establishment failures due to other reasons. The pmNoFailedRabEstAttemptLackUlAse, pmNoFailedRabEstAttemptLackDlAse, pmNoFailedRabEstAttemptLackDlChnlCode, pmNoFailedRabEstAttemptLackDlPwr, pmNoFailedRabEstAttemptLackUlHwBest, pmNoFailedRabEstAttemptLackDlHwBest counters are stepped when admission control fails with reject reason lack respectively of UL ASE, DL ASE, DL channelization codes, DL power, RBS UL HW and RBS DL HW. The pmNoFailedRabEstAttemptExceedConnLimit counter is stepped when admission control fails with reject reason value SF8, SF16, or SF32. This KPI can be computed per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

8.3.7 DL HW Limit Failure

KPI Name: REQDEN_DLHW RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+

+

+

+








/wBestmptLackDlHRabEstAttepmNoFailed*100






introduced.

KPI Description This KPI highlights the percentage of failed RAB establishments due to exceeding the configured connection limit when allocating DL Hardware over the total of RAB establishment failures due to other reasons. The pmNoFailedRabEstAttemptLackUlAse, pmNoFailedRabEstAttemptLackDlAse, pmNoFailedRabEstAttemptLackDlChnlCode, pmNoFailedRabEstAttemptLackDlPwr, pmNoFailedRabEstAttemptLackUlHwBest, pmNoFailedRabEstAttemptLackDlHwBest counters are stepped when admission control fails with reject reason lack respectively of UL ASE, DL ASE, DL channelization codes, DL power, RBS UL HW and RBS DL HW. The pmNoFailedRabEstAttemptExceedConnLimit counter is stepped when admission control fails with reject reason value SF8, SF16, or SF32. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





8.4 Congestion Control

8.4.1 Congestion Time UL

KPI Name: UL_CONG_TIME RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: Peg Target Value:


[ ]interval TimegeUlCellConpmTotalTim

Units: % Note:

KPI Description This KPI defines the percentage of time a cell has been congested in UL over the total period of measurement (in seconds). The pmTotalTimeUlCellCong counters defines the total amount of time (sec) a cell was congested in UL during a reporting. The counter is increased by 1 every second the cell is in congestion and it will be incremented only in the CRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation and Total Measurement Time has to be summed up for the total number of cells involved in the aggregated formula. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

8.4.2 Congestion Time DL

KPI Name: DL_CONG_TIME RNC Sw Release: P6 Importance: Medium





Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: Peg Target Value:


[ ]interval TimegeDlCellConpmTotalTim

Units: % Note:

KPI Description This KPI defines the percentage of time a cell has been congested in DL over the total period of measurement (in seconds). The pmTotalTimeDlCellCong counters defines the total amount of time (sec) a cell was congested in DL during a reporting. The counter is increased by 1 every second the cell is in congestion and it will be incremented only in the CRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation and Total Measurement Time has to be summed up for the total number of cells involved in the aggregated formula. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

8.4.3 Congestion Time HS-DSCH

KPI Name: HSDSCH_CONG_TIME RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: Peg Target Value:






[ ]interval TimerloadeHsdschOvepmTotalTim

Units: % Note: In P6, new counter pmTotalTimeHsdschOverload

has been introduced. The HS-DSCH overload detection is measured in pmHsdschOverloadDetection which indicate number of times HS-DSCH overload was detected (via Common Measurement Report). It is a new counter in P6

KPI Description

This KPI defines the percentage of time a cell has been congested in HS-DSCH over the total period of measurement (in seconds). The pmTotalTimeHsdschOverload counters defines the total amount of time (sec) a cell was congested in HS-DSCH during a reporting. The counter is increased by 1 every second the cell is in congestion and it will be incremented only in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation and Total Measurement Time has to be summed up for the total number of cells involved in the aggregated formula. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

8.4.4 Congestion Time IubLink Unavailable

KPI Name: IUBLINKUNAVAIL_CONG_TIME RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IubLink Counters Type: Peg Target Value:






[ ]interval TimeavaileIubLinkUnpmTotalTim

Units: % Note: In P6, new counter pmTotalTimeIubLinkUnavail

has been introduced. Counters is in MO class IubLink

KPI Description

This KPI defines the percentage of time a cell has been congested due to IubLink unavailable over the total period of measurement (in seconds). The pmTotalTimeIubLinkUnavail counter defines the time in seconds that the Iub link is unavailable for the NBAP Common part of the control plane due to network or node internal problems. The counter is incremented by one every second that the Iub link is unavailable for the NBAP Common part of the control plane. Note that the counter is not stepped for unavailability due to operator initiated activities (for example manual blocking of Iub link). Incremented in CRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation and Total Measurement Time has to be summed up for the total number of cells involved in the aggregated formula. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

8.4.5 Congestion Time IubLink Congested DL

KPI Name: IUBLINKCONGESTEDDL_CONG_TIME RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IubLink Counters Type: Peg Target Value:


[ ]interval TimengestedDleIubLinkCopmTotalTim





Units: % Note: In P6, new counter

pmTotalTimeiubLinkCongestedDl has been introduced. Counters is in MO class IubLink

KPI Description

This KPI defines the percentage of time a cell has been congested due to IubLink congested in the Down Link over the total period of measurement (in seconds). The pmTotalTimeIubLinkCongestedDl counter defines the time in seconds that the Iub link is congested for the NBAP Common part of the control plane.

Note that if the Iub link gets unavaliable, the counter will not be incremented any more, but the pmTotalTimeIubLinkUnavail will be incremented instead.

The counter is incremented by one every second that the Iub link is unavailable for the NBAP Common part of the control plane. Incremented in CRNC.

This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation and Total Measurement Time has to be summed up for the total number of cells involved in the aggregated formula. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

8.4.6 Congestion Time MBMS

KPI Name: MBMS_CONG_TIME RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: MbmsCch Counters Type: Peg Target Value:


[ ]interval TimeTimeCongestionpmMbmsCell

*100

Units: %





Note: In P6 MBMS service has been introduced

KPI Description This KPI defines the percentage of time a cell has been congested in MBMS session over the total period of measurement (in seconds). The pmMbmsCellCongestionTime counters defines the total amount of time (sec) a cell as long as there is any MBMS session that is not started in the cell and the cell is a PL cell for any of those MBMS sessions. The counter is increased by 1 every second the cell is in congestion and it will be incremented only in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation and Total Measurement Time has to be summed up for the total number of cells involved in the aggregated formula. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

8.4.7 Congestion Control Triggered UL

KPI Name: UL_CONG_TIMES RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: Peg Target Value:

KPI Recommended Formula esMeasOlUlpmSumOfTim

Units: Events Note:

KPI Description This KPI defines the number of times Congestion Control is triggered due to high UL interference. The pmSumOfTimesMeasOlUl counter is increased if congestion control function detects UL congestion. It is done by monitoring NBAP Common Measurement Reports for each cell to see if the UL power is above a threshold. If the cell is already in a "UL congestion state", the counter is not increased. The counter is





increased for cells controlled by this RNC. This KPI can be computed on a per RNC basis as well as a per cell basis.

8.4.8 Congestion Control Triggered DL

KPI Name: DL_CONG_TIMES RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: Peg Target Value:

KPI Recommended Formula esMeasOlDlpmSumOfTim

Units: Events Note:

KPI Description This KPI defines the number of times Congestion Control is triggered due to high DL power. The pmSumOfTimesMeasOlDl counter is increased if congestion control function detects DL congestion. It is done by monitoring NBAP Common Measurement Reports for each cell to see if the DL power is above a threshold. If the cell is already in a "DL congestion state", the counter is not increased. The counter is increased for cells controlled by this RNC. This KPI can be computed on a per RNC basis as well as a per cell basis.

8.4.9 Release Cs Data Connection

KPI Name: CS_CONG_REL RNC Sw Release: P6 Importance: Medium





Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: Peg Target Value:


ermsCsCongpmNoOfIurT CsCongpmNoOfTerm +

Units: Events Note:

KPI Description This KPI defines the number circuit-switched data Radio Connections served by this and another RNC terminated due to congestion. The pmNoOfTermCsCong and pmNoOfIurTermCsCong counters are increased when a UE using the CS data service is released due to cell congestion. The counters are increased in CRNC respectively for non-drifting and drifting UEs for the one cell with congestion. This KPI can be computed on a per RNC basis as well as a per cell basis.

8.4.10 Downgraded PS Data Connections Cong

KPI Name: PS_CONG_REL RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: Peg Target Value:


gwDownNgConpmNoOfIurS wnNgCongpmNoOfSwDo +

Units: Events Note:

In P6, the counter pmNoOfSwDownNgCong is





stepped per connection instead of per RAB (applies to the 2 and 3 times interactive case) in order to align its behavior with the corresponding counter pmNoOfIurSwDownNgCong.

KPI Description

This KPI defines the non-guaranteed users served by this and another RNC switched down to common or terminated due to congestion. The pmNoOfSwDownNgCong and pmNoOfIurSwDownNgCong counters UE using the best effort PS data service is switched down to common channel or released due to cell congestion. The counters are increased in CRNC respectively for non-drifting and drifting UEs for the one cell with congestion. There is a parameter that can make PS data on common channel not allowed for the whole RNC. If that parameter is set, this counter will show number of UEs released due to congestion since the connection shall be released instead of being switched to common channel. This KPI can be computed on a per RNC basis as well as a per cell basis.

8.4.11 Downgraded PS Data Connections Adm

KPI Name: PS_CONG_DOWNS_ADM RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: Peg Target Value:


dmwnNgpmNoOfSwDo A

Units: Events Note:

KPI Description This KPI defines the number of downswitches initiated from admission control for non-guaranteed users served by this RNC The pmNoOfSwDownNgAdm counter is incremented at downswitching from Cell_DCH 64/384–>64/128 or Cell_DCH 64/128–>64/64 initiated by admission





control to do Best Effort Cleanup. This is done after an admission rejection due to insufficient downlink power or code utilization limits. The connection to switch down is selected if it is a non-guaranteed and non-drifting connection with a lower spreading factor than that of the latest requested RL. The counter is increased in the cell which had to reject admission. If the UE is in macrodiversity the counter is not stepped in the other cells. Note that this counter is never stepped if there is inter-frequency load sharing. This KPI can be computed on a per RNC basis as well as a per cell basis.

8.4.12 Downgraded PS Data Connections HO

KPI Name: PS_CONG_DOWNS_HO RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: Peg Target Value:


wnNgHopmNoOfSwDo

Units: Events Note:

KPI Description This KPI defines the number of downswitch requests for non-guaranteed users served by this RNC due to handover. The pmNoOfSwDownNgHo counter is updated at channel switching attempts from Cell_DCH 64/384 to Cell_DCH 64/64, from Cell_DCH 64/128 to Cell_DCH 64/64 and for Cell_DCH CS speech 12.2 + SP64/64 to Cell_DCH CS speech 12.2 + SP0/0 due to soft/softer handover. An internal trigger is sent to initiate the channel switch if admission is rejected at addition of an RL to the active set. The counter is increased for the Best Cell in the Active Set in the S-RNC where the UE is located, if the UE is in macro diversity. The counter is not stepped for cells in the D-RNC. This KPI can be computed on a per RNC basis as well as a per cell basis.





8.4.13 Release Speech Connection

KPI Name: SPEECH_CONG_REL RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: Peg Target Value:


CongermsSpeechpmNoOfIurT SpeechCongpmNoOfTerm +

Units: Events Note:

KPI Description This KPI defines the number of Speech Radio Connections served by this and another RNC terminated due to congestion. The pmNoOfTermSpeechCong and pmNoOfIurTermSpeechCong counters are increased when a UE using the speech service is released due to cell congestion. The counters are increased in CRNC respectively for non-drifting and drifting UEs for the one cell with congestion. This KPI can be computed on a per RNC basis as well as a per cell basis.

8.4.14 Congestion Soft Downswitch HS

KPI Name: HS_CONG_DOWNS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:






wnHsCongpmNoOfSwDo

Units: Note:

KPI Description The counter pmNoOfSwDownHsCong is the number of Radio Connections served by an RNC, including an HSDPA service, which are channel switched down due to a congestion resolve action initiated on a serving Ue Context.

8.4.15 Congestion Soft Downswitch EUL

KPI Name: EUL_CONG_DOWNS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


wnEulCongpmNoOfSwDo

Units: Note:

KPI Description The counter pmNoOfSwDownEulCong is the number of E-DCH users served by an RNC, which are down-switched due to DL congestion in both EUL serving cell and EUL non-serving cell.





8.5 Traffic and Load

8.5.1 RNC Main Processor Load

KPI Name: RNC_MP_LOAD RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: LoadControl Counters Type: Acc, Scan Target Value:


deasuredLoapmSamplesMredLoadpmSumMeasu

Units: % Note:

KPI Description This KPI defines the percentage of load of RNC Main Processor. It is calculated as the rate between Accumulator and Scan counters: the first one is the sums of all sample values, collected every 30 seconds; the second one is the relative number of samples within the ROP period. The pmSamplesMeasuredLoad counter is incremented by 1 at every sample of the processor load. The processor load is sampled once every 30 seconds. The pmSumMeasuredLoad counter is incremented by the sampled load, every time the processor load is sampled. This KPI can be computed only a per RNC basis.

8.5.2 RNC Main Processor Load Distribution

KPI Name: RNC_MP_LOAD RNC Sw Release: P6 Importance: Medium





Scope: RNC Granularity: ROP – 15’ Time Resolution: Counters MO Class: LoadControl Counters Type: PDF Target Value:


LoadpmMeasured Units: % Note:

KPI Description This KPI defines Processor load.

Reported according to the following intervals: [0] : 0 <= x < 20 (%) [1] : 20 <= x < 30 [2] : 30 <= x < 40 [3] : 40 <= x < 50 [4] : 50 <= x < 60 [5] : 60 <= x < 70 [6] : 70 <= x < 80 [7] : 80 <= x

Incremented by one when a sample is within its range. Sampling Rate: 1 second. This KPI can be computed only a per RNC basis.





9 Mobility Intra Frequency Handover

9.1 Successful RL Addition

9.1.1 Successful RL Addition Source Best Cell Speech

KPI Name: SHO_SUCC_SPEECH_UR RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )ellSpeechemptsBestCpmRlAddAtt /llSpeechcessBestCepmRlAddSuc * 100

Units: % Note: In P6 counters stepped in SRNC, DRNC if


KPI Description The KPI defines the success rate for Speech RL addition, defined for the source best cell in the active set. It is calculated as the rate between the sum of RL addition success for speech RAB and the sum of RL addition attempts for speech RAB. The pmRlAddSuccessBestCellSpeech counter is increased when a new RL is attempted to be added to an active set for a CS Speech RAB. The counter is increased after a handover proposal has been received from the handover evaluation function or an RNSAP Radio Link Addition Request has been received, admission control has been granted, DL channelization code has been allocated for the new cell, RL Setup or RL Addition procedure is successfully completed with the RBS, the Active Set Update procedure is successfully completed with the UE, the necessary ATM resources have been set up between RBS and RNC, and the appropriate parameters are available. The pmRlAddAttemptsBestCellSpeech counter is increased when a new RL is attempted to be added to an active set for a CS Speech RAB. The counter is increased after a handover proposal has been received from the handover evaluation function or an RNSAP Radio Link Addition Request has been received. All these counters only monitor RLs for cells in the SRNC. If an RL is replaced in an active set, this counter is also stepped.






9.1.2 Successful RL Addition Source Best Cell CS64

KPI Name: SHO_SUCC_CS_CONV_UR RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )rsellCsConveemptsBestCpmRlAddAtt /sllCsConvercessBestCepmRlAddSuc * 100



KPI Description The KPI defines the success rate for RL addition, defined for the source best cell in the active set. It is calculated as the rate between the sum of RL addition success for CS64 conversational RABs and the sum of RL addition attempts for CS64 conversational RABs. The pmRlAddSuccessBestCellCsConvers counter is increased when a new RL is attempted to be added to an active set for a conversational CS64 RAB. The counter is increased after a handover proposal has been received from the handover evaluation function or an RNSAP Radio Link Addition Request has been received, admission control has been granted, DL channelization code has been allocated for the new cell, RL Setup or RL Addition procedure is successfully completed with the RBS, the Active Set Update procedure is successfully completed with the UE, the necessary ATM resources have been set up between RBS and RNC, and the appropriate parameters are available. The pmRlAddAttemptsBestCellCsConvers counter is increased when a new RL is attempted to be added to an active set for conversational CS 64 RAB. The counter is increased after a handover proposal has been received from the handover evaluation function or an RNSAP Radio Link





Addition Request has been received. This counter only monitors RLs for cells in the SRNC. If an RL is replaced in an active set, this counter is also stepped. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

9.1.3 Successful RL Addition Source Best Cell Packet Low

KPI Name: SHO_SUCC_PS_LOW_UR RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )owellPacketLemptsBestCpmRlAddAtt /wllPacketLocessBestCepmRlAddSuc * 100



KPI Description The KPI defines the success rate for RL addition, defined for the source best cell in the active set. It is calculated as the rate between the sum of RL addition success for Packet 64/64, Speech + packet 64Kbps and PS Streaming RABs and the sum of RL addition attempts for Packet 64/64, Speech + packet 64Kbps and PS Streaming RABs. The pmRlAddSuccessBestCellPacketLow counter is increased when a new RL is attempted to be added to an active set for a PS with a data rate of 64 kbps or less (also stepped for PS streaming + 8 kbps) RAB. The counter is increased after a handover proposal has been received from the handover evaluation function or an RNSAP Radio Link Addition Request has been received, admission control has been granted, DL channelization code has been allocated for the new cell, RL Setup or RL Addition procedure is successfully completed with the RBS, the Active Set Update procedure is successfully completed with the UE, the necessary ATM resources have been set up between RBS and RNC, and the appropriate





parameters are available. The pmRlAddAttemptsBestCellPacketLow counter is increased when a new RL is attempted to be added to an active set for a PS with a data rate of 64 kbps or less (also stepped for PS streaming + 8 kbps) RAB. The counter is increased after a handover proposal has been received from the handover evaluation function or an RNSAP Radio Link Addition Request has been received. All these counters only monitor RLs for cells in the SRNC. If an RL is replaced in an active set, this counter is also stepped. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

9.1.4 Successful RL Addition Source Best Cell Packet High

KPI Name: SHO_SUCC_PS_HIGH_UR RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )acketHighemptsBestPpmRlAddAtt /ghllPacketHicessBestCepmRlAddSuc * 100



KPI Description The KPI defines the success rate for RL addition high-rate packet RABs (radio connections in states with high-rate packet connections: Packet64_128 and Packet64_384), defined for the source best cell in the active set. It is calculated as the rate between the sum of RL addition success for PS with a data rate of greater that 64 kbps RABs and the sum of RL addition attempts for PS with a data rate of greater that 64 kbps RABs. The pmRlAddSuccessBestCellPacketHigh counter is increased when a new RL is attempted to be added to an active set for a PS with a data rate of greater that 64 kbps RAB. The counter is increased after a handover proposal has been received





from the handover evaluation function or an RNSAP Radio Link Addition Request has been received, admission control has been granted, DL channelization code has been allocated for the new cell, RL Setup or RL Addition procedure is successfully completed with the RBS, the Active Set Update procedure is successfully completed with the UE, the necessary ATM resources have been set up between RBS and RNC, and the appropriate parameters are available. The pmRlAddAttemptsBestCellPacketHigh counter is increased when a new RL is attempted to be added to an active set for a PS with a data rate of greater that 64 kbps RAB. The counter is increased after a handover proposal has been received from the handover evaluation function or an RNSAP Radio Link Addition Request has been received. All these counters only monitor RLs for cells in the SRNC. If an RL is replaced in an active set, this counter is also stepped. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

9.1.5 Successful RL Addition Source Best Cell Streaming

KPI Name: SHO_SUCC_CS_STREAM_UR RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )ellStreamemptsBestCpmRlAddAtt /llStreamcessBestCepmRlAddSuc * 100



KPI Description The KPI defines the success rate for radio link additions succeeded for streaming RABs (radio connections in states with streaming connections: 57kpbs CS data, variable rate; PS Streaming 16/64 + Packet 8kpbs; and PS Streaming 16/128 + Packet 8kbps).





The pmRlAddSuccessBestCellStream counter is incremented by one when a new RL is successfully added to an active set for streaming RABs (radio connections in states with streaming connections: 57kpbs CS data, variable rate, PS Streaming 16/64 + Packet 8kpbs and PS Streaming 16/128 + Packet 8kpbs). The counter is incremented after a Radio Link Addition Response is received. The counter only monitors RLs for cells in the SRNC. The counter is incremented if an RL is replaced in an active set. The counter is only incremented if there is a neighbor cell relation from the current best cell in the Active Set to the cell that has just been added

The pmRlAddAttemptsBestCellStream counter is incremented by one when a new RL is attempted to be added to an active set for streaming RABs (radio connections in states with streaming connections: 57 kpbs CS data, variable rate, PS Streaming 16/64 + Packet 8kpbs and PS Streaming 16/128 + Packet 8kpbs). The counter is incremented after a handover proposal has been received from the handover evaluation function. The counter only monitors RLs for cells in the SRNC. The counter is incremented if an RL is replaced in an active set. Note: The counter is incremented if there is a neighbor cell relation from the current best cell in the Active Set to the cell that is attempted to be added This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

9.1.6 Successful RL Addition Source Best Cell Stand Alone

KPI Name: SHO_SUCC_SRB_UR RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )oneellStandAlemptsBestCpmRlAddAtt /nellStandAlocessBestCepmRlAddSuc * 100







KPI Description The KPI defines the success rate for RL addition, defined for the source best cell in the active set. It is calculated as the rate between the sum of RL addition success for RRC only connection and the sum of RL addition attempts for RRC only connection. The pmRlAddSuccessBestCellStandAlone counter is increased when a new RL is attempted to be added to an active set for a RRC only connection. The counter is increased after a handover proposal has been received from the handover evaluation function or an RNSAP Radio Link Addition Request has been received, admission control has been granted, DL channelization code has been allocated for the new cell, RL Setup or RL Addition procedure is successfully completed with the RBS, the Active Set Update procedure is successfully completed with the UE, the necessary ATM resources have been set up between RBS and RNC, and the appropriate parameters are available. The pmRlAddAttemptsBestCellStandAlone counter is increased when a new RL is attempted to be added to an active set for a RRC only connection. The counter is increased after a handover proposal has been received from the handover evaluation function or an RNSAP Radio Link Addition Request has been received. All these counters only monitor RLs for cells in the SRNC. If an RL is replaced in an active set, this counter is also stepped. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

9.1.7 Successful RL Addition Target Cell

KPI Name: SHOSUCCESSRATE RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )ToActSetellFailAddpmNoTimesC et lAddToActSpmNoTimesRetlAddToActSpmNoTimesR

* 100+

Units: %





Note: In P6 counters stepped in SRNC, DRNC if IurLink::srncPmReporting = ON in SRNC

KPI Description

The KPI defines the rate of successful Radio Link addition for the target cell, computed for RL addition or replacement. It is calculated as the rate between the total number of RL addition success and the total number of RL addition attempts, defined as the sum of success and failures. The pmNoTimesRlAddToActSet counter is increased when a new RL is successfully added to an active set. The counter is increased after a handover proposal has been received from the handover evaluation function, admission control has been granted, DL channelization code has been allocated for the new cell, RL Setup or RL Addition procedure is successfully completed with the RBS (NBAP RL Setup Response or RL Addition Response received), the Active Set Update procedure is successfully completed with the UE (RRC Active Set Update Complete received), and the appropriate parameters are available. If an RL is replaced in an active set, this counter is increased for the cell which is added. While the pmNoTimesCellFailAddToActSet counter is increased if, during an attempt to add an RL, any of the following occur: admission is not granted, no DL channelization code is allocated, the RL Setup procedure fails (NBAP RL Setup Failure received), RL Addition procedure fails (NBAP RL Addition Failure received), RL Setup or Addition procedure times out in the RBS, the Active Set Update procedure fails (RRC Active Set Update Failure received) or Active Set Update procedure times out in the UE. It affects cells which can not enter into the active set. Note that both counters only monitor UEs in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





9.2 Soft/Softer Handover Overhead

9.2.1 Soft/Softer Handover Overhead Speech

KPI Name: SHO_OVERHEAD_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC Target Value:


⎟⎠⎞⎜

⎝⎛ − 1

EECHTRAFFIC_SPERS_SPEECHAVERAGE_US

* 100

Units: % Note:

KPI Description The KPI defines the percentage of soft HO overhead, calculated as the rate between the average number of active Speech RAB connections, in the ROP period, and traffic value (in Erlangs) for RABs Speech (including MultiRab). Please refer to the section about Traffic and capacity respectively for a more detailed description of TRAFFIC_SPEECH and AVERAGE_USERS_SPEECH. Note that both terms of the formula are measuring analog values with the difference that the numbers at the denominator are referred only to the best cell in the Active Set, while ones at the numerator give the average number of single RLs for the specific RAB. The rate between these clearly defines the overhead contribution due to soft/softer HO. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





9.2.2 Soft/Softer Handover Overhead AMR-NB

KPI Name: SHO_OVERHEAD_AMR-NB RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


⎟⎠⎞⎜

⎝⎛ − 1

RNBTRAFFIC_AMERS_AMRNBAVERAGE_US

* 100

Units: % Note:

KPI Description The KPI defines the percentage of soft HO overhead, calculated as the rate between the average number of active AMR-NB RAB connections, in the ROP period, and traffic value (in Erlangs) for RABs AMR-NB (including MultiRab). Please refer to the section about Traffic and capacity respectively for a more detailed description of TRAFFIC_AMR-NB and AVERAGE_USERS_ AMR-NB. Note that both terms of the formula are measuring analog values with the difference that the numbers at the denominator are referred only to the best cell in the Active Set, while ones at the numerator give the average number of single RLs for the specific RAB. The rate between these clearly defines the overhead contribution due to soft/softer HO. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

9.2.3 Soft/Softer Handover Overhead AMR-WB

KPI Name: SHO_OVERHEAD_AMRWB





RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


⎟⎠⎞⎜

⎝⎛ − 1

RWBTRAFFIC_AMERS_AMRWBAVERAGE_US

* 100

Units: % Note:

KPI Description The KPI defines the percentage of soft HO overhead, calculated as the rate between the average number of active AMR-WB RAB connections, in the ROP period, and traffic value (in Erlangs) for RABs AMR-WB (including MultiRab). Please refer to the section about Traffic and capacity respectively for a more detailed description of TRAFFIC_AMRWB and AVERAGE_USERS_ AMRWB. Note that both terms of the formula are measuring analog values with the difference that the numbers at the denominator are referred only to the best cell in the Active Set, while ones at the numerator give the average number of single RLs for the specific RAB. The rate between these clearly defines the overhead contribution due to soft/softer HO. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

9.2.4 Soft/Softer Handover Overhead CS Streaming Data

KPI Name: SHO_OVERHEAD_CSDATA RNC Sw Release: P6 Importance: Medium Scope: Cell





Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC Target Value:


⎟⎠⎞⎜

⎝⎛ − 1

TA_STREAM_DATRAFFIC_CSEAM_DATAERS_CS_STRAVERAGE_US

* 100

Units: % Note:

KPI Description The KPI defines the percentage of soft HO overhead, calculated as the rate between the average number of active CS57 Streaming RAB connections, in the ROP period, and traffic value (in Erlangs) for RABs CS57 Streaming (including MultiRab). Please refer to the section about Traffic and capacity respectively for a more detailed description of TRAFFIC_CS_STREAM_DATA and AVERAGE_USERS_CS_STREAM_DATA. Note that both terms of the formula are measuring analog values with the difference that the numbers at the denominator are referred only to the best cell in the Active Set, while ones at the numerator give the average number of single RLs for the specific RAB. The rate between these clearly defines the overhead contribution due to soft/softer HO. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

9.2.5 Soft/Softer Handover Overhead CS64 Data

KPI Name: SHO_OVERHEAD_CS64 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour





Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


⎟⎠⎞⎜

⎝⎛ − 1

64DATATRAFFIC_CSTAERS_CS64DAAVERAGE_US

* 100

Units: % Note:

KPI Description The KPI defines the percentage of soft HO overhead, calculated as the rate between the average number of active CS64 data RAB connections, in the ROP period, and traffic value (in Erlangs) for RABs CS64 data (including MultiRab). Please refer to the section about Traffic and capacity respectively for a more detailed description of TRAFFIC_CS64DATA and AVERAGE_USERS_CS64DATA. Note that both terms of the formula are measuring analog values with the difference that the numbers at the denominator are referred only to the best cell in the Active Set, while ones at the numerator give the average number of single RLs for the specific RAB. The rate between these clearly defines the overhead contribution due to soft/softer HO. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

9.2.6 Soft/Softer Handover Overhead PS64 Stream

KPI Name: SHO_OVERHEAD_PS64 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:






⎟⎠⎞⎜

⎝⎛ − 1

64_STREAMTRAFFIC_PSTREAMERS_PS64_SAVERAGE_US

* 100

Units: % Note:

KPI Description The KPI defines the percentage of soft HO overhead, calculated as the rate between the average number of active PS64 Streaming RAB connections, in the ROP period, and traffic value (in Erlangs) for RABs PS64 Streaming (including MultiRab). Please refer to the section about Traffic and capacity respectively for a more detailed description of TRAFFIC_PS64_STREAM and AVERAGE_USERS_PS64_STREAM. Note that both terms of the formula are measuring analog values with the difference that the numbers at the denominator are referred only to the best cell in the Active Set, while ones at the numerator give the average number of single RLs for the specific RAB. The rate between these clearly defines the overhead contribution due to soft/softer HO. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

9.2.7 Soft/Softer Handover Overhead PS128 Stream

KPI Name: SHO_OVERHEAD_PS128 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:






⎟⎠⎞⎜

⎝⎛ − 1

128_STREAMTRAFFIC_PSSTREAMERS_PS128_AVERAGE_US

* 100

Units: % Note:

KPI Description The KPI defines the percentage of soft HO overhead, calculated as the rate between the average number of active PS128 Streaming RAB connections, in the ROP period, and traffic value (in Erlangs) for RABs PS128 Streaming (including MultiRab). Please refer to the section about Traffic and capacity respectively for a more detailed description of TRAFFIC_PS128_STREAM and AVERAGE_USERS_PS128_STREAM. Note that both terms of the formula are measuring analog values with the difference that the numbers at the denominator are referred only to the best cell in the Active Set, while ones at the numerator give the average number of single RLs for the specific RAB. The rate between these clearly defines the overhead contribution due to soft/softer HO. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

9.2.8 Soft/Softer Handover Overhead PS Data DCH/FACH

KPI Name: SHO_OVERHEAD_PS_DCH/FACH RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:






⎟⎠⎞⎜

⎝⎛ − 1

CHDATA_DCHFATRAFFIC_PS_DCHFACHERS_PSDATAAVERAGE_US

* 100

Units: % Note:

KPI Description The KPI defines the percentage of soft HO overhead, calculated as the rate between the average number of active PS Data RAB connections on DCH and FACH, in the ROP period, and traffic value (in Erlangs) for RABs PS Data (including MultiRab) on DCH and FACH. Please refer to the section about Traffic and capacity respectively for a more detailed description of TRAFFIC_PSDATA_DCHFACH and AVERAGE_USERS_PSDATA_DCHFACH. Note that both terms of the formula are measuring analog values with the difference that the numbers at the denominator are referred only to the best cell in the Active Set, while ones at the numerator give the average number of single RLs for the specific RAB. The rate between these clearly defines the overhead contribution due to soft/softer HO. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

9.2.9 RL Soft/Softer Handover Overhead

KPI Name: RL_SHO_OVERHEAD RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC Target Value:






⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+

+

++

+

+

+

+

+

+

nActSetth3Rls3RlIpmSumUesWi



31



21


/







* 100

Units: % Note:

KPI Description The KPI defines the percentage of overhead due to soft and softer HO. It is, calculated as the rate between the total number of active RL and the same value decreased by soft and softer HO contribution. Both terms are calculated as the sum of Accumulator counters because, since the relative Scanner counters assume the same values, the formula can be simplified. The pmSumUesWithiRlsjRlInActSet counter contains the sum of all the snapshot values (of the total number of UEs with i RL set and j RL in the active set) taken in a ROP period added together. It is based on an internal level counter which is maintained by RNC. Values are read periodically, every minute, from the internal level counter. Each read results in the pmSamples counter being increased by one, and the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of the number UEs with i RL set and j RLs in the active set at any given instant in time, that is the counter can be decreased or increased. The level counter is updated by RRC Connection Setup, RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, RAB Establishment, RAB Release, Inter-frequency Handover, Channel Switching, Soft and Softer Handover. All of them are defined accordingly to the following table:

Note that, in this case, the formula has been defined only supposing maximum 3 RLs in active set.






9.2.10 RL Soft Only Handover Overhead

KPI Name: RL_SHO_OVERHEAD_SOFTONLY RNC Sw Release: P6 Importance: High Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC Target Value:


⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+

+

++

+

+

+

+

+

+




31



21


/


nActSetth2Rls3RlIpmSumUesWi32





* 100

Units: % Note:

KPI Description The KPI defines the percentage of overhead due only to soft HO. It is, calculated as the rate between the total number of active RL and the same value decreased by soft HO contribution. Both terms are calculated as the sum of Accumulator counters because, since the relative Scanner counters assume the same values, the formula can be simplified. The pmSumUesWithiRlsjRlInActSet counter contains the sum of all the snapshot values (of the total number of UEs with i RL set and j RL in the active set) taken in a





ROP period added together. It is based on an internal level counter which is maintained by RNC. Values are read periodically, every minute, from the internal level counter. Each read results in the pmSamples counter being increased by one, and the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of the number UEs with i RL set and j RLs in the active set at any given instant in time, that is the counter can be decreased or increased. The level counter is updated by RRC Connection Setup, RRC Connection Release, Inter-RAT Handover GSM to UTRAN, Inter-RAT Handover UTRAN to GSM, RAB Establishment, RAB Release, Inter-frequency Handover, Channel Switching, Soft and Softer Handover. All of them are defined accordingly to the following table:

Note that, in this case, the formula has been defined only supposing maximum 3 RLs in active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





9.3 Cell Update

9.3.1 Cell Update Success Rate

KPI Name: CELLUPD_SUCC_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


dAttemptpmNoCellUpdSuccesspmNoCellUp

* 100

Units: % Note:

KPI Description The KPI defines the success rate for Cell Update. It calculated as the rate between the total number of successful cell updates and the total number of attempted cell update procedures (periodic and cell reselection, that is RRC Cell Update message received with Cell Update Cause =Cell Reselection or Periodic Cell Update) The pmNoCellUpdAttempt counter is increased when the RRC message Cell Update is received in the SRNC with a valid U-RNTI (the UE is known in SRNC) after an integrity check is passed and the message is decoded. The counter is increased only if the cause value equals PERIODIC UPDATE or CELL RE-SELECTION and the counter is increased for the cell where the Cell Update message was received (in the new cell if it has changed). The pmNoCellUpdSuccess counter is increased in two cases: a) At cell re-selection. A new C-RNTI is assigned and a Cell Update Confirm message is sent. The counter is stepped when the UTRAN Mobility Information Confirm message is received from the UE. The counter is stepped for the cell that received the Cell Update Confirm message (in the new cell if it has changed). b) At periodic update. The counter is stepped when a Cell Update Confirm is received. The counter is stepped in the cell that received the Cell Update Confirm message. These cell update procedures can happen at cell update in the same cell (periodic update), cell update in a new cell (cell reselection), cell update during channel switching and cell update during RAB establishment. The cases when an AM RLC





error is detected at decoding are NOT counted. Note that only if the UE is non-drifting, or coming back from a DRNC, the counters can be increased. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





9.4 URA Update

9.4.1 URA Update Success Rate

KPI Name: URA_UPD_SUCC_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


AttemptpmNoUraUpdSuccesspmNoUraUpd

* 100

Units: % Note:

KPI Description The KPI defines the success rate of URA updates, defined as the ratio between the number of successful URA updates and the number of attempted URA updates. The counters pmNoUraUpdAttempt and pmNoUraUpdSuccess are increased respectively relatively for every attempted URA update and for every successful URA update. These counters are only incremented in the SRNC.





9.5 Core Network Hard Handover

9.5.1 CN Hard HO Outgoing Success Rate Speech

KPI Name: CN_HHO_SUCC_RATE_OUT_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranRelation Counters Type: PEG Target Value:


hCnhhoSpeecpmNoAttOutchtCnhhoSpeepmNoSuccOu

* 100

Units: % Note: In P6, counters stepped in SRNC, DRNC if


KPI Description The KPI defines the success rate of core network outgoing hard handover, for speech RAB. The counter pmNoSuccOutCnhhoSpeech provides the number of successful outgoing CN Hard Handover for speech RAB. When there are more than one cell in AS, the counter is stepped in the best cell. The counter is stepped at RANAP Iu Release Command with cause value ’Successful Relocation’ or ’Normal Release’. The counter pmNoAttOutCnhhoSpeech provides the number of attempts to perform an outgoing CN Hard Handover for speech RAB. When there are more than one cell in AS, the counter is stepped in the best cell. The counter is stepped when RRC Radio Bearer Reconfiguration, Physical Channel Reconfiguration, Transport Channel Reconfiguration, Radio Bearer Setup or Radio Bearer Release is sent.

9.5.2 CN Hard HO Outgoing Success Rate CS Non-speech

KPI Name: CN_HHO_SUCC_RATE_OUT_NSPEECH RNC Sw Release: P5





Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranRelation Counters Type: PEG Target Value:


SpeechCnhhoCsNonpmNoAttOutnSpeechtCnhhoCsNopmNoSuccOu

* 100



KPI Description The KPI defines the success rate of core network outgoing hard handover, for CS RAB, other than speech. The counter pmNoSuccOutCnhhoCsNonSpeech provides the number of successful outgoing CN Hard Handover for CS RAB, other than speech. When there are more than one cell in AS, the counter is stepped in the best cell. The counter is stepped at RANAP Iu Release Command with cause value ’Successful Relocation’ or ’Normal Release’. The counter pmNoAttOutCnhhoCsNonSpeech provides the number of attempts to perform an outgoing CN Hard Handover for CS RAB, other than speech. When there are more than one cell in AS, the counter is stepped in the best cell. The counter is stepped when RRC Radio Bearer Reconfiguration, Physical Channel Reconfiguration, Transport Channel Reconfiguration, Radio Bearer Setup or Radio Bearer Release is sent.

9.5.3 CN Hard HO Incoming Success Rate Speech

KPI Name: CN_HHO_SUCC_RATE_IN_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IurLink Counters Type: PEG





Target Value:


hCnhhoSpeecpmNoAttIncchcCnhhoSpeepmNoSuccIn

* 100



KPI Description The KPI defines the success rate of core network Incoming hard handover, for speech RAB. The counter pmNoSuccIncCnhhoSpeech provides the number of successful incoming CN Hard Handover for speech RAB. The counter is stepped when RRC Radio Bearer Reconfiguration Complete is received. The counter pmNoAttIncCnhhoSpeech provides the number of attempts to perform incoming CN Hard Handover for a speech RAB. The counter shall be stepped when: RANAP Relocation Request Acknowledge is sent.

9.5.4 CN Hard HO CS Incoming Success Rate Non-speech

KPI Name: CN_HHO_SUCC_RATE_IN_NSPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IurLink Counters Type: PEG Target Value:


SpeechCnhhoCsNonpmNoAttIncnSpeechcCnhhoCsNopmNoSuccIn

* 100







KPI Description The KPI defines the success rate of core network Incoming hard handover, for CS RAB, other than speech. The counter pmNoSuccIncCnhhoCsNonSpeech provides the number of successful incoming CN Hard Handover for a CS RAB (other than Speech). The counter is stepped when RRC Radio Bearer Reconfiguration Complete is received. The counter pmNoAttIncCnhhoCsNonSpeech provides the number of attempts to perform incoming CN Hard Handover for a CS RAB (other than speech). The counter shall be stepped when: RANAP Relocation Request Acknowledge is sent.





10 Mobility IRAT Handover

10.1 Compressed Mode

10.1.1 CM DL Activation Success Rate

KPI Name: CM_ATT_DL RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )( )f2pmCmAttDlS lspmCmAttDlH

Sf2pmCmSuccDl HlspmCmSuccDl * 100

+

+

Units: % Note:

KPI Description The KPI defines the success rate for DL CM starts. It calculated as the rate between the total number of successful CM starts for DL (Hls + Sf/2 method) and the total number of attempted CM starts for DL (Hls + Sf/2 method). The pmCmAttDlSf2, pmCmAttDlHls, pmCmSuccDlSf2 and pmCmSuccDlHls counters can be stepped in several scenarios: 1) Handover evaluation decides to start Inter-RAT or Inter-frequency measurements, and consequently initialize compressed mode. Respectively the SF/2 or the HLS CPM method is selected, based on established RAB and configured selection criteria. The counter is increased for every cell in the Active Set in the SRNC, respectively for the first two counters when the NBAP RL RECONFIGURATION READY message is received from RBS indicating a successful RL reconfiguration in RBS or respectively for the second two when the NBAP RADIO LINK RECONFIGURATION COMMIT is sent to the RBS after a successful reconfiguration of the physical channel in the UE. 2) During Soft Handover when a RL is added and Compressed Mode is already active. The counter is increased for each added cell in the Active Set in the SRNC, respectively for the first two counters after a successful RL establishment in RBS when the RRC ACTIVE SET UPDATE is sent to the UE and respectively for the





second two counters after the RRC ACTIVE SET UPDATE COMPLETE message is received from the UE indicating a successful active set update. 3) At channel switching between dedicated channels when the compressed mode method is changed due to a new radio connection state. The counter is increased for every cell in the Active Set in the SRNC, respectively for the first two counters when the RRC TRANSPORT CHANNEL RECONFIGURATION message is sent to the UE after a successful RL reconfiguration in RBS and respectively for the second two counters after the RRC TRANSPORT CHANNEL RECONFIGURATION COMPLETE message is received from the UE indicating successful reconfiguration of the transport channel in the UE. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.1.2 CM UL Activation Success Rate

KPI Name: CM_ATT_UL RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )( )f2pmCmAttUlS lspmCmAttUlH

Sf2pmCmSuccUl HlspmCmSuccUl * 100

+

+

Units: % Note:

KPI Description The KPI defines the success rate for UL CM starts. It calculated as the rate between the total number of successful CM starts for UL (Hls + Sf/2 method) and the total number of attempted CM starts for UL (Hls + Sf/2 method). The pmCmAttUlSf2, pmCmAttUlHls, pmCmSuccUlSf2 and pmCmSuccUlHls counters can be stepped in several scenarios: 1) Handover evaluation decides to start Inter-RAT or Inter-frequency





measurements, and consequently initialize compressed mode. Respectively the SF/2 or the HLS CPM method is selected, based on established RAB and configured selection criteria. The counter is increased for every cell in the Active Set in the SRNC, respectively for the first two counters when the NBAP RL RECONFIGURATION READY message is received from RBS indicating a successful RL reconfiguration in RBS or respectively for the second two when the NBAP RADIO LINK RECONFIGURATION COMMIT is sent to the RBS after a successful reconfiguration of the physical channel in the UE. 2) During Soft Handover when a RL is added and Compressed Mode is already active. The counter is increased for each added cell in the Active Set in the SRNC, respectively for the first two counters after a successful RL establishment in RBS when the RRC ACTIVE SET UPDATE is sent to the UE and respectively for the second two counters after the RRC ACTIVE SET UPDATE COMPLETE message is received from the UE indicating a successful active set update. 3) At channel switching between dedicated channels when the compressed mode method is changed due to a new radio connection state. The counter is increased for every cell in the Active Set in the SRNC, respectively for the first two counters when the RRC TRANSPORT CHANNEL RECONFIGURATION message is sent to the UE after a successful RL reconfiguration in RBS and respectively for the second two counters after the RRC TRANSPORT CHANNEL RECONFIGURATION COMPLETE message is received from the UE indicating successful reconfiguration of the transport channel in the UE. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.1.3 CM Alternative SC Usage

KPI Name: CM_ALT_SC_USAGE RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


emptCmdeAllocAttpmNoDlChCoCodeCmdeAllocAltpmNoDlChCo

* 100





Units: % Note:

KPI Description The KPI defines the percentage of attempted allocations with alternative scrambling code for compressed mode over the total number of attempts. The pmNoDlChCodeAllocAttemptCm counter is increased when there is a request to allocate either a normal or alternative DL channelization code for a UE with compressed mode. While the pmNoDlChCodeAllocAltCodeCm counter is increased when there is a request to allocate only an alternative DL channelization code for a UE with compressed mode. Both counters are increased in the cell where the channelization code is requested. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.1.4 CM Measurement Ratio

KPI Name: IRAT_MEAS_NOCM_FRACTION RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


( )rtmMeasCmStapmIratHoGs tart mMeasNoCmSpmIratHoGstartmMeasNoCmSpmIratHoGs

* 100+

Units: % Note:

KPI Description The KPI defines the percentage of GSM measurements start (without use of Compressed Mode) over the total number of GSM measurements start.





The RNC instructs the UE to start GSM measurements in preparation for a possible Inter-RAT (GSM) Handover / (GPRS) Cell Change due to poor radio quality. The UE sends a Measurement Report message with event 2d. Event id 2d is identified. The measurement handling algorithm is initiated. If the UE measures GSM frequencies relatively using Compressed Mode step or without using Compressed Mode step, the counter pmIratHoGsmMeasCmStart or pmIratHoGsmMeasNoCmStart are increased, when the Measurement Control (RRC) message to setup the 3a is sent to the UE. The counters are stepped for the best cell in the Active Set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.1.5 Number of CM Users per Cell

KPI Name: AVG_NUM_CONN_CM RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: SCAN, ACC Target Value:


ompModepmSamplesC

odepmSumCompM

Units: Number of users Note:

KPI Description The KPI defines the average number of compressed mode users, reported per cell. It is calculated as the rate between Accumulator and Scan counters: the first ones are the sums of all sample values, collected every 30 seconds; the second ones are the relative number of samples within the ROP period. A snapshot of the number of compressed mode users is taken once every 30 seconds in each cell and the pmSumCompMode counter contains the sum of all





snapshot values. The pmSamplesCompMode counter is increased at every occasion when the corresponding sum counter is increased. The sampling rate is once every 30 seconds. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





10.2 CS IRAT HO

10.2.1 IRAT HO Attempt Rate

KPI Name: IRATHO_ATTEMPT_RATE RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation, UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛ +

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

++

+

rtmMeasCmStapmIratHoGs tart mMeasNoCmSpmIratHoGs

daloneIratHoStanpmNoAttOut iIratHoMultpmNoAttOut

ch IratHoSpeepmNoAttOut tCcAtt pmNoOutIra

100 / *

Units: % Note:

KPI Description The KPI defines a sort of activity factor for IRAT HO to GSM: it is a rate between all the attempts of outgoing (to GSM) IRAT HO for all the RABs (allowed to IRAT HO procedure) and all GSM measurement starts (with or without CM). During Inter-RATCC from UTRAN to GPRS with UE on DCH, the Handover evaluation function triggers this function to indicate that we need to make handover to a GSM cell. (A Measurement Report message (RRC) for event 3a has been received from the UE). The pmNoOutIratCcAtt counter is increased when the Cell Change Order From UTRAN (RRC) message has been sent to the UE. The pmNoAttOutIratHoSpeech, pmNoAttOutIratHoMulti and pmNoAttOutIratHoStandalone counters are increased when RNC is received "HANDOVER FROM UTRAN COMMAND" respectively for RAB Speech, MultiRAB or ’Standalone Signalling connection’. These counters will only be incremented in the SRNC and for the best cell in active set that have GsmRelation with target GSM cell. The RNC instructs the UE to start GSM measurements in preparation for a possible Inter-RAT (GSM) Handover / (GPRS) Cell Change due to poor radio quality. The UE sends a Measurement Report message with event 2d. Event id 2d is identified. The measurement handling algorithm is initiated. If the UE measures GSM frequencies relatively without using Compressed Mode step or using Compressed Mode step the counter pmIratHoGsmMeasNoCmStart or





pmIratHoGsmMeasCmStart is increased, when the Measurement Control (RRC) message to setup the 3a is sent to the UE. Both counters are stepped for the best cell in the Active Set. This KPI can be computed on a per RNC basis as well as a per cell basis, but it is recommended to aggregate it on RNC level.

10.2.2 CS IRAT HO Activity Rate

KPI Name: IRATHO_ACTIVITY_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation, UtranCell Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛ +⎟⎟⎠

⎞⎜⎜⎝

⎛ +seSpeechlRabRealeapmNoSystem

eSpeech RabRealeaspmNoNormal oMultisOuttIratHpmNoSucces

Speech sOutIratHopmNoSucces100 / *

Units: % Note: Counters pmNoSuccessOutIratHoSpeech and

pmNoSuccessOutIratHoMulti incremented if the GsmRelation exist between Best AS cell and the target GSM cell.

KPI Description

The KPI defines the intensity of IRAT HO: it is a rate between all the success of outgoing (to GSM) IRAT HO (triggered when RAB release with cause Successful Relocation) for RAB Speech and Multi RAB and the total of RAB Speech and Multi RAB releases. The trigger pmNoSuccessOutIratHoSpeech is when IU RELEASE COMMAND is received with cause ’Normal release’ or ’Successful relocation’ and based on the CS RAB state. This counter will only be incremented in the SRNC. The trigger of the counter pmNoSuccessOutIratHoMulti is reception of "HANDOVER FROM UTRAN COMMAND". This counter will only be incremented in the SRNC. The pmNoNormalRabReleaseSpeech and pmNoSystemRabReleaseSpeech counters are only increased due to a RANAP Iu Release Command or RAB Assignment Request message for RAB Speech respectively with “release cause” = ’Normal Release’, ’Successful Relocation’, ’Resource Optimisation Relocation’, ’User





Inactivity’ or ’release-due-to-UE-generated-signaling-connection-release’ for the first one or anything except the previous causes for the second one. For UtranCell class, these counters are incremented for the best cell in the Active Set in the SRNC. Note that, in case of Multi RAB, in mentioned counters are included all the releases from Multi RAB to only PS RAB and to Idle state. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.2.3 Relocation Preparation Failure Rate

KPI Name: IRATHO_FAIL_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:


⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

++

+

⎟⎟⎠

⎞⎜⎜⎝

⎛ +

iIratHoMultpmNoAttOut ilureMultiGsmFalOutIratHopmNoAttFai

ch IratHoSpeepmNoAttOut ailureSpeechGsmFlOutIratHopmNoAttFai

retiGsmFailutIratHoMulpmNoFailOu ureechGsmFailtIratHoSpepmNoFailOu

100 / *

Units: % Note: Counters pmNoFailOutIratHoSpeechGsmFailure and

pmNoFailOutIratHoMultiGsmFailure incremented if the GsmRelation exist between Best AS cell and the target GSM cell

KPI Description

The KPI defines the failure rate for relocation preparation of IRAT HO for RAB Speech and Multi-RAB: it is a rate between all the failures of outgoing (to GSM) IRAT HO (due to GSM resource allocation failure) for RAB Speech and Multi RAB and the total of RAB Speech and Multi RAB outgoing (to GSM) IRAT HO attempts. The trigger of pmNoFailOutIratHoSpeechGsmFailure and





pmNoFailOutIratHoMultiGsmFailure is when a "RANAP RELOCATION PREPARATION FAILURE" message is received from CN or a timeout of timer T<RELOCprep> occurs, and based on the CS RAB state. This counter will only be incremented in the SRNC and for the best cell in the active set. The trigger pmNoSuccessOutIratHoSpeech is when IU RELEASE COMMAND is received with cause ’Normal release’ or ’Successful relocation’ and based on the CS RAB state. This counter will only be incremented in the SRNC and for the best cell in the active set. The trigger of the counter pmNoSuccessOutIratHoMulti is reception of "HANDOVER FROM UTRAN COMMAND". This counter will only be incremented in the SRNC and for the best cell in the active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.2.4 CS IRAT HO Success Rate

KPI Name: IRATHO_SUCC_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛ +⎟⎟⎠

⎞⎜⎜⎝

⎛ + iIratHoMultpmNoAttOut

ch IratHoSpeepmNoAttOutMultisOutIratHopmNoSuccespeech OutIratHoSmNoSuccess

100 / *

Units: % Note: Counters pmNoSuccessOutIratHoSpeech and

pmNoSuccessOutIratHoMulti incremented if the GsmRelation exist between Best AS cell and the target GSM cell.

KPI Description

The KPI defines the success rate for IRAT HO for RAB Speech and MultiRAB: it is calculated as the rate between all the success of outgoing (to GSM) IRAT for RAB Speech and Multi RAB and the total of attempts.





The pmNoAttOutIratHoSpeech and pmNoAttOutIratHoMulti counters are increased when RNC is received "HANDOVER FROM UTRAN COMMAND" respectively for RAB Speech and MultiRAB. These counters will only be incremented in the SRNC and for the best cell in active set. The trigger pmNoSuccessOutIratHoSpeech is when IU RELEASE COMMAND is received with cause ’Normal release’ or ’Successful relocation’ and based on the CS RAB state. This counter will only be incremented in the SRNC and for the best cell in the active set. The trigger of the counter pmNoSuccessOutIratHoMulti is reception of "HANDOVER FROM UTRAN COMMAND". This counter will only be incremented in the SRNC and for the best cell in the active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.2.5 CS IRAT Failure UE Rejection

KPI Name: IRATHO_FAIL_UEREJ RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛ +⎟⎟⎠

⎞⎜⎜⎝


ch IratHoSpeepmNoAttOutiontiUeRejecttIratHoMulpmNoFailOu

tion echUeRejectIratHoSpepmNoFailOu100 / *

Units: % Note: Counters pmNoFailOutIratHoSpeechueRejection and

pmNoFailOutIratHoMultiUeRejection incremented if the GsmRelation exist between Best AS cell and the target GSM cell.

KPI Description

The KPI defines the failure rate for outgoing (to GSM) inter-RAT handover, rejected by UE, for RAB Speech and MultiRAB over the total number of outgoing (to GSM) inter-RAT handover attempt.





The trigger of pmNoFailOutIratHoSpeechUeRejection and pmNoFailOutIratHoMultiUeRejection counters is when "HANDOVER FROM UTRAN FAILURE" is received with inter-RAT handover failure cause=configuration unacceptable, and based on the CS RAB state. This counter will only be incremented in the SRNC and for the best cell in the active set. The trigger pmNoSuccessOutIratHoSpeech is when IU RELEASE COMMAND is received with cause ’Normal release’ or ’Successful relocation’ and based on the CS RAB state. This counter will only be incremented in the SRNC and for the best cell in the active set. The trigger of the counter pmNoSuccessOutIratHoMulti is reception of "HANDOVER FROM UTRAN COMMAND". This counter will only be incremented in the SRNC and for the best cell in the active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.2.6 CS IRAT HO Failure Physical Channel

KPI Name: IRATHO_FAIL_PHYSCH RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛ +⎟⎟⎠

⎞⎜⎜⎝


ch IratHoSpeepmNoAttOutildChPhyChFatiReturnOltIratHoMulpmNoFailOu

ailldChPhyChFechReturnOtIratHoSpepmNoFailOu100 / *

Units: % Note: Counters

pmNoFailOutIratHoSpeechReturnOldChPhyChFail and pmNoFailOutIratHoMultReturnOldChPhyChFail incremented if the GsmRelation exist between Best AS cell and the target GSM cell.

KPI Description

The KPI defines the failure rate for outgoing (to GSM) inter-RAT handover, due to physical channel failure, where the UE returns to the present Active Set, for RAB





Speech and MultiRAB over the total number of outgoing (to GSM) inter-RAT handover attempt. The trigger of pmNoFailOutIratHoSpeechReturnOldChPhyChFail and pmNoFailOutIratHoMultiReturnOldChPhyChFail counters is the reception of "HANDOVER FROM UTRAN FAILURE" with inter-RAT handover failure cause=Physical Channel Failure and based on the CS RAB state. This counter will only be incremented in the SRNC and for the best cell in the active set. The trigger pmNoSuccessOutIratHoSpeech is when IU RELEASE COMMAND is received with cause ’Normal release’ or ’Successful relocation’ and based on the CS RAB state. This counter will only be incremented in the SRNC and for the best cell in the active set. The trigger of the counter pmNoSuccessOutIratHoMulti is reception of "HANDOVER FROM UTRAN COMMAND". This counter will only be incremented in the SRNC and for the best cell in the active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.2.7 CS IRAT HO Failure Not Physical Channel

KPI Name: IRATHO_FAIL_NPHYSCH RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛ +⎟⎟⎠

⎞⎜⎜⎝


ch IratHoSpeepmNoAttOuthFaildChNotPhyCtiReturnOltIratHoMulpmNoFailOu

ChFailldChNotPhyechReturnOtIratHoSpepmNoFailOu100 / *

Units: % Note: Counters

pmNoFailOutIratHoSpeechReturnOldChNotPhyChFail and pmNoFailOutIratHoMultReturnOldChNotPhyChFail incremented if the GsmRelation exist between Best AS cell and the target GSM cell.





KPI Description The KPI defines the failure rate for outgoing (to GSM) inter-RAT handover, due to reasons other than physical channel failure, where the UE returns to the present Active Set, for RAB Speech and MultiRAB over the total number of outgoing (to GSM) inter-RAT handover attempt. The trigger of pmNoFailOutIratHoSpeechReturnOldChNotPhyChFail and pmNoFailOutIratHoMultiReturnOldChNotPhyChFail counters is the reception of "HANDOVER FROM UTRAN FAILURE" with inter-RAT handover failure cause=any other cause apart from Physical channel failure or configuration unacceptable and based on the CS RAB state. This counter will only be incremented in the SRNC and for the best cell in the active set. The trigger pmNoSuccessOutIratHoSpeech is when IU RELEASE COMMAND is received with cause ’Normal release’ or ’Successful relocation’ and based on the CS RAB state. This counter will only be incremented in the SRNC and for the best cell in the active set. The trigger of the counter pmNoSuccessOutIratHoMulti is reception of "HANDOVER FROM UTRAN COMMAND". This counter will only be incremented in the SRNC and for the best cell in the active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.2.8 CS IRAT HO Failure UE Lost

KPI Name: IRATHO_FAIL_UELOST RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:






⎟⎟⎠

⎞⎜⎜⎝

⎛ +

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

−+

iIratHoMultpmNoAttOut ch IratHoSpeepmNoAttOut

hFaildChNotPhyCtiReturnOltIratHoMulpmNoFailOu- ildChPhyChFatiReturnOltIratHoMulpmNoFailOu

-ion tiUeRejecttIratHoMulpmNoFailOu-MultisOutIratHopmNoSucces

iIratHoMultpmNoAttOut ChFailldChNotPhyechReturnOtIratHoSpepmNoFailOu

- ailldChPhyChFechReturnOtIratHoSpepmNoFailOu -tion echUeRejectIratHoSpepmNoFailOu

-SpeechsOutIratHopmNoSucces-ch IratHoSpeepmNoAttOut

100 / *

Units: % Note:

KPI Description The KPI defines the failure rate for outgoing (to GSM) inter-RAT handover taking out every failure cause leading to a return to UMTS RAT (UE rejection, Return to Old Physical Channel). The pmNoAttOutIratHoSpeech and pmNoAttOutIratHoMulti counters are increased when RNC is received "HANDOVER FROM UTRAN COMMAND" respectively for RAB Speech and MultiRAB. The trigger pmNoSuccessOutIratHoSpeech is when IU RELEASE COMMAND is received with cause ’Normal release’ or ’Successful relocation’ and based on the CS RAB state. The trigger of the counter pmNoSuccessOutIratHoMulti is reception of "HANDOVER FROM UTRAN COMMAND". These counters will only be incremented in the SRNC and for the best cell in active set. The trigger of pmNoFailOutIratHoSpeechReturnOldChPhyChFail and pmNoFailOutIratHoMultiReturnOldChPhyChFail counters is the reception of "HANDOVER FROM UTRAN FAILURE" with inter-RAT handover failure cause=Physical Channel Failure and based on the CS RAB state. The trigger pmNoSuccessOutIratHoSpeech is when IU RELEASE COMMAND is received with cause ’Normal release’ or ’Successful relocation’ and based on the CS RAB state. The trigger of pmNoFailOutIratHoSpeechReturnOldChNotPhyChFail and pmNoFailOutIratHoMultiReturnOldChNotPhyChFail counters is the reception of "HANDOVER FROM UTRAN FAILURE" with inter-RAT handover failure cause=any other cause apart from Physical channel failure or configuration unacceptable and based on the CS RAB state. The trigger of pmNoFailOutIratHoSpeechUeRejection and pmNoFailOutIratHoMultiUeRejection counters is when "HANDOVER FROM UTRAN FAILURE" is received with inter-RAT handover failure cause=configuration unacceptable, and based on the CS RAB state. This counter will only be incremented in the SRNC and for the best cell in the active set. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





10.2.9 CS Incoming IRAT HO Success Rate

KPI Name: IRATHO_SUCC_RATE_CS_IN RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


atHoAttpmNoInCsIr

satHoSuccespmNoInCsIr* 100

Units: % Note:

KPI Description The KPI defines the percentage of incoming IRAT Handover Successful attempts for CS RAB, over the total attempts. The pmNoInCsIratHoSuccess counter provides the number of successful CS incoming Inter System Handovers. The counter is increased after reception of both RRC message “handover to UTRAN complete” (UE responds after completed RANAP procedure for Relocation Request) and NBAP message “RL restore ind” (RBS has received UL synchronisation with the UE). The pmNoInCsIratHoAtt counter provides the number of attempted CS incoming Inter System Handovers (counted before module and central MP load control, after SCCP MP load control). It is Increased at reception of RANAP message “relocation request” after successful load control of SCCP MP if the cell is recognized as being controlled by this RNC. (After the stepping also central MP and module MP is checked for overload). This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





10.2.10 CS Incoming IRAT HO Failure Rate due to Admission

KPI Name: IRATHO_FAIL_RATE_IN_ADM RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


atHoAttpmNoInCsIr

latHoAdmFaipmNoInCsIr* 100

Units: % Note:

KPI Description The KPI defines the percentage of incoming IRAT Handover attempts for CS RAB, failed due to admission blocking in UTRAN. The pmNoInCsIratHoAdmFail counter provides the number of CS incoming Inter System Handovers that failes due to admission blocking in Utran. It is increased whenever an Admission is rejected at RANAP Relocation Request. The pmNoInCsIratHoAtt counter provides the number of attempted CS incoming Inter System Handovers (counted before module and central MP load control, after SCCP MP load control). It is Increased at reception of RANAP message “relocation request” after successful load control of SCCP MP if the cell is recognized asbeing controlled by this RNC. (After the stepping also central MP and module MP is checked for overload). This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





10.3 PS IRAT

10.3.1 PS IRAT (UMTS to GSM) Success Rate

KPI Name: IRATCCSUCC_DCHATP_TO_GSM RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:


tCcAttemptpmNoOutIratCcSuccesspmNoOutIra

* 100

Units: % Note: New counter pmNoOutIratCcSuccess introduced in P5

KPI Description The KPI defines the success rate for PS Inter RAT cell change attempts for UE on dedicated channel. During Inter-RATCC from UTRAN to GPRS, UE on DCH, the Handover evaluation function triggers this function to indicate that we need to make handover to a GSM cell. (A Measurement Report message (RRC) for event 3a has been received from the UE). The counter pmNoOutIratCcAtt is increased when the Cell Change Order From UTRAN (RRC) message has been sent to the UE. The pmNoOutIratCcSuccess counter is triggered by CN Iu Release Command following the sending of the CELL CHANGE ORDER FROM UTRAN message. The Cell Change Order from UTRAN (RRC) message is sent to the UE and the counter is increased when an Iu Release Command is received from the PS CN, with cause ‘Normal release’ or ‘Successful Relocation’. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





10.3.2 PS IRAT HO Failure Rate

KPI Name: IRATCCFAIL_DCHATP_TO_GSM RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:


tCcAttemptpmNoOutIraldChtCCReturnOpmNoOutIra

* 100

Units: % Note:

KPI Description The KPI defines the percentage of failed attempts of PS Inter RAT Handover, over the total number of attempts. The counter pmNoOutIratCcAtt is increased when the Cell Change Order From UTRAN (RRC) message has been sent to the UE. The pmNoOutIratCcReturnOldCh counter provides the total number of the PS Inter-RATCC attempts for UE on DCH where the UE returns to old channel. It is stepped for Inter-RATCC from UTRAN to GPRS, UE on DCH. The counter is increased when the “Cell change order from UTRAN failure” (RRC) message is received from the UE. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.3.3 PS IRAT HO Incoming Success Rate

KPI Name: IRATHO_SUCC_RATE_PS_IN





RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:


CcOrder ConnectAtt pmTotNoRrcOrder cessIratCc ConnectSuc pmTotNoRrc

* 100

Units: % Note:

KPI Description The KPI defines the percentage of successful attempts of PS Incoming Inter RAT Handover, over the total number of attempts. The pmTotNoRrcConnectSuccessIratCcOrder provides the number of successful RRC Connection establishments with establishment cause Inter RAT cell change order. It is handled by RRC Connection Handling function. The counter is counting the number of successful RRC connection establishments with establishment cause "Inter-RAT cell change order". The pmTotNoRrcConnectAttIratCcOrder provides the total number of RRC connection establishment attempts with establishment cause Inter-RAT cell change order. It is handled by RRC Connection Handling function. The counter is counting the number of RRC connection establishment attempts with establishment cause "Inter-RAT cell change order". Note: This counter does not count the subsequent retransmissions. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.3.4 PS IRAT HO Incoming Failure Rate

KPI Name: IRATHO_FAIL_RATE_CS_IN RNC Sw Release: P6 Importance: Medium





Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:


CcOrder ConnectAtt pmTotNoRrccOrderlCongIratC ConnectFai pmTotNoRrc

* 100

Units: % Note:

KPI Description The KPI defines the percentage of failed attempts of PS Inter RAT Handover, over the total number of attempts, due to congestion. The pmTotNoRrcConnectFailCongIratCcOrder counter provides the number of unsuccessful RRC Connection establishments with establishment cause Inter-RAT cell change order, which failed due to congestion. The counter is increased when the “RRC coonection reject” message is sent with Rejection Cause="congestion" in response to a received “RRC Connection request” with establishment cause="InterRat cell change order". The pmTotNoRrcConnectAttIratCcOrder provides the total number of RRC connection establishment attempts with establishment cause Inter-RAT cell change order. It is handled by RRC Connection Handling function. The counter is counting the number of RRC connection establishment attempts with establishment cause "Inter-RAT cell change order". Note: This counter does not count the subsequent retransmissions. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





10.4 IRAT Cell Reselection

10.4.1 IRAT Cell Reselection Success Rate

KPI Name: IRATCR_RRCSUCCRATE RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


selIratCellReConnectAttpmTotNoRrcllReselcessIratCeConnectSucpmTotNoRrc

* 100

Units: % Note:

KPI Description The KPI defines the percentage of successful IRAT cell reselection attempts, over the total number of attempts. The pmTotNoRrcConnectSuccessIratCellResel counter provides the number of successful RRC Connection establishments with establishment cause Inter RAT cell reselection. It is Handled by RRC Connection Handling function. The counter is counting the number of successful RRC connection establishments with establishment cause "Inter-RAT cell reselection". The pmTotNoRrcConnectAttIratCellResel counter provides the total number of RRC connection establishment attempts with establishment cause Inter-RAT cell reselection Handled by RRC Connection Handling function. The counter is counting the number of RRC connection establishment attempts with establishment cause "Inter-RAT cell reselection". Note: This counter does not count the subsequent retransmissions. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





10.4.2 IRAT Cell Reselection Failure Rate due to Congestion

KPI Name: IRATCR_RRCFAILRATE RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


selIratCellReConnectAttpmTotNoRrcellResellCongIratCConnectFaipmTotNoRrc

* 100

Units: % Note:

KPI Description This KPI defines the percentage of IRAT cell reselection attempts failed due to congestion. The pmTotNoRrcConnectFailCongIratCellResel counter provides the number of unsuccessful RRC Connection establishments with establishment cause Inter-RAT cell reselection, which failed due to congestion. The counter is increased when the “RRC connection reject” mssage is sent with Rejection Cause="congestion" in response to a received RRC connection reject with establishment cause = "InterRat cell reselection". The pmTotNoRrcConnectAttIratCellResel counter provides the total number of RRC connection establishment attempts with establishment cause Inter-RAT cell reselection Handled by RRC Connection Handling function. The counter is counting the number of RRC connection establishment attempts with establishment cause "Inter-RAT cell reselection". Note: This counter does not count the subsequent retransmissions. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





10.5 Service Based Handover

10.5.1 Service Based HO Success Rate

KPI Name: SBHO_SUCC_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell,RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:


SbHoSpeechpmNoAttOuteechsOutSbHoSppmNoSucces

* 100

Units: % Note: Counters pmNoSuccessOutSbHoSpeech and

pmNoAttOutSbHoSpeech incremented if the GsmRelation exist between Best AS cell and the target GSM cell.

KPI Description

This KPI defines the percentage of successful Service Based handover attempts on GSM for conversational speech RAB, over the total number of IRAT HO attempts for speech RAB. The pmNoSuccessOutSbHoSpeech counter provides the number of successful outgoing Service Based GSM Handover for ’Conversational speech RAB’ for the best cell in the active set. The counter is increased when IU RELEASE COMMAND is received with cause ’Normal release’ or ’Successful relocation’. This counter will only be incremented in the SRNC. The pmNoAttOutSbHoSpeech counter provides the number of attempted outgoing Service Based GSM Handover for ’Conversational speech RAB’ for the best cell in the active set. The counter is increased when RNC sends HANDOVER FROM UTRAN COMMAND. This counter will only be incremented in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





10.5.2 Service Based HO Percentage

KPI Name: SBHO_ACTIVITY_RATE RNC Sw Release: P5 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:


chIratHoSpee pmNoAttOutSbHoSpeechpmNoAttOutSbHoSpeechpmNoAttOut

* 100+

Units: % Note: Counters pmNoAttOutSbHoSpeech incremented if the

GsmRelation exist between Best AS cell and the target GSM cell.

KPI Description

This KPI defines the percentage of successful Service Based handover attempts on GSM for conversational speech RAB, over the total number of attempts. The pmNoSuccessOutSbHoSpeech counter provides the number of successful outgoing Service Based GSM Handover for ’Conversational speech RAB’ for the best cell in the active set. The counter is increased when IU RELEASE COMMAND is received with cause ’Normal release’ or ’Successful relocation’. This counter will only be incremented in the SRNC. The pmNoAttOutSbHoSpeech counter provides the number of attempted outgoing Service Based GSM Handover for ’Conversational speech RAB’ for the best cell in the active set. The counter is increased when RNC sends HANDOVER FROM UTRAN COMMAND. This counter will only be incremented in the SRNC. The pmNoAttOutIratHoSpeech counter provides the number of attempted outgoing (to GSM) inter-RAT handover for ’Conversational speech RAB’ for the best cell in the active set. The counter is increased when RNC sends "HANDOVER FROM UTRAN COMMAND". This counter will only be incremented in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





10.5.3 Service Based HO Failure Rate

KPI Name: SBHO_FAIL_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: GsmRelation Counters Type: PEG Target Value:


SbHoSpeechpmNoAttOut

lChPhyChFaihReturnOldtSbHoSpeecpmNoFailOu

FailChNotPhyChhReturnOldtSbHoSpeecpmNoFailOu

on hUeRejectitSbHoSpeecpmNoFailOu

* 100⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛+

+

Units: % Note: Counters pmNoFailOutSbHoSpeechUeRejection,

pnNoFailOutSbHoSpeechReturnOldChNotPhyChFail and pnNoFailOutSbHoSpeechReturnOldChPhyChFail incremented if the GsmRelation exist between Best AS cell and the target GSM cell.

KPI Description

This KPI defines the percentage of Service Based Handover attempts failed, for speech RAB, over the total number of Service Based Handover attempts for speech RAB. The pmNoAttOutSbHoSpeech counter provides the number of attempted outgoing Service Based GSM Handover for ’Conversational speech RAB’ for the best cell in the active set. The counter is increased when RNC sends HANDOVER FROM UTRAN COMMAND. This counter will only be incremented in the SRNC. The pmNoFailOutSbHoSpeechUeRejection Counter provides the number of failed outgoing Service Based GSM Handover, rejected by UE, for ’Conversational speech RAB’ for the best cell in the active set. The counter is increased when HANDOVER FROM UTRAN FAILURE is received with cause ’Configuration unacceptable’. This counter will only be incremented in the SRNC. The pmNoFailOutSbHoSpeechReturnOldChNotPhyChFail counter provides the number of failed outgoing Service Based GSM Handover due to reasons other than physical channel failure, where the UE returns to the present Active Set for ’Conversational speech RAB’ for the best cell in the active set. The counter is increased when HANDOVER FROM UTRAN FAILURE is received with cause: any





other cause apart from ’Physical channel failure’ or ’Configuration unacceptable’. This counter will only be incremented in the SRNC. The pmNoFailOutSbHoSpeechReturnOldChPhyChFail counter provides the number of failed outgoing Service Based GSM Handover due to physical channel failure, where the UE returns to the present Active Set for ’Conversational speech RAB’ for the best cell in the active set. The counter is increased when HANDOVER FROM UTRAN FAILURE is received with cause ’Physical channel failure’. This counter will only be incremented in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

10.5.4 Service Based GSM HO Activity Rate

KPI Name: SBHO_GSM_ACTIVITY_RATE RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Handover Counters Type: PEG Target Value:


opmTotNoSbHasStartpmNoSbHoMe

* 100

Units: % Note:

KPI Description This KPI defines how many Service Based GSM Handover measurements per RNC have been started, expressed as a percentage over the total number of potential Service Based GSM Handover users. The pmNoSbHoMeasStart counter provides the total number of started Service Based GSM Handover measurements per RNC. The counter is stepped at the transmission of the measurement control for activating the Service Based GSM Handover measurements. The pmTotNoSbHo counter provides the total number of potential Service Based GSM Handover users per RNC. The counter is stepped at





the reception of RAB Assignment Request if the RAB combination is "speech only" and the IE Service Handover has value ’Handover to GSM should be performed’.

10.5.5 Service Based GSM HO Success Rate

KPI Name: SBHO_GSM_SUCC_RATE RNC Sw Release: P6 Importance: Medium Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: Handover Counters Type: PEG Target Value:


asStart pmNoSbHoMesSbHo pmNoSucces

* 100

Units: % Note:

KPI Description This KPI defines the percentage of successful outgoing Service Based GSM Handover per RNC, over the total number of started service based GSM handover measurements per RNC. The pmNoSuccessSbHo counter provides the total number of successful outgoing Service Based GSM Handover per RNC. The counter is stepped when Iu Release is received from CS CN. The pmNoSbHoMeasStart counter provides the total number of started Service Based GSM Handover measurements per RNC. The counter is stepped at the transmission of the measurement control for activating the Service Based GSM Handover measurements. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





11 Mobility Inter Frequency Handover

11.1 Inter frequency Handover

11.1.1 IF HO Radio Link Addition Failure

KPI Name: IFHO_RL_ADD_FAIL_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

+ ActSetfhoRlAddTopmNoTimesI et lAddToActSfhoCellFaipmNoTimesIetlAddToActSfhoCellFaipmNoTimesI

* 100

Units: % Note: In P6 counter pmNoTimesIfhoCellFaileAddToActSet


KPI Description

This KPI defines the percentage of failed IF HO Radio Link additions to active set, over the total number of RL addition attempts. The pmNoTimesIfhoCellFailAddToActSet provides the number of times a cell fails to be added to an active set. This counter is stepped after any occured failure of Radio Link Setup or Radio Link Addition procedure, regardless of the reason of the failure, at Intra RNC Inter Frequency Handover. This counter will only be incremented in the SRNC. The pmNoTimesIfhoRlAddToActSet counter provides the number of times an RL is added to an active set. This counter is stepped after RRC PHYSICAL CHANNEL RECONFIGURATION COMPLETE has been received at Intra RNC Inter Frequency Handover. This counter will only be incremented in the SRNC. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can






11.1.2 IF HO Success Rate CS Speech

KPI Name: IFHO_SUCC_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranRelation Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

ch12eqHoCsSpeeindInterFrpmAttNonBlech12reqHoCsSpelindInterFpmSuccNonB

* 100



KPI Description This KPI defines the percentage of successful non blind Inter Frequency Handovers for CS Speech, over the total number of non blind Inter Frequency Handover attempts for CS speech. The pmSuccNonBlindInterFreqHoCsSpeech12 Counter provides the number of successful non-blind outgoing inter-frequency handovers for RAB = Conversational speech. After Handover Evaluation has decided to initiate interfrequency handover for a CS speech RAB, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. When a successful response, RRC Physical Channel Reconfiguration Complete is received from the UE, this counter is stepped. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. The pmAttNonBlindInterFreqHoCsSpeech12 provides the number of attempted non-blind outgoing inter-frequency handovers for RAB = Conversational speech After Handover Evaluation has decided to initiate interfrequency handover for a CS speech RAB, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. This counter is stepped after that message is sent. The counter is stepped for the best





cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note1: The handover evaluation decision is based on measurements performed by the UE on the target frequency. Note2: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.1.3 IF HO Success Rate CS64

KPI Name: IFHO_SUCC_CS64 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranRelation Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

ersationaleqHoCsConvindInterFrpmAttNonBllversationareqHoCsConlindInterFpmSuccNonB

* 100



KPI Description This KPI defines the percentage of successful non blind Inter Frequency Handovers for CS conversational, other than speech, over the total number of non-blind Inter Frequency Handover attempts for CS conversational (other than speech). The pmSuccNonBlindInterFreqHoCsConversational Counter provides the number of successful non-blind outgoing inter-frequency handovers for RAB CS conversational except of speech. After Handover Evaluation has decided to initiate interfrequency handover for a CS coversational RAB, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message.





When a successful response, RRC Physical Channel Reconfiguration Complete is received from the UE, this counter is stepped. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. The pmAttNonBlindInterFreqHoCsConversational provides the number of attempted non-blind outgoing inter-frequency handovers for RAB CS Conversational except of speech. After Handover Evaluation has decided to initiate interfrequency handover for a CS conversational RAB, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. This counter is stepped after that message is sent. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note1: The handover evaluation decision is based on measurements performed by the UE on the target frequency. Note2: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.1.4 IF HO Success Rate PS Interactive Less Than 64

KPI Name: IFHO_SUCC_ PSINT_LESS64 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranRelation Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

s64ractiveLeseqHoPsInteindInterFrpmAttNonBlss64eractiveLereqHoPsIntlindInterFpmSuccNonB

* 100







KPI Description

This KPI defines the percentage of successful non blind Inter Frequency Handovers for PS interactive Rab with data rate less than or equal to 64 kbs, over the total number of non blind Inter Frequency Handover attempts for PS interactive Rab with data rate less than or equal to 64 kbs as rate. The pmSuccNonBlindInterFreqHoPsInteractiveLess64 Counter provides the number of successful non-blind outgoing inter-frequency handovers for PS interactive Rab with data rate less than or equal to 64 kbs. After Handover Evaluation has decided to initiate interfrequency handover for PS interactive Rab with data rate less than or equal to 64 kbs, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. When a successful response, RRC Physical Channel Reconfiguration Complete is received from the UE, this counter is stepped. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. The pmAttNonBlindInterFreqHoPsInteractiveLess64 provides the number of attempted non-blind outgoing inter-frequency handovers for PS interactive Rab with data rate less than or equal to 64 kbs. After Handover Evaluation has decided to initiate interfrequency handover for a PS interactive Rab with data rate less than or equal to 64 kbs, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. This counter is stepped after that message is sent. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note1: The handover evaluation decision is based on measurements performed by the UE on the target frequency. Note2: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.1.5 IF HO Success Rate PS Interactive Greater Than 64

KPI Name: IFHO_SUCC_PSINT_GREATER64 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour





Counters MO Class: UtranRelation Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

ater64ractiveGreeqHoPsInteindInterFrpmAttNonBleater64eractiveGrreqHoPsIntlindInterFpmSuccNonB

* 100



KPI Description This KPI defines the percentage of successful non blind Inter Frequency Handovers for PS interactive Rab with data rate greater than 64 kbs, over the total number of non blind Inter Frequency Handover attempts for PS interactive Rab with data rate greater than 64 kbs as rate. The pmSuccNonBlindInterFreqHoPsInteractiveGreater64 Counter provides the number of successful non-blind outgoing inter-frequency handovers for PS interactive Rab with data rate greater than 64 kbs. After Handover Evaluation has decided to initiate interfrequency handover for PS interactive Rab with data rate greater than 64 kbs, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. When a successful response, RRC Physical Channel Reconfiguration Complete is received from the UE, this counter is stepped. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. The pmAttNonBlindInterFreqHoPsInteractiveGreater64 provides the number of attempted non-blind outgoing inter-frequency handovers for PS interactive Rab with data rate greater than 64 kbs. After Handover Evaluation has decided to initiate interfrequency handover for a PS interactive Rab with data rate greater than 64 kbs, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. This counter is stepped after that message is sent. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note1: The handover evaluation decision is based on measurements performed by the UE on the target frequency. Note2: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





11.1.6 IF HO Success Rate Streaming

KPI Name: IFHO_SUCC_STREAMINGOTHER RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranRelation Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

ingOthereqHoStreamindInterFrpmAttNonBlmingOtherreqHoStrealindInterFpmSuccNonB

* 100



KPI Description This KPI defines the percentage of successful non blind Inter Frequency Handovers for streaming RABs (radio connections in states with streaming connections: 57kpbs CS data, variable rate; and PS Streaming 16/64 + Packet 8kpbs), over the total number of non blind Inter Frequency Handover attempts for streaming RABs (radio connections in states with streaming connections: 57kpbs CS data, variable rate; and PS Streaming 16/64 + Packet 8kpbs). The pmSuccNonBlindInterFreqHoStreamingOther Counter provides the number of successful non-blind outgoing inter-frequency handovers for streaming RABs (radio connections in states with streaming connections: 57kpbs CS data, variable rate; and PS Streaming 16/64 + Packet 8kpbs). After Handover Evaluation has decided to initiate interfrequency handover for streaming RABs (radio connections in states with streaming connections: 57kpbs CS data, variable rate; and PS Streaming 16/64 + Packet 8kpbs), the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. When a successful response, RRC Physical Channel Reconfiguration Complete is received from the UE, this counter is stepped. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. The pmAttNonBlindInterFreqHoStreamingOther provides the number of attempted non-blind outgoing inter-frequency handovers for streaming RABs (radio connections in states with streaming connections: 57kpbs





CS data, variable rate; and PS Streaming 16/64 + Packet 8kpbs). After Handover Evaluation has decided to initiate interfrequency handover for streaming RABs (radio connections in states with streaming connections: 57kpbs CS data, variable rate; and PS Streaming 16/64 + Packet 8kpbs), the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. This counter is stepped after that message is sent. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note1: The handover evaluation decision is based on measurements performed by the UE on the target frequency. Note2: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.1.7 IF HO Failure Rate Speech

KPI Name: IFHO_FAIL_SPEECH RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranRelation Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

12eqHoSpeechindInterFrpmAttNonBlh12evertSpeecreqHoFailRlindInterFpmFailNonB

* 100



KPI Description This KPI defines the percentage of Failed non blind Inter Frequency Handovers for CS Speech 12 RAB, over the total number of non blind Inter Frequency Handover attempts for CS Speech 12 RAB.





The pmFailNonBlindInterFreqHoFailRevertCsSpeech12 counter provides the number of failed non-blind outgoing inter-frequency handovers, where the UE fails to return to the present active set, for RAB = CS speech. After Handover Evaluation has decided to initiate interfrequency handover for a CS speech RAB, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. If there is a timeout on the RRC message (that is, no response received from the UE) this counter is stepped. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. The pmAttNonBlindInterFreqHoCsSpeech12 provides the number of attempted non-blind outgoing inter-frequency handovers for RAB = Conversational speech After Handover Evaluation has decided to initiate interfrequency handover for a CS speech RAB, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. This counter is stepped after that message is sent. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note1: The handover evaluation decision is based on measurements performed by the UE on the target frequency. Note2: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.1.8 IF HO Failure Rate CS 64

KPI Name: IFHO_FAIL_CS64 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranRelation Counters Type: PEG Target Value:






⎟⎠⎞

⎜⎝⎛

ersationaleqHoCsConvindInterFrpmAttNonBllversationaevertCsConreqHoFailRlindInterFpmFailNonB

* 100



KPI Description This KPI defines the percentage of Failed non blind Inter Frequency Handovers for CS Conversational except speech RAB, over the total number of non blind Inter Frequency Handover attempts for CS Conversational except speech RAB. The pmFailNonBlindInterFreqHoFailRevertCsConversational counter provides the number of failed non-blind outgoing inter-frequency handovers, where the UE fails to return to the present active set, for RAB = CS Conversational except speech. After Handover Evaluation has decided to initiate interfrequency handover for a CS conversational RAB, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. If there is a timeout on the RRC message (that is,no response received from the UE) this counter is stepped. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. The pmAttNonBlindInterFreqHoCsConversational provides the number of attempted non-blind outgoing inter-frequency handovers for RAB CS Conversational except of speech. After Handover Evaluation has decided to initiate interfrequency handover for a CS conversational RAB, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. This counter is stepped after that message is sent. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note1: The handover evaluation decision is based on measurements performed by the UE on the target frequency. Note2: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.1.9 IF HO Failure Rate PS Interactive Less Than 64

KPI Name: IFHO_FAIL_PSINT_LESS64 RNC Sw Release: P6





Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranRelation Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

s64ractiveLeseqHoPsInteindInterFrpmAttNonBlss64eractiveLeevertPsIntreqHoFailRlindInterFpmFailNonB

* 100



KPI Description This KPI defines the percentage of Failed non blind Inter Frequency Handovers for RAB Interactive less than or equal to 64 Kbps RAB, over the total number of non blind Inter Frequency Handover attempts for RAB Interactive less than or equal to 64 Kbps RAB. The pmFailNonBlindInterFreqHoFailRevertPsInteractiveLess64 counter provides the number of failed non-blind outgoing inter-frequency handovers, where the UE fails to return to the present active set, for RAB = Interactive less than or equal to 64 Kbps. After Handover Evaluation has decided to initiate interfrequency handover for a PS Interactive RAB with a data rate less than or equal to 64 Kbps, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. If there is a timeout on the RRC message (that is, no response received from the UE) this counter is stepped. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. The pmAttNonBlindInterFreqHoPsInteractiveLess64 provides the number of attempted non-blind outgoing inter-frequency handovers for PS interactive Rab with data rate less than or equal to 64 kbs. After Handover Evaluation has decided to initiate interfrequency handover for a PS interactive Rab with data rate less than or equal to 64 kbs, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. This counter is stepped after that message is sent. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note1: The handover evaluation decision is based on measurements performed by the UE on the target frequency. Note2: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented.






11.1.10 IF HO Failure Rate PS Interactive Greater Than 64

KPI Name: IFHO_FAIL_PSINT_GREATER64 RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranRelation Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

ater64ractiveGreeqHoPsInteindInterFrpmAttNonBleater64eractiveGrevertPsIntreqHoFailRlindInterFpmFailNonB

* 100



KPI Description This KPI defines the percentage of Failed non blind Inter Frequency Handovers for PS interactive Rab with data rate greater than 64 kbs, over the total number of non blind Inter Frequency Handover attempts for PS interactive Rab with data rate greater than 64 kbs. The pmFailNonBlindInterFreqHoFailRevertPsInteractiveGreater64 counter provides the number of failed non-blind outgoing inter-frequency handovers, where the UE fails to return to the present active set, for RAB = Interactive greater than 64 Kbps After Handover Evaluation has decided to initiate interfrequency handover for a PS Interactive RAB with a data rate greater than 64 Kbps, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. If there is a timeout on the RRC message (that is, no response received from the UE) this counter is stepped. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note: In case of a multi-RAB combination, the counters corresponding to each type of RAB





involved shall be incremented. The pmAttNonBlindInterFreqHoPsInteractiveGreater64 provides the number of attempted non-blind outgoing inter-frequency handovers for PS interactive Rab with data rate greater than 64 kbs. After Handover Evaluation has decided to initiate interfrequency handover for a PS interactive Rab with data rate greater than 64 kbs, the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. This counter is stepped after that message is sent. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note1: The handover evaluation decision is based on measurements performed by the UE on the target frequency. Note2: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.1.11 IF HO Failure Rate Streaming Other

KPI Name: IFHO_FAIL_STREAMINGOTHER RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranRelation Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

ingOthereqHoStreamindInterFrpmAttNonBlmingOtherevertStreareqHoFailRlindInterFpmFailNonB

* 100



KPI Description This KPI defines the percentage of Failed non blind Inter Frequency Handovers for PS interactive Rab with data rate greater than 64 kbs, over the total number of non





blind Inter Frequency Handover attempts for PS interactive Rab with data rate greater than 64 kbs. The pmFailNonBlindInterFreqHoFailRevertStreamingOther counter provides the number of failed non-blind outgoing inter-frequency handovers, where the UE fails to return to the present active set, for streaming RABs (radio connections in states with streaming connections: 57kpbs CS data, variable rate; and PS Streaming 16/64 + Packet 8kpbs). After Handover Evaluation has decided to initiate interfrequency handover for for streaming RABs (radio connections in states with streaming connections: 57kpbs CS data, variable rate; and PS Streaming 16/64 + Packet 8kpbs), the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. If there is a timeout on the RRC message (that is, no response received from the UE) this counter is stepped. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. The pmAttNonBlindInterFreqHoStreamingOther provides the number of attempted non-blind outgoing inter-frequency handovers for streaming RABs (radio connections in states with streaming connections: 57kpbs CS data, variable rate; and PS Streaming 16/64 + Packet 8kpbs). After Handover Evaluation has decided to initiate interfrequency handover for streaming RABs (radio connections in states with streaming connections: 57kpbs CS data, variable rate; and PS Streaming 16/64 + Packet 8kpbs), the UE is ordered to move to a new frequency by sending an RRC Physical Channel Reconfiguration message. This counter is stepped after that message is sent. The counter is stepped for the best cell in the active set but only if that cell has a cell relation towards the target cell. If the best cell in the active set has no cell relation towards the target cell, the counter is not stepped. Note1: The handover evaluation decision is based on measurements performed by the UE on the target frequency. Note2: In case of a multi-RAB combination, the counters corresponding to each type of RAB involved shall be incremented. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





11.2 Inter Frequency Hard HO

11.2.1 IF Hard HO HS Success Rate

KPI Name: IFHHO_SUCC_HS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

HhoAttemptpmEnableHsHhoSuccesspmEnableHs

* 100



KPI Description This KPI defines the percentage of successful attempts to do a Hard HO to a coverage related cell for Hs RAB, over the total number of HS Hard Handover attempts. The pmEnableHsHhoSuccess provides the number of successful attempts to do a Hard HO to a coverage related cell, with the purpose to enable the possibility to do a transition to a HS-DSCH connection. The counter is stepped in the best cell in the Active Set when the transition is triggered. The counter is stepped when Physical Channel Reconfiguration Complete is received from the UE, during an attempt to do a Hard HO to a Coverage Related cell when doing Serving HS-DSCH Cell Selection. The pmEnableHsHhoAttempt counter provides the number of attempts to do a Hard HO to a coverage related cell, with the purpose to enable the possibility to do a transition to a HS-DSCH connection. The counter is stepped in the best cell in the Active Set when the transition is triggered. The counter is stepped when Physical Channel Reconfiguration Complete is received from the UE, during an attempt to do a Hard HO to a Coverage Related cell when doing Serving HS-DSCH Cell Selection. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI






11.2.2 IF Hard HO EUL Success Rate

KPI Name: IFHHO_SUCC_HS RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

tlHhoAttemppmEnableEuslHhoSuccespmEnableEu

* 100



KPI Description This KPI defines the percentage of successful attempts to do a Hard HO to a coverage related cell for EUL RAB, over the total number of EUL Hard Handover attempts. The pmEnableEulHhoSuccess provides the number of successful attempts Number of successful Hard Handovers to a coverage-related EUL cell. The counter is incremented in the best cell in the Active Set when the transition is concluded. The best cell is the cell with the highest measured quality defined by parameter UeMeasControl::hsQualityEstimate. The counter is Incremented by one when Physical Channel Reconfiguration Complete is received from the UE, during an attempt to do a Hard HO to a Coverage Related cell when doing Serving E-DCH/HS-DSCH Cell Selection.

The pmEnableEulHhoAttempt counter provides the number of attempted Hard Handovers to a coverage-related E-DCH cell. The counter is incremented in the best cell in the Active Set when the transition is triggered. The best cell is the cell with the highest measured quality defined by parameter UeMeasControl::hsQualityEstimate. The counter is incremented by one when Physical Channel Reconfiguration is sent to the UE, for an attempt to do a Hard HO





to a Coverage Related cell when doing Serving E-DCH/HS-DSCH Cell Selection. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.2.3 IF Hard HO Hs Success Rate Incoming

KPI Name: IFHHO_SUCC_HS_IN RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

AttemptngHsHardHopmNoIncomiSuccessngHsHardHopmNoIncomi

* 100



KPI Description This KPI defines the percentage of successful attempts to do an incoming Hard HO for Hs RAB, over the total number of Incoming HS Hard Handover attempts. The pmNoIncomingHsHardHoSuccess counter provides the number of incoming successful Hard HO for serving HS-DSCH cell selection. The counter is stepped in the target cell after a RRC Physical Channel Reconfiguration Complete has been received from the UE during a Hard handover in Serving HS-DSCH Cell Selection. The pmNoIncomingHsHardHoAttempt provides the number of incoming attempted Hard HO for serving HS-DSCH cell selection. The counter is stepped in the target cell when a RRC Physical Channel Reconfiguration is sent to the UE during a Hard handover in Serving HS-DSCH Cell Selection. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC





basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.2.4 IF Hard HO Hs Success Rate Outgoing

KPI Name: IFHHO_SUCC_HS_OUT RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

AttemptngHsHardHopmNoOutgoiSuccessngHsHardHopmNoOutgoi

* 100



KPI Description This KPI defines the percentage of successful attempts to do an outgoing Hard HO for Hs RAB, over the total number of outgoing HS Hard Handover attempts. The pmNoOutgoingHsHardHoSuccess counter provides the number of Outgoing successful Hard HO for serving HS-DSCH cell selection. The counter is stepped in the source cell after a RRC Physical Channel Reconfiguration Complete has been received from the UE during a Hard handover in Serving HS-DSCH Cell Selection. The pmNoOutgoingHsHardHoAttempt provides the number of outgoing attempted Hard HO for serving HS-DSCH cell selection. The counter is stepped in the source cell when a RRC Physical Channel Reconfiguration is sent to the UE during a Hard handover in Serving HS-DSCH Cell Selection. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





11.2.5 IF Hard HO Hs Failure Rate Incoming

KPI Name: IFHHO_FAIL_HS_IN RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

AttemptngHsHardHopmNoIncomidChTargetHoReturnOlpmNoHsHard

* 100



KPI Description This KPI defines the percentage of failed attempts to do an incoming Hard HO for Hs RAB, over the total number of incoming HS Hard Handover attempts. The pmNoHsHardHoReturnOldChTarget counter provides the number of failed incoming Hard HO for serving HS-DSCH cell selection and UE connection maintained. The counter is stepped in the target cell after a RRC Physical Channel Reconfiguration Failure has been received from the UE during a Hard handover in Serving HS-DSCH Cell Selection. The pmNoIncomingHsHardHoAttempt provides the number of incoming attempted Hard HO for serving HS-DSCH cell selection. The counter is stepped in the target cell when a RRC Physical Channel Reconfiguration is sent to the UE during a Hard handover in Serving HS-DSCH Cell Selection. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





11.2.6 IF Hard HO Hs Failure Rate Outgoing

KPI Name: IFHHO_FAIL_HS_OUT RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

AttemptngHsHardHopmNoOutgoidChSourceHoReturnOlpmNoHsHard

* 100



KPI Description This KPI defines the percentage of failed attempts to do an outgoing Hard HO for Hs RAB, over the total number of outgoing HS Hard Handover attempts. The pmNoHsHardHoReturnOldChSource counter provides the number of failed outgoing Hard HO for serving HS-DSCH cell selection and UE connection maintained. The counter is stepped in the source cell after a RRC Physical Channel Reconfiguration Failure has been received from the UE during a Hard handover in Serving HS-DSCH Cell Selection. The pmNoOutgoingHsHardHoAttempt provides the number of outgoing attempted Hard HO for serving HS-DSCH cell selection. The counter is stepped in the source cell when a RRC Physical Channel Reconfiguration is sent to the UE during a Hard handover in Serving HS-DSCH Cell Selection. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.2.7 IF Hard HO Eul Success Rate Incoming





KPI Name: IFHHO_SUCC_EUL_IN RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value: In P6 counters stepped in SRNC, DRNC if



⎟⎠⎞

⎜⎝⎛

oAttemptngEulHardHpmNoIncomioSuccessngEulHardHpmNoIncomi

* 100

Units: % Note:

KPI Description This KPI defines the percentage of successful attempts to do an incoming Hard HO for Eul RAB, over the total number of Incoming Eul Hard Handover attempts. The pmNoIncomingEulHardHoSuccess provides the number of successful incoming Hard HO for serving E-DCH cell selection. The counter is stepped in the target cell. The counter is stepped in the target cell after a RRC Physical Channel Reconfiguration Complete has been received from the UE during a Hard handover in Serving E-DCH/HS-DSCH Cell Selection. The pmNoIncomingEulHardHoAttempt counter provides the number of attempted incoming Hard HO for serving E-DCH cell selection. The counter is stepped in the target cell. The counter is stepped in the target cell when a RRC Physical Channel Reconfiguration is sent to the UE during a Hard handover in Serving E-DCH/HS-DSCH Cell Selection. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.2.8 IF Hard HO Eul Success Rate Outgoing

KPI Name: IFHHO_SUCC_EUL_OUT RNC Sw Release: P6 Importance: Medium





Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value: In P6 counters stepped in SRNC, DRNC if



⎟⎠⎞

⎜⎝⎛

oAttemptngEulHardHpmNoOutgoioSuccessngEulHardHpmNoOutgoi

* 100

Units: % Note:

KPI Description This KPI defines the percentage of successful attempts to do an outgoing Hard HO for Eul RAB, over the total number of outgoing Eul Hard Handover attempts. The pmNoOutgoingEulHardHoSuccess counter provides the number of successful outgoing Hard HO for serving E-DCH cell selection. The counter is stepped in the best cell in the Active Set when the transition is triggered. The best cell is the cell with the highest measured quality defined by parameter UeMeasControl::hsQualityEstimate. The counter is stepped in the source cell after a RRC Physical Channel Reconfiguration Complete has been received from the UE during a Hard handover in Serving E-DCH/HS-DSCH Cell Selection. The pmNoOutgoingEulHardHoAttempt counter provides the number of attempted outgoing Hard HO for serving E-DCH cell selection. The counter is stepped in the best cell in the Active Set when the transition is triggered. The best cell is the cell with the highest measured quality defined by parameter UeMeasControl::hsQualityEstimate. The counter is stepped in the source cell when a RRC Physical Channel Reconfiguration is sent to the UE during a Hard handover in Serving E-DCH/HS-DSCH Cell Selection. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.2.9 IF Hard HO EUL Failure Rate Incoming

KPI Name: IFHHO_FAIL_EUL_IN RNC Sw Release: P6





Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

oAttemptngEulHardHpmNoIncomildChTargetdHoReturnOpmNoEulHar

* 100



KPI Description This KPI defines the percentage of failed attempts to do an incoming Hard HO for Eul RAB, over the total number of incoming Eul Hard Handover attempts. The pmNoEulHardHoReturnOldChTarget providees the number of failed Hard HO for serving E-DCH cell selection and UE maintained. The counter is stepped in the target cell. The counter is stepped in the target cell after a RRC Physical Channel Reconfiguration Failure has been received from the UE during a Hard handover in Serving E-DCH/HS-DSCH Cell Selection. The pmNoIncomingEulHardHoAttempt counter provides the number of attempted incoming Hard HO for serving E-DCH cell selection. The counter is stepped in the target cell. The counter is stepped in the target cell when a RRC Physical Channel Reconfiguration is sent to the UE during a Hard handover in Serving E-DCH/HS-DSCH Cell Selection. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.2.10 IF Hard HO Eul Failure Rate Outgoing

KPI Name: IFHHO_FAIL_EUL_OUT RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC





Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


⎟⎠⎞

⎜⎝⎛

oAttemptngEulHardHpmNoOutgoildChSourcedHoReturnOpmNoEulHar

* 100



KPI Description This KPI defines the percentage of failed attempts to do an outgoing Hard HO for Eul RAB, over the total number of outgoing Eul Hard Handover attempts. The pmNoEulHardHoReturnOldChSource counter provides the number of failed Hard HO for serving E-DCH cell selection and UE maintained. The counter is stepped in the best cell in the Active Set when the transition is triggered. The best cell is the cell with the highest measured quality defined by parameter UeMeasControl::hsQualityEstimate. The counter is stepped in the source cell after a RRC Physical Channel Reconfiguration Failure has been received from the UE during a Hard handover in Serving E-DCH/HS-DSCH Cell Selection. The pmNoOutgoingEulHardHoAttempt counter provides the number of attempted outgoing Hard HO for serving E-DCH cell selection. The counter is stepped in the best cell in the Active Set when the transition is triggered. The best cell is the cell with the highest measured quality defined by parameter UeMeasControl::hsQualityEstimate. The counter is stepped in the source cell when a RRC Physical Channel Reconfiguration is sent to the UE during a Hard handover in Serving E-DCH/HS-DSCH Cell Selection. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.2.11 IF Hard HO PS Streaming Hs Success Rate Incoming

KPI Name: IFHHO_SUCC_PSSTR_HS_IN RNC Sw Release: P6 Importance: Medium







⎟⎠⎞

⎜⎝⎛

ptHsHhoAttemngPsStreampmNoIncomissHsHhoSuccengPsStreampmNoIncomi

* 100


IurLink::srncPmReporting = ON in SRNC New RAB in P6, new KPI.

KPI Description

This KPI defines the percentage of successful attempts to an incoming Hard HO for serving HS-DSCH cell selection for PS Streaming Hard Handover attempts. The counter pmNoIncomingPsStreamHsHhoSuccess provides number of successful Hard HO for serving HS-DSCH cell selection for PS Streaming. Target cell. It is incremented by one in the target cell after a RRC Physical Channel Reconfiguration Complete has been received from the UE during a Hard handover in Serving HS-DSCH Cell Selection for PS Streaming.

The counter pmNoIncomingPsStreamHsHhoAttempt provides number of attempted Hard HO for serving HS-DSCH cell selection for PS Streaming. Target cell. It is incremented by one in the target cell when a RRC Physical Channel Reconfiguration is sent to the UE during a Hard handover in Serving HS-DSCH Cell Selection for PS Streaming. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.2.12 IF Hard HO PS Streaming HS Success Rate Outgoing

KPI Name: IFHHO_SUCC_PSSTR_HS_OUT RNC Sw Release: P6 Importance: Medium







⎟⎠⎞

⎜⎝⎛

ptHsHhoAttemngPsStreampmNoOutgoissHsHhoSuccengPsStreampmNoOutgoi

* 100



KPI Description

This KPI defines the percentage of successful attempts to an incoming Hard HO for serving HS-DSCH cell selection for PS Streaming Hard Handover attempts. The counter pmNoOutgoingPsStreamHsHhoSuccess provides number of successful Hard HO for serving HS-DSCH cell selection for PS Streaming. Source cell. It is incremented by one in the target cell after a RRC Physical Channel Reconfiguration Complete has been received from the UE during a Hard handover in Serving HS-DSCH Cell Selection for PS Streaming.

The counter pmNoOutgongPsStreamHsHhoAttempt provides number of attempted Hard HO for serving HS-DSCH cell selection for PS Streaming. Source cell. It is incremented by one in the target cell when a RRC Physical Channel Reconfiguration is sent to the UE during a Hard handover in Serving HS-DSCH Cell Selection for PS Streaming. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

11.2.13 IF Hard HO PS Streaming HS Failure Rate Incoming

KPI Name: IFHHO_FAIL_PSSTR_HS_IN RNC Sw Release: P6 Importance: Medium







⎟⎠⎞

⎜⎝⎛

ptHsHhoAttemngPsStreampmNoIncomieturnOldTargamHsHhoRetpmNoPsStre

* 100



KPI Description

This KPI defines the percentage of failed incoming Hard HO for serving HS-DSCH cell selection and UE connection maintained for PS Streaming

The counter pmNoPsStreamHsHhoReturnOldTarget provides Number of failed Hard HO for serving HS-DSCH cell selection and UE connection maintained for PS Streaming. Target Cell. It is incremented by one in the target cell after a RRC Physical Channel Reconfiguration Failure has been received from the UE during a Hard handover in Serving HS-DSCH Cell Selection for PS Streaming.


11.2.14 IF Hard HO PS Streaming Hs Failure Rate Outgoing

KPI Name: IFHHO_FAIL_PSSTR_HS_OUT RNC Sw Release: P6 Importance: Medium







⎟⎠⎞

⎜⎝⎛

ptHsHhoAttemngPsStreampmNoIncomiceurnOldSouramHsHhoRetpmNoPsStre

* 100



KPI Description

This KPI defines the percentage of failed outgoing Hard HO for serving HS-DSCH cell selection and UE connection maintained for PS Streaming

The counter pmNoPsStreamHsHhoReturnOldSource provides Number of failed Hard HO for serving HS-DSCH cell selection and UE connection maintained for PS Streaming. Source Cell. It is incremented by one in the target cell after a RRC Physical Channel Reconfiguration Failure has been received from the UE during a Hard handover in Serving HS-DSCH Cell Selection for PS Streaming.






12 Mobility HSDPA , EUL and PS Streaming HS

12.1 HSDPA Mobility

12.1.1 HSDPA Cell Change SR

KPI Name: HS_CC_SUCC_RATE RNC Sw Release: 6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


temptpmNoHsCcAtccesspmNoHsCcSu

* 100

Units: % Note:

KPI Description The KPI defines the success rate for Cell Change for HS RABs. It calculated as the rate between Cell Change succeeded and attempted Serving HS-DSCH Cell Change, counted on target cell. The pmNoHsCcAttempt counter is stepped after a RRC Physical Channel Reconfiguration has been sent to the UE during HS-DSCH Cell Change. The pmNoHsCcSuccess counter is stepped after a RRC Physical Channel Reconfiguration Complete has been received from the UE during HS-DSCH Cell Change. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





12.1.2 HSDPA to DCH Reconfiguration SR

KPI Name: HS_DCH_SUCC_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


ttemptpmHsToDchAuccesspmHsToDchS*100

Units: % Note: Counters pmHsToDchAttempt and pmHsToDchSuccess

stepped in the Best AS cell

KPI Description This KPI evaluates the success rate of HSDPA to DCH/DCH transitions. A transition HSDPA to DCH can occur in different scenario and according to network parameter setting. The parameter structure hsToDchTrigger can be set such that:

- hsToDchTrigger.poorQualityDetected regulates the possibility of a HS->DCH transition if a bad quality has been detected for an HS connection (events 2d, 6d)

- hsToDchTrigger.changeOfBestCellIntraRnc regulates the possibility of a HS->DCH transition when Serving HS-DSCH Cell Change can not be completed, when it has been triggered by a Change of Best Cell

- hsToDchTrigger.servHsChangeInterRnc regulates the possibility of a HS->DCH transition when the serving HS-DSCH cell is removed from the Active Set, a Serving HS-DSCH Cell Change can not be completed and the best cell is an inter-RNC UTRAN Cell.

- hsToDchTrigger.servHsChangeIntraRnc regulates the possibility of a HS->DCH transition when the serving HS-DSCH cell is removed from the Active Set, a Serving HS-DSCH Cell Change can not be completed and the best cell is an intra-RNC UTRAN Cell.

The counter pmHsToDchAttempt is the number of attempts to reconfigure a connection using a HS-DSCH to a DCH/DCH connection. The counter is stepped in the best cell in the Active Set when the transition is triggered, when Radio Bearer Reconfiguration is sent to the UE. The counter pmHsToDchSuccess is the number of successful reconfigurations of a connection using a HS-DSCH to a DCH





connection. The counter is stepped in the best cell in the Active Set when Radio Bearer Reconfiguration Complete is received from the UE. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





12.2 EUL Mobility

12.2.1 EUL Cell Change SR

KPI Name: EUL_CC_SUCC_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


ttemptpmNoEulCcAuccesspmNoEulCcS

*100

Units: % Note:

KPI Description The KPI defines the success rate for Cell Change for EUL/HS-DSCH. The pmNoEulCcAttempt counter is the number of attempted Serving E-DCH Cell Changes. The counter is incremented in the target cell after an RRC Physical Channel Reconfiguration/ Radio Bearer Reconfiguration has been sent to the UE during E-DCH/HS-DSCH Cell Change. The pmNoEulCcSuccess counter is the number of successful Serving E-DCH Cell Changes. The counter is incremented in the target cell after a RRC Physical Channel Reconfiguration Complete / Radio Bearer Reconfiguration Complete has been received from the UE during E-DCH/HS-DSCH Cell Change. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

12.2.2 EUL to DCH Reconfiguration SR





KPI Name: EUL_DCH_SUCC_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


AttemptpmEulToDchSuccesspmEulToDch*100

Units: % Note: Counters pmEulToDchAttempt and pmEulToDchSuccess

stepped in the Best AS cell

KPI Description This KPI evaluates the success rate of EUL/HSDPA to DCH/HS or DCH/DCH transitions. A transition EUL/HSDPA to DCH/HS or DCH/DCH can occur in different scenario and according to network parameter setting. The parameter structure hsToDchTrigger can be set such that:





Further to HS->DCH transitions, a EUL/HS to DCH/HS reconfiguration can occur if event1dRncThreshold (=4) consecutive events 1a and/or events 1c are received requesting to add the same non-EUL capable cell, and all reports are event1dRncOffset(=0) stronger than the current serving cell. In this case a reconfiguration to DCH in UL is triggered. The counter pmEulToDchAttempt is the number of attempted channel switches from E-DCH to a lower capability channel, that is, DCH/HS-DSCH or DCH/DCH.





The counter is stepped in the best cell in the Active Set when the transition is triggered (Radio Bearer Reconfiguration is sent to the UE). The counter pmEulToDchSuccess is the number of successful channel switches from E-DCH to a lower capability channel, that is, DCH/HS-DSCH or DCH/DCH. The counter is stepped in the best cell in the Active Set when the transition is concluded (Radio Bearer Reconfiguration Complete is received from the UE). This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





12.3 PS Streaming HS Mobility

12.3.1 PS Streaming HS Cell Change SR

KPI Name: PSSTRHS_CC_SUCC_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


mptamHsCcAttepmNoPsStreessamHsCcSuccpmNoPsStre

*100

Units: % Note: New counters introduced in P6

KPI Description The KPI defines the success rate for HS cell change attempts of RAB type streaming PS (HS), counted on the HS-serving cell. The pmNoPsStreamHsCcAttempt counter is the number of HS cell change attempts for RAB type streaming PS (HS), counted on the HS-serving cell. Incremented by one in the target cell at Serving HS-DSCH Cell Change attempt, when a Physical Channel Reconfiguration is sent to the UE.

The pmNoPsStreamHsCcSuccess counter is the number of successful HS cell change attempts for RAB type streaming PS (HS), counted on the HS-serving cell. Incremented by one in the target cell at Serving HS-DSCH Cell Change success, when a Physical Channel Reconfiguration Complete is received from the UE. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





12.3.2 PS Streaming HS to DCH Reconfiguration SR

KPI Name: PSSTRHS_DCH_SUCC_RATE RNC Sw Release: P6 Importance: Medium Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: PEG Target Value:


emptHsToDchAttpmPsStreamcessHsToDchSucpmPsStream*100


KPI Description This KPI evaluates the success rate of reconfiguration of HS-DSCH to DCH attempts for RAB type streaming PS (HS). A transition HSDPA to DCH/HS or DCH/DCH can occur in different scenario and according to network parameter setting. The parameter structure hsToDchTrigger can be set such that:





The counter pmPsStreamHsToDchAttempt is the number of reconfiguration HS-DSCH to DCH attempts for RAB type streaming PS (HS), counted in the best cell. Incremented by one in the best cell at HS-DSCH to DCH reconfiguration attempt for PS Streaming, when a Radio Bearer Reconfiguration is sent to the UE. The counter pmEulToDchSuccess is the number of successful reconfiguration HS-DSCH to





DCH successes for RAB type streaming PS (HS), counted in the best cell. Incremented by one in the best cell at HS-DSCH to DCH reconfiguration success for PS Streaming, when a Radio Bearer Reconfiguration Complete is received from the UE. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.





13 MBMS

13.1.1 Overall Accessibility Success Rate MBMS

KPI Name: MBMS_SESSUCCRATE RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: MbmsCch Counters Type: PEG Target Value:


⎟⎟⎠

⎞⎜⎜⎝

⎛ontMbmsSessipmNoAttemponsMbmsSessipmNoSucces

*100

Units: % Note: In P6 MBMS service has been introduced

KPI Description This KPI is an indication of accessibility for MBMS session, during the MBMS bearer service setup establishment phase. The counter pmNoAttemptMbmsSession is incremented by one when the cell is included in the set of PL cells at MBMS Session Start requested from SGSN. The counter is only stepped when a new MBMS session is about to start, i.e. re-establish attempts are NOT included

The counter pmNoSuccessMbmsSession is Incremented by one for each first successful establishment of an MBMS session in a PL cell. Any re-establishment of this session in this cell does not cause any step of the counter, that is, the counter is at maximum stepped once for each MBMS session in a cell This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give poor performances.

Note: These counters come with new MO class MbmsCch





13.1.2 Session Establishment Blocked due to TN MBMS

KPI Name: SESSION_BLOCK_TN_MBMS RNC Sw Release: P6 Importance: High Scope: RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: MbmsCch Counters Type: PEG Target Value:


nLackTnResMbmsSessiopmNoFailed

Units: Note: In P6 MBMS service has been introduced.

KPI Description This KPI provides the number of session establishment attempts for MBMS service that are blocked due to TN congestion or TN failure. This counter indicates number of un-successful MBMS session start attempts due to lack of TN resources. The counter is only stepped max. once per round of retries of all MBMS sessions in the pending queue in order to give the desired observability. This counter incremented by one, at maximum once per round of retries of all sessions in the pending queue, for a failed attempt to establish an MBMS session in a PL cell due to lack of TN resources The counter is stepped if the cell is in the SRNC.

13.1.3 Session Drop Rate MBMS

KPI Name DROPRATE_MBMS RNC Sw Release: P6 Importance: High





Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: MbmsCch Counters Type: PEG Target Value: NA


onStartsMbmsSessipmNoSuccesnStopMbmsSessiopmNoSystem

*100

Units: % Note: In P6 MBMS service has been introduced

KPI Description The KPI defines the drop rate for MBMS RB on Cell basis (all counters defined in MO class “MbmsCch”). It can be seen as the ratio between all the abnormal session releases over the total number of all session started. The counter pmNoSystemMbmsSessionStop is incremented by one for each MBMS session stop triggered by the WRAN system or due to a CN problem (i.e. system internal). This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

13.1.4 Cell Traffic MBMS

KPI Name: ERL_MBMS RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: MbmsCch Counters Type: ACC, SCAN Target Value:






bmsTrafficpmSamplesM

rafficpmSumMbmsT

Units: Erl Note: In P6 MBMS service has been introduced

KPI Description The formula defines the traffic value (in Erlangs), aggregated on cell level, for MBMS session. It is calculated as the ratio between Accumulator counter and the Scan counter for MBMS session. The pmSumMbmsTraffic sum all sample values recorded during a ROP for the MBMS traffic intensity. Values are read periodically from an internal level counter and added to this counter. The level counter maintains the current traffic intensity. The level counter is stepped as follows:

1x number of ongoing MBMS sessions with rate level 64.8 kbps + 2 x number of ongoing MBMS sessions with rate level 129.6 kbps + 4 x number of ongoing MBMS sessions with rate level 259.2 kbps +

The counted MBMS sessions are only those for which the cell is a PL cell and for which the concerned resources are established in the cell. Sampling at 5s interval

The pmSamplesMbmsTraffic counter, as a Scan counter, provides the number of samples collected by pmSumMbmsTraffic.

This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results. And of course, for optimization purpose or for finer RAB traffic monitor, this formula can be disaggregated, taking into consideration one RAB at the time.

13.1.5 Successful Sessions MBMS

KPI Name: NUMSESSION_MBMS RNC Sw Release: P6 Importance: High Scope: Mbms Granularity: ROP – 15’





Time Resolution: 1 hour Counters MO Class: MbmsCch Counters Type: PEG Target Value:


onStartsMbmsSessipmNoSucces

Units: Sessions Note: In P6 MBMS service has been introduced

KPI Description

The pmNoSuccessMbmsSessionStart counter incremented by one for each successful MBMS session start in a PL cell independent of if this is the first start or a re-establishment. Note: This counter is only incremented in the SRNC. Note that the MO class of the counters above is MbmsCch.

13.1.6 MBMS Session Admission Failure

KPI Name: MBMS_ADM_FAIL RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: MbmsCch Counters Type: PEG Target Value:


nLackRnResMbmsSessiopmNoFailed

Units: Note: In P6 MBMS service has been introduced

KPI Description This KPI is an indication of admission failure on MBMS session due to lack of radio network resources.





The counter pmNoFailedMbmsSessionLackRnRes is Incremented by one, at maximum once per round of retries of all sessions in the pending queue, for a failed attempt to establish an MBMS session in a PL cell due to lack of RN resources. Number of un-successful MBMS session start attempts due to lack of RN resources.

The counter is only stepped max. once per round of retries of all MBMS sessions in the pending queue in order to give the desired observability.

13.1.7 MBMS Average Session Throughput DL PS Streaming 64

KPI Name: MBMS_SESSION_DL_THROUGH_64 RNC Sw Release: P6 Importance: High Scope: Cell, RNC Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: MbmsCch Counters Type: TrigACC, TrigSCAN Target Value:


RlcUserThpsStrMbms64pmSamplesPserThpMbms64RlcUpmSumPsStr

Units: kbps Note: In P6 MBMS service has been introduced

KPI Description The formula evaluates the average session throughput for MBMS PS Streaming 64kbits in DL (kbps). It includes user data, Medium Access Control (MAC) and Radio Link Control (RLC) header information.

The counter pmSumPsStrMbms64RlcUserThp aggregate of all sample values recorded during a ROP for Streaming PS MBMS 64.8 RLC throughput amount. Values are read periodically from an internal level counter and added to this counter. The level counter maintains the current RLC throughput for Streaming PS MBMS 64.8. Counter sample at 0.5s interval.

The counter pmSamplesPsStrMbms64RlcUserThp is the number of samples in pmSumPsStrMbms64RlcuserThp (that is, pmSamplesPsStrMbms64RlcUserThp =





pmSamplesPsStrMbms64RlcUserThp +1, whenever pmSumPsStrMbms64RlcUserThp is to be updated).




p8RlcUserThsStrMbms12pmSamplesPUserThpMbms128RlcpmSumPsStr




The counter pmSamplesPsStrMbms128RlcUserThp is the number of samples in pmSumPsStrMbms128RlcuserThp (that is, pmSamplesPsStrMbms128RlcUserThp = pmSamplesPsStrMbms128RlcUserThp +1, whenever pmSumPsStrMbms128RlcUserThp is to be updated).








p6RlcUserThsStrMbms25pmSamplesPUserThpMbms256RlcpmSumPsStr




The counter pmSamplesPsStrMbms256RlcUserThp is the number of samples in pmSumPsStrMbms256RlcuserThp (that is, pmSamplesPsStrMbms256RlcUserThp = pmSamplesPsStrMbms256RlcUserThp +1, whenever pmSumPsStrMbms256RlcUserThp is to be updated).





14 Radio Resource Monitoring

14.1 Power

14.1.1 UL Average RSSI

KPI Name: UL_AVE_RSSI RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: TrigACC, TrigSCAN Target Value:


lRssipmSamplesUipmSumUlRss

Units: % Note:

KPI Description This KPI represents the average of Received Total Wideband Power in the Up Link.

The pmSumUlRssi counter incremented by the RTWP value, when a NBAP Common Measurement Report message containing a valid RTWP value is received. The RTWP Range is: 0-621 (corresponding to -112 ... -50dB).

The pmSamplesUlRssi counter provides the number of samples in pmSumUlRssi (i.e. pmSamplesUlRssi = pmSamplesUlRssi +1, whenever pmSumUlRssi is to be updated); it is reset at each ROP period.

14.1.2 UL Rssi Standard Deviation

KPI Name: UL_RSSI_STDEV RNC Sw Release: P6 Importance: Medium





Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: TrigSQR, TrigACC, TrigSCAN Target Value:


- RssipmSumSqrUl2

⎟⎟⎠

⎞⎜⎜⎝

⎛lRssipmSamplesU

ipmSumUlRsslRssipmSamplesU

Units: % Note:

KPI Description This kpi provides the standard deviation value of RTWP (Received Total Wideband Power) values received in NBAP Common Measurement Reports, where RTWP is a measurement of uplink RSSI.

The pmSumSqrUlRssi, as SQR counter, provides the squares of the individual measurements in pmSumUlRssi.

The pmSumUlRssi, as ACC counter, provides the Sum of valid RTWP values as a measurement of uplink RSSI.

The pmSamplesUlRssi, as SCAN counter, provides the Number of samples recorded within the ROP period for pmSumUlRssi (i.e. pmSamplesUlRssi = pmSamplesUlRssi +1, whenever pmSumUlRssi is to be updated); it is reset at each ROP period.





14.2 Code Consumption

14.2.1 DL Channelization Code Usage

KPI Name: DL_CODE_USAGE RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


lCodepmSamplesDepmSumDlCod

Units: % Note: The KPI measures R99 code usage only

KPI Description This KPI represents the average of Channelization Code usage in Down Link.

The pmSumDlCode counter provides the aggregate of DL Channelization code tree usage (percentage of lowest leaf, SF 256, usage: blocked or allocated) measurements.

The pmSamplesDlCode counter provides the number of samples in pmSumDlCode (i.e. pmSamplesDlCode = pmSamplesDlCode +1, whenever pmSumDlCode is to be updated); it is reset at each ROP period.

14.2.2 DL Channelization Code usage Standard Deviation

KPI Name: DL_CODE_STDEV RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’





Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: SQR, ACC, SCAN Target Value:


- CodepmSumSqrDl2

⎟⎟⎠

⎞⎜⎜⎝

⎛lCodepmSamplesD

epmSumDlCodlCodepmSamplesD

Units: % Note:

KPI Description This kpi provides the standard deviation value of of Channelization Code usage in Down Link. It’s expressed as the square root of the difference between the average amount of the squares of Channelization Code in Down Link and the square of the average amount of DL Channelization Code usage.

The pmSumSqrDlCode, as SQR counter, provides the sum of the squares of DL Channelization code tree usage (percentage of lowest leaf, SF 256, usage: blocked or allocated) measurements.

The pmSumDlCode, as ACC counter, provides the aggregate of DL Channelization code tree usage (percentage of lowest leaf, SF 256, usage: blocked or allocated) measurements.

The pmSamplesDlCode, as SCAN counter, provides the number of samples in pmSumDlCode (i.e. pmSamplesDlCode = pmSamplesDlCode +1, whenever pmSumDlCode is to be updated); it is reset at each ROP period





14.3 Credit Consumption

14.3.1 DL Credit Usage

KPI Name: DL_CREDIT_USAGE RNC Sw Release: P6 Importance: High Scope: RBS Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IubLink Counters Type: TrigACC, TrigSCAN Target Value:


lCreditspmSamplesDditspmSumDlCre

Units: Credits Note: This counters introduced in P5.0.23

KPI Description This KPI represents the average of RBS Credits usage in Down Link.

The pmSumDlCredits sums all sample values recorded during a ROP for consumed RBS DL credit measurements. Values are read periodically from an internal level counter and added to this counter.

The level counter maintains the current number of consumed RBS DL credits. Sample rate: 2s. Stepped in CRNC

The pmSamplesDlCredits counter provides the number of samples in pmSumDlCredits (i.e. pmSamplesDlCredits = pmSamplesDlCredits +1, whenever pmSumDlCredits is to be updated); it is reset at each ROP period.

14.3.2 DL Credits Usage Standard Deviation

KPI Name: DL_CREDIT_STDEV RNC Sw Release: P6 Importance: Medium





Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IubLink Counters Type: TrigSQR, TrigACC, TrigSCAN Target Value:


- CreditspmSumSqrDl2

⎟⎟⎠

⎞⎜⎜⎝

⎛lCreditspmSamplesD

ditspmSumDlCrelCreditspmSamplesD

Units: Credits Note:

KPI Description This kpi provides the standard deviation value of RBS credits consumed in Down Link. It’s expressed as the square root of the difference between the average amount of the squares of comsumed RBS credits measurements and the square of the average amount of comsumed RBS credits measurements.

The pmSumSqrDlCredits, as SQR counter, provides the sum of the squares of the consumed RBS credits measurements (in credits).

The pmSumDlCredits, as ACC counter, provides the aggregate of total consumed RBS credits measurements (in credits).

The pmSamplesDlCredits, as SCAN counter, provides the number of samples collected by pmSumDlCredits. This counter is reset at each ROP period.

14.3.3 DL Cedits Consumption Distribution

KPI Name: DL_CREDIT_CONSUMED RNC Sw Release: P6 Importance: High Scope: RBS Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IubLink Counters Type: PDF





Target Value:


spmDlCredit

Units: % Note: This counters introduced in P5.0.23

KPI Description Counter pmDlCredits measures the total consumed RBS DL credits. Incremented by one when a sample is within its range. Sampling rate: 2s

Reported according to the following intervals(range):

[0] : 0 <= x < 25 (%) [1] : 25 <= x < 50 [2] : 50 <= x < 60 [3] : 60 <= x < 70 [4] : 70 <= x < 75 [5] : 75 <= x < 80 [6] : 80 <= x < 85 [7] : 85 <= x < 90 [8] : 90 <= x < 95 [9] : 95 <= x

14.3.4 UL Credit Usage

KPI Name: UL_CREDIT_USAGE RNC Sw Release: P6 Importance: High Scope: RBS Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IubLink Counters Type: TrigACC, TrigSCAN Target Value:


lCreditspmSamplesUditspmSumUlCre






KPI Description This KPI represents the average of RBS Credits usage in Up Link.

The pmSumUlCredits sums all sample values recorded during a ROP for consumed RBS DL credit measurements. Values are read periodically from an internal level counter and added to this counter.

The level counter maintains the current number of consumed RBS UL credits. Sample rate: 2s. Stepped in CRNC

The pmSamplesUlCredits counter provides the number of samples in pmSumUlCredits (i.e. pmSamplesUlCredits = pmSamplesUlCredits +1, whenever pmSumUlCredits is to be updated); it is reset at each ROP period.

14.3.5 UL Credits Standard Deviation

KPI Name: UL_CREDIT_STDEV RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IubLink Counters Type: TrigSQR, TrigACC, TrigSCAN Target Value:


- CreditspmSumSqrUl2

⎟⎟⎠

⎞⎜⎜⎝

⎛lCreditspmSamplesU

ditspmSumUlCrelCreditspmSamplesU

Units: Credits Note:

KPI Description This kpi provides the standard deviation value of RBS credits consumed in Up Link. It’s expressed as the square root of the difference between the average amount of the squares of comsumed RBS credits measurements and the square of the





average amount of comsumed RBS credits measurements.

The pmSumSqrUlCredits, as SQR counter, provides the sum of the squares of the consumed RBS credits measurements (in credits).

The pmSumUlCredits, as ACC counter, provides the aggregate of total consumed RBS credits measurements (in credits).

The pmSamplesUlCredits, as SCAN counter, provides the number of samples collected by pmSumUlCredits. This counter is reset at each ROP period.

14.3.6 UL Cedits Consumption Distribution

KPI Name: UL_CREDIT_CONSUMED RNC Sw Release: P6 Importance: High Scope: RBS Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IubLink Counters Type: PDF Target Value:


spmUlCredit


KPI Description Counter pmUlCredits measures the total consumed RBS UL credits. Incremented by one when a sample is within its range. Sampling rate: 2s. Stepped in CRNC

Reported according to the following intervals(range):

[0] : 0 <= x < 25 (%) [1] : 25 <= x < 50 [2] : 50 <= x < 60 [3] : 60 <= x < 70 [4] : 70 <= x < 75 [5] : 75 <= x < 80 [6] : 80 <= x < 85 [7] : 85 <= x < 90 [8] : 90 <= x < 95





[9] : 95 <= x





14.4 ASE Consumption

14.4.1 DL Ase Usage

KPI Name: DL_ASE_USAGE RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


AseDlpmNoOfSamppAseDlpmSumOfSam

Units: 0.01 ASE Note: These counters are new in P6

KPI Description This KPI represents the average ASE consumption in DL.

The pmSumOfSampAseDl defines the sum of all sample values recorded during a ROP for the level of ASE in the DL in the cell. The values are read periodically from an internal level counter and added to this counter. The level counter maintains the current level of ASE in the DL in the cell..

The pmNoOfSampAseDl defines the number of samples recorded within the ROP period for pmSumOfSampAseDl. Incremented by one when the corresponding sum counter is incremented.

The pmNoOfSampAseDl counter provides the number of samples in pmSumOfSampAseDl (i.e. pmNoOfSamplAseDl = pmNoOfSamplAseDl +1, whenever pmSumOfSampAseDl is to be updated); it is reset at each ROP period.





14.4.2 UL Ase Usage

KPI Name: UL_ASE_USAGE RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: UtranCell Counters Type: ACC, SCAN Target Value:


AseUlpmNoOfSamppAseUlpmSumOfSam

Units: 0.01 ASE Note: These counters are new in P6

KPI Description This KPI represents the average ASE consumption in UL.

The pmSumOfSampAseUl defines the sum of all sample values recorded during a ROP for the level of ASE in the UL in the cell. The values are read periodically from an internal level counter and added to this counter. The level counter maintains the current level of ASE in the UL in the cell..

The pmNoOfSampAseUl defines the number of samples recorded within the ROP period for pmSumOfSampAseUl. Incremented by one when the corresponding sum counter is incremented.

The pmNoOfSampAseUl counter provides the number of samples in pmSumOfSampAseUl (i.e. pmNoOfSamplAseUl = pmNoOfSamplAseUl +1, whenever pmSumOfSampAseUl is to be updated); it is reset at each ROP period.





14.5 Node Synchronization

14.5.1 Out Of Sequence Frames UL

KPI Name: DCH_FRAME_OUTSEQ_UL RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IubLink, IurLink Counters Type: PEG Target Value:


enceUlsOutOfSequpmDchFrame


KPI Description The KPI used to monitor number of Iub DCH FP frames received out-of-sequence in UL. (Incremented in the SRNC direction for IurLink)

The pmDchFramesOutOfSequenceUl incremented by one when an out-of-sequence DCH frame protocol frame is received. A frame is considered to be out-of-sequence if frame_n(or less) arrives after frame_n+1. The counter is stepped only when the underlying transport network is IP. This KPI can be computed on a per RNC basis as well as a per cell basis. When computing the RNC result, individual cell counters should be summed on a RNC basis before applying KPI calculation. This is in contrast to applying the KPI equation to each cell and then taking an average across the RNC. The latter can give incorrect results.

14.5.2 Dynamic Delay on Radio Network Layer

KPI Name: DYN_DELAY_RN RNC Sw Release: P6





Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: NodeSynch Counters Type: GUAGE Target Value:


yMaxynamicDelapmIubLinkD


KPI Description The KPI used to monitor maximum dynamic delay in milliseconds between the RNC and RBS on the radio network layer.

The pmIubLinkDynamicDelayMax sets to the maximum one-way delay detected during node synchronisation on the FACH common channel, at the end of each ROP. The maximum one-way delay is regarded as the dynamic delay between RNC and RBS. This delay can be the delay in either the RNC to RBS or RBS to RNC direction whichever is the largest. This KPI can be computed on a per RBS basis only.

Good (i.e.small and unchanging) delay variation on the radio network layer is important to ensure better performance of radio clock accuracy in the RNC and RBS. Monitoring the delay variation can indicate both the accuracy of the radio clock and the quality of the radio connection end-to-end. If increasing delay variations are observed, this information may be used to detect if there is congestion in the network

14.5.3 Static Delay on Radio Network Layer

KPI Name: STA_DELAY_RN RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour





Counters MO Class: NodeSynch Counters Type: GUAGE Target Value:

KPI Recommended Formula taticDelaypmIubLinkS


KPI Description The KPI used to monitor maximum dynamic delay in milliseconds between the RNC and RBS on the radio network layer.

The pmIubLinkStaticDelay set to the lowest one-way delay detected between RNC and RBS, at the end of each ROP. This lowest delay value is considered to be the static delay, which is the delay experienced when the end-to-end connection is lightly loaded and the delay is due only to propogation and transmission delay in the network. The value recorded to the counter can be either the one-way delay from RNC to RBS, or from RBS to RNS, whichever is the lowest. This KPI can be computed on a per RBS basis only. It is useful to monitor delay in the network since certain services will not perform at an acceptable level if delay between hosts/nodes is large, the larger the delay the more difficult it is for high bandwidths to be sustained. Recording the lowest one-way delay will provide an indication of the delay experienced when the end-to-end connection is lightly loaded and the delay is due only to propagation and transmission delay in the network, in other words the Static Delay





14.6 Flow Controlled

14.6.1 HS Capacity Allocation Congestion Iub

KPI Name: HS_CA_CONG_IUB RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IubLink Counters Type: PEG Target Value:


CongpmHsSevere


KPI Description The KPI used to monitor number of severe congestion occurrences detected by the 'CAPACITY ALLOCATION Presence Supervision' function in RNC.

A CAPACITY ALLOCATION control frame is expected at least once per second from the RBS, per flow controlled HS flow. If a CA control frame hasn't been received for a fixed period of time, an HS Severe Congestion is considered to have occured. For each time period that passes without CA control frames having been correctly received, the counter is stepped by one. The counter should normally be zero. A non-zero value indicates that the uplink throughput has been congested, which prevented CAPACITY ALLOCATION control frames from coming through

The counter pmHsSevereCong is incremented by one when a severe congestion is detected by the "CAPACITY ALLOCATION Presence Supervision" function in RNC. A CAPACITY ALLOCATION control frame is expected at least every one second from RBS per flow controlled HS flow. If a CA hasn't been received for a longer period of time, an HS Severe Congestion is detected These interface counters shall normally be zero.





14.6.2 HS Capacity Allocation Congestion Iur

KPI Name: HS_CA_CONG_IUR RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IurLink Counters Type: PEG Target Value:


CongpmHsSevere


KPI Description The KPI used to monitor number of severe congestion occurrences detected by the 'CAPACITY ALLOCATION Presence Supervision' function in RNC.

A CAPACITY ALLOCATION control frame is expected at least once per second from the RBS, per flow controlled HS flow. If a CA control frame hasn't been received for a fixed period of time, an HS Severe Congestion is considered to have occured. For each time period that passes without CA control frames having been correctly received, the counter is stepped by one. The counter should normally be zero. A non-zero value indicates that the uplink throughput has been congested, which prevented CAPACITY ALLOCATION control frames from coming through

The counter pmHsSevereCong is Incremented by one for each severe congestion occurrence detected by the "CAPACITY ALLOCATION Presence Supervision" function in RNC. This is done per Iub/Iur interface. A CAPACITY ALLOCATION control frame is expected at least every one second from RBS per flow controlled HS flow. If a CA hasn't been received for a longer period of time, an HS Severe Congestion is detected These interface counters shall normally be zero.





14.6.3 E-DCH Data Frame Lost Ratio

KPI Name: EDCH_DF_LR RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IubEdch, IurLink Counters Type: PEG Target Value:


ceivedFramespmEdchDataFramesLostpmEdchData

Re*100


KPI Description The KPI used to monitor ratio of EDCH Data Frame lost over Iub and Iur.

The counter pmEdchDataFramesLoss is number of lost E-DCH Data frames. It will be incremented by one when an erroneous E-DCH data frame is received. The counter only considers the E-DCH data frames which carry payload towards the core network. Erroneous E-DCH data frames are those with wrong header CRC, wrong payload CRC and the ones not received at all (which can be detected to a certain degree by the use of the Frame Sequence Number, limited by the FSN length of 16). The counter pmEdchDataFramesReceived is Number of correctly received E-DCH Data frames. It will be Incremented by one when a correct E-DCH data frame is received. The counter only considers the E-DCH data frames which carry payload towards the core network. It is a measurement valid per Iub and Iur interface. The number of counter instances in RNC is equal to the number of EUL capable Iub and Iur interfaces that RNC supports

14.6.4 E-DCH Flow Dynamic Delay Over Iub

KPI Name: EDCH_F_DYNDLIUB





RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IubEdch Counters Type: PEG Target Value:


IubFrameDelaypmEdchData


KPI Description The KPI provide an overview of Dynamic Delay for EDCH Flow over Iub interface.

The counter pmEdchDataFramesDelayIub is the delay measurement when receiving an E-DCH frame. Increment by one when a measured delay sample is within its range.

Enhanced Uplink Iub dynamic delay measurement results. Reported according to the following intervals: [0] : 0 <= x < 10 (ms) [1] : 10 <= x < 20 [2] : 20 <= x < 30 [3] : 30 <= x < 40 [4] : 40 <= x < 50 [5] : 50 <= x < 60 [6] : 60 <= x < 70 [7] : 70 <= x < 80 [8] : 80 <= x < 90 [9] : 90 <= x < 100 [10] : 100 <= x < 110 [11] : 110 <= x < 120 [12] : 120 <= x < 130 [13] : 130 <= x < 140 [14] : 140 <= x < 150 [15] : x >= 150





14.6.5 E-DCH Flow Dynamic Delay Over Iur

KPI Name: EDCH_F_DYNDLIUR RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: IurLink Counters Type: PEG Target Value:


IubFrameDelaypmEdchData


KPI Description The KPI provide an overview of Enhanced Uplink Iub dynamic delay measurement results between RBS and SRNC, that is, the buffer build-up delay distribution

The counter pmEdchDataFramesDelayIub bridges both Iur and Iub and therefore reflects the delay across both. Note that the naming of this measurement uses "Iub" only as part of the name, despite bridging both Iub and Iur. Increment by one when a measured delay sample is within its range.

Enhanced Uplink Iub dynamic delay measurement results. Reported according to the following intervals: [0] : 0 <= x < 10 (ms) [1] : 10 <= x < 20 [2] : 20 <= x < 30 [3] : 30 <= x < 40 [4] : 40 <= x < 50 [5] : 50 <= x < 60 [6] : 60 <= x < 70 [7] : 70 <= x < 80 [8] : 80 <= x < 90 [9] : 90 <= x < 100 [10] : 100 <= x < 110 [11] : 110 <= x < 120 [12] : 120 <= x < 130 [13] : 130 <= x < 140





[14] : 140 <= x < 150 [15] : x >= 150





15 UE Positioning

15.1 Cell ID Positioning

15.1.1 Cell ID Positioning Success QoS Rate

KPI Name: UE_POSITION_CELLID_SQOSR RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: PositioningServiceClass Counters Type: PEG Target Value:


temptpmCellIDAtccQosOkpmCellIdSu*100


KPI Description The KPI provide rate of successful positioning attempts, using the Cell Id positioning method, which met the requested QoS level.

The counter pmCellIdSuccQosok defines the number of successful positioning attempts, using the Cell Id positioning method, which met the requested QoS level. Counter is incremented by one when a cell ID positioning attempt is successfully completed, with a QoS that meets the requested QoS.

The counter pmCellIDAttempt defines number of positioning attempts using the Cell Id positioning method. The counter incremented by one when a cell ID positioning attempt is started.

15.1.2 Cell ID Positioning Failure QoS Rate





KPI Name: UE_POSITION_CELLID_FQOSR RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: PositioningServiceClass Counters Type: PEG Target Value:


temptpmCellIDAtccQosNokpmCellIdSu*100


KPI Description The KPI provide rate of successful positioning attempts, using the Cell Id positioning method, which does not met the requested QoS level.

The counter pmCellIdSuccQosok defines the number of successful positioning attempts, using the Cell Id positioning method, which met the requested QoS level. Counter is incremented by one when a cell ID positioning attempt is successfully completed, with a QoS that does not meets the requested QoS.

The counter pmCellIDAttempt defines number of positioning attempts using the Cell Id positioning method. The counter incremented by one when a cell ID positioning attempt is started.





15.2 RTT Positioning

15.2.1 RTT Positioning Success QoS Rate

KPI Name: RTT_POSITION_CELLID_SQOSR RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: PositioningServiceClass Counters Type: PEG Target Value:


ptpmRttAttemosOkpmRttSuccQ*100


KPI Description The KPI provide rate of successful positioning attempts, using the RTT positioning method, which met the requested QoS level.

The counter pmRttSuccQosok defines the number of successful positioning attempts, using the RTT positioning method, which met the requested QoS level. Counter is incremented by one when a RTT positioning attempt is successfully completed, with a QoS that meets the requested QoS.

The counter pmRttAttempt defines number of positioning attempts using the RTT positioning method. The counter incremented by one when a RTT positioning attempt is started.

15.2.2 RTT Positioning Failure QoS Rate

KPI Name: RTT_POSITION_CELLID_FQOSR RNC Sw Release: P6





Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: PositioningServiceClass Counters Type: PEG Target Value:


ptpmRttAttemosNokpmRttSuccQ*100


KPI Description The KPI provide rate of successful positioning attempts, using the RTT positioning method, which does not met the requested QoS level.

The counter pmRttSuccQosok defines the number of successful positioning attempts, using the RTT positioning method, which met the requested QoS level. Counter is incremented by one when a RTT positioning attempt is successfully completed, with a QoS that does not meets the requested QoS.

The counter pmRttAttempt defines number of positioning attempts using the RTT positioning method. The counter incremented by one when a RTT positioning attempt is started.





15.3 AGPS Positioning

15.3.1 AGPS Positioning Success QoS Rate

KPI Name: AGPS_POSITION_CELLID_SQOSR RNC Sw Release: P6 Importance: Medium Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: PositioningServiceClass Counters Type: PEG Target Value:


mptpmAgpsAtteQosOkpmAgpsSucc*100


KPI Description The KPI provide rate of successful positioning attempts, using the AGPS positioning method, which met the requested QoS level.

The counter pmCellIdSuccQosok defines the number of successful positioning attempts, using the AGPS positioning method, which met the requested QoS level. Counter is incremented by one when a AGPS positioning attempt is successfully completed, with a QoS that meets the requested QoS.

The counter pmAgpsAttempt defines number of positioning attempts using the AGPS positioning method. The counter incremented by one when a AGPS positioning attempt is started.

15.3.2 AGPS Positioning Failure QoS Rate

KPI Name: AGPS_POSITION_CELLID_FQOSR RNC Sw Release: P6 Importance: Medium





Scope: Cell Granularity: ROP – 15’ Time Resolution: 1 hour Counters MO Class: PositioningServiceClass Counters Type: PEG Target Value:


mptpmAgpsAtteQosNokpmAgpsSucc*100


KPI Description The KPI provide rate of successful positioning attempts, using the AGPS positioning method, which does not met the requested QoS level.

The counter pmAgpsSuccQosok defines the number of successful positioning attempts, using the AGPS positioning method, which met the requested QoS level. Counter is incremented by one when a AGPS positioning attempt is successfully completed, with a QoS that does not meets the requested QoS.

The counter pmAgpsAttempt defines number of positioning attempts using the AGPS positioning method. The counter incremented by one when a AGPS positioning attempt is started.





16 Reference

[1] WCDMA RNC P5 KPIs Description 4/1553-FAF 102358 Uen A 2008-03-20

[2] Radio Network KPI WCDMA RAN 120/1553-HSD 10102/6 Uen A 2007-11-21

[3] Radio Network Performance Monitoring Counters, RNC RAN P5 – RAN P6 Delta Information 105/1553-HSD 10102/6 Uen B

[4] Performance Statistics Flowcharts for Counters 75/1551-AXD 10503/1 Uen B (RNC)

[5] Performance Statistics, 73/1551-AXD 10503/1 Uen B (RNC)

[6] Winnow Product Delivery: RNC UP 6.0 R9AS Release 2008-03-31





17 Appendix

UeRc index (Supported RAB Combinations)

0 Idle 1 Stand-alone SRB (13.6/13.6) kbps 2 Conv. CS speech (12.2/12.2 kbps) 3 Conv. CS unkn. (64/64 kbps) 4 Interact. PS (RACH/FACH) 5 Interact. PS (64/64 kbps) 6 Interact. PS (64/128 kbps) 7 Interact. PS (64/384 kbps) 8 Stream. CS unkn. (57.6/57.6 kbps) 9 Conv. CS speech (12.2/12.2 kbps) + Interact. PS (0/0 kbps) 10 Conv. CS speech (12.2/12.2 kbps) + Interact. PS (64/64 kbps) 11 RRC (13.6/13.6) kbps 12 Conv. CS speech (12.2/12.2 kbps) (preconfigured) 13 Stream. PS unkn. (16/64 kbps) + Interact. PS (8/8 kbps) 14 Conv. CS unkn. (64/64 kbps) + Interact. PS (8/8 kbps) 15 Interact. PS (64/HS kbps) 16 Interact. PS (384/HS kbps) 17 Stream. PS unkn. (16/128 kbps) + Interact. PS (8/8 kbps) 18 Interact. PS (128/128 kbps) 19 Conv. CS speech (12.2/12.2 kbps) + Interact. PS (64/HS kbps) 20 Conv. CS speech (12.2/12.2 kbps) + Interact. PS (384/HS kbps) 21 Interact. PS (URA-PCH) 22 Stream. PS unkn. (128/16 kbps) + Interact. PS (8/8 kbps) 23 Conv. CS speech (12.2/12.2 kbps) + Stream. PS unkn. (128/16 kbps) + Interact. PS

(8/8 kbps) 24 Conv. CS speech (12.2/12.2 kbps) + Stream. PS unkn. (16/128 kbps) + Interact. PS

(8/8 kbps) 25 Interact. PS (EUL/HS) 26 Interact. PS (64/64 kbps) + Interact. PS (64/64 kbps) 27 Interact. PS (64/64 kbps) + Interact. PS (64/64 kbps) + Conv. CS speech

(12.2/12.2 kbps) 28 Interact. PS (128/64 kbps) 29 Interact. PS (384/64 kbps) 30 Interact. PS (384/128 kbps) 31 Interact. PS (128/384 kbps) 32 Interact. PS (384/384 kbps) 33 Conv. CS speech AMR (7.95/7.95 kbps) 34 Conv. CS speech AMR (5.9/5.9 kbps) 35 Conv. CS speech AMR (4.75/4.75 kbps) 36 Conv. CS speech (12.2/12.2 kbps) + Interact. PS (64/128 kbps) 37 Conv. CS speech (12.2/12.2 kbps) + Interact. PS (128/64 kbps) 38 Conv. CS speech (12.2/12.2 kbps) + Interact. PS (64/384 kbps) 39 Interact. PS (64/128 kbps) + Interact. PS (64/128 kbps) 40 Conv. CS Speech (12.65 8.85 6.6) + SRB (3.4/3.4) + 0.15 SRB#5 41 Conv. CS S peech (12.65 8.85 6.6) + SRB (3.4/3.4) + 0.15 SRB#5, preconfigured





42 Conv. CS Speech (12.65 8.85 6.6) + Interact. PS (0/0) + SRB (3.4/3.4)+ 0.15 SRB#

43 Conv. CS Speech (12.65 8.85 6.6) + Interact. PS (64/64) + SRB (3.4/3.4) + 0.15 SRB#5



46 Streaming PS 128/HS + Interactive PS 8/HS 47 Conv. CS Speech (12.65 8.85 6.6) + Interact. PS (64/HS) + SRB (3.4/3.4) + 0.15

SRB#5 48 Conv. CS Speech (12.65 8.85 6.6) + Interact. PS (384/HS) + SRB (3.4/3.4) + 0.15

SRB#5 49 Conversational CS Speech 12.2/12.2 + Streaming PS 128/HS + Interactive 8/HS 50 Conv. CS Speech (12.65 8.85 6.6) + Stream. PS (16/128) + Interact. PS (8/8)+

SRB (3.4/3.4)+ 0.15 SRB 51 Conv. CS Speech (12.65 8.85 6.6) + Interact. PS (64/64) + Interact. PS (64/64) +

SRB (3.4/3.4)+ 0.15 SRB 52 Interact. PS (128/HS) 53 PS Interactive 16/HS 54 2* Interact. PS (64/HS) 55 2* Interact. PS (128/HS) 56 2* Interact. PS (384/HS) 57 Conv. CS speech 12.2 + 2* Interact. PS (64/HS) 58 Conv. CS speech 12.2 + 2* Interact. PS (128/HS) 59 Conv. CS speech 12.2 + 2* Interact. PS (384/HS) 60 Conv. CS speech 12.2 + Interact. PS (128/HS) 62 2* Interact. PS (EUL/HS) 66 3* Interact. PS (64/HS) 67 PS Interactive 16/16 68 PS Interactive 16/64 69 PS Interactive 64/16 72 Streaming PS 16/HS + Interactive PS 8/HS 73 Streaming PS 32/HS + Interactive PS 8/HS 74 PS Interactive 64/64 + PS Interactive 64/64 + PS Interactive 64/64 76 Speech 12200 + PS Interactive 128/128 + PS Interactive 128/128 77 Conversational CS Speech 12.2/12.2 + Streaming PS 16/HS + Interactive 8/HS 78 Conversational CS Speech 12.2/12.2 + Streaming PS 32/HS + Interactive 8/HS

Wcdma rnc p6 kpi description

Engineering

Transcript of Wcdma rnc p6 kpi description