BSC6900 UMTS Performance Counter Reference (V900R015C00 - 01) (PDF) - en

BSC6900 UMTS V900R015C00
Performance Counter Reference

Issue Date 01 2013-05-04
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Issue 01 (2013-05-04)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
BSC6900 UMTS Performance Counter Reference
About This Document
About This Document

Purpose
This document describes all the performance counters related to the BSC6900.
Product Version
The following table lists the product versions related to this document. Product Name BSC6900 Product Version V900R015C00
Intended Audience
This document is intended for: l l l l l l Network planners System engineers Field engineers Shift operators Site maintainers Network operators
Change History
For detailed performance counter changes, see the release notes.
Document Structure
Figure 1 shows the document structure.
Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ii
About This Document
Figure 1 Document structure
Table 1 explains the terms shown in Figure 1. Table 1 Terms Term Classification of object type Explanation On the top level, object types are classified into three categories: Radio Network Related Measurement, Transport Network Related Measurement, Hardware Platform Related Measurement. Object types are located at the second level of the document structure. One object type contains one or more function subsets. Function Subset Function Subsets are located at the third level of the document structure. One function subset contains one or more counters but belongs to only one object type. Counter Counters are located at the fourth level of the document structure. Counters are the basic elements of performance measurement. One counter can belong to only one function subset.
Object type
Counter Item Description

Table 2 lists the description of each counter item. Table 2 Description of each counter item Item Obj ect typ e
Issue 01 (2013-05-04)
Description Overvi ew Definition and function of a object type.
iii
About This Document
Item Functio n SubSet s Fun ctio n Set Fun ctio n Sub set Functio nSet Name Overvi ew Counte rs Counte r Relatio nship Co unt er Counte r ID Counte r Name Counte r Descri ption Descri ption Measur ement Point Formul a Unit Related Feature s
Description Function subsets contained in a object type.
Name of the function set. One function set contains one or more function subsets.
Definition of a function subset and the flowchart for measuring related counters. Counters contained in a function subset. A table that lists parent counters and their child counters in a table. Note that the child counters listed in the table cover only typical scenarios. That is, some scenarios are not covered by any counter. Therefore, the value of a parent counter is larger than or equal to the sum of the values of its child counters. Some counters may not be involved in any counter relationship. A string of digits that uniquely identifies a counter. Name of a counter. It is composed of a string of uppercase letters, lowercase letters, and dots. A phrase that provides a simple description about a counter. Related intermediate counters are described in Counter ID, Counter Name and Counter Description. Intermediate counter is invisible on the M2000 GUI. Invisible counters are internal sampling points used for calculating the visible counters inside the M2000.
Detailed description about a counter. Condition for triggering counter measurement.
Relationship among counters. Unit of a counter. Features related to a counter.
Issue 01 (2013-05-04)
iv
Contents
Contents
About This Document.....................................................................................................................ii 1 UMTS Radio Network Related Measurement.........................................................................1
1.1 Measurement of CNOPERATOR Performance(CNOPERATOR)....................................................................2 1.1.1 Measurement of active algorithm per PLMN(ALGO.PLMN.RNC).........................................................2 1.1.1.1 Number of TRBs of HSDPA Service on Which Packet Inspection (PI) Takes Effect for RNC ......................................................................................................................................................................3 1.1.2 Measurement of RAB assignment setup per PLMN(RAB.Estab.PLMN.RNC).......................................3 1.1.2.1 Number of RABs Requested to Establish for each Operator...........................................................4 1.1.2.2 Number of Successfully Established RABs for each Operator........................................................7 1.1.3 Measurement of RAB assignment release per PLMN(RAB.Rel.PLMN.RNC)........................................9 1.1.3.1 Number of Abnormally Released RABs for each Operator.............................................................9 1.1.3.2 Number of Normally Released RABs for each Operator...............................................................14 1.1.4 Traffic Measurement of CN Operator per RNC(TRAFF.LOAD.PLMN.RNC).....................................17 1.1.4.1 Equivalent Erlang of CS Domain of RNC for each Operator........................................................18 1.1.4.2 Maximum Equivalent Erlang of CS Domain of RNC for each Operator.......................................19 1.1.4.3 Uplink Traffic of R99 PS Domain of RNC for each Operator.......................................................20 1.1.4.4 Maximum Uplink Traffic of R99 PS Domain of RNC for each Operator.....................................21 1.1.4.5 Downlink Traffic of R99 PS Domain of RNC for each Operator..................................................22 1.1.4.6 Maximum Downlink Traffic of R99 PS Domain of RNC for each Operator................................23 1.1.4.7 Downlink Traffic of HSDPA PS Domain of RNC for each Operator............................................24 1.1.4.8 Maximum Downlink Traffic of HSDPA PS Domain of RNC for each Operator..........................25 1.1.4.9 Uplink Traffic of HSUPA PS Domain of RNC for each Operator................................................26 1.1.4.10 Maximum Uplink Traffic of HSUPA PS Domain of RNC for each Operator.............................27 1.1.4.11 Downlink Traffic of MBMS or IMB PS Domain of RNC for each Operator..............................28 1.1.4.12 Maximum Downlink Traffic of MBMS or IMB PS Domain of RNC for each Operator............29 1.1.4.13 Equivalent Erlang of CS Domain AMR Service of RNC for each Operator...............................30 1.1.4.14 Equivalent Erlang of CS Domain CS 64kbit/s Conversational Service of RNC for each Operator ....................................................................................................................................................................31 1.1.4.15 The Number of Cell_DCH UEs in PS Domain in RNC...............................................................32 1.1.4.16 Maximum Total Throughout of UL and DL PS Services per Operator for RNC........................33 1.1.4.17 Average Total Throughput of UL and DL PS Services per Operator for RNC...........................34 1.1.4.18 The Number of Cell_FACH UEs in PS Domain in RNC.............................................................35 1.2 Measurement of CPUS Performance(CPUS)...................................................................................................36 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
Contents
1.2.1 Measurement related to CPUS(CPUS)....................................................................................................36 1.2.1.1 Measurement of CS-Domain Equivalent Erlang of Each Subsystem in the RNC.........................45 1.2.1.2 Number of RRC Connection Requests in the CPUS subsystem....................................................46 1.2.1.3 Number of Successful RRC Connection Setups in the CPUS subsystem......................................47 1.2.1.4 Number of CS RAB Requests in the CPUS subsystem..................................................................49 1.2.1.5 Number of CS RABs successfully established in the CPUS subsystem........................................51 1.2.1.6 Number of RABs Abnormally Released in the CPUS subsystem..................................................53 1.2.1.7 Number of RABs Normally Released in the CPUS subsystem......................................................56 1.2.1.8 Number of CBS Requests Discarded Due to Flow Control for CPUS Subsystem........................59 1.2.1.9 Duration of CBS Flow Control for CPUS Subsystem....................................................................60 1.2.1.10 Number of Paging Messages Discarded Due to Flow Control for CPUS Subsystem..................60 1.2.1.11 Duration of Paging Message Flow Control for CPUS Subsystem...............................................61 1.2.1.12 Number of Cell Update Requests Discarded Due to Flow Control for CPUS Subsystem...........62 1.2.1.13 Duration of Cell Update Flow Control for CPUS Subsystem......................................................63 1.2.1.14 Number of Discarded RRC Connection Requests Due to Various Flow Control Functions.......64 1.2.1.15 Number of Various Priority RRC Requests Discarded Due to Flow Control for CPUS Subsystem ....................................................................................................................................................................65 1.2.1.16 Duration of Rejection of Various Priority RRC Requests Due to Flow Control for CPUS Subsystem ....................................................................................................................................................................66 1.2.1.17 Number of Various Priority CELL_UPDATE Messages Discarded Because CPU Usage Exceeds the Threshold in a CPUS............................................................................................................................67 1.2.1.18 Number of Various Priority CELL_UPDATE Messages Discarded Due to Queue-based Shaping in a CPUS...................................................................................................................................................69 1.2.1.19 Number of Discarded Event 4A Measurement Reports on PS BE Traffic in the CELL_DCH State ....................................................................................................................................................................71 1.2.1.20 Number of Discarded UL Event 4A Measurement Reports on Throughput for UEs in the CELL_DCH State.......................................................................................................................................72 1.2.1.21 Number of Discarded Event 4A Measurement Reports on PS BE Traffic in the CELL_FACH State ....................................................................................................................................................................73 1.2.1.22 Number of FlowControl RRC Connection Requests Due to FlowControl for CPUS Subsystem ....................................................................................................................................................................75 1.2.1.23 Number of FlowControl RT RRC Connection Requests Due to FlowControl for CPUS Subsystem ....................................................................................................................................................................76 1.2.1.24 Number of RRC CONNECTION REQUESTS for CS Services in a CPUS Subsystem Under Flow Control Triggered by Interface-Board CPU Overload...............................................................................78 1.2.1.25 Number of RRC CONNECTION REQUESTS in a CPUS Subsystem Under Flow Control Triggered by Interface-Board CPU Overload.............................................................................................79 1.2.1.26 Number of Discarded Iur-Interface Uplink Signalling Messages in a CPUS Subsystem Under Flow Control Triggered by CPU Overload..........................................................................................................79 1.2.1.27 Number of Discarded Iur-Interface Downlink Signalling Messages in a CPUS Subsystem Under Flow Control Triggered by CPU Overload................................................................................................80 1.3 Measurement of GTPU Performance(GTPU)..................................................................................................81 1.3.1 Measurement related to GTPU(GTPU)...................................................................................................82 1.3.1.1 Number of UL Packets Sent by GTP-U.........................................................................................84 1.3.1.2 Number of DL Packets Received by GTP-U..................................................................................85 1.3.1.3 Number of UL Bytes Sent by GTP-U............................................................................................86 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vi
Contents
1.3.1.4 Number of DL Bytes Received by GTP-U.....................................................................................86 1.3.1.5 Counters Related to the Number of Service PDUs Sent by GTP-U...............................................87 1.3.1.6 Counters Related to the Number of Service PDUs Received by GTP-U.......................................88 1.3.1.7 Number of MBMS or IMB Service Bytes Received by GTP-U....................................................89 1.3.1.8 Number of Echo Response Packets Sent by the GTP-U................................................................90 1.3.1.9 Number of Echo Response Packets Received by the GTP-U.........................................................90 1.3.1.10 Number of Echo Request Packets Sent by the GTP-U.................................................................91 1.3.1.11 Number of Echo Request Packets Received by the GTP-U.........................................................92 1.3.1.12 Number of Error Indication Packets Sent by the GTP-U.............................................................92 1.3.1.13 Number of Error Indication Packets Received by the GTP-U.....................................................93 1.4 Measurement of IU Interface Performance(IU)...............................................................................................94 1.4.1 Measurement related to CS Iu interface signalling(CS.SIG.IU).............................................................94 1.4.1.1 Number of RESET Messages Initiated by RNC to CS Domain.....................................................98 1.4.1.2 Number of RESET Messages Received by RNC from CS Domain..............................................99 1.4.1.3 Number of INITIAL UE MESSAGE Messages from RNC to CS Domain.................................101 1.4.1.4 Number of IU RELEASE REQUEST Messages from RNC to CS Domain................................102 1.4.1.5 Number of IU RELEASE COMMAND Messages from CS Domain to RNC............................103 1.4.1.6 Number of ERROR INDICATION Messages from RNC to CS Domain...................................105 1.4.1.7 Number of ERROR INDICATION Messages from CS Domain to RNC...................................107 1.4.1.8 Number of IU RELEASE REQUEST Messages from RNC to CS Domain for Different Causes ..................................................................................................................................................................108 1.4.1.9 Number of IU RELEASE COMMAND Messages from CS Domain to RNC for Different Causes ..................................................................................................................................................................111 1.4.1.10 Load Balancing of the MSC Pool on the CS Domain................................................................114 1.4.1.11 Number of Discarded Initial UE messages Under Iu Signaling Flow Control (CS Domain) ..................................................................................................................................................................116 1.4.1.12 Number of Paging Messages Received by RNC from CN in CS Domain.................................117 1.4.1.13 Number of RAN INFORMATION REQUEST Messages Received by RNC from CN...........119 1.4.1.14 Number of RAN INFORMATION Messages Sent by RNC to CN...........................................120 1.4.2 Measurement related to CS traffic(CS.TRF.IU)....................................................................................121 1.4.2.1 Number of DL Bytes of CS Conversational Service on Iu Interface...........................................122 1.4.2.2 Number of DL Bytes of CS Streaming Service on Iu Interface...................................................122 1.4.2.3 Number of UL Bytes of CS Conversational Service on Iu Interface...........................................123 1.4.2.4 Number of UL Bytes of CS Streaming Service on Iu Interface...................................................124 1.4.3 Measurement related to Iu interface(MBMS)(MBMS.IU)....................................................................125 1.4.3.1 Total Number of MBMS or IMB Service....................................................................................126 1.4.3.2 Number of Successful MBMS or IMB Service............................................................................127 1.4.3.3 Number of MBMS or IMB Service Setup Failures on the Iu Interface Due to Different Causes ..................................................................................................................................................................128 1.4.4 Measurement related to Iu interface(MOCN)(MOCN.IU)....................................................................130 1.4.4.1 Number of Redirect for Different Causes.....................................................................................131 1.4.5 Measurement related to NAS signaling(NAS.IU).................................................................................133 1.4.5.1 Number of Messages Forwarded by the RNC to the CN.............................................................135 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
1.4.5.2 Number of Messages Forwarded by the RNC from the CN.........................................................137 1.4.5.3 Number of Authentication Requests Received by the RNC from the CN...................................139 1.4.5.4 Number of Authentication Responses Forwarded by the RNC to the CN...................................140 1.4.5.5 Number of SECURITY MODE COMMAND Messages Received by the RNC from the CN ..................................................................................................................................................................142 1.4.5.6 Number of SECURITY MODE COMPLETE Messages Forwarded by the RNC to the CN ..................................................................................................................................................................143 1.4.6 Measurement related to PS Iu interface signalling(PS.SIG.IU)............................................................145 1.4.6.1 Number of RESET Messages Initiated by RNC to PS Domain...................................................149 1.4.6.2 Number of RESET Messages Received by RNC from PS Domain.............................................151 1.4.6.3 Number of INITIAL UE MESSAGE Messages from RNC to PS Domain.................................152 1.4.6.4 Number of IU RELEASE REQUEST Messages from RNC to PS Domain................................154 1.4.6.5 Number of IU RELEASE COMMAND Messages from PS Domain to RNC.............................155 1.4.6.6 Number of ERROR INDICATION Messages from RNC to PS Domain....................................157 1.4.6.7 Number of ERROR INDICATION Messages from PS Domain to RNC....................................158 1.4.6.8 Number of IU RELEASE REQUEST Messages from RNC to PS Domain for Different Causes ..................................................................................................................................................................160 1.4.6.9 Number of IU RELEASE COMMAND Messages from PS Domain to RNC for Different Causes ..................................................................................................................................................................162 1.4.6.10 Load Balancing of the MSC Pool on the PS Domain.................................................................165 1.4.6.11 Number of Discarded Initial UE messages Under Iu Signaling Flow Control (PS Domain) ..................................................................................................................................................................167 1.4.6.12 Number of Paging Messages Received by RNC from CN in PS Domain.................................169 1.4.6.13 Number of RIM Requests from the eNodeB to the RNC (System Information).......................170 1.4.6.14 Number of RIM Response Messages from the RNC to the eNodeB (System Information) ..................................................................................................................................................................172 1.4.6.15 Number of RIM Update Messages from the RNC to the eNodeB (System Information)..........174 1.4.6.16 Number of RIM acknowledgement messages from the eNodeB to the RNC (System Information) ..................................................................................................................................................................175 1.4.6.17 Number of RIM Requests from the eNodeB to the RNC (Load Information)...........................177 1.4.6.18 Number of RIM Response Messages from the RNC to the eNodeB (Load Information).........179 1.4.6.19 Number of RIM Update Messages from the RNC to the eNodeB (Load Information).............180 1.4.6.20 Number of RIM Acknowledgement Messages from the eNodeB to the RNC (Load Information) ..................................................................................................................................................................182 1.4.7 Measurement related to PS traffic(PS.TRF.IU).....................................................................................183 1.4.7.1 Number of UL Bytes of PS Conversational Service on Iu Interface............................................185 1.4.7.2 Number of UL Bytes of PS Streaming Service on Iu Interface....................................................186 1.4.7.3 Number of UL Bytes of PS Interactive Service on Iu Interface...................................................187 1.4.7.4 Number of UL Bytes of PS Background Service on Iu Interface.................................................188 1.4.7.5 Number of DL Bytes of PS Conversational Service on Iu Interface............................................189 1.4.7.6 Number of DL Bytes of PS Streaming Service on Iu Interface....................................................189 1.4.7.7 Number of DL Bytes of PS Interactive Service on Iu Interface...................................................190 1.4.7.8 Number of DL Bytes of PS Background Service on Iu Interface.................................................191 1.4.7.9 Number of UL Bytes of PS BE Service for Golden Subscriber on Iu Interface..........................192 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. viii
Contents
1.4.7.10 Number of UL Bytes of PS BE Service for Silver Subscriber on Iu Interface...........................192 1.4.7.11 Number of UL Bytes of PS BE Service for Copper Subscriber on Iu Interface........................193 1.4.7.12 Number of DL Bytes of PS BE Service for Golden Subscriber on Iu Interface........................194 1.4.7.13 Number of DL Bytes of PS BE Service for Silver Subscriber on Iu Interface...........................195 1.4.7.14 Number of DL Bytes of PS BE Service for Copper Subscriber on Iu Interface........................195 1.4.7.15 Total HTTP Traffic Volume on the RNC...................................................................................196 1.4.7.16 Total P2P Traffic Volume on the RNC......................................................................................197 1.4.7.17 Total Traffic Volume of all Subscribed Services on the RNC...................................................198 1.4.7.18 Total Traffic Volume of Undefined Services on the RNC.........................................................199 1.4.7.19 Traffic Volume of Services Cannot Be Identified by the RNC on Downlink............................199 1.4.8 Measurement Related to SCCP for Iu Interface(SIG.SCCP.IU)...........................................................200 1.4.8.1 Number of SCCP Connection Requests Sent by the RNC to the CN Through the Iu Interface ..................................................................................................................................................................201 1.4.8.2 Number of Successful SCCP Connection Requests Sent by the RNC to the CN Through the Iu Interface....................................................................................................................................................203 1.4.8.3 Number of SCCP Connection Requests Received by the RNC from the CN Through the Iu Interface ..................................................................................................................................................................204 1.4.8.4 Number of Successful SCCP Connection Requests Received by the RNC from the CN Through the Iu Interface................................................................................................................................................205 1.5 Measurement of IUR Interface Performance(IUR)........................................................................................207 1.5.1 Measurement related to DRNC in Iur interface(DRNC.IUR)...............................................................207 1.5.1.1 Number of ERROR INDICATION Messages Received by the RNC on Iur Interface................213 1.5.1.2 Number of ERROR INDICATION Messages Sent by the RNC on Iur Interface.......................214 1.5.1.3 Number of Requests to Establish a Radio Link Received by DRNC on Iur Interface.................215 1.5.1.4 Number of Successful Radio Link Establishments by DRNC on Iur Interface...........................216 1.5.1.5 Number of Radio Links Unsuccessfully Established by DRNC on Iur Interface for Different Causes ..................................................................................................................................................................218 1.5.1.6 Number of Radio Links to Be Deleted by DRNC on Iur Interface..............................................221 1.5.1.7 Number of Successful Radio Link Deletions by DRNC on Iur Interface....................................222 1.5.1.8 Number of Radio Link Addition Requests by DRNC on Iur Interface........................................224 1.5.1.9 Number of Successful Radio Link Additions on DRNC Iur Interface.........................................225 1.5.1.10 Number of Failed Radio Links Additions by DRNC on Iur Interface for Different Causes......226 1.5.1.11 Number of Radio Links to Be Reconfigured by DRNC.............................................................230 1.5.1.12 Number of Radio Links Successfully Reconfigured by DRNC on Iur Interface.......................231 1.5.1.13 Number of Failed Radio Link Synchronous Reconfigurations by DRNC on Iur Interface for Different Causes.......................................................................................................................................232 1.5.1.14 Number of Radio Links with Reconfiguration Canceled by the DRNC over Iur......................236 1.5.1.15 Number of Radio Link Failures on Iur Interface........................................................................237 1.5.1.16 Number of Failed Radio Links on Iur Interface for Different Causes........................................238 1.5.1.17 Number of RADIO LINK RESTORE INDICATION Messages sent by DRNC on Iur Interface ..................................................................................................................................................................241 1.5.1.18 Number of COMMON TRANSPORT CHANNEL RESOURCES REQUEST Messages Received by DRNC on Iur Interface........................................................................................................................242 1.5.1.19 Number of COMMON TRANSPORT CHANNEL RESOURCES RESPONSE Messages Sent by DRNC on Iur Interface.............................................................................................................................244 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
1.5.1.20 Number of COMMON TRANSPORT CHANNEL RESOURCES FAILURE Messages sent by DRNC on the Iur Interface due to Transport Resource Unavailable........................................................245 1.5.1.21 Number of COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST Messages Received by DRNC on Iur Interface........................................................................................247 1.5.2 Reserved counter for Iur interface(RESERVE.IUR).............................................................................248 1.5.2.1 Reserved counters for Iur interface...............................................................................................249 1.5.3 Measurement Related to SCCP for Iur Interface(SIG.SCCP.IUR).......................................................250 1.5.3.1 Number of SCCP Connection Requests Sent by the Local RNC to the Peer RNC Through the Iur Interface....................................................................................................................................................251 1.5.3.2 Number of Successful SCCP Connection Requests Sent by the Local RNC to the Peer RNC Through the Iur Interface........................................................................................................................................253 1.5.3.3 Number of SCCP Connection Requests Received by the Local RNC from the Peer RNC Through the Iur Interface........................................................................................................................................254 1.5.3.4 Number of Successful SCCP Connection Requests Received by the Local RNC from the Peer RNC Through the Iur Interface..........................................................................................................................255 1.5.4 Measurement related to SRNC in Iur interface(SRNC.IUR)................................................................257 1.5.4.1 Number of Radio Links Requested to Establish by SRNC on Iur Interface................................265 1.5.4.2 Number of Radio Links Successfully Established by SRNC on Iur Interface.............................266 1.5.4.3 Number of Failed Radio Link Establishments by SRNC on Iur Interface for Different Causes ..................................................................................................................................................................268 1.5.4.4 Number of Radio Links Deleted on Iur Interface for SRNC........................................................271 1.5.4.5 Number of Successful deleted Radio Links on Iur Interface for SRNC.......................................272 1.5.4.6 Number of Radio Links Requested to Add by SRNC on Iur Interface........................................274 1.5.4.7 Number of Radio Links Successfully Added by SRNC on Iur Interface.....................................275 1.5.4.8 Number of Failed Radio Link Additions for Different Causes on Iur Interface for SRNC.........276 1.5.4.9 Number of Radio Links Requested to Reconfigure by SRNC on Iur Interface...........................280 1.5.4.10 Number of Radio Links Successfully Reconfigured by SRNC on Iur Interface........................281 1.5.4.11 Number of Radio Links Unsuccessfully Reconfigured by SRNC on Iur Interface for Different Causes.......................................................................................................................................................282 1.5.4.12 Number of Radio Links Unsuccessfully Reconfigured by SRNC on Iur Interface for No Response ..................................................................................................................................................................285 1.5.4.13 Number of Failed Radio Links of SRNC on Iur Interface.........................................................286 1.5.4.14 Number of Failed Radio Links of SRNC on Iur Interface for Different Causes........................288 1.5.4.15 Number of Radio Links Restored by SRNC on Iur Interface.....................................................290 1.5.4.16 Number of Soft Handovers Initiated by SRNC on Iur Interface................................................291 1.5.4.17 Number of Successful Soft Handovers Initiated by SRNC on Iur Interface..............................292 1.5.4.18 Number of COMMON TRANSPORT CHANNEL RESOURCES REQUEST Messages Sent by SRNC on Iur Interface..............................................................................................................................293 1.5.4.19 Number of COMMON TRANSPORT CHANNEL RESOURCES RESPONSE Messages Received by SRNC on Iur Interface.........................................................................................................295 1.5.4.20 Number of COMMON TRANSPORT CHANNEL RESOURCES FAILURE Messages Received by SRNC on Iur Interface Due to Transport Resource Unavailable........................................................296 1.5.4.21 Number of COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST Messages of SRNC on Iur Interface.........................................................................................................298 1.5.4.22 Number of PS RABs Normally Released on CCH (FACH or PCH) for SRNC (Iur Interface) ..................................................................................................................................................................299 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. x
Contents
1.5.4.23 Number of Normally Released CS RABs According to Different Service on the IUR interface ..................................................................................................................................................................302 1.5.4.24 Number of Abnormally Released CS RABs According to Different Service on SRNC Iur Interface ..................................................................................................................................................................305 1.5.4.25 Number of PS RABs Abnormally Released on CCH (FACH or PCH) for SRNC (Iur Interface) ..................................................................................................................................................................309 1.5.4.26 Number of Normally Released PS RABs According to Different Service on the IUR interface ..................................................................................................................................................................311 1.5.4.27 Number of Normally Released HSPA RABs on Iur Interface for SRNC..................................315 1.5.4.28 Number of Abnormally Released PS RABs According to Different Service Type on SRNC Iur Interface....................................................................................................................................................317 1.5.4.29 Number of Abnormally Released HSPA-Carried RABs on SRNC Iur Interface......................321 1.5.4.30 Number of RLs with Reconfiguration Canceled by the SRNC over Iur....................................323 1.5.4.31 Number of CS Conversational RABs carried on HSPA Normally Released on Iur Interface for SRNC........................................................................................................................................................325 1.5.4.32 Number of CS Conversational RABs carried on HSPA Abnormally Released on Iur Interface for SRNC........................................................................................................................................................327 1.5.4.33 Number of Normally Released PS RABs that Are in CELL_PCH or URA_PCH State on Iur Interface for SRNC...................................................................................................................................330 1.5.4.34 Number of Abnormally Released PS RABs that Are in CELL_PCH or URA_PCH State on Iur Interface for SRNC...................................................................................................................................332 1.5.4.35 Number of RRC Connection Releases (CCCH) Sent by the SRNC over the Iur Interface due to DSCR........................................................................................................................................................335 1.5.4.36 Number of RRC Connection Releases (DCCH) Sent by the SRNC over the Iur Interface due to DSCR........................................................................................................................................................337 1.5.5 Measurement related to traffic for Iur Interface(TRFFIC.IUR)............................................................338 1.5.5.1 Number of UL Bytes of Signaling Data Received by SRNC on DCH of Iur Interface...............342 1.5.5.2 Number of DL Bytes of Signaling Data Sent by SRNC on DCH of Iur Interface.......................342 1.5.5.3 Number of Bytes of UL PS R99 Services Received by SRNC on Iur Interface..........................343 1.5.5.4 Number of Bytes of DL PS R99 Services Sent by SRNC on Iur Interface..................................345 1.5.5.5 Number of Bytes of UL CS Services Received by SRNC over DCH on Iur Interface................346 1.5.5.6 Number of Bytes of DL CS Services Sent by SRNC over DCH on Iur Interface........................347 1.5.5.7 Number of UL Bytes Sent by DRNC on DCH of Iur Interface...................................................348 1.5.5.8 Number of DL Bytes Received by DRNC on DCH of Iur Interface............................................348 1.5.5.9 Number of Bytes of PS HSUPA Services Received by SRNC on Iur Interface..........................349 1.5.5.10 Number of Bytes of PS HSDPA Services Received by SRNC on Iur Interface........................350 1.5.5.11 Number of bytes of CS HSDPA conversational service in SRNC for IUR...............................352 1.5.5.12 Number of bytes of HSDPA services in DRNC for IUR...........................................................352 1.5.5.13 Number of HSDPA Signaling Bytes on Iur Interface in SRNC.................................................353 1.5.5.14 Number of HSUPA Signaling Bytes on Iur Interface in SRNC.................................................354 1.5.5.15 Number of bytes of CS HSUPA conversational service in SRNC for IUR...............................355 1.6 Measurement of MPU Performance(MPU)....................................................................................................356 1.6.1 Measurement related to MPU(MPU)....................................................................................................356 1.6.1.1 Throughput of PS Uplink Data for MPU......................................................................................357 1.6.1.2 Throughput of PS Downlink Data for MPU.................................................................................357 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
1.7 Measurement of NODEB Performance(NODEB)..........................................................................................358 1.7.1 Measurement related to Algorithm per NodeB(ALGO.NODEB).........................................................359 1.7.1.1 Number of UL or DL Congestions on Iub Interface.....................................................................360 1.7.1.2 Time of UL or DL Congestions on Iub Interface.........................................................................361 1.7.1.3 NodeB Unavailability Time..........................................................................................................362 1.7.1.4 Total Dynamic Spectrum Sharing (DSS) Activation Duration....................................................363 1.7.1.5 Number of Received Dynamic Spectrum Sharing (DSS)............................................................364 1.7.1.6 Number of Normal Spectrum Withdrawals..................................................................................364 1.7.1.7 Number of Urgent Spectrum Withdrawals...................................................................................365 1.7.1.8 Number of Abnormal Spectrum Withdrawals..............................................................................366 1.7.1.9 NodeB Credit Usage When CE Overbooking Is Enabled............................................................367 1.8 Measurement of Physical RNC Node(NODESHARE)..................................................................................368 1.8.1 Radio Access Bearer (RAB) Measurement for Physical RNC Nodes(RAB.NODESHARE)..............368 1.8.1.1 Number of CS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Conversational Service)...............................................................................................................371 1.8.1.2 Number of Successful CS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Conversational Service).......................................................................................372 1.8.1.3 Number of PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes........................................................................................................................................................373 1.8.1.4 Number of Successful PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes................................................................................................................................375 1.8.1.5 Number of RABs Released Abnormally due to Radio Link Failure for UEs Whose Load Is Shared Between Physical RNC Nodes.................................................................................................................376 1.8.1.6 Number of RABs Released Abnormally for UEs Whose Load Is Shared Between Physical RNC Nodes........................................................................................................................................................380 1.8.1.7 Number of RABs Released Normally for UEs Whose Load Is Shared Between Physical RNC Nodes ..................................................................................................................................................................383 1.8.2 Radio Resource Control (RRC) Measurement for Physical RNC Nodes(RRC.NODESHARE)..........386 1.8.2.1 Number of RRC Connection Requests Sent by UEs Whose Load Is Shared Between Physical RNC Nodes........................................................................................................................................................387 1.8.2.2 Number of Successful RRC Connection Requests Sent by UEs Whose Load Is Shared Between Physical RNC Nodes................................................................................................................................388 1.8.2.3 Delay in Setting Up RRC Connection for UEs in CELL_DCH State Whose Load Is Shared Between Physical RNC Nodes................................................................................................................................390 1.8.2.4 Delay in Setting Up RRC Connection for UEs in CELL_FACH State Whose Load Is Shared Between Physical RNC Nodes................................................................................................................................392 1.8.2.5 Number of UEs Whose Load Is Shared Between Physical RNC Nodes......................................394 1.9 Measurement of Operator Performance at the NodeB Level(PLMN_NodeB)..............................................395 1.9.1 Measurement Related to Operators at the NodeB Level(PLMN.NodeB).............................................395 1.9.1.1 Number of UEs With Decreased BE Service Rate in the Case of UL Credit Resource Congestion for Operator..............................................................................................................................................396 1.9.1.2 Average NodeB Credit Consumption of an Operator in the Uplink............................................397 1.9.1.3 Maximum NodeB Credit Consumption of an Operator in the Uplink.........................................398 1.9.1.4 Average NodeB Credit Consumption of an Operator in the Downlink........................................398 1.9.1.5 Maximum NodeB Credit Consumption of an Operator in the Downlinke1.................................399 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xii
Contents
1.10 Measurement of RNC Performance(RNC)...................................................................................................400 1.10.1 Measurement related to AMR service(AMR.RNC)............................................................................401 1.10.1.1 The Average Number of AMR Users with Different UL and DL Rates....................................403 1.10.1.2 Number of Times That Silence Is Detected in Downlink for AMR Calls per RNC..................406 1.10.1.3 Number of Times That Silence Is Detected in Uplink for AMR Calls per RNC.......................407 1.10.2 Measurement related to CBS per RNC(CBS.RNC)............................................................................408 1.10.2.1 Number of ETWS-related WRITE-REPLACE Messages Received by the RNC.....................408 1.10.2.2 Number of ETWS-related WRITE-REPLACE FAILURE Messages Sent by the RNC...........410 1.10.3 Hard Handover Measurement per RNC(HHO.RNC)..........................................................................411 1.10.3.1 Number of Intra-Frequency Hard Handover Requests...............................................................413 1.10.3.2 Number of Inter-Frequency Hard Handover Requests...............................................................414 1.10.3.3 Number of Successful Inter-Frequency Hard Handovers...........................................................415 1.10.3.4 Number of Successful Intra-Frequency Hard Handovers...........................................................417 1.10.4 Measurement related to CS Inter-RAT handover per RNC(IRATHO.Cs.RNC)................................418 1.10.4.1 Number of CS Incoming Inter-RAT Handover Attempts..........................................................423 1.10.4.2 Number of CS Outgoing Inter-RAT Handover Attempts..........................................................424 1.10.4.3 Number of CS Outgoing Inter-RAT Handover Preparation Attempts.......................................426 1.10.4.4 Number of CS Incoming Inter-RAT Handover Preparation Attempts.......................................427 1.10.4.5 Number of Successful Preparations for CS Incoming Inter-RAT Handover.............................429 1.10.4.6 Number of Successful CS Outgoing Inter-RAT Handovers......................................................430 1.10.4.7 Number of Successful Preparations for CS Outgoing Inter-RAT Handover.............................432 1.10.4.8 Number of Successful CS Incoming Inter-RAT Handovers......................................................433 1.10.5 Measurement related to PS Inter-RAT handover per RNC(IRATHO.PS.RNC).................................435 1.10.5.1 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC..............................436 1.10.5.2 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by RNC..........................438 1.10.5.3 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by UE.................................439 1.10.5.4 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE.............................441 1.10.5.5 Number of LTE-to-UMTS PS Handover Attempts Caused by the CSFB of an LTE Emergency Call for RNC.............................................................................................................................................442 1.10.5.6 Number of Successful LTE-to-UMTS PS Handovers Caused by the CSFB of an LTE Emergency Call for RNC.............................................................................................................................................444 1.10.5.7 Number of Successful LTE-to-UMTS PS Handover Preparations Caused by the CSFB of LTE Emergency Calls for RNC........................................................................................................................445 1.10.6 Measurement related to LCS service(LCS.RNC)................................................................................447 1.10.6.1 Number of Successful Provisions of GPS Assistance Data.......................................................450 1.10.6.2 Number of Positioning Reports Meeting Accuracy Requirement..............................................451 1.10.6.3 Number of Positioning Requests with Different Event Types...................................................453 1.10.6.4 Number of Successful Positioning Reports with Different Event Types...................................454 1.10.6.5 Number of the positioning attempt of the different location method for RNC..........................456 1.10.6.6 Number of the successful positioning of the different location method for RNC......................458 1.10.6.7 Number of the times that the location in SAS centric mode is used in the RNC.......................460 1.10.6.8 Number of U-TDOA Positioning Attempts................................................................................461 1.10.6.9 Number of Successful U-TDOA Positionings............................................................................463 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
1.10.7 Measurement related to Paging per RNC(PAGE.RNC)......................................................................464 1.10.7.1 Number of Paging Messages to UE............................................................................................465 1.10.7.2 Number of Successful Paging Messages to UE..........................................................................467 1.10.7.3 Number of RNC-Originated PAGING TYPE 1 Messages........................................................468 1.10.7.4 Number of PAGING TYPE 2 Messages....................................................................................469 1.10.7.5 Number of Successful Responses to PAGING TYPE 1 Messages............................................471 1.10.7.6 Number of CS-Oriented PAGING Messages from the CN........................................................472 1.10.7.7 Number of PS-Oriented PAGING Messages from the CN........................................................474 1.10.7.8 Number of Failures to Respond to CS-Oriented PAGING Messages from the CN...................475 1.10.7.9 Number of Failures to Respond to PS-Oriented PAGING Messages from the CN...................476 1.10.7.10 Number of CELL UPDATE Messages from PTT UEs as Paging Response Received by RNC ..................................................................................................................................................................478 1.10.7.11 Number of RNC-Originated PAGING TYPE 1 Messages to PTT UEs in CELL_PCH or URA_PCH state........................................................................................................................................479 1.10.8 Measurement related to PDCP(PDCPGTPU.RNC)............................................................................481 1.10.8.1 Compression Ratio of DL Packet Headers Under ROHC..........................................................481 1.10.8.2 Compression Ratio of DL Packets Under ROHC......................................................................482 1.10.8.3 Ratio of UL ROHC Decompression Failures to Total UL ROHC Decompression Operations ..................................................................................................................................................................483 1.10.9 Measurement of CS RAB assignment setup per RNC(RAB.EstabCS.RNC).....................................484 1.10.9.1 Number of CS RABs Requested to Establish.............................................................................486 1.10.9.2 Mean Number of CS RABs........................................................................................................487 1.10.9.3 Number of CS VP RABs requested to establish in cell where VP is forbidden.........................488 1.10.9.4 Number of Successful RAB Establishments for CS Services....................................................489 1.10.10 Measurement of PS RAB assignment setup per RNC(RAB.EstabPS.RNC)....................................491 1.10.10.1 Counters Related to the Number of PS RAB Setup Requests for Different Services..............499 1.10.10.2 Signaling Delay of PS RAB Setup...........................................................................................501 1.10.10.3 Counters Related to the Number of PS RAB Setup Requests for Different Maximum Downlink Bit rates.....................................................................................................................................................503 1.10.10.4 Counters Related to the Number of Successful PS RAB Setups for Different Maximum Downlink Bit Rates...................................................................................................................................................507 1.10.10.5 Mean Number of PS RABs......................................................................................................511 1.10.10.6 Times of PS RAB established successfully with 0kbps for RNC............................................512 1.10.10.7 Number of Successful RAB Establishments for PS Services...................................................515 1.10.11 Measurement of CS RAB assignment modification per RNC(RAB.ModCs.RNC).........................518 1.10.11.1 Number of CS RAB Modification Requests............................................................................519 1.10.11.2 Number of VP Services Fallen Back to AMR Services...........................................................520 1.10.11.3 Number of Successful CS RAB Modifications........................................................................521 1.10.12 Measurement of PS RAB assignment modification per RNC(RAB.ModPs.RNC)..........................523 1.10.12.1 Number of PS RAB Modification Requests.............................................................................524 1.10.12.2 Number of Successful PS RAB Modifications.........................................................................526 1.10.13 Measurement of multi-RAB service per RNC(RAB.MultiRab.RNC)..............................................529 1.10.13.1 Mean Number of UEs with Multi-RABs in RNC....................................................................529 1.10.14 Measurement of RAB release per RNC(RAB.RelAbnormal.RNC)..................................................531 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiv
Contents
1.10.14.1 Number of Released RABs due to RF cause............................................................................535 1.10.14.2 Number of RABs Abnormally Released for RNC...................................................................538 1.10.14.3 Number of Normally Released RABs......................................................................................541 1.10.14.4 Number of Released RABs Triggered by RNC Due to UE Signaling Connection Release ..................................................................................................................................................................545 1.10.14.5 Number of Abnormally Released CS RABs............................................................................546 1.10.14.6 Times of PS RAB of 0kbps released for failing to rate up before timer expiry.......................549 1.10.15 Measurement of CS RAB release per RNC(RAB.RelCs.RNC)........................................................551 1.10.15.1 Number of CS RABs Requested to Release.............................................................................551 1.10.15.2 Number of Successful CS RAB Releases.................................................................................553 1.10.16 Measurement of PS RAB release per RNC(RAB.RelPs.RNC).........................................................554 1.10.16.1 Number of Successful PS RAB Releases.................................................................................555 1.10.16.2 Number of PS RABs Requested to Release.............................................................................556 1.10.17 Measurement of RB Procedure per RNC(RB.RNC).........................................................................558 1.10.17.1 Counters Related to the Average Number of RBs for PS R99 Conversational Services.........567 1.10.17.2 Counters Related to the Average Number of PS R99 Interactive Service RBs........................570 1.10.17.3 Counters Related to the Average Number of PS R99 Backgroud Service RBs.......................573 1.10.17.4 Counters Related to the Average Number of CS Streaming Service RBs...............................576 1.10.17.5 Counters Related to the Average Number of CS Conversational Service RBs........................577 1.10.17.6 Number of DCH-to-HSDPA Directed Retry Attempts............................................................578 1.10.17.7 Number of Successful DCH-to-HSDPA Directed Retry..........................................................580 1.10.17.8 Counters Related to the Average Number of PS R99 Streaming Service RBs........................582 1.10.18 Measurement of relocation per DRNC(Relocation.Drnc.RNC)........................................................585 1.10.18.1 Counters Related to the Number of Failed Relocation Executions for Different Causes for TRNC ..................................................................................................................................................................590 1.10.18.2 Number of Failed Relocation Resource Allocations Due to Reception of IU Release Command for TRNC..................................................................................................................................................591 1.10.18.3 Number of Failed Relocation Resource Allocations for TRNC...............................................592 1.10.18.4 Number of Reconfiguration Completions During Relocation for TRNC (UE Involved)........595 1.10.18.5 Number of Relocation Execution Attempts for TRNC (UE Not Involved).............................597 1.10.18.6 Number of Successful Relocation Executions for TRNC (UE Not Involved).........................598 1.10.18.7 Number of Successful Relocation Executions for TRNC (UE Involved)................................599 1.10.18.8 Number of Relocation Resource Allocation Attempts for TRNC............................................601 1.10.18.9 Number of Successful Relocation Resource Allocations for TRNC........................................602 1.10.18.10 Number of Successful TRNC Relocations in the CS Domain and PS Domain (UE Involved) ..................................................................................................................................................................604 1.10.18.11 Number of Successful TRNC Relocations in the CS Domain and PS Domain (UE Not Involved) ..................................................................................................................................................................606 1.10.19 Measurement of relocation per SRNC(Relocation.Srnc.RNC).........................................................607 1.10.19.1 Number of Relocation Preparation Attempts Due to Different Causes for SRNC...................619 1.10.19.2 Number of Relocation Preparation Attempts for SRNC..........................................................622 1.10.19.3 Number of Successful Relocation Preparations Due to Different Causes for SRNC...............623 1.10.19.4 Number of Successful Relocation Preparations for SRNC......................................................626 1.10.19.5 Number of Failed Relocation Preparations Due to Different Causes for SRNC......................627 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Contents
1.10.19.6 Counters Related to the Number of Failed Relocation Executions During Reconfiguration for Different Causes for SRNC......................................................................................................................633 1.10.19.7 Counters Related to the Number of Failed SRNC Relocation Executions Due to Timer Expiry for IU Release Command for SRNC........................................................................................................635 1.10.19.8 Counters Related to the Number of Relocation Execution Attempts for SRNC (UE Not Involved) ..................................................................................................................................................................637 1.10.19.9 Number of Failed Relocation Executions Due to Reception of IU Release Command for SRNC ..................................................................................................................................................................639 1.10.19.10 Counters Related to the Number of Reconfiguration Attempts During Relocation Execution for SRNC ( UE Involved)...............................................................................................................................640 1.10.19.11 Number of Successful Relocation Executions for SRNC......................................................642 1.10.20 RLC measurement per RNC(RLC.RNC)..........................................................................................644 1.10.20.1 Number of Packets Sent at the RLC Layer...............................................................................645 1.10.20.2 Number of Packets Received at the RLC Layer.......................................................................646 1.10.20.3 Number of Packets Discarded by All RLCs in RNC................................................................647 1.10.20.4 Number of Packets Retransmitted by All RLCs in AM Mode in RNC...................................648 1.10.20.5 Number of PDUs with the Size Smaller than 336 bit Received by RLCs In Acknowledged Mode Carried by TRB........................................................................................................................................649 1.10.20.6 Number of PDUs with the Size Greater than or Equal to 336 bit Received by RLCs In Acknowledged Mode Carried by TRB.....................................................................................................649 1.10.21 Measurement related to IMS(RNC.IMS)..........................................................................................650 1.10.21.1 Mean Number of UEs Setting Up Different IMS Services......................................................652 1.10.21.2 Number of UEs Setting Up IMS Services................................................................................654 1.10.22 RRC connection release measurement per RNC(RRC.Rel.RNC)....................................................654 1.10.22.1 Number of RRC Connection Releases.....................................................................................656 1.10.22.2 Counters Related to the Number of RRC Connection Releases due to Different Causes........657 1.10.22.3 Number of RRC Releases Due to Failure in the UE State Transition to CELL_PCH Triggered by Signaling Connection Release Indication.................................................................................................660 1.10.22.4 Number of RRC Connection Releases Triggered by SRNC Due to DSCR.............................661 1.10.22.5 Number of RRC Connection Releases Triggered by DRNC Due to DSCR............................663 1.10.23 RRC connection setup measurement per RNC(RRC.Setup.RNC)....................................................664 1.10.23.1 Counters Related to the Number of RRC Connection Requests Processed by RNC...............667 1.10.23.2 Total Number of RRC Connection Requests Received by RNC.............................................669 1.10.23.3 Counters Related to the Number of Successful RRC Connection Establishments..................670 1.10.24 RRC state measurement(RRC.STATE)............................................................................................672 1.10.24.1 Counters Related to the Number of UEs in Different RRC Connection States for RNC.........673 1.10.24.2 Number of PTT UEs in URA_PCH State for RNC..................................................................674 1.10.24.3 Average Number of UEs in the URA_PCH State and Carried on the EPCH for RNC...........675 1.10.25 Soft Handover Measurement per RNC(SHO.RNC)..........................................................................676 1.10.25.1 Number of Softer Handover Attempts......................................................................................677 1.10.25.2 Number of Soft Handover Attempts.........................................................................................679 1.10.25.3 Number of Successful Soft Handovers.....................................................................................680 1.10.25.4 Number of Successful Softer Handovers..................................................................................682 1.10.25.5 Mean Number of UEs with One to Six Radio Link.................................................................683 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvi
Contents
1.10.25.6 Number of Call Drops due to Soft Handover Failures.............................................................685 1.10.26 Measurement related to Security mode per RNC(SM.RNC)............................................................687 1.10.26.1 Number of SECURITY MODE COMMAND Messages Received by RNC from CN...........688 1.10.26.2 Number of SECURITY MODE COMPLETE Messages Sent from RNC to CN....................689 1.10.26.3 Number of SECURITY MODE REJECT Messages Sent from RNC to CN for Different Causes ..................................................................................................................................................................691 1.10.26.4 Number of SECURITY MODE COMMAND Messages Sent from RNC to UE....................692 1.10.26.5 Number of SECURITY MODE COMPLETE Messages Received by RNC from UE............694 1.10.27 Traffic Measurement per RNC(TRAFF.LOAD.RNC)......................................................................695 1.10.27.1 Equivalent Erlang of CS Domain in RNC................................................................................696 1.10.27.2 Maximum Equivalent Erlang of CS Domain in RNC..............................................................697 1.10.27.3 UL Traffic of R99 PS Domain in RNC....................................................................................698 1.10.27.4 Maximum UL Traffic of R99 PS Domain in RNC..................................................................699 1.10.27.5 DL Traffic of R99 PS Domain in RNC....................................................................................700 1.10.27.6 Maximum DL Traffic of R99 PS Domain in RNC..................................................................701 1.10.27.7 DL Traffic of HSDPA PS Domain in RNC..............................................................................702 1.10.27.8 Maximum DL Traffic of HSDPA PS Domain in RNC............................................................703 1.10.27.9 UL Traffic of HSUPA PS Domain in RNC..............................................................................703 1.10.27.10 Maximum UL Traffic of HSUPA PS Domain in RNC..........................................................704 1.10.27.11 DL Traffic of MBMS or IMB PS Domain in RNC................................................................705 1.10.27.12 Maximum DL Traffic of MBMS or IMB PS Domain in RNC..............................................706 1.10.27.13 Average Total Throughout of UL and DL PS Services for RNC...........................................707 1.10.27.14 Maximum Total Throughout of UL and DL PS Services......................................................707 1.10.27.15 Erlang of CS Services for RNC..............................................................................................708 1.11 Measurement of ROAMCNOPERATOR Performance(ROAM_CNOPERATOR)....................................709 1.11.1 Roaming UE Registration Measurement Under MOCN(MOCN.ROAM.CNOPERATOR)..............709 1.11.1.1 Number of Roaming UEs that Is Registered In Local Operator Under MOCN for the First Time ..................................................................................................................................................................710 1.12 Measurement of Radio Cell Performance(UCELL).....................................................................................711 1.12.1 Measurement related to Algorithm per cell(ALGO.Cell)....................................................................714 1.12.1.1 Number of DL Rate Increases for AMR Services......................................................................736 1.12.1.2 Counters Related to the Number of Successful Dynamic Channel Conversions Between DCH and FACH........................................................................................................................................................738 1.12.1.3 Number of State Transfer Attempts from CELL_FACH to CELL_PCH..................................739 1.12.1.4 Number of Successful State Transfers from CELL_FACH to CELL_PCH..............................741 1.12.1.5 Counters Related to the Number of Downlink DCH DCCC Downsizing Attempts Based on Different Strategies...................................................................................................................................742 1.12.1.6 Counters Related to the Number of Successful DL DCH DCCC Downsizings Based on Different DCCC Strategies.......................................................................................................................................744 1.12.1.7 Counters Related to the Number of UL or DL Overload Congestion........................................745 1.12.1.8 Counters Related to the Duration of UL or DL Overload Congestion.......................................747 1.12.1.9 Number of UEs Transferring BE Service to Common Channel in Overload Congestion.........748 1.12.1.10 Counters Related to the Duration of Cell in LDR State Due to Congestion of Various Resources ..................................................................................................................................................................748 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
1.12.1.11 Counters Related to the Number of Times a Cell Is in LDR State Due to Congestion of Various Resources..................................................................................................................................................750 1.12.1.12 Counters Related to the Number of UEs Performing BE Service TF Control in Overload Congestion................................................................................................................................................751 1.12.1.13 Counters Related to the Number of UEs Released Due to Overload Congestion....................752 1.12.1.14 Number of Failed Admissions Due to HSPA User Number Exceeding Threshold During RAB Establishment for Cell..............................................................................................................................754 1.12.1.15 Number of Preemptions During RAB Establishment...............................................................757 1.12.1.16 Number of Failed Requests for various Resources During SHO for Cell................................758 1.12.1.17 Number of Failed Requests for various Resources During DCCC for Cell.............................761 1.12.1.18 Counters Related to the Number of Failed Requests for Different Resources During Channel Type Switch.......................................................................................................................................................762 1.12.1.19 Number of Failed Requests for various Resources During HHO for Cell...............................765 1.12.1.20 Number of Preemptions During HHO......................................................................................767 1.12.1.21 Number of MBMS PTM Service Releases in Overload Congestion.......................................768 1.12.1.22 Number of MBMS PTP Service Releases in Overload Congestion.........................................769 1.12.1.23 Counters Related to the Number of UEs Performing Inter-Frequency Load Handovers in Basic Congestion................................................................................................................................................769 1.12.1.24 Counters Related to the Number of UEs Performing BE Service Downsizing in Basic Congestion ..................................................................................................................................................................771 1.12.1.25 Counters Related to the Number of UEs Performing Uncontrollable Real-Time Service QoS Renegotiation in Basic Congestion...........................................................................................................772 1.12.1.26 Counters Related to the Number of UEs Performing CS Inter-RAT Handovers in Basic Congestion................................................................................................................................................774 1.12.1.27 Counters Related to the Number of UEs Performing PS Inter-RAT Handovers in Basic Congestion ..................................................................................................................................................................775 1.12.1.28 Counters Related to the Number of UEs Performing AMR Rate Decrease in Basic Congestion ..................................................................................................................................................................776 1.12.1.29 Number of UEs Performing Code Adjustment Attempts in DL Basic Congestion for Cell ..................................................................................................................................................................777 1.12.1.30 Number of MBMS Services Performing Power Decreasing in Basic Congestion...................778 1.12.1.31 Counters Related to the Number of Qoffset Updates Due to Load Level Change...................779 1.12.1.32 Counters Related to the Number of Sintersearch Updates Due to Cell Load Change.............780 1.12.1.33 Number of Successful Cell Resource Requests During HHO..................................................782 1.12.1.34 Number of Cell Resource Requests During HHO....................................................................784 1.12.1.35 Number of Successful Cell Resource Requests During RAB Establishment..........................785 1.12.1.36 Number of Cell Resource Requests During RAB Establishment.............................................786 1.12.1.37 Number of Successful Cell Resource Requests due to UE Service Reconfiguration (Cell) ..................................................................................................................................................................788 1.12.1.38 Number of Cell Resource Requests due to UE Service Reconfiguration (Cell)......................789 1.12.1.39 Number of Successful Cell Resource Requests During SHO..................................................790 1.12.1.40 Number of Cell Resource Requests During SHO....................................................................791 1.12.1.41 Number of Successful Cell Resource Requests During Channel Type Switch........................792 1.12.1.42 Number of Cell Resource Requests During Channel Type Switch..........................................793 1.12.1.43 Counters Related to the Mean Number of Equivalent Voice UEs in CEL_DCH State...........795 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xviii
Contents
1.12.1.44 Duration of Cell Dynamic Shutdown Due to Automatic Shutdown........................................796 1.12.1.45 Cell Unavailability Duration caused by O&M (Cell)...............................................................796 1.12.1.46 Counters Related to the Cell Credit Usage...............................................................................797 1.12.1.47 Counters Related to the Duration of Max and Min Values of CPICH Power Due to Cell Breathing ..................................................................................................................................................................798 1.12.1.48 Counters Related to the Number of CPICH Power Adjustments Due to Cell Breathing.........800 1.12.1.49 Counters Related to the Duration of TCP Underload and Overload........................................801 1.12.1.50 Average CPICH Power for Cell...............................................................................................802 1.12.1.51 Counters Related to the Number of Dynamic Channel Conversion Attempts Between DCHs and FACHs......................................................................................................................................................803 1.12.1.52 Number of UL Rate Increases for AMR WB Speech Service..................................................804 1.12.1.53 Counters Related to the Number of UL EDCH DCCC Attempts Based on Throughput or RLC BO.............................................................................................................................................................805 1.12.1.54 Counters Related to the Number of Successful UL EDCH DCCC Operations Based on Throughput or RLC BO............................................................................................................................807 1.12.1.55 Number of UEs Performing Code Adjustment Based on HSDPA...........................................808 1.12.1.56 Number of DL DCH DCCC Upsizing Attempts Based on Throughput or RLC BO...............810 1.12.1.57 Number of Successful DL DCH DCCC Upsizings Based on Throughput or RLC BO...........811 1.12.1.58 Number of UL DCH DCCC Upsizing Attempts Based on Throughput or RLC BO...............813 1.12.1.59 Number of Successful UL DCH DCCC Upsizings Based on Throughput or RLC BO...........814 1.12.1.60 Counters Related to the Number of UL DCH DCCC Downsizing Attempts Based on Different Strategies..................................................................................................................................................816 1.12.1.61 Counters Related to the Number of Successful UL DCH DCCC Downsizings Based on Different Strategies..................................................................................................................................................817 1.12.1.62 Number of UEs Performing Successful Code Adjustment in DL Basic Congestion...............819 1.12.1.63 Number of UEs Performing Successful Code Adjustment Based on HSDPA.........................820 1.12.1.64 Duration of Cell Unavailability Due to System Faults.............................................................821 1.12.1.65 Duration of HSDPA Service Unavailability Due to System Fault...........................................822 1.12.1.66 Duration of HSUPA Service Unavailability Due to System Fault...........................................823 1.12.1.67 Number of Attempts to transfer state from CELL_PCH to CELL_FACH for cell..................824 1.12.1.68 Number of Successful state transfer from CELL_PCH to CELL_FACH for cell...................825 1.12.1.69 Number of state transfer from CELL_PCH to URA_PCH for cell..........................................828 1.12.1.70 Number of Attempts to transfer state from URA_PCH to CELL_FACH for cell...................829 1.12.1.71 Number of successful state transfer from URA_PCH to CELL_FACH in the best cell..........831 1.12.1.72 Number of Cell Deletions or Establishments Due to Dynamic Cell Shutdown.......................834 1.12.1.73 Number of State Transfer Attempts from CELL_DCH to CELL_PCH for Cell.....................835 1.12.1.74 Number of Successful State Transfers from CELL_DCH to CELL_PCH for Cell.................836 1.12.1.75 Number of State Transfer Attempts from CELL_DCH or CELL_FACH to CELL_PCH for FAST DORMANCY user for Cell......................................................................................................................838 1.12.1.76 Number of Successful State Transfers from CELL_DCH or CELL_FACH to CELL_PCH for FAST DORMANCY user........................................................................................................................840 1.12.1.77 Number of Attempts to transfer state from CELL_PCH to CELL_DCH for cell....................842 1.12.1.78 Number of Successful state transfer from CELL_PCH to CELL_DCH for cell......................843 1.12.1.79 Number of Attempts to transfer state from URA_PCH to CELL_DCH for cell......................845 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
1.12.1.80 Number of successful state transfer from URA_PCH to CELL_DCH in the best cell............846 1.12.1.81 Number of Attempts of CELL_PCH/URA_PCH-to-CELL_DCH State Transition Together with DRD for Cell............................................................................................................................................848 1.12.1.82 Number of Successful CELL_PCH/URA_PCH-to-CELL_DCH State Transitions Together with DRDs for Cell...........................................................................................................................................849 1.12.1.83 Number of CPICH Power Adjustments Based on RTWP for Cell..........................................851 1.12.1.84 Duration of PCPICH Power Under Minimum RTWP Threshold............................................852 1.12.1.85 Number of State Transfer Attempts from CELL_DCH to CELL_PCH or URA_PCH for Cell for HSDPA service.........................................................................................................................................853 1.12.1.86 Number of Successful Times That a UE Performing HSDPA Services Transits to CELL_PCH or URA_PCH State for cell......................................................................................................................854 1.12.1.87 Number of Attempts for a UE Performing HSUPA Services to Transit to CELL_PCH or URA_PCH State for Cell..........................................................................................................................856 1.12.1.88 Number of Successful Times That a UE Performing HSUPA Services Transits to CELL_PCH or URA_PCH State for cell......................................................................................................................857 1.12.1.89 Number of Attempts for a UE Performing PS R99 Services to Transit to CELL_PCH or URA_PCH State for Cell..........................................................................................................................859 1.12.1.90 Number of Successful Times That a UE Performing PS R99 Services Transits to CELL_PCH or URA_PCH State for cell...........................................................................................................................860 1.12.1.91 Number of Times That PS R99 Service Rate Is Found to Be Higher than HSUPA Service Rate ..................................................................................................................................................................862 1.12.1.92 Number of PS R99 BE Rate Reduction Requests Triggered by Unfairness Between PS R99 Service Rate and HSUPA Service Rate....................................................................................................863 1.12.1.93 Duration of CPU Resource Insufficiency Reported by NodeB................................................864 1.12.1.94 Congestion Duration of DCCHs, DTCHs and CCCHs Carried over FACHs for Cell............865 1.12.2 Algorithm Measurement2 for Cell(ALGO2.Cell)...............................................................................866 1.12.2.1 Average Number of UEs Using OLPC Enhancement Based on SIRerror Distribution.............872 1.12.2.2 Average and Maximum Uplink Background Noise...................................................................873 1.12.2.3 Number of Automatic Uplink Background Noise Updates........................................................874 1.12.2.4 Counters Related to the Number of Failed in Channal Transfering Process..............................875 1.12.2.5 Number of RoT adjustments in an HSUPA cell.........................................................................876 1.12.2.6 Number of Successful TTI Switchovers with Various Causes During RB Reconfiguration in a Cell (2ms to 10ms)...........................................................................................................................................877 1.12.2.7 Number of Times HSUPA UEs Processing BE Services Succeed in Setting Up RABs over the DCH in Case of Weak Coverage..............................................................................................................879 1.12.2.8 Mean Number of Access Classes Restricted Due to Cell Resource Congestion........................880 1.12.2.9 Duration of Access Class Restriction Triggered by Cell Resource Congestion.........................882 1.12.2.10 Number of UEs Involved in Inter-Frequency Load-based Handovers in a CLB Cell..............883 1.12.2.11 Number of Attempts to Configure CQI Feedback Period for a Cell........................................884 1.12.2.12 Number of Attempts to Configure BLER in a Congested or Normal Cell...............................885 1.12.2.13 Number of CS RABs Abnormally Released for Special UEs for Cell.....................................886 1.12.2.14 Number of CS RABs Normally Released for Special UEs for Cell.........................................889 1.12.2.15 Uplink Actual Cell Load...........................................................................................................891 1.12.2.16 Number of CELL_FACH to URA_PCH State Transition Attempts........................................893 1.12.2.17 Number of Successful CELL_FACH to URA_PCH State Transitions....................................895 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xx
Contents
1.12.2.18 Number of CELL_DCH to URA_PCH State Transition Attempts..........................................897 1.12.2.19 Number of Successful CELL_DCH to URA_PCH State Transitions......................................898 1.12.2.20 Number of Pilot PO Optimization Attempts in the DL DPCH for Cell...................................900 1.12.2.21 Number of Normal Pilot PO Attempts in the DL DPCH for Cell............................................900 1.12.2.22 Total number of times a micro cell transits to the total desensitization state...........................901 1.12.2.23 Total time periods of the total desensitization state for a micro cell........................................902 1.12.2.24 Average desensitization intensity for a micro cell....................................................................903 1.12.2.25 Average and Maximum Uplink Credit Usage of LCG for Cell................................................904 1.12.2.26 Number of State Transition Attempts from CELL_PCH or URA_PCH to CELL_FACH and then to CELL_DCH Due to Data Transmission Requirements for Cell..........................................................905 1.12.2.27 Number of Successful State Transitions from CELL_PCH or URA_PCH to CELL_FACH and then to CELL_DCH Due to Data Transmission Requirements for Cell..................................................906 1.12.3 Measurement related to BLER per cell(BLER.Cell)...........................................................................908 1.12.3.1 Percentage of Duration When UL BLER on DCH Exceeds Target Value for Cell...................914 1.12.3.2 UL BLER of Services on RACH or DCH for Cell.....................................................................918 1.12.3.3 Number of TBs with UL CRCI Errors for Services on RACH or DCH for Cell.......................921 1.12.3.4 Number of UL BLER Samplings for Services on the RACH or DCH for Cell.........................923 1.12.3.5 Percentage of Duration for AMR Voice Quality Being at A Level to Total Call Duration for Cell ..................................................................................................................................................................925 1.12.3.6 Average VQI for AMR Services................................................................................................927 1.12.4 Cell Measurement on BOOST(BOOST.CELL)..................................................................................928 1.12.4.1 Number of R99 Downlink Bytes of UU BOOST Anchor for Cell............................................931 1.12.4.2 Mean Throughput of R99 Downlink of UU BOOST Anchor for Cell.......................................931 1.12.4.3 Number of HSDPA Downlink Bytes of UU BOOST Anchor for Cell......................................932 1.12.4.4 Mean Throughput of HSDPA Downlink of UU BOOST Anchor for Cell................................933 1.12.4.5 Number of R99 Uplink Bytes of UU BOOST Anchor for Cell.................................................934 1.12.4.6 Mean Throughput of R99 Uplink of UU BOOST Anchor for Cell............................................935 1.12.4.7 Number of HSUPA Uplink Bytes of UU BOOST Anchor for Cell...........................................936 1.12.4.8 Mean Throughput of HSUPA Uplink of UU BOOST Anchor for Cell.....................................937 1.12.4.9 Number of R99 Downlink Bytes of UU BOOST Branch for Cell.............................................937 1.12.4.10 Mean Throughput of R99 Downlink of UU BOOST Branch for Cell.....................................938 1.12.4.11 Number of HSDPA Downlink Bytes of UU BOOST Branch for Cell....................................939 1.12.4.12 Mean Throughput of HSDPA Downlink of UU BOOST Branch for Cell...............................940 1.12.4.13 Number of R99 Uplink Bytes of UU BOOST Branch for Cell................................................941 1.12.4.14 Mean Throughput of R99 Uplink of UU BOOST Branch for Cell..........................................942 1.12.4.15 Number of HSUPA Uplink Bytes of UU BOOST Branch for Cell.........................................942 1.12.4.16 Mean Throughput of HSUPA Uplink of UU BOOST Branch for Cell....................................943 1.12.4.17 Number of UU BOOST BPL Capability Indication Messages Received for Cell...................944 1.12.4.18 Number of Successful Responses to UU BOOST BPL Capability Indication Messages Transmitted for Cell..................................................................................................................................945 1.12.4.19 Number of UU BOOST BPL User Information Indication Messages Received for Cell........946 1.12.4.20 Number of Successful Responses to UU BOOST BPL User Information Indication Messages Transmitted for Cell..................................................................................................................................948 1.12.4.21 Number of UU BOOST BPL Release Messages Transmitted for Cell....................................949 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
Contents
1.12.4.22 Number of Successful UU BOOST Setups for Cell.................................................................950 1.12.4.23 Number of Normal UU BOOST Anchor Releases for Cell.....................................................951 1.12.4.24 Number of Normal UU BOOST Branch Releases for Cell......................................................952 1.12.4.25 Average Number of UU BOOST Anchor UEs for Cell...........................................................953 1.12.4.26 Average Number of UU BOOST Branch UEs for Cell............................................................954 1.12.5 Common Channel Measurement per Cell(CCH.Cell).........................................................................955 1.12.5.1 Number of TBs That Contain only TRB Data on FACHs.........................................................955 1.12.5.2 Number of TBs That Contain SRB Data on FACHs..................................................................956 1.12.5.3 Number of TTIs During Which One SRB TB Is Transmitted on FACHs.................................957 1.12.5.4 Number of TRB TBs Received on RACHs................................................................................958 1.12.6 Cell Update Measurement per cell(CELLUPDATE.Cell)..................................................................959 1.12.6.1 Number of Unsuccessful Cell Updates due to RL Failure (No Response).................................963 1.12.6.2 Number of Confirmation Messages from SRNC.......................................................................965 1.12.6.3 Number of Cell Update Attempts for Different Causes.............................................................966 1.12.6.4 Number of Successful Cell Updates for Different Causes.........................................................969 1.12.6.5 Number of RRC Connection Releases due to Cell Update Failure............................................974 1.12.6.6 Number of Cell Update Failures due to No Response from UEs in the CELL_FACH State for Cell ..................................................................................................................................................................975 1.12.6.7 Number of Cell Updates in a Cell..............................................................................................976 1.12.6.8 Number of Cell Updates Triggered by CS Service Establishments in a Cell.............................977 1.12.6.9 Number of Cell Updates that Are Under CPU Usage-Based Flow Control and Are Triggered by CS Service Establishments in a Cell.........................................................................................................978 1.12.6.10 Number of Cell Updates that Are Under RRC Queuing-Based Flow Control and Are Triggered by CS Service Establishments in a Cell....................................................................................................979 1.12.6.11 Number of Cell Updates that Are Under RRC Queuing-Based Flow Control in a Cell..........980 1.12.6.12 Number of Cell Update Attempts for Cell (Originating Conversational Call).........................981 1.12.6.13 Number of Successful Cell Updates for Cell (Originating Conversational Call).....................982 1.12.6.14 Number of Outgoing P2F Redirections for Cell.......................................................................984 1.12.6.15 Number of Incoming P2F Redirections for Cell (Cell Update)................................................986 1.12.6.16 Number of P2F Redirection Failures Caused by UE Not Accessing the Target Frequency for Cell ..................................................................................................................................................................988 1.12.6.17 Number of P2F Redirection Failures Caused by UE No Response for Cell............................989 1.12.7 Measurement of Compressed Mode per cell(CM.Cell).......................................................................991 1.12.7.1 Number of Up Link SF-2 Compressed Mode Activation Attempts...........................................992 1.12.7.2 Number of Up Link HLS Compressed Mode Activation Attempts...........................................994 1.12.7.3 Number of Up Link SF-2 Compressed Mode Activation Fails..................................................995 1.12.7.4 Number of Up Link HLS Compressed Mode Activation Fails..................................................996 1.12.7.5 Number of Down Link SF-2 Compressed Mode Activation Attempts......................................997 1.12.7.6 Number of Down Link HLS Compressed Mode Activation Attempts......................................999 1.12.7.7 Number of Down Link SF-2 Compressed Mode Activation Fails...........................................1000 1.12.7.8 Number of Down Link HLS Compressed Mode Activation Fails...........................................1001 1.12.8 EFACH Measurement per cell(EFACH.Cell)...................................................................................1002 1.12.8.1 Number of RRC Connection Requests in a Cell (EFACH)......................................................1006 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxii
Contents
1.12.8.2 Number of Successful RRC Connection Setups in a Cell (EFACH).......................................1007 1.12.8.3 Number of PS RAB Setup Attempts on EFACH in a Cell.......................................................1009 1.12.8.4 Number of Successful PS RAB Setup on EFACH in a Cell....................................................1010 1.12.8.5 Signaling Delay of PS RAB Established on CCH in a Cell.....................................................1011 1.12.8.6 Number of Abnormally Released PS RABs on the EFACH in a Cell.....................................1013 1.12.8.7 Number of Normal Released PS RABs on the EFACH in a Cell............................................1016 1.12.8.8 Number of Downlink MAC PDU Bytes on the EFACH over the Iub Interface......................1018 1.12.8.9 Signaling Delay of RRC Established on EFACH in a Cell......................................................1019 1.12.8.10 Number of UEs Carried on the EFACH or Those Carried on the EFACH and Using E-DRX ................................................................................................................................................................1021 1.12.8.11 Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_DCH (DCH) for Cell....................................................................................................................................................1023 1.12.8.12 Number of Successful State Transitions from Enhanced CELL_FACH to CELL_DCH (DCH) for Cell....................................................................................................................................................1025 1.12.8.13 Number of Successful State Transitions from Enhanced CELL_FACH to CELL_DCH (HSDSCH) for Cell.......................................................................................................................................1027 1.12.8.14 Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_DCH (HSDSCH) for Cell.......................................................................................................................................1028 1.12.8.15 Number of Successful State Transitions from CELL_PCH or URA_PCH to Enhanced CELL_FACH for Cell............................................................................................................................1030 1.12.8.16 Number of Attempts at State Transitions from CELL_PCH or URA_PCH to Enhanced CELL_FACH for Cell............................................................................................................................1031 1.12.8.17 Number of Successful State Transitions from Enhanced CELL_FACH to CELL_PCH or URA_PCH for Cell.................................................................................................................................1033 1.12.8.18 Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_PCH or URA_PCH for Cell.................................................................................................................................1034 1.12.9 EPCH Measurement per cell(EPCH.Cell).........................................................................................1036 1.12.9.1 Average Number of UEs Carried on the EPCH or Those Carried on the EPCH and Allocated Dedicated H-RNTI for Cell....................................................................................................................1037 1.12.10 ERACH Measurement per cell(ERACH.Cell)................................................................................1038 1.12.10.1 Number of UEs Carried on ERACH for Cell.........................................................................1040 1.12.10.2 Number of Requests for Setting Up RRC Connections on an ERACH for Cell....................1040 1.12.10.3 Number of Successful RRC Connection Setups on an ERACH for Cell...............................1042 1.12.10.4 Number of PS RAB Setup Requests on an ERACH for Cell.................................................1043 1.12.10.5 Number of Successful PS RAB Setups on an ERACH for Cell.............................................1045 1.12.10.6 Number of PS RABs Normally Released on an ERACH for Cell.........................................1046 1.12.10.7 Number of PS RABs Abnormally Released on an ERACH for Cell.....................................1048 1.12.10.8 RRC Connection Setup Duration on an ERACH for Cell......................................................1051 1.12.10.9 Traffic over ERACH on Iub Interface....................................................................................1053 1.12.10.10 Number of Successful State Transitions from CELL_DCH (E-DCH) to Enhanced CELL_FACH (E-DCH) for Cell....................................................................................................................................1054 1.12.10.11 Number of Attempts at State Transitions from CELL_DCH (E-DCH) to Enhanced CELL_FACH (E-DCH) for Cell............................................................................................................1056 1.12.11 Hard Handover Measurement per cell(HHO.Cell)..........................................................................1058 1.12.11.1 Number of Incoming Hard Handover Attempts.....................................................................1079 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiii
Contents
1.12.11.2 Number of Successful Incoming Hard Handovers.................................................................1081 1.12.11.3 Number of Relocation Preparation Attempts with Outgoing Intra-Frequency Hard Handovers ................................................................................................................................................................1082 1.12.11.4 Number of Successful Relocation Preparations with Outgoing Intra-Frequency Hard Handovers ................................................................................................................................................................1084 1.12.11.5 Number of Relocation Preparation Attempts with Outgoing Inter-Frequency Hard Handovers ................................................................................................................................................................1085 1.12.11.6 Number of Successful Relocation Preparations with Outgoing Inter-Frequency Hard Handovers ................................................................................................................................................................1086 1.12.11.7 Number of Failed Outgoing Intra-Frequency Hard Handovers Due to No Response from the UE ................................................................................................................................................................1087 1.12.11.8 Number of Failed Preparations for Outgoing Intra-Frequency Hard Handovers...................1089 1.12.11.9 Number of Failed Preparations for Outgoing Inter-Frequency Hard Handovers...................1091 1.12.11.10 Number of Failed Preparations for Outgoing Intra-Frequency Hard Handovers Due to Radio Link Establishment Failure.....................................................................................................................1094 1.12.11.11 Number of Failed Preparations for Outgoing Inter-Frequency Hard Handovers Due to Radio Link Establishment Failure.....................................................................................................................1096 1.12.11.12 Counters Related to the Number of Failed Outgoing Intra-Frequency Hard Handovers for Different Causes.....................................................................................................................................1098 1.12.11.13 Number of CS Outgoing Inter-Band Hard Handover Attempts...........................................1100 1.12.11.14 Number of Successful CS Outgoing Inter-Band Hard Handovers.......................................1102 1.12.11.15 Number of PS Outgoing Inter-Band Hard Handover Attempts...........................................1103 1.12.11.16 Number of Successful PS Outgoing Inter-Band Hard Handovers.......................................1105 1.12.11.17 Number of Outgoing Intra-Frequency Hard Handover Attempts in NodeB........................1106 1.12.11.18 Number of Successful Outgoing Intra-Frequency Hard Handovers in NodeB....................1108 1.12.11.19 Number of Outgoing Intra-Frequency Hard Handover Attempts Between Different NodeBs of RNC........................................................................................................................................................1109 1.12.11.20 Number of Successful Outgoing Intra-Frequency Hard Handovers Between Different NodeBs of RNC....................................................................................................................................................1111 1.12.11.21 Number of Outgoing Intra-Frequency Hard Handover Attempts Between RNCs...............1112 1.12.11.22 Number of Successful Outgoing Intra-Frequency Hard Handovers Between RNCs...........1114 1.12.11.23 Counters Related to the Number of Failed Outgoing Intra-Frequency Hard Handovers Between RNCs for Different Causes.....................................................................................................................1115 1.12.11.24 Counters Related to the Number of Failed Relocation Preparations with Outgoing Hard Handovers for Different Causes.............................................................................................................1117 1.12.11.25 Number of Relocation Execution Attempts with Outgoing Intra-Frequency Hard Handovers ................................................................................................................................................................1120 1.12.11.26 Number of Successful Relocation Executions with Outgoing Intra-Frequency Hard Handovers ................................................................................................................................................................1121 1.12.11.27 Number of Decisions for Outgoing Hard Handovers...........................................................1123 1.12.11.28 Number of Decisions for Incoming Hard Handovers...........................................................1124 1.12.11.29 Number of Decisions for Outgoing Inter-Frequency Hard Handovers in Compressed Mode ................................................................................................................................................................1125 1.12.11.30 Number of Decisions for Incoming Inter-Frequency Hard Handovers in Compressed Mode ................................................................................................................................................................1127 1.12.11.31 Counters Related to the Number of Outgoing Inter-Frequency Hard Handover Attempts Due to Load Balancing.......................................................................................................................................1128 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiv
Contents
1.12.11.32 Counters Related to the Number of Successful Outgoing Inter-Frequency Hard Handovers Due to Load Balancing...................................................................................................................................1130 1.12.11.33 Number of Outgoing Inter-Frequency Hard Handover Attempts.........................................1131 1.12.11.34 Number of Successful Outgoing Inter-Frequency Hard Handovers.....................................1133 1.12.11.35 Counters Related to the Number of Failed Outgoing Inter-Frequency Hard Handovers for Different Causes.....................................................................................................................................1134 1.12.11.36 Number of Failed Outgoing Inter-Frequency Hard Handovers Due to No Response from the UE ................................................................................................................................................................1137 1.12.11.37 Number of Incoming Inter-Frequency Hard Handover Attempts........................................1138 1.12.11.38 Number of Successful Incoming Inter-Frequency Hard Handovers....................................1140 1.12.11.39 Number of Call Drops Due to Failed Outgoing Intra-Frequency Hard Handovers.............1142 1.12.11.40 Number of Outgoing Inter-Frequency Hard Handover Attempts in NodeB........................1144 1.12.11.41 Number of Successful Outgoing Inter-Frequency Hard Handovers in NodeB....................1145 1.12.11.42 Number of Outgoing Inter-Frequency Hard Handovers Attempts Between Different NodeBs of RNC........................................................................................................................................................1147 1.12.11.43 Number of Successful Outgoing Inter-Frequency Hard Handovers Between Different NodeBs of RNC....................................................................................................................................................1148 1.12.11.44 Number of Outgoing Inter-Frequency Hard Handovers Attempts Between RNCs.............1150 1.12.11.45 Number of Successful Outgoing Inter-Frequency Hard Handovers Between RNCs...........1151 1.12.11.46 Number of Relocation Execution Attempts with Outgoing Inter-Frequency Hard Handovers ................................................................................................................................................................1153 1.12.11.47 Number of Successful Relocation Executions with Outgoing Inter-Frequency Hard Handovers ................................................................................................................................................................1154 1.12.11.48 Number of Outgoing Emergency Blind Handover Attempts...............................................1156 1.12.11.49 Number of Successful Outgoing Emergency Blind Hard Handovers..................................1157 1.12.11.50 Counters Related to the Number of Handovers Not Performed Due to Inter-Frequency Measurement Expiry...............................................................................................................................1158 1.12.11.51 Number of Requests for CS and PS Outgoing Inter-Frequency Hard Handovers (Cell) ................................................................................................................................................................1160 1.12.11.52 Number of Successful for CS and PS Outgoing Inter-Frequency Hard Handovers (Cell) ................................................................................................................................................................1162 1.12.11.53 Number of Call Drops due to Unsuccessful Outgoing Inter-Frequency Hard Handovers (Cell) ................................................................................................................................................................1164 1.12.11.54 Number of Failed Outgoing Intra-Frequency Hard Handovers Between the RNCs Due to No Response from the UE............................................................................................................................1166 1.12.11.55 Counters Related to the Number of Failed Outgoing Inter-Frequency Hard Handovers Between the RNCs for Different Causes...............................................................................................................1167 1.12.11.56 Number of Failed Outgoing Inter-Frequency Hard Handovers Between the RNCs Due to No Response from the UE............................................................................................................................1170 1.12.11.57 Counters Related to the Number of Outgoing Inter-Frequency Hard Handover Attempts ................................................................................................................................................................1171 1.12.11.58 Counters Related to the Number of Successful Outgoing Inter-Frequency Hard Handovers ................................................................................................................................................................1176 1.12.11.59 Number of Inter-Frequency Hard Handover Attempts When only Signaling Exists for Cell ................................................................................................................................................................1181 1.12.11.60 Number of Successful Inter-Frequency Hard Handover Attempts When only Signaling Exists for Cell....................................................................................................................................................1183 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxv
Contents
1.12.11.61 Number of Outgoing Macro & Micro Joint Inter-frequency Handover Attempts in PS Domain for Cell....................................................................................................................................................1184 1.12.11.62 Number of Successful Outgoing Macro & Micro Joint Inter-frequency Handovers in PS Domain for Cell....................................................................................................................................................1187 1.12.12 HSDPA Measurement per cell(HSDPA.Cell).................................................................................1190 1.12.12.1 Number of Successful Channel Reconfigurations..................................................................1214 1.12.12.2 Number of Successful HSDPA MAC-d Flow Establishments for Cell.................................1216 1.12.12.3 Number of HSDPA UEs in a Cell..........................................................................................1218 1.12.12.4 Number of MAC-d Flows in a Cell........................................................................................1222 1.12.12.5 Mean Downlink Throughput of single HSDPA MAC-d Flows.............................................1223 1.12.12.6 Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow.....................................1226 1.12.12.7 Number of Handover Attempts Between Channels of Different Types.................................1228 1.12.12.8 Number of HSDPA Serving Cell Change Attempts for Cell.................................................1230 1.12.12.9 Number of Successful HSDPA Serving Cell Changes for Cell.............................................1232 1.12.12.10 Number of Inter-RNC HSDPA Hard Handover Attempts Without Channel Change for Cell ................................................................................................................................................................1234 1.12.12.11 Number of Successful Inter-RNC HSDPA Hard Handovers Without Channel Change for Cell ................................................................................................................................................................1236 1.12.12.12 Number of Successful Inter-Frequency HSDPA Hard Handovers Without Channel Change for Cell..........................................................................................................................................................1238 1.12.12.13 Number of HSDPA RAB Establishment Attempts for Cell.................................................1240 1.12.12.14 Number of Successful HSDPA RAB Establishments for Cell.............................................1243 1.12.12.15 Number of HSDPA RABs Abnormal Released for Cell......................................................1246 1.12.12.16 Number of HSDPA RABs Normal Released for Cell..........................................................1251 1.12.12.17 Number of Inter-RNC HSDPA Hard Handover Attempts for Cell(HSDPA to DCH)........1255 1.12.12.18 Number of Successful inter-RNC HSDPA Hard Handovers for Cell(HSDPA to DCH) ................................................................................................................................................................1257 1.12.12.19 Number of HSDPA UEs with Various Categories in a Cell................................................1259 1.12.12.20 Number of HSDPA MAC-d Flow Establishment Requests for Cell....................................1265 1.12.12.21 Number of Failed HSDPA Service Establishments Due to Insufficiency of Different Resources ................................................................................................................................................................1267 1.12.12.22 Number of MIMO UEs in a Cell..........................................................................................1268 1.12.12.23 Number of Outgoing DRD Attempts for HSDPA Users Through Intelligent User Recognition for Cell....................................................................................................................................................1270 1.12.12.24 Number of Successful Outgoing DRDs for HSDPA Users Through Intelligent User Recognition for Cell....................................................................................................................................................1272 1.12.12.25 Number of RABs Abnormally Released for PS HSDPA Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell.....................................................................1274 1.12.12.26 Average Throughput on HSDPA MAC-d Flow for Cell (Excluding the Data of Low-Traffic Users)......................................................................................................................................................1278 1.12.12.27 Number of Bytes Sent on HSDPA MAC-d Flow for Cell (Excluding the Bytes of Low-Traffic Users)......................................................................................................................................................1279 1.12.12.28 Number of Normal RAB Releases of HSDPA UEs for Cell (All Scenarios)......................1280 1.12.12.29 Number of Abnormal Released RABs for Cell When DB-HSDPA with MIMO Applied (RF Exceptions Considered)..........................................................................................................................1286 1.12.13 HSUPA Measurement per cell(HSUPA.Cell).................................................................................1289 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvi
Contents
1.12.13.1 Number of HSUPA UEs in a Cell..........................................................................................1303 1.12.13.2 Number of Successful EDCH MAC-d Flow Establishments for Cell....................................1304 1.12.13.3 Number of HSUPA RAB Establishment Attempts for Cell...................................................1306 1.12.13.4 Number of Successful HSUPA RAB Establishments for Cell...............................................1308 1.12.13.5 Number of HSUPA RAB establish attempts of BE Service for different prior Level Users (Cell) ................................................................................................................................................................1309 1.12.13.6 Number of Successful HSUPA RAB Establishments of BE Service for different prior Level Users (Cell).......................................................................................................................................................1311 1.12.13.7 Number of HSUPA RABs Abnormal Released for Cell........................................................1312 1.12.13.8 Number of HSUPA RABs Normal Released for Cell............................................................1315 1.12.13.9 Number of HSUPA RAB Released due to UE Signaling Connection failure for Cell..........1317 1.12.13.10 Number of EDCH RL Addition and Deletion Attempts by Soft Handover for Cell............1319 1.12.13.11 Number of Successful EDCH RL Additions and Deletions by Soft Handover for Cell ................................................................................................................................................................1320 1.12.13.12 Number of Successful HSUPA Serving Cell Changes in Soft Handover Status for Cell ................................................................................................................................................................1322 1.12.13.13 Number of HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell........1324 1.12.13.14 Number of inter-RNC HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell ................................................................................................................................................................1326 1.12.13.15 Number of Successful inter-RNC HSUPA Serving Cell Changes in Soft Handover Status for Cell..........................................................................................................................................................1328 1.12.13.16 Number of Successful HSUPA Serving Cell Changes Due to inter-RNC Hard Handover without Channel Change for Cell........................................................................................................................1331 1.12.13.17 Number of HSUPA Serving Cell Change Attempts Due to inter-RNC Hard Handover without Channel Change for Cell........................................................................................................................1332 1.12.13.18 Number of Successful HSUPA Serving Cell Changes Due to Intra-Frequency Hard Handover without Channel Change for Cell...........................................................................................................1334 1.12.13.19 Number of HSUPA Serving Cell Change Attempts Due to Intra-Frequency Hard Handover without Channel Change for Cell...........................................................................................................1336 1.12.13.20 Number of HSUPA Serving Cell Change Attempts Due to Inter-Frequency Hard Handover without Channel Change for Cell...........................................................................................................1338 1.12.13.21 Number of Successful HSUPA Intra-Frequency Hard Handovers for Cell(EDCH to DCH) ................................................................................................................................................................1339 1.12.13.22 Number of HSUPA Intra-Frequency Hard Handover Attempts for Cell(EDCH to DCH) ................................................................................................................................................................1341 1.12.13.23 Number of HSUPA Inter-Frequency Hard Handover Attempts for Cell(EDCH to DCH) ................................................................................................................................................................1342 1.12.13.24 Number of Channel Conversion Attempts According to Different Channel Switch Type for Cell ................................................................................................................................................................1344 1.12.13.25 Number of Successful Handovers Between Different Channel Types for Cell...................1345 1.12.13.26 Mean Uplink Throughput of single HSUPA MAC-d Flow.................................................1347 1.12.13.27 Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow................................1349 1.12.13.28 Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Golden Subscriber ................................................................................................................................................................1349 1.12.13.29 Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service for Golden Subscriber...............................................................................................................................................1351 1.12.13.30 Number of inter-RNC HSUPA Hard Handover Attempts for Cell(EDCH to DCH)...........1353 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvii
Contents
1.12.13.31 Number of Successful inter-RNC HSUPA Hard Handovers for Cell(EDCH to DCH) ................................................................................................................................................................1354 1.12.13.32 Number of Successful HSUPA 16QAM RAB Establishments for cell...............................1356 1.12.13.33 Number of HSUPA 16QAM RABs Abnormal Released for cell........................................1357 1.12.13.34 Number of HSUPA 16QAM RABs Normal Released for cell............................................1360 1.12.13.35 Number of HSUPA 16QAM RAB Setup Attempts for cell.................................................1362 1.12.13.36 Number of HSUPA RABs Abnormal Released due to RF Failures for Cell.......................1364 1.12.13.37 Number of HSUPA UEs with Various Categories in a Cell................................................1366 1.12.13.38 Number of EDCH MAC-d Flow Setup Requests for Cell...................................................1370 1.12.13.39 Number of Failed HSUPA Service Establishments Due to Insufficiency of Different Resources ................................................................................................................................................................1372 1.12.13.40 Average uplink throughput of the Traffic PS Conversational beared on E-DCH for cell ................................................................................................................................................................1374 1.12.13.41 Number of uplink bytes of Transport Blocks of Traffic PS Conversational beared on E-DCH for cell.....................................................................................................................................................1375 1.12.13.42 Counters Related to the Number of Transfers Between Small Retransmission and Large Retransmission for HSUPA 2ms TTI Users or HSUPA 10ms TTI Users.............................................1376 1.12.13.43 Number of TTI Switch Attempts During RB Reconfiguration for Cell...............................1378 1.12.13.44 Number of Successful TTI Switches During RB Reconfiguration for Cell.........................1380 1.12.13.45 Number of HSUPA 16QAM UEs in a Cell..........................................................................1381 1.12.13.46 Number of HSUPA Boosting UEs in a Cell.........................................................................1383 1.12.13.47 Number of UEs Supporting E-DPCCH Boosting and CPC for Cell....................................1383 1.12.13.48 Number of RABs Abnormally Released for PS HSUPA Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell.....................................................................1384 1.12.13.49 Number of HSUPA Boosting RAB Setup Attempts for Cell...............................................1387 1.12.13.50 Number of Successful HSUPA Boosting RAB Setups for Cell...........................................1389 1.12.13.51 Number of Abnormally Released HSUPA Boosting RABs for Cell...................................1390 1.12.13.52 Number of Normally Released HSUPA Boosting RABs for Cell.......................................1393 1.12.13.53 Number of HARQ PO Reconfiguration Attempts of HSUPA Users with 10 ms TTI for Cell ................................................................................................................................................................1395 1.12.13.54 Number of Successful HARQ PO Reconfigurations of HSUPA Users with 10 ms TTI for Cell ................................................................................................................................................................1397 1.12.13.55 Number of DC-HSUPA RAB Setup Attempts for Cell.......................................................1398 1.12.13.56 Number of Successful DC-HSUPA RAB Setups for Cell...................................................1400 1.12.13.57 Number of DC-HSUPA RABs Normally Released for Cell................................................1401 1.12.13.58 Number of DC-HSUPA RABs Abnormally Released for Cell............................................1403 1.12.13.59 Number of HSUPA UEs in a Cell........................................................................................1406 1.12.13.60 Number of HSUPA 2 ms TTI UEs in a Cell........................................................................1408 1.12.13.61 Number of HSUPA 10 ms TTI UEs in a Cell......................................................................1409 1.12.13.62 Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI in a Cell with Various Causes.................................................................................................................1410 1.12.13.63 Number of Abnormal RAB Releases for Cell During State Transition of HSUPA UEs to CELL/ URA_PCH..............................................................................................................................................1412 1.12.13.64 Number of Normal RAB Releases of HSUPA UEs for Cell (All Scenarios)......................1415 1.12.14 InterRAT Handover Measurement per cell(INTRAT.HO.Cell)......................................................1419 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxviii
Contents
1.12.14.1 Number of Successful CS or Enhanced PS Outgoing Inter-RAT Handovers for Cell...........1442 1.12.14.2 Number of Preparations for CS or Enhanced PS Outgoing Inter-RAT Handover for Cell ................................................................................................................................................................1445 1.12.14.3 Number of Successful Preparations for CS or Enhanced PS Outgoing Inter-RAT Handover for Cell..........................................................................................................................................................1448 1.12.14.4 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC for Cell.............1451 1.12.14.5 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by RNC for Cell.........1454 1.12.14.6 Number of Failed Preparations for CS or Enhanced PS Outgoing Inter-RAT Handover for Different Causes for Cell........................................................................................................................1456 1.12.14.7 Number of CS or Enhanced PS Outgoing Inter-RAT Handover Attempts for Cell...............1461 1.12.14.8 Number of Failed CS or Enhanced PS Outgoing Inter-RAT Handovers for Different Causes for Cell..........................................................................................................................................................1464 1.12.14.9 Number of Preparations for CS or Enhanced PS Incoming Inter-RAT Handover for Cell ................................................................................................................................................................1466 1.12.14.10 Number of Successful CS or Enhanced PS Incoming Inter-RAT Handovers for Cell........1468 1.12.14.11 Number of Failed Preparations for CS or Enhanced PS Incoming Inter-RAT Handover for Different Causes for Cell........................................................................................................................1469 1.12.14.12 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE for Cell..........1472 1.12.14.13 Number of Failed CS or Enhanced PS Inter-RAT Incoming Handovers Due to No Response from UE for Cell.....................................................................................................................................1474 1.12.14.14 Number of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC for Different Causes for Cell....................................................................................................................................................1475 1.12.14.15 Number of PS Outgoing Inter-RAT Handover Requests Initiated by UE for Cell..............1477 1.12.14.16 Number of Successful Preparations for CS or Enhanced PS Incoming Inter-RAT Handover for Cell..........................................................................................................................................................1479 1.12.14.17 Number of Times that the Timer Waiting for Iu Release Command Expires in CS or Enhanced PS Outgoing Inter-RAT Handover for Cell............................................................................................1481 1.12.14.18 Number of Times that the Timer Waiting for Iu Release Command Expires in PS Outgoing Inter-RAT Handover Initiated by RNC for Cell.....................................................................................1483 1.12.14.19 Counters Related to the Number of Inter-RAT Measurement Expiry for Cell....................1484 1.12.14.20 Counters Related to the Number of PS Outgoing Inter-RAT Handover Attempts..............1485 1.12.14.21 Counters Related to the Number of Successful PS Outgoing Inter-RAT Handovers..........1487 1.12.14.22 Number of CS Incoming Inter-RAT Handover Attempts for Cell.......................................1490 1.12.14.23 Number of Failed CS Outgoing Inter-RAT Handover Preparations (Relocation Command Wait Timeout) for Cell....................................................................................................................................1491 1.12.14.24 Number of CS Incoming Inter-RAT Handover Preparation Failures (Iu RELEASE COMMAND Received) for Cell...................................................................................................................................1493 1.12.14.25 Number of Abnormally Terminated CS Outgoing Inter-RAT Handovers for Cell..............1494 1.12.14.26 Number of CS Outgoing Inter-RAT Handover Preparation Failures (Iu RELEASE COMMAND Received) for Cell...................................................................................................................................1496 1.12.14.27 Number of Abnormally Terminated PS Outgoing Inter-RAT Handovers for Cell..............1497 1.12.14.28 Number of Failed Outgoing UMTS-to-GSM PS Handovers due to UE Reselection Back to a UTRAN Cell...........................................................................................................................................1499 1.12.14.29 Number of Outgoing Inter-RAT PS Handover Preparation Attempts Triggered by SRVCC for VoIP Services for Cell............................................................................................................................1501 1.12.14.30 Number of Successful Outgoing Inter-RAT PS Handover Preparations Triggered by SRVCC for VoIP Services for Cell......................................................................................................................1502 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxix
Contents
1.12.14.31 Number of Successful Outgoing Inter-RAT PS Handovers Triggered by SRVCC for VoIP Services for Cell.....................................................................................................................................1503 1.12.14.32 Number of Failed CS Outgoing Inter-RAT Handovers for Cell(Signalling Connection Release Indication)...............................................................................................................................................1505 1.12.14.33 Number of Failed PS Outgoing Inter-RAT Handovers for Cell(Signalling Connection Release Indication)...............................................................................................................................................1506 1.12.14.34 Number of Failed PS Outgoing Inter-RAT Handovers for Cell(No SRNS DATA Forward cmd) ................................................................................................................................................................1508 1.12.14.35 Number of Failed CS Outgoing Inter-RAT Handovers for Cell(Failure in the Radio Interface Procedure)...............................................................................................................................................1509 1.12.14.36 Number of Failed PS Outgoing Inter-RAT Handovers for Cell(Failure in the Radio Interface Procedure)...............................................................................................................................................1511 1.12.14.37 Number of RL Reestablishment Attempts After UEs Failed to Receive the CS Outgoing InterRAT Handover Command for Cell........................................................................................................1512 1.12.14.38 Number of RL Reestablishment Attempts After UEs Failed to Receive the PS Outgoing InterRAT Handover Command for Cell........................................................................................................1514 1.12.14.39 Number of Attempts to Obtain GSM System Information During RIM-based NACCs Triggered by Inter-RAT PS Handovers...................................................................................................................1516 1.12.14.40 Number of Successful That GSM System Information Is Obtained During RIM-based NACCs Triggered by Inter-RAT PS Handovers..................................................................................................1517 1.12.14.41 Number of Attempts to Obtain GSM System Information During Iur-g-based ENACCs Triggered by Inter-RAT PS Handovers..................................................................................................1519 1.12.14.42 Number of Successful Times That GSM System Information Is Obtained During Iur-g-based ENACCs Triggered by Inter-RAT PS Handovers..................................................................................1520 1.12.14.43 Number of Attempts at Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell ................................................................................................................................................................1521 1.12.14.44 Number of Successful Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell ................................................................................................................................................................1523 1.12.14.45 Number of Successful Preparations for Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell.........................................................................................................................................1524 1.12.14.46 Number of Preparation Attempts for Incoming LTE-to-UMTS CS+PS Handovers Triggered by SRVCC for VoIP Services.....................................................................................................................1525 1.12.14.47 Number of Successful Preparations for Incoming LTE-to-UMTS CS+PS Handovers Triggered by SRVCC for VoIP Services................................................................................................................1528 1.12.14.48 Number of Incoming LTE-to-UMTS CS+PS Handover Attempts Triggered by SRVCC for VoIP Services...................................................................................................................................................1530 1.12.14.49 Number of Successful Incoming LTE-to-UMTS CS+PS Handovers Triggered by SRVCC for VoIP Services.........................................................................................................................................1532 1.12.15 Measurement Related to the Release of Iu Signaling Connections (Without RAB) (Cell) (IU.Sig.Rel.Cell)...........................................................................................................................................1534 1.12.15.1 Number of Iu CS Signaling Connections (Without RAB) Normally Released for Cell........1536 1.12.15.2 Number of Iu PS Signaling Connections (Without RAB) Normally Released for Cell.........1537 1.12.15.3 Number of Iu CS Signaling Connections (Without RAB) Abnormally Released for Cell ................................................................................................................................................................1538 1.12.15.4 Number of Iu PS Signaling Connections (Without RAB) Abnormally Released for Cell ................................................................................................................................................................1540 1.12.15.5 Number of Iu CS Signaling Connections (Without RAB) Normally Released for Cell (Service Reasons)..................................................................................................................................................1541 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxx
Contents
1.12.15.6 Number of Iu PS Signaling Connections (Without RAB) Normally Released for Cell (Service Reasons)..................................................................................................................................................1543 1.12.15.7 Number of Iu CS Signaling Connections (Without RAB) Abnormally Released for Cell (Service Reasons)..................................................................................................................................................1544 1.12.15.8 Number of Iu PS Signaling Connections (Without RAB) Abnormally Released for Cell (Service Reasons)..................................................................................................................................................1546 1.12.15.9 Number of Iu CS Signaling Connections (Without RAB) Abnormally Released Due to Security Mode Procedure Failures for Cell (Service Reasons).............................................................................1547 1.12.15.10 Number of Iu PS Signaling Connections (Without RAB) Abnormally Released Due to Security Mode Procedure Failures for Cell (Service Reasons).............................................................................1549 1.12.16 Iub Interface Measurement per cell(IUB.Cell)................................................................................1550 1.12.16.1 Number of RLs with Synchronized Reconfiguration Cancelled on Iub Interface..................1554 1.12.16.2 Number of RL Failures on Iub Interface................................................................................1555 1.12.16.3 Number of RLs Unsuccessfully Restored on Iub Interface due to No Response...................1558 1.12.16.4 Number of RLs Unsuccessfully Added on Iub Interface for Different Causes......................1560 1.12.16.5 Number of RLs Unsuccessfully Synchronization Reconfigured on Iub Interface for Different Causes.....................................................................................................................................................1562 1.12.16.6 Number of RLs Unsuccessfully Reconfigured on Iub Interface due to No Response...........1564 1.12.16.7 Number of RLs Unsuccessfully Established on Iub Interface for Different Causes..............1565 1.12.16.8 Number of RLs Requested to Reconfigure with Synchronization on Iub Interface...............1568 1.12.16.9 Number of RLs Requested to Add on Iub Interface...............................................................1569 1.12.16.10 Number of RLs Requested to Delete on Iub Interface.........................................................1570 1.12.16.11 Number of RLs Requested to Establish on Iub Interface.....................................................1572 1.12.16.12 Number of RLs Restored on Iub Interface...........................................................................1573 1.12.16.13 Number of RLs Successfully Added on Iub Interface..........................................................1574 1.12.16.14 Number of RLs Successfully Deleted on Iub Interface........................................................1576 1.12.16.15 Number of RLs Successfully Reconfigured with Synchronization on Iub Interface...........1578 1.12.16.16 Number of RLs Successfully Established on Iub Interface..................................................1579 1.12.16.17 Number of RLs Unsuccessfully Established on Iub Interface due to No Response.............1581 1.12.17 Measurement related to LCS service per cell(LCS.CELL).............................................................1582 1.12.17.1 Number of Positioning Results Beyond Coverage of UE Reference Cell in UE Assisted AGPS Method....................................................................................................................................................1583 1.12.17.2 Number of Positioning Results Beyond Coverage of UE Reference Cell in UE-based AGPS Method....................................................................................................................................................1584 1.12.17.3 Number of Positioning Results Beyond Coverage of UE Reference Cell in OTDOA Method ................................................................................................................................................................1585 1.12.17.4 Number of Positioning Results Beyond Coverage of UE Reference Cell in CELLID + RTT method....................................................................................................................................................1586 1.12.18 MBMS Measurement per cell(MBMS.Cell)...................................................................................1587 1.12.18.1 Number of Releases of PTP MBMS Services because the new best cell is on PTM mode ................................................................................................................................................................1590 1.12.18.2 Number of Requests for PTP MBMS Setup...........................................................................1590 1.12.18.3 Number of Successful PTP MBMS Setups............................................................................1591 1.12.18.4 Number of Abnormal Releases of PTP MBMS Services for Different Causes.....................1592 1.12.18.5 Number of Normal Releases of PTP MBMS Services...........................................................1593 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxi
Contents
1.12.18.6 Number of Successful Setups of MBMS(PTM) Traffic Channel..........................................1593 1.12.18.7 Number of Unsuccessful Setups of MBMS(PTM) Traffic Channel......................................1595 1.12.18.8 Number of successful PTM to PTP transition in a cell..........................................................1595 1.12.18.9 Number of Successful Transitions from PTP MBMS Service to PTM MBMS Service........1597 1.12.18.10 Number of Transitions from PTP MBMS Service to PTM MBMS Service........................1598 1.12.18.11 Number of RBs in PTM MBMS Service..............................................................................1599 1.12.18.12 Number of PTM setup request..............................................................................................1600 1.12.18.13 Number of Successful Setups of PTM MBMS Service.......................................................1601 1.12.18.14 Mean number of PTP users in a cell of MBMS Channel.....................................................1601 1.12.18.15 Mean number of PTM users in a cell of MBMS Channel....................................................1603 1.12.18.16 A PTM Channel Duration in a cell MBMS service Channel...............................................1604 1.12.18.17 A PTP Channel Duration in a cell MBMS service Channel.................................................1605 1.12.19 RRC Reporting Measurement per cell(MEAR.Report.Cell)...........................................................1606 1.12.19.1 Number of Event 1A Measurement Reports..........................................................................1608 1.12.19.2 Number of Event 1B Measurement Reports...........................................................................1609 1.12.19.3 Number of Event 1C Measurement Reports...........................................................................1610 1.12.19.4 Number of Event 1D Measurement Reports..........................................................................1612 1.12.19.5 Number of Event 2D Measurement Reports..........................................................................1613 1.12.19.6 Number of Event 2F Measurement Reports...........................................................................1614 1.12.19.7 Number of Uplink Event 4A Measurement Reports..............................................................1616 1.12.19.8 Number of Uplink Event 4B Measurement Reports..............................................................1617 1.12.19.9 Number of Downlink Event 4A Measurement Reports.........................................................1619 1.12.19.10 Number of Downlink Event 4B Measurement Reports........................................................1619 1.12.19.11 Average RSCP for Cell.........................................................................................................1620 1.12.19.12 Average Ec/No for Cell........................................................................................................1622 1.12.20 Measurement related to Paging per cell(PAGE.CELL)..................................................................1623 1.12.20.1 Number of Paging Losses due to PCH Congestion................................................................1626 1.12.20.2 Number of Paging Type 1 Messages......................................................................................1627 1.12.20.3 Number of Preemptions by CS Paging due to PCH Congestion per Cell..............................1628 1.12.20.4 Number of Successful Preemptions by CS Paging due to PCH Congestion per Cell............1629 1.12.20.5 Number of Level-1 Paging Attempts for UEs Processing Real-Time or Non-Real-Time Services in the URA_PCH State...........................................................................................................................1631 1.12.20.6 Number of Successful Level-1 Paging Attempts for UEs Processing Real-Time or Non-RealTime Services in the URA_PCH State...................................................................................................1632 1.12.20.7 Number of Successful Layered Paging Attempts for UEs Processing Real-Time or Non-RealTime Services in the URA_PCH State...................................................................................................1634 1.12.20.8 Number of PAGING TYPE 1 Messages Sent by the RNC to UEs in the URA_PCH State ................................................................................................................................................................1635 1.12.20.9 Number of CS PAGING TYPE 1 Messages Sent by the RNC to UEs in the Idle State........1637 1.12.20.10 Number of PS PAGING TYPE 1 Messages Sent by the RNC to UEs in the Idle State ................................................................................................................................................................1638 1.12.20.11 Number of Level-1 Paging Attempts for UEs Performing Real-Time or Non-Real-Time Services in Idle Mode for Cell..............................................................................................................................1639
Issue 01 (2013-05-04)
xxxii
Contents
1.12.20.12 Number of Successful Level-1 Paging Attempts for UEs Performing Real-Time or Non-RealTime Services in Idle Mode for Cell......................................................................................................1640 1.12.20.13 Number of Times a UE Processing SMS services Attempts to Preempt Resources to Be Allocated to Other UEs When the PCH Is Congested for Cell...............................................................................1642 1.12.20.14 Number of Successful Preemptions by SMS Paging due to PCH Congestion per Cell ................................................................................................................................................................1643 1.12.20.15 Number of ETWS-related PAGING TYPE 1 Messages Sent in a Cell...............................1644 1.12.21 Measurement by Operator for Cell(PLMN.CELL).........................................................................1645 1.12.21.1 Credit Consumption of Operator0..........................................................................................1649 1.12.21.2 Credit Consumption of Operator1..........................................................................................1650 1.12.21.3 Credit Consumption of Operator2..........................................................................................1651 1.12.21.4 Credit Consumption of Operator3..........................................................................................1652 1.12.21.5 Equivalent Erlangs Consumed by CS Services of Operator0.................................................1653 1.12.21.6 Equivalent Erlangs Consumed by CS Services of Operator1.................................................1653 1.12.21.7 Equivalent Erlangs Consumed by CS Services of Operator2.................................................1654 1.12.21.8 Equivalent Erlangs Consumed by CS Services of Operator3.................................................1655 1.12.21.9 Number of Spreading Codes Occupied by Operator0............................................................1656 1.12.21.10 Number of Spreading Codes Occupied by Operator1..........................................................1657 1.12.21.11 Number of Spreading Codes Occupied by Operator2..........................................................1658 1.12.21.12 Number of Spreading Codes Occupied by Operator3..........................................................1659 1.12.21.13 Number of Spreading Codes Occupied by Shared Operator for MOCN Cell......................1660 1.12.22 Measurements related to PTT(PTT.Cell)........................................................................................1662 1.12.22.1 Number of Successful PTT Call Initiation Attempts or Responses During a P2D Procedure for UEs Processing PTT Services................................................................................................................1666 1.12.22.2 Number of PTT Call Initiation or Response Attempts of UEs Using Only the PTT Service in the CELL_FACH State for Cell...................................................................................................................1669 1.12.22.3 Number of Successful PTT Call Initiation Attempts or Responses of UEs Using Only the PTT Service in the CELL_FACH State for Cell............................................................................................1670 1.12.22.4 Number of Successful PTT Call Initiation Attempts or Responses of UEs Using the PTT and Other Services in the CELL_FACH State for Cell.................................................................................1672 1.12.22.5 Number of Complete PTT Calls for Cell................................................................................1673 1.12.22.6 Number of RABs Abnormally Released During PTT Calls for Cell.....................................1675 1.12.22.7 Number of Successful State Transitions from CELL_PCH/URA_PCH to CELL_DCH After the RNC Sends the CELL UPDATE CONFIRM Message for Cell............................................................1677 1.12.22.8 Number of Successful PTT Paging Attempts After the RNC Sends the PAGING TYPE 1 Message for Cell....................................................................................................................................................1681 1.12.22.9 Number of PTT Call Initiation or Response Attempts of UEs Using the PTT and Other Services in the CELL_FACH State for Cell.........................................................................................................1683 1.12.22.10 Number of Failed PTT Call Initiations or Responses Due to Resource Congestion During a P2D Procedure for UEs Processing PTT Services.........................................................................................1685 1.12.22.11 Number of Failed PTT Call Initiation Attempts or Responses of a UE in the CELL_FACH State Processing Only the PTT Service Due to Congestion for Cell...............................................................1687 1.12.22.12 Number of Failed PTT Call Initiation Attempts or Responses of a UE in the CELL_FACH State Processing Multiple Services Due to Congestion for Cell.....................................................................1688 1.12.22.13 Number of PTT Call Initiation Attempts or Responses During a P2D Procedure for UEs Processing PTT Services........................................................................................................................1689 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxiii
Contents
1.12.22.14 Uplink Traffic Volume of the PTT Service..........................................................................1692 1.12.22.15 Downlink Traffic Volume of the PTT Service.....................................................................1693 1.12.22.16 Number of Successful Serving Cell Changes of PTT Service in Soft Handover Status ................................................................................................................................................................1694 1.12.22.17 Number of Serving Cell Change Attempts of PTT Service in Soft Handover Status..........1697 1.12.22.18 Number of Successful Hard Handovers of PTT Service......................................................1700 1.12.22.19 Number of Hard Handover Attempts of PTT Service..........................................................1703 1.12.23 Measurement related to QOS per cell(QOS.Cell)...........................................................................1706 1.12.23.1 Delay of Different Services....................................................................................................1724 1.12.23.2 Counters Related to the Number of Times that DL Throughput of HSDPA Services Within Each Range......................................................................................................................................................1730 1.12.23.3 Counters Related to the Number of Times that UL Throughput of HSUPA Services Within Each Range......................................................................................................................................................1739 1.12.23.4 Service Setup Duration on an ERACH or EFACH for Cell...................................................1746 1.12.24 Measurement of CS RAB assignment setup per cell(RAB.EstabCS.Cell).....................................1749 1.12.24.1 Number of CS RAB Setup Requests for Different Services..................................................1758 1.12.24.2 Number of Successful CS RAB Establishments in the Cell for Different Services...............1762 1.12.24.3 Number of RAB Setup Attempts for CS HSPA Voice Services............................................1766 1.12.24.4 Number of Successful RAB Setups for CS Conversational Services....................................1768 1.12.24.5 Number of RAB Setup Attempts for VP Services when VP Call Is Limited........................1769 1.12.24.6 Number of CS Over HSPA in a Cell......................................................................................1770 1.12.24.7 Number of Queuing Attempts Due to Insufficient Resource in the CS RAB Assignment Establishment Procedure........................................................................................................................1771 1.12.24.8 Average Duration of a CS Queuing in the RAB Establishment Procedure............................1772 1.12.24.9 Number of Successful CS Establishment After Queuing.......................................................1773 1.12.24.10 Number of CS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell............................................................................1775 1.12.24.11 Number of Successful CS Service Setups Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell............................................................................1777 1.12.25 Measurement of PS RAB assignment setup per cell(RAB.EstabPS.Cell)......................................1780 1.12.25.1 Number of PS RAB Setup Requests for Different Services...................................................1785 1.12.25.2 Number of PS RABs Successfully Set Up in a Cell for Different Services...........................1788 1.12.25.3 Number of PS RABs Set Up Successfully at 0 Kbit/s............................................................1790 1.12.25.4 Number of Queuing Attempts Due to Insufficient Resource in the PS RAB Assignment Establishment Procedure........................................................................................................................1793 1.12.25.5 Average Duration of a PS Queuing in the RAB Establishment Procedure............................1795 1.12.25.6 Number of Successful PS Establishment After Queuing.......................................................1796 1.12.25.7 Number of PS RAB Setup Requests for Platinum UEs Performing Conversational Services for Cell..........................................................................................................................................................1797 1.12.25.8 Number of PS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell.................................................................................................1799 1.12.25.9 Number of Successful PS Service Setups Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell............................................................................1801 1.12.26 Measurement of CS RAB assignment failure per cell(RAB.EstFailCs.Cell)..................................1804 1.12.26.1 Number of CS RABs Unsuccessfully Established due to Congestion...................................1809 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxiv
Contents
1.12.26.2 Number of Failed CS RABs due to Radio Network Layer Cause..........................................1812 1.12.26.3 Number of CS RABs Unsuccessfully Established due to Transport Network Layer Cause ................................................................................................................................................................1813 1.12.26.4 Number of CS RABs Unsuccessfully Established due to Different Reasons of UE During the RB Setup Procedure for Cell.........................................................................................................................1815 1.12.26.5 Number of Failed CS RAB Establishments Due to Radio Link Configuration Failure.........1819 1.12.26.6 Number of Failed CS RAB Establishments Due to Uu Interface Configuration Failure ................................................................................................................................................................1822 1.12.26.7 Number of Failed CS RABs due to Unsupported Capabilities (Cell)....................................1824 1.12.27 Measurement of PS RAB assignment failure per cell(RAB.EstFailPs.Cell)..................................1825 1.12.27.1 Number of PS RABs Unsuccessfully Established due to Radio Network Layer Cause for Cell ................................................................................................................................................................1831 1.12.27.2 Number of PS RABs Unsuccessfully Established due to Transport Network Layer Cause ................................................................................................................................................................1833 1.12.27.3 Number of Failed PS RABs due to different reasons of UE During the RB Setup Procedure for cell..........................................................................................................................................................1834 1.12.27.4 Number of Failed PS RAB Establishments Due to Radio Link Configuration Failure.........1838 1.12.27.5 Number of Failed PS RAB Establishments Due to Uu Interface Configuration Failure ................................................................................................................................................................1841 1.12.27.6 Number of Failed PS RABs due to Unsupported Capabilities (Cell).....................................1843 1.12.27.7 Number of PS RABs Unsuccessfully Established due to Congestion....................................1844 1.12.27.8 Number of PS Free RAB Setup Failures due to DL Power Resource Congestion for Cell ................................................................................................................................................................1848 1.12.28 Measurement of CS RAB assignment modification per cell(RAB.ModCs.Cell)...........................1849 1.12.28.1 Number of Failed CS RAB Modifications Due to Transport Network Layer Cause.............1851 1.12.28.2 Counters Related to the Number of CS RAB Modification Requests....................................1852 1.12.28.3 Counters Related to the Number of Successful CS RAB Modifications...............................1853 1.12.28.4 Number of Failed CS RAB Modifications Due to Radio Network Layer Cause...................1855 1.12.29 Measurement of PS RAB assignment modification per cell(RAB.ModPs.Cell)............................1856 1.12.29.1 Number of Failed PS RAB Modifications Due to Iu Transport Connection Failure.............1858 1.12.29.2 Number of PS RAB Modification Requests...........................................................................1859 1.12.29.3 Number of Successful PS RAB Modifications.......................................................................1861 1.12.29.4 Number of Failed PS RAB Modifications Due to Radio Network Fault...............................1863 1.12.30 Measurement of multi-RAB service per cell(RAB.MultiRab.Cell)................................................1864 1.12.30.1 Mean Number of Single-RAB UEs Occupy the Codes with Different Spreading Factors ................................................................................................................................................................1870 1.12.30.2 Mean Number of Multi-RAB UEs Occupy the Codes with Different Spreading Factors ................................................................................................................................................................1871 1.12.30.3 Max Count of SF which has been occupied...........................................................................1873 1.12.30.4 Mean Throughput of a Single HSDPA MAC-d Flow in the Case of Multi-RAB Services for Cell ................................................................................................................................................................1874 1.12.30.5 Mean Throughput of a Single HSUPA MAC-d Flow in the Case of Multi-RAB Services for Cell ................................................................................................................................................................1875 1.12.30.6 Mean Downlink Throughput of a Single PS R99 RB in the Case of Multi-RAB Services for Cell ................................................................................................................................................................1876
Issue 01 (2013-05-04)
xxxv
Contents
1.12.30.7 Mean Uplink Throughput of a Single PS R99 RB in the Case of Multi-RAB Services for Cell ................................................................................................................................................................1878 1.12.30.8 Number of CS+PS Combined Service Setup Requests for Cell.............................................1879 1.12.30.9 Number of Successful CS+PS Combined Service Setups for Cell........................................1881 1.12.30.10 Number of Normal CS Service Releases of CS+PS Combined Services for Cell...............1884 1.12.30.11 Number of Abnormal PS Service Releases of PS+PS Combined Services for Cell............1887 1.12.30.12 Number of Abnormal CS Service Releases During PS Service Setup for Cell....................1891 1.12.30.13 Number of Abnormal CS Service Releases During PS Service Release for Cell................1893 1.12.30.14 Number of Normal PS Service Releases of CS+PS Combined Services for Cell................1896 1.12.30.15 Number of Abnormal PS Service Releases of CS+PS Combined Services for Cell............1899 1.12.30.16 Number of State Transition Attempts from CELL_PCH or URA_PCH to CELL_DCH with the Cause Value of CS Service for Cell.......................................................................................................1901 1.12.30.17 Number of Successful State Transitions from CELL_PCH or URA_PCH to CELL_DCH with the Cause Value of CS Service for Cell.................................................................................................1903 1.12.30.18 Number of Abnormal PS Service Releases in the Case of Multi-RAB Services for Cell during an inter-RAT handover( PS Resume Timer Expiry)..............................................................................1904 1.12.31 Measurement of RAB release per cell(RAB.RelAbnormal.Cell)....................................................1906 1.12.31.1 Number of CS RABs Abnormally Released Due to Different RF Causes for Cell...............1921 1.12.31.2 Number of CS RABs Abnormally Released for Different Services.......................................1925 1.12.31.3 Number of PS RABs Abnormally Released for Different Services.......................................1928 1.12.31.4 Number of CS RABs Normally Released for Different Services...........................................1932 1.12.31.5 Number of PS RABs Normally Released for Different Services...........................................1934 1.12.31.6 Number of CS RABs Abnormally Released for Cell.............................................................1937 1.12.31.7 Number of CS RABs Normally Released for Cell.................................................................1940 1.12.31.8 Number of PS RABs Abnormally Released for Cell.............................................................1942 1.12.31.9 Number of PS RABs Normally Released for Cell.................................................................1945 1.12.31.10 Number of CS AMRWB RABs Abnormally Released........................................................1947 1.12.31.11 Number of CS RABs Abnormally Released Triggered by Different Causes.......................1953 1.12.31.12 Number of CS AMR RABs Abnormally Released..............................................................1958 1.12.31.13 Number of PS RABs Abnormally Released Due to Different RF Causes for Cell..............1962 1.12.31.14 Number of PS RABs Abnormally Released Due to Different Causes.................................1966 1.12.31.15 Number of PS BE RABs Beared on HSPA Released due to Cell Congestion.....................1970 1.12.31.16 Number of PS RABs Normally Released According to Different Channel-beared Type ................................................................................................................................................................1973 1.12.31.17 Number of PS RABs Normally Released due to UE Signaling Connection Release..........1975 1.12.31.18 Number of CS over HSPA RABs Normal Released for Cell...............................................1977 1.12.31.19 Number of CS VP RABs Released Due to VP Forbiddance for Cell..................................1979 1.12.31.20 Times of PS RAB of 0kbit/s released for failed to rate up...................................................1981 1.12.31.21 Number of AMRWB RABs Normally Released for Cell....................................................1983 1.12.31.22 Number of CS RABs Normally Released Due to Uplink Signaling Connection Release ................................................................................................................................................................1988 1.12.31.23 Number of CS RABs Abnormally Released due to RF Failure for Different Service.........1989 1.12.31.24 Number of RABs Abnormally Released for PTT Services..................................................1992 1.12.31.25 Number of RABs Normally Released for PTT Services......................................................1995 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxvi
Contents
1.12.31.26 Number of PS R99 RABs Abnormally Released Due to RF Failure...................................1997 1.12.31.27 Number of PS RABs Abnormally Released According to Different Channel-beared Type ................................................................................................................................................................2000 1.12.31.28 Number of Normally Released PS RABs that Are in CELL_PCH or URA_PCH State for Cell ................................................................................................................................................................2003 1.12.31.29 Number of call drops During the F2P State Transition for Cell...........................................2005 1.12.31.30 Number of Abnormally Released PS RABs that Are in CELL_PCH or URA_PCH State for Cell ................................................................................................................................................................2007 1.12.31.31 Number of RABs Abnormally Released for PS Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell..............................................................................2010 1.12.31.32 Number of RABs Abnormally Released Due to Security Mode Procedure Failure............2014 1.12.31.33 Number of Released RABs Triggered by the Second RRC CONNECTION REQUEST Message from the Same UE in the CS Domain.....................................................................................................2017 1.12.31.34 Number of RAB Releases Triggered by the Second RRC CONNECTION REQUEST Message from the Same UE in the PS Domain.....................................................................................................2018 1.12.31.35 Number of RAB Releases Triggered by the Second RRC CONNECTION REQUEST Message from the Same UE in the PS Domain in Common Channel-related Scenarios for Cell.........................2019 1.12.31.36 Number of Released PS RABs due to Network Optimization for Cell................................2021 1.12.31.37 Number of Abnormally Released PS RABs Triggered by CN for Cell...............................2023 1.12.31.38 Number of Released CS RABs due to Network Optimization for Cell...............................2025 1.12.31.39 Number of Abnormally Released PS RABs Triggered by RNC for Cell............................2028 1.12.31.40 Number of Abnormally Released CS RABs Triggered by CN for Cell...............................2031 1.12.32 Measurement of CS RAB release per cell(RAB.RelCs.Cell)..........................................................2033 1.12.32.1 Number of CS RABs Released Due to Different Causes in RAB Assignment for Cell ................................................................................................................................................................2035 1.12.32.2 Number of Abnormally Released CS RABs Triggered by CN..............................................2037 1.12.32.3 Number of CS RABs Released in RAB Assignment for Cell................................................2039 1.12.33 Measurement of PS RAB release per cell(RAB.RelPs.Cell)...........................................................2040 1.12.33.1 Number of PS RABs Released by RAB ASSIGNMENT REQUEST for Different Cause ................................................................................................................................................................2042 1.12.33.2 Number of PS RAB Releases Triggered by CN.....................................................................2044 1.12.33.3 Number of PS RAB Release Attempts by RAB ASSIGNMENT REQUEST.......................2046 1.12.34 Measurement of RB Procedure per cell(RB.Cell)...........................................................................2047 1.12.34.1 Number of RB Setup Attempts...............................................................................................2067 1.12.34.2 Number of Successful RB Setups...........................................................................................2069 1.12.34.3 Counters Related to the Number of Failed RB Setups for Different Causes..........................2070 1.12.34.4 Number of RB Reconfiguration Attempts..............................................................................2073 1.12.34.5 Number of Successful RB Reconfigurations..........................................................................2074 1.12.34.6 Counters Related to the Number of Failed RB Reconfigurations for Different Causes ................................................................................................................................................................2075 1.12.34.7 Number of AMR Users with Different UL and DL Rates for Cell........................................2078 1.12.34.8 Average Number of CS Conversational or Streaming Service RBs for Cell.........................2085 1.12.34.9 Number of RBs for PS R99 Services with various Uplink and Downlink Rates for Cell ................................................................................................................................................................2086 1.12.34.10 Number of RB Setup Attempts for Outgoing Inter-Frequency Directed Retry....................2094 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxvii
Contents
1.12.34.11 Number of Successful RB Setup for Outgoing Inter-Frequency Directed Retry.................2095 1.12.34.12 Number of RB Setup Attempts for Incoming Inter-Frequency Directed Retry...................2097 1.12.34.13 Number of Successful RB Setup for Incoming Inter-Frequency Directed Retry.................2098 1.12.34.14 Number of RB Reconfiguration Attempts for Outgoing Inter-Frequency Directed Retry ................................................................................................................................................................2100 1.12.34.15 Number of Successful RB Reconfiguration for Outgoing Inter-Frequency Directed Retry ................................................................................................................................................................2101 1.12.34.16 Number of RB Reconfiguration Attempts for Incoming Inter-Frequency Directed Retry ................................................................................................................................................................2102 1.12.34.17 Number of Successful RB Reconfiguration for Incoming Inter-Frequency Directed Retry ................................................................................................................................................................2104 1.12.34.18 Number of Outgoing or Incoming DCH-to-HSDPA or DCH-to-HSUPA Directed Retry Attempts..................................................................................................................................................2105 1.12.34.19 Number of Successful Outgoing or Incoming DCH-to-HSDPA or DCH-to-HSUPA Directed Retry for Cell..........................................................................................................................................2108 1.12.34.20 Number of Successful Directed Retry Attempts Based on Inter-Frequency Measurement for Cell ................................................................................................................................................................2110 1.12.34.21 Number of Directed Retry Attempts Based on Inter-Frequency Measurement for Cell ................................................................................................................................................................2113 1.12.34.22 Number of Times that PS Rate Downgrades to 0 Kbit/s......................................................2115 1.12.34.23 Average Number of PS Conversation RBs on EDCH or HS-DSCH for Cell......................2115 1.12.34.24 Number of Outgoing DRD Attempts through Physical Channel Reconfiguration(Cell) ................................................................................................................................................................2116 1.12.34.25 Number of Successful Outgoing DRDs through Physical Channel Reconfiguration(Cell) ................................................................................................................................................................2117 1.12.34.26 Number of Incoming DRD Attempts through Physical Channel Reconfiguration (Cell) ................................................................................................................................................................2119 1.12.34.27 Number of Successful Incoming DRDs through Physical Channel Reconfiguration (Cell) ................................................................................................................................................................2120 1.12.34.28 Number of RB Setup Attempts After the RB Setup DRD Rollback....................................2122 1.12.34.29 Number of successful RB Setups After the RB Setup DRD Rollback.................................2123 1.12.34.30 Number of RB Reconfiguration Attempts After the RB Reconfiguration DRD Rollback ................................................................................................................................................................2125 1.12.34.31 Number of Successful RB Reconfigurations After the RB Reconfiguration DRD Rollback ................................................................................................................................................................2126 1.12.34.32 Number of Physical Channel Reconfiguration Attempts After the Physical Channel Reconfiguration DRD Rollback.............................................................................................................2128 1.12.34.33 Number of Successful Physical Channel Reconfigurations After the Physical Channel Reconfiguration DRD Rollback.............................................................................................................2129 1.12.34.34 Number of Outgoing or Incoming FACH-to-HSDPA or FACH-HSUPA Directed Retry Attempts for Cell....................................................................................................................................2131 1.12.34.35 Number of Successful Outgoing or Incoming FACH-to-HSDPA or FACH-HSUPA Directed Retry Attempts for Cell..........................................................................................................................2133 1.12.34.36 Number of CELL_FACH to CELL_PCH Transition Attempts by Physical Channel Reconfiguration for Cell.........................................................................................................................2136 1.12.34.37 Number of SuccessfulCELL_FACH to CELL_PCH Transitions by Physical Channel Reconfiguration for Cell.........................................................................................................................2137 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxviii
Contents
1.12.34.38 Number of Outgoing or Incoming Inter-Frequency DRD Attempts Triggered by Multiband Directed Retry Based on UE Location for Cell......................................................................................2139 1.12.34.39 Number of Successful Incoming Inter-Frequency DRDs Triggered by Multiband Directed Retry Based on UE Location for a Cell............................................................................................................2141 1.12.34.40 Number of Periodic Inter-Frequency Ingoing Directed Retry Attempts based on Measurement for Cell....................................................................................................................................................2144 1.12.34.41 Number of Successful Periodic Inter-Frequency Ingoing Directed Retry Attempts based on Measurement for Cell.............................................................................................................................2147 1.12.35 Reserved counter for cell(RESERVE.Cell).....................................................................................2149 1.12.35.1 Reserved counters for cell......................................................................................................2151 1.12.36 Measurement related to RLC per cell(RLC.Cell)............................................................................2153 1.12.36.1 Number of Downlink Service PDUs Retransmitted on AM RLC (L2 Enhancement)...........2155 1.12.36.2 Number of Downlink Service PDUs Sent on AM RLC.........................................................2156 1.12.36.3 Number of Downlink Signaling PDUs Sent on AM RLC......................................................2157 1.12.36.4 Number of Downlink Service PDUs Retransmitted on AM RLC..........................................2158 1.12.36.5 Number of Downlink Signaling PDUs Retransmitted on AM RLC......................................2159 1.12.36.6 Number of Downlink Service PDUs Discarded on AM RLC................................................2160 1.12.36.7 Number of Downlink Signaling PDUs Discarded on AM RLC............................................2161 1.12.37 RRC connection release measurement per cell(RRC.Rel.Cell).......................................................2162 1.12.37.1 Counters Related to the Number of RRC Connection Releases on DCCH due to Different Causes ................................................................................................................................................................2164 1.12.37.2 Counters Related to the Number of RRC Connection Releases on CCCH due to Different Causes ................................................................................................................................................................2167 1.12.37.3 Number of RRC Connection Releases due to Cell Update Failure in the Case of RL Failure ................................................................................................................................................................2170 1.12.37.4 Number of RRCs Released due to PS Data session end.........................................................2171 1.12.38 RRC connection setup measurement per cell(RRC.Setup.Cell)......................................................2172 1.12.38.1 Number of RRC Connection Setup Attempts with DRD out.................................................2195 1.12.38.2 Number of Successful RRC Connection Setups with DRD Out............................................2196 1.12.38.3 Number of RRC Connection Setup Attempts with DRD in...................................................2198 1.12.38.4 Counters Related to Duration of RRC Connection Setup on CELL_DCH............................2199 1.12.38.5 Counters Related to the Number of RRC Connection Requests for Various Reasons...........2202 1.12.38.6 Counters Related to the Number of Successful RRC Connection Setups for Various Reasons ................................................................................................................................................................2208 1.12.38.7 Number of RRC Connection Setup Messages Sent from RNC to UE...................................2213 1.12.38.8 Counters Related to the Number of Successful RRC Connection Setups..............................2215 1.12.38.9 Counters Related to the Number of Processed RRC Connection Requests...........................2217 1.12.38.10 Number of Successful RRC Connection Setups with Repeated RRC Connection Request Messages from UE..................................................................................................................................2219 1.12.38.11 Number of Automatic DSACs Triggered by Congestion on Iu Interface............................2222 1.12.38.12 Number of RRC Connection Requests sent by the UE for cell............................................2223 1.12.38.13 Number of PTT UEs with RRC Connection State of CELL_FACH...................................2225 1.12.38.14 Number of PTT UEs with RRC Connection State of CELL_DCH.....................................2225 1.12.38.15 Duration of RRC Establishment Process on FACH for Cell................................................2226 1.12.38.16 Number of PTT UEs in CELL_PCH State...........................................................................2229 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxix
Contents
1.12.38.17 Number of Retransmitted RRC Connection Setup Requests for Cell..................................2229 1.12.38.18 The average Ec/N0 at each propagation delay range in a cell..............................................2235 1.12.38.19 Number of RRC Connection Establishment Requests that propagation delay falls into different value ranges in a cell..............................................................................................................................2239 1.12.38.20 Number of Received RRC CONNECTION REQUESTS for CS Services in a Cell...........2243 1.12.38.21 Number of RRC CONNECTION REQUESTS Under Flow Control for Cell.....................2244 1.12.38.22 Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control for Cell..........................................................................................................................................................2245 1.12.38.23 Number of Cell Updates Under Flow Control Triggered by High CPU Usage for Cell......2247 1.12.38.24 Number of RRC Connection Setup Requests for Cell (PS Domain)...................................2248 1.12.38.25 Number of RRC Connection Setup Requests for Cell (CS Domain)...................................2249 1.12.38.26 Number of Rejected RRC Connection Setup Requests for CS Voice Services During Flow Control Caused by Interface-Board CPU Overload for Cell..................................................................2251 1.12.38.27 Number of Rejected RRC Connection Setup Requests During Flow Control Caused by InterfaceBoard CPU Overload for Cell................................................................................................................2252 1.12.38.28 Number of Rejected RRC Connection Setup Requests During Flow Control Caused by FACH Congestion for Cell.................................................................................................................................2253 1.12.38.29 Number of Rejected RRC Connection Setup Requests for CS Voice Services During E2E Flow Control Phase 1 for Cell.........................................................................................................................2254 1.12.38.30 Number of Rejected RRC Connection Setup Requests During E2E Flow Control Phase 1 for Cell..........................................................................................................................................................2254 1.12.38.31 Number of RRC CONNECTION REQUESTS in a Cell Under Cell Dynamic CAPS Flow Control....................................................................................................................................................2255 1.12.38.32 Number of RRC CONNECTION REQUESTS for CS Services in a Cell Under Cell Dynamic CAPS Flow Control................................................................................................................................2256 1.12.38.33 Number of RRC Connection Setup Requests that carried System Information Container Stored Indication for CS services.......................................................................................................................2257 1.12.38.34 Number of Successful RRC Connection Setups for CS services (RRC Connection Setup Requests that carried System Information Container Stored Indication)...............................................2259 1.12.38.35 Number of RRC Connection Setup Requests that carried System Information Container Stored Indication for PS services.......................................................................................................................2260 1.12.38.36 Number of Successful RRC Connection Setups for PS services (RRC Connection Setup Requests that carried System Information Container Stored Indication)...............................................2262 1.12.38.37 Number of RRC Connection Setup Requests for Platinum UEs Performing Conversational Services for Cell.....................................................................................................................................2263 1.12.38.38 Number of RRC Connection Setup Requests for Platinum UEs Performing Services for Cell ................................................................................................................................................................2264 1.12.38.39 Number of Successful RRC Connection Setups for Platinum UEs Performing Conversational Services for Cell.....................................................................................................................................2266 1.12.38.40 Number of Successful RRC Connection Setups for Platinum UEs for Cell........................2267 1.12.39 RRC connection reject measurement per cell(RRC.SetupFail.Cell)...............................................2268 1.12.39.1 Number of RRC Connection Rejects (RRC Redirection Triggered by Access Failure)........2273 1.12.39.2 Number of RRC Connection Rejects during redirection between inter-RAT cells................2275 1.12.39.3 Number of RRC Connection Rejects Due to Service-based RRC Redirection......................2276 1.12.39.4 Number of RRC Connection Rejects Due to Congestion.......................................................2278 1.12.39.5 Number of RRC Connection Rejects (Radio Resource Congestion).....................................2279 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xl
Contents
1.12.39.6 Number of RRC Connection Rejects Due to Timeout of RRC CONNECT SETUP COMPLETE ................................................................................................................................................................2282 1.12.39.7 Number of RRC Connection Rejects Due to Radio Link Setup Failure................................2284 1.12.39.8 Number of RRC Connection Rejects (Transmission Setup Failure on Iub Interface )..........2286 1.12.39.9 Number of RRC Connection Rejects......................................................................................2288 1.12.39.10 Number of Distance-Based RRC Redirections for Cell.......................................................2289 1.12.39.11 Number of Discarded RRC Connection Requests Due to Various Flow Control Functions ................................................................................................................................................................2291 1.12.39.12 Number of RRC Connection Requests of Different Priorities Discarded During RAN Integrated Flow Control for Cell.............................................................................................................................2292 1.12.39.13 Number of RRC Connection Rejects Due to NodeB Resource Unavailable.......................2293 1.12.39.14 Number of Outgoing Macro & Micro Joint Inter-frequency Redirections...........................2294 1.12.40 RRC state measurement<Cell>(RRC.State.Cell)............................................................................2296 1.12.40.1 Counters Related to the Number of UEs in Different RRC Connection States......................2297 1.12.41 UE Capability Measurement per cell(RRC.UECapab.Cell)............................................................2298 1.12.41.1 Number of Successful RRC Connection Setups (Including All the HS-DSCH Physical Layer Categories)..............................................................................................................................................2302 1.12.41.2 Number of Successful RRC Connection Setups for Cell (Including All the E-DCH Physical Layer Categories)..............................................................................................................................................2306 1.12.42 Cell TX and RX Power Measurement per cell(RTWPTCP.Cell)...................................................2309 1.12.42.1 Received Total Wideband Power for cell...............................................................................2311 1.12.42.2 Transmitted Power of Carrier for Cell....................................................................................2313 1.12.42.3 Transmitted Power of Non-HSDPA Carrier for Cell.............................................................2315 1.12.42.4 Power Required by HS-DSCH for Cell..................................................................................2317 1.12.42.5 Received Scheduled E-DCH Power Share in the Measurement Period for Cell....................2319 1.12.42.6 Average Power Required for Free HSDPA Users for Cell.....................................................2321 1.12.42.7 Power Required by 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell..............................2322 1.12.42.8 DL Transmit Power of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell........................2325 1.12.43 Soft Handover Measurement per cell(SHO.Cell)............................................................................2327 1.12.43.1 Number of Radio Link Addition Attempts in Softer Handover.............................................2333 1.12.43.2 Number of Successful Radio Link Additions in Softer Handover.........................................2334 1.12.43.3 Counters Related to the Number of Failed Radio Link Additions in Softer Handover due to Different Causes.....................................................................................................................................2335 1.12.43.4 Number of Failed Radio Link Additions in Softer Handover due to UE No Response.........2337 1.12.43.5 Number of Radio Link Deletion Attempts in Softer Handover..............................................2338 1.12.43.6 Number of Successful Radio Link Deletions in Softer Handover..........................................2340 1.12.43.7 Number of Radio Link Addition Attempts in Soft Handover................................................2341 1.12.43.8 Number of Successful Radio Link Additions in Soft Handover............................................2343 1.12.43.9 Counters Related to the Number of Failed Radio Link Additions in Soft Handover due to Different Causes.....................................................................................................................................................2345 1.12.43.10 Number of Failed Radio Link Additions in Soft Handover due to UE No Response..........2346 1.12.43.11 Number of Radio Link Deletion Attempts in Soft Handover...............................................2348 1.12.43.12 Number of Successful Radio Link Deletions in Soft Handover...........................................2349 1.12.43.13 Number of Soft Handover Attempts with only Signaling Connection.................................2351 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xli
Contents
1.12.43.14 Number of Successful Soft Handovers with only Signaling Connection.............................2352 1.12.43.15 Number of Soft Handover Decisions for Radio Link Addition Initiated by RNC...............2353 1.12.43.16 These counters provide the number of soft handover attempts in different service types in the target cell................................................................................................................................................2355 1.12.43.17 Counters Related to the Number of Successful Soft Handovers in Different Service Types ................................................................................................................................................................2356 1.12.43.18 Mean Number of UEs with One Radio Link........................................................................ 2358 1.12.43.19 Mean Number of UEs with Two Radio Links......................................................................2359 1.12.43.20 Mean Number of UEs with Three Radio Links....................................................................2359 1.12.43.21 Mean Number of UEs with Four Radio Links.....................................................................2360 1.12.43.22 Mean Number of UEs with Five Radio Links...................................................................... 2361 1.12.43.23 Mean Number of UEs with Six Radio Links........................................................................2362 1.12.43.24 Number of Soft Handover Attempts for PS Services for Cell..............................................2363 1.12.43.25 Number of Successful Soft Handovers for PS Services for Cell..........................................2364 1.12.44 Measurement related to SIRTARGET per cell(SIR.Cell)...............................................................2365 1.12.44.1 SIR Target Measurement for Different Services.................................................................... 2367 1.12.45 Measurement related to SPI per cell(SPI.Cell)................................................................................2371 1.12.45.1 Number of Times of Downlink Throughput of BE Services with SPI Set to 8 with a Certain Range in a Measurement Period for HSDPA Cell.............................................................................................2392 1.12.45.2 Number of Times of Downlink Throughput of BE Services with SPI Set to 5 with a Certain Range in a Measurement Period for HSDPA Cell.............................................................................................2396 1.12.45.3 Number of Times of Downlink Throughput of BE Services with SPI Set to 2 with a Certain Range in a Measurement Period for HSDPA Cell.............................................................................................2399 1.12.45.4 Number of Times of Uplink Throughput of BE Services with SPI Set to 8 with a Certain Range in a Measurement Period for HSUPA Cell.............................................................................................2403 1.12.45.5 Number of Times of Uplink Throughput of BE Services with SPI Set to 5 with a Certain Range in a Measurement Period for HSUPA Cell.............................................................................................2406 1.12.45.6 Number of Times of Uplink Throughput of BE Services with SPI Set to 2 with a Certain Range in a Measurement Period for HSUPA Cell.............................................................................................2408 1.12.45.7 Number of Bytes Sent on Downlink HSDPA Mac-d flow of BE Services with SPI Setting to Different Values.....................................................................................................................................2411 1.12.45.8 Number of Bytes Received on Uplink HSUPA Mac-d flow of BE Services with SPI Setting to Different Values.....................................................................................................................................2413 1.12.45.9 Mean Downlink Throughput of HSDPA Mac-d flow of BE Services with SPI Setting to Different Values.....................................................................................................................................................2415 1.12.45.10 Mean Downlink Throughput of HSUPA Mac-d flow of BE Services with SPI Setting to Different Values.....................................................................................................................................................2418 1.12.46 Measurement related to throughput and data rate per cell(THRUPUT.Cell)..................................2422 1.12.46.1 Average DL Rate of 64 Kbit/s CS Conversational Services..................................................2434 1.12.46.2 DL Traffic Volume of 64 Kbit/s CS Conversational Services...............................................2435 1.12.46.3 Average DL Rate of 57.6 Kbit/s CS Streaming Services.......................................................2436 1.12.46.4 DL Traffic Volume of 57.6 Kbit/s CS Streaming Services.................................................... 2437 1.12.46.5 Counters Related to the Average DL Rates of Different PS R99 Background Services........2438 1.12.46.6 Counters Related to the DL Traffic Volumes of Different PS R99 Background Services ................................................................................................................................................................2441 1.12.46.7 Counters Related to the Average DL Rates of Different PS R99 Interactive Services..........2442 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlii
Contents
1.12.46.8 Counters Related to the DL Traffic Volumes of Different PS R99 Interactive Services.......2445 1.12.46.9 Counters Related to the Average DL Rates of Different PS R99 Streaming Services...........2447 1.12.46.10 Counters Related to the DL Traffic Volumes of Different PS R99 Streaming Services ................................................................................................................................................................2449 1.12.46.11 Counters Related to the Average UL Rates of Different PS R99 Background Services ................................................................................................................................................................2451 1.12.46.12 Counters Related to the UL Traffic Volumes of Different PS R99 Background Services ................................................................................................................................................................2453 1.12.46.13 Counters Related to the Average UL Rates of Different PS R99 Interactive Services........2455 1.12.46.14 Counters Related to the UL Traffic Volumes of Different PS R99 Interactive Services ................................................................................................................................................................2458 1.12.46.15 Counters Related to the Average UL Rates of Different PS R99 Streaming Services.........2459 1.12.46.16 Counters Related to the UL Traffic Volumes of Different PS R99 Streaming Services ................................................................................................................................................................2461 1.12.46.17 Average UL Rate of Signaling on DCCH............................................................................2462 1.12.46.18 UL Traffic Volume of Signaling on DCCH.........................................................................2463 1.12.46.19 Average DL Rate of Signaling on DCCH............................................................................2464 1.12.46.20 DL Traffic Volume of Signaling on DCCH.........................................................................2465 1.12.46.21 UL Traffic Volume of AMR Services for Best Cell............................................................2465 1.12.46.22 DL Traffic Volume of AMR Services for Best Cell............................................................2466 1.12.46.23 UL Traffic Volume of VP Services for Best Cell................................................................2467 1.12.46.24 DL Traffic Volume of VP Services for Best Cell................................................................2468 1.12.46.25 UL Traffic of BE Services with Different PS Data Rates for Best Cell...............................2468 1.12.46.26 DL Traffic of BE Services with Different PS Data Rates for Best Cell...............................2470 1.12.46.27 Mean Number of AMR service UEs in the best cell............................................................2471 1.12.46.28 Mean Number of VP service UEs in the best cell................................................................2472 1.12.46.29 Average Throughput of PTM MBMS Services....................................................................2472 1.12.46.30 Average Throughput of PTP MBMS Services.....................................................................2473 1.12.46.31 Average DL Bit Rate of PS Conversational Service............................................................2474 1.12.46.32 DL Throughput of PS Conversational Service.....................................................................2475 1.12.46.33 Average UL Bit Rate of PS Conversational Service............................................................2476 1.12.46.34 UL Throughput of PS Conversational Service.....................................................................2477 1.12.46.35 Sum of Sampled Downlink BE Throughput of UEs with PS Services over DCHs.............2477 1.12.46.36 Number of Times Downlink BE Throughput of UEs with PS Services over DCHs Is Sampled ................................................................................................................................................................2478 1.12.46.37 Sum of Sampled Uplink BE Throughput of UEs with PS Services over DCHs..................2479 1.12.46.38 Number of Times Uplink BE Throughput of UEs with PS Services over DCHs Is Sampled ................................................................................................................................................................2480 1.12.46.39 Number of Erlangs for AMR Services for Cell....................................................................2481 1.12.47 Traffic Measurement per cell(TRFFIC.Cell)...................................................................................2482 1.12.47.1 DL Signaling Rate over BCCH on Iub Interface....................................................................2484 1.12.47.2 DL Signaling Rate over CCCH on Iub Interface....................................................................2485 1.12.47.3 UL Signaling Rate over CCCH on Iub Interface....................................................................2486 1.12.47.4 UL Service Traffic over DCH on Iub Interface for DRNC....................................................2487 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xliii
Contents
1.12.47.5 DL Service Traffic over DCH on Iub Interface for DRNC....................................................2488 1.12.47.6 UL Signaling Traffic on Iub Interface....................................................................................2489 1.12.47.7 DL Signaling Traffic on Iub Interface....................................................................................2490 1.12.47.8 UL PS R99 Traffic on Iub Interface.......................................................................................2490 1.12.47.9 DL PS R99 Traffic on Iub Interface.......................................................................................2492 1.12.47.10 UL CS Traffic on Iub Interface............................................................................................2493 1.12.47.11 DL CS Traffic on Iub Interface............................................................................................2494 1.12.47.12 Traffic over RACH on Iub Interface....................................................................................2494 1.12.47.13 Traffic over FACH on Iub Interface.....................................................................................2495 1.12.47.14 Traffic over PCH on Iub Interface........................................................................................2496 1.12.47.15 Counters Related to the Bandwidth of Common Channels on Iub Interface for CRNC......2497 1.12.47.16 Bandwidth of Channel for MBMS Services.........................................................................2498 1.12.47.17 PS Traffic over RACH on Iub Interface...............................................................................2498 1.12.47.18 PS Traffic over FACH on Iub Interface...............................................................................2499 1.12.47.19 DL HSDPA Traffic on Iub Interface....................................................................................2500 1.12.47.20 UL HSUPA Traffic on Iub Interface....................................................................................2501 1.12.48 Measurement related to U2L Handover per cell(U2LTE.HO.Cell)................................................2502 1.12.48.1 Number of UMTS-to-LTE PS Handover Attempts Triggered by RNC for Cell...................2506 1.12.48.2 Number of Successful UMTS-to-LTE PS Handovers for Cell..............................................2507 1.12.48.3 Number of Failed UMTS-to-LTE PS Handovers Due to Iu Release Command Timeout for Cell ................................................................................................................................................................2509 1.12.48.4 Number of Failed UMTS-to-LTE PS Handovers Due to Different Causes for Cell..............2511 1.12.48.5 Number of Abnormally Terminated Outgoing UMTS-to-LTE PS Handovers for Cell.........2512 1.12.48.6 Number of Outgoing UMTS-to-LTE PS Handover Preparation Attempts for Cell...............2514 1.12.48.7 Number of Successful Preparations for Outgoing UMTS-to-LTE PS Handovers for Cell ................................................................................................................................................................2515 1.12.48.8 Number of Failed Preparations for Outgoing UMTS-to-LTE PS Handovers Due to Different Causes.....................................................................................................................................................2516 1.12.48.9 Number of Redirection to LTE Through RRC Connection Release for Cell.........................2519 1.12.48.10 Number of Preparation Attempts for Outgoing Coverage-triggered UMTS-to-LTE PS Handovers...............................................................................................................................................2521 1.12.48.11 Number of Successful Preparations for Outgoing Coverage-triggered UMTS-to-LTE PS Handovers...............................................................................................................................................2522 1.12.48.12 Number of UMTS to LTE Blind Redirections Through RRC Connection Release for Cell ................................................................................................................................................................2524 1.12.49 URA Update Measurement per cell(URAUPDATE.Cell)..............................................................2526 1.12.49.1 Number of URA Updates due to Periodic URA Update........................................................2526 1.12.49.2 Number of URA Updates due to Change of URA.................................................................2528 1.12.49.3 Number of Successful URA Updates due to Periodic URA Update......................................2529 1.12.49.4 Number of Successful URA Updates due to Change of URA...............................................2531 1.12.50 WLAN Measurement per cell(WLAN.Cell)...................................................................................2532 1.12.50.1 Number of Wi-Fi Access Attempts for Cell...........................................................................2533 1.12.50.2 Number of Wi-Fi Access Failures for Cell.............................................................................2535 1.13 Measurement between a cell and a neighbour interRAT cell Performance(UCELL_GCELL).................2536 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xliv
Contents
1.13.1 Measurement between a cell and a intRAT cell(IRATHO.Gcell).....................................................2536 1.13.1.1 Number of CS Inter-RAT Outgoing Handover Attempts Between Neighboring Cells...........2538 1.13.1.2 Number of Successful CS Inter-RAT Outgoing Handovers Between Neighboring Cells.......2540 1.13.1.3 Number of Failed CS Inter-RAT Outgoing Handovers Between Neighboring Cells..............2541 1.13.1.4 Number of PS Inter-RAT Outgoing Handover Attempts Between Neighboring Cells............2543 1.13.1.5 Number of Successful PS Inter-RAT Outgoing Handovers Between Neighboring Cells........2544 1.13.1.6 Number of Failed PS Inter-RAT Outgoing Handovers Between Neighboring Cells...............2546 1.13.1.7 Number of CS Outgoing Inter-RAT Handover Preparation Attempts Between Neighboring Cells ................................................................................................................................................................2547 1.13.1.8 Number of CS Outgoing Inter-RAT Handover Preparation Attempts According to Different Causes Between Neighboring Cells....................................................................................................................2549 1.13.1.9 Number of Successful CS Outgoing Inter-RAT Handover Preparations Between Neighboring Cells ................................................................................................................................................................2551 1.13.1.10 Number of Failed CS Outgoing Inter-RAT Handover Preparations According to Different Causes Between Neighboring Cells....................................................................................................................2552 1.14 Measurement between a cell and a neighbour UMTS cell(UCELL_NCELL)...........................................2554 1.14.1 Measurement between a cell and a UMTS cell(CELL.Ncell)...........................................................2554 1.14.1.1 Number of Successful Soft Handovers Between Neighboring Cells.......................................2561 1.14.1.2 Number of Soft Handover Attempts Between Neighboring Cells...........................................2562 1.14.1.3 Number of Failed Soft Handovers Between Neighboring Cells Due to No Response from UE ................................................................................................................................................................2564 1.14.1.4 Number of Hard Handover Attempts Between Neighboring Cells..........................................2565 1.14.1.5 Number of Successful Hard Handovers Between Neighboring Cells......................................2567 1.14.1.6 Number of Failed Hard Handovers Between Neighboring Cells Due to No Response from UE ................................................................................................................................................................2568 1.14.1.7 Number of RL Addition Attempts in Soft Handover Between Neighboring Cells..................2570 1.14.1.8 Number of Successful RL Additions in Soft Handover Between Neighboring Cells..............2571 1.14.1.9 Number of RL Deletion Attempts in Soft Handover Between Neighboring Cells..................2573 1.14.1.10 Number of Successful RL Deletions in Soft Handover Between Neighboring Cells............2574 1.14.1.11 Number of Hard Handover Attempts from HS-DSCH to HS-DSCH Between Neighboring Cells ................................................................................................................................................................2576 1.14.1.12 Number of Successful Hard Handovers from HS-DSCH to HS-DSCH Between Neighboring Cells........................................................................................................................................................2577 1.14.1.13 Number of HSDPA Serving Cell Change Attempts Between Neighboring Cells.................2579 1.14.1.14 Number of Successful HSDPA Serving Cell Changes Between Neighboring Cells.............2581 1.14.1.15 Number of CS Domain Outgoing Inter-Cell Hard Handover Attempts Between Neighboring Cells ................................................................................................................................................................2582 1.14.1.16 Number of Successful CS Domain Outgoing Hard Handovers Between Neighboring Cells ................................................................................................................................................................2585 1.14.1.17 Number of Failed CS Domain Hard Handovers According to Different Causes Between Neighboring Cells...................................................................................................................................2587 1.14.1.18 Number of PS Domain Outgoing Inter-Cell Hard Handover Attempts Between Neighboring Cells ................................................................................................................................................................2591 1.14.1.19 Number of Successful PS Domain Outgoing Hard Handovers Between Neighboring Cells ................................................................................................................................................................2593
Issue 01 (2013-05-04)
xlv
Contents
1.14.1.20 Number of Failed PS Domain Hard Handovers According to Different Causes Between Neighboring Cells...................................................................................................................................2595 1.14.1.21 Number of Outgoing SRNS Relocation Executions with HHO Between Neighboring Cells ................................................................................................................................................................2599 1.14.1.22 Number of Successful Outgoing SRNS Relocations with HHO Between Neighboring Cells ................................................................................................................................................................2600 1.14.1.23 Number of Failed CS Domain Outgoing SRNS Relocation with HHO Preparations According to Different Causes Between Neighboring Cells........................................................................................2602 1.14.1.24 Number of Failed PS Domain Outgoing SRNS Relocation with HHO Preparations According to Different Causes Between Neighboring Cells........................................................................................2603 1.15 Measurement of UMTS DSP Performance(UDSP)...................................................................................2605 1.15.1 Measurement related to DSP performance(DSP)..............................................................................2605 1.15.1.1 Uplink PS Traffic Handled by the DSP....................................................................................2606 1.15.1.2 Downlink PS Traffic Handled by the DSP...............................................................................2607 1.15.1.3 Measurement of the DSP Usage in a Period.............................................................................2608
2 Transport Network Related Measurement.........................................................................2610

2.1 Measurement of AAL2PATH Performance(AAL2PATH)..........................................................................2627 2.1.1 AAL2 Path Measurement(AAL2PATH).............................................................................................2627 2.1.1.1 Number of Active AAL2 Connections to an Adjacent Node.....................................................2628 2.1.1.2 Counters Related to the Number of Congestions on the AAL2 Path.........................................2629 2.1.1.3 Counters Related to the Duration of Congestions on the AAL2 Path........................................2630 2.2 Measurement of AAL2PATH ATM Layer Performance(AAL2PATH_PVCLAYER)..............................2631 2.2.1 AAL2PATH ATM Layer Measurement(AAL2PATH.PVCLAYER)................................................2631 2.2.1.1 Counters Related to the Number of Cells Received, Transmitted or Dropped on an AAL2PATH Link ATM Layer....................................................................................................................................2634 2.2.1.2 Counters Related to the Number of Bytes Received or Transmitted on an AAL2PATH link ATM Layer.......................................................................................................................................................2635 2.3 Measurement of VCL PM on an AAL2 Path(AAL2PATH_VCLPM)........................................................2637 2.3.1 Measurement Related to VCL PM on an AAL2 Path(AAL2PATH.VCLPM)...................................2637 2.3.1.1 Number of VCL PM Cells on an AAL2 Path.............................................................................2640 2.3.1.2 Maximum Data Rate of VCL PM on an AAL2 Path.................................................................2641 2.3.1.3 VCL PM Cell Discard Rate on an AAL2 Path...........................................................................2642 2.3.1.4 Rate of Incorrectly Inserted VCL PM Cells on an AAL2 Path..................................................2643 2.3.1.5 Number of Error VCL PM Cell Blocks Failed BIP16 Check on an AAL2 Path.......................2644 2.4 Measurement of IP Transport Adjacent Node Connection Performance(ANI_IP)......................................2646 2.4.1 IP Transport Adjacent Node Connection Measurement(ANIIPCONN).............................................2646 2.4.1.1 Number of IP Connection Setup Requests Received by IP Transport Adjacent Node..............2647 2.4.1.2 Number of Successful IP Connections for IP Transport Adjacent Node...................................2648 2.4.1.3 Number of IP Connection Modifications...................................................................................2649 2.4.1.4 Number of Successful IP Connection Modifications for IP Transport Adjacent Node.............2650 2.4.2 IP Transport Adjacent Node Resource Operation Measurement(ANIIPTRM)..................................2651 2.4.2.1 Number of Requests for Resource Allocation on the IP Transport Adjacent Node...................2652 2.4.2.2 Number of Successful Resource Allocations on the IP Transport Adjacent Node....................2653 2.4.2.3 IP Path Forward Bandwidth Allocated to IP Transport Adjacent Node.....................................2654 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlvi
Contents
2.4.2.4 IP Path Backward Bandwidth Allocated to IP Transport Adjacent Node..................................2654 2.4.2.5 Number of Failed Resource Allocations Due to Insufficient Bandwidth on the IP Transport Adjacent Node........................................................................................................................................................2655 2.5 Measurement of QAAL2 Adjacent Node Performance(ANI_QAAL2).......................................................2656 2.5.1 QAAL2 Measurement(QAAL2)..........................................................................................................2657 2.5.1.1 Number of Resource Allocation Requests by QAAL2..............................................................2662 2.5.1.2 Number of Successful Resource Allocations by QAAL2..........................................................2663 2.5.1.3 Number of RLC messages received by the QAAL2..................................................................2663 2.5.1.4 Number of RLC messages sent by the QAAL2.........................................................................2665 2.5.1.5 Number of AAL2 Connection Establishment Requests Sent by the QAAL2............................2666 2.5.1.6 Number of AAL2 Connection Establishment Requests Received by the QAAL2....................2668 2.5.1.7 Number of AAL2 Connection Establishment Request Rejections Received by the QAAL2 ................................................................................................................................................................2669 2.5.1.8 Number of AAL2 Connection Establishment Confirmations Received by the QAAL2............2671 2.5.1.9 Number of AAL2 Connection Establishment Confirmations Sent by the QAAL2...................2672 2.5.1.10 Number of AAL2 Connection Establishment Rejections Sent by the QAAL2.......................2674 2.5.1.11 Number of AAL2 Connection Releases Initiated by QAAL2..................................................2675 2.5.1.12 Number of AAL2 Connection Releases Received by the QAAL2..........................................2677 2.5.1.13 Number of AAL2 Connection Confirmations Received by the QAAL2.................................2678 2.5.1.14 Number of AAL2 Connection Releases Confirmation Initiated by the QAAL2.....................2679 2.5.1.15 Number of AAL2 Connection Modification Request Rejections Received by the QAAL2 ................................................................................................................................................................2681 2.5.1.16 Number of AAL2 Connection Modification Rejections Sent by the QAAL2.........................2682 2.5.1.17 Number of AAL2 Connection Modification Requests Sent by the QAAL2............................2684 2.5.1.18 Number of AAL2 Connection Modification Requests Received by the QAAL2....................2684 2.5.1.19 Average Number of Active AAL2 Connections to an QAAL2 Adjacent Node......................2685 2.5.1.20 AAL2 Path Bandwidth Allocated to an Adjacent Node...........................................................2686 2.6 Measurement of Dual-Stack Transport Adjacent Node Performance(ANI_QAAL2_IP)............................2687 2.6.1 Dual-Stack Transport Adjacent Node IP Part Measurement(IPPART)..............................................2688 2.6.1.1 Number of IP Connection Setup Requests Received on Dual-Stack Transport Adjacent Node ................................................................................................................................................................2689 2.6.1.2 Number of Successful IP Connection Setups on the Dual-Stack Transport Adjacent Node ................................................................................................................................................................2690 2.6.1.3 Number of IP Connection Modifications on the Dual-Stack Transport Adjacent Node............2691 2.6.1.4 Number of Successful IP Connection Modifications on the Dual-Stack Transport Adjacent Node ................................................................................................................................................................2692 2.6.1.5 Number of IP Connection Releases on the Dual-Stack Transport Adjacent Node....................2693 2.6.1.6 Number of Active IP Connections on the Dual-Stack Transport Adjacent Node......................2694 2.6.1.7 IP Path Forward Bandwidth Allocated to a Dual-Stack Transport Adjacent Node...................2694 2.6.1.8 IP Path Backward Bandwidth Allocated to a Dual-Stack Transport Adjacent Node.................2695 2.6.2 Dual-Stack Transport Adjacent Node Measurement(QAAL2IP)........................................................2696 2.6.2.1 Number of Requests for Resource Allocations by Dual-Stack Transport Adjacent Node.........2697 2.6.2.2 Number of Successful Resource Allocations to Dual-Stack Transport Adjacent Node.............2698
Issue 01 (2013-05-04)
xlvii
Contents
2.6.2.3 Number of Failed Resource Allocations Due to Insufficient Bandwidth on the Dual-Stack Transport Adjacent Node........................................................................................................................................2699 2.6.3 Dual-Stack Transport Adjacent Node QAAL2 Part Measurement(QAAL2PART)...........................2700 2.6.3.1 Number of RLC messages received by the QAAL2 on Dual-Stack Adjacent Node.................2705 2.6.3.2 Number of RLC messages sent by the QAAL2 on Dual-Stack Adjacent Node........................2707 2.6.3.3 Number of AAL2 Connection Establishment Requests Sent by the QAAL2 on Dual-Stack Adjacent Node........................................................................................................................................................2709 2.6.3.4 Number of AAL2 Connection Establishment Requests Received by the QAAL2 on the Dual-Stack Adjacent Node........................................................................................................................................2710 2.6.3.5 Number of AAL2 Connection Establishment Request Rejections Received by the QAAL2 on the Dual-Stack Adjacent Node.....................................................................................................................2711 2.6.3.6 Number of AAL2 Connection Establishment Confirmations Received by the QAAL2 on Dual-Stack Adjacent Node........................................................................................................................................2712 2.6.3.7 Number of AAL2 Connection Establishment Confirmations Sent by the QAAL2 on Dual-Stack Adjacent Node........................................................................................................................................2714 2.6.3.8 Number of RLC Messages Sent by QAAL2 on Dual-Stack Adjacent Node after the QAAL2 Receives the Connection ERQ Message................................................................................................2715 2.6.3.9 Number of AAL2 Connection Releases Initiated by QAAL2 on Dual-Stack Adjacent Node ................................................................................................................................................................2716 2.6.3.10 Number of AAL2 Connection Releases Received by the QAAL2 on Dual-Stack Adjacent Node ................................................................................................................................................................2717 2.6.3.11 Number of AAL2 Connection Confirmations Received by the QAAL2 on Dual-Stack Adjacent Node........................................................................................................................................................2719 2.6.3.12 Number of AAL2 Connection Releases Confirmation Initiated by the QAAL2 on the Dual-Stack Adjacent Node........................................................................................................................................2720 2.6.3.13 Number of AAL2 Connection Modification Request Rejections Received by the QAAL2 on the Dual-Stack Adjacent Node.....................................................................................................................2721 2.6.3.14 Number of AAL2 Connection Modification Rejections Sent by the QAAL2 on Dual-Stack Adjacent Node........................................................................................................................................2723 2.6.3.15 Number of AAL2 Connection Modification Requests Sent by the QAAL2 on Dual-Stack Adjacent Node........................................................................................................................................................2724 2.6.3.16 Number of AAL2 Connection Modification Requests Received by the QAAL2 on Dual-Stack Adjacent Node........................................................................................................................................2725 2.6.3.17 Average Number of QAAL2 Connections to Dual-Stack Adjacent Node...............................2726 2.6.3.18 Counters Related to Average QAAL2 Bandwidth Allocated to Iub Adjacent Node on Dual-Stack Adjacent Node........................................................................................................................................2727 2.6.3.19 ..................................................................................................................................................2728 2.7 Measurement of ATM Logical Port Performance(ATM_LOGIC_PORT)..................................................2728 2.7.1 ATM Logical Port Measurement(ATM.LOGIC.PORT).....................................................................2729 2.7.1.1 Counters Related to the Bandwidth Assigned to an ATM Logical Port....................................2730 2.7.1.2 Counters Related to the Number of Congestions on the ATM Logical Port..............................2732 2.7.1.3 Counters Related to the Duration of Congestions on the ATM Logical Port.............................2733 2.8 Measurement of Channelized Optical Port Performance(CHANNELIZED_OPTICAL_PORT)...............2734 2.8.1 Channelized Optical Port Measurement(CHANNELIZED.OPTICAL.PORT)..................................2734 2.8.1.1 Duration of Faults in the optical port..........................................................................................2735 2.9 Measuement of E1T1 port error code Performance(E1T1_ES)...................................................................2735 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlviii
Contents
2.9.1 E1T1 Port Bit Error Measurement(E1T1_ES)....................................................................................2736 2.9.1.1 E1T1 Errored Second.................................................................................................................2738 2.9.1.2 E1T1 Severely Errored Second..................................................................................................2739 2.9.1.3 E1T1 Unavailable Second..........................................................................................................2740 2.9.1.4 E1T1 Background Error Block...................................................................................................2741 2.9.1.5 E1T1 Errored Second Rate.........................................................................................................2742 2.9.1.6 E1T1 Severely Errored Second Rate..........................................................................................2743 2.9.1.7 E1T1 Unavailable Second Rate..................................................................................................2744 2.9.1.8 E1T1 Background Block Error Rate..........................................................................................2744 2.10 Measurement of E1/T1 ELECT Port Performance(ELECT)......................................................................2745 2.10.1 E1/T1 Electronical Port Measurement(ELECT)...............................................................................2746 2.10.1.1 Counters Related to the Number of Cells with Error Codes in the E1/T1 electronical port ................................................................................................................................................................2747 2.10.1.2 Counters Related to the Rate of Cells in the E1/T1 electronical port.......................................2749 2.10.1.3 Duration of Faults in the E1/T1 electronical port.....................................................................2750 2.10.1.4 Number of Multiframes on the E1/T1 electronical port...........................................................2751 2.10.1.5 Counters Related to the Traffic Received or Transmitted on the E1/T1 electronical port.......2751 2.10.1.6 Number of Frame Alignment Changes of the E1/T1 electronical port....................................2752 2.11 Measurement of FEGE Ethernet Port Performance(FEGE).......................................................................2753 2.11.1 FEGE Ethernet Port Measurement(FEGE)........................................................................................2753 2.11.1.1 Counters Related to the Number of Bytes Received or Transmitted on the FEGE Ethernet port ................................................................................................................................................................2756 2.11.1.2 Counters Related to the Number of frames Received, Transmitted or Discarded on the FEGE Ethernet port...........................................................................................................................................2757 2.11.1.3 Duration of Faults in the FEGE Ethernet port..........................................................................2759 2.11.1.4 Counters related to the Receive Rate or Transmit Rate of the FEGE Ethernet port................2760 2.11.1.5 Counters Related to the Number of the PAUSE Control Frames on the FEGE Ethernet port ................................................................................................................................................................2762 2.11.1.6 5-Minute Measurement of the Highest Transmit and Receive Rates of the FEGE Ethernet port ................................................................................................................................................................2763 2.12 Measurement of Fractional ATM Link Performance(FRACATMLNK)...................................................2765 2.12.1 Fractional ATM Link Measurement(FRACATMLNK)....................................................................2765 2.12.1.1 Counters Related to the Number of Cells Received, Transmitted or Discarded on an Fractional ATM link................................................................................................................................................2768 2.12.1.2 Counters Related to the Receive Rate or Transmit Rate of an Fractional ATM link...............2769 2.12.1.3 Counters Related to the Occupied Forward Bandwidth or Backward Bandwidth of an FRA ATM Link.........................................................................................................................................................2771 2.12.1.4 Counters Related to the Number of Congestions on an FRA ATM Link................................2772 2.12.1.5 Counters Related to the Duration of Congestions on an FRA ATM Link...............................2773 2.13 Measurement of Fractioanl IMA Link Performance(FRACIMALNK).....................................................2774 2.13.1 Fractional IMA Link Measurement(FRACIMALNK)......................................................................2774 2.13.1.1 Counters Related to the Number of Cells Received, Transmitted or Discarded on an Fractional IMA Link................................................................................................................................................2776 2.13.1.2 Counters Related to the Receive Rate or Transmit Rate of an Fractional IMA Link...............2778 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlix
Contents
2.14 Measurement of IMA Group Performance(IMAGRP)...............................................................................2780 2.14.1 IMA Group Measurement(IMAGRP)...............................................................................................2780 2.14.1.1 Counters Related to the Number of Cells Received or Transmitted on an IMA Group...........2784 2.14.1.2 Counters Related to the Receive Rate or Transmit Rate of an IMA Group.............................2786 2.14.1.3 Counters Related to the Number of Error Cells Received or Transmitted on an IMA Group. 2787 2.14.1.4 Counters related to the Occupied Forward Bandwidth or Occupied Backward Bandwidth of an IMA Group.............................................................................................................................................2788 2.14.1.5 Counters Related to the Number of Congestions on an IMA Group........................................2789 2.14.1.6 Counters Related to the Duration of Congestion on an IMA Group........................................2790 2.15 Measurement of IMA Link Performance(IMALNK).................................................................................2791 2.15.1 IMA Link Measurement(IMALNK).................................................................................................2792 2.15.1.1 Counters Related to the Number of Packets Received or Transmitted on an IMA Link.........2795 2.15.1.2 Counters Related to the Receive Rate or Transmit Rate of an IMA Link................................2797 2.15.1.3 Number of Times That a Fault Occurs in an IMA Link...........................................................2798 2.15.1.4 Number of Times That a Fault Is Cleared in an IMA Link......................................................2799 2.15.1.5 Duration of Faults in an IMA Link...........................................................................................2800 2.16 Measurement of IPoA Link Performance(IPOALNK)...............................................................................2801 2.16.1 IPoA Link Measurement(IPOALNK)...............................................................................................2801 2.16.1.1 Counters Related to the Number of Cells Received or Transmitted Correctly on An IPoA Link ................................................................................................................................................................2803 2.16.1.2 Counters Related to the Number of Bytes Received or Transmitted on an IPoA Link............2804 2.16.1.3 Counters Related to the Maximum Receive Rate or the Maximum Transmit Rate of an IPoA Link ................................................................................................................................................................2805 2.16.1.4 Counters Related to the Number of Cells Discarded on an IPoA Link....................................2806 2.17 Measurement of VCL PM on an IPOAPVC link(IPOAPVC_VCLPM)....................................................2807 2.17.1 Measurement Related to VCL PM on an IPOAPVC link(IPOAPVC.VCLPM)...............................2808 2.17.1.1 Number of VCL PM Cells on an IPOAPVC link.....................................................................2809 2.17.1.2 Maximum Data Rate of VCL PM on an IPOAPVC link.........................................................2810 2.17.1.3 VCL PM Cell Discard Rate on an IPOAPVC link...................................................................2811 2.17.1.4 Rate of Incorrectly Inserted VCL PM Cells on an IPOAPVC link..........................................2813 2.17.1.5 Number of Error VCL PM Cell Blocks Failed BIP16 Check on an IPOAPVC link...............2814 2.18 Measurement of IP Path Performance(IPPATH).......................................................................................2816 2.18.1 IP Path Link Measurement(IPPATH)................................................................................................2816 2.18.1.1 Number of Active Connections on an IP Path..........................................................................2818 2.18.1.2 Average IP Path Ping Delay.....................................................................................................2818 2.18.1.3 Maximum IP Path Ping Delay..................................................................................................2819 2.18.1.4 Average IP Path Ping Delay Variation.....................................................................................2820 2.18.1.5 Maximum IP Path Ping Delay Variation..................................................................................2821 2.18.1.6 Average IP Path Ping Packet Loss Rate...................................................................................2822 2.18.1.7 Maximum IP Path Ping Packet Loss Rate................................................................................2823 2.18.1.8 Counters Related to the Number of Congestions on an IP Path...............................................2824 2.18.1.9 Counters Related to the Duration of Congestion on an IP Path...............................................2825 2.19 Measurement of IPPATH IP Layer Performance(IPPATH_IPLAYER)...................................................2826 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. l
Contents
2.19.1 IPPATH IP Layer Measurement(IPPATH.IPLAYER).....................................................................2827 2.19.1.1 Counters Related to the Number of Packets Received, Transmitted or Dropped at the IP Layer of an IPPATH.............................................................................................................................................2829 2.19.1.2 Counters Related to the Number of Bytes Received, Transmitted or Discarded at the IP Layer of an IPPATH.............................................................................................................................................2831 2.19.1.3 Counters Related to the Receive Rate or Transmit Rate of an IPPATH at the IP Layer..........2833 2.19.1.4 5-Minute Measurement of the Highest Transmit and Receive Rates of an IPPATH at the IP Layer ................................................................................................................................................................2834 2.20 Measurement of IPPATH PM Performance(IPPATH_PM)......................................................................2836 2.20.1 Measurement Related to IPPM(IPPATH.PM)..................................................................................2836 2.20.1.1 Bit Rate of IPPM......................................................................................................................2838 2.20.1.2 Packet TX and RX Rates of IPPM...........................................................................................2839 2.20.1.3 Forward Packet Loss Rate of IPPM.........................................................................................2840 2.20.1.4 Jitter Standard Deviation of IPPM............................................................................................2841 2.20.1.5 RTT Delay of IPPM.................................................................................................................2842 2.21 Measurement of IP-Path-Based RTP Performance(IPPATH_RTP)..........................................................2844 2.21.1 Measurement related to RTP flux in IPPATH(IPPATH.RTP)..........................................................2844 2.21.1.1 Total Number of RTP Packets Transmitted over a Single IP Path...........................................2845 2.21.1.2 Total Amount of RTP Data in KB Transmitted over a Single IP Path.....................................2846 2.21.1.3 Total Amount of RTP Data in KB Received over a Single IP Path.........................................2847 2.21.1.4 Loss Rate of RTP Packets Received over a Single IP Path......................................................2847 2.21.1.5 Total Number of RTP Packets Received over a Single IP Path...............................................2848 2.21.1.6 Mean Delay Jitter of RTP Packets Received over a Single IP Path.........................................2849 2.21.1.7 Mean RTT of Packets Received over a Single IP Path............................................................2850 2.21.1.8 Local Received Bandwidth of a Single IP Path........................................................................2851 2.21.1.9 Local Transmitted Bandwidth of a Single IP Path...................................................................2851 2.21.1.10 Ratio of Duration of RTP Delay Jitter Exceeding Threshold to Total Active Duration........2852 2.21.1.11 Ratio of Duration of RTT Exceeding Threshold to Total Active Duration............................2853 2.22 Measurement of Transmission Resource Pool Adjacent Node Connection Performance(IPPOOL_ADJNODE) ............................................................................................................................................................................2854 2.22.1 Measurement of IP Layer on User Plane of Transmission Resource Pool Adjacent Node (IPPOOL.ADJNODE.IPLAYER)................................................................................................................2855 2.22.1.1 Counters Related to the Number of Packets Received or Transmitted at the IP Layer on Adjacent Node User Plane.....................................................................................................................................2856 2.22.1.2 Counters Related to the Number of Bytes Received or Transmitted at the IP Layer on Adjacent Node User Plane.....................................................................................................................................2857 2.22.1.3 Counters Related to the Receive Rate or Transmit Rate at the IP Layer on Adjacent Node User Plane.......................................................................................................................................................2858 2.22.2 Measurement of IP Transmission Quality of Transmission Resource Pool Adjacent Node (IPPOOL.ADJNODE)..................................................................................................................................2859 2.22.2.1 Counters Related to the Number of Congestions of Adjacent Node........................................2861 2.22.2.2 Counters Related to the Duration of Congestion of Adjacent Node........................................2862 2.22.2.3 Average Ping Delay of Adjacent Node....................................................................................2863 2.22.2.4 Maximum Ping Delay of Adjacent Node.................................................................................2863 2.22.2.5 Average Ping Delay Variation of Adjacent Node....................................................................2864 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. li
Contents
2.22.2.6 Maximum Ping Delay Variation of Adjacent Node.................................................................2865 2.22.2.7 Average Ping Packet Loss Rate of Adjacent Node..................................................................2866 2.22.2.8 Maximum Ping Packet Loss Rate of Adjacent Node...............................................................2867 2.23 Measurement of Transmission Resource Pool IPPM Performance(IPPOOL_PM)...................................2868 2.23.1 Transmission Resource Pool IPPM Performance Measurement(IPPOOL.PM)...............................2869 2.23.1.1 Bit Rate of Transmission Resource Pool IPPM........................................................................2871 2.23.1.2 VS.IPPOOL.IPPM.ForwardPkts.MeansTx..............................................................................2873 2.23.1.3 VS.IPPOOL.IPPM.Forward.DropMeans.................................................................................2874 2.23.1.4 Forward Jitter of Transmission Resource Pool IPPM..............................................................2876 2.23.1.5 RTT Delay of Transmission Resource Pool IPPM...................................................................2876 2.24 Measurement of Transmission Resource Pool IP Address RTP Performance(IPPOOL_RTP).................2878 2.24.1 Measurement of Transmission Resource Pool IP Address RTP Performance(IPPOOL.RTP).........2878 2.24.1.1 Number of RTP Packets Sent Between an IP Address Pair.....................................................2880 2.24.1.2 Number of Bytes in RTP Packets Sent Between an IP Address Pair.......................................2881 2.24.1.3 Number of Bytes in RTP Packets Received Between an IP Address Pair...............................2881 2.24.1.4 Downlink Loss Rate of RTP Packets Between an IP Address Pair..........................................2882 2.24.1.5 Number of RTP Packets Received Between an IP Address Pair..............................................2883 2.24.1.6 Mean Delay Jitter for Receiving RTP Packets Between an IP Address Pair...........................2884 2.24.1.7 Mean RTT for RTP Packets Received Between an IP Address Pair........................................2885 2.24.1.8 Receive Bandwidth for RTP Packets Received Between an IP Address Pair..........................2885 2.24.1.9 Transmit Bandwidth for RTP Packets Sent Between an IP Address Pair................................2886 2.24.1.10 Percentage of Duration When Delay Jitter of RTP Packets Exceeds the Threshold to Total Activation Duration................................................................................................................................2887 2.24.1.11 Percentage of Duration When RTT of RTP Packets Exceeds the Threshold to Total Activation Duration..................................................................................................................................................2888 2.25 Measurement of Transmission Resource Pool Local IP Address Connection Performance(IPPOOL_SIP) ............................................................................................................................................................................2889 2.25.1 Transmission Resource Pool Local IP Address IP Layer Measurement(IPPOOL.SIP.IPLAYER) ......................................................................................................................................................................2890 2.25.1.1 Counters Related to the Number of Packets Received or Transmitted at the IP Layer on Local IP Address...................................................................................................................................................2891 2.25.1.2 Counters Related to the Number of Bytes Received or Transmitted at the IP Layer on Local IP Address...................................................................................................................................................2892 2.25.1.3 Counters Related to the Receive Rate or Transmit Rate at the IP Layer on Local IP Address ................................................................................................................................................................2893 2.25.2 Transmission Resource Pool Local IP Address Transmission Quality Measurement(IPPOOL.SIP) ......................................................................................................................................................................2894 2.25.2.1 Average Ping Packet Loss Rate of Local IP Address...............................................................2895 2.26 Measurement of IURP Link Performance(IURPLNK)..............................................................................2896 2.26.1 IURP Link Measurement(IURPLNK)...............................................................................................2896 2.26.1.1 Number of Packets Sent on the IURP Link..............................................................................2897 2.26.1.2 Number of Packets Received on the IURP Link......................................................................2898 2.26.1.3 Maximum Number of Packets Sent on the IURP Link............................................................2899 2.26.1.4 Maximum Number of Packets Received on the IURP Link....................................................2900 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lii
Contents
2.26.1.5 Number of IP Bytes Sent on the IURP Link............................................................................2901 2.26.1.6 Number of IP Bytes Received on the IURP Link.....................................................................2901 2.26.1.7 Maximum Number of IP Bytes Sent on the IURP Link...........................................................2902 2.26.1.8 Maximum Number of IP Bytes Received on the IURP Link...................................................2903 2.26.1.9 Service Duration of the IURP Link..........................................................................................2904 2.26.1.10 Number of Congestions on the IURP Link............................................................................2905 2.26.1.11 Congestion Duration of the IURP Link..................................................................................2905 2.26.1.12 Number of Overloads on the IURP Link................................................................................2906 2.26.1.13 Overload Duration of the IURP Link.....................................................................................2907 2.26.1.14 Number of Packets Resent on the IURP Link........................................................................2908 2.27 Measurement of Logic Port Performance(LOGIC_PORT)........................................................................2908 2.27.1 Logical Port Measurement(LOGIC.PORT)......................................................................................2909 2.27.1.1 Number of frames transmitted or discarded over a logical port...............................................2912 2.27.1.2 Number of bytes of data transmitted or discarded over a logical port......................................2913 2.27.1.3 Measurement of the Transmit Rate of the Logic Port..............................................................2913 2.27.1.4 Mean Forward Bandwidth Allocated on Logical Port..............................................................2914 2.27.1.5 Mean Backward Bandwidth Allocated on Logical Port...........................................................2915 2.27.1.6 Maximum Forward Bandwidth Allocated on Logical Port......................................................2916 2.27.1.7 Maximum Backward Bandwidth Allocated on Logical Port...................................................2917 2.27.1.8 Measurement of the Number of Congestions on the Logic Port..............................................2918 2.27.1.9 Measurement of Congestion Duration on the Logic Port.........................................................2919 2.27.1.10 5-Minute Measurement of the Highest Transmit Rates of of the Logic Port.........................2919 2.28 Measurement of Logic Port Queue Performance(LOGIC_PORT_QUEUE).............................................2921 2.28.1 Logical Port Queue Measurement(LOGIC.PORT.QUEUE).............................................................2921 2.28.1.1 Measurement of the Transmitted and Discarded Packets over a logical port queue................2922 2.28.1.2 Measurement of the Transmitted and Discarded Bytes over a logical port queue...................2923 2.28.1.3 Measurement of the Transmit Rate of logical port queue........................................................2924 2.29 Measurement of the M3UA Destination Entities Performance(M3UA_DE).............................................2925 2.29.1 M3UA Destination Entity Measurement(M3UA.DE).......................................................................2925 2.29.1.1 Number of M3UA Destination Entity Changes to Unavailable State......................................2926 2.29.1.2 Duration of M3UA Destination Entity in Unavailable State....................................................2927 2.30 Measurement of the M3UA Link Performance(M3UA_LNK)..................................................................2928 2.30.1 M3UA Link Measurement(M3UA.LNK).........................................................................................2928 2.30.1.1 Number of M3UA Link Failures..............................................................................................2929 2.30.1.2 Duration of M3UA Link Failure..............................................................................................2930 2.30.1.3 Duration of M3UA Link Congestion........................................................................................2930 2.30.1.4 Counters Related to the Number of Message Units Sent and Received on M3UA Link.........2931 2.31 Measurement of M3UA Link Set Performance(M3UA_LNK_SET)........................................................2933 2.31.1 M3UA Link Set Measurement(M3UA.LNKSET)............................................................................2933 2.31.1.1 Number of M3UA Link Set Failures........................................................................................2934 2.31.1.2 Duration of M3UA Link Set Failure........................................................................................2935 2.32 Measurement of MP Group Performance(MLPPP)...................................................................................2936 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. liii
Contents
2.32.1 MP Group Measurement(MLPPP)....................................................................................................2936 2.32.1.1 Counters Related to the Number of frames Received, Transmitted or Discarded on an MP Group ................................................................................................................................................................2939 2.32.1.2 Counters Related to the Number of Bytes of Data Received or Transmitted on an MP Group ................................................................................................................................................................2940 2.32.1.3 Duration of Faults in an MP Group..........................................................................................2941 2.32.1.4 Counters Related to the Receive Rate or Transmit Rate of an MP Group...............................2942 2.32.1.5 Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to an MLPPP Group ................................................................................................................................................................2943 2.32.1.6 Measurement of the Number of Congestions on an MLPPP Group........................................2945 2.32.1.7 Measurement of the Duration of Congestion on an MLPPP Group.........................................2946 2.33 Measurement of MP Queue Performance(MLPPP_QUEUE)....................................................................2947 2.33.1 MP Queue Measurement(MLPPP.QUEUE).....................................................................................2947 2.33.1.1 Counters Related to the Transmitted and Discarded Packets on an MP Queue.......................2949 2.33.1.2 Counters Related to the Number of Bytes Transmitted or Discarded on an MP Queue..........2950 2.33.1.3 Measurement Counters Related to the Transmit Rate of an MP Queue...................................2951 2.34 Measurement of MTP3 Destination Signaling Point Performance(MTP3_DSP)......................................2952 2.34.1 MTP3 Destination Signaling Point Measurement(MTP3.DSP)........................................................2952 2.34.1.1 Number of MTP3 Destination Signaling Point Failures..........................................................2953 2.34.1.2 Duration of MTP3 Destination Signaling Point Failure...........................................................2954 2.35 Measurement of MTP3 Signaling Link performance(MTP3_LNK)..........................................................2955 2.35.1 MTP3 Link Measurement(MTP3.LNK)............................................................................................2955 2.35.1.1 Service Duration of MTP3 Link...............................................................................................2957 2.35.1.2 Number of MTP3 Link Failures...............................................................................................2958 2.35.1.3 Duration of Out-of-Service MTP3 Link...................................................................................2958 2.35.1.4 Duration of MTP3 Link Congestion.........................................................................................2959 2.35.1.5 Number of Local Inhibitions on MTP3 Link............................................................................2960 2.35.1.6 Duration of Local Inhibition on MTP3 Link............................................................................2961 2.35.1.7 Number of Remote Inhibitions on MTP3 Link........................................................................2961 2.35.1.8 Duration of Remote Inhibition on MTP3 Link.........................................................................2962 2.35.1.9 Number of MTP3 Link Changeovers.......................................................................................2963 2.35.1.10 Number of Message Signal Units Sent by MTP3 Link..........................................................2964 2.35.1.11 Number of Message Signal Units Received by MTP3 Link..................................................2964 2.35.1.12 Number of MTP3 Link Congestions......................................................................................2965 2.35.1.13 Number of MSU Bytes Sent by MTP3 Link..........................................................................2966 2.35.1.14 Number of MSU Bytes Received by MTP3 Link..................................................................2967 2.35.1.15 MTP3 Link Remote Processor Failures..................................................................................2968 2.35.1.16 Number of Messages Discarded on MTP3 Link Due to Link Congestion.............................2968 2.35.1.17 Number of Transfer-Prohibited Signals Received on MTP3 Link.........................................2969 2.35.1.18 Number of Messages Discarded on MTP3 Link Due to Route Fail.......................................2970 2.35.1.19 Number of Transfer-Controlled Signals Received on MTP3 Link........................................2971 2.35.1.20 Duration of MTP3 Link Remote Processor Fault...................................................................2971 2.36 Measurement of MTP3 Link Set Performance(MTP3_LNK_SET)...........................................................2972 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. liv
Contents
2.36.1 MTP3 Link Set Measurement(MTP3.LNKSET)..............................................................................2973 2.36.1.1 Number of MTP3 Link Set Failures.........................................................................................2973 2.36.1.2 Duration of MTP3 Link Set in Unavailable State....................................................................2974 2.37 Measurement of Non-Channelized Optical Port Performance(NON_CHANNELIZED_OPTICAL_PORT) ............................................................................................................................................................................2975 2.37.1 Non Channelized Optical Port Measurement(NON.CHANNELIZED.OPTICAL.PORT)...............2975 2.37.1.1 Counters Related to the Number of Cells Received or Transmitted on the optical port..........2976 2.37.1.2 Duration of Faults in the optical port........................................................................................2977 2.37.1.3 Counters Related to the Receive Rate or Transmit Rate over the optical port.........................2978 2.37.2 Maximum flux of UOI board(UOI.BOARD)....................................................................................2979 2.37.2.1 Maximum receiving and transmitting rate of UOI board.........................................................2980 2.38 Measurement of NODEB OAM Flow Performance(OAM_FLOW).........................................................2981 2.38.1 NODEB OAM FLOW Measurement(OAM.FLOW)........................................................................2981 2.38.1.1 Counters Related to the Number of Packets Received or Transmitted in the OAM FLOW....2984 2.38.1.2 Counters Related to the Number of Bytes Received or Transmitted in the OAM FLOW.......2985 2.38.1.3 Counters Related to the Receive Rate or Transmit Rate of the OAM FLOW.........................2986 2.39 Measurement of PPP Link Performance(PPP)...........................................................................................2987 2.39.1 PPP Link Measurement(PPP)............................................................................................................2988 2.39.1.1 Number of Frames Received, Transmitted or Discarded on a PPP Link.................................2990 2.39.1.2 Number of Bytes Received or Transmitted on a PPP Link......................................................2992 2.39.1.3 Duration of Faults on a PPP Link.............................................................................................2992 2.39.1.4 Counters Related to the Receive Rate or Transmit Rate of a PPP Link...................................2993 2.39.1.5 Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to a PPP Link ................................................................................................................................................................2995 2.39.1.6 Measurement of the Number of Congestions on a PPP Link...................................................2996 2.39.1.7 Measurement of the Duration of Congestion on a PPP Link...................................................2997 2.40 Measurement of PPP Queue Performance(PPP_QUEUE).........................................................................2998 2.40.1 PPP Link Queue Measurement(PPP.QUEUE)..................................................................................2998 2.40.1.1 Counters Related to the Number of Packets Transmitted in a PPP Link Queue or Discarded in the Transmitting Direction of a PPP Link Queue.........................................................................................3000 2.40.1.2 Counters Related to the Number of Bytes Transmitted in a PPP Link Queue or Discarded in the Transmitting Direction of a PPP Link Queue.........................................................................................3001 2.40.1.3 Counters Related to the Transmit Rate of a PPP Link Queue..................................................3002 2.41 Measurement of SAAL Link Performance(SAAL_LNK).........................................................................3003 2.41.1 SAAL Link Measurement(SAAL.LNK)...........................................................................................3003 2.41.1.1 In-Service Duration of SAAL Link..........................................................................................3005 2.41.1.2 Number of SAAL Link Failures...............................................................................................3005 2.41.1.3 Number of Link Failures Due to No Response of SAAL Link................................................3006 2.41.1.4 Number of SAAL Link Failures Due to Excessive Errors.......................................................3007 2.41.1.5 Number of SAAL Link Failures Due to No Credit..................................................................3008 2.41.1.6 Number of SAAL Link Location Failures................................................................................3009 2.41.1.7 Number of Retransmissions of the downlink Lost Packet on the SAAL Link.........................3010 2.41.1.8 Number of Unexpected PDUs Received by SAAL Link.........................................................3011 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lv
Contents
2.41.1.9 Number of Errors of Other Types on SAAL Link....................................................................3011 2.41.1.10 Number of Retransmission Failures of Connection Control Message on SAAL Link..........3012 2.41.1.11 Number of Bytes Received by SAAL Link............................................................................3013 2.41.1.12 Number of Bytes Sent by SAAL Link....................................................................................3014 2.41.1.13 Number of Packets Discarded by SAAL Link Due to Buffer Congestion.............................3014 2.41.1.14 Number of Retransmissions of the uplink Lost Packet on the SAAL Link...........................3015 2.42 Measurement of SAAL Link ATM Layer Performance(SAALLNK_PVCLAYER)................................3016 2.42.1 SAAL link ATM Layer Measurement(SAALLNK.PVCLAYER)...................................................3017 2.42.1.1 Counters Related to the Number of Bytes Received or Transmitted on an SAAL link ATM Layer ................................................................................................................................................................3020 2.42.1.2 Counters Related to the Maximum Receive Rate or Maximum Transmit Rate of an SAAL link ATM Layer.............................................................................................................................................3021 2.42.1.3 Counters Related to the Number of Correct Packets Received or Transmitted on an SAAL link ATM Layer.............................................................................................................................................3022 2.42.1.4 Counters Related to the Number of Cells Discarded on an SAAL link ATM Layer...............3023 2.43 Measurement of VCL PM on a SAAL link(SAALLNK_VCLPM)...........................................................3024 2.43.1 Measurement Related to VCL PM on a SAAL link(SAALLNK.VCLPM)......................................3025 2.43.1.1 Number of VCL PM Cells on a SAAL link.............................................................................3027 2.43.1.2 Maximum Data Rate of VCL PM on a SAAL link..................................................................3028 2.43.1.3 VCL PM Cell Discard Rate on a SAAL link............................................................................3029 2.43.1.4 Rate of Incorrectly Inserted VCL PM Cells on a SAAL link...................................................3030 2.43.1.5 Number of Error VCL PM Cell Blocks Failed BIP16 Check on a SAAL link........................3031 2.44 Measurement of SCCP Based on OSP Performance(SCCP).....................................................................3033 2.44.1 SCCP Measurement(SCCP)..............................................................................................................3033 2.44.1.1 Number of SCCP Connection Release Expiry.........................................................................3037 2.44.1.2 Number of SCCP Connection Releases Due to SCCP Inactivity Test.....................................3038 2.44.1.3 Number of NSP-initiated SCCP Connection Releases Received by SCCP.............................3039 2.44.1.4 Number of SCCP XUDT Segmentation Failures.....................................................................3039 2.44.1.5 Number of RLSD Messages Received by the SCCP...............................................................3040 2.44.1.6 Number of XUDTS Messages Received by the SCCP with the Cause of Transmission Error ................................................................................................................................................................3042 2.44.1.7 Number of UDTS Messages Received by the SCCP with the Cause of Segmentation Failure ................................................................................................................................................................3043 2.44.1.8 Number of ERROR PDU Messages Received by the SCCP...................................................3044 2.44.1.9 Number of ERROR PDU Messages Sent by the SCCP...........................................................3044 2.44.1.10 Number of SCCP Routing Failures........................................................................................3045 2.44.1.11 Counters Related to Number of Messages Sent by the SCCP................................................3047 2.44.1.12 Counters Related to Number of Messages Received by the SCCP........................................3048 2.44.1.13 Number of Messages Handled by the SCCP..........................................................................3050 2.44.1.14 Number of Messages Sent by the SCCP to the Local Subsystem..........................................3050 2.44.1.15 Number of CR Messages Sent and Received by the SCCP...................................................3051 2.44.1.16 Number of CREF Messages Sent and Received by the SCCP...............................................3052 2.44.1.17 Ratio of the CREF Messages from the Peer SCCP................................................................3053 2.44.1.18 Ratio of the CREF Messages from the Local SCCP..............................................................3054 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lvi
Contents
2.44.1.19 Number of CC Messages Sent and Received by the SCCP...................................................3055 2.44.1.20 Number of RLSD Messages Sent by the SCCP.....................................................................3056 2.44.1.21 Number of RLC Messages Sent and Received by the SCCP.................................................3057 2.45 Measurement of SCTP Link Performance(SCTPLNK).............................................................................3058 2.45.1 SCTPIP Measurement(SCTPIP)........................................................................................................3058 2.45.1.1 Counters Related to Number of Bytes That the SCTP Link Receives from or Transmits to the IP Layer....................................................................................................................................................... 3059 2.45.1.2 Counters Related to the Number of IP Packets Received or Transmitted on the SCTP Link ................................................................................................................................................................3061 2.45.1.3 Number of Packets Resent on the SCTP Link..........................................................................3063 2.45.1.4 Number of Error Packets Received on SCTP Link..................................................................3064 2.45.1.5 Number of Retransmit Request Sent on the SCTP Link..........................................................3065 2.45.2 SCTP Link Measurement(SCTPLNK).............................................................................................. 3066 2.45.2.1 Service Duration of the SCTP Link..........................................................................................3066 2.45.2.2 Congestion Duration of the SCTP Link...................................................................................3067 2.45.2.3 Number of Packets Sent on the SCTP Link.............................................................................3068 2.45.2.4 Number of Packets Received on SCTP Link............................................................................3069 2.46 Measurement of SCTP Link IP Layer Performance(SCTPLNK_IPLAYER)...........................................3070 2.46.1 Measurement related to SCTP link IP layer(SCTPLNK.IPLAYER)................................................3070 2.46.1.1 Counters related to the Receive Rate or Transmit Rate of an SCTP link IP layer...................3072 2.47 Measurement of SDH Performance(SDH).................................................................................................3075 2.47.1 SDH Measurement(SDH)..................................................................................................................3075 2.47.1.1 Counters Related to the Number of SDH Port Switchovers.....................................................3076 2.47.1.2 Number of SDH Channel Failures............................................................................................3077 2.48 Measurement of Trunk Group Performance(Trunk)..................................................................................3078 2.48.1 Measurement of Trunk Group Performance(Trunk).........................................................................3078 2.48.1.1 Number of Bytes That Are Transmitted and Received by Trunk Group.................................3081 2.48.1.2 Receive Rate and Transmit Rate of Trunk Group....................................................................3082 2.48.1.3 BER of Data Transmitted and Received by Trunk Group........................................................3084 2.48.1.4 Number of Frames That Are Transmitted, Received, or Discarded by the Trunk Group........3085 2.49 Measurement of UNI Link Performance(UNILNK)..................................................................................3087 2.49.1 Measurement related to UNI link(UNILNK)....................................................................................3087 2.49.1.1 Counters Related to the Number of Cells Received or Transmitted on a UNI Link................ 3090 2.49.1.2 Counters Related to the Receive Rate or Transmit Rate of a UNI Link...................................3091 2.49.1.3 Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to a UNI Link ................................................................................................................................................................3092 2.49.1.4 Measurement of the Number of Congestions on a UNI Link...................................................3093 2.49.1.5 Measurement of the Duration of Congestion on an UNI Link.................................................3094 2.50 Measurement of VC Cross Performance(VCACROSS)............................................................................3095 2.50.1 VCACROSS Measurement(VCACROSS)........................................................................................3095 2.50.1.1 Measurement of the Number of Bytes Received or Transmitted on a VCCROSS Link..........3099 2.50.1.2 Measurement of the Number of Cells Received or Transmitted on a VCCROSS Link...........3100 2.50.1.3 Counters Related to the Receive Rate or Transmit Rate of a VC Cross Connection...............3102 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lvii
Contents
3 Hardware Platform Related Measurement.........................................................................3104

3.1 Measurement of DPU Performance(DPU)...................................................................................................3105 3.1.1 DPU Measurement(DPU)....................................................................................................................3105 3.1.1.1 Maximum CPU Usage of the DPU.............................................................................................3106 3.1.1.2 Average CPU Usage of the DPU................................................................................................3106 3.1.1.3 Rate of the Period in Which the CPU Usage of the DPU Exceeds the Alarm Threshold..........3107 3.1.1.4 Rate of the Period in Which the CPU Usage of the DPU Is Lower Than the Alarm Threshold ................................................................................................................................................................3108 3.2 Measurement of Inter-Subrack Traffic Performance(FRAME_FLUX).......................................................3109 3.2.1 Inter-Subrack Traffic Measurement(FRAME.FLUX).........................................................................3109 3.2.1.1 Peak Inter-Subrack Transmitting Traffic....................................................................................3109 3.2.1.2 Average Inter-Subrack Transmitting Traffic..............................................................................3110 3.2.1.3 Number of Discarded Inter-Subrack Packets.............................................................................3111 3.2.1.4 Number of Sent Inter-Subrack Packets......................................................................................3112 3.3 Measurement of GCU Performance(GCU)..................................................................................................3113 3.3.1 GCU Measurement(GCU)...................................................................................................................3113 3.3.1.1 Maximum CPU Usage of the GCU............................................................................................3114 3.3.1.2 Average CPU Usage of the GCU...............................................................................................3114 3.3.1.3 Rate of the Period in Which the CPU Usage of the GCU Exceeds the Alarm Threshold..........3115 3.3.1.4 Rate of the Period in Which the CPU Usage of the GCU Is Lower Than the Alarm Threshold ................................................................................................................................................................3116 3.4 Measurement of INT Performance(INT)......................................................................................................3117 3.4.1 Measurement related to INT(INT).......................................................................................................3117 3.4.1.1 Maximum CPU usage of the INT...............................................................................................3118 3.4.1.2 Average CPU Usage of the INT.................................................................................................3119 3.4.1.3 Rate of the Period in Which the CPU Usage of the INT Exceeds the Alarm Threshold...........3119 3.4.1.4 Rate of the Period in Which the CPU Usage of the INT Is Lower Than the Alarm Threshold ................................................................................................................................................................3120 3.4.1.5 Maximum Forwarding Ratio of Interface Boards......................................................................3121 3.4.1.6 Average Forwarding Ratio of Interface Boards..........................................................................3122 3.4.1.7 Number of Call Establishment Attempts And Number of Call Establishment Failures on an Interface Board......................................................................................................................................................3123 3.5 Measurement of NIU DSP Performance(NDSP).........................................................................................3124 3.5.1 Measurement related to NIU DSP performance(NDSP).....................................................................3124 3.5.1.1 Maximum CPU Usage of the NIU DSP.....................................................................................3125 3.5.1.2 Average CPU Usage of the NIU DSP........................................................................................3125 3.6 Measurement of NIU Performance(NIU).....................................................................................................3126 3.6.1 NIU Measurement(NIU)......................................................................................................................3127 3.6.1.1 Maximum CPU Usage of the NIU.............................................................................................3127 3.6.1.2 Average CPU Usage of the NIU.................................................................................................3128 3.7 Measurement of SCU Performance(SCU)...................................................................................................3129 3.7.1 SCU Measurement(SCU)....................................................................................................................3129 3.7.1.1 Maximum CPU Usage of the SCU.............................................................................................3130 Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lviii
Contents
3.7.1.2 Average CPU Usage of the SCU................................................................................................3130 3.7.1.3 Rate of the Period in Which the CPU Usage of the SCU Exceeds the Alarm Threshold..........3131 3.7.1.4 Rate of the Period in Which the CPU Usage of the SCU Is Lower Than the Alarm Threshold ................................................................................................................................................................3132 3.8 Measurement of XPU Performance(XPU)...................................................................................................3133 3.8.1 XPU Measurement(XPU)....................................................................................................................3133 3.8.1.1 Maximum CPU Usage of the XPU.............................................................................................3134 3.8.1.2 Average CPU Usage of the XPU................................................................................................3135 3.8.1.3 Rate of the Period in Which the CPU Usage of the XPU Exceeds the Alarm Threshold..........3135 3.8.1.4 Rate of the Period in Which the CPU Usage of the XPU Is Lower Than the Alarm Threshold ................................................................................................................................................................3136 3.8.1.5 Maximum Packet Usage of the XPU..........................................................................................3137 3.8.1.6 Average Packet Usage of the XPU.............................................................................................3138
Issue 01 (2013-05-04)
lix
1 UMTS Radio Network Related Measurement
1
About This Chapter
UMTS Radio Network Related Measurement
The following measurements are UMTS Radio Network Related Measurement. 1.1 Measurement of CNOPERATOR Performance(CNOPERATOR) 1.2 Measurement of CPUS Performance(CPUS) 1.3 Measurement of GTPU Performance(GTPU) 1.4 Measurement of IU Interface Performance(IU) 1.5 Measurement of IUR Interface Performance(IUR) 1.6 Measurement of MPU Performance(MPU) 1.7 Measurement of NODEB Performance(NODEB) 1.8 Measurement of Physical RNC Node(NODESHARE) 1.9 Measurement of Operator Performance at the NodeB Level(PLMN_NodeB) 1.10 Measurement of RNC Performance(RNC) 1.11 Measurement of ROAMCNOPERATOR Performance(ROAM_CNOPERATOR) 1.12 Measurement of Radio Cell Performance(UCELL) 1.13 Measurement between a cell and a neighbour interRAT cell Performance (UCELL_GCELL) 1.14 Measurement between a cell and a neighbour UMTS cell(UCELL_NCELL) 1.15 Measurement of UMTS DSP Performance(UDSP)
Issue 01 (2013-05-04)
1.1 Measurement of CNOPERATOR Performance (CNOPERATOR)

Overview
The CNOPERATOR Performance Measurement is to measure the overall performance for each Operator. It includes only one measurement set, CNOPERATOR performance measurement.
FunctionSubSets
FunctionSubSet ALGO.PLMN.RNC RAB.Estab.PLMN.RNC RAB.Rel.PLMN.RNC TRAFF.LOAD.PLMN.RNC FunctionSubSet Name Measurement of active algorithm per PLMN Measurement of RAB assignment setup per PLMN Measurement of RAB assignment release per PLMN Traffic Measurement of CN Operator per RNC
1.1.1 Measurement of active algorithm per PLMN (ALGO.PLMN.RNC)

Overview
Measurement is used to measure active algorithm of RNC for each Operator.
Counters
Counter ID 73394050 Counter Name VS.PI.HSDPA.TR BNum.PLMN.RNC Counter Description Number of TRBs of HSDPA Service on Which Packet Inspection (PI) Takes Effect for RNC Original Release V900R012
Counter Relationship
None
Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2
1.1.1.1 Number of TRBs of HSDPA Service on Which Packet Inspection (PI) Takes Effect for RNC Counters
Counter ID 73394050 Counter Name VS.PI.HSDPA.TRBNum.PL MN.RNC Counter Description Number of TRBs of HSDPA Service on Which Packet Inspection (PI) Takes Effect for RNC
Description
This counter provides the number of TRBs of the HSDPA service on which the PI takes effect under the RNC according to telecom operators. It reflects whether the PI algorithm is used by telecom operators.
Measurement point
This counter provides the number of TRBs of the HSDPA service on which the PI takes effect under the RNC according to telecom operators.This counter is incremented by one when the PI takes effect.This counter is measured only once for one HSDPA session.
Formula
None
Unit
None
Related Features
Counter Name VS.PI.HSDPA.TRBNum.PL MN.RNC Feature ID WRFD-020128 Feature Name Quality Improvement for Subscribed Service
1.1.2 Measurement of RAB assignment setup per PLMN (RAB.Estab.PLMN.RNC)

Overview
This function subset provides the number of service setup requests and successful service setups for different services of different operators. This enables the operators to monitor the RAB setup conditions.
Counters
Counter ID 67196186 Counter Name VS.RAB.AttEstab. AMR.PLMN.RNC Counter Description Number of AMR CS RABs Establishment Requests for Operator Number of AMR CS RABs Successfully Established for Operator(WB+NB) Number of 64kbit/s CS Conversational Service RABs Establishment Requests for Operator Number of 64kbit/s CS Conversational Service RABs Successfully Established for Operator Number of PS RABs Establishment Requests for Operator Number of PS RABs Successfully Established for Operator Original Release Earlier than V900R011
67196187
VS.RAB.SuccEstab .AMR.PLMN.RNC
Earlier than V900R011
67196188
VS.RAB.AttEstab. CS64.PLMN.RNC
67196189
VS.RAB.SuccEstab .CS64.PLMN.RNC
67196190
VS.RAB.AttEstab. PS.PLMN.RNC
67196191
VS.RAB.SuccEstab .PS.PLMN.RNC
None
1.1.2.1 Number of RABs Requested to Establish for each Operator Counters

Counter ID 67196186 Counter Name VS.RAB.AttEstab.AMR.PL MN.RNC Counter Description Number of AMR CS RABs Establishment Requests for Operator
4
Issue 01 (2013-05-04)
Counter ID 67196188
Counter Name VS.RAB.AttEstab.CS64.PL MN.RNC
Counter Description Number of 64kbit/s CS Conversational Service RABs Establishment Requests for Operator Number of PS RABs Establishment Requests for Operator
67196190
VS.RAB.AttEstab.PS.PLM N.RNC
Description
The measurement items provide the number of RABs requested to establish according to different types of service for each operator, as shown below. The following table describes the meaning of each counter. Counter Name VS.RAB.AttEstab.AMR.PLMN.RNC Description Number of AMR service RABs requested to establish for each operator( narrowband and wideband AMR services) Number of CS 64kbits/s conversational service RABs requested to establish for each operator Number of PS RABs requested to establish for each operator
VS.RAB.AttEstab.CS64.PLMN.RNC
VS.RAB.AttEstab.PS.PLMN.RNC
Measurement point
The measurement is triggered at point A as shown in the figure. If the RNC finds that some RABs need to be established after receiving a RAB ASSIGNMENT REQUEST message, the RNC measures the items according to the types of service for each operator.
Issue 01 (2013-05-04)
Figure 1-1 RAB setup procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstab.AMR.PL MN.RNC Feature ID WRFD-021311 WRFD-010501 WRFD-021311 WRFD-010501 WRFD-021311 WRFD-010510 Feature Name MOCN Introduction Package Conversational QoS Class VS.RAB.AttEstab.CS64.PL MN.RNC MOCN Introduction Package Conversational QoS Class VS.RAB.AttEstab.PS.PLM N.RNC MOCN Introduction Package 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
1.1.2.2 Number of Successfully Established RABs for each Operator Counters

Counter ID 67196187 Counter Name VS.RAB.SuccEstab.AMR.P LMN.RNC VS.RAB.SuccEstab.CS64.P LMN.RNC Counter Description Number of AMR CS RABs Successfully Established for Operator(WB+NB) Number of 64kbit/s CS Conversational Service RABs Successfully Established for Operator Number of PS RABs Successfully Established for Operator
67196189
67196191
VS.RAB.SuccEstab.PS.PL MN.RNC
Description
The measurement items provide the number of RABs successfully established according to different types of service for each operator, as shown below. The following table describes the meaning of each counter. Counter Name VS.RAB.SuccEstab.AMR.PLMN.RNC Description Number of AMR service RABs successfully established for each operator( narrowband and wideband AMR services) Number of CS 64kbits/s conversational service RABs successfully established for each operator Number of PS RABs successfully established for each operator
VS.RAB.SuccEstab.CS64.PLMN.RNC
VS.RAB.SuccEstab.PS.PLMN.RNC
Measurement point
The measurement is triggered at point B as shown in the figure.If the RNC finds that some RABs have been successfully set up after receiving a RADIO BEARER SETUP COMPLETE message from the UE, the RNC measures the items when the RNC sends RAB ASSIGNMENT RESPONSE message to CN according to the types of service for each operator.
Issue 01 (2013-05-04)
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstab.AMR.P LMN.RNC Feature ID WRFD-021311 WRFD-010501 WRFD-021311 WRFD-010501 WRFD-021311 WRFD-010510 Feature Name MOCN Introduction Package Conversational QoS Class VS.RAB.SuccEstab.CS64.P LMN.RNC MOCN Introduction Package Conversational QoS Class VS.RAB.SuccEstab.PS.PL MN.RNC MOCN Introduction Package 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
1.1.3 Measurement of RAB assignment release per PLMN (RAB.Rel.PLMN.RNC)

Overview
This function subset provides the number of normal service releases and abnormal service releases for different services of different operators. This enables the operators to monitor the RAB setup conditions.
Counters
Counter ID 67196192 Counter Name VS.RAB.AbnormR el.AMR.PLMN.RN C VS.RAB.NormRel. AMR.PLMN.RNC VS.RAB.AbnormR el.CS64.PLMN.RN C Counter Description Number of Abnormally Released AMR CS RABs for Operator Number of Normally Released AMR CS RABs for Operator Number of Abnormally Released 64kbit/s CS Conversational Service RABs for Operator Number of Normally Released 64kbit/s CS Conversational Service RABs for Operator Number of Abnormally Released PS RABs for Operator Number of Normally Released PS RABs for Operator Original Release Earlier than V900R011
67196193
Earlier than V900R011 Earlier than V900R011
67196194
67196195
VS.RAB.NormRel. CS64.PLMN.RNC
67196196
VS.RAB.AbnormR el.PS.PLMN.RNC
67196197
VS.RAB.NormRel. PS.PLMN.RNC
None
1.1.3.1 Number of Abnormally Released RABs for each Operator

Counters
Counter ID 67196192 Counter Name VS.RAB.AbnormRel.AMR. PLMN.RNC VS.RAB.AbnormRel.CS64. PLMN.RNC Counter Description Number of Abnormally Released AMR CS RABs for Operator Number of Abnormally Released 64kbit/s CS Conversational Service RABs for Operator Number of Abnormally Released PS RABs for Operator
67196194
67196196
VS.RAB.AbnormRel.PS.PL MN.RNC
Description
The measurement items take statistics of the number of abnormally released RABs of different type services for each Operator. The following table describes the meaning of each counter. Counter Name VS.RAB.AbnormRel.AMR.PLMN.RNC Description Number of abnormally released AMR service RABs for each operator(narrowband and wideband AMR services) Number of abnormally released CS 64K Conversational Service RABs for each operator Number of abnormally released PS RABs for each operator
VS.RAB.AbnormRel.CS64.PLMN.RNC
VS.RAB.AbnormRel.PS.PLMN.RNC
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items by the types of services and operators.
Issue 01 (2013-05-04)
10
Figure 1-3 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items by the types of services and operators.
Issue 01 (2013-05-04)
11
Figure 1-4 RAB release IU REL procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items by the types of services and operators.
Issue 01 (2013-05-04)
12
Figure 1-5 Iu connection release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.AMR. PLMN.RNC Feature ID WRFD-021311 WRFD-010501 WRFD-021311 WRFD-010501 WRFD-021311 WRFD-010510 Feature Name MOCN Introduction Package Conversational QoS Class VS.RAB.AbnormRel.CS64. PLMN.RNC MOCN Introduction Package Conversational QoS Class VS.RAB.AbnormRel.PS.PL MN.RNC MOCN Introduction Package 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
13
1.1.3.2 Number of Normally Released RABs for each Operator Counters

Counter ID 67196193 Counter Name VS.RAB.NormRel.AMR.PL MN.RNC VS.RAB.NormRel.CS64.PL MN.RNC Counter Description Number of Normally Released AMR CS RABs for Operator Number of Normally Released 64kbit/s CS Conversational Service RABs for Operator Number of Normally Released PS RABs for Operator
67196195
67196197
VS.RAB.NormRel.PS.PLM N.RNC
Description
The measurement items take statistics of the number of normally released RABs of different type services for each Operator. The following table describes the meaning of each counter. Counter Name VS.RAB.NormRel.AMR.PLMN.RNC Description Number of normally released AMR service RABs for each operator(narrowband and wideband AMR services) Number of normally released CS 64kbit/s Conversational Service RABs for each operator Number of normally released PS RABs for each operator
VS.RAB.NormRel.CS64.PLMN.RNC
VS.RAB.NormRel.PS.PLMN.RNC
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release", the RNC measures the items by the types of services and operators.
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release" ,the RNC measures the items by the types of services and operators.
Issue 01 (2013-05-04)
15
Figure 1-7 RAB release procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.AMR.PL MN.RNC Feature ID WRFD-021311 WRFD-010501 WRFD-021311 WRFD-010501 WRFD-021311 WRFD-010510 Feature Name MOCN Introduction Package Conversational QoS Class VS.RAB.NormRel.CS64.PL MN.RNC MOCN Introduction Package Conversational QoS Class VS.RAB.NormRel.PS.PLM N.RNC MOCN Introduction Package 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.1.4 Traffic Measurement of CN Operator per RNC (TRAFF.LOAD.PLMN.RNC)

Overview
Traffic Measurement for each Operator is used to measure the traffic of CS domain and PS domain of RNC for each Operator, and it contains the case of SHO. Where, the traffic of CS domain is denoted by equivalent Erlang; the traffic of PS domain is expressed in kbit/s.
Counters
Counter ID 67203962 Counter Name VS.CSLoad.Erlang .Equiv.PLMN.RNC VS.CSLoad.MaxEr lang.Equiv.PLMN. RNC VS.R99PSLoad.UL Thruput.PLMN.R NC VS.R99PSLoad.Ma xULThruput.PLM N.RNC VS.R99PSLoad.DL Thruput.PLMN.R NC VS.R99PSLoad.Ma xDLThruput.PLM N.RNC VS.HSDPAPSLoad .DLThruput.PLM N.RNC VS.HSDPAPSLoad .MaxDLThruput.P LMN.RNC VS.HSUPAPSLoad .ULThruput.PLM N.RNC Counter Description Equivalent CS Erlang for RNC per Operator Maximum equivalent CS Erlang for RNC per Operator Uplink PS R99 Traffic for RNC per Operator Maximum Uplink PS R99 Traffic for RNC per Operator Downlink PS R99 Traffic for RNC per Operator Maximum Downlink PS R99 Traffic for RNC per Operator Downlink PS HSDPA Traffic for RNC per Operator Maximum Downlink PS HSDPA Traffic for RNC per Operator Uplink PS HSUPA Traffic for RNC per Operator Original Release Earlier than V900R011 Earlier than V900R011
67192511
67204145
Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67193010
67204146
67193013
67204147
67193016
67204148
Issue 01 (2013-05-04)
17
Counter ID 67193019
Counter Name VS.HSUPAPSLoad .MaxULThruput.P LMN.RNC VS.MBMSPSLoad. DLThruput.PLMN .RNC VS.MBMSPSLoad. MaxDLThruput.P LMN.RNC VS.AMR.Erlang.E quiv.PLMN.RNC VS.VP.Erlang.Equi v.PLMN.RNC
Counter Description Maximum Uplink PS HSUPA Traffic for RNC per Operator Downlink PS MBMS Traffic for RNC per Operator Maximum Downlink PS MBMS Traffic for RNC per Operator Equivalent Erlang of CS AMR Service for RNC per Operator Equivalent Erlang of 64kbit/s CS Service for RNC per Operator Number of Cell_DCH UEs in PS Domain for RNC per Operator Maximum Total Throughout of UL and DL PS Services per Operator for RNC Average Total Throughput of UL and DL PS Services per Operator for RNC Number of Cell_FACH UEs in PS Domain for RNC per Operator
Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67204149
67193022
67204835
67204836
67204840
VS.PS.CellDchUEs. PLMN
73394023
VS.PSLoad.MaxTh ruput.PLMN.RNC
V900R012
73410502
VS.PSLoad.Thrup ut.PLMN.RNC
V900R012
73440109
VS.PS.CellFachUE s.PLMN
V900R012
None
1.1.4.1 Equivalent Erlang of CS Domain of RNC for each Operator

Counters
Counter ID 67203962 Counter Name VS.CSLoad.Erlang.Equiv.P LMN.RNC Counter Description Equivalent CS Erlang for RNC per Operator
Description
This measurement item provides the equivalent Erlang values of all services in the CS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the equivalent Erlang values of all services in the CS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the mean sample (divide the accumulated value by the sampling times), include the equivalent Erlang of all radio links of Soft Handover.Each time a CS domain service is admitted, the RNC converts its rate to the equivalent Erlang, and then increases the equivalent Erlang of the CS domain of the RNC. Each time a CS domain service is released, the RNC decreases the equivalent Erlang of the CS domain of the RNC.
Formula
None
Unit
Erl
Related Features
Counter Name VS.CSLoad.Erlang.Equiv.P LMN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.2 Maximum Equivalent Erlang of CS Domain of RNC for each Operator
Issue 01 (2013-05-04)
19
Counters
Counter ID 67192511 Counter Name VS.CSLoad.MaxErlang.Equ iv.PLMN.RNC Counter Description Maximum equivalent CS Erlang for RNC per Operator
Description
This measurement item provides the maximum equivalent Erlang values of all services in the CS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the equivalent Erlang values of all services in the CS domain for each Operator every five seconds and calculates the maximum, include the equivalent Erlang of all radio links of Soft Handover.Each time a CS domain service is admitted, the RNC converts its rate to the equivalent Erlang, and then increases the equivalent Erlang of the CS domain of the RNC. Each time a CS domain service is released, the RNC decreases the equivalent Erlang of the CS domain of the RNC.
Formula
None
Unit
Erl
Related Features
Counter Name VS.CSLoad.MaxErlang.Equ iv.PLMN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.3 Uplink Traffic of R99 PS Domain of RNC for each Operator Counters
Counter ID 67204145 Counter Name VS.R99PSLoad.ULThruput. PLMN.RNC
Counter Description Uplink PS R99 Traffic for RNC per Operator

20
Issue 01 (2013-05-04)
Description
This measurement item provides the uplink traffic of all the R99 services in the PS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the uplink traffic values (in kbit/s) of all the R99 services in the PS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the mean sample (divide the accumulated value by the sampling times).The mean uplink traffic of all the R99 services in the PS domain is the traffic measured at the RLC layer. The RLC header data is not included and the soft handover traffic is included.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.R99PSLoad.ULThruput. PLMN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.4 Maximum Uplink Traffic of R99 PS Domain of RNC for each Operator Counters
Counter ID 67193010 Counter Name VS.R99PSLoad.MaxULThr uput.PLMN.RNC Counter Description Maximum Uplink PS R99 Traffic for RNC per Operator
Description
This measurement item provides the maximum uplink traffic of all the R99 services in the PS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the uplink traffic values (in kbit/s) of all the R99 services in the PS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the maximum sample value.The mean uplink traffic of all the R99 services in the PS domain is the traffic measured at the RLC layer. The RLC header data is not included and the soft handover traffic is included.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.R99PSLoad.MaxULThr uput.PLMN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.5 Downlink Traffic of R99 PS Domain of RNC for each Operator Counters
Counter ID 67204146 Counter Name VS.R99PSLoad.DLThruput. PLMN.RNC Counter Description Downlink PS R99 Traffic for RNC per Operator
Description
This measurement item provides the downlink traffic of all the R99 services in the PS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the downlink traffic values (in kbit/s) of all the R99 services in the PS domain for each Operatorevery five seconds. At the end of the measurement period, the RNC calculates the mean sample (divide the accumulated value by the sampling times).The mean downlink traffic of all the R99 services in the PS domain is the traffic measured at the RLC layer. The RLC header data is not included and the soft handover traffic is included.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.R99PSLoad.DLThruput. PLMN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.6 Maximum Downlink Traffic of R99 PS Domain of RNC for each Operator Counters
Counter ID 67193013 Counter Name VS.R99PSLoad.MaxDLThr uput.PLMN.RNC Counter Description Maximum Downlink PS R99 Traffic for RNC per Operator
Description
This measurement item provides the maximum downlink traffic of all the R99 services in the PS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the downlink traffic values (in kbit/s) of all the R99 services in the PS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the maximum sample value.The mean downlink traffic of all the R99 services in the PS domain is the traffic measured at the RLC layer. The RLC header data is not included and the soft handover traffic is included.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.R99PSLoad.MaxDLThr uput.PLMN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.7 Downlink Traffic of HSDPA PS Domain of RNC for each Operator Counters
Counter ID 67204147 Counter Name VS.HSDPAPSLoad.DLThru put.PLMN.RNC Counter Description Downlink PS HSDPA Traffic for RNC per Operator
Description
This measurement item provides the downlink traffic of all the HSDPA services in the PS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the downlink traffic values (in kbit/s) of all the HSDPA services in the PS domain for each Operator every five seconds.At the end of the measurement period, the RNC calculates the mean sample (divide the accumulated value by the sampling times).The downlink traffic of all the HSDPA services in the PS domain refers to the traffic measured at the RLC layer. The data does not include the RLC head data.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
24
Related Features
Counter Name VS.HSDPAPSLoad.DLThru put.PLMN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.8 Maximum Downlink Traffic of HSDPA PS Domain of RNC for each Operator Counters
Counter ID 67193016 Counter Name VS.HSDPAPSLoad.MaxDL Thruput.PLMN.RNC Counter Description Maximum Downlink PS HSDPA Traffic for RNC per Operator
Description
This measurement item provides the maximum downlink traffic of all the HSDPA services in the PS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the downlink traffic values (in kbit/s) of all the HSDPA services in the PS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the maximum sample value.The downlink traffic of all the HSDPA services in the PS domain refers to the traffic measured at the RLC layer. The data does not include the RLC head data.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
25
Related Features
Counter Name VS.HSDPAPSLoad.MaxDL Thruput.PLMN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.9 Uplink Traffic of HSUPA PS Domain of RNC for each Operator Counters
Counter ID 67204148 Counter Name VS.HSUPAPSLoad.ULThru put.PLMN.RNC Counter Description Uplink PS HSUPA Traffic for RNC per Operator
Description
This measurement item provides the uplink traffic of all the HSUPA services in the PS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the uplink traffic values (in kbit/s) of all the HSUPA services in the PS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the mean sample (divide the accumulated value by the sampling times).The mean uplink traffic of all the HSUPA services in the PS domain is the traffic measured at the RLC layer. The RLC header data is not included and the soft handover traffic is included.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
26
Related Features
Counter Name VS.HSUPAPSLoad.ULThru put.PLMN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.10 Maximum Uplink Traffic of HSUPA PS Domain of RNC for each Operator Counters
Counter ID 67193019 Counter Name VS.HSUPAPSLoad.MaxUL Thruput.PLMN.RNC Counter Description Maximum Uplink PS HSUPA Traffic for RNC per Operator
Description
This measurement item provides the maximum uplink traffic of all the HSUPA services in the PS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the uplink traffic values (in kbit/s) of all the HSUPA services in the PS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the maximum sample value.The mean uplink traffic of all the HSUPA services in the PS domain is the traffic measured at the RLC layer. The RLC header data is not included and the soft handover traffic is included.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
27
Related Features
Counter Name VS.HSUPAPSLoad.MaxUL Thruput.PLMN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.11 Downlink Traffic of MBMS or IMB PS Domain of RNC for each Operator Counters
Counter ID 67204149 Counter Name VS.MBMSPSLoad.DLThru put.PLMN.RNC Counter Description Downlink PS MBMS Traffic for RNC per Operator
Description
This measurement item provides the downlink traffic of all the MBMS or IMB services in the PS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the downlink traffic values (in kbit/s) of all the MBMS or IMB services in the PS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the mean sample (divide the accumulated value by the sampling times).The downlink traffic of all the MBMS or IMB services in the PS domain refers to the traffic measured at the RLC layer. The data does not include the RLC head data.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
28
Related Features
Counter Name VS.MBMSPSLoad.DLThru put.PLMN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.12 Maximum Downlink Traffic of MBMS or IMB PS Domain of RNC for each Operator Counters
Counter ID 67193022 Counter Name VS.MBMSPSLoad.MaxDL Thruput.PLMN.RNC Counter Description Maximum Downlink PS MBMS Traffic for RNC per Operator
Description
This measurement item provides the maximum downlink traffic of all the MBMS or IMB services in the PS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the downlink traffic values (in kbit/s) of all the MBMS or IMB services in the PS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the maximum sample value.The downlink traffic of all the MBMS or IMB services in the PS domain refers to the traffic measured at the RLC layer. The data does not include the RLC head data.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
29
Related Features
Counter Name VS.MBMSPSLoad.MaxDL Thruput.PLMN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 WRFD-010616 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control MBMS Introduction Package
1.1.4.13 Equivalent Erlang of CS Domain AMR Service of RNC for each Operator Counters
Counter ID 67204835 Counter Name VS.AMR.Erlang.Equiv.PL MN.RNC Counter Description Equivalent Erlang of CS AMR Service for RNC per Operator
Description
This measurement item provides the equivalent Erlang values of AMR services(narrowband and wideband AMR services)in the CS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the equivalent Erlang values of AMR services in the CS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the mean sample (divide the accumulated value by the sampling times), include the equivalent Erlang of all radio links of Soft Handover. Each time a CS domain AMR service is admitted, the RNC converts its rate to the equivalent Erlang, and then increases the equivalent Erlang of the CS domain of the RNC. Each time a CS domain AMR service is released, the RNC decreases the equivalent Erlang of the CS domain of the RNC.
Formula
None
Unit
Erl
Issue 01 (2013-05-04)
30
Related Features
Counter Name VS.AMR.Erlang.Equiv.PL MN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.14 Equivalent Erlang of CS Domain CS 64kbit/s Conversational Service of RNC for each Operator Counters
Counter ID 67204836 Counter Name VS.VP.Erlang.Equiv.PLMN .RNC Counter Description Equivalent Erlang of 64kbit/ s CS Service for RNC per Operator
Description
This measurement item provides the equivalent Erlang values of CS 64kbit/s Conversational Services in the CS domain of the RNC for each Operator. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the equivalent Erlang values of CS 64kbit/s Conversational Services in the CS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the mean sample (divide the accumulated value by the sampling times), include the equivalent Erlang of all radio links of Soft Handover. Each time a CS domain CS 64kbit/s Conversational Service is admitted, the RNC converts its rate to the equivalent Erlang, and then increases the equivalent Erlang of the CS domain of the RNC. Each time a CS domain CS 64kbit/s Conversational Service is released, the RNC decreases the equivalent Erlang of the CS domain of the RNC.
Formula
None
Unit
Erl
Issue 01 (2013-05-04)
31
Related Features
Counter Name VS.VP.Erlang.Equiv.PLMN .RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.15 The Number of Cell_DCH UEs in PS Domain in RNC Counters

Counter ID 67204840 Counter Name VS.PS.CellDchUEs.PLMN Counter Description Number of Cell_DCH UEs in PS Domain for RNC per Operator
Description
This measurement item provides the mean number of Cell_DCH UEs in the PS domain of the RNC for each Operator.
Measurement point
The RNC periodically takes the samples of the number of Cell_DCH UEs in the PS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the mean sample (divide the accumulated value by the sampling times). When the Cell_DCH UEs join the PS operation for the first time, add the number of UEs. When all the PS operations are released, subtract the number of UEs
Formula
None
Unit
None
Issue 01 (2013-05-04)
32
Related Features
Counter Name VS.PS.CellDchUEs.PLMN Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.16 Maximum Total Throughout of UL and DL PS Services per Operator for RNC Counters
Counter ID 73394023 Counter Name VS.PSLoad.MaxThruput.PL MN.RNC Counter Description Maximum Total Throughout of UL and DL PS Services per Operator for RNC
Description
This counter provides the maximum total throughout of UL and DL PS services of an operator in the RNC. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The total throughput (unit: Kbit/s) of UL and DL PS services of the operator in the RNC is sampled periodically every five seconds. At the end of the measurement period, the maximum throughput is obtained. The RLC header is not included and the retransmission data is included in the counter.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
33
Related Features
Counter Name VS.PSLoad.MaxThruput.PL MN.RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.17 Average Total Throughput of UL and DL PS Services per Operator for RNC Counters
Counter ID 73410502 Counter Name VS.PSLoad.Thruput.PLMN. RNC Counter Description Average Total Throughput of UL and DL PS Services per Operator for RNC
Description
This counter provides the average total throughput of UL and DL PS services of an operator in the RNC. The item is measured only when the RAN sharing function or MOCN function is switched on.
Measurement point
The total throughput of UL and DL PS services of an operator in the RNC is sampled and accumulated periodically every five seconds. At the end of the measurement period, the average throughput is obtained as follows: dividing the accumulated throughput by the sampling times. The RLC header is not included and the retransmission data is included in the counter.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
34
Related Features
Counter Name VS.PSLoad.Thruput.PLMN. RNC Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.1.4.18 The Number of Cell_FACH UEs in PS Domain in RNC Counters

Counter ID 73440109 Counter Name VS.PS.CellFachUEs.PLMN Counter Description Number of Cell_FACH UEs in PS Domain for RNC per Operator
Description
This measurement item provides the mean number of Cell_FACH UEs in the PS domain of the RNC for each Operator.
Measurement point
The RNC periodically takes the samples of the number of Cell_FACH UEs in the PS domain for each Operator every five seconds. At the end of the measurement period, the RNC calculates the mean sample (divide the accumulated value by the sampling times). When the Cell_FACH UEs join the PS operation for the first time, add the number of UEs. When all the PS operations are released, subtract the number of UEs.
Formula
None
Unit
None
Issue 01 (2013-05-04)
35
Related Features
Counter Name VS.PS.CellFachUEs.PLMN Feature ID WRFD-021304 WRFD-021311 WRFD-02130404 Feature Name RAN Sharing Introduction Package MOCN Introduction Package Independent License Control
1.2 Measurement of CPUS Performance(CPUS)

Overview
The CPU for Service (CPUS) measurement provides the performance of the SPU board in the Main Processing Subrack (MPS) or Extended Processing Subrack (EPS) of the RNC. SPU boards can be divided into two types: main control SPU boards and non-main control SPU boards. In addition to processing UMTS control-plane services, main control SPU boards also manage the user-plane, control-plane, and transmission resources of the UMTS. Non-main control SPU boards only process UMTS control-plane services. Subsystem 0 of the main control SPU board is the Main Processing Unit (MPU) subsystem. It manages the user-plane, control-plane, and transmission resources of the UMTS. Other subsystems of the main control SPU board and all subsystems of non-main control SPU boards are CPUS subsystems. They process control-plane services. Different types of SPU boards have different number of subsystems. For example, each SPUa board has four subsystems, and each SPUb board has eight subsystems. In addition, an SPUa subsystem and an SPUb subsystem have different processing capabilities. The CPUS measurement is performed only to assess the performance of a single CPUS subsystem.
FunctionSubSets
FunctionSubSet CPUS FunctionSubSet Name Measurement related to CPUS
1.2.1 Measurement related to CPUS(CPUS)

Overview
The CPUS subsystem measurement provides the performance of a single CPUS in terms of the number of setup and release times of different services, and the number of times that each type of messages are discarded due to flow control.
If the value of a flow control-related counter increases dramatically in a period, check whether a signaling storm has occurred in the corresponding period.
Counters
Counter ID 67203413 Counter Name VS.CSLoad.Erlang .Equiv.CPUS VS.RRC.AttConnE stab.CPUS VS.RRC.SuccConn Estab.CPUS Counter Description Equivalent CS Conversational Erlang for CPUS Number of RRC Connection Requests for CPUS Number of Successful RRC Connection Establishments for CPUS Number of CS AMR RAB Establishing Requests for CPUS Number of CS AMR RABs Successfully Established for CPUS Number of CS 64kbit/s RAB Establishing Requests for CPUS Number of CS 64kbit/s RABs Successfully Established for CPUS Number of HSDPA RAB Establishing Requests for CPUS Number of HSDPA RABs Successfully Established for CPUS Number of HSUPA RAB Establishing Requests for CPUS Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67193077
67193078
67193079
VS.RAB.AttEstab. AMR.CPUS VS.RAB.SuccEstab .AMR.CPUS
67193080
67193081
VS.RAB.AttEstab. CS64.CPUS
67193082
VS.RAB.SuccEstab .CS64.CPUS
67193083
VS.HSDPA.RAB.A ttEstab.CPUS VS.HSDPA.RAB.S uccEstab.CPUS
67193084
67193085
VS.HSUPA.RAB.A ttEstab.CPUS
Issue 01 (2013-05-04)
37
Counter ID 67193086
Counter Name VS.HSUPA.RAB.S uccEstab.CPUS
Counter Description Number of HSUPA RABs Successfully Established for CPUS Number of PS RAB Establishing Requests for CPUS Number of PS RABs Successfully Established for CPUS Number of Abnormally Released CS AMR RABs for CPUS Number of Normally Released CS AMR RABs for CPUS Number of Abnormally Released CS 64kbit/s RABs for CPUS Number of Normally Released CS 64kbit/s RABs for CPUS Number of Abnormally Released PS RABs for CPUS Number of Normally Released PS RABs for CPUS Number of CBS Requests Discarded Due to Flow Control for CPUS Subsystem Duration of CBS Flow Control for CPUS Subsystem
Original Release Earlier than V900R011
67193087
VS.RAB.AttEstabP S.CPUS VS.RAB.SuccEstab PS.CPUS
67193088
67193089
VS.RAB.AbnormR el.AMR.CPUS
67193090
VS.RAB.NormRel. AMR.CPUS VS.RAB.AbnormR el.CS64.CPUS
67193091
67193092
VS.RAB.NormRel. CS64.CPUS VS.RAB.AbnormR el.PS.CPUS
67193093
67193094
VS.RAB.NormRel. PS.CPUS VS.CBS.FC.Disc.N um.CPUS
Earlier than V900R011 V900R012
73421896
73421897
VS.CBS.FC.Disc.Ti me.CPUS
V900R012
Issue 01 (2013-05-04)
38
Counter ID 73421898
Counter Name VS.Paging.FC.Disc. Num.CPUS
Counter Description Number of Paging Messages Discarded Due to Flow Control for CPUS Subsystem Duration of Paging Message Flow Control for CPUS Subsystem Number of Cell Update Requests Discarded Due to Flow Control for CPUS Subsystem Duration of Cell Update Flow Control for CPUS Subsystem Number of Discarded RRC Connection Requests Due to Burst Traffic for CPUS Subsystem Number of Discarded RRC Connection Requests Due to MPU Overload for CPUS Subsystem Number of Discarded RRC Connection Requests Due to RRC Queue Overflow for CPUS Subsystem Number of Discarded RRC Connection Requests Due to High CPU Usage for CPUS Subsystem Number of LowPriority RRC Requests Discarded Due to Flow Control for CPUS Subsystem
Original Release V900R012
73421899
VS.Paging.FC.Disc. Time.CPUS
V900R012
73421900
VS.CU.FC.Disc.Nu m.CPUS
V900R012
73421901
VS.CU.FC.Disc.Ti me.CPUS VS.RRC.FC.Disc.N um.CallShock.CPU S
V900R012
73423464
V900R013
73423465
VS.RRC.FC.Disc.N um.MPU.CPUS
V900R013
73423466
VS.RRC.FC.Disc.N um.RRCQueue.CP US
V900R013
73423467
VS.RRC.FC.Disc.N um.CPU.CPUS
V900R013
73421890
VS.LowPriRRC.F C.Disc.Num.CPUS
V900R012
Issue 01 (2013-05-04)
39
Counter ID 73421891
Counter Name VS.NormPriRRC.F C.Disc.Num.CPUS
Counter Description Number of NormalPriority RRC Requests Discarded Due to Flow Control for CPUS Subsystem Number of HighPriority RRC Requests Discarded Due to Flow Control for CPUS Subsystem Duration of Rejection of LowPriority RRC Requests Due to Flow Control for CPUS Subsystem Duration of Rejection of NormalPriority RRC Requests Due to Flow Control for CPUS Subsystem Duration of Rejection of HighPriority RRC Requests Due to Flow Control for CPUS Subsystem Number of LowPriority CELL UPDATE Messages Discarded Because CPU Usage Exceeds the Threshold for CPUS Subsystem Number of MediumPriority CELL UPDATE Messages Discarded Because CPU Usage Exceeds the Threshold for CPUS Subsystem
73421892
VS.HighPriRRC.F C.Disc.Num.CPUS
V900R012
73421893
VS.LowPriRRC.F C.Disc.Time.CPUS
V900R012
73421894
VS.NormPriRRC.F C.Disc.Time.CPUS
V900R012
73421895
VS.HighPriRRC.F C.Disc.Time.CPUS
V900R012
73423921
VS.LowPriCu.FC. Disc.Num.CPU
V900R014
73423923
VS.MidPriCu.FC. Disc.Num.CPU
V900R014
Issue 01 (2013-05-04)
40
Counter ID 73423924
Counter Name VS.HighPriCu.FC. Disc.Num.CPU
Counter Description Number of HighPriority CELL UPDATE Messages Discarded Because CPU Usage Exceeds the Threshold for CPUS Subsystem Number of LowPriority CELL UPDATE Messages Discarded Due to RRC Queue Overflow for CPUS Subsystem Number of MediumPriority CELL UPDATE Messages Discarded Due to RRC Queue Overflow for CPUS Subsystem Number of HighPriority CELL UPDATE Messages Discarded Due to RRC Queue Overflow for CPUS Subsystem Number of Discarded UL Event 4A Measurement Reports on PS BE Traffic in the CELL_DCH State in a CPUS Number of Discarded DL Event 4A Measurement Reports on PS BE Traffic in the CELL_DCH State in a CPUS
73423925
VS.LowPriCu.FC. Disc.Num.Queue
V900R014
73423926
VS.MidPriCu.FC. Disc.Num.Queue
V900R014
73423927
VS.HighPriCu.FC. Disc.Num.Queue
V900R014
73423928
VS.Traffic.Report4 A.CellDch.Disc.Nu m.UpLink.FC
V900R014
73423929
VS.Traffic.Report4 A.CellDch.Disc.Nu m.DownLink.FC
V900R014
Issue 01 (2013-05-04)
41
Counter ID 73423930
Counter Name VS.Throughput.Re port4A.Disc.Num. UpLink.FC
Counter Description Number of Discarded UL Event 4A Measurement Reports on Throughput for UEs in the CELL_DCH State in a CPUS Number of Discarded UL Event 4A Measurement Reports on PS BE Traffic in the CELL_FACH State in a CPUS Number of Discarded DL Event 4A Measurement Reports on PS BE Traffic in the CELL_FACH State in a CPUS Number of RRC CONNECTION REQUESTS Under Flow Control Due to High CPU Usage for CPUS Subsystem Number of RRC CONNECTION REQUESTS Under Flow Control Due to RRC Queue Overflow for CPUS Subsystem Number of RRC CONNECTION REQUESTS Under Flow Control Due to MPU Overload for CPUS Subsystem
73423931
VS.Traffic.Report4 A.CellFach.Disc.Nu m.UpLink.FC
V900R014
73423932
VS.Traffic.Report4 A.CellFach.Disc.Nu m.DownLink.FC
V900R014
73424215
VS.RRC.FC.Num. CPU.CPUS
V900R014
73424216
VS.RRC.FC.Num. RRCQueue.CPUS
V900R014
73424217
VS.RRC.FC.Num. MPU.CPUS
V900R014
Issue 01 (2013-05-04)
42
Counter ID 73424218
Counter Name VS.RRC.FC.Num. CallShock.CPUS
Counter Description Number of RRC CONNECTION REQUESTS Under Flow Control Due to Burst Traffic for CPUS Subsystem Number of RRC CONNECTION REQUESTS for CS Services Under Flow Control Due to High CPU Usage for CPUS Subsystem Number of RRC CONNECTION REQUESTS for CS Services Under Flow Control Due to RRC Queue Overflow for CPUS Subsystem Number of RRC CONNECTION REQUESTS for CS Services Under Flow Control Due to MPU Overload for CPUS Subsystem Number of RRC CONNECTION REQUESTS for CS Services Under Flow Control Due to Burst Traffic for CPUS Subsystem Number of RRC CONNECTION REQUESTS for CS Services in a CPUS Subsystem Under Flow Control Triggered by Interface-Board CPU Overload
73424219
VS.RRC.CONV.F C.Num.CPU.CPUS
V900R014
73424220
VS.RRC.CONV.F C.Num.RRCQueue .CPUS
V900R014
73424221
VS.RRC.CONV.F C.Num.MPU.CPU S
V900R014
73424222
VS.RRC.CONV.F C.Num.CallShock. CPUS
V900R014
73424482
VS.RRC.CONV.F C.Num.INT.CPUS
V900R014
Issue 01 (2013-05-04)
43
Counter ID 73424483
Counter Name VS.RRC.FC.Num.I NT.CPUS
Counter Description Number of RRC CONNECTION REQUESTS in a CPUS Subsystem Under Flow Control Triggered by Interface-Board CPU Overload Number of Discarded IurInterface Uplink Signalling Messages in a CPUS Subsystem Under Flow Control Triggered by CPU Overload Number of Discarded IurInterface Downlink Signalling Messages in a CPUS Subsystem Under Flow Control Triggered by CPU Overload
73424484
VS.IurUpLinkSig. Disc.Num.CPU.CP US
V900R014
73424485
VS.IurDownLinkSi g.Disc.Num.CPU.C PUS
V900R014
Counter VS.CU.FC.Disc.Num.CPUS Sub Counter VS.LowPriCu.FC.Disc.Num.CPU VS.MidPriCu.FC.Disc.Num.CPU VS.HighPriCu.FC.Disc.Num.CPU VS.LowPriCu.FC.Disc.Num.Queue VS.MidPriCu.FC.Disc.Num.Queue VS.HighPriCu.FC.Disc.Num.Queue VS.Throughput.Report4A.Disc.Num.UpLin k.FC VS.RRC.FC.Disc.Num.CPU.CPUS VS.Traffic.Report4A.CellDch.Disc.Num.U pLink.FC VS.RRC.CONV.FC.Num.CPU.CPUS VS.RRC.CONV.FC.Num.MPU.CPUS
Issue 01 (2013-05-04)
44
Counter VS.RRC.FC.Disc.Num.RRCQueue.CPUS VS.RRC.FC.Disc.Num.CallShock.CPUS VS.RRC.FC.Num.INT.CPUS
Sub Counter VS.RRC.CONV.FC.Num.RRCQueue.CPU S VS.RRC.CONV.FC.Num.CallShock.CPUS VS.RRC.CONV.FC.Num.INT.CPUS
1.2.1.1 Measurement of CS-Domain Equivalent Erlang of Each Subsystem in the RNC Counters
Counter ID 67203413 Counter Name VS.CSLoad.Erlang.Equiv.C PUS Counter Description Equivalent CS Conversational Erlang for CPUS
Description
This measurement counter provides the equivalent Erlang of all CS-domain services of each subsystem in the RNC.
Measurement point
The RNC takes samples on the equivalent Erlang of all CS-domain services of each subsystem in the RNC every five seconds. At the end of the measurement period, the RNC divides the accumulated value of all sampling data in the measurement period by the number of sampling times to obtain the equivalent Erlang of all CS-domain services of each subsystem in the RNC, include the equivalent Erlang of all radio links of Soft Handover.When a CS-domain service accesses the RNC, the service rate is converted into equivalent Erlang, and then the CS-domain equivalent Erlang of the corresponding subsystem in the current RNC is increased. When a CSdomain service is released from the RNC, the service rate is converted into equivalent Erlang, and then the Erlang of the corresponding subsystem in the current RNC is decreased.
Formula
None
Unit
Erl
Issue 01 (2013-05-04)
45
Related Features
Counter Name VS.CSLoad.Erlang.Equiv.C PUS Feature ID WRFD-040100 Feature Name Flow Control
1.2.1.2 Number of RRC Connection Requests in the CPUS subsystem Counters

Counter ID 67193077 Counter Name VS.RRC.AttConnEstab.CP US Counter Description Number of RRC Connection Requests for CPUS
Description
This measurement counter provides the number of RRC CONNECTION REQUEST messages processed by the RNC in the CPUS subsystem, excluding cases that such request is rejected because of redirection based on specific services, redirection based on inter-RAT and interfrequency distance, or redirection based on macro & micro joint inter-frequency.
Measurement point
At point A in Figure, after the RNC receives a RRC CONNECTION REQUEST message from the UE, if the message is processed by the RNC (that is, the RNC requests a resource and attempts to set up the RRC connection) and the message is not repeatedly reported by the same UE, excluding cases that such request is rejected because of redirection based on specific services, redirection based on inter-RAT and inter-frequency distance, or redirection based on macro & micro joint inter-frequency, the measurement is triggered in the CPUS subsystem.
Issue 01 (2013-05-04)
46
Figure 1-8 RRC connection setup process
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnEstab.CP US Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.2.1.3 Number of Successful RRC Connection Setups in the CPUS subsystem
Issue 01 (2013-05-04)
47
Counters
Counter ID 67193078 Counter Name VS.RRC.SuccConnEstab.C PUS Counter Description Number of Successful RRC Connection Establishments for CPUS
Description
This measurement counter provides the number of RRC CONNECTION SETUP COMPLETE messages received by the RNC in the CPUS subsystem.
Measurement point
The measurement is triggered at point C, as shown in Figure . After the RNC receives a RRC CONNECTION SETUP COMPLETE message from an UE, the measurement is triggered in the corresponding CPUS subsystem. Figure 1-9 RRC connection setup process
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.SuccConnEstab.C PUS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.2.1.4 Number of CS RAB Requests in the CPUS subsystem Counters

Counter ID 67193079 Counter Name VS.RAB.AttEstab.AMR.CP US VS.RAB.AttEstab.CS64.CP US VS.HSDPA.RAB.AttEstab. CPUS VS.HSUPA.RAB.AttEstab. CPUS VS.RAB.AttEstabPS.CPUS Counter Description Number of CS AMR RAB Establishing Requests for CPUS Number of CS 64kbit/s RAB Establishing Requests for CPUS Number of HSDPA RAB Establishing Requests for CPUS Number of HSUPA RAB Establishing Requests for CPUS Number of PS RAB Establishing Requests for CPUS
67193081
67193083
67193085
67193087
Description
These measurement counters provide the number of RAB requests in the CPUS subsystem according to the service type.The counter VS.RAB.AttEstab.AMR.CPUS includes narrowband and wideband AMR services.
Measurement point
The measurement is triggered at point A in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN, it measures the corresponding counter in the corresponding CPUS based on the service type.
Issue 01 (2013-05-04)
49
Figure 1-10 RAB setup process
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstab.AMR.CP US VS.RAB.AttEstab.CS64.CP US VS.HSDPA.RAB.AttEstab. CPUS Feature ID WRFD-010501 WRFD-010501 WRFD-01061008 WRFD-010630 Feature Name Conversational QoS Class Conversational QoS Class Interactive and Background Traffic Class on HSDPA Streaming Traffic Class on HSDPA VS.HSUPA.RAB.AttEstab. CPUS WRFD-01061206 WRFD-010632 Interactive and Background Traffic Class on HSUPA Streaming Traffic Class on HSUPA
Counter Name VS.RAB.AttEstabPS.CPUS
Feature ID WRFD-010510
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.2.1.5 Number of CS RABs successfully established in the CPUS subsystem Counters

Counter ID 67193080 Counter Name VS.RAB.SuccEstab.AMR.C PUS VS.RAB.SuccEstab.CS64.C PUS VS.HSDPA.RAB.SuccEstab .CPUS VS.HSUPA.RAB.SuccEstab .CPUS VS.RAB.SuccEstabPS.CPU S Counter Description Number of CS AMR RABs Successfully Established for CPUS Number of CS 64kbit/s RABs Successfully Established for CPUS Number of HSDPA RABs Successfully Established for CPUS Number of HSUPA RABs Successfully Established for CPUS Number of PS RABs Successfully Established for CPUS
67193082
67193084
67193086
67193088
Description
These counters provide the number of times that a RAB is successfully set up in the CPUS based on the service type.The counter VS.RAB.SuccEstab.AMR.CPUS includes narrowband and wideband AMR services.
Measurement point
The measurement is triggered at point B in the figure. After the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE and sends a RAB ASSIGNMENT RESPONSE message to the CN, it measures the corresponding counter in the corresponding CPUS based on the service type
Issue 01 (2013-05-04)
51
Figure 1-11 RAB setup process
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstab.AMR.C PUS VS.RAB.SuccEstab.CS64.C PUS VS.HSDPA.RAB.SuccEstab .CPUS Feature ID WRFD-010501 WRFD-010501 WRFD-01061008 WRFD-010630 Feature Name Conversational QoS Class Conversational QoS Class Interactive and Background Traffic Class on HSDPA Streaming Traffic Class on HSDPA VS.HSUPA.RAB.SuccEstab .CPUS WRFD-01061206 WRFD-010632 Interactive and Background Traffic Class on HSUPA Streaming Traffic Class on HSUPA
Counter Name VS.RAB.SuccEstabPS.CPU S
1.2.1.6 Number of RABs Abnormally Released in the CPUS subsystem Counters

Counter ID 67193089 Counter Name VS.RAB.AbnormRel.AMR. CPUS VS.RAB.AbnormRel.CS64. CPUS VS.RAB.AbnormRel.PS.CP US Counter Description Number of Abnormally Released CS AMR RABs for CPUS Number of Abnormally Released CS 64kbit/s RABs for CPUS Number of Abnormally Released PS RABs for CPUS
67193091
67193093
Description
These measurement counters provide the number of RAB abnormal releases triggered by the RNC in the CPUS subsystem on the basis of domain type and service attribute. The abnormal release here refers to all RAB releases except the one made by the RNC normally.The counter VS.RAB.AbnormRel.AMR.CPUS includes narrowband and wideband AMR services.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items by the service type in the corresponding CPUS subsystem.
Issue 01 (2013-05-04)
53
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items by the service type in the corresponding CPUS subsystem.
Issue 01 (2013-05-04)
54
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items by the service type in the corresponding CPUS subsystem.
Issue 01 (2013-05-04)
55
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.AMR. CPUS VS.RAB.AbnormRel.CS64. CPUS VS.RAB.AbnormRel.PS.CP US Feature ID WRFD-010501 WRFD-010501 WRFD-010510 Feature Name Conversational QoS Class Conversational QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.2.1.7 Number of RABs Normally Released in the CPUS subsystem

Counters
Counter ID 67193090 Counter Name VS.RAB.NormRel.AMR.CP US VS.RAB.NormRel.CS64.CP US VS.RAB.NormRel.PS.CPU S Counter Description Number of Normally Released CS AMR RABs for CPUS Number of Normally Released CS 64kbit/s RABs for CPUS Number of Normally Released PS RABs for CPUS
67193092
67193094
Description
These measurement counters provide the number of RABs normally released in the CPUS subsystem on the basis of service type. Here, normal RAB release refers to the RAB release triggered by the CN, the RAB release triggered by the RNC with the cause of User Inactivity, and the signaling connection release triggered by the UE. The counter VS.RAB.NormRel.AMR.CPUS includes narrowband and wideband AMR services.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release", the RNC measures these items by the service type in the corresponding CPUS subsystem. Figure 1-15 Iu release procedure
Issue 01 (2013-05-04)
57
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the RAB ASSIGNMENT REQUEST message indicates the reason is "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release" ,the RNC measures these items by the service type in the corresponding CPUS subsystem. Figure 1-16 RAB assignment release procedure
Formula
None
Unit
None
Issue 01 (2013-05-04)
58
Related Features
Counter Name VS.RAB.NormRel.AMR.CP US VS.RAB.NormRel.CS64.CP US VS.RAB.NormRel.PS.CPU S Feature ID WRFD-010501 WRFD-010501 WRFD-010510 Feature Name Conversational QoS Class Conversational QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.2.1.8 Number of CBS Requests Discarded Due to Flow Control for CPUS Subsystem Counters
Counter ID 73421896 Counter Name VS.CBS.FC.Disc.Num.CPU S Counter Description Number of CBS Requests Discarded Due to Flow Control for CPUS Subsystem
Description
This counter provides the number of times that a cell broadcast service (CBS) request message is discarded due to flow control.
Measurement point
When receiving a data request from the CBS server, the CPUS subsystem discards the CBS request if the CPUS subsystem is under the CBS flow control. The measurement is triggered in the CPUS subsystem when the CBS request is discarded.
Formula
None
Unit
None
Issue 01 (2013-05-04)
59
Related Features
Counter Name VS.CBS.FC.Disc.Num.CPU S Feature ID WRFD-040100 Feature Name Flow Control
1.2.1.9 Duration of CBS Flow Control for CPUS Subsystem Counters

Counter ID 73421897 Counter Name VS.CBS.FC.Disc.Time.CPU S Counter Description Duration of CBS Flow Control for CPUS Subsystem
Description
This counter provides the duration of CBS flow control in the CPUS subsystem.
Measurement point
In a measurement period, the duration for which the CPUS subsystem is in the flow control state is measured. In each second, the system checks whether an CBS message is rejected because of flow control. If an CBS message is rejected in a second, the corresponding counter is incremented by one.
Formula
None
Unit
s
Related Features
Counter Name VS.CBS.FC.Disc.Time.CPU S Feature ID WRFD-040100 Feature Name Flow Control
1.2.1.10 Number of Paging Messages Discarded Due to Flow Control for CPUS Subsystem
Counters
Counter ID 73421898 Counter Name VS.Paging.FC.Disc.Num.C PUS Counter Description Number of Paging Messages Discarded Due to Flow Control for CPUS Subsystem
Description
This counter provides the number of times that a paging message is discarded due to flow control.
Measurement point
When receiving a paging message from the CN, the CPUS subsystem discards the paging message if the CPUS subsystem is under the paging flow control. The measurement is triggered in the CPUS subsystem when the paging message is discarded.
Formula
None
Unit
None
Related Features
Counter Name VS.Paging.FC.Disc.Num.C PUS Feature ID WRFD-040100 Feature Name Flow Control
1.2.1.11 Duration of Paging Message Flow Control for CPUS Subsystem Counters
Counter ID 73421899 Counter Name VS.Paging.FC.Disc.Time.C PUS Counter Description Duration of Paging Message Flow Control for CPUS Subsystem
Description
This counter provides the duration of paging message flow control in the CPUS subsystem.
Measurement point
In a measurement period, the duration for which the CPUS subsystem is in the flow control state is measured. In each second, the system checks whether an paging message is rejected because of flow control. If an paging message is rejected in a second, the corresponding counter is incremented by one.
Formula
None
Unit
s
Related Features
Counter Name VS.Paging.FC.Disc.Time.C PUS Feature ID WRFD-040100 Feature Name Flow Control
1.2.1.12 Number of Cell Update Requests Discarded Due to Flow Control for CPUS Subsystem Counters
Counter ID 73421900 Counter Name VS.CU.FC.Disc.Num.CPUS Counter Description Number of Cell Update Requests Discarded Due to Flow Control for CPUS Subsystem
Description
This counter provides the number of times that a cell update request message is discarded due to flow control.
Measurement point
When receiving a cell update request from the UE, the CPUS subsystem discards the cell update request if the CPUS subsystem is under the cell update flow control. The measurement is triggered in the CPUS subsystem when the cell update request is discarded.
Formula
None
Unit
None
Related Features
Counter Name VS.CU.FC.Disc.Num.CPUS Feature ID WRFD-040100 Feature Name Flow Control
1.2.1.13 Duration of Cell Update Flow Control for CPUS Subsystem Counters
Counter ID 73421901 Counter Name VS.CU.FC.Disc.Time.CPU S Counter Description Duration of Cell Update Flow Control for CPUS Subsystem
Description
This counter provides the duration of cell update flow control in the CPUS subsystem.
Measurement point
In a measurement period, the duration for which the CPUS subsystem is in the flow control state is measured. In each second, the system checks whether an cell update message is rejected because of flow control. If an cell update message is rejected in a second, the corresponding counter is incremented by one.
Formula
None
Unit
s
Related Features
Counter Name VS.CU.FC.Disc.Time.CPU S Feature ID WRFD-040100 Feature Name Flow Control
Issue 01 (2013-05-04)
63
1.2.1.14 Number of Discarded RRC Connection Requests Due to Various Flow Control Functions Counters
Counter ID 73423464 Counter Name VS.RRC.FC.Disc.Num.Call Shock.CPUS Counter Description Number of Discarded RRC Connection Requests Due to Burst Traffic for CPUS Subsystem Number of Discarded RRC Connection Requests Due to MPU Overload for CPUS Subsystem Number of Discarded RRC Connection Requests Due to RRC Queue Overflow for CPUS Subsystem Number of Discarded RRC Connection Requests Due to High CPU Usage for CPUS Subsystem
73423465
VS.RRC.FC.Disc.Num.MP U.CPUS
73423466
VS.RRC.FC.Disc.Num.RR CQueue.CPUS
73423467
VS.RRC.FC.Disc.Num.CPU .CPUS
Description
This counter provides the number of RRC connection requests discarded by various flow control functions in a CPUS subsystem.
Measurement point
If a CPUS subsystem is under flow control after receiving an RRC CONNECTION REQUEST message from a UE, it determines whether to set up an RRC connection according to the flow control algorithm. If the CPUS subsystem determines that an RRC connection will not be set up, it performs the following operations: If the number of RRC connection rejections in last second does not exceed the configured RRC connection rejection threshold, the RNC responds to the UE with an RRC CONNECTION REJECT message. Otherwise, the RNC discards the RRC CONNECTION REQUEST message directly and measures the number of discarded RRC connection requests based on the flow control type.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.FC.Disc.Num.Call Shock.CPUS VS.RRC.FC.Disc.Num.MP U.CPUS VS.RRC.FC.Disc.Num.RR CQueue.CPUS VS.RRC.FC.Disc.Num.CPU .CPUS Feature ID WRFD-040100 WRFD-040100 WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control Flow Control Flow Control
1.2.1.15 Number of Various Priority RRC Requests Discarded Due to Flow Control for CPUS Subsystem Counters
Counter ID 73421890 Counter Name VS.LowPriRRC.FC.Disc.Nu m.CPUS Counter Description Number of Low-Priority RRC Requests Discarded Due to Flow Control for CPUS Subsystem Number of Normal-Priority RRC Requests Discarded Due to Flow Control for CPUS Subsystem Number of High-Priority RRC Requests Discarded Due to Flow Control for CPUS Subsystem
73421891
VS.NormPriRRC.FC.Disc.N um.CPUS
73421892
VS.HighPriRRC.FC.Disc.N um.CPUS
Description
These counters provide the number of times that the RRC connection setup request messages with various priorities are discarded because of flow control.
Measurement point
If a CPUS subsystem is under flow control after receiving an RRC CONNECTION REQUEST message from a UE, it determines whether to set up an RRC connection according to the flow control algorithm. If the CPUS subsystem determines that an RRC connection will not be set up, it performs the following operations: If the current number of RRC connection rejections does not exceed the configured RRC connection rejection threshold, the RNC responds to the UE with an RRC CONNECTION
REJECT message. Otherwise, the RNC discards the RRC CONNECTION REQUEST message directly and measures the number of discarded RRC connection requests for the corresponding service priority.
Formula
None
Unit
None
Related Features
Counter Name VS.LowPriRRC.FC.Disc.Nu m.CPUS VS.NormPriRRC.FC.Disc.N um.CPUS VS.HighPriRRC.FC.Disc.N um.CPUS Feature ID WRFD-040100 WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control Flow Control
1.2.1.16 Duration of Rejection of Various Priority RRC Requests Due to Flow Control for CPUS Subsystem Counters
Counter ID 73421893 Counter Name VS.LowPriRRC.FC.Disc.Ti me.CPUS Counter Description Duration of Rejection of Low-Priority RRC Requests Due to Flow Control for CPUS Subsystem Duration of Rejection of Normal-Priority RRC Requests Due to Flow Control for CPUS Subsystem Duration of Rejection of High-Priority RRC Requests Due to Flow Control for CPUS Subsystem
73421894
VS.NormPriRRC.FC.Disc.T ime.CPUS
73421895
VS.HighPriRRC.FC.Disc.Ti me.CPUS
Issue 01 (2013-05-04)
66
Description
These counters provide the duration for which the RRC connection requests of various priorities are rejected because of flow control.
Measurement point
In a measurement period, the duration for which the CPUS subsystem is in the flow control state is measured. In each second, the system checks whether an RRC connection request is rejected because of flow control. If an RRC connection request is rejected in a second, the corresponding counter is incremented by one.
Formula
None
Unit
s
Related Features
Counter Name VS.LowPriRRC.FC.Disc.Ti me.CPUS VS.NormPriRRC.FC.Disc.T ime.CPUS VS.HighPriRRC.FC.Disc.Ti me.CPUS Feature ID WRFD-040100 WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control Flow Control
1.2.1.17 Number of Various Priority CELL_UPDATE Messages Discarded Because CPU Usage Exceeds the Threshold in a CPUS Counters
Counter ID 73423921 Counter Name VS.LowPriCu.FC.Disc.Num .CPU Counter Description Number of Low-Priority CELL UPDATE Messages Discarded Because CPU Usage Exceeds the Threshold for CPUS Subsystem Number of Medium-Priority CELL UPDATE Messages Discarded Because CPU Usage Exceeds the Threshold for CPUS Subsystem
67
73423923
VS.MidPriCu.FC.Disc.Num .CPU
Issue 01 (2013-05-04)
Counter ID 73423924
Counter Name VS.HighPriCu.FC.Disc.Nu m.CPU
Counter Description Number of High-Priority CELL UPDATE Messages Discarded Because CPU Usage Exceeds the Threshold for CPUS Subsystem
Description
These counters provide the number of CELL_UPDATE messages discarded because CPU usage exceeds the threshold in a CPU subsystem (CPUS). These counters are measured by message priority.In a later version, this counter is to be replaced by the counters VS.CU.FC.Num.CPU.OverLoad (ID 73424232) and VS.CU.CONV.FC.Num.CPU.OverLoad (ID 73424917). In the current version, this counter is reserved but cannot work. Therefore, the value of this counter is 0 and you are advised to use new counters.
Measurement point
The measurement is triggered when CELL_UPDATE messages are discarded because CPU usage or the ratio of messages waiting in a queue in the CPUS reaches the corresponding threshold. The RNC prioritizes the received CELL_UPDATE messages into high, medium, and low based on the cause value for service setup carried in the extended information element UU_CELL_UPT_V590EXT_STRU and the cause value for cell update. Figure 1-17
Formula
None
Unit
None
Related Features
Counter Name VS.LowPriCu.FC.Disc.Num .CPU VS.MidPriCu.FC.Disc.Num .CPU VS.HighPriCu.FC.Disc.Nu m.CPU Feature ID WRFD-040100 WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control Flow Control
1.2.1.18 Number of Various Priority CELL_UPDATE Messages Discarded Due to Queue-based Shaping in a CPUS Counters
Counter ID 73423925 Counter Name VS.LowPriCu.FC.Disc.Num .Queue Counter Description Number of Low-Priority CELL UPDATE Messages Discarded Due to RRC Queue Overflow for CPUS Subsystem Number of Medium-Priority CELL UPDATE Messages Discarded Due to RRC Queue Overflow for CPUS Subsystem Number of High-Priority CELL UPDATE Messages Discarded Due to RRC Queue Overflow for CPUS Subsystem
73423926
VS.MidPriCu.FC.Disc.Num .Queue
73423927
VS.HighPriCu.FC.Disc.Nu m.Queue
Description
These counters provide the number of CELL_UPDATE messages discarded due to queue-based shaping in a CPU subsystem (CPUS). These counters are measured by message priority.In a later version, this counter is to be replaced by the counters: VS.CU.FC.Num.RRCQueue (ID 73424919) and VS.CU.CONV.FC.Num.RRCQueue (ID 73424918). In the current version, this counter is reserved but cannot work. Therefore, the value of this counter is 0 and you are advised to use new counters.
Measurement point
The measurement is triggered when conditions for discarding CELL_UPDATE messages of a priority based on queue-based shaping are met. The RNC prioritizes the received CELL_UPDATE messages into high, medium, and low based on the cause value for service setup carried in the extended information element UU_CELL_UPT_V590EXT_STRU and the cause value for cell update. Figure 1-18
Formula
None
Unit
None
Related Features
Counter Name VS.LowPriCu.FC.Disc.Num .Queue VS.MidPriCu.FC.Disc.Num .Queue VS.HighPriCu.FC.Disc.Nu m.Queue Feature ID WRFD-040100 WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control Flow Control
Issue 01 (2013-05-04)
70
1.2.1.19 Number of Discarded Event 4A Measurement Reports on PS BE Traffic in the CELL_DCH State Counters
Counter ID 73423928 Counter Name VS.Traffic.Report4A.CellD ch.Disc.Num.UpLink.FC Counter Description Number of Discarded UL Event 4A Measurement Reports on PS BE Traffic in the CELL_DCH State in a CPUS Number of Discarded DL Event 4A Measurement Reports on PS BE Traffic in the CELL_DCH State in a CPUS
73423929
VS.Traffic.Report4A.CellD ch.Disc.Num.DownLink.FC
Description
These counters provide the number of discarded event 4A measurement reports on PS BE traffic in the CELL_DCH state in a CPU subsystem (CPUS) due to flow control.
Measurement point
Measurement of the counter VS.Traffic.Report4A.CellDch.Disc.Num.UpLink.FC is triggered when the RNC discards the event 4A measurement report from a UE on PS BE traffic in the CELL_DCH state. The measurement report is discarded if flow control is performed on the dynamic channel configuration control (DCCC) procedure. Figure 1-19
Issue 01 (2013-05-04)
71
Formula
None
Unit
None
Related Features
Counter Name VS.Traffic.Report4A.CellD ch.Disc.Num.UpLink.FC VS.Traffic.Report4A.CellD ch.Disc.Num.DownLink.FC Feature ID WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control
1.2.1.20 Number of Discarded UL Event 4A Measurement Reports on Throughput for UEs in the CELL_DCH State Counters
Counter ID 73423930 Counter Name VS.Throughput.Report4A.D isc.Num.UpLink.FC Counter Description Number of Discarded UL Event 4A Measurement Reports on Throughput for UEs in the CELL_DCH State in a CPUS
Description
This counter provides the number of discarded UL event 4A measurement reports on throughput for UEs in the CELL_DCH state in a CPU subsystem (CPUS) due to flow control.
Measurement point
The measurement is triggered when the RNC discards an event 4A measurement report on throughput received from MAC-d. The measurement report is discarded if flow control is performed on the dynamic channel configuration control (DCCC) procedure.
Issue 01 (2013-05-04)
72
Figure 1-20
Formula
None
Unit
None
Related Features
Counter Name VS.Throughput.Report4A.D isc.Num.UpLink.FC Feature ID WRFD-040100 Feature Name Flow Control
1.2.1.21 Number of Discarded Event 4A Measurement Reports on PS BE Traffic in the CELL_FACH State Counters
Counter ID 73423931 Counter Name VS.Traffic.Report4A.CellFa ch.Disc.Num.UpLink.FC Counter Description Number of Discarded UL Event 4A Measurement Reports on PS BE Traffic in the CELL_FACH State in a CPUS
73
Issue 01 (2013-05-04)
Counter ID 73423932
Counter Name VS.Traffic.Report4A.CellFa ch.Disc.Num.DownLink.FC
Counter Description Number of Discarded DL Event 4A Measurement Reports on PS BE Traffic in the CELL_FACH State in a CPUS
Description
These counters provide the number of discarded event 4A measurement reports on PS BE traffic in the CELL_FACH state in a CPU subsystem (CPUS) due to flow control.
Measurement point
Measurement of the counter VS.Traffic.Report4A.CellFach.Disc.Num.UpLink.FC is triggered when the RNC discards the event 4A measurement report on traffic received from a UE in the CELL_FACH state. The measurement report is discarded if flow control is performed on the dynamic channel configuration control (DCCC) procedure. Figure 1-21
Formula
None
Unit
None
Related Features
Counter Name VS.Traffic.Report4A.CellFa ch.Disc.Num.UpLink.FC VS.Traffic.Report4A.CellFa ch.Disc.Num.DownLink.FC Feature ID WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control
1.2.1.22 Number of FlowControl RRC Connection Requests Due to FlowControl for CPUS Subsystem Counters
Counter ID 73424215 Counter Name VS.RRC.FC.Num.CPU.CP US Counter Description Number of RRC CONNECTION REQUESTS Under Flow Control Due to High CPU Usage for CPUS Subsystem Number of RRC CONNECTION REQUESTS Under Flow Control Due to RRC Queue Overflow for CPUS Subsystem Number of RRC CONNECTION REQUESTS Under Flow Control Due to MPU Overload for CPUS Subsystem Number of RRC CONNECTION REQUESTS Under Flow Control Due to Burst Traffic for CPUS Subsystem
73424216
VS.RRC.FC.Num.RRCQue ue.CPUS
73424217
VS.RRC.FC.Num.MPU.CP US
73424218
VS.RRC.FC.Num.CallShoc k.CPUS
Description
These counters provide the number of RRC CONNECTION REQUEST messages in a CPUS subsystem under flow control.
Issue 01 (2013-05-04)
75
Measurement point
To be translate.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.FC.Num.CPU.CP US VS.RRC.FC.Num.RRCQue ue.CPUS VS.RRC.FC.Num.MPU.CP US VS.RRC.FC.Num.CallShoc k.CPUS Feature ID WRFD-040100 WRFD-040100 WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control Flow Control Flow Control
1.2.1.23 Number of FlowControl RT RRC Connection Requests Due to FlowControl for CPUS Subsystem Counters
Counter ID 73424219 Counter Name VS.RRC.CONV.FC.Num.C PU.CPUS Counter Description Number of RRC CONNECTION REQUESTS for CS Services Under Flow Control Due to High CPU Usage for CPUS Subsystem Number of RRC CONNECTION REQUESTS for CS Services Under Flow Control Due to RRC Queue Overflow for CPUS Subsystem
73424220
VS.RRC.CONV.FC.Num.R RCQueue.CPUS
Issue 01 (2013-05-04)
76
Counter ID 73424221
Counter Name VS.RRC.CONV.FC.Num.M PU.CPUS
Counter Description Number of RRC CONNECTION REQUESTS for CS Services Under Flow Control Due to MPU Overload for CPUS Subsystem Number of RRC CONNECTION REQUESTS for CS Services Under Flow Control Due to Burst Traffic for CPUS Subsystem
73424222
VS.RRC.CONV.FC.Num.C allShock.CPUS
Description
These counters provide the number of RRC CONNECTION REQUEST messages for CS services in a CPUS subsystem under flow control. If the establishment cause in these requests is UU_ORIGINATING_CONVERSATIONAL_CALL_ESTAB_CAUSE or UU_TERMNT_CONVERSATIONAL_CALL_ESTAB_CAUSE, the RNC determines that the current service is a CS service.
Measurement point
To be translate.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.CONV.FC.Num.C PU.CPUS VS.RRC.CONV.FC.Num.R RCQueue.CPUS VS.RRC.CONV.FC.Num.M PU.CPUS VS.RRC.CONV.FC.Num.C allShock.CPUS Feature ID WRFD-040100 WRFD-040100 WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control Flow Control Flow Control
Issue 01 (2013-05-04)
77
1.2.1.24 Number of RRC CONNECTION REQUESTS for CS Services in a CPUS Subsystem Under Flow Control Triggered by Interface-Board CPU Overload Counters
Counter ID 73424482 Counter Name VS.RRC.CONV.FC.Num.I NT.CPUS Counter Description Number of RRC CONNECTION REQUESTS for CS Services in a CPUS Subsystem Under Flow Control Triggered by Interface-Board CPU Overload
Description
This counter measures the number of rejected radio resource control (RRC) connection setup requests for CS voice services during flow control caused by interface-board central processing unit (CPU) overload in a CPU subsystem (CPUS). If the cause value contained in an RRC CONNECTION REQUEST message is Originating Conversational Call or Terminating Conversational Call, the RRC connection setup request is for a CS voice service.
Measurement point
The measurement is triggered when all the following conditions are met: A CPUS receives an RRC CONNECTION REQUEST message from a UE. The CPUS rejects the UE's request because of interface-board CPU overload and failures in applying for transmission resources. This counter measures the number of rejected radio resource control (RRC) connection setup requests for CS voice services during flow control caused by interface-board central processing unit (CPU) overload in a CPU subsystem (CPUS).
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.CONV.FC.Num.I NT.CPUS Feature ID WRFD-040100 Feature Name Flow Control
Issue 01 (2013-05-04)
78
1.2.1.25 Number of RRC CONNECTION REQUESTS in a CPUS Subsystem Under Flow Control Triggered by Interface-Board CPU Overload Counters
Counter ID 73424483 Counter Name VS.RRC.FC.Num.INT.CPU S Counter Description Number of RRC CONNECTION REQUESTS in a CPUS Subsystem Under Flow Control Triggered by Interface-Board CPU Overload
Description
This counter measures the number of rejected RRC connection setup requests during flow control caused by interface-board CPU overload in a CPU subsystem (CPUS).
Measurement point
The measurement is triggered when all the following conditions are met: A CPUS receives an RRC CONNECTION REQUEST message from a UE. The CPUS rejects the UE's request because of interface-board CPU overload and failures in applying for transmission resources. This counter measures the number of rejected RRC connection setup requests during flow control caused by interface-board CPU overload in a CPU subsystem (CPUS).
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.FC.Num.INT.CPU S Feature ID WRFD-040100 Feature Name Flow Control
1.2.1.26 Number of Discarded Iur-Interface Uplink Signalling Messages in a CPUS Subsystem Under Flow Control Triggered by CPU Overload
Counters
Counter ID 73424484 Counter Name VS.IurUpLinkSig.Disc.Num .CPU.CPUS Counter Description Number of Discarded IurInterface Uplink Signalling Messages in a CPUS Subsystem Under Flow Control Triggered by CPU Overload
Description
This counter measures the number of discarded uplink signalling message during flow control caused by central processing unit (CPU) overload in a CPU subsystem (CPUS).
Measurement point
This counter measures the number of discarded UPLINK SIGNALLING TRANSFER INDICATION messages during flow control caused by central processing unit (CPU) overload in a CPU subsystem (CPUS). The measurement is triggered when a CPUS receives an uplink signalling message from a neighboring RNC and discards the message due to CPU overload in the CPUS.
Formula
None
Unit
None
Related Features
Counter Name VS.IurUpLinkSig.Disc.Num .CPU.CPUS Feature ID WRFD-040100 Feature Name Flow Control
1.2.1.27 Number of Discarded Iur-Interface Downlink Signalling Messages in a CPUS Subsystem Under Flow Control Triggered by CPU Overload
Issue 01 (2013-05-04)
80
Counters
Counter ID 73424485 Counter Name VS.IurDownLinkSig.Disc.N um.CPU.CPUS Counter Description Number of Discarded IurInterface Downlink Signalling Messages in a CPUS Subsystem Under Flow Control Triggered by CPU Overload
Description
This counter measures the number of discarded downlink signaling messages during flow control caused by central processing unit (CPU) overload in a CPU subsystem (CPUS).
Measurement point
The measurement is triggered when a CPU subsystem (CPUS) receives any of the following messages and discards the message due to CPU overload in the CPUS: RADIO LINK SETUP REQUEST PAGING REQUEST COMMON TRANSPORT CHANNEL RESOURCES REQUEST This counter measures the number of discarded downlink signaling messages during flow control caused by central processing unit (CPU) overload in a CPUS.
Formula
None
Unit
None
Related Features
Counter Name VS.IurDownLinkSig.Disc.N um.CPU.CPUS Feature ID WRFD-040100 Feature Name Flow Control
1.3 Measurement of GTPU Performance(GTPU)

Overview
GTPU measurement (GTPU) is used to measure the general performance of data transfer procedures of the GPRS Tunneling Protocol for User Plane (GTP-U). The GTPU measurement consists of only one function subset.
FunctionSubSets
FunctionSubSet GTPU FunctionSubSet Name Measurement related to GTPU
1.3.1 Measurement related to GTPU(GTPU)

Overview
When the UE is activated in PS domain, the RNC sets up the user plane to the SGSN and allocates GTP-U tunnels. All the data transmissions of the UE are performed through the GTPU tunnels. Therefore, it is necessary to calculate the number of messages and the bytes of messages that are received and transmitted by the GTP-U.
Counters
Counter ID 67178509 Counter Name VS.GTPU.Pkt.Tx Counter Description Number of UL Packets Sent by GTP-U Number of DL Packets Received by GTP-U Number of UL Bytes Sent by GTP-U Number of DL Bytes Received by GTP-U Number of UL Session Service Packets Sent by GTPU Number of DL Session Service Packets Received by GTPU Number of UL Streaming Service Packets Sent by GTPU Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67178512
VS.GTPU.Pkt.Rx
67199477 67199478 67204158
VS.GTPU.BytesPkt .Tx VS.GTPU.BytesPkt .Rx VS.GTPU.PktNum Conv.Tx
67204159
VS.GTPU.PktNum Conv.Rx
67204160
VS.GTPU.PktNum Str.Tx
Issue 01 (2013-05-04)
82
Counter ID 67204161
Counter Name VS.GTPU.PktNum Str.Rx
Counter Description Number of DL Streaming Service Packets Received by GTPU Number of UL Interactive Service Packets Sent by GTPU Number of DL Interactive Service Packets Received by GTPU Number of UL Background Service Packets Sent by GTPU Number of DL Background Service Packets Received by GTP Number of MBMS Service Bytes Received by GTP-U Number of Echo Response Packets Sent by the GTP-U Number of Echo Response Packets Received by the GTP-U Number of Echo Request Packets Sent by the GTP-U Number of Echo Request Packets Received by the GTP-U Number of Error Indication Packets Sent by the GTP-U
67204162
VS.GTPU.PktNum Int.Tx
67204163
VS.GTPU.PktNum Int.Rx
67204164
VS.GTPU.PktNum Bkg.Tx
67204165
VS.GTPU.PktNum Bkg.Rx
67192326
VS.GTPU.BytesMb ms.Rx VS.GTPU.EchoRsp .Tx VS.GTPU.EchoRsp .Rx
73424012
73424013
V900R014
73424014
VS.GTPU.EchoRe q.Tx VS.GTPU.EchoRe q.Rx
V900R014
73424015
V900R014
73424016
VS.GTPU.ErrInd. Tx
V900R014
Issue 01 (2013-05-04)
83
Counter ID 73424017
Counter Name VS.GTPU.ErrInd. Rx
Counter Description Number of Error Indication Packets Received by the GTP-U
Counter VS.GTPU.Pkt.Tx Sub Counter VS.GTPU.PktNumConv.Tx VS.GTPU.PktNumStr.Tx VS.GTPU.PktNumInt.Tx VS.GTPU.PktNumBkg.Tx VS.GTPU.Pkt.Rx VS.GTPU.PktNumConv.Rx VS.GTPU.PktNumStr.Rx VS.GTPU.PktNumInt.Rx VS.GTPU.PktNumBkg.Rx
1.3.1.1 Number of UL Packets Sent by GTP-U Counters

Counter ID 67178509 Counter Name VS.GTPU.Pkt.Tx Counter Description Number of UL Packets Sent by GTP-U
Description
This counter provides the number of data packets and control packets sent by the RNC to the GTP-U at the peer end.
Measurement point
This counter is incremented by one each time the RNC sends a data packet or control packet to the GTP-U at the peer end.
Formula
None
Unit
packet
Related Features
Counter Name VS.GTPU.Pkt.Tx Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.3.1.2 Number of DL Packets Received by GTP-U Counters

Counter ID 67178512 Counter Name VS.GTPU.Pkt.Rx Counter Description Number of DL Packets Received by GTP-U
Description
This counter provides the number of data packets and control packets received by the GTP-U on the RNC side.
Measurement point
This counter is incremented by one each time the RNC receives a data packet or control packet from the GTP-U at the peer end.
Formula
None
Unit
packet
Related Features
Counter Name VS.GTPU.Pkt.Rx Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
85
1.3.1.3 Number of UL Bytes Sent by GTP-U Counters

Counter ID 67199477 Counter Name VS.GTPU.BytesPkt.Tx Counter Description Number of UL Bytes Sent by GTP-U
Description
This counter provides the number of bytes in the data packets and control packets sent by the RNC to the GTP-U at the peer end.
Measurement point
This counter is incremented by one each time the RNC sends a data packet or control packet to the GTP-U at the peer end.
Formula
None
Unit
byte
Related Features
Counter Name VS.GTPU.BytesPkt.Tx Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.3.1.4 Number of DL Bytes Received by GTP-U Counters

Counter ID 67199478 Counter Name VS.GTPU.BytesPkt.Rx Counter Description Number of DL Bytes Received by GTP-U
Issue 01 (2013-05-04)
86
Description
This counter provides the number of bytes in the data packets and control packets received by the GTP-U on the RNC side.
Measurement point
This counter is incremented by one each time the RNC receives a data packet or control packet from the GTP-U at the peer end.
Formula
None
Unit
byte
Related Features
Counter Name VS.GTPU.BytesPkt.Rx Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.3.1.5 Counters Related to the Number of Service PDUs Sent by GTP-U Counters
Counter ID 67204158 Counter Name VS.GTPU.PktNumConv.Tx Counter Description Number of UL Session Service Packets Sent by GTPU Number of UL Streaming Service Packets Sent by GTPU Number of UL Interactive Service Packets Sent by GTPU Number of UL Background Service Packets Sent by GTPU
67204160
VS.GTPU.PktNumStr.Tx
67204162
VS.GTPU.PktNumInt.Tx
67204164
VS.GTPU.PktNumBkg.Tx
Issue 01 (2013-05-04)
87
Description
These counters provide the number of GTP-U PDUs that the RNC sends to the core network (CN).
Measurement point
When sending a service PDU to the peer GTP-U, the RNC measures this counter.
Formula
None
Unit
packet
Related Features
Counter Name VS.GTPU.PktNumConv.Tx VS.GTPU.PktNumStr.Tx VS.GTPU.PktNumInt.Tx VS.GTPU.PktNumBkg.Tx Feature ID WRFD-010501 WRFD-010502 WRFD-010503 WRFD-010504 Feature Name Conversational QoS Class Streaming QoS Class Interactive QoS Class Background QoS Class
1.3.1.6 Counters Related to the Number of Service PDUs Received by GTP-U Counters
Counter ID 67204159 Counter Name VS.GTPU.PktNumConv.Rx Counter Description Number of DL Session Service Packets Received by GTPU Number of DL Streaming Service Packets Received by GTPU Number of DL Interactive Service Packets Received by GTPU Number of DL Background Service Packets Received by GTP
67204161
VS.GTPU.PktNumStr.Rx
67204163
VS.GTPU.PktNumInt.Rx
67204165
VS.GTPU.PktNumBkg.Rx
Issue 01 (2013-05-04)
88
Description
These counters provide the number of GTP-U PDUs that the RNC receives from the CN.
Measurement point
When receiving a service PDU from the peer GTP-U, the RNC measures this counter.
Formula
None
Unit
packet
Related Features
Counter Name VS.GTPU.PktNumConv.Rx VS.GTPU.PktNumStr.Rx VS.GTPU.PktNumInt.Rx VS.GTPU.PktNumBkg.Rx Feature ID WRFD-010501 WRFD-010502 WRFD-010503 WRFD-010504 Feature Name Conversational QoS Class Streaming QoS Class Interactive QoS Class Background QoS Class
1.3.1.7 Number of MBMS or IMB Service Bytes Received by GTP-U Counters

Counter ID 67192326 Counter Name VS.GTPU.BytesMbms.Rx Counter Description Number of MBMS Service Bytes Received by GTP-U
Description
This counter provides the number of GTP-U PDU bytes of MBMS or IMB services received by the RNC.
Measurement point
When receiving an MBMS or IMB service PDU from the peer GTP-U, the RNC measures this counter.
Formula
None
Unit
byte
Related Features
Counter Name VS.GTPU.BytesMbms.Rx Feature ID WRFD-010616 Feature Name MBMS Introduction Package
1.3.1.8 Number of Echo Response Packets Sent by the GTP-U Counters

Counter ID 73424012 Counter Name VS.GTPU.EchoRsp.Tx Counter Description Number of Echo Response Packets Sent by the GTP-U
Description
This counter provides the number of Echo Response packets sent by the GTP-U on the RNC side.
Measurement point
This counter is incremented by one each time the RNC sends an Echo Response packet to the GTP-U at the peer end.
Formula
None
Unit
packet
Related Features
None
1.3.1.9 Number of Echo Response Packets Received by the GTP-U
Issue 01 (2013-05-04)
90
Counters
Counter ID 73424013 Counter Name VS.GTPU.EchoRsp.Rx Counter Description Number of Echo Response Packets Received by the GTP-U
Description
This counter provides the number of Echo Response packets received by the GTP-U on the RNC side.
Measurement point
This counter is incremented by one each time the RNC receives an Echo Response packet from the GTP-U at the peer end.
Formula
None
Unit
packet
Related Features
None
1.3.1.10 Number of Echo Request Packets Sent by the GTP-U Counters

Counter ID 73424014 Counter Name VS.GTPU.EchoReq.Tx Counter Description Number of Echo Request Packets Sent by the GTP-U
Description
This counter provides the number of Echo Request packets sent by the GTP-U on the RNC side.
Measurement point
This counter is incremented by one each time the RNC sends an Echo Request packet to the GTP-U at the peer end.
Formula
None
Unit
packet
Related Features
None
1.3.1.11 Number of Echo Request Packets Received by the GTP-U Counters

Counter ID 73424015 Counter Name VS.GTPU.EchoReq.Rx Counter Description Number of Echo Request Packets Received by the GTP-U
Description
This counter provides the number of Echo Request packets received by the GTP-U on the RNC side.
Measurement point
This counter is incremented by one each time the RNC receives an Echo Request packet from the GTP-U at the peer end.
Formula
None
Unit
packet
Related Features
None
1.3.1.12 Number of Error Indication Packets Sent by the GTP-U
Issue 01 (2013-05-04)
92
Counters
Counter ID 73424016 Counter Name VS.GTPU.ErrInd.Tx Counter Description Number of Error Indication Packets Sent by the GTP-U
Description
This counter provides the number of Error Indication packets sent by the GTP-U on the RNC side.
Measurement point
This counter is incremented by one each time the RNC sends an Error Indication packet to the GTP-U at the peer end.
Formula
None
Unit
packet
Related Features
None
1.3.1.13 Number of Error Indication Packets Received by the GTP-U Counters

Counter ID 73424017 Counter Name VS.GTPU.ErrInd.Rx Counter Description Number of Error Indication Packets Received by the GTP-U
Description
This counter provides the number of Error Indication packets received by the GTP-U on the RNC side.
Measurement point
This counter is incremented by one each time the RNC receives an Error Indication packet from the GTP-U at the peer end.
Formula
None
Unit
packet
Related Features
None
1.4 Measurement of IU Interface Performance(IU)

Overview
The measurement object of Iu Interface Performance Measurement (IU) is used to measure the overall performance of the basic signaling procedures and traffic flows on the Iu interface.
FunctionSubSets
FunctionSubSet CS.SIG.IU CS.TRF.IU MBMS.IU MOCN.IU NAS.IU PS.SIG.IU PS.TRF.IU SIG.SCCP.IU FunctionSubSet Name Measurement related to CS Iu interface signalling Measurement related to CS traffic Measurement related to Iu interface(MBMS) Measurement related to Iu interface(MOCN) Measurement related to NAS signaling Measurement related to PS Iu interface signalling Measurement related to PS traffic Measurement Related to SCCP for Iu Interface
1.4.1 Measurement related to CS Iu interface signalling(CS.SIG.IU)

Overview
This function subset aims at the connectionless signaling procedure and the signaling connection setup and release procedures on the Iu interface. In Iu Flex connection mode, the RNC measures the counters according to the CS CN nodes.
Counters
Counter ID 67176449 Counter Name VS.IU.ResetCS.Tx Counter Description Number of RESET Messages Sent by RNC to CN in CS Domain Number of RESET Messages Received by RNC from CN in CS Domain Number of INITIAL UE MESSAGE Messages Sent by RNC to CN in CS Domain Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain Number of IU RELEASE COMMAND Messages Received by RNC from CN in CS Domain Number of ERROR INDICATION Messages Sent by RNC to CN in CS Domain Number of ERROR INDICATION Messages Received by RNC from CN in CS Domain Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain (Repeated Integrity Checking Failure) Original Release Earlier than V900R011
67176453
VS.IU.ResetCS.Rx
67189920
VS.IU.SIG.AttConnEstabCS
67176546
VS.IU.RelReqCS.s um
67176552
VS.IU.RelCmdCS.s um
67176529
VS.IU.ErrInd.CS.T x
67176531
VS.IU.ErrInd.CS. Rx
67176549
VS.IU.RelReqCS.I ngChkFail
Issue 01 (2013-05-04)
95
Counter ID 67176550
Counter Name VS.IU.RelReqCS.Si gConnRel
Counter Description Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain (UE Signaling Connection Release) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain (Radio Connection With UE Lost) Number of IU RELEASE COMMAND Messages Received by RNC from CN in CS Domain (Relocation Success) Number of IU RELEASE COMMAND Messages Received by RNC from CN in CS Domain (Normal Release) Number of IU RELEASE COMMAND Messages Received by RNC from CN in CS Domain (UTRAN Generated) Number of IU RELEASE COMMAND Messages Received by RNC from CN in CS Domain (Relocation Cancelled)
67176551
VS.IU.RelReqCS.R adConnUELost
67176553
VS.IU.RelCmdCS. RelocSucc
67176554
VS.IU.RelCmdCS. NormRel
67176555
VS.IU.RelCmdCS. UTRANGen
67176556
VS.IU.RelCmdCS. RelocCan
Issue 01 (2013-05-04)
96
Counter ID 67176557
Counter Name VS.IU.RelCmdCS. NoRAB
Counter Description Number of IU RELEASE COMMAND Messages Received by RNC from CN in CS Domain (No Remaining RAB) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain (Failure in the Radio Interface Procedure) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain (RAB Preempted) Number of Times that CS Load Balancing is Performed by IMSI Users Number of Times that CS Load Balancing is Performed by TMSI Users Due to Invalid NRI Number of Times that CS Load Balancing is Performed by IMEI Users Number of Discarded CS Initial UE Messages when Signaling Flow Control is Triggered
67176573
VS.Iu.RelReqCS.R IPFail
67190182
VS.IU.RelReqCS.P reempt
67192538
VS.IU.LdBalRtCS. IMSI
67192539
VS.IU.LdBalRtCS. InValidNRI
67192540
VS.IU.LdBalRtCS. IMEI
67193095
VS.IU.FlowCtrl.Dis cInitDT.CS
Issue 01 (2013-05-04)
97
Counter ID 67196234
Counter Name VS.IU.RelReqCS.N etworkOpt
Counter Description Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain (VP Forbiddance) Number of Paging Messages Received by RNC from CN in CS Domain Number of RAN INFORMATION REQUEST Messages Received by RNC from CN Number of RAN INFORMATION Messages Sent by RNC to CN
73424970
VS.IU.CS.Paging
V900R014
73425021
VS.IU.RanInfoReq. Rx
V900R014
73425022
VS.IU.RanInfo.Tx
V900R014
None
1.4.1.1 Number of RESET Messages Initiated by RNC to CS Domain Counters

Counter ID 67176449 Counter Name VS.IU.ResetCS.Tx Counter Description Number of RESET Messages Sent by RNC to CN in CS Domain
Description
This measurement counter takes statistics of the number of RESET messages that the RNC sends to the CS domain according to respective CN nodes.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends a RESET message to the CS domain, it measures this counter. If the RNC does not receive the RESET
ACKNOWLEDGE message from the CN before the response timer expires, the RNC sends the RESET message again and this counter is also measured again. Figure 1-22 CS domain reset procedure initiated by the RNC (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.ResetCS.Tx Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.1.2 Number of RESET Messages Received by RNC from CS Domain
Issue 01 (2013-05-04)
99
Counters
Counter ID 67176453 Counter Name VS.IU.ResetCS.Rx Counter Description Number of RESET Messages Received by RNC from CN in CS Domain
Description
This counter provides the number of RESET messages that the RNC receives from the CS domain in the CN based on the corresponding CN node.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives a RESET message from the CS domain, it measures this counter. Figure 1-23 CS domain reset procedure initiated by the CN (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.ResetCS.Rx Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.1.3 Number of INITIAL UE MESSAGE Messages from RNC to CS Domain Counters

Counter ID 67189920 Counter Name VS.IU.SIG.AttConnEstabCS Counter Description Number of INITIAL UE MESSAGE Messages Sent by RNC to CN in CS Domain
Description
This measurement counter takes statistics of the number of INITIAL UE MESSAGE messages that the RNC sends to the CS domain. The RNC measures this counter according to the CN nodes.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends an INITIAL UE MESSAGE message to the CS domain, it measures this counter. Figure 1-24 Initial UE message procedure
Issue 01 (2013-05-04)
101
Formula
None
Unit
None
Related Features
Counter Name VS.IU.SIG.AttConnEstabCS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.1.4 Number of IU RELEASE REQUEST Messages from RNC to CS Domain Counters

Counter ID 67176546 Counter Name VS.IU.RelReqCS.sum Counter Description Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain
Description
This counter provides the number of IU RELEASE REQUEST messages sent by the RNC to the CS domain of the CN. The IU RELEASE REQUEST message is sent by the RNC to release an Iu signaling connection between the specific UE and the CS domain because of a UTRAN cause. The counter is measured based on the CN node to which the message is sent.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends an IU RELEASE REQUEST message to the CS domain, it measures this counter.
Issue 01 (2013-05-04)
102
Figure 1-25 Iu release procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RelReqCS.sum Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.1.5 Number of IU RELEASE COMMAND Messages from CS Domain to RNC
Issue 01 (2013-05-04)
103
Counters
Counter ID 67176552 Counter Name VS.IU.RelCmdCS.sum Counter Description Number of IU RELEASE COMMAND Messages Received by RNC from CN in CS Domain
Description
This counter provides the number of IU RELEASE COMMAND messages that the RNC receives from the CS domain based on the corresponding CN node. During the Iu release procedure of the CS domain, the Iu connection and all the UTRAN resources related to the Iu connection are released.
Measurement point
The measurement is triggered at point B as shown in the figure. In the RNC-initiated Iu release procedure, when the RNC receives an IU RELEASE COMMAND message from the CS domain, the RNC measures this counter. Figure 1-26 Iu release procedure (successful operation)
The measurement is triggered at point A as shown in the figure. In the CN-initiated Iu release procedure, when the RNC receives an IU RELEASE COMMAND message from the CS domain, the RNC measures this counter.
Figure 1-27 Iu release procedure initiated by the CN (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RelCmdCS.sum Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.1.6 Number of ERROR INDICATION Messages from RNC to CS Domain
Issue 01 (2013-05-04)
105
Counters
Counter ID 67176529 Counter Name VS.IU.ErrInd.CS.Tx Counter Description Number of ERROR INDICATION Messages Sent by RNC to CN in CS Domain
Description
This measurement counter takes statistics of the number of ERROR INDICATION messages that the RNC sends to the CS domain. The RNC measures this counter according to the CN nodes.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends an ERROR INDICATION message to the CS domain, it measures this counter. Figure 1-28 Error indication procedure initiated by the RNC
Formula
None
Issue 01 (2013-05-04)
106
Unit
None
Related Features
Counter Name VS.IU.ErrInd.CS.Tx Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.1.7 Number of ERROR INDICATION Messages from CS Domain to RNC Counters

Counter ID 67176531 Counter Name VS.IU.ErrInd.CS.Rx Counter Description Number of ERROR INDICATION Messages Received by RNC from CN in CS Domain
Description
This counter provides the number of ERROR INDICATION messages that the RNC receives from the CS domain based on the corresponding CN node.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives an ERROR INDICATION message from the CS domain, it measures this counter according to the CN nodes.
Issue 01 (2013-05-04)
107
Figure 1-29 Error indication procedure initiated by the CN
Formula
None
Unit
None
Related Features
Counter Name VS.IU.ErrInd.CS.Rx Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.1.8 Number of IU RELEASE REQUEST Messages from RNC to CS Domain for Different Causes
Issue 01 (2013-05-04)
108
Counters
Counter ID 67176549 Counter Name VS.IU.RelReqCS.IngChkFail Counter Description Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain (Repeated Integrity Checking Failure) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain (UE Signaling Connection Release) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain (Radio Connection With UE Lost) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain (Failure in the Radio Interface Procedure) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain (RAB Preempted) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in CS Domain (VP Forbiddance)
67176550
VS.IU.RelReqCS.SigConnRel
67176551
VS.IU.RelReqCS.RadConnUELost
67176573
VS.Iu.RelReqCS.RIPFail
67190182
VS.IU.RelReqCS.Preempt
67196234
VS.IU.RelReqCS.NetworkOpt
Description
These measurement counters take statistics of the number of IU RELEASE REQUEST messages that the RNC sends to the CS domain for different causes. The RNC measures these counters according to the CN nodes.Those release causes are just a part of release causes defined by protocol 25.413, and the other causes according to specification will be added into VS.IU.RelReqCS.sum.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends an IU RELEASE REQUEST message to the CS domain, it measures these counters according to different causes.
Issue 01 (2013-05-04)
109
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RelReqCS.IngChkFail Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.IU.RelReqCS.SigConnRel
WRFD-010510
VS.IU.RelReqCS.RadConnUELost
WRFD-010510
Issue 01 (2013-05-04)
110
Counter Name VS.Iu.RelReqCS.RIPFail
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Videophone Service Restriction
VS.IU.RelReqCS.Preempt
WRFD-010510
VS.IU.RelReqCS.NetworkOpt
WRFD-020130
1.4.1.9 Number of IU RELEASE COMMAND Messages from CS Domain to RNC for Different Causes Counters
Counter ID 67176553 Counter Name VS.IU.RelCmdCS.RelocSucc Counter Description Number of IU RELEASE COMMAND Messages Received by RNC from CN in CS Domain (Relocation Success) Number of IU RELEASE COMMAND Messages Received by RNC from CN in CS Domain (Normal Release) Number of IU RELEASE COMMAND Messages Received by RNC from CN in CS Domain (UTRAN Generated) Number of IU RELEASE COMMAND Messages Received by RNC from CN in CS Domain (Relocation Cancelled) Number of IU RELEASE COMMAND Messages Received by RNC from CN in CS Domain (No Remaining RAB)
67176554
VS.IU.RelCmdCS.NormRel
67176555
VS.IU.RelCmdCS.UTRANGen
67176556
VS.IU.RelCmdCS.RelocCan
67176557
VS.IU.RelCmdCS.NoRAB
Issue 01 (2013-05-04)
111
Description
These counters provide the number of IU RELEASE COMMAND messages with different release causes that the RNC receives from the CS domain based on the corresponding CN node.
Measurement point
The measurement is triggered at point B, as shown in the figure. In the RNC-initiated Iu release procedure, when the RNC receives an IU RELEASE COMMAND message from the CS domain, it measures these counters according to different causes. Figure 1-31 Iu release procedure (successful operation)
The measurement is triggered at point A as shown in the figure. In the CN-initiated Iu release procedure, when the RNC receives an IU RELEASE COMMAND message from the CS domain, it measures these counters according to different causes.
Issue 01 (2013-05-04)
112
Figure 1-32 Iu release procedure initiated by the CN (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RelCmdCS.RelocSucc Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.IU.RelCmdCS.NormRel
WRFD-010510
VS.IU.RelCmdCS.UTRANGen
WRFD-010510
Issue 01 (2013-05-04)
113
Counter Name VS.IU.RelCmdCS.RelocCan
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.IU.RelCmdCS.NoRAB
WRFD-010510
1.4.1.10 Load Balancing of the MSC Pool on the CS Domain Counters

Counter ID 67192538 Counter Name VS.IU.LdBalRtCS.IMSI Counter Description Number of Times that CS Load Balancing is Performed by IMSI Users Number of Times that CS Load Balancing is Performed by TMSI Users Due to Invalid NRI Number of Times that CS Load Balancing is Performed by IMEI Users
67192539
VS.IU.LdBalRtCS.InValidNRI
67192540
VS.IU.LdBalRtCS.IMEI
Description
The measurement counters provide the number of times that the UEs perform load balancing on the CS domain during CN node selection when the RNC processes the initial direct transfer message. The following table describes the meaning of each counter. Counter Name VS.IU.LdBalRtCS.IMSI Description Number of times that the CS CN is selected for load balancing by using the IMSI route parameter.
Issue 01 (2013-05-04)
114
Counter Name VS.IU.LdBalRtCS.InValidNRI
Description Number of times that load balancing is triggered due to invalid NRI route parameter, connection failure to the CN node corresponding to the route parameter, or the flow control of the CN node corresponding to the route parameter. Number of times that the CS CN is selected for load balancing by using the IMEI route parameter.
VS.IU.LdBalRtCS.IMEI
Measurement point
The measurement is triggered when the RNC sends an INITIAL UE MESSAGE message to the CN for load balancing, as shown by point A in the following figure. The corresponding counter is measured on the basis of the UE identification carried in the INITIAL DIRECT TRANSFER message from the UE to the RNC. Figure 1-33 Initial UE message procedure
Formula
None
Issue 01 (2013-05-04)
115
Unit
None
Related Features
Counter Name VS.IU.LdBalRtCS.IMSI VS.IU.LdBalRtCS.InValidNRI VS.IU.LdBalRtCS.IMEI Feature ID WRFD-021306 WRFD-021306 WRFD-021306 Feature Name Iu Flex Load Distribution Management Iu Flex Load Distribution Management Iu Flex Load Distribution Management
1.4.1.11 Number of Discarded Initial UE messages Under Iu Signaling Flow Control (CS Domain) Counters
Counter ID 67193095 Counter Name VS.IU.FlowCtrl.DiscInitDT. CS Counter Description Number of Discarded CS Initial UE Messages when Signaling Flow Control is Triggered
Description
This measurement counter provides the number of initial UE messages discarded under the flow control when the RNC receives the CS initial direct transfer messages.
Measurement point
The measurement is triggered when the RNC receives an INITIAL DIRECT TRANSFER message from a UE and then discards this message because the RNC finds that the Iu-CS interface is under flow control, as shown by point A in the following figure. After that, the RNC does not send the INITIAL UE MESSAGE to the CN.
Issue 01 (2013-05-04)
116
Figure 1-34 Process of discarding INITIAL DIRECT TRANSFER message
Formula
None
Unit
None
Related Features
Counter Name VS.IU.FlowCtrl.DiscInitDT. CS Feature ID WRFD-040100 Feature Name Flow Control
1.4.1.12 Number of Paging Messages Received by RNC from CN in CS Domain Counters

Counter ID 73424970 Counter Name VS.IU.CS.Paging Counter Description Number of Paging Messages Received by RNC from CN in CS Domain
Issue 01 (2013-05-04)
117
Description
This counter provides the number of PAGING messages that the RNC receives from the CS domain based on the corresponding CN node.
Measurement point
The measurement is triggered at point A shown in the following figure when both of the following conditions are met: -The RNC receives a paging message from the CN. -The value of the CN Domain Indicator IE contained in the message indicates the CS domain. Figure 1-35 Paging messages sent from the CN to the UE
Formula
None
Unit
None
Related Features
Counter Name VS.IU.CS.Paging Feature ID WRFD-010301 WRFD-010302 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) Paging UE in CELL_FACH, CELL_DCH State (Type 2)
Issue 01 (2013-05-04)
118
1.4.1.13 Number of RAN INFORMATION REQUEST Messages Received by RNC from CN Counters
Counter ID 73425021 Counter Name VS.IU.RanInfoReq.Rx Counter Description Number of RAN INFORMATION REQUEST Messages Received by RNC from CN
Description
This counter provides the number of RANAP DERECT INFORMATION TRANSER messages whose types are RAN INFORMATION REQUEST that the RNC receives from the CN based on the corresponding CN node.
Measurement point
The measurement is triggered at point A as shown in the figure. This counter is incremented by one each time the RNC receives a RANAP DERECT INFORMATION TRANSER message whose type is RAN INFORMATION REQUEST. Figure 1-36 Procedure for directly sending messages over the Iu interface
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RanInfoReq.Rx Feature ID WRFD-140224 Feature Name Fast CS Fallback Based on RIM
1.4.1.14 Number of RAN INFORMATION Messages Sent by RNC to CN Counters

Counter ID 73425022 Counter Name VS.IU.RanInfo.Tx Counter Description Number of RAN INFORMATION Messages Sent by RNC to CN
Description
This counter provides the number of RANAP DERECT INFORMATION TRANSER messages whose types are RAN INFORMATION that the RNC receives from the CN based on the corresponding CN node.
Measurement point
The measurement is triggered at point A as shown in the figure. This counter is incremented by one each time the RNC receives a RANAP DERECT INFORMATION TRANSER message whose type is RAN INFORMATION. Figure 1-37 Procedure for directly sending messages over the Iu interface
Issue 01 (2013-05-04)
120
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RanInfo.Tx Feature ID WRFD-140224 Feature Name Fast CS Fallback Based on RIM
1.4.2 Measurement related to CS traffic(CS.TRF.IU)

Overview
The function subset is used to measure the UL and DL traffic for various services of the CS domain on the Iu interface.
Counters
Counter ID 67199469 Counter Name VS.IuCS.BytesPayl dConv.Rx Counter Description Number of DL Bytes of CS Conversational Service on Iu-CS Interface Number of DL Bytes of CS Streaming Service on Iu-CS Interface Number of UL Bytes of CS Conversational Service on Iu-CS Interface Number of UL Bytes of CS Streaming Service on Iu-CS Interface Original Release Earlier than V900R011
67199470
VS.IuCS.BytesPayl dStr.Rx
67199473
VS.IuCS.BytesPayl dConv.Tx
67199474
VS.IuCS.BytesPayl dStr.Tx
None
1.4.2.1 Number of DL Bytes of CS Conversational Service on Iu Interface Counters

Counter ID 67199469 Counter Name VS.IuCS.BytesPayldConv.R x Counter Description Number of DL Bytes of CS Conversational Service on Iu-CS Interface
Description
This counter provides the number of DL payload bytes of CS Conversational service data on the Iu-CS interface received by the RNC.It includes the data at the application layer and excludes the IuUP header.
Measurement point
When receiving the DL CS conversational service data on the Iu-CS interface, the RNC measures the counter according to different Iu-CS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuCS.BytesPayldConv.R x Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.4.2.2 Number of DL Bytes of CS Streaming Service on Iu Interface Counters

Counter ID 67199470 Counter Name VS.IuCS.BytesPayldStr.Rx Counter Description Number of DL Bytes of CS Streaming Service on Iu-CS Interface
Issue 01 (2013-05-04)
122
Description
This counter provides the number of DL payload bytes of CS streaming service data on the IuCS interface received by the RNC.It includes the data at the application layer and excludes the IuUP header.
Measurement point
When receiving the DL CS streaming service data on the Iu-CS interface, the RNC measures the counter according to different Iu-CS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuCS.BytesPayldStr.Rx Feature ID WRFD-010502 Feature Name Streaming QoS Class
1.4.2.3 Number of UL Bytes of CS Conversational Service on Iu Interface Counters

Counter ID 67199473 Counter Name VS.IuCS.BytesPayldConv.T x Counter Description Number of UL Bytes of CS Conversational Service on Iu-CS Interface
Description
This counter provides the number of UL payload bytes of CS Conversational service data on the Iu-CS interface sent by the RNC.It includes the data at the application layer and excludes the IuUP header.
Measurement point
When receiving the UL CS Conversational service data on the Iu-CS interface, the RNC measures the counter according to different Iu-CS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuCS.BytesPayldConv.T x Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.4.2.4 Number of UL Bytes of CS Streaming Service on Iu Interface Counters

Counter ID 67199474 Counter Name VS.IuCS.BytesPayldStr.Tx Counter Description Number of UL Bytes of CS Streaming Service on Iu-CS Interface
Description
This counter provides the number of UL payload bytes of CS streaming service data on the IuCS interface received by the RNC.It includes the data at the application layer and excludes the IuUP header.
Measurement point
When receiving the UL CS streaming service data on the Iu-CS interface, the RNC measures the counter according to different Iu-CS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuCS.BytesPayldStr.Tx Feature ID WRFD-010502 Feature Name Streaming QoS Class
Issue 01 (2013-05-04)
124
1.4.3 Measurement related to Iu interface(MBMS)(MBMS.IU)

Overview
This function subset is used to measure the number of MBMS service establishments, including the total number of MBMS service establishments, the number of successful establishments, and the number of failed establishments.
Counters
Counter ID 67192077 Counter Name VS.IU.MBMS.Start Counter Description Number of MBMS Service Establishment Attempts Number of Successful MBMS Service Establishments Number of Failed MBMS Service Establishments Number of Failed MBMS Service Establishments Due to No Resource Number of Failed MBMS Service Establishments Due to NNSF Number of Failed MBMS Service Establishments Due to Iu User Plane Failure Number of Failed MBMS Service Establishments Due to Iu Signaling Connection Failure Original Release Earlier than V900R011
67192078
VS.IU.MBMS.Succ
67192079
VS.IU.MBMS.Fail
67192080
VS.IU.MBMS.Fail. NoRsrc
67192081
VS.IU.MBMS.Fail. NNSF
67192082
VS.IU.MBMS.Fail. IuUpFail
67192083
VS.IU.MBMS.Fail. IuSigFail
None
1.4.3.1 Total Number of MBMS or IMB Service Counters

Counter ID 67192077 Counter Name VS.IU.MBMS.Start Counter Description Number of MBMS Service Establishment Attempts
Description
This measurement item takes statistics of the number of MBMS or IMB service establishments.
Measurement point
The measurement is triggered at point A, as shown in the figure. The measurement is triggered when the RNC receives an MBMS SESSION START message from the PS domain. Figure 1-38 MBMS session (success procedure)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.MBMS.Start Feature ID WRFD-010616 Feature Name MBMS Introduction Package
1.4.3.2 Number of Successful MBMS or IMB Service Counters

Counter ID 67192078 Counter Name VS.IU.MBMS.Succ Counter Description Number of Successful MBMS Service Establishments
Description
This measurement item takes statistics of the number of successful MBMS or IMB service establishments.
Measurement point
The measurement is triggered at point B, as shown in the figure. The measurement is triggered when the RNC successfully establishes the MBMS or IMB service and sends an MBMS SESSION START RESPONSE message to the PS domain. Figure 1-39 3-17 MBMS session (success procedure)
Issue 01 (2013-05-04)
127
Formula
None
Unit
None
Related Features
Counter Name VS.IU.MBMS.Succ Feature ID WRFD-010616 Feature Name MBMS Introduction Package
1.4.3.3 Number of MBMS or IMB Service Setup Failures on the Iu Interface Due to Different Causes Counters
Counter ID 67192079 67192080 Counter Name VS.IU.MBMS.Fail VS.IU.MBMS.Fail.NoRsrc Counter Description Number of Failed MBMS Service Establishments Number of Failed MBMS Service Establishments Due to No Resource Number of Failed MBMS Service Establishments Due to NNSF Number of Failed MBMS Service Establishments Due to Iu User Plane Failure Number of Failed MBMS Service Establishments Due to Iu Signaling Connection Failure
67192081
VS.IU.MBMS.Fail.NNSF
67192082
VS.IU.MBMS.Fail.IuUpFail
67192083
VS.IU.MBMS.Fail.IuSigFail
Description
These counters provide the number of times that an MBMS fails to be set up due to different causes.
Measurement point
The measurement is triggered at point B in the figure. When the RNC fails to set up an MBMS or IMB service, it sends an RANAP MBMS SESSION START FAILURE message to the PS CN and measures the corresponding counter based on the failure cause. Figure 1-40 MBMS session (failure procedure)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.MBMS.Fail VS.IU.MBMS.Fail.NoRsrc VS.IU.MBMS.Fail.NNSF Feature ID WRFD-010616 WRFD-010616 WRFD-010616 Feature Name MBMS Introduction Package MBMS Introduction Package MBMS Introduction Package
Issue 01 (2013-05-04)
129
Counter Name VS.IU.MBMS.Fail.IuUpFail VS.IU.MBMS.Fail.IuSigFail
Feature ID WRFD-010616 WRFD-010616
Feature Name MBMS Introduction Package MBMS Introduction Package
1.4.4 Measurement related to Iu interface(MOCN)(MOCN.IU)

Overview
This function subset of "Iu interface MOCN measurement" is used to measure the number of Redirect when the RAN supports the multiple operator core network (MOCN).
Counters
Counter ID 67193097 Counter Name VS.IU.MOCN.CsPs Coordination Counter Description Number of Redirection Requests from CN (CS/PS Coordination Required) Number of Redirection Requests from CN (Location Area Not Allowed) Number of Redirection Requests from CN (PLMN Not Allowed) Number of Redirection Requests from CN (Roaming Not Allowed in this Location Area) Number of Redirection Requests from CN (No Suitable Cell in Location Area) Original Release Earlier than V900R011
67193098
VS.IU.MOCN.LocAreaNotAllowed
67193099
VS.IU.MOCN.Plm nNotAllowed
67193100
VS.IU.MOCN.Roa mNotAllowed
67193101
VS.IU.MOCN.NoSuitableCell
Issue 01 (2013-05-04)
130
Counter ID 67193102
Counter Name VS.IU.MOCN.Gpr sServicesNotAllowed
Counter Description Number of Redirection Requests from CN (GPRS Services Not Allowed in this PLMN)
None
1.4.4.1 Number of Redirect for Different Causes Counters

Counter ID 67193097 Counter Name VS.IU.MOCN.CsPsCoordination VS.IU.MOCN.LocAreaNotAllowed VS.IU.MOCN.PlmnNotAllowed VS.IU.MOCN.RoamNotAllowed Counter Description Number of Redirection Requests from CN (CS/PS Coordination Required) Number of Redirection Requests from CN (Location Area Not Allowed) Number of Redirection Requests from CN (PLMN Not Allowed) Number of Redirection Requests from CN (Roaming Not Allowed in this Location Area) Number of Redirection Requests from CN (No Suitable Cell in Location Area) Number of Redirection Requests from CN (GPRS Services Not Allowed in this PLMN)
67193098
67193099
67193100
67193101
VS.IU.MOCN.NoSuitableCell
67193102
VS.IU.MOCN.GprsServicesNotAllowed
Description
The measurement counters provide the number of Redirect in the scenario of the MOCN for different causes.
Measurement point
The measurement is triggered at point B shown in Figure 1. When the RNC receives from the CN a DIRECT TRANSFER message with the Redirection Indication IE, the corresponding counter is measured on the basis of the cause value carried in the Redirection Indication IE. Figure 1-41 Process of INIT UE MESSAGE Redirect
Formula
None
Unit
None
Related Features
Counter Name VS.IU.MOCN.CsPsCoordination VS.IU.MOCN.LocAreaNotAllowed VS.IU.MOCN.PlmnNotAllowed Feature ID WRFD-021311 WRFD-021311 WRFD-021311 Feature Name MOCN Introduction Package MOCN Introduction Package MOCN Introduction Package
Issue 01 (2013-05-04)
132
Counter Name VS.IU.MOCN.RoamNotAllowed VS.IU.MOCN.NoSuitableCell VS.IU.MOCN.GprsServicesNotAllowed
Feature ID WRFD-021311 WRFD-021311 WRFD-021311
Feature Name MOCN Introduction Package MOCN Introduction Package MOCN Introduction Package
1.4.5 Measurement related to NAS signaling(NAS.IU)

Overview
The function subset Non-Access Stratum (NAS) Signaling Measurement on the Iu Interface measures the number of NAS interactions on the Iu interface. The method of measuring NASrelated counters on the RNC are different from those on the CN,and the later prevails.
Counters
Counter ID 73423785 Counter Name VS.IU.MM.LocUp d.Req Counter Description Number of Location Area Update Requests Forwarded by the RNC to the CN Number of Accepted Location Area Update Requests Received by the RNC from the CN Number of Accepted Routing Area Update Requests Received by the RNC from the CN Number of Attach Requests Forwarded by the RNC to the CN Number of Accepted Attach Requests Received by the RNC from the CN Original Release V900R014
73423786
VS.IU.MM.LocUp d.Acc
V900R014
73423788
VS.IU.GMM.RAU. Acc
V900R014
73423789
VS.IU.GMM.Attac h.Req VS.IU.GMM.Attac h.Acc
V900R014
73423790
V900R014
Issue 01 (2013-05-04)
133
Counter ID 73423791
Counter Name VS.IU.GMM.PDP Act.Req
Counter Description Number of PDP Activation Requests Forwarded by the RNC to the CN Number of Accepted PDP Activation Requests Received by the RNC from the CN Number of Service Setup Requests Forwarded by the RNC to the CN Number of Rejected Service Setup Requests Received by the RNC from the CN Number of Authentication Requests Received by the RNC from the CN Number of Authentication Responses Forwarded by the RNC to the CN Number of SECURITY MODE COMMAND Messages Received by the RNC from the CN Number of SECURITY MODE COMPLETE Messages Forwarded by the RNC to the CN Number of Routing Area Update Requests Forwarded by the RNC to the CN
73423792
VS.IU.GMM.PDP Act.Acc
V900R014
73423793
VS.IU.Sevice.Req
V900R014
73423794
VS.IU.Sevice.Rej
V900R014
73423795
VS.IU.Auth.Req
V900R014
73423796
VS.IU.Auth.Rsp
V900R014
73423797
VS.IU.SecModeCm d.Num
V900R014
73423798
VS.IU.SecModeCm p.Num
V900R014
73423799
VS.IU.GMM.RAU. Req
V900R014
Issue 01 (2013-05-04)
134
None
1.4.5.1 Number of Messages Forwarded by the RNC to the CN Counters

Counter ID 73423785 Counter Name VS.IU.MM.LocUpd.Req Counter Description Number of Location Area Update Requests Forwarded by the RNC to the CN Number of Attach Requests Forwarded by the RNC to the CN Number of PDP Activation Requests Forwarded by the RNC to the CN Number of Service Setup Requests Forwarded by the RNC to the CN Number of Routing Area Update Requests Forwarded by the RNC to the CN
73423789
VS.IU.GMM.Attach.Req
73423791
VS.IU.GMM.PDPAct.Req
73423793
VS.IU.Sevice.Req
73423799
VS.IU.GMM.RAU.Req
Description
These counters provide the number of various types of messages forwarded by the RNC to the CN.
Measurement point
The measurement is triggered at point A as shown in the figure. The measurement is triggered when the RNC forwards to the CN an INITIAL UE MESSAGE or DIRECT TRANSFER message from a UE. The RNC decodes the message, determines the message type based on decoding result, and increments the number of this type of messages by one in the corresponding CN node.
Issue 01 (2013-05-04)
135
Figure 1-42 Process of INIT UE MESSAGE Direct TRANSFER
Formula
None
Unit
None
Related Features
Counter Name VS.IU.MM.LocUpd.Req Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.IU.GMM.Attach.Req
WRFD-010510
VS.IU.GMM.PDPAct.Req
WRFD-010510
Issue 01 (2013-05-04)
136
Counter Name VS.IU.Sevice.Req
VS.IU.GMM.RAU.Req
WRFD-010510
1.4.5.2 Number of Messages Forwarded by the RNC from the CN Counters

Counter ID 73423786 Counter Name VS.IU.MM.LocUpd.Acc Counter Description Number of Accepted Location Area Update Requests Received by the RNC from the CN Number of Accepted Routing Area Update Requests Received by the RNC from the CN Number of Accepted Attach Requests Received by the RNC from the CN Number of Accepted PDP Activation Requests Received by the RNC from the CN Number of Rejected Service Setup Requests Received by the RNC from the CN
73423788
VS.IU.GMM.RAU.Acc
73423790
VS.IU.GMM.Attach.Acc
73423792
VS.IU.GMM.PDPAct.Acc
73423794
VS.IU.Sevice.Rej
Description
These counters provide the number of various types of messages forwarded by the RNC from the CN.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC forwards the UE a DIRECT TRANSFER message sent by the CN, the RNC decodes the message and
determines the message type based on decoding result. This counter is measured in the corresponding CN node based on the message type. Figure 1-43 Process of INIT UE MESSAGE Direct TRANSFER
Formula
None
Unit
None
Related Features
Counter Name VS.IU.MM.LocUpd.Acc Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.IU.GMM.RAU.Acc
WRFD-010510
Issue 01 (2013-05-04)
138
Counter Name VS.IU.GMM.Attach.Acc
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.IU.GMM.PDPAct.Acc
WRFD-010510
VS.IU.Sevice.Rej
WRFD-010510
1.4.5.3 Number of Authentication Requests Received by the RNC from the CN Counters
Counter ID 73423795 Counter Name VS.IU.Auth.Req Counter Description Number of Authentication Requests Received by the RNC from the CN
Description
This counter provides the number of authentication requests received by the RNC from the CN.
Measurement point
The measurement is triggered at point B as shown in the figure. The measurement is triggered when the RNC receives a DIRECT TRANSFER message sent by the CN and determines that this message is an authentication request based on the message decoding result. In this case, this counter is incremented by one in the corresponding CN node.
Issue 01 (2013-05-04)
139
Figure 1-44 Process of INIT UE MESSAGE Direct TRANSFER
Formula
None
Unit
None
Related Features
Counter Name VS.IU.Auth.Req Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.5.4 Number of Authentication Responses Forwarded by the RNC to the CN
Issue 01 (2013-05-04)
140
Counters
Counter ID 73423796 Counter Name VS.IU.Auth.Rsp Counter Description Number of Authentication Responses Forwarded by the RNC to the CN
Description
This counter provides the number of authentication responses forwarded by the RNC to the CN.
Measurement point
The measurement is triggered at point A as shown in the figure. The measurement is triggered when the RNC forwards to the CN a DIRECT TRANSFER message sent by a UE and determines that this message is an authentication response based on the message decoding result. In this case, this counter is incremented by one in the corresponding CN node. Figure 1-45 Process of INIT UE MESSAGE Direct TRANSFER
Formula
None
Unit
None
Related Features
Counter Name VS.IU.Auth.Rsp Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.5.5 Number of SECURITY MODE COMMAND Messages Received by the RNC from the CN Counters
Counter ID 73423797 Counter Name VS.IU.SecModeCmd.Num Counter Description Number of SECURITY MODE COMMAND Messages Received by the RNC from the CN
Description
This counter provides the number of SECURITY MODE COMMAND messages received by the RNC from the CN.
Measurement point
The measurement is triggered at point A as shown in the figure. The measurement is triggered when the RNC receives a SECURITY MODE COMMAND message sent from the CN. In this case, this counter is incremented by one in the corresponding CN node.
Issue 01 (2013-05-04)
142
Figure 1-46 Security mode control procedure (CN to RNC)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.SecModeCmd.Num Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.5.6 Number of SECURITY MODE COMPLETE Messages Forwarded by the RNC to the CN
Issue 01 (2013-05-04)
143
Counters
Counter ID 73423798 Counter Name VS.IU.SecModeCmp.Num Counter Description Number of SECURITY MODE COMPLETE Messages Forwarded by the RNC to the CN
Description
This counter provides the number of SECURITY MODE COMPLETE messages forwarded by the RNC to the CN.
Measurement point
The measurement is triggered at point B as shown in the figure. The measurement is triggered when the RNC forwards a SECURITY MODE COMPLETE message to the CN. In this case, this counter is incremented by one in the corresponding CN node. Figure 1-47 Security mode control procedure (CN to RNC)
Formula
None
Issue 01 (2013-05-04)
144
Unit
None
Related Features
Counter Name VS.IU.SecModeCmp.Num Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.6 Measurement related to PS Iu interface signalling(PS.SIG.IU)

Overview
This function subset aims at the connectionless signaling procedure and the signaling connection setup and release procedures on the Iu interface. In Iu Flex connection mode, the RNC measures the counters according to the PS CN nodes.
Counters
Counter ID 67176481 Counter Name VS.IU.ResetPS.Tx Counter Description Number of RESET Messages Sent by RNC to CN in PS Domain Number of RESET Messages Received by RNC from CN in PS Domain Number of INITIAL UE MESSAGE Messages Sent by RNC to CN in PS Domain Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain Original Release Earlier than V900R011
67176485
VS.IU.ResetPS.Rx
67189921
VS.IU.SIG.AttConnEstabPS
67176559
VS.IU.RelReqPS.su m
Issue 01 (2013-05-04)
145
Counter ID 67176565
Counter Name VS.IU.RelCmdPS.s um
Counter Description Number of IU RELEASE COMMAND Messages Received by RNC from CN in PS Domain Number of ERROR INDICATION Messages Sent by RNC to CN in PS Domain Number of ERROR INDICATION Messages Received by RNC from CN in PS Domain Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain (User Inactive) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain (Repeated Integrity Checking Failure) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain (UE Signaling Connection Release)
67176530
VS.IU.ErrInd.PS.T x
67176532
VS.IU.ErrInd.PS.R x
67176561
VS.IU.RelReqPS.U srInact
67176562
VS.IU.RelReqPS.In gChkFail
67176563
VS.IU.RelReqPS.Si gConnRel
Issue 01 (2013-05-04)
146
Counter ID 67176564
Counter Name VS.IU.RelReqPS.U ELost
Counter Description Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain (RL Out of Synchronization) Number of IU RELEASE COMMAND Messages Received by RNC from CN in PS Domain (Relocation Success) Number of IU RELEASE COMMAND Messages Received by RNC from CN in PS Domain (Normal Release) Number of IU RELEASE COMMAND Messages Received by RNC from CN in PS Domain (UTRAN Generated) Number of IU RELEASE COMMAND Messages Received by RNC from CN in PS Domain (Relocation Cancelled) Number of IU RELEASE COMMAND Messages Received by RNC from CN in PS Domain (No Remaining RAB)
67176566
VS.IU.RelCmdPS. RelocSucc
67176567
VS.IU.RelCmdPS. NormRel
67176568
VS.IU.RelCmdPS. UTRANGen
67176569
VS.IU.RelCmdPS. RelocCanl
67176570
VS.IU.RelCmdPS. NoRAB
Issue 01 (2013-05-04)
147
Counter ID 67176574
Counter Name VS.Iu.RelReqPS.RI PFail
Counter Description Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain (Failure in the Radio Interface Procedure) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain (RAB Preempted) Number of Performed PS Load Balancing by IMSI Users Number of Performed PS Load Balancing by TMSI Users Due to Invalid NRI Number of Performed PS Load Balancing by IMEI Users Number of Discarded PS Initial UE Messages when Signaling Flow Control is Triggered Number of Paging Messages Received by RNC from CN in PS Domain Number of RIM Requests from the eNodeB to the RNC (System Information)
67190183
VS.IU.RelReqPS.P reempt
67192541
VS.IU.Load.Route PS.IMSI
67192542
VS.IU.Load.Route PS.NRI
67192543
VS.IU.Load.Route PS.IMEI
67193096
VS.IU.FlowCtrl.Dis c.InitDT.PS
73424971
VS.IU.PS.Paging
V900R014
73426319
VS.IU.RIM.L2U.SI .Req
V900R015
Issue 01 (2013-05-04)
148
Counter ID 73426320
Counter Name VS.IU.RIM.L2U.SI .Resp
Counter Description Number of RIM Response Messages from the RNC to the eNodeB (System Information) Number of RIM Update Messages from the RNC to the eNodeB (System Information) Number of RIM acknowledgement messages from the eNodeB to the RNC (System Information) Number of RIM Requests from the eNodeB to the RNC (Load Information) Number of RIM Response Messages from the RNC to the eNodeB (Load Information) Number of RIM Update Messages from the RNC to the eNodeB (Load Information) Number of RIM Acknowledgement Messages from the eNodeB to the RNC (Load Information)
73426321
VS.IU.RIM.L2U.SI .Update
V900R015
73426322
VS.IU.RIM.L2U.SI .Update.ACK
V900R015
73426323
VS.IU.RIM.L2U.L oad.Req
V900R015
73426324
VS.IU.RIM.L2U.L oad.Resp
V900R015
73426325
VS.IU.RIM.L2U.L oad.Update
V900R015
73426326
VS.IU.RIM.L2U.L oad.Update.ACK
V900R015
None
1.4.6.1 Number of RESET Messages Initiated by RNC to PS Domain
Issue 01 (2013-05-04)
149
Counters
Counter ID 67176481 Counter Name VS.IU.ResetPS.Tx Counter Description Number of RESET Messages Sent by RNC to CN in PS Domain
Description
This measurement counter takes statistics of the number of RESET messages that the RNC sends to the PS domain. The RNC measures this counter according to the CN nodes.
Measurement point
The measurement is triggered when the RNC sends a RESET message to the PS domain of the CN, as shown by point A in the following figure. If the RNC does not receive the RESET ACKNOWLEDGE message from the CN before the response timer expires, the RNC sends the RESET message again and this counter is also measured again. Figure 1-48 PS domain reset procedure initiated by the RNC (successful operation)
Formula
None
Issue 01 (2013-05-04)
150
Unit
None
Related Features
Counter Name VS.IU.ResetPS.Tx Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.6.2 Number of RESET Messages Received by RNC from PS Domain Counters

Counter ID 67176485 Counter Name VS.IU.ResetPS.Rx Counter Description Number of RESET Messages Received by RNC from CN in PS Domain
Description
This measurement counter takes statistics of the number of RESET messages that the PS domain sends to the RNC. The RNC measures this counter according to the CN nodes.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives a RESET message from the PS domain, it measures this counter.
Issue 01 (2013-05-04)
151
Figure 1-49 PS domain reset procedure initiated by the CN (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.ResetPS.Rx Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.6.3 Number of INITIAL UE MESSAGE Messages from RNC to PS Domain
Issue 01 (2013-05-04)
152
Counters
Counter ID 67189921 Counter Name VS.IU.SIG.AttConnEstabPS Counter Description Number of INITIAL UE MESSAGE Messages Sent by RNC to CN in PS Domain
Description
This measurement counter takes statistics of the number of INITIAL UE MESSAGE messages that the RNC sends to the PS domain. The RNC measures this counter according to the CN nodes.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends an INITIAL UE MESSAGE to the PS domain, it measures this counter. Figure 1-50 Initial UE message procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IU.SIG.AttConnEstabPS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.6.4 Number of IU RELEASE REQUEST Messages from RNC to PS Domain Counters

Counter ID 67176559 Counter Name VS.IU.RelReqPS.sum Counter Description Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain
Description
This counter provides the number of IU RELEASE REQUEST messages sent by the RNC to the PS domain of the CN. The IU RELEASE REQUEST message is sent by the RNC to release an Iu signaling connection between the specific UE and the PS domain because of a UTRAN cause. The counter is measured based on the CN node to which the message is sent.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends an IU RELEASE REQUEST message to the PS domain, it measures this counter. Figure 1-51 Iu release procedure (successful operation)
Issue 01 (2013-05-04)
154
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RelReqPS.sum Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.6.5 Number of IU RELEASE COMMAND Messages from PS Domain to RNC Counters

Counter ID 67176565 Counter Name VS.IU.RelCmdPS.sum Counter Description Number of IU RELEASE COMMAND Messages Received by RNC from CN in PS Domain
Description
This measurement counter takes statistics of the number of IU RELEASE COMMAND messages that the PS domain sends to the RNC. The RNC measures this counter according to the CN nodes. The Iu release procedure of the PS domain is a procedure to release the Iu connection and all the UTRAN resources related to the Iu connection.
Measurement point
The measurement is triggered at point B, as shown in the figure. In the RNC-initiated Iu release procedure, when the RNC receives an IU RELEASE COMMAND message from the PS domain, it measures this counter.
Issue 01 (2013-05-04)
155
The measurement is triggered at point A, as shown in the figure. In the CN-initiated Iu release procedure, when the RNC receives an IU RELEASE COMMAND message from the PS domain, it measures this counter. Figure 1-53 Iu release procedure initiated by the CN (successful operation)
Issue 01 (2013-05-04)
156
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RelCmdPS.sum Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.6.6 Number of ERROR INDICATION Messages from RNC to PS Domain Counters

Counter ID 67176530 Counter Name VS.IU.ErrInd.PS.Tx Counter Description Number of ERROR INDICATION Messages Sent by RNC to CN in PS Domain
Description
This measurement counter takes statistics of the number of ERROR INDICATION messages that the RNC sends to the PS domain.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends an ERROR INDICATION message to the PS domain, it measures this counter.
Issue 01 (2013-05-04)
157
Figure 1-54 Error indication procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.IU.ErrInd.PS.Tx Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.6.7 Number of ERROR INDICATION Messages from PS Domain to RNC
Issue 01 (2013-05-04)
158
Counters
Counter ID 67176532 Counter Name VS.IU.ErrInd.PS.Rx Counter Description Number of ERROR INDICATION Messages Received by RNC from CN in PS Domain
Description
This measurement counter takes statistics of the number of ERROR INDICATION messages that the PS domain sends to the RNC according to respective CN nodes.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives an ERROR INDICATION message from the PS domain, it measures this counter according to the CN nodes. Figure 1-55 Error indication procedure initiated by the CN
Formula
None
Issue 01 (2013-05-04)
159
Unit
None
Related Features
Counter Name VS.IU.ErrInd.PS.Rx Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.6.8 Number of IU RELEASE REQUEST Messages from RNC to PS Domain for Different Causes Counters
Counter ID 67176561 Counter Name VS.IU.RelReqPS.UsrInact Counter Description Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain (User Inactive) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain (Repeated Integrity Checking Failure) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain (UE Signaling Connection Release) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain (RL Out of Synchronization) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain (Failure in the Radio Interface Procedure) Number of IU RELEASE REQUEST Messages Sent by RNC to CN in PS Domain (RAB Preempted)
160
67176562
VS.IU.RelReqPS.IngChkFail
67176563
VS.IU.RelReqPS.SigConnRel
67176564
VS.IU.RelReqPS.UELost
67176574
VS.Iu.RelReqPS.RIPFail
67190183
VS.IU.RelReqPS.Preempt
Issue 01 (2013-05-04)
Description
These measurement counters take statistics of the number of IU RELEASE REQUEST messages that the RNC sends to the PS domain according to different Iu release request causes and respective CN nodes.Those release causes are just a part of release causes defined by protocol 25.413, and the other causes according to specification will be added into VS.IU.RelReqPS.sum.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends an IU RELEASE REQUEST message to the PS domain, it measures these counters according to different causes. Figure 1-56 Iu release procedure (successful operation)
Formula
None
Unit
None
Issue 01 (2013-05-04)
161
Related Features
Counter Name VS.IU.RelReqPS.UsrInact Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Queuing and Pre-Emption 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.IU.RelReqPS.IngChkFail
WRFD-010510
VS.IU.RelReqPS.SigConnRel
WRFD-010510
VS.IU.RelReqPS.UELost
WRFD-010510
VS.Iu.RelReqPS.RIPFail
WRFD-010510
VS.IU.RelReqPS.Preempt
WRFD-010505 WRFD-010510
1.4.6.9 Number of IU RELEASE COMMAND Messages from PS Domain to RNC for Different Causes Counters
Counter ID 67176566 Counter Name VS.IU.RelCmdPS.RelocSucc Counter Description Number of IU RELEASE COMMAND Messages Received by RNC from CN in PS Domain (Relocation Success)
Issue 01 (2013-05-04)
162
Counter ID 67176567
Counter Name VS.IU.RelCmdPS.NormRel
Counter Description Number of IU RELEASE COMMAND Messages Received by RNC from CN in PS Domain (Normal Release) Number of IU RELEASE COMMAND Messages Received by RNC from CN in PS Domain (UTRAN Generated) Number of IU RELEASE COMMAND Messages Received by RNC from CN in PS Domain (Relocation Cancelled) Number of IU RELEASE COMMAND Messages Received by RNC from CN in PS Domain (No Remaining RAB)
67176568
VS.IU.RelCmdPS.UTRANGen
67176569
VS.IU.RelCmdPS.RelocCanl
67176570
VS.IU.RelCmdPS.NoRAB
Description
These measurement counters take statistics of the number of IU RELEASE COMMAND messages that the RNC receives from the PS domain according to different Iu connection release causes according to respective CN nodes.
Measurement point
1) The measurement is triggered at point B, as shown in the figure. In the RNC-initiated Iu release procedure, when the RNC receives an IU RELEASE COMMAND message from the PS domain, it measures these counters.
Issue 01 (2013-05-04)
163
2) The measurement is triggered at point A, as shown in the figure. In the CN-initiated Iu release procedure, when the RNC receives an IU RELEASE COMMAND message from the PS domain, it measures these counters. Figure 1-58 Iu release procedure initiated by the CN (successful operation)
Issue 01 (2013-05-04)
164
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RelCmdPS.RelocSucc Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.IU.RelCmdPS.NormRel
WRFD-010510
VS.IU.RelCmdPS.UTRANGen
WRFD-010510
VS.IU.RelCmdPS.RelocCanl
WRFD-010510
VS.IU.RelCmdPS.NoRAB
WRFD-010510
1.4.6.10 Load Balancing of the MSC Pool on the PS Domain Counters

Counter ID 67192541 Counter Name VS.IU.Load.RoutePS.IMSI Counter Description Number of Performed PS Load Balancing by IMSI Users Number of Performed PS Load Balancing by TMSI Users Due to Invalid NRI
67192542
VS.IU.Load.RoutePS.NRI
Issue 01 (2013-05-04)
165
Counter ID 67192543
Counter Name VS.IU.Load.RoutePS.IMEI
Counter Description Number of Performed PS Load Balancing by IMEI Users
Description
The measurement counters provide the number of times that the UEs perform load balancing on the PS domain during CN node selection when the RNC processes the initial direct transfer message. The following table describes the meaning of each counter. Counter Name VS.IU.Load.RoutePS.IMSI Description Number of times that the PS CN is selected for load balancing by using the IMSI route parameter. Number of times that load balancing is triggered due to invalid NRI route parameter, connection failure to the CN node corresponding to the route parameter, or the flow control of the CN node corresponding to the route parameter. Number of times that the PS CN is selected for load balancing by using the IMEI route parameter.
VS.IU.Load.RoutePS.NRI
VS.IU.Load.RoutePS.IMEI
Measurement point
The measurement is triggered when the RNC sends an INITIAL UE MESSAGE message to the PS CN for load balancing, as shown by point A in the following figure. The corresponding counter is measured on the basis of the UE identification carried in the INITIAL DIRECT TRANSFER message from the UE to the RNC.
Issue 01 (2013-05-04)
166
Figure 1-59 Initial UE message procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IU.Load.RoutePS.IMSI VS.IU.Load.RoutePS.NRI VS.IU.Load.RoutePS.IMEI Feature ID WRFD-021306 WRFD-021306 WRFD-021306 Feature Name Iu Flex Load Distribution Management Iu Flex Load Distribution Management Iu Flex Load Distribution Management
1.4.6.11 Number of Discarded Initial UE messages Under Iu Signaling Flow Control (PS Domain)
Issue 01 (2013-05-04)
167
Counters
Counter ID 67193096 Counter Name VS.IU.FlowCtrl.Disc.InitDT .PS Counter Description Number of Discarded PS Initial UE Messages when Signaling Flow Control is Triggered
Description
This measurement counter provides the number of initial UE messages discarded under the SCCP flow control when the RNC receives the PS initial direct transfer message.
Measurement point
The measurement is triggered when the RNC receives an INITIAL DIRECT TRANSFER message from a UE and then discards this message because the RNC finds that the Iu-PS interface is under flow control. Then, the RNC does not send the INITIAL UE MESSAGE message to the CN. Figure 1-60 Process of discarding INITIAL DIRECT TRANSFER message
Formula
None
Unit
None
Related Features
Counter Name VS.IU.FlowCtrl.Disc.InitDT .PS Feature ID WRFD-040100 Feature Name Flow Control
1.4.6.12 Number of Paging Messages Received by RNC from CN in PS Domain Counters

Counter ID 73424971 Counter Name VS.IU.PS.Paging Counter Description Number of Paging Messages Received by RNC from CN in PS Domain
Description
This measurement counter provides the number of PAGING messages that the PS domain sends to the RNC according to respective CN nodes.
Measurement point
The measurement is triggered at point A shown in the following figure when both of the following conditions are met: -The RNC receives a paging message from the CN. -The value of the CN Domain Indicator IE contained in the message indicates the PS domain. Figure 1-61 Paging messages sent from the CN to the UE
Issue 01 (2013-05-04)
169
Formula
None
Unit
None
Related Features
Counter Name VS.IU.PS.Paging Feature ID WRFD-010301 WRFD-010302 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) Paging UE in CELL_FACH, CELL_DCH State (Type 2)
1.4.6.13 Number of RIM Requests from the eNodeB to the RNC (System Information) Counters
Counter ID 73426319 Counter Name VS.IU.RIM.L2U.SI.Req Counter Description Number of RIM Requests from the eNodeB to the RNC (System Information)
Description
This counter provides the number of RIM requests with system information the RNC receives from the eNodeB. The RIM requests include RAN-INFORMATION-REQUEST/Single Report and RAN-INFORMATION-REQUEST/Multiple Report.
Measurement point
The measurement is triggered at point A as shown in Figure 1. This counter is incremented by 1 when the RNC receives the RAN-INFORMATION-REQUEST/Single Report or RANINFORMATION-REQUEST/Multiple Report message with system information from the eNodeB on the Iu interface.
Issue 01 (2013-05-04)
170
Figure 1-62 RIM message procedure(single mode)
The measurement is triggered at point A as shown in Figure 2. This counter is incremented by 1 when the RNC receives the RAN-INFORMATION-REQUEST/Single Report or RANINFORMATION-REQUEST/Multiple Report message with system information from the eNodeB on the Iu interface. Figure 1-63 RIM message procedure(Multiple mode)
Issue 01 (2013-05-04)
171
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RIM.L2U.SI.Req Feature ID WRFD-140224 Feature Name Fast CS Fallback Based on RIM
1.4.6.14 Number of RIM Response Messages from the RNC to the eNodeB (System Information) Counters
Counter ID 73426320 Counter Name VS.IU.RIM.L2U.SI.Resp Counter Description Number of RIM Response Messages from the RNC to the eNodeB (System Information)
Description
This counter provides the number of RIM response messages with system information the RNC sends to the eNodeB. The RIM response messages include RAN-INFORMATION/Single Report and RAN-INFORMATION/Multiple Report-Initial.
Measurement point
The measurement is triggered at point B as shown in Figure 1. This counter is incremented by 1 when the RNC sends to the eNodeB the RAN-INFORMATION/Single Report or RANINFORMATION/Multiple Report-Initial message with system information on the Iu interface.
Issue 01 (2013-05-04)
172
Figure 1-64 RIM message procedure(single mode)
The measurement is triggered at point B as shown in Figure 2. This counter is incremented by 1 when the RNC sends to the eNodeB the RAN-INFORMATION/Single Report or RANINFORMATION/Multiple Report-Initial message with system information on the Iu interface. Figure 1-65 RIM message procedure(Multiple mode)
Issue 01 (2013-05-04)
173
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RIM.L2U.SI.Resp Feature ID WRFD-140224 Feature Name Fast CS Fallback Based on RIM
1.4.6.15 Number of RIM Update Messages from the RNC to the eNodeB (System Information) Counters
Counter ID 73426321 Counter Name VS.IU.RIM.L2U.SI.Update Counter Description Number of RIM Update Messages from the RNC to the eNodeB (System Information)
Description
This counter provides the number of RIM update messages with system information the RNC sends to the eNodeB. The RAN-INFORMATION/Multiple Report-Initial message is excluded.
Measurement point
The measurement is triggered at point C as shown in Figure 2. This counter is incremented by 1 when the RNC sends to the eNodeB the RAN-INFORMATION/Multiple Report message with system information on the Iu interface.
Issue 01 (2013-05-04)
174
Figure 1-66 RIM message procedure(Multiple mode)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RIM.L2U.SI.Update Feature ID WRFD-140224 Feature Name Fast CS Fallback Based on RIM
1.4.6.16 Number of RIM acknowledgement messages from the eNodeB to the RNC (System Information)
Issue 01 (2013-05-04)
175
Counters
Counter ID 73426322 Counter Name VS.IU.RIM.L2U.SI.Update. ACK Counter Description Number of RIM acknowledgement messages from the eNodeB to the RNC (System Information)
Description
This counter provides the number of RIM acknowledgement messages with system information the RNC receives from the eNodeB.
Measurement point
The measurement is triggered at point D as shown in Figure 2. This counter is incremented by 1 when the RNC receives the RAN-INFORMATION-ACK message with system information from the eNodeB on the Iu interface. Figure 1-67 RIM message procedure(Multiple mode)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RIM.L2U.SI.Update. ACK Feature ID WRFD-140224 Feature Name Fast CS Fallback Based on RIM
1.4.6.17 Number of RIM Requests from the eNodeB to the RNC (Load Information) Counters
Counter ID 73426323 Counter Name VS.IU.RIM.L2U.Load.Req Counter Description Number of RIM Requests from the eNodeB to the RNC (Load Information)
Description
This counter provides the number of RIM requests with load information the RNC receives from the eNodeB. The RIM requests include RAN-INFORMATION-REQUEST/Single Report and RAN-INFORMATION-REQUEST/Multiple Report.
Measurement point
The measurement is triggered at point A as shown in Figure 1. This counter is incremented by 1 when the RNC receives the RAN-INFORMATION-REQUEST/Single Report or RANINFORMATION-REQUEST/Multiple Report message with load information from the eNodeB on the Iu interface. Figure 1-68 RIM message procedure(single mode)
Issue 01 (2013-05-04)
177
The measurement is triggered at point A as shown in Figure 2. This counter is incremented by 1 when the RNC receives the RAN-INFORMATION-REQUEST/Single Report or RANINFORMATION-REQUEST/Multiple Report message with load information from the eNodeB on the Iu interface. Figure 1-69 RIM message procedure(Multiple mode)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RIM.L2U.Load.Req Feature ID WRFD-150230 Feature Name DPCH Pilot Power Adjustment
Issue 01 (2013-05-04)
178
1.4.6.18 Number of RIM Response Messages from the RNC to the eNodeB (Load Information) Counters
Counter ID 73426324 Counter Name VS.IU.RIM.L2U.Load.Resp Counter Description Number of RIM Response Messages from the RNC to the eNodeB (Load Information)
Description
This counter provides the number of RIM response messages with load information the RNC sends to the eNodeB. The RIM response messages include RAN-INFORMATION/Single Report and RAN-INFORMATION/Multiple Report-Initial.
Measurement point
The measurement is triggered at point B as shown in Figure 1. This counter is incremented by 1 when the RNC sends to the eNodeB the RAN-INFORMATION/Single Report or RANINFORMATION/Multiple Report-Initial message with load information on the Iu interface. Figure 1-70 RIM message procedure(single mode)
The measurement is triggered at point B as shown in Figure 2. This counter is incremented by 1 when the RNC sends to the eNodeB the RAN-INFORMATION/Single Report or RANINFORMATION/Multiple Report-Initial message with load information on the Iu interface.
Issue 01 (2013-05-04)
179
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RIM.L2U.Load.Resp Feature ID WRFD-150230 Feature Name DPCH Pilot Power Adjustment
1.4.6.19 Number of RIM Update Messages from the RNC to the eNodeB (Load Information)
Issue 01 (2013-05-04)
180
Counters
Counter ID 73426325 Counter Name VS.IU.RIM.L2U.Load.Update Counter Description Number of RIM Update Messages from the RNC to the eNodeB (Load Information)
Description
This counter provides the number of RIM update messages with load information the RNC sends to the eNodeB. The RAN-INFORMATION/Multiple Report-Initial message is excluded.
Measurement point
The measurement is triggered at point C as shown in Figure 2. This counter is incremented by 1 when the RNC sends to the eNodeB the RAN-INFORMATION/Multiple Report message with load information on the Iu interface. Figure 1-72 RIM message procedure(Multiple mode)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RIM.L2U.Load.Update Feature ID WRFD-150230 Feature Name DPCH Pilot Power Adjustment
1.4.6.20 Number of RIM Acknowledgement Messages from the eNodeB to the RNC (Load Information) Counters
Counter ID 73426326 Counter Name VS.IU.RIM.L2U.Load.Upda te.ACK Counter Description Number of RIM Acknowledgement Messages from the eNodeB to the RNC (Load Information)
Description
This counter provides the number of RIM acknowledgement messages with load information the RNC receives from the eNodeB.
Measurement point
The measurement is triggered at point D as shown in Figure 2. This counter is incremented by 1 when the RNC receives the RAN-INFORMATION-ACK message with load information from the eNodeB on the Iu interface.
Issue 01 (2013-05-04)
182
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RIM.L2U.Load.Upda te.ACK Feature ID WRFD-150230 Feature Name DPCH Pilot Power Adjustment
1.4.7 Measurement related to PS traffic(PS.TRF.IU)

Overview
This function subset is used to measure the UL and DL traffic for various services of the PS domain on the Iu interface.Without specific instructions,the measurement contains the header of GTPU.
Counters
Counter ID 67203893 Counter Name VS.IuPS.BytesPayl dConv.Tx Counter Description Number of UL Bytes of PS Conversational Service on Iu-PS Interface Number of UL Bytes of PS Streaming Service on Iu-PS Interface Number of UL Bytes of PS Interactive Service on Iu-PS Interface Number of UL Bytes of PS Background Service on Iu-PS Interface Number of DL Bytes of PS Conversational Service on Iu-PS Interface Number of DL Bytes of PS Streaming Service on Iu-PS Interface Number of DL Bytes of PS Interactive Service on Iu-PS Interface Number of DL Bytes of PS Background Service on Iu-PS Interface Number of UL Bytes of PS BE Service for Golden Subscriber on Iu-PS Interface Number of UL Bytes of PS BE Service for Silver Subscriber on Iu-PS Interface Original Release Earlier than V900R011
67203894
VS.IuPS.BytesPayl dStr.Tx
67203897
VS.IuPS.BytesPayl dIntact.Tx
67203898
VS.IuPS.BytesPayl dBgrd.Tx
67203895
VS.IuPS.BytesPayl dConv.Rx
67203896
VS.IuPS.BytesPayl dStr.Rx
67203899
VS.IuPS.BytesPayl dIntact.Rx
67203900
VS.IuPS.BytesPayl dBgrd.Rx
67204829
VS.IuPS.GoldenBE .Bytes.Tx
67204830
VS.IuPS.SilverBE. Bytes.Tx
Issue 01 (2013-05-04)
184
Counter ID 67204831
Counter Name VS.IuPS.CopperB E.Bytes.Tx
Counter Description Number of UL Bytes of PS BE Service for Copper Subscriber on Iu-PS Interface Number of DL Bytes of PS BE Service for Golden Subscriber on Iu-PS Interface Number of DL Bytes of PS BE Service for Silver Subscriber on Iu-PS Interface Number of DL Bytes of PS BE Service for Copper Subscriber on Iu-PS Interface Total HTTP Traffic Volume on the RNC Total P2P Traffic Volume on the RNC Total Traffic Volume of all Subscribed Services on the RNC Total Traffic Volume of Undefined Services on the RNC Traffic Volume of Services Cannot Be Identified by the RNC on Downlink
67204832
VS.IuPS.GoldenBE .Bytes.Rx
67204833
VS.IuPS.SilverBE. Bytes.Rx
67204834
VS.IuPS.CopperB E.Bytes.Rx
73441084 73441081 73441082
VS.IuPS.BytesPayl dHTTP.Rx VS.IuPS.BytesPayl dP2P.Rx VS.IuPS.BytesPayl dSubs.Rx VS.IuPS.BytesPayl dUndefined.Rx VS.IuPS.BytesPayl dUnawareness.RX
V900R013 V900R013 V900R013
73441083
V900R013
73426124
V900R015
None
1.4.7.1 Number of UL Bytes of PS Conversational Service on Iu Interface
Issue 01 (2013-05-04)
185
Counters
Counter ID 67203893 Counter Name VS.IuPS.BytesPayldConv.T x Counter Description Number of UL Bytes of PS Conversational Service on Iu-PS Interface
Description
This counter provides the number of UL payload bytes of PS Conversational service data on the Iu-PS interface sent by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When receiving the UL PS Conversational service data on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldConv.T x Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.4.7.2 Number of UL Bytes of PS Streaming Service on Iu Interface Counters

Counter ID 67203894 Counter Name VS.IuPS.BytesPayldStr.Tx Counter Description Number of UL Bytes of PS Streaming Service on Iu-PS Interface
Issue 01 (2013-05-04)
186
Description
This counter provides the number of UL payload bytes of PS streaming service data on the IuPS interface sent by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When receiving the UL PS streaming service data on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldStr.Tx Feature ID WRFD-010502 Feature Name Streaming QoS Class
1.4.7.3 Number of UL Bytes of PS Interactive Service on Iu Interface Counters

Counter ID 67203897 Counter Name VS.IuPS.BytesPayldIntact.T x Counter Description Number of UL Bytes of PS Interactive Service on Iu-PS Interface
Description
This counter provides the number of UL payload bytes of PS interactive service data on the IuPS interface sent by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When receiving the UL PS interactive service data on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldIntact.T x Feature ID WRFD-010503 Feature Name Interactive QoS Class
1.4.7.4 Number of UL Bytes of PS Background Service on Iu Interface Counters

Counter ID 67203898 Counter Name VS.IuPS.BytesPayldBgrd.T x Counter Description Number of UL Bytes of PS Background Service on IuPS Interface
Description
This counter provides the number of UL payload bytes of PS background service data on the IuPS interface sent by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When receiving the UL PS background service data on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldBgrd.T x Feature ID WRFD-010504 Feature Name Background QoS Class
Issue 01 (2013-05-04)
188
1.4.7.5 Number of DL Bytes of PS Conversational Service on Iu Interface Counters

Counter ID 67203895 Counter Name VS.IuPS.BytesPayldConv.R x Counter Description Number of DL Bytes of PS Conversational Service on Iu-PS Interface
Description
This counter provides the number of DL payload bytes of PS Conversational service data on the Iu-PS interface received by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When receiving the DL PS Conversational service data on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldConv.R x Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.4.7.6 Number of DL Bytes of PS Streaming Service on Iu Interface Counters

Counter ID 67203896 Counter Name VS.IuPS.BytesPayldStr.Rx Counter Description Number of DL Bytes of PS Streaming Service on Iu-PS Interface
Issue 01 (2013-05-04)
189
Description
This counter provides the number of DL payload bytes of PS streaming service data on the IuPS interface received by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When receiving the DL PS streaming service data on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldStr.Rx Feature ID WRFD-010502 Feature Name Streaming QoS Class
1.4.7.7 Number of DL Bytes of PS Interactive Service on Iu Interface Counters

Counter ID 67203899 Counter Name VS.IuPS.BytesPayldIntact.R x Counter Description Number of DL Bytes of PS Interactive Service on Iu-PS Interface
Description
This counter provides the number of DL payload bytes of PS interactive service data on the IuPS interface received by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When receiving the DL PS interactive service data on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldIntact.R x Feature ID WRFD-010503 Feature Name Interactive QoS Class
1.4.7.8 Number of DL Bytes of PS Background Service on Iu Interface Counters

Counter ID 67203900 Counter Name VS.IuPS.BytesPayldBgrd.R x Counter Description Number of DL Bytes of PS Background Service on IuPS Interface
Description
This counter provides the number of DL payload bytes of PS background service data on the IuPS interface received by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When receiving the DL PS background service data on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldBgrd.R x Feature ID WRFD-010504 Feature Name Background QoS Class
Issue 01 (2013-05-04)
191
1.4.7.9 Number of UL Bytes of PS BE Service for Golden Subscriber on Iu Interface Counters

Counter ID 67204829 Counter Name VS.IuPS.GoldenBE.Bytes.T x Counter Description Number of UL Bytes of PS BE Service for Golden Subscriber on Iu-PS Interface
Description
This counter provides the number of UL payload bytes of PS BE service data for golden subscriber on the Iu-PS interface sent by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When sending the UL data of PS BE service for golden subscriber on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.GoldenBE.Bytes.T x Feature ID WRFD-02130403 Feature Name Mobility Control and Service Differentiation
1.4.7.10 Number of UL Bytes of PS BE Service for Silver Subscriber on Iu Interface Counters

Counter ID 67204830 Counter Name VS.IuPS.SilverBE.Bytes.Tx Counter Description Number of UL Bytes of PS BE Service for Silver Subscriber on Iu-PS Interface
Issue 01 (2013-05-04)
192
Description
This counter provides the number of UL payload bytes of PS BE service data for silver subscriber on the Iu-PS interface sent by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When sending the UL PS BE service data for silver subscriber on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.SilverBE.Bytes.Tx Feature ID WRFD-02130403 Feature Name Mobility Control and Service Differentiation
1.4.7.11 Number of UL Bytes of PS BE Service for Copper Subscriber on Iu Interface Counters

Counter ID 67204831 Counter Name VS.IuPS.CopperBE.Bytes.T x Counter Description Number of UL Bytes of PS BE Service for Copper Subscriber on Iu-PS Interface
Description
This counter provides the number of UL payload bytes of PS BE service data for copper subscriber on the Iu-PS interface sent by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When sending the UL PS BE service data for copper subscriber on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.CopperBE.Bytes.T x Feature ID WRFD-02130403 Feature Name Mobility Control and Service Differentiation
1.4.7.12 Number of DL Bytes of PS BE Service for Golden Subscriber on Iu Interface Counters

Counter ID 67204832 Counter Name VS.IuPS.GoldenBE.Bytes.R x Counter Description Number of DL Bytes of PS BE Service for Golden Subscriber on Iu-PS Interface
Description
This counter provides the number of DL payload bytes of PS BE service data for golden subscriber on the Iu-PS interface received by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When receiving the DL PS BE service data for golden subscriber on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Issue 01 (2013-05-04)
194
Related Features
Counter Name VS.IuPS.GoldenBE.Bytes.R x Feature ID WRFD-02130403 Feature Name Mobility Control and Service Differentiation
1.4.7.13 Number of DL Bytes of PS BE Service for Silver Subscriber on Iu Interface Counters

Counter ID 67204833 Counter Name VS.IuPS.SilverBE.Bytes.Rx Counter Description Number of DL Bytes of PS BE Service for Silver Subscriber on Iu-PS Interface
Description
This counter provides the number of DL payload bytes of PS BE service data for silver subscriber on the Iu-PS interface received by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When receiving the DL PS BE service data for silver subscriber on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.SilverBE.Bytes.Rx Feature ID WRFD-02130403 Feature Name Mobility Control and Service Differentiation
1.4.7.14 Number of DL Bytes of PS BE Service for Copper Subscriber on Iu Interface

Counters
Counter ID 67204834 Counter Name VS.IuPS.CopperBE.Bytes.R x Counter Description Number of DL Bytes of PS BE Service for Copper Subscriber on Iu-PS Interface
Description
This counter provides the number of DL payload bytes of PS BE service data for copper subscriber on the Iu-PS interface received by the RNC. The value of this counter includes the bytes of application layer data without GTPU head.
Measurement point
When receiving the DL PS BE service data for copper subscriber on the Iu-PS interface, the RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.CopperBE.Bytes.R x Feature ID WRFD-02130403 Feature Name Mobility Control and Service Differentiation
1.4.7.15 Total HTTP Traffic Volume on the RNC Counters

Counter ID 73441084 Counter Name VS.IuPS.BytesPayldHTTP. Rx Counter Description Total HTTP Traffic Volume on the RNC
Description
This counter provides the number of bytes of downlink HTTP services received on the Iu-PS interface of the RNC. It includes the data at the application layer and excludes the GTP-U header.
The HTTP service type is identified by service awareness when the Web Browsing Acceleration feature is enabled.
Measurement point
This measurement is triggered on different Iu-PS interfaces when the RNC receives the downlink HTTP traffic data on Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldHTTP. Rx Feature ID WRFD-020132 Feature Name Web browsing acceleration
1.4.7.16 Total P2P Traffic Volume on the RNC Counters

Counter ID 73441081 Counter Name VS.IuPS.BytesPayldP2P.Rx Counter Description Total P2P Traffic Volume on the RNC
Description
This counter provides the number of bytes of downlink P2P services received on the Iu-PS interface of the RNC. It includes the data at the application layer and excludes the GTP-U header. The P2P service type is identified by service awareness when the P2P Downloading Rate Control during Busy Hour feature is enabled.
Measurement point
This measurement is triggered on different Iu-PS interfaces when the RNC receives the downlink P2P traffic data on Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldP2P.Rx Feature ID WRFD-020133 Feature Name P2P Downloading Rate Control during Busy Hour
1.4.7.17 Total Traffic Volume of all Subscribed Services on the RNC Counters
Counter ID 73441082 Counter Name VS.IuPS.BytesPayldSubs.R x Counter Description Total Traffic Volume of all Subscribed Services on the RNC
Description
This counter provides the number of bytes of downlink subscribed services received on the IuPS interface of the RNC. It includes the data at the application layer and excludes the GTPU header. The subscribed service is defined by the Quality Improvement for Subscribed Service feature.
Measurement point
This measurement is triggered on different Iu-PS interfaces when the RNC receives the downlink data of subscribed services on Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldSubs.R x Feature ID WRFD-020128 Feature Name Quality Improvement for Subscribed Service
Issue 01 (2013-05-04)
198
1.4.7.18 Total Traffic Volume of Undefined Services on the RNC Counters

Counter ID 73441083 Counter Name VS.IuPS.BytesPayldUndefin ed.Rx Counter Description Total Traffic Volume of Undefined Services on the RNC
Description
This counter provides the number of bytes of downlink undefined services received on the IuPS interface of the RNC. It includes the data at the application layer and excludes the GTP-U header. Undefined services are services other than the HTTP services, P2P services, subscribed services, and unidentified services.
Measurement point
This measurement is triggered on different Iu-PS interfaces when the RNC receives the downlink data of undefined services on Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldUndefin ed.Rx Feature ID WRFD-020132 WRFD-020133 WRFD-020128 Feature Name Web browsing acceleration P2P Downloading Rate Control during Busy Hour Quality Improvement for Subscribed Service
1.4.7.19 Traffic Volume of Services Cannot Be Identified by the RNC on Downlink
Issue 01 (2013-05-04)
199
Counters
Counter ID 73426124 Counter Name VS.IuPS.BytesPayldUnawar eness.RX Counter Description Traffic Volume of Services Cannot Be Identified by the RNC on Downlink
Description
This counter provides the number of bytes of downlink unidentified services received on the IuPS interface of the RNC. It includes the data at the application layer and excludes the GTPU header. Unidentified services are those whose service type cannot be identified by service awareness.
Measurement point
The measurement is triggered when the RNC receives downlink service data on the Iu-PS interface. The traffic volume is measured on each Iu-PS interface separately.
Formula
None
Unit
byte
Related Features
Counter Name VS.IuPS.BytesPayldUnawar eness.RX Feature ID WRFD-020132 WRFD-020133 WRFD-020128 Feature Name Web browsing acceleration P2P Downloading Rate Control during Busy Hour Quality Improvement for Subscribed Service
1.4.8 Measurement Related to SCCP for Iu Interface(SIG.SCCP.IU)

Overview
Measurement related to SCCP for Iu interface provides the counters related to the numbers of the RNC-initiated SCCP connection requests, RNC-initiated successful SCCP connection requests, CN-initiated SCCP connection requests, and CN-initiated successful SCCP connection requests.
Counters
Counter ID 67195049 Counter Name VS.IU.SCCP.Tx.Co n.Req Counter Description Number of SCCP Connection Requests Sent to the CN Through the Iu Interface Number of Successful SCCP Connection Requests Sent to the CN Through the Iu Interface Number of SCCP Connection Requests from the CN Through the Iu Interface Number of Successful SCCP Connection Requests from the CN Through the Iu Interface Original Release Earlier than V900R011
67195050
VS.IU.SCCP.Tx.Co n.Succ
67195051
VS.IU.SCCP.Rx.C on.Req
67195052
VS.IU.SCCP.Rx.C on.Succ
None
1.4.8.1 Number of SCCP Connection Requests Sent by the RNC to the CN Through the Iu Interface Counters
Counter ID 67195049 Counter Name VS.IU.SCCP.Tx.Con.Req Counter Description Number of SCCP Connection Requests Sent to the CN Through the Iu Interface
Issue 01 (2013-05-04)
201
Description
This counter provides the number of SCCP connection requests (CRs) that the RNC sends to the CN based on the corresponding CN node.
Measurement point
The measurement is triggered at point A as shown in the figure. In the measurement period, the counter is incremented by one when the RNC RANAP sends a SCCP connection request (CR) message to the CN. Figure 1-74 SCCP connection procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IU.SCCP.Tx.Con.Req Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
202
1.4.8.2 Number of Successful SCCP Connection Requests Sent by the RNC to the CN Through the Iu Interface Counters
Counter ID 67195050 Counter Name VS.IU.SCCP.Tx.Con.Succ Counter Description Number of Successful SCCP Connection Requests Sent to the CN Through the Iu Interface
Description
This counter provides the number of successful SCCP connection requests sent by the RNC to the CN based on the corresponding CN node.
Measurement point
The measurement is triggered at point B as shown in the figure. This counter is incremented by one when the local RNC RANAP receives a Connection Confirm (CC) message from the CN after sending a Connection Request (CR) message to the CN. Figure 1-75 SCCP connection procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IU.SCCP.Tx.Con.Succ Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.8.3 Number of SCCP Connection Requests Received by the RNC from the CN Through the Iu Interface Counters
Counter ID 67195051 Counter Name VS.IU.SCCP.Rx.Con.Req Counter Description Number of SCCP Connection Requests from the CN Through the Iu Interface
Description
This counter provides the number of SCCP connection requests received by the RNC from the CN based on the corresponding CN node.
Measurement point
The measurement is triggered at point A as shown in the figure. In the measurement period, the counter is incremented by one when the RNC RANAP receives a SCCP CR message from the CN.
Issue 01 (2013-05-04)
204
Figure 1-76 SCCP connection procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IU.SCCP.Rx.Con.Req Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.4.8.4 Number of Successful SCCP Connection Requests Received by the RNC from the CN Through the Iu Interface
Issue 01 (2013-05-04)
205
Counters
Counter ID 67195052 Counter Name VS.IU.SCCP.Rx.Con.Succ Counter Description Number of Successful SCCP Connection Requests from the CN Through the Iu Interface
Description
This counter provides the number of successful SCCP connection requests received by the RNC from the CN based on the corresponding CN node.
Measurement point
The measurement is triggered at point B as shown in the figure. This counter is incremented by one when the local RNC RANAP sends a Connection Confirm (CC) message to the CN after receiving a Connection Request (CR) message from the CN. Figure 1-77 SCCP connection procedure
Formula
None
Issue 01 (2013-05-04)
206
Unit
None
Related Features
Counter Name VS.IU.SCCP.Rx.Con.Succ Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.5 Measurement of IUR Interface Performance(IUR)

Overview
Iur Interface Measurement (IUR) is used to measure the performance of signaling procedures and traffic flows on the Iur interface.
FunctionSubSets
FunctionSubSet DRNC.IUR RESERVE.IUR SIG.SCCP.IUR SRNC.IUR TRFFIC.IUR FunctionSubSet Name Measurement related to DRNC in Iur interface Reserved counter for Iur interface Measurement Related to SCCP for Iur Interface Measurement related to SRNC in Iur interface Measurement related to traffic for Iur Interface
1.5.1 Measurement related to DRNC in Iur interface(DRNC.IUR)

Overview
The DRNC Iur Interface Measurement involves measurements of DCH procedures and common transport channel procedures. The DCH procedures include: RL setup procedures, RL addition procedures, RL deletion procedures, Synchronized RL reconfiguration procedures, RL failure procedures, RL restoration procedures; The common transport channel procedures include common transport channel setup procedures and common transport channel release procedures.
Counters
Counter ID 67179009 Counter Name VS.SHO.ErrIndIur .Rx Counter Description Number of Error Indication Messages Received on Iur Interface for DRNC Number of Error Indication Messages Sent on Iur Interface for DRNC Number of Radio Link Setup Requests on Iur Interface for DRNC Number of Successful Radio Link Setups on Iur Interface for DRNC Number of Failed Radio Link Setups on Iur Interface for DRNC (Device Fault) Number of Failed Radio Link Setups on Iur Interface for DRNC (Congestion) Number of Failed Radio Link Setups on Iur Interface for DRNC (Configuration Unsupported) Number of Radio Link Deletion Requests on Iur Interface for DRNC Number of Successful Radio Link Deletions on Iur Interface for DRNC Original Release Earlier than V900R011
67179010
VS.SHO.ErrIndIur .Tx
67179089
VS.SHO.AttRLSet upIur.Rx
67179090
VS.SHO.SuccRLSe tupIur.Tx
67179092
VS.SHO.FailRLSet upIur.HW.Tx
67179093
VS.SHO.FailRLSet upIur.CongTx
67179094
VS.SHO.FailRLSet upIur.CfgUTx
67179096
VS.SHO.AttRLDel Iur.Rx
67179097
VS.SHO.SuccRLD elIur.Tx
Issue 01 (2013-05-04)
208
Counter ID 67179098
Counter Name VS.SHO.AttRLAd dIur.Rx
Counter Description Number of Radio Link Addition Requests on Iur Interface for DRNC Number of Successful Radio Link Additions on Iur Interface for DRNC Number of Failed Radio Link Additions on Iur Interface for DRNC (OM Intervention) Number of Failed Radio Link Additions on Iur Interface for DRNC (Device Fault) Number of Failed Radio Link Additions on Iur Interface for DRNC (Congestion) Number of Failed Radio Link Additions on Iur Interface for DRNC (Configuration Unsupported) Number of Radio Link Synchronous Reconfiguration Requests on Iur Interface for DRNC Number of Successful Radio Link Synchronous Reconfigurations on Iur Interface for DRNC
67179099
VS.SHO.SuccRLA ddIur.Tx
67179100
VS.SHO.FailRLAd dIur.OM.Tx
67179101
VS.SHO.FailRLAd dIur.HW.Tx
67179102
VS.SHO.FailRLAd dIur.Cong.Tx
67179103
VS.SHO.FailRLAd dIur.CfgUnsTx
67179105
VS.SHO.AttRLRec fgIur.Rx
67179106
VS.SHO.SuccRLR ecfgIur.Tx
Issue 01 (2013-05-04)
209
Counter ID 67179109
Counter Name VS.SHO.FailRLRe cfgIur.CongTx
Counter Description Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for DRNC (Congestion) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for DRNC (Configuration Unsupported) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for DRNC (OM Intervention) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for DRNC (Device Fault) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for DRNC (Transport Resource Unavailable) Number of Failed Radio Link Setups on Iur Interface for DRNC (Transport Resource Unavailable)
67179110
VS.SHO.FailRLRe cfgIur.CfgUTx
67179107
VS.SHO.FailRLRe cfgIur.OM.Tx
67179108
VS.SHO.FailRLRe cfgIur.HW.Tx
67192579
VS.SHO.FailRLRe cfgIur.TransCongRx
67192580
VS.SHO.FailRLSet upIur.TransCongTx
Issue 01 (2013-05-04)
210
Counter ID 67192581
Counter Name VS.SHO.FailRLAd dIur.TransCong.T x
Counter Description Number of Failed Radio Link Additions on Iur Interface for DRNC (Transport Resource Unavailable) Number of Radio Link Synchronous Reconfiguration Cancellations on Iur Interface for DRNC Number of Radio Link Failures on Iur Interface for DRNC Number of Radio Link Failures on Iur Interface for DRNC (OM Intervention) Number of Radio Link Failures on Iur Interface for DRNC (Device Fault) Number of Radio Link Failures on Iur Interface for DRNC (Synchronization Failure) Number of Radio Link Failures on Iur Interface for DRNC (Configuration Unsupported) Number of Radio Link Failures on Iur Interface for DRNC (Other Reasons) Number of Radio Link Restorations on Iur Interface for DRNC
67179112
VS.SHO.CancelRL RecfgIur.Rx
67179113
VS.SHO.RLFail.Tx
67179114
VS.SHO.RLFail.O M.Tx
67179115
VS.SHO.RLFail.H W.Tx
67179116
VS.SHO.RLFail.Sy ncFail.Tx
67179117
VS.SHO.RLFail.Cf gUnsup.Tx
67190048
VS.SHO.RLFail.Ot her.Tx
67179118
VS.SHO.RLRestor e.Tx
Issue 01 (2013-05-04)
211
Counter ID 67179119
Counter Name VS.IUR.AttComTraChResDRNC
Counter Description Number of Common Transport Channel Resource Requests on Iur Interface for DRNC Number of Common Transport Channel Resource Responses on Iur Interface for DRNC Number of Common Transport Channel Resource Failures Due to Transport Resource Unavailable on Iur Interface for DRNC Number of Common Transport Channel Resource Release Requests on Iur Interface for DRNC Number of Failed Radio Link Setups on Iur interface for DRNC (NodeB Rehoming) Number of Failed Radio Link Additions on Iur interface for DRNC (NodeB Rehoming)
67179120
VS.IUR.SuccComTraChResDRNC
67179121
VS.IUR.FailCTCR DRNC.NotSupp
67179122
VS.IUR.AttRelCoTrChResDRNC
73423641
VS.SHO.FailRLSet upIur.NodeBReHo st.Tx
V900R014
73423642
VS.SHO.FailRLAd dIur.NodeBReHost .Tx
V900R014
Counter VS.SHO.RLFail.Tx Sub Counter VS.SHO.RLFail.OM.Tx VS.SHO.RLFail.HW.Tx VS.SHO.RLFail.SyncFail.Tx VS.SHO.RLFail.CfgUnsup.Tx VS.SHO.RLFail.Other.Tx
Issue 01 (2013-05-04)
212
1.5.1.1 Number of ERROR INDICATION Messages Received by the RNC on Iur Interface Counters
Counter ID 67179009 Counter Name VS.SHO.ErrIndIur.Rx Counter Description Number of Error Indication Messages Received on Iur Interface for DRNC
Description
This counter provides the number of ERROR INDICATION messages received on the Iur interface for the DRNC.
Measurement point
The measurement is triggered at point A, as shown in the figure. When a RNC receives an ERROR INDICATION message from another RNC, it measures this item. Figure 1-78 Error indication receiving procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.ErrIndIur.Rx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.1.2 Number of ERROR INDICATION Messages Sent by the RNC on Iur Interface Counters
Counter ID 67179010 Counter Name VS.SHO.ErrIndIur.Tx Counter Description Number of Error Indication Messages Sent on Iur Interface for DRNC
Description
This counter provides the number of ERROR INDICATION messages sent on the Iur interface for the DRNC.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends an ERROR INDICATION message to another RNC, it measures this item. Figure 1-79 Error indication sending procedure on the Iur interface
Issue 01 (2013-05-04)
214
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.ErrIndIur.Tx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.1.3 Number of Requests to Establish a Radio Link Received by DRNC on Iur Interface Counters
Counter ID 67179089 Counter Name VS.SHO.AttRLSetupIur.Rx Counter Description Number of Radio Link Setup Requests on Iur Interface for DRNC
Description
This measurement item takes statistics of the number of Radio Links that a DRNC requested to establish on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC receives a RADIO LINK SETUP REQUEST message from the SRNC, it measures this item on each Iur interface.
Issue 01 (2013-05-04)
215
Figure 1-80 Radio Link setup procedure on the Iur interface (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AttRLSetupIur.Rx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.1.4 Number of Successful Radio Link Establishments by DRNC on Iur Interface Counters
Counter ID 67179090 Counter Name VS.SHO.SuccRLSetupIur.T x Counter Description Number of Successful Radio Link Setups on Iur Interface for DRNC
Issue 01 (2013-05-04)
216
Description
This measurement item takes statistics of the number of successful radio link establishments by a DRNC on the Iur interface.
Measurement point
The measurement is triggered at point B, as shown in the figure. When a DRNC sends a RADIO LINK SETUP RESPONSE message to the SRNC, it measures this item. Figure 1-81 Radio Link setup procedure on the Iur interface (successful operation)
The measurement is triggered at point B, as shown in the figure. When the DRNC sends the SRNC a RADIO LINK SETUP FAILURE message and the message indicates that there are successfully established radio links, this item is measured on each Iur interface.
Issue 01 (2013-05-04)
217
Figure 1-82 Radio Link setup procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SuccRLSetupIur.T x Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.1.5 Number of Radio Links Unsuccessfully Established by DRNC on Iur Interface for Different Causes
Issue 01 (2013-05-04)
218
Counters
Counter ID 67179092 Counter Name VS.SHO.FailRLSetupIur.H W.Tx VS.SHO.FailRLSetupIur.Co ngTx VS.SHO.FailRLSetupIur.Cf gUTx Counter Description Number of Failed Radio Link Setups on Iur Interface for DRNC (Device Fault) Number of Failed Radio Link Setups on Iur Interface for DRNC (Congestion) Number of Failed Radio Link Setups on Iur Interface for DRNC (Configuration Unsupported) Number of Failed Radio Link Setups on Iur Interface for DRNC (Transport Resource Unavailable) Number of Failed Radio Link Setups on Iur interface for DRNC (NodeB Rehoming)
67179093
67179094
67192580
VS.SHO.FailRLSetupIur.Tr ansCongTx
73423641
VS.SHO.FailRLSetupIur.No deBReHost.Tx
Description
These measurement items take statistics of the number of Radio Links unsuccessfully established by a DRNC on the Iur interface according to different causes. The following table describes the meaning of each counter. Counter Name VS.SHO.FailRLSetupIur.HW.Tx Description Number of radio links unsuccessfully established by DRNC on Iur interface because of hardware failure (cause value: Hardware Failure) Number of radio links unsuccessfully established by DRNC on Iur interface because of insufficient RNC capability (cause value: Cell not Available, UL Scrambling Code Already in Use, DL Radio Resources not Available, UL Radio Resources not Available, Combining Resources not Available, Measurement Temporarily not Available, Cell Reserved for Operator Use, Control Processing Overload, or Not enough User Plane Processing Resources)
VS.SHO.FailRLSetupIur.CongTx
Issue 01 (2013-05-04)
219
Counter Name VS.SHO.FailRLSetupIur.CfgUTx
Description Number of radio links unsuccessfully established by DRNC on Iur interface because of improper configurations (cause value: Combining not Supported, UL Spreading Factor not Supported, DL Spreading Factor not Supported, Requested Tx Diversity Mode not supported, or CM not Supported) Number of radio links unsuccessfully established by DRNC on Iur interface because of insufficient RNC transmission capability (cause value: Transport Resource Unavailable) Number of radio links unsuccessfully established by DRNC on Iur interface because of NodeB Rehoming (cause value: NodeB Rehoming)
VS.SHO.FailRLSetupIur.TransCongTx
VS.SHO.FailRLSetupIur.NodeBReHost.Tx
Measurement point
The measurement is triggered at point B, as shown in the figure. When the DRNC sends the SRNC a RADIO LINK SETUP FAILURE message with failure causes, the items are measured on each Iur interface according to different causes. Figure 1-83 Radio Link setup procedure on the Iur interface (failed operation)
Issue 01 (2013-05-04)
220
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.FailRLSetupIur.H W.Tx VS.SHO.FailRLSetupIur.Co ngTx VS.SHO.FailRLSetupIur.Cf gUTx VS.SHO.FailRLSetupIur.Tr ansCongTx VS.SHO.FailRLSetupIur.No deBReHost.Tx Feature ID WRFD-020203 WRFD-020203 WRFD-020203 WRFD-020203 WRFD-020203 WRFD-040202 Feature Name Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover RNC Node Redundancy
1.5.1.6 Number of Radio Links to Be Deleted by DRNC on Iur Interface Counters

Counter ID 67179096 Counter Name VS.SHO.AttRLDelIur.Rx Counter Description Number of Radio Link Deletion Requests on Iur Interface for DRNC
Description
This measurement item takes statistics of the number of radio links that the DRNC is requested to delete on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC receives a RADIO LINK DELETION REQUEST message from the SRNC, this item shall be measured on each Iur interface.
Issue 01 (2013-05-04)
221
Figure 1-84 Radio Link deletion procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AttRLDelIur.Rx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.1.7 Number of Successful Radio Link Deletions by DRNC on Iur Interface Counters
Counter ID 67179097 Counter Name VS.SHO.SuccRLDelIur.Tx Counter Description Number of Successful Radio Link Deletions on Iur Interface for DRNC
Issue 01 (2013-05-04)
222
Description
This measurement item takes statistics of the number of successful radio link deletions by a DRNC on the Iur interface.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the DRNC sends the SRNC a RADIO LINK DELETION RESPONSE message, this item shall be measured on each Iur interface. Figure 1-85 RL deletion procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SuccRLDelIur.Tx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
Issue 01 (2013-05-04)
223
1.5.1.8 Number of Radio Link Addition Requests by DRNC on Iur Interface Counters
Counter ID 67179098 Counter Name VS.SHO.AttRLAddIur.Rx Counter Description Number of Radio Link Addition Requests on Iur Interface for DRNC
Description
This measurement item takes statistics of the number of radio links that the DRNC is requested to add on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC receives a RADIO LINK ADDITION REQUEST message from the SRNC, this item shall be measured on each Iur interface. Figure 1-86 Radio Link addition procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AttRLAddIur.Rx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.1.9 Number of Successful Radio Link Additions on DRNC Iur Interface Counters
Counter ID 67179099 Counter Name VS.SHO.SuccRLAddIur.Tx Counter Description Number of Successful Radio Link Additions on Iur Interface for DRNC
Description
This measurement item takes statistics of the number of successful radio link additions by a DRNC on the Iur interface.
Measurement point
The measurement is triggered at point B, as shown in the figure, when the DRNC sends the SRNC a RADIO LINK ADDITION RESPONSE message, this item shall be measured on each Iur interface.. Figure 1-87 Radio Link addition procedure (successful operation)
Issue 01 (2013-05-04)
225
The measurement is triggered at point B, as shown in the figure. When the DRNC sends a RADIO LINK ADDITION FAILURE message to the SRNC and the message indicates that there are successfully added radio links, this item shall be measured on each Iur interface. Figure 1-88 Radio Link addition procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SuccRLAddIur.Tx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.1.10 Number of Failed Radio Links Additions by DRNC on Iur Interface for Different Causes
Issue 01 (2013-05-04)
226
Counters
Counter ID 67179100 Counter Name VS.SHO.FailRLAddIur.OM .Tx VS.SHO.FailRLAddIur.HW .Tx VS.SHO.FailRLAddIur.Con g.Tx VS.SHO.FailRLAddIur.Cfg UnsTx Counter Description Number of Failed Radio Link Additions on Iur Interface for DRNC (OM Intervention) Number of Failed Radio Link Additions on Iur Interface for DRNC (Device Fault) Number of Failed Radio Link Additions on Iur Interface for DRNC (Congestion) Number of Failed Radio Link Additions on Iur Interface for DRNC (Configuration Unsupported) Number of Failed Radio Link Additions on Iur Interface for DRNC (Transport Resource Unavailable) Number of Failed Radio Link Additions on Iur interface for DRNC (NodeB Rehoming)
67179101
67179102
67179103
67192581
VS.SHO.FailRLAddIur.Tra nsCong.Tx
73423642
VS.SHO.FailRLAddIur.Nod eBReHost.Tx
Description
The measurement items provide the number of failed radio link additions by a DRNC on the Iur interface according to different causes. The following table describes the meaning of each counter. Counter Name VS.SHO.FailRLAddIur.OM.Tx Description Number of failed radio link additions by DRNC on Iur interface because of OM intervention (cause value: OM Intervention) Number of failed radio link additions by DRNC on Iur interface because of hardware failure (cause value: Hardware Failure)
VS.SHO.FailRLAddIur.HW.Tx
Issue 01 (2013-05-04)
227
Counter Name VS.SHO.FailRLAddIur.Cong.Tx
Description Number of failed radio link additions by DRNC on Iur interface because of insufficient RNC capability (cause value: Cell not Available, UL Scrambling Code Already in Use, DL Radio Resources not Available, UL Radio Resources not Available, Combining Resources not Available, Measurement Temporarily not Available, Cell Reserved for Operator Use, Control Processing Overload, or Not enough User Plane Processing Resources) Number of failed radio link additions by DRNC on Iur interface because of improper configurations (cause value: Combining not Supported, UL Spreading Factor not Supported, DL Spreading Factor not Supported, Requested Tx Diversity Mode not supported, or CM not Supported) Number of failed radio link additions by DRNC on Iur interface because of insufficient RNC transmission capability (cause value: Transport Resource Unavailable) Number of failed radio link additions caused by NodeB Rehoming on Iur interface for DRNC (cause value: NodeB Rehoming)
VS.SHO.FailRLAddIur.CfgUnsTx
VS.SHO.FailRLAddIur.TransCong.Tx
VS.SHO.FailRLAddIur.NodeBReHost.Tx
Measurement point
The measurement is triggered at point B, as shown in the figure. When the DRNC sends the SRNC a RADIO LINK ADDITION FAILURE message with different failure causes, these items shall be measured separately on each Iur interface.
Issue 01 (2013-05-04)
228
Figure 1-89 Radio Link addition procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.FailRLAddIur.OM .Tx VS.SHO.FailRLAddIur.HW .Tx VS.SHO.FailRLAddIur.Con g.Tx VS.SHO.FailRLAddIur.Cfg UnsTx VS.SHO.FailRLAddIur.Tra nsCong.Tx VS.SHO.FailRLAddIur.Nod eBReHost.Tx Feature ID WRFD-020203 WRFD-020203 WRFD-020203 WRFD-020203 WRFD-020203 WRFD-020203 WRFD-040202 Feature Name Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover RNC Node Redundancy
229
Issue 01 (2013-05-04)
1.5.1.11 Number of Radio Links to Be Reconfigured by DRNC Counters

Counter ID 67179105 Counter Name VS.SHO.AttRLRecfgIur.Rx Counter Description Number of Radio Link Synchronous Reconfiguration Requests on Iur Interface for DRNC
Description
This measurement item takes statistics of the number of radio links that a DRNC is requested to reconfigure on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC receives a RADIO LINK RECONFIGURATION PREPARE message, this item shall be measured on each Iur interface. Figure 1-90 Radio Link synchronous reconfiguration preparation procedure (successful operation)
Issue 01 (2013-05-04)
230
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AttRLRecfgIur.Rx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.1.12 Number of Radio Links Successfully Reconfigured by DRNC on Iur Interface Counters
Counter ID 67179106 Counter Name VS.SHO.SuccRLRecfgIur.T x Counter Description Number of Successful Radio Link Synchronous Reconfigurations on Iur Interface for DRNC
Description
This measurement item takes statistics of the number of successful radio link synchronous reconfigurations by a DRNC on the Iur interface.
Measurement point
The measurement is triggered at point C, as shown in the figure. When the DRNC receives a RADIO LINK RECONFIGURATION COMMIT message from the SRNC, this item shall be measured on each Iur interface.
Issue 01 (2013-05-04)
231
Figure 1-91 Successful radio link synchronous reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SuccRLRecfgIur.T x Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.1.13 Number of Failed Radio Link Synchronous Reconfigurations by DRNC on Iur Interface for Different Causes
Issue 01 (2013-05-04)
232
Counters
Counter ID 67179107 Counter Name VS.SHO.FailRLRecfgIur.O M.Tx Counter Description Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for DRNC (OM Intervention) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for DRNC (Congestion) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for DRNC (Configuration Unsupported) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for DRNC (Device Fault) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for DRNC (Transport Resource Unavailable)
67179109
VS.SHO.FailRLRecfgIur.C ongTx
67179110
VS.SHO.FailRLRecfgIur.Cf gUTx
67179108
VS.SHO.FailRLRecfgIur.H W.Tx
67192579
VS.SHO.FailRLRecfgIur.Tr ansCongRx
Description
The measurement items provide the number of failed radio link synchronous reconfigurations by a DRNC on the Iur interface according to different causes. The following table describes the meaning of each counter. Counter Name VS.SHO.FailRLRecfgIur.OM.Tx Description Number of failed radio link synchronous reconfigurations by DRNC on Iur interface because of OM intervention (cause value: OM Intervention)
Issue 01 (2013-05-04)
233
Counter Name VS.SHO.FailRLRecfgIur.CongTx
Description Number of failed radio link synchronous reconfigurations by DRNC on Iur interface because of insufficient RNC capability (cause value: Cell not Available, UL Scrambling Code Already in Use, DL Radio Resources not Available, UL Radio Resources not Available, Combining Resources not Available, Measurement Temporarily not Available, Cell Reserved for Operator Use, Control Processing Overload, or Not enough User Plane Processing Resources) Number of failed radio link synchronous reconfigurations by DRNC on Iur interface because of improper configurations (cause value: UL SF not supported, DL SF not supported, Downlink Shared Channel Type not supported, Uplink Shared Channel Type not supported, CM not supported, Number of DL codes not supported, or Number of UL codes not supported) Number of failed radio link synchronous reconfigurations by DRNC on Iur interface because of hardware failure (cause value: Hardware Failure) Number of failed radio link synchronous reconfigurations by DRNC on Iur interface because of insufficient RNC transmission capability (cause value: Transport Resource Unavailable)
VS.SHO.FailRLRecfgIur.CfgUTx
VS.SHO.FailRLRecfgIur.HW.Tx
VS.SHO.FailRLRecfgIur.TransCongRx
Measurement point
The measurement is triggered at point B as shown in the figure. When the DRNC sends the SRNC a RADIO LINK RECONFIGURATION FAILURE message with different failure causes as shown below, these items shall be measured separately on each Iur interface.
Issue 01 (2013-05-04)
234
Figure 1-92 Synchronized RL reconfiguration procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.FailRLRecfgIur.O M.Tx VS.SHO.FailRLRecfgIur.C ongTx VS.SHO.FailRLRecfgIur.Cf gUTx VS.SHO.FailRLRecfgIur.H W.Tx VS.SHO.FailRLRecfgIur.Tr ansCongRx Feature ID WRFD-020203 WRFD-020203 WRFD-020203 WRFD-020203 WRFD-020203 Feature Name Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover
Issue 01 (2013-05-04)
235
1.5.1.14 Number of Radio Links with Reconfiguration Canceled by the DRNC over Iur Counters
Counter ID 67179112 Counter Name VS.SHO.CancelRLRecfgIur .Rx Counter Description Number of Radio Link Synchronous Reconfiguration Cancellations on Iur Interface for DRNC
Description
This measurement item takes statistics of the number of radio links whose reconfiguration is canceled by the SRNC over the Iur interface.
Measurement point
The measurement is triggered at point C as shown in the figure. When the DRNC receives a RADIO LINK RECONFIGURATION CANCEL message from the SRNC, the DRNC measures the item for each Iur interface. Figure 1-93 Radio link reconfiguration cancellation procedure over Iur
Issue 01 (2013-05-04)
236
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.CancelRLRecfgIur .Rx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.1.15 Number of Radio Link Failures on Iur Interface Counters

Counter ID 67179113 Counter Name VS.SHO.RLFail.Tx Counter Description Number of Radio Link Failures on Iur Interface for DRNC
Description
This measurement item takes statistics of the number of failed radio links of a DRNC on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC sends a RADIO LINK FAILURE INDICATION message to the SRNC, this item shall be measured on each Iur interface.
Issue 01 (2013-05-04)
237
Figure 1-94 RL failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.RLFail.Tx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.1.16 Number of Failed Radio Links on Iur Interface for Different Causes Counters
Counter ID 67179114 Counter Name VS.SHO.RLFail.OM.Tx Counter Description Number of Radio Link Failures on Iur Interface for DRNC (OM Intervention)
Issue 01 (2013-05-04)
238
Counter ID 67179115
Counter Name VS.SHO.RLFail.HW.Tx
Counter Description Number of Radio Link Failures on Iur Interface for DRNC (Device Fault) Number of Radio Link Failures on Iur Interface for DRNC (Synchronization Failure) Number of Radio Link Failures on Iur Interface for DRNC (Configuration Unsupported) Number of Radio Link Failures on Iur Interface for DRNC (Other Reasons)
67179116
VS.SHO.RLFail.SyncFail.T x
67179117
VS.SHO.RLFail.CfgUnsup. Tx
67190048
VS.SHO.RLFail.Other.Tx
Description
These measurement items take statistics of the number of failed radio link in RADIO LINK FAILURE INDICATION messages sent by DRNC on the Iur interface according to different causes. The following table describes the meaning of each counter. Counter Name VS.SHO.RLFail.OM.Tx Description Number of failed radio links on Iur Interface Because of OM Intervention (OM Intervention) Number of failed radio links on Iur Interface Because of Hardware Failure (Hardware Failure) Number of failed radio links on Iur Interface Because of Synchronization Failure (Synchronization Failure) Number of failed radio links on Iur Interface Because of Improper Configurations (UL SF not supported, DL SF not supported, Downlink Shared Channel Type not supported, Uplink Shared Channel Type not supported, CM not supported, Number of DL codes not supported, Number of UL codes not supported)
VS.SHO.RLFail.HW.Tx
VS.SHO.RLFail.SyncFail.Tx
VS.SHO.RLFail.CfgUnsup.Tx
Issue 01 (2013-05-04)
239
Counter Name VS.SHO.RLFail.Other.Tx
Description Number of failed radio links on Iur Interface Because of Other Cause (cause other than OM Intervention, Hardware Failure, Synchronization Failure, and Improper Configurations)
Measurement point
The measurement is triggered at point A as shown in the figure. When the DRNC sends the SRNC a RADIO LINK FAILURE INDICATION message with different failure causes as shown below, these items shall be measured separately on each Iur interface. Figure 1-95 Radio Link failure procedure on the Iur interface
Formula
None
Unit
None
Issue 01 (2013-05-04)
240
Related Features
Counter Name VS.SHO.RLFail.OM.Tx VS.SHO.RLFail.HW.Tx VS.SHO.RLFail.SyncFail.T x VS.SHO.RLFail.CfgUnsup. Tx VS.SHO.RLFail.Other.Tx Feature ID WRFD-020203 WRFD-020203 WRFD-020203 WRFD-020203 WRFD-020203 Feature Name Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover
1.5.1.17 Number of RADIO LINK RESTORE INDICATION Messages sent by DRNC on Iur Interface Counters
Counter ID 67179118 Counter Name VS.SHO.RLRestore.Tx Counter Description Number of Radio Link Restorations on Iur Interface for DRNC
Description
These measurement items take statistics of the number of RADIO LINK RESTORE INDICATION messages sent by a DRNC on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC sends the SRNC a RADIO LINK RESTORE INDICATION message, this item shall be measured on each Iur interface.
Issue 01 (2013-05-04)
241
Figure 1-96 Radio Link restoration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.RLRestore.Tx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.1.18 Number of COMMON TRANSPORT CHANNEL RESOURCES REQUEST Messages Received by DRNC on Iur Interface
Issue 01 (2013-05-04)
242
Counters
Counter ID 67179119 Counter Name VS.IUR.AttComTraChResDRNC Counter Description Number of Common Transport Channel Resource Requests on Iur Interface for DRNC
Description
These measurement items take statistics of the number of COMMON TRANSPORT CHANNEL RESOURCES REQUEST messages received by a DRNC on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC receives from the SRNC a COMMON TRANSPORT CHANNEL RESOURCES REQUEST message on the Iur interface, this item shall be measured on each Iur interface. Figure 1-97 Common transport channel resources initialization procedure on the Iur interface
Formula
None
Issue 01 (2013-05-04)
243
Unit
None
Related Features
Counter Name VS.IUR.AttComTraChResDRNC Feature ID WRFD-010802 Feature Name Inter RNC Cell Update
1.5.1.19 Number of COMMON TRANSPORT CHANNEL RESOURCES RESPONSE Messages Sent by DRNC on Iur Interface Counters
Counter ID 67179120 Counter Name VS.IUR.SuccComTraChResDRNC Counter Description Number of Common Transport Channel Resource Responses on Iur Interface for DRNC
Description
These measurement items take statistics of the number of COMMON TRANSPORT CHANNEL RESOURCES RESPONSE messages sent from DRNC to SRNC on the Iur interface.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the DRNC sends the SRNC a COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message on the Iur interface, this item shall be measured on each Iur interface.
Issue 01 (2013-05-04)
244
Figure 1-98 Common transport channel resources initialization procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name VS.IUR.SuccComTraChResDRNC Feature ID WRFD-010802 Feature Name Inter RNC Cell Update
1.5.1.20 Number of COMMON TRANSPORT CHANNEL RESOURCES FAILURE Messages sent by DRNC on the Iur Interface due to Transport Resource Unavailable
Issue 01 (2013-05-04)
245
Counters
Counter ID 67179121 Counter Name VS.IUR.FailCTCRDRNC.N otSupp Counter Description Number of Common Transport Channel Resource Failures Due to Transport Resource Unavailable on Iur Interface for DRNC
Description
These measurement items take statistics of the number of COMMON TRANSPORT CHANNEL RESOURCES FAILURE messages that the DRNC sends to the SRNC with the cause of "Common Transport Channel Type Not Supported" on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC sends the SRNC a COMMON TRANSPORT CHANNEL RESOURCES FAILURE message with the cause of "Common Transport Channel Type Not Supported" on the Iur interface, this item shall be measured on each Iur interface. Figure 1-99 Common transport channel resources failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name VS.IUR.FailCTCRDRNC.N otSupp Feature ID WRFD-010802 Feature Name Inter RNC Cell Update
1.5.1.21 Number of COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST Messages Received by DRNC on Iur Interface Counters
Counter ID 67179122 Counter Name VS.IUR.AttRelCoTrChResDRNC Counter Description Number of Common Transport Channel Resource Release Requests on Iur Interface for DRNC
Description
These measurement items take statistics of the number of COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST messages received by a DRNC on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC receives from the SRNC a COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST message on the Iur interface, this item shall be measured on each Iur interface.
Issue 01 (2013-05-04)
247
Figure 1-100 Common transport channel resources release procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name VS.IUR.AttRelCoTrChResDRNC Feature ID WRFD-010802 Feature Name Inter RNC Cell Update
1.5.2 Reserved counter for Iur interface(RESERVE.IUR)

Overview
Reserved counter for Iur interface.
Issue 01 (2013-05-04)
248
Counters
Counter ID 73423446 73423447 73423448 73423449 73423450 73423451 73423452 73423453 73423454 73423455 Counter Name VS.Reserve.Counte r1.Iur VS.Reserve.Counte r2.Iur VS.Reserve.Counte r3.Iur VS.Reserve.Counte r4.Iur VS.Reserve.Counte r5.Iur VS.Reserve.Counte r6.Iur VS.Reserve.Counte r7.Iur VS.Reserve.Counte r8.Iur VS.Reserve.Counte r9.Iur VS.Reserve.Counte r10.Iur Counter Description Reserved counter 1 for Iur interface Reserved counter 2 for Iur interface Reserved counter 3 for Iur interface Reserved counter 4 for Iur interface Reserved counter 5 for Iur interface Reserved counter 6 for Iur interface Reserved counter 7 for Iur interface Reserved counter 8 for Iur interface Reserved counter 9 for Iur interface Reserved counter 10 for Iur interface Original Release V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013
None
1.5.2.1 Reserved counters for Iur interface Counters

Counter ID 73423446 73423447 73423448 Counter Name VS.Reserve.Counter1.Iur VS.Reserve.Counter2.Iur VS.Reserve.Counter3.Iur Counter Description Reserved counter 1 for Iur interface Reserved counter 2 for Iur interface Reserved counter 3 for Iur interface
249
Issue 01 (2013-05-04)
Counter ID 73423449 73423450 73423451 73423452 73423453 73423454 73423455
Counter Name VS.Reserve.Counter4.Iur VS.Reserve.Counter5.Iur VS.Reserve.Counter6.Iur VS.Reserve.Counter7.Iur VS.Reserve.Counter8.Iur VS.Reserve.Counter9.Iur VS.Reserve.Counter10.Iur
Counter Description Reserved counter 4 for Iur interface Reserved counter 5 for Iur interface Reserved counter 6 for Iur interface Reserved counter 7 for Iur interface Reserved counter 8 for Iur interface Reserved counter 9 for Iur interface Reserved counter 10 for Iur interface
Description
Reserved counters for Iur interface.
Measurement point
Reserved counters for Iur interface.
Formula
None
Unit
None
Related Features
None
1.5.3 Measurement Related to SCCP for Iur Interface (SIG.SCCP.IUR)

Overview
Measurement related to SCCP for Iur interface provides the counters related to the numbers of the local-RNC-initiated SCCP connection requests, local-RNC-initiated successful SCCP connection requests, peer-RNC-initiated SCCP connection requests, and peer-RNC-initiated successful SCCP connection requests.
Counters
Counter ID 67195053 Counter Name VS.IUR.SCCP.Tx. Con.Req Counter Description Number of SCCP Connection Requests Sent to Other RNC Through the Iur Interface Number of Successful SCCP Connection Requests Sent to Other RNC Through the Iur Interface Number of SCCP Connection Requests from Other RNC Through the Iur Interface Number of Successful SCCP Connection Requests from Other RNC Through the Iur Interface Original Release Earlier than V900R011
67195054
VS.IUR.SCCP.Tx. Con.Succ
67195055
VS.IUR.SCCP.Rx. Con.Req
67195056
VS.IUR.SCCP.Rx. Con.Succ
None
1.5.3.1 Number of SCCP Connection Requests Sent by the Local RNC to the Peer RNC Through the Iur Interface Counters
Counter ID 67195053 Counter Name VS.IUR.SCCP.Tx.Con.Req Counter Description Number of SCCP Connection Requests Sent to Other RNC Through the Iur Interface
Issue 01 (2013-05-04)
251
Description
This counter provides the number of SCCP connection requests sent by the local RNC to the peer RNC.
Measurement point
The measurement is triggered at point A, as shown in the figure. In the measurement period, the counter is incremented by one when the local RNC RNSAP sends a SCCP CR message to the peer RNC. Figure 1-101 SCCP connection requests sent by the local RNC to the peer RNC
Formula
None
Unit
None
Related Features
Counter Name VS.IUR.SCCP.Tx.Con.Req Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
252
Issue 01 (2013-05-04)
1.5.3.2 Number of Successful SCCP Connection Requests Sent by the Local RNC to the Peer RNC Through the Iur Interface Counters
Counter ID 67195054 Counter Name VS.IUR.SCCP.Tx.Con.Succ Counter Description Number of Successful SCCP Connection Requests Sent to Other RNC Through the Iur Interface
Description
This counter provides the successful number of SCCP connection requests sent by the local RNC to the peer RNC.
Measurement point
The measurement is triggered at point B, as shown in the figure. This counter is incremented by one when the local RNC RNSAP receives a Connection Confirm (CC) message from the peer RNC after sending a Connection Request (CR) message to the peer RNC. Figure 1-102 Successful SCCP connection requests sent by the local RNC to the peer RNC
Issue 01 (2013-05-04)
253
Formula
None
Unit
None
Related Features
Counter Name VS.IUR.SCCP.Tx.Con.Succ Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.5.3.3 Number of SCCP Connection Requests Received by the Local RNC from the Peer RNC Through the Iur Interface Counters
Counter ID 67195055 Counter Name VS.IUR.SCCP.Rx.Con.Req Counter Description Number of SCCP Connection Requests from Other RNC Through the Iur Interface
Description
This counter provides the number of SCCP connection requests received by the local RNC from the peer RNC.
Measurement point
The measurement is triggered at point A, as shown in the figure. In the measurement period, the counter is incremented by one when the local RNC RNSAP receives a SCCP CR message from the peer RNC.
Issue 01 (2013-05-04)
254
Figure 1-103 SCCP connection requests received by the local RNC from the peer RNC
Formula
None
Unit
None
Related Features
Counter Name VS.IUR.SCCP.Rx.Con.Req Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.5.3.4 Number of Successful SCCP Connection Requests Received by the Local RNC from the Peer RNC Through the Iur Interface
Issue 01 (2013-05-04)
255
Counters
Counter ID 67195056 Counter Name VS.IUR.SCCP.Rx.Con.Succ Counter Description Number of Successful SCCP Connection Requests from Other RNC Through the Iur Interface
Description
This counter provides the number of successful SCCP connection requests received by the local RNC from the peer RNC.
Measurement point
The measurement is triggered at point B, as shown in the figure. This counter is incremented by one when the local RNC RNSAP sends a Connection Confirm (CC) message to the peer RNC after receiving a Connection Request (CR) message from the peer RNC. Figure 1-104 Successful SCCP connection requests received by the local RNC from the peer RNC
Formula
None
Unit
None
Related Features
Counter Name VS.IUR.SCCP.Rx.Con.Succ Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.5.4 Measurement related to SRNC in Iur interface(SRNC.IUR)

Overview
The SRNC Iur Interface Measurement involves measurements of DCH procedures, common transport channel procedures, and cross-Iur RAB and RRC connection release procedures. The DCH procedures include: Radio link (RL) setup procedures, RL addition procedures, RL deletion procedures, Synchronized RL reconfiguration procedures, RL failure procedures, RL restoration procedures; Common transport channel procedures include common transport channel setup procedures and common transport channel release procedures.
Counters
Counter ID 67179025 Counter Name VS.SHO.AttRLSet upIur.Tx Counter Description Number of Radio Link Setup Requests on Iur Interface from SRNC Number of Radio Links Successfully Set Up on the Iur Interface for SRNC Number of Radio Link Setup Failures on Iur Interface for SRNC (Device Fault) Number of Radio Link Setup Failures on Iur Interface for SRNC (Congestion) Original Release Earlier than V900R011
67179026
VS.SHO.SuccRLSe tupIur.Rx
67179028
VS.SHO.FailRLSet upIur.HW.Rx
67179029
VS.SHO.FailRLSet upIur.Cong.Rx
Issue 01 (2013-05-04)
257
Counter ID 67179030
Counter Name VS.SHO.FailRLSet upIur.CfgUnsupp. Rx
Counter Description Number of Radio Link Setup Failures on Iur Interface for SRNC (Configuration Unsupported) Number of Radio Link Setup Failures on Iur Interface for SRNC (Transport Resource Unavailable) Number of Radio Link Addition Failures on Iur Interface for SRNC (Transport Resource Unavailable) Number of Radio Links Deleted on Iur Interface for SRNC Number of Successful deleted Radio Links on Iur Interface for SRNC Number of Radio Link Addition Requests on Iur Interface from SRNC Number of Successful Radio Link Additions on Iur Interface for SRNC Number of Failed Radio Link Additions on Iur Interface for SRNC (Device Fault) Number of Failed Radio Link Additions on Iur Interface for SRNC (Congestion)
67192577
VS.SHO.FailRLSet upIur.TransCong. Rx
67192578
VS.SHO.FailRLAd dIur.TransCong.R x
67179032
VS.SHO.AttRLDel Iur.Tx VS.SHO.SuccRLD elIur.Rx
V900R012
67179033
V900R012
67179035
VS.SHO.AttRLAd dIur.Tx
67179036
VS.SHO.SuccRLA ddIur.Rx
67179038
VS.SHO.FailRLAd dIur.HW.Rx
67179039
VS.SHO.FailRLAd dIur.Cong.Rx
Issue 01 (2013-05-04)
258
Counter ID 67179040
Counter Name VS.SHO.FailRLAd dIur.CfgUnsupp.R x
Counter Description Number of Failed Radio Link Additions on Iur Interface for SRNC (Configuration Unsupported) Number of Radio Link Reconfiguration Requests on Iur Interface from SRNC Number of Successful Radio Link Reconfigurations on Iur Interface for SRNC Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for SRNC (Device Fault) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for SRNC (Congestion) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for SRNC (Configuration Unsupported) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for SRNC (No Response)
67179042
VS.SHO.AttRLRec fgIur.Tx
67179043
VS.SHO.SuccRLR ecfgIur.Rx
67179045
VS.SHO.FailRLRe cfgIur.HW.Rx
67179046
VS.SHO.FailRLRe cfgIur.Cong.Rx
67179047
VS.SHO.FailRLRe cfgIur.CfgUnsupp. Rx
67179048
VS.SHO.FailRLRe cfgIur.NoReply
Issue 01 (2013-05-04)
259
Counter ID 67179051
Counter Name VS.SHO.RLFailIn dIur.Rx VS.SHO.RLFailIur .HW.Rx
Counter Description Number of Radio Link Failures on Iur Interface for SRNC Number of Radio Link Failures on Iur Interface for SRNC (Device Fault) Number of Radio Link Failures on Iur Interface for SRNC (Synchronization Failure) Number of Radio Link Failures on Iur Interface for SRNC (Configuration Unsupported) Number of Radio Link Restorations on Iur Interface for SRNC Number of Soft Handovers Initiated by SRNC on Iur Interface Number of Successful Soft Handovers Initiated by SRNC on Iur Interface Number of Common Transport Channel Resource Requests Sent by SRNC on Iur Interface Number of Common Transport Channel Resource Responses Received by SRNC on Iur Interface
Original Release Earlier than V900R011 Earlier than V900R011
67179053
67179054
VS.SHO.RLFailIur .SyncFail.Rx
67179055
VS.SHO.RLFailIur .CfgUnsup.Rx
67179056
VS.SHO.RLRestor eIur.Rx
67179061
VS.SHO.Att.Iur
67179062
VS.SHO.Succ.Iur
67179057
VS.AttCommTrCh ResIur.Tx
67179058
VS.SuccCommTrC hResIur.Rx
Issue 01 (2013-05-04)
260
Counter ID 67179059
Counter Name VS.FailCommTrC hResIur.NotSupp. Rx
Counter Description Number of Common Transport Channel Resource Failures Due to Transport Resource Unavailable on Iur Interface for SRNC Number of Common Transport Channel Resource Release Requests on Iur Interface from SRNC Number of CS Conversational RABs Normally Released on the SRNC Iur Interface for SRNC (Conversational with DL Max Bit Rate as 64kbit/s) Number of PS RABs Normally Released on Iur Interface for SRNC (CCH User Only) Number of Normally Released AMR RABs on Iur Interface for SRNC (not including WBAMR) Number of Abnormally Released AMR RABs on Iur Interface for SRNC (not including WBAMR)
67179060
VS.AttRelCommTr ChResIur.Tx
67191845
VS.RAB.NormRel. CS64.Iur
67191850
VS.RAB.NormRel. PS.CCH.Iur
67191858
VS.RAB.NormRel. AMR.Iur
67191859
VS.RAB.AbnormR el.AMR.Iur
Issue 01 (2013-05-04)
261
Counter ID 67191860
Counter Name VS.RAB.AbnormR el.CS64.Iur
Counter Description Number of CS Conversational RABs Abnormally Released on the SRNC Iur Interface for SRNC (Conversational with DL Max Bitrate as 64kbit/s) Number of PS RABs Abnormally Released on Iur Interface for SRNC (CCH User Only) Number of CS Streaming RABs Normally Released on Iur Interface for SRNC Number of RABs Normally Released for PS Conversational Services on Iur Interface for SRNC Number of RABs Normally Released for PS Streaming Services on Iur Interface for SRNC Number of Normally Released HSDSCHCarried RABs on Iur Interface for SRNC Number of EDCHCarried RABs Normally Released on Iur Interface for SRNC Number of CS Streaming RABs Abnormally Released on Iur Interface for SRNC
67191865
VS.RAB.AbnormR el.PS.CCH.Iur
67194987
VS.RAB.NormRel. CS.Str.Iur
67194988
VS.RAB.NormRel. PS.Conv.Iur
67194989
VS.RAB.NormRel. PS.Str.Iur
67194990
VS.RAB.NormRel. HSDPA.Iur
67194991
VS.RAB.NormRel. HSUPA.Iur
67194997
VS.RAB.AbnormR el.CS.Str.Iur
Issue 01 (2013-05-04)
262
Counter ID 67194998
Counter Name VS.RAB.AbnormR el.PS.Conv.Iur
Counter Description Number of RABs Abnormally Released for PS Conversational Services on Iur Interface for SRNC Number of RABs Abnormally Released for PS Streaming Services on Iur Interface for SRNC Number of HSDSCH-Carried RABs Abnormally Released on Iur Interface for SRNC Number of EDCHCarried RABs Abnormally Released on Iur Interface for SRNC Number of Radio Link Synchronous Reconfiguration Cancellations on Iur Interface for SRNC Number of HSPACarried CS Conversational RABs Normally Released on Iur Interface for SRNC Number of HSPACarried CS Conversational RABs Abnormally Released on Iur Interface for SRNC Number of CS AMRWB RABs Abnormally Released on the SRNC Iur Interface for SRNC
67194999
VS.RAB.AbnormR el.PS.Str.Iur
67195000
VS.RAB.AbnormR el.HSDPA.Iur
67195001
VS.RAB.AbnormR el.HSUPA.Iur
67179050
VS.SHO.CancelRL RecfgIur.Tx
67196206
VS.RAB.NormRel. CS.HSPA.Conv.Iur
67196207
VS.RAB.AbnormR el.CS.HSPA.Conv.I ur
73403815
VS.RAB.AbnormR el.AMRWB.Iur
V900R012
Issue 01 (2013-05-04)
263
Counter ID 73403816
Counter Name VS.RAB.NormRel. AMRWB.Iur
Counter Description Number of CS AMRWB RABs Normally Released on the SRNC Iur Interface for SRNC Number of PS BE RABs Normally Released on Iur Interface for SRNC Number of PS BE RABs Abnormally Released on Iur Interface for SRNC Number of Normally Released PS RABs that Are in CELL_PCH or URA_PCH State on Iur Interface for SRNC Number of Abnormally Released PS RABs that Are in CELL_PCH or URA_PCH State on Iur Interface for SRNC Number of RRC Connection Releases (CCCH) Sent by the SRNC over the Iur Interface due to DSCR Number of RRC Connection Releases (DCCH) Sent by the SRNC over the Iur Interface due to DSCR Number of Radio Link Setup Failures on Iur interface for SRNC (NodeB Rehoming)
73393847
VS.RAB.NormRel. PS.BE.Iur
V900R012
73393848
VS.RAB.AbnormR el.PS.BE.Iur
V900R012
73421884
VS.RAB.NormRel. PS.PCH.Iur
V900R012
73421885
VS.RAB.AbnormR el.PS.PCH.Iur
V900R012
73423384
VS.RRC.AttConnR elCCCH.DSCR.Iur
V900R013
73423385
VS.RRC.AttConnR elDCCH.DSCR.Iur
V900R013
73423639
VS.SHO.FailRLSet upIur.NodeBReHo st.Rx
V900R014
Issue 01 (2013-05-04)
264
Counter ID 73423640
Counter Name VS.SHO.FailRLAd dIur.NodeBReHost .Rx
Counter Description Number of Failed Radio Link Additions on Iur interface for SRNC (NodeB Rehoming)
Counter VS.SHO.FailRLSetupIur.Cong.Rx VS.SHO.FailRLAddIur.Cong.Rx VS.SHO.RLFailIndIur.Rx Sub Counter VS.SHO.FailRLSetupIur.TransCong.Rx VS.SHO.FailRLAddIur.TransCong.Rx VS.SHO.RLFailIur.HW.Rx VS.SHO.RLFailIur.SyncFail.Rx VS.SHO.RLFailIur.CfgUnsup.Rx VS.RAB.NormRel.PS.CCH.Iur VS.RAB.AbnormRel.PS.CCH.Iur VS.RAB.NormRel.PS.PCH.Iur VS.RAB.AbnormRel.PS.PCH.Iur
1.5.4.1 Number of Radio Links Requested to Establish by SRNC on Iur Interface Counters
Counter ID 67179025 Counter Name VS.SHO.AttRLSetupIur.Tx Counter Description Number of Radio Link Setup Requests on Iur Interface from SRNC
Description
This measurement item takes statistics of the number of radio links that the SRNC requests to establish on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the SRNC sends a RADIO LINK SETUP REQUEST message to the DRNC, the SRNC measures this item on each Iur interface.
Issue 01 (2013-05-04)
265
Figure 1-105 Radio Link setup procedure on the Iur interface (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AttRLSetupIur.Tx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.4.2 Number of Radio Links Successfully Established by SRNC on Iur Interface Counters
Counter ID 67179026 Counter Name VS.SHO.SuccRLSetupIur.R x Counter Description Number of Radio Links Successfully Set Up on the Iur Interface for SRNC
Issue 01 (2013-05-04)
266
Description
This measurement item takes statistics of the number of radio links successfully established by the SRNC on the Iur interface.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the SRNC receives a RADIO LINK SETUP RESPONSE message from the DRNC, it measures this item on each Iur interface. Figure 1-106 Radio Link setup procedure on the Iur interface (successful operation)
The measurement is triggered at point B, as shown in the figure. When the SRNC receives a RADIO LINK SETUP FAILURE message from the DRNC and the message indicates that there are successfully established radio links, the RNC measures this item on each Iur interface.
Issue 01 (2013-05-04)
267
Figure 1-107 Radio Link setup failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SuccRLSetupIur.R x Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.4.3 Number of Failed Radio Link Establishments by SRNC on Iur Interface for Different Causes
Issue 01 (2013-05-04)
268
Counters
Counter ID 67179028 Counter Name VS.SHO.FailRLSetupIur.H W.Rx VS.SHO.FailRLSetupIur.Co ng.Rx VS.SHO.FailRLSetupIur.Cf gUnsupp.Rx Counter Description Number of Radio Link Setup Failures on Iur Interface for SRNC (Device Fault) Number of Radio Link Setup Failures on Iur Interface for SRNC (Congestion) Number of Radio Link Setup Failures on Iur Interface for SRNC (Configuration Unsupported) Number of Radio Link Setup Failures on Iur Interface for SRNC (Transport Resource Unavailable) Number of Radio Link Setup Failures on Iur interface for SRNC (NodeB Rehoming)
67179029
67179030
67192577
VS.SHO.FailRLSetupIur.Tr ansCong.Rx
73423639
VS.SHO.FailRLSetupIur.No deBReHost.Rx
Description
The measurement items provide the number of failed radio link establishments by the SRNC on the Iur interface for different causes. The following table describes the meaning of each counter. Counter Name VS.SHO.FailRLSetupIur.HW.Rx Description Number of failed radio link establishments caused by Hardware Failure on Iur interface for SRNC (cause value: Hardware Failure) Number of failed radio link establishments caused by Unavailable RNC Resources on Iur interface for SRNC (cause value: Cell not Available, UL Scrambling Code Already in Use, DL Radio Resources not Available, UL Radio Resources not Available, Combining Resources not Available, Measurement Temporarily not Available, Cell Reserved for Operator Use, Control Processing Overload, Not enough User Plane Processing Resources or Transport Resource Unavailable)
VS.SHO.FailRLSetupIur.Cong.Rx
Issue 01 (2013-05-04)
269
Counter Name VS.SHO.FailRLSetupIur.CfgUnsupp.Rx
Description Number of failed radio link establishments caused by Improper Configurations on Iur interface for SRNC (cause value: Combining not Supported, UL Spreading Factor not Supported, DL Spreading Factor not Supported, Requested Tx Diversity Mode not supported, or CM not Supported) Number of failed radio link establishments caused by Transport Resource Unavailable on Iur interface for SRNC (cause value: Transport Resource Unavailable) Number of failed radio link establishments caused by NodeB Rehoming on Iur interface for SRNC (cause value: NodeB Rehoming)
VS.SHO.FailRLSetupIur.TransCong.Rx
VS.SHO.FailRLSetupIur.NodeBReHost.Rx
Measurement point
The measurement is triggered at point B, as shown in the figure. When the SRNC receives a RADIO LINK SETUP FAILURE message from the DRNC, the SRNC measures the item according to different failure causes on each Iur interface. Figure 1-108 Radio Link setup failure procedure on the Iur interface
Issue 01 (2013-05-04)
270
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.FailRLSetupIur.H W.Rx VS.SHO.FailRLSetupIur.Co ng.Rx VS.SHO.FailRLSetupIur.Cf gUnsupp.Rx VS.SHO.FailRLSetupIur.Tr ansCong.Rx VS.SHO.FailRLSetupIur.No deBReHost.Rx Feature ID WRFD-020203 WRFD-020203 WRFD-020203 WRFD-020203 WRFD-020203 WRFD-040202 Feature Name Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover RNC Node Redundancy
1.5.4.4 Number of Radio Links Deleted on Iur Interface for SRNC Counters
Counter ID 67179032 Counter Name VS.SHO.AttRLDelIur.Tx Counter Description Number of Radio Links Deleted on Iur Interface for SRNC
Description
This measurement item provides the number of radio links deleted on the Iur interface for SRNC.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the SRNC sends a RADIO LINK DELETION REQUEST message to the DRNC, the SRNC measures this item on each Iur interface.
Issue 01 (2013-05-04)
271
Figure 1-109 Radio Link deletion procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AttRLDelIur.Tx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.4.5 Number of Successful deleted Radio Links on Iur Interface for SRNC Counters
Counter ID 67179033 Counter Name VS.SHO.SuccRLDelIur.Rx Counter Description Number of Successful deleted Radio Links on Iur Interface for SRNC
Issue 01 (2013-05-04)
272
Description
This measurement item provides the number of successful deleted radio links on the Iur interface for SRNC.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the SRNC receives a RADIO LINK DELETION RESPONSE message from the DRNC, the SRNC measures this item on each Iur interface. Figure 1-110 Radio Link deletion procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SuccRLDelIur.Rx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
Issue 01 (2013-05-04)
273
1.5.4.6 Number of Radio Links Requested to Add by SRNC on Iur Interface Counters
Counter ID 67179035 Counter Name VS.SHO.AttRLAddIur.Tx Counter Description Number of Radio Link Addition Requests on Iur Interface from SRNC
Description
This measurement item takes statistics of the number of radio links that the SRNC requests to add on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the SRNC sends the DRNC a RADIO LINK ADDITION REQUEST message, the SRNC measures this item on each Iur interface. Figure 1-111 Radio Link addition procedure on the Iur interface (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AttRLAddIur.Tx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.4.7 Number of Radio Links Successfully Added by SRNC on Iur Interface Counters
Counter ID 67179036 Counter Name VS.SHO.SuccRLAddIur.Rx Counter Description Number of Successful Radio Link Additions on Iur Interface for SRNC
Description
This measurement item takes statistics of the number of radio links successfully added by the SRNC on the Iur interface.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the SRNC receives a RADIO LINK ADDITION RESPONSE message from the DRNC, the SRNC measures the item on each Iur interface. Figure 1-112 Radio Link addition procedure on the Iur interface (successful operation)
Issue 01 (2013-05-04)
275
The measurement is triggered at point B, as shown in the figure. When the SRNC receives a RADIO LINK ADDITION FAILURE message from the DRNC and if there are successfully added radio links, the SRNC measures this item on each Iur interface. Figure 1-113 Radio Link addition procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SuccRLAddIur.Rx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.4.8 Number of Failed Radio Link Additions for Different Causes on Iur Interface for SRNC
Issue 01 (2013-05-04)
276
Counters
Counter ID 67179038 Counter Name VS.SHO.FailRLAddIur.HW .Rx VS.SHO.FailRLAddIur.Tra nsCong.Rx Counter Description Number of Failed Radio Link Additions on Iur Interface for SRNC (Device Fault) Number of Radio Link Addition Failures on Iur Interface for SRNC (Transport Resource Unavailable) Number of Failed Radio Link Additions on Iur Interface for SRNC (Congestion) Number of Failed Radio Link Additions on Iur Interface for SRNC (Configuration Unsupported) Number of Failed Radio Link Additions on Iur interface for SRNC (NodeB Rehoming)
67192578
67179039
VS.SHO.FailRLAddIur.Con g.Rx VS.SHO.FailRLAddIur.Cfg Unsupp.Rx
67179040
73423640
VS.SHO.FailRLAddIur.Nod eBReHost.Rx
Description
The measurement items provide the number of failed radio link additions for different causes on the Iur interface for SRNC. The following table describes the meaning of each counter. Counter Name VS.SHO.FailRLAddIur.HW.Rx Description Number of failed radio link additions caused by hardware failure on Iur interface for SRNC (cause value: Hardware Failure) Number of failed radio link additions caused by insufficient RNC transmission capability on Iur interface for SRNC (cause value: Transport Resource Unavailable)
VS.SHO.FailRLAddIur.TransCong.Rx
Issue 01 (2013-05-04)
277
Counter Name VS.SHO.FailRLAddIur.Cong.Rx
Description Number of failed radio link additions caused by insufficient RNC capability on Iur interface for SRNC (cause value: Cell not Available, UL Scrambling Code Already in Use, DL Radio Resources not Available, UL Radio Resources not Available, Combining Resources not Available, Measurement Temporarily not Available, Cell Reserved for Operator Use, Control Processing Overload, Not enough User Plane Processing Resources or Transport Resource Unavailable) Number of failed radio link additions caused by improper configurations on Iur interface for SRNC (cause value: Combining not Supported, UL Spreading Factor not Supported, DL Spreading Factor not Supported, Requested Tx Diversity Mode not supported, or CM not Supported) Number of failed radio link additions caused by NodeB Rehoming on Iur interface for SRNC (cause value: NodeB Rehoming)
VS.SHO.FailRLAddIur.CfgUnsupp.Rx
VS.SHO.FailRLAddIur.NodeBReHost.Rx
Measurement point
The measurement is triggered at point B, as shown in the figure. When the SRNC receives a RADIO LINK ADDITION FAILURE message from the DRNC, the SRNC measures the item according to different failure causes on each Iur interface.
Issue 01 (2013-05-04)
278
Figure 1-114 Radio Link addition procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.FailRLAddIur.HW .Rx VS.SHO.FailRLAddIur.Tra nsCong.Rx VS.SHO.FailRLAddIur.Con g.Rx VS.SHO.FailRLAddIur.Cfg Unsupp.Rx VS.SHO.FailRLAddIur.Nod eBReHost.Rx Feature ID WRFD-020203 WRFD-020203 WRFD-020203 WRFD-020203 WRFD-040202 WRFD-020203 Feature Name Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover RNC Node Redundancy Inter RNC Soft Handover
Issue 01 (2013-05-04)
279
1.5.4.9 Number of Radio Links Requested to Reconfigure by SRNC on Iur Interface Counters
Counter ID 67179042 Counter Name VS.SHO.AttRLRecfgIur.Tx Counter Description Number of Radio Link Reconfiguration Requests on Iur Interface from SRNC
Description
This measurement item takes statistics of the number of radio links that the SRNC requests to reconfigure on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the DRNC, the SRNC measures this item on each Iur interface. Figure 1-115 Synchronized radio link reconfiguration procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AttRLRecfgIur.Tx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.4.10 Number of Radio Links Successfully Reconfigured by SRNC on Iur Interface Counters
Counter ID 67179043 Counter Name VS.SHO.SuccRLRecfgIur.R x Counter Description Number of Successful Radio Link Reconfigurations on Iur Interface for SRNC
Description
This measurement item takes statistics of the number of radio links successfully reconfigured by the SRNC.
Measurement point
The measurement is triggered at point C, as shown in the figure. When the SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the DRNC, if there is an indication of successfully reconfigured radio links in the message, the SRNC measures this item on each Iur interface.
Issue 01 (2013-05-04)
281
Figure 1-116 Synchronized radio link reconfiguration commit procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SuccRLRecfgIur.R x Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.4.11 Number of Radio Links Unsuccessfully Reconfigured by SRNC on Iur Interface for Different Causes
Issue 01 (2013-05-04)
282
Counters
Counter ID 67179045 Counter Name VS.SHO.FailRLRecfgIur.H W.Rx Counter Description Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for SRNC (Device Fault) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for SRNC (Congestion) Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for SRNC (Configuration Unsupported)
67179046
VS.SHO.FailRLRecfgIur.C ong.Rx
67179047
VS.SHO.FailRLRecfgIur.Cf gUnsupp.Rx
Description
The measurement items provide the number of radio links unsuccessfully reconfigured by the SRNC on the Iur interface for different causes. The following table describes the meaning of each counter. Counter Name VS.SHO.FailRLRecfgIur.HW.Rx Description Number of failed radio link reconfigurations by hardware failure on Iur interface for SRNC (cause value: Hardware Failure) Number of failed radio link reconfigurations caused by hardware failure on Iur interface for SRNC (cause value: Cell not Available, UL Scrambling Code Already in Use, DL Radio Resources not Available, UL Radio Resources not Available, Combining Resources not Available, Measurement Temporarily not Available, Cell Reserved for Operator Use, Transport Resource Unavailable, Control Processing Overload, or Not enough User Plane Processing Resources)
VS.SHO.FailRLRecfgIur.Cong.Rx
Issue 01 (2013-05-04)
283
Counter Name VS.SHO.FailRLRecfgIur.CfgUnsupp.Rx
Description Number of failed radio link reconfigurations caused by insufficient RNC capability on Iur interface for SRNC (cause value: Cell not Available, UL Scrambling Code Already in Use, DL Radio Resources not Available, UL Radio Resources not Available, Combining Resources not Available, Measurement Temporarily not Available, Cell Reserved for Operator Use, Transport Resource Unavailable, Control Processing Overload, or Not enough User Plane Processing Resources)
Measurement point
The measurement is triggered at point B, as shown in the figure. When the SRNC receives a RADIO LINK RECONFIGURATION FAILURE message from the DRNC, the SRNC measures the item according to different failure causes on each Iur interface. Figure 1-117 Synchronized radio link reconfiguration procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.FailRLRecfgIur.H W.Rx VS.SHO.FailRLRecfgIur.C ong.Rx VS.SHO.FailRLRecfgIur.Cf gUnsupp.Rx Feature ID WRFD-020203 WRFD-020203 WRFD-020203 Feature Name Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover
1.5.4.12 Number of Radio Links Unsuccessfully Reconfigured by SRNC on Iur Interface for No Response Counters
Counter ID 67179048 Counter Name VS.SHO.FailRLRecfgIur.N oReply Counter Description Number of Failed Radio Link Synchronous Reconfigurations on Iur Interface for SRNC (No Response)
Description
This measurement item provides the number of radio links unsuccessfully reconfigured by the SRNC on the Iur interface due to no response.
Measurement point
The measurement is triggered at point A as shown in the figure. When the SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the DRNC, the SRNC starts the timer to wait for the response message from the DRNC. If the SRNC does not receive a response message until the timer expires, it triggers the the measurement of this item on each Iur interface.
Issue 01 (2013-05-04)
285
Figure 1-118 Radio Link synchronous reconfiguration preparation procedure (failed operation) (no reply)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.FailRLRecfgIur.N oReply Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.4.13 Number of Failed Radio Links of SRNC on Iur Interface Counters

Counter ID 67179051 Counter Name VS.SHO.RLFailIndIur.Rx Counter Description Number of Radio Link Failures on Iur Interface for SRNC
286
Issue 01 (2013-05-04)
Description
This measurement item takes statistics of the number of failed radio links in the RADIO LINK FAILURE INDICATION message on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the SRNC receives a RADIO LINK FAILURE INDICATION message from the DRNC, it measures this item on each Iur interface. Figure 1-119 Radio Link failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.RLFailIndIur.Rx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
Issue 01 (2013-05-04)
287
1.5.4.14 Number of Failed Radio Links of SRNC on Iur Interface for Different Causes Counters
Counter ID 67179053 Counter Name VS.SHO.RLFailIur.HW.Rx Counter Description Number of Radio Link Failures on Iur Interface for SRNC (Device Fault) Number of Radio Link Failures on Iur Interface for SRNC (Synchronization Failure) Number of Radio Link Failures on Iur Interface for SRNC (Configuration Unsupported)
67179054
VS.SHO.RLFailIur.SyncFai l.Rx
67179055
VS.SHO.RLFailIur.CfgUns up.Rx
Description
These measurement items take statistics of the number of failed radio links in the RADIO LINK FAILURE INDICATION message on the Iur interface for different causes. The following table describes the meaning of each counter. Counter Name VS.SHO.RLFailIur.HW.Rx Description Number of failed radio links of SRNC on Iur interface because of hardware failure (cause value: Hardware Failure) Number of failed radio links of SRNC on Iur interface because of synchronization failure (cause value: Synchronization Failure) Number of failed radio links of SRNC on Iur interface because of improper configurations (cause value: UL SF not supported, DL SF not supported, Downlink Shared Channel Type not supported, Uplink Shared Channel Type not supported, CM not supported, Number of DL codes not supported, or Number of UL codes not supported)
VS.SHO.RLFailIur.SyncFail.Rx
VS.SHO.RLFailIur.CfgUnsup.Rx
Issue 01 (2013-05-04)
288
Measurement point
The measurement is triggered at point A, as shown in the figure. When the SRNC receives from the DRNC a RADIO LINK FAILURE INDICATION message, the SRNC measures these items according to different failure causes on each Iur interface. Figure 1-120 Radio Link failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.RLFailIur.HW.Rx VS.SHO.RLFailIur.SyncFai l.Rx VS.SHO.RLFailIur.CfgUns up.Rx Feature ID WRFD-020203 WRFD-020203 WRFD-020203 Feature Name Inter RNC Soft Handover Inter RNC Soft Handover Inter RNC Soft Handover
Issue 01 (2013-05-04)
289
1.5.4.15 Number of Radio Links Restored by SRNC on Iur Interface Counters

Counter ID 67179056 Counter Name VS.SHO.RLRestoreIur.Rx Counter Description Number of Radio Link Restorations on Iur Interface for SRNC
Description
This measurement item takes statistics of the number of radio links restored by the SRNC on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the SRNC receives a RADIO LINK RESTORE INDICATION message from the DRNC, the SRNC measures this item on each Iur interface. Figure 1-121 Radio Link restoration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.RLRestoreIur.Rx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.4.16 Number of Soft Handovers Initiated by SRNC on Iur Interface Counters

Counter ID 67179061 Counter Name VS.SHO.Att.Iur Counter Description Number of Soft Handovers Initiated by SRNC on Iur Interface
Description
This measurement item takes statistics of the number of soft handovers initiated by the SRNC on Iur Interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the SRNC sends an UE an ACTIVE SET UPDATE message on the Iur interface, and when the added or deleted radio link exists in the DRNC, the SRNC measures this item on each Iur interface. Figure 1-122 Active set update procedure (successful operation)
Issue 01 (2013-05-04)
291
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.Att.Iur Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.4.17 Number of Successful Soft Handovers Initiated by SRNC on Iur Interface Counters
Counter ID 67179062 Counter Name VS.SHO.Succ.Iur Counter Description Number of Successful Soft Handovers Initiated by SRNC on Iur Interface
Description
This measurement item takes statistics of the number of successful soft handovers initiated by the SRNC on Iur Interface.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the SRNC receives from the UE an ACTIVE SET UPDATE COMPLETE message and detects that the added or deleted radio link exists in the DRNC, this item shall be measured on each Iur interface.
Issue 01 (2013-05-04)
292
Figure 1-123 Active set update procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.Succ.Iur Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.4.18 Number of COMMON TRANSPORT CHANNEL RESOURCES REQUEST Messages Sent by SRNC on Iur Interface
Issue 01 (2013-05-04)
293
Counters
Counter ID 67179057 Counter Name VS.AttCommTrChResIur.T x Counter Description Number of Common Transport Channel Resource Requests Sent by SRNC on Iur Interface
Description
This measurement item takes statistics of the number of COMMON TRANSPORT CHANNEL RESOURCES REQUEST messages sent by the SRNC on the Iur interface.
Measurement point
The measurement is triggered at point A as shown in the figure. During the common channel setup procedure over the Iur interface, this counter is incremented by one each time the SRNC sends a COMMON TRANSPORT CHANNEL RESOURCES REQUEST message based on different Iur interfaces. Figure 1-124 Initialization procedure of common transport channel resources on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name VS.AttCommTrChResIur.T x Feature ID WRFD-010802 Feature Name Inter RNC Cell Update
1.5.4.19 Number of COMMON TRANSPORT CHANNEL RESOURCES RESPONSE Messages Received by SRNC on Iur Interface Counters
Counter ID 67179058 Counter Name VS.SuccCommTrChResIur. Rx Counter Description Number of Common Transport Channel Resource Responses Received by SRNC on Iur Interface
Description
This measurement item takes statistics of the number of COMMON TRANSPORT CHANNEL RESOURCES RESPONSE messages received by the SRNC on the Iur interface.
Measurement point
The measurement is triggered at point B, as shown in the figure. During the common channel setup procedure over the Iur interface, this counter is incremented by one each time the SRNC receives a COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message based on different Iur interfaces.
Issue 01 (2013-05-04)
295
Figure 1-125 Initialization procedure of common transport channel resources on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name VS.SuccCommTrChResIur. Rx Feature ID WRFD-010802 Feature Name Inter RNC Cell Update
1.5.4.20 Number of COMMON TRANSPORT CHANNEL RESOURCES FAILURE Messages Received by SRNC on Iur Interface Due to Transport Resource Unavailable
Issue 01 (2013-05-04)
296
Counters
Counter ID 67179059 Counter Name VS.FailCommTrChResIur.N otSupp.Rx Counter Description Number of Common Transport Channel Resource Failures Due to Transport Resource Unavailable on Iur Interface for SRNC
Description
This measurement item takes statistics of the number of COMMON TRANSPORT CHANNEL RESOURCES FAILURE messages received by the SRNC on the Iur interface with the cause of "Common Transport Channel Type Not Supported".
Measurement point
The measurement is triggered at point A, as shown in the figure. When the SRNC receives a COMMON TRANSPORT CHANNEL RESOURCES FAILURE message on the Iur interface with the cause of "Common Transport Channel Type Not Supported", it measures this item on each Iur interface. Figure 1-126 Common transport channel resource failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name VS.FailCommTrChResIur.N otSupp.Rx Feature ID WRFD-010802 Feature Name Inter RNC Cell Update
1.5.4.21 Number of COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST Messages of SRNC on Iur Interface Counters
Counter ID 67179060 Counter Name VS.AttRelCommTrChResIu r.Tx Counter Description Number of Common Transport Channel Resource Release Requests on Iur Interface from SRNC
Description
This measurement item takes statistics of the number of COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST messages sent by the SRNC on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the SRNC sends a COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST message on the Iur interface, the SRNC measures this item on each Iur interface.
Issue 01 (2013-05-04)
298
Figure 1-127 Common transport channel resource release procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name VS.AttRelCommTrChResIu r.Tx Feature ID WRFD-010802 Feature Name Inter RNC Cell Update
1.5.4.22 Number of PS RABs Normally Released on CCH (FACH or PCH) for SRNC (Iur Interface)
Issue 01 (2013-05-04)
299
Counters
Counter ID 67191850 Counter Name VS.RAB.NormRel.PS.CCH. Iur Counter Description Number of PS RABs Normally Released on Iur Interface for SRNC (CCH User Only)
Description
When the best cell is under a DRNC, these measurement items take statistics of the number of RABs normally released on CCH (FACH or PCH) on the SRNC IUR interface.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization" , or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures each item according to different types of service on Iur Interface. Figure 1-128 Iu release procedure
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal
Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release" ,the RNC measures each item according to different types of service on Iur Interface. Figure 1-129 RAB release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS.CCH. Iur Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
301
1.5.4.23 Number of Normally Released CS RABs According to Different Service on the IUR interface Counters
Counter ID 67191858 Counter Name VS.RAB.NormRel.AMR.Iur Counter Description Number of Normally Released AMR RABs on Iur Interface for SRNC(not including WB-AMR) Number of CS Conversational RABs Normally Released on the SRNC Iur Interface for SRNC (Conversational with DL Max Bit Rate as 64kbit/s) Number of CS Streaming RABs Normally Released on Iur Interface for SRNC Number of CS AMRWB RABs Normally Released on the SRNC Iur Interface for SRNC
67191845
VS.RAB.NormRel.CS64.Iur
67194987
VS.RAB.NormRel.CS.Str.Iu r VS.RAB.NormRel.AMRW B.Iur
73403816
Description
When the best cell is under a DRNC, these measurement items take statistics of the number of RABs normally released by the DRNC according to different service on the SRNC IUR interface.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization" , or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures each item according to different types of service on Iur Interface.
Issue 01 (2013-05-04)
302
Figure 1-130 Iu release procedure
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release" ,the RNC measures each item according to different types of service on Iur Interface.
Issue 01 (2013-05-04)
303
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.AMR.Iur VS.RAB.NormRel.CS64.Iur VS.RAB.NormRel.CS.Str.Iu r VS.RAB.NormRel.AMRW B.Iur Feature ID WRFD-010501 WRFD-010501 WRFD-010502 WRFD-010613 WRFD-010501 Feature Name Conversational QoS Class Conversational QoS Class Streaming QoS Class AMR-WB (Adaptive Multi Rate Wide Band) Conversational QoS Class
Issue 01 (2013-05-04)
304
1.5.4.24 Number of Abnormally Released CS RABs According to Different Service on SRNC Iur Interface Counters
Counter ID 67191859 Counter Name VS.RAB.AbnormRel.AMR. Iur Counter Description Number of Abnormally Released AMR RABs on Iur Interface for SRNC(not including WB-AMR) Number of CS Conversational RABs Abnormally Released on the SRNC Iur Interface for SRNC (Conversational with DL Max Bitrate as 64kbit/s) Number of CS Streaming RABs Abnormally Released on Iur Interface for SRNC Number of CS AMRWB RABs Abnormally Released on the SRNC Iur Interface for SRNC
67191860
VS.RAB.AbnormRel.CS64. Iur
67194997
VS.RAB.AbnormRel.CS.Str .Iur VS.RAB.AbnormRel.AMR WB.Iur
73403815
Description
When the best cell is under a DRNC, the measurement items take statistics of the number of abnormally released CS RABs according to different types of services on the SRNC IUR interface.
Measurement point
The measurement is triggered at point A as shown in the figure. The SRNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the SRNC measures the items by the types of services on the IUR interface.
Issue 01 (2013-05-04)
305
The measurement is triggered at point A as shown in the figure. The SRNC RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the SRNC measures the items by the types of services on the IUR interface.
Issue 01 (2013-05-04)
306
The measurement is triggered at point A as shown in the figure. The SRNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the SRNC measures the items by the types of services on the IUR interface.
Issue 01 (2013-05-04)
307
Figure 1-134 Iu connection release procedure triggered by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.AMR. Iur VS.RAB.AbnormRel.CS64. Iur VS.RAB.AbnormRel.CS.Str .Iur VS.RAB.AbnormRel.AMR WB.Iur Feature ID WRFD-010501 WRFD-010501 WRFD-010502 WRFD-010613 WRFD-010501 Feature Name Conversational QoS Class Conversational QoS Class Streaming QoS Class AMR-WB (Adaptive Multi Rate Wide Band) Conversational QoS Class
Issue 01 (2013-05-04)
308
1.5.4.25 Number of PS RABs Abnormally Released on CCH (FACH or PCH) for SRNC (Iur Interface) Counters
Counter ID 67191865 Counter Name VS.RAB.AbnormRel.PS.CC H.Iur Counter Description Number of PS RABs Abnormally Released on Iur Interface for SRNC (CCH User Only)
Description
When the best cell is under a DRNC, the measurement items take statistics of the number of abnormally released PS RABs beared on CCH on the SRNC IUR interface.
Measurement point
The measurement is triggered at point A as shown in the figure. When the best cell is a DRNC cell, The SRNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the SRNC measures the item on the IUR interface if the released RAB belongs to PS domain and its bear is CCH. Figure 1-135 RAB release procedure
Issue 01 (2013-05-04)
309
The measurement is triggered at point A as shown in the figure. When the best cell is a DRNC cell, The SRNC RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the SRNC measures the item on the IUR interface if the released RAB belongs to PS domain and its bear is CCH. Figure 1-136 RAB release IU REL procedure
The measurement is triggered at point A as shown in the figure. When the best cell is a DRNC cell, The SRNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the SRNC measures the item on the IUR interface if the released RAB belongs to PS domain and its bear is CCH.
Issue 01 (2013-05-04)
310
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.CC H.Iur Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.5.4.26 Number of Normally Released PS RABs According to Different Service on the IUR interface
Issue 01 (2013-05-04)
311
Counters
Counter ID 67194988 Counter Name VS.RAB.NormRel.PS.Conv .Iur Counter Description Number of RABs Normally Released for PS Conversational Services on Iur Interface for SRNC Number of RABs Normally Released for PS Streaming Services on Iur Interface for SRNC Number of PS BE RABs Normally Released on Iur Interface for SRNC
67194989
VS.RAB.NormRel.PS.Str.Iu r
73393847
VS.RAB.NormRel.PS.BE.Iu r
Description
When the best cell is under a DRNC, these measurement items take statistics of the number of RABs normally released by the DRNC according to service types in PS domain on the SRNC IUR interface.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures each item according to service types in PS domain on Iur Interface.
Issue 01 (2013-05-04)
312
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release" ,the RNC measures each item according to service types in PS domain on Iur Interface.
Issue 01 (2013-05-04)
313
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS.Conv .Iur VS.RAB.NormRel.PS.Str.Iu r VS.RAB.NormRel.PS.BE.Iu r Feature ID WRFD-010501 WRFD-010502 WRFD-010510 WRFD-010503 WRFD-010504 Feature Name Conversational QoS Class Streaming QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Interactive QoS Class Background QoS Class
Issue 01 (2013-05-04)
314
1.5.4.27 Number of Normally Released HSPA RABs on Iur Interface for SRNC Counters
Counter ID 67194990 Counter Name VS.RAB.NormRel.HSDPA. Iur Counter Description Number of Normally Released HSDSCH-Carried RABs on Iur Interface for SRNC Number of EDCH-Carried RABs Normally Released on Iur Interface for SRNC
67194991
VS.RAB.NormRel.HSUPA. Iur
Description
When the best cell is under a DRNC, these counters provide the number of RABs normally released on the Iur interface according to different bearer types.
Measurement point
The measurement can be triggered at point A as shown in the figure. When the RNC receives from the CN an IU RELEASE COMMAND message, it releases the corresponding RAB, and then sends to the CN an IU RELEASE COMPLETE message. If the release cause contained in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful Relocation" or "Network Optimization", or if the RNC initiates a release request with the cause value of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before receiving the IU RELEASE COMMAND message from the CN, then this counter is measured on the Iur interface according to the bearer types. Figure 1-140 Iu release procedure
Issue 01 (2013-05-04)
315
The measurement can also be triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message, it releases the corresponding RAB, and then sends to the CN a RAB ASSIGNMENT RESPONSE message. If the release cause contained in the RAB ASSIGNMENT REQUEST message is "User Inactivity", "Normal Release", "Successful Relocation" or "Network Optimization", or if the RNC initiates a release request with the cause value of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before receiving the RAB ASSIGNMENT REQUEST message from the CN, then this counter is measured on the Iur interface according to the bearer types. Figure 1-141 RAB release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.HSDPA. Iur
Issue 01 (2013-05-04)
Feature Name HSDPA over Iur
316
Counter Name VS.RAB.NormRel.HSUPA. Iur
Feature Name HSUPA over Iur
1.5.4.28 Number of Abnormally Released PS RABs According to Different Service Type on SRNC Iur Interface Counters
Counter ID 67194998 Counter Name VS.RAB.AbnormRel.PS.Co nv.Iur Counter Description Number of RABs Abnormally Released for PS Conversational Services on Iur Interface for SRNC Number of RABs Abnormally Released for PS Streaming Services on Iur Interface for SRNC Number of PS BE RABs Abnormally Released on Iur Interface for SRNC
67194999
VS.RAB.AbnormRel.PS.Str .Iur
73393848
VS.RAB.AbnormRel.PS.BE .Iur
Description
When the best cell is under a DRNC, these counters provide the number of RABs abnormally released on the Iur interface according to service types in PS domain.
Measurement point
As shown in point A of the figure, when an exception occurs, the SRNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then the SRNC measures the corresponding counter on the Iur interface according to the service types in PS domain.
Issue 01 (2013-05-04)
317
As shown in point A of the figure, when an exception occurs, the SRNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then the SRNC measures the corresponding counter on the Iur interface according to the service types in PS domain.
Issue 01 (2013-05-04)
318
As shown in point A of the figure, when an exception occurs, the SRNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then the SRNC measures the corresponding counter on the Iur interface according to the service types in PS domain.
Issue 01 (2013-05-04)
319
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.Co nv.Iur VS.RAB.AbnormRel.PS.Str .Iur VS.RAB.AbnormRel.PS.BE .Iur Feature ID WRFD-010501 WRFD-010502 WRFD-010510 WRFD-010503 WRFD-010504 Feature Name Conversational QoS Class Streaming QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Interactive QoS Class Background QoS Class
Issue 01 (2013-05-04)
320
1.5.4.29 Number of Abnormally Released HSPA-Carried RABs on SRNC Iur Interface Counters
Counter ID 67195000 Counter Name VS.RAB.AbnormRel.HSDP A.Iur Counter Description Number of HSDSCHCarried RABs Abnormally Released on Iur Interface for SRNC Number of EDCH-Carried RABs Abnormally Released on Iur Interface for SRNC
67195001
VS.RAB.AbnormRel.HSUP A.Iur
Description
When the best cell is under a DRNC, the measurement items take statistics of the number of abnormally released RABs according to different bearer types on the SRNC IUR interface.
Measurement point
As shown in point A of the figure, when an exception occurs, the SRNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation" or "Network Optimization", for details, see 3GPP TS 25.413), then the SRNC measures the corresponding counter on the Iur interface according to the bearer types if the serving cell belongs to DRNC. Figure 1-145 RAB release procedure
Issue 01 (2013-05-04)
321
As shown in point A of the figure, when an exception occurs, the SRNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation" or "Network Optimization", for details, see 3GPP TS 25.413), then the SRNC measures the corresponding counter on the Iur interface according to the bearer types if the serving cell belongs to DRNC. Figure 1-146 RAB release IU REL procedure
As shown in point A of the figure, when an exception occurs, the SRNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation" or "Network Optimization", for details, see 3GPP TS 25.413), then the SRNC measures the corresponding counter on the Iur interface according to the bearer types if the serving cell belongs to DRNC.
Issue 01 (2013-05-04)
322
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.HSDP A.Iur VS.RAB.AbnormRel.HSUP A.Iur Feature ID WRFD-010651 WRFD-010635 Feature Name HSDPA over Iur HSUPA over Iur
1.5.4.30 Number of RLs with Reconfiguration Canceled by the SRNC over Iur
Issue 01 (2013-05-04)
323
Counters
Counter ID 67179050 Counter Name VS.SHO.CancelRLRecfgIur .Tx Counter Description Number of Radio Link Synchronous Reconfiguration Cancellations on Iur Interface for SRNC
Description
This measurement item takes statistics of the number of RLs whose reconfiguration is canceled by the SRNC over the Iur interface.
Measurement point
The measurement is triggered at point C as shown in the figure. When the SRNC sends a RADIO LINK RECONFIGURATION CANCEL message to the DRNC, the SRNC measures the item for each Iur interface. Figure 1-148 Radio link reconfiguration cancellation procedure over Iur
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.CancelRLRecfgIur .Tx Feature ID WRFD-020203 Feature Name Inter RNC Soft Handover
1.5.4.31 Number of CS Conversational RABs carried on HSPA Normally Released on Iur Interface for SRNC Counters
Counter ID 67196206 Counter Name VS.RAB.NormRel.CS.HSP A.Conv.Iur Counter Description Number of HSPA-Carried CS Conversational RABs Normally Released on Iur Interface for SRNC
Description
When the best cell is under a DRNC, these measurement items take statistics of the number of CS Conversational RABs carried on HSPA normally released by the DRNC according to different service on the SRNC IUR interface.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization" , or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures each item according to different types of service on Iur Interface.
Issue 01 (2013-05-04)
325
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release" ,the RNC measures each item according to different types of service on Iur Interface.
Issue 01 (2013-05-04)
326
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.CS.HSP A.Conv.Iur Feature ID WRFD-010619 WRFD-010651 WRFD-010635 Feature Name CS voice over HSPA/HSPA + HSDPA over Iur HSUPA over Iur
1.5.4.32 Number of CS Conversational RABs carried on HSPA Abnormally Released on Iur Interface for SRNC
Issue 01 (2013-05-04)
327
Counters
Counter ID 67196207 Counter Name VS.RAB.AbnormRel.CS.HS PA.Conv.Iur Counter Description Number of HSPA-Carried CS Conversational RABs Abnormally Released on Iur Interface for SRNC
Description
When the best cell is under a DRNC, the measurement items take statistics of the number of abnormally released CS RABs carried on HSPA on the SRNC IUR interface.
Measurement point
The measurement is triggered at point A as shown in the figure. The SRNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the SRNC measures the items by the types of services on the IUR interface. Figure 1-151 RAB release procedure
The measurement is triggered at point A as shown in the figure. The SRNC RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling
Connection Release", reference to 3GPP TS 25.413),the SRNC measures the items by the types of services on the IUR interface. Figure 1-152 RAB release IU REL procedure
The measurement is triggered at point A as shown in the figure. The SRNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the SRNC measures the items by the types of services on the IUR interface.
Issue 01 (2013-05-04)
329
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.CS.HS PA.Conv.Iur Feature ID WRFD-010619 WRFD-010651 WRFD-010635 Feature Name CS voice over HSPA/HSPA + HSDPA over Iur HSUPA over Iur
1.5.4.33 Number of Normally Released PS RABs that Are in CELL_PCH or URA_PCH State on Iur Interface for SRNC
Issue 01 (2013-05-04)
330
Counters
Counter ID 73421884 Counter Name VS.RAB.NormRel.PS.PCH. Iur Counter Description Number of Normally Released PS RABs that Are in CELL_PCH or URA_PCH State on Iur Interface for SRNC
Description
This counter provides the number of normally released PS RABs that are in CELL_PCH or URA_PCH state on the Iur interface if the UE camps on a cell under the DRNC. The release of RABs in URA_PCH state is measured in the last cell that the UE camps on before entering the URA_PCH state.
Measurement point
The measurement is triggered at point A as shown in the following figure. After receiving an IU RELEASE COMMAND message from the CN, the RNC releases the corresponding RAB and then sends an IU RELEASE COMPLETE message to the CN. If the release cause in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", or if the RNC has sent a release request with the cause of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before the RNC receives the IU RELEASE COMMAND message, then the counter is measured on the Iur interface if the UE camps on a cell under the DRNC. Figure 1-154 Iu release procedure
Issue 01 (2013-05-04)
331
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS.PCH. Iur Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.5.4.34 Number of Abnormally Released PS RABs that Are in CELL_PCH or URA_PCH State on Iur Interface for SRNC Counters
Counter ID 73421885 Counter Name VS.RAB.AbnormRel.PS.PC H.Iur Counter Description Number of Abnormally Released PS RABs that Are in CELL_PCH or URA_PCH State on Iur Interface for SRNC
Description
This counter provides the number of abnormally released PS RABs that are in CELL_PCH or URA_PCH state on the Iur interface if the UE camps on a cell under the DRNC. The release of RABs in URA_PCH state is measured in the last cell that the UE camps on before entering the URA_PCH state.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the UE camps on a cell under the DRNC and a failure occurs, the SRNC sends the CN an RAB RELEASE REQUEST message. After receiving the message, the CN sends an RAB ASSIGNMENT REQUEST message to the RNC. If the RAB ASSIGNMENT REQUEST message contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), the SNRC measures a counter on the Iur interface according to the RAB type.
The measurement is triggered at point A as shown in the following figure. When the UE camps on a cell under the DRNC and a failure occurs, the SRNC sends the CN an RAB RELEASE REQUEST message. After receiving the message, the CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE COMMAND message contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), the SNRC measures a counter on the Iur interface according to the RAB type.
Issue 01 (2013-05-04)
333
The measurement is triggered at point A as shown in the following figure. When the UE camps on a cell under the DRNC and a failure occurs, the SRNC sends the CN an IU RELEASE REQUEST message. After receiving the message, the CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE COMMAND message contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), the SNRC measures a counter on the Iur interface according to the RAB type.
Issue 01 (2013-05-04)
334
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.PC H.Iur Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.5.4.35 Number of RRC Connection Releases (CCCH) Sent by the SRNC over the Iur Interface due to DSCR
Issue 01 (2013-05-04)
335
Counters
Counter ID 73423384 Counter Name VS.RRC.AttConnRelCCCH .DSCR.Iur Counter Description Number of RRC Connection Releases (CCCH) Sent by the SRNC over the Iur Interface due to DSCR
Description
This counter provides the number of RRC CONNECTION RELEASE (CCCH) messages sent by the SRNC over the Iur Interface because of Directed Signaling Connection Re-establishment (DSCR).
Measurement point
The measurement is triggered at point A as shown in the figure, when the SRNC sends the UE an RRC CONNECTION RELEASE (CCCH) message over the Iur interface because of DSCR. Figure 1-158 RRC connection release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnRelCCCH .DSCR.Iur Feature ID WRFD-021400 WRFD-010510 Feature Name Direct Signaling Connection Re-establishment (DSCR) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.5.4.36 Number of RRC Connection Releases (DCCH) Sent by the SRNC over the Iur Interface due to DSCR Counters
Counter ID 73423385 Counter Name VS.RRC.AttConnRelDCCH .DSCR.Iur Counter Description Number of RRC Connection Releases (DCCH) Sent by the SRNC over the Iur Interface due to DSCR
Description
This counter provides the number of RRC CONNECTION RELEASE (DCCH) messages sent by the SRNC over the Iur interface because of Directed Signaling Connection Re-establishment (DSCR).
Measurement point
The measurement is triggered at point A as shown in the figure, when the SRNC sends the UE an RRC CONNECTION RELEASE (DCCH) message over the Iur interface because of DSCR. Figure 1-159 RRC connection release procedure
Issue 01 (2013-05-04)
337
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnRelDCCH .DSCR.Iur Feature ID WRFD-021400 WRFD-010510 Feature Name Direct Signaling Connection Re-establishment (DSCR) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.5.5 Measurement related to traffic for Iur Interface(TRFFIC.IUR)

Overview
The Iur interface traffic measurement is used to measure the uplink (UL) and downlink (DL) signaling flows on the Iur interface and the UL and DL data streams in the CS and PS domains.
Counters
Counter ID 67199487 Counter Name VS.SRNCIurBytes SigDCH.Rx Counter Description Number of UL Bytes of Signaling Data Received by SRNC on DCH of Iur Interface Number of DL Bytes of Signaling Data Sent by SRNC on DCH of Iur Interface Number of UL Bytes of PS R99 Conversational Service Received by SRNC on Iur Interface Original Release Earlier than V900R011
67199488
VS.SRNCIurBytes SigDCH.Tx
67199497
VS.SRNCIurBytes PSR99Conv.Rx
Issue 01 (2013-05-04)
338
Counter ID 67199498
Counter Name VS.SRNCIurBytes PSR99Str.Rx
Counter Description Number of UL Bytes of PS R99 Streaming Service Received by SRNC on Iur Interface Number of UL Bytes of PS R99 Interactive Service Received by SRNC on Iur Interface Number of UL Bytes of PS R99 Background Service Received by SRNC on Iur Interface Number of DL Bytes of PS R99 Conversational Service Sent by SRNC on Iur Interface Number of DL Bytes of PS R99 Streaming Service Sent by SRNC on Iur Interface Number of DL Bytes of PS R99 Interactive Service Sent by SRNC on Iur Interface Number of DL Bytes of PS R99 Background Service Sent by SRNC on Iur Interface Number of UL Bytes of CS Conversational Service Received by SRNC on DCH of Iur Interface
67199499
VS.SRNCIurBytes PSR99Int.Rx
67199500
VS.SRNCIurBytes PSR99Bkg.Rx
67199501
VS.SRNCIurBytes PSR99Conv.Tx
67199502
VS.SRNCIurBytes PSR99Str.Tx
67199503
VS.SRNCIurBytes PSR99Int.Tx
67199504
VS.SRNCIurBytes PSR99Bkg.Tx
67199489
VS.SRNCIurBytes CSConv.Rx
Issue 01 (2013-05-04)
339
Counter ID 67199490
Counter Name VS.SRNCIurBytes CSStr.Rx
Counter Description Number of UL Bytes of CS Streaming Service Received by SRNC on DCH of Iur Interface Number of DL Bytes of CS Conversational Service Sent by SRNC on DCH of Iur Interface Number of DL Bytes of CS Streaming Service Sent by SRNC on DCH of Iur Interface Number of UL Bytes Sent by DRNC on DCH of Iur Interface Number of DL Bytes Received by DRNC Over DCH FP on the Iur Interface Number of bytes of PS HSUPA conversational service in SRNC for IUR Number of bytes of PS HSUPA streaming service in SRNC for IUR Number of bytes of PS HSUPA interactive service in SRNC for IUR Number of bytes of PS HSUPA background service in SRNC for IUR
67199493
VS.SRNCIurBytes CSConv.Tx
67199494
VS.SRNCIurBytes CSStr.Tx
67199505
VS.DRNCIurBytes DCH.Tx VS.DRNCIurBytes DCH.Rx
67199506
73410465
VS.SRNCIurBytes PSConvHSUPA.Rx
V900R012
73410466
VS.SRNCIurBytes PSStrHSUPA.Rx
V900R012
73410467
VS.SRNCIurBytes PSIntHSUPA.Rx
V900R012
73410470
VS.SRNCIurBytes PSBkgHSUPA.Rx
V900R012
Issue 01 (2013-05-04)
340
Counter ID 73410471
Counter Name VS.SRNCIurBytes PSConvHSDPA.Tx
Counter Description Number of bytes of PS HSDPA conversational service in SRNC for IUR Number of bytes of PS HSDPA streaming service in SRNC for IUR Number of bytes of PS HSDPA interactive service in SRNC for IUR Number of bytes of PS HSDPA background service in SRNC for IUR Number of bytes of CS HSDPA conversational service in SRNC for IUR Number of bytes of HSDPA services in DRNC for IUR Number of HSDPA Signaling Bytes on Iur Interface in SRNC Number of HSUPA Signaling Bytes on Iur Interface in SRNC Number of bytes of CS HSUPA conversational service in SRNC for IUR
73410472
VS.SRNCIurBytes PSStrHSDPA.Tx
V900R012
73410473
VS.SRNCIurBytes PSIntHSDPA.Tx
V900R012
73410474
VS.SRNCIurBytes PSBkgHSDPA.Tx
V900R012
73410476
VS.SRNCIurBytes CSConvHSDPA.Tx
V900R012
73410478
VS.DRNCIurBytes HSDPA.Rx VS.SRNCIurBytes SigHSDPA.Tx
V900R012
73410479
V900R012
73410480
VS.SRNCIurBytes SigHSUPA.Rx
V900R012
73410481
VS.SRNCIurBytes CSConvHSUPA.Rx
V900R012
None
1.5.5.1 Number of UL Bytes of Signaling Data Received by SRNC on DCH of Iur Interface Counters
Counter ID 67199487 Counter Name VS.SRNCIurBytesSigDCH. Rx Counter Description Number of UL Bytes of Signaling Data Received by SRNC on DCH of Iur Interface
Description
This counter provides the number of UL bytes of signaling data that the SRNC receives from the DRNC on the DCH FP of the Iur interface.
Measurement point
When receiving UL signaling data on the signaling bearer DCH FP (excluding the EDCH FP) of the Iur interface, the SRNC measures this counter. The value of this counter does not include the number of bytes of FP headers and this counter is measured separately on different Iur interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIurBytesSigDCH. Rx Feature ID WRFD-021000 Feature Name Transport Channel Management
1.5.5.2 Number of DL Bytes of Signaling Data Sent by SRNC on DCH of Iur Interface
Issue 01 (2013-05-04)
342
Counters
Counter ID 67199488 Counter Name VS.SRNCIurBytesSigDCH. Tx Counter Description Number of DL Bytes of Signaling Data Sent by SRNC on DCH of Iur Interface
Description
This counter provides the number of DL bytes of signaling data that the SRNC sends to the DRNC on the DCH FP of the Iur interface.
Measurement point
When sending DL signaling data to the DRNC on the signaling bearer DCH FP (excluding the HS-DSCH FP) of the Iur interface, the SRNC measures this counter. The value of this counter does not include the number of bytes of FP headers and this counter is measured separately on different Iur interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIurBytesSigDCH. Tx Feature ID WRFD-021000 Feature Name Transport Channel Management
1.5.5.3 Number of Bytes of UL PS R99 Services Received by SRNC on Iur Interface Counters
Counter ID 67199497 Counter Name VS.SRNCIurBytesPSR99Co nv.Rx Counter Description Number of UL Bytes of PS R99 Conversational Service Received by SRNC on Iur Interface
Issue 01 (2013-05-04)
343
Counter ID 67199498
Counter Name VS.SRNCIurBytesPSR99Str .Rx
Counter Description Number of UL Bytes of PS R99 Streaming Service Received by SRNC on Iur Interface Number of UL Bytes of PS R99 Interactive Service Received by SRNC on Iur Interface Number of UL Bytes of PS R99 Background Service Received by SRNC on Iur Interface
67199499
VS.SRNCIurBytesPSR99Int .Rx
67199500
VS.SRNCIurBytesPSR99Bk g.Rx
Description
These counters provide the number of bytes of UL PS R99 service data that the SRNC receives from the DRNC on the DCH FP of the Iur interface based on the service type.
Measurement point
The measurement is triggered based on the service type when the SRNC receives data of PS R99 services over the DCH FP on the Iur interface. The measured data excludes FP headers and the counters are measured separately on different Iur interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIurBytesPSR99Co nv.Rx VS.SRNCIurBytesPSR99Str .Rx VS.SRNCIurBytesPSR99Int .Rx VS.SRNCIurBytesPSR99Bk g.Rx Feature ID WRFD-010501 WRFD-010502 WRFD-010503 WRFD-010504 Feature Name Conversational QoS Class Streaming QoS Class Interactive QoS Class Background QoS Class
Issue 01 (2013-05-04)
344
1.5.5.4 Number of Bytes of DL PS R99 Services Sent by SRNC on Iur Interface Counters
Counter ID 67199501 Counter Name VS.SRNCIurBytesPSR99Co nv.Tx Counter Description Number of DL Bytes of PS R99 Conversational Service Sent by SRNC on Iur Interface Number of DL Bytes of PS R99 Streaming Service Sent by SRNC on Iur Interface Number of DL Bytes of PS R99 Interactive Service Sent by SRNC on Iur Interface Number of DL Bytes of PS R99 Background Service Sent by SRNC on Iur Interface
67199502
VS.SRNCIurBytesPSR99Str .Tx VS.SRNCIurBytesPSR99Int .Tx VS.SRNCIurBytesPSR99Bk g.Tx
67199503
67199504
Description
These counters provide the number of bytes of DL PS R99 service data that the SRNC sends to the DRNC on the DCH FP of the Iur interface based on the service type.
Measurement point
The measurement is triggered based on the service type when the SRNC sends data of PS R99 services to the DRNC over the DCH FP on the Iur interface. The measured data excludes FP headers and the counters are measured separately on different Iur interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIurBytesPSR99Co nv.Tx Feature ID WRFD-010501 Feature Name Conversational QoS Class
Issue 01 (2013-05-04)
345
Counter Name VS.SRNCIurBytesPSR99Str .Tx VS.SRNCIurBytesPSR99Int .Tx VS.SRNCIurBytesPSR99Bk g.Tx
Feature Name Streaming QoS Class Interactive QoS Class Background QoS Class
1.5.5.5 Number of Bytes of UL CS Services Received by SRNC over DCH on Iur Interface Counters
Counter ID 67199489 Counter Name VS.SRNCIurBytesCSConv. Rx Counter Description Number of UL Bytes of CS Conversational Service Received by SRNC on DCH of Iur Interface Number of UL Bytes of CS Streaming Service Received by SRNC on DCH of Iur Interface
67199490
VS.SRNCIurBytesCSStr.Rx
Description
These counters provide the number of bytes of UL CS service data that the SRNC receives from the DRNC on the DCH FP of the Iur interface based on the service type.
Measurement point
The measurement is triggered based on the service type when the SRNC receives data of CS services over the DCH FP (not including the EDCH FP) on the Iur interface. The measured data excludes FP headers and the counters are measured separately on different Iur interfaces.
Formula
None
Unit
byte
Issue 01 (2013-05-04)
346
Related Features
Counter Name VS.SRNCIurBytesCSConv. Rx VS.SRNCIurBytesCSStr.Rx Feature ID WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class
1.5.5.6 Number of Bytes of DL CS Services Sent by SRNC over DCH on Iur Interface Counters
Counter ID 67199493 Counter Name VS.SRNCIurBytesCSConv. Tx Counter Description Number of DL Bytes of CS Conversational Service Sent by SRNC on DCH of Iur Interface Number of DL Bytes of CS Streaming Service Sent by SRNC on DCH of Iur Interface
67199494
VS.SRNCIurBytesCSStr.Tx
Description
These counters provide the number of bytes of DL CS service data that the SRNC sends to the DRNC on the DCH FP of the Iur interface based on the service type.
Measurement point
The measurement is triggered based on the service type when the SRNC sends data of CS services over the DCH FP (not including the HS-DSCH FP) on the Iur interface. The measured data excludes FP headers and the counters are measured separately on different Iur interfaces.
Formula
None
Unit
byte
Issue 01 (2013-05-04)
347
Related Features
Counter Name VS.SRNCIurBytesCSConv. Tx VS.SRNCIurBytesCSStr.Tx Feature ID WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class
1.5.5.7 Number of UL Bytes Sent by DRNC on DCH of Iur Interface Counters

Counter ID 67199505 Counter Name VS.DRNCIurBytesDCH.Tx Counter Description Number of UL Bytes Sent by DRNC on DCH of Iur Interface
Description
This counter provides the number of UL data bytes that the DRNC sends to the SRNC on the DCH of the Iur interface.
Measurement point
When sending the UL MAC PDU on the DCH FP of the Iur interface, the DRNC measures this counter separately on different Iur interfaces (excluding the number of bytes of FP headers).
Formula
None
Unit
byte
Related Features
Counter Name VS.DRNCIurBytesDCH.Tx Feature ID WRFD-021000 Feature Name Transport Channel Management
1.5.5.8 Number of DL Bytes Received by DRNC on DCH of Iur Interface

Counters
Counter ID 67199506 Counter Name VS.DRNCIurBytesDCH.Rx Counter Description Number of DL Bytes Received by DRNC Over DCH FP on the Iur Interface
Description
This counter provides the number of DL data bytes that the DRNC receives from the SRNC Over DCH FP on the Iur interface.
Measurement point
When receiving the DL MAC PDU on the DCH FP of the Iur interface, the DRNC measures this counter separately on different Iur interfaces (excluding the number of bytes of FP headers).
Formula
None
Unit
byte
Related Features
Counter Name VS.DRNCIurBytesDCH.Rx Feature ID WRFD-021000 Feature Name Transport Channel Management
1.5.5.9 Number of Bytes of PS HSUPA Services Received by SRNC on Iur Interface Counters
Counter ID 73410465 Counter Name VS.SRNCIurBytesPSConv HSUPA.Rx VS.SRNCIurBytesPSStrHS UPA.Rx Counter Description Number of bytes of PS HSUPA conversational service in SRNC for IUR Number of bytes of PS HSUPA streaming service in SRNC for IUR
73410466
Issue 01 (2013-05-04)
349
Counter ID 73410467
Counter Name VS.SRNCIurBytesPSIntHS UPA.Rx VS.SRNCIurBytesPSBkgH SUPA.Rx
Counter Description Number of bytes of PS HSUPA interactive service in SRNC for IUR Number of bytes of PS HSUPA background service in SRNC for IUR
73410470
Description
These counters provide the number of bytes of PS HSUPA service data that the SRNC receives from the DRNC on the EDCH FP of the Iur interface based on the service type.
Measurement point
The measurement is triggered based on the service type when the SRNC receives data of PS HSUPA services over the EDCH FP on the Iur interface. The measured data excludes FP headers and the counters are measured separately on different Iur interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIurBytesPSConv HSUPA.Rx VS.SRNCIurBytesPSStrHS UPA.Rx VS.SRNCIurBytesPSIntHS UPA.Rx VS.SRNCIurBytesPSBkgH SUPA.Rx Feature ID WRFD-010617 WRFD-010501 WRFD-010635 WRFD-010635 WRFD-010635 Feature Name VoIP over HSPA/HSPA+ Conversational QoS Class HSUPA over Iur HSUPA over Iur HSUPA over Iur
1.5.5.10 Number of Bytes of PS HSDPA Services Received by SRNC on Iur Interface
Issue 01 (2013-05-04)
350
Counters
Counter ID 73410471 Counter Name VS.SRNCIurBytesPSConv HSDPA.Tx VS.SRNCIurBytesPSStrHS DPA.Tx VS.SRNCIurBytesPSIntHS DPA.Tx VS.SRNCIurBytesPSBkgH SDPA.Tx Counter Description Number of bytes of PS HSDPA conversational service in SRNC for IUR Number of bytes of PS HSDPA streaming service in SRNC for IUR Number of bytes of PS HSDPA interactive service in SRNC for IUR Number of bytes of PS HSDPA background service in SRNC for IUR
73410472
73410473
73410474
Description
These counters provide the number of bytes of PS HSDPA service data that the SRNC sends to the DRNC on the HSDSCH FP of the Iur interface based on the service type.
Measurement point
The measurement is triggered based on the service type when the SRNC receives data of PS HSDPA services over the HSDSCH FP on the Iur interface. The measured data excludes FP headers and the counters are measured separately on different Iur interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIurBytesPSConv HSDPA.Tx VS.SRNCIurBytesPSStrHS DPA.Tx VS.SRNCIurBytesPSIntHS DPA.Tx
Issue 01 (2013-05-04)
Feature ID WRFD-010617 WRFD-010501 WRFD-010651 WRFD-010651
Feature Name VoIP over HSPA/HSPA+ Conversational QoS Class HSDPA over Iur HSDPA over Iur
351
Counter Name VS.SRNCIurBytesPSBkgH SDPA.Tx
Feature Name HSDPA over Iur
1.5.5.11 Number of bytes of CS HSDPA conversational service in SRNC for IUR Counters
Counter ID 73410476 Counter Name VS.SRNCIurBytesCSConv HSDPA.Tx Counter Description Number of bytes of CS HSDPA conversational service in SRNC for IUR
Description
This counter provides the DL bytes of the DRNC CS conversational services. The bytes are sent by the SRNC over the HSDSCH FP on the Iur interface.
Measurement point
The measurement is triggered when the DL data CS HSDPA conversational services is sent by the SRNC over the HSDSCH FP on the Iur interface. The FP header is not included. The measurement is performed respectively on the basis of Iur interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIurBytesCSConv HSDPA.Tx Feature ID WRFD-010619 Feature Name CS voice over HSPA/HSPA +
1.5.5.12 Number of bytes of HSDPA services in DRNC for IUR
Issue 01 (2013-05-04)
352
Counters
Counter ID 73410478 Counter Name VS.DRNCIurBytesHSDPA. Rx Counter Description Number of bytes of HSDPA services in DRNC for IUR
Description
This counter provides the DL bytes of the DRNC HSDSCH service. The byte are sent by the SRNC.
Measurement point
The measurement is triggered when the DRNC receives DL MAC PDUs over the HSDSCH FP on the Iur interface. The FP header is not included. The measurement is performed respectively on the basis of Iur interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.DRNCIurBytesHSDPA. Rx Feature ID WRFD-010651 Feature Name HSDPA over Iur
1.5.5.13 Number of HSDPA Signaling Bytes on Iur Interface in SRNC Counters

Counter ID 73410479 Counter Name VS.SRNCIurBytesSigHSDP A.Tx Counter Description Number of HSDPA Signaling Bytes on Iur Interface in SRNC
Description
This counter provides the number of the DL signaling bytes that are sent to the DRNC from the SRNC over the HSDSCH FP on the Iur interface.
Measurement point
The measurement is triggered when the SRNC sends DL signaling over the HSDSCH FP carrying the signaling on the Iur interface to the DRNC. The FP header is not included. The measurement is performed respectively on the basis of Iur interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIurBytesSigHSDP A.Tx Feature ID WRFD-010651 WRFD-010652 Feature Name HSDPA over Iur SRB over HSDPA
1.5.5.14 Number of HSUPA Signaling Bytes on Iur Interface in SRNC Counters

Counter ID 73410480 Counter Name VS.SRNCIurBytesSigHSUP A.Rx Counter Description Number of HSUPA Signaling Bytes on Iur Interface in SRNC
Description
This counter provides the DRNC UL signaling bytes received by the SRNC over the EDCH FP on the Iur interface.
Measurement point
The measurement is triggered when the SRNC receives UL signaling on the EDCH FP carrying the signaling on the Iur interface. The FP header is not included. The measurement is performed respectively on the basis of Iur interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIurBytesSigHSUP A.Rx Feature ID WRFD-010635 WRFD-010636 Feature Name HSUPA over Iur SRB over HSUPA
1.5.5.15 Number of bytes of CS HSUPA conversational service in SRNC for IUR Counters
Counter ID 73410481 Counter Name VS.SRNCIurBytesCSConv HSUPA.Rx Counter Description Number of bytes of CS HSUPA conversational service in SRNC for IUR
Description
This counter provides the UL bytes of the DRNC CS HSUPA streaming services. The bytes are received by the SRNC over the EDCH FP on the Iur interface.
Measurement point
The measurement is triggered when the UL data of CS HSUPA streaming services is received by the SRNC over the EDCH FP on the Iur interface. The FP header is not included. The measurement is performed respectively on the basis of Iur interfaces.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIurBytesCSConv HSUPA.Rx Feature ID WRFD-010619 Feature Name CS voice over HSPA/HSPA +
Issue 01 (2013-05-04)
355
1.6 Measurement of MPU Performance(MPU)

Overview
The Main Processing Unit (MPU) measurement is used to assess the performance of the MPU subsystem of a main control SPU board in a Main Processing Subrack (MPS) or Extended Processing Subrack (EPS) of the RNC. SPU boards can be divided into two types: main control SPU boards and non-main control SPU boards. In addition to processing UMTS control-plane services, main control SPU boards also manage the user-plane, control-plane, and transmission resources of the UMTS. Non-main control SPU boards only process UMTS control-plane services. Subsystem 0 of the main control SPU board is the Main Processing Unit (MPU) subsystem. It manages the user-plane, control-plane, and transmission resources of the UMTS. Other subsystems of the main control SPU board and all subsystems of non-main control SPU boards are CPUS subsystems. They process control-plane services. Different types of SPU boards have different number of subsystems. For example, each SPUa board has four subsystems, and each SPUb board has eight subsystems. In addition, an SPUa subsystem and an SPUb subsystem have different processing capabilities. The MPU measurement is performed only to assess the performance of a single MPU subsystem.
FunctionSubSets
FunctionSubSet MPU FunctionSubSet Name Measurement related to MPU
1.6.1 Measurement related to MPU(MPU)

Overview
The MPU measurement is used to assess the running performance of an MPU subsystem in the RNC.
Counters
Counter ID 67204521 Counter Name VS.PSLoad.ULThr uput.MPU VS.PSLoad.DLThr uput.MPU Counter Description Throughput of PS Uplink Data for MPU Throughput of PS Downlink Data for MPU Original Release Earlier than V900R011 Earlier than V900R011
67204522
Issue 01 (2013-05-04)
356
None
1.6.1.1 Throughput of PS Uplink Data for MPU Counters

Counter ID 67204521 Counter Name VS.PSLoad.ULThruput.MP U Counter Description Throughput of PS Uplink Data for MPU
Description
This counter provides the total uplink PS throughput in the MPU subsystem, including retransmitted data. This counter is measured at the Radio Link Control (RLC) layer, whereas RLC headers are not measured. During soft handovers, the throughput is measured before the RNC combines the traffic on each link.
Measurement point
The RNC takes samples on the uplink traffic of all PS services every five seconds in the specified measurement period. At the end of the measurement period, the RNC divides the accumulated uplink traffic by the sampling duration to obtain the uplink PS throughput of the MPU in the measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.PSLoad.ULThruput.MP U Feature ID WRFD-040100 Feature Name Flow Control
1.6.1.2 Throughput of PS Downlink Data for MPU

Counters
Counter ID 67204522 Counter Name VS.PSLoad.DLThruput.MP U Counter Description Throughput of PS Downlink Data for MPU
Description
This counter provides the downlink throughput of all PS services in the MPU subsystem, including retransmitted data. This counter is measured at the Radio Link Control (RLC) layer and RLC headers are not measured. During soft handovers (not including softer handovers), the throughput on all links are measured.
Measurement point
The RNC takes samples on the downlink traffic of all PS services every five seconds in the specified measurement period. At the end of the measurement period, the RNC divides the accumulated downlink traffic by the sampling duration to obtain the downlink PS throughput of the MPU in the measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.PSLoad.DLThruput.MP U Feature ID WRFD-040100 Feature Name Flow Control
1.7 Measurement of NODEB Performance(NODEB)

Overview
The measurement object type NodeB is used to measure the performance of a NodeB. The NodeB belongs to the RNC and contains one measurement set NODEB.
Issue 01 (2013-05-04)
358
FunctionSubSets
FunctionSubSet ALGO.NODEB FunctionSubSet Name Measurement related to Algorithm per NodeB
1.7.1 Measurement related to Algorithm per NodeB (ALGO.NODEB)

Overview
The NodeB algorithm measurement involves the Iub congestion measurement, NodeB unavailability measurement, dynamic spectrum sharing measurement, and uplink NodeB credit resource consumption for UE admission. Iub congestion measurement is aimed to check whether the configured Iub bandwidth can meet the requirements of UEs under the NodeB. Based on this measurement result, operators can perform fault location or determine whether capacity expansion is required. The RNC periodically monitors the bandwidth usage of each Iub path under the NodeB. If the remaining bandwidth is less than a congestion left bandwidth threshold, the RNC determines that congestion occurs and sends a congestion indication message. After the RNC detects that the remaining bandwidth is more than the congestion clear clearing threshold, it sends a congestion elimination message. NodeB unavailability measurement is aimed to detect the condition that a NodeB becomes unavailable due to a fault or misoperation. This measurement can be used to analyze the impact of the fault or misoperation on services. Dynamic spectrum sharing enables the UMTS network to use some spectrums of the GSM network when the GSM traffic is light. Dynamic spectrum sharing measurement is used to assess the performance of this function. These counters measure the NodeB credit usage when CE Overbooking is enabled to determine whether to perform capacity expansion for CE resources and to locate the fault.
Counters
Counter ID 67192134 67192135 67203854 67203855 Counter Name VS.IUB.UL.Cong. Num VS.IUB.DL.Cong. Num VS.IUB.UL.Cong.T ime VS.IUB.DL.Cong.T ime Counter Description Number of Iub UL Congestions Number of Iub DL Congestions Duration of Iub UL Congestion Duration of Iub DL Congestion Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
359
Issue 01 (2013-05-04)
Counter ID 67203853 73441119
Counter Name VS.NodeB.UnavailTime VS.DSS.NodeB.Act .Duration
Counter Description Duration of NodeB Unavailability Total Dynamic Spectrum Sharing (DSS) Activation Duration Number of Received Dynamic Spectrum Sharing (DSS) Number of Normal Spectrum Withdrawals Number of Urgent Spectrum Withdrawals Number of Abnormal Spectrum Withdrawals Average NodeB Uplink Credit Usage When CE Overbooking Is Enabled for NodeB Maximum NodeB Uplink Credit Usage When CE Overbooking Is Enabled for NodeB Minimum NodeB Uplink Credit Usage When CE Overbooking Is Enabled for NodeB
Original Release Earlier than V900R011 V900R013
73423295
VS.DSS.NodeB.Act .Num VS.DSS.NodeB.Nor malDeAct.Num VS.DSS.NodeB.Urg entDeAct.Num VS.DSS.NodeB.Ab normalDeAct.Num VS.NodeB.ULCred itUsed.Mean
V900R013
73423296
V900R013
73423297
V900R013
73423298
V900R013
73441218
V900R014
73424007
VS.NodeB.ULCred itUsed.Max
V900R014
73424008
VS.NodeB.ULCred itUsed.Min
V900R014
None
1.7.1.1 Number of UL or DL Congestions on Iub Interface
Issue 01 (2013-05-04)
360
Counters
Counter ID 67192134 67192135 Counter Name VS.IUB.UL.Cong.Num VS.IUB.DL.Cong.Num Counter Description Number of Iub UL Congestions Number of Iub DL Congestions
Description
These counters provide the number of uplink or downlink bandwidth resource congestion occurrences on the Iub interface of the NodeB. When the residual bandwidth on the Iub interface is less than the configured congestion bandwidth threshold, congestion occurs on the Iub interface.
Measurement point
In the measurement period, the RNC measures the corresponding counter when it detects that the uplink or downlink bandwidth resources of a NodeB change from non-congested state to congested state.
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.UL.Cong.Num VS.IUB.DL.Cong.Num Feature ID WRFD-020106 WRFD-020106 Feature Name Load Reshuffling Load Reshuffling
1.7.1.2 Time of UL or DL Congestions on Iub Interface Counters

Counter ID 67203854 Counter Name VS.IUB.UL.Cong.Time Counter Description Duration of Iub UL Congestion
361
Issue 01 (2013-05-04)
Counter ID 67203855
Counter Name VS.IUB.DL.Cong.Time
Counter Description Duration of Iub DL Congestion
Description
These counters provide the duration of uplink or downlink bandwidth resource congestion occurrences on the Iub interface of a NodeB. When the residual bandwidth on the Iub interface is less than the configured congestion bandwidth threshold, congestion occurs on the Iub interface.
Measurement point
In the measurement period, the RNC measures the accumulated duration of uplink or downlink bandwidth resource congestion for each NodeB.
Formula
None
Unit
s
Related Features
Counter Name VS.IUB.UL.Cong.Time VS.IUB.DL.Cong.Time Feature ID WRFD-020106 WRFD-020106 Feature Name Load Reshuffling Load Reshuffling
1.7.1.3 NodeB Unavailability Time Counters

Counter ID 67203853 Counter Name VS.NodeB.UnavailTime Counter Description Duration of NodeB Unavailability
Description
This counter provides the unavailability time of a NodeB, that is, the out-of-service time of a NodeB. The NodeB is unavailable in the following conditions: The NodeB is blocked, the NCP or CCP port is faulty, or all the cells under a NodeB are out of service.
Measurement point
The RNC measures this item based on the accumulated unavailability time of the NodeB in a measurement period.
Formula
None
Unit
s
Related Features
Counter Name VS.NodeB.UnavailTime Feature ID WRFD-031000 Feature Name Intelligently Out of Service
1.7.1.4 Total Dynamic Spectrum Sharing (DSS) Activation Duration Counters

Counter ID 73441119 Counter Name VS.DSS.NodeB.Act.Duration Counter Description Total Dynamic Spectrum Sharing (DSS) Activation Duration
Description
This counter provides the duration when Dynamic Spectrum Sharing (DSS) is activated for a NodeB.
Measurement point
The measurement starts when a NodeB receives a spectrum activation command and stops when the NodeB receives a spectrum deactivation command. At the end of the measurement period, DSS activation duration is accumulated in this NodeB.
Formula
None
Unit
s
Related Features
Counter Name VS.DSS.NodeB.Act.Duration Feature ID MRFD-221802 Feature Name GSM and UMTS Dynamic Spectrum Sharing(UMTS)
1.7.1.5 Number of Received Dynamic Spectrum Sharing (DSS) Counters

Counter ID 73423295 Counter Name VS.DSS.NodeB.Act.Num Counter Description Number of Received Dynamic Spectrum Sharing (DSS)
Description
This counter provides the number of received commands that instruct a NodeB in Dynamic Spectrum Sharing (DSS).
Measurement point
In a measurement period, this counter is incremented by one each time the NodeB receives a spectrum activation command that instructs it in DSS.
Formula
None
Unit
None
Related Features
Counter Name VS.DSS.NodeB.Act.Num Feature ID MRFD-221802 Feature Name GSM and UMTS Dynamic Spectrum Sharing(UMTS)
1.7.1.6 Number of Normal Spectrum Withdrawals
Issue 01 (2013-05-04)
364
Counters
Counter ID 73423296 Counter Name VS.DSS.NodeB.NormalDe Act.Num Counter Description Number of Normal Spectrum Withdrawals
Description
This counter provides the number of received commands that instruct a NodeB in a normal spectrum withdrawal.
Measurement point
In a measurement period, this counter is incremented by one each time the NodeB receives a spectrum deactivation command that instructs it in a normal spectrum withdrawal.
Formula
None
Unit
None
Related Features
Counter Name VS.DSS.NodeB.NormalDe Act.Num Feature ID MRFD-221802 Feature Name GSM and UMTS Dynamic Spectrum Sharing(UMTS)
1.7.1.7 Number of Urgent Spectrum Withdrawals Counters

Counter ID 73423297 Counter Name VS.DSS.NodeB.UrgentDeA ct.Num Counter Description Number of Urgent Spectrum Withdrawals
Description
This counter provides the number of received commands that instruct a NodeB in an urgent spectrum withdrawal.
Measurement point
In a measurement period, this counter is incremented by one each time the NodeB receives a spectrum deactivation command that instructs it in an urgent spectrum withdrawal.
Formula
None
Unit
None
Related Features
Counter Name VS.DSS.NodeB.UrgentDeA ct.Num Feature ID MRFD-221802 Feature Name GSM and UMTS Dynamic Spectrum Sharing(UMTS)
1.7.1.8 Number of Abnormal Spectrum Withdrawals Counters

Counter ID 73423298 Counter Name VS.DSS.NodeB.AbnormalD eAct.Num Counter Description Number of Abnormal Spectrum Withdrawals
Description
This counter provides the number of times that connections between the RNC and the M2000 are abnormally disconnected.
Measurement point
In a measurement period, this counter is incremented by one each time a spectrum is deactivated for a spectrum withdrawal that is initiated by the RNC and triggered by failed handshakes between the RNC and the M2000.
Formula
None
Unit
None
Related Features
Counter Name VS.DSS.NodeB.AbnormalD eAct.Num Feature ID MRFD-221802 Feature Name GSM and UMTS Dynamic Spectrum Sharing(UMTS)
1.7.1.9 NodeB Credit Usage When CE Overbooking Is Enabled Counters

Counter ID 73441218 Counter Name VS.NodeB.ULCreditUsed. Mean Counter Description Average NodeB Uplink Credit Usage When CE Overbooking Is Enabled for NodeB Maximum NodeB Uplink Credit Usage When CE Overbooking Is Enabled for NodeB Minimum NodeB Uplink Credit Usage When CE Overbooking Is Enabled for NodeB
73424007
VS.NodeB.ULCreditUsed. Max
73424008
VS.NodeB.ULCreditUsed. Min
Description
These counters measure the average, maximum, and minimum NodeB credit usage when CE Overbooking is enabled. When CE Overbooking is disabled, the measurement result is 0.
Measurement point
The RNC takes samples of the NodeB credit usage when CE Overbooking is enabled in a measurement period of 5s. At the end of the measurement period, the RNC obtains the maximum and minimum NodeB credit usage, and then divides the accumulated NodeB credit usage by the number of samples to obtain the average NodeB credit usage in the measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.NodeB.ULCreditUsed. Mean VS.NodeB.ULCreditUsed. Max VS.NodeB.ULCreditUsed. Min Feature ID WRFD-140212 WRFD-140212 WRFD-140212 Feature Name CE Overbooking CE Overbooking CE Overbooking
1.8 Measurement of Physical RNC Node(NODESHARE)

Overview
Physical RNC Node
FunctionSubSets
FunctionSubSet RAB.NODESHARE RRC.NODESHARE FunctionSubSet Name Radio Access Bearer (RAB) Measurement for Physical RNC Nodes Radio Resource Control (RRC) Measurement for Physical RNC Nodes
1.8.1 Radio Access Bearer (RAB) Measurement for Physical RNC Nodes(RAB.NODESHARE)
Overview
This function subset provides RAB measurement for UEs whose load is shared between physical RNC nodes.
Issue 01 (2013-05-04)
368
Counters
Counter ID 73426004 Counter Name VS.RAB.AttEstab CS.Conv.NodeShare Counter Description Number of CS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Conversational Service) Number of Successful CS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Conversational Service) Number of PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Background Service) Number of PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Interactive Service) Number of Successful PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Background Service) Original Release V900R015
73426005
VS.RAB.SuccEstab CS.Conv.NodeShare
V900R015
73426006
VS.RAB.AttEstabP S.Bkg.NodeShare
V900R015
73426007
VS.RAB.AttEstabP S.Int.NodeShare
V900R015
73426008
VS.RAB.SuccEstab PS.Bkg.NodeShare
V900R015
Issue 01 (2013-05-04)
369
Counter ID 73426009
Counter Name VS.RAB.SuccEstab PS.Int.NodeShare
Counter Description Number of Successful PS RAB assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Interactive Service) Number of CS RABs Released Abnormally due to Radio Link Failure for UEs Whose Load Is Shared Between Physical RNC Nodes Number of PS RABs Released Abnormally due to Radio Link Failure for UEs Whose Load Is Shared Between Physical RNC Nodes Number of CS RABs Released Abnormally for UEs Whose Load Is Shared Between Physical RNC Nodes Number of PS RABs Released Abnormally for UEs Whose Load Is Shared Between Physical RNC Nodes Number of CS RABs Released Normally for UEs Whose Load Is Shared Between Physical RNC Nodes Number of PS RABs Released Normally for UEs Whose Load Is Shared Between Physical RNC Nodes
73426010
VS.RAB.AbnormR el.CS.RF.NodeShare
V900R015
73426011
VS.RAB.AbnormR el.PS.RF.NodeShare
V900R015
73426012
VS.RAB.AbnormR el.CS.NodeShare
V900R015
73426013
VS.RAB.AbnormR el.PS.NodeShare
V900R015
73426014
VS.RAB.NormRel. CS.NodeShare
V900R015
73426015
VS.RAB.NormRel. PS.NodeShare
V900R015
Issue 01 (2013-05-04)
370
None
1.8.1.1 Number of CS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Conversational Service) Counters
Counter ID 73426004 Counter Name VS.RAB.AttEstabCS.Conv. NodeShare Counter Description Number of CS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Conversational Service)
Description
This function subset provides the number of CS RAB assignment requests for UEs whose load is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point A shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN, this counter is measured based on the CS service type and physical RNC node if the UE load is shared between physical RNC nodes. Figure 1-160 RAB setup procedure (successful operation)
Issue 01 (2013-05-04)
371
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabCS.Conv. NodeShare Feature ID WRFD-150211 Feature Name RNC in Pool Load Sharing
1.8.1.2 Number of Successful CS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Conversational Service) Counters
Counter ID 73426005 Counter Name VS.RAB.SuccEstabCS.Con v.NodeShare Counter Description Number of Successful CS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Conversational Service)
Description
This function subset provides the number of successful CS RAB assignment requests for UEs whose load is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point B shown in the figure. When the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE and sends a RAB ASSIGNMENT RESPONSE message to the CN, this counter is measured based on the CS service type and physical RNC node if the UE load is shared between physical RNC nodes.
Issue 01 (2013-05-04)
372
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstabCS.Con v.NodeShare Feature ID WRFD-150211 Feature Name RNC in Pool Load Sharing
1.8.1.3 Number of PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes
Issue 01 (2013-05-04)
373
Counters
Counter ID 73426006 Counter Name VS.RAB.AttEstabPS.Bkg.N odeShare Counter Description Number of PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Background Service) Number of PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Interactive Service)
73426007
VS.RAB.AttEstabPS.Int.No deShare
Description
This function subset provides the number of PS RAB assignment requests for UEs whose load is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point A shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN, this counter is measured based on the PS service type and physical RNC node if the UE load is shared between physical RNC nodes. Figure 1-162 Successful RAB setup procedure
Issue 01 (2013-05-04)
374
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabPS.Bkg.N odeShare VS.RAB.AttEstabPS.Int.No deShare Feature ID WRFD-150211 WRFD-150211 Feature Name RNC in Pool Load Sharing RNC in Pool Load Sharing
1.8.1.4 Number of Successful PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes Counters
Counter ID 73426008 Counter Name VS.RAB.SuccEstabPS.Bkg. NodeShare Counter Description Number of Successful PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Background Service) Number of Successful PS RAB assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Interactive Service)
73426009
VS.RAB.SuccEstabPS.Int.N odeShare
Description
This function subset provides the number of successful PS RAB assignment requests for UEs whose load is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point B shown in the figure. When the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE and sends a RAB ASSIGNMENT RESPONSE message to the CN, this counter is measured based on the PS service type and physical RNC node if the UE load is shared between physical RNC nodes.
Figure 1-163 PS RAB setup procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstabPS.Bkg. NodeShare VS.RAB.SuccEstabPS.Int.N odeShare Feature ID WRFD-150211 WRFD-150211 Feature Name RNC in Pool Load Sharing RNC in Pool Load Sharing
1.8.1.5 Number of RABs Released Abnormally due to Radio Link Failure for UEs Whose Load Is Shared Between Physical RNC Nodes
Issue 01 (2013-05-04)
376
Counters
Counter ID 73426010 Counter Name VS.RAB.AbnormRel.CS.RF .NodeShare Counter Description Number of CS RABs Released Abnormally due to Radio Link Failure for UEs Whose Load Is Shared Between Physical RNC Nodes Number of PS RABs Released Abnormally due to Radio Link Failure for UEs Whose Load Is Shared Between Physical RNC Nodes
73426011
VS.RAB.AbnormRel.PS.RF .NodeShare
Description
This counter provides the number of CS RABs released abnormally due to the radio link failure for UEs whose load is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point A shown in the figure. When radio link failure occurs, the RNC sends a RAB RELEASE REQUEST message to the CN with the cause value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure." Then, when the RNC receives a RAB ASSIGNMENT REQUEST message from the CN with a cause value other than "User Inactivity," "Normal Release," "Successful Relocation," and "Network Optimization," this counter is measured based on the service domain and the physical RNC node if the UE load is shared between physical RNC nodes. For details on cause values indicating a normal release, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
377
This measurement is triggered at point A shown in the figure. When radio link failure occurs, the RNC sends a RAB RELEASE REQUEST message to the CN with the cause value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure." Then, when the RNC receives an IU RELEASE COMMAND message from the CN with a cause value other than "User Inactivity," "Normal Release," "Successful Relocation," and "Network Optimization," this counter is measured based on the service domain and the physical RNC node if the UE load is shared between physical RNC nodes. For details on cause values indicating a normal release, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
378
This measurement is triggered at point A shown in the figure. When radio link failure occurs, the RNC sends an IU RELEASE REQUEST message to the CN with the cause value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure." Then, when the RNC receives an IU RELEASE COMMAND message from the CN with a cause value other than "User Inactivity," "Normal Release," "Successful Relocation," and "Network Optimization," this counter is measured based on the service domain and the physical RNC node if the UE load is shared between physical RNC nodes. For details on cause values indicating a normal release, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
379
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.CS.RF .NodeShare VS.RAB.AbnormRel.PS.RF .NodeShare Feature ID WRFD-150211 WRFD-150211 Feature Name RNC in Pool Load Sharing RNC in Pool Load Sharing
1.8.1.6 Number of RABs Released Abnormally for UEs Whose Load Is Shared Between Physical RNC Nodes
Issue 01 (2013-05-04)
380
Counters
Counter ID 73426012 Counter Name VS.RAB.AbnormRel.CS.No deShare Counter Description Number of CS RABs Released Abnormally for UEs Whose Load Is Shared Between Physical RNC Nodes Number of PS RABs Released Abnormally for UEs Whose Load Is Shared Between Physical RNC Nodes
73426013
VS.RAB.AbnormRel.PS.No deShare
Description
This counter provides the number of RABs released abnormally for UEs whose load is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point A shown in the figure. When a failure occurs, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN a RAB ASSIGNMENT REQUEST message with a cause value other than "User Inactivity," "Normal Release," "Successful Relocation," and "Network Optimization," this counter is measured based on the domain of the RAB service and the physical RNC node if the UE load is shared between physical RNC nodes. For details on cause values indicating a normal release, see 3GPP TS 25.413. Figure 1-167 RAB release procedure
Issue 01 (2013-05-04)
381
This measurement is triggered at point A shown in the figure. When a failure occurs, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message with a cause value other than "User Inactivity," "Normal Release," "Successful Relocation," and "Network Optimization," this counter is measured based on the domain of the RAB service and the physical RNC node if the UE load is shared between physical RNC nodes. For details on cause values indicating a normal release, see 3GPP TS 25.413. Figure 1-168 RAB release IU REL procedure
This measurement is triggered at point A shown in the figure. When a failure occurs, the RNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message with a cause value other than "User Inactivity," "Normal Release," "Successful Relocation," and "Network Optimization," this counter is measured based on the domain of the RAB service and the physical RNC node if the UE load is shared between physical RNC nodes. For details on cause values indicating a normal release, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
382
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.CS.No deShare VS.RAB.AbnormRel.PS.No deShare Feature ID WRFD-150211 WRFD-150211 Feature Name RNC in Pool Load Sharing RNC in Pool Load Sharing
1.8.1.7 Number of RABs Released Normally for UEs Whose Load Is Shared Between Physical RNC Nodes
Issue 01 (2013-05-04)
383
Counters
Counter ID 73426014 Counter Name VS.RAB.NormRel.CS.NodeShare Counter Description Number of CS RABs Released Normally for UEs Whose Load Is Shared Between Physical RNC Nodes Number of PS RABs Released Normally for UEs Whose Load Is Shared Between Physical RNC Nodes
73426015
VS.RAB.NormRel.PS.NodeShare
Description
This counter provides the number of RABs released normally for UEs whose load is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point A shown in the figure. After receiving an IU RELEASE COMMAND message from the CN, the RNC releases the corresponding RAB and then sends an IU RELEASE COMPLETE message to the CN. If the release cause in the IU RELEASE COMMAND message is "User Inactivity," "Normal Release," "Successful Relocation," or "Network Optimization," or if the RNC has sent a release request with the cause value of "User Inactivity," "Network Optimization," or "UE Generated Signalling Connection Release" before the RNC receives the IU RELEASE COMMAND message, then this counter is measured based on the domain of the RAB service and the physical RNC node if the UE load is shared between physical RNC nodes. Figure 1-170 Iu release procedure
Issue 01 (2013-05-04)
384
This measurement is triggered at point A shown in the figure. After receiving a RAB ASSIGNMENT REQUEST message with a RAB release request from the CN, the RNC releases the corresponding RAB and then sends a RAB ASSIGNMENT RESPONSE message to the CN. If the release cause in the RAB ASSIGNMENT REQUEST message is "User Inactivity," "Normal Release," "Successful Relocation," or "Network Optimization," or if the RNC has sent a release request with the cause value of "User Inactivity," "Network Optimization," or "UE Generated Signalling Connection Release" before the RNC receives the IU RELEASE COMMAND message, then this counter is measured based on the domain of the RAB service and the physical RNC node if the UE load is shared between physical RNC nodes. Figure 1-171 Successful RAB release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.CS.NodeShare
Issue 01 (2013-05-04)
Feature Name RNC in Pool Load Sharing
385
Counter Name VS.RAB.NormRel.PS.NodeShare
Feature Name RNC in Pool Load Sharing
1.8.2 Radio Resource Control (RRC) Measurement for Physical RNC Nodes(RRC.NODESHARE)
Overview
This function subset provides RRC measurement for UEs whose load is shared between physical RNC nodes.
Counters
Counter ID 73426016 Counter Name VS.RRC.AttConnE stab.NodeShare Counter Description Number of RRC Connection Requests Sent by UEs Whose Load Is Shared Between Physical RNC Nodes Number of Successful RRC Connection Requests Sent by UEs Whose Load Is Shared Between Physical RNC Nodes Maximum Delay in Setting Up RRC Connection for UEs in CELL_DCH State Whose Load Is Shared Between Physical RNC Nodes Maximum Delay in Setting Up RRC Connection for UEs in CELL_FACH State Whose Load Is Shared Between Physical RNC Nodes Original Release V900R015
73426017
VS.RRC.SuccConn Estab.NodeShare
V900R015
73426018
VS.RRC.ConnEsta bTimeMax.CellDC H.NodeShare
V900R015
73426020
VS.RRC.ConnEsta bTimeMax.CellFA CH.NodeShare
V900R015
Issue 01 (2013-05-04)
386
Counter ID 73426019
Counter Name VS.RRC.ConnEsta bTimeMean.CellD CH.NodeShare
Counter Description Average Delay in Setting Up RRC Connection for UEs in CELL_DCH State Whose Load Is Shared Between Physical RNC Nodes Average Delay in Setting Up RRC Connection for UEs in CELL_FACH State Whose Load Is Shared Between Physical RNC Nodes Number of UEs Whose Load Is Shared Between Physical RNC Nodes
73426021
VS.RRC.ConnEsta bTimeMean.CellF ACH.NodeShare
V900R015
73426167
VS.LoadSharedAct iveUEs.NodeShare
V900R015
None
1.8.2.1 Number of RRC Connection Requests Sent by UEs Whose Load Is Shared Between Physical RNC Nodes Counters
Counter ID 73426016 Counter Name VS.RRC.AttConnEstab.NodeShare Counter Description Number of RRC Connection Requests Sent by UEs Whose Load Is Shared Between Physical RNC Nodes
Description
This counter provides the number of RRC connection requests sent by UEs whose load is shared between physical RNC nodes.
Issue 01 (2013-05-04)
387
Measurement point
This measurement is triggered at point A shown in the figure. When the RNC receives an RRC CONNECTION REQUEST message from a UE, this counter is measured for the RNC if the UE load is shared between physical RNC nodes. Figure 1-172 Procedure for successful RRC connection setup
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnEstab.NodeShare Feature ID WRFD-150211 Feature Name RNC in Pool Load Sharing
1.8.2.2 Number of Successful RRC Connection Requests Sent by UEs Whose Load Is Shared Between Physical RNC Nodes
Counters
Counter ID 73426017 Counter Name VS.RRC.SuccConnEstab.N odeShare Counter Description Number of Successful RRC Connection Requests Sent by UEs Whose Load Is Shared Between Physical RNC Nodes
Description
This counter provides the number of successful RRC connection requests sent by UEs whose load is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point C shown in the figure. When the RNC receives an RRC CONNECTION SETUP COMPLETE message from the UE, this counter is measured based on the physical RNC node if the UE load is shared between physical RNC nodes. Figure 1-173 Procedure for successful RRC connection setup
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.SuccConnEstab.N odeShare Feature ID WRFD-150211 Feature Name RNC in Pool Load Sharing
1.8.2.3 Delay in Setting Up RRC Connection for UEs in CELL_DCH State Whose Load Is Shared Between Physical RNC Nodes Counters
Counter ID 73426018 Counter Name VS.RRC.ConnEstabTimeM ax.CellDCH.NodeShare Counter Description Maximum Delay in Setting Up RRC Connection for UEs in CELL_DCH State Whose Load Is Shared Between Physical RNC Nodes Average Delay in Setting Up RRC Connection for UEs in CELL_DCH State Whose Load Is Shared Between Physical RNC Nodes
73426019
VS.RRC.ConnEstabTimeM ean.CellDCH.NodeShare
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73426180 Counter Name VS.RRC.ConnEstabTime.C ellDCH.NodeShare.Cum Counter Description Cumulative Duration of Setting Up RRC Connection for UEs in CELL_DCH State Whose Load Is Shared Between Physical RNC Nodes Number of Samples in Setting Up RRC Connection for UEs in CELL_DCH State Whose Load Is Shared Between Physical RNC Nodes
73426181
VS.RRC.ConnEstabTime.C ellDCH.NodeShare.Sample
Issue 01 (2013-05-04)
390
Description
This counter provides the maximum delay in setting up RRC connection for UEs in CELL_DCH state whose load is shared between physical RNC nodes.
Measurement point
When the RNC receives an RRC CONNECTION REQUEST message at point A shown in the figure, the receiving time T1 is recorded. When the RNC receives an RRC CONNECTION SETUP COMPLETE message at point C shown in the figure, the receiving time T2 is recorded. Assume that delta T=T2-T1. If the RRC connection is set up on a dedicated channel and the UE load is shared between physical RNC nodes, delta T is the delay in setting up the RRC connection for UEs in CELL_DCH state whose load is shared between physical RNC nodes. This counter is measured based on the physical RNC node. Figure 1-174 Procedure for successful RRC connection setup
Formula
VS.RRC.ConnEstabTimeMean.CellDCH.NodeShare = [VS.RRC.ConnEstabTime.CellDCH.NodeShare.Cum]/ [VS.RRC.ConnEstabTime.CellDCH.NodeShare.Sample]
Unit
ms
Issue 01 (2013-05-04)
391
Related Features
Counter Name VS.RRC.ConnEstabTimeM ax.CellDCH.NodeShare VS.RRC.ConnEstabTimeM ean.CellDCH.NodeShare Feature ID WRFD-150211 WRFD-150211 Feature Name RNC in Pool Load Sharing RNC in Pool Load Sharing
1.8.2.4 Delay in Setting Up RRC Connection for UEs in CELL_FACH State Whose Load Is Shared Between Physical RNC Nodes Counters
Counter ID 73426020 Counter Name VS.RRC.ConnEstabTimeM ax.CellFACH.NodeShare Counter Description Maximum Delay in Setting Up RRC Connection for UEs in CELL_FACH State Whose Load Is Shared Between Physical RNC Nodes Average Delay in Setting Up RRC Connection for UEs in CELL_FACH State Whose Load Is Shared Between Physical RNC Nodes
73426021
VS.RRC.ConnEstabTimeM ean.CellFACH.NodeShare
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73426182 Counter Name VS.RRC.ConnEstabTime.C ellFACH.NodeShare.Cum Counter Description Cumulative Duration of Setting Up RRC Connection for UEs in CELL_FACH State Whose Load Is Shared Between Physical RNC Nodes Number of Samples in Setting Up RRC Connection for UEs in CELL_FACH State Whose Load Is Shared Between Physical RNC Nodes
73426183
VS.RRC.ConnEstabTime.C ellFACH.NodeShare.Sample
Issue 01 (2013-05-04)
392
Description
This counter provides the maximum delay in setting up RRC connection for UEs in CELL_FACH state whose load is shared between physical RNC nodes.
Measurement point
When the RNC receives an RRC CONNECTION REQUEST message at point A shown in the figure, the receiving time T1 is recorded. When the RNC receives an RRC CONNECTION SETUP COMPLETE message at point C shown in the figure, the receiving time T2 is recorded. Assume that delta T=T2-T1. If the RRC connection is set up on the forward access channel (FACH) and the UE load is shared between physical RNC nodes, delta T is the delay in setting up RRC connection for UEs in CELL_FACH state whose load is shared between physical RNC nodes. This counter is measured based on the physical RNC node. Figure 1-175 Procedure for successful RRC connection setup
Formula
VS.RRC.ConnEstabTimeMean.CellFACH.NodeShare = [VS.RRC.ConnEstabTime.CellFACH.NodeShare.Cum]/ [VS.RRC.ConnEstabTime.CellFACH.NodeShare.Sample]
Unit
ms
Issue 01 (2013-05-04)
393
Related Features
Counter Name VS.RRC.ConnEstabTimeM ax.CellFACH.NodeShare VS.RRC.ConnEstabTimeM ean.CellFACH.NodeShare Feature ID WRFD-150211 WRFD-150211 Feature Name RNC in Pool Load Sharing RNC in Pool Load Sharing
1.8.2.5 Number of UEs Whose Load Is Shared Between Physical RNC Nodes Counters
Counter ID 73426167 Counter Name VS.LoadSharedActiveUEs. NodeShare Counter Description Number of UEs Whose Load Is Shared Between Physical RNC Nodes
Description
This counter provides the number of UEs whose load is shared between physical RNC nodes.
Measurement point
The RNC takes samples of UEs which are in CELL_DCH and CELL_FACH states after the logic RNC shares the load with the overflow RNC every five seconds. Then, the RNC adds the numbers of UEs in CELL_DCH and CELL_FACH states. At the end of the measurement period, the RNC divides the accumulated value on every sampling point in the measurement period by the number of samples to obtain the number of UEs whose load is shared between physical RNC nodes. NOTE: This counter is measured only on the master physical RNC corresponding to the logic RNC.
Formula
None
Unit
None
Related Features
Counter Name VS.LoadSharedActiveUEs. NodeShare Feature ID WRFD-150211 Feature Name RNC in Pool Load Sharing
Issue 01 (2013-05-04)
394
1.9 Measurement of Operator Performance at the NodeB Level(PLMN_NodeB)

Overview
Measurement of Operator per NodeB
FunctionSubSets
FunctionSubSet PLMN.NodeB FunctionSubSet Name Measurement Related to Operators at the NodeB Level
1.9.1 Measurement Related to Operators at the NodeB Level (PLMN.NodeB)

Overview
On the RNC side, measurements are performed at the NodeB level on a per operator basis.
Counters
Counter ID 73425875 Counter Name VS.NodeB.LDR.UL .BERateDown.PL MN Counter Description Number of UEs With Decreased BE Service Rate in the Case of UL Credit Resource Congestion for Operator Average NodeB Credit Consumption of an Operator in the Uplink Maximum NodeB Credit Consumption of an Operator in the Uplink Original Release V900R015
73425876
VS.NodeB.ULCred itUsed.Mean.PLM N VS.NodeB.ULCred itUsed.Max.PLMN
V900R015
73425879
V900R015
Issue 01 (2013-05-04)
395
Counter ID 73425880
Counter Name VS.NodeB.DLCred itUsed.Mean.PLM N VS.NodeB.DLCred itUsed.Max.PLMN
Counter Description Average NodeB Credit Consumption of an Operator in the Downlink Maximum NodeB Credit Consumption of an Operator in the Downlink
73425883
V900R015
None
1.9.1.1 Number of UEs With Decreased BE Service Rate in the Case of UL Credit Resource Congestion for Operator Counters
Counter ID 73425875 Counter Name VS.NodeB.LDR.UL.BERate Down.PLMN Counter Description Number of UEs With Decreased BE Service Rate in the Case of UL Credit Resource Congestion for Operator
Description
This counter measures the number of UEs with decreased BE service rate when the uplink credit resources for the operator of the UE are in basic congestion state and load reshuffling (LDR) is triggered for the UEs of the operator.
Measurement point
When the uplink credit resources for an operator are in basic congestion state, the RNC decreases the rates of UEs that belong to the operator and are performing the best effort (BE) service. This counter is increased by one each time the RNC decreases the rate of a UE performing the BE service.
Formula
None
Unit
None
Related Features
Counter Name VS.NodeB.LDR.UL.BERate Down.PLMN Feature ID WRFD-150214 Feature Name MOCN Independent CE Resource Allocation
1.9.1.2 Average NodeB Credit Consumption of an Operator in the Uplink Counters

Counter ID 73425876 Counter Name VS.NodeB.ULCreditUsed. Mean.PLMN Counter Description Average NodeB Credit Consumption of an Operator in the Uplink
Description
This counter measures the average NodeB credit consumption of an operator in the uplink.
Measurement point
The RNC takes samples of the NodeB credit resources occupied by the UEs of an operator in the uplink every 5 seconds in a measurement period. At the end of the measurement period, the RNC obtains the value of this counter by dividing the accumulated NodeB credit consumption by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.NodeB.ULCreditUsed. Mean.PLMN Feature ID WRFD-150214 Feature Name MOCN Independent CE Resource Allocation
Issue 01 (2013-05-04)
397
1.9.1.3 Maximum NodeB Credit Consumption of an Operator in the Uplink Counters

Counter ID 73425879 Counter Name VS.NodeB.ULCreditUsed. Max.PLMN Counter Description Maximum NodeB Credit Consumption of an Operator in the Uplink
Description
This counter measures the maximum NodeB credit consumption of an operator in the uplink.
Measurement point
The RNC takes samples of the NodeB credit resources occupied by the UEs of an operator in the uplink every 5 seconds in a measurement period. At the end of the measurement period, the RNC obtains the maximum NodeB credit consumption of the operator in the uplink.
Formula
None
Unit
None
Related Features
Counter Name VS.NodeB.ULCreditUsed. Max.PLMN Feature ID WRFD-150214 Feature Name MOCN Independent CE Resource Allocation
1.9.1.4 Average NodeB Credit Consumption of an Operator in the Downlink Counters

Counter ID 73425880 Counter Name VS.NodeB.DLCreditUsed. Mean.PLMN Counter Description Average NodeB Credit Consumption of an Operator in the Downlink
Issue 01 (2013-05-04)
398
Description
This counter measures the average NodeB credit consumption of an operator in the downlink.
Measurement point
The RNC takes samples of the NodeB credit resources occupied by the UEs of an operator in the downlink every 5 seconds in a measurement period. At the end of the measurement period, the RNC obtains the value of this counter by dividing the accumulated NodeB credit consumption by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.NodeB.DLCreditUsed. Mean.PLMN Feature ID WRFD-150214 Feature Name MOCN Independent CE Resource Allocation
1.9.1.5 Maximum NodeB Credit Consumption of an Operator in the Downlinke1 Counters

Counter ID 73425883 Counter Name VS.NodeB.DLCreditUsed. Max.PLMN Counter Description Maximum NodeB Credit Consumption of an Operator in the Downlink
Description
This counter measures the maximum NodeB credit consumption of an operator in the downlink.
Measurement point
The RNC takes samples of the NodeB credit resources occupied by the UEs of an operator in the downlink every 5 seconds in a measurement period. At the end of the measurement period, the RNC obtains the maximum NodeB credit consumption of the operator in the downlink.
Formula
None
Unit
None
Related Features
Counter Name VS.NodeB.DLCreditUsed. Max.PLMN Feature ID WRFD-150214 Feature Name MOCN Independent CE Resource Allocation
1.10 Measurement of RNC Performance(RNC)

Overview
The RNC performance measurement (RNC) is used to measure the overall performance of the basic signaling procedures of the RNC. It includes only one measurement set, that is, RNC performance measurement (RNC).
FunctionSubSets
FunctionSubSet AMR.RNC CBS.RNC HHO.RNC IRATHO.Cs.RNC IRATHO.PS.RNC LCS.RNC PAGE.RNC PDCPGTPU.RNC RAB.EstabCS.RNC RAB.EstabPS.RNC RAB.ModCs.RNC RAB.ModPs.RNC RAB.MultiRab.RNC
Issue 01 (2013-05-04)
FunctionSubSet Name Measurement related to AMR service Measurement related to CBS per RNC Hard Handover Measurement per RNC Measurement related to CS Inter-RAT handover per RNC Measurement related to PS Inter-RAT handover per RNC Measurement related to LCS service Measurement related to Paging per RNC Measurement related to PDCP Measurement of CS RAB assignment setup per RNC Measurement of PS RAB assignment setup per RNC Measurement of CS RAB assignment modification per RNC Measurement of PS RAB assignment modification per RNC Measurement of multi-RAB service per RNC
400
FunctionSubSet RAB.RelAbnormal.RNC RAB.RelCs.RNC RAB.RelPs.RNC RB.RNC Relocation.Drnc.RNC Relocation.Srnc.RNC RLC.RNC RNC.IMS RRC.Rel.RNC RRC.Setup.RNC RRC.STATE SHO.RNC SM.RNC TRAFF.LOAD.RNC
FunctionSubSet Name Measurement of RAB release per RNC Measurement of CS RAB release per RNC Measurement of PS RAB release per RNC Measurement of RB Procedure per RNC Measurement of relocation per DRNC Measurement of relocation per SRNC RLC measurement per RNC Measurement related to IMS RRC connection release measurement per RNC RRC connection setup measurement per RNC RRC state measurement Soft Handover Measurement per RNC Measurement related to Security mode per RNC Traffic Measurement per RNC
1.10.1 Measurement related to AMR service(AMR.RNC)

Overview
The purpose of the Adaptive Multi-Rate (AMR) technique is to use the minimal power resources to meet the Quality of Service (QoS) requirements. There are eight coding rates for the AMR speech service. During light traffic load, higher bit rates can be used to provide higher speech quality but they consume more resources. During heavy traffic load, however, lower bit rates can be used to enlarge the capacity but they provide lower speech quality.
Counters
Counter ID 67202488 Counter Name VS.RB.AMR.UL. 5.9.RNC Counter Description Average Number of AMR Service Users With UL Rate of 5.9 Kbit/s for RNC Original Release Earlier than V900R011
Issue 01 (2013-05-04)
401
Counter ID 67202489
Counter Name VS.RB.AMR.DL. 10.2.RNC
Counter Description Average Number of AMR Service Users With DL Rate of 10.2 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 12.2 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 4.75 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 5.15 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 5.9 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 7.4 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 7.95 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 10.2 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 12.2 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 4.75 Kbit/s for RNC
67202490
VS.RB.AMR.DL. 12.2.RNC
67202491
67202492
67202493
67202494
67202495
67202496
VS.RB.AMR.UL. 10.2.RNC
67202497
67202498
Issue 01 (2013-05-04)
402
Counter ID 67202499
Counter Name VS.RB.AMR.UL. 5.15.RNC
Counter Description Average Number of AMR Service Users With UL Rate of 5.15 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 7.4 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 7.95 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 6.7 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 6.7 Kbit/s for RNC Number of Times That Silence Is Detected in Downlink for AMR Calls per RNC Number of Times That Silence Is Detected in Uplink for AMR Calls per RNC
67202500
67202501
67202562
67202563
73422074
VS.AMR.DLSilent. Num
V900R012
73422075
VS.AMR.ULSilent. Num
V900R012
None
1.10.1.1 The Average Number of AMR Users with Different UL and DL Rates
Issue 01 (2013-05-04)
403
Counters
Counter ID 67202491 Counter Name VS.RB.AMR.DL.4.75.RNC Counter Description Average Number of AMR Service Users With DL Rate of 4.75 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 5.9 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 10.2 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 12.2 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 5.15 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 5.9 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 7.4 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 7.95 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 10.2 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 12.2 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 4.75 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 5.15 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 7.4 Kbit/s for RNC
67202488
VS.RB.AMR.UL.5.9.RNC
67202489
VS.RB.AMR.DL.10.2.RNC
67202490
67202492
67202493
67202494
67202495
67202496
67202497
67202498
67202499
67202500
Issue 01 (2013-05-04)
404
Counter ID 67202501
Counter Name VS.RB.AMR.UL.7.95.RNC
Counter Description Average Number of AMR Service Users With UL Rate of 7.95 Kbit/s for RNC Average Number of AMR Service Users With UL Rate of 6.7 Kbit/s for RNC Average Number of AMR Service Users With DL Rate of 6.7 Kbit/s for RNC
67202562
67202563
Description
These counters provide the average number of AMR users with different UL and DL rates in the RNC.
Measurement point
The number of AMR users with each UL or DL rate is sampled every five seconds in the RNC. At the end of the measurement period, the value of each counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.RB.AMR.DL.4.75.RNC VS.RB.AMR.UL.5.9.RNC VS.RB.AMR.DL.10.2.RNC VS.RB.AMR.DL.12.2.RNC VS.RB.AMR.DL.5.15.RNC VS.RB.AMR.DL.5.9.RNC VS.RB.AMR.DL.7.4.RNC VS.RB.AMR.DL.7.95.RNC
Issue 01 (2013-05-04)
Feature ID WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501
Feature Name Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class
405
Counter Name VS.RB.AMR.UL.10.2.RNC VS.RB.AMR.UL.12.2.RNC VS.RB.AMR.UL.4.75.RNC VS.RB.AMR.UL.5.15.RNC VS.RB.AMR.UL.7.4.RNC VS.RB.AMR.UL.7.95.RNC VS.RB.AMR.UL.6.7.RNC VS.RB.AMR.DL.6.7.RNC
Feature Name Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class
1.10.1.2 Number of Times That Silence Is Detected in Downlink for AMR Calls per RNC Counters
Counter ID 73422074 Counter Name VS.AMR.DLSilent.Num Counter Description Number of Times That Silence Is Detected in Downlink for AMR Calls per RNC
Description
This counter provides the number of times that silence is detected in downlink for AMR calls (narrowband and wideband AMR services) on an RNC.
Measurement point
The RNC detects the speech frames in downlink at the IUUP layer. It checks whether frame loss or erroneous frame exists in downlink at the IUUP layer every two seconds. If the ratio of lost frames or erroneous frames exceeds the threshold for three consecutive measurement periods (a measurement period lasts two seconds), the RNC considers that silence is detected during the call. Only one silence can be calculated for a call, regardless of the number of times that silence is detected during the call.
Formula
None
Unit
None
Related Features
Counter Name VS.AMR.DLSilent.Num Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.10.1.3 Number of Times That Silence Is Detected in Uplink for AMR Calls per RNC Counters
Counter ID 73422075 Counter Name VS.AMR.ULSilent.Num Counter Description Number of Times That Silence Is Detected in Uplink for AMR Calls per RNC
Description
This counter provides the number of times that silence is detected in uplink for AMR calls (narrowband and wideband AMR services) on an RNC.
Measurement point
The RNC detects the speech frames in uplink at the IUUP layer. It checks whether frame loss or erroneous frame exists in uplink at the IUUP layer every two seconds. If the ratio of lost frames or erroneous frames exceeds the threshold for three consecutive measurement periods (a measurement period lasts two seconds), the RNC considers that silence is detected in the call. Only one silence can be calculated for a call, regardless of the number of times that silence is detected during the call.
Formula
None
Unit
None
Related Features
Counter Name VS.AMR.ULSilent.Num Feature ID WRFD-010501 Feature Name Conversational QoS Class
Issue 01 (2013-05-04)
407
1.10.2 Measurement related to CBS per RNC(CBS.RNC)

Overview
The Cell Broadcast Service (CBS) is a type of point-to-multipoint multicast service similar to text broadcast on televisions. It provides the function of broadcasting in unacknowledged mode a certain number of messages in a specified geographical area. The CBS on the Iu-BC interface is specified by the Service Area Broadcast Protocol (SABP) in 3GPP 25.419. Cell Broadcast Service measurement is used to measure the basic cell broadcast procedures from the RNC perspective.
Counters
Counter ID 73426311 Counter Name VS.ETWS.WriteRe place Counter Description Number of ETWSrelated WRITEREPLACE Messages Received by the RNC Number of ETWSrelated WRITEREPLACE FAILURE Messages Sent by the RNC Original Release V900R015
73426312
VS.ETWS.WriteRe placeFail
V900R015
None
1.10.2.1 Number of ETWS-related WRITE-REPLACE Messages Received by the RNC Counters

Counter ID 73426311 Counter Name VS.ETWS.WriteReplace Counter Description Number of ETWS-related WRITE-REPLACE Messages Received by the RNC
Description
This counter provides the number of ETWS-related WRITE-REPLACE messages received by the RNC that carry the Paging ETWS Indicator information element. ETWS is short for Earthquake and Tsunami Warning System.
Measurement point
The measurement is triggered at point A as shown in the figure when the RNC receives a WRITEREPLACE message carrying the Paging ETWS Indicator information element, which indicates that the CBC initiates an ETWS warning process. CBC is short for cell broadcast center. Figure 1-176 Message interactions for a successful ETWS warning process
The measurement is triggered at point A as shown in the figure when the RNC receives a WRITEREPLACE message carrying the Paging ETWS Indicator information element, which indicates that the CBC initiates an ETWS warning process. Figure 1-177 Message interactions for a failed ETWS warning process
Issue 01 (2013-05-04)
409
Formula
None
Unit
None
Related Features
Counter Name VS.ETWS.WriteReplace Feature ID WRFD-150234 Feature Name Earthquake and Tsunami Warning System (ETWS)
1.10.2.2 Number of ETWS-related WRITE-REPLACE FAILURE Messages Sent by the RNC Counters
Counter ID 73426312 Counter Name VS.ETWS.WriteReplaceFail Counter Description Number of ETWS-related WRITE-REPLACE FAILURE Messages Sent by the RNC
Description
This counter provides the number of WRITE-REPLACE FAILURE messages sent by the RNC in response to the WRITE-REPLACE message that carry the Paging ETWS Indicator information element.
Measurement point
The measurement is triggered at point B as shown in the figure when the RNC sends the CBC a WRITE-REPLACE FAILURE message in response to the WRITE-REPLACE message carrying the Paging ETWS Indicator information element. The WRITE-REPLACE FAILURE message indicates a failed ETWS warning process.
Issue 01 (2013-05-04)
410
Figure 1-178 Message interactions for a failed ETWS warning process
Formula
None
Unit
None
Related Features
Counter Name VS.ETWS.WriteReplaceFail Feature ID WRFD-150234 Feature Name Earthquake and Tsunami Warning System (ETWS)
1.10.3 Hard Handover Measurement per RNC(HHO.RNC)

Overview
Hard handover is a handover procedure in which all the existing radio links connected to a UE are released before a new one is set up. That is, communication on the old radio link is interrupted and then that on the new radio link is established. Therefore, the performance of hard handover is not as good as that of soft handover. In normal cases, hard handover is triggered by the coverage, QoS, HCS, and LDR algorithm. Hard handovers are mainly classified into the intra-frequency handover and inter-frequency handover. Intra-frequency hard handover: In this mode, the cells that the UE camps on before and after the handover use the same frequency. The intra-frequency hard handover can be
performed only when soft handover is not available. The intra-frequency hard handover is performed through blind handover triggered by event 1D or 1F of intra-frequency measurement events. Inter-frequency hard handover: In this mode, the cells that the UE camps on before and after the handover use different frequencies. In addition, the inter-frequency hard handover involves the inter-band hard handover. Inter-frequency hard handover can balance the loads and achieve seamless connection between different TRXs. Generally, before an inter-frequency hard handover, the UE requires compressed mode configurations to perform an inter-frequency measurement according to its capability. The decision of inter-frequency hard handover is mainly based on inter-frequency measurement reports. When deciding to perform a hard handover, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message, TRANSPORT CHANNEL RECONFIGURATION message, RADIO BEARER RECONFIGURATION message, RADIO BEARER SETUP message, or RADIO BEARER RELEASE message to the UE for response. If the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message, TRANSPORT CHANNEL RECONFIGURATION COMPLETE message, RADIO BEARER RECONFIGURATION COMPLETE message, RADIO BEARER SETUP COMPLETE message, or RADIO BEARER RELEASE COMPLETE message from the UE in the target cell, the hard handover succeeds. If the RNC receives the PHYSICAL CHANNEL RECONFIGURATION FAILURE message, TRANSPORT CHANNEL RECONFIGURATION FAILURE message, RADIO BEARER RECONFIGURATION FAILURE message, RADIO BEARER SETUP FAILURE message, or RADIO BEARER RELEASE FAILURE message in the source cell before the hard handover or the RNC does not receive the response message from the UE before the timer expires, the hard handover fails. Hard Handover Measurement per RNC measures the number of intra-frequency and interfrequency hard handovers separately at the RNC level. Hard handovers with relocation are not measured.
Counters
Counter ID 67192284 Counter Name VS.HHO.AttIntraF req.RNC Counter Description Number of IntraFrequency Hard Handover Requests for RNC Number of InterFrequency Hard Handover Requests for RNC Number of Successful InterFrequency Hard Handovers for RNC Number of Successful IntraFrequency Hard Handovers for RNC Original Release Earlier than V900R011
67175428
VS.HHO.AttInterF req.RNC
67175429
VS.HHO.SuccInter Freq.RNC
67192285
VS.HHO.SuccIntra Freq.RNC
Issue 01 (2013-05-04)
412
None
1.10.3.1 Number of Intra-Frequency Hard Handover Requests Counters

Counter ID 67192284 Counter Name VS.HHO.AttIntraFreq.RNC Counter Description Number of Intra-Frequency Hard Handover Requests for RNC
Description
This counter provides the number of intra-frequency hard handover requests initiated by the RNC.
Measurement point
The measurement is triggered in point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. When initiating the intrafrequency hard handover, the RNC establishes RL and then sends the RADIO LINK SETUP REQUEST message to the NodeB. After the RNC receives the RADIO LINK SETUP RESPONSE message indicating a successful RL establishment, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. In this case, the RNC measures the counter. Figure 1-179 Successful hard handover procedure
Issue 01 (2013-05-04)
413
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttIntraFreq.RNC Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
1.10.3.2 Number of Inter-Frequency Hard Handover Requests Counters

Counter ID 67175428 Counter Name VS.HHO.AttInterFreq.RNC Counter Description Number of Inter-Frequency Hard Handover Requests for RNC
Description
This counter provides the number of inter-frequency hard handover requests initiated by the RNC.
Measurement point
The measurement is triggered in point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. When initiating the interfrequency hard handover, the RNC establishes RL and then sends the RADIO LINK SETUP REQUEST message to the NodeB. After the RNC receives the RADIO LINK SETUP RESPONSE message indicating a successful RL establishment, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. In this case, the RNC measures the counter.
Issue 01 (2013-05-04)
414
Figure 1-180 Successful hard handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttInterFreq.RNC Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.10.3.3 Number of Successful Inter-Frequency Hard Handovers
Issue 01 (2013-05-04)
415
Counters
Counter ID 67175429 Counter Name VS.HHO.SuccInterFreq.RN C Counter Description Number of Successful InterFrequency Hard Handovers for RNC
Description
This counter provides the number of successful inter-frequency hard handovers initiated by the RNC.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the inter-frequency hard handover, when the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the inter-frequency hard handover succeeds. In this case, the RNC measures the counter. Figure 1-181 Successful hard handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccInterFreq.RN C Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.10.3.4 Number of Successful Intra-Frequency Hard Handovers Counters

Counter ID 67192285 Counter Name VS.HHO.SuccIntraFreq.RN C Counter Description Number of Successful IntraFrequency Hard Handovers for RNC
Description
This counter provides the number of successful intra-frequency hard handovers initiated by the RNC.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the intra-frequency hard handover, when the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the intra-frequency hard handover succeeds. In this case, the RNC measures the counter.
Issue 01 (2013-05-04)
417
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccIntraFreq.RN C Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
1.10.4 Measurement related to CS Inter-RAT handover per RNC (IRATHO.Cs.RNC)

Overview
This function subset measures the CS inter-RAT handover between WCDMA and GSM at the RNC level. The CS inter-RAT handover is classified into CS outgoing inter-RAT handover and CS incoming inter-RAT handover.
The measurement of CS outgoing inter-RAT handover measures the handover from WCDMA to GSM at the RNC level. CS outgoing inter-RAT handover can be divided into two phases: the handover preparation phase and the handover execution phase. The handover preparation phase starts from the time when the RNC makes the decision of CS outgoing inter-RAT handover and sends a RELOCATION REQUIRED message to the CN, to the time when the RNC receives a RELOCATION COMMAND message from the CN. If the handover preparation phase is completed successfully, the outgoing inter-RAT handover execution phase is initiated when the RNC sends a HANDOVER FROM UTRAN COMMAND message to the UE. The outgoing inter-RAT handover execution phase lasts until the RNC receives an IU RELEASE COMMAND message from the CN. The measurement of CS incoming inter-RAT handover measures the handover from GSM to WCDMA at the RNC level. CS incoming inter-RAT handover can be divided into two phases: the handover preparation phase and the handover execution phase. The handover preparation phase starts from the time when the RNC allocates resources for the UE after receiving a RELOCATION REQUEST message, to the time when the RNC sends a RELOCATION REQUEST ACKNOWLEDGE message to the CN. After the handover preparation phase ends, the handover execution phase starts. If the handover from GSM to WCDMA is completed successfully, the UE sends a HANDOVER TO UTRAN COMPLETE message to the RNC. Then the RNC sends a RELOCATION COMPLETE message to the CN, and the handover execution phase is completed successfully.
Issue 01 (2013-05-04)
419
Figure 1-183 Flow chart of CS outgoing inter-RAT handover
Table 1 describes the measurement points shown in Figure1. Measurement points A

Issue 01 (2013-05-04)
Description VS.IRATHO.AttRelocPrepOutCS.RNC
420
Measurement points B C D
Description VS.IRATHO.SuccRelocPrepOutCS.RNC VS.IRATHO.AttOutCS.RNC VS.IRATHO.SuccOutCS.RNC
Figure 1-184 Flow chart of CS incoming inter-RAT
Issue 01 (2013-05-04)
421
Table 2 describes the measurement points shown in Figure2. Measurement points A B C D Description VS.IRATHO.AttRelocPrepInCS.RNC VS.IRATHO.SuccRelocPrepInCS.RNC VS.IRATHO.AttInCS.RNC VS.IRATHO.SuccInCS.RNC
Counters
Counter ID 67176008 Counter Name VS.IRATHO.AttIn CS.RNC Counter Description Number of CS Incoming Inter-RAT Handover Attempts for RNC Number of CS Outgoing Inter-RAT Handover Attempts for RNC Number of CS Outgoing Inter-RAT Handover Preparation Attempts for RNC Number of CS Incoming Inter-RAT Handover Preparation Attempts for RNC Number of Successful Preparations for CS Incoming Inter-RAT Handover for RNC Number of Successful CS Outgoing Inter-RAT Handovers for RNC Original Release Earlier than V900R011
67175945
VS.IRATHO.AttO utCS.RNC
67190398
VS.IRATHO.AttRe locPrepOutCS.RN C
67190311
VS.IRATHO.AttRe locPrepInCS.RNC
67190312
VS.IRATHO.Succ RelocPrepInCS.RN C
67190399
VS.IRATHO.Succ OutCS.RNC
Issue 01 (2013-05-04)
422
Counter ID 67190400
Counter Name VS.IRATHO.Succ RelocPrepOutCS.R NC
Counter Description Number of Successful Preparations for CS Outgoing Inter-RAT Handover for RNC Number of Successful CS Incoming Inter-RAT Handovers for RNC
67190314
VS.IRATHO.SuccI nCS.RNC
None
1.10.4.1 Number of CS Incoming Inter-RAT Handover Attempts Counters

Counter ID 67176008 Counter Name VS.IRATHO.AttInCS.RNC Counter Description Number of CS Incoming Inter-RAT Handover Attempts for RNC
Description
This counter provides the number of CS incoming inter-RAT handover attempts in the RNC.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC receives a HANDOVER TO UTRAN COMPLETE message from the UE, or when the RNC receives a RADIO LINK RESTORE INDICATION message from the Node B after sending a RELOCATION REQUEST ACKNOWLEDGE message to the CN and finishing the preparation for CS inter-RAT handover during the CS incoming inter-RAT handover. Only one of the two messages triggers the measurement. There is no repeated measurement.
Issue 01 (2013-05-04)
423
Figure 1-185 Normal incoming inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttInCS.RNC Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.10.4.2 Number of CS Outgoing Inter-RAT Handover Attempts
Issue 01 (2013-05-04)
424
Counters
Counter ID 67175945 Counter Name VS.IRATHO.AttOutCS.RN C Counter Description Number of CS Outgoing Inter-RAT Handover Attempts for RNC
Description
This counter provides the number of CS outgoing inter-RAT handover attempts in the RNC.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends a HANDOVER FROM UTRAN COMMAND message to the UE during the CS outgoing interRAT handover. Figure 1-186 Normal CS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttOutCS.RN C Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.10.4.3 Number of CS Outgoing Inter-RAT Handover Preparation Attempts Counters

Counter ID 67190398 Counter Name VS.IRATHO.AttRelocPrep OutCS.RNC Counter Description Number of CS Outgoing Inter-RAT Handover Preparation Attempts for RNC
Description
This counter provides the number of CS outgoing inter-RAT handover preparation attempts in the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a RELOCATION REQUIRED message to the CN during the CS outgoing inter-RAT handover.
Issue 01 (2013-05-04)
426
Figure 1-187 Normal CS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttRelocPrep OutCS.RNC Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.10.4.4 Number of CS Incoming Inter-RAT Handover Preparation Attempts
Issue 01 (2013-05-04)
427
Counters
Counter ID 67190311 Counter Name VS.IRATHO.AttRelocPrepI nCS.RNC Counter Description Number of CS Incoming Inter-RAT Handover Preparation Attempts for RNC
Description
This counter provides the number of CS incoming inter-RAT handover preparation attempts in the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a RELOCATION REQUEST message from the CN during the CS incoming inter-RAT handover. Figure 1-188 Normal incoming inter-RAT handover
Formula
None
Issue 01 (2013-05-04)
428
Unit
None
Related Features
Counter Name VS.IRATHO.AttRelocPrepI nCS.RNC Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.10.4.5 Number of Successful Preparations for CS Incoming Inter-RAT Handover Counters

Counter ID 67190312 Counter Name VS.IRATHO.SuccRelocPre pInCS.RNC Counter Description Number of Successful Preparations for CS Incoming Inter-RAT Handover for RNC
Description
This counter provides the number of successful preparations for CS incoming inter-RAT handover in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends a RELOCATION REQUEST ACKNOWLEDGE message to the CN during the CS incoming inter-RAT handover.
Issue 01 (2013-05-04)
429
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccRelocPre pInCS.RNC Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.10.4.6 Number of Successful CS Outgoing Inter-RAT Handovers
Issue 01 (2013-05-04)
430
Counters
Counter ID 67190399 Counter Name VS.IRATHO.SuccOutCS.R NC Counter Description Number of Successful CS Outgoing Inter-RAT Handovers for RNC
Description
This counter provides the number of successful CS outgoing inter-RAT handovers in the RNC.
Measurement point
The measurement is triggered at point D as shown in the figure, when the RNC receives an IU RELEASE COMMAND message with the cause value of "Successful Relocation", "Normal Release", or "Network Optimization" after sending a HANDOVER FROM UTRAN COMMAND message during the CS outgoing inter-RAT handover. In this case, the outgoing handover succeeds and this counter is measured. Figure 1-190 Normal CS outgoing inter-RAT handover
Formula
None
Issue 01 (2013-05-04)
431
Unit
None
Related Features
Counter Name VS.IRATHO.SuccOutCS.R NC Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.10.4.7 Number of Successful Preparations for CS Outgoing Inter-RAT Handover Counters

Counter ID 67190400 Counter Name VS.IRATHO.SuccRelocPre pOutCS.RNC Counter Description Number of Successful Preparations for CS Outgoing Inter-RAT Handover for RNC
Description
This counter provides the number of successful preparations for CS outgoing inter-RAT handover in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives a RELOCATION COMMAND message from the CN during the CS outgoing inter-RAT handover.
Issue 01 (2013-05-04)
432
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccRelocPre pOutCS.RNC Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.10.4.8 Number of Successful CS Incoming Inter-RAT Handovers
Issue 01 (2013-05-04)
433
Counters
Counter ID 67190314 Counter Name VS.IRATHO.SuccInCS.RN C Counter Description Number of Successful CS Incoming Inter-RAT Handovers for RNC
Description
This counter provides the number of successful CS incoming inter-RAT handovers in the RNC.
Measurement point
The measurement is triggered at point D as shown in the figure, when the RNC sends a RELOCATION COMPLETE message to the CN during the CS incoming inter-RAT handover. Figure 1-192 Normal incoming inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccInCS.RN C Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.10.5 Measurement related to PS Inter-RAT handover per RNC (IRATHO.PS.RNC)

Overview
The measurement of PS inter-RAT handover measures the inter-RAT handover between WCDMA and GPRS from the perspective of the RNC. According to different initiators, PS outgoing inter-RAT handover can be classified into two types: PS inter-RAT handover initiated by the UE and PS inter-RAT handover initiated by the RNC. After an UE sets up PS services in WCDMA, if the UE is in the state of CELL_FACH, CELL_PCH, or URA_PCH, and the UE initiates a cell reselection from WCDMA to GPRS, the handover is called PS inter-RAT handover initiated by the UE. If the UE is in the state of CELL_DCH, and the RNC initiates CELL CHANGE ORDER FROM UTRAN between WCDMA and GPRS, the handover is called PS inter-RAT handover initiated by the RNC.
Counters
Counter ID 67176098 Counter Name VS.IRATHO.AttO utPSUTRAN.RNC Counter Description Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC for RNC Number of Successful PS Outgoing Inter-RAT Handovers Initiated by RNC for RNC Number of PS Outgoing Inter-RAT Handover Attempts Initiated by UE for RNC Original Release Earlier than V900R011
67176100
VS.IRATHO.Succ OutPSUTRAN.RN C
67190316
VS.IRATHO.AttO utPSUE.RNC
Issue 01 (2013-05-04)
435
Counter ID 67176102
Counter Name VS.IRATHO.Succ OutPSUE.RNC
Counter Description Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE for RNC Number of LTE-toUMTS PS Handover Attempts Caused by the CSFB of an LTE Emergency Call for RNC Number of Successful LTE-toUMTS PS Handovers Caused by the CSFB of an LTE Emergency Call for RNC Number of Successful LTE-toUMTS PS Handover Preparations Caused by the CSFB of LTE Emergency Calls for RNC
73424356
VS.L2U.AttRelocP repInPS.Emerg.RN C
V900R014
73424357
VS.L2U.SuccReloc InPS.Emerg.RNC
V900R014
73426204
VS.L2U.SuccReloc PrepInPS.Emerg.R NC
V900R015
None
1.10.5.1 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC Counters

Counter ID 67176098 Counter Name VS.IRATHO.AttOutPSUTR AN.RNC Counter Description Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC for RNC
Issue 01 (2013-05-04)
436
Description
This counter provides the number of attempts of PS outgoing inter-RAT handover initiated by the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the CELL CHANGE ORDER FROM UTRAN message during the PS outgoing inter-RAT handover. Figure 1-193 Successful PS outgoing inter-RAT handover initiated by the RNC
Formula
None
Unit
None
Issue 01 (2013-05-04)
437
Related Features
Counter Name VS.IRATHO.AttOutPSUTR AN.RNC Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.10.5.2 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by RNC Counters

Counter ID 67176100 Counter Name VS.IRATHO.SuccOutPSUT RAN.RNC Counter Description Number of Successful PS Outgoing Inter-RAT Handovers Initiated by RNC for RNC
Description
This counter provides the number of successful PS outgoing inter-RAT handovers initiated by the RNC.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends the IU RELEASE COMPLETE message after receiving the IU RELEASE COMMAND message with the cause value of "Successful Relocation", "Normal Release", or "Network Optimization" during the PS outgoing inter-RAT handover. In this case, the PS outgoing inter-RAT handover succeeds and the counter is measured.
Issue 01 (2013-05-04)
438
Figure 1-194 Successful PS outgoing inter-RAT handover initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccOutPSUT RAN.RNC Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.10.5.3 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by UE
Issue 01 (2013-05-04)
439
Counters
Counter ID 67190316 Counter Name VS.IRATHO.AttOutPSUE. RNC Counter Description Number of PS Outgoing Inter-RAT Handover Attempts Initiated by UE for RNC
Description
This counter provides the number of attempts of PS outgoing inter-RAT handover initiated by the UE in the RNC.
Measurement point
When the UE is the state of CELL_FACH, CELL_PCH, or URA_PCH after PS service setup in WCDMA, the UE can reselect the GPRS network according to the cell reselection criteria. After entering the GPRS network through the reselection, the UE re-establishes PS services. During the re-establishment process, through SRNS CONTEXT REQUEST, the 2.5G SGSN inquires of the RNC about the context information of the PS RAB set up by the UE in the WCDMA network. The measurement is triggered at point A as shown in the figure, when the RNC receives the SRNS CONTEXT REQUEST message. Figure 1-195 PS outgoing inter-RAT handover initiated by the UE
Issue 01 (2013-05-04)
440
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttOutPSUE. RNC Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.10.5.4 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE Counters

Counter ID 67176102 Counter Name VS.IRATHO.SuccOutPSUE .RNC Counter Description Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE for RNC
Description
This counter provides the number of successful PS outgoing inter-RAT handovers initiated by the UE in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure, when the CN sends the IU RELEASE COMMAND message to release the context set up by the UE in the WCDMA system after receiving the SRNS CONTEXT RESPONSE message from the SRNC during the PS outgoing inter-RAT handover initiated by the UE. In this case, the PS outgoing inter-RAT handover initiated by the UE succeeds and the counter is measured.
Issue 01 (2013-05-04)
441
Figure 1-196 PS outgoing inter-RAT handover initiated by the UE
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccOutPSUE .RNC Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.10.5.5 Number of LTE-to-UMTS PS Handover Attempts Caused by the CSFB of an LTE Emergency Call for RNC
Issue 01 (2013-05-04)
442
Counters
Counter ID 73424356 Counter Name VS.L2U.AttRelocPrepInPS. Emerg.RNC Counter Description Number of LTE-to-UMTS PS Handover Attempts Caused by the CSFB of an LTE Emergency Call for RNC
Description
This counter measures the number of LTE-to-UMTS PS handover in preparation attempts caused by the CS fallback (CSFB) of an LTE emergency call at the RNC level.
Measurement point
The measurement is triggered at point A shown in figure 1, when the RNC receives a RELOCATION REQUEST message in which the information element (IE) Source RNC To Target RNC Transparent Container contains CSFB High Priority. In this case, this counter is incremented by one in the RNC. Figure 1-197 Emergency call signaling procedure on the LTE side
Formula
None
Unit
None
Related Features
Counter Name VS.L2U.AttRelocPrepInPS. Emerg.RNC Feature ID WRFD-140102 Feature Name CS Fallback Guarantee for LTE Emergency Calls
1.10.5.6 Number of Successful LTE-to-UMTS PS Handovers Caused by the CSFB of an LTE Emergency Call for RNC Counters
Counter ID 73424357 Counter Name VS.L2U.SuccRelocInPS.Em erg.RNC Counter Description Number of Successful LTEto-UMTS PS Handovers Caused by the CSFB of an LTE Emergency Call for RNC
Description
This counter measures the number of successful LTE-to-UMTS PS handovers caused by the CS fallback (CSFB) of an LTE emergency call at the RNC level.
Measurement point
The measurement is triggered at point D shown in figure 1, when the RNC sends the CN a RELOCATION COMPLETE message in which the corresponding UE information contains CSFB High Priority. In this case, this counter is incremented by one in the RNC.
Issue 01 (2013-05-04)
444
Figure 1-198 Emergency call signaling procedure on the LTE side
Formula
None
Unit
None
Related Features
Counter Name VS.L2U.SuccRelocInPS.Em erg.RNC Feature ID WRFD-140102 Feature Name CS Fallback Guarantee for LTE Emergency Calls
1.10.5.7 Number of Successful LTE-to-UMTS PS Handover Preparations Caused by the CSFB of LTE Emergency Calls for RNC
Issue 01 (2013-05-04)
445
Counters
Counter ID 73426204 Counter Name VS.L2U.SuccRelocPrepInP S.Emerg.RNC Counter Description Number of Successful LTEto-UMTS PS Handover Preparations Caused by the CSFB of LTE Emergency Calls for RNC
Description
This counter measures the number of successful preparations for LTE-to-UMTS PS handovers caused by the CSFB of LTE emergency calls.
Measurement point
This counter measures the number of successful preparations for LTE-to-UMTS PS handovers caused by the CSFB of LTE emergency calls. The measurement is triggered at point B shown in figure 1 when the RNC sends the CN a RELOCATION REQUEST ACKNOWLEDGE message in which the corresponding UE information contains CSFB High Priority. In this case, this counter is incremented by one on the RNC. Figure 1-199 Emergency call signaling procedure on the LTE side
Formula
None
Unit
None
Related Features
Counter Name VS.L2U.SuccRelocPrepInP S.Emerg.RNC Feature ID WRFD-140102 Feature Name CS Fallback Guarantee for LTE Emergency Calls
1.10.6 Measurement related to LCS service(LCS.RNC)

Overview
When the RNC receives a LOCATION REPORTING CONTROL message from the CN, it utilizes different positioning methods to determine the position of a UE according to the combinations of various factors. The UE positioning methods include: CELLID method, OTDOA method, Assisted GPS (AGPS) method. Hybrid positioning method, including AGPS, OTDOA and CELLID methods. After determining the appropriate positioning method, the RNC shall send positioning measurement request to the NodeB or UE to obtain the measurement results used for the UE position calculation. These positioning measurements include: UE-assisted CELLID measurements, UE-assisted OTDOA measurements, UE-assisted AGPS measurements, UE-based AGPS measurements, RTT measurements. When the RNC receives a LOCATION RELATED DATA REQUEST message from the CN, it determines the location-related assistance data according to the requested data type and sends the data in the ASSISTANCE DATA DELIVERY message to the UE. If the data transmission is successful, the RNC indicates the successful delivery to the CN in the LOCATION RELATED DATA RESPONSE message. If the data delivery fails, the RNC indicates failure to the CN in the LOCATION RELATED DATA FAILURE message. Location-related assistance data is mainly used for a UE to determine its own position. The types of assistance data presently supported by the RNC include: AGPS assistance data, OTDOA assistance data.
Issue 01 (2013-05-04)
447
Counters
Counter ID 67190216 Counter Name VS.LCS.AsstGpsDataTransDel Counter Description Number of Times that RNC Successfully Sends GPS Assistance Data to CN Number of Location Reports with Position Estimate Satisfying the Requested Accuracy for RNC Number of the positioning attempt of the different location method (AGPS) for RNC Number of OTDOA Based Positioning Procedures for RNC Number of Requests for Positioning upon Change of Service Area for RNC Number of Direct Positioning Requests for RNC Number of Successful Location Report upon Change of Service Area for RNC Number of Successful Direct Location Reports for RNC Number of the positioning attempt of the different location method (CELLID + RTT) for RNC Original Release Earlier than V900R011
67181025
VS.LCS.QoSAccur Met
67176209
VS.LCS.Agps.Att
67176211
VS.LCS.Otdoa.Att
67176214
VS.LCS.AttCsa
67176213
VS.LCS.AttDir
67176218
VS.LCS.SuccCsa
67176217
VS.LCS.SuccDir
73404075
VS.LCS.CellIdRtt. Att
V900R012
Issue 01 (2013-05-04)
448
Counter ID 73404076
Counter Name VS.LCS.CellCenter .Att
Counter Description Number of the positioning attempt of the different location method (CELLID CENTER) for RNC Number of the successful positioning of the different location method (CELL CENTER) for RNC Number of the successful positioning of the different location method (CELLID + RTT) for RNC Number of the successful positioning of the different location method (OTDOA) for RNC Number of the successful positioning of the different location method (AGPS) for RNC Number of the positioning attempt of using SAS centric mode for RNC Number of the successful positioning of using SAS centric mode for RNC Number of U-TDOA Positioning Attempts for RNC
73404077
VS.LCS.CellCenter .Succ
V900R012
73404078
VS.LCS.CellIdRtt. Succ
V900R012
73404079
VS.LCS.Otdoa.Suc c
V900R012
73404080
VS.LCS.Agps.Succ
V900R012
73394012
VS.LCS.SasMode. Att
V900R012
73394013
VS.LCS.SasMode.S ucc
V900R012
73423867
VS.LCS.Utdoa.Att
V900R013
Issue 01 (2013-05-04)
449
Counter ID 73423868
Counter Name VS.LCS.Utdoa.Suc c
Counter Description Number of Successful U-TDOA Positionings for RNC
Counter VS.LCS.SasMode.Att VS.LCS.SasMode.Succ Sub Counter VS.LCS.Utdoa.Att VS.LCS.Utdoa.Succ
1.10.6.1 Number of Successful Provisions of GPS Assistance Data Counters

Counter ID 67190216 Counter Name VS.LCS.AsstGpsDataTransDel Counter Description Number of Times that RNC Successfully Sends GPS Assistance Data to CN
Description
This measurement item takes statistics of the number of times that the RNC successfully provides the Global Positioning System assistance data after receiving the LOCATION RELATED DATA REQUEST message from the CN.
Measurement point
The measurement is triggered at point A as shown in figure. When the RNC receives from the CN a LOCATION RELATED DATA REQUEST message in which the IE "Location Related Data Request Type" is set to "Dedicated Assistance Data for Assisted GPS", the RNC measures this item when it responds with a LOCATION RELATED DATA RESPONSE message to the CN.
Issue 01 (2013-05-04)
450
Figure 1-200 Location related data request procedure
Formula
None
Unit
None
Related Features
Counter Name VS.LCS.AsstGpsDataTransDel Feature ID WRFD-020803 Feature Name A-GPS Based LCS
1.10.6.2 Number of Positioning Reports Meeting Accuracy Requirement Counters

Counter ID 67181025 Counter Name VS.LCS.QoSAccurMet Counter Description Number of Location Reports with Position Estimate Satisfying the Requested Accuracy for RNC
451
Issue 01 (2013-05-04)
Description
This measurement item takes statistics of the number of LOCATION REPORT messages from the RNC to the CN which meet the positioning accuracy requirement.
Measurement point
The measurement is triggered at point A as shown in figure. When the RNC sends the CN a LOCATION REPORT message, and if the Accuracy Code is smaller than or equal to that in the LOCATION REPORTING CONTROL message from the CN, it indicates that the LOCATION REPORT message meets the positioning accuracy requirement. In this case, the RNC measures this item. Figure 1-201 Location reporting procedure
Formula
None
Unit
None
Issue 01 (2013-05-04)
452
Related Features
Counter Name VS.LCS.QoSAccurMet Feature ID WRFD-020801 WRFD-020802 WRFD-020803 Feature Name Cell ID + RTT Function Based LCS OTDOA Based LCS A-GPS Based LCS
1.10.6.3 Number of Positioning Requests with Different Event Types Counters

Counter ID 67176213 Counter Name VS.LCS.AttDir Counter Description Number of Direct Positioning Requests for RNC Number of Requests for Positioning upon Change of Service Area for RNC
67176214
VS.LCS.AttCsa
Description
These measurement items take statistics of the number of positioning requests when the RNC receives a LOACTION REPORTING CONTROL message from the CN. These request messages have different event types. The following table describes the meaning of each counter. Counter Name VS.LCS.AttDir VS.LCS.AttCsa Description Event type is Direct Event type is Change of service area
Measurement point
The measurement is triggered at point A as shown in figure. When the RNC receives a LOCATION REPORTING CONTROL message containing one of the event types, the RNC measures these items.
Issue 01 (2013-05-04)
453
Figure 1-202 Location reporting control procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.LCS.AttDir Feature ID WRFD-020801 WRFD-020802 WRFD-020803 VS.LCS.AttCsa WRFD-020801 WRFD-020802 WRFD-020803 Feature Name Cell ID + RTT Function Based LCS OTDOA Based LCS A-GPS Based LCS Cell ID + RTT Function Based LCS OTDOA Based LCS A-GPS Based LCS
1.10.6.4 Number of Successful Positioning Reports with Different Event Types

Counters
Counter ID 67176217 67176218 Counter Name VS.LCS.SuccDir VS.LCS.SuccCsa Counter Description Number of Successful Direct Location Reports for RNC Number of Successful Location Report upon Change of Service Area for RNC
Description
These measurement items take statistics of the number of successful positioning reports sent by the RNC to the CN. These reports have different event types. The following table describes the meaning of each counter. Counter Name VS.LCS.SuccDir VS.LCS.SuccCsa Description Event type is Direct Event type is Change of service area
Measurement point
The measurement is triggered at point A as shown in figure. When the RNC receives a LOCATION REPORTING CONTROL message from the CN, and if the positioning procedure succeeds, the RNC sends the CN a LOCATION REPORT message containing an "Area Identity" IE. In this case, the RNC measures these items according to different event types. Figure 1-203 Location reporting procedure
Issue 01 (2013-05-04)
455
Formula
None
Unit
None
Related Features
Counter Name VS.LCS.SuccDir Feature ID WRFD-020801 WRFD-020802 WRFD-020803 VS.LCS.SuccCsa WRFD-020801 WRFD-020802 WRFD-020803 Feature Name Cell ID + RTT Function Based LCS OTDOA Based LCS A-GPS Based LCS Cell ID + RTT Function Based LCS OTDOA Based LCS A-GPS Based LCS
1.10.6.5 Number of the positioning attempt of the different location method for RNC Counters
Counter ID 73404076 Counter Name VS.LCS.CellCenter.Att Counter Description Number of the positioning attempt of the different location method (CELLID CENTER) for RNC Number of the positioning attempt of the different location method (AGPS) for RNC Number of OTDOA Based Positioning Procedures for RNC Number of the positioning attempt of the different location method (CELLID + RTT) for RNC
67176209
VS.LCS.Agps.Att
67176211
VS.LCS.Otdoa.Att
73404075
VS.LCS.CellIdRtt.Att
Issue 01 (2013-05-04)
456
Description
The measurement items take statistics of the number of the positioning attempt of the different location method for RNC The following table describes the meaning of each counter. Counter Name VS.LCS.Agps.Att VS.LCS.Otdoa.Att Description AGPS OTDOA
Measurement point
The measurement is triggered at point A as shown in figure. When the RNC receives a LOCATION REPORTING CONTROL message from the CN and determines a positioning method. Figure 1-204 Location reporting control procedure
Formula
None
Unit
None
Related Features
Counter Name VS.LCS.CellCenter.Att VS.LCS.Agps.Att VS.LCS.Otdoa.Att VS.LCS.CellIdRtt.Att Feature ID WRFD-020801 WRFD-020803 WRFD-020802 WRFD-020801 WRFD-020807 Feature Name Cell ID + RTT Function Based LCS A-GPS Based LCS OTDOA Based LCS Cell ID + RTT Function Based LCS Iupc Interface for LCS service
1.10.6.6 Number of the successful positioning of the different location method for RNC Counters
Counter ID 73404077 Counter Name VS.LCS.CellCenter.Succ Counter Description Number of the successful positioning of the different location method (CELL CENTER) for RNC Number of the successful positioning of the different location method (CELLID + RTT) for RNC Number of the successful positioning of the different location method (OTDOA) for RNC Number of the successful positioning of the different location method (AGPS) for RNC
73404078
VS.LCS.CellIdRtt.Succ
73404079
VS.LCS.Otdoa.Succ
73404080
VS.LCS.Agps.Succ
Description
The measurement items take statistics of the number of the successful positioning of the different location method for RNC
Measurement point
The measurement is triggered at point A as shown in figure. When the RNC receives a LOCATION REPORTING CONTROL message from the CN, and if the positioning procedure
succeeds, the RNC sends the CN a LOCATION REPORT message.In this case, the RNC measures these items according to different positioning methods. Figure 1-205 Location reporting procedure
Formula
None
Unit
None
Related Features
Counter Name VS.LCS.CellCenter.Succ VS.LCS.CellIdRtt.Succ Feature ID WRFD-020801 WRFD-020801 WRFD-020807 Feature Name Cell ID + RTT Function Based LCS Cell ID + RTT Function Based LCS Iupc Interface for LCS service VS.LCS.Otdoa.Succ WRFD-020802 OTDOA Based LCS
Issue 01 (2013-05-04)
459
Counter Name VS.LCS.Agps.Succ
Feature Name A-GPS Based LCS Iupc Interface for LCS service
1.10.6.7 Number of the times that the location in SAS centric mode is used in the RNC Counters
Counter ID 73394012 Counter Name VS.LCS.SasMode.Att Counter Description Number of the positioning attempt of using SAS centric mode for RNC Number of the successful positioning of using SAS centric mode for RNC
73394013
VS.LCS.SasMode.Succ
Description
This counter provides the number of times that the location in SAS centric mode is used in the RNC.
Measurement point
SAS is an abbreviation for Stand-Alone SMLC. It provides auxiliary data for location and performs related calculation. The interface between the RNC and the SAS is the Iu-PS interface. This counter helps assessing the success rate of SAS centric location on the Iu-PC interface. The measurement of VS.LCS.SasMode.Att is triggered at point A as shown in the figure, when the RNC sends the SAS an IUPC POSITION INITIATION REQUEST message. The measurement of VS.LCS.SasMode.Succ is triggered at point B, when the RNC receives from the SAS a POSITION INITIATION RESPONSE message that contains the location result.
Issue 01 (2013-05-04)
460
Figure 1-206 SAS location procedure
Formula
None
Unit
None
Related Features
Counter Name VS.LCS.SasMode.Att VS.LCS.SasMode.Succ Feature ID WRFD-020807 WRFD-020807 Feature Name Iupc Interface for LCS service Iupc Interface for LCS service
1.10.6.8 Number of U-TDOA Positioning Attempts Counters

Counter ID 73423867 Counter Name VS.LCS.Utdoa.Att Counter Description Number of U-TDOA Positioning Attempts for RNC
Issue 01 (2013-05-04)
461
Description
This counter provides the number of Uplink-Time Difference Of Arrival (U-TDOA) positioning attempts under an RNC.
Measurement point
In Stand-Alone SMLC (SAS) centric mode, the measurement is triggered at point B as shown in the figure. This counter is incremented by one when the RNC receives a PCAP POSITION ACTIVATION REQUEST message that designates the U-TDOA positioning method from the SAS. Note: If the SAS retransmits the PCAP POSITION ACTIVATION REQUEST message, only one is counted. Figure 1-207 U-TDOA positioning procedure in SAS centric mode
Formula
None
Unit
None
Related Features
Counter Name VS.LCS.Utdoa.Att Feature ID WRFD-020802 Feature Name OTDOA Based LCS
Issue 01 (2013-05-04)
462
1.10.6.9 Number of Successful U-TDOA Positionings Counters

Counter ID 73423868 Counter Name VS.LCS.Utdoa.Succ Counter Description Number of Successful UTDOA Positionings for RNC
Description
This counter provides the number of successful U-TDOA positionings under an RNC.
Measurement point
In SAS centric mode, the measurement is triggered at point D as shown in the figure. This counter is incremented by one when the RNC receives a PCAP POSITION INITIATION RESPONSE message and the following conditions are both met: 1. The RNC receives a PCAP POSITION ACTIVATION REQUEST message that designates the U-TDOA positioning method from the SAS at a point of time between point A when a PCAP POSITION INITIATION REQUEST message is received and point D when a PCAP POSITION INITIATION RESPONSE message is received. 2. At point C, the RNC sends the SAS a PCAP POSITION ACTIVATION RESPONSE message that contains UE's U-TDOA positioning information. Figure 1-208 U-TDOA positioning procedure in SAS centric mode
Issue 01 (2013-05-04)
463
Formula
None
Unit
None
Related Features
Counter Name VS.LCS.Utdoa.Succ Feature ID WRFD-020802 Feature Name OTDOA Based LCS
1.10.7 Measurement related to Paging per RNC(PAGE.RNC)

Overview
To page an UE, the CN sends a PAGING message to the RNC. Then, the RNC sends a PAGING TYPE 1 message or a PAGING TYPE 2 message to the UE according to the status of the UE. If the paged UE is in idle mode, CELL_PCH state or URA_PCH state, the RNC shall send a PAGING TYPE 1 message on the PCH to the cell in the paged area. If the UE is in CELL_PCH state and EPCH is supported by the network and the UE, the RNC sends a PAGING TYPE 2 message to the cells in the paging area. If the UE is in CELL_FACH or CELL_DCH state, the RNC shall send a PAGING TYPE 2 message to the UE on the DCCH. In addition, the UTRAN can send a PAGING TYPE 1 message to an UE in idle mode, CELL_PCH state or URA_PCH state for system information update. Also, the UTRAN can send a PAGING TYPE 1 message to an UE in CELL_PCH or URA_PCH state for UE state transition to support data transmission. If the paged UE is in idle mode, it will send a RRC CONNECTION REQUEST message to the RNC after receiving a PAGING TYPE 1 message. If the UE is in CELL_PCH or URA_PCH state, it will send a CELL UPDATE message with the cell update cause of "paging response" to the RNC after it receives a PAGING TYPE 1 message. For more information, refer to 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Counter ID 67174402 Counter Name VS.RANAP.Paging .Att.IdleUE VS.RANAP.Paging .Succ.IdleUE Counter Description Number of CN Pagings to Idle UE for RNC Number of Successful CN Pagings to Idle UE for RNC Original Release Earlier than V900R011 Earlier than V900R011
67174403
Issue 01 (2013-05-04)
464
Counter ID 67174405
Counter Name VS.UTRAN.Paging 1.Att
Counter Description Number of UTRANOriginated PAGING TYPE 1 Messages for RNC Number of PAGING TYPE 2 Messages for RNC Number of Successful Responses to PAGING TYPE 1 Messages for RNC Number of CN Paging Requests of CS Domain for RNC Number of CN Paging Requests of PS Domain for RNC Number of Unsuccessful CN Paging Requests of CS Domain for RNC Number of Unsuccessful CN Paging Requests of PS Domain for RNC Number of Successful PAGING TYPE 1 Message Responses from PTT UEs Received by RNC Number of RNCOriginated PAGING TYPE 1 Messages to PTT UEs
67174404
VS.UTRAN.Paging 2.Att VS.UTRAN.SuccPage1
67174406
67193711
VS.RANAP.CsPagi ng.Att VS.RANAP.PsPagi ng.Att VS.RANAP.CsPagi ng.Loss
Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67193712
67193713
67192714
VS.RANAP.PsPagi ng.Loss
73394071
VS.Paging1.Succ.P TT.RNC
V900R012
73394072
VS.Paging1.Att.PT T.RNC
V900R012
None
1.10.7.1 Number of Paging Messages to UE

Counters
Counter ID 67174402 Counter Name VS.RANAP.Paging.Att.Idle UE Counter Description Number of CN Pagings to Idle UE for RNC
Description
This measurement counter takes statistics of the number of PAGING TYPE 1 messages from the RNC to the UEs in idle mode after it receives the PAGING messages from the CN.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives a PAGING message from the CN, and if the paged UE is in idle mode, the RNC sends a PAGING TYPE 1 message to the cell in the paged area. In this case, the RNC measures this counter. Figure 1-209 Number of Paging Messages to UEs in Idle Mode
Formula
None
Unit
None
Related Features
Counter Name VS.RANAP.Paging.Att.Idle UE Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
1.10.7.2 Number of Successful Paging Messages to UE Counters

Counter ID 67174403 Counter Name VS.RANAP.Paging.Succ.Idl eUE Counter Description Number of Successful CN Pagings to Idle UE for RNC
Description
This measurement counter takes statistics of the number of RRC CONNECTION REQUEST messages from the UEs to the RNC that has sent a PAGING TYPE 1 messages to page the UEs in idle mode.
Measurement point
The measurement is triggered at point C as shown in in the figure. The RNC measures this counter when it receives a RRC CONNECTION REQUEST message from an UE with one of the following causes: "Terminating Conversational Call", "Terminating Streaming Call", "Terminating Interactive Call", "Terminating Background Call", "Terminating High Priority Signaling", "Terminating Low Priority Signaling, "Terminating cause unknown". Figure 1-210 Number of Paging Messages to UEs in Idle Mode
Issue 01 (2013-05-04)
467
Formula
None
Unit
None
Related Features
Counter Name VS.RANAP.Paging.Succ.Idl eUE Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
1.10.7.3 Number of RNC-Originated PAGING TYPE 1 Messages Counters

Counter ID 67174405 Counter Name VS.UTRAN.Paging1.Att Counter Description Number of UTRANOriginated PAGING TYPE 1 Messages for RNC
Description
This measurement counter takes statistics of the number of PAGING TYPE 1 messages originated by the RNC for triggering the state transition of an UE in CELL_PCH or URA_PCH state. Statistics taken by this item excludes the number of PAGING TYPE 1 messages that the RNC originates for the modification of system information.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC measures this counter when it initiates and sends a PAGING TYPE 1 message to an UE in CELL_PCH or URA_PCH state.
Issue 01 (2013-05-04)
468
Figure 1-211 Response of an UE in CELL_PCH or URA_PCH state to the PAGING TYPE 1 message
Formula
None
Unit
None
Related Features
Counter Name VS.UTRAN.Paging1.Att Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
1.10.7.4 Number of PAGING TYPE 2 Messages Counters

Counter ID 67174404 Counter Name VS.UTRAN.Paging2.Att Counter Description Number of PAGING TYPE 2 Messages for RNC
469
Issue 01 (2013-05-04)
Description
This measurement counter takes statistics of the number of PAGING TYPE 2 messages from the RNC to the UE in CELL_FACH or CELL_DCH state. When the RNC receives PAGING messages from the CN, it sends a PAGING TYPE 2 message to the UE if the paged UE is in CELL_FACH or CELL_DCH state.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives PAGING messages from the CN, it sends a PAGING TYPE 2 message to the UE in CELL_FACH or CELL_DCH state after receiving a PAGING message from the CN. In this case, the RNC measures this counter. Figure 1-212 Procedure of CN paging UE in CELL_FACH or CELL_DCH state
Formula
None
Unit
None
Issue 01 (2013-05-04)
470
Related Features
Counter Name VS.UTRAN.Paging2.Att Feature ID WRFD-010302 Feature Name Paging UE in CELL_FACH, CELL_DCH State (Type 2)
1.10.7.5 Number of Successful Responses to PAGING TYPE 1 Messages Counters

Counter ID 67174406 Counter Name VS.UTRAN.SuccPage1 Counter Description Number of Successful Responses to PAGING TYPE 1 Messages for RNC
Description
This measurement counter takes statistics of the number of CELL UPDATE messages from the UEs to the RNC. These messages are taken as successful responses to the PAGING TYPE 1 messages sent by the RNC to the UEs in CELL_PCH or URA_PCH state. After receiving the PAGING TYPE 1 messages, the UEs in CELL_PCH or URA_PCH state send CELL UPDATE messages with the cause of "paging response" to the RNC. A PAGING TYPE 1 message may be sent to an UE in CELL_PCH or URA_PCH state for the following reasons: The RNC receives a PAGING message from the CN. The UTRAN enables the UE to update system information.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives a CELL UPDATE message with the cause of "paging response", it measures this counter.
Issue 01 (2013-05-04)
471
Figure 1-213 Response of an UE in CELL_PCH or URA_PCH state to the PAGING TYPE 1 message
Formula
None
Unit
None
Related Features
Counter Name VS.UTRAN.SuccPage1 Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
1.10.7.6 Number of CS-Oriented PAGING Messages from the CN
Issue 01 (2013-05-04)
472
Counters
Counter ID 67193711 Counter Name VS.RANAP.CsPaging.Att Counter Description Number of CN Paging Requests of CS Domain for RNC
Description
This measurement counter takes statistics of the number of CS-oriented PAGING messages from the CN to the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a PAGING message from the CN, the measurement of this counter is triggered if the CN Domain Indicator IE in the message indicates the CS domain. Figure 1-214 Procedure of paging from the CN
Formula
None
Unit
None
Related Features
Counter Name VS.RANAP.CsPaging.Att Feature ID WRFD-010301 WRFD-010302 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) Paging UE in CELL_FACH, CELL_DCH State (Type 2)
1.10.7.7 Number of PS-Oriented PAGING Messages from the CN Counters

Counter ID 67193712 Counter Name VS.RANAP.PsPaging.Att Counter Description Number of CN Paging Requests of PS Domain for RNC
Description
This measurement counter takes statistics of the number of PS-oriented PAGING messages from the CN to the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a PAGING message from the CN, the measurement of this counter is triggered if the CN Domain Indicator IE in the message indicates the PS domain. Figure 1-215 Procedure of paging from the CN
Issue 01 (2013-05-04)
474
Formula
None
Unit
None
Related Features
Counter Name VS.RANAP.PsPaging.Att Feature ID WRFD-010301 WRFD-010302 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) Paging UE in CELL_FACH, CELL_DCH State (Type 2)
1.10.7.8 Number of Failures to Respond to CS-Oriented PAGING Messages from the CN Counters
Counter ID 67193713 Counter Name VS.RANAP.CsPaging.Loss Counter Description Number of Unsuccessful CN Paging Requests of CS Domain for RNC
Description
This measurement counter takes statistics of the number of failures to respond to CS-oriented PAGING messages from the CN to the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives from the CN a PAGING message in which the CN Domain Indicator IE indicates the CS domain, the measurement of this counter is triggered if the RNC does not send a Paging type 1 or Paging type 2 message. The reason why the RNC does not send a Paging type 1 or Paging type 2 message might be Iu flow control, or high CPU usage. If the RNC does not respond to a paging message that is consecutively retransmitted, the RNC counts it only once.
Issue 01 (2013-05-04)
475
Figure 1-216 Procedure of paging from the CN
Formula
None
Unit
None
Related Features
Counter Name VS.RANAP.CsPaging.Loss Feature ID WRFD-010301 WRFD-010302 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) Paging UE in CELL_FACH, CELL_DCH State (Type 2)
1.10.7.9 Number of Failures to Respond to PS-Oriented PAGING Messages from the CN
Issue 01 (2013-05-04)
476
Counters
Counter ID 67192714 Counter Name VS.RANAP.PsPaging.Loss Counter Description Number of Unsuccessful CN Paging Requests of PS Domain for RNC
Description
This measurement item takes statistics of the number of failures to respond to PS-oriented PAGING messages from the CN to the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives from the CN a PAGING message in which the CN Domain Indicator IE indicates the PS domain, the measurement of this item is triggered if the RNC does not send a Paging type 1 or Paging type 2 message. The reason why the RNC does not send a Paging type 1 or Paging type 2 message might be Iu flow control, or high CPU usage. Figure 1-217 Procedure of paging from the CN
Formula
None
Unit
None
Related Features
Counter Name VS.RANAP.PsPaging.Loss Feature ID WRFD-010301 WRFD-010302 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) Paging UE in CELL_FACH, CELL_DCH State (Type 2)
1.10.7.10 Number of CELL UPDATE Messages from PTT UEs as Paging Response Received by RNC Counters
Counter ID 73394071 Counter Name VS.Paging1.Succ.PTT.RNC Counter Description Number of Successful PAGING TYPE 1 Message Responses from PTT UEs Received by RNC
Description
This counter provides the number of times that the RNC receives from the UE a CELL UPDATE message with a cause value of "paging response" after the RNC sends to the PTT UEs in CELL_PCH or URA_PCH state a PAGING TYPE 1 message.
Measurement point
This measurement is triggered at point B as shown in the figure, when the RNC receives from the PTT UE a CELL UPDATE message with a cause value of "paging response".
Issue 01 (2013-05-04)
478
Figure 1-218 Procedure for UEs in CELL_PCH or URA_PCH state to respond to the PAGING TYPE 1 message
Formula
None
Unit
None
Related Features
Counter Name VS.Paging1.Succ.PTT.RNC Feature ID WRFD-010301 WRFD-020134 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) Push to Talk
1.10.7.11 Number of RNC-Originated PAGING TYPE 1 Messages to PTT UEs in CELL_PCH or URA_PCH state
Issue 01 (2013-05-04)
479
Counters
Counter ID 73394072 Counter Name VS.Paging1.Att.PTT.RNC Counter Description Number of RNC-Originated PAGING TYPE 1 Messages to PTT UEs
Description
This counter provides the number of PAGING TYPE 1 messages sent automatically by the RNC to PTT UEs.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC automatically sends a PAGING TYPE 1 message to the PTT UEs in CELL_PCH or URA_PCH state. The PAGING TYPE 1 message sent by the RNC due to system information change are not measured in this counter. Figure 1-219 Procedure for UEs in CELL_PCH or URA_PCH state to respond to the PAGING TYPE 1 message
Formula
None
Unit
None
Related Features
Counter Name VS.Paging1.Att.PTT.RNC Feature ID WRFD-010301 WRFD-020134 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) Push to Talk
1.10.8 Measurement related to PDCP(PDCPGTPU.RNC)

Overview
The RNC-based PDCP measurement focuses on the Robust Header Compression (ROHC) of PDCP headers.
Counters
Counter ID 67204484 Counter Name VS.PDCP.DL.ROH C.HdrCompressRa tio VS.PDCP.DL.ROH C.PktCompressRatio VS.PDCP.UL.ROH C.FailDecompRatio Counter Description Compression Rate of DL Packet Header Through ROHC Compression Compression Rate of DL Packets After ROHC Compression Decompression Failure Rate of UL Packets Through ROHC Algorithm Original Release Earlier than V900R011
67204485
67204486
None
1.10.8.1 Compression Ratio of DL Packet Headers Under ROHC
Issue 01 (2013-05-04)
481
Counters
Counter ID 67204484 Counter Name VS.PDCP.DL.ROHC.HdrC ompressRatio Counter Description Compression Rate of DL Packet Header Through ROHC Compression
Description
This measurement item takes statistics of the ratio of the packet header size after all downlink PS packets undergo Robust Header Compression (ROHC) to the header size before the ROHC during a measurement period in the RNC. This measurement item is valid when the ROHC algorithm is configured.
Measurement point
When a PDCP entity receives a downlink packet, it judges whether the packet is configured with ROHC. If the packet is not configured with ROHC, the PDCP entity does not report this measurement item. If the packet is configured with ROHC, the PDCP entity goes through the sub-headers of the packet to obtain the chain size before adding the size to the item DL Packet Header Size before Compression. After the compression, the PDCP entity then adds the new sub-header chain size to the item DL Packet Header Size after Compression. At the end of the measurement period, the PDCP entity reports the two item values to the performance function subset and resets the two items. Then the performance function subset calculates the compression ratio of the downlink packet headers under ROHC based on the reported values of DL Packet Header Size before Compression and DL Packet Header Size after Compression.
Formula
None
Unit
%
Related Features
Counter Name VS.PDCP.DL.ROHC.HdrC ompressRatio Feature ID WRFD-010617 Feature Name VoIP over HSPA/HSPA+
1.10.8.2 Compression Ratio of DL Packets Under ROHC
Issue 01 (2013-05-04)
482
Counters
Counter ID 67204485 Counter Name VS.PDCP.DL.ROHC.PktCo mpressRatio Counter Description Compression Rate of DL Packets After ROHC Compression
Description
This measurement item takes statistics of the ratio of the packet size after all downlink PS packets undergo Robust Header Compression (ROHC) to the packet size before the ROHC during a measurement period in the RNC. This measurement item is valid when the ROHC algorithm is configured.
Measurement point
When a PDCP entity receives a downlink packet, it judges whether the packet is configured with ROHC. If the packet is not configured with ROHC, the PDCP entity does not report this measurement item. If the packet is configured with ROHC, the number of compressed downlink packets increases by one. Meanwhile, the PDCP entity adds the initial packet size to the item DL Packet Size before Compression. After the compression, it adds the packet size to the item DL Packet Size after Compression. At the end of the measurement period, the PDCP entity reports the two item values to the performance function subset and resets the two items. Then the performance function subset calculates the compression ratio of the downlink packets under ROHC based on the reported values of DL Packet Size before Compression and DL Packet Size after Compression. Both service data and packet headers are measured.
Formula
None
Unit
%
Related Features
Counter Name VS.PDCP.DL.ROHC.PktCo mpressRatio Feature ID WRFD-010617 Feature Name VoIP over HSPA/HSPA+
1.10.8.3 Ratio of UL ROHC Decompression Failures to Total UL ROHC Decompression Operations
Issue 01 (2013-05-04)
483
Counters
Counter ID 67204486 Counter Name VS.PDCP.UL.ROHC.FailDecompRatio Counter Description Decompression Failure Rate of UL Packets Through ROHC Algorithm
Description
This measurement item takes statistics of the ratio of the number of UL PS packets failing to be decompressed by Robust Header Compression (ROHC) to the total number of UL packets undergoing ROHC decompression during a measurement period in the RNC. This measurement item is valid when the ROHC algorithm is configured.
Measurement point
When a PDCP entity receives an uplink packet, it judges whether the packet is configured with ROHC. If the packet is configured with ROHC, the value of the item Number of Uplink Packets to Be Decompressed increases by 1. Then, if the decompression fails, the value of the item Number of UL Packets Failing to Be Decompressed increases by 1. At the end of the measurement period, the PDCP entity reports the two item values to the performance function subset and resets the two items. Then, the performance function subset calculates the ratio of Number of Uplink Packets Failing to Be Decompressed to Number of UL Packets to Be Decompressed.
Formula
None
Unit
%
Related Features
Counter Name VS.PDCP.UL.ROHC.FailDecompRatio Feature ID WRFD-010617 Feature Name VoIP over HSPA/HSPA+
1.10.9 Measurement of CS RAB assignment setup per RNC (RAB.EstabCS.RNC)

Overview
The CN in CS domain initiates the radio access bearer setup procedure by sending a RAB ASSIGNMENT REQUEST message to the RNC.
After receiving the RAB ASSIGNMENT REQUEST message, the RNC selects an appropriate cell, allocates resources, and performs admission control based on the information in the message (such as service type, QoS, and priority), the traffic load of the system, and the networking strategy (such as DRD). The requirements of high-priority users are met preferentially(That is, when the resources are insufficient and the UEs with low-priority cannot set up the RAB, the RNC sends to the CN a RAB ASSGNMENT RESPONSE message if the queuing algorithm is enabled, indicating that the RAB is in the queue to wait for resources).If the admission of the RAB succeeds, the RNC starts the Iu transport connection setup procedure, the Iub radio bearer setup procedure, and the Uu radio bearer setup procedure. At last, the RNC sends to the CN a RAB ASSNMENT RESPONSE, indicating whether the RAB setup is successful. For details, refer to 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Counter ID 67174721 Counter Name VS.RAB.AttEstab CS.Conv.RNC Counter Description Number of CS Conversational RAB Establishment Attempts for RNC Number of CS Streaming RAB Establishment Attempts for RNC Mean Number of CS RABs for RNC Number of Attempted 64kbit/s CS RAB Establishments in a Cell Where 64kbit/s CS Service is Forbidden for RNC Number of Successful RAB Establishments for CS Conversational Services for RNC Number of Successful CS Streaming RAB Establishments for RNC Original Release Earlier than V900R011
67174722
VS.RAB.AttEstab CS.Str.RNC
67199791 67196235
VS.RAB.Num.CS. Mean VS.RAB.AttEstab CS.VPLimit.RNC
73394064
VS.RAB.SuccEstab CS.Conv.RNC
V900R012
73394065
VS.RAB.SuccEstab CS.Str.RNC
V900R012
None
1.10.9.1 Number of CS RABs Requested to Establish Counters

Counter ID 67174721 Counter Name VS.RAB.AttEstabCS.Conv. RNC Counter Description Number of CS Conversational RAB Establishment Attempts for RNC Number of CS Streaming RAB Establishment Attempts for RNC
67174722
VS.RAB.AttEstabCS.Str.R NC
Description
This counter provides the number of CS RABs establishment requests in the RNC according to different services.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message and if the message is from the CS domain, the RNC measures these items according to different types of services. Figure 1-220 RAB setup procedure (successful operation)
Issue 01 (2013-05-04)
486
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabCS.Conv. RNC VS.RAB.AttEstabCS.Str.R NC Feature ID WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class
1.10.9.2 Mean Number of CS RABs Counters

Counter ID 67199791 Counter Name VS.RAB.Num.CS.Mean Counter Description Mean Number of CS RABs for RNC
Description
This counter provides the average number of CS RABs in the RNC within a measurement period.
Measurement point
The RNC periodically samples (sampling periodicity is 5 seconds) the number of CS RABs. At the end of the measurement period, the RNC divides the total number of CS RABs by the number of samples to obtain the average number of CS RABs.
Formula
None
Unit
None
Issue 01 (2013-05-04)
487
Related Features
Counter Name VS.RAB.Num.CS.Mean Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.9.3 Number of CS VP RABs requested to establish in cell where VP is forbidden Counters

Counter ID 67196235 Counter Name VS.RAB.AttEstabCS.VPLi mit.RNC Counter Description Number of Attempted 64kbit/s CS RAB Establishments in a Cell Where 64kbit/s CS Service is Forbidden for RNC
Description
This counter provides the number of RAB setup requests for VP services when the VP call is limited.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN in the CS domain, it measures the counter if the RAB is for the VP service and it is limited for the best cell.
Issue 01 (2013-05-04)
488
Figure 1-221 RAB setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabCS.VPLi mit.RNC Feature ID WRFD-020130 Feature Name Videophone Service Restriction
1.10.9.4 Number of Successful RAB Establishments for CS Services
Issue 01 (2013-05-04)
489
Counters
Counter ID 73394064 Counter Name VS.RAB.SuccEstabCS.Con v.RNC Counter Description Number of Successful RAB Establishments for CS Conversational Services for RNC Number of Successful CS Streaming RAB Establishments for RNC
73394065
VS.RAB.SuccEstabCS.Str.R NC
Description
These counters provide the number of successful RAB establishments for different CS services in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message after receiving a RADIO BEARER SETUP COMPLETE message from the UE, the corresponding counter is measured according to the service type of the RAB. Figure 1-222 RAB setup procedure
Issue 01 (2013-05-04)
490
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstabCS.Con v.RNC VS.RAB.SuccEstabCS.Str.R NC Feature ID WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class
1.10.10 Measurement of PS RAB assignment setup per RNC (RAB.EstabPS.RNC)

Overview
The CN in PS domain initiates the radio access bearer setup procedure by sending a RAB ASSIGNMENT REQUEST message to the RNC. After receiving the RAB ASSIGNMENT REQUEST message, the RNC selects an appropriate cell, allocates resources, and performs admission control based on the information in the message (such as service type, QoS, and priority), the traffic load of the system, and the networking strategy (such as DRD). The requirements of high-priority users are met preferentially(That is, when the resources are insufficient and the UEs with low-priority cannot set up the RAB, the RNC sends to the CN a RAB ASSGNMENT RESPONSE message if the queuing algorithm is enabled, indicating that the RAB is in the queue to wait for resources). If the admission of the RAB succeeds, the RNC starts the Iu transport connection setup procedure, the Iub radio bearer setup procedure, and the Uu radio bearer setup procedure. At last, the RNC sends to the CN a RAB ASSNMENT RESPONSE, indicating whether the RAB setup is successful. For details, refer to 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Counter ID 67174785 Counter Name VS.RAB.AttEstabP S.Bkg.RNC Counter Description Number of PS Background RAB Establishment Attempts for RNC Original Release Earlier than V900R011
Issue 01 (2013-05-04)
491
Counter ID 67174788
Counter Name VS.RAB.AttEstabP S.Conv.RNC
Counter Description Number of PS Conversational RAB Establishment Attempts for RNC Number of PS Interactive RAB Establishment Attempts for RNC Number of PS Streaming RAB Establishment Attempts for RNC Maximum Duration of PS RAB Establishments Mapped on CCH for RNC Mean Duration of PS RAB Establishments Mapped on CCH for RNC Maximum Duration of PS RAB Establishments Mapped on DCH for RNC Mean Duration of PS RAB Establishments Mapped on DCH for RNC Number of PS Background RAB Establishment Attempts for RNC (Max DL Bit Rate in [0,32]kbit/s) Number of PS Background RAB Establishment Attempts for RNC (Max DL Bit Rate in (144,384]kbit/s)
67174787
VS.RAB.AttEstabP S.Int.RNC
67174786
VS.RAB.AttEstabP S.Str.RNC
67174812
VS.RAB.EstabPS. CellFACH.MaxTi me
67199679
VS.RAB.EstabPS. CellFACH.MeanTime VS.RAB.EstabPS. CellDCH.MaxTime
67174809
67199427
VS.RAB.EstabPS. CellDCH.MeanTim e VS.RAB.AttEstPS Bkg0.32.RNC
67174827
67174830
VS.RAB.AttEstabP S.Bkg. 144.384.RNC
Issue 01 (2013-05-04)
492
Counter ID 67174828
Counter Name VS.RAB.AttEstabP S.Bkg.32.64.RNC
Counter Description Number of PS Background RAB Establishment Attempts for RNC (Max DL Bit Rate in (32,64]kbit/s) Number of PS Background RAB Establishment Attempts for RNC (Max DL Bit Rate in (64,144]kbit/s) Number of PS Background RAB Establishment Attempts for RNC (Max DL Bit Rate More Than 384kbit/ s) Number of PS Conversational RAB Establishment Attempts for RNC (Max DL Bit Rate in [0,32]kbit/s) Number of PS Conversational RAB Establishment Attempts for RNC (Max DL Bit Rate More Than 32kbit/s) Number of PS Interactive RAB Establishment Attempts for RNC (Max DL Bit Rate in [0,32]kbit/s) Number of PS Interactive RAB Establishment Attempts for RNC (Max DL Bit Rate in (144,384]kbit/s)
67174829
VS.RAB.AttEstabP S.Bkg.64.144.RNC
67174831
VS.RAB.AttEstabP S.Bkg.Mor384.RN C
67174815
VS.RAB.AttEstabP S.Conv.0.32.RNC
67174816
VS.RAB.AttEstabP S.Conv.Mor32.RN C
67174822
VS.RAB.AttEstabP S.Int.0.32.RNC
67174825
Issue 01 (2013-05-04)
493
Counter ID 67174823
Counter Name VS.RAB.AttEstabP S.Int.32.64.RNC
Counter Description Number of PS Interactive RAB Establishment Attempts for RNC (Max DL Bit Rate in (32,64]kbit/s) Number of PS Interactive RAB Establishment Attempts for RNC (Max DL Bit Rate in (64,144]kbit/s) Number of PS Interactive RAB Establishment Attempts for RNC (Max DL Bit Rate More Than 384kbit/ s) Number of PS Streaming RAB Establishment Attempts for RNC (Max DL Bit Rate in [0,32]kbit/s) Number of PS Streaming RAB Establishment Attempts for RNC (Max DL Bit Rate in (32,64]kbit/s) Number of PS Streaming RAB Establishment Attempts for RNC (Max DL Bit Rate in (144,384]kbit/s) Number of PS Streaming RAB Establishment Attempts for RNC (Max DL Bit Rate in (64,144]kbit/s)
67174824
67174826
VS.RAB.AttEstabP S.Int.Mor384.RNC
67174817
VS.RAB.AttEstabP S.Str.0.32.RNC
67174818
67174820
67174819
Issue 01 (2013-05-04)
494
Counter ID 67174821
Counter Name VS.RAB.AttEstabP S.Str.Mor384
Counter Description Number of PS Streaming RAB Establishment Attempts for RNC (Max DL Bit Rate More Than 384kbit/ s) Number of Successful PS Background RAB Establishments for RNC (Max DL Bit Rate in [0,32]kbit/s) Number of Successful PS Background RAB Establishments for RNC (Max DL Bit Rate in (144,384] kbit/s) Number of Successful PS Background RAB Establishments for RNC (Max DL Bit Rate in (32,64]kbit/s) Number of Successful PS Background RAB Establishments for RNC (Max DL Bit Rate in (64,144]kbit/ s) Number of Successful PS Conversational RAB Establishments for RNC (Max DL Bit Rate in [0,32]kbit/s)
67174844
VS.RAB.SuccEstab PS.Bkg.0.32.RNC
67174847
VS.RAB.SuccEstab PS.Bkg. 144.384.RNC
67174845
VS.RAB.SuccEstab PS.Bkg.32.64.RNC
67174846
VS.RAB.SuccEstab PS.Bkg. 64.144.RNC
67174832
VS.RAB.SuccEstab PS.Conv.0.32.RNC
Issue 01 (2013-05-04)
495
Counter ID 67174833
Counter Name VS.RAB.SuccEstab PS.Conv.Mor32.R NC
Counter Description Number of Successful PS Conversational RAB Establishments for RNC (Max DL Bit Rate More Than 32kbit/s) Number of Successful PS Streaming RAB Establishments for RNC (Max DL Bit Rate More Than 384kbit/s) Number of Successful PS Interactive RAB Establishments for RNC (Max DL Bit Rate in [0,32]kbit/s) Number of Successful PS Interactive RAB Establishments for RNC (Max DL Bit Rate in (144,384] kbit/s) Number of Successful PS Interactive RAB Establishments for RNC (Max DL Bit Rate in (32,64]kbit/s) Number of Successful PS Interactive RAB Establishments for RNC (Max DL Bit Rate in (64,144]kbit/ s)
67174838
VS.RAB.SuccEstab PS.Str.Mor384.RN C
67174839
VS.RAB.SuccEstab PS.Int.0.32.RNC
67174842
VS.RAB.SuccEstab PS.Int. 144.384.RNC
67174840
67174841
Issue 01 (2013-05-04)
496
Counter ID 67174843
Counter Name VS.RAB.SuccEstab PS.Int.Mor384.RN C
Counter Description Number of Successful PS Interactive RAB Establishments for RNC (Max DL Bit Rate More Than 384kbit/s) Number of Successful PS Background RAB Establishments for RNC (Max DL Bit Rate More Than 384kbit/s) Number of Successful PS Streaming RAB Establishments for RNC (Max DL Bit Rate in [0,32]kbit/s) Number of Successful PS Streaming RAB Establishments for RNC (Max DL Bit Rate in (144,384] kbit/s) Number of Successful PS Streaming RAB Establishments for RNC (Max DL Bit Rate in (32,64]kbit/s) Number of Successful PS Streaming RAB Establishments for RNC (Max DL Bit Rate in (64,144]kbit/ s) Mean Number of PS RABs for RNC
67174848
VS.RAB.SuccEstab PS.Bkg.Mor384.R NC
67174834
VS.RAB.SuccEstab .PS.Str.0.32.RNC
67174837
VS.RAB.SuccEstab .PS.Str. 144.384.RNC
67174835
67174836
67199790
VS.RAB.Num.PS. Mean
Issue 01 (2013-05-04)
497
Counter ID 67196304
Counter Name VS.RAB.SuccEstab .PS.0kbps.RNC
Counter Description Number of PS RABs Established Successfully with 0 kbit/s for RNC Number of Successful RAB Establishments for PS Background Services for RNC Number of Successful RAB Establishments for PS Streaming Services for RNC Number of Successful RAB Establishments for PS Conversational Services for RNC Number of Successful RAB Establishments for PS Interactive Services for RNC
73394066
VS.RAB.SuccEstab PS.Bkg.RNC
V900R012
73394067
VS.RAB.SuccEstab PS.Str.RNC
V900R012
73394068
VS.RAB.SuccEstab PS.Conv.RNC
V900R012
73394069
VS.RAB.SuccEstab PS.Int.RNC
V900R012
Counter VS.RAB.AttEstabPS.Bkg.RNC Sub Counter VS.RAB.AttEstPSBkg0.32.RNC VS.RAB.AttEstabPS.Bkg.144.384.RNC VS.RAB.AttEstabPS.Bkg.32.64.RNC VS.RAB.AttEstabPS.Bkg.64.144.RNC VS.RAB.AttEstabPS.Bkg.Mor384.RNC VS.RAB.AttEstabPS.Conv.RNC VS.RAB.AttEstabPS.Conv.0.32.RNC VS.RAB.AttEstabPS.Conv.Mor32.RNC VS.RAB.AttEstabPS.Int.RNC VS.RAB.AttEstabPS.Int.0.32.RNC VS.RAB.AttEstabPS.Int.144.384.RNC VS.RAB.AttEstabPS.Int.32.64.RNC VS.RAB.AttEstabPS.Int.64.144.RNC VS.RAB.AttEstabPS.Int.Mor384.RNC
Counter VS.RAB.AttEstabPS.Str.RNC
Sub Counter VS.RAB.AttEstabPS.Str.0.32.RNC VS.RAB.AttEstabPS.Str.32.64.RNC VS.RAB.AttEstabPS.Str.144.384.RNC VS.RAB.AttEstabPS.Str.64.144.RNC VS.RAB.AttEstabPS.Str.Mor384
VS.RAB.SuccEstabPS.Bkg.RNC
VS.RAB.SuccEstabPS.Bkg.0.32.RNC VS.RAB.SuccEstabPS.Bkg.144.384.RNC VS.RAB.SuccEstabPS.Bkg.32.64.RNC VS.RAB.SuccEstabPS.Bkg.64.144.RNC VS.RAB.SuccEstabPS.Bkg.Mor384.RNC
VS.RAB.SuccEstabPS.Conv.RNC
VS.RAB.SuccEstabPS.Conv.0.32.RNC VS.RAB.SuccEstabPS.Conv.Mor32.RNC
VS.RAB.SuccEstabPS.Str.RNC
VS.RAB.SuccEstabPS.Str.Mor384.RNC VS.RAB.SuccEstab.PS.Str.0.32.RNC VS.RAB.SuccEstab.PS.Str.144.384.RNC VS.RAB.SuccEstab.PS.Str.32.64.RNC VS.RAB.SuccEstab.PS.Str.64.144.RNC
VS.RAB.SuccEstabPS.Int.RNC
VS.RAB.SuccEstabPS.Int.0.32.RNC VS.RAB.SuccEstabPS.Int.144.384.RNC VS.RAB.SuccEstabPS.Int.32.64.RNC VS.RAB.SuccEstabPS.Int.64.144.RNC VS.RAB.SuccEstabPS.Int.Mor384.RNC
1.10.10.1 Counters Related to the Number of PS RAB Setup Requests for Different Services Counters
Counter ID 67174788 Counter Name VS.RAB.AttEstabPS.Conv. RNC Counter Description Number of PS Conversational RAB Establishment Attempts for RNC Number of PS Background RAB Establishment Attempts for RNC
67174785
VS.RAB.AttEstabPS.Bkg.R NC
Issue 01 (2013-05-04)
499
Counter ID 67174787
Counter Name VS.RAB.AttEstabPS.Int.RN C VS.RAB.AttEstabPS.Str.RN C
Counter Description Number of PS Interactive RAB Establishment Attempts for RNC Number of PS Streaming RAB Establishment Attempts for RNC
67174786
Description
These measurement items take statistics of the number of PS RABs requested to establish in the RNC according to different types of services.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives from the SGSN a RAB ASSIGNMENT REQUEST message about the PS domain, the RNC measures these items according to different types of services. Figure 1-223 Successful RAB setup procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabPS.Conv. RNC VS.RAB.AttEstabPS.Bkg.R NC VS.RAB.AttEstabPS.Int.RN C VS.RAB.AttEstabPS.Str.RN C Feature ID WRFD-010501 WRFD-010504 WRFD-010503 WRFD-010502 Feature Name Conversational QoS Class Background QoS Class Interactive QoS Class Streaming QoS Class
1.10.10.2 Signaling Delay of PS RAB Setup Counters

Counter ID 67174812 Counter Name VS.RAB.EstabPS.CellFAC H.MaxTime VS.RAB.EstabPS.CellFAC H.MeanTime VS.RAB.EstabPS.CellDCH. MaxTime VS.RAB.EstabPS.CellDCH. MeanTime Counter Description Maximum Duration of PS RAB Establishments Mapped on CCH for RNC Mean Duration of PS RAB Establishments Mapped on CCH for RNC Maximum Duration of PS RAB Establishments Mapped on DCH for RNC Mean Duration of PS RAB Establishments Mapped on DCH for RNC
67199679
67174809
67199427
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67174810 Counter Name VS.RAB.EstabPS.CellDCH. Cum Counter Description Cumulative Duration of PS RAB Establishments Mapped on DCH for RNC
501
Issue 01 (2013-05-04)
Counter ID 67174811
Counter Name VS.RAB.EstabPS.CellDCH. Sample
Counter Description Number of Samples Recorded for Duration of PS RAB Establishments Mapped on DCH for RNC Cumulative Duration of PS RAB Establishments Mapped on CCH for RNC Number of Samples of Duration of PS RAB Establishments Mapped on CCH for RNC
67174813
VS.RAB.EstabPS.CellFAC H.Cum VS.RAB.EstabPS.CellFAC H.Sample
67174814
Description
These measurement items take statistics of the signaling delay of PS RAB setup from different angles.
Measurement point
SGSN a RAB ASSIGNMENT REQUEST message for establishing PS RABs. 2)At point B, the RNC records the time (T2) when it receives a RADIO BEARER SETUP COMPLETE message and sends a RAB ASSIGNMENT RESPONSE message to the SGSN. Suppose delta T represents the signaling delay of this PS RAB setup. Then, delta T=T2-T1. Through delta T of each PS RAB setup in a measurement period, you can obtain the values of previous measurement items. Figure 1-224 Flow chart of successful RAB setup
Issue 01 (2013-05-04)
502
Formula
VS.RAB.EstabPS.CellFACH.MeanTime = [VS.RAB.EstabPS.CellFACH.Cum]/ [VS.RAB.EstabPS.CellFACH.Sample] VS.RAB.EstabPS.CellDCH.MeanTime = [VS.RAB.EstabPS.CellDCH.Cum]/ [VS.RAB.EstabPS.CellDCH.Sample]
Unit
ms
Related Features
Counter Name VS.RAB.EstabPS.CellFAC H.MaxTime Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.EstabPS.CellFAC H.MeanTime
WRFD-010510
VS.RAB.EstabPS.CellDCH. MaxTime
WRFD-010510
VS.RAB.EstabPS.CellDCH. MeanTime
WRFD-010510
1.10.10.3 Counters Related to the Number of PS RAB Setup Requests for Different Maximum Downlink Bit rates Counters
Counter ID 67174815 Counter Name VS.RAB.AttEstabPS.Conv. 0.32.RNC Counter Description Number of PS Conversational RAB Establishment Attempts for RNC (Max DL Bit Rate in [0,32]kbit/s)
503
Issue 01 (2013-05-04)
Counter ID 67174827
Counter Name VS.RAB.AttEstPSBkg0.32. RNC
Counter Description Number of PS Background RAB Establishment Attempts for RNC (Max DL Bit Rate in [0,32]kbit/s) Number of PS Background RAB Establishment Attempts for RNC (Max DL Bit Rate in (144,384]kbit/s) Number of PS Background RAB Establishment Attempts for RNC (Max DL Bit Rate in (32,64]kbit/s) Number of PS Background RAB Establishment Attempts for RNC (Max DL Bit Rate in (64,144]kbit/s) Number of PS Background RAB Establishment Attempts for RNC (Max DL Bit Rate More Than 384kbit/ s) Number of PS Conversational RAB Establishment Attempts for RNC (Max DL Bit Rate More Than 32kbit/s) Number of PS Interactive RAB Establishment Attempts for RNC (Max DL Bit Rate in [0,32]kbit/s) Number of PS Interactive RAB Establishment Attempts for RNC (Max DL Bit Rate in (144,384]kbit/s) Number of PS Interactive RAB Establishment Attempts for RNC (Max DL Bit Rate in (32,64]kbit/s) Number of PS Interactive RAB Establishment Attempts for RNC (Max DL Bit Rate in (64,144]kbit/s)
67174830
VS.RAB.AttEstabPS.Bkg. 144.384.RNC
67174828
67174829
67174831
VS.RAB.AttEstabPS.Bkg.M or384.RNC
67174816
VS.RAB.AttEstabPS.Conv. Mor32.RNC
67174822
VS.RAB.AttEstabPS.Int. 0.32.RNC
67174825
67174823
67174824
Issue 01 (2013-05-04)
504
Counter ID 67174826
Counter Name VS.RAB.AttEstabPS.Int.Mo r384.RNC
Counter Description Number of PS Interactive RAB Establishment Attempts for RNC (Max DL Bit Rate More Than 384kbit/ s) Number of PS Streaming RAB Establishment Attempts for RNC (Max DL Bit Rate in [0,32]kbit/s) Number of PS Streaming RAB Establishment Attempts for RNC (Max DL Bit Rate in (32,64]kbit/s) Number of PS Streaming RAB Establishment Attempts for RNC (Max DL Bit Rate in (144,384]kbit/s) Number of PS Streaming RAB Establishment Attempts for RNC (Max DL Bit Rate in (64,144]kbit/s) Number of PS Streaming RAB Establishment Attempts for RNC (Max DL Bit Rate More Than 384kbit/ s)
67174817
VS.RAB.AttEstabPS.Str. 0.32.RNC
67174818
67174820
67174819
67174821
VS.RAB.AttEstabPS.Str.Mo r384
Description
These measurement items take statistics of the number of PS RABs requested to establish at different maximum downlink bit rates in the RNC according to different types of services.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives from the SGSN a RAB ASSIGNMENT REQUEST message about the PS domain, the RNC measures these items according to different types of services.
Issue 01 (2013-05-04)
505
Figure 1-225 Successful RAB setup procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabPS.Conv. 0.32.RNC VS.RAB.AttEstPSBkg0.32. RNC VS.RAB.AttEstabPS.Bkg. 144.384.RNC VS.RAB.AttEstabPS.Bkg. 32.64.RNC VS.RAB.AttEstabPS.Bkg. 64.144.RNC VS.RAB.AttEstabPS.Bkg.M or384.RNC
Issue 01 (2013-05-04)
Feature ID WRFD-010501 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504
Feature Name Conversational QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class
506
Counter Name VS.RAB.AttEstabPS.Conv. Mor32.RNC VS.RAB.AttEstabPS.Int. 0.32.RNC VS.RAB.AttEstabPS.Int. 144.384.RNC VS.RAB.AttEstabPS.Int. 32.64.RNC VS.RAB.AttEstabPS.Int. 64.144.RNC VS.RAB.AttEstabPS.Int.Mo r384.RNC VS.RAB.AttEstabPS.Str. 0.32.RNC VS.RAB.AttEstabPS.Str. 32.64.RNC VS.RAB.AttEstabPS.Str. 144.384.RNC VS.RAB.AttEstabPS.Str. 64.144.RNC VS.RAB.AttEstabPS.Str.Mo r384
Feature ID WRFD-010501 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502
Feature Name Conversational QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class
1.10.10.4 Counters Related to the Number of Successful PS RAB Setups for Different Maximum Downlink Bit Rates Counters
Counter ID 67174832 Counter Name VS.RAB.SuccEstabPS.Conv .0.32.RNC Counter Description Number of Successful PS Conversational RAB Establishments for RNC (Max DL Bit Rate in [0,32] kbit/s) Number of Successful PS Background RAB Establishments for RNC (Max DL Bit Rate in [0,32] kbit/s)
507
67174844
VS.RAB.SuccEstabPS.Bkg. 0.32.RNC
Issue 01 (2013-05-04)
Counter ID 67174847
Counter Name VS.RAB.SuccEstabPS.Bkg. 144.384.RNC
Counter Description Number of Successful PS Background RAB Establishments for RNC (Max DL Bit Rate in (144,384]kbit/s) Number of Successful PS Background RAB Establishments for RNC (Max DL Bit Rate in (32,64] kbit/s) Number of Successful PS Background RAB Establishments for RNC (Max DL Bit Rate in (64,144] kbit/s) Number of Successful PS Conversational RAB Establishments for RNC (Max DL Bit Rate More Than 32kbit/s) Number of Successful PS Streaming RAB Establishments for RNC (Max DL Bit Rate More Than 384kbit/s) Number of Successful PS Interactive RAB Establishments for RNC (Max DL Bit Rate in [0,32] kbit/s) Number of Successful PS Interactive RAB Establishments for RNC (Max DL Bit Rate in (144,384]kbit/s) Number of Successful PS Interactive RAB Establishments for RNC (Max DL Bit Rate in (32,64] kbit/s) Number of Successful PS Interactive RAB Establishments for RNC (Max DL Bit Rate in (64,144] kbit/s)
67174845
67174846
67174833
VS.RAB.SuccEstabPS.Conv .Mor32.RNC
67174838
VS.RAB.SuccEstabPS.Str. Mor384.RNC
67174839
VS.RAB.SuccEstabPS.Int. 0.32.RNC
67174842
67174840
67174841
Issue 01 (2013-05-04)
508
Counter ID 67174843
Counter Name VS.RAB.SuccEstabPS.Int. Mor384.RNC
Counter Description Number of Successful PS Interactive RAB Establishments for RNC (Max DL Bit Rate More Than 384kbit/s) Number of Successful PS Background RAB Establishments for RNC (Max DL Bit Rate More Than 384kbit/s) Number of Successful PS Streaming RAB Establishments for RNC (Max DL Bit Rate in [0,32] kbit/s) Number of Successful PS Streaming RAB Establishments for RNC (Max DL Bit Rate in (144,384]kbit/s) Number of Successful PS Streaming RAB Establishments for RNC (Max DL Bit Rate in (32,64] kbit/s) Number of Successful PS Streaming RAB Establishments for RNC (Max DL Bit Rate in (64,144] kbit/s)
67174848
VS.RAB.SuccEstabPS.Bkg. Mor384.RNC
67174834
VS.RAB.SuccEstab.PS.Str. 0.32.RNC
67174837
67174835
67174836
Description
These counters provide the number of times that the PS RAB is set up successfully for different maximum downlink bit rates.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from an UE a RADIO BEARER SETUP COMPLETE message about the PS domain, the RNC measures these items according to types of services and maximum downlink bit rates.
Issue 01 (2013-05-04)
509
Figure 1-226 Successful RAB setup procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstabPS.Conv .0.32.RNC VS.RAB.SuccEstabPS.Bkg. 0.32.RNC VS.RAB.SuccEstabPS.Bkg. 144.384.RNC VS.RAB.SuccEstabPS.Bkg. 32.64.RNC VS.RAB.SuccEstabPS.Bkg. 64.144.RNC VS.RAB.SuccEstabPS.Conv .Mor32.RNC
Issue 01 (2013-05-04)
Feature Name Conversational QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Conversational QoS Class
510
Counter Name VS.RAB.SuccEstabPS.Str. Mor384.RNC VS.RAB.SuccEstabPS.Int. 0.32.RNC VS.RAB.SuccEstabPS.Int. 144.384.RNC VS.RAB.SuccEstabPS.Int. 32.64.RNC VS.RAB.SuccEstabPS.Int. 64.144.RNC VS.RAB.SuccEstabPS.Int. Mor384.RNC VS.RAB.SuccEstabPS.Bkg. Mor384.RNC VS.RAB.SuccEstab.PS.Str. 0.32.RNC VS.RAB.SuccEstab.PS.Str. 144.384.RNC VS.RAB.SuccEstab.PS.Str. 32.64.RNC VS.RAB.SuccEstab.PS.Str. 64.144.RNC
Feature Name Streaming QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Background QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class
1.10.10.5 Mean Number of PS RABs Counters

Counter ID 67199790 Counter Name VS.RAB.Num.PS.Mean Counter Description Mean Number of PS RABs for RNC
Description
This counter provides the average number of PS RABs in the RNC within a measurement period.
Issue 01 (2013-05-04)
511
Measurement point
The RNC periodically samples (sampling periodicity is 5 seconds) the number of PS RABs. At the end of the measurement period, the RNC divides the total number of PS RABs by the number of samples to obtain the average number of PS RABs.
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.Num.PS.Mean Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.10.6 Times of PS RAB established successfully with 0kbps for RNC Counters
Counter ID 67196304 Counter Name VS.RAB.SuccEstab.PS. 0kbps.RNC Counter Description Number of PS RABs Established Successfully with 0 kbit/s for RNC
Description
This counter provides the number of times that an UE access the network successfully through the 0 Kbit/s RAB in the RNC during the procedures of RAB establishment, RAB modification, Cell update, relocation (UE involved) and hard handover.
Measurement point
The measurement is triggered at point A as shown in the following figure 1. During a RAB setup procedure, when the RNC receives a RADIO BEARER SETUP COMPLETE message from UE, it measures this counter in the RNC if the rate of the RAB is 0 Kbit/s.
Issue 01 (2013-05-04)
512
The measurement is triggered at point A as shown in the following figure 2. During a RAB modification procedure, when the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from UE, it measures this counter in the RNC if the rate of the RAB is 0 Kbit/s. Figure 1-228 RAB modification procedure
The measurement is triggered at point A as shown in the following figure 3. During a P2D procedure, when the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from UE, it measures this counter in the RNC if the rate of the RAB is 0 Kbit/s.
Issue 01 (2013-05-04)
513
Figure 1-229 P2D procedure
The measurement is triggered at point A as shown in the following figure 4. During a relocation (UE involved) procedure, when the RNC sends a RELOCATION COMPLETE message to CN, it measures this counter in the RNC if the rate of the RAB is 0 Kbit/s. Figure 1-230 relocation (UE involved) procedure
The measurement is triggered at point A as shown in the following figure 5. During a hard handover procedure, when the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from UE, it measures this counter in the RNC if the rate of the RAB is 0 Kbit/s.
Issue 01 (2013-05-04)
514
Figure 1-231 hard handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstab.PS. 0kbps.RNC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.10.7 Number of Successful RAB Establishments for PS Services
Issue 01 (2013-05-04)
515
Counters
Counter ID 73394066 Counter Name VS.RAB.SuccEstabPS.Bkg. RNC Counter Description Number of Successful RAB Establishments for PS Background Services for RNC Number of Successful RAB Establishments for PS Streaming Services for RNC Number of Successful RAB Establishments for PS Conversational Services for RNC Number of Successful RAB Establishments for PS Interactive Services for RNC
73394067
VS.RAB.SuccEstabPS.Str.R NC VS.RAB.SuccEstabPS.Conv .RNC
73394068
73394069
VS.RAB.SuccEstabPS.Int.R NC
Description
These counters provide the number of RAB establishments for different PS services in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends to the SGSN a RAB ASSIGNMENT RESPONSE message after receiving a RADIO BEARER SETUP COMPLETE message from the UE, the corresponding counter is measured according to the service type of the RAB.
Issue 01 (2013-05-04)
516
Figure 1-232 PS RAB setup procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstabPS.Bkg. RNC VS.RAB.SuccEstabPS.Str.R NC VS.RAB.SuccEstabPS.Conv .RNC VS.RAB.SuccEstabPS.Int.R NC Feature ID WRFD-010504 WRFD-010502 WRFD-010501 WRFD-010503 Feature Name Background QoS Class Streaming QoS Class Conversational QoS Class Interactive QoS Class
Issue 01 (2013-05-04)
517
1.10.11 Measurement of CS RAB assignment modification per RNC (RAB.ModCs.RNC)

Overview
If the parameters, such as QoS, of a CS service are changed after the RAB is set up, the CN sends to the RNC a RAB ASSIGNMENT REQUEST message. After receiving this message, the RNC initiates the RAB modification procedure. If the RAB modification succeeds, the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message indicating that the RAB modification succeeds. If the RAB modification fails, the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message indicating that the RAB modification fails. For details, see 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Counter ID 67174725 Counter Name VS.RAB.AttModC S.Conv.RNC Counter Description Number of RAB Modification Requests for CS Conversational Services for RNC Number of RAB Modification Requests for CS Streaming Services for RNC Number of Successful RAB Modifications for CS Streaming Services for RNC Number of VP Services Fallen Back to AMR Services for RNC Number of Successful RAB Modifications for CS Conversational Services for RNC Original Release Earlier than V900R011
67174726
VS.RAB.AttModC S.Str.RNC
67174728
VS.RAB.SuccMod CS.Str.RNC
67203800
VS.RAB.ModReqC S.VP.Fallback.RN C VS.RAB.SuccMod CS.Conv.RNC
67174727
None
1.10.11.1 Number of CS RAB Modification Requests Counters

Counter ID 67174725 Counter Name VS.RAB.AttModCS.Conv.R NC Counter Description Number of RAB Modification Requests for CS Conversational Services for RNC Number of RAB Modification Requests for CS Streaming Services for RNC
67174726
VS.RAB.AttModCS.Str.RN C
Description
These counters provide the number of RAB modification requests for CS services in the RNC based on the service type.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message, it measures the corresponding counter based on the service type only if the RAB is for CS services. Figure 1-233 RAB modification procedure
Issue 01 (2013-05-04)
519
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttModCS.Conv.R NC VS.RAB.AttModCS.Str.RN C Feature ID WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class
1.10.11.2 Number of VP Services Fallen Back to AMR Services Counters

Counter ID 67203800 Counter Name VS.RAB.ModReqCS.VP.Fa llback.RNC Counter Description Number of VP Services Fallen Back to AMR Services for RNC
Description
This counter provides the number of times that the RNC triggers the fallback of the VP service to the AMR service.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends to the CN a RAB MODIFICATION REQUEST message to request that the VP services fall back to AMR services.
Issue 01 (2013-05-04)
520
Figure 1-234 RAB modification procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.ModReqCS.VP.Fa llback.RNC Feature ID WRFD-020303 WRFD-020305 WRFD-020306 WRFD-021200 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load HCS (Hierarchical Cell Structure)
1.10.11.3 Number of Successful CS RAB Modifications
Issue 01 (2013-05-04)
521
Counters
Counter ID 67174727 Counter Name VS.RAB.SuccModCS.Conv. RNC Counter Description Number of Successful RAB Modifications for CS Conversational Services for RNC Number of Successful RAB Modifications for CS Streaming Services for RNC
67174728
VS.RAB.SuccModCS.Str.R NC
Description
These counters provide the number of times that the RAB is modified successfully for CS services in the RNC based on the service type.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message after receiving from the UE a RADIO BEARER RECONFIGURATION COMPLETE message, it measures this counter based on the service type only if the RAB is for CS services. Figure 1-235 RAB modification procedure
Issue 01 (2013-05-04)
522
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccModCS.Conv. RNC VS.RAB.SuccModCS.Str.R NC Feature ID WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class
1.10.12 Measurement of PS RAB assignment modification per RNC (RAB.ModPs.RNC)

Overview
If the parameters, such as QoS, of a PS service are changed after the RAB is set up, the CN sends to the RNC a RAB ASSIGNMENT REQUEST message. If the RNC determines that the RAB modification is needed (a RAB exists before the RAB ASSIGNMENT REQUEST message is received) after receiving the message, it sends to the UE a RADIO BEARER RECONFIGURATION message. If the RAB modification succeeds, the UE sends to the RNC a RADIO BEARER RECONFIGURATION COMPLETE message. The RNC then sends to the CN a RAB ASSIGNMENT RESPONSE message indicating that the RAB modification succeeds. For details, see 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Counter ID 67174793 Counter Name RAB.AttModPS.Co nv.RNC Counter Description Number of RAB Modification Requests for PS Conversational Services for RNC Number of RAB Modification Requests for PS Streaming Services for RNC Original Release Earlier than V900R011
67174794
RAB.AttModPS.St r.RNC
Issue 01 (2013-05-04)
523
Counter ID 67174795
Counter Name RAB.AttModPS.In t.RNC
Counter Description Number of RAB Modification Requests for PS Interactive Services for RNC Number of RAB Modification Requests for PS Background Services for RNC Number of Successful RAB Modifications for PS Streaming Services for RNC Number of Successful RAB Modifications for PS Conversational Services for RNC Number of Successful RAB Modifications for PS Interactive Services for RNC Number of Successful RAB Modifications for PS Background Services for RNC
67174796
RAB.AttModPS.Bg rd.RNC
67174798
VS.RAB.SuccMod PS.Str.RNC
67174797
VS.RAB.SuccMod PS.Conv.RNC
67174799
VS.RAB.SuccMod PS.Int.RNC
67174800
VS.RAB.SuccMod PS.Bkg.RNC
None
1.10.12.1 Number of PS RAB Modification Requests
Issue 01 (2013-05-04)
524
Counters
Counter ID 67174793 Counter Name RAB.AttModPS.Conv.RNC Counter Description Number of RAB Modification Requests for PS Conversational Services for RNC Number of RAB Modification Requests for PS Streaming Services for RNC Number of RAB Modification Requests for PS Interactive Services for RNC Number of RAB Modification Requests for PS Background Services for RNC
67174794
RAB.AttModPS.Str.RNC
67174795
RAB.AttModPS.Int.RNC
67174796
RAB.AttModPS.Bgrd.RNC
Description
These counters provide the number of RAB modification requests for PS services in the RNC based on the service type.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message, it measures the corresponding counter based on the service type if the RAB is for PS services.
Issue 01 (2013-05-04)
525
Figure 1-236 PS RAB modification procedure
Formula
None
Unit
None
Related Features
Counter Name RAB.AttModPS.Conv.RNC RAB.AttModPS.Str.RNC RAB.AttModPS.Int.RNC RAB.AttModPS.Bgrd.RNC Feature ID WRFD-010501 WRFD-010502 WRFD-010503 WRFD-010504 Feature Name Conversational QoS Class Streaming QoS Class Interactive QoS Class Background QoS Class
1.10.12.2 Number of Successful PS RAB Modifications
Issue 01 (2013-05-04)
526
Counters
Counter ID 67174797 Counter Name VS.RAB.SuccModPS.Conv. RNC Counter Description Number of Successful RAB Modifications for PS Conversational Services for RNC Number of Successful RAB Modifications for PS Streaming Services for RNC Number of Successful RAB Modifications for PS Interactive Services for RNC Number of Successful RAB Modifications for PS Background Services for RNC
67174798
VS.RAB.SuccModPS.Str.R NC VS.RAB.SuccModPS.Int.R NC VS.RAB.SuccModPS.Bkg. RNC
67174799
67174800
Description
These counters provide the number of times that the RAB is modified successfully for PS services in the RNC based on the service type.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message after receiving from the UE a RADIO BEARER RECONFIGURATION COMPLETE message, it measures this counter based on the service type if the RAB is for PS services.
Issue 01 (2013-05-04)
527
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccModPS.Conv. RNC VS.RAB.SuccModPS.Str.R NC VS.RAB.SuccModPS.Int.R NC VS.RAB.SuccModPS.Bkg. RNC Feature ID WRFD-010501 WRFD-010502 WRFD-010503 WRFD-010504 Feature Name Conversational QoS Class Streaming QoS Class Interactive QoS Class Background QoS Class
Issue 01 (2013-05-04)
528
1.10.13 Measurement of multi-RAB service per RNC (RAB.MultiRab.RNC)

Overview
Multi-RAB measurement includes: Measurement of the number of UEs with multiple RABs. Multiple RABs can be multiple CS domain RABs, multiple PS domain RABs or the combinations of CS domain and PS domain RABs. The combinations of RABs can be denoted by abbreviations. For example: 1CS+1PS indicates that there are concurrently one CS domain RAB and one PS domain RAB. 1CS+2PS indicates that there are concurrently one CS domain RAB and two PS domain RABs. 2CS indicates that there are concurrently two CS domain RABs.
Counters
Counter ID 67199688 67199684 Counter Name VS.MultRAB.0CS. 2PS.RNC VS.MultRAB. 1CS1PS.RNC VS.MultRAB. 1CS2PS.RNC VS.MultRAB. 0CS3PS.RNC VS.MultRAB. 1CS3PS.RNC VS.MultRAB. 0CS4PS.RNC Counter Description Number of UEs with 2PS RABs for RNC Number of UEs with 1CS+1PS RABs for RNC Number of UEs with 1CS+2PS RABs for RNC Number of UEs with 0CS+3PS RABs for RNC Number of UEs with 1CS+3PS RABs for RNC Number of UEs with 0CS+4PS RABs for RNC Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67199685
67199690
67199695
67204757
None
1.10.13.1 Mean Number of UEs with Multi-RABs in RNC

Counters
Counter ID 67199688 67199684 67199685 67199690 67199695 67204757 Counter Name VS.MultRAB.0CS. 2PS.RNC VS.MultRAB.1CS1PS.RNC VS.MultRAB.1CS2PS.RNC VS.MultRAB.0CS3PS.RNC VS.MultRAB.1CS3PS.RNC VS.MultRAB.0CS4PS.RNC Counter Description Number of UEs with 2PS RABs for RNC Number of UEs with 1CS +1PS RABs for RNC Number of UEs with 1CS +2PS RABs for RNC Number of UEs with 0CS +3PS RABs for RNC Number of UEs with 1CS +3PS RABs for RNC Number of UEs with 0CS +4PS RABs for RNC
Description
This measurement item takes statistics of the average number of UEs with multi RABs in the RNC.
Measurement point
The RNC takes a sample from the number of UEs with multi RABs every five seconds. At the end of the measurement period, the RNC divides the total number of UEs with multi RABs by the number of samples to obtain the average number.
Formula
None
Unit
None
Related Features
Counter Name VS.MultRAB.0CS. 2PS.RNC VS.MultRAB.1CS1PS.RNC VS.MultRAB.1CS2PS.RNC Feature ID WRFD-01061501 WRFD-01060902 WRFD-01061502 Feature Name Combination of Two PS Services Combination of One CS Service and One PS Service Combination of One CS Service and Two PS Services
530
Issue 01 (2013-05-04)
Counter Name VS.MultRAB.0CS3PS.RNC VS.MultRAB.1CS3PS.RNC
Feature Name Combination of Three PS Services Combination of One CS Service and Three PS Services Combination of Four PS Services
VS.MultRAB.0CS4PS.RNC
WRFD-01061505
1.10.14 Measurement of RAB release per RNC (RAB.RelAbnormal.RNC)

Overview
The RAB release can be classified into the following types: 1) The RAB release initiated by the RNC. When the RNC detects that the UE has no data to transmit for a long period or the RNC is faulty (for example, the SRB resets or the AAL2 link on the Iu interface is faulty), the RNC sends to the CN a RAB RELEASE REQUEST message to release the RAB or an IU RELEASE REQUEST message to release the Iu connection. If the cause value is "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", the RAB release is considered as normal release; otherwise, the RAB release is considered as abnormal release. For details, see the middle of the figure. 2) The RAB release initiated by the CN. The RNC initiates the RAB release by sending the RAB ASSIGNMENT REQUEST message and initiates the Iu connection release by sending the IU RELEASE COMMAND message. All the RAB releases initiated by the CN are considered as normal releases. For details, see the left part of the figure. 3) The RAB release initiated by the UE. The UE initiates the RAB release by sending the SIGNALING CONNECTION RELEASE INDICATION message. According to the domain information in the message, the RNC sends an IU RELEASE REQUEST message to the CN node (SGSN or MSC) to release the Iu connection. After the Iu connection is released, the RNC initiates the RRC release if no Iu connection exists in another domain. All the RAB releases initiated by the UE are considered as normal releases. For details, see the right part of the figure. Note: If the Iu interface is reset, released services will be regarded as being normally released. The sub procedures mentioned in figure 1 are as following.
Issue 01 (2013-05-04)
531
Figure 1-238 Flow chart of Drop
Issue 01 (2013-05-04)
532
Figure 1-239 Sub flow chart of Drop
Table 2 describes the measurement points shown in Figure2. Measurement points A B C D Description VS.RAB.AbnormRel.CS.RNC VS.RAB.NormRel.CS.RNC VS.RAB.NormRel.PS.RNC VS.RAB.AbnormRel.PS.RNC
Counters
Counter ID 67174954 Counter Name VS.RAB.AbnormR el.CS.RF.RNC Counter Description Number of CS RABs Abnormally Released due to RF cause for RNC Original Release Earlier than V900R011
Issue 01 (2013-05-04)
533
Counter ID 67174955
Counter Name VS.RAB.AbnormR el.PS.RF.RNC
Counter Description Number of PS RABs Abnormally Released due to RF cause for RNC Number of CS RABs Abnormally Released for RNC Number of PS RABs Abnormally Released for RNC Number of CS RABs Normally Released for RNC Number of PS RABs Normally Released for RNC Number of CS RABs Normally Released for RNC (UE Generated Signaling Connection Release) Number of PS RABs Normally Released for RNC (UE Generated Signaling Connection Release) Number of CS RABs Abnormally Released for RNC (AMR) Number of CS RABs Abnormally Released for RNC (64kbit/s Conversational Services) Number of 64kbit/s CS RABs Normally Released for RNC Due to 64kbit/s CS Service Forbiddance in Target Cell
67174963
VS.RAB.AbnormR el.CS.RNC VS.RAB.AbnormR el.PS.RNC VS.RAB.NormRel. CS.RNC VS.RAB.NormRel. PS.RNC VS.RAB.NormRel. CS.UEGen.RNC
Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67174964
67174965
67174966
67190454
67190455
VS.RAB.NormRel. PS.UEGen.RNC
67174951
VS.RAB.AbnormR el.AMR.RNC
67174952
VS.RAB.AbnormR el.CS64.RNC
67196236
VS.RAB.NormRel. VPLimit.RNC
Issue 01 (2013-05-04)
534
Counter ID 67196305
Counter Name VS.RAB.NormRel. PS. 0kbps.Timeout.RN C
Counter Description Number of PS RABs of 0 kbit/s Released for Failed to Rate up for RNC
None
1.10.14.1 Number of Released RABs due to RF cause Counters

Counter ID 67174954 Counter Name VS.RAB.AbnormRel.CS.RF .RNC VS.RAB.AbnormRel.PS.RF .RNC Counter Description Number of CS RABs Abnormally Released due to RF cause for RNC Number of PS RABs Abnormally Released due to RF cause for RNC
67174955
Description
These measurement items provide the number of released RABs triggered by the RNC due to RF failure.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message with cause "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure" in the case of RF failure(for example:SRB reset, TRB reset, radio link synchronous failure or UU interface no reply,etc.). If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items by the CN domains.
Issue 01 (2013-05-04)
535
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message with cause "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure" in the case of RF failure(for example:SRB reset, TRB reset, radio link synchronous failure or UU interface no reply,etc.).If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items by the CN domains.
Issue 01 (2013-05-04)
536
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message with cause "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure" in the case of RF failure (for example:SRB reset, TRB reset, radio link synchronous failure or UU interface no reply,etc.).If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items by the CN domains.
Issue 01 (2013-05-04)
537
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.CS.RF .RNC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AbnormRel.PS.RF .RNC
WRFD-010510
1.10.14.2 Number of RABs Abnormally Released for RNC
Issue 01 (2013-05-04)
538
Counters
Counter ID 67174963 Counter Name VS.RAB.AbnormRel.CS.R NC VS.RAB.AbnormRel.PS.RN C Counter Description Number of CS RABs Abnormally Released for RNC Number of PS RABs Abnormally Released for RNC
67174964
Description
These counters provide the number of RABs abnormally released in the RNC according to the domain types.
Measurement point
As shown in point A of the figure, when an exception occurs, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then the corresponding counter is measured according to the domain types. Figure 1-243 RAB release procedure
As shown in point A of the figure, when an exception occurs, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE
COMMAND message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then the corresponding counter is measured according to the domain types. Figure 1-244 RAB release IU REL procedure
As shown in point A of the figure, when an exception occurs, the RNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then the corresponding counter is measured according to the domain types.
Issue 01 (2013-05-04)
540
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.CS.R NC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AbnormRel.PS.RN C
WRFD-010510
1.10.14.3 Number of Normally Released RABs
Issue 01 (2013-05-04)
541
Counters
Counter ID 67174965 67174966 67196236 Counter Name VS.RAB.NormRel.CS.RNC VS.RAB.NormRel.PS.RNC VS.RAB.NormRel.VPLimit. RNC Counter Description Number of CS RABs Normally Released for RNC Number of PS RABs Normally Released for RNC Number of 64kbit/s CS RABs Normally Released for RNC Due to 64kbit/s CS Service Forbiddance in Target Cell
Description
These measurement items take statistics of the number of normally released RABs according to different domains. The following table describes the meaning of each counter. Counter Name VS.RAB.NormRel.VPLimit.RNC Description Number of normally released CS VP RABs triggered by RNC(with cause of "Network Optimization") because VP is forbidden in target cell
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release", the RNC measures these items by the CN domains.
Issue 01 (2013-05-04)
542
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release" ,the RNC measures these items by the CN domains.
Issue 01 (2013-05-04)
543
Figure 1-247 Successful RAB release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.CS.RNC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Videophone Service Restriction
VS.RAB.NormRel.PS.RNC
WRFD-010510
VS.RAB.NormRel.VPLimit. RNC
WRFD-020130
Issue 01 (2013-05-04)
544
1.10.14.4 Number of Released RABs Triggered by RNC Due to UE Signaling Connection Release Counters
Counter ID 67190454 Counter Name VS.RAB.NormRel.CS.UEG en.RNC Counter Description Number of CS RABs Normally Released for RNC (UE Generated Signaling Connection Release) Number of PS RABs Normally Released for RNC (UE Generated Signaling Connection Release)
67190455
VS.RAB.NormRel.PS.UEG en.RNC
Description
These measurement items take statistics of the number of released RABs triggered by the RNC due to UE signaling connection release according to different domains.
Measurement point
The measurement is triggered at point A as shown in the figure. In the case of UE generated signalling connection release, the RNC sends to the CN an IU RELEASE REQUEST message (with release cause of "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items by the CN domains. Figure 1-248 Iu connection release procedure
Issue 01 (2013-05-04)
545
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.CS.UEG en.RNC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.NormRel.PS.UEG en.RNC
WRFD-010510
1.10.14.5 Number of Abnormally Released CS RABs Counters

Counter ID 67174951 Counter Name VS.RAB.AbnormRel.AMR. RNC VS.RAB.AbnormRel.CS64. RNC Counter Description Number of CS RABs Abnormally Released for RNC (AMR) Number of CS RABs Abnormally Released for RNC (64kbit/s Conversational Services)
67174952
Description
These measurement items provide the number of abnormally released CS RABs according to different types of services.The counter VS.RAB.AbnormRel.AMR.RNC includes narrowband and wideband AMR services.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB
ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items by the types of services. Figure 1-249 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items by the types of services.
Issue 01 (2013-05-04)
547
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items by the types of services. Figure 1-251 Iu connection release procedure
Issue 01 (2013-05-04)
548
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.AMR. RNC VS.RAB.AbnormRel.CS64. RNC Feature ID WRFD-010501 WRFD-010501 Feature Name Conversational QoS Class Conversational QoS Class
1.10.14.6 Times of PS RAB of 0kbps released for failing to rate up before timer expiry Counters
Counter ID 67196305 Counter Name VS.RAB.NormRel.PS. 0kbps.Timeout.RNC Counter Description Number of PS RABs of 0 kbit/s Released for Failed to Rate up for RNC
Description
This measurement item provides the times of releasing RAB of 0kbps for failing to rate up before timer expiry in RNC level.
Measurement point
The measurement is triggered when a PS RAB of 0kbps released by RNC, due to failure of rating up before the timer of kbit/s expires. The measurement is triggered at point A in the figure. When the RNC initiates an Iu connection release procedure with the cause "Network Optimization" and PS services are released due to the failure of 0 kbit/s PS RAB rating up before timer expiry, it measures the number of times of releasing RAB of 0 kbit/s for failing to rate up before timer expiry in RNC level.
Issue 01 (2013-05-04)
549
The measurement is triggered at point B in the figure. When the RNC initiates a RAB assignment release procedure with the cause "Network Optimization" and PS services are released due to the failure of 0 kbit/s PS RAB rating up before timer expiry, it measures the number of times of releasing RAB of 0 kbit/s for failing to rate up before timer expiry in RNC level. Figure 1-253 RAB release procedure (successful operation)
Issue 01 (2013-05-04)
550
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS. 0kbps.Timeout.RNC Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.10.15 Measurement of CS RAB release per RNC(RAB.RelCs.RNC)

Overview
If a CS RAB needs to be released, the CN sends to the RNC a RAB ASSIGNMENT REQUEST message, indicating the RNC to release the RAB. After receiving this message, the RNC sends to the CN a RADIO BEARER RELEASE message. If the radio bearer (RB) is released successfully, the UE sends to the RNC a RADIO BEARER RELEASE COMPLETE. Then the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message, indicating that the RAB is released. For details, see 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Counter ID 67192101 Counter Name VS.RAB.AttRelCS. RNC VS.RAB.SuccRelC S.RNC Counter Description Number of CS RAB Release Attempts for RNC Number of Successful CS RAB Releases for RNC Original Release V900R012
67192102
None
1.10.15.1 Number of CS RABs Requested to Release

Counters
Counter ID 67192101 Counter Name VS.RAB.AttRelCS.RNC Counter Description Number of CS RAB Release Attempts for RNC
Description
This measurement item provides the total number of CS RABs requested to release in the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the CN a RAB ASSIGNMENT REQUEST message indicating that a CS RAB needs to be released. In this case, this counter is measured in the best cell that the UE camps on. Figure 1-254 RAB assignment release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttRelCS.RNC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.15.2 Number of Successful CS RAB Releases Counters

Counter ID 67192102 Counter Name VS.RAB.SuccRelCS.RNC Counter Description Number of Successful CS RAB Releases for RNC
Description
This counter provides the number of times that a RAB for CS services is released successfully in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message indicating that the RAB release succeeds and the RAB is for CS services.
Issue 01 (2013-05-04)
553
Figure 1-255 RAB assignment release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccRelCS.RNC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.16 Measurement of PS RAB release per RNC(RAB.RelPs.RNC)

Overview
If a PS RAB needs to be released, the CN sends to the RNC a RAB ASSIGNMENT REQUEST message, indicating the RNC to release the RAB. After receiving this message, the RNC sends
to the CN a RADIO BEARER RELEASE message. If the radio bearer (RB) is released successfully, the UE sends to the RNC a RADIO BEARER RELEASE COMPLETE. Then the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message, indicating that the RAB is released. For details, see 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Counter ID 67192104 Counter Name VS.RAB.SuccRelP S.RNC VS.RAB.AttRelPS. RNC Counter Description Number of Successful PS RAB Releases for RNC Number of PS RAB Release Attempts for RNC Original Release Earlier than V900R011 V900R012
73394107
None
1.10.16.1 Number of Successful PS RAB Releases Counters

Counter ID 67192104 Counter Name VS.RAB.SuccRelPS.RNC Counter Description Number of Successful PS RAB Releases for RNC
Description
This counter provides the number of times that a RAB for PS services is released successfully in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message indicating that the RAB release succeeds and the RAB is for PS services.
Issue 01 (2013-05-04)
555
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccRelPS.RNC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.16.2 Number of PS RABs Requested to Release
Issue 01 (2013-05-04)
556
Counters
Counter ID 73394107 Counter Name VS.RAB.AttRelPS.RNC Counter Description Number of PS RAB Release Attempts for RNC
Description
This measurement item provides the total number of PS RABs requested to release in the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC measures the item, if the RNC finds that some RABs need to be released after receiving a RAB ASSIGNMENT REQUEST message about the PS domain from the SGSN. Figure 1-257 RAB release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttRelPS.RNC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.17 Measurement of RB Procedure per RNC(RB.RNC)

Overview
The CS domain has four types of services, namely, conversational service, streaming service, interactive service, and background service. At present, it only supports the first two services. The PS domain carried on the DCH also has the same four types of services, among which the conversational service supports eight variable rates, the streaming service supports eight variable rates, the interactive service supports eight variable rates, and the background service supports eight variable-rates. UTRAN can provide different rates according to the resource status and requirement type. If the RRC state of service switches from CELL_DCH to other states, the measurement item decreases by one. If the RRC state of service switches from other states to CELL_DCH, the measurement item increases by one. If the RRC state of service switches from CELL_DCH to CELL_DCH and the bandwidth is adjusted, the old measurement item decreases by one and the new one increases by one.
Counters
Counter ID 67202577 Counter Name VS.RB.PS.Conv.D L.8.RNC Counter Description Average Number of RBs for PS R99 Conversational Services with DL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with DL Rate of 16 Kbit/s for RNC Original Release Earlier than V900R011
67202580
VS.RB.PS.Conv.D L.16.RNC
Issue 01 (2013-05-04)
558
Counter ID 67202583
Counter Name VS.RB.PS.Conv.D L.32.RNC
Counter Description Average Number of RBs for PS R99 Conversational Services with DL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with DL Rate of 64 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 64 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with DL Rate of 144 Kbit/s for RNC
67202586
67202589
VS.RB.PS.Conv.U L.8.RNC
67202592
67202595
67202598
67202604
VS.RB.PS.Str.DL. 144.RNC
Issue 01 (2013-05-04)
559
Counter ID 67202607
Counter Name VS.RB.PS.Str.DL. 128.RNC
Counter Description Average Number of RBs for PS R99 Streaming Services with DL Rate of 128 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with DL Rate of 64 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with DL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with DL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with DL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 144 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 128 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 64 Kbit/s for RNC
67202610
67202613
67202616
67202619
67202625
VS.RB.PS.Str.UL. 144.RNC
67202628
67202631
Issue 01 (2013-05-04)
560
Counter ID 67202634
Counter Name VS.RB.PS.Str.UL. 32.RNC
Counter Description Average Number of RBs for PS R99 Streaming Services with UL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 384 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 256 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 144 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 128 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 64 Kbit/s for RNC
67202637
67202640
67202643
VS.RB.PS.Int.DL. 384.RNC
67202646
67202649
67202652
67202655
Issue 01 (2013-05-04)
561
Counter ID 67202658
Counter Name VS.RB.PS.Int.DL. 32.RNC
Counter Description Average Number of RBs for PS R99 Interactive Services with DL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 384 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 256 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 144 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 128 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 64 Kbit/s for RNC
67202661
67202664
67202667
VS.RB.PS.Int.UL. 384.RNC
67202670
67202673
67202676
67202679
Issue 01 (2013-05-04)
562
Counter ID 67202682
Counter Name VS.RB.PS.Int.UL. 32.RNC
Counter Description Average Number of RBs for PS R99 Interactive Services with UL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 384 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 256 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 144 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 128 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 64 Kbit/s for RNC
67202685
67202688
67202691
VS.RB.PS.Bkg.DL. 384.RNC
67202694
67202697
67202700
67202703
Issue 01 (2013-05-04)
563
Counter ID 67202706
Counter Name VS.RB.PS.Bkg.DL. 32.RNC
Counter Description Average Number of RBs for PS R99 Background Services with DL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 384 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 256 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 144 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 128 Kbit/s for RNC
67202709
67202712
67202715
VS.RB.PS.Bkg.UL. 384.RNC
67202718
67202721
67202724
Issue 01 (2013-05-04)
564
Counter ID 67202727
Counter Name VS.RB.PS.Bkg.UL. 64.RNC
Counter Description Average Number of RBs for PS R99 Background Services with UL Rate of 64 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 8 Kbit/s for RNC Average Number of RBs for CS Streaming Services with DL Rate of 57.6 Kbit/s for RNC Average Number of RBs for CS Streaming Services with UL Rate of 57.6 Kbit/s for RNC Average Number of RBs for CS Conversational Services with DL Rate of 64 Kbit/s for RNC
67202730
67202733
67202736
67202739
VS.RB.CS.Str.DL. 57.6.RNC
67202748
VS.RB.CS.Str.UL. 57.6.RNC
67202766
VS.RB.CS.Conv.D L.64.RNC
Issue 01 (2013-05-04)
565
Counter ID 67202778
Counter Name VS.RB.CS.Conv.U L.64.RNC
Counter Description Average Number of RBs for CS Conversational Services with UL Rate of 64 Kbit/s for RNC Number of DCH-toHSDPA Directed Retry Attempts for RNC Number of Successful DCH-toHSDPA Directed Retry for RNC Average Number of RBs for PS R99 Streaming Services with DL Rate of 256 Kbit/s or 384 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 256 Kbit/s or 384 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with DL Rate of 38.8 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with DL Rate of 39.2 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with DL Rate of 40 Kbit/s for RNC
67192444
VS.DRD.RB.D2H. Att.RNC
67192445
VS.DRD.RB.D2H.S ucc.RNC
67202601
VS.RB.PS.Str.DL. 256.384.RNC
67202622
VS.RB.PS.Str.UL. 256.384.RNC
67204798
VS.RB.PS.Conv.D L.38.8.RNC
67204799
VS.RB.PS.Conv.D L.39.2.RNC
67204800
Issue 01 (2013-05-04)
566
Counter ID 67204801
Counter Name VS.RB.PS.Conv.D L.42.8.RNC
Counter Description Average Number of RBs for PS R99 Conversational Services with DL Rate of 42.8 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 38.8 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 39.2 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 40 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 42.8 Kbit/s for RNC
67204802
VS.RB.PS.Conv.U L.38.8.RNC
67204803
67204804
67204805
None
1.10.17.1 Counters Related to the Average Number of RBs for PS R99 Conversational Services
Issue 01 (2013-05-04)
567
Counters
Counter ID 67202577 Counter Name VS.RB.PS.Conv.DL.8.RNC Counter Description Average Number of RBs for PS R99 Conversational Services with DL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with DL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with DL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with DL Rate of 64 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 64 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with DL Rate of 38.8 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with DL Rate of 39.2 Kbit/s for RNC
67202580
VS.RB.PS.Conv.DL. 16.RNC
67202583
67202586
67202589
VS.RB.PS.Conv.UL.8.RNC
67202592
VS.RB.PS.Conv.UL. 16.RNC
67202595
67202598
67204798
VS.RB.PS.Conv.DL. 38.8.RNC
67204799
Issue 01 (2013-05-04)
568
Counter ID 67204800
Counter Name VS.RB.PS.Conv.DL. 40.RNC
Counter Description Average Number of RBs for PS R99 Conversational Services with DL Rate of 40 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with DL Rate of 42.8 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 38.8 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 39.2 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 40 Kbit/s for RNC Average Number of RBs for PS R99 Conversational Services with UL Rate of 42.8 Kbit/s for RNC
67204801
67204802
VS.RB.PS.Conv.UL. 38.8.RNC
67204803
67204804
67204805
Description
These counters provide the average number of RBs for PS R99 conversational services in the RNC based on different UL and DL rates.
Measurement point
The number of RBs for each type of PS R99 conversational services is sampled periodically (sampling periodicity is 5 seconds) in the RNC. At the end of the measurement period, the value of each counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.RB.PS.Conv.DL.8.RNC VS.RB.PS.Conv.DL. 16.RNC VS.RB.PS.Conv.DL. 32.RNC VS.RB.PS.Conv.DL. 64.RNC VS.RB.PS.Conv.UL.8.RNC VS.RB.PS.Conv.UL. 16.RNC VS.RB.PS.Conv.UL. 32.RNC VS.RB.PS.Conv.UL. 64.RNC VS.RB.PS.Conv.DL. 38.8.RNC VS.RB.PS.Conv.DL. 39.2.RNC VS.RB.PS.Conv.DL. 40.RNC VS.RB.PS.Conv.DL. 42.8.RNC VS.RB.PS.Conv.UL. 38.8.RNC VS.RB.PS.Conv.UL. 39.2.RNC VS.RB.PS.Conv.UL. 40.RNC VS.RB.PS.Conv.UL. 42.8.RNC Feature ID WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 Feature Name Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class
1.10.17.2 Counters Related to the Average Number of PS R99 Interactive Service RBs
Issue 01 (2013-05-04)
570
Counters
Counter ID 67202643 Counter Name VS.RB.PS.Int.DL.384.RNC Counter Description Average Number of RBs for PS R99 Interactive Services with DL Rate of 384 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 256 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 144 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 128 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 64 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with DL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 384 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 256 Kbit/s for RNC
67202646
VS.RB.PS.Int.DL.256.RNC
67202649
67202652
67202655
67202658
67202661
67202664
67202667
VS.RB.PS.Int.UL.384.RNC
67202670
Issue 01 (2013-05-04)
571
Counter ID 67202673
Counter Name VS.RB.PS.Int.UL.144.RNC
Counter Description Average Number of RBs for PS R99 Interactive Services with UL Rate of 144 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 128 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 64 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Interactive Services with UL Rate of 8 Kbit/s for RNC
67202676
67202679
67202682
67202685
67202688
Description
These counters provide the average number of RBs for PS R99 interactive services in the uplink or downlink.
Measurement point
The number of RBs for each type of PS R99 conversational services, interactive services, or background services is sampled periodically (sampling periodicity is 5 seconds) in the RNC. At the end of the measurement period, the value of each counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.RB.PS.Int.DL.384.RNC VS.RB.PS.Int.DL.256.RNC VS.RB.PS.Int.DL.144.RNC VS.RB.PS.Int.DL.128.RNC VS.RB.PS.Int.DL.64.RNC VS.RB.PS.Int.DL.32.RNC VS.RB.PS.Int.DL.16.RNC VS.RB.PS.Int.DL.8.RNC VS.RB.PS.Int.UL.384.RNC VS.RB.PS.Int.UL.256.RNC VS.RB.PS.Int.UL.144.RNC VS.RB.PS.Int.UL.128.RNC VS.RB.PS.Int.UL.64.RNC VS.RB.PS.Int.UL.32.RNC VS.RB.PS.Int.UL.16.RNC VS.RB.PS.Int.UL.8.RNC Feature ID WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 Feature Name Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class
1.10.17.3 Counters Related to the Average Number of PS R99 Backgroud Service RBs Counters
Counter ID 67202691 Counter Name VS.RB.PS.Bkg.DL. 384.RNC Counter Description Average Number of RBs for PS R99 Background Services with DL Rate of 384 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 256 Kbit/s for RNC
67202694
Issue 01 (2013-05-04)
573
Counter ID 67202697
Counter Name VS.RB.PS.Bkg.DL. 144.RNC
Counter Description Average Number of RBs for PS R99 Background Services with DL Rate of 144 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 128 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 64 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with DL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 384 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 256 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 144 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 128 Kbit/s for RNC
67202700
67202703
VS.RB.PS.Bkg.DL.64.RNC
67202706
67202709
67202712
67202715
67202718
67202721
67202724
Issue 01 (2013-05-04)
574
Counter ID 67202727
Counter Name VS.RB.PS.Bkg.UL.64.RNC
Counter Description Average Number of RBs for PS R99 Background Services with UL Rate of 64 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Background Services with UL Rate of 8 Kbit/s for RNC
67202730
VS.RB.PS.Bkg.UL.32.RNC
67202733
67202736
Description
These counters provide the average number of RBs for PS R99 background services in the uplink or downlink.
Measurement point
The number of RBs for each type of PS R99 backgroud services is sampled periodically (sampling periodicity is 5 seconds) in the RNC. At the end of the measurement period, the value of each counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.RB.PS.Bkg.DL. 384.RNC VS.RB.PS.Bkg.DL. 256.RNC
Issue 01 (2013-05-04)
Feature Name Background QoS Class Background QoS Class
575
Counter Name VS.RB.PS.Bkg.DL. 144.RNC VS.RB.PS.Bkg.DL. 128.RNC VS.RB.PS.Bkg.DL.64.RNC VS.RB.PS.Bkg.DL.32.RNC VS.RB.PS.Bkg.DL.16.RNC VS.RB.PS.Bkg.DL.8.RNC VS.RB.PS.Bkg.UL. 384.RNC VS.RB.PS.Bkg.UL. 256.RNC VS.RB.PS.Bkg.UL. 144.RNC VS.RB.PS.Bkg.UL. 128.RNC VS.RB.PS.Bkg.UL.64.RNC VS.RB.PS.Bkg.UL.32.RNC VS.RB.PS.Bkg.UL.16.RNC VS.RB.PS.Bkg.UL.8.RNC
Feature ID WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504
Feature Name Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class
1.10.17.4 Counters Related to the Average Number of CS Streaming Service RBs Counters
Counter ID 67202739 Counter Name VS.RB.CS.Str.DL. 57.6.RNC Counter Description Average Number of RBs for CS Streaming Services with DL Rate of 57.6 Kbit/s for RNC Average Number of RBs for CS Streaming Services with UL Rate of 57.6 Kbit/s for RNC
67202748
VS.RB.CS.Str.UL. 57.6.RNC
Issue 01 (2013-05-04)
576
Description
The measurement items provide the mean number of streaming service RBs in the CS domain at different UL and DL bit rates in the RNC.
Measurement point
The RNC periodically takes a sample (sampling periodicity is 5 seconds) from the number of RBs in the CS domain at each of the UL and DL rates of the streaming service. At the end of the measurement period, the RNC divides the accumulated number of RBs at one bit rate by the number of samples to obtain the mean number of such RBs.
Formula
None
Unit
None
Related Features
Counter Name VS.RB.CS.Str.DL. 57.6.RNC VS.RB.CS.Str.UL. 57.6.RNC Feature ID WRFD-010502 WRFD-010502 Feature Name Streaming QoS Class Streaming QoS Class
1.10.17.5 Counters Related to the Average Number of CS Conversational Service RBs Counters
Counter ID 67202766 Counter Name VS.RB.CS.Conv.DL. 64.RNC Counter Description Average Number of RBs for CS Conversational Services with DL Rate of 64 Kbit/s for RNC Average Number of RBs for CS Conversational Services with UL Rate of 64 Kbit/s for RNC
67202778
VS.RB.CS.Conv.UL. 64.RNC
Issue 01 (2013-05-04)
577
Description
The measurement items provide the mean number of conversational service RBs in the CS domain at different UL and DL bit rates in the RNC.
Measurement point
The number of RBs for conversational services are sampled periodically (sampling periodicity is 5 seconds) in the RNC. At the end of the measurement period, the value of each counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.RB.CS.Conv.DL. 64.RNC VS.RB.CS.Conv.UL. 64.RNC Feature ID WRFD-010501 WRFD-010501 Feature Name Conversational QoS Class Conversational QoS Class
1.10.17.6 Number of DCH-to-HSDPA Directed Retry Attempts Counters

Counter ID 67192444 Counter Name VS.DRD.RB.D2H.Att.RNC Counter Description Number of DCH-to-HSDPA Directed Retry Attempts for RNC
Description
This counter provides the number of directed retry attempts from DCH to HSDPA in the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure. The measurement is triggered when the RNC sends the UE a RADIO BEARER SETUP message during the RAB assignment procedure for the directed retry from DCH to HSDPA.
Figure 1-258 RB setup procedure (successful operation)
The measurement is triggered at point A as shown in the figure. The measurement is triggered when the RNC sends the UE a RADIO BEARER RECONFIGURATION message during the RAB assignment procedure for the directed retry from DCH to HSDPA. Figure 1-259 RB reconfiguration procedure (successful operation)
Issue 01 (2013-05-04)
579
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RB.D2H.Att.RNC Feature ID WRFD-01061112 WRFD-02040001 Feature Name HSDPA DRD Intra System Direct Retry
1.10.17.7 Number of Successful DCH-to-HSDPA Directed Retry Counters

Counter ID 67192445 Counter Name VS.DRD.RB.D2H.Succ.RN C Counter Description Number of Successful DCHto-HSDPA Directed Retry for RNC
Description
This counter provides the number of times that the directed retry from DCH to HSDPA succeeds in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure. The measurement is triggered when the RNC receives from the UE a RADIO BEARER SETUP COMMPLETE message during the RAB assignment procedure for the directed retry from DCH to HSDPA.
Issue 01 (2013-05-04)
580
The measurement is triggered at point B as shown in the figure. The measurement is triggered when the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMMPLETE message during the RAB assignment procedure for the directed retry from DCH to HSDPA. Figure 1-261 RB reconfiguration procedure (successful operation)
Issue 01 (2013-05-04)
581
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RB.D2H.Succ.RN C Feature ID WRFD-01061112 WRFD-02040001 Feature Name HSDPA DRD Intra System Direct Retry
1.10.17.8 Counters Related to the Average Number of PS R99 Streaming Service RBs Counters
Counter ID 67202601 Counter Name VS.RB.PS.Str.DL. 256.384.RNC Counter Description Average Number of RBs for PS R99 Streaming Services with DL Rate of 256 Kbit/s or 384 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with DL Rate of 144 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with DL Rate of 128 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with DL Rate of 64 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with DL Rate of 32 Kbit/s for RNC
67202604
VS.RB.PS.Str.DL.144.RNC
67202607
67202610
67202613
Issue 01 (2013-05-04)
582
Counter ID 67202616
Counter Name VS.RB.PS.Str.DL.16.RNC
Counter Description Average Number of RBs for PS R99 Streaming Services with DL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with DL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 144 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 128 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 64 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 32 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 16 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 8 Kbit/s for RNC Average Number of RBs for PS R99 Streaming Services with UL Rate of 256 Kbit/s or 384 Kbit/s for RNC
67202619
67202625
VS.RB.PS.Str.UL.144.RNC
67202628
67202631
67202634
67202637
67202640
67202622
VS.RB.PS.Str.UL. 256.384.RNC
Description
These counters provide the average number of RBs for PS P99 streaming services in the uplink or downlink.
Issue 01 (2013-05-04)
583
Measurement point
The number of RBs for each type of PS R99 streaming services is sampled periodically (sampling periodicity is 5 seconds) in the RNC. At the end of the measurement period, the value of each counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.RB.PS.Str.DL. 256.384.RNC VS.RB.PS.Str.DL.144.RNC VS.RB.PS.Str.DL.128.RNC VS.RB.PS.Str.DL.64.RNC VS.RB.PS.Str.DL.32.RNC VS.RB.PS.Str.DL.16.RNC VS.RB.PS.Str.DL.8.RNC VS.RB.PS.Str.UL.144.RNC VS.RB.PS.Str.UL.128.RNC VS.RB.PS.Str.UL.64.RNC VS.RB.PS.Str.UL.32.RNC VS.RB.PS.Str.UL.16.RNC VS.RB.PS.Str.UL.8.RNC VS.RB.PS.Str.UL. 256.384.RNC Feature ID WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 Feature Name Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class
Issue 01 (2013-05-04)
584
1.10.18 Measurement of relocation per DRNC (Relocation.Drnc.RNC)

Overview
TRNC relocation involves two stages: TRNC relocation preparation and TRNC relocation execution. The TRNC relocation preparation involves the following messages: RELOCATION REQUEST , RELOCATION REQUEST ACKNOWLEDGE , and RELOCATION FAILURE . If the resource allocation for TRNC relocation succeeds, the TRNC sends a RELOCATION REQUEST ACKNOWLEDGE to the CN. If the resource allocation for TRNC relocation fails, the TRNC sends a RELOCATION FAILURE with the cause value to the CN. TRNC relocation execution is a procedure in which the TRNC receives a RELOCATION COMMIT from the SRNC or receives the reconfiguration response from the UE after successful relocation preparation. If the preparation procedure indicates that the relocation is a "UE not Involved" relocation, the TRNC receives a RELOCATION COMMIT from the SRNC after successful relocation preparation. If the preparation procedure indicates that the relocation is a "UE Involved" relocation, the TRNC receives the reconfiguration response from the UE after successful relocation preparation. The reconfiguration procedure involves the following messages: RADIO BEARER SETUP COMPLETE , RADIO BEARER RECONFIGURATION COMPLETE , RADIO BEARER RELEASE COMPLETE , TRANSPORT CHANNEL RECONFIGURATION COMPLETE , and PHYSICAL CHANNEL RECONFIGURATION COMPLETE .
Counters
Counter ID 67175893 Counter Name VS.DRELOC.FailE xec.Cong Counter Description Number of Failed Relocation Executions for TRNC (Resources Unavailable) Number of Failed Relocation Executions for TRNC (Protocol Cause) Number of Failed Relocation Preparations Due to Reception of IU Release Command for TRNC Original Release Earlier than V900R011
67175894
VS.DRELOC.FailE xec.Unsp
67190207
VS.DRELOC.FailP rep.IuRel
Issue 01 (2013-05-04)
585
Counter ID 67175881
Counter Name VS.DRELOC.FailP rep.NAS
Counter Description Number of Failed Relocation Preparations for TRNC (NAS Cause) Number of Failed Relocation Preparations for TRNC (Radio Network Layer Cause) Number of Failed Relocation Preparations for TRNC (Transport Layer Cause) Number of Relocation Execution Attempts for TRNC (UE Involved) Number of Relocation Execution Attempts for TRNC (UE Not Involved) Number of Successful Relocation Executions for TRNC (UE Not Involved) Number of Successful Relocation Executions for TRNC (UE Involved) Number of PS Relocation Resource Allocation Attempts for TRNC (UE Involved)
67175879
VS.DRELOC.FailP rep.RNL
67175880
VS.DRELOC.FailP rep.TNL
67190208
VS.TRELOC.AttE xecUEInvol
67190209
VS.TRELOC.AttE xecUENotInvol
67190212
VS.TRELOC.SuccExecUENotInvol
67190213
VS.TRELOC.SuccExecUEInvol
67191091
RELOC.AttResAllocUEInvolPS
Issue 01 (2013-05-04)
586
Counter ID 67191092
Counter Name RELOC.AttResAllocUENotInvolPS
Counter Description Number of PS Relocation Resource Allocation Attempts for TRNC (UE Not Involved) Number of Successful PS Relocation Resource Allocations for TRNC (UE Involved) Number of Successful PS Relocation Resource Allocations for TRNC (UE Not Involved) Number of Failed PS Relocation Preparations for TRNC (UE Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed PS Relocation Preparations for TRNC (UE Not Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed PS Relocation Preparations for TRNC (UE Involved) (No Resources Available)
67191097
RELOC.SuccResAl locUEInvolPS
67191098
RELOC.SuccResAl locUENotInvolPS
67191099
RELOC.FailResAll ocUEInvolPS.CiphUnSupp
67191100
RELOC.FailResAll ocUENotInvolPS.C iphUnSupp
67191101
RELOC.FailResAll ocUEInvolPS.ResUnavail
Issue 01 (2013-05-04)
587
Counter ID 67191102
Counter Name RELOC.FailResAll ocUENotInvolPS.R esUnavail
Counter Description Number of Failed PS Relocation Preparations for TRNC (UE Not Involved) (No Resources Available) Number of CS Relocation Resource Allocation Attempts for TRNC (UE Involved) Number of CS Relocation Resource Allocation Attempts for TRNC (UE Not Involved) Number of Successful CS Relocation Resource Allocations for TRNC (UE Involved) Number of Successful CS Relocation Resource Allocations for TRNC (UE Not Involved) Number of Failed CS Relocation Preparations for TRNC (UE Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported)
67191107
RELOC.AttResAllocUEInvolCS
67191108
RELOC.AttResAllocUENotInvolCS
67191113
RELOC.SuccResAl locUEInvolCS
67191114
RELOC.SuccResAl locUENotInvolCS
67191115
RELOC.FailResAll ocUEInvolCS.CiphUnSupp
Issue 01 (2013-05-04)
588
Counter ID 67191116
Counter Name RELOC.FailResAll ocUENotInvolCS.C iphUnSupp
Counter Description Number of Failed CS Relocation Preparations for TRNC (UE Not Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed CS Relocation Preparations for TRNC (UE Not Involved) (No Resources Available) Number of Failed Relocation Preparations for TRNC (NodeB Rehoming) Number of Successful CS Relocations for TRNC (UE Involved) Number of Successful PS Relocations for TRNC (UE Involved) Number of Successful CS Relocations for TRNC (UE Not Involved) Number of Successful PS Relocations for TRNC (UE Not Involved)
67191117
RELOC.FailResAll ocUENotInvolCS.R esUnavail
73423643
VS.DRELOC.FailP rep.NodeBReHost
V900R014
73424478
VS.TRELOC.SuccExecUEInvolCS
V900R014
73424479
VS.TRELOC.SuccExecUEInvolPS
V900R014
73424480
VS.TRELOC.SuccExecUENotInvolCS
V900R014
73424481
VS.TRELOC.SuccExecUENotInvolPS
V900R014
Issue 01 (2013-05-04)
589
None
1.10.18.1 Counters Related to the Number of Failed Relocation Executions for Different Causes for TRNC Counters
Counter ID 67175893 Counter Name VS.DRELOC.FailExec.Con g VS.DRELOC.FailExec.Uns p Counter Description Number of Failed Relocation Executions for TRNC (Resources Unavailable) Number of Failed Relocation Executions for TRNC (Protocol Cause)
67175894
Description
These counters provide the number of failed relocation executions in the TRNC according to different failure causes.
Measurement point
The measurement is triggered at point A as shown in the following figure. Before the relocation is complete and after the resource allocation for relocation is complete, the TRNC measures the related counter according to different failure causes when sending a RRC CONNECTION RELEASE message to the UE. Figure 1-262 Failed TRNC relocation execution procedure
Issue 01 (2013-05-04)
590
Formula
None
Unit
None
Related Features
Counter Name VS.DRELOC.FailExec.Con g VS.DRELOC.FailExec.Uns p Feature ID WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.18.2 Number of Failed Relocation Resource Allocations Due to Reception of IU Release Command for TRNC Counters
Counter ID 67190207 Counter Name VS.DRELOC.FailPrep.IuRel Counter Description Number of Failed Relocation Preparations Due to Reception of IU Release Command for TRNC
Description
This counter provides the number of failed relocation preparations due to the reception of IU RELEASE COMMAND message from the CN during the relocation.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the TRNC receives an IU RELEASE COMMAND message from the CN during the relocation preparation, the relocation preparation fails. In this case, the TRNC measures the counter.
Issue 01 (2013-05-04)
591
Figure 1-263 Failed resource allocation for TRNC relocation due to reception of IU release command
Formula
None
Unit
None
Related Features
Counter Name VS.DRELOC.FailPrep.IuRel Feature ID WRFD-020605 Feature Name SRNS Relocation Introduction Package
1.10.18.3 Number of Failed Relocation Resource Allocations for TRNC Counters

Counter ID 67175881 Counter Name VS.DRELOC.FailPrep.NAS Counter Description Number of Failed Relocation Preparations for TRNC (NAS Cause)
592
Issue 01 (2013-05-04)
Counter ID 67175879
Counter Name VS.DRELOC.FailPrep.RNL
Counter Description Number of Failed Relocation Preparations for TRNC (Radio Network Layer Cause) Number of Failed Relocation Preparations for TRNC (Transport Layer Cause) Number of Failed PS Relocation Preparations for TRNC (UE Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed PS Relocation Preparations for TRNC (UE Not Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed PS Relocation Preparations for TRNC (UE Involved) (No Resources Available) Number of Failed PS Relocation Preparations for TRNC (UE Not Involved) (No Resources Available) Number of Failed CS Relocation Preparations for TRNC (UE Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed CS Relocation Preparations for TRNC (UE Not Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed CS Relocation Preparations for TRNC (UE Not Involved) (No Resources Available)
67175880
VS.DRELOC.FailPrep.TNL
67191099
RELOC.FailResAllocUEInv olPS.CiphUnSupp
67191100
RELOC.FailResAllocUENo tInvolPS.CiphUnSupp
67191101
RELOC.FailResAllocUEInv olPS.ResUnavail
67191102
RELOC.FailResAllocUENo tInvolPS.ResUnavail
67191115
RELOC.FailResAllocUEInv olCS.CiphUnSupp
67191116
RELOC.FailResAllocUENo tInvolCS.CiphUnSupp
67191117
RELOC.FailResAllocUENo tInvolCS.ResUnavail
Issue 01 (2013-05-04)
593
Counter ID 73423643
Counter Name VS.DRELOC.FailPrep.NodeBReHost
Counter Description Number of Failed Relocation Preparations for TRNC (NodeB Rehoming)
Description
These counters provide the numbers of failed relocation resource allocations for the TRNC based on failure causes.
Measurement point
The measurement is triggered at point A as shown in the figure. During a relocation preparation, when the relocation resource allocation fails, the TRNC sends a RELOCATION FAILURE message to the CN. In this case, the TRNC measures the related counter based on failure causes. Figure 1-264 Failed resource allocation procedure for TRNC relocation
Formula
None
Unit
None
Issue 01 (2013-05-04)
594
Related Features
Counter Name VS.DRELOC.FailPrep.NAS VS.DRELOC.FailPrep.RNL VS.DRELOC.FailPrep.TNL RELOC.FailResAllocUEInv olPS.CiphUnSupp RELOC.FailResAllocUENo tInvolPS.CiphUnSupp RELOC.FailResAllocUEInv olPS.ResUnavail RELOC.FailResAllocUENo tInvolPS.ResUnavail RELOC.FailResAllocUEInv olCS.CiphUnSupp RELOC.FailResAllocUENo tInvolCS.CiphUnSupp RELOC.FailResAllocUENo tInvolCS.ResUnavail VS.DRELOC.FailPrep.NodeBReHost Feature ID WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-040202 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package RNC Node Redundancy SRNS Relocation Introduction Package
1.10.18.4 Number of Reconfiguration Completions During Relocation for TRNC (UE Involved) Counters
Counter ID 67190208 Counter Name VS.TRELOC.AttExecUEInvol Counter Description Number of Relocation Execution Attempts for TRNC (UE Involved)
Issue 01 (2013-05-04)
595
Description
This counter provides the number of TRNC reconfiguration completions during the relocation (UE involved).
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the RADIO BEARER RECONFIGURATION COMPLETE message as an example. During the relocation (UE involved), the TRNC measures the counter when receiving a RADIO BEARER RECONFIGURATION COMPLETE message from the UE. Figure 1-265 Reconfiguration procedure during the TRNC relocation (UE involved)
Formula
None
Unit
None
Related Features
Counter Name VS.TRELOC.AttExecUEInvol Feature ID WRFD-020605 Feature Name SRNS Relocation Introduction Package
Issue 01 (2013-05-04)
596
1.10.18.5 Number of Relocation Execution Attempts for TRNC (UE Not Involved) Counters
Counter ID 67190209 Counter Name VS.TRELOC.AttExecUENotInvol Counter Description Number of Relocation Execution Attempts for TRNC (UE Not Involved)
Description
This counter provides the number of TRNC relocation execution attempts during the relocation (UE not involved).
Measurement point
The measurement is triggered at point A as shown in the following figure. During the relocation (UE not involved), the TRNC measures this counter when receiving a RELOCATION COMMIT message from the SRNC. Figure 1-266 TRNC relocation execution procedure (UE not involved)
Formula
None
Unit
None
Related Features
Counter Name VS.TRELOC.AttExecUENotInvol Feature ID WRFD-020605 Feature Name SRNS Relocation Introduction Package
1.10.18.6 Number of Successful Relocation Executions for TRNC (UE Not Involved) Counters
Counter ID 67190212 Counter Name VS.TRELOC.SuccExecUENotInvol Counter Description Number of Successful Relocation Executions for TRNC (UE Not Involved)
Description
These counters provide the number of successful TRNC relocation executions during the relocation (UE not involved).
Measurement point
The measurement is triggered at point B as shown in the following figure. When the TRNC relocation is complete, the TRNC sends a RELOCATION COMPLETE message to the CN. In this case, the TRNC measures the related counters according to different relocation types. If the UE connects to both the CS domain and the PS domain at the same time, the related counters are increased by one respectively every time the TRNC sends a RELOCATION COMPLETE message to the CNs in the CS domain and PS domain.
Issue 01 (2013-05-04)
598
Figure 1-267 TRNC relocation execution procedure (UE not involved)
Formula
None
Unit
None
Related Features
Counter Name VS.TRELOC.SuccExecUENotInvol Feature ID WRFD-020605 Feature Name SRNS Relocation Introduction Package
1.10.18.7 Number of Successful Relocation Executions for TRNC (UE Involved) Counters
Counter ID 67190213 Counter Name VS.TRELOC.SuccExecUEInvol Counter Description Number of Successful Relocation Executions for TRNC (UE Involved)
Issue 01 (2013-05-04)
599
Description
These counters provide the number of successful TRNC relocation executions during the relocation (UE involved).
Measurement point
The measurement is triggered at point B as shown in the following figure. When the TRNC relocation is complete, the TRNC sends a RELOCATION COMPLETE message to the CN. In this case, the TRNC measures the related counters according to different relocation types. If the UE connects to both the CS domain and the PS domain at the same time, the related counters are increased by one respectively every time the TRNC sends a RELOCATION COMPLETE message to the CNs in the CS domain and PS domain. Figure 1-268 Reconfiguration procedure during the TRNC relocation (UE involved)
Formula
None
Unit
None
Issue 01 (2013-05-04)
600
Related Features
Counter Name VS.TRELOC.SuccExecUEInvol Feature ID WRFD-020605 Feature Name SRNS Relocation Introduction Package
1.10.18.8 Number of Relocation Resource Allocation Attempts for TRNC Counters

Counter ID 67191091 Counter Name RELOC.AttResAllocUEInvolPS Counter Description Number of PS Relocation Resource Allocation Attempts for TRNC (UE Involved) Number of PS Relocation Resource Allocation Attempts for TRNC (UE Not Involved) Number of CS Relocation Resource Allocation Attempts for TRNC (UE Involved) Number of CS Relocation Resource Allocation Attempts for TRNC (UE Not Involved)
67191092
RELOC.AttResAllocUENotInvolPS
67191107
RELOC.AttResAllocUEInvolCS
67191108
RELOC.AttResAllocUENotInvolCS
Description
These counters provide the numbers of CS or PS relocation resource allocations initiated by the TRNC based on the relocation type.
Measurement point
The measurement is triggered at point A as shown in the figure. When the TRNC receives a RELOCATION REQUEST message from the CS domain or PS domain in the CN, the TRNC measures the related counter based on relocation types.
Issue 01 (2013-05-04)
601
Figure 1-269 TRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
Counter Name RELOC.AttResAllocUEInvolPS RELOC.AttResAllocUENotInvolPS RELOC.AttResAllocUEInvolCS RELOC.AttResAllocUENotInvolCS Feature ID WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.18.9 Number of Successful Relocation Resource Allocations for TRNC

Counters
Counter ID 67191097 Counter Name RELOC.SuccResAllocUEInvolPS Counter Description Number of Successful PS Relocation Resource Allocations for TRNC (UE Involved) Number of Successful PS Relocation Resource Allocations for TRNC (UE Not Involved) Number of Successful CS Relocation Resource Allocations for TRNC (UE Involved) Number of Successful CS Relocation Resource Allocations for TRNC (UE Not Involved)
67191098
RELOC.SuccResAllocUENotInvolPS
67191113
RELOC.SuccResAllocUEInvolCS
67191114
RELOC.SuccResAllocUENotInvolCS
Description
These counters provide the numbers of successful CS or PS relocation resource allocations initiated by the TRNC based on the relocation type.
Measurement point
The measurement is triggered at point B as shown in the figure. When the relocation resource allocation is complete, the TRNC sends a RELOCATION REQUEST ACKNOWLEDGE message to the CS domain or PS domain in the CN. In this case, the TRNC measures the related counter based on relocation types.
Issue 01 (2013-05-04)
603
Figure 1-270 TRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
Counter Name RELOC.SuccResAllocUEInvolPS RELOC.SuccResAllocUENotInvolPS RELOC.SuccResAllocUEInvolCS RELOC.SuccResAllocUENotInvolCS Feature ID WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.18.10 Number of Successful TRNC Relocations in the CS Domain and PS Domain (UE Involved)
Counters
Counter ID 73424478 Counter Name VS.TRELOC.SuccExecUEInvolCS VS.TRELOC.SuccExecUEInvolPS Counter Description Number of Successful CS Relocations for TRNC (UE Involved) Number of Successful PS Relocations for TRNC (UE Involved)
73424479
Description
These counters measure the number of successful target RNC (TRNC) relocations.
Measurement point
The measurement is triggered at point B shown in figure 1 when the TRNC sends a RELOCATION COMPLETE message to the CN upon completing a relocation. In this case, these counters are measured based on the service type. Figure 1-271 Reconfiguration during a TRNC relocation (UE Involved)
Formula
None
Unit
None
Related Features
Counter Name VS.TRELOC.SuccExecUEInvolCS VS.TRELOC.SuccExecUEInvolPS Feature ID WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.18.11 Number of Successful TRNC Relocations in the CS Domain and PS Domain (UE Not Involved) Counters
Counter ID 73424480 Counter Name VS.TRELOC.SuccExecUENotInvolCS VS.TRELOC.SuccExecUENotInvolPS Counter Description Number of Successful CS Relocations for TRNC (UE Not Involved) Number of Successful PS Relocations for TRNC (UE Not Involved)
73424481
Description
These counters measure the number of successful target RNC (TRNC) relocations.
Measurement point
The measurement is triggered at point B shown in figure 1 when the TRNC sends a RELOCATION COMPLETE message to the CN upon completing a relocation. In this case, these counters are measured based on the service type.
Issue 01 (2013-05-04)
606
Figure 1-272 TRNC relocation execution procedure (UE not involved)
Formula
None
Unit
None
Related Features
Counter Name VS.TRELOC.SuccExecUENotInvolCS VS.TRELOC.SuccExecUENotInvolPS Feature ID WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.19 Measurement of relocation per SRNC (Relocation.Srnc.RNC)

Overview
SRNC relocation involves two stages: SRNC relocation preparation and SRNC relocation execution.
SRNC relocation preparation involves the following messages: RELOCATION REQUIRED message, RELOCATION COMMAND message, and RELOCATION FAILURE message. When the relocation conditions are satisfied, the SRNC sends a RELOCATION REQUIRED message to the CN. If the SRNC then receives a RELOCATION COMMAND message from the CN, the relocation preparation succeeds. If the SRNC receives from the CN a RELOCATION FAILURE message with the failure cause, the relocation preparation fails. SRNC relocation execution is a procedure in which the SRNC sends a RELOCATION COMMIT message to the TRNC or initiates a reconfiguration procedure to the UE after successful preparation. If the preparation procedure indicates that the relocation is a "UE not Involved" relocation, the SRNC sends a RELOCATION COMMIT message to the TRNC after successful preparation. If the preparation procedure indicates that the relocation is a "UE Involved" relocation, the SRNC initiates a reconfiguration procedure to the UE after successful preparation. The reconfiguration procedure involves the following messages: RADIO BEARER SETUP message, RADIO BEARER RECONFIGURATION message, RADIO BEARER RELEASE message, TRANSPORT CHANNEL RECONFIGURATION message, and PHYSICAL CHANNEL RECONFIGURATION message. If the SRNC receives a RADIO BEARER SETUP FAILURE message, RADIO BEARER RECONFIGURATION FAILURE message, RADIO BEARER RELEASE FAILURE message, TRANSPORT CHANNEL RECONFIGURATION FAILURE message, or PHYSICAL CHANNEL RECONFIGURATION FAILURE message, the reconfiguration fails. During the relocation execution, if the SRNC receives an IU RELEASE COMMAND message with the cause value of "Successful Relocation", "Normal Release", or "Network Optimization", the relocation execution succeeds.
Counters
Counter ID 67190184 Counter Name VS.RELOC.AttPre pUEInvolCS.TimeCrit Counter Description Number of CS Relocation Preparation Attempts for SRNC (UE Involved) (Time Critical Relocation) Number of CS Relocation Preparation Attempts for SRNC (UE Involved) (Relocation Desirable for Radio Reasons) Number of CS Relocation Preparation Attempts for SRNC (UE Involved) Original Release Earlier than V900R011
67190185
VS.RELOC.AttPre pUEInvolCS.RF
67190186
RELOC.AttPrepUEInvolCS
Issue 01 (2013-05-04)
608
Counter ID 67190187
Counter Name VS.RELOC.SuccPr epUEInvolCS.Time Crit
Counter Description Number of Successful CS Relocation Preparations for SRNC (UE Involved) (Time Critical Relocation) Number of Successful CS Relocation Preparations for SRNC (UE Involved) (Relocation Desirable for Radio Reasons) Number of Successful CS Relocation Preparations for SRNC (UE Involved) Number of Failed CS Relocation Preparations for SRNC (UE Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed CS Relocation Preparations for SRNC (UE Involved) (Trelocprep Expiry)
67190188
VS.RELOC.SuccPr epUEInvolCS.RF
67190189
RELOC.SuccPrepUEInvolCS
67190192
RELOC.FailPrepU EInvolCS.CiphUnSupp
67175739
RELOC.FailPrepU EInvolCS.TrelocprepExp
Issue 01 (2013-05-04)
609
Counter ID 67175740
Counter Name RELOC.FailPrepU EInvolCS.TgtSysUnsupp
Counter Description Number of Failed CS Relocation Preparations for SRNC (UE Involved) (Relocation Not Supported in Target RNC or Target System) Number of Failed CS Relocation Preparations for SRNC (UE Involved) (Relocation Target Not Allowed) Number of Failed CS Relocation Preparations for SRNC (UE Involved) (No Resources Available) Number of Failed CS Relocation Preparations for SRNC (UE Involved) (Unspecified Failure) Number of Failed Relocation Executions During Reconfiguration for SRNC (Configuration Unsupported) Number of Failed Relocation Executions During Reconfiguration for SRNC (Physical Channel Failure)
67190193
RELOC.FailPrepU EInvolCS.TgtNotAllow
67190194
RELOC.FailPrepU EInvolCS.ResUnavail
67190195
RELOC.FailPrepU EInvolCS.Unsp
67175799
VS.SRELOC.FailE xec.CfgUnsupp
67175800
VS.SRELOC.FailE xec.PhyChFail
Issue 01 (2013-05-04)
610
Counter ID 67175802
Counter Name VS.SRELOC.FailE xec.InvCfg
Counter Description Number of Failed Relocation Executions During Reconfiguration for SRNC (Invalid Configuration) Number of Failed Relocation Executions During Reconfiguration for SRNC (Configuration Incomplete) Number of Failed SRNC Relocation Executions Due to Timer Expiry for IU Release Command for SRNC (PS Domain) Number of Failed SRNC Relocation Executions Due to Timer Expiry for IU Release Command for SRNC (CS Domain) Number of PS Relocation Execution Attempts for SRNC (UE Not Involved) Number of CS Relocation Execution Attempts for SRNC (UE Not Involved) Number of Failed Relocation Executions Due to Reception of IU Release Command for SRNC
67175803
VS.SRELOC.FailE xec.CfgIncomp
67192140
VS.SRELOC.FailE xecPS.Expire
67192141
VS.SRELOC.FailE xecCS.Expire
67192142
VS.SRELOC.AttE xecUENotInvolPS
67192143
VS.SRELOC.AttE xecUENotInvolCS
67175805
VS.SRELOC.FailE xec.IuRel
Issue 01 (2013-05-04)
611
Counter ID 67191047
Counter Name VS.RELOC.AttPre pUENotInvolCS.Ti meCrit
Counter Description Number of CS Relocation Preparation Attempts for SRNC (UE Not Involved) (Time Critical Relocation) Number of CS Relocation Preparation Attempts for SRNC (UE Not Involved) (Relocation Desirable for Radio Reasons) Number of CS Relocation Preparation Attempts for SRNC (UE Not Involved) Number of Successful CS Relocation Preparations for SRNC (UE Not Involved) (Time Critical Relocation) Number of Successful CS Relocation Preparations for SRNC (UE Not Involved) (Relocation Desirable for Radio Reasons) Number of Successful CS Relocation Preparations for SRNC (UE Not Involved)
67191048
VS.RELOC.AttPre pUENotInvolCS.R F
67191049
RELOC.AttPrepU ENotInvolCS
67191050
VS.RELOC.SuccPr epUENotInvolCS.T imeCrit
67191051
VS.RELOC.SuccPr epUENotInvolCS.R F
67191052
RELOC.SuccPrepUENotInvolCS
Issue 01 (2013-05-04)
612
Counter ID 67191053
Counter Name RELOC.FailPrepU ENotInvolCS.CiphUnSupp
Counter Description Number of Failed CS Relocation Preparations for SRNC (UE Not Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed CS Relocation Preparations for SRNC (UE Not Involved) (Trelocprep Expiry) Number of Failed CS Relocation Preparations for SRNC (UE Not Involved) (Relocation Not Supported in Target RNC or Target System) Number of Failed CS Relocation Preparations for SRNC (UE Not Involved) (Relocation Target Not Allowed) Number of Failed CS Relocation Preparations for SRNC (UE Not Involved) (No Resources Available) Number of Failed CS Relocation Preparations for SRNC (UE Not Involved) (Unspecified Failure)
67191054
RELOC.FailPrepU ENotInvolCS.TrelocprepExp
67191055
RELOC.FailPrepU ENotInvolCS.TgtS ysUnsupp
67191056
RELOC.FailPrepU ENotInvolCS.TgtN otAllow
67191058
RELOC.FailPrepU ENotInvolCS.ResUnavail
67191059
RELOC.FailPrepU ENotInvolCS.Unsp
Issue 01 (2013-05-04)
613
Counter ID 67191060
Counter Name VS.RELOC.AttPre pUEInvolPS.TimeCrit
Counter Description Number of PS Relocation Preparation Attempts for SRNC (UE Involved) (Time Critical Relocation) Number of PS Relocation Preparation Attempts for SRNC (UE Not Involved) (Time Critical Relocation) Number of PS Relocation Preparation Attempts for SRNC (UE Involved) (Relocation Desirable for Radio Reasons) Number of PS Relocation Preparation Attempts for SRNC (UE Not Involved) (Relocation Desirable for Radio Reasons) Number of PS Relocation Preparation Attempts for SRNC (UE Involved) Number of PS Relocation Preparation Attempts for SRNC (UE Not Involved)
67191061
VS.RELOC.AttPre pUENotInvolPS.Ti meCrit
67191062
VS.RELOC.AttPre pUEInvolPS.RF
67191063
VS.RELOC.AttPre pUENotInvolPS.R F
67191064
RELOC.AttPrepUEInvolPS
67191065
RELOC.AttPrepU ENotInvolPS
Issue 01 (2013-05-04)
614
Counter ID 67191066
Counter Name VS.RELOC.SuccPr epUEInvolPS.Time Crit
Counter Description Number of Successful PS Relocation Preparations for SRNC (UE Involved) (Time Critical Relocation) Number of Successful PS Relocation Preparations for SRNC (UE Not Involved) (Time Critical Relocation) Number of Successful PS Relocation Preparations for SRNC (UE Involved) (Relocation Desirable for Radio Reasons) Number of Successful PS Relocation Preparations for SRNC (UE Not Involved) (Relocation Desirable for Radio Reasons) Number of Successful PS Relocation Preparations for SRNC (UE Involved) Number of Successful PS Relocation Preparations for SRNC (UE Not Involved)
67191067
VS.RELOC.SuccPr epUENotInvolPS.T imeCrit
67191068
VS.RELOC.SuccPr epUEInvolPS.RF
67191069
VS.RELOC.SuccPr epUENotInvolPS.R F
67191070
RELOC.SuccPrepUEInvolPS
67191071
RELOC.SuccPrepUENotInvolPS
Issue 01 (2013-05-04)
615
Counter ID 67191072
Counter Name RELOC.FailPrepU EInvolPS.CiphUnSupp
Counter Description Number of Failed PS Relocation Preparations for SRNC (UE Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed PS Relocation Preparations for SRNC (UE Not Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (Trelocprep Expiry) Number of Failed PS Relocation Preparations for SRNC (UE Not Involved) (Trelocprep Expiry) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (Relocation Not Supported in Target RNC or Target System)
67191073
RELOC.FailPrepU ENotInvolPS.CiphUnSupp
67191074
RELOC.FailPrepU EInvolPS.TrelocprepExp
67191075
RELOC.FailPrepU ENotInvolPS.TrelocprepExp
67191076
RELOC.FailPrepU EInvolPS.TgtSysUnsupp
Issue 01 (2013-05-04)
616
Counter ID 67191077
Counter Name RELOC.FailPrepU ENotInvolPS.TgtSy sUnsupp
Counter Description Number of Failed PS Relocation Preparations for SRNC (UE Not Involved) (Relocation Not Supported in Target RNC or Target System) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (Relocation Target Not Allowed) Number of Failed PS Relocation Preparations for SRNC (UE Not Involved) (Relocation Target Not Allowed) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (No Resources Available) Number of Failed PS Relocation Preparations for SRNC (UE Not Involved) (No Resources Available) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (Unspecified Failure)
67191078
RELOC.FailPrepU EInvolPS.TgtNotAllow
67191079
RELOC.FailPrepU ENotInvolPS.TgtN otAllow
67191082
RELOC.FailPrepU EInvolPS.ResUnavail
67191083
RELOC.FailPrepU ENotInvolPS.ResUnavail
67191084
RELOC.FailPrepU EInvolPS.Unsp
Issue 01 (2013-05-04)
617
Counter ID 67191085
Counter Name RELOC.FailPrepU ENotInvolPS.Unsp
Counter Description Number of Failed PS Relocation Preparations for SRNC (UE Not Involved) (Unspecified Failure) Number of CS Relocation Execution Attempts for SRNC (UE Involved) Number of PS Relocation Execution Attempts for SRNC (UE Involved) Number of Successful CS Relocation Executions for SRNC (UE Involved) Number of Successful PS Relocation Executions for SRNC (UE Involved) Number of Successful CS Relocation Executions for SRNC (UE Not Involved) Number of Successful PS Relocation Executions for SRNC (UE Not Involved)
67192683
VS.SRELOC.AttE xecUEInvolCS
67192684
VS.SRELOC.AttE xecUEInvolPS
67192685
VS.SRELOC.SuccExecUEInvolCS
67192686
VS.SRELOC.SuccExecUEInvolPS
67192687
VS.SRELOC.SuccExecUENonInvolCS
67192688
VS.SRELOC.SuccExecUENonInvolPS
Issue 01 (2013-05-04)
618
Counter ID 73423644
Counter Name RELOC.FailPrepU EInvolCS.NodeBReHost
Counter Description Number of Failed CS Relocation Preparations for SRNC (UE Involved) (NodeB Rehoming) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (NodeB Rehoming)
73423645
RELOC.FailPrepU EInvolPS.NodeBReHost
V900R014
None
1.10.19.1 Number of Relocation Preparation Attempts Due to Different Causes for SRNC Counters
Counter ID 67190184 Counter Name VS.RELOC.AttPrepUEInvo lCS.TimeCrit Counter Description Number of CS Relocation Preparation Attempts for SRNC (UE Involved) (Time Critical Relocation) Number of CS Relocation Preparation Attempts for SRNC (UE Involved) (Relocation Desirable for Radio Reasons) Number of CS Relocation Preparation Attempts for SRNC (UE Not Involved) (Time Critical Relocation) Number of CS Relocation Preparation Attempts for SRNC (UE Not Involved) (Relocation Desirable for Radio Reasons)
67190185
VS.RELOC.AttPrepUEInvo lCS.RF
67191047
VS.RELOC.AttPrepUENotI nvolCS.TimeCrit
67191048
VS.RELOC.AttPrepUENotI nvolCS.RF
Issue 01 (2013-05-04)
619
Counter ID 67191060
Counter Name VS.RELOC.AttPrepUEInvo lPS.TimeCrit
Counter Description Number of PS Relocation Preparation Attempts for SRNC (UE Involved) (Time Critical Relocation) Number of PS Relocation Preparation Attempts for SRNC (UE Not Involved) (Time Critical Relocation) Number of PS Relocation Preparation Attempts for SRNC (UE Involved) (Relocation Desirable for Radio Reasons) Number of PS Relocation Preparation Attempts for SRNC (UE Not Involved) (Relocation Desirable for Radio Reasons)
67191061
VS.RELOC.AttPrepUENotI nvolPS.TimeCrit
67191062
VS.RELOC.AttPrepUEInvo lPS.RF
67191063
VS.RELOC.AttPrepUENotI nvolPS.RF
Description
These counters provide the numbers of CS or PS relocation preparation attempts (UE involved or UE not involved) initiated by the SRNC based on different causes.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the SRNC sends a RELOCATION REQUIRED message to the CN in the CS or PS domain, the SRNC measures the related counters based on different causes if the relocation request type is "UE involved" or "UE not involved."
Issue 01 (2013-05-04)
620
Figure 1-273 SRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RELOC.AttPrepUEInvo lCS.TimeCrit VS.RELOC.AttPrepUEInvo lCS.RF VS.RELOC.AttPrepUENotI nvolCS.TimeCrit VS.RELOC.AttPrepUENotI nvolCS.RF VS.RELOC.AttPrepUEInvo lPS.TimeCrit VS.RELOC.AttPrepUENotI nvolPS.TimeCrit Feature ID WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package
Issue 01 (2013-05-04)
621
Counter Name VS.RELOC.AttPrepUEInvo lPS.RF VS.RELOC.AttPrepUENotI nvolPS.RF
Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.19.2 Number of Relocation Preparation Attempts for SRNC Counters

Counter ID 67190186 Counter Name RELOC.AttPrepUEInvolCS Counter Description Number of CS Relocation Preparation Attempts for SRNC (UE Involved) Number of CS Relocation Preparation Attempts for SRNC (UE Not Involved) Number of PS Relocation Preparation Attempts for SRNC (UE Involved) Number of PS Relocation Preparation Attempts for SRNC (UE Not Involved)
67191049
RELOC.AttPrepUENotInvolCS RELOC.AttPrepUEInvolPS
67191064
67191065
RELOC.AttPrepUENotInvolPS
Description
These counters provide the numbers of CS or PS relocation preparation attempts initiated by the SRNC based on the relocation type.
Measurement point
The measurement is triggered at point A as shown in the figure. When the SRNC sends a RELOCATION REQUIRED message to the CS domain or PS domain in the CN, the SRNC measures the related counter based on relocation types and CN domains.
Issue 01 (2013-05-04)
622
Formula
None
Unit
None
Related Features
Counter Name RELOC.AttPrepUEInvolCS RELOC.AttPrepUENotInvolCS RELOC.AttPrepUEInvolPS RELOC.AttPrepUENotInvolPS Feature ID WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.19.3 Number of Successful Relocation Preparations Due to Different Causes for SRNC
Counters
Counter ID 67190187 Counter Name VS.RELOC.SuccPrepUEInv olCS.TimeCrit Counter Description Number of Successful CS Relocation Preparations for SRNC (UE Involved) (Time Critical Relocation) Number of Successful CS Relocation Preparations for SRNC (UE Involved) (Relocation Desirable for Radio Reasons) Number of Successful CS Relocation Preparations for SRNC (UE Not Involved) (Time Critical Relocation) Number of Successful CS Relocation Preparations for SRNC (UE Not Involved) (Relocation Desirable for Radio Reasons) Number of Successful PS Relocation Preparations for SRNC (UE Involved) (Time Critical Relocation) Number of Successful PS Relocation Preparations for SRNC (UE Not Involved) (Time Critical Relocation) Number of Successful PS Relocation Preparations for SRNC (UE Involved) (Relocation Desirable for Radio Reasons) Number of Successful PS Relocation Preparations for SRNC (UE Not Involved) (Relocation Desirable for Radio Reasons)
67190188
VS.RELOC.SuccPrepUEInv olCS.RF
67191050
VS.RELOC.SuccPrepUENo tInvolCS.TimeCrit
67191051
VS.RELOC.SuccPrepUENo tInvolCS.RF
67191066
VS.RELOC.SuccPrepUEInv olPS.TimeCrit
67191067
VS.RELOC.SuccPrepUENo tInvolPS.TimeCrit
67191068
VS.RELOC.SuccPrepUEInv olPS.RF
67191069
VS.RELOC.SuccPrepUENo tInvolPS.RF
Description
These counters provide the numbers of successful CS or PS relocation preparations (UE involved or UE not involved) initiated by the SRNC based on different causes.
Issue 01 (2013-05-04)
624
Measurement point
The measurement is triggered at point B as shown in the figure. After the SRNC initiates a relocation procedure (UE involved or UE not involved), the outgoing relocation preparation succeeds if the SRNC receives a RELOCATION COMMAND message from the CS domain or PS domain in the CN. In this case, the SRNC measures the related counter based on relocation causes, CN domains, and whether the UE is involved. Figure 1-275 SRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RELOC.SuccPrepUEInv olCS.TimeCrit VS.RELOC.SuccPrepUEInv olCS.RF VS.RELOC.SuccPrepUENo tInvolCS.TimeCrit Feature ID WRFD-020605 WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package
Issue 01 (2013-05-04)
625
Counter Name VS.RELOC.SuccPrepUENo tInvolCS.RF VS.RELOC.SuccPrepUEInv olPS.TimeCrit VS.RELOC.SuccPrepUENo tInvolPS.TimeCrit VS.RELOC.SuccPrepUEInv olPS.RF VS.RELOC.SuccPrepUENo tInvolPS.RF
Feature ID WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605
Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.19.4 Number of Successful Relocation Preparations for SRNC Counters

Counter ID 67190189 Counter Name RELOC.SuccPrepUEInvolCS RELOC.SuccPrepUENotInvolCS RELOC.SuccPrepUEInvolPS RELOC.SuccPrepUENotInvolPS Counter Description Number of Successful CS Relocation Preparations for SRNC (UE Involved) Number of Successful CS Relocation Preparations for SRNC (UE Not Involved) Number of Successful PS Relocation Preparations for SRNC (UE Involved) Number of Successful PS Relocation Preparations for SRNC (UE Not Involved)
67191052
67191070
67191071
Description
These counters provide the numbers of successful CS or PS relocation preparations initiated by the SRNC based on the relocation type.
Measurement point
The measurement is triggered at point B as shown in the figure. After the SRNC initiates a relocation procedure, the outgoing relocation preparation succeeds if the SRNC receives a RELOCATION COMMAND message from the CS domain or PS domain in the CN. In this case, the SRNC measures the related counter based on relocation types and CN domains.
Formula
None
Unit
None
Related Features
Counter Name RELOC.SuccPrepUEInvolCS RELOC.SuccPrepUENotInvolCS RELOC.SuccPrepUEInvolPS RELOC.SuccPrepUENotInvolPS Feature ID WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.19.5 Number of Failed Relocation Preparations Due to Different Causes for SRNC
Counters
Counter ID 67190192 Counter Name RELOC.FailPrepUEInvolC S.CiphUnSupp Counter Description Number of Failed CS Relocation Preparations for SRNC (UE Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed CS Relocation Preparations for SRNC (UE Involved) (Trelocprep Expiry) Number of Failed CS Relocation Preparations for SRNC (UE Involved) (Relocation Not Supported in Target RNC or Target System) Number of Failed CS Relocation Preparations for SRNC (UE Involved) (Relocation Target Not Allowed) Number of Failed CS Relocation Preparations for SRNC (UE Involved) (No Resources Available) Number of Failed CS Relocation Preparations for SRNC (UE Involved) (Unspecified Failure) Number of Failed CS Relocation Preparations for SRNC (UE Not Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed CS Relocation Preparations for SRNC (UE Not Involved) (Trelocprep Expiry)
67175739
RELOC.FailPrepUEInvolC S.TrelocprepExp
67175740
RELOC.FailPrepUEInvolC S.TgtSysUnsupp
67190193
RELOC.FailPrepUEInvolC S.TgtNotAllow
67190194
RELOC.FailPrepUEInvolC S.ResUnavail
67190195
RELOC.FailPrepUEInvolC S.Unsp
67191053
RELOC.FailPrepUENotInv olCS.CiphUnSupp
67191054
RELOC.FailPrepUENotInv olCS.TrelocprepExp
Issue 01 (2013-05-04)
628
Counter ID 67191055
Counter Name RELOC.FailPrepUENotInv olCS.TgtSysUnsupp
Counter Description Number of Failed CS Relocation Preparations for SRNC (UE Not Involved) (Relocation Not Supported in Target RNC or Target System) Number of Failed CS Relocation Preparations for SRNC (UE Not Involved) (Relocation Target Not Allowed) Number of Failed CS Relocation Preparations for SRNC (UE Not Involved) (No Resources Available) Number of Failed CS Relocation Preparations for SRNC (UE Not Involved) (Unspecified Failure) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed PS Relocation Preparations for SRNC (UE Not Involved) (Requested Ciphering and/or Integrity Protection Algorithms Not Supported) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (Trelocprep Expiry) Number of Failed PS Relocation Preparations for SRNC (UE Not Involved) (Trelocprep Expiry) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (Relocation Not Supported in Target RNC or Target System)
67191056
RELOC.FailPrepUENotInv olCS.TgtNotAllow
67191058
RELOC.FailPrepUENotInv olCS.ResUnavail
67191059
RELOC.FailPrepUENotInv olCS.Unsp
67191072
RELOC.FailPrepUEInvolPS .CiphUnSupp
67191073
RELOC.FailPrepUENotInv olPS.CiphUnSupp
67191074
RELOC.FailPrepUEInvolPS .TrelocprepExp
67191075
RELOC.FailPrepUENotInv olPS.TrelocprepExp
67191076
RELOC.FailPrepUEInvolPS .TgtSysUnsupp
Issue 01 (2013-05-04)
629
Counter ID 67191077
Counter Name RELOC.FailPrepUENotInv olPS.TgtSysUnsupp
Counter Description Number of Failed PS Relocation Preparations for SRNC (UE Not Involved) (Relocation Not Supported in Target RNC or Target System) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (Relocation Target Not Allowed) Number of Failed PS Relocation Preparations for SRNC (UE Not Involved) (Relocation Target Not Allowed) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (No Resources Available) Number of Failed PS Relocation Preparations for SRNC (UE Not Involved) (No Resources Available) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (Unspecified Failure) Number of Failed PS Relocation Preparations for SRNC (UE Not Involved) (Unspecified Failure) Number of Failed CS Relocation Preparations for SRNC (UE Involved) (NodeB Rehoming) Number of Failed PS Relocation Preparations for SRNC (UE Involved) (NodeB Rehoming)
67191078
RELOC.FailPrepUEInvolPS .TgtNotAllow
67191079
RELOC.FailPrepUENotInv olPS.TgtNotAllow
67191082
RELOC.FailPrepUEInvolPS .ResUnavail
67191083
RELOC.FailPrepUENotInv olPS.ResUnavail
67191084
RELOC.FailPrepUEInvolPS .Unsp
67191085
RELOC.FailPrepUENotInv olPS.Unsp
73423644
RELOC.FailPrepUEInvolC S.NodeBReHost
73423645
RELOC.FailPrepUEInvolPS .NodeBReHost
Issue 01 (2013-05-04)
630
Description
These counters provide the numbers of failed CS or PS relocation preparations (UE involved or UE not involved) initiated by the SRNC based on different causes.
Measurement point
The measurement is triggered at point A as shown in the figure. After the SRNC initiates a relocation procedure (UE involved or UE not involved), the outgoing relocation preparation fails if the SRNC receives a RELOCATION PREPARATION FAILURE message from the CS domain or PS domain in the CN. In this case, the SRNC measures the related counter based on failure causes, CN domains, and whether the UE is involved. Figure 1-277 Failed SRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
Counter Name RELOC.FailPrepUEInvolC S.CiphUnSupp
Issue 01 (2013-05-04)
Feature Name SRNS Relocation Introduction Package

631
Counter Name RELOC.FailPrepUEInvolC S.TrelocprepExp RELOC.FailPrepUEInvolC S.TgtSysUnsupp RELOC.FailPrepUEInvolC S.TgtNotAllow RELOC.FailPrepUEInvolC S.ResUnavail RELOC.FailPrepUEInvolC S.Unsp RELOC.FailPrepUENotInv olCS.CiphUnSupp RELOC.FailPrepUENotInv olCS.TrelocprepExp RELOC.FailPrepUENotInv olCS.TgtSysUnsupp RELOC.FailPrepUENotInv olCS.TgtNotAllow RELOC.FailPrepUENotInv olCS.ResUnavail RELOC.FailPrepUENotInv olCS.Unsp RELOC.FailPrepUEInvolPS .CiphUnSupp RELOC.FailPrepUENotInv olPS.CiphUnSupp RELOC.FailPrepUEInvolPS .TrelocprepExp RELOC.FailPrepUENotInv olPS.TrelocprepExp RELOC.FailPrepUEInvolPS .TgtSysUnsupp RELOC.FailPrepUENotInv olPS.TgtSysUnsupp RELOC.FailPrepUEInvolPS .TgtNotAllow RELOC.FailPrepUENotInv olPS.TgtNotAllow
Feature ID WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605
Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package
Issue 01 (2013-05-04)
632
Counter Name RELOC.FailPrepUEInvolPS .ResUnavail RELOC.FailPrepUENotInv olPS.ResUnavail RELOC.FailPrepUEInvolPS .Unsp RELOC.FailPrepUENotInv olPS.Unsp RELOC.FailPrepUEInvolC S.NodeBReHost
Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package RNC Node Redundancy SRNS Relocation Introduction Package RNC Node Redundancy SRNS Relocation Introduction Package
RELOC.FailPrepUEInvolPS .NodeBReHost
1.10.19.6 Counters Related to the Number of Failed Relocation Executions During Reconfiguration for Different Causes for SRNC Counters
Counter ID 67175799 Counter Name VS.SRELOC.FailExec.Cfg Unsupp Counter Description Number of Failed Relocation Executions During Reconfiguration for SRNC (Configuration Unsupported) Number of Failed Relocation Executions During Reconfiguration for SRNC (Physical Channel Failure) Number of Failed Relocation Executions During Reconfiguration for SRNC (Invalid Configuration) Number of Failed Relocation Executions During Reconfiguration for SRNC (Configuration Incomplete)
67175800
VS.SRELOC.FailExec.Phy ChFail
67175802
VS.SRELOC.FailExec.InvC fg
67175803
VS.SRELOC.FailExec.CfgI ncomp
Issue 01 (2013-05-04)
633
Description
These counters provide the number of failed relocation (UE involved) executions during the reconfiguration according to different failure causes.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the RADIO BEARER RECONFIGURATION FAILURE message as an example. During the relocation execution, when the SRNC receives a RADIO BEARER RECONFIGURATION FAILURE message from the UE, the relocation execution fails. In this case, the SRNC measures the related counter according to different failure causes. Figure 1-278 Failed SRNC relocation procedure during the reconfiguration (UE involved)
Formula
None
Unit
None
Related Features
Counter Name VS.SRELOC.FailExec.Cfg Unsupp
Issue 01 (2013-05-04)
Feature Name SRNS Relocation Introduction Package

634
Counter Name VS.SRELOC.FailExec.Phy ChFail VS.SRELOC.FailExec.InvC fg VS.SRELOC.FailExec.CfgI ncomp
Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.19.7 Counters Related to the Number of Failed SRNC Relocation Executions Due to Timer Expiry for IU Release Command for SRNC Counters
Counter ID 67192140 Counter Name VS.SRELOC.FailExecPS.E xpire Counter Description Number of Failed SRNC Relocation Executions Due to Timer Expiry for IU Release Command for SRNC (PS Domain) Number of Failed SRNC Relocation Executions Due to Timer Expiry for IU Release Command for SRNC (CS Domain)
67192141
VS.SRELOC.FailExecCS.E xpire
Description
These counters provide the number of times that the relocation execution fails because the timer set to wait for the IU RELEASE COMMAND message expires according to different domain types.
Measurement point
The measurement is triggered at point A as shown in the following figure. After sending a RELOCATION COMMIT message (during the relocation that the UE is not involved), the SRNC starts the timer to wait for the IU RELEASE COMMAND message. If the SRNC does not receive an IU RELEASE COMMAND message before the timer expires, the SRNC sends an IU RELEASE REQUEST message to the CN. In addition, the SRNC measures the related counter according to different domain types.
Issue 01 (2013-05-04)
635
Figure 1-279 Failed SRNC relocation execution procedure due to timer expiry for IU release command (UE not involved)
The measurement is triggered at point A as shown in the following figure. After sending a reconfiguration message to the UE (during the relocation that the UE is involved. The following figure takes the RADIO BEARER RECONFIGURATION message as an example), the SRNC starts the timer to wait for the IU RELEASE COMMAND message. If the SRNC does not receive an IU RELEASE COMMAND message before the timer expires, the SRNC sends an IU RELEASE REQUEST message to the CN. In addition, the SRNC measures the related counter according to different domain types.
Issue 01 (2013-05-04)
636
Figure 1-280 Failed SRNC relocation execution procedure due to timer expiry for IU release command (UE involved)
Formula
None
Unit
None
Related Features
Counter Name VS.SRELOC.FailExecPS.E xpire VS.SRELOC.FailExecCS.E xpire Feature ID WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.19.8 Counters Related to the Number of Relocation Execution Attempts for SRNC (UE Not Involved)
Issue 01 (2013-05-04)
637
Counters
Counter ID 67192142 Counter Name VS.SRELOC.AttExecUENotInvolPS VS.SRELOC.AttExecUENotInvolCS Counter Description Number of PS Relocation Execution Attempts for SRNC (UE Not Involved) Number of CS Relocation Execution Attempts for SRNC (UE Not Involved)
67192143
Description
These counters provide the number of relocation execution attempts initiated by the SRNC during the relocation according to different domain types.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the SRNC sends a RELOCATION COMMIT message to the TRNC, if the relocation request type is "UE Not Involved", the SRNC measures the related counter according to different domain types. Figure 1-281 SRNC relocation execution procedure (UE not involved)
Formula
None
Issue 01 (2013-05-04)
638
Unit
None
Related Features
Counter Name VS.SRELOC.AttExecUENotInvolPS VS.SRELOC.AttExecUENotInvolCS Feature ID WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.19.9 Number of Failed Relocation Executions Due to Reception of IU Release Command for SRNC Counters
Counter ID 67175805 Counter Name VS.SRELOC.FailExec.IuRel Counter Description Number of Failed Relocation Executions Due to Reception of IU Release Command for SRNC
Description
This counter provides the number of failed relocation executions when the SRNC receives an IU RELEASE COMMAND message from the CN and the cause value contained in the message is not "Successful Relocation", "Normal Release", or "Network Optimization."
Measurement point
The measurement is triggered at point A as shown in the following figure. During the relocation execution, when receiving an IU RELEASE COMMAND message from the CN, the SRNC measures the counter if the cause value contained in the message is not "Successful Relocation", "Normal Release", or "Network Optimization."
Issue 01 (2013-05-04)
639
Figure 1-282 Failed SRNC relocation execution procedure (reception of IU release command)
Formula
None
Unit
None
Related Features
Counter Name VS.SRELOC.FailExec.IuRel Feature ID WRFD-020605 Feature Name SRNS Relocation Introduction Package
1.10.19.10 Counters Related to the Number of Reconfiguration Attempts During Relocation Execution for SRNC ( UE Involved)
Issue 01 (2013-05-04)
640
Counters
Counter ID 67192683 Counter Name VS.SRELOC.AttExecUEInvolCS VS.SRELOC.AttExecUEInvolPS Counter Description Number of CS Relocation Execution Attempts for SRNC (UE Involved) Number of PS Relocation Execution Attempts for SRNC (UE Involved)
67192684
Description
These counters provide the number of reconfiguration attempts (UE involved) initiated by the SRNC during the relocation according to different CN domains.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the RADIO BEARER RECONFIGURATION message as an example. During the SRNC relocation, when sending a RADIO BEARER RECONFIGURATION message to the UE, the SRNC measures the related counter according to the CN domain. Figure 1-283 Reconfiguration procedure during the SRNC relocation (UE involved)
Formula
None
Unit
None
Related Features
Counter Name VS.SRELOC.AttExecUEInvolCS VS.SRELOC.AttExecUEInvolPS Feature ID WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package
1.10.19.11 Number of Successful Relocation Executions for SRNC Counters

Counter ID 67192685 Counter Name VS.SRELOC.SuccExecUEInvolCS VS.SRELOC.SuccExecUEInvolPS VS.SRELOC.SuccExecUENonInvolCS VS.SRELOC.SuccExecUENonInvolPS Counter Description Number of Successful CS Relocation Executions for SRNC (UE Involved) Number of Successful PS Relocation Executions for SRNC (UE Involved) Number of Successful CS Relocation Executions for SRNC (UE Not Involved) Number of Successful PS Relocation Executions for SRNC (UE Not Involved)
67192686
67192687
67192688
Description
These counters provide the numbers of successful relocation executions (UE involved or UE not involved) initiated by the SRNC based on different CN domains.
Measurement point
The measurement is triggered at point A as shown in the figure. During the relocation (UE involved or UE not involved), when the SRNC receives an IU RELEASE COMMAND message with the cause value "Successful Relocation", "Normal Release", or "Network Optimization", the relocation succeeds. In this case, the SRNC measures the related counter based on CN domains and whether the UE is involved.
Figure 1-284 Successful SRNC relocation procedure
Formula
None
Unit
None
Related Features
Counter Name VS.SRELOC.SuccExecUEInvolCS VS.SRELOC.SuccExecUEInvolPS VS.SRELOC.SuccExecUENonInvolCS VS.SRELOC.SuccExecUENonInvolPS Feature ID WRFD-020605 WRFD-020605 WRFD-020605 WRFD-020605 Feature Name SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package SRNS Relocation Introduction Package
Issue 01 (2013-05-04)
643
1.10.20 RLC measurement per RNC(RLC.RNC)

Overview
This function subset measures the number of packets sent, received, discarded, and retransmitted at the RLC layer.
Counters
Counter ID 67202533 Counter Name RLC.NbrBlocksSe nt.TM RLC.NbrBlocksSe nt.AM RLC.NbrBlocksSe nt.UM RLC.NbrBlocksRe ceived.TM RLC.NbrBlocksRe ceived.AM RLC.NbrBlocksRe ceived.UM RLC.DiscardedBlocksByRNC RLC.RetransmittedBlocksToUE RLC.NbrBlocksRe ceived.AM.1 Counter Description Number of PDUs Sent by TM RLCs for RNC Number of PDUs Sent by AM RLCs for RNC Number of PDUs Sent by UM RLCs for RNC Number of PDUs Received by TM RLCs for RNC Number of PDUs Received by AM RLCs for RNC Number of PDUs Received by UM RLCs for RNC Number of PDUs Discarded by RLCs for RNC Number of PDUs Retransmitted by RLCs for RNC Number of PDUs with the Size Smaller than 336 bit Received by RLCs In Acknowledged Mode Carried by TRB Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 V900R012
67202534
67202535
67202536
67202537
67202538
67202539
67202540
67204246
Issue 01 (2013-05-04)
644
Counter ID 67204247
Counter Name RLC.NbrBlocksRe ceived.AM.2
Counter Description Number of PDUs with the Size Greater than or Equal to 336 bit Received by RLCs In Acknowledged Mode Carried by TRB
None
1.10.20.1 Number of Packets Sent at the RLC Layer Counters

Counter ID 67202533 67202534 67202535 Counter Name RLC.NbrBlocksSent.TM RLC.NbrBlocksSent.AM RLC.NbrBlocksSent.UM Counter Description Number of PDUs Sent by TM RLCs for RNC Number of PDUs Sent by AM RLCs for RNC Number of PDUs Sent by UM RLCs for RNC
Description
These counters provide the number of packets sent in TM, AM, and UM modes at the RLC layer in the RNC.
Measurement point
These counters are incremented by one each time the RLC layer on the RNC side sends a packet.
Formula
None
Unit
packet
Related Features
Counter Name RLC.NbrBlocksSent.TM Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
RLC.NbrBlocksSent.AM
WRFD-010510
RLC.NbrBlocksSent.UM
WRFD-010510
1.10.20.2 Number of Packets Received at the RLC Layer Counters

Counter ID 67202536 67202537 67202538 Counter Name RLC.NbrBlocksReceived.T M RLC.NbrBlocksReceived.A M RLC.NbrBlocksReceived.U M Counter Description Number of PDUs Received by TM RLCs for RNC Number of PDUs Received by AM RLCs for RNC Number of PDUs Received by UM RLCs for RNC
Description
These counters provide the number of packets received by the RLC layers in TM, AM, and UM modes on the RNC side.
Measurement point
These counters are incremented by one each time the RLC layer on the RNC receives a packet.
Formula
None
Unit
packet
Related Features
Counter Name RLC.NbrBlocksReceived.T M Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
RLC.NbrBlocksReceived.A M
WRFD-010510
RLC.NbrBlocksReceived.U M
WRFD-010510
1.10.20.3 Number of Packets Discarded by All RLCs in RNC Counters

Counter ID 67202539 Counter Name RLC.DiscardedBlocksByRNC Counter Description Number of PDUs Discarded by RLCs for RNC
Description
This measurement item takes statistics of the number of packets discarded by all the RLCs in the RNC.
Measurement point
The measurement is triggered when an RLC discards a packet.
Formula
None
Unit
packet
Issue 01 (2013-05-04)
647
Related Features
Counter Name RLC.DiscardedBlocksByRNC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.20.4 Number of Packets Retransmitted by All RLCs in AM Mode in RNC Counters

Counter ID 67202540 Counter Name RLC.RetransmittedBlocksToUE Counter Description Number of PDUs Retransmitted by RLCs for RNC
Description
This counter provides the number of PDUs that are retransmitted by the RLC in AM mode in the RNC. It excludes the number of PDUs that are automatically retransmitted by the RLC.
Measurement point
The measurement is triggered when an RLC in AM mode retransmits a packet.
Formula
None
Unit
packet
Related Features
Counter Name RLC.RetransmittedBlocksToUE Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
648
1.10.20.5 Number of PDUs with the Size Smaller than 336 bit Received by RLCs In Acknowledged Mode Carried by TRB Counters
Counter ID 67204246 Counter Name RLC.NbrBlocksReceived.A M.1 Counter Description Number of PDUs with the Size Smaller than 336 bit Received by RLCs In Acknowledged Mode Carried by TRB
Description
This counter provides the number of PDUs with the size smaller than 336 bit received by RLCs in acknowledged mode carried by the traffic radio bearer (TRB).
Measurement point
This counter is measured at the RNC when RLCs in acknowledge mode carried by the TRB receive a PDU with the size smaller than 336 bit.
Formula
None
Unit
packet
Related Features
Counter Name RLC.NbrBlocksReceived.A M.1 Feature ID WRFD-010695 Feature Name UL Layer 2 Improvement
1.10.20.6 Number of PDUs with the Size Greater than or Equal to 336 bit Received by RLCs In Acknowledged Mode Carried by TRB
Issue 01 (2013-05-04)
649
Counters
Counter ID 67204247 Counter Name RLC.NbrBlocksReceived.A M.2 Counter Description Number of PDUs with the Size Greater than or Equal to 336 bit Received by RLCs In Acknowledged Mode Carried by TRB
Description
This counter provides the number of PDUs with the size greater than or equal to 336 bit received by RLCs in acknowledged mode carried by the traffic radio bearer (TRB).
Measurement point
This counter is measured at the RNC when RLCs in acknowledge mode carried by the TRB receive a PDU with the size greater than or equal to 336 bit.
Formula
None
Unit
packet
Related Features
Counter Name RLC.NbrBlocksReceived.A M.2 Feature ID WRFD-010695 Feature Name UL Layer 2 Improvement
1.10.21 Measurement related to IMS(RNC.IMS)

Overview
A new CN domain, known as IMS domain, is introduced into the system architecture of 3GPP R5. With the UTRAN PS features and PS CN, the IMS domain provides various standard services, such as packet call and IP multimedia conference. In addition, it can also provide real time or approximate real time voice, data and video communications, such as PTT service. Seen from the access network, the IMS service is carried by two PS RABs. One carries the Session Initiation Protocol (SIP) of the IMS signaling, and the other carries IMS application. Both RABs have their own service features.
Counters
Counter ID 67202541 Counter Name VS.RABCmb.Num IMS.Str8.8 VS.RABCmb.Num IMS.Con8.8 Counter Description Number of IMS_PoC Users in the Statistic Period for RNC Number of IMS_VoIP Users in the Statistic Period for RNC Number of IMS Users in the Statistic Period for RNC Number of IMS Users in the Statistic Period for RNC (Signaling at 16kbit/s and Services at 42.8kbit/s) Number of IMS Users in the Statistic Period for RNC (Signaling at 16kbit/s and Services at 32kbit/s) Number of IMS Users in the Statistic Period for RNC (Signaling at 16kbit/s and Services at 64kbit/s) Number of IMS Users in the Statistic Period for RNC (Signaling at 8kbit/s and Services at 16kbit/s) Number of IMS Users in the Statistic Period for RNC (Signaling at 8kbit/s and Services at 32kbit/s) Original Release Earlier than V900R011 Earlier than V900R011
67202542
67202546
VS.IMS.NumSigUs er VS.RABCmb.IMSSigCon16.42.8
67203417
67203418
VS.RABCmb.IMSSigCon16.32
67203419
67203420
67203421
Issue 01 (2013-05-04)
651
Counter ID 67203422
Counter Name VS.RABCmb.IMSSigCon16.16
Counter Description Number of IMS Users in the Statistic Period for RNC (Signaling at 16kbit/s and Services at 16kbit/s)
None
1.10.21.1 Mean Number of UEs Setting Up Different IMS Services Counters

Counter ID 67202541 Counter Name VS.RABCmb.NumIMS.Str8 .8 VS.RABCmb.NumIMS.Con 8.8 VS.RABCmb.IMSSigCon16.42.8 Counter Description Number of IMS_PoC Users in the Statistic Period for RNC Number of IMS_VoIP Users in the Statistic Period for RNC Number of IMS Users in the Statistic Period for RNC (Signaling at 16kbit/s and Services at 42.8kbit/s) Number of IMS Users in the Statistic Period for RNC (Signaling at 16kbit/s and Services at 32kbit/s) Number of IMS Users in the Statistic Period for RNC (Signaling at 16kbit/s and Services at 64kbit/s) Number of IMS Users in the Statistic Period for RNC (Signaling at 8kbit/s and Services at 16kbit/s) Number of IMS Users in the Statistic Period for RNC (Signaling at 8kbit/s and Services at 32kbit/s)
652
67202542
67203417
67203418
67203419
67203420
67203421
Issue 01 (2013-05-04)
Counter ID 67203422
Counter Description Number of IMS Users in the Statistic Period for RNC (Signaling at 16kbit/s and Services at 16kbit/s)
Description
The measurement items provide the mean number of UEs according to different IMS service types in the RNC, as listed in Table
Measurement point
The RNC periodically takes samples from the number of UEs that set up different IMS services every five seconds. At the end of the measurement period, the RNC divides the accumulated number by the number of samples to obtain the mean number of UEs setting up IMS services.
Formula
None
Unit
None
Related Features
Counter Name VS.RABCmb.NumIMS.Str8 .8 VS.RABCmb.NumIMS.Con 8.8 VS.RABCmb.IMSSigCon16.42.8 VS.RABCmb.IMSSigCon16.32 VS.RABCmb.IMSSigCon16.64 VS.RABCmb.IMSSigCon8.16 VS.RABCmb.IMSSigCon8.32 Feature ID WRFD-010617 WRFD-010617 WRFD-010617 WRFD-010617 WRFD-010617 WRFD-010617 WRFD-010617 Feature Name VoIP over HSPA/HSPA+ VoIP over HSPA/HSPA+ VoIP over HSPA/HSPA+ VoIP over HSPA/HSPA+ VoIP over HSPA/HSPA+ VoIP over HSPA/HSPA+ VoIP over HSPA/HSPA+
Issue 01 (2013-05-04)
653
Feature Name VoIP over HSPA/HSPA+
1.10.21.2 Number of UEs Setting Up IMS Services Counters

Counter ID 67202546 Counter Name VS.IMS.NumSigUser Counter Description Number of IMS Users in the Statistic Period for RNC
Description
This measurement item provides the number of UEs setting up IMS services in the RNC.
Measurement point
The RNC periodically takes samples from the number of UEs that setting up IMS services every five seconds. At the end of the measurement period, the RNC divides the accumulated number by the number of samples to obtain the mean number of UEs setting up IMS services.
Formula
None
Unit
None
Related Features
Counter Name VS.IMS.NumSigUser Feature ID WRFD-010617 Feature Name VoIP over HSPA/HSPA+
1.10.22 RRC connection release measurement per RNC (RRC.Rel.RNC)

Overview
When the RNC release a RRC connection, it sends a RRC CONNECTION RELEASE message to the UE to release the resources related to the UE. The RRC connection release measurement
counts the RRC connection release messages of the entire RNC by the RRC connection release cause.
Counters
Counter ID 67174454 Counter Name VS.RRC.AttConnR el.RNC VS.RRC.AttConnR el.Norm.RNC Counter Description Number of RRC Connection Releases for RNC Number of RRC Connection Releases due to Normal Event for RNC Number of RRC Connection Releases due to Congestion for RNC Number of RRC Connection Releases due to Preemption for RNC Number of RRC Connection Releases due to User Inactivity for RNC Number of RRC Connection Releases due to Reestablishment Reject for RNC Number of RRC Connection Releases due to Directed Signaling Connection Reestablishment for RNC Number of RRC Connection Releases due to Unspecified Causes for RNC Original Release Earlier than V900R011 Earlier than V900R011
67174641
67190072
VS.RRC.AttConnR el.Cong.RNC
67190073
VS.RRC.AttConnR el.Preempt.RNC
67190074
VS.RRC.AttConnR el.UsrInact.RNC
67190075
VS.RRC.AttConnR el.ReEstRej.RNC
67190076
VS.RRC.AttConnR el.DSCR.RNC
67174647
VS.RRC.AttConnR el.Unspec.RNC
Issue 01 (2013-05-04)
655
Counter ID 73421937
Counter Name VS.RRC.AttConRe l.SCRI.DF2P.NoRe ply.RNC
Counter Description Number of RRC Releases Due to Failure in the UE State Transition to CELL_PCH Triggered by Signaling Connection Release Indication Number of RRC Connection Releases Triggered by SRNC Due to DSCR Number of RRC Connection Releases Triggered by DRNC Due to DSCR
73423382
VS.RRC.AttConnR el.DSCR.SRNC
V900R013
73423383
VS.RRC.AttConnR el.DSCR.DRNC
V900R013
None
1.10.22.1 Number of RRC Connection Releases Counters

Counter ID 67174454 Counter Name VS.RRC.AttConnRel.RNC Counter Description Number of RRC Connection Releases for RNC
Description
When the network side needs to release a RRC connection because of a certain cause, for example, the call ends, the RRC connection sends a RRC CONNECTION RELEASE message to the UE. This counter provides the number of RRC CONNECTION RELEASE messages sent by the RNC to the UE.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends a RRC CONNECTION RELEASE message to the UE, this counter is measured.
Figure 1-285 RRC connection release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnRel.RNC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.22.2 Counters Related to the Number of RRC Connection Releases due to Different Causes
Issue 01 (2013-05-04)
657
Counters
Counter ID 67174641 Counter Name VS.RRC.AttConnRel.Norm. RNC VS.RRC.AttConnRel.Cong. RNC VS.RRC.AttConnRel.Preem pt.RNC VS.RRC.AttConnRel.UsrIn act.RNC VS.RRC.AttConnRel.ReEst Rej.RNC Counter Description Number of RRC Connection Releases due to Normal Event for RNC Number of RRC Connection Releases due to Congestion for RNC Number of RRC Connection Releases due to Preemption for RNC Number of RRC Connection Releases due to User Inactivity for RNC Number of RRC Connection Releases due to Reestablishment Reject for RNC Number of RRC Connection Releases due to Directed Signaling Connection Reestablishment for RNC Number of RRC Connection Releases due to Unspecified Causes for RNC
67190072
67190073
67190074
67190075
67190076
VS.RRC.AttConnRel.DSCR .RNC
67174647
VS.RRC.AttConnRel.Unspe c.RNC
Description
These counters provide the number of RRC CONNECTION RELEASE messages with certain causes sent by the RNC to the UE.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC initiates the RRC connection release procedure, the RNC sends a RRC CONNECTION RELEASE message to the UE. These counters are measured on the RNC side when a RRN CONNECTION RELEASE message with the corresponding cause is sent to the UE. For details, see section 10.3.3.32 in 3GPP TS 25.331.
Issue 01 (2013-05-04)
658
Figure 1-286 RRC connection release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnRel.Norm. RNC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Queuing and Pre-Emption 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
659
VS.RRC.AttConnRel.Cong. RNC
WRFD-010510
VS.RRC.AttConnRel.Preem pt.RNC
WRFD-010505 WRFD-010510
Issue 01 (2013-05-04)
Counter Name VS.RRC.AttConnRel.UsrIn act.RNC
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Direct Signaling Connection Re-establishment (DSCR) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RRC.AttConnRel.ReEst Rej.RNC
WRFD-010510
VS.RRC.AttConnRel.DSCR .RNC
WRFD-021400 WRFD-010510
VS.RRC.AttConnRel.Unspe c.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.22.3 Number of RRC Releases Due to Failure in the UE State Transition to CELL_PCH Triggered by Signaling Connection Release Indication Counters
Counter ID 73421937 Counter Name VS.RRC.AttConRel.SCRI.D F2P.NoReply.RNC Counter Description Number of RRC Releases Due to Failure in the UE State Transition to CELL_PCH Triggered by Signaling Connection Release Indication
Description
This counter provides the number of times that an RRC connection is released because no UE response is received after the RNC sends a RADIO BEAR RECONFIGURATION or PHYSICAL CHANNEL RECONFIGURATION message to the UE, instructing the UE to transfer to the CELL_PCH state.
Measurement point
The measurement is triggered at point A as shown in the figure. After receiving the SIGNALLING CONNECTION RELEASE INDICATION message from the UE, the RNC
sends a RADIO BEAR RECONFIGURATION or PHYSICAL CHANNEL RECONFIGURATION message to the UE, instructing the UE to transfer to the CELL_PCH state. If no response from the UE is received before the timer expires, the RNC releases the RRC connection and measure this counter. Figure 1-287 RB reconfiguration or Physical Channel reconfiguration failure procedure (UE no response)
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConRel.SCRI.D F2P.NoReply.RNC Feature ID WRFD-020500 Feature Name Enhanced Fast Dormancy
1.10.22.4 Number of RRC Connection Releases Triggered by SRNC Due to DSCR
Issue 01 (2013-05-04)
661
Counters
Counter ID 73423382 Counter Name VS.RRC.AttConnRel.DSCR .SRNC Counter Description Number of RRC Connection Releases Triggered by SRNC Due to DSCR
Description
This counter provides the number of RRC CONNECTION RELEASE messages sent by the SRNC to the UE because of Directed Signaling Connection Re-establishment (DSCR).
Measurement point
The measurement is triggered at point A as shown in the figure, when the SRNC sends the UE an RRC CONNECTION RELEASE message because of DSCR. Figure 1-288 RRC connection release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnRel.DSCR .SRNC Feature ID WRFD-021400 WRFD-010510 Feature Name Direct Signaling Connection Re-establishment (DSCR) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.22.5 Number of RRC Connection Releases Triggered by DRNC Due to DSCR Counters
Counter ID 73423383 Counter Name VS.RRC.AttConnRel.DSCR .DRNC Counter Description Number of RRC Connection Releases Triggered by DRNC Due to DSCR
Description
This counter provides the number of RRC CONNECTION RELEASE messages sent by the DRNC to the UE because of Directed Signaling Connection Re-establishment (DSCR).
Measurement point
The measurement is triggered at point A as shown in the figure, when the DRNC sends the UE an RRC CONNECTION RELEASE message because of DSCR. Figure 1-289 RRC connection release procedure
Issue 01 (2013-05-04)
663
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnRel.DSCR .DRNC Feature ID WRFD-021400 WRFD-010510 Feature Name Direct Signaling Connection Re-establishment (DSCR) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.23 RRC connection setup measurement per RNC (RRC.Setup.RNC)

Overview
When an UE needs to access the network, setting up the RRC connection is the first step. From the cell where the UE is located, the UE sends a RRC CONNECTION REQUEST message to request network access. After receiving the RRC CONNECTION REQUEST message, the RNC initiates the admission procedure and allocates relevant resources to the UE. Following successful allocation of resources, the RNC sends a RRC CONNECTION SETUP message to the UE and waits for a RRC CONNECTION SETUP COMPLETE message, a response message from the UE. When the RNC receives a RRC CONNECTION SETUP COMPLETE message, the procedure for RRC connection setup is finished. For more details, see 3GPP TS 25.331. The number of RRC connection setup attempts and rejects does not include service-based redirections, inter-RAT and inter-frequency distance-based redirections, and macro & micro joint inter-frequency redirections. During the resource admission and radio link setup process, if DRD is configured when resource admission and radio link setup fail and the configured DRD succeeds, the measurement is triggered in the target cell for the UE. If the configured DRD fails, the measurement is triggered in the source cell for the UE. Note that the measurement is not triggered for RRC CONNECTION REQUEST messages retransmitted by the UE. The following figure shows the measurement points of the counters.
Issue 01 (2013-05-04)
664
Figure 1-290 Flow chart of RRC connection setup
Issue 01 (2013-05-04)
665
Table 1 describes the measurement points shown in Figure1. Measurement points A Description VS.RRC.AttConnEstab.RNC,VS.RRC.AttC onnEstab.Msg.RNC,VS.RRC.AttConnEstab .CellDCH.RNC,VS.RRC.AttConnEstab.Cel lFACH.RNC See:RRC.Setup.Cell VS.RRC.SuccConnEstab.RNC,VS.RRC.Su ccConnEstab.CellFACH.RNC,VS.RRC.Suc cConnEstab.CellDCH.RNC See:RRC.Setup.Cell See:RRC.SetupFail.Cell
B C
D E~L
Counters
Counter ID 67174450 Counter Name VS.RRC.AttConnE stab.RNC VS.RRC.AttConnE stab.Msg.RNC Counter Description Number of RRC Connection Requests Processed by RNC Total Number of RRC Connection Requests Received by RNC Number of RRC Connection Requests for RNC (UE Target State of CELL_DCH) Number of RRC Connection Requests for RNC (UE Target State of CELL_FACH) Number of Successful RRC Connection Establishments for RNC Original Release Earlier than V900R011 Earlier than V900R011
67174449
67174689
VS.RRC.AttConnE stab.CellDCH.RNC
67174705
VS.RRC.AttConnE stab.CellFACH.RN C
67174452
VS.RRC.SuccConn Estab.RNC
Issue 01 (2013-05-04)
666
Counter ID 67174706
Counter Name VS.RRC.SuccConn Estab.CellFACH.R NC
Counter Description Number of Successful RRC Connection Establishments on CELL_FACH Number of Successful RRC Connection Establishments on CELL_DCH
67174691
VS.RRC.SuccConn Estab.CellDCH.RN C
Counter VS.RRC.AttConnEstab.Msg.RNC VS.RRC.AttConnEstab.RNC Sub Counter VS.RRC.AttConnEstab.RNC VS.RRC.AttConnEstab.CellDCH.RNC VS.RRC.AttConnEstab.CellFACH.RNC VS.RRC.SuccConnEstab.RNC VS.RRC.SuccConnEstab.CellFACH.RNC VS.RRC.SuccConnEstab.CellDCH.RNC
1.10.23.1 Counters Related to the Number of RRC Connection Requests Processed by RNC Counters
Counter ID 67174450 67174689 Counter Name VS.RRC.AttConnEstab.RN C VS.RRC.AttConnEstab.Cell DCH.RNC VS.RRC.AttConnEstab.Cell FACH.RNC Counter Description Number of RRC Connection Requests Processed by RNC Number of RRC Connection Requests for RNC (UE Target State of CELL_DCH) Number of RRC Connection Requests for RNC (UE Target State of CELL_FACH)
67174705
Issue 01 (2013-05-04)
667
Description
These counters provide the number of RRC CONNECTION REQUEST messages actually processed by the RNC after the RNC receives the messages from the UE. These counters exclude the number of rejected RRC connection requests caused by service-based redirection, inter-RAT and inter-frequency distance-based redirection, or macro & micro joint inter-frequency redirection.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a RRC CONNECTION REQUEST message from the UE. These counters exclude the number of rejected RRC connection requests caused by service-based redirection, inter-RAT and interfrequency distance-based redirection, or macro & micro joint inter-frequency redirection. Note that the measurement is not triggered for a RRC CONNECTION REQUEST message that is retransmitted by the UE. Figure 1-291 Procedure for successful RRC connection setup
Formula
None
Unit
None
Issue 01 (2013-05-04)
668
Related Features
Counter Name VS.RRC.AttConnEstab.RN C Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RRC.AttConnEstab.Cell DCH.RNC
WRFD-010510
VS.RRC.AttConnEstab.Cell FACH.RNC
WRFD-010510
1.10.23.2 Total Number of RRC Connection Requests Received by RNC Counters

Counter ID 67174449 Counter Name VS.RRC.AttConnEstab.Msg .RNC Counter Description Total Number of RRC Connection Requests Received by RNC
Description
This counter provides the total number of RRC CONNECTION REQUEST messages received by the RNC from the UE, including the retransmitted ones.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a RRC CONNECTION REQUEST message from the UE. Note that the UE may send a RRC CONNECTION REQUEST message for several times to increase the access rate. The retransmitted RRC CONNECTION REQUEST messages from the UE are all measured by the RNC.
Issue 01 (2013-05-04)
669
Figure 1-292 Procedure for successful RRC connection setup
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnEstab.Msg .RNC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.10.23.3 Counters Related to the Number of Successful RRC Connection Establishments
Issue 01 (2013-05-04)
670
Counters
Counter ID 67174452 Counter Name VS.RRC.SuccConnEstab.R NC VS.RRC.SuccConnEstab.Ce llFACH.RNC VS.RRC.SuccConnEstab.Ce llDCH.RNC Counter Description Number of Successful RRC Connection Establishments for RNC Number of Successful RRC Connection Establishments on CELL_FACH Number of Successful RRC Connection Establishments on CELL_DCH
67174706
67174691
Description
These counters provide the number of RRC CONNECTION SETUP COMPLETE messages sent from the UE to the RNC.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC receives a RRC CONNECTION SETUP COMPLETE message from the UE. Figure 1-293 Procedure for successful RRC connection setup
Issue 01 (2013-05-04)
671
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.SuccConnEstab.R NC Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RRC.SuccConnEstab.Ce llFACH.RNC
WRFD-010510
VS.RRC.SuccConnEstab.Ce llDCH.RNC
WRFD-010510
1.10.24 RRC state measurement(RRC.STATE)

Overview
This function subset provides the average number of UEs in different RRC connection states in the RNC.
Counters
Counter ID 67199465 Counter Name VS.CellDCHUEs.R NC VS.CellFACHUEs. RNC VS.CellPCHUEs.R NC Counter Description Number of UEs in CELL_DCH State for RNC Number of UEs in CELL_FACH State for RNC Number of UEs in CELL_PCH State for RNC Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67199466
67199467
Issue 01 (2013-05-04)
672
Counter ID 67199468
Counter Name VS.UraPCHUEs.R NC VS.UraPCHUEs.P TT.RNC
Counter Description Number of UEs in URA_PCH State for RNC Average Number of PTT UEs with RRC Connection State of URA_PCH for RNC Average Number of UEs in the URA_PCH State and Carried on the EPCH for RNC
73410506
73441130
VS.UraEPCHUEs. RNC
V900R013
None
1.10.24.1 Counters Related to the Number of UEs in Different RRC Connection States for RNC Counters
Counter ID 67199465 67199466 67199467 67199468 Counter Name VS.CellDCHUEs.RNC VS.CellFACHUEs.RNC VS.CellPCHUEs.RNC VS.UraPCHUEs.RNC Counter Description Number of UEs in CELL_DCH State for RNC Number of UEs in CELL_FACH State for RNC Number of UEs in CELL_PCH State for RNC Number of UEs in URA_PCH State for RNC
Description
These counters provide the number of UEs in different RRC connection states in the RNC.
Measurement point
The system periodically takes samples of the number of UEs in each RRC connection state every five seconds. At the end of the measurement period, by dividing the accumulated value of sample
data in the period by the number of samples, the average number of UEs in each RRC connection state in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Name VS.CellDCHUEs.RNC Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
VS.CellFACHUEs.RNC
WRFD-010202
VS.CellPCHUEs.RNC
WRFD-010202
VS.UraPCHUEs.RNC
WRFD-010202
1.10.24.2 Number of PTT UEs in URA_PCH State for RNC Counters

Counter ID 73410506 Counter Name VS.UraPCHUEs.PTT.RNC Counter Description Average Number of PTT UEs with RRC Connection State of URA_PCH for RNC
Description
This counter provides the numbers of PTT UEs in URA_PCH state in the RNC.
Measurement point
The system periodically takes samples of the number of PTT UEs in the RRC connection state of URA_PCH every five seconds. At the end of the measurement period, the value of this counter is obtained by dividing the accumulated value of UE number by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.UraPCHUEs.PTT.RNC Feature ID WRFD-010202 WRFD-020134 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Push to Talk
1.10.24.3 Average Number of UEs in the URA_PCH State and Carried on the EPCH for RNC Counters
Counter ID 73441130 Counter Name VS.UraEPCHUEs.RNC Counter Description Average Number of UEs in the URA_PCH State and Carried on the EPCH for RNC
Description
This counter provides the average number of UEs that are in the URA_PCH state and use the EPCH function under an RNC.
Measurement point
UEs that are in the URA_PCH state and use the EPCH function are sampled at a certain interval every five seconds. At the end of a measurement period, this counter measured at each sampling site is calculated by dividing the accumulated number of the UEs by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name VS.UraEPCHUEs.RNC Feature ID WRFD-020134 Feature Name Push to Talk
1.10.25 Soft Handover Measurement per RNC(SHO.RNC)

Overview
Soft handover is the procedure during which a radio link is added to or deleted from the active set. When an UE moves or the radio link quality fluctuates, the RNC adds a radio link to the active set if the RNC detects that the cell of the radio link is of good signal quality. If the quality of a radio link in a cell in the active set becomes lower than the predefined threshold, the RNC deletes this radio link from the active set. A soft handover is considered as a softer handover if the two radio links of the UE connection are established with cells belonging to the same NodeB. The RNC determines whether to perform soft handover based on the intra-frequency measurement of the UE. When the RNC receives a measurement report (MR) from the UE and determines that a soft handover is required, it sends an ACTIVE SET UPDATE message to the UE, and starts a timer to wait for the response from the UE. If the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE before the timer expires, the soft handover is considered successful. If the RNC receives an ACTIVE SET UPDATE FAILURE message from the UE or does not receive any message from the UE before the timer expires, the soft handover is considered as a failure.
Counters
Counter ID 67175268 Counter Name VS.SoHO.Att.RNC Counter Description Number of Softer Handovers Initiated by RNC for RNC Number of Soft Handovers Initiated by RNC for RNC Number of Successful Soft Handovers Initiated by RNC for RNC Number of Successful Softer Handovers Initiated by RNC for RNC Mean Number of UEs with One Radio Link for RNC Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67175266
VS.SHO.Att.RNC
67175267
VS.SHO.Succ.RNC
67175269
VS.SoHO.Succ.RN C
67199432
VS.SHO.AS.1.RNC
Issue 01 (2013-05-04)
676
Counter ID 67199434
Counter Name VS.SHO.AS. 2Soft.RNC
Counter Description Mean Number of UEs with Two Uncombined Radio Links for RNC Mean Number of UEs with Three Radio Links and Two Combined for RNC Mean Number of UEs with Three Uncombined Radio Links for RNC Mean Number of UEs with Two Combined Radio Links for RNC Mean Number of UEs with Three Combined Radio Links for RNC Mean Number of UEs with Four Radio Links for RNC Mean Number of UEs with Five Radio Links for RNC Mean Number of UEs with Six Radio Links for RNC Number of Call Drops Due to Soft Handover Failures for RNC
67199437
VS.SHO.AS. 3Soft2Softer.RNC
67199436
VS.SHO.AS. 3Soft.RNC
67199433
VS.SHO.AS. 2Softer.RNC
67199435
VS.SHO.AS. 3Softer.RNC
67203933
VS.SHO.AS.4.RNC
Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67203934
VS.SHO.AS.5.RNC
67203935
VS.SHO.AS.6.RNC
67175283
VS.SHO.Drop.RN C
None
1.10.25.1 Number of Softer Handover Attempts
Issue 01 (2013-05-04)
677
Counters
Counter ID 67175268 Counter Name VS.SoHO.Att.RNC Counter Description Number of Softer Handovers Initiated by RNC for RNC
Description
This counter provides the number of softer handover attempts in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure. This counter is incremented by one each time the RNC sends an ACTIVE SET UPDATE message to the UE during the softer handover procedure. Figure 1-294 Successful soft handover procedure
Formula
None
Issue 01 (2013-05-04)
678
Unit
None
Related Features
Counter Name VS.SoHO.Att.RNC Feature ID WRFD-020201 WRFD-020202 Feature Name Intra Node B Softer Handover Intra RNC Soft Handover
1.10.25.2 Number of Soft Handover Attempts Counters

Counter ID 67175266 Counter Name VS.SHO.Att.RNC Counter Description Number of Soft Handovers Initiated by RNC for RNC
Description
This counter provides the number of soft handover (including softer handover) attempts in the RNC.
Measurement point
The measurement is triggered at point B, as shown in the figure. This counter is incremented by one each time the RNC sends an ACTIVE SET UPDATE message to the UE during the soft handover (including the softer handover) procedure.
Issue 01 (2013-05-04)
679
Figure 1-295 Successful soft handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.Att.RNC Feature ID WRFD-020202 WRFD-020203 Feature Name Intra RNC Soft Handover Inter RNC Soft Handover
1.10.25.3 Number of Successful Soft Handovers
Issue 01 (2013-05-04)
680
Counters
Counter ID 67175267 Counter Name VS.SHO.Succ.RNC Counter Description Number of Successful Soft Handovers Initiated by RNC for RNC
Description
This counter provides the number of successful soft handovers (including softer handovers) in the RNC.
Measurement point
The measurement is triggered at point C, as shown in the figure. Each time the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover (including the softer handover) procedure, the soft handover is considered as successful, and the RNC measures the item. Figure 1-296 Successful soft handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.Succ.RNC Feature ID WRFD-020202 WRFD-020203 Feature Name Intra RNC Soft Handover Inter RNC Soft Handover
1.10.25.4 Number of Successful Softer Handovers Counters

Counter ID 67175269 Counter Name VS.SoHO.Succ.RNC Counter Description Number of Successful Softer Handovers Initiated by RNC for RNC
Description
This counter provides the number of successful softer handovers in the RNC.
Measurement point
The measurement is triggered at point C, as shown in the figure. Each time the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the softer handover procedure, the softer handover is considered as successful, and the RNC measures the item.
Issue 01 (2013-05-04)
682
Figure 1-297 Successful soft handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.SoHO.Succ.RNC Feature ID WRFD-020201 WRFD-020202 Feature Name Intra Node B Softer Handover Intra RNC Soft Handover
1.10.25.5 Mean Number of UEs with One to Six Radio Link
Issue 01 (2013-05-04)
683
Counters
Counter ID 67199432 67199434 Counter Name VS.SHO.AS.1.RNC VS.SHO.AS.2Soft.RNC Counter Description Mean Number of UEs with One Radio Link for RNC Mean Number of UEs with Two Uncombined Radio Links for RNC Mean Number of UEs with Three Radio Links and Two Combined for RNC Mean Number of UEs with Three Uncombined Radio Links for RNC Mean Number of UEs with Two Combined Radio Links for RNC Mean Number of UEs with Three Combined Radio Links for RNC Mean Number of UEs with Four Radio Links for RNC Mean Number of UEs with Five Radio Links for RNC Mean Number of UEs with Six Radio Links for RNC
67199437
VS.SHO.AS. 3Soft2Softer.RNC VS.SHO.AS.3Soft.RNC
67199436
67199433
VS.SHO.AS.2Softer.RNC
67199435
VS.SHO.AS.3Softer.RNC
67203933 67203934 67203935
VS.SHO.AS.4.RNC VS.SHO.AS.5.RNC VS.SHO.AS.6.RNC
Description
These counters provide the mean number of UEs with one to six radio links (RLs) in an RNC. The mean number of UEs with two or three RLs is measured with consideration of the number of combined RLs at the NodeB.
Measurement point
The RNC takes samples of the number of UEs with one to six radio links every five seconds in a measurement period. At the end of the measurement period, the RNC divides the accumulated numbers by the number of samples to obtain the mean number of UEs with one to six RLs in the measurement period in the RNC.
Formula
None
Issue 01 (2013-05-04)
684
Unit
None
Related Features
Counter Name VS.SHO.AS.1.RNC Feature ID WRFD-020202 WRFD-020203 VS.SHO.AS.2Soft.RNC WRFD-020202 WRFD-020203 VS.SHO.AS. 3Soft2Softer.RNC VS.SHO.AS.3Soft.RNC WRFD-020202 WRFD-020203 WRFD-020202 WRFD-020203 VS.SHO.AS.2Softer.RNC WRFD-020202 WRFD-020203 VS.SHO.AS.3Softer.RNC WRFD-020202 WRFD-020203 VS.SHO.AS.4.RNC WRFD-020202 WRFD-020203 VS.SHO.AS.5.RNC WRFD-020202 WRFD-020203 VS.SHO.AS.6.RNC WRFD-020202 WRFD-020203 Feature Name Intra RNC Soft Handover Inter RNC Soft Handover Intra RNC Soft Handover Inter RNC Soft Handover Intra RNC Soft Handover Inter RNC Soft Handover Intra RNC Soft Handover Inter RNC Soft Handover Intra RNC Soft Handover Inter RNC Soft Handover Intra RNC Soft Handover Inter RNC Soft Handover Intra RNC Soft Handover Inter RNC Soft Handover Intra RNC Soft Handover Inter RNC Soft Handover Intra RNC Soft Handover Inter RNC Soft Handover
1.10.25.6 Number of Call Drops due to Soft Handover Failures Counters

Counter ID 67175283 Counter Name VS.SHO.Drop.RNC Counter Description Number of Call Drops Due to Soft Handover Failures for RNC
Description
This counter provides the number of call drops caused by soft handover failures in the RNC.
Measurement point
The measurement is triggered at point A, as shown in the figure. During the soft handover (including the softer handover), when the RNC sends an ACTIVE SET UPDATE message to the UE, it starts a timer to wait for the response from the UE. If the RNC does not receive the response before the timer expires, it releases the corresponding RRC connection, which results in a call drop. In this case, this counter is incremented by one. Figure 1-298 A failed soft handover (timer expiry)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.Drop.RNC Feature ID WRFD-020202 WRFD-020201 WRFD-020203 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover Inter RNC Soft Handover
Issue 01 (2013-05-04)
686
1.10.26 Measurement related to Security mode per RNC(SM.RNC)

Overview
The security mode control procedure is to send encryption and integrity protection information to the UTRAN. With the information, the UTRAN can encrypt user data and signaling data, and provide integrity protection for signaling data.
Counters
Counter ID 67190317 Counter Name VS.IU.AttSecMode Counter Description Number of SECURITY MODE COMMAND Messages Received by RNC from CN Number of SECURITY MODE COMPLETE Messages Sent by RNC to CN Number of SECURITY MODE REJECT Messages Sent by RNC to CN (Radio Network Layer Cause) Number of SECURITY MODE REJECT Messages Sent by RNC to CN (Transport Layer Cause) Number of SECURITY MODE REJECT Messages Sent by RNC to CN (NAS Cause) Number of SECURITY MODE REJECT Messages Sent by RNC to CN (Unspecified Failure) Original Release Earlier than V900R011
67190318
VS.IU.SuccSecMode
67190319
VS.IU.RejSecMd.R nl
67190320
VS.IU.RejSecMd.T nl
67190321
VS.IU.RejSecMd.N AS
67190323
VS.IU.RejSecMd.U nsp
Issue 01 (2013-05-04)
687
Counter ID 67190324
Counter Name VS.UU.AttSecMod e
Counter Description Number of SECURITY MODE COMMAND Messages Sent by RNC to UE Number of SECURITY MODE COMPLETE Messages Received by RNC from UE
67190325
VS.UU.SuccSecMode
None
1.10.26.1 Number of SECURITY MODE COMMAND Messages Received by RNC from CN Counters
Counter ID 67190317 Counter Name VS.IU.AttSecMode Counter Description Number of SECURITY MODE COMMAND Messages Received by RNC from CN
Description
This measurement item takes statistics of the number of SECURITY MODE COMMAND messages that the RNC receives from the CN.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives a SECURITY MODE COMMAND message from the CN, the RNC measures this item.
Issue 01 (2013-05-04)
688
Figure 1-299 Security mode control procedure (CN to RNC)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.AttSecMode Feature ID WRFD-011401 Feature Name Integrity Protection
1.10.26.2 Number of SECURITY MODE COMPLETE Messages Sent from RNC to CN
Issue 01 (2013-05-04)
689
Counters
Counter ID 67190318 Counter Name VS.IU.SuccSecMode Counter Description Number of SECURITY MODE COMPLETE Messages Sent by RNC to CN
Description
This measurement item takes statistics of the number of SECURITY MODE COMPLETE messages that the RNC sends to the CN.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends a SECURITY MODE COMPLETE message to the CN, the RNC measures this item. Figure 1-300 Security mode control procedure (CN to RNC)
Formula
None
Unit
None
Related Features
Counter Name VS.IU.SuccSecMode Feature ID WRFD-011401 Feature Name Integrity Protection
1.10.26.3 Number of SECURITY MODE REJECT Messages Sent from RNC to CN for Different Causes Counters
Counter ID 67190319 Counter Name VS.IU.RejSecMd.Rnl Counter Description Number of SECURITY MODE REJECT Messages Sent by RNC to CN (Radio Network Layer Cause) Number of SECURITY MODE REJECT Messages Sent by RNC to CN (Transport Layer Cause) Number of SECURITY MODE REJECT Messages Sent by RNC to CN (NAS Cause) Number of SECURITY MODE REJECT Messages Sent by RNC to CN (Unspecified Failure)
67190320
VS.IU.RejSecMd.Tnl
67190321
VS.IU.RejSecMd.NAS
67190323
VS.IU.RejSecMd.Unsp
Description
These measurement items take statistics of the number of SECURITY MODE REJECT messages that the RNC sends to the CN according to different causes.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends the CN a SECURITY MODE REJECT message, the RNC measures these items according to different failure causes.
Issue 01 (2013-05-04)
691
Figure 1-301 Security mode rejection procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IU.RejSecMd.Rnl VS.IU.RejSecMd.Tnl VS.IU.RejSecMd.NAS VS.IU.RejSecMd.Unsp Feature ID WRFD-011401 WRFD-011401 WRFD-011401 WRFD-011401 Feature Name Integrity Protection Integrity Protection Integrity Protection Integrity Protection
1.10.26.4 Number of SECURITY MODE COMMAND Messages Sent from RNC to UE
Issue 01 (2013-05-04)
692
Counters
Counter ID 67190324 Counter Name VS.UU.AttSecMode Counter Description Number of SECURITY MODE COMMAND Messages Sent by RNC to UE
Description
This measurement item takes statistics of the number of SECURITY MODE COMMAND messages that the RNC sends to the UE.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends a SECURITY MODE COMMAND message to the UE, the RNC measures this item. Figure 1-302 Security mode control procedure (RNC to UE)
Formula
None
Unit
None
Related Features
Counter Name VS.UU.AttSecMode Feature ID WRFD-011401 Feature Name Integrity Protection
1.10.26.5 Number of SECURITY MODE COMPLETE Messages Received by RNC from UE Counters
Counter ID 67190325 Counter Name VS.UU.SuccSecMode Counter Description Number of SECURITY MODE COMPLETE Messages Received by RNC from UE
Description
This measurement item takes statistics of the number of SECURITY MODE COMPLETE messages that the RNC receives from the UE.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC receives a SECURITY MODE COMPLETE message from the UE, the RNC measures this item. Figure 1-303 Security mode control procedure (RNC to UE)
Issue 01 (2013-05-04)
694
Formula
None
Unit
None
Related Features
Counter Name VS.UU.SuccSecMode Feature ID WRFD-011401 Feature Name Integrity Protection
1.10.27 Traffic Measurement per RNC(TRAFF.LOAD.RNC)

Overview
The RNC traffic measurement is used to measure the traffic of the CS domain and PS domain in the RNC. Here, the traffic of the CS domain is indicated by equivalent Erlang while the traffic of the PS domain by kbit per second.
Counters
Counter ID 67202970 Counter Name VS.CSLoad.Erlang .Equiv.RNC VS.CSLoad.MaxEr lang.Equiv.RNC Counter Description Equivalent CS Conversational Erlang for RNC Maximum equivalent CS Conversational Erlang for RNC Throughput of Uplink PS R99 Traffic for RNC Maximum Throughput of Uplink PS R99 Traffic for RNC Throughput of Downlink PS R99 Traffic for RNC Original Release Earlier than V900R011 Earlier than V900R011
67192086
67204135
VS.R99PSLoad.UL Thruput.RNC VS.R99PSLoad.Ma xULThruput.RNC
67192985
67204136
VS.R99PSLoad.DL Thruput.RNC
Issue 01 (2013-05-04)
695
Counter ID 67192988
Counter Name VS.R99PSLoad.Ma xDLThruput.RNC
Counter Description Maximum Throughput of Downlink PS R99 Traffic for RNC Throughput of PS HSDPA Traffic for RNC Maximum Throughput of PS HSDPA Traffic for RNC Throughput of PS HSUPA Traffic for RNC Maximum Throughput of PS HSUPA Traffic for RNC Throughput of PS MBMS Traffic for RNC Maximum Throughput of PS MBMS Traffic for RNC Average Total Throughout of UL and DL PS Services for RNC Maximum Total Throughout of UL and DL PS Services for RNC Erlang of CS Services for RNC
67204137
VS.HSDPAPSLoad .DLThruput.RNC VS.HSDPAPSLoad .MaxDLThruput.R NC VS.HSUPAPSLoad .ULThruput.RNC VS.HSUPAPSLoad .MaxULThruput.R NC VS.MBMSPSLoad. DLThruput.RNC VS.MBMSPSLoad. MaxDLThruput.R NC VS.PSLoad.Thrup ut.RNC
67192991
67204138
67192994
67204139
67192997
73410501
V900R012
73394059
VS.PSLoad.MaxTh ruput.RNC
V900R012
73394070
VS.CS.Erlang.RNC
V900R012
None
1.10.27.1 Equivalent Erlang of CS Domain in RNC

Counters
Counter ID 67202970 Counter Name VS.CSLoad.Erlang.Equiv.R NC Counter Description Equivalent CS Conversational Erlang for RNC
Description
This measurement item provides the equivalent Erlang values of all the services in the CS domain in the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The RNC periodically takes the samples from the equivalent Erlang values of all the services in the CS domain every five seconds. At the end of the measurement period, the RNC divides the accumulated equivalent Erlang values by the number of samples to obtain the mean equivalent Erlang values of all the services in the CS domain, include the equivalent Erlang of all radio links of Soft Handover.Each time a CS domain service is established, the RNC converts its rate to the equivalent Erlang, and then increases the equivalent Erlang of the CS domain in the current RNC. Each time a CS domain service is released, the RNC converts its rate to the equivalent Erlang and decreases the equivalent Erlang of the CS domain in the current RNC.
Formula
None
Unit
Erl
Related Features
Counter Name VS.CSLoad.Erlang.Equiv.R NC Feature ID MRFD-210403 Feature Name License Management
1.10.27.2 Maximum Equivalent Erlang of CS Domain in RNC
Issue 01 (2013-05-04)
697
Counters
Counter ID 67192086 Counter Name VS.CSLoad.MaxErlang.Equ iv.RNC Counter Description Maximum equivalent CS Conversational Erlang for RNC
Description
This measurement item provides the maximum equivalent Erlang values of all the services in the CS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the equivalent Erlang values of all the services in the CS domain every five seconds. At the end of the period, the RNC calculates the maximum equivalent Erlang of all the services in the CS domain within the RNC, include the equivalent Erlang of all radio links of Soft Handover.Each time a CS domain service is established, the RNC converts its rate to the equivalent Erlang, and then increases the equivalent Erlang of the CS domain in the current RNC. Each time a CS domain service is released, the RNC decreases the equivalent Erlang of the CS domain in the current RNC.
Formula
None
Unit
Erl
Related Features
Counter Name VS.CSLoad.MaxErlang.Equ iv.RNC Feature ID MRFD-210403 Feature Name License Management
1.10.27.3 UL Traffic of R99 PS Domain in RNC Counters

Counter ID 67204135 Counter Name VS.R99PSLoad.ULThruput. RNC Counter Description Throughput of Uplink PS R99 Traffic for RNC
Issue 01 (2013-05-04)
698
Description
This measurement item provides the uplink traffic of all the R99 services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the uplink traffic values of all the R99 services in the PS domain every five seconds. At the end of the measurement period, the RNC divides the accumulated values by the number of samples to obtain the mean uplink traffic of all the R99 services in the PS domain.The mean uplink traffic of all the R99 services in the PS domain is the traffic measured at the RLC layer. The RLC header data is not included and the soft handover traffic is included.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.R99PSLoad.ULThruput. RNC Feature ID MRFD-210403 Feature Name License Management
1.10.27.4 Maximum UL Traffic of R99 PS Domain in RNC Counters

Counter ID 67192985 Counter Name VS.R99PSLoad.MaxULThr uput.RNC Counter Description Maximum Throughput of Uplink PS R99 Traffic for RNC
Description
This measurement item provides the maximum uplink traffic of all the R99 services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the uplink traffic values of all the R99 services in the PS domain every five seconds. At the end of the measurement period, the RNC calculates
the maximum uplink traffic of all the R99 services in the PS domain within the RNC.The mean uplink traffic of all the R99 services in the PS domain is the traffic measured at the RLC layer. The RLC header data is not included and the soft handover traffic is included.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.R99PSLoad.MaxULThr uput.RNC Feature ID MRFD-210403 Feature Name License Management
1.10.27.5 DL Traffic of R99 PS Domain in RNC Counters

Counter ID 67204136 Counter Name VS.R99PSLoad.DLThruput. RNC Counter Description Throughput of Downlink PS R99 Traffic for RNC
Description
This measurement item provides the downlink traffic of all the R99 services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the downlink traffic values of all the R99 services in the PS domain every five seconds. At the end of the measurement period, the RNC divides the accumulated traffic values by the number of samples to obtain the mean downlink traffic of all the R99 services in the PS domain.The mean downlink traffic of all the R99 services in the PS domain is the traffic measured at the RLC layer. The RLC header data is not included and the soft handover traffic is included.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.R99PSLoad.DLThruput. RNC Feature ID MRFD-210403 Feature Name License Management
1.10.27.6 Maximum DL Traffic of R99 PS Domain in RNC Counters

Counter ID 67192988 Counter Name VS.R99PSLoad.MaxDLThr uput.RNC Counter Description Maximum Throughput of Downlink PS R99 Traffic for RNC
Description
This measurement item provides the maximum downlink traffic of all the R99 services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the downlink traffic values of all the R99 services in the PS domain every five seconds. At the end of the measurement period, the RNC calculates the maximum downlink traffic of all the R99 services in PS domain within the RNC.The mean downlink traffic of all the R99 services in the PS domain is the traffic measured at the RLC layer. The RLC header data is not included and the soft handover traffic is included.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
701
Related Features
Counter Name VS.R99PSLoad.MaxDLThr uput.RNC Feature ID MRFD-210403 Feature Name License Management
1.10.27.7 DL Traffic of HSDPA PS Domain in RNC Counters

Counter ID 67204137 Counter Name VS.HSDPAPSLoad.DLThru put.RNC Counter Description Throughput of PS HSDPA Traffic for RNC
Description
This measurement item provides the downlink traffic of all the HSDPA services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the downlink traffic values of all the HSDPA services in the PS domain every five seconds. At the end of the measurement period, the RNC divides the accumulated traffic values by the number of samples to obtain the mean downlink traffic of all the HSDPA services in the PS domain.The downlink traffic of all the HSDPA services in the PS domain refers to the traffic measured at the RLC layer. The data does not include the RLC head data.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.HSDPAPSLoad.DLThru put.RNC Feature ID WRFD-010610 Feature Name HSDPA Introduction Package
Issue 01 (2013-05-04)
702
1.10.27.8 Maximum DL Traffic of HSDPA PS Domain in RNC Counters

Counter ID 67192991 Counter Name VS.HSDPAPSLoad.MaxDL Thruput.RNC Counter Description Maximum Throughput of PS HSDPA Traffic for RNC
Description
This measurement item provides the maximum downlink traffic of all the HSDPA services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the downlink traffic values of all the HSDPA services in the PS domain every five seconds. At the end of the measurement period, the RNC calculates the maximum downlink traffic of all the HSDPA services in PS domain within the RNC.The downlink traffic of all HSDPA services in the PS domain refers to the traffic obtained at the RLC layer. The data does not include the RLC head data.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.HSDPAPSLoad.MaxDL Thruput.RNC Feature ID WRFD-010610 Feature Name HSDPA Introduction Package
1.10.27.9 UL Traffic of HSUPA PS Domain in RNC Counters

Counter ID 67204138 Counter Name VS.HSUPAPSLoad.ULThru put.RNC Counter Description Throughput of PS HSUPA Traffic for RNC
Issue 01 (2013-05-04)
703
Description
This measurement item provides the uplink traffic of all the HSUPA services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the uplink traffic values of all the HSUPA services in the PS domain every five seconds. At the end of the measurement period, the RNC divides the accumulated values by the number of samples to obtain the mean uplink traffic of all the HSUPA services in the PS domain.The mean uplink traffic of all the HSUPA services in the PS domain is the traffic measured at the RLC layer. The RLC header data is not included and the soft handover traffic is included.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.HSUPAPSLoad.ULThru put.RNC Feature ID WRFD-010612 Feature Name HSUPA Introduction Package
1.10.27.10 Maximum UL Traffic of HSUPA PS Domain in RNC Counters

Counter ID 67192994 Counter Name VS.HSUPAPSLoad.MaxUL Thruput.RNC Counter Description Maximum Throughput of PS HSUPA Traffic for RNC
Description
This measurement item provides the maximum uplink traffic of all the HSUPA services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the uplink traffic values of all the HSUPA services in the PS domain every five seconds. At the end of the measurement period, the RNC calculates
the maximum uplink traffic of all the HSUPA services in the PS domain within the RNC.The mean uplink traffic of all the HSUPA services in the PS domain is the traffic measured at the RLC layer. The RLC header data is not included and the soft handover traffic is included.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.HSUPAPSLoad.MaxUL Thruput.RNC Feature ID WRFD-010612 Feature Name HSUPA Introduction Package
1.10.27.11 DL Traffic of MBMS or IMB PS Domain in RNC Counters

Counter ID 67204139 Counter Name VS.MBMSPSLoad.DLThru put.RNC Counter Description Throughput of PS MBMS Traffic for RNC
Description
This measurement item provides the downlink traffic of all the MBMS or IMB services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the downlink traffic values of all the MBMS or IMB services in the PS domain every five seconds. At the end of the measurement period, the RNC divides the accumulated traffic values by the number of samples to obtain the mean downlink traffic of all the MBMS or IMB services in the PS domain.The downlink traffic of all the MBMS or IMB services in the PS domain refers to the traffic measured at the RLC layer. The data does not include the RLC head data.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.MBMSPSLoad.DLThru put.RNC Feature ID WRFD-010616 Feature Name MBMS Introduction Package
1.10.27.12 Maximum DL Traffic of MBMS or IMB PS Domain in RNC Counters

Counter ID 67192997 Counter Name VS.MBMSPSLoad.MaxDL Thruput.RNC Counter Description Maximum Throughput of PS MBMS Traffic for RNC
Description
This measurement item provides the maximum downlink traffic of all the MBMS or IMB services in the PS domain within the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the downlink traffic values of all the MBMS or IMB services in the PS domain every five seconds. At the end of the measurement period, the RNC calculates the maximum downlink traffic of all the MBMS or IMB services in PS domain within the RNC.The downlink traffic of all MBMS or IMB services in the PS domain refers to the traffic obtained at the RLC layer. The data does not include the RLC head data.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.MBMSPSLoad.MaxDL Thruput.RNC Feature ID WRFD-010616 Feature Name MBMS Introduction Package
Issue 01 (2013-05-04)
706
1.10.27.13 Average Total Throughout of UL and DL PS Services for RNC Counters

Counter ID 73410501 Counter Name VS.PSLoad.Thruput.RNC Counter Description Average Total Throughout of UL and DL PS Services for RNC
Description
This counter provides the average total throughput of downlink and uplink PS services in the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The total throughput of uplink and downlink PS services in the RNC is sampled and accumulated periodically every five seconds. At the end of the measurement period, the average throughput is obtained as follows: dividing the accumulated throughput by the sampling times. The RLC header is not included and the retransmission data is included in the counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.PSLoad.Thruput.RNC Feature ID MRFD-210403 Feature Name License Management
1.10.27.14 Maximum Total Throughout of UL and DL PS Services Counters

Counter ID 73394059 Counter Name VS.PSLoad.MaxThruput.R NC Counter Description Maximum Total Throughout of UL and DL PS Services for RNC
Issue 01 (2013-05-04)
707
Description
This counter provides the maximum total throughput of uplink and downlink PS services in the RNC. The item is measured only when the RAN sharing function and MOCN function are switched off.
Measurement point
The total throughput of uplink and downlink PS services in the RNC is sampled periodically every five seconds. At the end of the measurement period, the maximum throughput is obtained. The RLC header is not included and the retransmission data is included in the counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.PSLoad.MaxThruput.R NC Feature ID MRFD-210403 Feature Name License Management
1.10.27.15 Erlang of CS Services for RNC Counters

Counter ID 73394070 Counter Name VS.CS.Erlang.RNC Counter Description Erlang of CS Services for RNC
Description
This counter provides the Erlang of CS services according to the call duration in the RNC.
Measurement point
This counter is measured based on the actual call duration, that is, the time interval between the RAB setup and the RAB release. The value of this counter is measured as follows: SUM (All CS RAB holding time in minutes)/60 min. Here, the holding time of all RABs are converted to that in AMR 12.2 kbit/s.
Formula
None
Unit
Erl
Related Features
Counter Name VS.CS.Erlang.RNC Feature ID MRFD-210403 Feature Name License Management
1.11 Measurement of ROAMCNOPERATOR Performance (ROAM_CNOPERATOR)

Overview
Roaming UE registration measurement indicates the registration of roaming UEs by the RNC.
FunctionSubSets
FunctionSubSet MOCN.ROAM_CNOPERATOR FunctionSubSet Name Roaming UE Registration Measurement Under MOCN
1.11.1 Roaming UE Registration Measurement Under MOCN (MOCN.ROAM.CNOPERATOR)

Overview
Roaming UE registration measurement under MOCN provides the number of times that a roaming UE is registered in an operator under the MOCN after the roaming UE starts the CS or PS registration.
Issue 01 (2013-05-04)
709
Counters
Counter ID 73423374 Counter Name VS.Roam.Cnoperat or.MOCN.Num Counter Description Number of Roaming UEs that Is Registered In Local Operator Under MOCN for the First Time Original Release V900R013
None
1.11.1.1 Number of Roaming UEs that Is Registered In Local Operator Under MOCN for the First Time Counters
Counter ID 73423374 Counter Name VS.Roam.Cnoperator.MOC N.Num Counter Description Number of Roaming UEs that Is Registered In Local Operator Under MOCN for the First Time
Description
This counter provides the number of times that a roaming UE is registered in the local operator under the MOCN to indicate that when the operator of the roaming UE has signed the roaming contract with multiple operators under the MOCN, the RNC routes the roaming UEs to different operators according to the preset proportion.
Measurement point
The measurement is triggered at point B as shown in the following figure. After receiving an RRC setup request from a roaming UE with the cause value indicating registration, the RNC starts the MOCN roaming. This counter is measured when the RNC receives an RANAP DIRECT TRANSFER message containing the Redirection Complete IE from the CN.
Issue 01 (2013-05-04)
710
Figure 1-304 INIT UE MESSAGE Redirect procedure
Formula
None
Unit
None
Related Features
Counter Name VS.Roam.Cnoperator.MOC N.Num Feature ID WRFD-02131106 Feature Name Routing Roaming UEs in Proportion
1.12 Measurement of Radio Cell Performance(UCELL)

Overview
The measurement object type CELL is used to measure the performance of a cell. The cell belongs to the RNC and contains one measurement set: CELL.
Issue 01 (2013-05-04)
711
FunctionSubSets
FunctionSubSet ALGO.Cell ALGO2.Cell BLER.Cell BOOST.CELL CCH.Cell CELLUPDATE.Cell CM.Cell EFACH.Cell EPCH.Cell ERACH.Cell HHO.Cell HSDPA.Cell HSUPA.Cell INTRAT.HO.Cell IU.Sig.Rel.Cell IUB.Cell LCS.CELL MBMS.Cell MEAR.Report.Cell PAGE.CELL PLMN.CELL PTT.Cell QOS.Cell RAB.EstabCS.Cell RAB.EstabPS.Cell RAB.EstFailCs.Cell FunctionSubSet Name Measurement related to Algorithm per cell Algorithm Measurement2 for Cell Measurement related to BLER per cell Cell Measurement on BOOST Common Channel Measurement per Cell Cell Update Measurement per cell Measurement of Compressed Mode per cell EFACH Measurement per cell EPCH Measurement per cell ERACH Measurement per cell Hard Handover Measurement per cell HSDPA Measurement per cell HSUPA Measurement per cell InterRAT Handover Measurement per cell Measurement Related to the Release of Iu Signaling Connections (Without RAB) (Cell) Iub Interface Measurement per cell Measurement related to LCS service per cell MBMS Measurement per cell RRC Reporting Measurement per cell Measurement related to Paging per cell Measurement by Operator for Cell Measurements related to PTT Measurement related to QOS per cell Measurement of CS RAB assignment setup per cell Measurement of PS RAB assignment setup per cell Measurement of CS RAB assignment failure per cell
Issue 01 (2013-05-04)
712
FunctionSubSet RAB.EstFailPs.Cell RAB.ModCs.Cell RAB.ModPs.Cell RAB.MultiRab.Cell RAB.RelAbnormal.Cell RAB.RelCs.Cell RAB.RelPs.Cell RB.Cell RESERVE.Cell RLC.Cell RRC.Rel.Cell RRC.Setup.Cell RRC.SetupFail.Cell RRC.State.Cell RRC.UECapab.Cell RTWPTCP.Cell SHO.Cell SIR.Cell SPI.Cell THRUPUT.Cell TRFFIC.Cell U2LTE.HO.Cell URAUPDATE.Cell WLAN.Cell
FunctionSubSet Name Measurement of PS RAB assignment failure per cell Measurement of CS RAB assignment modification per cell Measurement of PS RAB assignment modification per cell Measurement of multi-RAB service per cell Measurement of RAB release per cell Measurement of CS RAB release per cell Measurement of PS RAB release per cell Measurement of RB Procedure per cell Reserved counter for cell Measurement related to RLC per cell RRC connection release measurement per cell RRC connection setup measurement per cell RRC connection reject measurement per cell RRC state measurement<Cell> UE Capability Measurement per cell Cell TX and RX Power Measurement per cell Soft Handover Measurement per cell Measurement related to SIRTARGET per cell Measurement related to SPI per cell Measurement related to throughput and data rate per cell Traffic Measurement per cell Measurement related to U2L Handover per cell URA Update Measurement per cell WLAN Measurement per cell
Issue 01 (2013-05-04)
713
1.12.1 Measurement related to Algorithm per cell(ALGO.Cell)

Overview
Radio Resource Management (RRC) algorithm is an important function of the WCDMA system. It is used to manage cell resources effectively and to increase resource utilization. This function subset provides measurements related to the radio resource management algorithm.
Counters
Counter ID 67180678 Counter Name VS.AMR.DL.Rate Up VS.AMR.DL.RateDown VS.AMR.UL.Rate Up VS.AMR.UL.RateDown VS.DCCC.Succ.F2 D Counter Description Number of DL Rate Increases for AMR Services for Cell Number of DL Rate Decreases for AMR Services for Cell Number of UL Rate Increases for AMR Services for Cell Number of UL Rate Decreases for AMR Services for Cell Number of Successful Channel Conversions from FACH to DCH for Cell Number of Successful Channel Conversions from DCHs to FACHs for Cell Number of State Transfer Attempts from CELL_FACH to CELL_PCH for Cell Number of Successful State Transfers from CELL_FACH to CELL_PCH for Cell Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67190519
67190520
67180677
67180675
67180676
VS.DCCC.Succ.D2 F
67192583
VS.DCCC.Att.F2P
67192584
VS.DCCC.Succ.F2 P
Issue 01 (2013-05-04)
714
Counter ID 67192587
Counter Name VS.DCCC.AttDow nsizing.DL.Thr
Counter Description Number of Downlink DCH DCCC Downsizing Attempts Based on Throughput or RLC BO for Cell Number of Successful DL DCH DCCC Downsizings Based on Throughput or RLC BO for Cell Number of Downlink DCH DCCC Downsizing Attempts Based on Coverage (QoS) for Cell Number of Successful DL DCH DCCC Downsizings Based on Coverage (QoS) for Cell Number of Downlink DCH DCCC Downsizing Attempts Based on Resource Congestion Algorithm for Cell Number of Successful DL DCH DCCC Downsizings Based on Resource Congestion Algorithm for Cell Number of UL Overload Congestions for Cell Number of DL Overload Congestions for Cell
67192588
VS.DCCC.SuccDo wnsizing.DL.Thr
67192589
VS.DCCC.AttDow nsizing.DL.Cov
67192590
VS.DCCC.SuccDo wnsizing.DL.Cov
67192591
VS.DCCC.AttDow nsizing.DL.Cong
67192592
VS.DCCC.SuccDo wnsizing.DL.Cong
67189852
VS.LCC.OLC.UL. Num VS.LCC.OLC.DL. Num
67189853
Issue 01 (2013-05-04)
715
Counter ID 67203402
Counter Name VS.LCC.OLC.UL. Time VS.LCC.OLC.DL. Time VS.LCC.OLC.HSD PA.UserRel
Counter Description Duration of UL Overload Congestion for Cell Duration of DL Overload Congestion for Cell Number of HSDPA UEs Released Due to Overload Congestion for Cell Number of UEs Transferring BE Service to Common Channel in Overload Congestion for Cell Duration of Cell in LDR State Due to UL Power Congestion for Cell Duration of Cell in LDR State Due to DL Power Congestion for Cell Duration of Cell in LDR State Due to DL Code Resource Congestion for Cell Duration of Cell in LDR State Due to UL CE Resource Congestion Duration of Cell in LDR State Due to DL CE Resource Congestion Duration of Cell in LDR State Due to UL Iub Transmission Resource Congestion for Cell
67203403
67191150
67192549
VS.LCC.OLC.D2C
67203991
VS.LCC.LDR.Tim e.ULPower
67203992
VS.LCC.LDR.Tim e.DLPower
67203993
VS.LCC.LDR.Tim e.DLCode
67203994
VS.LCC.LDR.Tim e.ULCE
67203995
VS.LCC.LDR.Tim e.DLCE
67203996
VS.LCC.LDR.Tim e.ULIub
Issue 01 (2013-05-04)
716
Counter ID 67203997
Counter Name VS.LCC.LDR.Tim e.DLIub
Counter Description Duration of Cell in LDR State Due to DL Iub Transmission Resource Congestion for Cell Number of Times a Cell Is in LDR State Due to UL Power Congestion for Cell Number of Times a Cell Is in LDR State Due to DL Power Congestion for Cell Number of Times a Cell Is in LDR State Due to DL Code Resource Congestion for Cell Number of Times a Cell Is in LDR State Due to UL CE Resource Congestion for Cell Number of Times a Cell Is in LDR State Due to DL CE Resource Congestion for Cell Number of Times a Cell Is in LDR State Due to UL Iub Transmission Resource Congestion for Cell Number of Times a Cell Is in LDR State Due to DL Iub Transmission Resource Congestion for Cell
67192637
VS.LCC.LDR.Num .ULPower
67192638
VS.LCC.LDR.Num .DLPower
67192639
VS.LCC.LDR.Num .DLCode
67192640
VS.LCC.LDR.Num .ULCE
67192641
VS.LCC.LDR.Num .DLCE
67192642
VS.LCC.LDR.Num .ULIub
67192643
VS.LCC.LDR.Num .DLIub
Issue 01 (2013-05-04)
717
Counter ID 67192644
Counter Name VS.LCC.LDR.HSU PA.InterFreq
Counter Description Number of HSUPA UEs Performing Inter-Frequency Load Handovers in Basic Congestion for Cell Number of HSUPA UEs Performing PS Inter-RAT Handover in Basic Congestion for Cell Number of UEs Performing BE Service TF Control in UL Overload Congestion for Cell Number of UEs Released Due to UL Overload Congestion for Cell Number of HSUPA UEs Released during Overload Congestion for Cell Number of UEs Performing BE Service TF Control in DL Overload Congestion for Cell Number of UEs Released Due to DL Overload Congestion for Cell Number of Failed Admissions Due to HSDPA User Number Exceeding Threshold During RAB Establishment for Cell
67192645
VS.LCC.LDR.HSU PA.InterRATPS
67192646
VS.LCC.OLC.UL. TF
67192647
VS.LCC.OLC.UL. UserRel
67192648
VS.LCC.OLC.HSU PA.UserRel
67192649
VS.LCC.OLC.DL. TF
67192650
VS.LCC.OLC.DL. UserRel
67192916
VS.RAC.NewCallR eq.Fail.HSDPANu m.Cong
Issue 01 (2013-05-04)
718
Counter ID 67192917
Counter Name VS.RAC.NewCallR eq.Fail.HSUPANu m.Cong
Counter Description Number of Failed Admissions Due to HSUPA User Number Exceeding Threshold During RAB Establishment for Cell Number of Preemptions During RAB Establishment for Cell Number of Failed Requests for UL Power Resources During SHO for Cell Number of Failed Requests for DL Power Resources During SHO for Cell Number of Failed Requests for Code Resources During SHO for Cell Number of Failed Requests for UL Iub Transmission Resources During SHO for Cell Number of Failed Requests for DL Iub Transmission Resources During SHO for Cell Number of Failed Admissions Due to HSUPA User Number Exceeding Threshold During SHO for Cell Number of Failed Requests for UL Power Resources During DCCC for Cell
67192937
VS.RAC.NewCallR eq.Preempt.Cong
67192939
VS.RAC.SHO.Fail. ULPower.Cong
67192940
VS.RAC.SHO.Fail. DLPower.Cong
67192918
VS.RAC.SHO.Fail. Code.Cong
67192919
VS.RAC.SHO.Fail. ULIUBBand.Cong
67192920
VS.RAC.SHO.Fail. DLIUBBand.Cong
67192921
VS.RAC.SHO.Fail. HSUPANum.Cong
67192943
VS.RAC.DCCC.Fa il.ULPower.Cong
Issue 01 (2013-05-04)
719
Counter ID 67192944
Counter Name VS.RAC.DCCC.Fa il.DLPower.Cong
Counter Description Number of Failed Requests for DL Power Resources During DCCC for Cell Number of Failed Requests for DL Code Resources During DCCC for Cell Number of Failed Requests for UL CE Resources During Channel Type Switch for Cell Number of Failed Requests for DL CE Resources During Channel Type Switch for Cell Number of Failed Requests for UL Power Resources During Channel Type Switch for Cell Number of Failed Requests for DL Power Resources During Channel Type Switch for Cell Number of Failed Requests for Code Resources During Channel Type Switch for Cell Number of Failed Requests for UL Iub Transmission Resources During Channel Type Switch for Cell
67192922
VS.RAC.DCCC.Fa il.Code.Cong
67192923
VS.RAC.TrChSwit ch.Fail.ULCE.Con g
67192924
VS.RAC.TrChSwit ch.Fail.DLCE.Con g
67192945
VS.RAC.TrChSwit ch.Fail.ULPower.C ong
67192946
VS.RAC.TrChSwit ch.Fail.DLPower.C ong
67192925
VS.RAC.TrChSwit ch.Fail.Code.Cong
67192926
VS.RAC.TrChSwit ch.Fail.ULIUBBan d.Cong
Issue 01 (2013-05-04)
720
Counter ID 67192927
Counter Name VS.RAC.TrChSwit ch.Fail.DLIUBBan d.Cong
Counter Description Number of Failed Requests for DL Iub Transmission Resources During Channel Type Switch for Cell Number of Failed Admissions Due to HSDPA User Number Exceeding Threshold During Channel Type Switch for Cell Number of Failed Admissions Due to HSUPA User Number Exceeding Threshold During Channel Type Switch for Cell Number of Failed Requests for UL Power Resources During HHO for Cell Number of Failed Requests for DL Power Resources During HHO for Cell Number of Failed Requests for UL Iub Transmission Resources During HHO for Cell Number of Failed Requests for DL Iub Transmission Resources During HHO for Cell Number of Failed Admissions Due to HSDPA User Number Exceeding Threshold During HHO for Cell
67192928
VS.RAC.TrChSwit ch.Fail.HSDPANu m.Cong
67192929
VS.RAC.TrChSwit ch.Fail.HSUPANu m.Cong
67192941
VS.RAC.HHO.Fail .ULPower.Cong
67192942
VS.RAC.HHO.Fail .DLPower.Cong
67192930
VS.RAC.HHO.Fail .ULIUBBand.Cong
67192931
VS.RAC.HHO.Fail .DLIUBBand.Cong
67192932
VS.RAC.HHO.Fail .HSDPANum.Cong
Issue 01 (2013-05-04)
721
Counter ID 67192933
Counter Name VS.RAC.HHO.Fail .HSUPANum.Cong
Counter Description Number of Failed Admissions Due to HSUPA User Number Exceeding Threshold During HHO for Cell Number of Preemptions During HHO for Cell Number of MBMS PTM Service Releases in Overload Congestion for Cell Number of MBMS PTP Service Releases in Overload Congestion for Cell Number of UEs Performing InterFrequency Load Handovers in Basic Congestion for Cell Number of HSDPA UEs Performing Inter-Frequency Load Handovers in Basic Congestion for Cell Number of UEs Performing BE Service Downsizing in UL Basic Congestion Number of UEs Performing BE Service Downsizing in DL Basic Congestion
67192938
VS.RAC.HHO.Pre empt.Cong VS.LCC.OLC.MB MS.PTM.RBRel
67194970
67194971
VS.LCC.OLC.MB MS.PTP.RBRel
67190435
VS.LCC.LDR.InterFreq
67191151
VS.LCC.LDR.HSD PA.InterFreq
67190436
VS.LCC.LDR.UL. BERateDown
67190437
VS.LCC.LDR.DL. BERateDown
Issue 01 (2013-05-04)
722
Counter ID 67190438
Counter Name VS.LCC.LDR.UL. QosReNego
Counter Description Number of UEs Performing Uncontrollable RealTime Service QoS Renegotiation in UL Basic Congestion for Cell Number of UEs Performing Uncontrollable RealTime Service QoS Renegotiation in DL Basic Congestion for Cell Number of UEs Performing CS InterRAT Handovers in Basic Congestion for Cell Number of UEs Performing PS InterRAT Handovers in Basic Congestion for Cell Number of HSDPA UEs Performing PS Inter-RAT Handovers in Basic Congestion for Cell Number of UEs Performing AMR Rate Decrease in UL Basic Congestion for Cell Number of UEs Performing AMR Rate Decrease in DL Basic Congestion for Cell Number of UEs Performing Code Adjustment Attempts in DL Basic Congestion for Cell
67190439
VS.LCC.LDR.DL. QosReNego
67190440
VS.LCC.LDR.InterRATCS
67190441
VS.LCC.LDR.InterRATPS
67191152
VS.LCC.LDR.HSD PA.InterRATPS
67192426
VS.LCC.LDR.AM RRateUL
67192427
VS.LCC.LDR.AM RRateDL
67192397
VS.LCC.LDR.Cod eAdj.Att
Issue 01 (2013-05-04)
723
Counter ID 67192398
Counter Name VS.LCC.LDR.Mb msPowerDec
Counter Description Number of MBMS Services Performing Power Decreasing in Basic Congestion for Cell Number of Qoffset Updates Due to Heavy Load for Cell Number of Qoffset Updates Due to Light Load for Cell Number of Qoffset Updates Due to Normal Load for Cell Number of Sintersearch Updates Due to Light Load for Cell Number of Sintersearch Updates Due to Normal Load for Cell Number of Sintersearch Updates Due to Heavy Load for Cell Number of Failed Requests for Code Resources During HHO for Cell Number of Successful Cell Resource Requests During HHO for Cell Number of Cell Resource Requests During HHO for Cell
67189856
VS.PUC.High.Offs et.Updt VS.PUC.Light.Offs et.Updt VS.PUC.Norm.Offs et.Updt VS.PUC.Light.IntS rch.Updt
67189857
67189858
67190442
67190443
VS.PUC.Norm.IntS rch.Updt
67190444
VS.PUC.High.IntS rch.Updt
67189859
VS.RAC.HHO.Fail .Code.Cong
67181079
VS.RAC.HHOCallAcc
67181074
VS.RAC.HHOCallReq
Issue 01 (2013-05-04)
724
Counter ID 67181076
Counter Name VS.RAC.NewCallAcc
Counter Description Number of Successful Cell Resource Requests During RAB Establishment for Cell Number of Cell Resource Requests During RAB Establishment for Cell Number of Successful Cell Resource Requests Due to UE RAB Reconfiguration for Cell Number of Cell Resource Requests Due to UE RAB Reconfiguration for Cell Number of Successful Cell Resource Requests During SHO for Cell Number of Cell Resource Requests During SHO for Cell Number of Successful Cell Resource Requests During Channel Type Switch for Cell Number of Cell Resource Requests During Channel Type Switch for Cell Mean Number of DL Equivalent Voice UEs in CEL_DCH State for Cell
67181071
VS.RAC.NewCallReq
67181078
VS.RAC.ReconfigCallAcc
67181073
VS.RAC.ReconfigCallReq
67181077
VS.RAC.SHOCallAcc
67181072
VS.RAC.SHOCallReq VS.RAC.TrChSwit chCallAcc
67181080
67181075
VS.RAC.TrChSwit chCallReq
67199664
VS.RAC.DL.EqvUserNum
Issue 01 (2013-05-04)
725
Counter ID 67199663
Counter Name VS.RAC.UL.EqvUserNum
Counter Description Mean Number of UL Equivalent Voice UEs in CEL_DCH State for Cell Duration of Cell Dynamic Shutdown Due to Automatic Shutdown for Cell Cell Unavailability Duration Mean Usage of UL Credit for Cell Maximum Usage of UL Credit for Cell Minimum Usage of UL Credit for Cell Mean Usage of DL Credit for Cell Maximum Usage of DL Credit for Cell Minimum Usage of DL Credit for Cell Duration of Minimum Values of CPICH Power Due to Cell Breathing for Cell Duration of Maximum Values of CPICH Power Due to Cell Breathing for Cell Number of Upward CPICH Power Adjustments Due to Cell Breathing for Cell
67204134
VS.Cell.DynShutD own.Time
V900R012
67199736 67202567 67191165 67191166 67202570 67191167 67191168 67202917
VS.Cell.UnavailTime VS.LC.ULCreditU sed.Mean VS.LC.ULCreditU sed.Max VS.LC.ULCreditU sed.Min VS.LC.DLCreditU sed.Mean VS.LC.DLCreditU sed.Max VS.LC.DLCreditU sed.Min VS.CellBreath.CPI CHMin.Time
Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67202918
VS.CellBreath.CPI CHMax.Time
67190846
VS.CellBreath.CPI CHUp
Issue 01 (2013-05-04)
726
Counter ID 67190847
Counter Name VS.CellBreath.CPI CHDown
Counter Description Number of Downward CPICH Power Adjustments Due to Cell Breathing for Cell Duration of TCP Smaller Than Cell Breathing Lower Threshold for Cell Duration of TCP Greater Than Cell Breathing Upper Threshold for Cell Average CPICH Power for Cell Number of Dynamic Channel Conversion Attempts from DCHs to FACHs for Cell Number of Dynamic Channel Conversion Attempts from FACHs to DCHs for Cell Number of Increases of DL Rate for AMR WB Speech Service Number of Decreases of DL Rate for AMR WB Speech Service Number of Increases of UL Rate for AMR WB Speech Service Number of Decreases of UL Rate for AMR WB Speech Service Number of Failed Requests for UL CE Resources During DCCC for Cell
67202919
VS.CellBreath.TC PUnder.Time
67202920
VS.CellBreath.TC POver.Time
67202921 67190706
VS.CPICH.MeanP wr VS.DCCC.D2C.Att
V900R013 Earlier than V900R011
67190707
VS.DCCC.C2D.Att
67192001
VS.AMRWB.DLR ateUp VS.AMRWB.DLR ateDown
67192002
67192003
VS.AMRWB.ULR ateUp VS.AMRWB.ULR ateDown
67192004
67191839
VS.RAC.DCCC.Fa il.ULCE.Cong
Issue 01 (2013-05-04)
727
Counter ID 67191840
Counter Name VS.RAC.DCCC.Fa il.DLCE.Cong
Counter Description Number of Failed Requests for DL CE Resources During DCCC for Cell Number of Failed Requests for UL CE Resources During SHO for Cell Number of Failed Requests for DL CE Resources During SHO for Cell Number of Failed Requests for UL CE Resources During HHO for Cell Number of Failed Requests for DL CE Resources During HHO for Cell Number of Failed Requests for Uplink CE Resources During RAB Establishment for Cell Number of Failed Requests for Downlink CE Resources During RAB Establishment for Cell Number of UL EDCH-EDCH DCCC Upsizing Attempts Based on the Throughput or RLC BO for Cell Number of UL EDCH-EDCH DCCC Downsizing Attempts Based on the Throughput or RLC BO for Cell
67191841
VS.RAC.SHO.Fail. ULCE.Cong
67191842
VS.RAC.SHO.Fail. DLCE.Cong
67192492
VS.RAC.HHO.Fail .ULCE.Cong
67192493
VS.RAC.HHO.Fail. DLCE.Cong
67191843
VS.RAC.NewCallR eq.Fail.ULCE.Con g
67191844
VS.RAC.NewCallR eq.Fail.DLCE.Con g
67184359
VS.DCCC.AttUpsi zing.E2E.Thr
67196026
VS.DCCC.AttDow nsizing.E2E.Thr
Issue 01 (2013-05-04)
728
Counter ID 67196027
Counter Name VS.DCCC.SuccUps izing.E2E.Thr
Counter Description Number of Successful UL EDCH-EDCH DCCC Upsizings Based on the Throughput or RLC BO for Cell Number of Successful UL EDCH-EDCH DCCC Downsizings Based on the Throughput or RLC BO for Cell Number of UEs Performing Code Adjustment Based on HSDPA for Cell Number of HSUPA UEs Performing CS Inter-RAT Handovers in Basic Congestion for Cell Number of HSDPA UEs Performing CS Inter-RAT Handovers in Basic Congestion for Cell Number of DL DCH DCCC Upsizing Attempts Based on Throughput or RLC BO for Cell Number of Successful DL DCH DCCC Upsizings Based on Throughput or RLC BO for Cell Number of UL DCH DCCC Upsizing Attempts Based on Throughput or RLC BO for Cell
67196028
VS.DCCC.SuccDo wnsizing.E2E.Thr
67195992
VS.LCC.HSDPA.C odeAdj.Att
V900R012
67196029
VS.LCC.LDR.HSU PA.InterRATCS
67196030
VS.LCC.LDR.HSD PA.InterRATCS
67192585
VS.DCCC.AttUpsi zing.DL.Thr
67192586
VS.DCCC.SuccUps izing.DL.Thr
67192593
VS.DCCC.AttUpsi zing.UL.Thr
Issue 01 (2013-05-04)
729
Counter ID 67192594
Counter Name VS.DCCC.SuccUps izing.UL.Thr
Counter Description Number of Successful UL DCH DCCC Upsizings Based on Throughput or RLC BO for Cell Number of UL DCH DCCC Downsizing Attempts Based on the Throughput or RLC BO for Cell Number of Successful UL DCH DCCC Downsizings Based on Throughput or RLC BO for Cell Number of UL DCH DCCC Downsizing Attempts Based on the Coverage (QoS) for Cell Number of Successful UL DCH DCCC Downsizings Based on Coverage (QoS) for Cell Number of UL DCH DCCC Downsizing Attempts Based on the Resource Congestion Algorithm for Cell Number of Successful UL DCH DCCC Downsizings Based on Resource Congestion Algorithm for Cell Number of UEs Performing Successful Code Adjustment in DL Basic Congestion for Cell
67192595
VS.DCCC.AttDow nsizing.UL.Thr
67192596
VS.DCCC.SuccDo wnsizing.UL.Thr
67196032
VS.DCCC.AttDow nsizing.UL.Cov
67196033
VS.DCCC.SuccDo wnsizing.UL.Cov
67196034
VS.DCCC.AttDow nsizing.UL.Cong
67196035
VS.DCCC.SuccDo wnsizing.UL.Cong
67193409
VS.LCC.LDR.Cod eAdj.Succ
Issue 01 (2013-05-04)
730
Counter ID 67193410
Counter Name VS.LCC.HSDPA.C odeAdj.Succ
Counter Description Number of UEs Performing Successful Code Adjustment Based on HSDPA for Cell Duration of Cell Unavailability Due to System Faults for Cell Duration of HSDPA Service Unavailability Due to System Fault for Cell Duration of HSUPA Service Unavailability Due to System Fault for Cell Number of Attempts to transfer state from CELL_PCH to CELL_FACH for cell Number of Successful state transfer from CELL_PCH to CELL_FACH for cell Number of state transfer from CELL_PCH to URA_PCH for cell Number of Attempts to transfer state from URA_PCH to CELL_FACH for cell
67204837
VS.Cell.UnavailTi me.Sys
67204838
VS.Cell.HSDPA.Un availTime
67204839
VS.Cell.HSUPA.Un availTime
V900R012
73403799
VS.DCCC.P2F.Att
V900R012
73403800
VS.DCCC.P2F.Suc c
V900R012
73403801
VS.DCCC.P2URA P
V900R012
73403802
VS.DCCC.URAP2 F.Att
V900R012
Issue 01 (2013-05-04)
731
Counter ID 73403803
Counter Name VS.DCCC.URAP2 F.Succ
Counter Description Number of successful state transfer from URA_PCH to CELL_FACH in the best cell. Number of Cell Deletions Due to Dynamic Cell Shutdown Number of Cell Setup Due to Dynamic Cell Shutdown Number of Failed Requests for Uplink Power Resources in the RAB Setup Procedure for Cell Number of Failed Requests for Downlink Power Resources in the RAB Setup Procedure for Cell Number of Failed Requests for Code Resources in the RAB Setup Procedure for Cell Number of Failed Requests for Uplink Iub Bandwidth Resources in the RAB Setup Procedure for Cell Number of Failed Requests for Downlink Iub Bandwidth Resources in the RAB Setup Procedure for Cell
73393802
VS.DynClose.CellDel
V900R012
73393803
VS.DynOpen.CellSetup
V900R012
73393961
VS.RAC.NewCallR eq.Fail.ULPower.C ong
V900R012
73393962
VS.RAC.NewCallR eq.Fail.DLPower.C ong
V900R012
73393963
VS.RAC.NewCallR eq.Fail.Code.Cong
V900R012
73393964
VS.RAC.NewCallR eq.Fail.ULIUBBan d.Cong
V900R012
73393965
VS.RAC.NewCallR eq.Fail.DLIUBBan d.Cong
V900R012
Issue 01 (2013-05-04)
732
Counter ID 73421765
Counter Name VS.DCCC.D2P.Att
Counter Description Number of State Transfer Attempts from CELL_DCH to CELL_PCH for Cell Number of Successful State Transfers from CELL_DCH to CELL_PCH for Cell Number of State Transfer Attempts from CELL_DCH or CELL_FACH to CELL_PCH for FAST DORMANCY user for Cell Number of Successful State Transfers from CELL_DCH or CELL_FACH to CELL_PCH for FAST DORMANCY user for Cell Congestion Duration of DTCHs Carried over FACHs for Cell Number of Attempts to transfer state from CELL_PCH to CELL_DCH for cell Number of Successful state transfer from CELL_PCH to CELL_DCH for cell Number of Attempts to transfer state from URA_PCH to CELL_DCH for cell
73421766
VS.DCCC.D2P.Suc c
V900R012
73421767
VS.DCCC.FastDor mUe.DF2P.Att
V900R012
73421768
VS.DCCC.FastDor mUe.DF2P.Succ
V900R012
73439971
VS.FACH.DTCH. CONG.TIME VS.DCCC.P2D.Att
V900R012
73421933
V900R012
73421934
VS.DCCC.P2D.Suc c
V900R012
73421935
VS.DCCC.URAP2 D.Att
V900R012
Issue 01 (2013-05-04)
733
Counter ID 73421936
Counter Name VS.DCCC.URAP2 D.Succ
Counter Description Number of successful state transfer from URA_PCH to CELL_DCH in the best cell. Number of Attempts of CELL_PCH/ URA_PCH-toCELL_DCH State Transition Together with DRD for Cell Number of Successful CELL_PCH/ URA_PCH-toCELL_DCH State Transitions Together with DRDs for Cell Number of CPICH Power Adjustments Based on RTWP for Cell Duration of PCPICH Power Under Minimum RTWP Threshold Number of State Transfer Attempts from CELL_DCH to CELL_PCH or URA_PCH for Cell for HSDPA service Number of Successful Times That a UE Performing HSDPA Services Transits to CELL_PCH or URA_PCH State for cell
73422068
VS.DCCC.P2D.DR D.Att
V900R012
73422069
VS.DCCC.P2D.DR D.Succ
V900R012
73423313
VS.ULB.CPICH.A djustNum
V900R013
73441123
VS.ULB.CPICHMi n.Time
V900R013
73422160
VS.HSDPA.H2P.At t
V900R012
73422161
VS.HSDPA.H2P.Su cc
V900R012
Issue 01 (2013-05-04)
734
Counter ID 73422162
Counter Name VS.HSUPA.E2P.At t
Counter Description Number of Attempts for a UE Performing HSUPA Services to Transit to CELL_PCH or URA_PCH State for Cell Number of Successful Times That a UE Performing HSUPA Services Transits to CELL_PCH or URA_PCH State for cell Number of Attempts for a UE Performing PS R99 Services to Transit to CELL_PCH or URA_PCH State for Cell Number of Successful Times That a UE Performing PS R99 Services Transits to CELL_PCH or URA_PCH State for cell Number of Times That PS R99 Service Rate Is Found to Be Higher than HSUPA Service Rate Number of PS R99 BE Rate Reduction Requests Triggered by Unfairness Between PS R99 Service Rate and HSUPA Service Rate
73422163
VS.HSUPA.E2P.Su cc
V900R012
73422164
VS.PSR99.D2P.Att
V900R012
73422165
VS.PSR99.D2P.Suc c
V900R012
73423357
VS.HSUPAR99.Un fairness
V900R013
73423358
VS.HSUPAR99.Un fairness.R99BERateDown
V900R013
Issue 01 (2013-05-04)
735
Counter ID 73411191
Counter Name VS.NodeB.CPU.Co ng.Dur
Counter Description Duration of CPU Resource Insufficiency Reported by NodeB for Cell Congestion Duration of DCCHs Carried over FACHs for Cell Congestion Duration of CCCHs Carried over FACHs for Cell
73439970
VS.FACH.DCCH. CONG.TIME VS.FACH.CCCH. CONG.TIME
V900R012
73424009
V900R014
Counter VS.LCC.LDR.InterFreq Sub Counter VS.LCC.LDR.HSUPA.InterFreq VS.LCC.LDR.HSDPA.InterFreq VS.LCC.LDR.InterRATPS VS.LCC.LDR.InterRATCS VS.LCC.LDR.HSDPA.InterRATPS VS.LCC.LDR.HSUPA.InterRATCS VS.LCC.LDR.HSDPA.InterRATCS
1.12.1.1 Number of DL Rate Increases for AMR Services Counters

Counter ID 67180678 Counter Name VS.AMR.DL.RateUp Counter Description Number of DL Rate Increases for AMR Services for Cell Number of DL Rate Decreases for AMR Services for Cell Number of Increases of DL Rate for AMR WB Speech Service
67190519
VS.AMR.DL.RateDown
67192001
VS.AMRWB.DLRateUp
Issue 01 (2013-05-04)
736
Counter ID 67192002
Counter Name VS.AMRWB.DLRateDown
Counter Description Number of Decreases of DL Rate for AMR WB Speech Service
Description
These counters provide the number of times the DL rate of narrowband or wideband AMR services is adjusted upward and downward.
Measurement point
The measurement is triggered at point B as shown in the following figure. The RNC sends the RATE CONTROL control frame to the CN through the IUUP layer to request an increase or decrease in the DL rate of narrowband or wideband AMR services. If the RNC receives the RATE CONTROL ACK control frame from the CN, the DL rate of AMR services successfully increases or decreases. In this case, the RNC measures the counters in the best cell where the UE camps on. Figure 1-305 DL AMR rate adjustment procedure
Formula
None
Unit
None
Issue 01 (2013-05-04)
737
Related Features
Counter Name VS.AMR.DL.RateUp VS.AMR.DL.RateDown VS.AMRWB.DLRateUp VS.AMRWB.DLRateDown Feature ID WRFD-020701 WRFD-020701 WRFD-020701 WRFD-020701 Feature Name AMR/WB-AMR Speech Rates Control AMR/WB-AMR Speech Rates Control AMR/WB-AMR Speech Rates Control AMR/WB-AMR Speech Rates Control
1.12.1.2 Counters Related to the Number of Successful Dynamic Channel Conversions Between DCH and FACH Counters
Counter ID 67180675 Counter Name VS.DCCC.Succ.F2D Counter Description Number of Successful Channel Conversions from FACH to DCH for Cell Number of Successful Channel Conversions from DCHs to FACHs for Cell
67180676
VS.DCCC.Succ.D2F
Description
These counters provide the number of successful conversions from the DCH to FACH or from the FACH to DCH. When a UE in the CELL_DCH state performs a soft handover or softer handover, the RNC measures counters related to DCH to FACH state transitions in the best cell before state transition.
Measurement point
The measurement is triggered at point B as shown in the following figure. In the process of state transition, when the RNC receives the RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the RNC measures the related counter in the best cell where the UE camps on before the state transition if the DCH is converted to the FACH. If the FACH is converted to the DCH, the RNC measures the related counter in the cell where the UE in the CELL_FACH state camps on after the state transition.
Issue 01 (2013-05-04)
738
Figure 1-306 Dynamic channel conversion procedure (RB reconfiguration)
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.Succ.F2D Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC) Dynamic Channel Configuration Control (DCCC)
VS.DCCC.Succ.D2F
WRFD-021101
1.12.1.3 Number of State Transfer Attempts from CELL_FACH to CELL_PCH
Issue 01 (2013-05-04)
739
Counters
Counter ID 67192583 Counter Name VS.DCCC.Att.F2P Counter Description Number of State Transfer Attempts from CELL_FACH to CELL_PCH for Cell
Description
This counter provides the number of state transition attempts from CELL_FACH to CELL_PCH in a cell.
Measurement point
The measurement is triggered at point A, as shown in the following figure. When the RNC sends a RADIO BEARER RECONFIGURATION or PHYSICAL CHANNEL RECONFIGURATION message to a UE, instructing the UE to transfer from the CELL_FACH state to the CELL_PCH state, this counter is incremented by one in the cell where the UE is camping. Figure 1-307 RB reconfiguration and physical channel reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.Att.F2P Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.1.4 Number of Successful State Transfers from CELL_FACH to CELL_PCH Counters

Counter ID 67192584 Counter Name VS.DCCC.Succ.F2P Counter Description Number of Successful State Transfers from CELL_FACH to CELL_PCH for Cell
Description
This counter provides the number of successful state transitions from CELL_FACH to CELL_PCH in a cell.
Measurement point
The measurement is triggered at point B, as shown in the following figure. When the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE or a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from a UE, indicating that the UE has transfered from the CELL_FACH state to the CELL_PCH state, this counter is incremented by one in the cell where the UE is camping. Figure 1-308 RB reconfiguration and physical channel reconfiguration procedure
Issue 01 (2013-05-04)
741
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.Succ.F2P Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.1.5 Counters Related to the Number of Downlink DCH DCCC Downsizing Attempts Based on Different Strategies Counters
Counter ID 67192587 Counter Name VS.DCCC.AttDownsizing. DL.Thr Counter Description Number of Downlink DCH DCCC Downsizing Attempts Based on Throughput or RLC BO for Cell Number of Downlink DCH DCCC Downsizing Attempts Based on Coverage (QoS) for Cell Number of Downlink DCH DCCC Downsizing Attempts Based on Resource Congestion Algorithm for Cell
67192589
VS.DCCC.AttDownsizing. DL.Cov
67192591
VS.DCCC.AttDownsizing. DL.Cong
Description
These counters provide the number of downlink DCH DCCC downsizing attempts based on different strategies in the best cell where the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending the RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the related
counter based on different DCCC strategies in the best cell where the UE camps on if downlink services are carried on the DCH before and after the reconfiguration. Figure 1-309 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.AttDownsizing. DL.Thr VS.DCCC.AttDownsizing. DL.Cov VS.DCCC.AttDownsizing. DL.Cong Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC) Dynamic Channel Configuration Control (DCCC) Dynamic Channel Configuration Control (DCCC)
WRFD-021101
WRFD-021101
Issue 01 (2013-05-04)
743
1.12.1.6 Counters Related to the Number of Successful DL DCH DCCC Downsizings Based on Different DCCC Strategies Counters
Counter ID 67192588 Counter Name VS.DCCC.SuccDownsizing. DL.Thr Counter Description Number of Successful DL DCH DCCC Downsizings Based on Throughput or RLC BO for Cell Number of Successful DL DCH DCCC Downsizings Based on Coverage (QoS) for Cell Number of Successful DL DCH DCCC Downsizings Based on Resource Congestion Algorithm for Cell
67192590
VS.DCCC.SuccDownsizing. DL.Cov
67192592
VS.DCCC.SuccDownsizing. DL.Cong
Description
These counters provide the number of successful downlink DCH DCCC downsizings based on different strategies in the best cell where the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending the RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the related counter based on different DCCC strategies in the best cell where the UE camps on if downlink services are carried on the DCH before and after the reconfiguration.
Issue 01 (2013-05-04)
744
Figure 1-310 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.SuccDownsizing. DL.Thr VS.DCCC.SuccDownsizing. DL.Cov VS.DCCC.SuccDownsizing. DL.Cong Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC) Dynamic Channel Configuration Control (DCCC) Dynamic Channel Configuration Control (DCCC)
WRFD-021101
WRFD-021101
1.12.1.7 Counters Related to the Number of UL or DL Overload Congestion

Counters
Counter ID 67189852 67189853 Counter Name VS.LCC.OLC.UL.Num VS.LCC.OLC.DL.Num Counter Description Number of UL Overload Congestions for Cell Number of DL Overload Congestions for Cell
Description
These counters provide the number of UL or DL overload congestion in a cell. A cell enters the congestion state when the uplink power or downlink power exceeds the preset Overload Control (OLC) threshold.
Measurement point
The measurement is triggered at point A as shown in the following figure. After receiving the COMMON MEASUREMENT REPORT message from the NodeB, the RNC measures the related counter in the cell where the overload congestion occurs at UL or DL. If a cell is detected as being in the overload congestion state for two consecutive times, the counter is not increased by one for the second instance. Figure 1-311 Common measurement report procedure
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.OLC.UL.Num VS.LCC.OLC.DL.Num Feature ID WRFD-020107 WRFD-020107 Feature Name Overload Control Overload Control
1.12.1.8 Counters Related to the Duration of UL or DL Overload Congestion Counters

Counter ID 67203402 67203403 Counter Name VS.LCC.OLC.UL.Time VS.LCC.OLC.DL.Time Counter Description Duration of UL Overload Congestion for Cell Duration of DL Overload Congestion for Cell
Description
These counters provide the duration of UL or DL overload congestion in a cell.
Measurement point
After a cell is set up, the RNC measures and accumulates the durations of UL or DL overload congestion in the cell to obtain the value of these counters in a measurement period.
Formula
None
Unit
s
Related Features
Counter Name VS.LCC.OLC.UL.Time VS.LCC.OLC.DL.Time Feature ID WRFD-020107 WRFD-020107 Feature Name Overload Control Overload Control
Issue 01 (2013-05-04)
747
1.12.1.9 Number of UEs Transferring BE Service to Common Channel in Overload Congestion Counters
Counter ID 67192549 Counter Name VS.LCC.OLC.D2C Counter Description Number of UEs Transferring BE Service to Common Channel in Overload Congestion for Cell
Description
When the cell is in overload congestion, the RNC transfer certain UEs performing BE services to common channels (CCHs) to decrease the throughput of interactive and background services, thus reducing the cell load. This counter provides the number of UEs performing BE services that are transferred to CCHs.
Measurement point
When the cell is in overload congestion, the RNC measures the counter in the best cell where the UE camps on every time a UE performing BE services is transited from the DCH to the CCH.
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.OLC.D2C Feature ID WRFD-020107 Feature Name Overload Control
1.12.1.10 Counters Related to the Duration of Cell in LDR State Due to Congestion of Various Resources
Issue 01 (2013-05-04)
748
Counters
Counter ID 67203991 Counter Name VS.LCC.LDR.Time.ULPower VS.LCC.LDR.Time.DLPow er VS.LCC.LDR.Time.DLCod e VS.LCC.LDR.Time.ULCE Counter Description Duration of Cell in LDR State Due to UL Power Congestion for Cell Duration of Cell in LDR State Due to DL Power Congestion for Cell Duration of Cell in LDR State Due to DL Code Resource Congestion for Cell Duration of Cell in LDR State Due to UL CE Resource Congestion Duration of Cell in LDR State Due to DL CE Resource Congestion Duration of Cell in LDR State Due to UL Iub Transmission Resource Congestion for Cell Duration of Cell in LDR State Due to DL Iub Transmission Resource Congestion for Cell
67203992
67203993
67203994
67203995
VS.LCC.LDR.Time.DLCE
67203996
VS.LCC.LDR.Time.ULIub
67203997
VS.LCC.LDR.Time.DLIub
Description
These counters provide the duration of a cell in LDR state due to congestion of various resources.
Measurement point
If the cell is in LDR state due to congestion of various resources, in a measurement period the RNC measures the duration that the cell is in LDR state due to uplink or downlink congestion of various resources.
Formula
None
Unit
s
Issue 01 (2013-05-04)
749
Related Features
Counter Name VS.LCC.LDR.Time.ULPower VS.LCC.LDR.Time.DLPow er VS.LCC.LDR.Time.DLCod e VS.LCC.LDR.Time.ULCE VS.LCC.LDR.Time.DLCE VS.LCC.LDR.Time.ULIub VS.LCC.LDR.Time.DLIub Feature ID WRFD-020106 WRFD-020106 WRFD-020106 WRFD-020106 WRFD-020106 WRFD-020106 WRFD-020106 Feature Name Load Reshuffling Load Reshuffling Load Reshuffling Load Reshuffling Load Reshuffling Load Reshuffling Load Reshuffling
1.12.1.11 Counters Related to the Number of Times a Cell Is in LDR State Due to Congestion of Various Resources Counters
Counter ID 67192637 Counter Name VS.LCC.LDR.Num.ULPower VS.LCC.LDR.Num.DLPow er VS.LCC.LDR.Num.DLCod e VS.LCC.LDR.Num.ULCE Counter Description Number of Times a Cell Is in LDR State Due to UL Power Congestion for Cell Number of Times a Cell Is in LDR State Due to DL Power Congestion for Cell Number of Times a Cell Is in LDR State Due to DL Code Resource Congestion for Cell Number of Times a Cell Is in LDR State Due to UL CE Resource Congestion for Cell Number of Times a Cell Is in LDR State Due to DL CE Resource Congestion for Cell Number of Times a Cell Is in LDR State Due to UL Iub Transmission Resource Congestion for Cell
67192638
67192639
67192640
67192641
VS.LCC.LDR.Num.DLCE
67192642
VS.LCC.LDR.Num.ULIub
Issue 01 (2013-05-04)
750
Counter ID 67192643
Counter Name VS.LCC.LDR.Num.DLIub
Counter Description Number of Times a Cell Is in LDR State Due to DL Iub Transmission Resource Congestion for Cell
Description
These counters provide the number of times that a cell is in LDR state due to congestion of various resources.
Measurement point
If the cell is in LDR state due to congestion of various resources, in a measurement period the RNC measures the number of times that the cell is in LDR state due to uplink or downlink congestion of various resources.
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.LDR.Num.ULPower VS.LCC.LDR.Num.DLPow er VS.LCC.LDR.Num.DLCod e VS.LCC.LDR.Num.ULCE VS.LCC.LDR.Num.DLCE VS.LCC.LDR.Num.ULIub VS.LCC.LDR.Num.DLIub Feature ID WRFD-020106 WRFD-020106 WRFD-020106 WRFD-020106 WRFD-020106 WRFD-020106 WRFD-020106 Feature Name Load Reshuffling Load Reshuffling Load Reshuffling Load Reshuffling Load Reshuffling Load Reshuffling Load Reshuffling
1.12.1.12 Counters Related to the Number of UEs Performing BE Service TF Control in Overload Congestion
Counters
Counter ID 67192646 Counter Name VS.LCC.OLC.UL.TF Counter Description Number of UEs Performing BE Service TF Control in UL Overload Congestion for Cell Number of UEs Performing BE Service TF Control in DL Overload Congestion for Cell
67192649
VS.LCC.OLC.DL.TF
Description
When the cell is in overload congestion, the RNC selects certain UEs performing BE services to implement TF control, that is, reduce the BE throughput based on the MAC control though the TFC selection process. VS.LCC.OLC.UL.TF and VS.LCC.OLC.DL.TF provide the number of UEs performing BE service TF control in UL and DL respectively.
Measurement point
When the cell is in overload congestion, every time the RNC selects a UE to perform BE service TF control, the RNC measures the related counters in the best cell where the UE camps on according to the UL or DL overload congestion.
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.OLC.UL.TF VS.LCC.OLC.DL.TF Feature ID WRFD-020107 WRFD-020107 Feature Name Overload Control Overload Control
1.12.1.13 Counters Related to the Number of UEs Released Due to Overload Congestion
Issue 01 (2013-05-04)
752
Counters
Counter ID 67192647 Counter Name VS.LCC.OLC.UL.UserRel Counter Description Number of UEs Released Due to UL Overload Congestion for Cell Number of HSDPA UEs Released Due to Overload Congestion for Cell Number of HSUPA UEs Released during Overload Congestion for Cell Number of UEs Released Due to DL Overload Congestion for Cell
67191150
VS.LCC.OLC.HSDPA.User Rel VS.LCC.OLC.HSUPA.User Rel VS.LCC.OLC.DL.UserRel
67192648
67192650
Description
When the cell is in overload congestion, the RNC shall release certain UEs if the overload congestion in the cell cannot be relieved through the following operations: (1) Performing TF control through BE services. (2) Transferring BE services to CCHs. (3) Decreasing the power of FACHs. VS.LCC.OLC.UL.UserRel and VS.LCC.OLC.DL.UserRel are used to measure the number of UEs released due to the UL and DL overload congestions in the cell respectively. VS.LCC.OLC.HSDPA.UserRel and VS.LCC.OLC.HSUPA.UserRel are used to measure the number of HSDPA and HSUPA UEs released due to the overload congestion in the cell respectively.For DC-HSDPA or DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
When the cell is in overload congestion, every time a UE is released, as shown of point A in Figure1,the RNC measures VS.LCC.OLC.UL.UserRel and VS.LCC.OLC.DL.UserRel in the cell where the UE camps on according to the uplink or downlink overload congestion. If a HSDPA UE is released, the RNC measures VS.LCC.OLC.HSDPA.UserRel in the cell where the UE camps on. If a HSUPA is released, the RNC measures VS.LCC.OLC.HSUPA.UserRel in the cell where the UE camps on.
Issue 01 (2013-05-04)
753
Figure 1-312 User release procedure for Cell in congestion state
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.OLC.UL.UserRel VS.LCC.OLC.HSDPA.User Rel VS.LCC.OLC.HSUPA.User Rel VS.LCC.OLC.DL.UserRel Feature ID WRFD-020107 WRFD-020107 WRFD-020107 WRFD-020107 Feature Name Overload Control Overload Control Overload Control Overload Control
1.12.1.14 Number of Failed Admissions Due to HSPA User Number Exceeding Threshold During RAB Establishment for Cell
Counters
Counter ID 67192916 Counter Name VS.RAC.NewCallReq.Fail. HSDPANum.Cong Counter Description Number of Failed Admissions Due to HSDPA User Number Exceeding Threshold During RAB Establishment for Cell Number of Failed Admissions Due to HSUPA User Number Exceeding Threshold During RAB Establishment for Cell Number of Failed Requests for Uplink CE Resources During RAB Establishment for Cell Number of Failed Requests for Downlink CE Resources During RAB Establishment for Cell Number of Failed Requests for Uplink Power Resources in the RAB Setup Procedure for Cell Number of Failed Requests for Downlink Power Resources in the RAB Setup Procedure for Cell Number of Failed Requests for Code Resources in the RAB Setup Procedure for Cell Number of Failed Requests for Uplink Iub Bandwidth Resources in the RAB Setup Procedure for Cell Number of Failed Requests for Downlink Iub Bandwidth Resources in the RAB Setup Procedure for Cell
67192917
VS.RAC.NewCallReq.Fail. HSUPANum.Cong
67191843
VS.RAC.NewCallReq.Fail. ULCE.Cong
67191844
VS.RAC.NewCallReq.Fail. DLCE.Cong
73393961
VS.RAC.NewCallReq.Fail. ULPower.Cong
73393962
VS.RAC.NewCallReq.Fail. DLPower.Cong
73393963
VS.RAC.NewCallReq.Fail. Code.Cong
73393964
VS.RAC.NewCallReq.Fail. ULIUBBand.Cong
73393965
VS.RAC.NewCallReq.Fail. DLIUBBand.Cong
Issue 01 (2013-05-04)
755
Description
These counters provide the number of failed resource requests due to insufficient resources of different types, such as CE resources, power resources, Iub bandwidth resources, code resources, number of HSDPA users, and number of HSUPA users, in a cell in the RAB setup procedure. For DC-HSDPA users, VS.RAC.NewCallReq.Fail.HSDPANum.Cong is measured only in the cell with the primary carrier. For DC-HSUPA users, VS.RAC.NewCallReq.Fail.HSUPANum.Cong is measured only in the cell with the primary carrier. The following table describes the meaning of each counter. Counter Name VS.RAC.NewCallReq.Fail.HSUPANum.Co ng Description This counter measure the number of failed admissions due to HSUPA user number exceeding threshold during RAB establishment for cell.
Measurement point
The measurement is triggered at point A as shown in Figure 1. After receiving the RAB ASSIGNMENT REQUEST message from the CN, the RNC initiates the admission procedure to request different resources. If the resource request fails, the RNC measures these counters in the cell where the admission fails according to the limited resource type. Figure 1-313
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.NewCallReq.Fail. HSDPANum.Cong VS.RAC.NewCallReq.Fail. HSUPANum.Cong VS.RAC.NewCallReq.Fail. ULCE.Cong VS.RAC.NewCallReq.Fail. DLCE.Cong VS.RAC.NewCallReq.Fail. ULPower.Cong VS.RAC.NewCallReq.Fail. DLPower.Cong VS.RAC.NewCallReq.Fail. Code.Cong VS.RAC.NewCallReq.Fail. ULIUBBand.Cong VS.RAC.NewCallReq.Fail. DLIUBBand.Cong Feature ID WRFD-01061003 WRFD-01061202 WRFD-020101 WRFD-020101 WRFD-020101 WRFD-020101 WRFD-020101 WRFD-020101 WRFD-020101 Feature Name HSDPA Admission Control HSUPA Admission Control Admission Control Admission Control Admission Control Admission Control Admission Control Admission Control Admission Control
1.12.1.15 Number of Preemptions During RAB Establishment Counters

Counter ID 67192937 Counter Name VS.RAC.NewCallReq.Pree mpt.Cong Counter Description Number of Preemptions During RAB Establishment for Cell
Description
This counter provides the number of service preemptions in a cell during the RAB establishment.
Measurement point
During the RAB establishment, services with high priorities may preempt the resources that are occupied by services with low priorities. If the resource request fails, the RNC measures the counter in the cell where the resource request fails The measurement is triggered at point A as shown in Figure 1. After receiving the RAB ASSIGNMENT REQUEST message from the CN, the RNC initiates the admission procedure to request different resources. If the resource request
fails, the RNC initiates a procedure of preempting the resources occupied by low-priority services by high-priority services. This counter is measured in the cell that fails to request the resources. Figure 1-314
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.NewCallReq.Pree mpt.Cong Feature ID WRFD-010505 Feature Name Queuing and Pre-Emption
1.12.1.16 Number of Failed Requests for various Resources During SHO for Cell Counters
Counter ID 67192939 Counter Name VS.RAC.SHO.Fail.ULPowe r.Cong VS.RAC.SHO.Fail.DLPowe r.Cong Counter Description Number of Failed Requests for UL Power Resources During SHO for Cell Number of Failed Requests for DL Power Resources During SHO for Cell
758
67192940
Issue 01 (2013-05-04)
Counter ID 67192918
Counter Name VS.RAC.SHO.Fail.Code.Co ng VS.RAC.SHO.Fail.ULIUB Band.Cong
Counter Description Number of Failed Requests for Code Resources During SHO for Cell Number of Failed Requests for UL Iub Transmission Resources During SHO for Cell Number of Failed Requests for DL Iub Transmission Resources During SHO for Cell Number of Failed Admissions Due to HSUPA User Number Exceeding Threshold During SHO for Cell Number of Failed Requests for UL CE Resources During SHO for Cell Number of Failed Requests for DL CE Resources During SHO for Cell
67192919
67192920
VS.RAC.SHO.Fail.DLIUB Band.Cong
67192921
VS.RAC.SHO.Fail.HSUPA Num.Cong
67191841
VS.RAC.SHO.Fail.ULCE.C ong VS.RAC.SHO.Fail.DLCE.C ong
67191842
Description
These counters provide the number of failed resource requests due to insufficient resources of different types, such as CE resources, power resources, Iub bandwidth resources, and number of HSUPA users, in a cell in the soft handover procedure. For DC-HSDPA users, VS.RAC.SHO.Fail.HSUPANum.Cong is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in Figure 1. After receiving the MEASUREMENT REPORT message from the UE, the RNC initiates the admission procedure to request different resources if the RNC decides to perform soft handover. If the resource request fails, the RNC measures the related counter in the cell where the admission fails according to the limited resource type.
Issue 01 (2013-05-04)
759
Figure 1-315
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.SHO.Fail.ULPowe r.Cong VS.RAC.SHO.Fail.DLPowe r.Cong VS.RAC.SHO.Fail.Code.Co ng VS.RAC.SHO.Fail.ULIUB Band.Cong VS.RAC.SHO.Fail.DLIUB Band.Cong VS.RAC.SHO.Fail.HSUPA Num.Cong VS.RAC.SHO.Fail.ULCE.C ong VS.RAC.SHO.Fail.DLCE.C ong Feature ID WRFD-020101 WRFD-020101 WRFD-020101 WRFD-020101 WRFD-020101 WRFD-01061202 WRFD-020101 WRFD-020101 Feature Name Admission Control Admission Control Admission Control Admission Control Admission Control HSUPA Admission Control Admission Control Admission Control
Issue 01 (2013-05-04)
760
1.12.1.17 Number of Failed Requests for various Resources During DCCC for Cell Counters
Counter ID 67192943 Counter Name VS.RAC.DCCC.Fail.ULPo wer.Cong VS.RAC.DCCC.Fail.DLPo wer.Cong VS.RAC.DCCC.Fail.Code. Cong VS.RAC.DCCC.Fail.ULCE. Cong VS.RAC.DCCC.Fail.DLCE. Cong Counter Description Number of Failed Requests for UL Power Resources During DCCC for Cell Number of Failed Requests for DL Power Resources During DCCC for Cell Number of Failed Requests for DL Code Resources During DCCC for Cell Number of Failed Requests for UL CE Resources During DCCC for Cell Number of Failed Requests for DL CE Resources During DCCC for Cell
67192944
67192922
67191839
67191840
Description
These counters provide the number of failed resource requests due to insufficient resources of different types such as CE resources, power resources, and code resources in a cell in the DCCC procedure.
Measurement point
The measurement is triggered at point A as shown in the following figure. The admission fails because of certain limited resources in the DCCC procedure. In this case, the RNC measures the related counters in the cells where certain resources are limited according to the limited resource type. Figure 1-316
Issue 01 (2013-05-04)
761
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.DCCC.Fail.ULPo wer.Cong VS.RAC.DCCC.Fail.DLPo wer.Cong VS.RAC.DCCC.Fail.Code. Cong VS.RAC.DCCC.Fail.ULCE. Cong VS.RAC.DCCC.Fail.DLCE. Cong Feature ID WRFD-020101 WRFD-020101 WRFD-020101 WRFD-020101 WRFD-020101 Feature Name Admission Control Admission Control Admission Control Admission Control Admission Control
1.12.1.18 Counters Related to the Number of Failed Requests for Different Resources During Channel Type Switch Counters
Counter ID 67192923 Counter Name VS.RAC.TrChSwitch.Fail.U LCE.Cong Counter Description Number of Failed Requests for UL CE Resources During Channel Type Switch for Cell Number of Failed Requests for DL CE Resources During Channel Type Switch for Cell Number of Failed Requests for UL Power Resources During Channel Type Switch for Cell
67192924
VS.RAC.TrChSwitch.Fail.D LCE.Cong
67192945
VS.RAC.TrChSwitch.Fail.U LPower.Cong
Issue 01 (2013-05-04)
762
Counter ID 67192946
Counter Name VS.RAC.TrChSwitch.Fail.D LPower.Cong
Counter Description Number of Failed Requests for DL Power Resources During Channel Type Switch for Cell Number of Failed Requests for Code Resources During Channel Type Switch for Cell Number of Failed Requests for UL Iub Transmission Resources During Channel Type Switch for Cell Number of Failed Requests for DL Iub Transmission Resources During Channel Type Switch for Cell Number of Failed Admissions Due to HSDPA User Number Exceeding Threshold During Channel Type Switch for Cell Number of Failed Admissions Due to HSUPA User Number Exceeding Threshold During Channel Type Switch for Cell
67192925
VS.RAC.TrChSwitch.Fail.C ode.Cong
67192926
VS.RAC.TrChSwitch.Fail.U LIUBBand.Cong
67192927
VS.RAC.TrChSwitch.Fail.D LIUBBand.Cong
67192928
VS.RAC.TrChSwitch.Fail.H SDPANum.Cong
67192929
VS.RAC.TrChSwitch.Fail.H SUPANum.Cong
Description
These counters provide the number of failed resources requests because of limited resources of different types in a cell during the channel type switch. The resources include CE resources, power resources, Iub bandwidth resources, code resources, number of HSDPA users, and number of HSUPA users. For DC-HSDPA users, VS.RAC.TrChSwitch.Fail.HSDPANum.Cong is measured only in the cell with the primary carrier.For DC-HSUPA users, VS.RAC.TrChSwitch.Fail.HSUPANum.Cong is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in Figure 1. During the channel type change, the RNC initiates the admission procedure to request resources. If the resource request fails, the RNC measures these counters in the cell where the admission fails according to the limited resource type. In addition, only the number of failed requests for different resources in a cell during the channel type change is measured.
Figure 1-317
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.TrChSwitch.Fail.U LCE.Cong VS.RAC.TrChSwitch.Fail.D LCE.Cong VS.RAC.TrChSwitch.Fail.U LPower.Cong VS.RAC.TrChSwitch.Fail.D LPower.Cong VS.RAC.TrChSwitch.Fail.C ode.Cong VS.RAC.TrChSwitch.Fail.U LIUBBand.Cong VS.RAC.TrChSwitch.Fail.D LIUBBand.Cong VS.RAC.TrChSwitch.Fail.H SDPANum.Cong
Issue 01 (2013-05-04)
Feature Name Admission Control Admission Control Admission Control Admission Control Admission Control Admission Control Admission Control HSDPA Admission Control
764
Counter Name VS.RAC.TrChSwitch.Fail.H SUPANum.Cong
Feature Name HSUPA Admission Control
1.12.1.19 Number of Failed Requests for various Resources During HHO for Cell Counters
Counter ID 67192941 Counter Name VS.RAC.HHO.Fail.ULPow er.Cong VS.RAC.HHO.Fail.DLPow er.Cong VS.RAC.HHO.Fail.ULIUB Band.Cong Counter Description Number of Failed Requests for UL Power Resources During HHO for Cell Number of Failed Requests for DL Power Resources During HHO for Cell Number of Failed Requests for UL Iub Transmission Resources During HHO for Cell Number of Failed Requests for DL Iub Transmission Resources During HHO for Cell Number of Failed Admissions Due to HSDPA User Number Exceeding Threshold During HHO for Cell Number of Failed Admissions Due to HSUPA User Number Exceeding Threshold During HHO for Cell Number of Failed Requests for Code Resources During HHO for Cell Number of Failed Requests for UL CE Resources During HHO for Cell
67192942
67192930
67192931
VS.RAC.HHO.Fail.DLIUB Band.Cong
67192932
VS.RAC.HHO.Fail.HSDPA Num.Cong
67192933
VS.RAC.HHO.Fail.HSUPA Num.Cong
67189859
VS.RAC.HHO.Fail.Code.C ong VS.RAC.HHO.Fail.ULCE. Cong
67192492
Issue 01 (2013-05-04)
765
Description
These counters provide the number of failed resources requests due to insufficient resources of different types, such as CE resources, power resources, Iub bandwidth resources, code resources, number of HSDPA users, and number of HSUPA users, in a cell during the hard handover. For DC-HSDPA users, VS.RAC.HHO.Fail.HSDPANum.Cong is measured only in the cell with the primary carrier. For DC-HSUPA users, VS.RAC.HHO.Fail.HSUPANum.Cong is measured only in the cell with the primary carrier.
Measurement point
123 Figure 1-318
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.HHO.Fail.ULPow er.Cong VS.RAC.HHO.Fail.DLPow er.Cong VS.RAC.HHO.Fail.ULIUB Band.Cong
Issue 01 (2013-05-04)
Feature Name Admission Control Admission Control Admission Control
766
Counter Name VS.RAC.HHO.Fail.DLIUB Band.Cong VS.RAC.HHO.Fail.HSDPA Num.Cong VS.RAC.HHO.Fail.HSUPA Num.Cong VS.RAC.HHO.Fail.Code.C ong VS.RAC.HHO.Fail.ULCE. Cong
Feature Name Admission Control HSDPA Admission Control HSUPA Admission Control Admission Control Admission Control
1.12.1.20 Number of Preemptions During HHO Counters

Counter ID 67192938 Counter Name VS.RAC.HHO.Preempt.Con g Counter Description Number of Preemptions During HHO for Cell
Description
This counter provides the number of service preemptions in a cell during the hard handover.
Measurement point
The measurement is triggered at point A as shown in the following figure. After receiving the measurement report, the RNC initiates the admission procedure to request resources if the RNC decides to perform a hard handover. If the resource request fails, the RNC initiates a procedure of preempting the resources occupied by low-priority services by high-priority services and measures the counter in the cell that performs preemption. Figure 1-319
Issue 01 (2013-05-04)
767
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.HHO.Preempt.Con g Feature ID WRFD-010505 Feature Name Queuing and Pre-Emption
1.12.1.21 Number of MBMS PTM Service Releases in Overload Congestion Counters

Counter ID 67194970 Counter Name VS.LCC.OLC.MBMS.PTM. RBRel Counter Description Number of MBMS PTM Service Releases in Overload Congestion for Cell
Description
This counter provides the number of times the MBMS PTM service is released when the cell is in overload congestion.
Measurement point
When the cell is in overload congestion and the MBMS PTM service releases, the RNC measures the counter.
Formula
None
Unit
None
Issue 01 (2013-05-04)
768
Related Features
Counter Name VS.LCC.OLC.MBMS.PTM. RBRel Feature ID WRFD-020107 Feature Name Overload Control
1.12.1.22 Number of MBMS PTP Service Releases in Overload Congestion Counters

Counter ID 67194971 Counter Name VS.LCC.OLC.MBMS.PTP. RBRel Counter Description Number of MBMS PTP Service Releases in Overload Congestion for Cell
Description
This counter provides the number of the times the RB is released due to the MBMS PTP services when the cell is in overload congestion.
Measurement point
When the cell is in overload congestion and the MBMS PTP services trigger the RB release, the RNC measures the counter.
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.OLC.MBMS.PTP. RBRel Feature ID WRFD-020107 Feature Name Overload Control
1.12.1.23 Counters Related to the Number of UEs Performing Inter-Frequency Load Handovers in Basic Congestion
Counters
Counter ID 67190435 Counter Name VS.LCC.LDR.InterFreq Counter Description Number of UEs Performing Inter-Frequency Load Handovers in Basic Congestion for Cell Number of HSUPA UEs Performing Inter-Frequency Load Handovers in Basic Congestion for Cell Number of HSDPA UEs Performing Inter-Frequency Load Handovers in Basic Congestion for Cell
67192644
VS.LCC.LDR.HSUPA.InterFreq
67191151
VS.LCC.LDR.HSDPA.InterFreq
Description
When the cell is in basic congestion, the RNC selects certain UEs to perform inter-frequency load handover. VS.LCC.LDR.InterFreq is used to measure the number of UEs performing interfrequency handovers. VS.LCC.LDR.HSDPA.InterFreq is used to measure the number of HSDPA UEs performing inter-frequency handovers. For DC-HSDPA users, this counter is measured only in the cell with the primary carrier. VS.LCC.LDR.HSUPA.InterFreq is used to measure the number of HSUPA UEs performing inter-frequency handovers.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
When the cell is in basic congestion, VS.LCC.LDR.InterFreq is measured in the cell where the UE camps on every time the RNC selects a UE to perform inter-frequency handover. If the RNC selects an HSDPA UE, VS.LCC.LDR.HSDPA.InterFreq is measured in the cell where the UE camps on. If the RNC selects an HSUPA UE, VS.LCC.LDR.HSUPA.InterFreq is measured in the cell where the UE camps on.
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.LDR.InterFreq Feature ID WRFD-020103 Feature Name Inter Frequency Load Balance
770
Issue 01 (2013-05-04)
Counter Name VS.LCC.LDR.HSUPA.InterFreq VS.LCC.LDR.HSDPA.InterFreq
Feature Name Inter Frequency Load Balance Inter Frequency Load Balance
1.12.1.24 Counters Related to the Number of UEs Performing BE Service Downsizing in Basic Congestion Counters
Counter ID 67190436 Counter Name VS.LCC.LDR.UL.BERateDown VS.LCC.LDR.DL.BERateDown Counter Description Number of UEs Performing BE Service Downsizing in UL Basic Congestion Number of UEs Performing BE Service Downsizing in DL Basic Congestion
67190437
Description
When the cell is in basic congestion, the RNC selects certain UEs for BE service downsizing to relieve congestion. These counters provide the number of UEs performing BE service downsizing according to the UL or DL congestion.
Measurement point
When the cell is in basic congestion, the RNC sends the RADIO BEARER RECONFIGURATION message to the UE through the UU interface every time the RNC selects a UE to perform BE service downsizing. The measurement is triggered at point A as shown in the following figure. The RNC measures the related counter in the cell where the UE camps on according to the UL or DL congestion. Figure 1-320 RB reconfiguration procedure
Issue 01 (2013-05-04)
771
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.LDR.UL.BERateDown VS.LCC.LDR.DL.BERateDown Feature ID WRFD-020106 WRFD-020106 Feature Name Load Reshuffling Load Reshuffling
1.12.1.25 Counters Related to the Number of UEs Performing Uncontrollable RealTime Service QoS Renegotiation in Basic Congestion Counters
Counter ID 67190438 Counter Name VS.LCC.LDR.UL.QosReNego Counter Description Number of UEs Performing Uncontrollable Real-Time Service QoS Renegotiation in UL Basic Congestion for Cell Number of UEs Performing Uncontrollable Real-Time Service QoS Renegotiation in DL Basic Congestion for Cell
67190439
VS.LCC.LDR.DL.QosReNego
Description
When the cell is in basic congestion, the RNC decreases the service QoS of certain UEs performing uncontrollable real-time service to relieve congestion. VS.LCC.LDR.UL.QosReNego and VS.LCC.LDR.DL.QosReNego provide the number of UEs performing uncontrollable real-time service QoS renegotiation according to the UL or DL congestion respectively.
Issue 01 (2013-05-04)
772
Measurement point
The measurement is triggered at point A as shown in the following figure. When the cell is in basic congestion, the RNC selects certain UEs to perform QoS renegotiation. At the same time, the RNC sends the RAB MODIFY REQUEST message to the CN. In this case, the RNC measures the related counter in the cell where the UE camps on according to the UL or DL congestion. Figure 1-321 Uncontrollable real-time service QoS renegotiation procedure
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.LDR.UL.QosReNego VS.LCC.LDR.DL.QosReNego Feature ID WRFD-020106 WRFD-020106 Feature Name Load Reshuffling Load Reshuffling
Issue 01 (2013-05-04)
773
1.12.1.26 Counters Related to the Number of UEs Performing CS Inter-RAT Handovers in Basic Congestion Counters
Counter ID 67190440 Counter Name VS.LCC.LDR.InterRATCS Counter Description Number of UEs Performing CS Inter-RAT Handovers in Basic Congestion for Cell Number of HSUPA UEs Performing CS Inter-RAT Handovers in Basic Congestion for Cell Number of HSDPA UEs Performing CS Inter-RAT Handovers in Basic Congestion for Cell
67196029
VS.LCC.LDR.HSUPA.InterRATCS
67196030
VS.LCC.LDR.HSDPA.InterRATCS
Description
When the cell is in basic congestion, the RNC selects certain UEs to perform CS inter-RAT load handover. VS.LCC.LDR.InterRATCS is used to measure the number of UEs performing CS inter-RAT handovers. VS.LCC.LDR.HSDPA.InterRATCS is used to measure the number of HSDPA UEs performing CS inter-RAT handovers. For DC-HSDPA users, this counter is measured only in the cell with the primary carrier. VS.LCC.LDR.HSUPA.InterRATCS is used to measure the number of HSUPA UEs performing CS inter-RAT handovers.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
When the cell is in basic congestion, VS.LCC.LDR.InterRATCS is measured in the cell where the UE camps on every time the RNC selects a UE to perform CS inter-RAT handover. If the RNC selects a HSDPA UE, VS.LCC.LDR.HSDPA.InterRATCS is measured in the cell where the UE camps on. If the RNC selects a HSUPA UE, VS.LCC.LDR.HSUPA.InterRATCS is measured in the cell where the UE camps on.
Formula
None
Unit
None
Issue 01 (2013-05-04)
774
Related Features
Counter Name VS.LCC.LDR.InterRATCS VS.LCC.LDR.HSUPA.InterRATCS VS.LCC.LDR.HSDPA.InterRATCS Feature ID WRFD-020306 WRFD-020306 WRFD-020306 Feature Name Inter-RAT Handover Based on Load Inter-RAT Handover Based on Load Inter-RAT Handover Based on Load
1.12.1.27 Counters Related to the Number of UEs Performing PS Inter-RAT Handovers in Basic Congestion Counters
Counter ID 67190441 Counter Name VS.LCC.LDR.InterRATPS Counter Description Number of UEs Performing PS Inter-RAT Handovers in Basic Congestion for Cell Number of HSUPA UEs Performing PS Inter-RAT Handover in Basic Congestion for Cell Number of HSDPA UEs Performing PS Inter-RAT Handovers in Basic Congestion for Cell
67192645
VS.LCC.LDR.HSUPA.InterRATPS
67191152
VS.LCC.LDR.HSDPA.InterRATPS
Description
When the cell is in basic congestion, the RNC selects certain UEs to perform PS inter-RAT load handovers. VS.LCC.LDR.InterRATPS is used to measure the number of UEs performing PS inter-RAT handovers. VS.HSDPA.LDR.InterRATPS is used to measure the number of HSDPA UEs performing PS inter-RAT handovers. For DC-HSDPA users, this counter is measured only in the cell with the primary carrier. VS.LCC.LDR.HSUPA.InterRATPS is used to measure the number of HSUPA UEs performing PS inter-RAT handovers. For DC-HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
When the cell is in basic congestion, VS.LCC.LDR.InterRATPS is measured in the cell where the UE camps on every time the RNC selects a UE to perform PS inter-RAT handover. If the RNC selects an HSDPA UE, VS.HSDPA.LDR.InterRATPS is measured in the cell where the
UE camps on. If the RNC selects an HSUPA UE, VS.LCC.LDR.HSUPA.InterRATPS is measured in the cell where the UE camps on.
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.LDR.InterRATPS VS.LCC.LDR.HSUPA.InterRATPS VS.LCC.LDR.HSDPA.InterRATPS Feature ID WRFD-020306 WRFD-020306 WRFD-020306 Feature Name Inter-RAT Handover Based on Load Inter-RAT Handover Based on Load Inter-RAT Handover Based on Load
1.12.1.28 Counters Related to the Number of UEs Performing AMR Rate Decrease in Basic Congestion Counters
Counter ID 67192426 Counter Name VS.LCC.LDR.AMRRateUL Counter Description Number of UEs Performing AMR Rate Decrease in UL Basic Congestion for Cell Number of UEs Performing AMR Rate Decrease in DL Basic Congestion for Cell
67192427
VS.LCC.LDR.AMRRateDL
Description
When the cell is in basic congestion, the RNC selects certain UEs to perform narrowband and wideband AMR services rate decrease. VS.LCC.LDR.AMRRateUL and VS.LCC.LDR.AMRRateDL provide the number of UEs performing AMR rate decrease according to the UL or DL congestion respectively.
Issue 01 (2013-05-04)
776
Measurement point
When the cell is in basic congestion, according to the UL or DL congestion, the RNC measures the related counters in the cell where the UE camps on every time the RNC selects a UE to perform AMR rate decrease.
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.LDR.AMRRateUL VS.LCC.LDR.AMRRateDL Feature ID WRFD-020106 WRFD-020106 Feature Name Load Reshuffling Load Reshuffling
1.12.1.29 Number of UEs Performing Code Adjustment Attempts in DL Basic Congestion for Cell Counters
Counter ID 67192397 Counter Name VS.LCC.LDR.CodeAdj.Att Counter Description Number of UEs Performing Code Adjustment Attempts in DL Basic Congestion for Cell
Description
When the cell is in basic congestion, the RNC selects certain UEs to perform code adjustment attempts. The counter provides the number of UEs performing code adjustment attempts in a cell. When a cell is in basic congestion of downlink code resources, the RNC selects certain UEs in the cell to perform code adjustment so that some idle codes are combined to meet the requirement of a higher rate.
Measurement point
When the cell is in basic congestion, the RNC measures the counter in the cell where the UE camps on every time the RNC selects a UE to perform code adjustment attempt.
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.LDR.CodeAdj.Att Feature ID WRFD-020106 Feature Name Load Reshuffling
1.12.1.30 Number of MBMS Services Performing Power Decreasing in Basic Congestion Counters
Counter ID 67192398 Counter Name VS.LCC.LDR.MbmsPowerDec Counter Description Number of MBMS Services Performing Power Decreasing in Basic Congestion for Cell
Description
When the cell is in basic congestion, the RNC selects certain MBMS services to perform power decreasing. This counter provides the number of MBMS services performing power decreasing in a cell.
Measurement point
When the cell is in basic congestion, the RNC measures the counter in the cell where the MBMS service is processed every time the RNC selects an MBMS service to perform power decreasing.
Formula
None
Unit
None
Issue 01 (2013-05-04)
778
Related Features
Counter Name VS.LCC.LDR.MbmsPowerDec Feature ID WRFD-020106 Feature Name Load Reshuffling
1.12.1.31 Counters Related to the Number of Qoffset Updates Due to Load Level Change Counters
Counter ID 67189856 67189857 67189858 Counter Name VS.PUC.High.Offset.Updt VS.PUC.Light.Offset.Updt VS.PUC.Norm.Offset.Updt Counter Description Number of Qoffset Updates Due to Heavy Load for Cell Number of Qoffset Updates Due to Light Load for Cell Number of Qoffset Updates Due to Normal Load for Cell
Description
These counters provide the number of Qoffset updates by the PUC (Potential User Control) algorithm when the load of the current cell becomes light, normal, or heavy. Qoffset, the selection/reselection parameter in system information block (SIB) 11, defines the selection/ reselection offset between two cells. The network can instruct a UE to camp on either of the two cells based on the value for Qoffset. For details about this parameter, see 3GPP TS 25.304. PUC algorithm: When the load of the serving cell is light, the RNC sets the Qoffset between the serving cell and the neighboring cells to a larger value by updating system information. Therefore, the UE in idle mode is not apt to reselect another heavily-loaded cell. When the load of the serving cell is heavy, the RNC sets the Qoffset between the serving cell and the neighboring cells to a smaller value by updating system information. Therefore, the UE in idle mode is apt to reselect another lightly-loaded cell, which reduces the potential load of the current cell.
Measurement point
The measurement is triggered at point A shown in the following figure. The RNC measures the related counter when updating Qoffset in SIB 11 according to the change in the cell load level in the common measurement report.
Issue 01 (2013-05-04)
779
Figure 1-322 Qoffset update procedure (based on load)
Formula
None
Unit
None
Related Features
Counter Name VS.PUC.High.Offset.Updt VS.PUC.Light.Offset.Updt VS.PUC.Norm.Offset.Updt Feature ID WRFD-020105 WRFD-020105 WRFD-020105 Feature Name Potential User Control Potential User Control Potential User Control
1.12.1.32 Counters Related to the Number of Sintersearch Updates Due to Cell Load Change
Counters
Counter ID 67190444 Counter Name VS.PUC.High.IntSrch.Updt Counter Description Number of Sintersearch Updates Due to Heavy Load for Cell Number of Sintersearch Updates Due to Light Load for Cell Number of Sintersearch Updates Due to Normal Load for Cell
67190442
VS.PUC.Light.IntSrch.Updt
67190443
VS.PUC.Norm.IntSrch.Updt
Description
These counters provide the number of Sintersearch updates by the PUC (Potential User Control) algorithm when the load of the current cell becomes light, normal, or heavy. Sintersearch, the selection/reselection parameter in system information block (SIB) 3, defines the quality requirement of starting a measurement for inter-frequency cell reselection. If the UE finds that the quality of the serving cell is worse than the value for Sintersearch, it starts the inter-frequency measurement so that UE can reselect to another cell. PUC algorithm: When the load of the serving cell is light, the RNC can set a smaller value for Sintersearch by updating system information. Therefore, the UE in idle mode is not apt to start cell reselection. When the load of the serving cell is heavy, the RNC can set a larger value for Sintersearch by updating system information. Therefore, the UE in idle mode is apt to start cell reselection, which reduces the potential load of the current cell.
Measurement point
The measurement is triggered at point A shown in the following figure. The RNC measures the related counter when updating Sintersearch in SIB 3 according to the change in the cell load level in the common measurement report.
Issue 01 (2013-05-04)
781
Figure 1-323 Sintersearch update procedure (based on load)
Formula
None
Unit
None
Related Features
Counter Name VS.PUC.High.IntSrch.Updt VS.PUC.Light.IntSrch.Updt VS.PUC.Norm.IntSrch.Updt Feature ID WRFD-020105 WRFD-020105 WRFD-020105 Feature Name Potential User Control Potential User Control Potential User Control
1.12.1.33 Number of Successful Cell Resource Requests During HHO
Issue 01 (2013-05-04)
782
Counters
Counter ID 67181079 Counter Name VS.RAC.HHOCallAcc Counter Description Number of Successful Cell Resource Requests During HHO for Cell
Description
After receiving a measurement report from the UE, the RNC requests cell resources for a successful hard handover to a new cell. This counter provides the number of successful cell resource requests in the target cell during a hard handover.
Measurement point
The measurement is triggered at point B as shown in the following figure. After receiving the MEASUREMENT REPORT message from the UE, the RNC requests cell resources for hard handover to a new cell. If the request succeeds, the RNC measures the counter in the target cell for handover. Figure 1-324 Successful handover admission
Formula
None
Unit
None
Issue 01 (2013-05-04)
783
Related Features
Counter Name VS.RAC.HHOCallAcc Feature ID WRFD-020101 Feature Name Admission Control
1.12.1.34 Number of Cell Resource Requests During HHO Counters

Counter ID 67181074 Counter Name VS.RAC.HHOCallReq Counter Description Number of Cell Resource Requests During HHO for Cell
Description
After receiving a measurement report from the UE, the RNC requests cell resource for hard handover to a new cell. This counter provides the number of cell resource requests for hard handover in the target cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. After receiving the MEASUREMENT REPORT message from the UE, the RNC requests cell resources for hard handover to a new cell. In this case, the RNC measures the counter in the target cell for handover. Figure 1-325 Successful handover admission
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.HHOCallReq Feature ID WRFD-020101 Feature Name Admission Control
1.12.1.35 Number of Successful Cell Resource Requests During RAB Establishment Counters
Counter ID 67181076 Counter Name VS.RAC.NewCallAcc Counter Description Number of Successful Cell Resource Requests During RAB Establishment for Cell
Description
This counter provides the number of successful cell resource requests during the RAB establishment.
Measurement point
The measurement is triggered at point B as shown in the Figure1. After receiving the RAB ASSIGNMENT REQUEST message from the CN, the RNC requests cell resources for the UE. In this case, the counter will be measured in the cell in which the resources(E.g. Iub bandwidth, CE, power, code, user number etc.) are assigned successfully. If the assignments succeed in more than one cell(E.g. in SHO or DRD case.), the RNC measures the counter in every cell in which the assignments succeed.
Issue 01 (2013-05-04)
785
Figure 1-326 Successful admission during the RAB establishment
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.NewCallAcc Feature ID WRFD-020101 Feature Name Admission Control
1.12.1.36 Number of Cell Resource Requests During RAB Establishment
Issue 01 (2013-05-04)
786
Counters
Counter ID 67181071 Counter Name VS.RAC.NewCallReq Counter Description Number of Cell Resource Requests During RAB Establishment for Cell
Description
This counter provides the number of cell resource requests during the RAB establishment.
Measurement point
The measurement is triggered at point A as shown in the Figure1. After receiving the RAB ASSIGNMENT REQUEST message from the CN, the RNC requests cell resources for the UE. In this case, the counter will be measured in the cell in which the resources(E.g. Iub bandwidth, CE, power, code, user number etc.) are requested. If the resources are requested in more than one cell(E.g. in SHO or DRD case.), the RNC measures the counter in every cell in which the resources are requested. Figure 1-327 Successful admission during the RAB establishment
Formula
None
Unit
None
Issue 01 (2013-05-04)
787
Related Features
Counter Name VS.RAC.NewCallReq Feature ID WRFD-020101 Feature Name Admission Control
1.12.1.37 Number of Successful Cell Resource Requests due to UE Service Reconfiguration (Cell) Counters
Counter ID 67181078 Counter Name VS.RAC.ReconfigCallAcc Counter Description Number of Successful Cell Resource Requests Due to UE RAB Reconfiguration for Cell
Description
This counter provides the number of successful cell resource requests during the RAB modification process.
Measurement point
When the RNC receives a RAB ASSIGNMENT REQUEST message with the cause of "RABs To Be Modified", it shall request cell resource again for this UE. If the request succeeds, as shown of point B in Figure1, the RNC measures this item in the cell that the UE camps on. Figure 1-328 RAB reconfiguration procedure
Issue 01 (2013-05-04)
788
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.ReconfigCallAcc Feature ID WRFD-020101 Feature Name Admission Control
1.12.1.38 Number of Cell Resource Requests due to UE Service Reconfiguration (Cell) Counters
Counter ID 67181073 Counter Name VS.RAC.ReconfigCallReq Counter Description Number of Cell Resource Requests Due to UE RAB Reconfiguration for Cell
Description
This counter provides the number of cell resource requests during the RAB modification process.
Measurement point
The measurement is triggered at point A as shown in Figure1. When receiving a RAB ASSIGNMENT REQUEST message with the cause value of "RABs To Be Modified", the RNC requests cell resources again for this UE. In this case, the RNC measures this item in the cell that the UE camps on. Figure 1-329 RAB reconfiguration procedure
Issue 01 (2013-05-04)
789
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.ReconfigCallReq Feature ID WRFD-020101 Feature Name Admission Control
1.12.1.39 Number of Successful Cell Resource Requests During SHO Counters

Counter ID 67181077 Counter Name VS.RAC.SHOCallAcc Counter Description Number of Successful Cell Resource Requests During SHO for Cell
Description
After receiving an intra-frequency measurement report from the UE, the RNC requests cell resources for a successful soft handover to a new cell. This counter provides the number of successful cell resource requests in the target cell where the UE is handed over during a soft handover.
Measurement point
The measurement is triggered at point B as shown in the following figure. After receiving the MEASUREMENT REPORT message from the UE, the RNC requests cell resources for soft handover to a new cell. If the request succeeds, the RNC measures the counter in the target cell for handover. If the request for multiple cells' resources succeeds, the RNC measures the counter in each cell.
Issue 01 (2013-05-04)
790
Figure 1-330 Successful handover admission
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.SHOCallAcc Feature ID WRFD-020101 Feature Name Admission Control
1.12.1.40 Number of Cell Resource Requests During SHO Counters

Counter ID 67181072 Counter Name VS.RAC.SHOCallReq Counter Description Number of Cell Resource Requests During SHO for Cell
Description
After receiving an intra-frequency measurement report from the UE, the RNC requests cell resource for soft handover to a new cell. This counter provides the number of cell resource requests for soft handover in the target cell for handover.
Measurement point
The measurement is triggered at point A as shown in the following figure. After receiving the MEASUREMENT REPORT message from the UE, the RNC requests cell resources for soft handover to a new cell. In this case, the RNC measures the counter in the target cell for handover. If the request for multiple cells' resources succeeds, the RNC measures the counter in each cell. Figure 1-331 Successful handover admission
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.SHOCallReq Feature ID WRFD-020101 Feature Name Admission Control
1.12.1.41 Number of Successful Cell Resource Requests During Channel Type Switch Counters
Counter ID 67181080 Counter Name VS.RAC.TrChSwitchCallAcc Counter Description Number of Successful Cell Resource Requests During Channel Type Switch for Cell
Issue 01 (2013-05-04)
792
Description
When a UE experiences a channel type change, such as from the FACH to the DCH or from the DCH to the FACH, the RNC requests cell resources for the UE again. This counter provides the number of successful cell resource requests in a cell during the channel type change. Only the number of successful cell resource requests in a cell during the channel type change is measured.
Measurement point
The measurement is triggered at point B as shown in the following figure. During a channel type change, the RNC requests related resources. If the resource request succeeds, the RNC measures the counter in the cell where the UE camps on. Figure 1-332
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.TrChSwitchCallAcc Feature ID WRFD-020101 Feature Name Admission Control
1.12.1.42 Number of Cell Resource Requests During Channel Type Switch

Counters
Counter ID 67181075 Counter Name VS.RAC.TrChSwitchCallReq Counter Description Number of Cell Resource Requests During Channel Type Switch for Cell
Description
The measurement is triggered at point A as shown in the following figure. When the type of channel where the UE occupies in a cell switches, the RNC requests related resources and measures the counter in the cell where the UE camps on.
Measurement point
When the type of channel where the UE occupies in a cell switches, the RNC requests cell resources for the UE. In this case, the RNC measures the counter in the cell where the UE camps on. Figure 1-333
Formula
None
Unit
None
Issue 01 (2013-05-04)
794
Related Features
Counter Name VS.RAC.TrChSwitchCallReq Feature ID WRFD-020101 Feature Name Admission Control
1.12.1.43 Counters Related to the Mean Number of Equivalent Voice UEs in CEL_DCH State Counters
Counter ID 67199663 Counter Name VS.RAC.UL.EqvUserNum Counter Description Mean Number of UL Equivalent Voice UEs in CEL_DCH State for Cell Mean Number of DL Equivalent Voice UEs in CEL_DCH State for Cell
67199664
VS.RAC.DL.EqvUserNum
Description
These counters provide the mean number of UL and DL equivalent UEs in CELL_DCH state in a cell within a measurement period.
Measurement point
In a measurement period, the RNC samples the number of equivalent UEs in the CELL_DCH state in the UL and DL every 5 seconds. At the end of the measurement period, the RNC divides the accumulated data from all the sampling points by the number of samples to obtain the values of the related counters.
Formula
None
Unit
None
Related Features
Counter Name VS.RAC.UL.EqvUserNum VS.RAC.DL.EqvUserNum
Issue 01 (2013-05-04)
Feature Name Admission Control Admission Control

795
1.12.1.44 Duration of Cell Dynamic Shutdown Due to Automatic Shutdown Counters

Counter ID 67204134 Counter Name VS.Cell.DynShutDown.Tim e Counter Description Duration of Cell Dynamic Shutdown Due to Automatic Shutdown for Cell
Description
This counter provides the duration of cell dynamic shutdown when the cell dynamic shutdown algorithm takes effect.
Measurement point
After a cell is set up, the RNC measures the accumulated duration of cell dynamic shutdown in the measurement period.
Formula
None
Unit
s
Related Features
Counter Name VS.Cell.DynShutDown.Tim e Feature ID WRFD-020117 WRFD-020122 Feature Name Multi-Carrier Switch off Based on Traffic Load Multi-Carrier Switch off Based on QoS
1.12.1.45 Cell Unavailability Duration caused by O&M (Cell) Counters

Counter ID 67199736 Counter Name VS.Cell.UnavailTime Counter Description Cell Unavailability Duration
Issue 01 (2013-05-04)
796
Description
This counter provides the duration of cell unavailability due to cell maintenance and operation.
Measurement point
After a cell is set up, all services may become unavailable in the cell if the cell is blocked on the LMT. In this case, the RNC measures the duration of service unavailability to obtain the value of this counter in a measurement period.
Formula
None
Unit
s
Related Features
Counter Name VS.Cell.UnavailTime Feature ID WRFD-031000 Feature Name Intelligently Out of Service
1.12.1.46 Counters Related to the Cell Credit Usage Counters

Counter ID 67202567 67191165 67191166 67202570 67191167 67191168 Counter Name VS.LC.ULCreditUsed.Mean VS.LC.ULCreditUsed.Max VS.LC.ULCreditUsed.Min VS.LC.DLCreditUsed.Mean VS.LC.DLCreditUsed.Max VS.LC.DLCreditUsed.Min Counter Description Mean Usage of UL Credit for Cell Maximum Usage of UL Credit for Cell Minimum Usage of UL Credit for Cell Mean Usage of DL Credit for Cell Maximum Usage of DL Credit for Cell Minimum Usage of DL Credit for Cell
Description
These counters provide uplink or downlink credit usage on the RNC side in a cell. Note: Credit resources on the RNC side are equivalent to CE resources on the NodeB side. The uplink credit
number is twice the number of uplink CEs, and the downlink credit number is equal to the number of downlink CEs. The CE-related counters measured at the RNC have different values from these measured at the NodeB. CE-related counters measured at the RNC are mainly used to estimate the access capability and are measured based on the number of CEs consumed in the access strategy. CE-related counters measured at the NodeB are mainly used to calculate the CEs that are actually used. In addition, the sampling period of the CE-related counters measured at the RNC is 5s, which is different from that of the CE-related counters measured at the NodeB (2 ms). Therefore, the counter values are not comparable, extremely when the NodeB dynamic CE function is enabled.
Measurement point
The RNC takes samples from the UL and DL credit usage in the cell every 5s. At the end of the measurement period, the RNC calculates the maximum and minimum credit usage, and divides the accumulated credit usage by the number of samples to obtain the mean usage of both UL and DL credit resources in the measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.LC.ULCreditUsed.Mean VS.LC.ULCreditUsed.Max VS.LC.ULCreditUsed.Min VS.LC.DLCreditUsed.Mean VS.LC.DLCreditUsed.Max VS.LC.DLCreditUsed.Min Feature ID WRFD-020101 WRFD-020101 WRFD-020101 WRFD-020101 WRFD-020101 WRFD-020101 Feature Name Admission Control Admission Control Admission Control Admission Control Admission Control Admission Control
1.12.1.47 Counters Related to the Duration of Max and Min Values of CPICH Power Due to Cell Breathing Counters
Counter ID 67202917 Counter Name VS.CellBreath.CPICHMin. Time Counter Description Duration of Minimum Values of CPICH Power Due to Cell Breathing for Cell
798
Issue 01 (2013-05-04)
Counter ID 67202918
Counter Name VS.CellBreath.CPICHMax. Time
Counter Description Duration of Maximum Values of CPICH Power Due to Cell Breathing for Cell
Description
These counters provide the duration of maximum or minimum value of P-CPICH power due to the downlink load-based dynamic adjustment of P-CPICH algorithm in a cell. Note: 1. The downlink load-based dynamic adjustment of P-CPICH algorithm refers to the TCP-based intrafrequency load balancing algorithm or load-based dynamic adjustment of P-CPICH algorithm. 2. The preceding two algorithms mutually exclude each other. When the two algorithms are enabled at the same time, the load-based dynamic adjustment of P-CPICH algorithm takes precedence. 3. If the two algorithms are disabled in the measurement period, the value of this counter is zero.
Measurement point
When the downlink cell power load in a cell is heavy according to the load level specified by the dynamic adjustment of P-CPICH algorithm, the RNC needs to reduce the power of P-CPICH. However, if the power of P-CPICH reaches the minimum value, the P-CPICH power cannot be reduced. The controlling RNC (CRNC) measures the accumulated duration of the maximum value of P-CPICH power for a cell in the measurement period. When the downlink cell power load in a cell is light according to the load level specified by the dynamic adjustment of P-CPICH algorithm, the RNC needs to increase the power of P-CPICH. However, if the power of P-CPICH reaches the maximum value, P-CPICH power cannot be increased. The CRNC measures the accumulated duration of the minimum value of P-CPICH power for a cell in the measurement period.
Formula
None
Unit
s
Related Features
Counter Name VS.CellBreath.CPICHMin. Time VS.CellBreath.CPICHMax. Time Feature ID WRFD-020104 WRFD-020104 Feature Name Intra Frequency Load Balance Intra Frequency Load Balance
Issue 01 (2013-05-04)
799
1.12.1.48 Counters Related to the Number of CPICH Power Adjustments Due to Cell Breathing Counters
Counter ID 67190846 Counter Name VS.CellBreath.CPICHUp Counter Description Number of Upward CPICH Power Adjustments Due to Cell Breathing for Cell Number of Downward CPICH Power Adjustments Due to Cell Breathing for Cell
67190847
VS.CellBreath.CPICHDown
Description
These counters provide the number of P-CPICH power adjustments due to the downlink loadbased dynamic adjustment of P-CPICH algorithm in a cell.
Measurement point
When the downlink cell power load in a cell is heavy according to the load level specified by the dynamic adjustment of P-CPICH algorithm, the RNC needs to reduce the power of P-CPICH. When the downlink cell power load in a cell is light according to the load level specified by the dynamic adjustment of P-CPICH algorithm, the RNC needs to increase the power of P-CPICH. The CRNC measures the number of P-CPICH power adjustments for a cell in the measurement period. Note: 1. The downlink load-based dynamic adjustment of P-CPICH algorithm refers to the TCP-based intra-frequency load balancing algorithm or load-based dynamic adjustment of P-CPICH algorithm. If the former algorithm is used, downlink power refers to transmitted carrier power (TCP). If the latter is used, downlink power refers to non-HSDPA transmit power (NonHSTCP). 2. The preceding two algorithms mutually exclude each other. When the two algorithms are enabled at the same time, the load-based dynamic adjustment of P-CPICH algorithm takes precedence. 3. If the two algorithms are disabled in the measurement period, the value of this counter is zero.
Formula
None
Unit
None
Issue 01 (2013-05-04)
800
Related Features
Counter Name VS.CellBreath.CPICHUp VS.CellBreath.CPICHDown Feature ID WRFD-020104 WRFD-020104 Feature Name Intra Frequency Load Balance Intra Frequency Load Balance
1.12.1.49 Counters Related to the Duration of TCP Underload and Overload Counters
Counter ID 67202919 Counter Name VS.CellBreath.TCPUnder.T ime VS.CellBreath.TCPOver.Ti me Counter Description Duration of TCP Smaller Than Cell Breathing Lower Threshold for Cell Duration of TCP Greater Than Cell Breathing Upper Threshold for Cell
67202920
Description
These counters provide the overloaded or underloaded duration of transmit carrier power (TCP) specified by the TCP-based intra-frequency load balancing algorithm in a cell. When the cell TCP load is lower than a specified threshold, the cell is in the underloaded state. When the cell TCP load is higher than a specified threshold, the cell is in overloaded state.
Measurement point
The CRNC measures the accumulated duration in which the TCP is higher than the overloaded threshold or the accumulated duration in which the TCP is lower than the underloaded threshold in the measurement period for a cell. Note: The values of these counters are not affected by whether the TCP-based intra-frequency load balancing algorithm is enabled or not in the measurement period.
Formula
None
Unit
s
Issue 01 (2013-05-04)
801
Related Features
Counter Name VS.CellBreath.TCPUnder.T ime VS.CellBreath.TCPOver.Ti me Feature ID WRFD-020104 WRFD-020104 Feature Name Intra Frequency Load Balance Intra Frequency Load Balance
1.12.1.50 Average CPICH Power for Cell Counters

Counter ID 67202921 Counter Name VS.CPICH.MeanPwr Counter Description Average CPICH Power for Cell
Description
This counter provides the average P-CPICH power in a cell. Note: When the dynamic adjustment of P-CPICH algorithm (including the RTWP/TCP-based intra-frequency load balancing algorithm and load-based dynamic adjustment of P-CPICH algorithm) is enabled, the RNC adjusts P-CPICH power based on cell load. This counter is measured based on the adjusted PCPICH power.
Measurement point
The RNC takes samples P-CPICH power in a cell every 5s. At the end of the measurement period, the average P-CPICH power is obtained by dividing the accumulated P-CPICH power by the number of samples.
Formula
None
Unit
dBm
Related Features
Counter Name VS.CPICH.MeanPwr Feature ID WRFD-020101 Feature Name Admission Control
Issue 01 (2013-05-04)
802
1.12.1.51 Counters Related to the Number of Dynamic Channel Conversion Attempts Between DCHs and FACHs Counters
Counter ID 67190707 Counter Name VS.DCCC.C2D.Att Counter Description Number of Dynamic Channel Conversion Attempts from FACHs to DCHs for Cell Number of Dynamic Channel Conversion Attempts from DCHs to FACHs for Cell
67190706
VS.DCCC.D2C.Att
Description
These counters provide the number of conversion attempts from the DCH to the FACH or from FACH to DCH. When a UE in the CELL_DCH state performs a soft handover or softer handover, the number of successful conversions from the DCH to the FACH is measured in the best cell where the UE camps on before state transition.
Measurement point
The measurement is triggered at point A as shown in the following figure. In the process of state transition, when the RNC receives the RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the RNC measures the related counter in the best cell where the UE camps on before the state transition if the DCH is converted to the FACH. If the FACH is converted to the DCH, the RNC measures the related counter in the cell where the UE in the CELL_FACH state camps on after the state transition. Figure 1-334 Dynamic channel conversion procedure (RB reconfiguration)
Issue 01 (2013-05-04)
803
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.C2D.Att Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC) Dynamic Channel Configuration Control (DCCC)
VS.DCCC.D2C.Att
WRFD-021101
1.12.1.52 Number of UL Rate Increases for AMR WB Speech Service Counters

Counter ID 67192003 Counter Name VS.AMRWB.ULRateUp Counter Description Number of Increases of UL Rate for AMR WB Speech Service Number of UL Rate Increases for AMR Services for Cell Number of UL Rate Decreases for AMR Services for Cell Number of Decreases of UL Rate for AMR WB Speech Service
67190520
VS.AMR.UL.RateUp
67180677
VS.AMR.UL.RateDown
67192004
VS.AMRWB.ULRateDown
Description
These counters provide the number of times the UL rate of narrowband or wideband AMR services is adjusted upward and downward.
Measurement point
The measurement is triggered at point A as shown in the following figure. The RNC sends TRANSPORT FORMAT COMBINATION CONTROL messages to UEs to request an increase or decrease in the UL rate of narrowband or wideband AMR services. If the RNC does not receive TRANSPORT FORMAT COMBINATION CONTROL FAILURE messages from UEs, the UL rate of AMR services successfully increases or decreases. In this case, the RNC measures the counters in the best cell where the UE camps on. Figure 1-335 UL AMR rate adjustment procedure
Formula
None
Unit
None
Related Features
Counter Name VS.AMRWB.ULRateUp VS.AMR.UL.RateUp VS.AMR.UL.RateDown VS.AMRWB.ULRateDown Feature ID WRFD-020701 WRFD-020701 WRFD-020701 WRFD-020701 Feature Name AMR/WB-AMR Speech Rates Control AMR/WB-AMR Speech Rates Control AMR/WB-AMR Speech Rates Control AMR/WB-AMR Speech Rates Control
1.12.1.53 Counters Related to the Number of UL EDCH DCCC Attempts Based on Throughput or RLC BO
Counters
Counter ID 67184359 Counter Name VS.DCCC.AttUpsizing.E2E .Thr Counter Description Number of UL EDCHEDCH DCCC Upsizing Attempts Based on the Throughput or RLC BO for Cell Number of UL EDCHEDCH DCCC Downsizing Attempts Based on the Throughput or RLC BO for Cell
67196026
VS.DCCC.AttDownsizing.E 2E.Thr
Description
These counters provide the number of rate increase and decrease attempts for uplink E-DCH BE services according to DCCC strategies, DCCC based on traffic volume and DCCC based on throughput, in the HSUPA serving cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending the RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the counters based on decreases and increases in BE services due to different DCCC strategies in HSUPA serving cell if uplink services are carried on the E-DCH before and after the reconfiguration. Figure 1-336 RB reconfiguration procedure
Issue 01 (2013-05-04)
806
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.AttUpsizing.E2E .Thr VS.DCCC.AttDownsizing.E 2E.Thr Feature ID WRFD-01061208 WRFD-01061208 Feature Name HSUPA DCCC HSUPA DCCC
1.12.1.54 Counters Related to the Number of Successful UL EDCH DCCC Operations Based on Throughput or RLC BO Counters
Counter ID 67196027 Counter Name VS.DCCC.SuccUpsizing.E2 E.Thr Counter Description Number of Successful UL EDCH-EDCH DCCC Upsizings Based on the Throughput or RLC BO for Cell Number of Successful UL EDCH-EDCH DCCC Downsizings Based on the Throughput or RLC BO for Cell
67196028
VS.DCCC.SuccDownsizing. E2E.Thr
Description
These counters provide the number of successful times the RNC increases and decreases uplink E-DCH BE services according to DCCC strategies, DCCC based on traffic volume and DCCC based on throughput, in the HSUPA serving cell.
Measurement point
The measurement is triggered at point B as shown in the following figure. When receiving the RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the RNC
measures the counters based on decreases and increases in BE services due to different DCCC strategies in HSUPA serving cell if uplink services are carried on the E-DCH before and after the reconfiguration. Figure 1-337 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.SuccUpsizing.E2 E.Thr VS.DCCC.SuccDownsizing. E2E.Thr Feature ID WRFD-01061208 WRFD-01061208 Feature Name HSUPA DCCC HSUPA DCCC
1.12.1.55 Number of UEs Performing Code Adjustment Based on HSDPA

Counters
Counter ID 67195992 Counter Name VS.LCC.HSDPA.CodeAdj. Att Counter Description Number of UEs Performing Code Adjustment Based on HSDPA for Cell
Description
In order to get more available HSDPA codes, the RNC shall select certain UEs to perform code adjustments. This counter provides the number of UEs that perform code adjustment attempts based on the HSDPA in a cell. For DC-HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in the following figure. The RNC measures the counter in the best cell where the UE camps on every time the RNC selects a UE to perform code adjustment attempt and sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE. Figure 1-338
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.HSDPA.CodeAdj. Att Feature ID WRFD-020108 Feature Name Code Resource Management
1.12.1.56 Number of DL DCH DCCC Upsizing Attempts Based on Throughput or RLC BO Counters
Counter ID 67192585 Counter Name VS.DCCC.AttUpsizing.DL. Thr Counter Description Number of DL DCH DCCC Upsizing Attempts Based on Throughput or RLC BO for Cell
Description
This counter provides the number of rate increase attempts for downlink DCH BE services on the UE according to DCCC strategies, DCCC based on traffic volume and DCCC based on throughput, in the best cell where the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending the RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the counter based on different DCCC strategies in the best cell where the UE camps on if downlink services are carried on the DCH before and after the reconfiguration.
Issue 01 (2013-05-04)
810
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.AttUpsizing.DL. Thr Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.1.57 Number of Successful DL DCH DCCC Upsizings Based on Throughput or RLC BO
Issue 01 (2013-05-04)
811
Counters
Counter ID 67192586 Counter Name VS.DCCC.SuccUpsizing.D L.Thr Counter Description Number of Successful DL DCH DCCC Upsizings Based on Throughput or RLC BO for Cell
Description
This counter provides the number of successful times the RNC increases downlink DCH BE services on the UE according to DCCC strategies, DCCC based on traffic volume and DCCC based on throughput, in the best cell where the UE camps on.
Measurement point
The measurement is triggered at point B as shown in the following figure. When receiving the RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the RNC measures the counter based on different DCCC strategies in the best cell where the UE camps on if downlink services are carried on the DCH before and after the reconfiguration. Figure 1-340 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.SuccUpsizing.D L.Thr Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.1.58 Number of UL DCH DCCC Upsizing Attempts Based on Throughput or RLC BO Counters
Counter ID 67192593 Counter Name VS.DCCC.AttUpsizing.UL. Thr Counter Description Number of UL DCH DCCC Upsizing Attempts Based on Throughput or RLC BO for Cell
Description
This counter provides the number of rate increase attempts for uplink DCH BE services on the UE according to DCCC strategies, DCCC based on traffic volume and DCCC based on throughput, in the best cell where the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending the RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the counter based on different DCCC strategies in the best cell where the UE camps on if uplink services are carried on the DCH before and after the reconfiguration.
Issue 01 (2013-05-04)
813
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.AttUpsizing.UL. Thr Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.1.59 Number of Successful UL DCH DCCC Upsizings Based on Throughput or RLC BO
Issue 01 (2013-05-04)
814
Counters
Counter ID 67192594 Counter Name VS.DCCC.SuccUpsizing.U L.Thr Counter Description Number of Successful UL DCH DCCC Upsizings Based on Throughput or RLC BO for Cell
Description
This counter provides the number of successful times the RNC increases uplink DCH BE services on the UE according to DCCC strategies, DCCC based on traffic volume and DCCC based on throughput, in the best cell where the UE camps on.
Measurement point
The measurement is triggered at point B as shown in the following figure. When receiving the RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the RNC measures the counter based on different DCCC strategies in the best cell where the UE camps on if uplink services are carried on the DCH before and after the reconfiguration. Figure 1-342 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.SuccUpsizing.U L.Thr Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.1.60 Counters Related to the Number of UL DCH DCCC Downsizing Attempts Based on Different Strategies Counters
Counter ID 67192595 Counter Name VS.DCCC.AttDownsizing. UL.Thr Counter Description Number of UL DCH DCCC Downsizing Attempts Based on the Throughput or RLC BO for Cell Number of UL DCH DCCC Downsizing Attempts Based on the Coverage (QoS) for Cell Number of UL DCH DCCC Downsizing Attempts Based on the Resource Congestion Algorithm for Cell
67196032
VS.DCCC.AttDownsizing. UL.Cov
67196034
VS.DCCC.AttDownsizing. UL.Cong
Description
These counters provide the number of rate decrease attempts for uplink DCH BE services on the UE according to DCCC strategies in the best cell where the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending the RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the related counter based on different DCCC strategies in the best cell where the UE camps on if uplink services are carried on the DCH before and after the reconfiguration.
Issue 01 (2013-05-04)
816
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.AttDownsizing. UL.Thr VS.DCCC.AttDownsizing. UL.Cov VS.DCCC.AttDownsizing. UL.Cong Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC) Dynamic Channel Configuration Control (DCCC) Dynamic Channel Configuration Control (DCCC)
WRFD-021101
WRFD-021101
1.12.1.61 Counters Related to the Number of Successful UL DCH DCCC Downsizings Based on Different Strategies
Counters
Counter ID 67192596 Counter Name VS.DCCC.SuccDownsizing. UL.Thr Counter Description Number of Successful UL DCH DCCC Downsizings Based on Throughput or RLC BO for Cell Number of Successful UL DCH DCCC Downsizings Based on Coverage (QoS) for Cell Number of Successful UL DCH DCCC Downsizings Based on Resource Congestion Algorithm for Cell
67196033
VS.DCCC.SuccDownsizing. UL.Cov
67196035
VS.DCCC.SuccDownsizing. UL.Cong
Description
These counters provide the number of successful times the RNC decreases uplink DCH BE services on the UE based on different strategies in the best cell where the UE camps on.
Measurement point
The measurement is triggered at point B as shown in the following figure. When receiving the RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the related counter based on different DCCC strategies in the best cell where the UE camps on if uplink services are carried on the DCH before and after the reconfiguration. Figure 1-344 RB reconfiguration procedure
Issue 01 (2013-05-04)
818
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.SuccDownsizing. UL.Thr VS.DCCC.SuccDownsizing. UL.Cov VS.DCCC.SuccDownsizing. UL.Cong Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC) Dynamic Channel Configuration Control (DCCC) Dynamic Channel Configuration Control (DCCC)
WRFD-021101
WRFD-021101
1.12.1.62 Number of UEs Performing Successful Code Adjustment in DL Basic Congestion Counters
Counter ID 67193409 Counter Name VS.LCC.LDR.CodeAdj.Suc c Counter Description Number of UEs Performing Successful Code Adjustment in DL Basic Congestion for Cell
Description
When the cell is in basic congestion, the counter provides the number of UEs that has performed code adjustment successfully in a cell. When a cell is in basic congestion of downlink code resources, the RNC selects certain UEs in the cell to perform code adjustment so that some idle codes are combined to meet the requirement of a higher rate.
Measurement point
When a cell is in basic congestion, the RNC selects certain UEs in the cell to perform code adjustment. Upon receiving the PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message from the UEs, the RNC determines that code adjustment is successful. In this case, this counter is measured in the cell where the selected UEs camp on.
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.LDR.CodeAdj.Suc c Feature ID WRFD-020108 Feature Name Code Resource Management
1.12.1.63 Number of UEs Performing Successful Code Adjustment Based on HSDPA Counters
Counter ID 67193410 Counter Name VS.LCC.HSDPA.CodeAdj. Succ Counter Description Number of UEs Performing Successful Code Adjustment Based on HSDPA for Cell
Description
In order to get more available HSDPA codes, the RNC shall select certain UEs to perform code adjustments. This counter provides the number of UEs that perform successful code adjustments based on the HSDPA in a cell. For DC-HSDPA users, this counter is measured only in the cell with the primary carrier. This counter reflects the success rate of code adjustments.
Measurement point
The measurement is triggered at point B as shown in the following figure. The RNC measures the counter in the best cell where the UE camps on every time the RNC selects a UE to perform code adjustment attempt and receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE.
Issue 01 (2013-05-04)
820
Figure 1-345
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.HSDPA.CodeAdj. Succ Feature ID WRFD-020108 Feature Name Code Resource Management
1.12.1.64 Duration of Cell Unavailability Due to System Faults Counters

Counter ID 67204837 Counter Name VS.Cell.UnavailTime.Sys Counter Description Duration of Cell Unavailability Due to System Faults for Cell
Issue 01 (2013-05-04)
821
Description
This counter provides the duration of cell unavailability due to system faults of the RNC in a cell. Cell unavailability is caused by various reasons, such as cell setup failures, common channel faults, or NCP/CCP port faults.
Measurement point
After a cell is set up, the cell may be out of service if the cell is not blocked through the LMT in the measurement period. In this case, the RNC measures the accumulated duration of cell unavailability to obtain the value of this counter. When the cell is out of service, no services can be performed.
Formula
None
Unit
s
Related Features
Counter Name VS.Cell.UnavailTime.Sys Feature ID WRFD-031000 Feature Name Intelligently Out of Service
1.12.1.65 Duration of HSDPA Service Unavailability Due to System Fault Counters

Counter ID 67204838 Counter Name VS.Cell.HSDPA.UnavailTime Counter Description Duration of HSDPA Service Unavailability Due to System Fault for Cell
Description
This counter provides the duration of HSDPA service unavailability due to system faults of the RNC in a cell. The counter is not measured when the whole cell is unavailable. For DC-HSDPA users, this counter is measured only in the primary cell. System faults are caused by various reasons, such as the HSDPA channel fails to be set up or the state of the HSDPA channel changes from available to unavailable.
Measurement point
In a measurement period, after a cell is set up, the RNC measures the duration of HSDPA service unavailability in a cell provided that the HSDPA service is not barred through the LMT.
Formula
None
Unit
s
Related Features
Counter Name VS.Cell.HSDPA.UnavailTime Feature ID WRFD-031000 Feature Name Intelligently Out of Service
1.12.1.66 Duration of HSUPA Service Unavailability Due to System Fault Counters

Counter ID 67204839 Counter Name VS.Cell.HSUPA.UnavailTime Counter Description Duration of HSUPA Service Unavailability Due to System Fault for Cell
Description
This counter provides the duration of HSUPA service unavailability due to system faults of the RNC in a cell. The counter is not measured when the whole cell is unavailable. For DC-HSUPA users, this counter is measured only in the primary cell.
Measurement point
In a measurement period, after a cell is set up, the RNC measures the duration of HSUPA service unavailability in a cell provided that the HSUPA service is not barred through the LMT.
Formula
None
Unit
s
Issue 01 (2013-05-04)
823
Related Features
Counter Name VS.Cell.HSUPA.UnavailTime Feature ID WRFD-031000 Feature Name Intelligently Out of Service
1.12.1.67 Number of Attempts to transfer state from CELL_PCH to CELL_FACH for cell Counters
Counter ID 73403799 Counter Name VS.DCCC.P2F.Att Counter Description Number of Attempts to transfer state from CELL_PCH to CELL_FACH for cell
Description
This counter provides the number of state transition attempts from CELL_PCH to CELL_FACH in the cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends the UE a CELL UPDATE CONFIRM message, the RNC measures the counter in the best cell that the UE camps on if the UE tries to transit from CELL_PCH to CELL_FACH. Figure 1-346 cell update
Issue 01 (2013-05-04)
824
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.P2F.Att Feature ID WRFD-010202 WRFD-021101 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Dynamic Channel Configuration Control (DCCC)
1.12.1.68 Number of Successful state transfer from CELL_PCH to CELL_FACH for cell Counters
Counter ID 73403800 Counter Name VS.DCCC.P2F.Succ Counter Description Number of Successful state transfer from CELL_PCH to CELL_FACH for cell
Description
This counter provides the number of successful state transitions from CELL_PCH to CELL_FACH in the best cell.
Measurement point
The measurement is triggered at point C as shown in the figure. When the RNC received from the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message after sending a CELL UPDATE CONFIRM message to the UE, the RNC measures the counter in the best cell that the UE camps on, if the UE transits from CELL_PCH to CELL_FACH.
Issue 01 (2013-05-04)
825
Figure 1-347 CELL UPDATE
The measurement is triggered at point C as shown in the figure. When the RNC received from the UE a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message after sending a CELL UPDATE CONFIRM message to the UE, the RNC measures the counter in the best cell that the UE camps on, if the UE transits from CELL_PCH to CELL_FACH. Figure 1-348
The measurement is triggered at point C as shown in the figure. When the RNC received from the UE a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message after sending a CELL UPDATE CONFIRM message to the UE, the RNC measures the counter in the best cell that the UE camps on, if the UE transits from CELL_PCH to CELL_FACH.
Issue 01 (2013-05-04)
826
Figure 1-349
The measurement is triggered at point C as shown in the figure. When the RNC received from the UE a RADIO BEARER RECONFIGURATION COMPLETE message after sending a CELL UPDATE CONFIRM message to the UE, the RNC measures the counter in the best cell that the UE camps on, if the UE transits from CELL_PCH to CELL_FACH. Figure 1-350
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.P2F.Succ Feature ID WRFD-010202 WRFD-021101 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Dynamic Channel Configuration Control (DCCC)
1.12.1.69 Number of state transfer from CELL_PCH to URA_PCH for cell Counters
Counter ID 73403801 Counter Name VS.DCCC.P2URAP Counter Description Number of state transfer from CELL_PCH to URA_PCH for cell
Description
This counter provides the number of state transition attempts from CELL_PCH to URA_PCH in the cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends the UE a CELL UPDATE CONFIRM message after receiving a CELL UPDATE message from the UE, the RNC measures the counter in the best cell that the UE camps on, if the UE tries to transit from CELL_PCH to URA_PCH.
Issue 01 (2013-05-04)
828
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.P2URAP Feature ID WRFD-010202 WRFD-021101 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Dynamic Channel Configuration Control (DCCC)
1.12.1.70 Number of Attempts to transfer state from URA_PCH to CELL_FACH for cell
Issue 01 (2013-05-04)
829
Counters
Counter ID 73403802 Counter Name VS.DCCC.URAP2F.Att Counter Description Number of Attempts to transfer state from URA_PCH to CELL_FACH for cell
Description
This counter provides the number of state transition attempts from URA_PCH to CELL_FACH in the cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends the UE a CELL UPDATE CONFIRM message after receiving a CELL UPDATE message from the UE, the RNC measures the counter in the best cell that the UE camps on, if the UE tries to transit from URA_PCH to CELL_FACH. Figure 1-352 CELL UPDATE
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.URAP2F.Att Feature ID WRFD-010202 WRFD-021101 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Dynamic Channel Configuration Control (DCCC)
1.12.1.71 Number of successful state transfer from URA_PCH to CELL_FACH in the best cell Counters
Counter ID 73403803 Counter Name VS.DCCC.URAP2F.Succ Counter Description Number of successful state transfer from URA_PCH to CELL_FACH in the best cell.
Description
This counter provides the number of successful state transitions from URA_PCH to CELL_FACH in the best cell.
Measurement point
The measurement is triggered at point C as shown in the figure. When the RNC receives from the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to a UE, the RNC measures the counter in the best cell that the UE camps on, if the UE transits from URA_PCH to CELL_FACH.
Issue 01 (2013-05-04)
831
The measurement is triggered at point C as shown in the figure. When the RNC receives from the UE a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message after sending a CELL UPDATE CONFIRM message to a UE, the RNC measures the counter in the best cell that the UE camps on, if the UE transits from URA_PCH to CELL_FACH. Figure 1-354
The measurement is triggered at point C as shown in the figure. When the RNC receives from the UE a UTRAN MOBILITY INFORMATION CONFIRM message after sending a CELL UPDATE CONFIRM message to a UE, the RNC measures the counter in the best cell that the UE camps on, if the UE transits from URA_PCH to CELL_FACH.
Issue 01 (2013-05-04)
832
Figure 1-355
The measurement is triggered at point C as shown in the figure. When the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message after sending a CELL UPDATE CONFIRM message to a UE, the RNC measures the counter in the best cell that the UE camps on, if the UE transits from URA_PCH to CELL_FACH. Figure 1-356
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.URAP2F.Succ Feature ID WRFD-010202 WRFD-021101 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Dynamic Channel Configuration Control (DCCC)
1.12.1.72 Number of Cell Deletions or Establishments Due to Dynamic Cell Shutdown Counters
Counter ID 73393802 Counter Name VS.DynClose.CellDel Counter Description Number of Cell Deletions Due to Dynamic Cell Shutdown Number of Cell Setup Due to Dynamic Cell Shutdown
73393803
VS.DynOpen.CellSetup
Description
These counters provide the number of cell deletions or establishments due to dynamic cell shutdown in a cell.
Measurement point
After dynamic cell shutdown takes effect, if the conditions of dynamic cell shutdown are met and the action of shutdown or power-on is triggered, this counter is increased by one when the cell is deleted or set up. The accumulated number of cell deletions or establishments is the value of this counter.
Formula
None
Unit
None
Issue 01 (2013-05-04)
834
Related Features
Counter Name VS.DynClose.CellDel Feature ID WRFD-020117 WRFD-020122 Feature Name Multi-Carrier Switch off Based on Traffic Load Multi-Carrier Switch off Based on QoS VS.DynOpen.CellSetup WRFD-020117 WRFD-020122 Multi-Carrier Switch off Based on Traffic Load Multi-Carrier Switch off Based on QoS
1.12.1.73 Number of State Transfer Attempts from CELL_DCH to CELL_PCH for Cell Counters
Counter ID 73421765 Counter Name VS.DCCC.D2P.Att Counter Description Number of State Transfer Attempts from CELL_DCH to CELL_PCH for Cell
Description
This counter provides the number of state transition attempts from CELL_DCH to CELL_FACH or URA_PCH in the cell. When a UE in the CELL_DCH state performs a soft handover or softer handover, the counter is measured in the best cell in the active set for soft handovers. The best cell is obtained before the state transition.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending the RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the counter in the best cell where the UE camps on if the state is transited from CELL_DCH to CELL_PCH or URA_PCH.
Issue 01 (2013-05-04)
835
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.D2P.Att Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.1.74 Number of Successful State Transfers from CELL_DCH to CELL_PCH for Cell
Issue 01 (2013-05-04)
836
Counters
Counter ID 73421766 Counter Name VS.DCCC.D2P.Succ Counter Description Number of Successful State Transfers from CELL_DCH to CELL_PCH for Cell
Description
This counter provides the number of successful state transitions from CELL_DCH to CELL_FACH or URA_PCH in the cell. When a UE in the CELL_DCH state performs a soft handover or softer handover, the counter is measured in the best cell in the active set for soft handovers. The best cell is obtained before the state transition.
Measurement point
The measurement is triggered at point B as shown in the following figure. When receiving the RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the RNC measures the counter in the best cell where the UE camps on if the state is transferred from CELL_DCH to CELL_PCH. Figure 1-358 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.D2P.Succ Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.1.75 Number of State Transfer Attempts from CELL_DCH or CELL_FACH to CELL_PCH for FAST DORMANCY user for Cell Counters
Counter ID 73421767 Counter Name VS.DCCC.FastDormUe.DF 2P.Att Counter Description Number of State Transfer Attempts from CELL_DCH or CELL_FACH to CELL_PCH for FAST DORMANCY user for Cell
Description
This counter provides the number of state transition attempts from CELL_DCH or CELL_FACH to CELL_PCH or URA_PCH for Fast Dormancy user in a cell. When a UE in the CELL_DCH state performs a soft handover or softer handover, the counter is measured in the best cell in the active set for soft handovers. The best cell is obtained before the state transition. In case of the state transition from CELL_FACH to CELL_PCH or UAR_PCH, the counter is measured in the cell where the UE in the CELL_FACH state camps on.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to a UE supporting the fast dormancy function, instructing the UE to transit from the CELL_FACH or CELL_DCH state to the CELL_PCH or URA_PCH state, this counter is incremented by one in the cell where the UE is camping. When a UE in the CELL_DCH state performs a soft handover or softer handover, the counter is measured in the best cell in the active set for soft handovers. The best cell is obtained before the state transition.
Issue 01 (2013-05-04)
838
Figure 1-359 physical channel reconfiguration procedure
The measurement is triggered at point A as shown in the following figure. When the RNC sends a RADIO BEARER RECONFIGURATION message to a UE supporting the fast dormancy function, instructing the UE to transit from the CELL_FACH or CELL_DCH state to the CELL_PCH or URA_PCH state, this counter is incremented by one in the cell where the UE is camping. When a UE in the CELL_DCH state performs a soft handover or softer handover, the counter is measured in the best cell in the active set for soft handovers. The best cell is obtained before the state transition. Figure 1-360
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.FastDormUe.DF 2P.Att Feature ID WRFD-020500 Feature Name Enhanced Fast Dormancy
1.12.1.76 Number of Successful State Transfers from CELL_DCH or CELL_FACH to CELL_PCH for FAST DORMANCY user Counters
Counter ID 73421768 Counter Name VS.DCCC.FastDormUe.DF 2P.Succ Counter Description Number of Successful State Transfers from CELL_DCH or CELL_FACH to CELL_PCH for FAST DORMANCY user for Cell
Description
This counter provides the number of successful state transitions from CELL_DCH or CELL_FACH to CELL_PCH or URA_PCH for Fast Dormancy user in a cell. When a UE in the CELL_DCH state performs a soft handover or softer handover, the counter is measured in the best cell in the active set for soft handovers. The best cell is obtained before the state transition. In case of the state transition from CELL_FACH to CELL_PCH or UAR_PCH, the counter is measured in the cell where the UE in the CELL_FACH state camps on.
Measurement point
The measurement is triggered at point B as shown in the following figure. When the RNC receives a message from a UE supporting the fast dormancy feature, indicating that the UE has transited from the CELL_FACH or CELL_DCH state to the CELL_PCH state, this counter is incremented by one in the cell where the UE is camping. When a UE in the CELL_DCH state performs a soft handover or softer handover, the counter is measured in the best cell in the active set for soft handovers. The best cell is obtained before the state transition.
Issue 01 (2013-05-04)
840
Figure 1-361 physical channel reconfiguration procedure
The measurement is triggered at point B as shown in the following figure. When the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from a UE supporting the fast dormancy feature, indicating that the UE has transited from the CELL_FACH or CELL_DCH state to the CELL_PCH state, this counter is incremented by one in the cell where the UE is camping. When a UE in the CELL_DCH state performs a soft handover or softer handover, the counter is measured in the best cell in the active set for soft handovers. The best cell is obtained before the state transition. Figure 1-362
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.FastDormUe.DF 2P.Succ Feature ID WRFD-020500 Feature Name Enhanced Fast Dormancy
1.12.1.77 Number of Attempts to transfer state from CELL_PCH to CELL_DCH for cell Counters
Counter ID 73421933 Counter Name VS.DCCC.P2D.Att Counter Description Number of Attempts to transfer state from CELL_PCH to CELL_DCH for cell
Description
This counter provides the number of state transition attempts from CELL_PCH to CELL_DCH in the cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends the UE a CELL UPDATE CONFIRM message, the RNC measures the counter in the cell where the UE camps on before the state transition, if the UE tries to transit from CELL_PCH to CELL_DCH.
Issue 01 (2013-05-04)
842
Figure 1-363 cell update
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.P2D.Att Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.1.78 Number of Successful state transfer from CELL_PCH to CELL_DCH for cell
Issue 01 (2013-05-04)
843
Counters
Counter ID 73421934 Counter Name VS.DCCC.P2D.Succ Counter Description Number of Successful state transfer from CELL_PCH to CELL_DCH for cell
Description
This counter provides the number of successful state transitions from CELL_PCH to CELL_DCH in the cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives the UE a RADIO BEARER RECONFIGURATION COMPLETE message, the RNC measures the counter in the cell where the UE camps on before the state transition, if the UE transits from CELL_PCH to CELL_DCH. Figure 1-364 CELL UPDATE
Formula
None
Issue 01 (2013-05-04)
844
Unit
None
Related Features
Counter Name VS.DCCC.P2D.Succ Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.1.79 Number of Attempts to transfer state from URA_PCH to CELL_DCH for cell Counters
Counter ID 73421935 Counter Name VS.DCCC.URAP2D.Att Counter Description Number of Attempts to transfer state from URA_PCH to CELL_DCH for cell
Description
This counter provides the number of state transition attempts from URA_PCH to CELL_DCH in the cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends the UE a CELL UPDATE CONFIRM message, the RNC measures the counter in the cell where the UE camps on before the state transition, if the UE tries to transit from URA_PCH to CELL_DCH.
Issue 01 (2013-05-04)
845
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.URAP2D.Att Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.1.80 Number of successful state transfer from URA_PCH to CELL_DCH in the best cell
Issue 01 (2013-05-04)
846
Counters
Counter ID 73421936 Counter Name VS.DCCC.URAP2D.Succ Counter Description Number of successful state transfer from URA_PCH to CELL_DCH in the best cell.
Description
This counter provides the number of successful state transitions from URA_PCH to CELL_DCH in the cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives the UE a RADIO BEARER RECONFIGURATION COMPLETE message, the RNC measures the counter in the cell where the UE camps on before the state transition, if the UE transits from URA_PCH to CELL_DCH. Figure 1-366 CELL UPDATE
Formula
None
Issue 01 (2013-05-04)
847
Unit
None
Related Features
Counter Name VS.DCCC.URAP2D.Succ Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.1.81 Number of Attempts of CELL_PCH/URA_PCH-to-CELL_DCH State Transition Together with DRD for Cell Counters
Counter ID 73422068 Counter Name VS.DCCC.P2D.DRD.Att Counter Description Number of Attempts of CELL_PCH/URA_PCH-toCELL_DCH State Transition Together with DRD for Cell
Description
This counter provides the number of times the RNC attempts to trigger the state transition from CELL_PCH or URA_PCH to CELL_DCH together with DRD in a cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends the UE a CELL UPDATE CONFIRM message, instructing the UE to transfer its state from CELL_PCH or URA_PCH to CELL_DCH and to trigger DRD, this counter is measured in the cell that the UE camps on when sending the CELL UPDATE message.
Issue 01 (2013-05-04)
848
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.P2D.DRD.Att Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.1.82 Number of Successful CELL_PCH/URA_PCH-to-CELL_DCH State Transitions Together with DRDs for Cell
Issue 01 (2013-05-04)
849
Counters
Counter ID 73422069 Counter Name VS.DCCC.P2D.DRD.Succ Counter Description Number of Successful CELL_PCH/URA_PCH-toCELL_DCH State Transitions Together with DRDs for Cell
Description
This counter provides the number of times a UE successfully transit its state from CELL_PCH or URA_PCH to CELL_DCH together with DRDs in a cell.
Measurement point
The measurement is triggered at point C as shown in the figure. When the RNC received RADIO BEARER RECONFIGURATION COMPLETE message from the UE after the UE transfers its state from CELL_PCH or URA_PCH to CELL_DCH and the DRD is performed, this counter is measured in the cell that the UE camps on when sending the CELL UPDATE message. Figure 1-368 CELL UPDATE
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.P2D.DRD.Succ Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.1.83 Number of CPICH Power Adjustments Based on RTWP for Cell Counters
Counter ID 73423313 Counter Name VS.ULB.CPICH.AdjustNum Counter Description Number of CPICH Power Adjustments Based on RTWP for Cell
Description
This counter provides the number of power adjustments of the Common Pilot Channel (CPICH) triggered by the RTWP-based uplink intra-frequency load balancing algorithm. RTWP is short for Received Total Wideband Power (RTWP).
Measurement point
At point A as shown in the figure, When RTWP is higher than a certain threshold, the RNC needs to decrease CPICH power. When RTWP is lower than a certain threshold, the RNC needs to increase CPICH power. This counter provides the accumulated number of CPICH power adjustments in a measurement period in a cell. Figure 1-369 Cell reconfiguration procedure
Issue 01 (2013-05-04)
851
Formula
None
Unit
None
Related Features
Counter Name VS.ULB.CPICH.AdjustNum Feature ID WRFD-020104 Feature Name Intra Frequency Load Balance
1.12.1.84 Duration of PCPICH Power Under Minimum RTWP Threshold Counters

Counter ID 73441123 Counter Name VS.ULB.CPICHMin.Time Counter Description Duration of PCPICH Power Under Minimum RTWP Threshold
Description
This counter provides the duration of CPICH power being lower than Min Transmit Power of P-CPICH when the CPICH power is adjusted by the RTWP-based uplink intra-frequency load balancing algorithm.
Measurement point
The measurement starts when CPICH power is adjusted to be lower than Min Transmit Power of P-CPICH and stops when CPICH power is adjusted to be higher than Min Transmit Power of PCPICH. This counter is the accumulated value of such durations in the measurement period.
Formula
None
Unit
s
Related Features
Counter Name VS.ULB.CPICHMin.Time Feature ID WRFD-020104 Feature Name Intra Frequency Load Balance
1.12.1.85 Number of State Transfer Attempts from CELL_DCH to CELL_PCH or URA_PCH for Cell for HSDPA service Counters
Counter ID 73422160 Counter Name VS.HSDPA.H2P.Att Counter Description Number of State Transfer Attempts from CELL_DCH to CELL_PCH or URA_PCH for Cell for HSDPA service
Description
This counter provides the number of times a UE performing HSDPA services attempts to transit from the CELL_DCH state to the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the UE a RADIO BEARER RECONFIGURATION message, instructing the UE performing HSDPA services to transit from the CELL_DCH state to the CELL_PCH or URA_PCH state, this counter is measured at the serving cell where the UE camps on. For DC-HSDPA users, this counter is measured only in the cell with the primary carrier.
Issue 01 (2013-05-04)
853
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.H2P.Att Feature ID WRFD-01061111 Feature Name HSDPA State Transition
1.12.1.86 Number of Successful Times That a UE Performing HSDPA Services Transits to CELL_PCH or URA_PCH State for cell
Issue 01 (2013-05-04)
854
Counters
Counter ID 73422161 Counter Name VS.HSDPA.H2P.Succ Counter Description Number of Successful Times That a UE Performing HSDPA Services Transits to CELL_PCH or URA_PCH State for cell
Description
This counter provides the number of times a UE performing HSDPA services successfully transits from the CELL_DCH state to the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from the UE, indicating that the UE performing HSDPA services successfully transits from the CELL_DCH state to the CELL_PCH or URA_PCH state, this counter is measured at the serving cell where the UE camps on. For DC-HSDPA users, this counter is measured only in the cell with the primary carrier. Figure 1-371 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.H2P.Succ Feature ID WRFD-01061111 Feature Name HSDPA State Transition
1.12.1.87 Number of Attempts for a UE Performing HSUPA Services to Transit to CELL_PCH or URA_PCH State for Cell Counters
Counter ID 73422162 Counter Name VS.HSUPA.E2P.Att Counter Description Number of Attempts for a UE Performing HSUPA Services to Transit to CELL_PCH or URA_PCH State for Cell
Description
This counter provides the number of times a UE performing HSUPA services attempts to transit from the CELL_DCH state to the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the UE a RADIO BEARER RECONFIGURATION message, instructing the UE performing HSUPA services to transit from the CELL_DCH state to the CELL_PCH or URA_PCH state, this counter is measured at the serving cell where the UE camps on. For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Issue 01 (2013-05-04)
856
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.E2P.Att Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.1.88 Number of Successful Times That a UE Performing HSUPA Services Transits to CELL_PCH or URA_PCH State for cell
Issue 01 (2013-05-04)
857
Counters
Counter ID 73422163 Counter Name VS.HSUPA.E2P.Succ Counter Description Number of Successful Times That a UE Performing HSUPA Services Transits to CELL_PCH or URA_PCH State for cell
Description
This counter provides the number of times a UE performing HSUPA services successfully transits from the CELL_DCH state to the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from the UE, indicating that the UE performing HSUPA services successfully transits from the CELL_DCH state to the CELL_PCH or URA_PCH state, this counter is measured at the serving cell where the UE camps on. For DC-HSUPA users, this counter is measured only in the cell with the primary carrier. Figure 1-373 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.E2P.Succ Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.1.89 Number of Attempts for a UE Performing PS R99 Services to Transit to CELL_PCH or URA_PCH State for Cell Counters
Counter ID 73422164 Counter Name VS.PSR99.D2P.Att Counter Description Number of Attempts for a UE Performing PS R99 Services to Transit to CELL_PCH or URA_PCH State for Cell
Description
This counter provides the number of times a UE performing PS R99 services attempts to transit from the CELL_DCH state to the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending the RADIO BEARER RECONFIGURATION message to the UE, instructing the UE performing PS R99 services to transit from the CELL_DCH state to the CELL_PCH or URA_PCH state, this counter is measured at the serving cell that the UE camps on.
Issue 01 (2013-05-04)
859
Formula
None
Unit
None
Related Features
Counter Name VS.PSR99.D2P.Att Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.1.90 Number of Successful Times That a UE Performing PS R99 Services Transits to CELL_PCH or URA_PCH State for cell
Issue 01 (2013-05-04)
860
Counters
Counter ID 73422165 Counter Name VS.PSR99.D2P.Succ Counter Description Number of Successful Times That a UE Performing PS R99 Services Transits to CELL_PCH or URA_PCH State for cell
Description
This counter provides the number of times a UE performing PS R99 services successfully transits from the CELL_DCH state to the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives RADIO BEARER RECONFIGURATION COMPLETE message from the UE, indicating that the UE performing PS R99 services transits from CELL_DCH state to CELL_PCH or URA_PCH state successfully, this counter is measured at the serving cell that the UE camps on. Figure 1-375 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.PSR99.D2P.Succ Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.1.91 Number of Times That PS R99 Service Rate Is Found to Be Higher than HSUPA Service Rate Counters
Counter ID 73423357 Counter Name VS.HSUPAR99.Unfairness Counter Description Number of Times That PS R99 Service Rate Is Found to Be Higher than HSUPA Service Rate
Description
This counter provides the number of times that the PS R99 service rate is found to be higher than the HSUPA service rate in an HSUPA cell in the case that the cell fairness switch is set to ON.
Measurement point
This counter is increased by one each time the PS R99 service rate is found to be higher than the HSUPA service rate in the period of time specified by the fairness period timer length parameter.
Formula
None
Unit
None
Issue 01 (2013-05-04)
862
Related Features
Counter Name VS.HSUPAR99.Unfairness Feature ID WRFD-020131 Feature Name Optimization of R99 and HSUPA Users Fairness
1.12.1.92 Number of PS R99 BE Rate Reduction Requests Triggered by Unfairness Between PS R99 Service Rate and HSUPA Service Rate Counters
Counter ID 73423358 Counter Name VS.HSUPAR99.Unfairness. R99BERateDown Counter Description Number of PS R99 BE Rate Reduction Requests Triggered by Unfairness Between PS R99 Service Rate and HSUPA Service Rate
Description
This counter provides the number of times that PS R99 BE users are selected for rate reduction in the cell in the case that the PS R99 BE service rate is found to be higher than the HSUPA service rate.
Measurement point
The measurement is triggered at point A shown in figure 1. When the RNC determines that the PS R99 service rate is higher than the HSUPA service rate in an HSUPA cell, the RNC reduces the rate of certain R99 BE users. The measurement is triggered in the best HSUPA cell when the RNC sends a RADIO BERER RECONFIGURATION message to the UE.
Issue 01 (2013-05-04)
863
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPAR99.Unfairness. R99BERateDown Feature ID WRFD-020131 Feature Name Optimization of R99 and HSUPA Users Fairness
1.12.1.93 Duration of CPU Resource Insufficiency Reported by NodeB Counters

Counter ID 73411191 Counter Name VS.NodeB.CPU.Cong.Dur Counter Description Duration of CPU Resource Insufficiency Reported by NodeB for Cell
Issue 01 (2013-05-04)
864
Description
This counter provides the duration of CPU resource insufficiency reported by NodeB in a cell.
Measurement point
After receiving a message from the NodeB, indicating that CPU resources in a cell are insufficient, the RNC starts to measure the CPU insufficiency duration in the cell. When the RNC receives a message from the NodeB, indicating that CPU resources in the cell become sufficient, the RNC stops measuring the CPU insufficiency duration.
Formula
None
Unit
s
Related Features
Counter Name VS.NodeB.CPU.Cong.Dur Feature ID WRFD-040100 Feature Name Flow Control
1.12.1.94 Congestion Duration of DCCHs, DTCHs and CCCHs Carried over FACHs for Cell Counters
Counter ID 73439970 Counter Name VS.FACH.DCCH.CONG.TI ME VS.FACH.DTCH.CONG.TI ME VS.FACH.CCCH.CONG.TI ME Counter Description Congestion Duration of DCCHs Carried over FACHs for Cell Congestion Duration of DTCHs Carried over FACHs for Cell Congestion Duration of CCCHs Carried over FACHs for Cell
73439971
73424009
Description
These counters provide the congestion durations of the CCCH, DCCH, and DTCH carried on the FACH, respectively. A CCCH, DCCH, and DTCH carried on the FACH are considered as congested when the messages saved in the buffer of these channels cannot be sent out within
the specified time period. The congestion on the CCCH, DCCH, and DTCH is cleared when the messages saved in the buffer of these channels can be sent out.
Measurement point
The measurement is triggered as long as one CCCH/DCCH/DTCH is congested when the cell is configured with multiple FACHs and each FACH carries a CCCH/DCCH/DTCH.The counter is not measured only when all the CCCHs/DCCHs/DTCHs in the cell are not congested.
Formula
None
Unit
s
Related Features
Counter Name VS.FACH.DCCH.CONG.TI ME VS.FACH.DTCH.CONG.TI ME VS.FACH.CCCH.CONG.TI ME Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
WRFD-010202
WRFD-010202
1.12.2 Algorithm Measurement2 for Cell(ALGO2.Cell)

Overview
Radio Resource Management (RRC) algorithm is an important function of the WCDMA system. It is used to manage cell resources effectively and to increase resource utilization. This function subset(ALGO2.Cell) provides measurements related to the radio resource management algorithm.
Issue 01 (2013-05-04)
866
Counters
Counter ID 73441210 Counter Name VS.SirDist.OLPC. User Counter Description Number of UEs Using OLPC Enhancement Based on SIRerror Distribution for Cell Average Uplink Background Noise in a Cell Number of Automatic Uplink Background Noise Updates in a Cell Maximum Uplink Background Noise in a Cell Counters Related to the Failed Number of F2D Process Triggered by DCCH Congestion Counters Related to the Failed Number of D2F Process Triggered by DCCH Congestion Counters Related to the Failed Number of D2F Process Triggered by DSP Overload Number of times the RoT value is increased Number of times the RoT value is decreased Original Release V900R013
73441212
VS.BackGroundNo ise.Mean VS.BackGroundNo ise.Update
V900R014
73423948
V900R014
73441215
VS.BackGroundNo ise.Max VS.RAC.TrChSwit ch.Fail.DCCH.Con g.F2D
V900R014
73423955
V900R014
73423956
VS.RAC.TrChSwit ch.Fail.DCCH.Con g.D2F
V900R014
73423957
VS.RAC.TrChSwit ch.Fail.DSP.Overlo ad.D2F
V900R014
73423994
VS.HSUPA.TgtRoTInc VS.HSUPA.TgtRo TDec
V900R014
73423995
V900R014
Issue 01 (2013-05-04)
867
Counter ID 73424209
Counter Name VS.HSUPA.TTI2to 10.ADMCE.Succ
Counter Description Number of Successful TTI Switchovers Based on Admitted CEs During RB Reconfiguration in a Cell(2ms to 10ms) Number of Successful TTI Switchovers Based on Coverage During RB Reconfiguration in a Cell(2ms to 10ms) Number of Successful TTI Switchovers Based on RTWP During RB Reconfiguration in a Cell(2ms to 10ms) Number of Successful TTI Switchovers Based on Number of Occupied CEs During RB Reconfiguration in a Cell(2ms to 10ms) Number of Times HSUPA UEs Processing BE Services Succeed in Setting Up RABs over the DCH in Case of Weak Coverage Mean Number of PS Access Classes Restricted Due to Cell Resource Congestion (R6 or Later)
73424210
VS.HSUPA.TTI2to 10.COVER.Succ
V900R014
73424211
VS.HSUPA.TTI2to 10.ResRTWP.Succ
V900R014
73424212
VS.HSUPA.TTI2to 10.ResUsedCE.Suc c
V900R014
73424214
VS.RABEstabE2D. COVER.Succ
V900R014
73441241
VS.AC.CongCtl.M eanAcBarNum.Abo veR6.PS
V900R014
Issue 01 (2013-05-04)
868
Counter ID 73441243
Counter Name VS.AC.CongCtl.M eanAcBarNum.UnderR5
Counter Description Mean Number of Access Classes Restricted Due to Cell Resource Congestion (R5 or Earlier) Mean Number of CS Access Classes Restricted Due to Cell Resource Congestion (R6 or Later) Duration of Access Class Restriction Triggered by Cell Resource Congestion Number of CS UEs Involved in InterFrequency Loadbased Handovers in a CS CLB Cell Number of PS UEs Involved in InterFrequency Loadbased Handovers in a PS CLB Cell Number of Successful TTI Switchovers Based on Iub Resources During RB Reconfiguration in a Cell(2ms to 10ms) Number of Attempts to Configure a Long CQI Feedback Period for a Cell Number of Attempts to Configure a Short CQI Feedback Period for a Cell
73441244
VS.AC.CongCtl.M eanAcBarNum.Abo veR6.CS
V900R014
73441245
VS.AC.CongCtl.Ti me
V900R014
73441246
VS.LCC.CLB.CS.I nterFreq
V900R014
73441247
VS.LCC.CLB.PS.I nterFreq
V900R014
73424471
VS.HSUPA.TTI2to 10.ResIUB.Succ
V900R014
73424472
VS.HSDPA.DynCf gAtt.LongCQI
V900R014
73424473
VS.HSDPA.DynCf gAtt.ShortCQI
V900R014
Issue 01 (2013-05-04)
869
Counter ID 73424474
Counter Name VS.ULBler.BE.Lar ge VS.ULBler.BE.Sm all VS.RAB.SpecialUs er.AbnormRel.CS
Counter Description Number of Attempts to Configure BLER in a Congested Cell Number of Attempts to Configure BLER in a Normal Cell Number of CS RABs Abnormally Released for Special UEs for Cell Number of CS RABs Normally Released for Special UEs for Cell Mean Uplink Actual Cell Load Max Uplink Actual Cell Load Min Uplink Actual Cell Load Number of CELL_FACH to URA_PCH State Transition Attempts for Cell Number of Successful CELL_FACH to URA_PCH State Transitions for Cell Number of CELL_DCH to URA_PCH State Transition Attempts for Cell Number of Successful CELL_DCH to URA_PCH State Transitions for Cell
73424475
V900R014
73424760
V900R014
73424761
VS.RAB.SpecialUs er.NormRel.CS
V900R014
73441505 73424787 73424788 73424896
VS.MeanULActual PowerLoad VS.MaxULActualPowerLoad VS.MinULActualPowerLoad VS.DCCC.Att.F2U
V900R014 V900R014 V900R014 V900R014
73424897
VS.DCCC.Succ.F2 U
V900R014
73424898
VS.DCCC.Att.D2U
V900R014
73424899
VS.DCCC.Succ.D2 U
V900R014
Issue 01 (2013-05-04)
870
Counter ID 73425824
Counter Name VS.DL.DPCH.Opti PilotPOAttNum
Counter Description Number of Pilot PO Optimization Attempts in the DL DPCH for Cell Number of Normal Pilot PO Attempts in the DL DPCH for Cell Total number of times a micro cell transits to the total desensitization state Total time periods of the total desensitization state for a micro cell Average desensitization intensity for a micro cell Average Uplink Credit Usage of LCG for Cell Maximum Uplink Credit Usage of LCG for Cell Number of State Transition Attempts from CELL_PCH or URA_PCH to CELL_FACH and then to CELL_DCH Due to Data Transmission Requirements for Cell
73425825
VS.DL.DPCH.NormalPilotPOAttNu m VS.TotalDesense.N um
V900R015
73426173
V900R015
73426176
VS.TotalDesense.Ti me
V900R015
73426179
VS.MeanDesensePwr
V900R015
73426283
VS.LCG.ULCredit Usage.Mean VS.LCG.ULCredit Usage.Max VS.DCCC.Att.F2D. AfterP2F
V900R015
73426284
V900R015
73426333
V900R015
Issue 01 (2013-05-04)
871
Counter ID 73426334
Counter Name VS.DCCC.Succ.F2 D.AfterP2F
Counter Description Number of Successful State Transitions from CELL_PCH or URA_PCH to CELL_FACH and then to CELL_DCH Due to Data Transmission Requirements for Cell
None
1.12.2.1 Average Number of UEs Using OLPC Enhancement Based on SIRerror Distribution Counters
Counter ID 73441210 Counter Name VS.SirDist.OLPC.User Counter Description Number of UEs Using OLPC Enhancement Based on SIRerror Distribution for Cell
Description
This counter provides the average number of UEs using the algorithm OLPC Enhancement Based on SIRerror Distribution in a cell that is their best cell.
Measurement point
The RNC takes samples of UEs using the algorithm OLPC Enhancement Based on SIRerror Distribution in a cell that is their best cell. The samples are taken every five seconds. At the end of a measurement period, the RNC accumulates the values obtained at each sampling point and divides the accumulated value by the number of samples for the average value. A UE is considered to be using this algorithm if the DEDICATED MEASUREMENT INITIATION procedure related to this algorithm is successfully started in all cells in the active set for the UE.
Formula
None
Unit
None
Related Features
Counter Name VS.SirDist.OLPC.User Feature ID WRFD-020503 Feature Name Outer Loop Power Control
1.12.2.2 Average and Maximum Uplink Background Noise Counters

Counter ID 73441212 73441215 Counter Name VS.BackGroundNoise.Mean VS.BackGroundNoise.Max Counter Description Average Uplink Background Noise in a Cell Maximum Uplink Background Noise in a Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73423946 73423947 Counter Name VS.BackGroundNoise.CUM VS.BackGroundNoise.SAM PLE Counter Description Accumulated Totally Background Noise for Cell Number of the Background Noise for Cell
Description
These counters provide the average and maximum uplink background noise, respectively, in a cell.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of the cell background noise after the RNC updates. At the end of a measurement period, the average uplink background noise is obtained by dividing the accumulated value by the sample number. The maximum uplink background noise is also obtained at the end of the measurement period.
Issue 01 (2013-05-04)
873
Formula
VS.BackGroundNoise.Mean = ([VS.BackGroundNoise.CUM]/ [VS.BackGroundNoise.SAMPLE]-{1121})/{10}
Unit
dBm
Related Features
Counter Name VS.BackGroundNoise.Mean VS.BackGroundNoise.Max Feature ID WRFD-020102 WRFD-020102 Feature Name Load Measurement Load Measurement
1.12.2.3 Number of Automatic Uplink Background Noise Updates Counters

Counter ID 73423948 Counter Name VS.BackGroundNoise.Update Counter Description Number of Automatic Uplink Background Noise Updates in a Cell
Description
This counter provides the number of automatic uplink background noise updates in a cell.
Measurement point
The measurement is triggered when the RNC makes a decision on a cell background noise update during the period when the algorithm for automatic uplink background noise updates takes effect.
Formula
None
Unit
None
Issue 01 (2013-05-04)
874
Related Features
Counter Name VS.BackGroundNoise.Update Feature ID WRFD-020102 Feature Name Load Measurement
1.12.2.4 Counters Related to the Number of Failed in Channal Transfering Process Counters
Counter ID 73423955 Counter Name VS.RAC.TrChSwitch.Fail.D CCH.Cong.F2D Counter Description Counters Related to the Failed Number of F2D Process Triggered by DCCH Congestion Counters Related to the Failed Number of D2F Process Triggered by DCCH Congestion Counters Related to the Failed Number of D2F Process Triggered by DSP Overload
73423956
VS.RAC.TrChSwitch.Fail.D CCH.Cong.D2F
73423957
VS.RAC.TrChSwitch.Fail.D SP.Overload.D2F
Description
These counters measure the number of failed resource applications during a channel conversion.
Measurement point
UEs must apply for resources before state transitions. When a UE fails to apply for resources due to resource congestion, these counters are measured in the cell that the UE fails to access based on the causes of resource congestion.
Formula
None
Unit
None
Issue 01 (2013-05-04)
875
Related Features
Counter Name VS.RAC.TrChSwitch.Fail.D CCH.Cong.F2D VS.RAC.TrChSwitch.Fail.D CCH.Cong.D2F VS.RAC.TrChSwitch.Fail.D SP.Overload.D2F Feature ID WRFD-020101 WRFD-020101 WRFD-020101 Feature Name Admission Control Admission Control Admission Control
1.12.2.5 Number of RoT adjustments in an HSUPA cell Counters

Counter ID 73423994 73423995 Counter Name VS.HSUPA.TgtRoTInc VS.HSUPA.TgtRoTDec Counter Description Number of times the RoT value is increased Number of times the RoT value is decreased
Description
This counter provides the number of Rise over Thermal (RoT) adjustments in an HSUPA cell.
Measurement point
The RNC decides whether to adjust the RoT value based on the UL Timeslot ISCP value reported by the NodeB and transmit power of R99 users in an HSUPA cell. Once the RNC decides to adjust the RoT value, this counter is increased by one.
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.TgtRoTInc Feature ID WRFD-140211 Feature Name Dynamic Target ROT Adjustment
876
Issue 01 (2013-05-04)
Counter Name VS.HSUPA.TgtRoTDec
Feature Name Dynamic Target ROT Adjustment
1.12.2.6 Number of Successful TTI Switchovers with Various Causes During RB Reconfiguration in a Cell(2ms to 10ms) Counters
Counter ID 73424209 Counter Name VS.HSUPA.TTI2to10.ADM CE.Succ Counter Description Number of Successful TTI Switchovers Based on Admitted CEs During RB Reconfiguration in a Cell (2ms to 10ms) Number of Successful TTI Switchovers Based on Coverage During RB Reconfiguration in a Cell (2ms to 10ms) Number of Successful TTI Switchovers Based on RTWP During RB Reconfiguration in a Cell (2ms to 10ms) Number of Successful TTI Switchovers Based on Number of Occupied CEs During RB Reconfiguration in a Cell(2ms to 10ms) Number of Successful TTI Switchovers Based on Iub Resources During RB Reconfiguration in a Cell (2ms to 10ms)
73424210
VS.HSUPA.TTI2to10.COV ER.Succ
73424211
VS.HSUPA.TTI2to10.ResR TWP.Succ
73424212
VS.HSUPA.TTI2to10.ResU sedCE.Succ
73424471
VS.HSUPA.TTI2to10.ResI UB.Succ
Description
These counters provide the number of successful TTI switchovers from 2 ms to 10 ms during RB reconfiguration in a cell. For DC-HSUPA UEs, these counters are measured only in the primary cell. TTI is short for transmission time interval.
Issue 01 (2013-05-04)
877
Measurement point
The measurement is triggered at point B shown in the following figure. When the UE sends the RNC a RADIO BEARER RECONFIGURATION COMPLETE message, a specific counter is increased by one if the UE performs a successful TTI switchover from 2 ms to 10 ms in its HSUPA serving cell. This counter is determined based on the specific TTI switchover cause. At the end of the measurement period, the RNC calculates the accumulated times of successful TTI handovers caused by different reasons. Figure 1-377 RB reconfig procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.TTI2to10.ADM CE.Succ Feature ID WRFD-01061404 Feature Name HSUPA 2ms/10ms TTI Handover
Issue 01 (2013-05-04)
878
Counter Name VS.HSUPA.TTI2to10.COV ER.Succ
Feature Name TTI Switch for BE Services Based on Coverage HSUPA 2ms/10ms TTI Handover
VS.HSUPA.TTI2to10.ResR TWP.Succ VS.HSUPA.TTI2to10.ResU sedCE.Succ VS.HSUPA.TTI2to10.ResI UB.Succ
WRFD-01061404 WRFD-01061404 WRFD-01061404
HSUPA 2ms/10ms TTI Handover HSUPA 2ms/10ms TTI Handover HSUPA 2ms/10ms TTI Handover
1.12.2.7 Number of Times HSUPA UEs Processing BE Services Succeed in Setting Up RABs over the DCH in Case of Weak Coverage Counters
Counter ID 73424214 Counter Name VS.RABEstabE2D.COVER. Succ Counter Description Number of Times HSUPA UEs Processing BE Services Succeed in Setting Up RABs over the DCH in Case of Weak Coverage
Description
This counter provides the number of times HSUPA UEs processing BE services succeed in setting up RABs over the DCH in case of weak coverage.
Measurement point
At measure point B shown in the following figure, the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE and sends an RAB ASSIGNMENT RESPONSE message to the CN. The UEs eventually succeed in setting up the RABs over the DCH due to a small Ec/ N0 even through conditions for setting up the RABs over the E-DCH has been met. In such a case, this counter in the serving cell is increased by one.
Issue 01 (2013-05-04)
879
Formula
None
Unit
None
Related Features
Counter Name VS.RABEstabE2D.COVER. Succ Feature ID WRFD-01061208 Feature Name HSUPA DCCC
1.12.2.8 Mean Number of Access Classes Restricted Due to Cell Resource Congestion
Issue 01 (2013-05-04)
880
Counters
Counter ID 73441241 Counter Name VS.AC.CongCtl.MeanAcBa rNum.AboveR6.PS Counter Description Mean Number of PS Access Classes Restricted Due to Cell Resource Congestion (R6 or Later) Mean Number of Access Classes Restricted Due to Cell Resource Congestion (R5 or Earlier) Mean Number of CS Access Classes Restricted Due to Cell Resource Congestion (R6 or Later)
73441243
VS.AC.CongCtl.MeanAcBa rNum.UnderR5
73441244
VS.AC.CongCtl.MeanAcBa rNum.AboveR6.CS
Description
These counters provide the mean number of PS access classes restricted due to cell resource congestion for UEs of Release 6 or later, mean number of access classes restricted due to cell resource congestion for UEs of Release 5 or earlier, and mean number of CS access classes restricted due to cell resource congestion for UEs of Release 6 or later, respectively. Note: AC restrictions for UEs of Release 6 or later can be performed for the PS or CS domain, respectively. AC restrictions for UEs of Release 5 or earlier cannot be performed for the PS or CS domain, respectively.
Measurement point
The RNC takes samples every time it attempts to restrict access classes due to congested cell resources. At the end of each measurement period, the RNC sums sample results and divides the sum by the number of samples. The division result is the mean number of restricted access classes within a specific measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.AC.CongCtl.MeanAcBa rNum.AboveR6.PS
Issue 01 (2013-05-04)
Feature Name Intelligent Access Class Control

881
Counter Name VS.AC.CongCtl.MeanAcBa rNum.UnderR5 VS.AC.CongCtl.MeanAcBa rNum.AboveR6.CS
Feature Name Intelligent Access Class Control Intelligent Access Class Control
1.12.2.9 Duration of Access Class Restriction Triggered by Cell Resource Congestion Counters
Counter ID 73441245 Counter Name VS.AC.CongCtl.Time Counter Description Duration of Access Class Restriction Triggered by Cell Resource Congestion
Description
This counter provides the duration of access class restriction triggered by cell resource congestion.
Measurement point
When cell resources become congested, the RNC calculates the duration of access class restriction for the cell. Access class restriction: At least one of the AC number restricted for PS UEs of Release 6 or later, CS UEs of Release 5 or earlier and Release 6 or later is not zero. This counter is calculated by the accumulated duration of access class restriction in the measurement period.
Formula
None
Unit
s
Related Features
Counter Name VS.AC.CongCtl.Time Feature ID WRFD-140213 Feature Name Intelligent Access Class Control
Issue 01 (2013-05-04)
882
1.12.2.10 Number of UEs Involved in Inter-Frequency Load-based Handovers in a CLB Cell Counters
Counter ID 73441246 Counter Name VS.LCC.CLB.CS.InterFreq Counter Description Number of CS UEs Involved in Inter-Frequency Loadbased Handovers in a CS CLB Cell Number of PS UEs Involved in Inter-Frequency Loadbased Handovers in a PS CLB Cell
73441247
VS.LCC.CLB.PS.InterFreq
Description
These counters provide the number of UEs involved in inter-frequency load-based handovers in a CLB cell.
Measurement point
In a CS CLB cell, the RNC instructs some UEs processing CS or CS/PS combined services to perform inter-frequency load-based handovers. In such a case, the counter VS.LCC.CLB.CS.InterFreq is increased by one. In a PS CLB cell, the RNC instructs some UEs processing PS services to perform inter-frequency load-based handovers. In such a case, the counter VS.LCC.CLB.PS.InterFreq is increased by one.
Formula
None
Unit
None
Related Features
Counter Name VS.LCC.CLB.CS.InterFreq Feature ID WRFD-140217 Feature Name Inter-Frequency Load Balancing Based on Configurable Load Threshold
Issue 01 (2013-05-04)
883
Counter Name VS.LCC.CLB.PS.InterFreq
Feature Name Inter-Frequency Load Balancing Based on Configurable Load Threshold
1.12.2.11 Number of Attempts to Configure CQI Feedback Period for a Cell Counters
Counter ID 73424472 Counter Name VS.HSDPA.DynCfgAtt.Lon gCQI VS.HSDPA.DynCfgAtt.Sho rtCQI Counter Description Number of Attempts to Configure a Long CQI Feedback Period for a Cell Number of Attempts to Configure a Short CQI Feedback Period for a Cell
73424473
Description
These counters provide the number of attempts to configure a short or long CQI feedback period for an HSDPA serving cell. The RNC prolongs the CQI feedback period if the uplink cell load is heavy, UEs move to areas with poor signal quality, or UEs process CS and PS combined services. A short CQI feedback period is the period configured by the RNC before Dynamic Configuration of HSDPA CQI Feedback Period is introduced.
Measurement point
During each measurement period, the RNC takes samples during the procedures involved when settings of physical-layer parameters are changed, including RB reconfiguration, RB setup, cell update, DRD, soft handover, and hard handover.
Formula
None
Unit
None
Issue 01 (2013-05-04)
884
Related Features
Counter Name VS.HSDPA.DynCfgAtt.Lon gCQI VS.HSDPA.DynCfgAtt.Sho rtCQI Feature ID WRFD-140215 Feature Name Dynamic Configuration of HSDPA CQI Feedback Period Dynamic Configuration of HSDPA CQI Feedback Period
WRFD-140215
1.12.2.12 Number of Attempts to Configure BLER in a Congested or Normal Cell Counters

Counter ID 73424474 Counter Name VS.ULBler.BE.Large Counter Description Number of Attempts to Configure BLER in a Congested Cell Number of Attempts to Configure BLER in a Normal Cell
73424475
VS.ULBler.BE.Small
Description
These counters provide the number of attempts to configure BLER in the best cell, which may be under congestion. In addition, in this cell, uplink data is carried over the DCH and all the services on the DCH are BE services.
Measurement point
Within a measurement period, this counter is increased when any process is completed, uplink data is carried over the DCH, and all the services on the DCH are BE services. This process can be designated for RAB establishment, RAB modification, DRD, soft handover, and hard handover.
Formula
None
Unit
None
Issue 01 (2013-05-04)
885
Related Features
Counter Name VS.ULBler.BE.Large VS.ULBler.BE.Small Feature ID WRFD-140216 WRFD-140216 Feature Name Load-based Uplink Target BLER Configuration Load-based Uplink Target BLER Configuration
1.12.2.13 Number of CS RABs Abnormally Released for Special UEs for Cell Counters
Counter ID 73424760 Counter Name VS.RAB.SpecialUser.Abnor mRel.CS Counter Description Number of CS RABs Abnormally Released for Special UEs for Cell
Description
This counter measures the number of CS radio access bearers (RABs) abnormally released for special UEs in the best cell. Special UEs are UEs that are configured with weak reception.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message with the cause other than "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization"(reference to 3GPP TS 25.413), this counter is incremented by one in the best cell that the UE camps on if the released RABs belong to CS domain.
Issue 01 (2013-05-04)
886
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message with the cause other than "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization"(reference to 3GPP TS 25.413), this counter is incremented by one in the best cell that the UE camps on if the released RABs belong to CS domain.
Issue 01 (2013-05-04)
887
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message with the cause other than "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization"(reference to 3GPP TS 25.413), this counter is incremented by one in the best cell that the UE camps on if the released RABs belong to CS domain.
Issue 01 (2013-05-04)
888
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SpecialUser.Abnor mRel.CS Feature ID WRFD-140205 Feature Name Voice Service Experience Improvement for Weak Reception UEs
1.12.2.14 Number of CS RABs Normally Released for Special UEs for Cell Counters
Counter ID 73424761 Counter Name VS.RAB.SpecialUser.Norm Rel.CS Counter Description Number of CS RABs Normally Released for Special UEs for Cell
889
Issue 01 (2013-05-04)
Description
This counter measures the number of CS RABs normally released for special UEs in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicates the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",this counter is incremented by one in the best cell which the UE camps on if the released RAB belongs to CS domain. Figure 1-382 Iu connection release procedure
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicates the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",this counter is incremented by one in the best cell which the UE camps on if the released RAB belongs to CS domain.
Issue 01 (2013-05-04)
890
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SpecialUser.Norm Rel.CS Feature ID WRFD-140205 Feature Name Voice Service Experience Improvement for Weak Reception UEs
1.12.2.15 Uplink Actual Cell Load
Issue 01 (2013-05-04)
891
Counters
Counter ID 73441505 73424787 73424788 Counter Name VS.MeanULActualPowerLoad VS.MaxULActualPowerLoad VS.MinULActualPowerLoad Counter Description Mean Uplink Actual Cell Load Max Uplink Actual Cell Load Min Uplink Actual Cell Load
Description
These counters measure the average, maximum, and minimum uplink actual cell load in a cell. These counters indicate the percentage of the uplink actual cell load in the received total wideband power (RTWP).
Measurement point
The measurement is triggered at point A shown in figure 1 when the RNC receives a COMMON MEASUREMENT REPORT message containing the RTWP for a cell. In this case, this counter is calculated based on the measurement results contained in the message and the measurement period is 5s. At the end of the measurement period, the RNC measures the maximum and minimum uplink actual cell load and divides the accumulated value by the number of samples to obtain the average uplink actual cell load. Figure 1-384 Common measurement report procedure
Issue 01 (2013-05-04)
892
Formula
None
Unit
%
Related Features
Counter Name VS.MeanULActualPowerLoad VS.MaxULActualPowerLoad VS.MinULActualPowerLoad Feature ID WRFD-020102 WRFD-020102 WRFD-020102 Feature Name Load Measurement Load Measurement Load Measurement
1.12.2.16 Number of CELL_FACH to URA_PCH State Transition Attempts Counters

Counter ID 73424896 Counter Name VS.DCCC.Att.F2U Counter Description Number of CELL_FACH to URA_PCH State Transition Attempts for Cell
Description
This counter provides the number of state transition attempts from CELL_FACH to URA_PCH in the cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending a RADIO BEARER RECONFIGURATION message, instructing the UE to transit from the CELL_FACH state to the URA_PCH state, the RNC measures the counter in the best cell where the UE camps on before the state transition.
Issue 01 (2013-05-04)
893
Figure 1-385 RB Reconfiguration Procedure
The measurement is triggered at point A as shown in the following figure. When sending a PHYSICAL CHANNEL RECONFIGURATION message, instructing the UE to transit from the CELL_FACH state to the URA_PCH state, the RNC measures the counter in the best cell where the UE camps on before the state transition. Figure 1-386
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.Att.F2U Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.2.17 Number of Successful CELL_FACH to URA_PCH State Transitions Counters

Counter ID 73424897 Counter Name VS.DCCC.Succ.F2U Counter Description Number of Successful CELL_FACH to URA_PCH State Transitions for Cell
Description
This counter provides the number of successful state transitions from CELL_FACH to URA_PCH in the cell.
Measurement point
The measurement is triggered at point B as shown in the following figure. When receiving a RADIO BEARER RECONFIGURATION COMPLETE message, indicating that the UE has transited from the CELL_FACH state to the URA_PCH state, the RNC measures the counter in the best cell where the UE camps on before the state transition.
Issue 01 (2013-05-04)
895
The measurement is triggered at point B as shown in the following figure. When receiving a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message, indicating that the UE has transited from the CELL_FACH state to the URA_PCH state, the RNC measures the counter in the best cell where the UE camps on before the state transition. Figure 1-388
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.Succ.F2U Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.2.18 Number of CELL_DCH to URA_PCH State Transition Attempts Counters

Counter ID 73424898 Counter Name VS.DCCC.Att.D2U Counter Description Number of CELL_DCH to URA_PCH State Transition Attempts for Cell
Description
This counter provides the number of state transition attempts from CELL_DCH to URA_PCH in the cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending the RADIO BEARER RECONFIGURATION message to the UE, instructing the UE to transit from the CELL_DCH state to the URA_PCH state, the RNC measures the counter in the best cell where the UE camps on before the state transition.
Issue 01 (2013-05-04)
897
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.Att.D2U Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.2.19 Number of Successful CELL_DCH to URA_PCH State Transitions Counters

Counter ID 73424899 Counter Name VS.DCCC.Succ.D2U Counter Description Number of Successful CELL_DCH to URA_PCH State Transitions for Cell
898
Issue 01 (2013-05-04)
Description
This counter provides the number of successful state transitions from CELL_DCH to URA_PCH in the cell.
Measurement point
The measurement is triggered at point B as shown in the following figure. When receiving a RADIO BEARER RECONFIGURATION COMPLETE message, indicating that the UE has transited from the CELL_DCH state to the URA_PCH state, the RNC measures the counter in the best cell where the UE camps on before the state transition. Figure 1-390 RB Reconfiguration Procedure
Formula
None
Unit
None
Issue 01 (2013-05-04)
899
Related Features
Counter Name VS.DCCC.Succ.D2U Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.2.20 Number of Pilot PO Optimization Attempts in the DL DPCH for Cell Counters
Counter ID 73425824 Counter Name VS.DL.DPCH.OptiPilotPOAttNum Counter Description Number of Pilot PO Optimization Attempts in the DL DPCH for Cell
Description
This counter measures the number of the attempts to optimize the pilot PO in the best cell in a measurement period.
Measurement point
This counter measures the number of the attempts to optimize the pilot PO in the downlink DPCH in the best cell in a measurement period. The optimization attempt occurs during physical parameter change procedures at the physical layer, including radio bearer (RB) setups, RB reconfigurations, cell updates, and hard handovers.
Formula
None
Unit
None
Related Features
Counter Name VS.DL.DPCH.OptiPilotPOAttNum Feature ID WRFD-150230 Feature Name DPCH Pilot Power Adjustment
1.12.2.21 Number of Normal Pilot PO Attempts in the DL DPCH for Cell

Counters
Counter ID 73425825 Counter Name VS.DL.DPCH.NormalPilotPOAttNum Counter Description Number of Normal Pilot PO Attempts in the DL DPCH for Cell
Description
This counter measures the number of the attempts to configure a normal pilot PO in the best cell in a measurement period.
Measurement point
This counter measures the number of attempts to configure a normal pilot PO in the best cell in the measurement period. The optimization attempt occurs during RRC connection setup, hard handover H2D fallback, hard handover with relocation, inter-RAT incoming handover, P2D state transition, DCCC F2D state transition, F2D state transition due to service establishment, DRD procedure for HSPA retry, or RAB establishment for DRD to other cells.
Formula
None
Unit
None
Related Features
Counter Name VS.DL.DPCH.NormalPilotPOAttNum Feature ID WRFD-150230 Feature Name DPCH Pilot Power Adjustment
1.12.2.22 Total number of times a micro cell transits to the total desensitization state Counters
Counter ID 73426173 Counter Name VS.TotalDesense.Num Counter Description Total number of times a micro cell transits to the total desensitization state
Issue 01 (2013-05-04)
901
Description
This counter indicates the total number of times a micro cell transits to the total desensitization state.
Measurement point
This counter increases by increments of 1 each time the micro cell transits from partial desensitization to total desensitization.
Formula
None
Unit
None
Related Features
Counter Name VS.TotalDesense.Num Feature ID WRFD-150201 WRFD-15020103 Feature Name Macro & Micro Co-carrier Uplink Interference Control Micro Cell Dynamic Rx Sensitivity Control
1.12.2.23 Total time periods of the total desensitization state for a micro cell Counters
Counter ID 73426176 Counter Name VS.TotalDesense.Time Counter Description Total time periods of the total desensitization state for a micro cell
Description
This counter indicates the total time periods of the total desensitization state for a micro cell.
Measurement point
This counter starts to measure the time period of the total desensitization state when the micro cell transits from partial desensitization to total desensitization and stops the measurement when the micro cell transits from total desensitization to partial desensitization. This counter is equal to the sum of the time periods of the total desensitization state.
Formula
None
Unit
s
Related Features
Counter Name VS.TotalDesense.Time Feature ID WRFD-150201 WRFD-15020103 Feature Name Macro & Micro Co-carrier Uplink Interference Control Micro Cell Dynamic Rx Sensitivity Control
1.12.2.24 Average desensitization intensity for a micro cell Counters

Counter ID 73426179 Counter Name VS.MeanDesensePwr Counter Description Average desensitization intensity for a micro cell
Description
This counter indicates the average desensitization intensity for a micro cell. (Note: This counter measures the intensity of desensitization on the NodeB, which is configured on the RNC. It does not measure the intensity of static desensitization on the NodeB.)
Measurement point
When sending the physical sharing channel reconfiguration message to the NodeB, the RNC reports the latest desensitization intensity to the platform if the desensitization intensity is changed. In addition, the RNC reports the current desensitization intensity to the platform every minute. The average desensitization intensity is equal to the sum of reported desensitization intensity values divided by the number of reports in a measurement period.
Formula
None
Unit
dBm
Related Features
Counter Name VS.MeanDesensePwr Feature ID WRFD-150201 WRFD-15020103 Feature Name Macro & Micro Co-carrier Uplink Interference Control Micro Cell Dynamic Rx Sensitivity Control
1.12.2.25 Average and Maximum Uplink Credit Usage of LCG for Cell Counters
Counter ID 73426283 73426284 Counter Name VS.LCG.ULCreditUsage.M ean VS.LCG.ULCreditUsage.M ax Counter Description Average Uplink Credit Usage of LCG for Cell Maximum Uplink Credit Usage of LCG for Cell
Description
These counters provide the average and maximum uplink credit usage of the local cell group (LCG) where the cell belongs. Note: The CE-related counters measured at the RNC have different values from these measured at the NodeB. CE-related counters measured at the RNC are mainly used to estimate the access capability and are measured based on the number of CEs consumed in the access strategy. CE-related counters measured at the NodeB are mainly used to calculate the CEs that are actually used. In addition, the sampling period of the CE-related counters measured at the RNC is 5s, which is different from that of the CE-related counters measured at the NodeB (2 ms). Therefore, the counter values are not comparable, extremely when the NodeB dynamic CE function is enabled.
Measurement point
The system samples the uplink credit usage of the logical cell group (LCG) every 5s. At the end of the measurement period, the maximum uplink credit usage of the LCG for the cell is obtained. The average uplink credit usage of the LCG for the cell equals to accumulated value of the credit usage at the sampling points divided by the number of sampling times.Counters related to CE resource measurement by the RNC are different from those related to CE resource measurement by the NodeB in that:? The counters related to CE resource measurement by the RNC estimate the access capabilities based on the CE resources consumed by the admission policy, while the counters related to CE resource measurement by the NodeB estimate the actual CE usage and indicate the CE resources available for connected UEs. When the dynamic CE function is enabled on the NodeB, the values of the counters related to CE resource measurement by the RNC are quite different from the counters related to CE resource measurement by the NodeB.The RNC measures the related counters every 5 s, while the NodeB measures the related counters every 2 ms TTI.
Formula
None
Unit
per mill
Related Features
Counter Name VS.LCG.ULCreditUsage.M ean VS.LCG.ULCreditUsage.M ax Feature ID WRFD-140212 WRFD-140212 Feature Name CE Overbooking CE Overbooking
1.12.2.26 Number of State Transition Attempts from CELL_PCH or URA_PCH to CELL_FACH and then to CELL_DCH Due to Data Transmission Requirements for Cell Counters
Counter ID 73426333 Counter Name VS.DCCC.Att.F2D.AfterP2 F Counter Description Number of State Transition Attempts from CELL_PCH or URA_PCH to CELL_FACH and then to CELL_DCH Due to Data Transmission Requirements for Cell
Description
This counter measures the number of state transition attempts from CELL_PCH or URA_PCH or CELL_FACH and then to CELL_DCH due to data transmission requirements in a cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives a CELL UPDATE message with cause value "uplink data transmission" or "paging response" from a UE in the CELL_PCH or URA_PCH state and the cell update procedure is successful. The RNC then instructs the UE to transition from the CELL_FACH state to the CELL_DCH state. When the RNC sends a RADIO BEARER RECONFIGURATION message to the UE, this counter is measured in the cell that the UE camps on.
Figure 1-391 RB Reconfiguration procedure after cell update procedure
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.Att.F2D.AfterP2 F Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.2.27 Number of Successful State Transitions from CELL_PCH or URA_PCH to CELL_FACH and then to CELL_DCH Due to Data Transmission Requirements for Cell
Issue 01 (2013-05-04)
906
Counters
Counter ID 73426334 Counter Name VS.DCCC.Succ.F2D.AfterP 2F Counter Description Number of Successful State Transitions from CELL_PCH or URA_PCH to CELL_FACH and then to CELL_DCH Due to Data Transmission Requirements for Cell
Description
This counter measures the number of successful state transitions from CELL_PCH or URA_PCH or CELL_FACH and then to CELL_DCH due to data transmission requirements in a cell.
Measurement point
The measurement is triggered at point B, as shown in the figure. The RNC receives a CELL UPDATE message with cause value "uplink data transmission" or "paging response" from a UE in the CELL_PCH or URA_PCH state and the cell update procedure is successful. The RNC then instructs the UE to transition from the CELL_FACH state to the CELL_DCH state. When the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from the UE, this counter is measured in the cell that the UE camps on. Figure 1-392 RB Reconfiguration procedure after cell update procedure
Issue 01 (2013-05-04)
907
Formula
None
Unit
None
Related Features
Counter Name VS.DCCC.Succ.F2D.AfterP 2F Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.3 Measurement related to BLER per cell(BLER.Cell)

Overview
Cell UL BLER Measurement is used to measure the BLER of the uplink data transmission of all UEs in a cell according to different service classes and traffic rates.
Counters
Counter ID 67199797 67184402 Counter Name VS.ULBler.AMR VS.ULBler.AMR.E rrTB Counter Description UL BLER of AMR Services for Cell Number of TBs with UL CRCI Error for AMR Services for Cell Number of BLER Samplings for AMR Services for Cell UL BLER of CS 64 Kbit/s Conversational Services on DCH for Cell Number of TBs with UL CRCI Error for CS 64 Kbit/s Conversational Services for Cell Original Release Earlier than V900R011 Earlier than V900R011
67184403
VS.ULBler.AMR.S ample VS.ULBler.CS64
73394082
73394083
VS.ULBler.CS64.E rrTB
V900R012
Issue 01 (2013-05-04)
908
Counter ID 73394084
Counter Name VS.ULBler.CS64.S ample
Counter Description Number of BLER Samplings for CS 64 Kbit/s Conversational Services for Cell UL BLER of PS 8 Kbit/s BE Services on DCH for Cell Number of TBs with UL CRCI Error for PS 8 Kbit/s BE Services for Cell Sampling Times of BLER for PS 8 Kbit/ s BE Services for Cell UL BLER of PS 16 Kbit/s BE Services on DCH for Cell Number of TBs with UL CRCI Error for PS 16 Kbit/s BE Services for Cell Sampling Times of BLER for PS 16 Kbit/s BE Services for Cell UL BLER of PS 32 Kbit/s BE Services on DCH for Cell Number of TBs with UL CRCI Error for PS 32 Kbit/s BE Services for Cell Sampling Times of BLER for PS 32 Kbit/s BE Services for Cell UL BLER of PS 64 Kbit/s BE Services on DCH for Cell
67199806
VS.ULBler.PS.BE. DCH.8 VS.ULBler.PS.BE. DCH.8.ErrTB
67184420
67184421
VS.ULBler.PS.BE. DCH.8.Sample
67199807
67184422
67184423
67199808
67184424
67184425
67199809
VS.ULBler.PS.BE. DCH.64
Issue 01 (2013-05-04)
909
Counter ID 67184426
Counter Name VS.ULBler.PS.BE. DCH.64.ErrTB
Counter Description Number of TBs with UL CRCI Error for PS 64 Kbit/s BE Services for Cell Sampling Times of BLER for PS 64 Kbit/s BE Services for Cell UL BLER of PS 128 Kbit/s BE Services on DCH for Cell Number of TBs with UL CRCI Error for PS 128 Kbit/s BE Services for Cell Sampling Times of BLER for PS 128 Kbit/s BE Services for Cell UL BLER of PS 144 Kbit/s BE Services on DCH for Cell Number of TBs with UL CRCI Error for PS 144 Kbit/s BE Services for Cell Sampling Times of BLER for PS 144 Kbit/s BE Services for Cell UL BLER of PS 256 Kbit/s BE Services on DCH for Cell Number of TBs with UL CRCI Error for PS 256 Kbit/s BE Services for Cell Sampling Times of BLER for PS 256 Kbit/s BE Services for Cell
67184427
67199810
67184428
67184429
67199811
67184430
67184431
67199812
67184432
67184433
Issue 01 (2013-05-04)
910
Counter ID 67199813
Counter Name VS.ULBler.PS.BE. DCH.384 VS.ULBler.PS.BE. DCH.384.ErrTB
Counter Description UL BLER of PS 384 Kbit/s BE Services on DCH for Cell Number of TBs with UL CRCI Error for PS 384 Kbit/s BE Services for Cell Sampling Times of BLER for PS 384 Kbit/s BE Services for Cell Rate of Duration that UL BLER of AMR Services Exceeds Target Value for Cell Rate of Duration that UL BLER of CS 64 Kbit/s Conversational Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 8 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 16 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 32 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 64 Kbit/s BE Services on DCH Exceeds Target Value for Cell
67184434
67184435
67202429
VS.ULBLer.Out.A MR
73394085
VS.ULBler.Out.CS 64
V900R012
67202439
VS.ULBler.Out.PS. BE.DCH.8
67202440
67202441
67202442
Issue 01 (2013-05-04)
911
Counter ID 67202443
Counter Name VS.ULBler.Out.PS. BE.DCH.128
Counter Description Rate of Duration that UL BLER of PS 128 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 144 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 256 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 384 Kbit/s BE Services on DCH Exceeds Target Value for Cell UL BLER of PS 8 Kbit/s BE Service on RACH for Cell Number of Error Blocks of PS 8 kbit/s BE Services on RACH for Cell Number of PS 8 kbit/ s BE Service Samplings on RACH for Cell Rate of Duration that AMR Speech Quality is GOOD for Cell Rate of Duration that AMR Speech Quality is ACCEPT for Cell Rate of Duration that AMR Speech Quality is BAD for Cell
67202444
67202445
67202446
67202447
VS.ULBler.PS.BE. RACH VS.ULBler.PS.BE. RACH.ErrTB
67189898
67189899
VS.ULBler.PS.BE. RACH.Sample
V900R012
67204479
VS.Voice.VQI.Goo d.TimeRate
67204480
VS.Voice.VQI.Acce pt.TimeRate
67204481
VS.Voice.VQI.Bad. TimeRate
Issue 01 (2013-05-04)
912
Counter ID 73410495
Counter Name VS.ULBler.PS.Con v
Counter Description UL BLER of PS Conversational Services on DCH for Cell Number of TBs with UL CRCI Error for PS Conversational Services for Cell Sampling Times of BLER for PS Conversational Services for Cell UL BLER of PS Streaming Services on DCH for Cell Number of TBs with UL CRCI Error for PS Streaming Services for Cell Sampling Times of BLER for PS Streaming Services for Cell Rate of Duration that UL BLER of PS Conversational Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS Streaming Services on DCH Exceeds Target Value for Cell Rate of Duration that AMR Speech Quality is POOR for Cell Rate of Duration that AMR Speech Quality is EXCELLENT for Cell
73394040
VS.ULBler.PS.Con v.ErrTB
V900R012
73394041
VS.ULBler.PS.Con v.Sample
V900R012
73410496
VS.ULBler.PS.Str
V900R012
73394042
VS.ULBler.PS.Str. ErrTB
V900R012
73394043
VS.ULBler.PS.Str. Sample
V900R012
73410497
VS.ULBler.Out.PS. Conv
V900R012
73410498
VS.ULBler.Out.PS. Str
V900R012
73441535
VS.Voice.VQI.Poor .TimeRate
V900R014
73441536
VS.Voice.VQI.Exce llent.TimeRate
V900R014
Issue 01 (2013-05-04)
913
Counter ID 73442310
Counter Name VS.Voice.VQI.Aver age
Counter Description Average VQI for AMR Services
None
1.12.3.1 Percentage of Duration When UL BLER on DCH Exceeds Target Value for Cell Counters
Counter ID 67202429 Counter Name VS.ULBLer.Out.AMR Counter Description Rate of Duration that UL BLER of AMR Services Exceeds Target Value for Cell Rate of Duration that UL BLER of CS 64 Kbit/s Conversational Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 8 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 16 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 32 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 64 Kbit/s BE Services on DCH Exceeds Target Value for Cell
73394085
VS.ULBler.Out.CS64
67202439
VS.ULBler.Out.PS.BE.DC H.8
67202440
67202441
67202442
Issue 01 (2013-05-04)
914
Counter ID 67202443
Counter Name VS.ULBler.Out.PS.BE.DC H.128
Counter Description Rate of Duration that UL BLER of PS 128 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 144 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 256 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS 384 Kbit/s BE Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS Conversational Services on DCH Exceeds Target Value for Cell Rate of Duration that UL BLER of PS Streaming Services on DCH Exceeds Target Value for Cell
67202444
67202445
67202446
73410497
VS.ULBler.Out.PS.Conv
73410498
VS.ULBler.Out.PS.Str
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67189862 Counter Name VS.ULBler.Out.AMR.OutTime Counter Description Duration that UL BLER of AMR Speech Services Reaches Target Value for Cell Duration that UL BLER of CS 64 kbit/s Real-Time Services Reaches Target Value for Cell Duration that UL BLER of PS 128 kbit/s Non-RealTime Services on DCH Reaches Target Value for Cell
67189870
VS.ULBler.Out.CSRT. 64.OutTime
67189890
VS.ULBler.Out.PSNrt.DCH .128.OutTime
Issue 01 (2013-05-04)
915
Counter ID 67189892
Counter Name VS.ULBler.Out.PSNrt.DCH .144.OutTime
Counter Description Duration that UL BLER of PS 144 kbit/s Non-RealTime Services on DCH Reaches Target Value for Cell Duration that UL BLER of PS 16 kbit/s Non-Real-Time Services Reaches Target Value for Cell Duration that UL BLER of PS 256 kbit/s Non-RealTime Services on DCH Reaches Target Value for Cell Duration that UL BLER of PS 32 kbit/s Non-Real-Time Services on DCH Reaches Target Value for Cell Duration that UL BLER of PS 384 kbit/s Non-RealTime Services on DCH Reaches Target Value for Cell Duration that UL BLER of PS 64 kbit/s Non-Real-Time Services on DCH Reaches Target Value for Cell Duration that UL BLER of PS 8 kbit/s Non-Real-Time Services Reaches Target Value for Cell Duration that UL BLER of PS Conversational Services Reaches Target Value for Cell Duration that UL BLER of PS Streaming Services Reaches Target Value for Cell
67189884
67189894
67189886
67189896
67189888
67189882
73394044
VS.ULBler.PS.Conv.OutTime
73394045
VS.ULBler.PS.Str.OutTime
Description
These counters provide the percentage of the duration when the uplink block error rate (BLER) on the DCH exceeds target value for services in the best cell. The measured services include the
adaptive multirate (AMR) service, CS 64 kbit/s conversational service, PS conversational service, PS streaming service, and PS BE service. The VS.ULBLer.Out.AMR counter measures only the narrowband AMR service.
Measurement point
The measurement is triggered in the best cell when the number of uplink TBs carrying services on the DCH reaches the defined sampling window (500 TBs). The measured services include the AMR service, CS 64 kbit/s conversational service, PS conversational service, PS streaming service, and PS BE service. At the end of the measurement period, this counter is calculated by dividing the number of times that the measured BLER exceeds the target value by the total number of sampling times.
Formula
VS.ULBLer.Out.AMR = {100}*[VS.ULBler.Out.AMR.OutTime]/ [VS.ULBler.AMR.Sample] VS.ULBler.Out.CS64 = {100}*[VS.ULBler.Out.CSRT.64.OutTime]/ [VS.ULBler.CS64.Sample] VS.ULBler.Out.PS.BE.DCH.8 = {100}*[VS.ULBler.Out.PSNrt.DCH.8.OutTime]/ [VS.ULBler.PS.BE.DCH.8.Sample] VS.ULBler.Out.PS.BE.DCH.16 = {100}*[VS.ULBler.Out.PSNrt.DCH.16.OutTime]/ [VS.ULBler.PS.BE.DCH.16.Sample] VS.ULBler.Out.PS.BE.DCH.32 = {100}*[VS.ULBler.Out.PSNrt.DCH.32.OutTime]/ [VS.ULBler.PS.BE.DCH.32.Sample] VS.ULBler.Out.PS.BE.DCH.64 = {100}*[VS.ULBler.Out.PSNrt.DCH.64.OutTime]/ [VS.ULBler.PS.BE.DCH.64.Sample] VS.ULBler.Out.PS.BE.DCH.128 = {100}*[VS.ULBler.Out.PSNrt.DCH.128.OutTime]/ [VS.ULBler.PS.BE.DCH.128.Sample] VS.ULBler.Out.PS.BE.DCH.144 = {100}*[VS.ULBler.Out.PSNrt.DCH.144.OutTime]/ [VS.ULBler.PS.BE.DCH.144.Sample] VS.ULBler.Out.PS.BE.DCH.256 = {100}*[VS.ULBler.Out.PSNrt.DCH.256.OutTime]/ [VS.ULBler.PS.BE.DCH.256.Sample] VS.ULBler.Out.PS.BE.DCH.384 = {100}*[VS.ULBler.Out.PSNrt.DCH.384.OutTime]/ [VS.ULBler.PS.BE.DCH.384.Sample] VS.ULBler.Out.PS.Conv = {100}*[VS.ULBler.PS.Conv.OutTime]/ [VS.ULBler.PS.Conv.Sample] VS.ULBler.Out.PS.Str = {100}*[VS.ULBler.PS.Str.OutTime]/[VS.ULBler.PS.Str.Sample]
Unit
%
Issue 01 (2013-05-04)
917
Related Features
Counter Name VS.ULBLer.Out.AMR VS.ULBler.Out.CS64 VS.ULBler.Out.PS.BE.DC H.8 VS.ULBler.Out.PS.BE.DC H.16 VS.ULBler.Out.PS.BE.DC H.32 VS.ULBler.Out.PS.BE.DC H.64 VS.ULBler.Out.PS.BE.DC H.128 VS.ULBler.Out.PS.BE.DC H.144 VS.ULBler.Out.PS.BE.DC H.256 VS.ULBler.Out.PS.BE.DC H.384 VS.ULBler.Out.PS.Conv VS.ULBler.Out.PS.Str Feature ID WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 Feature Name Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control
1.12.3.2 UL BLER of Services on RACH or DCH for Cell Counters

Counter ID 67202447 67199797 73394082 Counter Name VS.ULBler.PS.BE.RACH VS.ULBler.AMR VS.ULBler.CS64 Counter Description UL BLER of PS 8 Kbit/s BE Service on RACH for Cell UL BLER of AMR Services for Cell UL BLER of CS 64 Kbit/s Conversational Services on DCH for Cell UL BLER of PS 8 Kbit/s BE Services on DCH for Cell
67199806
VS.ULBler.PS.BE.DCH.8
Issue 01 (2013-05-04)
918
Counter ID 67199807 67199808 67199809 67199810 67199811 67199812 67199813 73410495
Counter Name VS.ULBler.PS.BE.DCH.16 VS.ULBler.PS.BE.DCH.32 VS.ULBler.PS.BE.DCH.64 VS.ULBler.PS.BE.DCH. 128 VS.ULBler.PS.BE.DCH. 144 VS.ULBler.PS.BE.DCH. 256 VS.ULBler.PS.BE.DCH. 384 VS.ULBler.PS.Conv
Counter Description UL BLER of PS 16 Kbit/s BE Services on DCH for Cell UL BLER of PS 32 Kbit/s BE Services on DCH for Cell UL BLER of PS 64 Kbit/s BE Services on DCH for Cell UL BLER of PS 128 Kbit/s BE Services on DCH for Cell UL BLER of PS 144 Kbit/s BE Services on DCH for Cell UL BLER of PS 256 Kbit/s BE Services on DCH for Cell UL BLER of PS 384 Kbit/s BE Services on DCH for Cell UL BLER of PS Conversational Services on DCH for Cell UL BLER of PS Streaming Services on DCH for Cell
73410496
VS.ULBler.PS.Str
Description
These counters provide the uplink block error rate (BLER) of services on the RACH or DCH in the best cell. The measured services include the adaptive multirate (AMR) service, CS 64 kbit/ s conversational service, PS conversational service, PS streaming service, and PS BE service. The VS.ULBler.AMR counter applies only to the narrowband AMR service. Counters VS.ULBler.AMR, VS.ULBler.CS64, VS.ULBler.PS.Conv, and VS.ULBler.PS.Str measure the uplink BLER on the DCH.
Measurement point
The measurement is triggered in the best cell when the number of uplink TBs carrying services on the RACH or DCH reaches the defined sampling window (500 TBs). The measured services include the AMR service, CS 64 kbit/s conversational service, PS conversational service, PS streaming service, and PS BE service.
Formula
VS.ULBler.PS.BE.RACH = [VS.ULBler.PS.BE.RACH.ErrTB]/ ([VS.ULBler.PS.BE.RACH.Sample]*{5}) VS.ULBler.AMR = [VS.ULBler.AMR.ErrTB]/([VS.ULBler.AMR.Sample]*{5}) VS.ULBler.CS64 = [VS.ULBler.CS64.ErrTB]/([VS.ULBler.CS64.Sample]*{5})
VS.ULBler.PS.BE.DCH.8 = [VS.ULBler.PS.BE.DCH.8.ErrTB]/([VS.ULBler.PS.BE.DCH. 8.Sample]*{5}) VS.ULBler.PS.BE.DCH.16 = [VS.ULBler.PS.BE.DCH.16.ErrTB]/ ([VS.ULBler.PS.BE.DCH.16.Sample]*{5}) VS.ULBler.PS.BE.DCH.32 = [VS.ULBler.PS.BE.DCH.32.ErrTB]/ ([VS.ULBler.PS.BE.DCH.32.Sample]*{5}) VS.ULBler.PS.BE.DCH.64 = [VS.ULBler.PS.BE.DCH.64.ErrTB]/ ([VS.ULBler.PS.BE.DCH.64.Sample]*{5}) VS.ULBler.PS.BE.DCH.128 = [VS.ULBler.PS.BE.DCH.128.ErrTB]/ ([VS.ULBler.PS.BE.DCH.128.Sample]*{5}) VS.ULBler.PS.BE.DCH.144 = [VS.ULBler.PS.BE.DCH.144.ErrTB]/ ([VS.ULBler.PS.BE.DCH.144.Sample]*{5}) VS.ULBler.PS.BE.DCH.256 = [VS_ULBler_PS_BE_DCH_256_ErrTB]/ ([VS_ULBler_PS_BE_DCH_256_Sample]*{5}) VS.ULBler.PS.BE.DCH.384 = [VS.ULBler.PS.BE.DCH.384.ErrTB]/ ([VS.ULBler.PS.BE.DCH.384.Sample]*{5}) VS.ULBler.PS.Conv = [VS.ULBler.PS.Conv.ErrTB]/([VS.ULBler.PS.Conv.Sample]*{5}) VS.ULBler.PS.Str = [VS.ULBler.PS.Str.ErrTB]/([VS.ULBler.PS.Str.Sample]*{5})
Unit
%
Related Features
Counter Name VS.ULBler.PS.BE.RACH VS.ULBler.AMR VS.ULBler.CS64 VS.ULBler.PS.BE.DCH.8 VS.ULBler.PS.BE.DCH.16 VS.ULBler.PS.BE.DCH.32 VS.ULBler.PS.BE.DCH.64 VS.ULBler.PS.BE.DCH. 128 VS.ULBler.PS.BE.DCH. 144 VS.ULBler.PS.BE.DCH. 256
Issue 01 (2013-05-04)
Feature ID WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503
Feature Name Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control
920
Counter Name VS.ULBler.PS.BE.DCH. 384 VS.ULBler.PS.Conv VS.ULBler.PS.Str
Feature Name Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control
1.12.3.3 Number of TBs with UL CRCI Errors for Services on RACH or DCH for Cell Counters
Counter ID 67189898 Counter Name VS.ULBler.PS.BE.RACH.E rrTB VS.ULBler.AMR.ErrTB Counter Description Number of Error Blocks of PS 8 kbit/s BE Services on RACH for Cell Number of TBs with UL CRCI Error for AMR Services for Cell Number of TBs with UL CRCI Error for CS 64 Kbit/s Conversational Services for Cell Number of TBs with UL CRCI Error for PS 8 Kbit/s BE Services for Cell Number of TBs with UL CRCI Error for PS 16 Kbit/s BE Services for Cell Number of TBs with UL CRCI Error for PS 32 Kbit/s BE Services for Cell Number of TBs with UL CRCI Error for PS 64 Kbit/s BE Services for Cell Number of TBs with UL CRCI Error for PS 128 Kbit/ s BE Services for Cell Number of TBs with UL CRCI Error for PS 144 Kbit/ s BE Services for Cell
67184402
73394083
VS.ULBler.CS64.ErrTB
67184420
VS.ULBler.PS.BE.DCH. 8.ErrTB VS.ULBler.PS.BE.DCH. 16.ErrTB VS.ULBler.PS.BE.DCH. 32.ErrTB VS.ULBler.PS.BE.DCH. 64.ErrTB VS.ULBler.PS.BE.DCH. 128.ErrTB VS.ULBler.PS.BE.DCH. 144.ErrTB
67184422
67184424
67184426
67184428
67184430
Issue 01 (2013-05-04)
921
Counter ID 67184432
Counter Name VS.ULBler.PS.BE.DCH. 256.ErrTB VS.ULBler.PS.BE.DCH. 384.ErrTB VS.ULBler.PS.Conv.ErrTB
Counter Description Number of TBs with UL CRCI Error for PS 256 Kbit/ s BE Services for Cell Number of TBs with UL CRCI Error for PS 384 Kbit/ s BE Services for Cell Number of TBs with UL CRCI Error for PS Conversational Services for Cell Number of TBs with UL CRCI Error for PS Streaming Services for Cell
67184434
73394040
73394042
VS.ULBler.PS.Str.ErrTB
Description
These counters provide the number of TBs with uplink cyclic redundancy check indicator (CRCI) errors for services on the RACH or DCH in the best cell. The measured services include the adaptive multirate (AMR) service, CS 64 kbit/s conversational service, PS conversational service, PS streaming service, and PS BE service. The VS.ULBler.AMR.ErrTB counter applies only to the narrowband AMR service. Counters VS.ULBler.AMR.ErrTB, VS.ULBler.CS64.ErrTB, VS.ULBler.PS.Conv.ErrTB, and VS.ULBler.PS.Str.ErrTB measure TBs with uplink CRCI errors on the DCH.
Measurement point
Formula
None
Unit
None
Related Features
Counter Name VS.ULBler.PS.BE.RACH.E rrTB VS.ULBler.AMR.ErrTB
Issue 01 (2013-05-04)
Feature Name Outer Loop Power Control Outer Loop Power Control
922
Counter Name VS.ULBler.CS64.ErrTB VS.ULBler.PS.BE.DCH. 8.ErrTB VS.ULBler.PS.BE.DCH. 16.ErrTB VS.ULBler.PS.BE.DCH. 32.ErrTB VS.ULBler.PS.BE.DCH. 64.ErrTB VS.ULBler.PS.BE.DCH. 128.ErrTB VS.ULBler.PS.BE.DCH. 144.ErrTB VS.ULBler.PS.BE.DCH. 256.ErrTB VS.ULBler.PS.BE.DCH. 384.ErrTB VS.ULBler.PS.Conv.ErrTB VS.ULBler.PS.Str.ErrTB
Feature Name Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control
1.12.3.4 Number of UL BLER Samplings for Services on the RACH or DCH for Cell Counters
Counter ID 67189899 Counter Name VS.ULBler.PS.BE.RACH.S ample VS.ULBler.AMR.Sample VS.ULBler.CS64.Sample Counter Description Number of PS 8 kbit/s BE Service Samplings on RACH for Cell Number of BLER Samplings for AMR Services for Cell Number of BLER Samplings for CS 64 Kbit/s Conversational Services for Cell Sampling Times of BLER for PS 8 Kbit/s BE Services for Cell
67184403 73394084
67184421
VS.ULBler.PS.BE.DCH. 8.Sample
Issue 01 (2013-05-04)
923
Counter ID 67184423
Counter Name VS.ULBler.PS.BE.DCH. 16.Sample VS.ULBler.PS.BE.DCH. 32.Sample VS.ULBler.PS.BE.DCH. 64.Sample VS.ULBler.PS.BE.DCH. 128.Sample VS.ULBler.PS.BE.DCH. 144.Sample VS.ULBler.PS.BE.DCH. 256.Sample VS.ULBler.PS.BE.DCH. 384.Sample VS.ULBler.PS.Conv.Sample VS.ULBler.PS.Str.Sample
Counter Description Sampling Times of BLER for PS 16 Kbit/s BE Services for Cell Sampling Times of BLER for PS 32 Kbit/s BE Services for Cell Sampling Times of BLER for PS 64 Kbit/s BE Services for Cell Sampling Times of BLER for PS 128 Kbit/s BE Services for Cell Sampling Times of BLER for PS 144 Kbit/s BE Services for Cell Sampling Times of BLER for PS 256 Kbit/s BE Services for Cell Sampling Times of BLER for PS 384 Kbit/s BE Services for Cell Sampling Times of BLER for PS Conversational Services for Cell Sampling Times of BLER for PS Streaming Services for Cell
67184425
67184427
67184429
67184431
67184433
67184435
73394041
73394043
Description
These counters provide the number of uplink block error rate (BLER) samplings for services on the RACH or DCH in the best cell. The measured services include the adaptive multirate (AMR) service, CS 64 kbit/s conversational service, PS conversational service, PS streaming service, and PS BE service. The VS.ULBler.AMR.Sample counter applies only to the narrowband AMR service. Counters VS.ULBler.AMR.Sample, VS.ULBler.CS64.Sample, VS.ULBler.PS.Conv.Sample, and VS.ULBler.PS.Str.Sample measure the number of uplink BLER samplings on the DCH.
Measurement point
Formula
None
Unit
None
Related Features
Counter Name VS.ULBler.PS.BE.RACH.S ample VS.ULBler.AMR.Sample VS.ULBler.CS64.Sample VS.ULBler.PS.BE.DCH. 8.Sample VS.ULBler.PS.BE.DCH. 16.Sample VS.ULBler.PS.BE.DCH. 32.Sample VS.ULBler.PS.BE.DCH. 64.Sample VS.ULBler.PS.BE.DCH. 128.Sample VS.ULBler.PS.BE.DCH. 144.Sample VS.ULBler.PS.BE.DCH. 256.Sample VS.ULBler.PS.BE.DCH. 384.Sample VS.ULBler.PS.Conv.Sample VS.ULBler.PS.Str.Sample Feature ID WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 Feature Name Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control
1.12.3.5 Percentage of Duration for AMR Voice Quality Being at A Level to Total Call Duration for Cell
Issue 01 (2013-05-04)
925
Counters
Counter ID 73441536 Counter Name VS.Voice.VQI.Excellent.Ti meRate VS.Voice.VQI.Good.TimeRate VS.Voice.VQI.Accept.Time Rate VS.Voice.VQI.Bad.TimeRate VS.Voice.VQI.Poor.TimeRate Counter Description Rate of Duration that AMR Speech Quality is EXCELLENT for Cell Rate of Duration that AMR Speech Quality is GOOD for Cell Rate of Duration that AMR Speech Quality is ACCEPT for Cell Rate of Duration that AMR Speech Quality is BAD for Cell Rate of Duration that AMR Speech Quality is POOR for Cell
67204479
67204480
67204481
73441535
Description
These counters provide the percentage of duration when the broadband or narrowband adaptive multirate (AMR) voice quality is assessed as EXCELLENT, GOOD, ACCEPT, BAD, or POOR to the total call duration. The mapping between the AMR voice quality level and the voice quality indicator (VQI) are as follows: EXCELLENT: VQI > 4 GOOD: VQI > 3 and VQI <= 4 ACCEPT: VQI > 2 and VQI <= 3 BAD: VQI > 1 and VQI <= 2 POOR: VQI <= 1
Measurement point
In a measurement period, the duration when the AMR voice quality is assessed as EXCELLENT, GOOD, ACCEPT, BAD, or POOR is sampled every 2.4s. At the end of the measurement period, these counters are calculated by dividing the corresponding accumulated duration by the total call duration in the best cell.
Formula
None
Unit
%
Related Features
Counter Name VS.Voice.VQI.Excellent.Ti meRate VS.Voice.VQI.Good.TimeRate VS.Voice.VQI.Accept.Time Rate VS.Voice.VQI.Bad.TimeRate VS.Voice.VQI.Poor.TimeRate Feature ID WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 Feature Name Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class
1.12.3.6 Average VQI for AMR Services Counters

Counter ID 73442310 Counter Name VS.Voice.VQI.Average Counter Description Average VQI for AMR Services
Description
This counter provides the average uplink VQI for narrowband and broadband AMR services in the best cell.
Measurement point
The system calculates the total uplink VQI for narrowband and broadband AMR services in the best cell. Within each measurement period, this counter divides the total uplink VQI by the sampling times.
Formula
None
Unit
None
Issue 01 (2013-05-04)
927
Related Features
Counter Name VS.Voice.VQI.Average Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.12.4 Cell Measurement on BOOST(BOOST.CELL)

Overview
The BOOST.CELL function subset includes the numbers of UU BOOST service establishments and releases for UMTS-UMTS dual terminal in the downlink, and indicators related to UU BOOST traffic. This function subset is effective only when the UMTS-UMTS Dual Terminal Downlink BOOST feature is enabled.
Counters
Counter ID 73424977 Counter Name VS.BOOST.UU.An chor.DL.R99.Bytes Counter Description Number of R99 Downlink Bytes of UU BOOST Anchor for Cell Mean Throughput of R99 Downlink of UU BOOST Anchor for Cell Number of HSDPA Downlink Bytes of UU BOOST Anchor for Cell Mean Throughput of HSDPA Downlink of UU BOOST Anchor for Cell Number of R99 Uplink Bytes of UU BOOST Anchor for Cell Mean Throughput of R99 Uplink of UU BOOST Anchor for Cell Original Release V900R014
73441547
VS.BOOST.UU.An chor.DL.R99.Mean Throughput VS.BOOST.UU.An chor.DL.HSDPA.B ytes VS.BOOST.UU.An chor.DL.HSDPA.M eanThroughput VS.BOOST.UU.An chor.UL.R99.Bytes
V900R014
73424979
V900R014
73441548
V900R014
73424981
V900R014
73441549
VS.BOOST.UU.An chor.UL.R99.Mean Throughput
V900R014
Issue 01 (2013-05-04)
928
Counter ID 73424983
Counter Name VS.BOOST.UU.An chor.UL.HSUPA.B ytes VS.BOOST.UU.An chor.UL.HSUPA.M eanThroughput VS.BOOST.UU.Br anch.DL.R99.Bytes
Counter Description Number of HSUPA Uplink Bytes of UU BOOST Anchor for Cell Mean Throughput of HSUPA Uplink of UU BOOST Anchor for Cell Number of R99 Downlink Bytes of UU BOOST Branch for Cell Mean Throughput of R99 Downlink of UU BOOST Branch for Cell Number of HSDPA Downlink Bytes of UU BOOST Branch for Cell Mean Throughput of HSDPA Downlink of UU BOOST Branch for Cell Number of R99 Uplink Bytes of UU BOOST Branch for Cell Mean Throughput of R99 Uplink of UU BOOST Branch for Cell Number of HSUPA Uplink Bytes of UU BOOST Branch for Cell Mean Throughput of HSUPA Uplink of UU BOOST Branch for Cell
73441550
V900R014
73424985
V900R014
73441551
VS.BOOST.UU.Br anch.DL.R99.Mean Throughput VS.BOOST.UU.Br anch.DL.HSDPA.B ytes VS.BOOST.UU.Br anch.DL.HSDPA. MeanThroughput VS.BOOST.UU.Br anch.UL.R99.Bytes
V900R014
73424987
V900R014
73441552
V900R014
73424989
V900R014
73441553
VS.BOOST.UU.Br anch.UL.R99.Mean Throughput VS.BOOST.UU.Br anch.UL.HSUPA.B ytes VS.BOOST.UU.Br anch.UL.HSUPA. MeanThroughput
V900R014
73424991
V900R014
73441554
V900R014
Issue 01 (2013-05-04)
929
Counter ID 73424993
Counter Name VS.BOOST.UU.BP LCapRprtInd
Counter Description Number of UU BOOST BPL Capability Indication Messages Received for Cell Number of Successful Responses to UU BOOST BPL Capability Indication Messages Transmitted for Cell Number of UU BOOST BPL User Information Indication Messages Received for Cell Number of Successful Responses to UU BOOST BPL User Information Indication Messages Transmitted for Cell Number of UU BOOST BPL Release Messages Transmitted for Cell Number of Successful UU BOOST Setups for Cell Number of Normal UU BOOST Anchor Releases for Cell Number of Normal UU BOOST Branch Releases for Cell Average Number of UU BOOST Anchor UEs for Cell
73424994
VS.BOOST.UU.BP LCapRsp.Succ
V900R014
73424995
VS.BOOST.UU.BP LInfoRprtInd
V900R014
73424996
VS.BOOST.UU.BP LInfoRsp.Succ
V900R014
73424997
VS.BOOST.UU.BP LRel
V900R014
73424998
VS.BOOST.UU.Su ccEstab
V900R014
73424999
VS.BOOST.UU.An chor.NormRel VS.BOOST.UU.Br anch.NormRel VS.BOOST.UU.An chorUEs.Mean
V900R014
73425000
V900R014
73441555
V900R014
Issue 01 (2013-05-04)
930
Counter ID 73441556
Counter Name VS.BOOST.UU.Br anchUEs.Mean
Counter Description Average Number of UU BOOST Branch UEs for Cell
None
1.12.4.1 Number of R99 Downlink Bytes of UU BOOST Anchor for Cell Counters
Counter ID 73424977 Counter Name VS.BOOST.UU.Anchor.DL .R99.Bytes Counter Description Number of R99 Downlink Bytes of UU BOOST Anchor for Cell
Description
This counter provides the total RLC traffic volume transmitted by PS services of UU BOOST anchor UEs on downlink R99 channels in cells in the active set. RLC headers and retransmitted data are not included.
Measurement point
When downlink PS RABs of UU BOOST anchor UEs are carried over R99 channels (including the DCH and FACH) and there is downlink data transmission, the RNC measures the number of all bytes (data of all service types) transmitted on the downlink RLC layer of cells in the active set. RLC headers and retransmitted data are not included.
Formula
None
Unit
byte
Related Features
None
1.12.4.2 Mean Throughput of R99 Downlink of UU BOOST Anchor for Cell

Counters
Counter ID 73441547 Counter Name VS.BOOST.UU.Anchor.DL .R99.MeanThroughput Counter Description Mean Throughput of R99 Downlink of UU BOOST Anchor for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73424978 Counter Name VS.BOOST.UU.Anchor.DL .R99.Time Counter Description Duration of R99 Downlink Sending Data of UU BOOST Anchor for Cell
Description
This counter provides the mean throughput rate of PS services of UU BOOST anchor UEs transmitted on downlink R99 channels of cells in the active set.
Measurement point
When downlink PS RABs of UU BOOST anchor UEs are carried over R99 channels (including the DCH and FACH) and there is downlink data transmission, the RNC measures the total actual data transmission time and number of all transmitted bytes of cells in the active set. At the end of a measurement period, the RNC measures this item by dividing the number of all transmitted bytes by the total actual data transmission time. In soft handover scenarios, the RNC measures this item of each cell in the active set separately.
Formula
VS.BOOST.UU.Anchor.DL.R99.MeanThroughput = [VS.BOOST.UU.Anchor.DL.R99.Bytes]*{8}/[VS.BOOST.UU.Anchor.DL.R99.Time]
Unit
kbit/s
Related Features
None
1.12.4.3 Number of HSDPA Downlink Bytes of UU BOOST Anchor for Cell
Issue 01 (2013-05-04)
932
Counters
Counter ID 73424979 Counter Name VS.BOOST.UU.Anchor.DL .HSDPA.Bytes Counter Description Number of HSDPA Downlink Bytes of UU BOOST Anchor for Cell
Description
This counter provides the total RLC traffic volume transmitted by PS services of UU BOOST anchor UEs on downlink HSDPA channels in the HSDPA serving cell. RLC headers and retransmitted data are not included.
Measurement point
When downlink PS RABs of UU BOOST anchor UEs are carried over HSDPA channels and there is downlink data transmission, the RNC measures the number of all bytes (data of all service types) transmitted on the downlink RLC layer in the HSDPA serving cell. RLC headers and retransmitted data are not included.
Formula
None
Unit
byte
Related Features
None
1.12.4.4 Mean Throughput of HSDPA Downlink of UU BOOST Anchor for Cell Counters
Counter ID 73441548 Counter Name VS.BOOST.UU.Anchor.DL .HSDPA.MeanThroughput Counter Description Mean Throughput of HSDPA Downlink of UU BOOST Anchor for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas.
Issue 01 (2013-05-04)
933
Counter ID 73424980
Counter Name VS.BOOST.UU.Anchor.DL .HSDPA.Time
Counter Description Duration of HSDPA Downlink Sending Data of UU BOOST Anchor for Cell
Description
This counter provides the mean throughput rate of PS services of UU BOOST anchor UEs transmitted on downlink HSDPA channels in the HSDPA serving cell.
Measurement point
When downlink PS RABs of UU BOOST anchor UEs are carried over HSDPA channels and there is downlink data transmission, the RNC measures the total actual data transmission time and number of all transmitted bytes in the HSDPA serving cell. At the end of a measurement period, the RNC measures this item by dividing the number of all transmitted bytes by the total actual data transmission time.
Formula
VS.BOOST.UU.Anchor.DL.HSDPA.MeanThroughput = [VS.BOOST.UU.Anchor.DL.HSDPA.Bytes]*{8}/ [VS.BOOST.UU.Anchor.DL.HSDPA.Time]
Unit
kbit/s
Related Features
None
1.12.4.5 Number of R99 Uplink Bytes of UU BOOST Anchor for Cell Counters
Counter ID 73424981 Counter Name VS.BOOST.UU.Anchor.UL .R99.Bytes Counter Description Number of R99 Uplink Bytes of UU BOOST Anchor for Cell
Description
This counter provides the total RLC traffic volume received by PS services of UU BOOST anchor UEs on uplink R99 channels in cells in the active set. RLC headers and retransmitted data are not included.
Measurement point
When uplink PS RABs of UU BOOST anchor UEs are carried over R99 channels (including the DCH and RACH) and there is uplink data reception, the RNC measures the number of all bytes (data of all service types) received on the uplink RLC layer of cells in the active set. RLC headers and retransmitted data are not included.
Formula
None
Unit
byte
Related Features
None
1.12.4.6 Mean Throughput of R99 Uplink of UU BOOST Anchor for Cell Counters
Counter ID 73441549 Counter Name VS.BOOST.UU.Anchor.UL .R99.MeanThroughput Counter Description Mean Throughput of R99 Uplink of UU BOOST Anchor for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73424982 Counter Name VS.BOOST.UU.Anchor.UL .R99.Time Counter Description Duration of R99 Uplink Receiving Data of UU BOOST Anchor for Cell
Description
This counter provides the mean throughput rate of PS services of UU BOOST anchor UEs received on uplink R99 channels of cells in the active set.
Measurement point
When uplink PS RABs of UU BOOST anchor UEs are carried over R99 channels (including the DCH and RACH) and there is uplink data reception, the RNC measures the total actual data reception time and number of all received bytes of cells in the active set. At the end of a measurement period, the RNC measures this item by dividing the number of all received bytes
by the total actual data reception time. In soft handover scenarios, the RNC measures this item of each cell in the active set separately after combination.
Formula
VS.BOOST.UU.Anchor.UL.R99.MeanThroughput = [VS.BOOST.UU.Anchor.UL.R99.Bytes]*{8}/[VS.BOOST.UU.Anchor.UL.R99.Time]
Unit
kbit/s
Related Features
None
1.12.4.7 Number of HSUPA Uplink Bytes of UU BOOST Anchor for Cell Counters
Counter ID 73424983 Counter Name VS.BOOST.UU.Anchor.UL .HSUPA.Bytes Counter Description Number of HSUPA Uplink Bytes of UU BOOST Anchor for Cell
Description
This counter provides the total RLC traffic volume received by PS services of UU BOOST anchor UEs on uplink HSUPA channels in cells in the HSUPA active set. RLC headers and retransmitted data are not included.
Measurement point
When uplink PS RABs of UU BOOST anchor UEs are carried over HSUPA channels and there is uplink data reception, the RNC measures the number of all bytes (data of all service types) received on the uplink RLC layer of cells in the HSUPA active set. RLC headers and retransmitted data are not included. In soft handover scenarios, the RNC measures this item of each cell in the HSUPA active set separately after combination.
Formula
None
Unit
byte
Related Features
None
1.12.4.8 Mean Throughput of HSUPA Uplink of UU BOOST Anchor for Cell Counters
Counter ID 73441550 Counter Name VS.BOOST.UU.Anchor.UL .HSUPA.MeanThroughput Counter Description Mean Throughput of HSUPA Uplink of UU BOOST Anchor for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73424984 Counter Name VS.BOOST.UU.Anchor.UL .HSUPA.Time Counter Description Duration of HSUPA Uplink Receiving Data of UU BOOST Anchor for Cell
Description
This counter provides the mean throughput rate of PS services of UU BOOST anchor UEs received on uplink HSUPA channels of cells in the HSUPA active set.
Measurement point
When uplink PS RABs of UU BOOST anchor UEs are carried over HSUPA channels and there is uplink data reception, the RNC measures the total actual data reception time and number of all received bytes of cells in the HSUPA active set. At the end of a measurement period, the RNC measures this item by dividing the number of all received bytes by the total actual data reception time. In soft handover scenarios, the RNC measures this item of each cell in the HSUPA active set separately after combination.
Formula
VS.BOOST.UU.Anchor.UL.HSUPA.MeanThroughput = [VS.BOOST.UU.Anchor.UL.HSUPA.Bytes]*{8}/ [VS.BOOST.UU.Anchor.UL.HSUPA.Time]
Unit
kbit/s
Related Features
None
1.12.4.9 Number of R99 Downlink Bytes of UU BOOST Branch for Cell

Counters
Counter ID 73424985 Counter Name VS.BOOST.UU.Branch.DL. R99.Bytes Counter Description Number of R99 Downlink Bytes of UU BOOST Branch for Cell
Description
This counter provides the total RLC traffic volume transmitted by PS services of UU BOOST branch UEs on downlink R99 channels in cells in the active set. RLC headers and retransmitted data are not included.
Measurement point
When downlink PS RABs of UU BOOST branch UEs are carried over R99 channels (including the DCH and FACH) and there is downlink data transmission, the RNC measures the number of all bytes (data of all service types) transmitted on the downlink RLC layer of cells in the active set. RLC headers and retransmitted data are not included.
Formula
None
Unit
byte
Related Features
None
1.12.4.10 Mean Throughput of R99 Downlink of UU BOOST Branch for Cell Counters
Counter ID 73441551 Counter Name VS.BOOST.UU.Branch.DL. R99.MeanThroughput Counter Description Mean Throughput of R99 Downlink of UU BOOST Branch for Cell
Issue 01 (2013-05-04)
938
Counter ID 73424986
Counter Name VS.BOOST.UU.Branch.DL. R99.Time
Counter Description Duration of R99 Downlink Sending Data of UU BOOST Branch for Cell
Description
This counter provides the mean throughput rate of PS services of UU BOOST branch UEs transmitted on downlink R99 channels of cells in the active set.
Measurement point
When downlink PS RABs of UU BOOST branch UEs are carried over R99 channels (including the DCH and FACH) and there is downlink data transmission, the RNC measures the total actual data transmission time and number of all transmitted bytes of cells in the active set. At the end of a measurement period, the RNC measures this item by dividing the number of all transmitted bytes by the total actual data transmission time. In soft handover scenarios, the RNC measures this item of each cell in the active set separately.
Formula
VS.BOOST.UU.Branch.DL.R99.MeanThroughput = [VS.BOOST.UU.Branch.DL.R99.Bytes]*{8}/[VS.BOOST.UU.Branch.DL.R99.Time]
Unit
kbit/s
Related Features
None
1.12.4.11 Number of HSDPA Downlink Bytes of UU BOOST Branch for Cell Counters
Counter ID 73424987 Counter Name VS.BOOST.UU.Branch.DL. HSDPA.Bytes Counter Description Number of HSDPA Downlink Bytes of UU BOOST Branch for Cell
Description
This counter provides the total RLC traffic volume transmitted by PS services of UU BOOST branch UEs on downlink HSDPA channels in the HSDPA serving cell. RLC headers and retransmitted data are not included.
Measurement point
When downlink PS RABs of UU BOOST branch UEs are carried over HSDPA channels and there is downlink data transmission, the RNC measures the number of all bytes (data of all service types) transmitted on the downlink RLC layer in the HSDPA serving cell. RLC headers and retransmitted data are not included.
Formula
None
Unit
byte
Related Features
None
1.12.4.12 Mean Throughput of HSDPA Downlink of UU BOOST Branch for Cell Counters
Counter ID 73441552 Counter Name VS.BOOST.UU.Branch.DL. HSDPA.MeanThroughput Counter Description Mean Throughput of HSDPA Downlink of UU BOOST Branch for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73424988 Counter Name VS.BOOST.UU.Branch.DL. HSDPA.Time Counter Description Duration of HSDPA Downlink Sending Data of UU BOOST Branch for Cell
Description
This counter provides the mean throughput rate of PS services of UU BOOST branch UEs transmitted on downlink HSDPA channels in the HSDPA serving cell.
Measurement point
When downlink PS RABs of UU BOOST branch UEs are carried over HSDPA channels and there is downlink data transmission, the RNC measures the total actual data transmission time and number of all transmitted bytes in the HSDPA serving cell. At the end of a measurement
period, the RNC measures this item by dividing the number of all transmitted bytes by the total actual data transmission time.
Formula
VS.BOOST.UU.Branch.DL.HSDPA.MeanThroughput = [VS.BOOST.UU.Branch.DL.HSDPA.Bytes]*{8}/ [VS.BOOST.UU.Branch.DL.HSDPA.Time]
Unit
kbit/s
Related Features
None
1.12.4.13 Number of R99 Uplink Bytes of UU BOOST Branch for Cell Counters
Counter ID 73424989 Counter Name VS.BOOST.UU.Branch.UL. R99.Bytes Counter Description Number of R99 Uplink Bytes of UU BOOST Branch for Cell
Description
This counter provides the total RLC traffic volume received by PS services of UU BOOST branch UEs on uplink R99 channels in cells in the active set. RLC headers and retransmitted data are not included.
Measurement point
When uplink PS RABs of UU BOOST branch UEs are carried over R99 channels (including the DCH and RACH) and there is uplink data reception, the RNC measures the number of all bytes (data of all service types) received on the uplink RLC layer of cells in the active set. RLC headers and retransmitted data are not included.
Formula
None
Unit
byte
Related Features
None
1.12.4.14 Mean Throughput of R99 Uplink of UU BOOST Branch for Cell Counters
Counter ID 73441553 Counter Name VS.BOOST.UU.Branch.UL. R99.MeanThroughput Counter Description Mean Throughput of R99 Uplink of UU BOOST Branch for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73424990 Counter Name VS.BOOST.UU.Branch.UL. R99.Time Counter Description Duration of R99 Uplink Receiving Data of UU BOOST Branch for Cell
Description
This counter provides the mean throughput rate of PS services of UU BOOST branch UEs received on uplink R99 channels of cells in the active set.
Measurement point
When uplink PS RABs of UU BOOST branch UEs are carried over R99 channels (including the DCH and RACH) and there is uplink data reception, the RNC measures the total actual data reception time and number of all received bytes of cells in the active set. At the end of a measurement period, the RNC measures this item by dividing the number of all received bytes by the total actual data reception time. In soft handover scenarios, the RNC measures this item of each cell in the active set separately after combination.
Formula
VS.BOOST.UU.Branch.UL.R99.MeanThroughput = [VS.BOOST.UU.Branch.UL.R99.Bytes]*{8}/[VS.BOOST.UU.Branch.UL.R99.Time]
Unit
kbit/s
Related Features
None
1.12.4.15 Number of HSUPA Uplink Bytes of UU BOOST Branch for Cell

Counters
Counter ID 73424991 Counter Name VS.BOOST.UU.Branch.UL. HSUPA.Bytes Counter Description Number of HSUPA Uplink Bytes of UU BOOST Branch for Cell
Description
This counter provides the total RLC traffic volume received by PS services of UU BOOST branch UEs on uplink HSUPA channels in cells in the HSUPA active set. RLC headers and retransmitted data are not included.
Measurement point
When uplink PS RABs of UU BOOST branch UEs are carried over HSUPA channels and there is uplink data reception, the RNC measures the number of all bytes (data of all service types) received on the uplink RLC layer of cells in the HSUPA active set. RLC headers and retransmitted data are not included. In soft handover scenarios, the RNC measures this item of each cell in the HSUPA active set separately after combination.
Formula
None
Unit
byte
Related Features
None
1.12.4.16 Mean Throughput of HSUPA Uplink of UU BOOST Branch for Cell Counters
Counter ID 73441554 Counter Name VS.BOOST.UU.Branch.UL. HSUPA.MeanThroughput Counter Description Mean Throughput of HSUPA Uplink of UU BOOST Branch for Cell
Counter ID 73424992
Counter Name VS.BOOST.UU.Branch.UL. HSUPA.Time
Counter Description Duration of HSUPA Uplink Receiving Data of UU BOOST Branch for Cell
Description
This counter provides the mean throughput rate of PS services of UU BOOST branch UEs received on uplink HSUPA channels of cells in the HSUPA active set.
Measurement point
When uplink PS RABs of UU BOOST branch UEs are carried over HSUPA channels and there is uplink data reception, the RNC measures the total actual data reception time and number of all received bytes of cells in the HSUPA active set. At the end of a measurement period, the RNC measures this item by dividing the number of all received bytes by the total actual data reception time. In soft handover scenarios, the RNC measures this item of each cell in the HSUPA active set separately after combination.
Formula
VS.BOOST.UU.Branch.UL.HSUPA.MeanThroughput = [VS.BOOST.UU.Branch.UL.HSUPA.Bytes]*{8}/ [VS.BOOST.UU.Branch.UL.HSUPA.Time]
Unit
kbit/s
Related Features
None
1.12.4.17 Number of UU BOOST BPL Capability Indication Messages Received for Cell Counters
Counter ID 73424993 Counter Name VS.BOOST.UU.BPLCapRp rtInd Counter Description Number of UU BOOST BPL Capability Indication Messages Received for Cell
Description
This counter provides the number of UU BOOST BPL capability indication messages received in the best cell.
Measurement point
This measurement is triggered at point A as shown in the figure. When the RNC receives a UU BOOST BPL capability indication message after PS RAB establishment, the RNC measures this item in the best cell of the UE. Figure 1-393 BPL Message Interaction
Formula
None
Unit
None
Related Features
None
1.12.4.18 Number of Successful Responses to UU BOOST BPL Capability Indication Messages Transmitted for Cell Counters
Counter ID 73424994 Counter Name VS.BOOST.UU.BPLCapRs p.Succ Counter Description Number of Successful Responses to UU BOOST BPL Capability Indication Messages Transmitted for Cell
Issue 01 (2013-05-04)
945
Description
This counter provides the number of successful responses to UU BOOST BPL capability indication messages transmitted in the best cell.
Measurement point
This measurement is triggered at point B as shown in the figure. When the RNC successfully responds to a UU BOOST BPL capability indication message after PS RAB establishment, the RNC measures this item in the best cell of the UE. Figure 1-394 BPL Message Interaction
Formula
None
Unit
None
Related Features
None
1.12.4.19 Number of UU BOOST BPL User Information Indication Messages Received for Cell
Issue 01 (2013-05-04)
946
Counters
Counter ID 73424995 Counter Name VS.BOOST.UU.BPLInfoRprtInd Counter Description Number of UU BOOST BPL User Information Indication Messages Received for Cell
Description
This counter provides the number of UU BOOST BPL user information indication messages received in the best cell.
Measurement point
This measurement is triggered at point C as shown in the figure. When the RNC receives a UU BOOST BPL user information indication message after PS RAB establishment, the RNC measures this item in the best cell of the UE. Figure 1-395 BPL Message Interaction
Formula
None
Unit
None
Related Features
None
1.12.4.20 Number of Successful Responses to UU BOOST BPL User Information Indication Messages Transmitted for Cell Counters
Counter ID 73424996 Counter Name VS.BOOST.UU.BPLInfoRs p.Succ Counter Description Number of Successful Responses to UU BOOST BPL User Information Indication Messages Transmitted for Cell
Description
This counter provides the number of successful responses to UU BOOST BPL user information indication messages transmitted in the best cell.
Measurement point
This measurement is triggered at point D as shown in the figure. When the RNC successfully responds to a UU BOOST BPL user information indication message after PS RAB establishment, the RNC measures this item in the best cell of the UE. Figure 1-396 BPL Message Interaction
Formula
None
Issue 01 (2013-05-04)
948
Unit
None
Related Features
None
1.12.4.21 Number of UU BOOST BPL Release Messages Transmitted for Cell Counters
Counter ID 73424997 Counter Name VS.BOOST.UU.BPLRel Counter Description Number of UU BOOST BPL Release Messages Transmitted for Cell
Description
This counter provides the number of UU BOOST BPL release messages transmitted in the best cell.
Measurement point
This measurement is triggered at point E as shown in the figure. When the RNC transmits a UU BOOST BPL release message after PS RAB establishment and branch connection timeout, the RNC measures this item in the best cell of the UE. Figure 1-397 BPL Message Interaction
Issue 01 (2013-05-04)
949
Formula
None
Unit
None
Related Features
None
1.12.4.22 Number of Successful UU BOOST Setups for Cell Counters

Counter ID 73424998 Counter Name VS.BOOST.UU.SuccEstab Counter Description Number of Successful UU BOOST Setups for Cell
Description
This counter provides the number of successful UU BOOST setups in the best cell.
Measurement point
The measurement is triggered at point D as shown in the figure. When the RNC successfully responds to a UU BOOST BPL user information indication message and anchor and branch UEs complete UU BOOST configuration after PS RAB establishment, the RNC measures this item in the best cell of the anchor UE. Figure 1-398 BPL Message Interaction
Issue 01 (2013-05-04)
950
Formula
None
Unit
None
Related Features
None
1.12.4.23 Number of Normal UU BOOST Anchor Releases for Cell Counters

Counter ID 73424999 Counter Name VS.BOOST.UU.Anchor.Nor mRel Counter Description Number of Normal UU BOOST Anchor Releases for Cell
Description
This counter provides the number of normal UU BOOST anchor UE releases in the best cell.
Measurement point
This measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message from the CN, the RNC releases related RAB resources and responds with an IU RELEASE COMPLETE message. The RNC measures this item in the best cell of the UE if the following conditions are met: The UE is the UU BOOST anchor UE and has PS services to be released. The release cause in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization". OR The RNC initiates a release request with the release cause of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release".
Issue 01 (2013-05-04)
951
Figure 1-399 Iu release
Formula
None
Unit
None
Related Features
None
1.12.4.24 Number of Normal UU BOOST Branch Releases for Cell Counters

Counter ID 73425000 Counter Name VS.BOOST.UU.Branch.Nor mRel Counter Description Number of Normal UU BOOST Branch Releases for Cell
Description
This counter provides the number of normal UU BOOST branch UE releases in the best cell.
Measurement point
This measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message from the CN, the RNC releases related RAB resources and responds with an IU RELEASE COMPLETE message. The RNC measures this item in the best cell of the UE if the following conditions are met: The UE is the UU BOOST branch UE and has PS services to be released. The release cause in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization". OR The RNC initiates a release request with the release cause of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release". Figure 1-400 IU
Formula
None
Unit
None
Related Features
None
1.12.4.25 Average Number of UU BOOST Anchor UEs for Cell
Issue 01 (2013-05-04)
953
Counters
Counter ID 73441555 Counter Name VS.BOOST.UU.AnchorUEs .Mean Counter Description Average Number of UU BOOST Anchor UEs for Cell
Description
This counter provides the average number of UU BOOST anchor UEs in the best cell.
Measurement point
In the best cell of the anchor UEs, the RNC periodically samples the number of UU BOOST anchor UEs. The sample period is 5s. At the end of a measurement period, the RNC measures this item by calculating the sum of UEs at all sample points and dividing the sum by the times of sampling.
Formula
None
Unit
None
Related Features
None
1.12.4.26 Average Number of UU BOOST Branch UEs for Cell Counters

Counter ID 73441556 Counter Name VS.BOOST.UU.BranchUEs .Mean Counter Description Average Number of UU BOOST Branch UEs for Cell
Description
This counter provides the average number of UU BOOST branch UEs in the best cell.
Measurement point
In the best cell of the branch UEs, the RNC periodically samples the number of UU BOOST branch UEs. The sample period is 5s. At the end of a measurement period, the RNC measures this item by calculating the sum of UEs at all sample points and dividing the sum by the times of sampling.
Formula
None
Unit
None
Related Features
None
1.12.5 Common Channel Measurement per Cell(CCH.Cell)

Overview
This function subset measures the amount of traffic in the uplink and downlink of a common transport channel such as a PCH, RACH, and FACH in a cell.
Counters
Counter ID 73423941 Counter Name VS.IndepTRBNum .FACH VS.SRBNum.FAC H VS.OneSRBTTINu m.FACH Counter Description Number of TBs That Contain only TRB Data on FACHs Number of TBs That Contain SRB Data on FACHs Number of TTIs During Which One SRB TB Is Transmitted on FACHs Number of TRB TBs Received on RACHs Original Release V900R014
73423942
V900R014
73423943
V900R014
73423944
VS.TRBNum.RAC H
V900R014
None
1.12.5.1 Number of TBs That Contain only TRB Data on FACHs
Issue 01 (2013-05-04)
955
Counters
Counter ID 73423941 Counter Name VS.IndepTRBNum.FACH Counter Description Number of TBs That Contain only TRB Data on FACHs
Description
This counter measures the number of TBs that contain only TRB data on FACHs in a cell. It indicates the amount of user plane traffic transmitted on FACHs in a cell.
Measurement point
This counter is measured at MAC-c according to the type of data transmitted on FACHs during each transmission time interval (TTI).
Formula
None
Unit
None
Related Features
Counter Name VS.IndepTRBNum.FACH Feature ID WRFD-021000 Feature Name Transport Channel Management
1.12.5.2 Number of TBs That Contain SRB Data on FACHs Counters

Counter ID 73423942 Counter Name VS.SRBNum.FACH Counter Description Number of TBs That Contain SRB Data on FACHs
Description
This counter measures the number of TBs that contain SRB data on FACHs in a cell. It indicates the amount of control plane traffic transmitted on FACHs in a cell.
Measurement point
This counter is measured at MAC-c according to the type of data transmitted on FACHs during each transmission time interval (TTI).
Formula
None
Unit
None
Related Features
Counter Name VS.SRBNum.FACH Feature ID WRFD-021000 Feature Name Transport Channel Management
1.12.5.3 Number of TTIs During Which One SRB TB Is Transmitted on FACHs Counters
Counter ID 73423943 Counter Name VS.OneSRBTTINum.FACH Counter Description Number of TTIs During Which One SRB TB Is Transmitted on FACHs
Description
This counter measures the number of TTIs during which one SRB TB is transmitted on FACHs in a cell. It indicates the amount of control plane traffic transmitted on FACHs in a cell.
Measurement point
This counter is measured at MAC-c according to the type of data transmitted on FACHs during each transmission time interval (TTI). When only one S-CCPCH is configured, one SRB TB can be transmitted during one TTI in scenarios of FACH SRB TB x 1 and PCH TB + FACH SRB TB x 1. When two S-CCPCHs are configured, one SRB TB can be transmitted during one TTI in the scenario of FACH SRB TB x 1.
Formula
None
Unit
None
Related Features
Counter Name VS.OneSRBTTINum.FACH Feature ID WRFD-021000 Feature Name Transport Channel Management
1.12.5.4 Number of TRB TBs Received on RACHs Counters

Counter ID 73423944 Counter Name VS.TRBNum.RACH Counter Description Number of TRB TBs Received on RACHs
Description
This counter measures the number of TRB TBs received on RACHs in a cell.
Measurement point
This counter is measured at MAC-c.
Formula
None
Unit
None
Related Features
Counter Name VS.TRBNum.RACH Feature ID WRFD-021000 Feature Name Transport Channel Management
Issue 01 (2013-05-04)
958
1.12.6 Cell Update Measurement per cell(CELLUPDATE.Cell)

Overview
An UE may send a CELL UPDATE message to the RNC for different causes, such as uplink data transmission, paging response, radio link failure, re-entering service area, RLC unrecoverable error, cell reselection, and periodical cell update. This function subset is used to assess the cell update procedure by measuring the number of cell updates triggered by different causes, and the number of successful or failed cell updates triggered by each cause.
Counters
Counter ID 67180378 Counter Name VS.AttCellUpdt.R LFail Counter Description Number of Cell Updates Due to Radio Link Failure for Cell Number of Successful Cell Updates Due to Radio Link Failure for Cell Number of Failed Cell Updates Due to No Response from UE for Cell (Cell Update Caused by RL Failure) Number of CELL UPDATE CONFIRM Messages from SRNC for Cell Number of Cell Updates for Cell Number of Cell Updates Due to SRB RLC Unrecoverable Error for Cell Number of Cell Updates Due to TRB RLC Unrecoverable Error for Cell Original Release Earlier than V900R011
67189767
VS.SuccCellUpdt.R LFail
67189768
VS.FailCellUpdt.R LFail.NoReply
67180370
VS.CellUpdt.Confirm
67192569 67192570
VS.AttCellUpdt VS.AttCellUpdt.Er rSRB
67192571
VS.AttCellUpdt.Er rTRB
Issue 01 (2013-05-04)
959
Counter ID 67192572
Counter Name VS.SuccCellUpdt.E rrTRB
Counter Description Number of Successful Cell Updates Due to TRB RLC Unrecoverable Error for Cell Number of Cell Updates Due to MBMS Reception for Cell Number of Successful Cell Updates Due to MBMS Reception for Cell Number of Cell Updates Due to MBMS PtP RB Request for Cell Number of Successful Cell Updates Due to MBMS PtP RB Request for Cell Number of Periodical Cell Updates for Cell Number of Cell Updates Due to Cell Reselection for Cell Number of Cell Updates Due to ReEntering Service Area for Cell Number of Cell Updates Due to Paging Response for Cell Number of Cell Updates Due to Uplink Data Transmission for Cell
67192573
VS.AttCellUpdt.M bmsRecv
67192574
VS.SuccCellUpdt. MbmsRecv
67192575
VS.AttCellUpdt.M bmsPtpRbReq
67192576
VS.SuccCellUpdt. MbmsPtpRbReq
67180372
VS.AttCellUpdt.Pr d VS.AttCellUpdt.Re sel VS.AttCellUpdt.RS A
67180373
67180374
67180375
VS.AttCellUpdt.Pa geRsp
67180376
VS.AttCellUpdt.U LDataTrans
Issue 01 (2013-05-04)
960
Counter ID 67180379
Counter Name VS.SuccCellUpdt.P rd
Counter Description Number of Successful Periodical Cell Updates for Cell Number of Successful Cell Updates Due to Cell Reselection for Cell Number of Successful Cell Updates Due to ReEntering Service Area for Cell Number of Successful Cell Updates Due to Paging Response for Cell Number of Successful Cell Updates Due to Uplink Data Transmission for Cell Number of Successful Cell Updates for Cell Number of RRC Connection Releases Due to Cell Update Failure for Cell Number of Successful Cell Updates Due to SRB RLC Unrecoverable Error for Cell Number of Cell Update Failures due to No Response from UEs in the CELL_FACH State (SRB RLC ERROR) for Cell
67180380
VS.SuccCellUpdt.R esel
67180381
VS.SuccCellUpdt.R sa
67180382
VS.SuccCellUpdt.P ageRsp
67180383
VS.SuccCellUpdt.U LDataTrans
67180371
VS.SuccCellUpdt
67180386
VS.CellUpdt.RRC Rel
73423781
VS.SuccCellUpdt.E rrSRB
V900R013
73424125
VS.FailCellUpdt.E rrSRB.NoReply.FA CH
V900R014
Issue 01 (2013-05-04)
961
Counter ID 73424126
Counter Name VS.FailCellUpdt.E rrTRB.NoReply.F ACH
Counter Description Number of Cell Update Failures due to No Response from UEs in the CELL_FACH State (TRB RLC ERROR) for Cell Number of Cell Updates in a Cell Number of Cell Updates Triggered by CS Service Establishments in a Cell Number of Cell Updates that Are Under CPU UsageBased Flow Control and Are Triggered by CS Service Establishments in a Cell Number of Cell Updates that Are Under RRC Queuing-Based Flow Control and Are Triggered by CS Service Establishments in a Cell Number of Cell Updates that Are Under RRC Queuing-Based Flow Control in a Cell Number of Cell Update Attempts for Cell (Originating Conversational Call) Number of Cell Update Attempts for Cell (Terminating Conversational Call)
73424915 73424916
VS.AttCellUpdt.Ms g VS.AttCellUpdt.Ms g.Conv
V900R014 V900R014
73424917
VS.CU.CONV.FC. Num.CPU.OverLo ad
V900R014
73424918
VS.CU.CONV.FC. Num.RRCQueue
V900R014
73424919
VS.CU.FC.Num.R RCQueue
V900R014
73426327
VS.AttCellUpdt.Or gConvCall.PCH
V900R015
73426328
VS.AttCellUpdt.T mConvCall.PCH
V900R015
Issue 01 (2013-05-04)
962
Counter ID 73426329
Counter Name VS.AttCellUpdt.E mgCall.PCH
Counter Description Number of Cell Update Attempts for Cell (Emergency Call) Number of Successful Cell Updates for Cell (Originating Conversational Call) Number of Successful Cell Updates for Cell (Terminating Conversational Call) Number of Successful Cell Updates for Cell (Emergency Call) Number of Outgoing P2F Redirections for Cell Number of Incoming P2F Redirections for Cell (Cell Update) Number of P2F Redirection Failures Caused by UE Not Accessing the Target Frequency for Cell Number of P2F Redirection Failures Caused by UE No Response for Cell
73426330
VS.SuccCellUpdt. OrgConvCall.PCH
V900R015
73426331
VS.SuccCellUpdt.T mConvCall.PCH
V900R015
73426332
VS.SuccCellUpdt.E mgCall.PCH
V900R015
73426363
VS.P2F.Redir.Out
V900R015
73426364
VS.P2F.Redir.In.U seNewCU VS.P2F.Redir.Fail Out.NonTargetFC N
V900R015
73426365
V900R015
73426366
VS.P2F.Redir.Fail Out.NoReply
V900R015
None
1.12.6.1 Number of Unsuccessful Cell Updates due to RL Failure (No Response)
Issue 01 (2013-05-04)
963
Counters
Counter ID 67189768 Counter Name VS.FailCellUpdt.RLFail.No Reply Counter Description Number of Failed Cell Updates Due to No Response from UE for Cell (Cell Update Caused by RL Failure)
Description
This counter provides the number of times that a cell update triggered by "radio link failure" fails due to UE no response.
Measurement point
The measurement is triggered at point A in Figure 1. After receiving a CELL UPDATE message carrying a cause value of "radio link failure" from the UE, the RNC sends a CELL UPDATE CONFIRM message to the UE and starts a timer to wait for a response message from the UE (Figure 1 uses the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message as an example.) If the RNC does not receive any response message from the UE before the timer expires, this counter is measured for the cell where the UE sends the CELL UPDATE message. Figure 1-401 Cell update procedure (failed operation due to timer expiry)
Issue 01 (2013-05-04)
964
Formula
None
Unit
None
Related Features
Counter Name VS.FailCellUpdt.RLFail.No Reply Feature ID WRFD-010801 WRFD-010802 Feature Name Intra RNC Cell Update Inter RNC Cell Update
1.12.6.2 Number of Confirmation Messages from SRNC Counters

Counter ID 67180370 Counter Name VS.CellUpdt.Confirm Counter Description Number of CELL UPDATE CONFIRM Messages from SRNC for Cell
Description
This measurement item provides the number of CELL UPDATE CONFIRM messages sent from the SRNC to the UE in a cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the SRNC sends a CELL UPDATE CONFIRM message to the UE. In this case, the RNC measures the item in the cell that the UE has selected during the cell update procedure. Note that the measurement is not triggered for a CELL UPDATE CONFIRM message that is retransmitted by the RNC.
Issue 01 (2013-05-04)
965
Figure 1-402 Cell update procedure
Formula
None
Unit
None
Related Features
Counter Name VS.CellUpdt.Confirm Feature ID WRFD-010801 WRFD-010802 Feature Name Intra RNC Cell Update Inter RNC Cell Update
1.12.6.3 Number of Cell Update Attempts for Different Causes Counters

Counter ID 67180372 Counter Name VS.AttCellUpdt.Prd Counter Description Number of Periodical Cell Updates for Cell
966
Issue 01 (2013-05-04)
Counter ID 67180378 67192569 67192570
Counter Name VS.AttCellUpdt.RLFail VS.AttCellUpdt VS.AttCellUpdt.ErrSRB
Counter Description Number of Cell Updates Due to Radio Link Failure for Cell Number of Cell Updates for Cell Number of Cell Updates Due to SRB RLC Unrecoverable Error for Cell Number of Cell Updates Due to TRB RLC Unrecoverable Error for Cell Number of Cell Updates Due to MBMS Reception for Cell Number of Cell Updates Due to MBMS PtP RB Request for Cell Number of Cell Updates Due to Cell Reselection for Cell Number of Cell Updates Due to Re-Entering Service Area for Cell Number of Cell Updates Due to Paging Response for Cell Number of Cell Updates Due to Uplink Data Transmission for Cell
67192571
VS.AttCellUpdt.ErrTRB
67192573 67192575
VS.AttCellUpdt.MbmsRecv VS.AttCellUpdt.MbmsPtpR bReq VS.AttCellUpdt.Resel VS.AttCellUpdt.RSA
67180373 67180374
67180375 67180376
VS.AttCellUpdt.PageRsp VS.AttCellUpdt.ULDataTrans
Description
These counters provide the number of CELL UPDATE messages received by the RNC according to different cause values.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a CELL UPDATE message from the UE and the UE is not involved in a RRC connection release procedure, the RNC measures the items based on different cell update causes in the cell that the UE chooses during the cell update. The table describes these measurement items.This counter is not measured for a CELL UPDATE message retransmitted by the UE in the same cell.
Issue 01 (2013-05-04)
967
Formula
None
Unit
None
Related Features
Counter Name VS.AttCellUpdt.Prd Feature ID WRFD-010801 WRFD-010802 VS.AttCellUpdt.RLFail WRFD-010801 WRFD-010802 VS.AttCellUpdt WRFD-010801 WRFD-010802 VS.AttCellUpdt.ErrSRB WRFD-010801 WRFD-010802 VS.AttCellUpdt.ErrTRB WRFD-010801 WRFD-010802
Issue 01 (2013-05-04) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Feature Name Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update
968
Counter Name VS.AttCellUpdt.MbmsRecv
Feature Name Intra RNC Cell Update Inter RNC Cell Update MBMS Introduction Package Intra RNC Cell Update Inter RNC Cell Update MBMS Introduction Package Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update
VS.AttCellUpdt.MbmsPtpR bReq
WRFD-010801 WRFD-010802 WRFD-010616
VS.AttCellUpdt.Resel
WRFD-010801 WRFD-010802
VS.AttCellUpdt.RSA
WRFD-010801 WRFD-010802
VS.AttCellUpdt.PageRsp
WRFD-010801 WRFD-010802
VS.AttCellUpdt.ULDataTrans
WRFD-010801 WRFD-010802
1.12.6.4 Number of Successful Cell Updates for Different Causes Counters

Counter ID 67180371 67189767 Counter Name VS.SuccCellUpdt VS.SuccCellUpdt.RLFail Counter Description Number of Successful Cell Updates for Cell Number of Successful Cell Updates Due to Radio Link Failure for Cell Number of Successful Cell Updates Due to TRB RLC Unrecoverable Error for Cell Number of Successful Cell Updates Due to MBMS Reception for Cell Number of Successful Cell Updates Due to MBMS PtP RB Request for Cell
67192572
VS.SuccCellUpdt.ErrTRB
67192574
VS.SuccCellUpdt.MbmsRec v VS.SuccCellUpdt.MbmsPtp RbReq
67192576
Issue 01 (2013-05-04)
969
Counter ID 67180379
Counter Name VS.SuccCellUpdt.Prd
Counter Description Number of Successful Periodical Cell Updates for Cell Number of Successful Cell Updates Due to Cell Reselection for Cell Number of Successful Cell Updates Due to Re-Entering Service Area for Cell Number of Successful Cell Updates Due to Paging Response for Cell Number of Successful Cell Updates Due to Uplink Data Transmission for Cell Number of Successful Cell Updates Due to SRB RLC Unrecoverable Error for Cell
67180380
VS.SuccCellUpdt.Resel
67180381
VS.SuccCellUpdt.Rsa
67180382
VS.SuccCellUpdt.PageRsp
67180383
VS.SuccCellUpdt.ULDataTrans VS.SuccCellUpdt.ErrSRB
73423781
Description
The measurement items provide the number of successful cell updates for different causes in a cell. When the SRB reestablishment algorithm is enabled, the VS.SuccCellUpdt.ErrSRB counter is measured at a point shown in the following figures. When the algorithm is disabled, the counter is measured after the RNC receives a cell update message and performs the RRC connection release procedure.
Measurement point
There are two types of cell update procedures: cell update requiring UE response and cell update requiring no UE response. In a cell update requiring no UE response, the RNC determines that the cell update is successful after sending the CELL UPDATE CONFIRM message. In this procedure, the measurement is triggered after the RNC sends a CELL UPDATE CONFIRM message to the UE based on the cause value, as shown by point B in the following figure. The corresponding counter is measured in the cell that is selected by the UE for cell update.
Issue 01 (2013-05-04)
970
Figure 1-404 Basic cell update procedure
In a cell update requiring UE response, the RNC determines that the cell update is successful upon receiving the response message from the UE after sending a CELL UPDATE CONFIRM message to the UE. In this procedure, the measurement is triggered after the RNC receives a response message (such as the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message) from the UE based on the cause value, as shown by point C in the following figure. The corresponding counter is measured in the cell that is selected by the UE for cell update. The UE may respond with one of the following messages after receiving a CELL UPDATE CONFIRM message: UTRAN MOBILITY INFORMATION CONFIRM PHYSICAL CHANNEL RECONFIGURATION COMPLETE TRANSPORT CHANNEL RECONFIGURATION COMPLETE RADIO BEARER RECONFIGURATION COMPLETE RADIO BEARER RELEASE COMPLETE.
Issue 01 (2013-05-04)
971
Figure 1-405 Cell update procedure with physical channel reconfiguration
After the RNC receives a cell update message, if the RNC directly performs the RRC connection release procedure rather than performs a cell update, the counter is measured at point B, as shown in the following figure. For example, for cell updates due to SRB RLC unrecoverable errors, when the SRB reestablishment algorithm is disabled, the counter is measured after the RNC performs the RRC connection release procedure. Figure 1-406 Basic cell update procedure
Issue 01 (2013-05-04)
972
Formula
None
Unit
None
Related Features
Counter Name VS.SuccCellUpdt Feature ID WRFD-010801 WRFD-010802 VS.SuccCellUpdt.RLFail WRFD-010801 WRFD-010802 VS.SuccCellUpdt.ErrTRB WRFD-010801 WRFD-010802 VS.SuccCellUpdt.MbmsRec v WRFD-010801 WRFD-010802 WRFD-010616 VS.SuccCellUpdt.MbmsPtp RbReq WRFD-010801 WRFD-010802 WRFD-010616 VS.SuccCellUpdt.Prd WRFD-010801 WRFD-010802 VS.SuccCellUpdt.Resel WRFD-010801 WRFD-010802 VS.SuccCellUpdt.Rsa WRFD-010801 WRFD-010802 VS.SuccCellUpdt.PageRsp WRFD-010801 WRFD-010802 VS.SuccCellUpdt.ULDataTrans VS.SuccCellUpdt.ErrSRB WRFD-010801 WRFD-010802 WRFD-010801 WRFD-010802 Feature Name Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update MBMS Introduction Package Intra RNC Cell Update Inter RNC Cell Update MBMS Introduction Package Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update
Issue 01 (2013-05-04)
973
1.12.6.5 Number of RRC Connection Releases due to Cell Update Failure Counters
Counter ID 67180386 Counter Name VS.CellUpdt.RRCRel Counter Description Number of RRC Connection Releases Due to Cell Update Failure for Cell
Description
This counter provides the number of RRC connection releases due to cell update failures.
Measurement point
The measurement is triggered at point A in the following figure. If the cell update fails and therefore the RRC connection needs to be released, the RNC sends an RRC CONNECTION RELEASE message to the UE and measures this counter in the cell that is selected by the UE for cell update. Figure 1-407 RRC connection release procedure triggered by cell update
Formula
None
Unit
None
Related Features
Counter Name VS.CellUpdt.RRCRel Feature ID WRFD-010801 WRFD-010802 WRFD-010510 Feature Name Intra RNC Cell Update Inter RNC Cell Update 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.6.6 Number of Cell Update Failures due to No Response from UEs in the CELL_FACH State for Cell Counters
Counter ID 73424125 Counter Name VS.FailCellUpdt.ErrSRB.N oReply.FACH Counter Description Number of Cell Update Failures due to No Response from UEs in the CELL_FACH State (SRB RLC ERROR) for Cell Number of Cell Update Failures due to No Response from UEs in the CELL_FACH State (TRB RLC ERROR)for Cell
73424126
VS.FailCellUpdt.ErrTRB.N oReply.FACH
Description
These counters measure the number of cell update failures due to no response from UEs in the CELL_FACH state (with the cause value of RLC unrecoverable error) in a cell.
Measurement point
The measurement is triggered at point A in the Figure. After receiving a CELL UPDATE message carrying a cause value of "RLC unrecoverable error" from the UE in the RRC state of CELL_FACH, the RNC sends a CELL UPDATE CONFIRM message to the UE and starts a timer to wait for a response message from the UE (in the figure, the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message is simply an example). If the RNC does not receive any response message from the UE before the timer expires, these counters are increased by one in the cell where the UE sends the CELL UPDATE message according to the value carried
in the IE "AM_RLC error indication(RB2, RB3 or RB4)" and IE "AM_RLC error indication (RB>4)" in the CELL UPDATE message. Figure 1-408 Cell update procedure (failed operation due to timer expiry)
Formula
None
Unit
None
Related Features
Counter Name VS.FailCellUpdt.ErrSRB.N oReply.FACH VS.FailCellUpdt.ErrTRB.N oReply.FACH Feature ID WRFD-010801 WRFD-010802 WRFD-010801 WRFD-010802 Feature Name Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update
1.12.6.7 Number of Cell Updates in a Cell
Issue 01 (2013-05-04)
976
Counters
Counter ID 73424915 Counter Name VS.AttCellUpdt.Msg Counter Description Number of Cell Updates in a Cell
Description
This counter provides the total number of CELL UPDATE messages received in a cell. In addition, This counter also include those CELL UPDATE messages that are re-sent by UE.
Measurement point
This counter provides the total number of CELL UPDATE messages received in a cell. This counter is counted When the RNC receives a CELL UPDATE message which UE is in CELL_PCH/URA_PCH state.
Formula
None
Unit
None
Related Features
Counter Name VS.AttCellUpdt.Msg Feature ID WRFD-040100 Feature Name Flow Control
1.12.6.8 Number of Cell Updates Triggered by CS Service Establishments in a Cell Counters

Counter ID 73424916 Counter Name VS.AttCellUpdt.Msg.Conv Counter Description Number of Cell Updates Triggered by CS Service Establishments in a Cell
Description
This counter provides the number of CELL UPDATE messages due to establish CS services received in a cell. When the cause of CELL UPDATE is UU_ORIGINATING_CONVERSATIONAL_CALL_ESTAB_CAUSE,UU_TERMNT_CON
VERSATIONAL_CALL_ESTAB_CAUSE or UU_EMERGENCY_CALL_ESTAB_CAUSE, The RNC judges this service as CS Services.In addition, These counters also include those CELL UPDATE messages that are re-sent by UE.
Measurement point
This counter provides the number of CELL UPDATE messages due to establish CS servcies received in a cell. This counter is counted When the RNC receives a CELL UPDATE message which UE is in CELL_PCH/URA_PCH state.
Formula
None
Unit
None
Related Features
Counter Name VS.AttCellUpdt.Msg.Conv Feature ID WRFD-040100 Feature Name Flow Control
1.12.6.9 Number of Cell Updates that Are Under CPU Usage-Based Flow Control and Are Triggered by CS Service Establishments in a Cell Counters
Counter ID 73424917 Counter Name VS.CU.CONV.FC.Num.CP U.OverLoad Counter Description Number of Cell Updates that Are Under CPU UsageBased Flow Control and Are Triggered by CS Service Establishments in a Cell
Description
This counter provides the number of CELL UPDATE messages received in a cell which is Under Flow Control Triggered by CPU Usage. When the cause of CELL UPDATE is UU_ORIGINATING_CONVERSATIONAL_CALL_ESTAB_CAUSE,UU_TERMNT_CON VERSATIONAL_CALL_ESTAB_CAUSE or UU_EMERGENCY_CALL_ESTAB_CAUSE, The RNC judges this service as CS Services.In addition, These counters also include those CELL UPDATE messages that are re-sent by UE.
Issue 01 (2013-05-04)
978
Measurement point
If the cell is Under Flow Control Triggered by CPU Usage, the CELL UPDATE message will be discarded When this cell receives a CELL UPDATE message from the UE.
Formula
None
Unit
None
Related Features
Counter Name VS.CU.CONV.FC.Num.CP U.OverLoad Feature ID WRFD-040100 Feature Name Flow Control
1.12.6.10 Number of Cell Updates that Are Under RRC Queuing-Based Flow Control and Are Triggered by CS Service Establishments in a Cell Counters
Counter ID 73424918 Counter Name VS.CU.CONV.FC.Num.RR CQueue Counter Description Number of Cell Updates that Are Under RRC QueuingBased Flow Control and Are Triggered by CS Service Establishments in a Cell
Description
This counter provides the number of CELL UPDATE messages due to CS services received in a cell which is Under Flow Control Triggered by RRC Queue. When the cause of CELL UPDATE is UU_ORIGINATING_CONVERSATIONAL_CALL_ESTAB_CAUSE,UU_TERMNT_CON VERSATIONAL_CALL_ESTAB_CAUSE or UU_EMERGENCY_CALL_ESTAB_CAUSE, The RNC judges this service as CS Services.In addition, These counters also include those CELL UPDATE messages that are re-sent by UE.
Measurement point
If the cell is Under Flow Control Triggered by by RRC Queue, the CELL UPDATE messsage will be discarded When this cell receives a CELL UPDATE message from the UE.
Formula
None
Unit
None
Related Features
Counter Name VS.CU.CONV.FC.Num.RR CQueue Feature ID WRFD-040100 Feature Name Flow Control
1.12.6.11 Number of Cell Updates that Are Under RRC Queuing-Based Flow Control in a Cell Counters
Counter ID 73424919 Counter Name VS.CU.FC.Num.RRCQueue Counter Description Number of Cell Updates that Are Under RRC QueuingBased Flow Control in a Cell
Description
This counter provides the number of CELL UPDATE messages received in a cell which is Under Flow Control Triggered by RRC Queue. The CELL UPDATE or URA UPDATE messages are Flow Controled when the UE is in CELL_PCH/URA_PCH state. In addition, The counter also include those CELL UPDATE or URA UPDATE messages that are re-sent by UE.
Measurement point
This counter provides the number of CELL UPDATE or URA UPDATE messages received in a cell which is Under Flow Control Triggered by RRC Queue. (1)If the cell is Under Flow Control Triggered by RRC Queue, This counter will be counted When this cell receives a CELL UPDATE message from the UE in CELL_PCH/URA_PCH state. (2)If the cell is Under Flow Control Triggered by RRC Queue, This counter will be counted When this cell receives a URA UPDATE message from the UE in URA_PCH state.
Formula
None
Unit
None
Related Features
Counter Name VS.CU.FC.Num.RRCQueue Feature ID WRFD-040100 Feature Name Flow Control
1.12.6.12 Number of Cell Update Attempts for Cell (Originating Conversational Call) Counters
Counter ID 73426327 Counter Name VS.AttCellUpdt.OrgConvCa ll.PCH Counter Description Number of Cell Update Attempts for Cell (Originating Conversational Call) Number of Cell Update Attempts for Cell (Terminating Conversational Call) Number of Cell Update Attempts for Cell (Emergency Call)
73426328
VS.AttCellUpdt.TmConvCa ll.PCH
73426329
VS.AttCellUpdt.EmgCall.P CH
Description
These counters measure the number of cell update attempts made by UEs in the CELL_PCH or URA_PCH state to establish new services in a cell. These counters are measured based on the specific causes of cell update attempts.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives a CELL UPDATE message with the cause value "uplink data transmission" or "paging response" from a UE in the CELL_PCH or URA_PCH state, the RNC calculates the numbers of cell update attempts based on the cause values. The retransmitted CELL UPDATE messages are not calculated into these counters.
Issue 01 (2013-05-04)
981
Formula
None
Unit
None
Related Features
Counter Name VS.AttCellUpdt.OrgConvCa ll.PCH VS.AttCellUpdt.TmConvCa ll.PCH VS.AttCellUpdt.EmgCall.P CH Feature ID WRFD-010801 WRFD-010802 WRFD-010801 WRFD-010802 WRFD-010801 WRFD-010802 Feature Name Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update
1.12.6.13 Number of Successful Cell Updates for Cell (Originating Conversational Call)
Counters
Counter ID 73426330 Counter Name VS.SuccCellUpdt.OrgConv Call.PCH VS.SuccCellUpdt.TmConv Call.PCH Counter Description Number of Successful Cell Updates for Cell (Originating Conversational Call) Number of Successful Cell Updates for Cell (Terminating Conversational Call) Number of Successful Cell Updates for Cell (Emergency Call)
73426331
73426332
VS.SuccCellUpdt.EmgCall. PCH
Description
These counters measure the number of cell update attempts made by UEs in the CELL_PCH or URA_PCH state to establish new services in a cell. These counters are measured based on the specific causes of cell update attempts.
Measurement point
When receiving a CELL UPDATE message with the cause value "uplink data transmission" or "paging response" from a UE in the CELL_PCH or URA_PCH state, the RNC returns a CELL UPDATE CONFIRM message. If the RNC receives a response from the UE, the RNC considers the cell update procedure successful. The measurement is triggered at point C, as shown in the figure (The PHYSICAL CHANNEL RECONFIGURATION COMPLETE message in the figure is used as an example). On receiving the response from the UE, the RNC calculates the number of successful cell updates based on the cause values in the CELL UPDATE message. On receiving the CELL UPDATE CONFIRM message, the UE returns one of the following messages based on the IE carried in the CELL UPDATE CONFIRM message: UTRAN MOBILITY INFORMATION CONFIRM PHYSICAL CHANNEL RECONFIGURATION COMPLETE TRANSPORT CHANNEL RECONFIGURATION COMPLETE RADIO BEARER RECONFIGURATION COMPLETE RADIO BEARER RELEASE COMPLETE
Issue 01 (2013-05-04)
983
Figure 1-410 Cell update procedure with physical channel reconfiguration
Formula
None
Unit
None
Related Features
Counter Name VS.SuccCellUpdt.OrgConv Call.PCH VS.SuccCellUpdt.TmConv Call.PCH VS.SuccCellUpdt.EmgCall. PCH Feature ID WRFD-010801 WRFD-010802 WRFD-010801 WRFD-010802 WRFD-010801 WRFD-010802 Feature Name Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update Intra RNC Cell Update Inter RNC Cell Update
1.12.6.14 Number of Outgoing P2F Redirections for Cell
Issue 01 (2013-05-04)
984
Counters
Counter ID 73426363 Counter Name VS.P2F.Redir.Out Counter Description Number of Outgoing P2F Redirections for Cell
Description
This counter measures the number of outgoing redirections triggered by state transitions from CELL_PCH or URA_PCH to CELL_FACH in a cell. This counter is measured in the source cell and excludes the CELL UPDATE CONFIRM messages retransmitted by the RNC. In the current version, the value of this counter is 0. Using this counter is not recommended.
Measurement point
The measurement is triggered at point A, as shown in figure. The RNC receives a CELL UPDATE message with the cause value "uplink data transmission" or "paging response" from a UE in the CELL_PCH or URA_PCH state, and sends a CELL UPDATE CONFIRM message to the UE, instructing the UE to perform a P2F redirection. In this case, this counter is increased by one in the source cell. The retransmitted CELL UPDATE CONFIRM messages are not calculated into this counter. Figure 1-411 Cell update P2F redirection procedure
The measurement is triggered at point A, as shown in figure. The RNC receives a CELL UPDATE message with the cause value "uplink data transmission" or "paging response" from a UE in the CELL_PCH or URA_PCH state, and sends a CELL UPDATE CONFIRM message to the UE, instructing the UE to perform a P2F redirection. In this case, this counter is increased
by one in the source cell. The retransmitted CELL UPDATE CONFIRM messages are not calculated into this counter. Figure 1-412 Cell update P2F redirection procedure
Formula
None
Unit
None
Related Features
None
1.12.6.15 Number of Incoming P2F Redirections for Cell (Cell Update)
Issue 01 (2013-05-04)
986
Counters
Counter ID 73426364 Counter Name VS.P2F.Redir.In.UseNewCU Counter Description Number of Incoming P2F Redirections for Cell (Cell Update)
Description
This counter measures the number of incoming redirections triggered by state transitions from CELL_PCH or URA_PCH to CELL_FACH in the target cell for the redirection. In the current version, the value of this counter is 0. Using this counter is not recommended.
Measurement point
The measurement is triggered at point B, as shown in figure. The RNC receives a CELL UPDATE message with the cause value "uplink data transmission" or "paging response" from a UE in the CELL_PCH or URA_PCH state, and sends a CELL UPDATE CONFIRM message to the UE, instructing the UE to perform a P2F redirection. If the RNC receives a cell update request on the target frequency for the redirection, this counter is increased by one in the target cell. Figure 1-413 Cell update P2F redirection procedure
Issue 01 (2013-05-04)
987
Formula
None
Unit
None
Related Features
None
1.12.6.16 Number of P2F Redirection Failures Caused by UE Not Accessing the Target Frequency for Cell Counters
Counter ID 73426365 Counter Name VS.P2F.Redir.FailOut.NonTargetFCN Counter Description Number of P2F Redirection Failures Caused by UE Not Accessing the Target Frequency for Cell
Description
This counter measures the number of redirection failures caused by UE not accessing the target frequency for the redirection. The redirection must be triggered by state transitions from CELL_PCH or URA_PCH to CELL_FACH. This counter is measured in the source cell. In the current version, the value of this counter is 0. Using this counter is not recommended.
Measurement point
The measurement is triggered at point B, as shown in figure. The RNC receives a CELL UPDATE message with the cause value "uplink data transmission" or "paging response" from a UE in the CELL_PCH or URA_PCH state, and sends a CELL UPDATE CONFIRM message to the UE, instructing the UE to perform a P2F redirection. If the RNC receives a cell update request on a frequency other than the target frequency for the redirection, this counter is increased by one in the source cell.
Issue 01 (2013-05-04)
988
Figure 1-414 Cell update P2F redirection procedure
Formula
None
Unit
None
Related Features
None
1.12.6.17 Number of P2F Redirection Failures Caused by UE No Response for Cell Counters
Counter ID 73426366 Counter Name VS.P2F.Redir.FailOut.NoRe ply Counter Description Number of P2F Redirection Failures Caused by UE No Response for Cell
Issue 01 (2013-05-04)
989
Description
This counter measures the number of redirection failures caused by UE no response. The redirection must be triggered by state transitions from CELL_PCH or URA_PCH to CELL_FACH. This counter is measured in the source cell. In the current version, the value of this counter is 0. Using this counter is not recommended.
Measurement point
The measurement is triggered at point B, as shown in figure. The RNC receives a CELL UPDATE message with the cause value "uplink data transmission" or "paging response" from a UE in the CELL_PCH or URA_PCH state, and sends a CELL UPDATE CONFIRM message to the UE, instructing the UE to perform a P2F redirection. If the RNC does not receive a PHYSICAL CHANNEL RECONFIGURATION COMPLETE or CELL UPDATE message from the UE before the timer expires, this counter is increased by one in the source cell. Figure 1-415 Cell update P2F redirection procedure
The measurement is triggered at point B, as shown in figure. The RNC receives a CELL UPDATE message with the cause value "uplink data transmission" or "paging response" from a UE in the CELL_PCH or URA_PCH state, and sends a CELL UPDATE CONFIRM message to the UE, instructing the UE to perform a P2F redirection. If the RNC does not receive a PHYSICAL CHANNEL RECONFIGURATION COMPLETE or CELL UPDATE message from the UE before the timer expires, this counter is increased by one in the source cell.
Issue 01 (2013-05-04)
990
Figure 1-416 Cell update P2F redirection procedure
Formula
None
Unit
None
Related Features
None
1.12.7 Measurement of Compressed Mode per cell(CM.Cell)

Overview
This function subset is used to measure the number of Compressed Mode Activation Attempts and the number of Compressed Mode Activation fails.
Issue 01 (2013-05-04)
991
Counters
Counter ID 67194881 Counter Name VS.CM.ULSF2.Act .Att Counter Description Number of Uplink SF-2 Compression Mode Activation Requests for Cell Number of Uplink HLS Compression Mode Activation Requests for Cell Number of Uplink SF-2 Compression Mode Activation Failures for Cell Number of Uplink HLS Compression Mode Activation Failures for Cell Number of Downlink SF-2 Compression Mode Activation Requests for Cell Number of Downlink HLS Compression Mode Activation Requests for Cell Number of Downlink SF-2 Compression Mode Activation Failures for Cell Number of Downlink HLS Compression Mode Activation Failures for Cell Original Release Earlier than V900R011
67194882
VS.CM.ULHLS.Ac t.Att
67194883
VS.CM.ULSF2.Act .Fail
67194884
VS.CM.ULHLS.Ac t.Fail
67194885
VS.CM.DLSF2.Act .Att
67194886
VS.CM.DLHLS.Ac t.Att
67194887
VS.CM.DLSF2.Act .Fail
67194888
VS.CM.DLHLS.Ac t.Fail
None
1.12.7.1 Number of Up Link SF-2 Compressed Mode Activation Attempts
Issue 01 (2013-05-04)
992
Counters
Counter ID 67194881 Counter Name VS.CM.ULSF2.Act.Att Counter Description Number of Uplink SF-2 Compression Mode Activation Requests for Cell
Description
This measurement item provides the number of Up Link SF-2 Compressed Mode Activation Attempts in a cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC sends the UE a MEASUREMENT CONTROL message, the RNC measures the counter if the SF/2 compressed mode is used in the uplink. Figure 1-417 Flow chart of Measurement of Compressed Mode
Formula
None
Unit
None
Issue 01 (2013-05-04)
993
Related Features
Counter Name VS.CM.ULSF2.Act.Att Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.7.2 Number of Up Link HLS Compressed Mode Activation Attempts Counters

Counter ID 67194882 Counter Name VS.CM.ULHLS.Act.Att Counter Description Number of Uplink HLS Compression Mode Activation Requests for Cell
Description
This measurement item provides the number of Up Link HLS Compressed Mode Activation Attempts in a cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC sends the UE a MEASUREMENT CONTROL message, the RNC measures the counter if the high layer scheduling (HLS) compressed mode is used in the uplink. Figure 1-418 Flow chart of Measurement of Compressed Mode
Issue 01 (2013-05-04)
994
Formula
None
Unit
None
Related Features
Counter Name VS.CM.ULHLS.Act.Att Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.7.3 Number of Up Link SF-2 Compressed Mode Activation Fails Counters

Counter ID 67194883 Counter Name VS.CM.ULSF2.Act.Fail Counter Description Number of Uplink SF-2 Compression Mode Activation Failures for Cell
Description
This measurement item provides the number of Up Link SF-2 Compressed Mode Activation Fails in a cell.
Measurement point
The measurement is triggered at point C as shown in the following figure. When the RNC receives a MEASUREMENT CONTROL FAILURE message related to the Up Link SF/2 compressed mode from the UE or does not receive the ACK message for MEASUREMENT CONTROL, it measures the counter.
Issue 01 (2013-05-04)
995
Figure 1-419 Flow chart of Measurement of Compressed Mode
Formula
None
Unit
None
Related Features
Counter Name VS.CM.ULSF2.Act.Fail Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.7.4 Number of Up Link HLS Compressed Mode Activation Fails Counters

Counter ID 67194884 Counter Name VS.CM.ULHLS.Act.Fail Counter Description Number of Uplink HLS Compression Mode Activation Failures for Cell
Description
This measurement item provides the number of Up Link HLS Compressed Mode Activation Fails in a cell.
Measurement point
The measurement is triggered at point C as shown in the following figure. When the RNC receives a MEASUREMENT CONTROL FAILURE message related to the Up Link HLS compressed mode from the UE or does not receive the ACK message for MEASUREMENT CONTROL, it measures the counter. Figure 1-420 Flow chart of Measurement of Compressed Mode
Formula
None
Unit
None
Related Features
Counter Name VS.CM.ULHLS.Act.Fail Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.7.5 Number of Down Link SF-2 Compressed Mode Activation Attempts
Issue 01 (2013-05-04)
997
Counters
Counter ID 67194885 Counter Name VS.CM.DLSF2.Act.Att Counter Description Number of Downlink SF-2 Compression Mode Activation Requests for Cell
Description
This measurement item provides the number of Down Link SF-2 Compressed Mode Activation Attempts in a cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC sends the UE a MEASUREMENT CONTROL message, the RNC measures the counter if the SF/2 compressed mode is used in the downlink. Figure 1-421 Flow chart of Measurement of Compressed Mode
Formula
None
Unit
None
Issue 01 (2013-05-04)
998
Related Features
Counter Name VS.CM.DLSF2.Act.Att Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.7.6 Number of Down Link HLS Compressed Mode Activation Attempts Counters
Counter ID 67194886 Counter Name VS.CM.DLHLS.Act.Att Counter Description Number of Downlink HLS Compression Mode Activation Requests for Cell
Description
This measurement item provides the number of Down Link HLS Compressed Mode Activation Attempts in a cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC sends the UE a MEASUREMENT CONTROL message, the RNC measures the counter if the HLS compressed mode is used in the downlink. Figure 1-422 Flow chart of Measurement of Compressed Mode
Issue 01 (2013-05-04)
999
Formula
None
Unit
None
Related Features
Counter Name VS.CM.DLHLS.Act.Att Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.7.7 Number of Down Link SF-2 Compressed Mode Activation Fails Counters
Counter ID 67194887 Counter Name VS.CM.DLSF2.Act.Fail Counter Description Number of Downlink SF-2 Compression Mode Activation Failures for Cell
Description
This measurement item provides the number of Down Link SF-2 Compressed Mode Activation Fails in a cell.
Measurement point
The measurement is triggered at point C as shown in the following figure. When the RNC receives a MEASUREMENT CONTROL FAILURE message related to the Down Link SF/2 compressed mode from the UE or does not receive the ACK message for MEASUREMENT CONTROL, it measures the counter.
Issue 01 (2013-05-04)
1000
Figure 1-423 Flow chart of Measurement of Compressed Mode
Formula
None
Unit
None
Related Features
Counter Name VS.CM.DLSF2.Act.Fail Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.7.8 Number of Down Link HLS Compressed Mode Activation Fails Counters
Counter ID 67194888 Counter Name VS.CM.DLHLS.Act.Fail Counter Description Number of Downlink HLS Compression Mode Activation Failures for Cell
Description
This measurement item provides the number of Down Link HLS Compressed Mode Activation Fails in a cell.
Measurement point
The measurement is triggered at point C as shown in the following figure. When the RNC receives a MEASUREMENT CONTROL FAILURE message related to the Down Link HLS compressed mode from the UE or does not receive the ACK message for MEASUREMENT CONTROL, it measures the counter. Figure 1-424 Flow chart of Measurement of Compressed Mode
Formula
None
Unit
None
Related Features
Counter Name VS.CM.DLHLS.Act.Fail Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.8 EFACH Measurement per cell(EFACH.Cell)

Overview
UEs in the E-FACH state are those in the CELL_FACH state and use the HS-DSCH for downlink transmission. EFACH refers to the status that the UE uplink is established on the RACH and the UE downlink is established on the HSDSCH. This technology can increase CELL_FACH user downlink data
peak rate and shorten state transfer delay time. The function subset EFACH Measurement (Cell) is used to measure this technology related services on the basis of Cell.
Counters
Counter ID 67193111 Counter Name VS.RRC.AttConnE stab.EFACH Counter Description Number of RRC Establishment Requests on EFACH for Cell Number of Successful RRC Establishments on EFACH for Cell Number of PS RAB Establishment Requests on EFACH for Cell Number of Successful PS RAB Establishments on EFACH for Cell Maximum Duration of PS RAB Establishment Process on FACH for Cell Mean Duration of PS RAB Establishment Process on FACH for Cell Number of Abnormal RAB Releases on EFACH for Cell Number of Normal PS RAB Release on EFACH for Cell Number of Bytes of MAC PDUs Sent on IUB EFACH FP for Cell Original Release Earlier than V900R011
67193112
VS.RRC.SuccConn Estab.EFACH
67193119
VS.RAB.AttEstPS. EFACH
67193120
VS.RAB.SuccEstP S.EFACH
67193121
VS.RAB.Estab.PS. CellFACH.MaxTi me
67204169
VS.RAB.Estab.PS. CellFACH.MeanTime VS.RAB.AbnormR el.PS.EFACH
67193127
67193128
VS.RAB.NormRel. PS.EFACH VS.CRNCIubBytes EFACH.Tx
67204778
Issue 01 (2013-05-04)
1003
Counter ID 73410512
Counter Name VS.EFACHUEs
Counter Description Number of UEs carried on EFACH for Cell Maximum Duration of RRC Establishment Process on EFACH for Cell Mean Duration of RRC Establishment Process on EFACH for Cell Number of UEs Carried on the EFACH and Using E-DRX Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_DCH (DCH) for Cell Number of Attempts at State Transitions from CELL_DCH (DCH) to Enhanced CELL_FACH for Cell Number of Successful State Transitions from Enhanced CELL_FACH to CELL_DCH (DCH) for Cell Number of Successful State Transitions from CELL_DCH (DCH) to Enhanced CELL_FACH for Cell
73421757
VS.RRC.ConnEsta bTimeMax.CellFA CH.EFACH
73439900
VS.RRC.ConnEsta bTimeMean.CellF ACH.EFACH VS.EDRXUEs
V900R012
73441122
V900R013
73426149
VS.EFACH.F2D.At t
V900R015
73426150
VS.EFACH.D2F.At t
V900R015
73426151
VS.EFACH.F2D.S ucc
V900R015
73426152
VS.EFACH.D2F.S ucc
V900R015
Issue 01 (2013-05-04)
1004
Counter ID 73426153
Counter Name VS.EFACH.H2F.S ucc
Counter Description Number of Successful State Transitions from CELL_DCH (HSDSCH) to Enhanced CELL_FACH for Cell Number of Successful State Transitions from Enhanced CELL_FACH to CELL_DCH (HSDSCH) for Cell Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_DCH (HSDSCH) for Cell Number of Attempts at State Transitions from CELL_DCH (HS-DSCH) to Enhanced CELL_FACH for Cell Number of Successful State Transitions from CELL_PCH or URA_PCH to Enhanced CELL_FACH for Cell Number of Attempts at State Transitions from CELL_PCH or URA_PCH to Enhanced CELL_FACH for Cell
73426154
VS.EFACH.F2H.S ucc
V900R015
73426155
VS.EFACH.F2H.A tt
V900R015
73426156
VS.EFACH.H2F.A tt
V900R015
73426160
VS.EFACH.P2F.Su cc
V900R015
73426159
VS.EFACH.P2F.At t
V900R015
Issue 01 (2013-05-04)
1005
Counter ID 73426158
Counter Name VS.EFACH.F2P.Su cc
Counter Description Number of Successful State Transitions from Enhanced CELL_FACH to CELL_PCH or URA_PCH for Cell Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_PCH or URA_PCH for Cell Maximum Number of UEs on E_FACH for Cell
73426157
VS.EFACH.F2P.At t
V900R015
73426171
VS.EFACHUEs.M ax
V900R015
Counter VS.EFACHUEs Sub Counter VS.EDRXUEs
1.12.8.1 Number of RRC Connection Requests in a Cell (EFACH) Counters

Counter ID 67193111 Counter Name VS.RRC.AttConnEstab.EF ACH Counter Description Number of RRC Establishment Requests on EFACH for Cell
Description
This measurement item provides the number of requests for the RRC connection that the RNC decides to set up on the EFACH in a cell after the RNC receives a RRC CONNECTION REQUEST message from the UE.
Measurement point
The measurement is triggered at point A, as shown in the figure. After the RNC receives a RRC CONNECTION REQUEST message from the UE, it assigns the basic channel resources for the
UE. If the RNC decides that the RRC signaling is established on the EFACH, it measures the item in the cell on which the UE camps. The measurement is triggered for only once if the RNC repeatedly receives the RRC CONNECTION REQUEST message from the UE. Figure 1-425 RRC connection setup success flow
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnEstab.EF ACH Feature ID WRFD-010688 Feature Name Downlink Enhanced CELL_FACH
1.12.8.2 Number of Successful RRC Connection Setups in a Cell (EFACH)
Issue 01 (2013-05-04)
1007
Counters
Counter ID 67193112 Counter Name VS.RRC.SuccConnEstab.EF ACH Counter Description Number of Successful RRC Establishments on EFACH for Cell
Description
This counter provides the number of successful RRC connection setups on the EFACH. Success rate of RRC connection setups on the EFACH = VS.RRC.SuccConnEstab.EFACH/ VS.RRC.AttConnEstab.EFACH
Measurement point
The measurement is triggered at point C, as shown in the figure. After the RNC receives a RRC CONNECTION SETUP COMPLETE message from the UE, it measures the item in the cell on which the UE camps if the RRC signaling is established on the EFACH. Figure 1-426 RRC connection setup success flow
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.SuccConnEstab.EF ACH Feature ID WRFD-010688 Feature Name Downlink Enhanced CELL_FACH
1.12.8.3 Number of PS RAB Setup Attempts on EFACH in a Cell Counters

Counter ID 67193119 Counter Name VS.RAB.AttEstPS.EFACH Counter Description Number of PS RAB Establishment Requests on EFACH for Cell
Description
This counter provides the number of PS RAB setup attempts on the EFACH.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the SGSN, it measures the item in the best cell on which the UE camps when the PS service is established on the EFACH. Figure 1-427 RAB setup procedure (successful operation)
Issue 01 (2013-05-04)
1009
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstPS.EFACH Feature ID WRFD-010688 Feature Name Downlink Enhanced CELL_FACH
1.12.8.4 Number of Successful PS RAB Setup on EFACH in a Cell Counters

Counter ID 67193120 Counter Name VS.RAB.SuccEstPS.EFAC H Counter Description Number of Successful PS RAB Establishments on EFACH for Cell
Description
This counter provides the number of successful PS RAB setups on the EFACH. Success rate of PS RAB setups on the EFACH = VS.RAB.SuccEstPS.EFACH/ VS.RAB.AttEstPS.EFACH
Measurement point
The measurement is triggered at point B, as shown in Figure. When the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE and sends a RAB ASSIGNMENT RESPONSE message to SGSN as a response, it measures the item in the best cell on which the UE camps when the PS service is established on the EFACH.
Issue 01 (2013-05-04)
1010
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstPS.EFAC H Feature ID WRFD-010688 Feature Name Downlink Enhanced CELL_FACH
1.12.8.5 Signaling Delay of PS RAB Established on CCH in a Cell Counters

Counter ID 67193121 Counter Name VS.RAB.Estab.PS.CellFAC H.MaxTime Counter Description Maximum Duration of PS RAB Establishment Process on FACH for Cell
1011
Issue 01 (2013-05-04)
Counter ID 67204169
Counter Name VS.RAB.Estab.PS.CellFAC H.MeanTime
Counter Description Mean Duration of PS RAB Establishment Process on FACH for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67193123 Counter Name VS.RAB.Estab.PS.CellFAC H.Cum VS.RAB.Estab.PS.CellFAC H.Sample Counter Description Accumulative Duration of PS RAB Establishment Process on FACH for Cell Number of Samples of Accumulative Duration of PS RAB Establishment Process on FACH for Cell
67193124
Description
These counters provide the signaling delay of PS RAB setup of the UE in CELL_FACH status.
Measurement point
The measurement is triggered at points A and B, as shown in Figure: At point A, the RNC records the time (T1) when it receives a RAB ASSIGNMENT REQUEST message and decides the PS RAB is set up on the CCH. At point B, the RNC records the time (T2) when it sends a RAB ASSIGNMENT RESPONSE message to the CN after receiving a RADIO BEARER SETUP COMPLETE message. Suppose delta T represents the signaling delay of the RAB connection setup. Then, delta T = T2 - T1 when the RRC connection is set up on the CCH.
Issue 01 (2013-05-04)
1012
Formula
VS.RAB.Estab.PS.CellFACH.MeanTime = [VS.RAB.Estab.PS.CellFACH.Cum]/ [VS.RAB.Estab.PS.CellFACH.Sample]
Unit
ms
Related Features
Counter Name VS.RAB.Estab.PS.CellFAC H.MaxTime VS.RAB.Estab.PS.CellFAC H.MeanTime Feature ID WRFD-010688 WRFD-010688 Feature Name Downlink Enhanced CELL_FACH Downlink Enhanced CELL_FACH
1.12.8.6 Number of Abnormally Released PS RABs on the EFACH in a Cell
Issue 01 (2013-05-04)
1013
Counters
Counter ID 67193127 Counter Name VS.RAB.AbnormRel.PS.EF ACH Counter Description Number of Abnormal RAB Releases on EFACH for Cell
Description
This counter provides the number of abnormally released PS RABs on the EFACH. Success rate of abnormally released RABs on EFACH = VS.RAB.AbnormRel.PS.EFACH/ VS.RAB.NormRel.PS.EFACH
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", reference to 3GPP TS 25.413),the RNC measures the item in the best cell which the UE camps on when the released PS RAB is carried on the EFACH. Figure 1-430 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", reference to 3GPP TS 25.413),the
RNC measures the item in the best cell which the UE camps on when the released PS RAB is carried on the EFACH. Figure 1-431 RAB release IU REL procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", reference to 3GPP TS 25.413),the RNC measures the item in the best cell which the UE camps on when the released PS RAB is carried on the EFACH.
Issue 01 (2013-05-04)
1015
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.EF ACH Feature ID WRFD-010688 Feature Name Downlink Enhanced CELL_FACH
1.12.8.7 Number of Normal Released PS RABs on the EFACH in a Cell Counters

Counter ID 67193128 Counter Name VS.RAB.NormRel.PS.EFA CH Counter Description Number of Normal PS RAB Release on EFACH for Cell
Issue 01 (2013-05-04)
1016
Description
This measurement item provides the number of normally released PS RABs on the EFACH in the cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release", the RNC measures the item in the best cell which the UE camps on when the released PS RAB is carried on the EFACH. Figure 1-433 Iu connection release procedure
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release" or "Successful Relocation","Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release" ,the RNC measures the item in the best cell which the UE camps on when the released PS RAB is carried on the EFACH.
Issue 01 (2013-05-04)
1017
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS.EFA CH Feature ID WRFD-010688 Feature Name Downlink Enhanced CELL_FACH
1.12.8.8 Number of Downlink MAC PDU Bytes on the EFACH over the Iub Interface
Issue 01 (2013-05-04)
1018
Counters
Counter ID 67204778 Counter Name VS.CRNCIubBytesEFACH. Tx Counter Description Number of Bytes of MAC PDUs Sent on IUB EFACH FP for Cell
Description
This measurement counter provides the number of downlink MAC PDU bytes sent by the CRNC on the EFACH over the Iub interface in a cell (including signaling and service data but excluding FP headers).
Measurement point
This counter is measured when the CRNC sends data on the EFACH over the Iub interface. In a measurement period, the bytes of uplink MAC PDUs (including the signaling and service data but not including the FP header) that are received by the CRNC on the EFACH over the Iub interface are accumulated in a cell.
Formula
None
Unit
byte
Related Features
Counter Name VS.CRNCIubBytesEFACH. Tx Feature ID WRFD-010688 Feature Name Downlink Enhanced CELL_FACH
1.12.8.9 Signaling Delay of RRC Established on EFACH in a Cell Counters

Counter ID 73421757 Counter Name VS.RRC.ConnEstabTimeM ax.CellFACH.EFACH Counter Description Maximum Duration of RRC Establishment Process on EFACH for Cell
Issue 01 (2013-05-04)
1019
Counter ID 73439900
Counter Name VS.RRC.ConnEstabTimeM ean.CellFACH.EFACH
Counter Description Mean Duration of RRC Establishment Process on EFACH for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73421758 Counter Name VS.RRC.ConnEstabTime.C CH.HSDSCH.Cum VS.RRC.ConnEstabTime.C CH.HSDSCH.Sample Counter Description Accumulative Duration of RRC Establishment Process on EFACH for Cell Number of Samples of Cumulative Duration of RRC Establishment Process on EFACH for Cell
73421759
Description
These counters provide the average and maximum durations of RRC signaling setups on the EFACH in a cell.
Measurement point
As shown in the figure, when the RNC receives an RRC CONNECTION REQUEST message at point A, it records the time T1. When the RNC receives an RRC CONNECTION SETUP COMPLETE message at point C, it records the time T2. Assume that delta T is the duration of RRC signaling setup on the EFACH in a cell, delta T = T2-T1. The RNC takes samples of the durations of RRC signaling setups on the EFACH every 5 seconds. At the end of a measurement period, the RNC obtains the average duration by dividing the accumulated number by the sampling times. The maximum number in a measurement period is the maximum duration.
Issue 01 (2013-05-04)
1020
Figure 1-435 RRC connection setup success flow
Formula
VS.RRC.ConnEstabTimeMean.CellFACH.EFACH = [VS.RRC.ConnEstabTime.CCH.HSDSCH.Cum]/ [VS.RRC.ConnEstabTime.CCH.HSDSCH.Sample]
Unit
ms
Related Features
Counter Name VS.RRC.ConnEstabTimeM ax.CellFACH.EFACH VS.RRC.ConnEstabTimeM ean.CellFACH.EFACH Feature ID WRFD-010688 WRFD-010688 Feature Name Downlink Enhanced CELL_FACH Downlink Enhanced CELL_FACH
1.12.8.10 Number of UEs Carried on the EFACH or Those Carried on the EFACH and Using E-DRX
Issue 01 (2013-05-04)
1021
Counters
Counter ID 73441122 Counter Name VS.EDRXUEs Counter Description Number of UEs Carried on the EFACH and Using EDRX Number of UEs carried on EFACH for Cell Maximum Number of UEs on E_FACH for Cell
73410512 73426171
VS.EFACHUEs VS.EFACHUEs.Max
Description
These counters provide the average number or maximum number of UEs that are carried on the EFACH, and the average number of UEs that are carried on the EFACH and enabled with the Enhanced Discontinuous Reception (E-DRX) function in a cell.
Measurement point
The number of UEs carried on the EFACH in a cell is sampled every 5 seconds. At the end of a measurement period, the average number of UEs that are carried on the EFACH is calculated by dividing the accumulated number of the UEs measured at each sampling point by the number of samples. The maximum number of UEs that are carried on the EFACH measured at each sampling point is the maximum value obtained in a measurement period. The number of UEs carried on the EFACH and using the E-DRX function in a cell is sampled every 5 seconds. At the end of a measurement period, the average number of UEs that are carried on the EFACH and use the E-DRX function is calculated by dividing the accumulated number of the UEs measured at each sampling point by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name VS.EDRXUEs VS.EFACHUEs VS.EFACHUEs.Max Feature ID WRFD-010702 WRFD-010688 WRFD-010688 Feature Name Enhanced DRX Downlink Enhanced CELL_FACH Downlink Enhanced CELL_FACH
Issue 01 (2013-05-04)
1022
1.12.8.11 Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_DCH (DCH) for Cell Counters
Counter ID 73426149 Counter Name VS.EFACH.F2D.Att Counter Description Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_DCH (DCH) for Cell Number of Attempts at State Transitions from CELL_DCH (DCH) to Enhanced CELL_FACH for Cell
73426150
VS.EFACH.D2F.Att
Description
These counters provide the number of UE state transition attempts from enhanced CELL_FACH (E-DCH) to CELL_DCH (DCH) and from CELL_DCH (DCH) to enhanced CELL_FACH (EDCH) in a cell. Enhanced CELL_FACH refers to that a UE in the CELL_FACH state uses the HS-DSCH in the downlink.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the UE a RADIO BEARER RECONFIGURATION message during a state transition from CELL_DCH (DCH) to enhanced CELL_FACH, this counter is measured in the best cell that the UE camps on before the state transition. When the RNC sends the UE a RADIO BEARER RECONFIGURATION message during a state transition from enhanced CELL_FACH to CELL_DCH (DCH), this counter is measured in the cell that the UE currently camps on.
Issue 01 (2013-05-04)
1023
Formula
None
Unit
None
Related Features
Counter Name VS.EFACH.F2D.Att Feature ID WRFD-021101 WRFD-010688 Feature Name Dynamic Channel Configuration Control (DCCC) Downlink Enhanced CELL_FACH VS.EFACH.D2F.Att WRFD-021101 WRFD-010688 Dynamic Channel Configuration Control (DCCC) Downlink Enhanced CELL_FACH
Issue 01 (2013-05-04)
1024
1.12.8.12 Number of Successful State Transitions from Enhanced CELL_FACH to CELL_DCH (DCH) for Cell Counters
Counter ID 73426151 Counter Name VS.EFACH.F2D.Succ Counter Description Number of Successful State Transitions from Enhanced CELL_FACH to CELL_DCH (DCH) for Cell Number of Successful State Transitions from CELL_DCH (DCH) to Enhanced CELL_FACH for Cell
73426152
VS.EFACH.D2F.Succ
Description
These counters provide the number of UE successful state transitions from enhanced CELL_FACH to CELL_DCH (DCH) and state transitions from CELL_DCH (DCH) to enhanced CELL_FACH in a cell. Enhanced CELL_FACH refers to the state in which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message during a state transition from CELL_DCH (DCH) to enhanced CELL_FACH, this counter is measured in the best cell that the UE camps on before the state transition. When the RNC receives the UE a RADIO BEARER RECONFIGURATION COMPLETE message during a state transition from enhanced CELL_FACH to CELL_DCH (DCH), this counter is measured in the cell that the UE currently camps on.
Issue 01 (2013-05-04)
1025
Formula
None
Unit
None
Related Features
Counter Name VS.EFACH.F2D.Succ Feature ID WRFD-021101 WRFD-010688 Feature Name Dynamic Channel Configuration Control (DCCC) Downlink Enhanced CELL_FACH VS.EFACH.D2F.Succ WRFD-021101 WRFD-010688 Dynamic Channel Configuration Control (DCCC) Downlink Enhanced CELL_FACH
Issue 01 (2013-05-04)
1026
1.12.8.13 Number of Successful State Transitions from Enhanced CELL_FACH to CELL_DCH (HS-DSCH) for Cell Counters
Counter ID 73426154 Counter Name VS.EFACH.F2H.Succ Counter Description Number of Successful State Transitions from Enhanced CELL_FACH to CELL_DCH (HS-DSCH) for Cell Number of Successful State Transitions from CELL_DCH (HS-DSCH) to Enhanced CELL_FACH for Cell
73426153
VS.EFACH.H2F.Succ
Description
These counters provide the number of UE successful state transitions from enhanced CELL_FACH to CELL_DCH (HS-DSCH) and state transitions from CELL_DCH (HS-DSCH) to enhanced CELL_FACH in a cell. Enhanced CELL_FACH refers to the state in which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message during a state transition from CELL_DCH (HS-DSCH) to enhanced CELL_FACH, this counter is measured in the best cell that the UE camps on before the state transition. When the RNC receives the UE a RADIO BEARER RECONFIGURATION COMPLETE message during a state transition from enhanced CELL_FACH to CELL_DCH (HS-DSCH), this counter is measured in the cell that the UE currently camps on.
Issue 01 (2013-05-04)
1027
Formula
None
Unit
None
Related Features
Counter Name VS.EFACH.F2H.Succ Feature ID WRFD-01061111 WRFD-010688 VS.EFACH.H2F.Succ WRFD-01061111 WRFD-010688 Feature Name HSDPA State Transition Downlink Enhanced CELL_FACH HSDPA State Transition Downlink Enhanced CELL_FACH
1.12.8.14 Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_DCH (HS-DSCH) for Cell
Issue 01 (2013-05-04)
1028
Counters
Counter ID 73426155 Counter Name VS.EFACH.F2H.Att Counter Description Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_DCH (HS-DSCH) for Cell Number of Attempts at State Transitions from CELL_DCH (HS-DSCH) to Enhanced CELL_FACH for Cell
73426156
VS.EFACH.H2F.Att
Description
These counters provide the number of UE attempts at state transitions from enhanced CELL_FACH to CELL_DCH (HS-DSCH) and state transitions from CELL_DCH (HS-DSCH) to enhanced CELL_FACH in a cell. Enhanced CELL_FACH refers to the state in which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the UE a RADIO BEARER RECONFIGURATION message during a state transition from CELL_DCH (HS-DSCH) to enhanced CELL_FACH, this counter is measured in the best cell that the UE camps on before the state transition. When the RNC sends the UE a RADIO BEARER RECONFIGURATION message during a state transition from enhanced CELL_FACH to CELL_DCH (HS-DSCH), this counter is measured in the cell that the UE currently camps on. Figure 1-439 RB reconfiguration procedure
Issue 01 (2013-05-04)
1029
Formula
None
Unit
None
Related Features
Counter Name VS.EFACH.F2H.Att Feature ID WRFD-01061111 WRFD-010688 VS.EFACH.H2F.Att WRFD-01061111 WRFD-010688 Feature Name HSDPA State Transition Downlink Enhanced CELL_FACH HSDPA State Transition Downlink Enhanced CELL_FACH
1.12.8.15 Number of Successful State Transitions from CELL_PCH or URA_PCH to Enhanced CELL_FACH for Cell Counters
Counter ID 73426160 Counter Name VS.EFACH.P2F.Succ Counter Description Number of Successful State Transitions from CELL_PCH or URA_PCH to Enhanced CELL_FACH for Cell
Description
This counter provides the number of UE successful state transitions from CELL_PCH or URA_PCH to enhanced CELL_FACH in a cell. Enhanced CELL_FACH refers to the state in which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
When the RNC receives any of the following messages from a UE during a state transition from CELL_PCH or URA_PCH to CELL_FACH, this counter is increased by one in the cell where the UE sends the RNC a CELL UPDATE message: ? UTRAN MOBILITY INFORMATION CONFIRM ? PHYSICAL CHANNEL RECONFIGURATION COMPLETE ? TRANSPORT CHANNEL RECONFIGURATION COMPLETE ? RADIO BEARER RECONFIGURATION COMPLETE The measurement is triggered at point C, as shown in the following figure.
Formula
None
Unit
None
Related Features
Counter Name VS.EFACH.P2F.Succ Feature ID WRFD-010202 WRFD-010688 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Downlink Enhanced CELL_FACH
1.12.8.16 Number of Attempts at State Transitions from CELL_PCH or URA_PCH to Enhanced CELL_FACH for Cell
Issue 01 (2013-05-04)
1031
Counters
Counter ID 73426159 Counter Name VS.EFACH.P2F.Att Counter Description Number of Attempts at State Transitions from CELL_PCH or URA_PCH to Enhanced CELL_FACH for Cell
Description
This counter provides the number of UE attempts at state transitions from CELL_PCH or URA_PCH to enhanced CELL_FACH in a cell. Enhanced CELL_FACH refers to the state in which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
When the RNC sends a UE a CELL UPDATE CONFIRM message during a state transition from CELL_PCH or URA_PCH to enhanced CELL_FACH, this counter is increased by one in the cell where the UE sends the RNC a CELL UPDATE message. The measurement is triggered at point B, as shown in the following figure. Figure 1-441 cell update
Formula
None
Unit
None
Related Features
Counter Name VS.EFACH.P2F.Att Feature ID WRFD-010202 WRFD-010688 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Downlink Enhanced CELL_FACH
1.12.8.17 Number of Successful State Transitions from Enhanced CELL_FACH to CELL_PCH or URA_PCH for Cell Counters
Counter ID 73426158 Counter Name VS.EFACH.F2P.Succ Counter Description Number of Successful State Transitions from Enhanced CELL_FACH to CELL_PCH or URA_PCH for Cell
Description
This counter provides the number of UE successful state transitions from enhanced CELL_FACH to CELL_PCH or URA_PCH in a cell. Enhanced CELL_FACH refers to the state in which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
When the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from a UE during a state transition from enhanced CELL_FACH to CELL_PCH or URA_PCH, this counter is increased by one in the serving cell where the UE camps. The measurement is triggered at point B, as shown in the following figure.
Issue 01 (2013-05-04)
1033
Formula
None
Unit
None
Related Features
Counter Name VS.EFACH.F2P.Succ Feature ID WRFD-010202 WRFD-010688 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Downlink Enhanced CELL_FACH
1.12.8.18 Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_PCH or URA_PCH for Cell
Issue 01 (2013-05-04)
1034
Counters
Counter ID 73426157 Counter Name VS.EFACH.F2P.Att Counter Description Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_PCH or URA_PCH for Cell
Description
This counter provides the number of UE attempts at state transitions from enhanced CELL_FACH to CELL_PCH or URA_PCH in a cell. Enhanced CELL_FACH refers to the state in which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
When the RNC sends a UE a RADIO BEARER RECONFIGURATION message during a state transition from enhanced CELL_FACH to CELL_PCH or URA_PCH, this counter is increased by one in the best cell where the UE camps. The measurement is triggered at point A, as shown in the following figure. Figure 1-443 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.EFACH.F2P.Att Feature ID WRFD-010202 WRFD-010688 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Downlink Enhanced CELL_FACH
1.12.9 EPCH Measurement per cell(EPCH.Cell)

Overview
UEs in the E-PCH state are those in the CELL_PCH or URA_PCH state and use the HS-DSCH for downlink transmission. The EPCH feature is introduced in 3GPP R7. It allows the PCCH to be mapped to the HS-DSCH for UEs in the CELL_PCH or URA_PCH state and therefore enables transmission on the HSDSCH. It also allows the DCCH/DTCH to be mapped to the HS-DSCH for UEs in the CELL_PCH state and therefore enables data transmission on the HS-DSCH. In this way, downlink peak rate is increased and delay in signaling interaction is reduced.
Counters
Counter ID 73441131 Counter Name VS.EPCHUEs Counter Description Average Number of UEs Carried on the EPCH for Cell Average Number of UEs Carried on the EPCH and Allocated Dedicated H-RNTI for Cell Original Release V900R013
73441132
VS.EPCHUEs.DH RNTI
V900R013
Counter VS.EPCHUEs Sub Counter VS.EPCHUEs.DHRNTI
Issue 01 (2013-05-04)
1036
1.12.9.1 Average Number of UEs Carried on the EPCH or Those Carried on the EPCH and Allocated Dedicated H-RNTI for Cell Counters
Counter ID 73441131 73441132 Counter Name VS.EPCHUEs VS.EPCHUEs.DHRNTI Counter Description Average Number of UEs Carried on the EPCH for Cell Average Number of UEs Carried on the EPCH and Allocated Dedicated HRNTI for Cell
Description
These counters provide the average number of UEs in the CELL_PCH state and carried on EPCH and the average number of those carried on the E-PCH and allocated dedicated HS-DSCH Radio Network Temporary Identifier (H-RNTI) in a cell.
Measurement point
The number of UEs in the CELL_PCH state and carried on the E-PCH is sampled every 5 seconds. At the end of a measurement period, this counter is calculated by dividing the accumulated number of the UEs measured at each sampling point by the number of samples. The number of UEs in the CELL_PCH state and carried on the E-PCH and allocated dedicated H-RNTI are sampled every 5 seconds. At the end of a measurement period, this counter is calculated by dividing the accumulated number of the UEs measured at each sampling point by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name VS.EPCHUEs VS.EPCHUEs.DHRNTI Feature ID WRFD-020134 WRFD-020134 Feature Name Push to Talk Push to Talk
Issue 01 (2013-05-04)
1037
1.12.10 ERACH Measurement per cell(ERACH.Cell)

Overview
In ERACH mode, UEs in CELL_FACH state use the E-DCH as the uplink transport channel and use the HS-DSCH as the downlink transport channel. The ERACH feature is introduced in R8. The E-DCH carries message data, replacing the traditional RACH for a higher uplink peak rate. In this way, delay of UEs in the IDLE mode or in the CELL_FACH, CELL_PCH, or URA_PCH state on the user plane and control plane is reduced and delay in transition from the CELL_FACH, CELL_PCH, or URA_PCH state to the CELL_DCH state is reduced.
Counters
Counter ID 73441118 Counter Name VS.ERACHUEs Counter Description Number of UEs Carried on ERACH for Cell Number of Requests for Setting Up RRC Connections on an ERACH for Cell Number of Successful RRC Connection Setups on an ERACH for Cell Number of PS RAB Setup Requests on an ERACH for Cell Number of Successful PS RAB Setups on an ERACH for Cell Number of PS RABs Normally Released on an ERACH for Cell Number of PS RABs Abnormally Released on an ERACH for Cell Original Release V900R013
73423340
VS.RRC.AttConnE stab.ERACH
V900R013
73423341
VS.RRC.SuccConn Estab.ERACH
V900R013
73423342
VS.RAB.AttEstabP S.ERACH VS.RAB.SuccEstab PS.ERACH
V900R013
73423343
V900R013
73423344
VS.RAB.NormRel. PS.ERACH
V900R013
73423345
VS.RAB.AbnormR el.PS.ERACH
V900R013
Issue 01 (2013-05-04)
1038
Counter ID 73423346
Counter Name VS.RRC.ConnEsta bTimeMax.ERAC H VS.RRC.ConnEsta bTimeMean.ERAC H VS.CRNCIubBytes ERACH.Rx VS.ERACH.E2F.S ucc
Counter Description Maximum RRC Connection Setup Duration on an ERACH for Cell Average RRC Connection Setup Duration on an ERACH for Cell Number of Bytes over Iub ERACH for Cell Number of Successful State Transitions from CELL_DCH (EDCH) to Enhanced CELL_FACH (EDCH) for Cell Number of Successful State Transitions from Enhanced CELL_FACH (EDCH) to CELL_DCH (EDCH) for Cell Number of Attempts at State Transitions from CELL_DCH (E-DCH) to Enhanced CELL_FACH (EDCH) for Cell Number of Attempts at State Transition from Enhanced CELL_FACH (EDCH) to CELL_DCH (EDCH) for Cell Maximum Number of UEs on E_RACH for Cell
73441135
V900R013
73441170
V900R013
73426161
V900R015
73426162
VS.ERACH.F2E.S ucc
V900R015
73426163
VS.ERACH.E2F.A tt
V900R015
73426164
VS.ERACH.F2E.A tt
V900R015
73426172
VS.ERACHUEs.M ax
V900R015
Issue 01 (2013-05-04)
1039
None
1.12.10.1 Number of UEs Carried on ERACH for Cell Counters

Counter ID 73441118 73426172 Counter Name VS.ERACHUEs VS.ERACHUEs.Max Counter Description Number of UEs Carried on ERACH for Cell Maximum Number of UEs on E_RACH for Cell
Description
These counters provide the average and maximum numbers of UEs that are carried on the ERACH in a cell.
Measurement point
The RNC takes a sample from the number of UEs carried on the ERACH in a cell every 5s. At the end of the measurement period, the RNC obtains the value of VS.ERACHUEs in the measurement period by dividing the accumulated number of the UEs by the number of samples and the RNC takes the maximum sampling number as the value of VS.ERACHUEs.Max.
Formula
None
Unit
None
Related Features
Counter Name VS.ERACHUEs VS.ERACHUEs.Max Feature ID WRFD-010701 WRFD-010701 Feature Name Uplink Enhanced CELL_FACH Uplink Enhanced CELL_FACH
1.12.10.2 Number of Requests for Setting Up RRC Connections on an ERACH for Cell
Counters
Counter ID 73423340 Counter Name VS.RRC.AttConnEstab.ER ACH Counter Description Number of Requests for Setting Up RRC Connections on an ERACH for Cell
Description
This counter provides the number of requests for setting up an RRC connection on the ERACH.
Measurement point
The measurement is triggered at point A shown in the following figure. After receiving an RRC CONNECTION REQUEST message from a UE, the RNC allocates channel resources to the RRC connection. If the RNC determines that the RRC signaling be setup on an ERACH, this counter is measured in the cell where the UE camps. This counter is measured only once if the RNC receives multiple RRC CONNECTION REQUEST messages repeatedly from a UE. Figure 1-444 RRC connection setup success flow
Formula
None
Issue 01 (2013-05-04)
1041
Unit
None
Related Features
Counter Name VS.RRC.AttConnEstab.ER ACH Feature ID WRFD-010701 Feature Name Uplink Enhanced CELL_FACH
1.12.10.3 Number of Successful RRC Connection Setups on an ERACH for Cell Counters
Counter ID 73423341 Counter Name VS.RRC.SuccConnEstab.E RACH Counter Description Number of Successful RRC Connection Setups on an ERACH for Cell
Description
This counter provides the number of times that an RRC connection is set up successfully on the ERACH. Together with "Number of Requests for Setting Up RRC Connections on ERACHs for Cell", this counter reflects the RRC setup success rate on the ERACH. The formula is as follows: RRC setup success rate on the ERACH = VS.RRC.SuccConnEstab.ERACH/ VS.RRC.AttConnEstab.ERACH.
Measurement point
The measurement is triggered at point C shown in the following figure. After receiving an RRC CONNECTION SETUP COMPLETE message from an UE, the RNC measures this counter if the RRC connection is set up on an ERACH.
Issue 01 (2013-05-04)
1042
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.SuccConnEstab.E RACH Feature ID WRFD-010701 Feature Name Uplink Enhanced CELL_FACH
1.12.10.4 Number of PS RAB Setup Requests on an ERACH for Cell Counters

Counter ID 73423342 Counter Name VS.RAB.AttEstabPS.ERAC H Counter Description Number of PS RAB Setup Requests on an ERACH for Cell
Issue 01 (2013-05-04)
1043
Description
This counter provides the number of requests for setting up a PS RAB on the ERACH in a cell.
Measurement point
The measurement is triggered at point A shown in the following figure. When the RNC receives from the CN an RAB ASSIGNMENT REQUEST message, the counter is measured in the cell that the UE camps on if the request is for setting up a PS RAB on an ERACH. Figure 1-446 RAB setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabPS.ERAC H Feature ID WRFD-010701 Feature Name Uplink Enhanced CELL_FACH
Issue 01 (2013-05-04)
1044
1.12.10.5 Number of Successful PS RAB Setups on an ERACH for Cell Counters

Counter ID 73423343 Counter Name VS.RAB.SuccEstabPS.ERA CH Counter Description Number of Successful PS RAB Setups on an ERACH for Cell
Description
This counter provides the number of times that a PS RAB is successfully set up on the ERACH in a cell. Together with "Number of PS RAB Setup Requests on ERACH for Cell", this counter reflects the PS RAB setup success rate on the ERACH. The formula is as follows: PS RAB setup success rate = VS.RAB.SuccEstabPS.ERACH/VS.RAB.AttEstabPS.ERACH .
Measurement point
The measurement is triggered at point B shown in the following figure. When the RNC sends the CN an RAB ASSIGNMENT RESPONSE message after receiving from the UE a RADIO BEARER SETUP COMPLETE message, it measures the counter in the cell that the UE camps on if the PS RAB is set up on an ERACH. Figure 1-447 RAB setup procedure (successful operation)
Issue 01 (2013-05-04)
1045
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstabPS.ERA CH Feature ID WRFD-010701 Feature Name Uplink Enhanced CELL_FACH
1.12.10.6 Number of PS RABs Normally Released on an ERACH for Cell Counters

Counter ID 73423344 Counter Name VS.RAB.NormRel.PS.ERA CH Counter Description Number of PS RABs Normally Released on an ERACH for Cell
Description
This counter provides the number of times that a PS RAB is normally released on the ERACH in a cell.
Measurement point
The measurement is triggered at point A in the figure. After receiving from the CN an IU RELEASE COMMAND message, the RNC releases the corresponding RAB, and then sends the CN an IU RELEASE COMPLETE message. If the release cause in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", or if the RNC has sent a release request with the cause of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before the RNC receives the IU RELEASE COMMAND message and the RAB to be released is a PS RAB carried on an ERACH, then the counter is measured in the cell that the UE camps on.
Issue 01 (2013-05-04)
1046
The measurement is triggered at point B in the following figure. After receiving an RAB ASSIGNMENT REQUEST message with an RAB release request from the CN, the RNC releases the corresponding RAB and then sends an RAB ASSIGNMENT RESPONSE message to the CN. If the release cause in the RAB ASSIGNMENT REQUEST message is "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", or if the RNC has sent a release request with the cause of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before the RNC receives the IU RELEASE COMMAND message and the RAB to be released is a PS RAB carried on an ERACH, then the counter is measured in the cell that the UE camps on.
Issue 01 (2013-05-04)
1047
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS.ERA CH Feature ID WRFD-010701 Feature Name Uplink Enhanced CELL_FACH
1.12.10.7 Number of PS RABs Abnormally Released on an ERACH for Cell
Issue 01 (2013-05-04)
1048
Counters
Counter ID 73423345 Counter Name VS.RAB.AbnormRel.PS.ER ACH Counter Description Number of PS RABs Abnormally Released on an ERACH for Cell
Description
This counter provides the number of times that a PS RAB is abnormally released on the ERACH in a cell. Together with "Number of PS RABs Normally Released on the ERACH for Cell", this counter reflects the ratio of abnormal PS RAB releases on ERACHs. The formula is as follows: Ratio of abnormal PS RAB releases on the ERACH = VS.RAB.AbnormRel.PS.ERACH/ VS.RAB.NormRel.PS.ERACH .
Measurement point
As shown by point A in the following figure, when an abnormal release occurs, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an RAB ASSIGNMENT REQUEST message which contains a cause value of the abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413) and the RAB to be released is a PS RAB carried on an ERACH, then this counter is measured in the cell that the UE camps on. Figure 1-450 RAB release procedure
As shown by point A in the following figure, when an abnormal release occurs, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an IU
RELEASE COMMAND message which contains a cause value of the abnormal release (causes except "User Inactivity," "Normal Release," "Successful Relocation," or "Network Optimization," for details, see 3GPP TS 25.413) and the RAB to be released is a PS RAB carried on an ERACH, then this counter is measured in the cell that the UE camps on. Figure 1-451 RAB release IU REL procedure
As shown by point A in the following figure, when an abnormal release occurs, the RNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of the abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413) and the RAB to be released is a PS RAB carried on an ERACH, then this counter is measured in the cell that the UE camps on.
Issue 01 (2013-05-04)
1050
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.ER ACH Feature ID WRFD-010701 Feature Name Uplink Enhanced CELL_FACH
1.12.10.8 RRC Connection Setup Duration on an ERACH for Cell Counters

Counter ID 73423346 Counter Name VS.RRC.ConnEstabTimeM ax.ERACH Counter Description Maximum RRC Connection Setup Duration on an ERACH for Cell
1051
Issue 01 (2013-05-04)
Counter ID 73441135
Counter Name VS.RRC.ConnEstabTimeM ean.ERACH
Counter Description Average RRC Connection Setup Duration on an ERACH for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73423347 Counter Name VS.RRC.ConnEstabTime.C CH.ERACH.Cum VS.RRC.ConnEstabTime.C CH.ERACH.Sample Counter Description Accumulative Duration of RRC Establishment Process on ERACH for Cell Number of Samples of Cumulative Duration of RRC Establishment Process on ERACH for Cell
73423348
Description
These counters provide the maximum and average durations taken by an RRC connection setup on the ERACH in a cell.
Measurement point
As shown in the figure, when the RNC receives an RRC CONNECTION REQUEST message at point A, the time is recorded as T1. When the RNC receives an RRC CONNECTION SETUP COMPLETE message at point C, the time is recorded as T2. The RNC uses delta T = T2-T1 as the RRC connection setup duration on the ERACH if the RRC connection is set up on the ERACH. The RNC takes a sample from durations taken by an RRC connection setup on the ERACH every 5s. At the end of the measurement period, the RNC obtains the value of VS.RRC.ConnEstabTimeMean.ERACH for Cell by dividing the accumulated numbers by the number of samples. In addition, the RNC takes the maximum sampling number as the value of VS.RRC.ConnEstabTimeMax.ERACH.
Issue 01 (2013-05-04)
1052
Formula
VS.RRC.ConnEstabTimeMean.ERACH = [VS.RRC.ConnEstabTime.CCH.ERACH.Cum]/ [VS.RRC.ConnEstabTime.CCH.ERACH.Sample]
Unit
ms
Related Features
Counter Name VS.RRC.ConnEstabTimeM ax.ERACH VS.RRC.ConnEstabTimeM ean.ERACH Feature ID WRFD-010701 WRFD-010701 Feature Name Uplink Enhanced CELL_FACH Uplink Enhanced CELL_FACH
1.12.10.9 Traffic over ERACH on Iub Interface
Issue 01 (2013-05-04)
1053
Counters
Counter ID 73441170 Counter Name VS.CRNCIubBytesERACH. Rx Counter Description Number of Bytes over Iub ERACH for Cell
Description
This counter provides the bytes of UL MAC PDUs (including the signaling data and the service data, not including the FP header) received by the CRNC over the ERACH FP on the Iub interface.
Measurement point
The measurement is triggered when the CRNC sends UL data over the ERACH FP on the Iub interface. At the end of the measurement period, the bytes of UL data over the ERACH FP are accumulated to obtain the bytes of UL MAC PDUs (including the signaling data and the service data, not including the FP header) received by the CRNC over the ERACH FP on the Iub interface.
Formula
None
Unit
byte
Related Features
Counter Name VS.CRNCIubBytesERACH. Rx Feature ID WRFD-010701 Feature Name Uplink Enhanced CELL_FACH
1.12.10.10 Number of Successful State Transitions from CELL_DCH (E-DCH) to Enhanced CELL_FACH (E-DCH) for Cell Counters
Counter ID 73426161 Counter Name VS.ERACH.E2F.Succ Counter Description Number of Successful State Transitions from CELL_DCH (E-DCH) to Enhanced CELL_FACH (EDCH) for Cell
1054
Issue 01 (2013-05-04)
Counter ID 73426162
Counter Name VS.ERACH.F2E.Succ
Counter Description Number of Successful State Transitions from Enhanced CELL_FACH (E-DCH) to CELL_DCH (E-DCH) for Cell
Description
These counters provide the number of successful state transitions from enhanced CELL_FACH (E-DCH) to CELL_DCH (E-DCH) and state transitions from CELL_DCH (E-DCH) to enhanced CELL_FACH (E-DCH). Enhanced CELL_FACH (E-DCH) refers to the state in which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink and E-DCHs in the uplink.
Measurement point
When the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from a UE during a state transition from CELL_DCH (E-DCH) to enhanced CELL_FACH (EDCH), VS.ERACH.E2F.Succ is increased by one in the serving cell where the UE camps before the state transition. If the state transition is from enhanced CELL_FACH (E-DCH) to CELL_DCH (E-DCH), VS.ERACH.F2E.Succ is increased by one in the cell where the UE now camps. The measurement is triggered at point B, as shown in the following figure. Figure 1-454 RB reconfiguration procedure
Issue 01 (2013-05-04)
1055
Formula
None
Unit
None
Related Features
Counter Name VS.ERACH.E2F.Succ Feature ID WRFD-01061208 WRFD-010701 VS.ERACH.F2E.Succ WRFD-01061208 WRFD-010701 Feature Name HSUPA DCCC Uplink Enhanced CELL_FACH HSUPA DCCC Uplink Enhanced CELL_FACH
1.12.10.11 Number of Attempts at State Transitions from CELL_DCH (E-DCH) to Enhanced CELL_FACH (E-DCH) for Cell Counters
Counter ID 73426163 Counter Name VS.ERACH.E2F.Att Counter Description Number of Attempts at State Transitions from CELL_DCH (E-DCH) to Enhanced CELL_FACH (EDCH) for Cell Number of Attempts at State Transition from Enhanced CELL_FACH (E-DCH) to CELL_DCH (E-DCH) for Cell
73426164
VS.ERACH.F2E.Att
Description
These counters provide the number of attempts at state transitions from enhanced CELL_FACH (E-DCH) to CELL_DCH (E-DCH) and state transitions from CELL_DCH (E-DCH) to enhanced CELL_FACH (E-DCH). Enhanced CELL_FACH (E-DCH) refers to the state in which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink and E-DCHs in the uplink.
Measurement point
When the RNC sends a UE a RADIO BEARER RECONFIGURATION message during a state transition from CELL_DCH (E-DCH) to enhanced CELL_FACH (E-DCH),
VS.ERACH.E2F.Att is increased by one in the serving cell where the UE camps before the state transition. If the state transition is from enhanced CELL_FACH (E-DCH) to CELL_DCH (EDCH), VS.ERACH.F2E.Att is increased by one in the cell where the UE now camps. The measurement is triggered at point A, as shown in the following figure. Figure 1-455 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.ERACH.E2F.Att Feature ID WRFD-01061208 WRFD-010701 VS.ERACH.F2E.Att WRFD-01061208 WRFD-010701 Feature Name HSUPA DCCC Uplink Enhanced CELL_FACH HSUPA DCCC Uplink Enhanced CELL_FACH
Issue 01 (2013-05-04)
1057
1.12.11 Hard Handover Measurement per cell(HHO.Cell)

Overview
This function subset provides measurements on messages involved in hard handovers on a cell basis. Hard handover is a handover procedure in which all the existing radio links connected to a UE are released before a new one is set up. That is, communications on the existing radio links are interrupted, and then communications on the new radio link are established. Therefore, the performance of hard handover is not as good as that of soft handover. In most cases, hard handover is triggered by coverage, QoS, HCS, LDR, and CLB algorithm. Hard handover can be classified into intra-frequency hard handover and inter-frequency hard handover. Intra-frequency hard handover: In this mode, the cells that the UE camps on before and after the handover use the same frequency. The intra-frequency hard handover can be performed only when soft handover is not available. Inter-frequency hard handover: In this mode, the cells that the UE camps on before and after the handover use different frequencies. In addition, the inter-band hard handover are included in the inter-frequency hard handover. Inter-frequency hard handover can balance the loads and implement seamless connection between different TRXs. Generally, before an inter-frequency hard handover, the UE requires compressed mode configurations to perform an inter-frequency measurement according to its capability. The decision of inter-frequency hard handover is mainly based on inter-frequency measurement reports. When deciding to perform a hard handover, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message, TRANSPORT CHANNEL RECONFIGURATION message, RADIO BEARER RECONFIGURATION message, RADIO BEARER SETUP message, or RADIO BEARER RELEASE message to the UE for response. If the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message, TRANSPORT CHANNEL RECONFIGURATION COMPLETE message, RADIO BEARER RECONFIGURATION COMPLETE message, RADIO BEARER SETUP COMPLETE message, or RADIO BEARER RELEASE COMPLETE message from the UE in the target cell, the hard handover succeeds. If the RNC receives the PHYSICAL CHANNEL RECONFIGURATION FAILURE message, TRANSPORT CHANNEL RECONFIGURATION FAILURE message, RADIO BEARER RECONFIGURATION FAILURE message, RADIO BEARER SETUP FAILURE message, or RADIO BEARER RELEASE FAILURE message in the source cell during the hard handover or the RNC does not receive the response message from the UE before the timer expires, the hard handover fails. The relocation with hard handover has the same procedure. The following figure shows the related procedure. Hard Handover Measurement per cell(HHO Cell) provides measurements on the messages involved in hard handovers from the view of cell. This function subset consists of measurements on incoming hard handovers and outgoing hard handovers. The measurement of incoming hard handover is triggered in the target cell, whereas the measurement of outgoing hard handover is triggered in the best cell before hard handover. If the RNC triggers hard handovers for UEs processing combined services, the measurement is triggered by counters that do not differentiate services. The measurement is also triggered by counters that differentiate services based on the RAB numbers for each type of services. For example, if the RNC triggers inter-RNC inter-frequency hard handovers for UEs processing combined services, the measurement is triggered by the VS.HHO.SuccInterFreqOut.InterRNC counter. The measurement is also triggered by the VS.HHO.SuccInterFreqOut.CS and VS.HHO.SuccInterFreqOut.PS counters based on the RB numbers occupied by CS and PS services, respectively.
Figure 1-456 Flow chart of hard handover and hard handover with relocation
Table 1 describes the measurement points shown in Figure1. Measurement points A B C Description VS.HHO.EvalOut,VS.HHO.EvalIn VS.HHO.AttInterFreqIn ,VS.HHO.AttInterFreqOut VS.HHO.AttIntraFreqOut.IntraNodeB,VS. HHO.AttInterFreqOut.IntraNodeB
Issue 01 (2013-05-04)
1059
Measurement points D E
Description VS.HHO.SuccIntraFreqOut.IntraNodeB,VS. HHO.SuccInterFreqOut.IntraNodeB VS.HHO.AttIntraFreqOut.InterNodeBIntra RNC,VS.HHO.AttInterFreqOut.InterNodeBIntraRNC VS.HHO.SuccIntraFreqOut.InterNodeBIntr aRNC,VS.HHO.SuccInterFreqOut.InterNodeBIntraRNC VS.HHO.AttIntraFreqOut.InterRNC,VS.HH O.AttInterFreqOut.InterRNC VS.HHO.SuccIntraFreqOut.InterRNC,VS.H HO.SuccInterFreqOut.InterRNC VS.HHO.SuccInterFreqOut ,VS.HHO.SuccInterFreqOut VS.HHO.FailIntraFreqOut.InterRNC.CfgU nsupp ,VS.HHO.FailInterFreqOut.InterRNC .CfgUnsupp ,VS.HHO.FailIntraFreqOut.Inte rRNC.NoReply, VS.HHO.FailInterFreqOut.InterRNC.NoReply VS.HHO.FailIntraFreqOut.CfgUnsupp,VS. HHO.FailInterFreqOut.CfgUnsupp,VS.HH O.FailIntraFreqOut.NoReply,VS.HHO.FailI nterFreqOut.NoReply VS.HHO.FailIntraFreqOut.RLSetupFail,VS. HHO.FailInterFreqOut.RLSetupFail VS.HHO.FailIntraFreqOut.PrepFail,VS.HH O.FailInterFreqOut.PrepFail VS.HHO.AttIntraFreqRelocPrep,VS.HHO. AttInterFreqRelocPrep VS.HHO.SuccIntraFreqRelocPrep,VS.HHO .SuccInterFreqRelocPrep VS.HHO.AttIntraFreqRelocExec,VS.HHO. AttInterFreqRelocExec VS.HHO.SuccIntraFreqRelocExec,VS.HH O.SuccInterFreqRelocExec HHO.FailRelocPrepOut.NoResAvail,HHO. FailRelocPrepOut.Texp
G H I J
L M N O P Q R
Issue 01 (2013-05-04)
1060
Measurement points *
Description The RL establishment consists of the RL establishment on the Iub interface and RL establishment on the Iur interface. In the reconfiguration procedure, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION, TRANSPORT CHANNEL RECONFIGURATION, RADIO BEARER RECONFIGURATION, RADIO BEARER SETUP, or RADIO BEARER RELEASE message to the UE. The procedure shown in the figure takes the PHYSICAL CHANNEL RECONFIGURATION message as an example. The cause value of normal releases is "Successful Relocation", "Normal Release", or "Network Optimization."
**
***
Counters
Counter ID 67180565 Counter Name VS.HHO.AttIn Counter Description Number of Incoming Hard Handover Attempts for Cell Number of Successful Incoming Hard Handovers in the RNC for Cell Number of Relocation Preparation Attempts with Outgoing IntraFrequency Hard Handovers for Cell Number of Successful Relocation Preparations with Outgoing IntraFrequency Hard Handovers for Cell Original Release Earlier than V900R011 Earlier than V900R011
67180566
VS.HHO.SuccIn
67193708
VS.HHO.AttIntraFreqRelocPrep
67192770
VS.HHO.SuccIntraFreqRelocPrep
Issue 01 (2013-05-04)
1061
Counter ID 67192551
Counter Name VS.HHO.AttInterFreqRelocPrep
Counter Description Number of Relocation Preparation Attempts with Outgoing InterFrequency Hard Handovers for Cell Number of Successful Relocation Preparations with Outgoing InterFrequency Hard Handovers for Cell Number of Failed Outgoing IntraFrequency Hard Handovers Due to No Response from the UE for Cell Number of Failed Preparations for Outgoing IntraFrequency Hard Handovers for Cell Number of Failed Preparations for Outgoing InterFrequency Hard Handovers for Cell Number of Failed Preparations for Outgoing IntraFrequency Hard Handovers Due to Radio Link Establishment Failure for Cell
67192552
VS.HHO.SuccInterFreqRelocPrep
67192553
VS.HHO.FailIntra FreqOut.NoReply
67192554
VS.HHO.FailIntra FreqOut.PrepFail
67192555
VS.HHO.FailInter FreqOut.PrepFail
67192556
VS.HHO.FailIntra FreqOut.RLSetupFail
Issue 01 (2013-05-04)
1062
Counter ID 67192557
Counter Name VS.HHO.FailInter FreqOut.RLSetupFail
Counter Description Number of Failed Preparations for Outgoing InterFrequency Hard Handovers Due to Radio Link Establishment Failure for Cell Number of Failed Outgoing IntraFrequency Hard Handovers for Cell (Invalid Configuration) Number of Failed Outgoing IntraFrequency Hard Handovers for Cell (Configuration Unsupported) Number of Failed Outgoing IntraFrequency Hard Handovers for Cell (Physical Channel Failure) Number of Failed Outgoing IntraFrequency Hard Handovers for Cell (Incompatible Simultaneous Reconfiguration) Number of Failed Outgoing IntraFrequency Hard Handovers for Cell (Cell Update Occurred) Number of CS Outgoing Inter-Band Hard Handover Attempts for Cell
67192614
VS.HHO.FailIntra FreqOut.InvCfg
67192558
VS.HHO.FailIntra FreqOut.CfgUnsupp
67192559
VS.HHO.FailIntra FreqOut.PyhChFail
67192560
VS.HHO.FailIntra FreqOut.ISR
67192561
VS.HHO.FailIntra FreqOut.CellUpdt
67193565
VS.HHO.AttMulti BandOut.CS
Issue 01 (2013-05-04)
1063
Counter ID 67193566
Counter Name VS.HHO.SuccMult iBandOut.CS
Counter Description Number of Successful CS Outgoing Inter-Band Hard Handovers for Cell Number of PS Outgoing Inter-Band Hard Handover Attempts for Cell Number of Successful PS Outgoing Inter-Band Hard Handovers for Cell Number of Outgoing Intra-Frequency Hard Handover Attempts in NodeB for Cell Number of Successful Outgoing Intra-Frequency Hard Handovers in NodeB for Cell Number of Outgoing Intra-Frequency Hard Handover Attempts Between Different NodeBs of RNC for Cell Number of Successful Outgoing Intra-Frequency Hard Handovers Between Different NodeBs of RNC for Cell Number of Outgoing Intra-Frequency Hard Handover Attempts Between RNCs for Cell
67192567
VS.HHO.AttMulti BandOut.PS
67192568
VS.HHO.SuccMult iBandOut.PS
67180585
VS.HHO.AttIntraF reqOut.IntraNodeB
67180586
VS.HHO.SuccIntra FreqOut.IntraNodeB
67180587
VS.HHO.AttIntraF reqOut.InterNodeBIntraRNC
67180588
VS.HHO.SuccIntra FreqOut.InterNodeBIntraRNC
67180589
VS.HHO.AttIntraF reqOut.InterRNC
Issue 01 (2013-05-04)
1064
Counter ID 67180590
Counter Name VS.HHO.SuccIntra FreqOut.InterRNC
Counter Description Number of Successful Outgoing Intra-Frequency Hard Handovers Between RNCs for Cell Number of Failed Outgoing IntraFrequency Hard Handovers Between RNCs for Cell (Configuration Unsupported) Number of Failed Outgoing IntraFrequency Hard Handovers Between RNCs for Cell (Physical Channel Failure) Number of Failed Outgoing IntraFrequency Hard Handovers Between RNCs for Cell (Incompatible Simultaneous Reconfiguration) Number of Failed Outgoing IntraFrequency Hard Handovers Between RNCs for Cell (Invalid Configuration) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (No Radio Resources Available in Target Cell)
67189701
VS.HHO.FailIntra FreqOut.InterRNC .CfgUnsupp
67189702
VS.HHO.FailIntra FreqOut.InterRNC .PhyChFail
67189703
VS.HHO.FailIntra FreqOut.InterRNC .ISR
67189704
VS.HHO.FailIntra FreqOut.InterRNC .InvCfg
67189708
HHO.FailRelocPre pOut.NoResAvail
Issue 01 (2013-05-04)
1065
Counter ID 67189709
Counter Name HHO.FailRelocPre pOut.Texp
Counter Description Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (TRELOCalloc Expiry) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (Relocation Failure in Target CN/RNC or Target System) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (Relocation Not Supported in Target RNC or Target System) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (Relocation Target Not Allowed) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (O&M Intervention) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (No Resource Available)
67189710
HHO.FailRelocPre pOut.TgtFail
67189711
HHO.FailRelocPre pOut.RelocUnsupp
67189712
HHO.FailRelocPre pOut.TgtNotAllow
67189713
HHO.FailRelocPre pOut.OM
67189714
HHO.FailRelocPre pOut.ResUnavail
Issue 01 (2013-05-04)
1066
Counter ID 67189715
Counter Name HHO.FailRelocPre pOut.Unspec
Counter Description Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (Unspecified Failure) Number of Relocation Execution Attempts with Outgoing IntraFrequency Hard Handovers for Cell Number of Successful Relocation Executions with Outgoing IntraFrequency Hard Handovers for Cell Number of Decisions for Outgoing Hard Handovers for Cell Number of Decisions for Incoming Hard Handovers for Cell Number of Decisions for Outgoing InterFrequency Hard Handovers in Compressed Mode for Cell Number of Decisions for Incoming InterFrequency Hard Handovers in Compressed Mode for Cell Number of Outgoing Inter-Frequency Hard Handover Attempts Due to Load Balancing for Cell (Single RL)
67189716
VS.HHO.AttIntraFreqRelocExec
67189717
VS.HHO.SuccIntraFreqRelocExec
67189722
VS.HHO.EvalOut
67189723
VS.HHO.EvalIn
67180551
VS.HHO.InterFreq Out.Eval.CM
67180570
VS.HHO.InterFreq In.Eval.CM
67180549
VS.HHO.AttInterC ellLB.SingleRL
Issue 01 (2013-05-04)
1067
Counter ID 67180550
Counter Name VS.HHO.SuccInter CellLB.SingleRL
Counter Description Number of Successful Outgoing Inter-Frequency Hard Handovers Due to Load Balancing for Cell (Single RL) Number of Outgoing Inter-Frequency Hard Handover Attempts Due to Load Balancing for Cell (Multiple RLs) Number of Successful Outgoing Inter-Frequency Hard Handovers Due to Load Balancing for Cell (Multiple RLs) Number of Outgoing Inter-Frequency Hard Handover Attempts for Cell Number of Successful Outgoing Inter-Frequency Hard Handovers for Cell Number of Failed Outgoing InterFrequency Hard Handovers for Cell (Configuration Unsupported) Number of Failed Outgoing InterFrequency Hard Handovers for Cell (Physical Channel Failure)
67193709
VS.HHO.AttInterC ellLB.MultiRL
67193710
VS.HHO.SuccInter CellLB.MultiRL
67183900
VS.HHO.AttInterFreqOut
67183901
VS.HHO.SuccInterFreqOut
67183902
VS.HHO.FailInter FreqOut.CfgUnsupp
67183903
VS.HHO.FailInter FreqOut.PyhChFail
Issue 01 (2013-05-04)
1068
Counter ID 67183904
Counter Name VS.HHO.FailInter FreqOut.ISR
Counter Description Number of Failed Outgoing InterFrequency Hard Handovers for Cell (Incompatible Simultaneous Reconfiguration) Number of Failed Outgoing InterFrequency Hard Handovers for Cell (Cell Update Occurred) Number of Failed Outgoing InterFrequency Hard Handovers for Cell (Invalid Configuration) Number of Failed Outgoing InterFrequency Hard Handovers Due to No Response from the UE for Cell Number of Incoming Inter-Frequency Hard Handover Attempts for Cell Number of Successful Incoming Inter-Frequency Hard Handovers for Cell Number of Call Drops Due to Failed Outgoing IntraFrequency Hard Handovers for Cell Number of Outgoing Inter-Frequency Hard Handover Attempts in NodeB for Cell
67183906
VS.HHO.FailInter FreqOut.CellUpdt
67183907
VS.HHO.FailInter FreqOut.InvCfg
67183908
VS.HHO.FailInter FreqOut.NoReply
67183912
VS.HHO.AttInterFreqIn
67183913
VS.HHO.SuccInterFreqIn
67183926
VS.HHO.IntraFreq Out.Drop
67190877
VS.HHO.AttInterF reqOut.IntraNodeB
Issue 01 (2013-05-04)
1069
Counter ID 67190878
Counter Name VS.HHO.SuccInter FreqOut.IntraNodeB
Counter Description Number of Successful Outgoing Inter-Frequency Hard Handovers in NodeB for Cell Number of Outgoing Inter-Frequency Hard Handovers Attempts Between Different NodeBs of RNC for Cell Number of Successful Outgoing Inter-Frequency Hard Handovers Between Different NodeBs of RNC for Cell Number of Outgoing Inter-Frequency Hard Handovers Attempts Between RNCs for Cell Number of Successful Outgoing Inter-Frequency Hard Handovers Between RNCs for Cell Number of Relocation Execution Attempts with Outgoing InterFrequency Hard Handovers for Cell Number of Successful Relocation Executions with Outgoing InterFrequency Hard Handovers for Cell
67190884
VS.HHO.AttInterF reqOut.InterNodeBIntraRNC
67190885
VS.HHO.SuccInter FreqOut.InterNodeBIntraRNC
67190891
VS.HHO.AttInterF reqOut.InterRNC
67190892
VS.HHO.SuccInter FreqOut.InterRNC
67190898
VS.HHO.AttInterFreqRelocExec
67190899
VS.HHO.SuccInterFreqRelocExec
Issue 01 (2013-05-04)
1070
Counter ID 67191694
Counter Name VS.HHO.AttBlindHO
Counter Description Number of Outgoing Emergency Blind Handover Attempts for Cell Number of Successful Outgoing Emergency Blind Hard Handovers for Cell Number of Handovers Not Performed Due to CS Inter-Frequency Measurement Expiry for Cell Number of Handovers Not Performed Due to PS Inter-Frequency Measurement Expiry for Cell Number of CS InterFrequency Hard Handover Attempts Based on RSCP for Cell Number of CS InterFrequency Hard Handover Attempts Based on EcNo for Cell Number of PS InterFrequency Hard Handover Attempts Based on RSCP for Cell Number of PS InterFrequency Hard Handover Attempts Based on EcNo for Cell
67191695
VS.HHO.SuccBlindHO
67193397
VS.HHO.InterFreq Out.CS.MeasTimeOut
67193398
VS.HHO.InterFreq Out.PS.MeasTimeOut
67193401
VS.HHO.AttInterF reqOut.CS.TrigRsc p
67193402
VS.HHO.AttInterF reqOut.CS.TrigEcNo
67193403
VS.HHO.AttInterF reqOut.PS.TrigRsc p
67193404
VS.HHO.AttInterF reqOut.PS.TrigEcNo
Issue 01 (2013-05-04)
1071
Counter ID 73403768
Counter Name VS.HHO.AttInterF reqIn.CS
Counter Description Number of Requests for CS Incoming Inter-Frequency Hard Handovers for Cell Number of Requests for PS Incoming Inter-Frequency Hard Handovers for Cell Number of Requests for CS Outgoing Inter-Frequency Hard Handovers for Cell Number of Requests for PS Outgoing Inter-Frequency Hard Handovers for Cell Number of Successful for CS Incoming InterFrequency Hard Handovers for Cell Number of Successful for PS Incoming InterFrequency Hard Handovers for Cell Number of Successful for CS Outgoing InterFrequency Hard Handovers for Cell Number of Successful for PS Outgoing InterFrequency Hard Handovers for Cell
73403769
VS.HHO.AttInterF reqIn.PS
V900R012
73403770
VS.HHO.AttInterF reqOut.CS
V900R012
73403771
VS.HHO.AttInterF reqOut.PS
V900R012
73403772
VS.HHO.SuccInter FreqIn.CS
V900R012
73403773
VS.HHO.SuccInter FreqIn.PS
V900R012
73403774
VS.HHO.SuccInter FreqOut.CS
V900R012
73403775
VS.HHO.SuccInter FreqOut.PS
V900R012
Issue 01 (2013-05-04)
1072
Counter ID 73403776
Counter Name VS.HHO.InterFreq Out.CS.Drop
Counter Description Number of CS Call Drops due to Unsuccessful Outgoing InterFrequency Hard Handovers for cell Number of PS Call Drops due to Unsuccessful Outgoing InterFrequency Hard Handovers for cell Number of Successful CS InterFrequency Hard Handovers Based on RSCP for Cell Number of Successful CS InterFrequency Hard Handovers Based on EcNo for Cell Number of Successful PS InterFrequency Hard Handovers Based on RSCP for Cell Number of Successful PS InterFrequency Hard Handovers Based on EcNo for Cell Number of Failed Outgoing IntraFrequency Hard Handovers Between RNCs for Cell (Cell update occurred) Number of Failed Outgoing IntraFrequency Hard Handovers Between the RNCs Due to No Response from the UE for Cell
73403777
VS.HHO.InterFreq Out.PS.Drop
V900R012
73404081
VS.HHO.SuccInter FreqOut.CS.Rscp
V900R012
73404082
VS.HHO.SuccInter FreqOut.CS.EcNo
V900R012
73404083
VS.HHO.SuccInter FreqOut.PS.Rscp
V900R012
73404084
VS.HHO.SuccInter FreqOut.PS.EcNo
V900R012
73393851
VS.HHO.FailIntra FreqOut.InterRNC .CellUpdt
V900R012
73393852
VS.HHO.FailIntra FreqOut.InterRNC .NoReply
V900R012
Issue 01 (2013-05-04)
1073
Counter ID 73393853
Counter Name VS.HHO.FailInter FreqOut.InterRNC .CfgUnsupp
Counter Description Number of Failed Outgoing InterFrequency Hard Handovers Between the RNCs for Cell (Configuration Unsupported) Number of Failed Outgoing InterFrequency Hard Handovers Between the RNCs for Cell (Physical Channel Failure) Number of Failed Outgoing InterFrequency Hard Handovers Between the RNCs for Cell (Incompatible Simultaneous Reconfiguration) Number of Failed Outgoing InterFrequency Hard Handovers Between the RNCs for Cell (Invalid Configuration) Number of Failed Outgoing InterFrequency Hard Handovers Between the RNCs for Cell (Cell Update Occurred) Number of Failed Outgoing InterFrequency Hard Handovers Between the RNCs Due to No Response from the UE for Cell
73393854
VS.HHO.FailInter FreqOut.InterRNC .PhyChFail
V900R012
73393855
VS.HHO.FailInter FreqOut.InterRNC .ISR
V900R012
73393856
VS.HHO.FailInter FreqOut.InterRNC .InvCfg
V900R012
73393857
VS.HHO.FailInter FreqOut.InterRNC .CellUpdt
V900R012
73393858
VS.HHO.FailInter FreqOut.InterRNC .NoReply
V900R012
Issue 01 (2013-05-04)
1074
Counter ID 73393934
Counter Name VS.HHO.AttInterF reqOut.PS.UlBler
Counter Description Number of PS InterFrequency Hard Handover Attempts Based on UL BLER for Cell Number of CS InterFrequency Hard Handover Attempts Based on UE Transmit Power for Cell Number of PS InterFrequency Hard Handover Attempts Based on UE Transmit Power for Cell Number of CS InterFrequency Hard Handover Attempts Based on DL Transmit Power for Cell Number of PS InterFrequency Hard Handover Attempts Based on DL Transmit Power for Cell Number of CS InterFrequency Hard Handover Attempts Based on Cell Total Transmit Power for Cell Number of PS InterFrequency Hard Handover Attempts Based on Cell Total Transmit Power for Cell
73393935
VS.HHO.AttInterF reqOut.CS.UeTxP wr
V900R012
73393936
VS.HHO.AttInterF reqOut.PS.UeTxP wr
V900R012
73393937
VS.HHO.AttInterF reqOut.CS.Tcp
V900R012
73393938
VS.HHO.AttInterF reqOut.PS.Tcp
V900R012
73393939
VS.HHO.AttInterF reqOut.CS.TotalTxPwr
V900R012
73393940
VS.HHO.AttInterF reqOut.PS.TotalTxPwr
V900R012
Issue 01 (2013-05-04)
1075
Counter ID 73393941
Counter Name VS.HHO.AttInterF reqOut.CS.TotalRxPwr
Counter Description Number of CS InterFrequency Hard Handover Attempts Based on Cell Total Receive Power for Cell Number of PS InterFrequency Hard Handover Attempts Based on Cell Total Receive Power for Cell Number of CS InterFrequency Hard Handover Attempts Based on Code Resources for Cell Number of PS InterFrequency Hard Handover Attempts Based on Code Resources for Cell Number of Successful PS InterFrequency Hard Handovers Based on UL BLER for Cell Number of Successful CS InterFrequency Hard Handovers Based on UE Transmit Power for Cell Number of Successful PS InterFrequency Hard Handovers Based on UE Transmit Power for Cell Number of Successful CS InterFrequency Hard Handovers Based on DL Transmit Power for Cell
73393942
VS.HHO.AttInterF reqOut.PS.TotalRxPwr
V900R012
73393943
VS.HHO.AttInterF reqOut.CS.Code
V900R012
73393944
VS.HHO.AttInterF reqOut.PS.Code
V900R012
73393945
VS.HHO.SuccInter FreqOut.PS.UlBler
V900R012
73393946
VS.HHO.SuccInter FreqOut.CS.UeTx Pwr
V900R012
73393947
VS.HHO.SuccInter FreqOut.PS.UeTxP wr
V900R012
73393948
VS.HHO.SuccInter FreqOut.CS.Tcp
V900R012
Issue 01 (2013-05-04)
1076
Counter ID 73393949
Counter Name VS.HHO.SuccInter FreqOut.PS.Tcp
Counter Description Number of Successful PS InterFrequency Hard Handovers Based on DL Transmit Power for Cell Number of Successful CS InterFrequency Hard Handovers Based on Cell Total Transmit Power for Cell Number of Successful PS InterFrequency Hard Handovers Based on Cell Total Transmit Power for Cell Number of Successful CS InterFrequency Hard Handovers Based on Cell Total Receive Power for Cell Number of Successful PS InterFrequency Hard Handovers Based on Cell Total Receive Power for Cell Number of Successful CS InterFrequency Hard Handovers Based on Code Resources for Cell Number of Successful PS InterFrequency Hard Handovers Based on Code Resources for Cell
73393950
VS.HHO.SuccInter FreqOut.CS.TotalTxPwr
V900R012
73393951
VS.HHO.SuccInter FreqOut.PS.TotalTxPwr
V900R012
73393952
VS.HHO.SuccInter FreqOut.CS.TotalRxPwr
V900R012
73393953
VS.HHO.SuccInter FreqOut.PS.TotalRxPwr
V900R012
73393954
VS.HHO.SuccInter FreqOut.CS.Code
V900R012
73393955
VS.HHO.SuccInter FreqOut.PS.Code
V900R012
Issue 01 (2013-05-04)
1077
Counter ID 73424203
Counter Name VS.HHO.AttInterF reqOut.PS.UlCE
Counter Description Number of PS InterFrequency Hard Handover Attempts Based on UL CE for Cell Number of Successful PS InterFrequency Hard Handovers Based on UL CE for Cell Number of PS InterFrequency Hard Handover Attempts Based on DL CE for Cell Number of Successful PS InterFrequency Hard Handovers Based on DL CE for Cell Number of CS InterFrequency Hard Handover Attempts Based on DL CE for Cell Number of CS InterFrequency Hard Handover Attempts Based on UL CE for Cell Number of Successful CS InterFrequency Hard Handovers Based on UL CE for Cell Number of Successful CS InterFrequency Hard Handovers Based on DL CE for Cell
73424204
VS.HHO.SuccInter FreqOut.PS.UlCE
V900R014
73424243
VS.HHO.AttInterF reqOut.PS.DlCE
V900R014
73424244
VS.HHO.SuccInter FreqOut.PS.DlCE
V900R014
73424245
VS.HHO.AttInterF reqOut.CS.DlCE
V900R014
73424246
VS.HHO.AttInterF reqOut.CS.UlCE
V900R014
73424247
VS.HHO.SuccInter FreqOut.CS.UlCE
V900R014
73424248
VS.HHO.SuccInter FreqOut.CS.DlCE
V900R014
Issue 01 (2013-05-04)
1078
Counter ID 73425014
Counter Name VS.HHO.AttInterF reqOut.Sig
Counter Description Number of InterFrequency Hard Handover Attempts When only Signaling Exists for Cell Number of Successful InterFrequency Hard Handover Attempts When only Signaling Exists for Cell Number of Outgoing Macro & Micro Joint Inter-frequency Handover Attempts in PS Domain for Cell Number of Successful Outgoing Macro & Micro Joint Inter-frequency Handovers in PS Domain for Cell
73425015
VS.HHO.SuccInter FreqOut.Sig
V900R014
73425831
VS.HHO.AttInterF reqOut.PS.CoMacroMicro
V900R015
73425832
VS.HHO.SuccInter FreqOut.PS.CoMacroMicro
V900R015
Counter VS.HHO.AttInterFreqOut Sub Counter VS.HHO.AttInterFreqOut.IntraNodeB VS.HHO.AttInterFreqOut.InterNodeBIntraRNC VS.HHO.AttInterFreqOut.InterRNC VS.HHO.SuccInterFreqOut VS.HHO.SuccInterFreqOut.IntraNodeB VS.HHO.SuccInterFreqOut.InterNodeBIntraRNC VS.HHO.SuccInterFreqOut.InterRNC
1.12.11.1 Number of Incoming Hard Handover Attempts
Issue 01 (2013-05-04)
1079
Counters
Counter ID 67180565 Counter Name VS.HHO.AttIn Counter Description Number of Incoming Hard Handover Attempts for Cell
Description
This counter provides the number of incoming hard handover attempts. The measurement is performed in the target cell in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. When the hard handover decision conditions are met, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE and measures the counter in the target cell of the hard handover. Figure 1-457 Successful hard handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttIn Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.2 Number of Successful Incoming Hard Handovers Counters

Counter ID 67180566 Counter Name VS.HHO.SuccIn Counter Description Number of Successful Incoming Hard Handovers in the RNC for Cell
Description
This counter provides the number of successful incoming hard handovers. The measurement is performed in the target cell in the RNC.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the hard handover, if the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the hard handover succeeds. In this case, the RNC measures the counter in the target cell of incoming hard handover.
Issue 01 (2013-05-04)
1081
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccIn Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.3 Number of Relocation Preparation Attempts with Outgoing IntraFrequency Hard Handovers
Counters
Counter ID 67193708 Counter Name VS.HHO.AttIntraFreqRelocPrep Counter Description Number of Relocation Preparation Attempts with Outgoing Intra-Frequency Hard Handovers for Cell
Description
This counter provides the number of relocation preparation attempts with outgoing intrafrequency hard handovers. The measurement is performed in the best cell of the SRNC where the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the following figure. During the relocation preparation with outgoing intra-frequency hard handover, when the SRNC sends a RELOCATION REQUIRED message to the CN, the SRNC measures the counter in the best cell of the SRNC where the UE camps on. If the UE connects to the CS and PS domains at the same time during relocation preparation, the RNC will send the RELOCATION REQUIRED message to both domains. In this case, the RNC measures the counter once only. Figure 1-459 SRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttIntraFreqRelocPrep Feature ID WRFD-02060502 Feature Name SRNS Relocation with Hard Handover
1.12.11.4 Number of Successful Relocation Preparations with Outgoing IntraFrequency Hard Handovers Counters
Counter ID 67192770 Counter Name VS.HHO.SuccIntraFreqRelocPrep Counter Description Number of Successful Relocation Preparations with Outgoing Intra-Frequency Hard Handovers for Cell
Description
This counter provides the number of successful relocation preparations with outgoing intrafrequency hard handovers. The measurement is performed in the best cell of the SRNC where the UE camps on.
Measurement point
The measurement is triggered at point B as shown in the following figure. During the relocation preparation with outgoing intra-frequency hard handover, when the SRNC receives a RELOCATION COMMAND message from the CN, the SRNC measures the counter in the best cell of the SRNC where the UE camps on. If the UE connects to the CS and PS domains at the same time during relocation preparation, both domains will send a RELOCATION COMMAND message to the RNC. In this case, the RNC measures the counter once only. Figure 1-460 SRNC relocation preparation procedure
Issue 01 (2013-05-04)
1084
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccIntraFreqRelocPrep Feature ID WRFD-02060502 Feature Name SRNS Relocation with Hard Handover
1.12.11.5 Number of Relocation Preparation Attempts with Outgoing InterFrequency Hard Handovers Counters
Counter ID 67192551 Counter Name VS.HHO.AttInterFreqRelocPrep Counter Description Number of Relocation Preparation Attempts with Outgoing Inter-Frequency Hard Handovers for Cell
Description
This counter provides the number of relocation preparation attempts with outgoing interfrequency hard handovers. The measurement is performed in the best cell of the SRNC where the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the following figure. During the relocation preparation with outgoing inter-frequency hard handover, when the SRNC sends a RELOCATION REQUIRED message to the CN, the SRNC measures the counter in the best cell of the SRNC where the UE camps on. If the UE connects to the CS and PS domains at the same time during relocation preparation, the RNC will send a RELOCATION REQUIRED message to both domains. In this case, the RNC measures the counter once only.
Issue 01 (2013-05-04)
1085
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttInterFreqRelocPrep Feature ID WRFD-02060502 Feature Name SRNS Relocation with Hard Handover
1.12.11.6 Number of Successful Relocation Preparations with Outgoing InterFrequency Hard Handovers Counters
Counter ID 67192552 Counter Name VS.HHO.SuccInterFreqRelocPrep Counter Description Number of Successful Relocation Preparations with Outgoing Inter-Frequency Hard Handovers for Cell
Issue 01 (2013-05-04)
1086
Description
This counter provides the number of successful relocation preparations with outgoing interfrequency hard handovers. The measurement is performed in the best cell of the SRNC where the UE camps on.
Measurement point
The measurement is triggered at point B as shown in the following figure. During the relocation preparation with inter-frequency hard handover, when the SRNC receives a RELOCATION COMMAND message from the CN, the SRNC measures the counter in the best cell of the SRNC where the UE camps on. If the UE connects to the CS and PS domains at the same time during relocation preparation, both domains will send a RELOCATION COMMAND message to the RNC. In this case, the RNC measures the counter once only. Figure 1-462 SRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccInterFreqRelocPrep Feature ID WRFD-02060502 Feature Name SRNS Relocation with Hard Handover
1.12.11.7 Number of Failed Outgoing Intra-Frequency Hard Handovers Due to No Response from the UE
Counters
Counter ID 67192553 Counter Name VS.HHO.FailIntraFreqOut. NoReply Counter Description Number of Failed Outgoing Intra-Frequency Hard Handovers Due to No Response from the UE for Cell
Description
This counter provides the number of failed outgoing intra-frequency hard handovers due to no response from the UE. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the intra-frequency hard handover, the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE and starts the associated timer to wait for the response from the UE. If the RNC does not receive the response message from the UE before the timer is expired, the RNC measures the counter in the best cell where the UE camps on before the intra-frequency hard handover. Figure 1-463 Failed hard handover procedure (UE no response)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailIntraFreqOut. NoReply Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
1.12.11.8 Number of Failed Preparations for Outgoing Intra-Frequency Hard Handovers Counters
Counter ID 67192554 Counter Name VS.HHO.FailIntraFreqOut.P repFail Counter Description Number of Failed Preparations for Outgoing Intra-Frequency Hard Handovers for Cell
Description
This counter provides the number of failed preparations for outgoing intra-frequency hard handovers. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point A as shown in the figure, where the PHYSICAL CHANNEL RECONFIGURATION message is used as an example. The RNC initiates a request for an intra-frequency hard handover if the criteria of the decision to perform the handover are fulfilled. If the admission fails, this counter is increased by one in the best cell that the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1089
Figure 1-464 Failed hard handover procedure (admission fails)
The measurement is triggered at point B as shown in the figure, where the PHYSICAL CHANNEL RECONFIGURATION message is used as an example. The RNC initiates a request for an intra-frequency hard handover if the criteria of the decision to perform the handover are fulfilled. If the preparation for the intra-frequency hard handover fails before the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE, including the failure in the RL establishment on the Iub and Iur interfaces, this counter is increased by one in the best cell that the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1090
Figure 1-465 Failed hard handover procedure (failure in the RL establishment on the Iur interface)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailIntraFreqOut.P repFail Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
1.12.11.9 Number of Failed Preparations for Outgoing Inter-Frequency Hard Handovers

Counters
Counter ID 67192555 Counter Name VS.HHO.FailInterFreqOut.P repFail Counter Description Number of Failed Preparations for Outgoing Inter-Frequency Hard Handovers for Cell
Description
This counter provides the number of failed preparations for outgoing inter-frequency hard handovers. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point A as shown in the figure, where the PHYSICAL CHANNEL RECONFIGURATION message is used as an example. The RNC initiates a request for an inter-frequency hard handover if the criteria of the decision to perform the handover are fulfilled. If the admission fails, this counter is increased by one in the best cell that the UE camps on before the hard handover. Figure 1-466 Failed hard handover procedure (admission fails)
The measurement is triggered at point B as shown in the following figure, where the PHYSICAL CHANNEL RECONFIGURATION message is used as an example. The RNC initiates a request for an inter-frequency hard handover if the criteria of the decision to perform the handover are fulfilled. If the preparation for the hard handover fails before the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE, including the failure in the RL
establishment on the Iub and Iur interfaces, this counter is increased by one in the best cell that the UE camps on before the hard handover. Figure 1-467 Failed hard handover procedure (failure in the RL establishment on the Iur interface)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailInterFreqOut.P repFail Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
Issue 01 (2013-05-04)
1093
1.12.11.10 Number of Failed Preparations for Outgoing Intra-Frequency Hard Handovers Due to Radio Link Establishment Failure Counters
Counter ID 67192556 Counter Name VS.HHO.FailIntraFreqOut. RLSetupFail Counter Description Number of Failed Preparations for Outgoing Intra-Frequency Hard Handovers Due to Radio Link Establishment Failure for Cell
Description
This counter provides the number of failed preparations for outgoing intra-frequency hard handovers due to radio link establishment failures. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC initiates the request for an intra-frequency hard handover if the criteria of the decision to perform handover are fulfilled. Then, if the preparation for the handover fails due to the failure to establish radio links on the Iub interface before the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC measures the counter at point B as shown in the following figure in the best cell where the UE camps on before the hard handover. Figure 1-468 Failed hard handover procedure (failure in the RL establishment on the Iub interface)
Issue 01 (2013-05-04)
1094
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC initiates the request for an intra-frequency hard handover if the criteria of the decision to perform handover are fulfilled. Then, if the preparation for the handover fails due to the failure to establish radio links on the Iur interface before the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC measures the counter at point B as shown in the following figure in the best cell where the UE camps on before the hard handover. Figure 1-469 Failed hard handover procedure (failure in the RL establishment on the Iur interface)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailIntraFreqOut. RLSetupFail Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
Issue 01 (2013-05-04)
1095
1.12.11.11 Number of Failed Preparations for Outgoing Inter-Frequency Hard Handovers Due to Radio Link Establishment Failure Counters
Counter ID 67192557 Counter Name VS.HHO.FailInterFreqOut. RLSetupFail Counter Description Number of Failed Preparations for Outgoing Inter-Frequency Hard Handovers Due to Radio Link Establishment Failure for Cell
Description
This counter provides the number of failed preparations for outgoing inter-frequency hard handovers due to radio link establishment failures. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC initiates the request for an inter-frequency hard handover if the criteria of the decision to perform the handover are fulfilled. Then, if the preparation for the handover fails due to the failure to establish radio links on the Iub interface before the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC measures the counter at point B as shown in the following figure in the best cell where the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1096
Figure 1-470 Failed hard handover procedure (failure in the RL establishment on the Iub interface)
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC initiates the request for an inter-frequency hard handover if the criteria of the decision to perform the handover are fulfilled. Then, if the preparation for the handover fails due to the failure to establish radio links on the Iur interface before the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC measures the counter at point B as shown in the following figure in the best cell where the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1097
Figure 1-471 Failed hard handover procedure (failure in the RL establishment on the Iur interface)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailInterFreqOut. RLSetupFail Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.12 Counters Related to the Number of Failed Outgoing Intra-Frequency Hard Handovers for Different Causes
Counters
Counter ID 67192558 Counter Name VS.HHO.FailIntraFreqOut. CfgUnsupp Counter Description Number of Failed Outgoing Intra-Frequency Hard Handovers for Cell (Configuration Unsupported) Number of Failed Outgoing Intra-Frequency Hard Handovers for Cell (Invalid Configuration) Number of Failed Outgoing Intra-Frequency Hard Handovers for Cell (Physical Channel Failure) Number of Failed Outgoing Intra-Frequency Hard Handovers for Cell (Incompatible Simultaneous Reconfiguration) Number of Failed Outgoing Intra-Frequency Hard Handovers for Cell (Cell Update Occurred)
67192614
VS.HHO.FailIntraFreqOut.I nvCfg
67192559
VS.HHO.FailIntraFreqOut.P yhChFail
67192560
VS.HHO.FailIntraFreqOut.I SR
67192561
VS.HHO.FailIntraFreqOut. CellUpdt
Description
These counters provide the number of failed outgoing intra-frequency hard handovers due to different failure causes. The measurements are performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurements are triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the intrafrequency hard handover, after receiving the PHYSICAL CHANNEL RECONFIGURATION FAILURE message from the UE, the RNC measures the related counters in the best cell where the UE camps on before the intra-frequency hard handover according to the failure cause contained in the message.
Issue 01 (2013-05-04)
1099
Figure 1-472 Failed hard handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailIntraFreqOut. CfgUnsupp VS.HHO.FailIntraFreqOut.I nvCfg VS.HHO.FailIntraFreqOut.P yhChFail VS.HHO.FailIntraFreqOut.I SR VS.HHO.FailIntraFreqOut. CellUpdt Feature ID WRFD-020301 WRFD-020301 WRFD-020301 WRFD-020301 WRFD-020301 Feature Name Intra Frequency Hard Handover Intra Frequency Hard Handover Intra Frequency Hard Handover Intra Frequency Hard Handover Intra Frequency Hard Handover
1.12.11.13 Number of CS Outgoing Inter-Band Hard Handover Attempts
Issue 01 (2013-05-04)
1100
Counters
Counter ID 67193565 Counter Name VS.HHO.AttMultiBandOut. CS Counter Description Number of CS Outgoing Inter-Band Hard Handover Attempts for Cell
Description
This counter provides the number of CS outgoing inter-band hard handover attempts. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs hard handover for CS services if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. If the source cell and target cell are not on the same frequency band, the RNC measures the counter in the best cell where the UE camps on before the hard handover. Figure 1-473 Successful hard handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttMultiBandOut. CS Feature ID WRFD-020110 Feature Name Multi Frequency Band Networking Management
1.12.11.14 Number of Successful CS Outgoing Inter-Band Hard Handovers Counters

Counter ID 67193566 Counter Name VS.HHO.SuccMultiBandOu t.CS Counter Description Number of Successful CS Outgoing Inter-Band Hard Handovers for Cell
Description
This counter provides the number of successful CS outgoing inter-band hard handovers. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs hard handover for CS services if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. When the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the hard handover succeeds. If the source cell and target cell are not on the same frequency band, the RNC measures the counter in the best cell where the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1102
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccMultiBandOu t.CS Feature ID WRFD-020110 Feature Name Multi Frequency Band Networking Management
1.12.11.15 Number of PS Outgoing Inter-Band Hard Handover Attempts Counters

Counter ID 67192567 Counter Name VS.HHO.AttMultiBandOut. PS Counter Description Number of PS Outgoing Inter-Band Hard Handover Attempts for Cell
Issue 01 (2013-05-04)
1103
Description
This counter provides the number of PS outgoing inter-band hard handover attempts. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs hard handover for PS services if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. If the source cell and target cell are not on the same frequency band, the RNC measures the counter in the best cell where the UE camps on before the hard handover. Figure 1-475 Successful hard handover procedure
Formula
None
Unit
None
Issue 01 (2013-05-04)
1104
Related Features
Counter Name VS.HHO.AttMultiBandOut. PS Feature ID WRFD-020110 Feature Name Multi Frequency Band Networking Management
1.12.11.16 Number of Successful PS Outgoing Inter-Band Hard Handovers Counters

Counter ID 67192568 Counter Name VS.HHO.SuccMultiBandOu t.PS Counter Description Number of Successful PS Outgoing Inter-Band Hard Handovers for Cell
Description
This counter provides the number of successful PS outgoing inter-band hard handovers. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs hard handover for PS services if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. When the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the hard handover succeeds. If the source cell and target cell are not on the same frequency band, the RNC measures the counter in the best cell where the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1105
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccMultiBandOu t.PS Feature ID WRFD-020110 Feature Name Multi Frequency Band Networking Management
1.12.11.17 Number of Outgoing Intra-Frequency Hard Handover Attempts in NodeB
Issue 01 (2013-05-04)
1106
Counters
Counter ID 67180585 Counter Name VS.HHO.AttIntraFreqOut.In traNodeB Counter Description Number of Outgoing IntraFrequency Hard Handover Attempts in NodeB for Cell
Description
This counter provides the number of outgoing intra-frequency hard handover attempts in the NodeB. The measurement is performed in the best cell where the UE camps on before the hard handover. In the case of intra-frequency hard handover in the NodeB, the best source cell and the target cell must belong to the same NodeB.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs intrafrequency hard handover if the criteria of the decision to perform the hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. If the best cell before the hard handover and target cell belong to the same NodeB and use the same frequency, the RNC measures this counter in the best cell where the UE camps on before the hard handover. Figure 1-477 Successful hard handover procedure
Issue 01 (2013-05-04)
1107
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttIntraFreqOut.In traNodeB Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
1.12.11.18 Number of Successful Outgoing Intra-Frequency Hard Handovers in NodeB Counters

Counter ID 67180586 Counter Name VS.HHO.SuccIntraFreqOut. IntraNodeB Counter Description Number of Successful Outgoing Intra-Frequency Hard Handovers in NodeB for Cell
Description
This counter provides the number of successful outgoing intra-frequency hard handovers in the NodeB. The measurement is performed in the best cell where the UE camps on before the hard handover. In the case of intra-frequency hard handover in the NodeB, the best source cell and the target cell must belong to the same NodeB.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs intrafrequency hard handover if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. When the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the hard handover succeeds. If the best cell before the hard handover and target cell belong to the same NodeB and use the same frequency, the RNC measures this counter in the best cell where the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1108
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccIntraFreqOut. IntraNodeB Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
1.12.11.19 Number of Outgoing Intra-Frequency Hard Handover Attempts Between Different NodeBs of RNC
Issue 01 (2013-05-04)
1109
Counters
Counter ID 67180587 Counter Name VS.HHO.AttIntraFreqOut.In terNodeBIntraRNC Counter Description Number of Outgoing IntraFrequency Hard Handover Attempts Between Different NodeBs of RNC for Cell
Description
This counter provides the number of outgoing intra-frequency hard handover attempts between different NodeBs of the same RNC. The measurement is performed in the best cell where the UE camps on before the hard handover. In the case of intra-frequency hard handover attempts between different NodeBs of the same RNC, the best source cell and the target cell must belong to different NodeBs of the same RNC.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs intrafrequency hard handover if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. If the best cell before the hard handover and target cell belong to different NodeBs of the same RNC and use the same frequency, the RNC measures this counter in the best cell where the UE camps on before the hard handover. Figure 1-479 Successful hard handover procedure
Issue 01 (2013-05-04)
1110
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttIntraFreqOut.In terNodeBIntraRNC Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
1.12.11.20 Number of Successful Outgoing Intra-Frequency Hard Handovers Between Different NodeBs of RNC Counters
Counter ID 67180588 Counter Name VS.HHO.SuccIntraFreqOut. InterNodeBIntraRNC Counter Description Number of Successful Outgoing Intra-Frequency Hard Handovers Between Different NodeBs of RNC for Cell
Description
This counter provides the number of successful outgoing intra-frequency hard handovers between different NodeBs of the same RNC. The measurement is performed in the best cell where the UE camps on before the hard handover. In the case of intra-frequency hard handover attempts between different NodeBs of the same RNC, the best source cell and the target cell must belong to different NodeBs of the same RNC.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs intrafrequency hard handover if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. When the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the hard handover succeeds. If the best cell before the hard handover and target cell belong to different NodeBs of the same RNC and use the same frequency, the RNC measures this counter in the best cell where the UE camps on before the hard handover.
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccIntraFreqOut. InterNodeBIntraRNC Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
1.12.11.21 Number of Outgoing Intra-Frequency Hard Handover Attempts Between RNCs
Issue 01 (2013-05-04)
1112
Counters
Counter ID 67180589 Counter Name VS.HHO.AttIntraFreqOut.In terRNC Counter Description Number of Outgoing IntraFrequency Hard Handover Attempts Between RNCs for Cell
Description
This counter provides the number of outgoing intra-frequency hard handover attempts between the RNCs. The measurement is performed in the best cell where the UE camps on before the hard handover. In the case of intra-frequency hard handover between the RNCs, the source cell and the target cell must belong to different RNCs and the handover is performed through the Iur interface between the RNCs.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs intrafrequency hard handover if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. If the best cell before the hard handover and the target cell are controlled by the SRNC and the DRNC respectively and use the same frequency, the SRNC measures this counter in the best cell where the UE camps on before the hard handover. Figure 1-481 Hard handover procedure (between different RNCs)
Issue 01 (2013-05-04)
1113
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttIntraFreqOut.In terRNC Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
1.12.11.22 Number of Successful Outgoing Intra-Frequency Hard Handovers Between RNCs Counters
Counter ID 67180590 Counter Name VS.HHO.SuccIntraFreqOut. InterRNC Counter Description Number of Successful Outgoing Intra-Frequency Hard Handovers Between RNCs for Cell
Description
This counter provides the number of successful outgoing intra-frequency hard handovers between the RNCs. The measurement is performed in the best cell where the UE camps on before the hard handover. In the case of intra-frequency hard handover between the RNCs, the source cell and the target cell must belong to different RNCs and the handover is performed through the Iur interface between the RNCs.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs intrafrequency hard handover if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. When the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the hard handover succeeds. If the best cell before the hard handover and the target cell are controlled by the SRNC and the DRNC respectively and use the same frequency, the SRNC measures this counter in the best cell where the UE camps on before the hard handover.
Figure 1-482 Hard handover procedure (between different RNCs)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccIntraFreqOut. InterRNC Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
1.12.11.23 Counters Related to the Number of Failed Outgoing Intra-Frequency Hard Handovers Between RNCs for Different Causes
Issue 01 (2013-05-04)
1115
Counters
Counter ID 67189701 Counter Name VS.HHO.FailIntraFreqOut.I nterRNC.CfgUnsupp Counter Description Number of Failed Outgoing Intra-Frequency Hard Handovers Between RNCs for Cell (Configuration Unsupported) Number of Failed Outgoing Intra-Frequency Hard Handovers Between RNCs for Cell (Physical Channel Failure) Number of Failed Outgoing Intra-Frequency Hard Handovers Between RNCs for Cell (Incompatible Simultaneous Reconfiguration) Number of Failed Outgoing Intra-Frequency Hard Handovers Between RNCs for Cell (Invalid Configuration) Number of Failed Outgoing Intra-Frequency Hard Handovers Between RNCs for Cell (Cell update occurred)
67189702
VS.HHO.FailIntraFreqOut.I nterRNC.PhyChFail
67189703
VS.HHO.FailIntraFreqOut.I nterRNC.ISR
67189704
VS.HHO.FailIntraFreqOut.I nterRNC.InvCfg
73393851
VS.HHO.FailIntraFreqOut.I nterRNC.CellUpdt
Description
These counters provide the number of failed outgoing intra-frequency hard handovers between the RNCs due to different failure causes. The measurements are performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurements are triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the intrafrequency hard handover between the RNCs, after receiving the PHYSICAL CHANNEL RECONFIGURATION FAILURE message from the UE, the RNC measures the related counters in the best cell where the UE camps on before the hard handover according to the failure cause contained in the message. In this case, the best cell before the hard handover and the target cell must belong to the SRNC and the DRNC respectively and use the same frequency.
Issue 01 (2013-05-04)
1116
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailIntraFreqOut.I nterRNC.CfgUnsupp VS.HHO.FailIntraFreqOut.I nterRNC.PhyChFail VS.HHO.FailIntraFreqOut.I nterRNC.ISR VS.HHO.FailIntraFreqOut.I nterRNC.InvCfg VS.HHO.FailIntraFreqOut.I nterRNC.CellUpdt Feature ID WRFD-020301 WRFD-020301 WRFD-020301 WRFD-020301 WRFD-020301 Feature Name Intra Frequency Hard Handover Intra Frequency Hard Handover Intra Frequency Hard Handover Intra Frequency Hard Handover Intra Frequency Hard Handover
1.12.11.24 Counters Related to the Number of Failed Relocation Preparations with Outgoing Hard Handovers for Different Causes
Issue 01 (2013-05-04)
1117
Counters
Counter ID 67189708 Counter Name HHO.FailRelocPrepOut.No ResAvail Counter Description Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (No Radio Resources Available in Target Cell) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (TRELOCalloc Expiry) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (Relocation Failure in Target CN/RNC or Target System) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (Relocation Not Supported in Target RNC or Target System) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (Relocation Target Not Allowed) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (O&M Intervention) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (No Resource Available) Number of Failed Relocation Preparations with Outgoing Hard Handovers for Cell (Unspecified Failure)
67189709
HHO.FailRelocPrepOut.Tex p
67189710
HHO.FailRelocPrepOut.Tgt Fail
67189711
HHO.FailRelocPrepOut.RelocUnsupp
67189712
HHO.FailRelocPrepOut.Tgt NotAllow
67189713
HHO.FailRelocPrepOut.OM
67189714
HHO.FailRelocPrepOut.ResUnavail
67189715
HHO.FailRelocPrepOut.Unspec
Description
These counters provide the number of failed relocation preparations with outgoing hard handovers. The measurements are performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurements are triggered at point A as shown in the following figure. During the relocation preparation with outgoing hard handover, after receiving the RELOCATION PREPARATION FAILURE message from the CN, the SRNC measures the related counters in the best cell where the UE camps on before the hard handover according to the failure cause contained in the message. In this case, the best cell must be controlled by the SRNC. Figure 1-484 Failed SRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
Counter Name HHO.FailRelocPrepOut.No ResAvail HHO.FailRelocPrepOut.Tex p HHO.FailRelocPrepOut.Tgt Fail HHO.FailRelocPrepOut.RelocUnsupp HHO.FailRelocPrepOut.Tgt NotAllow
Issue 01 (2013-05-04)
Feature Name SRNS Relocation with Hard Handover SRNS Relocation with Hard Handover SRNS Relocation with Hard Handover SRNS Relocation with Hard Handover SRNS Relocation with Hard Handover
1119
Counter Name HHO.FailRelocPrepOut.OM HHO.FailRelocPrepOut.ResUnavail HHO.FailRelocPrepOut.Unspec
Feature Name SRNS Relocation with Hard Handover SRNS Relocation with Hard Handover SRNS Relocation with Hard Handover
1.12.11.25 Number of Relocation Execution Attempts with Outgoing IntraFrequency Hard Handovers Counters
Counter ID 67189716 Counter Name VS.HHO.AttIntraFreqRelocExec Counter Description Number of Relocation Execution Attempts with Outgoing Intra-Frequency Hard Handovers for Cell
Description
The counter provides the number of relocation execution attempts with outgoing intra-frequency hard handovers. The measurement is performed in the best cell controlled by the SRNC. In terms of relocation with outgoing intra-frequency hard handover, the relocation execution refers to that the SRNC initiates the reconfiguration for the UE after the successful preparation for the relocation. In this case, the source cell and the target cell involved in the intra-frequency hard handover must be controlled by different RNCs.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the relocation with intrafrequency hard handover, after sending the PHYSICAL CHANNEL RECONFIGURATION message to the UE, the SRNC measures the counter in the best cell where the UE camps on before the relocation. In this case, the best cell before the relocation and the target cell must be controlled by the SRNC and the TRNC respectively.
Issue 01 (2013-05-04)
1120
Figure 1-485 Reconfiguration procedure during SRNC relocation with hard handover
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttIntraFreqRelocExec Feature ID WRFD-02060502 Feature Name SRNS Relocation with Hard Handover
1.12.11.26 Number of Successful Relocation Executions with Outgoing IntraFrequency Hard Handovers Counters
Counter ID 67189717 Counter Name VS.HHO.SuccIntraFreqRelocExec Counter Description Number of Successful Relocation Executions with Outgoing Intra-Frequency Hard Handovers for Cell
Issue 01 (2013-05-04)
1121
Description
The counter provides the number of successful relocation executions with outgoing intrafrequency hard handovers. The measurement is performed in the best cell controlled by the SRNC.
Measurement point
The measurement is triggered at point A as shown in the following figure. During the relocation with intra-frequency hard handover, when the SRNC receives the IU RELEASE COMMAND message from the CN and the cause value contained in the message is "Successful Relocation", "Normal Release", or "Network Optimization", the SRNC measures the counter in the best cell where the UE camps on before the relocation. In this case, the best cell before the relocation and the target cell must be controlled by the SRNC and the TRNC respectively. Figure 1-486 Successful SRNC relocation procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccIntraFreqRelocExec
Issue 01 (2013-05-04)
Feature Name SRNS Relocation with Hard Handover

1122
1.12.11.27 Number of Decisions for Outgoing Hard Handovers Counters

Counter ID 67189722 Counter Name VS.HHO.EvalOut Counter Description Number of Decisions for Outgoing Hard Handovers for Cell
Description
This counter provides the number of outgoing hard handover decisions initiated by the RNC. The measurement is performed in the best cell where the UE camps on before the hard handover when handover conditions are met.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. When hard handover conditions are met, the RNC initiates an outgoing hard handover, and then measures the counter in the best cell where the UE camps on before the hard handover. Figure 1-487 Successful hard handover procedure
Issue 01 (2013-05-04)
1123
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.EvalOut Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.28 Number of Decisions for Incoming Hard Handovers Counters

Counter ID 67189723 Counter Name VS.HHO.EvalIn Counter Description Number of Decisions for Incoming Hard Handovers for Cell
Description
This counter provides the number of incoming hard handover decisions initiated by the RNC. The measurement is performed in the target cell when handover conditions are met.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. When hard handover conditions are met, the RNC initiates an incoming hard handover, and then measures the counter in the target cell.
Issue 01 (2013-05-04)
1124
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.EvalIn Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.29 Number of Decisions for Outgoing Inter-Frequency Hard Handovers in Compressed Mode
Counters
Counter ID 67180551 Counter Name VS.HHO.InterFreqOut.Eval. CM Counter Description Number of Decisions for Outgoing Inter-Frequency Hard Handovers in Compressed Mode for Cell
Description
This counter provides the number of outgoing inter-frequency hard handover decisions initiated by the RNC when the inter-frequency compressed mode is started and hard handover conditions are met. The measurement is performed in the best cell before the hard handover.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. When the inter-frequency compressed mode is started, the RNC initiates an outgoing inter-frequency hard handover if hard handover conditions for inter-frequency measurements are met. In this case, the RNC measures the counter in the best cell where the UE camps on before the hard handover. Figure 1-489 Successful hard handover procedure
Issue 01 (2013-05-04)
1126
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.InterFreqOut.Eval. CM Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.30 Number of Decisions for Incoming Inter-Frequency Hard Handovers in Compressed Mode Counters
Counter ID 67180570 Counter Name VS.HHO.InterFreqIn.Eval.C M Counter Description Number of Decisions for Incoming Inter-Frequency Hard Handovers in Compressed Mode for Cell
Description
This counter provides the number of incoming inter-frequency hard handover decisions initiated by the RNC when the inter-frequency compressed mode is started and hard handover conditions are met. The measurement is performed in the target cell.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. When the inter-frequency compressed mode is started, the RNC initiates an incoming inter-frequency hard handover if hard handover conditions for inter-frequency measurements are met. In this case, the RNC measures the counter in the target cell.
Issue 01 (2013-05-04)
1127
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.InterFreqIn.Eval.C M Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.31 Counters Related to the Number of Outgoing Inter-Frequency Hard Handover Attempts Due to Load Balancing
Counters
Counter ID 67180549 Counter Name VS.HHO.AttInterCellLB.Si ngleRL Counter Description Number of Outgoing InterFrequency Hard Handover Attempts Due to Load Balancing for Cell (Single RL) Number of Outgoing InterFrequency Hard Handover Attempts Due to Load Balancing for Cell (Multiple RLs)
67193709
VS.HHO.AttInterCellLB.M ultiRL
Description
These counters provide the number of outgoing inter-frequency hard handover attempts due to the load balancing. The measurements are performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurements are triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. After an outgoing inter-frequency hard handover due to the load balancing is triggered, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. According to the RL state during the handover, the RNC measures the related counters in the best cell where the UE camps on before the hard handover. Figure 1-491 Successful hard handover procedure due to the load balancing
Issue 01 (2013-05-04)
1129
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttInterCellLB.Si ngleRL VS.HHO.AttInterCellLB.M ultiRL Feature ID WRFD-020103 WRFD-020103 Feature Name Inter Frequency Load Balance Inter Frequency Load Balance
1.12.11.32 Counters Related to the Number of Successful Outgoing Inter-Frequency Hard Handovers Due to Load Balancing Counters
Counter ID 67180550 Counter Name VS.HHO.SuccInterCellLB.S ingleRL Counter Description Number of Successful Outgoing Inter-Frequency Hard Handovers Due to Load Balancing for Cell (Single RL) Number of Successful Outgoing Inter-Frequency Hard Handovers Due to Load Balancing for Cell (Multiple RLs)
67193710
VS.HHO.SuccInterCellLB. MultiRL
Description
These counters provide the number of successful outgoing inter-frequency hard handovers due to the load balancing. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurements are triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. After an outgoing
inter-frequency hard handover due to the load balancing is triggered, if the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the handover succeeds. According to the RL state during the handover, the RNC measures the related counters in the best cell where the UE camps on before the hard handover. Figure 1-492 Successful hard handover procedure due to the load balancing
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccInterCellLB.S ingleRL VS.HHO.SuccInterCellLB. MultiRL Feature ID WRFD-020103 WRFD-020103 Feature Name Inter Frequency Load Balance Inter Frequency Load Balance
1.12.11.33 Number of Outgoing Inter-Frequency Hard Handover Attempts

Counters
Counter ID 67183900 Counter Name VS.HHO.AttInterFreqOut Counter Description Number of Outgoing InterFrequency Hard Handover Attempts for Cell
Description
This counter provides the number of outgoing inter-frequency hard handover attempts. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. After deciding to perform outgoing inter-frequency hard handover, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. In this case, the RNC measures the counter in the best cell where the UE camps on before the inter-frequency hard handover. Figure 1-493 Successful hard handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttInterFreqOut Feature ID WRFD-020302 WRFD-020304 WRFD-020106 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS Load Reshuffling
1.12.11.34 Number of Successful Outgoing Inter-Frequency Hard Handovers Counters

Counter ID 67183901 Counter Name VS.HHO.SuccInterFreqOut Counter Description Number of Successful Outgoing Inter-Frequency Hard Handovers for Cell
Description
This counter provides the number of successful outgoing inter-frequency hard handovers. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the inter-frequency hard handover, when the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the hard handover succeeds. In this case, the RNC measures the counter in the best cell where the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1133
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccInterFreqOut Feature ID WRFD-020302 WRFD-020304 WRFD-020106 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS Load Reshuffling
1.12.11.35 Counters Related to the Number of Failed Outgoing Inter-Frequency Hard Handovers for Different Causes
Counters
Counter ID 67183902 Counter Name VS.HHO.FailInterFreqOut. CfgUnsupp Counter Description Number of Failed Outgoing Inter-Frequency Hard Handovers for Cell (Configuration Unsupported) Number of Failed Outgoing Inter-Frequency Hard Handovers for Cell (Physical Channel Failure) Number of Failed Outgoing Inter-Frequency Hard Handovers for Cell (Incompatible Simultaneous Reconfiguration) Number of Failed Outgoing Inter-Frequency Hard Handovers for Cell (Cell Update Occurred) Number of Failed Outgoing Inter-Frequency Hard Handovers for Cell (Invalid Configuration)
67183903
VS.HHO.FailInterFreqOut.P yhChFail
67183904
VS.HHO.FailInterFreqOut.I SR
67183906
VS.HHO.FailInterFreqOut. CellUpdt
67183907
VS.HHO.FailInterFreqOut.I nvCfg
Description
These counters provide the number of failed outgoing inter-frequency hard handovers due to different failure causes. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurements are triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the interfrequency hard handover, after the RNC receives the PHYSICAL CHANNEL RECONFIGURATION FAILURE message from the UE, according to the failure cause contained in the message, the RNC measures the related counters in the best cell where the UE camps on before the inter-frequency hard handover.
Issue 01 (2013-05-04)
1135
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailInterFreqOut. CfgUnsupp Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailInterFreqOut.P yhChFail WRFD-020302 WRFD-020304 Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailInterFreqOut.I SR WRFD-020302 WRFD-020304 Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
Issue 01 (2013-05-04)
1136
Counter Name VS.HHO.FailInterFreqOut. CellUpdt
Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
VS.HHO.FailInterFreqOut.I nvCfg
WRFD-020302 WRFD-020304
Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.36 Number of Failed Outgoing Inter-Frequency Hard Handovers Due to No Response from the UE Counters
Counter ID 67183908 Counter Name VS.HHO.FailInterFreqOut. NoReply Counter Description Number of Failed Outgoing Inter-Frequency Hard Handovers Due to No Response from the UE for Cell
Description
This counter provides the number of failed outgoing inter-frequency hard handovers due to no response from the UE. The measurement is performed in the best cell before the hard handover.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the inter-frequency hard handover, after sending the PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC starts the associated timer to wait for the response from the UE. If the RNC fails to receive the response message from the UE before the timer expires, the hard handover fails. In this case, the RNC measures the counter in the best cell where the UE camps on before the inter-frequency hard handover.
Issue 01 (2013-05-04)
1137
Figure 1-496 Failed hard handover procedure (UE no response)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailInterFreqOut. NoReply Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.37 Number of Incoming Inter-Frequency Hard Handover Attempts Counters

Counter ID 67183912 Counter Name VS.HHO.AttInterFreqIn Counter Description Number of Incoming InterFrequency Hard Handover Attempts for Cell
1138
Issue 01 (2013-05-04)
Counter ID 73403768
Counter Name VS.HHO.AttInterFreqIn.CS
Counter Description Number of Requests for CS Incoming Inter-Frequency Hard Handovers for Cell Number of Requests for PS Incoming Inter-Frequency Hard Handovers for Cell
73403769
VS.HHO.AttInterFreqIn.PS
Description
This counter provides the number of incoming inter-frequency hard handover attempts. The measurement is performed in the target cell.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. After deciding to perform incoming inter-frequency hard handover, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. In this case, the RNC measures the counter in the target cell. Figure 1-497 Successful hard handover procedure
Issue 01 (2013-05-04)
1139
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttInterFreqIn Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.AttInterFreqIn.CS WRFD-020302 WRFD-020304 Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.AttInterFreqIn.PS WRFD-020302 WRFD-020304 Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.38 Number of Successful Incoming Inter-Frequency Hard Handovers Counters

Counter ID 67183913 Counter Name VS.HHO.SuccInterFreqIn Counter Description Number of Successful Incoming Inter-Frequency Hard Handovers for Cell Number of Successful for CS Incoming Inter-Frequency Hard Handovers for Cell Number of Successful for PS Incoming Inter-Frequency Hard Handovers for Cell
73403772
VS.HHO.SuccInterFreqIn.C S VS.HHO.SuccInterFreqIn.P S
73403773
Issue 01 (2013-05-04)
1140
Description
This counter provides the number of successful incoming inter-frequency hard handovers. The measurement is performed in the target cell.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the inter-frequency hard handover, when the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the hard handover succeeds. In this case, the RNC measures the counter in the target cell. Figure 1-498 Successful hard handover procedure
Formula
None
Unit
None
Issue 01 (2013-05-04)
1141
Related Features
Counter Name VS.HHO.SuccInterFreqIn Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.SuccInterFreqIn.C S WRFD-020302 WRFD-020304 Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.SuccInterFreqIn.P S WRFD-020302 WRFD-020304 Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.39 Number of Call Drops Due to Failed Outgoing Intra-Frequency Hard Handovers Counters
Counter ID 67183926 Counter Name VS.HHO.IntraFreqOut.Drop Counter Description Number of Call Drops Due to Failed Outgoing IntraFrequency Hard Handovers for Cell
Description
This counter provides the number of call drops due to failed intra-frequency hard handovers. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the intra-frequency hard handover, after sending the PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC starts the associated timer to wait for the response from the UE. When the RNC receives the PHYSICAL CHANNEL RECONFIGURATION FAILURE message from the UE before the timer expires, the hard handover fails. If the RNC cannot maintain the call connection established before the handover, the RNC may initiate the RRC connection release procedure,
which leads to call drops. In this case, the RNC measures the counter in the best cell where the UE camps on before the intra-frequency hard handover. Figure 1-499 Failed hard handover procedure
The measurement is triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the intra-frequency hard handover, after sending the PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC starts the associated timer to wait for the response from the UE. If the RNC does not receive the response message from the UE before the timer expires, the hard handover fails. If the RNC cannot maintain the call connection established before the intra-frequency hard handover, the RNC may initiate the RRC connection release procedure, which leads to call drops. In this case, the RNC measures the counter in the best cell where the UE camps on before the intra-frequency hard handover. Figure 1-500 Failed hard handover procedure (timer expiry)
Issue 01 (2013-05-04)
1143
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.IntraFreqOut.Drop Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
1.12.11.40 Number of Outgoing Inter-Frequency Hard Handover Attempts in NodeB Counters

Counter ID 67190877 Counter Name VS.HHO.AttInterFreqOut.In traNodeB Counter Description Number of Outgoing InterFrequency Hard Handover Attempts in NodeB for Cell
Description
This counter provides the number of outgoing inter-frequency hard handover attempts in the NodeB. The measurement is performed in the best cell where the UE camps on before the hard handover. In the case of inter-frequency hard handover in the NodeB, the best source cell and the target cell must belong to the same NodeB.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs interfrequency hard handover if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. If the best cell before the hard handover and the target cell belong to the same NodeB and use different frequencies, the RNC measures this counter in the best cell where the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1144
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttInterFreqOut.In traNodeB Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.41 Number of Successful Outgoing Inter-Frequency Hard Handovers in NodeB

Counters
Counter ID 67190878 Counter Name VS.HHO.SuccInterFreqOut. IntraNodeB Counter Description Number of Successful Outgoing Inter-Frequency Hard Handovers in NodeB for Cell
Description
This counter provides the number of successful outgoing inter-frequency hard handovers in the NodeB. The measurement is performed in the best cell where the UE camps on before the hard handover. In the case of inter-frequency hard handover in the NodeB, the best source cell and the target cell must belong to the same NodeB.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs interfrequency hard handover if the criteria of the decision to perform the hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. When the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the hard handover succeeds. If the best cell before the hard handover and the target cell belong to the same NodeB and use different frequencies, the RNC measures this counter in the best cell where the UE camps on before the hard handover. Figure 1-502 Successful hard handover procedure
Issue 01 (2013-05-04)
1146
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccInterFreqOut. IntraNodeB Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.42 Number of Outgoing Inter-Frequency Hard Handovers Attempts Between Different NodeBs of RNC Counters
Counter ID 67190884 Counter Name VS.HHO.AttInterFreqOut.In terNodeBIntraRNC Counter Description Number of Outgoing InterFrequency Hard Handovers Attempts Between Different NodeBs of RNC for Cell
Description
This counter provides the number of outgoing inter-frequency hard handover attempts between different NodeBs of the same RNC. The measurement is performed in the best cell where the UE camps on before the hard handover. In the case of inter-frequency hard handover between different NodeBs of the same RNC, the best source cell and the target cell must belong to different NodeBs of the same RNC.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs interfrequency hard handover if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. If the best cell before the hard handover and target cell belong to different NodeBs of the same RNC and use different frequencies, the RNC measures this counter in the best cell where the UE camps on before the hard handover.
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttInterFreqOut.In terNodeBIntraRNC Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.43 Number of Successful Outgoing Inter-Frequency Hard Handovers Between Different NodeBs of RNC
Counters
Counter ID 67190885 Counter Name VS.HHO.SuccInterFreqOut. InterNodeBIntraRNC Counter Description Number of Successful Outgoing Inter-Frequency Hard Handovers Between Different NodeBs of RNC for Cell
Description
This counter provides the number of successful outgoing inter-frequency hard handovers between different NodeBs of the same RNC. The measurement is performed in the best cell where the UE camps on before the hard handover. In the case of inter-frequency hard handover between different NodeBs of the same RNC, the best source cell and the target cell must belong to different NodeBs of the same RNC.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs interfrequency hard handover if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. When the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the hard handover succeeds. If the best cell before the hard handover and target cell belong to different NodeBs of the same RNC and use different frequencies, the RNC measures this counter in the best cell where the UE camps on before the hard handover. Figure 1-504 Successful hard handover procedure
Issue 01 (2013-05-04)
1149
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccInterFreqOut. InterNodeBIntraRNC Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.44 Number of Outgoing Inter-Frequency Hard Handovers Attempts Between RNCs Counters
Counter ID 67190891 Counter Name VS.HHO.AttInterFreqOut.In terRNC Counter Description Number of Outgoing InterFrequency Hard Handovers Attempts Between RNCs for Cell
Description
This counter provides the number of attempts to perform outgoing inter-frequency hard handovers between the RNCs. The measurement is performed in the best cell where the UE camps on before the hard handover. In the case of inter-frequency hard handover between the RNCs, the source cell and the target cell must be controlled by different RNCs and the handover is performed through the Iur interface between the RNCs.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs interfrequency hard handover if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. If the best cell before the hard handover and the target cell are controlled by the SRNC and the DRNC respectively and use different frequencies, the SRNC measures this counter in the best cell where the UE camps on before the hard handover.
Figure 1-505 Successful hard handover procedure (between different RNCs)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttInterFreqOut.In terRNC Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.45 Number of Successful Outgoing Inter-Frequency Hard Handovers Between RNCs
Issue 01 (2013-05-04)
1151
Counters
Counter ID 67190892 Counter Name VS.HHO.SuccInterFreqOut. InterRNC Counter Description Number of Successful Outgoing Inter-Frequency Hard Handovers Between RNCs for Cell
Description
This counter provides the number of successful outgoing inter-frequency hard handovers between the RNCs. The measurement is performed in the best cell where the UE camps on before the hard handover. In the case of inter-frequency hard handover between the RNCs, the source cell and the target cell must be controlled by different RNCs and the handover is performed through the Iur interface between the RNCs.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. The RNC performs interfrequency hard handover if the criteria of the decision to perform hard handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. When the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the hard handover succeeds. If the best cell before the hard handover and the target cell are controlled by the SRNC and the DRNC respectively and use different frequencies, the SRNC measures this counter in the best cell where the UE camps on before the hard handover. Figure 1-506 Successful hard handover procedure (between different RNCs)
Issue 01 (2013-05-04)
1152
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccInterFreqOut. InterRNC Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.46 Number of Relocation Execution Attempts with Outgoing InterFrequency Hard Handovers Counters
Counter ID 67190898 Counter Name VS.HHO.AttInterFreqRelocExec Counter Description Number of Relocation Execution Attempts with Outgoing Inter-Frequency Hard Handovers for Cell
Description
This counter provides the number of relocation execution attempts with outgoing inter-frequency hard handovers. The measurement is performed in the best cell of the SRNC where the UE camps on before the hard handover. In terms of relocation with inter-frequency hard handover, the relocation execution refers to that the SRNC initiates the reconfiguration for the UE after the successful preparation for the relocation. In this case, the source cell and the target cell involved in the inter-frequency hard handover must be controlled by different RNCs.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the relocation with interfrequency hard handover, after sending the PHYSICAL CHANNEL RECONFIGURATION message to the UE, the SRNC measures the counter in the best cell where the UE camps on before the relocation. In this case, the best cell before the relocation and the target cell must be controlled by the SRNC and the TRNC respectively.
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttInterFreqRelocExec Feature ID WRFD-02060502 Feature Name SRNS Relocation with Hard Handover
1.12.11.47 Number of Successful Relocation Executions with Outgoing InterFrequency Hard Handovers Counters
Counter ID 67190899 Counter Name VS.HHO.SuccInterFreqRelocExec Counter Description Number of Successful Relocation Executions with Outgoing Inter-Frequency Hard Handovers for Cell
Issue 01 (2013-05-04)
1154
Description
This counter provides the number of successful relocation executions with outgoing interfrequency hard handovers. The measurement is performed in the best cell of the SRNC where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point A as shown in the figure, where the PHYSICAL CHANNEL RECONFIGURATION message is used as an example. During the relocation triggered by an inter-frequency hard handover, when the SRNC receives an IU RELEASE COMMAND message with the cause value "Successful Relocation", "Normal Release", or "Network Optimization" from the CN, this counter is increased by one in the best cell that the UE camps on before the relocation if the best cell is controlled by the SRNC. Figure 1-508 Successful SRNC relocation procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccInterFreqRelocExec
Issue 01 (2013-05-04)
Feature Name SRNS Relocation with Hard Handover

1155
1.12.11.48 Number of Outgoing Emergency Blind Handover Attempts Counters

Counter ID 67191694 Counter Name VS.HHO.AttBlindHO Counter Description Number of Outgoing Emergency Blind Handover Attempts for Cell
Description
This counter provides the number of outgoing emergency blind handover attempts initiated by the RNC. The measurement is performed in the best cell where the UE camps on before the handover.
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. After deciding to trigger an emergency blind handover, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. In this case, the RNC measures the counter in the best cell where the UE camps on before the handover. Figure 1-509 Successful hard handover procedure
Issue 01 (2013-05-04)
1156
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttBlindHO Feature ID WRFD-020302 Feature Name Inter Frequency Hard Handover Based on Coverage
1.12.11.49 Number of Successful Outgoing Emergency Blind Hard Handovers Counters

Counter ID 67191695 Counter Name VS.HHO.SuccBlindHO Counter Description Number of Successful Outgoing Emergency Blind Hard Handovers for Cell
Description
This counter provides the number of successful outgoing emergency blind handovers initiated by the RNC. The measurement is performed in the best cell where the UE camps on before the handover.
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the emergency blind handover, when the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the hard handover succeeds. In this case, the RNC measures the counter in the best cell where the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1157
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccBlindHO Feature ID WRFD-020302 Feature Name Inter Frequency Hard Handover Based on Coverage
1.12.11.50 Counters Related to the Number of Handovers Not Performed Due to Inter-Frequency Measurement Expiry
Issue 01 (2013-05-04)
1158
Counters
Counter ID 67193397 Counter Name VS.HHO.InterFreqOut.CS. MeasTimeOut Counter Description Number of Handovers Not Performed Due to CS InterFrequency Measurement Expiry for Cell Number of Handovers Not Performed Due to PS InterFrequency Measurement Expiry for Cell
67193398
VS.HHO.InterFreqOut.PS. MeasTimeOut
Description
These counters provide the number of times that no appropriate inter-frequency cell is detected and hard handover has not performed before the measurement timer expires when the interfrequency measurement is initiated during the inter-frequency handover for CS and PS services. The measurements are performed in the best cell where the UE camps on before the hard handover.
Measurement point
After the inter-frequency measurement is initiated, if inter-frequency handover is not performed before the timer for the inter-frequency measurement expires, the inter-frequency measurement is stopped and the corresponding compressed mode (if enabled) is disabled for the UE. In this case, the RNC measures the related counters in the best cell where the UE camps on before the hard handover.
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.InterFreqOut.CS. MeasTimeOut Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
Issue 01 (2013-05-04)
1159
Counter Name VS.HHO.InterFreqOut.PS. MeasTimeOut
1.12.11.51 Number of Requests for CS and PS Outgoing Inter-Frequency Hard Handovers (Cell) Counters
Counter ID 73403770 Counter Name VS.HHO.AttInterFreqOut.C S VS.HHO.AttInterFreqOut.P S Counter Description Number of Requests for CS Outgoing Inter-Frequency Hard Handovers for Cell Number of Requests for PS Outgoing Inter-Frequency Hard Handovers for Cell
73403771
Description
The measurement items take statistics of the number of requests for Outgoing inter-frequency hard handovers initiated by the RNC according to different domain types.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC decides to execute inter-frequency hard handover for different services and sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE. In this case, the RNC measures the item in the best cell that the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1160
Figure 1-511 Hard handover procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttInterFreqOut.C S Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.AttInterFreqOut.P S WRFD-020302 WRFD-020304 Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
Issue 01 (2013-05-04)
1161
1.12.11.52 Number of Successful for CS and PS Outgoing Inter-Frequency Hard Handovers (Cell) Counters
Counter ID 73403774 Counter Name VS.HHO.SuccInterFreqOut. CS VS.HHO.SuccInterFreqOut. PS Counter Description Number of Successful for CS Outgoing Inter-Frequency Hard Handovers for Cell Number of Successful for PS Outgoing Inter-Frequency Hard Handovers for Cell
73403775
Description
This measurement item takes statistics of the number of successful for CS or PS Outgoing interfrequency hard handovers initiated by the RNC.
Measurement point
The measurement is triggered at point C shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the inter-frequency hard handover for different services, when the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, it indicates that the hard handover succeeds. In this case, the RNC measures the counter in the best cell that the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1162
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccInterFreqOut. CS Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.SuccInterFreqOut. PS WRFD-020302 WRFD-020304 Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
Issue 01 (2013-05-04)
1163
1.12.11.53 Number of Call Drops due to Unsuccessful Outgoing Inter-Frequency Hard Handovers (Cell) Counters
Counter ID 73403776 Counter Name VS.HHO.InterFreqOut.CS. Drop Counter Description Number of CS Call Drops due to Unsuccessful Outgoing Inter-Frequency Hard Handovers for cell Number of PS Call Drops due to Unsuccessful Outgoing Inter-Frequency Hard Handovers for cell
73403777
VS.HHO.InterFreqOut.PS.D rop
Description
This measurement item takes statistics of CS or PS call drops due to unsuccessful inter-frequency hard handovers.
Measurement point
The measurement is triggered at point A shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the inter-frequency hard handover from a cell, the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE and starts a timer to wait for the response from the UE. If the UE returns a PHYSICAL CHANNEL RECONFIGURATION FAILURE message, it indicates that the interfrequency hard handover fails. If the RNC cannot keep the UE connected before the interfrequency hard handover, it initiates a RRC connection release procedure, which results in call drops. In this case, the RNC measures the counter in the best cell that the UE camps on before the inter-frequency hard handover. Figure 1-513 Hard handover procedure (failed operation)
Issue 01 (2013-05-04)
1164
The measurement is triggered at point A shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the inter-frequency hard handover from a cell, the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE and then starts a timer to wait for the response from the UE. If the RNC fails to receive the response from the UE upon expiry of the timer, it indicates that the inter-frequency hard handover fails. If the RNC cannot keep the UE connected before the inter-frequency hard handover, it initiates a RRC connection release procedure, which results in call drops. In this case, the RNC measures the counter in the best cell that the UE camps on before the interfrequency hard handover. Figure 1-514 Hard handover procedure (failed operation for timer expiry)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.InterFreqOut.CS. Drop Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
Issue 01 (2013-05-04)
1165
Counter Name VS.HHO.InterFreqOut.PS.D rop
1.12.11.54 Number of Failed Outgoing Intra-Frequency Hard Handovers Between the RNCs Due to No Response from the UE Counters
Counter ID 73393852 Counter Name VS.HHO.FailIntraFreqOut.I nterRNC.NoReply Counter Description Number of Failed Outgoing Intra-Frequency Hard Handovers Between the RNCs Due to No Response from the UE for Cell
Description
This counter provides the number of failed outgoing intra-frequency hard handovers between the RNCs due to no response from the UE. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the intra-frequency hard handover between the RNCs, after sending the PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC starts the associated timer to wait for the response from the UE. If the RNC does not receive the response message from the UE before the timer expires, the hard handover fails. If the best cell before the hard handover and the target cell are controlled by the SRNC and the DRNC respectively and use the same frequency, the SRNC measures this counter in the best cell where the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1166
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailIntraFreqOut.I nterRNC.NoReply Feature ID WRFD-020301 Feature Name Intra Frequency Hard Handover
1.12.11.55 Counters Related to the Number of Failed Outgoing Inter-Frequency Hard Handovers Between the RNCs for Different Causes Counters
Counter ID 73393853 Counter Name VS.HHO.FailInterFreqOut.I nterRNC.CfgUnsupp Counter Description Number of Failed Outgoing Inter-Frequency Hard Handovers Between the RNCs for Cell (Configuration Unsupported)
1167
Issue 01 (2013-05-04)
Counter ID 73393854
Counter Name VS.HHO.FailInterFreqOut.I nterRNC.PhyChFail
Counter Description Number of Failed Outgoing Inter-Frequency Hard Handovers Between the RNCs for Cell (Physical Channel Failure) Number of Failed Outgoing Inter-Frequency Hard Handovers Between the RNCs for Cell (Incompatible Simultaneous Reconfiguration) Number of Failed Outgoing Inter-Frequency Hard Handovers Between the RNCs for Cell (Invalid Configuration) Number of Failed Outgoing Inter-Frequency Hard Handovers Between the RNCs for Cell (Cell Update Occurred)
73393855
VS.HHO.FailInterFreqOut.I nterRNC.ISR
73393856
VS.HHO.FailInterFreqOut.I nterRNC.InvCfg
73393857
VS.HHO.FailInterFreqOut.I nterRNC.CellUpdt
Description
These counters provide the number of failed outgoing inter-frequency hard handovers between the RNCs due to different failure causes. The measurements are performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurements are triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the interfrequency hard handover between the RNCs, after receiving the PHYSICAL CHANNEL RECONFIGURATION FAILURE message from the UE, the RNC measures the related counters in the best cell where the UE camps on before the hard handover according to the failure cause contained in the message. In this case, the best cell before the hard handover and the target cell must be controlled by the SRNC and the DRNC respectively and use different frequencies.
Issue 01 (2013-05-04)
1168
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailInterFreqOut.I nterRNC.CfgUnsupp Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailInterFreqOut.I nterRNC.PhyChFail WRFD-020302 WRFD-020304 Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailInterFreqOut.I nterRNC.ISR WRFD-020302 WRFD-020304 Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
Issue 01 (2013-05-04)
1169
Counter Name VS.HHO.FailInterFreqOut.I nterRNC.InvCfg
VS.HHO.FailInterFreqOut.I nterRNC.CellUpdt
WRFD-020302 WRFD-020304
Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.56 Number of Failed Outgoing Inter-Frequency Hard Handovers Between the RNCs Due to No Response from the UE Counters
Counter ID 73393858 Counter Name VS.HHO.FailInterFreqOut.I nterRNC.NoReply Counter Description Number of Failed Outgoing Inter-Frequency Hard Handovers Between the RNCs Due to No Response from the UE for Cell
Description
This counter provides the number of failed outgoing inter-frequency hard handovers between the RNCs due to no response from the UE. The measurement is performed in the best cell where the UE camps on before the hard handover.
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. During the inter-frequency hard handover between the RNCs, after sending the PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC starts the associated timer to wait for the response from the UE. If the RNC does not receive the response message from the UE before the timer expires, the hard handover fails. If the best cell before the hard handover and the target cell are controlled by the SRNC and the DRNC respectively and use different frequencies, the RNC measures this counter in the best cell where the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1170
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailInterFreqOut.I nterRNC.NoReply Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.57 Counters Related to the Number of Outgoing Inter-Frequency Hard Handover Attempts
Issue 01 (2013-05-04)
1171
Counters
Counter ID 73393934 Counter Name VS.HHO.AttInterFreqOut.P S.UlBler Counter Description Number of PS InterFrequency Hard Handover Attempts Based on UL BLER for Cell Number of CS InterFrequency Hard Handover Attempts Based on RSCP for Cell Number of CS InterFrequency Hard Handover Attempts Based on EcNo for Cell Number of PS InterFrequency Hard Handover Attempts Based on RSCP for Cell Number of PS InterFrequency Hard Handover Attempts Based on EcNo for Cell Number of CS InterFrequency Hard Handover Attempts Based on UE Transmit Power for Cell Number of PS InterFrequency Hard Handover Attempts Based on UE Transmit Power for Cell Number of CS InterFrequency Hard Handover Attempts Based on DL Transmit Power for Cell Number of PS InterFrequency Hard Handover Attempts Based on DL Transmit Power for Cell Number of CS InterFrequency Hard Handover Attempts Based on Cell Total Transmit Power for Cell
67193401
VS.HHO.AttInterFreqOut.C S.TrigRscp
67193402
VS.HHO.AttInterFreqOut.C S.TrigEcNo
67193403
VS.HHO.AttInterFreqOut.P S.TrigRscp
67193404
VS.HHO.AttInterFreqOut.P S.TrigEcNo
73393935
VS.HHO.AttInterFreqOut.C S.UeTxPwr
73393936
VS.HHO.AttInterFreqOut.P S.UeTxPwr
73393937
VS.HHO.AttInterFreqOut.C S.Tcp
73393938
VS.HHO.AttInterFreqOut.P S.Tcp
73393939
VS.HHO.AttInterFreqOut.C S.TotalTxPwr
Issue 01 (2013-05-04)
1172
Counter ID 73393940
Counter Name VS.HHO.AttInterFreqOut.P S.TotalTxPwr
Counter Description Number of PS InterFrequency Hard Handover Attempts Based on Cell Total Transmit Power for Cell Number of CS InterFrequency Hard Handover Attempts Based on Cell Total Receive Power for Cell Number of PS InterFrequency Hard Handover Attempts Based on Cell Total Receive Power for Cell Number of CS InterFrequency Hard Handover Attempts Based on Code Resources for Cell Number of PS InterFrequency Hard Handover Attempts Based on Code Resources for Cell Number of PS InterFrequency Hard Handover Attempts Based on UL CE for Cell Number of PS InterFrequency Hard Handover Attempts Based on DL CE for Cell Number of CS InterFrequency Hard Handover Attempts Based on DL CE for Cell Number of CS InterFrequency Hard Handover Attempts Based on UL CE for Cell
73393941
VS.HHO.AttInterFreqOut.C S.TotalRxPwr
73393942
VS.HHO.AttInterFreqOut.P S.TotalRxPwr
73393943
VS.HHO.AttInterFreqOut.C S.Code
73393944
VS.HHO.AttInterFreqOut.P S.Code
73424203
VS.HHO.AttInterFreqOut.P S.UlCE
73424243
VS.HHO.AttInterFreqOut.P S.DlCE
73424245
VS.HHO.AttInterFreqOut.C S.DlCE
73424246
VS.HHO.AttInterFreqOut.C S.UlCE
Description
These counters provide the number of outgoing inter-frequency hard handover attempts for CS services or PS services due to different causes in the best cell before the handover.
Issue 01 (2013-05-04)
1173
Measurement point
The measurements can be triggered at point A as shown in the figure, taking the PHYSICAL CHANNEL RECONFIGURATION message as an example. When the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message, the corresponding counter is measured in the best cell that the UE camps on before the handover based on the handover cause and the service type. Note: 1. If an inter-frequency hard handover is triggered due to high BLER, and the transmit power of the UE is also limited. In this case, both the counter related to the number of inter-frequency hard handover attempts based on UL BLER and the counter related to the number of inter-frequency hard handover attempts based on transmit power are measured. 2. The UL and DL power-triggered LDR inter-frequency hard handovers include the UL and DL inter-frequency hard handovers triggered based on the equivalent user number respectively. Figure 1-518 Handover Indication
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttInterFreqOut.P S.UlBler
Issue 01 (2013-05-04)
Feature Name Inter Frequency Hard Handover Based on DL QoS

1174
Counter Name VS.HHO.AttInterFreqOut.C S.TrigRscp VS.HHO.AttInterFreqOut.C S.TrigEcNo VS.HHO.AttInterFreqOut.P S.TrigRscp VS.HHO.AttInterFreqOut.P S.TrigEcNo VS.HHO.AttInterFreqOut.C S.UeTxPwr VS.HHO.AttInterFreqOut.P S.UeTxPwr VS.HHO.AttInterFreqOut.C S.Tcp VS.HHO.AttInterFreqOut.P S.Tcp VS.HHO.AttInterFreqOut.C S.TotalTxPwr
Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS Inter Frequency Hard Handover Based on DL QoS Inter Frequency Hard Handover Based on DL QoS Inter Frequency Hard Handover Based on DL QoS Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold
WRFD-020302
WRFD-020302
WRFD-020302
WRFD-020304 WRFD-020304 WRFD-020304 WRFD-020304 WRFD-020106 WRFD-140217
VS.HHO.AttInterFreqOut.P S.TotalTxPwr
WRFD-020106 WRFD-140217
VS.HHO.AttInterFreqOut.C S.TotalRxPwr
WRFD-020106 WRFD-140217
VS.HHO.AttInterFreqOut.P S.TotalRxPwr
WRFD-020106 WRFD-140217
Issue 01 (2013-05-04)
1175
Counter Name VS.HHO.AttInterFreqOut.C S.Code
Feature Name Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold Inter-Frequency Load Balancing Based on Configurable Load Threshold Inter-Frequency Load Balancing Based on Configurable Load Threshold Inter-Frequency Load Balancing Based on Configurable Load Threshold
VS.HHO.AttInterFreqOut.P S.Code
WRFD-020106 WRFD-140217
VS.HHO.AttInterFreqOut.P S.UlCE
WRFD-020106 WRFD-140217
VS.HHO.AttInterFreqOut.P S.DlCE
WRFD-140217
VS.HHO.AttInterFreqOut.C S.DlCE
WRFD-140217
VS.HHO.AttInterFreqOut.C S.UlCE
WRFD-140217
1.12.11.58 Counters Related to the Number of Successful Outgoing Inter-Frequency Hard Handovers Counters
Counter ID 73393945 Counter Name VS.HHO.SuccInterFreqOut. PS.UlBler Counter Description Number of Successful PS Inter-Frequency Hard Handovers Based on UL BLER for Cell
Issue 01 (2013-05-04)
1176
Counter ID 73404081
Counter Name VS.HHO.SuccInterFreqOut. CS.Rscp
Counter Description Number of Successful CS Inter-Frequency Hard Handovers Based on RSCP for Cell Number of Successful CS Inter-Frequency Hard Handovers Based on EcNo for Cell Number of Successful PS Inter-Frequency Hard Handovers Based on RSCP for Cell Number of Successful PS Inter-Frequency Hard Handovers Based on EcNo for Cell Number of Successful CS Inter-Frequency Hard Handovers Based on UE Transmit Power for Cell Number of Successful PS Inter-Frequency Hard Handovers Based on UE Transmit Power for Cell Number of Successful CS Inter-Frequency Hard Handovers Based on DL Transmit Power for Cell Number of Successful PS Inter-Frequency Hard Handovers Based on DL Transmit Power for Cell Number of Successful CS Inter-Frequency Hard Handovers Based on Cell Total Transmit Power for Cell Number of Successful PS Inter-Frequency Hard Handovers Based on Cell Total Transmit Power for Cell
73404082
VS.HHO.SuccInterFreqOut. CS.EcNo
73404083
VS.HHO.SuccInterFreqOut. PS.Rscp
73404084
VS.HHO.SuccInterFreqOut. PS.EcNo
73393946
VS.HHO.SuccInterFreqOut. CS.UeTxPwr
73393947
VS.HHO.SuccInterFreqOut. PS.UeTxPwr
73393948
VS.HHO.SuccInterFreqOut. CS.Tcp
73393949
VS.HHO.SuccInterFreqOut. PS.Tcp
73393950
VS.HHO.SuccInterFreqOut. CS.TotalTxPwr
73393951
VS.HHO.SuccInterFreqOut. PS.TotalTxPwr
Issue 01 (2013-05-04)
1177
Counter ID 73393952
Counter Name VS.HHO.SuccInterFreqOut. CS.TotalRxPwr
Counter Description Number of Successful CS Inter-Frequency Hard Handovers Based on Cell Total Receive Power for Cell Number of Successful PS Inter-Frequency Hard Handovers Based on Cell Total Receive Power for Cell Number of Successful CS Inter-Frequency Hard Handovers Based on Code Resources for Cell Number of Successful PS Inter-Frequency Hard Handovers Based on Code Resources for Cell Number of Successful PS Inter-Frequency Hard Handovers Based on UL CE for Cell Number of Successful PS Inter-Frequency Hard Handovers Based on DL CE for Cell Number of Successful CS Inter-Frequency Hard Handovers Based on UL CE for Cell Number of Successful CS Inter-Frequency Hard Handovers Based on DL CE for Cell
73393953
VS.HHO.SuccInterFreqOut. PS.TotalRxPwr
73393954
VS.HHO.SuccInterFreqOut. CS.Code
73393955
VS.HHO.SuccInterFreqOut. PS.Code
73424204
VS.HHO.SuccInterFreqOut. PS.UlCE
73424244
VS.HHO.SuccInterFreqOut. PS.DlCE
73424247
VS.HHO.SuccInterFreqOut. CS.UlCE
73424248
VS.HHO.SuccInterFreqOut. CS.DlCE
Description
These counters provide the number of successful outgoing inter-frequency hard handovers for CS services or PS services in the best cell before the handover due to different causes.
Measurement point
Take the PHYSICAL CHANNEL RECONFIGURATION message as an example, the measurement can be triggered at point B as shown in the figure. After determining interfrequency hard handovers, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. When receiving from the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message, the RNC measures the counter measured in the
best cell that the UE camps on before the inter-frequency hard handover based on the handover cause and the service type. Note: 1. If an inter-frequency hard handover is triggered due to high BLER and the transmit power of the UE is also limited, the counter measuring the number of successful inter-frequency hard handovers based on UL BLER and the counter measuring the number of successful inter-frequency hard handovers based on transmit power are measured. 2. Inter-frequency hard handovers include those that are involved in the LDR or CLB triggered by the high power or large number of equivalent UEs. However, the RNC regards such handovers as being triggered by high power. Figure 1-519 Handover Indication
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccInterFreqOut. PS.UlBler Feature ID WRFD-020304 Feature Name Inter Frequency Hard Handover Based on DL QoS
Issue 01 (2013-05-04)
1179
Counter Name VS.HHO.SuccInterFreqOut. CS.Rscp VS.HHO.SuccInterFreqOut. CS.EcNo VS.HHO.SuccInterFreqOut. PS.Rscp VS.HHO.SuccInterFreqOut. PS.EcNo VS.HHO.SuccInterFreqOut. CS.UeTxPwr VS.HHO.SuccInterFreqOut. PS.UeTxPwr VS.HHO.SuccInterFreqOut. CS.Tcp VS.HHO.SuccInterFreqOut. PS.Tcp VS.HHO.SuccInterFreqOut. CS.TotalTxPwr
Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS Inter Frequency Hard Handover Based on DL QoS Inter Frequency Hard Handover Based on DL QoS Inter Frequency Hard Handover Based on DL QoS Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold
WRFD-020302
WRFD-020302
WRFD-020302
WRFD-020304 WRFD-020304 WRFD-020304 WRFD-020304 WRFD-020106 WRFD-140217
VS.HHO.SuccInterFreqOut. PS.TotalTxPwr
WRFD-020106 WRFD-140217
VS.HHO.SuccInterFreqOut. CS.TotalRxPwr
WRFD-020106 WRFD-140217
VS.HHO.SuccInterFreqOut. PS.TotalRxPwr
WRFD-020106 WRFD-140217
Issue 01 (2013-05-04)
1180
Counter Name VS.HHO.SuccInterFreqOut. CS.Code
Feature Name Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold Load Reshuffling Inter-Frequency Load Balancing Based on Configurable Load Threshold Inter-Frequency Load Balancing Based on Configurable Load Threshold Inter-Frequency Load Balancing Based on Configurable Load Threshold Inter-Frequency Load Balancing Based on Configurable Load Threshold
VS.HHO.SuccInterFreqOut. PS.Code
WRFD-020106 WRFD-140217
VS.HHO.SuccInterFreqOut. PS.UlCE
WRFD-020106 WRFD-140217
VS.HHO.SuccInterFreqOut. PS.DlCE
WRFD-140217
VS.HHO.SuccInterFreqOut. CS.UlCE
WRFD-140217
VS.HHO.SuccInterFreqOut. CS.DlCE
WRFD-140217
1.12.11.59 Number of Inter-Frequency Hard Handover Attempts When only Signaling Exists for Cell Counters
Counter ID 73425014 Counter Name VS.HHO.AttInterFreqOut.Si g Counter Description Number of Inter-Frequency Hard Handover Attempts When only Signaling Exists for Cell
Issue 01 (2013-05-04)
1181
Description
This counter provides the number of outgoing inter-frequency hard handover attempts in the best cell before the handover when the UE has only signalling.
Measurement point
The measurement is triggered at point B as shown in the figure, the procedure shown in the figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an example, when the RNC decides to execute single-signaling inter-frequency hard handover and sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE. In this case, this counter is increased by one in the best cell where the UE is camping before the inter-frequency hard handover. Figure 1-520 Hard handover procedure (successful operation)
Formula
None
Unit
None
Issue 01 (2013-05-04)
1182
Related Features
Counter Name VS.HHO.AttInterFreqOut.Si g Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.60 Number of Successful Inter-Frequency Hard Handover Attempts When only Signaling Exists for Cell Counters
Counter ID 73425015 Counter Name VS.HHO.SuccInterFreqOut. Sig Counter Description Number of Successful InterFrequency Hard Handover Attempts When only Signaling Exists for Cell
Description
This counter provides the number of successful outgoing inter-frequency hard handover in the best cell before the handover when the UE has only signalling.
Measurement point
The measurement is triggered at point C as shown in the figure, the procedure shown in the figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an example, when the RNC decides to execute single-signaling inter-frequency hard handover and sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE.In this case,this counter is increased by one in the best cell where the UE is camping before the interfrequency hard handover.
Issue 01 (2013-05-04)
1183
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccInterFreqOut. Sig Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.11.61 Number of Outgoing Macro & Micro Joint Inter-frequency Handover Attempts in PS Domain for Cell
Issue 01 (2013-05-04)
1184
Counters
Counter ID 73425831 Counter Name VS.HHO.AttInterFreqOut.P S.CoMacroMicro Counter Description Number of Outgoing Macro & Micro Joint Interfrequency Handover Attempts in PS Domain for Cell
Description
This counter measures the number of outgoing macro & micro joint inter-frequency handover attempts in the PS domain in a cell.
Measurement point
In the figure 1, Both SHO and Non-SHO areas are macro & micro joint inter-frequency handover area. Figure 1-522 Macro and micro joint inter-frequency handover area
The measurement is triggered at point A as shown in Figure 2. When the RNC determines that a UE is in the Macro & Micro joint inter-frequency handover area, it triggers a Macro & Micro joint inter-frequency handover and sends the UE a PHYSICAL CHANNEL RECONFIGURATION message. In this case, the counter is measured in the best cell where the UE camps on before the hard handover.
Issue 01 (2013-05-04)
1185
Figure 1-523 Successful physical channel reconfiguration procedure
This measurement is triggered at point A in figure 3. The RNC determines that a UE is in the macro & micro joint inter-frequency handover area and triggers a macro & micro joint interfrequency handover. This counter is increased by one in the serving cell where the UE camps each time the RNC sends a TRANSPORT CHANNEL RECONFIGURATION message to the UE. Figure 1-524 Successful transport channel reconfiguration procedure
This measurement is triggered at point A in figure 4. The RNC determines that a UE is in the macro & micro joint inter-frequency handover area and triggers a macro & micro joint interfrequency handover. This counter is increased by one in the serving cell where the UE camps each time the RNC sends a RADIO BEARER RECONFIGURATION message to the UE.
Issue 01 (2013-05-04)
1186
Figure 1-525 Successful radio bearer reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttInterFreqOut.P S.CoMacroMicro Feature ID WRFD-150201 WRFD-15020102 Feature Name Macro & Micro Co-carrier Uplink Interference Control Macro & Micro Joint Interfrequency Handover
1.12.11.62 Number of Successful Outgoing Macro & Micro Joint Inter-frequency Handovers in PS Domain for Cell Counters
Counter ID 73425832 Counter Name VS.HHO.SuccInterFreqOut. PS.CoMacroMicro Counter Description Number of Successful Outgoing Macro & Micro Joint Inter-frequency Handovers in PS Domain for Cell
1187
Issue 01 (2013-05-04)
Description
This counter measures the number of successful outgoing macro & micro joint inter-frequency handovers in the PS domain in a cell.
Measurement point
This measurement is triggered at point B in figure 2. The RNC determines that a UE is in the macro & micro joint inter-frequency handover area and triggers a macro & micro joint interfrequency handover. This counter is increased by one in the serving cell where the UE camps each time the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE in the target cell after sending a PHYSICAL CHANNEL RECONFIGURATION message to the UE. Figure 1-527 Successful physical channel reconfiguration procedure
Issue 01 (2013-05-04)
1188
This measurement is triggered at point B in figure 3. The RNC determines that a UE is in the macro & micro joint inter-frequency handover area and triggers a macro & micro joint interfrequency handover. This counter is increased by one in the serving cell where the UE camps before the handover each time the RNC receives a TRANSPORT CHANNEL RECONFIGURATION COMPLETE in the target cell after sending a TRANSPORT CHANNEL RECONFIGURATION message to the UE. Figure 1-528 Successful transport channel reconfiguration procedure
This measurement is triggered at point B in figure 4. The RNC determines that a UE is in the macro & micro joint inter-frequency handover area and triggers a macro & micro joint interfrequency handover. This counter is increased by one in the serving cell where the UE camps before the handover each time the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE in the target cell after sending a RADIO BEARER RECONFIGURATION message to the UE. Figure 1-529 Successful radio bearer reconfiguration procedure
Issue 01 (2013-05-04)
1189
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccInterFreqOut. PS.CoMacroMicro Feature ID WRFD-150201 WRFD-15020102 Feature Name Macro & Micro Co-carrier Uplink Interference Control Macro & Micro Joint Interfrequency Handover
1.12.12 HSDPA Measurement per cell(HSDPA.Cell)

Overview
High Speed Downlink Packet Access (HSDPA) is a DL high speed data solution of WCDMA. The HSDPA system has the following features: Adopting 2 ms short frame, Adopting link adaptive technologies such as HARQ and AMC on physical layer, Introducing high-order modulation to increase spectrum utilization, Scheduling between UEs by code division and time division. The above technologies can implement the following: Increasing DL peak data rate and shortening service delay, Increasing DL throughput of such services as receiving Email and browsing on WEB and Increasing DL capacity by effectively using DL code resource and power resource. The function subset HSDPA Measurement(Cell) is used to measure the related HSDPA service on the basis of Cell. This function subset contains counters related to the number of successful or RRC connection setups, normal or abnormal RRC connection release, handovers, and state transitions for HSDPA users of different capability levels, service delay, and throughput.
Counters
Counter ID 67189830 Counter Name VS.HSDPA.D2H.S ucc Counter Description Number of Successful Channel Conversions from DCH to HS-DSCH for HSDPA Service for Cell Original Release Earlier than V900R011
Issue 01 (2013-05-04)
1190
Counter ID 67189831
Counter Name VS.HSDPA.F2H.Su cc
Counter Description Number of Successful Channel Conversions from FACH to HS-DSCH for HSDPA Service for Cell Number of Successful Channel Conversions from HS-DSCH to DCH for HSDPA Service for Cell Number of Successful Channel Conversions from HS-DSCH to FACH for HSDPA Service for Cell Number of Successful HSDPA MAC-d Flow Establishments for Cell Average Number of HSDPA UEs in a Cell Average Number of MAC-d Flows in a Cell Mean Downlink Throughput of single HSDPA MAC-d Flows for Cell Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow for Cell Mean Downlink Throughput of HSDPA MAC-d Flow of BE Service for Golden Subscriber for Cell
67189832
VS.HSDPA.H2D.S ucc
67189833
VS.HSDPA.H2F.Su cc
67189834
VS.HSDPA.MACD .SuccSetup
67202932
VS.HSDPA.UE.Me an.Cell VS.HSDPA.MACD .Mean.Cell VS.HSDPA.MeanChThroughput
67202941
67202894
67189840
VS.HSDPA.MeanC hThroughput.TotalBytes
67204510
VS.HSDPA.MeanGoldenBeChThroughput
Issue 01 (2013-05-04)
1191
Counter ID 67194867
Counter Name VS.HSDPA.MeanG oldenBeChThroug hput.TotalBytes
Counter Description Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow of BE Service for Golden Subscriber for Cell Mean Downlink Throughput of HSDPA MAC-d Flow of BE Service for Silver Subscriber for Cell Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow of BE Service for Silver Subscriber for Cell Mean Downlink Throughput of HSDPA MAC-d Flow of BE Service for Copper Subscriber for Cell Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow of BE Service for Copper Subscriber for Cell Number of Channel Conversion Attempts from HSDSCH to DCH for HSDPA Service for Cell Number of Channel Conversion Attempts from DCH to HS-DSCH for HSDPA Service for Cell
67204511
VS.HSDPA.MeanSilverBeChThroughput
67194869
VS.HSDPA.MeanS ilverBeChThrough put.TotalBytes
67204512
VS.HSDPA.MeanCopperBeChThroughput
67194871
VS.HSDPA.MeanC opperBeChThroug hput.TotalBytes
67190690
VS.HSDPA.H2D.A tt
67190693
VS.HSDPA.D2H.A tt
Issue 01 (2013-05-04)
1192
Counter ID 67190696
Counter Name VS.HSDPA.F2H.At t
Counter Description Number of Channel Conversion Attempts from FACH to HS-DSCH for HSDPA Service for Cell Number of Channel Conversion Attempts from HSDSCH to FACH for HSDPA Service for Cell Number of IntraRNC HSDPA Serving Cell Change Attempts for Cell Number of IntraRNC HSDPA Serving Cell Change Success in RNC for Cell Number of InterRNC HSDPA Serving Cell Change Attempts for Cell Number of InterRNC HSDPA Serving Cell Change Success for Cell Number of InterRNC HSDPA Hard Handover Attempts Without Channel Change for Cell Number of Successful InterRNC HSDPA Hard Handovers Without Channel Change for Cell
67190697
VS.HSDPA.H2F.At t
67190698
VS.HSDPA.SHO.S ervCellChg.AttOut
67190699
VS.HSDPA.SHO.S ervCellChg.SuccOut
67195481
VS.HSDPA.SHO.S ervCellChg.AttOutIur VS.HSDPA.SHO.S ervCellChg.SuccOutIur VS.HSDPA.HHO. H2H.AttOutIur
67195482
67195483
67195484
VS.HSDPA.HHO. H2H.SuccOutIur
Issue 01 (2013-05-04)
1193
Counter ID 67190700
Counter Name VS.HSDPA.HHO. H2H.AttOutIntraFreq
Counter Description Number of IntraFrequency HSDPA Hard Handover Attempts Without Channel Change for Cell Number of Successful IntraFrequency HSDPA Hard Handovers Without Channel Change for Cell Number of InterFrequency HSDPA Hard Handover Attempts Without Channel Change for Cell Number of Successful InterFrequency HSDPA Hard Handovers Without Channel Change for Cell Number of IntraFrequency H2D Hard Handover Attempts for Cell Number of Successful IntraFrequency H2D Hard Handovers for Cell Number of InterFrequency H2D Hard Handover Attempts for Cell Number of Successful InterFrequency H2D Hard Handovers for Cell
67190701
VS.HSDPA.HHO. H2H.SuccOutIntraFreq
67190702
VS.HSDPA.HHO. H2H.AttOutInterFreq
67190703
VS.HSDPA.HHO. H2H.SuccOutInterFreq
67191157
VS.HSDPA.HHO. H2D.AttOutIntraFreq VS.HSDPA.HHO. H2D.SuccOutIntraFreq
67191158
67191159
VS.HSDPA.HHO. H2D.AttOutInterFreq VS.HSDPA.HHO. H2D.SuccOutInterFreq
67191160
Issue 01 (2013-05-04)
1194
Counter ID 67190704
Counter Name VS.HSDPA.RAB.A ttEstab VS.HSDPA.RAB.A ttEstab.BE.Golden
Counter Description Number of HSDPA RAB Establishment Attempts for Cell Number of HSDPA RAB Establishment Attempts of BE Service for Golden Level User for Cell Number of HSDPA RAB Establishment Attempts of BE Service for Silver Level User for Cell Number of HSDPA RAB Establishment Attempts of BE Service for Copper Level User for Cell Number of Successful HSDPA RAB Establishments for Cell Number of Successful HSDPA RAB Establishments of BE Service for Golden Level User for Cell Number of Successful HSDPA RAB Establishments of BE Service for Silver Level User for Cell Number of Successful HSDPA RAB Establishments of BE Service for Copper Level User for Cell Number of HSDPA RAB Releases Due to User Inactivity for Cell
67195507
67195508
VS.HSDPA.RAB.A ttEstab.BE.Silver
67195509
VS.HSDPA.RAB.A ttEstab.BE.Copper
67190705
VS.HSDPA.RAB.S uccEstab
67195510
VS.HSDPA.RAB.S uccEstab.BE.Golden
67195511
VS.HSDPA.RAB.S uccEstab.BE.Silver
67195512
VS.HSDPA.RAB.S uccEstab.BE.Copper
67191161
VS.HSDPA.RAB.N ormRel.UsrInact
Issue 01 (2013-05-04)
1195
Counter ID 67191162
Counter Name VS.HSDPA.RAB.A bnormRel VS.HSDPA.RAB.A bnormRel.RF
Counter Description Number of HSDPA RABs Abnormal Released for Cell Number of HSDPA RABs Abnormal Released Due to RF Cause for Cell Number of HSDPA RABs Normal Released for Cell Maximum Number of HSDPA UEs in a Cell number of InterRNC H2D Hard Handover Attempts for Cell Number of Successful InterRNC H2D Hard Handovers for Cell Number of HSDPA 64QAM RAB Setup Requests for cell Number of HSDPA 64QAM RABs Setup Successfully for cell Number of HSDPA 64QAM RABs Abnormal Released for cell Number of HSDPA 64QAM RABs Normal Released for Cell Number of HSDPA MIMO RABs Setup Request for Cell Number of HSDPA MIMO RABs Setup Successfully for cell
67191163
67191164
VS.HSDPA.RAB.N ormRel VS.HSDPA.UE.Ma x.Cell VS.HSDPA.HHO. H2D.AttOutIur
73403763
73403764
V900R012
73403765
VS.HSDPA.HHO. H2D.SuccOutIur
V900R012
73403817
VS.HSDPA.RAB. 64QAM.AttEstab VS.HSDPA.RAB. 64QAM.SuccEstab VS.HSDPA.RAB.A bnormRel.64QAM
V900R012
73403818
V900R012
73403819
V900R012
73403820
VS.HSDPA.RAB.N ormRel.64QAM
V900R012
73403821
VS.HSDPA.RAB. MIMO.AttEstab VS.HSDPA.RAB. MIMO.SuccEstab
V900R012
73403822
V900R012
Issue 01 (2013-05-04)
1196
Counter ID 73403823
Counter Name VS.HSDPA.RAB.N ormRel.MIMO
Counter Description Number of HSDPA MIMO RABs Normal Released for cell Number of HSDPA MIMO+64QAM RABs Setup Request for cell Number of HSDPA MIMO+64QAM RABs Setup Successfully for cell Number of HSDPA MIMO+64QAM RABs Abnormal Released for cell Number of HSDPA MIMO+64QAM RABs Normal Released for cell Number of DCHSDPA RAB Setup Requests in the primary carrier of DC-HSDPA counted for cell Number of DCHSDPA RABs Setup Successfully in the primary carrier of DC-HSDPA counted for cell Number of DCHSDPA RABs Abnormal Released in the primary carrier of DC counted for Cell(including RF Cause) Number of DCHSDPA RABs Normal Released in the primary carrier of DC counted for Cell
73403824
VS.HSDPA.RAB. MIMO64QAM.Att Estab VS.HSDPA.RAB. MIMO64QAM.Suc cEstab VS.HSDPA.RAB.A bnormRel.MIMO6 4QAM VS.HSDPA.RAB.N ormRel.MIMO64Q AM VS.HSDPA.RAB.D C.AttEstab
V900R012
73403825
V900R012
73403826
V900R012
73403827
V900R012
73403828
V900R012
73403829
VS.HSDPA.RAB.D C.SuccEstab
V900R012
73403830
VS.HSDPA.RAB.A bnormRel.DC
V900R012
73403831
VS.HSDPA.RAB.N ormRel.DC
V900R012
Issue 01 (2013-05-04)
1197
Counter ID 73403832
Counter Name VS.HSDPA.RAB.A bnormRel.MIMO
Counter Description Number of HSDPA MIMO RABs Abnormal Released for cell(Including RF Cause) Average Number of HSDPA UEs with Category 1-6 in a Cell Maximum Number of HSDPA UEs with Category 1-6 in a Cell Average Number of HSDPA UEs with Category 7-10 in a Cell Maximum Number of HSDPA UEs with Category 7-10 in a Cell Average Number of HSDPA UEs with Category 11-12 in a Cell Maximum Number of HSDPA UEs with Category 11-12 in a Cell Average Number of HSDPA UEs with Category 13-14 in a Cell Maximum Number of HSDPA UEs with Category 13-14 in a Cell Average Number of HSDPA UEs with Category 15-16 in a Cell
67204259
VS.HSDPA.UE.Me an.CAT1.6
V900R012
67193578
VS.HSDPA.UE.Ma x.CAT1.6
V900R012
67204260
V900R012
67193581
V900R012
67204261
V900R012
67193584
V900R012
67204262
V900R012
67193587
V900R012
67204263
V900R012
Issue 01 (2013-05-04)
1198
Counter ID 67193590
Counter Name VS.HSDPA.UE.Ma x.CAT15.16
Counter Description Maximum Number of HSDPA UEs with Category 15-16 in a Cell Average Number of HSDPA UEs with Category 17-20 in a Cell Maximum Number of HSDPA UEs with Category 17-20 in a Cell Average Number of HSDPA UEs with Category 21-24 in a Cell Maximum Number of HSDPA UEs with Category 21-24 in a Cell Number of HSDPA MAC-d Flow Establishment Requests for Cell Number of Failed HSDPA Service Establishments Due to DL Power Insufficiency for Cell Number of Failed HSDPA Service Establishments Due to DL Iub Bandwidth Insufficiency for Cell Average downlink throughput of the Traffic PS Conversational beared on HSDSCH for cell
67204264
V900R012
67193593
V900R012
67204265
V900R012
67193596
V900R012
73393828
VS.HSDPA.MACD .AttSetup
V900R012
73393830
VS.HSDPA.RAB.F ailEstab.DLPower. Cong
V900R012
73393831
VS.HSDPA.RAB.F ailEstab.DLIUBBa nd.Cong
V900R012
73410484
VS.PS.Conv.Kbps. HSDSCH
V900R012
Issue 01 (2013-05-04)
1199
Counter ID 73393912
Counter Name VS.PS.Conv.Traffi c.HSDSCH
Counter Description Number of downlink bytes of Transport Blocks of Traffic PS Conversational beared on HSDSCH for cell Average Number of 64QAM UEs in a Cell Average Number of MIMO UEs in a Cell Average Number of MIMO+64QAM UEs in a Cell Average number of DC-HSDPA UEs in anchor carrier in a Cell Average number of DC-HSDPA UEs in supplementary carrier in a Cell Number of Outgoing DRD Attempts for HSDPA Users Through Intelligent User Recognition for Cell Number of Successful Outgoing DRDs for HSDPA Users Through Intelligent User Recognition for Cell Number of Incoming DRD Attempts for HSDPA Users Through Intelligent User Recognition for Cell
73410491
VS.HSDPA. 64QAM.UE.Mean. Cell VS.HSDPA.MIMO .UE.Mean.Cell VS.HSDPA.MIMO 64QAM.UE.Mean. Cell VS.HSDPA.DC.PR IM.UE.Mean.Cell
V900R012
73410492 73410493
V900R012 V900R012
73410508
V900R012
73410509
VS.HSDPA.DC.SE C.UE.Mean.Cell
V900R012
73421686
VS.HSDPA.DRD.A ttOut.Intelligence
V900R012
73421687
VS.HSDPA.DRD.S uccOut.Intelligence
V900R012
73421688
VS.HSDPA.DRD.A ttIn.Intelligence
V900R012
Issue 01 (2013-05-04)
1200
Counter ID 73421689
Counter Name VS.HSDPA.DRD.S uccIn.Intelligence
Counter Description Number of Successful Incoming DRDs for HSDPA Users Through Intelligent User Recognition for Cell Number of RABs Abnormally Released for PS HSDPA Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell Maximum Number of HSDPA UEs with Category 25-28 in a Cell Average Number of HSDPA UEs with Category 25-28 in a Cell Number of DCHSDPA+MIMO RAB Setup Requests in the Primary Carrier of DCHSDPA for Cell Number of Successful DCHSDPA+MIMO RAB Setups in the Primary Carrier of DC-HSDPA for cell Number of Normal DC-HSDPA+MIMO RAB Releases in the Primary Carrier of DC-HSDPA for cell
73422167
VS.HSDPA.RAB.A bnormRel.H2P
V900R012
73423377
V900R013
73441138
V900R013
73423378
VS.HSDPA.RAB.D CMIMO.AttEstab
V900R013
73423379
VS.HSDPA.RAB.D CMIMO.SuccEsta b
V900R013
73423380
VS.HSDPA.RAB.D CMIMO.NormRel
V900R013
Issue 01 (2013-05-04)
1201
Counter ID 73423381
Counter Name VS.HSDPA.RAB.D CMIMO.AbnormR el
Counter Description Number of Abnormal DCHSDPA+MIMO RAB Releases in the Primary Carrier of DC-HSDPA for cell Mean Throughput on HSDPA MAC-d Flow for Cell (Excluding the Data of Low-Traffic Users) Number of Bytes Sent on HSDPA MAC-d Flow for Cell (Excluding the Bytes of Low-Traffic Users) Average Number of Free HSDPA Users in a Cell Maximum Number of Free HSDPA Users in a Cell Number of Serving Cell Change Attempts Triggered by Unbalanced Iub Resources for Cell Number of Successful Serving Cell Changes Triggered by Unbalanced Iub Resources for Cell Average Number of 4C-HSDPA UEs Using This Cell as the Primary Carrier Cell
73441141
VS.HSDPA.MeanC hThrouput.HighLoad
V900R013
73423462
VS.HSDPA.Traffic. HighLoad
V900R013
73441142
VS.HSDPA.UE.Me an.Cell.Free VS.HSDPA.UE.Ma x.Cell.Free VS.HSDPA.SHO.I ubBasedServCellC hg.AttOut
V900R013
73423469
V900R013
73423900
V900R013
73423901
VS.HSDPA.SHO.I ubBasedServCellC hg.SuccOut
V900R013
73425884
VS.HSDPA. 4C.PRIM.UE.Mea n.Cell
V900R015
Issue 01 (2013-05-04)
1202
Counter ID 73425887
Counter Name VS.HSDPA. 3C.PRIM.UE.Mea n.Cell
Counter Description Average Number of 3C-HSDPA UEs Using This Cell as the Primary Carrier Cell Average Number of 4C-HSDPA/DBHSDPA/DCHSDPA UEs Using This Cell as the Secondary Carrier Cell Average Number of DB-HSDPA UEs Using This Cell as the Primary Carrier Cell Number of Abnormal RAB Releases for Cell During State Transition of DCHSDPA UEs to CELL/URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of HSDPA+64QAM UEs to CELL/ URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of MIMO UEs to CELL/ URA_PCH
73425890
VS.HSDPA.MC.SE C.UE.Mean.Cell
V900R015
73425893
VS.HSDPA.DB.PR IM.UE.Mean.Cell
V900R015
73425928
VS.HSDPA.RAB.A bnormRel.DC2P
V900R015
73425929
VS.HSDPA.RAB.A bnormRel. 64QAM2P
V900R015
73425930
VS.HSDPA.RAB.A bnormRel.MIMO2 P
V900R015
Issue 01 (2013-05-04)
1203
Counter ID 73425931
Counter Name VS.HSDPA.RAB.A bnormRel.DCMIM O2P
Counter Description Number of Abnormal RAB Releases for Cell During State Transition of DCHSDPA+MIMO UEs to CELL/ URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of MIMO +64QAM UEs to CELL/URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of 3CHSDPA UEs to CELL/URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of 3CHSDPA+MIMO UEs to CELL/ URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of 4CHSDPA UEs to CELL/URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of 4CHSDPA+MIMO UEs to CELL/ URA_PCH
73425932
VS.HSDPA.RAB.A bnormRel.MIMO6 4QAM2P
V900R015
73425933
VS.HSDPA.RAB.A bnormRel.3C2P
V900R015
73425934
VS.HSDPA.RAB.A bnormRel. 3CMIMO2P
V900R015
73425935
VS.HSDPA.RAB.A bnormRel.4C2P
V900R015
73425936
VS.HSDPA.RAB.A bnormRel. 4CMIMO2P
V900R015
Issue 01 (2013-05-04)
1204
Counter ID 73425937
Counter Name VS.HSDPA.RAB.A bnormRel.DB2P
Counter Description Number of Abnormal RAB Releases for Cell During State Transition of DBHSDPA UEs to CELL/URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of DBHSDPA+MIMO UEs to CELL/ URA_PCH Number of Normal RAB Releases of DC-HSDPA UEs for Cell (All Scenarios) Number of Normal RAB Releases of HSDPA+64QAM UEs for Cell (All Scenarios) Number of Normal RAB Releases of HSDPA+MIMO UEs for Cell (All Scenarios) Number of Normal RAB Releases of DC-HSDPA+MIMO UEs for Cell (All Scenarios) Number of Normal RAB Releases of HSDPA MIMO +64QAM UEs for Cell (All Scenarios) Number of Normal RAB Releases of 3CHSDPA UEs for Cell (All Scenarios)
73425938
VS.HSDPA.RAB.A bnormRel.DBMIM O2P
V900R015
73425939
VS.HSDPA.RAB.N ormRel.DC.All
V900R015
73425940
VS.HSDPA.RAB.N ormRel. 64QAM.All
V900R015
73425941
VS.HSDPA.RAB.N ormRel.MIMO.All
V900R015
73425942
VS.HSDPA.RAB.N ormRel.DCMIMO. All
V900R015
73425943
VS.HSDPA.RAB.N ormRel.MIMO64Q AM.All
V900R015
73425944
VS.HSDPA.RAB.N ormRel.3C.All
V900R015
Issue 01 (2013-05-04)
1205
Counter ID 73425945
Counter Name VS.HSDPA.RAB.N ormRel. 3CMIMO.All
Counter Description Number of Normal RAB Releases of 3CHSDPA+MIMO UEs for Cell (All Scenarios) Number of Normal RAB Releases of 4CHSDPA UEs for Cell (All Scenarios) Number of Normal RAB Releases of 4CHSDPA+MIMO UEs for Cell (All Scenarios) Number of Normal RAB Releases of DB-HSDPA UEs for Cell (All Scenarios) Number of Normal RAB Releases of DB-HSDPA+MIMO UEs for Cell (All Scenarios) Average number of Category 29 HSDPA users in a cell Maximum number of Category 29 HSDPA users in a cell Average number of Category 30 HSDPA users in a cell Maximum number of Category 30 HSDPA users in a cell Average number of Category 31 HSDPA users in a cell Maximum number of Category 31 HSDPA users in a cell
73425946
VS.HSDPA.RAB.N ormRel.4C.All
V900R015
73425947
VS.HSDPA.RAB.N ormRel. 4CMIMO.All
V900R015
73425948
VS.HSDPA.RAB.N ormRel.DB.All
V900R015
73425949
VS.HSDPA.RAB.N ormRel.DBMIMO. All
V900R015
73426132
VS.HSDPA.UE.Me an.CAT29 VS.HSDPA.UE.Ma x.CAT29 VS.HSDPA.UE.Me an.CAT30 VS.HSDPA.UE.Ma x.CAT30 VS.HSDPA.UE.Me an.CAT31 VS.HSDPA.UE.Ma x.CAT31
V900R015
73426133
V900R015
73426136
V900R015
73426137
V900R015
73426140
V900R015
73426141
V900R015
Issue 01 (2013-05-04)
1206
Counter ID 73426144
Counter Name VS.HSDPA.UE.Me an.CAT32 VS.HSDPA.UE.Ma x.CAT32 VS.HSDPA.SRBoH .UE.Mean.Cell
Counter Description Average number of Category 32 HSDPA users in a cell Maximum number of Category 32 HSDPA users in a cell Average number of users capable of the SRB over HSDPA feature in a cell Number of RAB Setup Attempts for Cell When 3CHSDPA with MIMO Applied Number of Successful RAB Setups for Cell When 3C-HSDPA with MIMO Applied Number of Abnormally Released RABs for Cell When 3CHSDPA with MIMO Applied (RF Exceptions Considered) Number of Normally Released RABs for Cell When 3CHSDPA with MIMO Applied Number of RAB Setup Attempts for Cell When 3CHSDPA Applied Number of Successful RAB Setups for Cell When 3C-HSDPA Applied
73426145
V900R015
73426170
V900R015
73426094
VS.HSDPA.RAB. 3CMIMO.AttEstab
V900R015
73426095
VS.HSDPA.RAB. 3CMIMO.SuccEsta b
V900R015
73426096
VS.HSDPA.RAB.A bnormRel. 3CMIMO
V900R015
73426097
VS.HSDPA.RAB.N ormRel.3CMIMO
V900R015
73426098
VS.HSDPA.RAB. 3C.AttEstab
V900R015
73426099
VS.HSDPA.RAB. 3C.SuccEstab
V900R015
Issue 01 (2013-05-04)
1207
Counter ID 73426100
Counter Name VS.HSDPA.RAB.A bnormRel.3C
Counter Description Number of Abnormally Released RABs for Cell When 3CHSDPA Applied (RF Exceptions Considered) Number of Normally Released RABs for Cell When 3CHSDPA Applied Number of RAB Setup Attempts for Cell Where 4CHSDPA with MIMO Applied Number of Successful RAB Setups for Cell When 4C-HSDPA with MIMO Applied Number of Abnormally Released RABs for Cell When 4CHSDPA with MIMO Applied (RF Exceptions Considered) Number of Normally Released RABs for Cell When 4CHSDPA with MIMO Applied Number of RAB Setup Attempts for Cell When DBHSDPA with MIMO Applied Number of Successful RAB Setups for Cell When DB-HSDPA with MIMO Applied
73426101
VS.HSDPA.RAB.N ormRel.3C
V900R015
73426102
VS.HSDPA.RAB. 4CMIMO.AttEstab
V900R015
73426103
VS.HSDPA.RAB. 4CMIMO.SuccEsta b
V900R015
73426104
VS.HSDPA.RAB.A bnormRel. 4CMIMO
V900R015
73426105
VS.HSDPA.RAB.N ormRel.4CMIMO
V900R015
73426106
VS.HSDPA.RAB.D BMIMO.AttEstab
V900R015
73426107
VS.HSDPA.RAB.D BMIMO.SuccEstab
V900R015
Issue 01 (2013-05-04)
1208
Counter ID 73426108
Counter Name VS.HSDPA.RAB.A bnormRel.DBMIM O
Counter Description Number of Abnormal Released RABs for Cell When DB-HSDPA with MIMO Applied (RF Exceptions Considered) Number of Normally Released RABs for Cell When DBHSDPA with MIMO Applied Number of RAB Setup Attempts for Cell When 4CHSDPA Applied Number of Successful RAB Setups for Cell When 4C-HSDPA Applied Number of Abnormal Released RABs for Cell When 4C-HSDPA Applied (RF Exceptions Considered) Number of Normally Released RABs for Cell When 4CHSDPA Applied Number of RAB Setup Attempts for Cell When DBHSDPA Applied Number of Successful RAB Setups for Cell When DB-HSDPA Applied
73426109
VS.HSDPA.RAB.N ormRel.DBMIMO
V900R015
73426110
VS.HSDPA.RAB. 4C.AttEstab
V900R015
73426111
VS.HSDPA.RAB. 4C.SuccEstab
V900R015
73426112
VS.HSDPA.RAB.A bnormRel.4C
V900R015
73426113
VS.HSDPA.RAB.N ormRel.4C
V900R015
73426114
VS.HSDPA.RAB.D B.AttEstab
V900R015
73426115
VS.HSDPA.RAB.D B.SuccEstab
V900R015
Issue 01 (2013-05-04)
1209
Counter ID 73426116
Counter Name VS.HSDPA.RAB.A bnormRel.DB
Counter Description Number of Abnormally Released RABs for Cell When DBHSDPA Applied (RF Exceptions Considered) Number of Normally Released RABs for Cell When DBHSDPA Applied Number of Abnormally Released RABs During State Transition of SRB over HSDPA Users to CELL_PCH or URA_PCH for Cell Number of Abnormally Released RABs of SRB over HSDPA Users for Cell Number of Normally Released RABs of SRB over HSDPA Users for Cell (All Scenarios)
73426117
VS.HSDPA.RAB.N ormRel.DB
V900R015
73426316
VS.HSDPA.RAB.A bnormRel.SRBoH. H2P
V900R015
73426317
VS.HSDPA.RAB.A bnormRel.SRBoH
V900R015
73426318
VS.HSDPA.RAB.N ormRel.SRBoH.All
V900R015
Counter VS.HSDPA.MeanChThroughput.TotalBytes Sub Counter VS.HSDPA.MeanGoldenBeChThroughput. TotalBytes VS.HSDPA.MeanSilverBeChThroughput.T otalBytes VS.HSDPA.MeanCopperBeChThroughput. TotalBytes VS.PS.Conv.Traffic.HSDSCH VS.HSDPA.Traffic.HighLoad
Issue 01 (2013-05-04)
1210
Counter VS.HSDPA.SHO.ServCellChg.AttOut
Sub Counter VS.HSDPA.SHO.ServCellChg.AttOutIur VS.HSDPA.SHO.IubBasedServCellChg.Att Out
VS.HSDPA.SHO.ServCellChg.SuccOut
VS.HSDPA.SHO.ServCellChg.SuccOutIur VS.HSDPA.SHO.IubBasedServCellChg.Su ccOut
VS.HSDPA.HHO.H2H.AttOutIur
VS.HSDPA.HHO.H2H.AttOutIntraFreq VS.HSDPA.HHO.H2H.AttOutInterFreq
VS.HSDPA.HHO.H2H.SuccOutIur
VS.HSDPA.HHO.H2H.SuccOutIntraFreq VS.HSDPA.HHO.H2H.SuccOutInterFreq
VS.HSDPA.HHO.H2D.AttOutIur
VS.HSDPA.HHO.H2D.AttOutIntraFreq VS.HSDPA.HHO.H2D.AttOutInterFreq
VS.HSDPA.HHO.H2D.SuccOutIur
VS.HSDPA.HHO.H2D.SuccOutIntraFreq VS.HSDPA.HHO.H2D.SuccOutInterFreq
VS.HSDPA.RAB.AttEstab
VS.HSDPA.RAB.AttEstab.BE.Golden VS.HSDPA.RAB.AttEstab.BE.Silver VS.HSDPA.RAB.AttEstab.BE.Copper VS.HSDPA.RAB.64QAM.AttEstab VS.HSDPA.RAB.MIMO.AttEstab VS.HSDPA.RAB.MIMO64QAM.AttEstab VS.HSDPA.RAB.DC.AttEstab VS.HSDPA.RAB.DCMIMO.AttEstab VS.HSDPA.RAB.3CMIMO.AttEstab VS.HSDPA.RAB.3C.AttEstab VS.HSDPA.RAB.4CMIMO.AttEstab VS.HSDPA.RAB.DBMIMO.AttEstab VS.HSDPA.RAB.4C.AttEstab VS.HSDPA.RAB.DB.AttEstab
Issue 01 (2013-05-04)
1211
Counter VS.HSDPA.RAB.SuccEstab
Sub Counter VS.HSDPA.RAB.SuccEstab.BE.Golden VS.HSDPA.RAB.SuccEstab.BE.Silver VS.HSDPA.RAB.SuccEstab.BE.Copper VS.HSDPA.RAB.64QAM.SuccEstab VS.HSDPA.RAB.MIMO.SuccEstab VS.HSDPA.RAB.MIMO64QAM.SuccEstab VS.HSDPA.RAB.DC.SuccEstab VS.HSDPA.RAB.DCMIMO.SuccEstab VS.HSDPA.RAB.3CMIMO.SuccEstab VS.HSDPA.RAB.3C.SuccEstab VS.HSDPA.RAB.4CMIMO.SuccEstab VS.HSDPA.RAB.DBMIMO.SuccEstab VS.HSDPA.RAB.4C.SuccEstab VS.HSDPA.RAB.DB.SuccEstab
VS.HSDPA.RAB.AbnormRel
VS.HSDPA.RAB.AbnormRel.RF VS.HSDPA.RAB.AbnormRel.64QAM VS.HSDPA.RAB.AbnormRel.MIMO64QA M VS.HSDPA.RAB.AbnormRel.DC VS.HSDPA.RAB.AbnormRel.MIMO VS.HSDPA.RAB.AbnormRel.H2P VS.HSDPA.RAB.DCMIMO.AbnormRel VS.HSDPA.RAB.AbnormRel.3CMIMO VS.HSDPA.RAB.AbnormRel.3C VS.HSDPA.RAB.AbnormRel.4CMIMO VS.HSDPA.RAB.AbnormRel.DBMIMO VS.HSDPA.RAB.AbnormRel.4C VS.HSDPA.RAB.AbnormRel.DB VS.HSDPA.RAB.AbnormRel.SRBoH
Issue 01 (2013-05-04)
1212
Counter VS.HSDPA.RAB.NormRel
Sub Counter VS.HSDPA.RAB.NormRel.64QAM VS.HSDPA.RAB.NormRel.MIMO VS.HSDPA.RAB.NormRel.MIMO64QAM VS.HSDPA.RAB.NormRel.DC VS.HSDPA.RAB.DCMIMO.NormRel VS.HSDPA.RAB.NormRel.3CMIMO VS.HSDPA.RAB.NormRel.3C VS.HSDPA.RAB.NormRel.4CMIMO VS.HSDPA.RAB.NormRel.DBMIMO VS.HSDPA.RAB.NormRel.4C VS.HSDPA.RAB.NormRel.DB
VS.HSDPA.UE.Mean.Cell
VS.HSDPA.UE.Mean.CAT1.6 VS.HSDPA.UE.Mean.CAT7.10 VS.HSDPA.UE.Mean.CAT11.12 VS.HSDPA.UE.Mean.CAT13.14 VS.HSDPA.UE.Mean.CAT15.16 VS.HSDPA.UE.Mean.CAT17.20 VS.HSDPA.UE.Mean.CAT21.24 VS.HSDPA.64QAM.UE.Mean.Cell VS.HSDPA.MIMO.UE.Mean.Cell VS.HSDPA.MIMO64QAM.UE.Mean.Cell VS.HSDPA.DC.PRIM.UE.Mean.Cell VS.HSDPA.UE.Mean.CAT25.28 VS.HSDPA.UE.Mean.Cell.Free VS.HSDPA.4C.PRIM.UE.Mean.Cell VS.HSDPA.3C.PRIM.UE.Mean.Cell VS.HSDPA.DB.PRIM.UE.Mean.Cell VS.HSDPA.UE.Mean.CAT29 VS.HSDPA.UE.Mean.CAT30 VS.HSDPA.UE.Mean.CAT31 VS.HSDPA.UE.Mean.CAT32 VS.HSDPA.SRBoH.UE.Mean.Cell
Issue 01 (2013-05-04)
1213
Counter VS.HSDPA.UE.Max.Cell
Sub Counter VS.HSDPA.UE.Max.CAT1.6 VS.HSDPA.UE.Max.CAT7.10 VS.HSDPA.UE.Max.CAT11.12 VS.HSDPA.UE.Max.CAT13.14 VS.HSDPA.UE.Max.CAT15.16 VS.HSDPA.UE.Max.CAT17.20 VS.HSDPA.UE.Max.CAT21.24 VS.HSDPA.UE.Max.CAT25.28 VS.HSDPA.UE.Max.Cell.Free VS.HSDPA.UE.Max.CAT29 VS.HSDPA.UE.Max.CAT30 VS.HSDPA.UE.Max.CAT31 VS.HSDPA.UE.Max.CAT32
VS.HSDPA.RAB.AbnormRel.H2P
VS.HSDPA.RAB.AbnormRel.DC2P VS.HSDPA.RAB.AbnormRel.64QAM2P VS.HSDPA.RAB.AbnormRel.MIMO2P VS.HSDPA.RAB.AbnormRel.DCMIMO2P VS.HSDPA.RAB.AbnormRel.MIMO64QA M2P VS.HSDPA.RAB.AbnormRel.3C2P VS.HSDPA.RAB.AbnormRel.3CMIMO2P VS.HSDPA.RAB.AbnormRel.4C2P VS.HSDPA.RAB.AbnormRel.4CMIMO2P VS.HSDPA.RAB.AbnormRel.DB2P VS.HSDPA.RAB.AbnormRel.DBMIMO2P VS.HSDPA.RAB.AbnormRel.SRBoH.H2P
1.12.12.1 Number of Successful Channel Reconfigurations Counters

Counter ID 67189831 Counter Name VS.HSDPA.F2H.Succ Counter Description Number of Successful Channel Conversions from FACH to HS-DSCH for HSDPA Service for Cell
Issue 01 (2013-05-04)
1214
Counter ID 67189830
Counter Name VS.HSDPA.D2H.Succ
Counter Description Number of Successful Channel Conversions from DCH to HS-DSCH for HSDPA Service for Cell Number of Successful Channel Conversions from HS-DSCH to DCH for HSDPA Service for Cell Number of Successful Channel Conversions from HS-DSCH to FACH for HSDPA Service for Cell
67189832
VS.HSDPA.H2D.Succ
67189833
VS.HSDPA.H2F.Succ
Description
This counter provides the number of successful channel reconfigurations by channel reconfiguration type in the HSDPA serving cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter. Counter Name VS.HSDPA.F2H.Succ Description VS.HSDPA.F2H.Succ provides the number of successful channel conversions from the FACH to the HS-DSCH in a cell. VS.HSDPA.D2H.Succ provides the number of successful channel conversions from the DCH to the HS-DSCH in a cell. VS.HSDPA.H2D.Succ provides the number of successful channel conversions from the HS-DSCH to the DCH in a cell. VS.HSDPA.H2F.Succ provides the number of successful channel conversions from the HS-DSCH to the FACH in a cell.
VS.HSDPA.D2H.Succ
VS.HSDPA.H2D.Succ
VS.HSDPA.H2F.Succ
Measurement point
The measurement is triggered at point B as shown in the following figure. The RNC receives from a UE a RADIO BEARER RECONFIGURATION COMPLETE message indicating a channel reconfiguration in the DCCC or RAB MODIFY procedure. If a channel conversion occurs, the RNC measures this counter in the HSDPA serving cell according to the channel status before and after the reconfiguration.
Figure 1-530 Dynamic channel configuration procedure (RB reconfiguration)
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.F2H.Succ VS.HSDPA.D2H.Succ VS.HSDPA.H2D.Succ VS.HSDPA.H2F.Succ Feature ID WRFD-01061111 WRFD-01061111 WRFD-01061111 WRFD-01061111 Feature Name HSDPA State Transition HSDPA State Transition HSDPA State Transition HSDPA State Transition
1.12.12.2 Number of Successful HSDPA MAC-d Flow Establishments for Cell
Issue 01 (2013-05-04)
1216
Counters
Counter ID 67189834 Counter Name VS.HSDPA.MACD.SuccSetup Counter Description Number of Successful HSDPA MAC-d Flow Establishments for Cell
Description
This measurement item provides the number of successful HSDPA MAC-d flow establishments in a cell.For DC-HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
During the RL reconfiguration, if the RADIO LINK RECONFIGURATION PREPARE message contains an IE "HSDSCH FDD Information" or "HS-DSCH MAC-d Flows To Add", it indicates that the RL is set up for HSDPA service. The measurement is triggered at point C as shown in the following figure. When the RNC sends the NodeB a RADIO LINK RECONFIGURATION COMMIT message, this counter is measured in the cell in which the RL is set up. Figure 1-531 Synchronized RL reconfiguration commit procedure
During the RL reconfiguration, if the RADIO LINK SETUP REQUEST message contains an IE "HSDSCH FDD Information", it indicates that the RL is set up for HSDPA service in the serving cell. The measurement is triggered at point B as shown in the following figure. When the RNC receives a RADIO LINK SETUP RESPONSE message from the NodeB, this counter is measured in the cell in which the RL is set up.
Figure 1-532 Radio link setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.MACD.SuccSetup Feature ID WRFD-010610 Feature Name HSDPA Introduction Package
1.12.12.3 Number of HSDPA UEs in a Cell Counters

Counter ID 67202932 Counter Name VS.HSDPA.UE.Mean.Cell Counter Description Average Number of HSDPA UEs in a Cell
Issue 01 (2013-05-04)
1218
Counter ID 73403763 73410491 73410493 73410508
Counter Name VS.HSDPA.UE.Max.Cell VS.HSDPA. 64QAM.UE.Mean.Cell VS.HSDPA.MIMO64QAM. UE.Mean.Cell VS.HSDPA.DC.PRIM.UE. Mean.Cell VS.HSDPA.DC.SEC.UE.M ean.Cell
Counter Description Maximum Number of HSDPA UEs in a Cell Average Number of 64QAM UEs in a Cell Average Number of MIMO +64QAM UEs in a Cell Average number of DCHSDPA UEs in anchor carrier in a Cell Average number of DCHSDPA UEs in supplementary carrier in a Cell Average Number of Free HSDPA Users in a Cell Maximum Number of Free HSDPA Users in a Cell Average Number of 4CHSDPA UEs Using This Cell as the Primary Carrier Cell Average Number of 3CHSDPA UEs Using This Cell as the Primary Carrier Cell Average Number of 4CHSDPA/DB-HSDPA/DCHSDPA UEs Using This Cell as the Secondary Carrier Cell Average Number of DBHSDPA UEs Using This Cell as the Primary Carrier Cell Average number of users capable of the SRB over HSDPA feature in a cell
73410509
73441142 73423469 73425884
VS.HSDPA.UE.Mean.Cell. Free VS.HSDPA.UE.Max.Cell.Fr ee VS.HSDPA. 4C.PRIM.UE.Mean.Cell VS.HSDPA. 3C.PRIM.UE.Mean.Cell VS.HSDPA.MC.SEC.UE.M ean.Cell
73425887
73425890
73425893
VS.HSDPA.DB.PRIM.UE. Mean.Cell VS.HSDPA.SRBoH.UE.Me an.Cell
73426170
Issue 01 (2013-05-04)
1219
Counter ID 73393975
Counter Name VS.HSDPA. 64QAM.UE.Mean.Cell.DENO VS.HSDPA. 64QAM.UE.Mean.Cell.NU M VS.HSDPA.MIMO64QAM. UE.Mean.Cell.DENO VS.HSDPA.MIMO64QAM. UE.Mean.Cell.NUM VS.HSDPA.UE.Mean.Cell. Free.DENO VS.HSDPA.UE.Mean.Cell. Free.NUM
Counter Description Average Number of 64QAM UEs in a Cell(Denominator) Average Number of 64QAM UEs in a Cell(Numerator) Average Number of MIMO +64QAM UEs in a Cell (Denominator) Average Number of MIMO +64QAM UEs in a Cell (Numerator) VS.HSDPA.UE.Mean.Cell. Free.DENO VS.HSDPA.UE.Mean.Cell. Free.NUM
73393974
73393979
73393978
73423471 73423470
Description
These counters provide the average number and maximum number of HSDPA UEs in a serving cell when different technologies are used. For DC-HSDPA, 3C-HSDPA, 4C-HSDPA, or DB-HSDPA users, these counters, excluding VS.HSDPA.DC.SEC.UE.Mean.Cell and VS.HSDPA.MC.SEC.UE.Mean.Cell, are measured only in the cell with the primary carrier for once. VS.HSDPA.UE.Mean.Cell provides the average number of HSDPA UEs in a serving cell. VS.HSDPA.UE.MaX.Cell provides the maximum number of HSDPA UEs in a serving cell. The other counters provide the average or maximum number of UEs when different features are used in a serving cell. VS.HSDPA.DC.SEC.UE.Mean.Cell provides the average number of DC-HSDPA UEs whose secondary carrier is the current cell in a serving cell. VS.HSDPA.MC.SEC.UE.Mean.Cell provides the average number of 4C-HSDPA, 3C-HSDPA, DB-HSDPA, and DC-HSDPA UEs (including UEs using both multi-carrier HSDPA and MIMO) whose secondary carrier is the current cell in a serving cell.
Measurement point
The system samples the number of HSDPA UEs using various technologies every 5s. Assume that the total number of samples is N within a measurement period. At the end of the measurement period, the system divides N by the accumulated value of sampled data to obtain the average number of UEs using various features. The maximum sampled value is used as the maximum number of UEs using various technologies.
Formula
VS.HSDPA.64QAM.UE.Mean.Cell = [VS.HSDPA.64QAM.UE.Mean.Cell.NUM]/ [VS.HSDPA.64QAM.UE.Mean.Cell.DENO] VS.HSDPA.MIMO64QAM.UE.Mean.Cell = [VS.HSDPA.MIMO64QAM.UE.Mean.Cell.NUM]/ [VS.HSDPA.MIMO64QAM.UE.Mean.Cell.DENO] VS.HSDPA.UE.Mean.Cell.Free = [VS.HSDPA.UE.Mean.Cell.Free.NUM]/ [VS.HSDPA.UE.Mean.Cell.Free.DENO]
Unit
None
Related Features
Counter Name VS.HSDPA.UE.Mean.Cell Feature ID WRFD-01061016 WRFD-010622 WRFD-010623 VS.HSDPA.UE.Max.Cell WRFD-01061003 WRFD-020101 VS.HSDPA. 64QAM.UE.Mean.Cell VS.HSDPA.MIMO64QAM. UE.Mean.Cell VS.HSDPA.DC.PRIM.UE. Mean.Cell VS.HSDPA.DC.SEC.UE.M ean.Cell VS.HSDPA.UE.Mean.Cell. Free VS.HSDPA.UE.Max.Cell.Fr ee VS.HSDPA. 4C.PRIM.UE.Mean.Cell VS.HSDPA. 3C.PRIM.UE.Mean.Cell WRFD-010683 WRFD-010693 WRFD-010696 WRFD-010696 WRFD-01061003 WRFD-01061003 WRFD-150207 WRFD-150223 WRFD-150207 WRFD-150223 Feature Name 16 HSDPA Users per Cell 32 HSDPA Users per Cell 64 HSDPA Users per Cell HSDPA Admission Control Admission Control Downlink 64QAM DL 64QAM+MIMO DC-HSDPA DC-HSDPA HSDPA Admission Control HSDPA Admission Control 4C-HSDPA 4C-HSDPA+MIMO 4C-HSDPA 4C-HSDPA+MIMO
Issue 01 (2013-05-04)
1221
Counter Name VS.HSDPA.MC.SEC.UE.M ean.Cell
Feature Name 4C-HSDPA Flexible DC/DB-HSDPA DB-HSDPA DC-HSDPA+MIMO DC-HSDPA DB-HSDPA DB-HSDPA+MIMO SRB over HSDPA
VS.HSDPA.DB.PRIM.UE. Mean.Cell VS.HSDPA.SRBoH.UE.Me an.Cell
WRFD-150209 WRFD-150227 WRFD-010652
1.12.12.4 Number of MAC-d Flows in a Cell Counters

Counter ID 67202941 Counter Name VS.HSDPA.MACD.Mean.C ell Counter Description Average Number of MAC-d Flows in a Cell
Description
This counter provides the average number of MAC-d flows in a serving cell.For DC-HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The system samples the number of MAC-d flows every 5s. Assume that the total number of samples within a measurement period is N. at the end of a measurement period, the RNC divides N by the accumulated value of sampled data to obtain the average number of MAC-d flows.
Formula
None
Unit
None
Issue 01 (2013-05-04)
1222
Related Features
Counter Name VS.HSDPA.MACD.Mean.C ell Feature ID WRFD-01061016 WRFD-010622 WRFD-010623 Feature Name 16 HSDPA Users per Cell 32 HSDPA Users per Cell 64 HSDPA Users per Cell
1.12.12.5 Mean Downlink Throughput of single HSDPA MAC-d Flows Counters

Counter ID 67202894 Counter Name VS.HSDPA.MeanChThroughput VS.HSDPA.MeanGoldenBeChThroughput Counter Description Mean Downlink Throughput of single HSDPA MAC-d Flows for Cell Mean Downlink Throughput of HSDPA MAC-d Flow of BE Service for Golden Subscriber for Cell Mean Downlink Throughput of HSDPA MAC-d Flow of BE Service for Silver Subscriber for Cell Mean Downlink Throughput of HSDPA MAC-d Flow of BE Service for Copper Subscriber for Cell Average downlink throughput of the Traffic PS Conversational beared on HSDSCH for cell
67204510
67204511
67204512
VS.HSDPA.MeanCopperBeChThroughput
73410484
VS.PS.Conv.Kbps.HSDSC H
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67190567 67194872 Counter Name VS.HSDPA.MeanChThroug hput.Times VS.HSDPA.MeanCopperBe ChThroughput.Times Counter Description Duration of HSDPA MAC-D Flow Sending Data for Cell Duration of Copper BE HSDPA MAC-D Flow Sending Data for Cell
1223
Issue 01 (2013-05-04)
Counter ID 67194868
Counter Name VS.HSDPA.MeanGoldenBe ChThroughput.Times VS.HSDPA.MeanSilverBeC hThroughput.Times VS.PS.Conv.Times.HSDSC H
Counter Description Duration of Golden BE HSDPA MAC-D Flow Sending Data for Cell Duration of Silver BE HSDPA MAC-D Flow Sending Data for Cell Duration of PS Conversational HSDPA MAC-D Flow Sending Data for Cell
67194870
73393913
Description
These counters provide the mean downlink throughput of single HSDPA MAC-d flows in a serving cell according to user priorities or service types. For multi-carrier HSDPA users, this counter is measured only in the primary cell based on the total throughput on the primary and secondary carriers. The following table describes the meaning of each counter. Counter Name VS.HSDPA.MeanChThroughput Description VS.HSDPA.MeanChThroughput provides the mean downlink throughput of all single HSDPA MAC-d flows in a cell. VS.HSDPA.MeanGoldenBeChThroughput, VS.HSDPA.MeanSilverBeChThroughput, and VS.HSDPA.MeanCopperBeChThroughput provide the mean downlink throughput of HSDPA MAC-d flows of BE services for golden subscribers, silver subscribers, and copper subscribers in a cell, respectively. VS.HSDPA.MeanGoldenBeChThroughput, VS.HSDPA.MeanSilverBeChThroughput, and VS.HSDPA.MeanCopperBeChThroughput provide the mean downlink throughput of HSDPA MAC-d flows of BE services for golden subscribers, silver subscribers, and copper subscribers in a cell, respectively.
VS.HSDPA.MeanGoldenBeChThroughput
Issue 01 (2013-05-04)
1224
Counter Name VS.HSDPA.MeanCopperBeChThroughput
Description VS.HSDPA.MeanGoldenBeChThroughput, VS.HSDPA.MeanSilverBeChThroughput, and VS.HSDPA.MeanCopperBeChThroughput provide the mean downlink throughput of HSDPA MAC-d flows of BE services for golden subscribers, silver subscribers, and copper subscribers in a cell, respectively. VS.PS.Conv.Kbps.HSDSCH provides the average downlink throughput of single MACd flows of PS conversational services carried on HSDSCH.
VS.PS.Conv.Kbps.HSDSCH
Measurement point
When data is sent in an HSDPA serving cell, the RNC measures the total data transmission time of the MAC-d flows in the serving cell and the total bytes sent in the HSDPA serving cell. When data of BE services for golden/silver/copper subscribers or data of PS conversational services carried on the HS-DSCH is sent in the serving cell, the RNC measures the total data transmission time of MAC-d flows for these services and the total bits sent in the HSDPA serving cell. At the end of the measurement period, the RNC divides the total data transmission time by the total number of bits to obtain the mean downlink throughput of MAC-d flows at the RLC layer in the cell. The total bits do not include the RLC header and the retransmitted data in the unit of bit. The total number of bits is calculated by converting the total number of bytes. The total data transmission time is measured in the unit of ms.
Formula
VS.HSDPA.MeanChThroughput = {8}*[VS.HSDPA.MeanChThroughput.TotalBytes]/ [VS.HSDPA.MeanChThroughput.Times] VS.HSDPA.MeanGoldenBeChThroughput = {8}* [VS.HSDPA.MeanGoldenBeChThroughput.TotalBytes]/ [VS.HSDPA.MeanGoldenBeChThroughput.Times] VS.HSDPA.MeanSilverBeChThroughput = {8}* [VS.HSDPA.MeanSilverBeChThroughput.TotalBytes]/ [VS.HSDPA.MeanSilverBeChThroughput.Times] VS.HSDPA.MeanCopperBeChThroughput = {8}* [VS.HSDPA.MeanCopperBeChThroughput.TotalBytes]/ [VS.HSDPA.MeanCopperBeChThroughput.Times] VS.PS.Conv.Kbps.HSDSCH = {8}*[VS.PS.Conv.Traffic.HSDSCH]/ [VS.PS.Conv.Times.HSDSCH]
Unit
kbit/s
Related Features
Counter Name VS.HSDPA.MeanChThroughput VS.HSDPA.MeanGoldenBeChThroughput Feature ID WRFD-010610 WRFD-01061008 WRFD-020806 Feature Name HSDPA Introduction Package Interactive and Background Traffic Class on HSDPA Differentiated Service Based on SPI Weight VS.HSDPA.MeanSilverBeChThroughput WRFD-01061008 WRFD-020806 Interactive and Background Traffic Class on HSDPA Differentiated Service Based on SPI Weight VS.HSDPA.MeanCopperBeChThroughput WRFD-01061008 WRFD-020806 Interactive and Background Traffic Class on HSDPA Differentiated Service Based on SPI Weight VS.PS.Conv.Kbps.HSDSC H WRFD-010617 WRFD-010501 VoIP over HSPA/HSPA+ Conversational QoS Class
1.12.12.6 Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow Counters
Counter ID 67189840 Counter Name VS.HSDPA.MeanChThroug hput.TotalBytes VS.HSDPA.MeanGoldenBe ChThroughput.TotalBytes Counter Description Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow for Cell Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow of BE Service for Golden Subscriber for Cell Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow of BE Service for Silver Subscriber for Cell Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow of BE Service for Copper Subscriber for Cell
1226
67194867
67194869
VS.HSDPA.MeanSilverBeC hThroughput.TotalBytes
67194871
VS.HSDPA.MeanCopperBe ChThroughput.TotalBytes
Issue 01 (2013-05-04)
Counter ID 73393912
Counter Name VS.PS.Conv.Traffic.HSDSC H
Counter Description Number of downlink bytes of Transport Blocks of Traffic PS Conversational beared on HSDSCH for cell
Description
These counters provide the number of bytes sent in the downlink for a single HSDPA MAC-d flow according to user priorities or service types in a serving cell. For multi-carrier HSDPA users, this counter is measured only in the primary cell based on the total number of bytes sent on the primary and secondary carriers. VS.HSDPA.MeanChThroughput provides total number of bytes sent in the downlink on all HSDPA Mac-d flows. VS.HSDPA.MeanGoldenBeChThroughput, VS.HSDPA.MeanSilverBeChThroughput, and VS.HSDPA.MeanCopperBeChThroughput provide the number of bytes sent in the downlink on the HSDPA MAC-d flows of BE services for golden subscribers, silver subscribers, and copper subscribers in a cell, respectively. VS.PS.Conv.Kbps.HSDSCH provides the number of bytes sent in the downlink on the MAC-d flows of PS conversational services carried on HS-DSCH.
Measurement point
The RNC measures the number of total bytes (including all types of service data) sent in the downlink at the RLC layer of the MAC-d flow in the serving cell. When data of BE services for golden/silver/copper subscribers or data of PS conversational services carried on the HS-DSCH is sent in the serving cell, the RNC measures the total number of bytes sent in the downlink at the RLC layer of the MAC-d flow HSDPA serving cell. The total bytes do not include the RLC header and the retransmitted data.
Formula
None
Unit
byte
Related Features
Counter Name VS.HSDPA.MeanChThroug hput.TotalBytes Feature ID WRFD-010610 Feature Name HSDPA Introduction Package
Issue 01 (2013-05-04)
1227
Counter Name VS.HSDPA.MeanGoldenBe ChThroughput.TotalBytes
Feature Name Interactive and Background Traffic Class on HSDPA Differentiated Service Based on SPI Weight
VS.HSDPA.MeanSilverBeC hThroughput.TotalBytes
WRFD-01061008 WRFD-020806
Interactive and Background Traffic Class on HSDPA Differentiated Service Based on SPI Weight
VS.HSDPA.MeanCopperBe ChThroughput.TotalBytes
WRFD-01061008 WRFD-020806
Interactive and Background Traffic Class on HSDPA Differentiated Service Based on SPI Weight
VS.PS.Conv.Traffic.HSDSC H
WRFD-010617 WRFD-010501
VoIP over HSPA/HSPA+ Conversational QoS Class
1.12.12.7 Number of Handover Attempts Between Channels of Different Types Counters

Counter ID 67190690 Counter Name VS.HSDPA.H2D.Att Counter Description Number of Channel Conversion Attempts from HS-DSCH to DCH for HSDPA Service for Cell Number of Channel Conversion Attempts from DCH to HS-DSCH for HSDPA Service for Cell Number of Channel Conversion Attempts from FACH to HS-DSCH for HSDPA Service for Cell Number of Channel Conversion Attempts from HS-DSCH to FACH for HSDPA Service for Cell
67190693
VS.HSDPA.D2H.Att
67190696
VS.HSDPA.F2H.Att
67190697
VS.HSDPA.H2F.Att
Issue 01 (2013-05-04)
1228
Description
This counter provides the number of handover attempts between channels of different types in a cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter. Counter Name VS.HSDPA.H2D.Att Description VS.HSDPA.H2D.Att provides the number of channel conversion attempts from the HSDSCH to the DCH in a cell. VS.HSDPA.D2H.Att provides the number of channel conversion attempts from the DCH to the HS-DSCH in a cell. VS.HSDPA.F2H.Att provides the number of channel conversion attempts from the FACH to the HS-DSCH in a cell. VS.HSDPA.H2F.Att provides the number of channel conversion attempts from the HSDSCH to the FACH in a cell.
VS.HSDPA.D2H.Att
VS.HSDPA.F2H.Att
VS.HSDPA.H2F.Att
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC decides to perform a channel handover, it sends a RADIO BEARER RECONFIGURATION message to a UE during the DCCC or RAB MODIFY procedure. The RNC measures these counters in the HSDPA serving cell according to the channel status before and after the reconfiguration. Figure 1-533 Dynamic channel configuration procedure (RB reconfiguration)
Issue 01 (2013-05-04)
1229
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.H2D.Att VS.HSDPA.D2H.Att VS.HSDPA.F2H.Att VS.HSDPA.H2F.Att Feature ID WRFD-01061111 WRFD-01061111 WRFD-01061111 WRFD-01061111 Feature Name HSDPA State Transition HSDPA State Transition HSDPA State Transition HSDPA State Transition
1.12.12.8 Number of HSDPA Serving Cell Change Attempts for Cell Counters
Counter ID 67190698 Counter Name VS.HSDPA.SHO.ServCellC hg.AttOut VS.HSDPA.SHO.ServCellC hg.AttOutIur VS.HSDPA.SHO.IubBased ServCellChg.AttOut Counter Description Number of Intra-RNC HSDPA Serving Cell Change Attempts for Cell Number of Inter-RNC HSDPA Serving Cell Change Attempts for Cell Number of Serving Cell Change Attempts Triggered by Unbalanced Iub Resources for Cell
67195481
73423900
Description
These counters provide the number of serving cell change attempts for cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter.
Issue 01 (2013-05-04)
1230
Counter Name VS.HSDPA.SHO.ServCellChg.AttOut
Description VS.HSDPA.SHO.ServCellChg.AttOut provides the number of HSDPA serving cell change attempts in a cell. VS.HSDPA.SHO.ServCellChg.AttOutIur provides the number of inter-RNC HSDPA serving cell change attempts in a cell. VS.HSDPA.SHO.IubBasedServCellChg.Att Out provides the number of HSDPA serving cell change attempts that are triggered by unbalanced Iub resources between NodeBs.
VS.HSDPA.SHO.ServCellChg.AttOutIur
VS.HSDPA.SHO.IubBasedServCellChg.Att Out
Measurement point
During an HSDPA serving cell change when a soft handover occurs, the RNC may send the UE the following messages: (1)PHYSICAL CHANNEL RECONFIGURATION, (2)TRANSPORT CHANNEL RECONFIGURATION, (3)RADIO BEARER RECONFIGURATION, (4)ACTIVE SET UPDATE. The measurement is triggered at point A as shown in the following figure. Assume that the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message, the RNC measures these counters in the original serving cell based on the type of serving cell change. Figure 1-534 HSDPA Serving cell change procedure (successful operation)
Issue 01 (2013-05-04)
1231
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.SHO.ServCellC hg.AttOut VS.HSDPA.SHO.ServCellC hg.AttOutIur Feature ID WRFD-01061006 WRFD-01061006 Feature Name HSDPA Mobility Management HSDPA Mobility Management
1.12.12.9 Number of Successful HSDPA Serving Cell Changes for Cell Counters
Counter ID 67190699 Counter Name VS.HSDPA.SHO.ServCellC hg.SuccOut VS.HSDPA.SHO.ServCellC hg.SuccOutIur VS.HSDPA.SHO.IubBased ServCellChg.SuccOut Counter Description Number of Intra-RNC HSDPA Serving Cell Change Success in RNC for Cell Number of Inter-RNC HSDPA Serving Cell Change Success for Cell Number of Successful Serving Cell Changes Triggered by Unbalanced Iub Resources for Cell
67195482
73423901
Description
These counters provide the number of successful serving cell changes of different types only during a soft handover. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter. Counter Name VS.HSDPA.SHO.ServCellChg.SuccOut Description VS.HSDPA.SHO.ServCellChg.SuccOut provides the number of successful HSDPA serving cell changes in a cell.
1232
Issue 01 (2013-05-04)
Counter Name VS.HSDPA.SHO.ServCellChg.SuccOutIur
Description VS.HSDPA.SHO.ServCellChg.SuccOutIur provides the number of successful inter-RNC HSDPA serving cell changes in a cell. VS.HSDPA.SHO.IubBasedServCellChg.Su ccOut provides the number of successful HSDPA serving cell changes that are triggered by unbalanced Iub resources between NodeBs.
VS.HSDPA.SHO.IubBasedServCellChg.Su ccOut
Measurement point
During an HSDPA serving cell change when a soft handover occurs, the RNC may send the UE the following messages: (1)PHYSICAL CHANNEL RECONFIGURATION, (2)TRANSPORT CHANNEL RECONFIGURATION, (3)RADIO BEARER RECONFIGURATION, (4)ACTIVE SET UPDATE. The measurement is triggered at point B as shown in the following figure. Assume that the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message, the RNC measures these counters in the original serving cell based on the type of serving cell change. Figure 1-535 HSDPA Serving cell change procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.SHO.ServCellC hg.SuccOut VS.HSDPA.SHO.ServCellC hg.SuccOutIur Feature ID WRFD-01061006 WRFD-01061006 Feature Name HSDPA Mobility Management HSDPA Mobility Management
1.12.12.10 Number of Inter-RNC HSDPA Hard Handover Attempts Without Channel Change for Cell Counters
Counter ID 67195483 Counter Name VS.HSDPA.HHO.H2H.AttOutIur Counter Description Number of Inter-RNC HSDPA Hard Handover Attempts Without Channel Change for Cell Number of Intra-Frequency HSDPA Hard Handover Attempts Without Channel Change for Cell Number of Inter-Frequency HSDPA Hard Handover Attempts Without Channel Change for Cell
67190700
VS.HSDPA.HHO.H2H.AttOutIntraFreq
67190702
VS.HSDPA.HHO.H2H.AttOutInterFreq
Description
These counters provide the number of attempts for outgoing hard handovers of different types on the HSDPA channel in a serving cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter.
Issue 01 (2013-05-04)
1234
Counter Name VS.HSDPA.HHO.H2H.AttOutIur
Description VS.HSDPA.HHO.H2H.AttOutIur provides the number of inter-RNC HSDPA hard handover attempts without channel change in the serving cell. VS.HSDPA.HHO.H2H.AttOutIntraFreq provides the number of intra-frequency HSDPA hard handover attempts without channel change in a cell. VS.HSDPA.HHO.H2H.AttOutInterFreq provides the number of inter-frequency HSDPA hard handover attempts without channel change in a cell.
VS.HSDPA.HHO.H2H.AttOutIntraFreq
VS.HSDPA.HHO.H2H.AttOutInterFreq
Measurement point
During the hard handover on the HSDPA channel, the RNC may send the UE the following messages: (1) PHYSICAL CHANNEL RECONFIGURATION, (2) TRANSPORT CHANNEL RECONFIGURATION, (3) RADIO BEARER RECONFIGURATION, (4) RADIO BEARER SETUP, (5) RADIO BEARER RELEASE. The measurement is triggered at point A as shown in the following figure. Assume that the RNC sends the UE a PHYSICAL CHANNEL RECONFIGRATION message, the RNC measures these counters in the best cell before the hard handover according to the hard handover type. Figure 1-536 HSDPA Serving cell change procedure (successful operation)
Issue 01 (2013-05-04)
1235
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.HHO.H2H.AttOutIur VS.HSDPA.HHO.H2H.AttOutIntraFreq VS.HSDPA.HHO.H2H.AttOutInterFreq Feature ID WRFD-01061006 WRFD-01061006 WRFD-01061006 Feature Name HSDPA Mobility Management HSDPA Mobility Management HSDPA Mobility Management
1.12.12.11 Number of Successful Inter-RNC HSDPA Hard Handovers Without Channel Change for Cell Counters
Counter ID 67195484 Counter Name VS.HSDPA.HHO.H2H.SuccOutIur Counter Description Number of Successful InterRNC HSDPA Hard Handovers Without Channel Change for Cell Number of Successful IntraFrequency HSDPA Hard Handovers Without Channel Change for Cell
67190701
VS.HSDPA.HHO.H2H.SuccOutIntraFreq
Description
These counters provide the number of successful outgoing hard handovers of different types on the HSDPA channel in a serving cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter.
Issue 01 (2013-05-04)
1236
Counter Name VS.HSDPA.HHO.H2H.SuccOutIur
Description VS .HSDPA.HHO.H2H.SuccOutIur provides the number of successful inter-RNC HSDPA hard handover attempts without channel change in the serving cell. VS.HSDPA.HHO.H2H.SuccOutIntraFreq provides the number of successful intrafrequency HSDPA hard handover attempts without channel change in a cell.
VS.HSDPA.HHO.H2H.SuccOutIntraFreq
Measurement point
During the hard handover on the HSDPA channel, the RNC may send the UE the following messages: (1) PHYSICAL CHANNEL RECONFIGURATION, (2) TRANSPORT CHANNEL RECONFIGURATION, (3) RADIO BEARER RECONFIGURATION, (4) RADIO BEARER SETUP, (5) RADIO BEARER RELEASE. The measurement is triggered at point B as shown in the following figure. Assume that the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATIO COMPLETE message, the RNC measures these counters in the best cell before the hard handover according to the hard handover type. Figure 1-537 HSDPA Serving cell change procedure (successful operation)
Issue 01 (2013-05-04)
1237
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.HHO.H2H.SuccOutIur VS.HSDPA.HHO.H2H.SuccOutIntraFreq Feature ID WRFD-01061006 WRFD-01061006 Feature Name HSDPA Mobility Management HSDPA Mobility Management
1.12.12.12 Number of Successful Inter-Frequency HSDPA Hard Handovers Without Channel Change for Cell Counters
Counter ID 67190703 Counter Name VS.HSDPA.HHO.H2H.SuccOutInterFreq Counter Description Number of Successful InterFrequency HSDPA Hard Handovers Without Channel Change for Cell
Description
This measurement item provides the number of successful inter-frequency hard handovers from the HSDPA to the HSDPA in a cell. The hard handover procedure can be triggered with the following messages:[1]PHYSICAL CHANNEL RECONFIGURATION,[2]TRANSPORT CHANNEL RECONFIGURATION,[3]RADIO BEARER RECONFIGURATION,[4]RADIO BEARER SETUP,[5]RADIO BEARER RELEASE message. Accordingly, UE may send [1] PHYSICAL CHANNEL RECONFIGURATION COMPLETE,[2]PHYSICAL CHANNEL RECONFIGURATION FAILURE,[3]TRANSPORT CHANNEL RECONFIGURATION COMPLETE,[4]TRANSPORT CHANNEL RECONFIGURATION FAILURE,[5]RADIO BEARER RECONFIGURATION COMPLETE,[6]RADIO BEARER RECONFIGURATION FAILURE,[7]RADIO BEARER SETUP COMPLETE,[8]RADIO BEARER SETUP FAILURE,[9]RADIO BEARER RELEASE COMPLETE,[10]RADIO BEARER RELEASE FAILURE message to RNC as a response.For DC-HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter.
Counter Name VS.HSDPA.HHO.H2H.SuccOutInterFreq
Description VS.HSDPA.HHO.H2H.SuccOutInterFreq provides the number of successful interfrequency HSDPA hard handover attempts without channel change in a cell.
Measurement point
The measurement is triggered at point B as shown in the figure, the procedure shown in the figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an exampl, when receiving from a UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message,the RNC measures this item in best the cell from which the UE is handed over if an inter-frequency HSDPA hard handover without channel change is performed. Figure 1-538 HSDPA Serving cell change procedure (successful operation)
Formula
None
Unit
None
Issue 01 (2013-05-04)
1239
Related Features
Counter Name VS.HSDPA.HHO.H2H.SuccOutInterFreq Feature ID WRFD-01061006 Feature Name HSDPA Mobility Management
1.12.12.13 Number of HSDPA RAB Establishment Attempts for Cell Counters

Counter ID 67190704 Counter Name VS.HSDPA.RAB.AttEstab Counter Description Number of HSDPA RAB Establishment Attempts for Cell Number of HSDPA RAB Establishment Attempts of BE Service for Golden Level User for Cell Number of HSDPA RAB Establishment Attempts of BE Service for Silver Level User for Cell Number of HSDPA RAB Establishment Attempts of BE Service for Copper Level User for Cell Number of HSDPA 64QAM RAB Setup Requests for cell Number of HSDPA MIMO RABs Setup Request for Cell Number of HSDPA MIMO +64QAM RABs Setup Request for cell Number of DC-HSDPA RAB Setup Requests in the primary carrier of DCHSDPA counted for cell Number of DC-HSDPA +MIMO RAB Setup Requests in the Primary Carrier of DC-HSDPA for Cell
67195507
VS.HSDPA.RAB.AttEstab. BE.Golden
67195508
VS.HSDPA.RAB.AttEstab. BE.Silver
67195509
VS.HSDPA.RAB.AttEstab. BE.Copper
73403817 73403821 73403824
VS.HSDPA.RAB. 64QAM.AttEstab VS.HSDPA.RAB.MIMO.At tEstab VS.HSDPA.RAB.MIMO64 QAM.AttEstab VS.HSDPA.RAB.DC.AttEstab
73403828
73423378
VS.HSDPA.RAB.DCMIM O.AttEstab
Issue 01 (2013-05-04)
1240
Counter ID 73426094
Counter Name VS.HSDPA.RAB. 3CMIMO.AttEstab VS.HSDPA.RAB. 3C.AttEstab VS.HSDPA.RAB. 4CMIMO.AttEstab VS.HSDPA.RAB.DBMIM O.AttEstab VS.HSDPA.RAB. 4C.AttEstab VS.HSDPA.RAB.DB.AttEstab
Counter Description Number of RAB Setup Attempts for Cell When 3CHSDPA with MIMO Applied Number of RAB Setup Attempts for Cell When 3CHSDPA Applied Number of RAB Setup Attempts for Cell Where 4CHSDPA with MIMO Applied Number of RAB Setup Attempts for Cell When DBHSDPA with MIMO Applied Number of RAB Setup Attempts for Cell When 4CHSDPA Applied Number of RAB Setup Attempts for Cell When DBHSDPA Applied
73426098
73426102
73426106
73426110
73426114
Description
These counters provide the number of HSDPA RAB establishment attempts for different priority level users (including gold, silver, and copper) when different features (such as 64QAM, MIMO, and DC) are enabled in a cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN for setting up HSDPA services, the RNC measures the measurement items by the priority level or used technology in the serving cell.
Issue 01 (2013-05-04)
1241
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.RAB.AttEstab Feature ID WRFD-01061008 WRFD-010630 Feature Name Interactive and Background Traffic Class on HSDPA Streaming Traffic Class on HSDPA VS.HSDPA.RAB.AttEstab. BE.Golden VS.HSDPA.RAB.AttEstab. BE.Silver VS.HSDPA.RAB.AttEstab. BE.Copper VS.HSDPA.RAB. 64QAM.AttEstab
Issue 01 (2013-05-04)
WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-010683
Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Downlink 64QAM
1242
Counter Name VS.HSDPA.RAB.MIMO.At tEstab VS.HSDPA.RAB.MIMO64 QAM.AttEstab VS.HSDPA.RAB.DC.AttEstab VS.HSDPA.RAB.DCMIM O.AttEstab VS.HSDPA.RAB. 3CMIMO.AttEstab VS.HSDPA.RAB. 3C.AttEstab VS.HSDPA.RAB. 4CMIMO.AttEstab VS.HSDPA.RAB.DBMIM O.AttEstab VS.HSDPA.RAB. 4C.AttEstab VS.HSDPA.RAB.DB.AttEstab
Feature Name 2 x 2 MIMO DL 64QAM+MIMO DC-HSDPA DC-HSDPA+MIMO 4C-HSDPA+MIMO 4C-HSDPA 4C-HSDPA+MIMO DB-HSDPA+MIMO 4C-HSDPA DB-HSDPA
1.12.12.14 Number of Successful HSDPA RAB Establishments for Cell Counters

Counter ID 67190705 Counter Name VS.HSDPA.RAB.SuccEstab Counter Description Number of Successful HSDPA RAB Establishments for Cell Number of Successful HSDPA RAB Establishments of BE Service for Golden Level User for Cell Number of Successful HSDPA RAB Establishments of BE Service for Silver Level User for Cell
1243
67195510
VS.HSDPA.RAB.SuccEstab .BE.Golden
67195511
VS.HSDPA.RAB.SuccEstab .BE.Silver
Issue 01 (2013-05-04)
Counter ID 67195512
Counter Name VS.HSDPA.RAB.SuccEstab .BE.Copper
Counter Description Number of Successful HSDPA RAB Establishments of BE Service for Copper Level User for Cell Number of HSDPA 64QAM RABs Setup Successfully for cell Number of HSDPA MIMO RABs Setup Successfully for cell Number of HSDPA MIMO +64QAM RABs Setup Successfully for cell Number of DC-HSDPA RABs Setup Successfully in the primary carrier of DCHSDPA counted for cell Number of Successful DCHSDPA+MIMO RAB Setups in the Primary Carrier of DC-HSDPA for cell Number of Successful RAB Setups for Cell When 3CHSDPA with MIMO Applied Number of Successful RAB Setups for Cell When 3CHSDPA Applied Number of Successful RAB Setups for Cell When 4CHSDPA with MIMO Applied Number of Successful RAB Setups for Cell When DBHSDPA with MIMO Applied Number of Successful RAB Setups for Cell When 4CHSDPA Applied Number of Successful RAB Setups for Cell When DBHSDPA Applied
73403818
VS.HSDPA.RAB. 64QAM.SuccEstab VS.HSDPA.RAB.MIMO.Su ccEstab VS.HSDPA.RAB.MIMO64 QAM.SuccEstab VS.HSDPA.RAB.DC.SuccEstab
73403822
73403825
73403829
73423379
VS.HSDPA.RAB.DCMIM O.SuccEstab
73426095
VS.HSDPA.RAB. 3CMIMO.SuccEstab VS.HSDPA.RAB. 3C.SuccEstab VS.HSDPA.RAB. 4CMIMO.SuccEstab VS.HSDPA.RAB.DBMIM O.SuccEstab VS.HSDPA.RAB. 4C.SuccEstab VS.HSDPA.RAB.DB.SuccEstab
73426099
73426103
73426107
73426111
73426115
Issue 01 (2013-05-04)
1244
Description
These counters provide the number of HSDPA RAB establishment attempts for different priority level users (including gold, silver, and copper) when different features (such as 64QAM, MIMO, and DC) are enabled in a cell. For DC-HSDPA, 3C-HSDPA, 4C-HSDPA, or DB-HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point B as shown in the following figure. After receiving a RADIO BEARER SETUP COMPLETE message from the UE, the RNC sends the CN a RAB ASSIGNMENT RESPONSE message. If the assignment is for setting up HSDPA services, the RNC measures the measurement items by the priority level or used technology in the serving cell. Figure 1-540 RAB setup procedure (successful operation)
Formula
None
Unit
None
Issue 01 (2013-05-04)
1245
Related Features
Counter Name VS.HSDPA.RAB.SuccEstab Feature ID WRFD-01061008 WRFD-010630 Feature Name Interactive and Background Traffic Class on HSDPA Streaming Traffic Class on HSDPA VS.HSDPA.RAB.SuccEstab .BE.Golden VS.HSDPA.RAB.SuccEstab .BE.Silver VS.HSDPA.RAB.SuccEstab .BE.Copper VS.HSDPA.RAB. 64QAM.SuccEstab VS.HSDPA.RAB.MIMO.Su ccEstab VS.HSDPA.RAB.MIMO64 QAM.SuccEstab VS.HSDPA.RAB.DC.SuccEstab VS.HSDPA.RAB.DCMIM O.SuccEstab VS.HSDPA.RAB. 3CMIMO.SuccEstab VS.HSDPA.RAB. 3C.SuccEstab VS.HSDPA.RAB. 4CMIMO.SuccEstab VS.HSDPA.RAB.DBMIM O.SuccEstab VS.HSDPA.RAB. 4C.SuccEstab VS.HSDPA.RAB.DB.SuccEstab WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-010683 WRFD-010684 WRFD-010693 WRFD-010696 WRFD-010699 WRFD-150223 WRFD-150207 WRFD-150223 WRFD-150227 WRFD-150207 WRFD-150209 Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Downlink 64QAM 2 x 2 MIMO DL 64QAM+MIMO DC-HSDPA DC-HSDPA+MIMO 4C-HSDPA+MIMO 4C-HSDPA 4C-HSDPA+MIMO DB-HSDPA+MIMO 4C-HSDPA DB-HSDPA
1.12.12.15 Number of HSDPA RABs Abnormal Released for Cell
Issue 01 (2013-05-04)
1246
Counters
Counter ID 67191162 67191163 Counter Name VS.HSDPA.RAB.AbnormRel VS.HSDPA.RAB.AbnormR el.RF VS.HSDPA.RAB.AbnormRel.64QAM VS.HSDPA.RAB.AbnormR el.MIMO64QAM VS.HSDPA.RAB.AbnormR el.DC Counter Description Number of HSDPA RABs Abnormal Released for Cell Number of HSDPA RABs Abnormal Released Due to RF Cause for Cell Number of HSDPA 64QAM RABs Abnormal Released for cell Number of HSDPA MIMO +64QAM RABs Abnormal Released for cell Number of DC-HSDPA RABs Abnormal Released in the primary carrier of DC counted for Cell(including RF Cause) Number of HSDPA MIMO RABs Abnormal Released for cell(Including RF Cause) Number of Abnormal DCHSDPA+MIMO RAB Releases in the Primary Carrier of DC-HSDPA for cell Number of Abnormally Released RABs for Cell When 3C-HSDPA with MIMO Applied (RF Exceptions Considered) Number of Abnormally Released RABs for Cell When 3C-HSDPA Applied (RF Exceptions Considered) Number of Abnormally Released RABs for Cell When 4C-HSDPA with MIMO Applied (RF Exceptions Considered) Number of Abnormal Released RABs for Cell When 4C-HSDPA Applied (RF Exceptions Considered)
73403819
73403826
73403830
73403832
VS.HSDPA.RAB.AbnormR el.MIMO VS.HSDPA.RAB.DCMIM O.AbnormRel
73423381
73426096
VS.HSDPA.RAB.AbnormRel.3CMIMO
73426100
VS.HSDPA.RAB.AbnormRel.3C
73426104
VS.HSDPA.RAB.AbnormRel.4CMIMO
73426112
VS.HSDPA.RAB.AbnormRel.4C
Issue 01 (2013-05-04)
1247
Counter ID 73426116
Counter Name VS.HSDPA.RAB.AbnormR el.DB
Counter Description Number of Abnormally Released RABs for Cell When DB-HSDPA Applied (RF Exceptions Considered) Number of Abnormally Released RABs of SRB over HSDPA Users for Cell
73426317
VS.HSDPA.RAB.AbnormR el.SRBoH
Description
These counters provide the number of times RABs are abnormally released when different technologies such as 64QAM, MIMO, and DC are used due to different factors including the RF failures in a serving cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. Note: Unless otherwise specified, SRB over HSDPA users are in the CELL_DCH state, and their SRBs are carried on the HSDPA channel. The following table describes the meaning of each counter. Counter Name VS.HSDPA.RAB.AbnormRel Description VS.HSDPA.RAB.AbnormRel provides the number of abnormal HSDPA RAB releases in a cell. VS.HSDPA.RAB.AbnormRel.RF provides the number of times HSDPA RABs are abnormally released due to RF failures in a cell. RF failures are indicated by the IEs "Radio Connection With UE Lost" and "Failure in the Radio Interface Procedure."
VS.HSDPA.RAB.AbnormRel.RF
Measurement point
As shown in point A of the following figure, when an exception occurs, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal release, the counters related to abnormal release when different technologies are used are measured.
Issue 01 (2013-05-04)
1248
As shown in point A of the following figure, when an exception occurs, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release, the counters related to abnormal release when different technologies are used are measured. Figure 1-542 RAB release IU REL procedure
Issue 01 (2013-05-04)
1249
As shown in point A of the following figure, when an exception occurs, the RNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release, the counters related to abnormal release when different technologies are used are measured. The cause values for normal release include "User Inactivity", "Normal Release", "Successful Relocation", and "Network Optimization". For details, see 3GPP TS 25.413. Figure 1-543 Iu connection release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.RAB.AbnormRel Feature ID WRFD-01061008 WRFD-010630 Feature Name Interactive and Background Traffic Class on HSDPA Streaming Traffic Class on HSDPA
Counter Name VS.HSDPA.RAB.AbnormR el.RF
Feature Name Interactive and Background Traffic Class on HSDPA Streaming Traffic Class on HSDPA
VS.HSDPA.RAB.AbnormRel.64QAM VS.HSDPA.RAB.AbnormR el.MIMO64QAM VS.HSDPA.RAB.AbnormR el.DC VS.HSDPA.RAB.AbnormR el.MIMO VS.HSDPA.RAB.DCMIM O.AbnormRel VS.HSDPA.RAB.AbnormRel.3CMIMO VS.HSDPA.RAB.AbnormRel.3C VS.HSDPA.RAB.AbnormRel.4CMIMO VS.HSDPA.RAB.AbnormRel.4C VS.HSDPA.RAB.AbnormR el.DB VS.HSDPA.RAB.AbnormR el.SRBoH
WRFD-010683 WRFD-010693 WRFD-010696 WRFD-010684 WRFD-010699 WRFD-150223 WRFD-150207 WRFD-150223 WRFD-150207 WRFD-150209 WRFD-010652
Downlink 64QAM DL 64QAM+MIMO DC-HSDPA 2 x 2 MIMO DC-HSDPA+MIMO 4C-HSDPA+MIMO 4C-HSDPA 4C-HSDPA+MIMO 4C-HSDPA DB-HSDPA SRB over HSDPA
1.12.12.16 Number of HSDPA RABs Normal Released for Cell Counters

Counter ID 67191164 67191161 Counter Name VS.HSDPA.RAB.NormRel VS.HSDPA.RAB.NormRel. UsrInact Counter Description Number of HSDPA RABs Normal Released for Cell Number of HSDPA RAB Releases Due to User Inactivity for Cell
Issue 01 (2013-05-04)
1251
Counter ID 73403820
Counter Name VS.HSDPA.RAB.NormRel. 64QAM VS.HSDPA.RAB.NormRel. MIMO VS.HSDPA.RAB.NormRel. MIMO64QAM VS.HSDPA.RAB.NormRel. DC
Counter Description Number of HSDPA 64QAM RABs Normal Released for Cell Number of HSDPA MIMO RABs Normal Released for cell Number of HSDPA MIMO +64QAM RABs Normal Released for cell Number of DC-HSDPA RABs Normal Released in the primary carrier of DC counted for Cell Number of Normal DCHSDPA+MIMO RAB Releases in the Primary Carrier of DC-HSDPA for cell Number of Normally Released RABs for Cell When 3C-HSDPA with MIMO Applied Number of Normally Released RABs for Cell When 3C-HSDPA Applied Number of Normally Released RABs for Cell When 4C-HSDPA with MIMO Applied Number of Normally Released RABs for Cell When DB-HSDPA with MIMO Applied Number of Normally Released RABs for Cell When 4C-HSDPA Applied Number of Normally Released RABs for Cell When DB-HSDPA Applied
73403823
73403827
73403831
73423380
VS.HSDPA.RAB.DCMIM O.NormRel
73426097
VS.HSDPA.RAB.NormRel. 3CMIMO
73426101
VS.HSDPA.RAB.NormRel. 3C VS.HSDPA.RAB.NormRel. 4CMIMO
73426105
73426109
VS.HSDPA.RAB.NormRel. DBMIMO
73426113
VS.HSDPA.RAB.NormRel. 4C VS.HSDPA.RAB.NormRel. DB
73426117
Issue 01 (2013-05-04)
1252
Description
These counters provide the number of times RABs are abnormally released when different technologies such as 64QAM, MIMO, and DC are used in a serving cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter. Counter Name VS.HSDPA.RAB.NormRel Description VS.HSDPA.RAB.NormRel provides the number of normal HSDPA RAB releases in a cell. VS.HSDPA.RAB.NormRel.UsrInact provides the number of normal HSDPA RAB releases due to user inactivity in a cell.
VS.HSDPA.RAB.NormRel.UsrInact
Measurement point
The measurement is triggered at point A as shown in the following figure. Upon receiving an IU RELEASE COMMAND message from the CN, the RNC releases related RABs and then sends the CN an IU RELEASE COMPLETE message. If the IU RELEASE COMPLETE message carries a cause value of normal release and HSDPA services are performed, the RNC measures the related counter in the serving cell according to the used technology. Figure 1-544 Iu release procedure
The measurement is triggered at point B as shown in the following figure. Upon receiving a RAB ASSIGNMENT REQUEST message that carries the RABs to be released, the RNC releases the related RABs and then sends the CN a RAB ASSIGNMENT RESPONSE message.
If the RAB ASSIGNMENT REQUEST message carries a cause value of normal release, HSDPA services are performed, and 4C-HSDPA is enabled, the RNC measures the related counter in the serving cell according to the used technology. The cause values for normal release include "User Inactivity", "Normal Release", "Successful Relocation", and "Network Optimization". For details, see 3GPP TS 25.413. Figure 1-545 Successful RAB release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.RAB.NormRel Feature ID WRFD-01061008 WRFD-010630 Feature Name Interactive and Background Traffic Class on HSDPA Streaming Traffic Class on HSDPA
Issue 01 (2013-05-04)
1254
Counter Name VS.HSDPA.RAB.NormRel. UsrInact
Feature Name Interactive and Background Traffic Class on HSDPA Streaming Traffic Class on HSDPA
VS.HSDPA.RAB.NormRel. 64QAM VS.HSDPA.RAB.NormRel. MIMO VS.HSDPA.RAB.NormRel. MIMO64QAM VS.HSDPA.RAB.NormRel. DC VS.HSDPA.RAB.DCMIM O.NormRel VS.HSDPA.RAB.NormRel. 3CMIMO VS.HSDPA.RAB.NormRel. 3C VS.HSDPA.RAB.NormRel. 4CMIMO VS.HSDPA.RAB.NormRel. DBMIMO VS.HSDPA.RAB.NormRel. 4C VS.HSDPA.RAB.NormRel. DB
WRFD-010683 WRFD-010684 WRFD-010693 WRFD-010696 WRFD-010699 WRFD-150223 WRFD-150207 WRFD-150223 WRFD-150227 WRFD-150207 WRFD-150209
Downlink 64QAM 2 x 2 MIMO DL 64QAM+MIMO DC-HSDPA DC-HSDPA+MIMO 4C-HSDPA+MIMO 4C-HSDPA 4C-HSDPA+MIMO DB-HSDPA+MIMO 4C-HSDPA DB-HSDPA
1.12.12.17 Number of Inter-RNC HSDPA Hard Handover Attempts for Cell (HSDPA to DCH) Counters
Counter ID 73403764 Counter Name VS.HSDPA.HHO.H2D.AttOutIur Counter Description number of Inter-RNC H2D Hard Handover Attempts for Cell
Issue 01 (2013-05-04)
1255
Counter ID 67191157
Counter Name VS.HSDPA.HHO.H2D.AttOutIntraFreq VS.HSDPA.HHO.H2D.AttOutInterFreq
Counter Description Number of Intra-Frequency H2D Hard Handover Attempts for Cell Number of Inter-Frequency H2D Hard Handover Attempts for Cell
67191159
Description
These counters provide the number of successful outgoing DCH hard handovers of different types on the HSDPA channel in a serving cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter. Counter Name VS.HSDPA.HHO.H2D.AttOutIur Description VS.HSDPA.HHO.H2D.AttOutIur provides the number of inter-RNC hard handover from HSDPA to DCH attempts in the serving cell. VS.HSDPA.HHO.H2D.AttOutIntraFreq provides the number of intra-frequency hard handover from HSDPA to DCH attempts in a cell. VS.HSDPA.HHO.H2D.AttOutInterFreq provides the number of inter-frequency hard handover from HSDPA to DCH attempts in a cell.
VS.HSDPA.HHO.H2D.AttOutIntraFreq
VS.HSDPA.HHO.H2D.AttOutInterFreq
Measurement point
During the hard handover from the HSDPA channel to the DCH, the RNC may send the UE the following messages: (1) RADIO BEARER RECONFIGURATION, (2) RADIO BEARER SETUP, (3) RADIO BEARER RELEASE. The measurement is triggered at point A as shown in the following figure. Assume that the RNC sends the UE a RADIO BEARER RECONFIGURATION message, the RNC measures these counters in the best cell before the hard handover according to the hard handover type.
Issue 01 (2013-05-04)
1256
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.HHO.H2D.AttOutIur VS.HSDPA.HHO.H2D.AttOutIntraFreq VS.HSDPA.HHO.H2D.AttOutInterFreq Feature ID WRFD-01061006 WRFD-01061006 WRFD-01061006 Feature Name HSDPA Mobility Management HSDPA Mobility Management HSDPA Mobility Management
1.12.12.18 Number of Successful inter-RNC HSDPA Hard Handovers for Cell (HSDPA to DCH)
Issue 01 (2013-05-04)
1257
Counters
Counter ID 73403765 Counter Name VS.HSDPA.HHO.H2D.SuccOutIur VS.HSDPA.HHO.H2D.SuccOutIntraFreq VS.HSDPA.HHO.H2D.SuccOutInterFreq Counter Description Number of Successful InterRNC H2D Hard Handovers for Cell Number of Successful IntraFrequency H2D Hard Handovers for Cell Number of Successful InterFrequency H2D Hard Handovers for Cell
67191158
67191160
Description
These counters provide the number of successful outgoing hard handovers of different types from the HSDPA channel to the DCH in a serving cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter. Counter Name VS.HSDPA.HHO.H2D.SuccOutIur Description VS.HSDPA.HHO.H2D.SuccOutIur provides the number of successful inter-RNC hard handovers from HSDPA to DCH in a cell. VS.HSDPA.HHO.H2D.SuccOutIntraFreq provides the number of successful intrafrequency hard handovers from HSDPA to DCH in a cell. VS.HSDPA.HHO.H2D.SuccOutInterFreq provides the number of successful interfrequency hard handovers from HSDPA to DCH in a cell.
VS.HSDPA.HHO.H2D.SuccOutIntraFreq
VS.HSDPA.HHO.H2D.SuccOutInterFreq
Measurement point
During the hard handover from the HSDPA channel to the DCH, the RNC may send the UE the following messages: (1) RADIO BEARER RECONFIGURATION, (2) RADIO BEARER SETUP, (3) RADIO BEARER RELEASE. The measurement is triggered at point B as shown in the following figure. Assume that the RNC sends the UE a RADIO BEARER RECONFIGURATION COMPLETE message, the RNC
measures these counters in the best cell before the hard handover according to the hard handover type. Figure 1-547 Dynamic channel configuration procedure (RB reconfiguration)
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.HHO.H2D.SuccOutIur VS.HSDPA.HHO.H2D.SuccOutIntraFreq VS.HSDPA.HHO.H2D.SuccOutInterFreq Feature ID WRFD-01061006 WRFD-01061006 WRFD-01061006 Feature Name HSDPA Mobility Management HSDPA Mobility Management HSDPA Mobility Management
1.12.12.19 Number of HSDPA UEs with Various Categories in a Cell
Issue 01 (2013-05-04)
1259
Counters
Counter ID 67204259 Counter Name VS.HSDPA.UE.Mean.CAT 1.6 VS.HSDPA.UE.Max.CAT1. 6 VS.HSDPA.UE.Mean.CAT 7.10 VS.HSDPA.UE.Max.CAT7. 10 VS.HSDPA.UE.Mean.CAT 11.12 VS.HSDPA.UE.Max.CAT1 1.12 VS.HSDPA.UE.Mean.CAT 13.14 VS.HSDPA.UE.Max.CAT1 3.14 VS.HSDPA.UE.Mean.CAT 15.16 VS.HSDPA.UE.Max.CAT1 5.16 VS.HSDPA.UE.Mean.CAT 17.20 VS.HSDPA.UE.Max.CAT1 7.20 VS.HSDPA.UE.Mean.CAT 21.24 Counter Description Average Number of HSDPA UEs with Category 1-6 in a Cell Maximum Number of HSDPA UEs with Category 1-6 in a Cell Average Number of HSDPA UEs with Category 7-10 in a Cell Maximum Number of HSDPA UEs with Category 7-10 in a Cell Average Number of HSDPA UEs with Category 11-12 in a Cell Maximum Number of HSDPA UEs with Category 11-12 in a Cell Average Number of HSDPA UEs with Category 13-14 in a Cell Maximum Number of HSDPA UEs with Category 13-14 in a Cell Average Number of HSDPA UEs with Category 15-16 in a Cell Maximum Number of HSDPA UEs with Category 15-16 in a Cell Average Number of HSDPA UEs with Category 17-20 in a Cell Maximum Number of HSDPA UEs with Category 17-20 in a Cell Average Number of HSDPA UEs with Category 21-24 in a Cell
67193578
67204260
67193581
67204261
67193584
67204262
67193587
67204263
67193590
67204264
67193593
67204265
Issue 01 (2013-05-04)
1260
Counter ID 67193596
Counter Name VS.HSDPA.UE.Max.CAT2 1.24 VS.HSDPA.UE.Max.CAT2 5.28 VS.HSDPA.UE.Mean.CAT 25.28 VS.HSDPA.UE.Mean.CAT 29 VS.HSDPA.UE.Max.CAT2 9 VS.HSDPA.UE.Mean.CAT 30 VS.HSDPA.UE.Max.CAT3 0 VS.HSDPA.UE.Mean.CAT 31 VS.HSDPA.UE.Max.CAT3 1 VS.HSDPA.UE.Mean.CAT 32 VS.HSDPA.UE.Max.CAT3 2
Counter Description Maximum Number of HSDPA UEs with Category 21-24 in a Cell Maximum Number of HSDPA UEs with Category 25-28 in a Cell Average Number of HSDPA UEs with Category 25-28 in a Cell Average number of Category 29 HSDPA users in a cell Maximum number of Category 29 HSDPA users in a cell Average number of Category 30 HSDPA users in a cell Maximum number of Category 30 HSDPA users in a cell Average number of Category 31 HSDPA users in a cell Maximum number of Category 31 HSDPA users in a cell Average number of Category 32 HSDPA users in a cell Maximum number of Category 32 HSDPA users in a cell
73423377
73441138
73426132 73426133
73426136 73426137
73426140 73426141
73426144 73426145
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67193583 Counter Name VS.HSDPA.UE.Mean.CAT 11.12.DENO VS.HSDPA.UE.Mean.CAT 11.12.NUM Counter Description Average Number of HSDPA UEs with Category 11-12 in a Cell(Denominator) Average Number of HSDPA UEs with Category 11-12 in a Cell(Numerator)
1261
67193582
Issue 01 (2013-05-04)
Counter ID 67193586
Counter Name VS.HSDPA.UE.Mean.CAT 13.14.DENO VS.HSDPA.UE.Mean.CAT 13.14.NUM VS.HSDPA.UE.Mean.CAT 15.16.DENO VS.HSDPA.UE.Mean.CAT 15.16.NUM VS.HSDPA.UE.Mean.CAT 17.20.DENO VS.HSDPA.UE.Mean.CAT 17.20.NUM VS.HSDPA.UE.Mean.CAT 1.6.DENO VS.HSDPA.UE.Mean.CAT 1.6.NUM VS.HSDPA.UE.Mean.CAT 21.24.DENO VS.HSDPA.UE.Mean.CAT 21.24.NUM VS.HSDPA.UE.Mean.CAT 25.28.DENO VS.HSDPA.UE.Mean.CAT 25.28.NUM VS.HSDPA.UE.Mean.CAT 7.10.DENO VS.HSDPA.UE.Mean.CAT 7.10.NUM
Counter Description Average Number of HSDPA UEs with Category 13-14 in a Cell(Denominator) Average Number of HSDPA UEs with Category 13-14 in a Cell(Numerator) Average Number of HSDPA UEs with Category 15-16 in a Cell(Denominator) Average Number of HSDPA UEs with Category 15-16 in a Cell(Numerator) Average Number of HSDPA UEs with Category 17-20 in a Cell(Denominator) Average Number of HSDPA UEs with Category 17-20 in a Cell(Numerator) Average num of CAT1-6 HSDPA UEs (Denominator) Average Number of HSDPA UEs with Category 1-6 in a Cell(Numerator) Average Number of HSDPA UEs with Category 21-24 in a Cell(Denominator) Average Number of HSDPA UEs with Category 21-24 in a Cell(Numerator) Average Number of HSDPA UEs with Category 25-28 in a Cell(Denominator) Average Number of HSDPA UEs with Category 25-28 in a Cell(Numerator) Average Number of HSDPA UEs with Category 7-10 in a Cell(Denominator) Average Number of HSDPA UEs with Category 7-10 in a Cell(Numerator)
67193585
67193589
67193588
67193592
67193591
67193577 67193576
67193595
67193594
73423376
73423375
67193580
67193579
Issue 01 (2013-05-04)
1262
Description
These counters provide the average and maximum number of HSDPA UEs with various categories in a serving cell. The HSDPA UEs with categories 21-28 using the multi-carrier HSDPA feature are only sampled in the cells with primary carriers.
Measurement point
The system takes samples of the number of HSDPA UEs with various categories every 5s. At the end of the measurement period, by dividing the accumulated value of sample data in the period by the number of samples, the average number of HSDPA UEs with various categories in the measurement period is obtained; by selecting the maximum value of sample data in the period, the maximum number of HSDPA UEs with various categories in the measurement period is obtained.
Formula
VS.HSDPA.UE.Mean.CAT1.6 = [VS.HSDPA.UE.Mean.CAT1.6.NUM]/ [VS.HSDPA.UE.Mean.CAT1.6.DENO] VS.HSDPA.UE.Mean.CAT7.10 = [VS.HSDPA.UE.Mean.CAT7.10.NUM]/ [VS.HSDPA.UE.Mean.CAT7.10.DENO] VS.HSDPA.UE.Mean.CAT11.12 = [VS.HSDPA.UE.Mean.CAT11.12.NUM]/ [VS.HSDPA.UE.Mean.CAT11.12.DENO] VS.HSDPA.UE.Mean.CAT13.14 = [VS.HSDPA.UE.Mean.CAT13.14.NUM]/ [VS.HSDPA.UE.Mean.CAT13.14.DENO] VS.HSDPA.UE.Mean.CAT15.16 = [VS.HSDPA.UE.Mean.CAT15.16.NUM]/ [VS.HSDPA.UE.Mean.CAT15.16.DENO] VS.HSDPA.UE.Mean.CAT17.20 = [VS.HSDPA.UE.Mean.CAT17.20.NUM]/ [VS.HSDPA.UE.Mean.CAT17.20.DENO] VS.HSDPA.UE.Mean.CAT21.24 = [VS.HSDPA.UE.Mean.CAT21.24.NUM]/ [VS.HSDPA.UE.Mean.CAT21.24.DENO] VS.HSDPA.UE.Mean.CAT25.28 = [VS.HSDPA.UE.Mean.CAT25.28.NUM]/ [VS.HSDPA.UE.Mean.CAT25.28.DENO]
Unit
None
Related Features
Counter Name VS.HSDPA.UE.Mean.CAT 1.6
Issue 01 (2013-05-04)
Feature Name HSDPA UE Category 1 to 28
1263
Counter Name VS.HSDPA.UE.Max.CAT1. 6 VS.HSDPA.UE.Mean.CAT 7.10 VS.HSDPA.UE.Max.CAT7. 10 VS.HSDPA.UE.Mean.CAT 11.12 VS.HSDPA.UE.Max.CAT1 1.12 VS.HSDPA.UE.Mean.CAT 13.14 VS.HSDPA.UE.Max.CAT1 3.14 VS.HSDPA.UE.Mean.CAT 15.16 VS.HSDPA.UE.Max.CAT1 5.16 VS.HSDPA.UE.Mean.CAT 17.20 VS.HSDPA.UE.Max.CAT1 7.20 VS.HSDPA.UE.Mean.CAT 21.24 VS.HSDPA.UE.Max.CAT2 1.24 VS.HSDPA.UE.Max.CAT2 5.28 VS.HSDPA.UE.Mean.CAT 25.28 VS.HSDPA.UE.Mean.CAT 29 VS.HSDPA.UE.Max.CAT2 9 VS.HSDPA.UE.Mean.CAT 30 VS.HSDPA.UE.Max.CAT3 0
Feature Name HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 DC-HSDPA+MIMO DC-HSDPA+MIMO 4C-HSDPA 4C-HSDPA 4C-HSDPA 4C-HSDPA
Issue 01 (2013-05-04)
1264
Counter Name VS.HSDPA.UE.Mean.CAT 31 VS.HSDPA.UE.Max.CAT3 1 VS.HSDPA.UE.Mean.CAT 32 VS.HSDPA.UE.Max.CAT3 2
Feature Name 4C-HSDPA 4C-HSDPA 4C-HSDPA 4C-HSDPA
1.12.12.20 Number of HSDPA MAC-d Flow Establishment Requests for Cell Counters
Counter ID 73393828 Counter Name VS.HSDPA.MACD.AttSetup Counter Description Number of HSDPA MAC-d Flow Establishment Requests for Cell
Description
This counter provides the number of HSDPA MAC-d flow establishment requests in the cell.For DC-HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement can be triggered at point A as shown in the figure. When the RNC sends the NodeB a RADIO LINK SETUP REQUEST message, this counter is measured in the HSDPA serving cell if the message contains the "HSDSCH FDD Information" IE.
Issue 01 (2013-05-04)
1265
Figure 1-548 Radio link setup procedure (successful operation)
The measurement can also be triggered at point A as shown in the figure. When the RNC sends the NodeB a RADIO LINK RECONFIGURATION PREPARE message, this counter is measured in the HSDPA serving cell if the message contains the "HSDSCH FDD Information" or "HS-DSCH MAC-d Flows To Add" IE. Figure 1-549 Synchronized RL reconfiguration commit procedure
Issue 01 (2013-05-04)
1266
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.MACD.AttSetup Feature ID WRFD-010610 Feature Name HSDPA Introduction Package
1.12.12.21 Number of Failed HSDPA Service Establishments Due to Insufficiency of Different Resources Counters
Counter ID 73393830 Counter Name VS.HSDPA.RAB.FailEstab. DLPower.Cong Counter Description Number of Failed HSDPA Service Establishments Due to DL Power Insufficiency for Cell Number of Failed HSDPA Service Establishments Due to DL Iub Bandwidth Insufficiency for Cell
73393831
VS.HSDPA.RAB.FailEstab. DLIUBBand.Cong
Description
These counters provide the number of HSDPA RABs failed to be established due to insufficiency of different resources in the HSDPA serving cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. VS.HSDPA.RAB.FailEstab.DLPower.Cong provides the number of HSDPA RABs failed to be established due to insufficient downlink power resources. VS.HSDPA.RAB.FailEstab.DLIUBBand.Cong provides the number of HSDPA RABs failed to be established due to insufficient downlink Iub bandwidth resources.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request,
it requests related radio resources. This counter is measured in the HSDPA serving cell when the RAB is for a HSDPA service and the resource request fails. Figure 1-550 Failed RAB establishments due to resource insufficiency
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.RAB.FailEstab. DLPower.Cong VS.HSDPA.RAB.FailEstab. DLIUBBand.Cong Feature ID WRFD-01061003 WRFD-01061003 Feature Name HSDPA Admission Control HSDPA Admission Control
1.12.12.22 Number of MIMO UEs in a Cell
Issue 01 (2013-05-04)
1268
Counters
Counter ID 73410492 Counter Name VS.HSDPA.MIMO.UE.Mea n.Cell Counter Description Average Number of MIMO UEs in a Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73393977 73393976 Counter Name VS.HSDPA.MIMO.UE.Mea n.Cell.DENO VS.HSDPA.MIMO.UE.Mea n.Cell.NUM Counter Description Average Number of MIMO UEs in a Cell(Denominator) Average Number of MIMO UEs in a Cell(Numerator)
Description
This counter provides the average number of MIMO UEs in a serving cell.For DC-HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The system periodically takes samples(sampling periodicity is 5 seconds) of the number of MIMO UEs. At the end of the measurement period, by dividing the accumulated value of sample data in the period by the number of samples, the average number of MIMO UEs in the measurement period is obtained.
Formula
VS.HSDPA.MIMO.UE.Mean.Cell = [VS.HSDPA.MIMO.UE.Mean.Cell.NUM]/ [VS.HSDPA.MIMO.UE.Mean.Cell.DENO]
Unit
None
Related Features
Counter Name VS.HSDPA.MIMO.UE.Mea n.Cell Feature ID WRFD-010684 Feature Name 2 x 2 MIMO
Issue 01 (2013-05-04)
1269
1.12.12.23 Number of Outgoing DRD Attempts for HSDPA Users Through Intelligent User Recognition for Cell Counters
Counter ID 73421686 Counter Name VS.HSDPA.DRD.AttOut.Int elligence Counter Description Number of Outgoing DRD Attempts for HSDPA Users Through Intelligent User Recognition for Cell Number of Incoming DRD Attempts for HSDPA Users Through Intelligent User Recognition for Cell
73421688
VS.HSDPA.DRD.AttIn.Intelligence
Description
These counters provide the number of times the RNC attempts to switch HSDPA users in connected mode into or out of the serving cell through the DRD procedure according to the intelligent user recognition algorithm in the HSDPA serving cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter. Counter Name VS.HSDPA.DRD.AttOut.Intelligence Description VS.HSDPA.DRD.AttOut.Intelligence provides the number of times the RNC attempts to switch HSDPA users in connected mode out of the serving cell through the DRD procedure according to the intelligent user recognition algorithm. VS.HSDPA.DRD.AttIn.Intelligence provides the number of times the RNC attempts to switch HSDPA users in connected mode into the serving cell through the DRD procedure according to the intelligent user recognition algorithm.
VS.HSDPA.DRD.AttIn.Intelligence
Measurement point
The measurement is triggered at point A as shown in the following figure. According to the intelligent user recognition algorithm, after the RNC receives a Channel Quality Indicator (CQI) measurement report from the NodeB, the RNC selects a proper target cell and then initiates an inter-frequency handover. Before the handover, the RNC takes statistics of the number of times that the RNC attempts to switch HSDPA users in connected mode out of the serving cell through
the DRD procedure. The RNC takes statistics of the number of times that the RNC attempts to switch HSDPA users in connected mode into the target cell through the DRD procedure. Figure 1-551 The DRD Process triggered by Intelligent User Recognition
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.DRD.AttOut.Int elligence VS.HSDPA.DRD.AttIn.Intelligence Feature ID WRFD-01061004 WRFD-01061004 Feature Name HSDPA Power Control HSDPA Power Control
Issue 01 (2013-05-04)
1271
1.12.12.24 Number of Successful Outgoing DRDs for HSDPA Users Through Intelligent User Recognition for Cell Counters
Counter ID 73421687 Counter Name VS.HSDPA.DRD.SuccOut.I ntelligence Counter Description Number of Successful Outgoing DRDs for HSDPA Users Through Intelligent User Recognition for Cell Number of Successful Incoming DRDs for HSDPA Users Through Intelligent User Recognition for Cell
73421689
VS.HSDPA.DRD.SuccIn.Int elligence
Description
These counters provide the number of times the RNC successfully switches HSDPA users in connected mode into or out of the serving cell through the DRD procedure according to the intelligent user recognition algorithm in the HSDPA serving cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter. Counter Name VS.HSDPA.DRD.SuccOut.Intelligence Description VS.HSDPA.DRD.SuccOut.Intelligence provides the number of times the RNC successfully switches HSDPA users in connected mode out of the serving cell through the DRD procedure according to the intelligent user recognition algorithm. VS.HSDPA.DRD.SuccIn.Intelligence provides the number of times the RNC successfully switches HSDPA users in connected mode into the serving cell through the DRD procedure according to the intelligent user recognition algorithm.
VS.HSDPA.DRD.SuccIn.Intelligence
Measurement point
The measurement is triggered at point B as shown in the following figure. When the RNC receives a PHYSICAL CHANNEL RECONFIG COMPLETE message from the UE, the RNC measures the number of times HSDPA users in connected mode are successfully switched out of the serving cell before the DRD procedure if an inter-frequency handover is to be performed on HSDPA users using the intelligent user recognition algorithm. The RNC measures the number of times HSDPA users are successfully switched into the target cell through the DRD procedure
in the target cell for DRD. Note that this counter is measured for only HSDPA users in connected mode. Figure 1-552 The DRD Process triggered by Intelligent User Recognition
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.DRD.SuccOut.I ntelligence VS.HSDPA.DRD.SuccIn.Int elligence Feature ID WRFD-01061004 WRFD-01061004 Feature Name HSDPA Power Control HSDPA Power Control
Issue 01 (2013-05-04)
1273
1.12.12.25 Number of RABs Abnormally Released for PS HSDPA Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell Counters
Counter ID 73422167 Counter Name VS.HSDPA.RAB.AbnormR el.H2P Counter Description Number of RABs Abnormally Released for PS HSDPA Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell Number of Abnormal RAB Releases for Cell During State Transition of DCHSDPA UEs to CELL/ URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of HSDPA +64QAM UEs to CELL/ URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of MIMO UEs to CELL/URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of DCHSDPA+MIMO UEs to CELL/URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of MIMO +64QAM UEs to CELL/ URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of 3CHSDPA UEs to CELL/ URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of 3CHSDPA+MIMO UEs to CELL/URA_PCH
1274
73425928
VS.HSDPA.RAB.AbnormR el.DC2P
73425929
VS.HSDPA.RAB.AbnormRel.64QAM2P
73425930
VS.HSDPA.RAB.AbnormR el.MIMO2P
73425931
VS.HSDPA.RAB.AbnormR el.DCMIMO2P
73425932
VS.HSDPA.RAB.AbnormR el.MIMO64QAM2P
73425933
VS.HSDPA.RAB.AbnormRel.3C2P
73425934
VS.HSDPA.RAB.AbnormRel.3CMIMO2P
Issue 01 (2013-05-04)
Counter ID 73425935
Counter Name VS.HSDPA.RAB.AbnormRel.4C2P
Counter Description Number of Abnormal RAB Releases for Cell During State Transition of 4CHSDPA UEs to CELL/ URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of 4CHSDPA+MIMO UEs to CELL/URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of DBHSDPA UEs to CELL/ URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of DBHSDPA+MIMO UEs to CELL/URA_PCH Number of Abnormally Released RABs During State Transition of SRB over HSDPA Users to CELL_PCH or URA_PCH for Cell
73425936
VS.HSDPA.RAB.AbnormRel.4CMIMO2P
73425937
VS.HSDPA.RAB.AbnormR el.DB2P
73425938
VS.HSDPA.RAB.AbnormR el.DBMIMO2P
73426316
VS.HSDPA.RAB.AbnormR el.SRBoH.H2P
Description
These counters provide the number of times RABs are abnormally released when different technologies such as 64QAM, MIMO, and DC are used due to different factors including the RF failures in a serving cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier. Note: Unless otherwise specified, SRB over HSDPA users are in the CELL_DCH state, and their SRBs are carried on the HSDPA channel.
Measurement point
As shown in point A of the following figure. When the UE fails to transit to CELL_PCH or URA_PCH, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal release, the counters related to abnormal release when different technologies are used are measured.
Issue 01 (2013-05-04)
1275
As shown in point A of the following figure. When the UE fails to transit to CELL_PCH or URA_PCH, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release, the counters related to abnormal release when different technologies are used are measured. Figure 1-554 RAB release IU REL procedure
Issue 01 (2013-05-04)
1276
As shown in point A of the following figure. When the UE fails to transit to CELL_PCH or URA_PCH, the RNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release, the counters related to abnormal release when different technologies are used are measured. The cause values for normal release include "User Inactivity", "Normal Release", "Successful Relocation", and "Network Optimization". For details, see 3GPP TS 25.413. Figure 1-555 IU release procedure triggered by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.RAB.AbnormR el.H2P Feature ID WRFD-010202 WRFD-010610 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) HSDPA Introduction Package
Counter Name VS.HSDPA.RAB.AbnormR el.DC2P VS.HSDPA.RAB.AbnormRel.64QAM2P VS.HSDPA.RAB.AbnormR el.MIMO2P VS.HSDPA.RAB.AbnormR el.DCMIMO2P VS.HSDPA.RAB.AbnormR el.MIMO64QAM2P VS.HSDPA.RAB.AbnormRel.3C2P VS.HSDPA.RAB.AbnormRel.3CMIMO2P VS.HSDPA.RAB.AbnormRel.4C2P VS.HSDPA.RAB.AbnormRel.4CMIMO2P VS.HSDPA.RAB.AbnormR el.DB2P VS.HSDPA.RAB.AbnormR el.DBMIMO2P VS.HSDPA.RAB.AbnormR el.SRBoH.H2P
Feature ID WRFD-010696 WRFD-010683 WRFD-010684 WRFD-010699 WRFD-010693 WRFD-150207 WRFD-150207 WRFD-150207 WRFD-150207 WRFD-150209 WRFD-150227 WRFD-010652
Feature Name DC-HSDPA Downlink 64QAM 2 x 2 MIMO DC-HSDPA+MIMO DL 64QAM+MIMO 4C-HSDPA 4C-HSDPA 4C-HSDPA 4C-HSDPA DB-HSDPA DB-HSDPA+MIMO SRB over HSDPA
1.12.12.26 Average Throughput on HSDPA MAC-d Flow for Cell (Excluding the Data of Low-Traffic Users) Counters
Counter ID 73441141 Counter Name VS.HSDPA.MeanChThroup ut.HighLoad Counter Description Mean Throughput on HSDPA MAC-d Flow for Cell (Excluding the Data of Low-Traffic Users)
Counter ID 73423463
Counter Name VS.HSDPA.Times.HighLoad
Counter Description Duration of Data Sending on HSDPA MAC-d flow for Cell (Excluding the Duration of Data Sending by LowTraffic Users)
Description
This counter provides the mean downlink throughput on HSDPA Single MAC-d flow in a cell. It excludes the data sent by low-traffic users.For DC-HSDPA users, this counter is measured only in the primary cell based on the total throughput on the primary and secondary carriers.
Measurement point
The amount of data that is sent in downlink on HSDPA MAC-d flow at the RLC layer (excluding the retransmitted RLC data and RLC headers) is measured every second in the serving cell. The amount of data that is measured in one second is considered as valid only when the amount of data received on the Iu interface within that second is greater than or equal to 80 KB and the amount of data in the RLC buffer within that second is greater than or equal to 80 KB. At the end of the measurement period, the mean throughput on HSDPA MAC-d flow is calculated by dividing the total amount of data that is considered as valid by the total period of valid time. Note that the total amount of data excludes the data sent by low-traffic users.
Formula
VS.HSDPA.MeanChThrouput.HighLoad = {8}*[VS.HSDPA.Traffic.HighLoad]/ [VS.HSDPA.Times.HighLoad]
Unit
kbit/s
Related Features
Counter Name VS.HSDPA.MeanChThroup ut.HighLoad Feature ID WRFD-010610 WRFD-01061008 Feature Name HSDPA Introduction Package Interactive and Background Traffic Class on HSDPA
1.12.12.27 Number of Bytes Sent on HSDPA MAC-d Flow for Cell (Excluding the Bytes of Low-Traffic Users)
Counters
Counter ID 73423462 Counter Name VS.HSDPA.Traffic.HighLoad Counter Description Number of Bytes Sent on HSDPA MAC-d Flow for Cell (Excluding the Bytes of Low-Traffic Users)
Description
This counter provides the number of bytes that are sent in downlink on HSDPA MAC-d flow in a cell. It excludes the number of bytes that are sent by low-traffic users.For DC-HSDPA users, this counter is measured only in the primary cell based on the total number of bytes sent on the primary and secondary carriers.
Measurement point
The number of bytes that are sent in downlink on HSDPA MAC-d flow at the RLC layer (excluding the retransmitted RLC data and RLC headers) is measured every second in the serving cell. The number of bytes that is measured in one second is calculated into the counter only when the amount of data received on the Iu interface within that second is greater than or equal to 80 KB and the amount of data in the RLC buffer within that second is greater than or equal to 80 KB. At the end of the measurement period, the number of bytes that can be calculated into the counter is accumulated. Note that the total number of bytes excludes the number of bytes sent by lowtraffic users at the RLC layer.
Formula
None
Unit
byte
Related Features
Counter Name VS.HSDPA.Traffic.HighLoad Feature ID WRFD-010610 WRFD-01061008 Feature Name HSDPA Introduction Package Interactive and Background Traffic Class on HSDPA
1.12.12.28 Number of Normal RAB Releases of HSDPA UEs for Cell (All Scenarios)
Counters
Counter ID 73425939 Counter Name VS.HSDPA.RAB.NormRel. DC.All VS.HSDPA.RAB.NormRel. 64QAM.All Counter Description Number of Normal RAB Releases of DC-HSDPA UEs for Cell (All Scenarios) Number of Normal RAB Releases of HSDPA +64QAM UEs for Cell (All Scenarios) Number of Normal RAB Releases of HSDPA+MIMO UEs for Cell (All Scenarios) Number of Normal RAB Releases of DC-HSDPA +MIMO UEs for Cell (All Scenarios) Number of Normal RAB Releases of HSDPA MIMO +64QAM UEs for Cell (All Scenarios) Number of Normal RAB Releases of 3C-HSDPA UEs for Cell (All Scenarios) Number of Normal RAB Releases of 3C-HSDPA +MIMO UEs for Cell (All Scenarios) Number of Normal RAB Releases of 4C-HSDPA UEs for Cell (All Scenarios) Number of Normal RAB Releases of 4C-HSDPA +MIMO UEs for Cell (All Scenarios) Number of Normal RAB Releases of DB-HSDPA UEs for Cell (All Scenarios) Number of Normal RAB Releases of DB-HSDPA +MIMO UEs for Cell (All Scenarios)
73425940
73425941
VS.HSDPA.RAB.NormRel. MIMO.All VS.HSDPA.RAB.NormRel. DCMIMO.All
73425942
73425943
VS.HSDPA.RAB.NormRel. MIMO64QAM.All
73425944
VS.HSDPA.RAB.NormRel. 3C.All VS.HSDPA.RAB.NormRel. 3CMIMO.All
73425945
73425946
VS.HSDPA.RAB.NormRel. 4C.All VS.HSDPA.RAB.NormRel. 4CMIMO.All
73425947
73425948
VS.HSDPA.RAB.NormRel. DB.All VS.HSDPA.RAB.NormRel. DBMIMO.All
73425949
Issue 01 (2013-05-04)
1281
Counter ID 73426318
Counter Name VS.HSDPA.RAB.NormRel. SRBoH.All
Counter Description Number of Normally Released RABs of SRB over HSDPA Users for Cell (All Scenarios)
Description
These counters provide the number of normal RAB releases in a cell where HSDPA is applied. For multi-carrier HSDPA UEs, these counters are measured only in the primary carrier cell. Note: The normal RAB releases on HSDPA channels include the RAB releases over the Iu interface and the switchover of the RAB from a technique to another one. The following uses DC-HSDPA as an example to describe a normal RAB release. (1)The DC-HSDPA RAB has been released over the Iu interface. (2)The RAB successfully falls back from DC-HSDPA to SC-HSDPA or R99 through a channel switchover procedure. In R99, the UE can be in the CELL_DCH, CELL_FACH, CELL_PCH, or URA_PCH state. (3)The RAB successfully falls back from DC-HSDPA to SC-HSDPA or to R99 in CELL_DCH state through an inter-cell hard handover procedure. Note: Unless otherwise specified, SRB over HSDPA users are in the CELL_DCH state, and their SRBs are carried on the HSDPA channel.
Measurement point
As shown by point A in figure 1 (HSDPA UEs enter the idle state), after receiving an IU RELEASE COMMAND message from the CN, the RNC releases the corresponding RAB and then sends an IU RELEASE COMPLETE message to the CN. This counter is increased by one in the serving cell where the UE camps when either of the following condition is met: The cause value in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization." Alternatively, the RNC has initiated a release request with the cause value "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before receiving the IU RELEASE COMMAND message.
Issue 01 (2013-05-04)
1282
As shown by point B in figure 2 (HSDPA UEs enter the idle state), after receiving an RAB ASSIGNMENT REQUEST message with an RAB release request from the CN, the RNC releases the corresponding RAB and then sends an RAB ASSIGNMENT RESPONSE message to the CN. This counter is increased by one in the serving cell where the UE camps when either of the following condition is met: The cause value in the RAB ASSIGNMENT REQUEST message is "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization." Alternatively, the RNC has initiated a release request with the cause value "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before receiving the RAB ASSIGNMENT REQUEST message.
Issue 01 (2013-05-04)
1283
As shown by point B in figure 3 (all types of hard handovers for HSDPA UEs), the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from a UE. If the UE is performing a hard handover on the RAB from a HSDPA channel to channels of other types, this counter is increased by one in the serving cell of the UE. As shown by point B in figure 3 (all types of channel switchovers for HSDPA UEs), the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from a UE. If the UE is performing a switchover on the RAB from a HSDPA channel to channels of other types, this counter is increased by one in the serving cell of the UE.
Issue 01 (2013-05-04)
1284
As shown by point B in figure 4 (all types of hard handovers for HSDPA UEs), the RNC receives a RADIO BEARER SETUP COMPLETE message from a UE. If the UE is performing a switchover of SRB from a HSDPA channel to channels of other types, this counter is increased by one in the serving cell of the UE. Figure 1-559 RB setup procedure (successful operation)
Issue 01 (2013-05-04)
1285
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.RAB.NormRel. DC.All VS.HSDPA.RAB.NormRel. 64QAM.All VS.HSDPA.RAB.NormRel. MIMO.All VS.HSDPA.RAB.NormRel. DCMIMO.All VS.HSDPA.RAB.NormRel. MIMO64QAM.All VS.HSDPA.RAB.NormRel. 3C.All VS.HSDPA.RAB.NormRel. 3CMIMO.All VS.HSDPA.RAB.NormRel. 4C.All VS.HSDPA.RAB.NormRel. 4CMIMO.All VS.HSDPA.RAB.NormRel. DB.All VS.HSDPA.RAB.NormRel. DBMIMO.All VS.HSDPA.RAB.NormRel. SRBoH.All Feature ID WRFD-010696 WRFD-010683 WRFD-010684 WRFD-010699 WRFD-010693 WRFD-150207 WRFD-150207 WRFD-150207 WRFD-150207 WRFD-150209 WRFD-150227 WRFD-010652 Feature Name DC-HSDPA Downlink 64QAM 2 x 2 MIMO DC-HSDPA+MIMO DL 64QAM+MIMO 4C-HSDPA 4C-HSDPA 4C-HSDPA 4C-HSDPA DB-HSDPA DB-HSDPA+MIMO SRB over HSDPA
1.12.12.29 Number of Abnormal Released RABs for Cell When DB-HSDPA with MIMO Applied (RF Exceptions Considered)
Counters
Counter ID 73426108 Counter Name VS.HSDPA.RAB.AbnormR el.DBMIMO Counter Description Number of Abnormal Released RABs for Cell When DB-HSDPA with MIMO Applied (RF Exceptions Considered)
Description
This counter provides the number of abnormally released RABs in a cell when DB-HSDPA with MIMO is applied. The instances are calculated in the cell with the primary carrier and RF exceptions are considered.
Measurement point
As shown by point A in the following figure, when an exception occurs, the RNC sends the CN an RAB RELEASE REQUEST message. When the RNC receives from the CN an RAB ASSIGNMENT REQUEST message with the cause value not being "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", this counter is increased by one in the serving cell where the UE in question camps if the UE is processing HSDPA services and DB-HSDPA with MIMO is applied. For details on cause values indicating abnormal RAB releases, see 3GPP TS 25.413. Figure 1-560 RAB release procedure
As shown by point A in the following figure, when an exception occurs, the RNC sends the CN an RAB RELEASE REQUEST message. When the RNC receives from the CN an IU RELEASE
COMMAND message with the cause value not being "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", this counter is increased by one in the serving cell where the UE in question camps if the UE is processing HSDPA services and DBHSDPA with MIMO is applied. For details on cause values indicating abnormal RAB releases, see 3GPP TS 25.413. Figure 1-561 RAB release IU REL procedure
As shown by point A in the following figure, when an exception occurs, the RNC sends the CN an IU RELEASE REQUEST message. When the RNC receives from the CN an IU RELEASE COMMAND message with the cause value not being "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", this counter is increased by one in the serving cell where the UE in question camps if the UE is processing HSDPA services and DBHSDPA with MIMO is applied. For details on cause values indicating abnormal RAB releases, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
1288
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.RAB.AbnormR el.DBMIMO Feature ID WRFD-150227 Feature Name DB-HSDPA+MIMO
1.12.13 HSUPA Measurement per cell(HSUPA.Cell)

Overview
This function subset is used to measure the number of attempts to set up and release the HSUPA RABs, and the number of attempts to switch the EDCH channels for the HSUPA service.
Issue 01 (2013-05-04)
1289
Counters
Counter ID 67203850 Counter Name VS.HSUPA.UE.Me an.Cell VS.HSUPA.MACD .SuccSetup Counter Description Average Number of HSUPA UEs in a Cell Number of Successful EDCH MAC-d Flow Establishments for Cell Number of HSUPA RAB Establishment Attempts for Cell Number of Successful HSUPA RAB Establishments for Cell Number of HSUPA RAB Establishment Attempts of BE Service for Golden Level User for Cell Number of HSUPA RAB Establishment Attempts of BE Service for Silver Level User for Cell Number of HSUPA RAB Establishment Attempts of BE Service for Copper Level User for Cell Number of Successful HSUPA RAB Establishments of BE Service for Golden Level User for Cell Number of Successful HSUPA RAB Establishments of BE Service for Silver Level User for Cell Original Release Earlier than V900R011 Earlier than V900R011
67192110
67192114
VS.HSUPA.RAB.A ttEstab VS.HSUPA.RAB.S uccEstab
67192115
67192969
VS.HSUPA.RAB.A ttEstab.BE.Golden
67192970
VS.HSUPA.RAB.A ttEstab.BE.Silver
67192971
VS.HSUPA.RAB.A ttEstab.BE.Copper
67192972
VS.HSUPA.RAB.S uccEstab.BE.Golden
67192973
VS.HSUPA.RAB.S uccEstab.BE.Silver
Issue 01 (2013-05-04)
1290
Counter ID 67192974
Counter Name VS.HSUPA.RAB.S uccEstab.BE.Copper
Counter Description Number of Successful HSUPA RAB Establishments of BE Service for Copper Level User for Cell Number of HSUPA RABs Abnormal Releases for Cell Number of HSUPA RABs Normal Released for Cell Number of HSUPA RAB Releases Due to UE Signal Connection Release for Cell Number of EDCH RL Addition and Deletion Attempts by Soft Handover for Cell Number of Successful EDCH RL Additions and Deletions by Soft Handover for Cell Number of Successful HSUPA Serving Cell Changes in Soft Handover Status for Cell Number of HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell Number of interRNC HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell
67192364
VS.HSUPA.RAB.A bnormRel VS.HSUPA.RAB.N ormRel VS.HSUPA.RAB.N ormRel.UEGen
67192365
67192366
67192367
VS.HSUPA.SHO.A ttOut
67192368
VS.HSUPA.SHO.S uccOut
67192369
VS.HSUPA.SHO.S ervCellChg.SuccOut
67192370
VS.HSUPA.SHO.S ervCellChg.AttOut
67195485
VS.HSUPA.SHO.S ervCellChg.AttOutIur
Issue 01 (2013-05-04)
1291
Counter ID 67195486
Counter Name VS.HSUPA.SHO.S ervCellChg.SuccOutIur
Counter Description Number of Successful interRNC HSUPA Serving Cell Changes in Soft Handover Status for Cell Number of Successful HSUPA Serving Cell Changes Due to inter-RNC Hard Handover without Channel Change for Cell Number of HSUPA Serving Cell Change Attempts Due to inter-RNC Hard Handover without Channel Change for Cell Number of Successful HSUPA Serving Cell Changes Due to Intra-Frequency Hard Handover without Channel Change for Cell Number of HSUPA Serving Cell Change Attempts Due to Intra-Frequency Hard Handover without Channel Change for Cell Number of Successful HSUPA Serving Cell Changes Due to Inter-Frequency Hard Handover without Channel Change for Cell
67195487
VS.HSUPA.HHO.E 2E.SuccOutIur
67195488
VS.HSUPA.HHO.E 2E.AttOutIur
67192371
VS.HSUPA.HHO.E 2E.SuccOutIntraFreq
67192372
VS.HSUPA.HHO.E 2E.AttOutIntraFreq
67192373
VS.HSUPA.HHO.E 2E.SuccOutInterFreq
Issue 01 (2013-05-04)
1292
Counter ID 67192374
Counter Name VS.HSUPA.HHO.E 2E.AttOutInterFreq
Counter Description Number of HSUPA Serving Cell Change Attempts Due to Inter-Frequency Hard Handover without Channel Change for Cell Number of Successful Channel Conversions from EDCH to DCH for HSUPA Service for Cell Number of Channel Conversion Attempts from EDCH to DCH for HSUPA Service for Cell Number of Successful HSUPA Intra-Frequency Hard Handovers for Cell(EDCH to DCH) Number of HSUPA Intra-Frequency Hard Handover Attempts for Cell (EDCH to DCH) Number of Successful HSUPA Inter-Frequency Hard Handovers for Cell(EDCH to DCH) Number of HSUPA Inter-Frequency Hard Handover Attempts for Cell (EDCH to DCH) Number of Successful Channel Conversions from DCH to EDCH for HSUPA Service for Cell
67192470
VS.HSUPA.E2D.Su cc
67192471
VS.HSUPA.E2D.At t
67192472
VS.HSUPA.HHO.E 2D.SuccOutIntraFreq
67192473
VS.HSUPA.HHO.E 2D.AttOutIntraFreq
67192474
VS.HSUPA.HHO.E 2D.SuccOutInterFreq
67192475
VS.HSUPA.HHO.E 2D.AttOutInterFreq
67192476
VS.HSUPA.D2E.Su cc
Issue 01 (2013-05-04)
1293
Counter ID 67192477
Counter Name VS.HSUPA.D2E.At t
Counter Description Number of Channel Conversion Attempts from DCH to EDCH for HSUPA Service for Cell Number of Channel Conversion Attempts from EDCH to FACH for HSUPA Service for Cell Number of Successful Channel Conversions from EDCH to FACH for HSUPA Service for Cell Number of Channel Conversion Attempts from FACH to EDCH for HSUPA Service for Cell Number of Successful Channel Conversions from FACH to EDCH for HSUPA Service for Cell Mean Uplink Throughput of single HSUPA MAC-d Flow for Cell Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow for Cell Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Golden Subscriber for Cell
67192480
VS.HSUPA.E2F.At t
67192481
VS.HSUPA.E2F.Su cc
67192482
VS.HSUPA.F2E.At t
67192483
VS.HSUPA.F2E.Su cc
67203932
VS.HSUPA.MeanChThroughput
67192486
VS.HSUPA.MeanC hThroughput.TotalBytes
67204513
VS.HSUPA.Golden BeMeanChThroug hput
Issue 01 (2013-05-04)
1294
Counter ID 67194873
Counter Name VS.HSUPA.Golden BeMeanChThroug hput.TotalBytes
Counter Description Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service for Golden Subscriber for Cell Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Silver Subscriber for Cell Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service for Silver Subscriber for Cell Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Copper Subscriber for Cell Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service for Copper Subscriber for Cell Maximum Number of HSUPA UEs in a Cell Number of interRNC HSUPA Hard Handover Attempts for Cell(EDCH to DCH) Number of Successful interRNC HSUPA Hard Handovers for Cell (EDCH to DCH)
67204514
VS.HSUPA.SilverBeMeanChThroug hput
67194875
VS.HSUPA.SilverB eMeanChThrough put.TotalBytes
67204515
VS.HSUPA.Copper BeMeanChThroug hput
67194889
VS.HSUPA.Copper BeMeanChThroug hput.TotalBytes
73403761
VS.HSUPA.UE.Ma x.Cell VS.HSUPA.HHO.E 2D.AttOutIur
V900R012
73403766
V900R012
73403767
VS.HSUPA.HHO.E 2D.SuccOutIur
V900R012
Issue 01 (2013-05-04)
1295
Counter ID 73403795
Counter Name VS.HSUPA.RAB. 16QAM.SuccEstab
Counter Description Number of Successful HSUPA 16QAM RAB Establishments for cell Number of HSUPA 16QAM RABs Abnormal Released Including RF Cause for cell Number of HSUPA 16QAM RABs Normal Released for cell Number of HSUPA 16QAM RAB Setup Attempts for cell Number of HSUPA RABs Abnormal Released due to RF Failures for Cell Average Number of HSUPA UEs with Category 1-4 in a Cell Average Number of HSUPA UEs with Category 5 in a Cell Average Number of HSUPA UEs with Category 6 in a Cell Average Number of HSUPA UEs with Category 7 in a Cell Maximum Number of HSUPA UEs with Category1-4 in a Cell Maximum Number of HSUPA UEs with Category 5 in a Cell
73403796
VS.HSUPA.RAB.A bnormRel.16QAM
V900R012
73403797
VS.HSUPA.RAB.N ormRel.16QAM
V900R012
73403794
VS.HSUPA.RAB. 16QAM.AttEstab VS.HSUPA.RAB.A bnormRel.RF
V900R012
73391136
V900R012
67204266
VS.HSUPA.UE.Me an.CAT1.4
V900R012
67204267
VS.HSUPA.UE.Me an.CAT5 VS.HSUPA.UE.Me an.CAT6 VS.HSUPA.UE.Me an.CAT7 VS.HSUPA.UE.Ma x.CAT1.4 VS.HSUPA.UE.Ma x.CAT5
V900R012
67204268
V900R012
67204269
V900R012
67193599
V900R012
67193602
V900R012
Issue 01 (2013-05-04)
1296
Counter ID 67193605
Counter Name VS.HSUPA.UE.Ma x.CAT6 VS.HSUPA.UE.Ma x.CAT7 VS.HSUPA.MACD .AttSetup VS.HSUPA.RAB.F ailEstab.ULPower. Cong
Counter Description Maximum Number of HSUPA UEs with Category 6 in a Cell Maximum Number of HSUPA UEs with Category 7 in a Cell Number of EDCH MAC-d Flow Setup Requests for Cell Number of Failed HSUPA Service Establishments Due to UL Power Insufficiency for Cell Number of Failed HSUPA Service Establishments Due to UL Iub Bandwidth Insufficiency for Cell Number of Failed HSUPA Service Establishments Due to UL CE Insufficiency for Cell Average uplink throughput of the Traffic PS Conversational beared on E-DCH for cell Number of uplink bytes of Transport Blocks of Traffic PS Conversational beared on E-DCH for cell Number of Times that HSUPA 2ms TTI Users Transfer from Small Retransmission to Large Retransmission for Cell
67193608
V900R012
73393829
V900R012
73393832
V900R012
73393833
VS.HSUPA.RAB.F ailEstab.ULIUBBa nd.Cong
V900R012
73393834
VS.HSUPA.RAB.F ailEstab.ULCE.Co ng
V900R012
73410485
VS.PS.Conv.Kbps. EDCH
V900R012
73393914
VS.PS.Conv.Traffi c.EDCH
V900R012
73393956
VS.HSUPA.RsnSm all2Large.TTI2ms
V900R012
Issue 01 (2013-05-04)
1297
Counter ID 73393957
Counter Name VS.HSUPA.RsnSm all2Large.TTI10ms
Counter Description Number of Times that HSUPA 10ms TTI Users Transfer from Small Retransmission to Large Retransmission for Cell Number of Times that HSUPA 2ms TTI Users Transfer from Large Retransmission to Small Retransmission for Cell Number of Times that HSUPA 10ms TTI Users Transfer from Large Retransmission to Small Retransmission for Cell Number of TTI Switch Attempts During RB Reconfiguration for Cell(2ms to 10ms) Number of Successful TTI Switches During RB Reconfiguration for Cell(2ms to 10ms) Number of TTI Switch Attempts During RB Reconfiguration for Cell(10ms to 2ms) Number of Successful TTI Switches During RB Reconfiguration for Cell(10ms to 2ms)
73393958
VS.HSUPA.RsnLa rge2Small.TTI2ms
V900R012
73393959
VS.HSUPA.RsnLa rge2Small.TTI10m s
V900R012
73393984
VS.HSUPA.TTI2to 10.Att
V900R012
73393985
VS.HSUPA.TTI2to 10.Succ
V900R012
73393986
VS.HSUPA.TTI10t o2.Att
V900R012
73393987
VS.HSUPA.TTI10t o2.Succ
V900R012
Issue 01 (2013-05-04)
1298
Counter ID 73410507
Counter Name VS.HSUPA. 16QAM.UE.Mean. Cell VS.HSUPA.Boostin g.UE.Mean.Cell
Counter Description Average Number of HSUPA 16QAM UEs in a Cell Number of UEs Supporting EDPCCH Boosting for Cell Number of UEs Supporting EDPCCH Boosting and CPC for Cell Number of RABs Abnormally Released for PS HSUPA Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell Number of HSUPA Boosting RAB Setup Attempts for Cell Number of Successful HSUPA Boosting RAB Setups for Cell Number of Abnormally Released HSUPA Boosting RABs for Cell Number of Normally Released HSUPA Boosting RABs for Cell Number of HARQ PO Reconfiguration Attempts of HSUPA Users with 10 ms TTI for Cell
73441120
V900R013
73441121
VS.HSUPA.Boostin gCPC.UE.Mean.Ce ll VS.HSUPA.RAB.A bnormRel.E2P
V900R013
73422168
V900R012
73423359
VS.HSUPA.RAB.B oosting.AttEstab VS.HSUPA.RAB.B oosting.SuccEstab
V900R013
73423360
V900R013
73423361
VS.HSUPA.RAB.A bnormRel.Boosting
V900R013
73423362
VS.HSUPA.RAB.N ormRel.Boosting
V900R013
73423567
VS.HSUPA.HARQ. POReCfgAtt.TTI1 0ms
V900R013
Issue 01 (2013-05-04)
1299
Counter ID 73423568
Counter Name VS.HSUPA.HARQ. POReCfgSucc.TTI 10ms
Counter Description Number of Successful HARQ PO Reconfigurations of HSUPA Users with 10 ms TTI for Cell Number of DCHSUPA RAB Setup Attempts for Cell Number of Successful DCHSUPA RAB Setups for Cell Number of DCHSUPA RABs Normally Released for Cell Number of DCHSUPA RABs Abnormally Released for Cell Average Number of HSUPA UEs with Category 8 in a Cell Maximum Number of HSUPA UEs with Category 8 in a Cell Average Number of HSUPA UEs with Category 9 in a Cell Maximum Number of HSUPA UEs with Category 9 in a Cell Mean Number of DC-HSUPA Users in the Cell with the Primary Carrier Mean Number of DC-HSUPA Users in the Cell with the Secondary Carrier
73424115
VS.HSUPA.RAB.D C.AttEstab VS.HSUPA.RAB.D C.SuccEstab
V900R014
73424116
V900R014
73424117
VS.HSUPA.RAB.D C.NormRel
V900R014
73424118
VS.HSUPA.RAB.D C.AbnormRel
V900R014
73441235
VS.HSUPA.UE.Me an.CAT8 VS.HSUPA.UE.Ma x.CAT8 VS.HSUPA.UE.Me an.CAT9 VS.HSUPA.UE.Ma x.CAT9 VS.HSUPA.DC.PR IM.UE.Mean.Cell
V900R014
73424186
V900R014
73441236
V900R014
73424189
V900R014
73424192
V900R014
73441238
VS.HSUPA.DC.SE C.UE.Mean.Cell
V900R014
Issue 01 (2013-05-04)
1300
Counter ID 73441239
Counter Name VS.HSUPA.UE.Me an.TTI2ms VS.HSUPA.UE.Ma x.TTI2ms VS.HSUPA.UE.Me an.TTI10ms VS.HSUPA.UE.Ma x.TTI10ms VS.HSUPA.RABEs tabTTI10ms.AdmC E.Succ
Counter Description Average Number of HSUPA 2 ms TTI UEs in a Cell Maximum Number of HSUPA 2 ms TTI UEs in a Cell Average number of HSUPA 10 ms TTI UEs in a Cell Maximum Number of HSUPA 10 ms TTI UEs in a Cell Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI Due to Congestion of Admitted CEs in a Cell Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI Due to RTWP Congestion in a Cell Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI Due to Congestion of Occupied CEs in a Cell
73424199
V900R014
73441240
V900R014
73424202
V900R014
73424205
V900R014
73424206
VS.HSUPA.RABEs tabTTI10ms.ResR TWP.Succ
V900R014
73424207
VS.HSUPA.RABEs tabTTI10ms.ResUs edCE.Succ
V900R014
Issue 01 (2013-05-04)
1301
Counter ID 73424208
Counter Name VS.HSUPA.RABEs tabTTI10ms.ResIU B.Succ
Counter Description Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI Due to Iub Resource Congestion in a Cell Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI Due to Limited Uplink Coverage Number of Abnormal RAB Releases for Cell During State Transition of HSUPA+16QAM UEs to CELL/ URA_PCH Number of Abnormal RAB Releases for Cell During State Transition of DCHSUPA UEs to CELL/URA_PCH Number of Normal RAB Releases of HSUPA+16QAM UEs for Cell (All Scenarios) Number of Normal RAB Releases of DC-HSUPA UEs for Cell (All Scenarios)
73424967
VS.HSUPA.RABEs tabTTI10ms.Cover .Succ
V900R014
73425950
VS.HSUPA.RAB.A bnormRel. 16QAM2P
V900R015
73425951
VS.HSUPA.RAB.A bnormRel.DC2P
V900R015
73425952
VS.HSUPA.RAB.N ormRel. 16QAM.All
V900R015
73425953
VS.HSUPA.RAB.N ormRel.DC.All
V900R015
Issue 01 (2013-05-04)
1302
Counter VS.HSUPA.RAB.AttEstab Sub Counter VS.HSUPA.RAB.AttEstab.BE.Golden VS.HSUPA.RAB.AttEstab.BE.Silver VS.HSUPA.RAB.AttEstab.BE.Copper VS.HSUPA.RAB.SuccEstab VS.HSUPA.RAB.SuccEstab.BE.Golden VS.HSUPA.RAB.SuccEstab.BE.Silver VS.HSUPA.RAB.SuccEstab.BE.Copper
1.12.13.1 Number of HSUPA UEs in a Cell Counters

Counter ID 67203850 73403761 Counter Name VS.HSUPA.UE.Mean.Cell VS.HSUPA.UE.Max.Cell Counter Description Average Number of HSUPA UEs in a Cell Maximum Number of HSUPA UEs in a Cell
Description
These counters provide the average and maximum number of HSUPA UEs in active set cells.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of the number of HSUPA UEs. At the end of the measurement period, by dividing the accumulated value of sample data in the period by the number of samples, the average number of HSUPA UEs in the measurement period is obtained; by selecting the maximum value of sample data in the period, the maximum number of HSUPA UEs in the measurement period is obtained.
Formula
None
Unit
None
Issue 01 (2013-05-04)
1303
Related Features
Counter Name VS.HSUPA.UE.Mean.Cell Feature ID WRFD-01061211 WRFD-010634 WRFD-010639 VS.HSUPA.UE.Max.Cell WRFD-01061202 WRFD-020101 Feature Name 20 HSUPA Users per Cell 60 HSUPA Users per Cell 96 HSUPA Users per Cell HSUPA Admission Control Admission Control
1.12.13.2 Number of Successful EDCH MAC-d Flow Establishments for Cell Counters
Counter ID 67192110 Counter Name VS.HSUPA.MACD.SuccSetup Counter Description Number of Successful EDCH MAC-d Flow Establishments for Cell
Description
This measurement item takes statistics of the number of successful EDCH MAC-d flow establishments for UE by RNC in a cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point C as shown in Figure. When the RNC sends a RADIO LINK RECONFIGURATION COMMIT message to the NodeB, the RNC measures this item in the cell where the radio link exists if the HSUPA RABs are setup. During the reconfiguration of the radio link, the HSUPA RABs are set up if the message RADIO LINK RECONFIGURATION PREPARE contains the newly added EDCH MACD FLOW.
Issue 01 (2013-05-04)
1304
Figure 1-563 Synchronized RL reconfiguration commit procedure
This measurement is triggered at point B as shown in Figure. When the RNC sends a RADIO LINK SETUP REQUEST/RADIO LINK ADDITION REQUEST message to the NodeB, the RNC measures this item in the cell where the radio link is successfully set up for the HSUPA service if the RNC receives a RADIO LINK SETUP RESPONSE/RADIO LINK ADDITION RESPONSE message from the NodeB. During the setup of the radio link, the radio link for the HSUPA cell will be established if the RADIO LINK SETUP REQUEST/RADIO LINK ADDITION REQUEST message contains the EDCH FDD Information.
Issue 01 (2013-05-04)
1305
Figure 1-564 RL setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.MACD.SuccSetup Feature ID WRFD-010612 Feature Name HSUPA Introduction Package
1.12.13.3 Number of HSUPA RAB Establishment Attempts for Cell Counters

Counter ID 67192114 Counter Name VS.HSUPA.RAB.AttEstab Counter Description Number of HSUPA RAB Establishment Attempts for Cell
Issue 01 (2013-05-04)
1306
Description
This measurement item takes statistics of the number of HSUPA RAB establishment attempts in a cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN, and if the the RNC decides the HSUPA RABs, it measures this item in the HSUPA serving cell. Figure 1-565 RAB setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.AttEstab Feature ID WRFD-01061206 WRFD-010632 Feature Name Interactive and Background Traffic Class on HSUPA Streaming Traffic Class on HSUPA
1.12.13.4 Number of Successful HSUPA RAB Establishments for Cell Counters

Counter ID 67192115 Counter Name VS.HSUPA.RAB.SuccEstab Counter Description Number of Successful HSUPA RAB Establishments for Cell
Description
This measurement item takes statistics of the number of successful HSUPA RAB establishments in a cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point B as shown in the figure. When the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE and sends a RAB ASSIGNMENT RESPONSE message to the CN, the RNC measures this item in the HSUPA serving cell if the assignment is for establishing the HSUPA RABs. Figure 1-566 RAB setup procedure (successful operation)
Issue 01 (2013-05-04)
1308
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.SuccEstab Feature ID WRFD-01061206 WRFD-010632 Feature Name Interactive and Background Traffic Class on HSUPA Streaming Traffic Class on HSUPA
1.12.13.5 Number of HSUPA RAB establish attempts of BE Service for different prior Level Users (Cell) Counters
Counter ID 67192969 Counter Name VS.HSUPA.RAB.AttEstab. BE.Golden Counter Description Number of HSUPA RAB Establishment Attempts of BE Service for Golden Level User for Cell Number of HSUPA RAB Establishment Attempts of BE Service for Silver Level User for Cell Number of HSUPA RAB Establishment Attempts of BE Service for Copper Level User for Cell
67192970
VS.HSUPA.RAB.AttEstab. BE.Silver
67192971
VS.HSUPA.RAB.AttEstab. BE.Copper
Description
These counters provide the number of HSUPA RAB establishment attempts of BE service for different prior level users (golden, silver, and copper users) in the HSUPA serving cell. For DCHSUPA users, these counters are measured only in the cell with the primary carrier.
Issue 01 (2013-05-04)
1309
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the CN a RAB ASSIGNMENT REQUEST message for setting up the HSUPA service,the RNC measures the items by the prior lever in the HSUPA serving cell. Figure 1-567 RAB setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.AttEstab. BE.Golden VS.HSUPA.RAB.AttEstab. BE.Silver VS.HSUPA.RAB.AttEstab. BE.Copper Feature ID WRFD-01061206 WRFD-01061206 WRFD-01061206 Feature Name Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA
Issue 01 (2013-05-04)
1310
1.12.13.6 Number of Successful HSUPA RAB Establishments of BE Service for different prior Level Users (Cell) Counters
Counter ID 67192972 Counter Name VS.HSUPA.RAB.SuccEstab .BE.Golden Counter Description Number of Successful HSUPA RAB Establishments of BE Service for Golden Level User for Cell Number of Successful HSUPA RAB Establishments of BE Service for Silver Level User for Cell Number of Successful HSUPA RAB Establishments of BE Service for Copper Level User for Cell
67192973
VS.HSUPA.RAB.SuccEstab .BE.Silver
67192974
VS.HSUPA.RAB.SuccEstab .BE.Copper
Description
These counters provide the number of successful HSUPA RAB establishments of BE service for different prior level users (golden, silver, and copper users) in the HSUPA serving cell. For DC-HSUPA users, these counters are measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point B as shown in the figure. After receiving a RADIO BEARER SETUP COMPLETE message from a UE, the RNC sends a RAB ASSIGNMENT RESPONSE message to the CN. If the assignment is for setting up the HSUPA service, the RNC measures the items by the prior lever in the HSUPA serving cell.
Issue 01 (2013-05-04)
1311
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.SuccEstab .BE.Golden VS.HSUPA.RAB.SuccEstab .BE.Silver VS.HSUPA.RAB.SuccEstab .BE.Copper Feature ID WRFD-01061206 WRFD-01061206 WRFD-01061206 Feature Name Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA
1.12.13.7 Number of HSUPA RABs Abnormal Released for Cell
Issue 01 (2013-05-04)
1312
Counters
Counter ID 67192364 Counter Name VS.HSUPA.RAB.AbnormRel Counter Description Number of HSUPA RABs Abnormal Releases for Cell
Description
This measurement item takes statistics of the number of HSUPA RABs abnormal released by the RNC in a cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", reference to 3GPP TS 25.413),the RNC measures the items in the HSUPA serving cell if the released RAB is a HSUPA service. Figure 1-569 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", reference to 3GPP TS 25.413),the RNC measures the items in the HSUPA serving cell if the released RAB is a HSUPA service.
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", reference to 3GPP TS 25.413),the RNC measures the items in the HSUPA serving cell if the released RAB is a HSUPA service. Figure 1-571 Iu connection release procedure
Issue 01 (2013-05-04)
1314
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.AbnormRel Feature ID WRFD-01061206 WRFD-010632 Feature Name Interactive and Background Traffic Class on HSUPA Streaming Traffic Class on HSUPA
1.12.13.8 Number of HSUPA RABs Normal Released for Cell Counters

Counter ID 67192365 Counter Name VS.HSUPA.RAB.NormRel Counter Description Number of HSUPA RABs Normal Released for Cell
Description
This measurement item takes statistics of the number of HSUPA RABs normally released by the RNC in the HSUPA serving cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release", the RNC measures the item in the HSUPA serving cell if it is a HSUPA service.
Issue 01 (2013-05-04)
1315
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release" ,the RNC measures the item in the HSUPA serving cell if it is a HSUPA service.
Issue 01 (2013-05-04)
1316
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.NormRel Feature ID WRFD-01061206 WRFD-010632 Feature Name Interactive and Background Traffic Class on HSUPA Streaming Traffic Class on HSUPA
1.12.13.9 Number of HSUPA RAB Released due to UE Signaling Connection failure for Cell
Issue 01 (2013-05-04)
1317
Counters
Counter ID 67192366 Counter Name VS.HSUPA.RAB.NormRel. UEGen Counter Description Number of HSUPA RAB Releases Due to UE Signal Connection Release for Cell
Description
This measurement item takes statistics of the number of HSUPA RABs released by the RNC due to UE Signal Connection Release.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point A shown in the figure. When the RNC received a SIGNALLING CONNECTION RELEASE INDICATION message from UE, it sends an IU RELEASE REQUEST message to the CN. And the RNC will releases corresponding RABs after it receives an IU RELEASE COMMAND message from the CN. When the RNC sends an IU RELEASE COMPLETE message to the CN, the RNC measures the item in the HSUPA serving cell if the released RAB is HSUPA service. Figure 1-574 UL SIG connection release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.NormRel. UEGen Feature ID WRFD-01061206 WRFD-010632 Feature Name Interactive and Background Traffic Class on HSUPA Streaming Traffic Class on HSUPA
1.12.13.10 Number of EDCH RL Addition and Deletion Attempts by Soft Handover for Cell Counters
Counter ID 67192367 Counter Name VS.HSUPA.SHO.AttOut Counter Description Number of EDCH RL Addition and Deletion Attempts by Soft Handover for Cell
Description
This measurement item takes statistics of the number of EDCH RL addition and deletion attempts by soft handover in a cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point B as shown in the figure. When the RNC sends an ACTIVE SET UPDATE message to the UE and there is EDCH RL to be deleted or added during the soft handover, the RNC measures this item in the cell where the EDCH link is added or deleted.
Issue 01 (2013-05-04)
1319
Figure 1-575 Soft handover procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.SHO.AttOut Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.11 Number of Successful EDCH RL Additions and Deletions by Soft Handover for Cell
Issue 01 (2013-05-04)
1320
Counters
Counter ID 67192368 Counter Name VS.HSUPA.SHO.SuccOut Counter Description Number of Successful EDCH RL Additions and Deletions by Soft Handover for Cell
Description
This measurement item takes statistics of the number of successful EDCH RL additions and deletions due to soft handover in a cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point C as shown in the figure. When the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE and an EDCH link is added or deleted during the soft handover, the RNC measures this item in the cell where the EDCH link is added or deleted. Figure 1-576 Soft handover procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.SHO.SuccOut Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.12 Number of Successful HSUPA Serving Cell Changes in Soft Handover Status for Cell Counters
Counter ID 67192369 Counter Name VS.HSUPA.SHO.ServCellC hg.SuccOut Counter Description Number of Successful HSUPA Serving Cell Changes in Soft Handover Status for Cell
Description
This measurement item takes statistics of the number of successful HSUPA serving cell changes in soft handover status for cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement item takes statistics of the number of successful HSUPA serving cell changes in soft handover status for cell. This procedure can be triggered with the following messages: [1]PHYSICAL CHANNEL RECONFIGURATION,[2]TRANSPORT CHANNEL RECONFIGURATION,[3]RADIO BEARER RECONFIGURATION message. Accordingly, UE may send [1]PHYSICAL CHANNEL RECONFIGURATION COMPLETE,[2]PHYSICAL CHANNEL RECONFIGURATION FAILURE,[3]TRANSPORT CHANNEL RECONFIGURATION COMPLETE,[4]TRANSPORT CHANNEL RECONFIGURATION FAILURE,[5]RADIO BEARER RECONFIGURATION COMPLETE,[6]RADIO BEARER RECONFIGURATION FAILURE message to RNC as a response. This measurement is triggered at point B as shown in Figure, the procedure shown in the figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an example. When the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the RNC measures this item in the original HSUPA serving cell if the HSUPA serving cell is changed. The item is used to indicate the change of HSUPA serving cells in the soft handover state instead of the hard handover state.
Issue 01 (2013-05-04)
1322
Figure 1-577 Serving cell change procedure (successful operation)
This measurement triggered at point C as shown in Figure , when the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE. If the HSUPA serving cell changes during the soft handover, the RNC measures this item in the original HSUPA serving cell. Figure 1-578 Soft handover procedure (successful operation)
Issue 01 (2013-05-04)
1323
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.SHO.ServCellC hg.SuccOut Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.13 Number of HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell Counters
Counter ID 67192370 Counter Name VS.HSUPA.SHO.ServCellC hg.AttOut Counter Description Number of HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell
Description
This measurement item takes statistics of the number of HSUPA serving cell change attempts in soft handover status for cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement item takes statistics of the number of HSUPA serving cell change attempts in soft handover status for cell. This procedure can be triggered with the following messages: [1]PHYSICAL CHANNEL RECONFIGURATION,[2]TRANSPORT CHANNEL RECONFIGURATION,[3]RADIO BEARER RECONFIGURATION message. Accordingly, UE may send [1]PHYSICAL CHANNEL RECONFIGURATION COMPLETE,[2]PHYSICAL CHANNEL RECONFIGURATION FAILURE,[3]TRANSPORT CHANNEL RECONFIGURATION COMPLETE,[4]TRANSPORT CHANNEL RECONFIGURATION FAILURE,[5]RADIO BEARER RECONFIGURATION COMPLETE,[6]RADIO BEARER RECONFIGURATION FAILURE message to RNC as a response. This measurement is triggered at point A as shown in Figure, the procedure shown in the figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an example. When the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC measures this item in the original HSUPA serving cell if the HSUPA serving cell is changed. This item is used to indicate the change of HSUPA serving cells in the soft handover status instead of the hard handover status.
This measurement triggered at point B as shown in Figure , when the RNC sends an ACTIVE SET UPDATE message to the UE. If the HSUPA serving cell changes during the soft handover, the RNC measures this item in the original HSUPA serving cell. Figure 1-580 Soft handover procedure (successful operation)
Issue 01 (2013-05-04)
1325
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.SHO.ServCellC hg.AttOut Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.14 Number of inter-RNC HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell Counters
Counter ID 67195485 Counter Name VS.HSUPA.SHO.ServCellC hg.AttOutIur Counter Description Number of inter-RNC HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell
Description
This measurement counter takes statistics of the number of inter-RNC HSUPA serving cell change attempts in soft handover status for cell. It is measured in a serving cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement counter takes statistics of the number of inter-RNC HSUPA serving cell change attempts in soft handover status for cell. It is mearued in a serving cell. This procedure can be triggered with the following messages:[1]PHYSICAL CHANNEL RECONFIGURATION,[2]TRANSPORT CHANNEL RECONFIGURATION,[3]RADIO BEARER RECONFIGURATION message. Accordingly, UE may send [1]PHYSICAL CHANNEL RECONFIGURATION COMPLETE,[2]PHYSICAL CHANNEL RECONFIGURATION FAILURE,[3]TRANSPORT CHANNEL RECONFIGURATION COMPLETE,[4]TRANSPORT CHANNEL RECONFIGURATION FAILURE,[5]RADIO BEARER RECONFIGURATION COMPLETE,[6]RADIO BEARER RECONFIGURATION FAILURE message to RNC as a response. This measurement is triggered at point A as shown in Figure, the procedure shown in the figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an example, when the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE. If the HSUPA serving cell changes, the RNC
measures this item in the original HSUPA serving cell. This item is used to indicate the change of HSUPA serving cells in the soft handover status instead of the hard handover status. Figure 1-581 Serving cell change procedure (successful operation)
This measurement is triggered at point B as shown in Figure, when the RNC sends an ACTIVE SET UPDATE message to the UE. If the HSUPA serving cell changes, and the target cell belongs to DRNC, the SRNC measures this item in the original HSUPA serving cell. This item is used to indicate the change of HSUPA serving cells in the soft handover status instead of the hard handover status.
Issue 01 (2013-05-04)
1327
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.SHO.ServCellC hg.AttOutIur Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.15 Number of Successful inter-RNC HSUPA Serving Cell Changes in Soft Handover Status for Cell
Issue 01 (2013-05-04)
1328
Counters
Counter ID 67195486 Counter Name VS.HSUPA.SHO.ServCellC hg.SuccOutIur Counter Description Number of Successful interRNC HSUPA Serving Cell Changes in Soft Handover Status for Cell
Description
This measurement counter takes statistics of the number of successful HSUPA serving cell changes in soft handover status for cell. It is measured in a serving cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement counter takes statistics of the number of successful HSUPA serving cell changes in soft handover status. It is mearued in a serving cell. This procedure can be triggered with the following messages:[1]PHYSICAL CHANNEL RECONFIGURATION,[2] TRANSPORT CHANNEL RECONFIGURATION,[3]RADIO BEARER RECONFIGURATION message. Accordingly, UE may send [1]PHYSICAL CHANNEL RECONFIGURATION COMPLETE,[2]PHYSICAL CHANNEL RECONFIGURATION FAILURE,[3]TRANSPORT CHANNEL RECONFIGURATION COMPLETE,[4] TRANSPORT CHANNEL RECONFIGURATION FAILURE,[5]RADIO BEARER RECONFIGURATION COMPLETE,[6]RADIO BEARER RECONFIGURATION FAILURE message to RNC as a response. This measurement is triggered at point B as shown in Figure, the procedure shown in the figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an example. When the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the RNC measures this item in the original HSUPA serving cell if the HSUPA serving cell is changed. The item is used to indicate the change of HSUPA serving cells in the soft handover status instead of the hard handover status.
Issue 01 (2013-05-04)
1329
This measurement is triggered at point C as shown in Figure , when the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE. If the HSUPA serving cell changes during the soft handover, the RNC measures this item in the original HSUPA serving cell. Figure 1-584 Soft handover procedure (successful operation)
Issue 01 (2013-05-04)
1330
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.SHO.ServCellC hg.SuccOutIur Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.16 Number of Successful HSUPA Serving Cell Changes Due to inter-RNC Hard Handover without Channel Change for Cell Counters
Counter ID 67195487 Counter Name VS.HSUPA.HHO.E2E.SuccOutIur Counter Description Number of Successful HSUPA Serving Cell Changes Due to inter-RNC Hard Handover without Channel Change for Cell
Description
This measurement item provides the number of successful HSUPA serving cell changes due to inter-RNC hard handover for cell. It is measured in the original serving cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.The hard handover procedure can be triggered with the following messages:[1]PHYSICAL CHANNEL RECONFIGURATION,[2]TRANSPORT CHANNEL RECONFIGURATION,[3]RADIO BEARER RECONFIGURATION,[4]RADIO BEARER SETUP,[5]RADIO BEARER RELEASE message. Accordingly, UE may send [1]PHYSICAL CHANNEL RECONFIGURATION COMPLETE,[2]PHYSICAL CHANNEL RECONFIGURATION FAILURE,[3]TRANSPORT CHANNEL RECONFIGURATION COMPLETE,[4] TRANSPORT CHANNEL RECONFIGURATION FAILURE,[5]RADIO BEARER RECONFIGURATION COMPLETE,[6]RADIO BEARER RECONFIGURATION FAILURE,[7]RADIO BEARER SETUP COMPLETE,[8]RADIO BEARER SETUP FAILURE,[9]RADIO BEARER RELEASE COMPLETE,[10]RADIO BEARER RELEASE FAILURE message to RNC as a response.
Measurement point
This measurement is triggered at point B as shown in Figure. The procedure shown in the figure takes a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message as an example.
When the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the RNC measures the item in the HSUPA serving cell before the hard handover on condition that the hard handover is performed over the Iur interface from EDCH to EDCH. Figure 1-585 HSUPA Serving cell change procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.HHO.E2E.SuccOutIur Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.17 Number of HSUPA Serving Cell Change Attempts Due to inter-RNC Hard Handover without Channel Change for Cell
Issue 01 (2013-05-04)
1332
Counters
Counter ID 67195488 Counter Name VS.HSUPA.HHO.E2E.AttOutIur Counter Description Number of HSUPA Serving Cell Change Attempts Due to inter-RNC Hard Handover without Channel Change for Cell
Description
This measurement counter takes statistics of the number of HSUPA serving cell change attempts due to inter-RNC hard handover.It is measured in a serving cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.The hard handover procedure can be triggered with the following messages:[1]PHYSICAL CHANNEL RECONFIGURATION, [2]TRANSPORT CHANNEL RECONFIGURATION,[3]RADIO BEARER RECONFIGURATION,[4]RADIO BEARER SETUP,[5]RADIO BEARER RELEASE message. Accordingly, UE may send [1]PHYSICAL CHANNEL RECONFIGURATION COMPLETE,[2]PHYSICAL CHANNEL RECONFIGURATION FAILURE,[3]TRANSPORT CHANNEL RECONFIGURATION COMPLETE,[4]TRANSPORT CHANNEL RECONFIGURATION FAILURE,[5]RADIO BEARER RECONFIGURATION COMPLETE,[6]RADIO BEARER RECONFIGURATION FAILURE,[7]RADIO BEARER SETUP COMPLETE,[8]RADIO BEARER SETUP FAILURE,[9]RADIO BEARER RELEASE COMPLETE,[10]RADIO BEARER RELEASE FAILURE message to RNC as a response.
Measurement point
This measurement is triggered at point A as shown in Figure. The procedure shown in the figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an example. When the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC measure the item in the serving cell before hard handover on condition that this hard handover is performed over the Iur interface from EDCH to EDCH.
Issue 01 (2013-05-04)
1333
Figure 1-586 HSUPA Serving cell change procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.HHO.E2E.AttOutIur Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.18 Number of Successful HSUPA Serving Cell Changes Due to IntraFrequency Hard Handover without Channel Change for Cell
Issue 01 (2013-05-04)
1334
Counters
Counter ID 67192371 Counter Name VS.HSUPA.HHO.E2E.SuccOutIntraFreq Counter Description Number of Successful HSUPA Serving Cell Changes Due to IntraFrequency Hard Handover without Channel Change for Cell Number of Successful HSUPA Serving Cell Changes Due to InterFrequency Hard Handover without Channel Change for Cell
67192373
VS.HSUPA.HHO.E2E.SuccOutInterFreq
Description
These counters provide the number of successful HSUPA serving cell changes due to E-DCHto-E-DCH intra-frequency and inter-frequency hard handover. For DC-HSUPA users, these counters are measured only in the cell with the primary carrier.
Measurement point
These measurements are triggered at point B shown in the figure. When receiving a message PHYSICAL CHANNEL RECONFIGURATION COMPLETE or TRANSPORT CHANNEL RECONFIGURATION COMPLETE or RADIO BEARER RECONFIGURATION COMPLETE or RADIO BEARER SETUP COMPLETE or RADIO BEARER RELEASE COMPLETE message from the UE, the RNC measures VS.HSUPA.HHO.E2E.SuccOutIntraFreq in the HSUPA serving cell before the hard handover if an E-DCH-to-E-DCH intra-frequency hard handover is performed, or measures VS.HSUPA.HHO.E2E.SuccOutInterFreq in the HSUPA serving cell before the hard handover if an E-DCH-to-E-DCH inter-frequency hard handover is performed.
Issue 01 (2013-05-04)
1335
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.HHO.E2E.SuccOutIntraFreq VS.HSUPA.HHO.E2E.SuccOutInterFreq Feature ID WRFD-01061204 WRFD-01061204 Feature Name HSUPA Mobility Management HSUPA Mobility Management
1.12.13.19 Number of HSUPA Serving Cell Change Attempts Due to IntraFrequency Hard Handover without Channel Change for Cell
Issue 01 (2013-05-04)
1336
Counters
Counter ID 67192372 Counter Name VS.HSUPA.HHO.E2E.AttOutIntraFreq Counter Description Number of HSUPA Serving Cell Change Attempts Due to Intra-Frequency Hard Handover without Channel Change for Cell
Description
These counters provide the number of HSUPA serving cell change attempts due to E-DCH-toE-DCH intra-frequency and inter-frequency hard handover. For DC-HSUPA users, these counters are measured only in the cell with the primary carrier.
Measurement point
These measurements are triggered at point A shown in the figure. When sending the UE a message PHYSICAL CHANNEL RECONFIGRATION, TRANSPORT CHANNEL RECONFIGURATION, RADIO BEARER RECONFIGURATION, RADIO BEARER SETUP message, or RADIO BEARER RELEASE, the RNC measures VS.HSUPA.HHO.E2E.AttOutIntraFreq in the HSUPA serving cell before the hard handover if an E-DCH-to-EDCH intra-frequency hard handover is performed, or measures VS.HSUPA.HHO.E2E.AttOutInterFreq in the HSUPA serving cell before the hard handover if an E-DCH-to-E-DCH inter-frequency hard handover is performed. Figure 1-588 HSUPA Serving cell change procedure (successful operation)
Issue 01 (2013-05-04)
1337
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.HHO.E2E.AttOutIntraFreq Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.20 Number of HSUPA Serving Cell Change Attempts Due to InterFrequency Hard Handover without Channel Change for Cell Counters
Counter ID 67192374 Counter Name VS.HSUPA.HHO.E2E.AttOutInterFreq Counter Description Number of HSUPA Serving Cell Change Attempts Due to Inter-Frequency Hard Handover without Channel Change for Cell
Description
This measurement item takes statistics of the number of HSUPA serving cell change attempts due to inter-frequency hard handover without channel change for cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point A shown in the figure. When the RNC sends a PHYSICAL CHANNEL RECONFIGRATION message or a TRANSPORT CHANNEL RECONFIGRATION message or a RADIO BEARER RECONFIGRATION message or a RADIO BEARER SETUP message or a RADIO BEARER RELEASE message to the UE, the RNC measures the item in the HSUPA serving cell before the hard handover if an EDCH-toEDCH inter-frequency hard handover is performed.
Issue 01 (2013-05-04)
1338
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.HHO.E2E.AttOutInterFreq Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.21 Number of Successful HSUPA Intra-Frequency Hard Handovers for Cell (EDCH to DCH)
Issue 01 (2013-05-04)
1339
Counters
Counter ID 67192472 Counter Name VS.HSUPA.HHO.E2D.SuccOutIntraFreq Counter Description Number of Successful HSUPA Intra-Frequency Hard Handovers for Cell (EDCH to DCH) Number of Successful HSUPA Inter-Frequency Hard Handovers for Cell (EDCH to DCH)
67192474
VS.HSUPA.HHO.E2D.SuccOutInterFreq
Description
These counters provide the number of successful HSUPA intra-frequency/inter-frequency hard handovers from EDCH to DCH in a cell. For DC-HSUPA users, these counters are measured only in the cell with the primary carrier.
Measurement point
These measurements are triggered at point B shown in the figure. When receiving a RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the RNC measures VS.HSUPA.HHO.E2D.SuccOutIntraFreq in the HSUPA serving cell before the hard handover if an EDCH-to-DCH intra-frequency hard handover is performed or measures VS.HSUPA.HHO.E2D.SuccOutInterFreq in the HSUPA serving cell before the hard handover if an EDCH-to-DCH inter-frequency hard handover is performed. Figure 1-590 Dynamic channel configuration procedure (RB reconfiguration)
Issue 01 (2013-05-04)
1340
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.HHO.E2D.SuccOutIntraFreq VS.HSUPA.HHO.E2D.SuccOutInterFreq Feature ID WRFD-01061204 WRFD-01061204 Feature Name HSUPA Mobility Management HSUPA Mobility Management
1.12.13.22 Number of HSUPA Intra-Frequency Hard Handover Attempts for Cell (EDCH to DCH) Counters
Counter ID 67192473 Counter Name VS.HSUPA.HHO.E2D.AttOutIntraFreq Counter Description Number of HSUPA IntraFrequency Hard Handover Attempts for Cell(EDCH to DCH)
Description
These counters provide the number of attempts to switch the channel type from E-DCH to DCH due to intra-frequency/inter-frequency hard handover in a cell. For DC-HSUPA users, these counters are measured only in the cell with the primary carrier.
Measurement point
These measurements are triggered at point A shown in the figure. When sending the UE a message RADIO BEARER RECONFIGURATION, the RNC measures VS.HSUPA.HHO.E2D.AttOutIntraFreq in the HSUPA serving cell before the hard handover if an EDCH-to-DCH intra-frequency hard handover is performed, or measures VS.HSUPA.HHO.E2D.AttOutInterFreq in the HSUPA serving cell before the hard handover if an EDCH-to-DCH inter-frequency hard handover is performed.
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.HHO.E2D.AttOutIntraFreq Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.23 Number of HSUPA Inter-Frequency Hard Handover Attempts for Cell (EDCH to DCH)
Issue 01 (2013-05-04)
1342
Counters
Counter ID 67192475 Counter Name VS.HSUPA.HHO.E2D.AttOutInterFreq Counter Description Number of HSUPA InterFrequency Hard Handover Attempts for Cell(EDCH to DCH)
Description
This measurement item takes statistics of the number of HSUPA Inter-Frequency Hard Handover Attempts from EDCH to DCH in a cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point A shown in the figure. When the RNC sends a RADIO BEARER RECONFIGURATION message to the UE, the RNC measures this item in the HSUPA serving cell before the hard handover if an EDCH-to-DCH inter-frequency hard handover is performed. Figure 1-592 Dynamic channel configuration procedure (RB reconfiguration)
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.HHO.E2D.AttOutInterFreq Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.24 Number of Channel Conversion Attempts According to Different Channel Switch Type for Cell Counters
Counter ID 67192480 Counter Name VS.HSUPA.E2F.Att Counter Description Number of Channel Conversion Attempts from EDCH to FACH for HSUPA Service for Cell Number of Channel Conversion Attempts from EDCH to DCH for HSUPA Service for Cell Number of Channel Conversion Attempts from DCH to EDCH for HSUPA Service for Cell Number of Channel Conversion Attempts from FACH to EDCH for HSUPA Service for Cell
67192471
VS.HSUPA.E2D.Att
67192477
VS.HSUPA.D2E.Att
67192482
VS.HSUPA.F2E.Att
Description
These counters provide the number of channel conversion attempts according to different channel switch type in the same cell of the RNC for HSUPA service. For DC-HSUPA users, these counters are measured only in the cell with the primary carrier.
Measurement point
This measurement is performed at point A shown in the figure. The RNC sends a RADIO BEAR RECONFIGURE message to the UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the same cell after reconfigurations, the RNC measures the items in the HSUPA serving cell by the channel switch type.
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.E2F.Att VS.HSUPA.E2D.Att VS.HSUPA.D2E.Att VS.HSUPA.F2E.Att Feature ID WRFD-01061208 WRFD-01061208 WRFD-01061208 WRFD-01061208 Feature Name HSUPA DCCC HSUPA DCCC HSUPA DCCC HSUPA DCCC
1.12.13.25 Number of Successful Handovers Between Different Channel Types for Cell
Issue 01 (2013-05-04)
1345
Counters
Counter ID 67192481 Counter Name VS.HSUPA.E2F.Succ Counter Description Number of Successful Channel Conversions from EDCH to FACH for HSUPA Service for Cell Number of Successful Channel Conversions from EDCH to DCH for HSUPA Service for Cell Number of Successful Channel Conversions from DCH to EDCH for HSUPA Service for Cell Number of Successful Channel Conversions from FACH to EDCH for HSUPA Service for Cell
67192470
VS.HSUPA.E2D.Succ
67192476
VS.HSUPA.D2E.Succ
67192483
VS.HSUPA.F2E.Succ
Description
These counters provide the number of times that the handover between different channels succeeds in the cell. For DC-HSUPA users, these counters are measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point B shown in the figure. The RNC receives a RB RECFG CMP message from the UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the same cell after reconfigurations, the RNC measures the items in the HSUPA serving cell by the channel switch type.
Issue 01 (2013-05-04)
1346
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.E2F.Succ VS.HSUPA.E2D.Succ VS.HSUPA.D2E.Succ VS.HSUPA.F2E.Succ Feature ID WRFD-01061208 WRFD-01061208 WRFD-01061208 WRFD-01061208 Feature Name HSUPA DCCC HSUPA DCCC HSUPA DCCC HSUPA DCCC
1.12.13.26 Mean Uplink Throughput of single HSUPA MAC-d Flow
Issue 01 (2013-05-04)
1347
Counters
Counter ID 67203932 Counter Name VS.HSUPA.MeanChThroughput Counter Description Mean Uplink Throughput of single HSUPA MAC-d Flow for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67192487 Counter Name VS.HSUPA.MeanChThroug hput.Times Counter Description Duration of HSUPA MAC-D Flow Receiving Data for Cell
Description
This counter provides the mean uplink throughput of single HSUPA MAC-d flows in HSUPA cells in active set.For DC-HSUPA users, this counter is measured only in the primary cell based on the total throughput on the primary and secondary carriers.
Measurement point
When data is received in HSUPA active cells, the RNC measures the total data transfer time of all the UEs and the total number of bits received in the cell. At the end of the measurement period, the RNC divides the total number of bits by the total data transfer time to obtain the mean uplink throughput of MAC-d flows at the RLC layer. Note that the total number of bits measured excludes RLC headers and retransmitted data. In the case of a soft handover, the RNC measures the number of bits received after combining in all cells of the active set.
Formula
VS.HSUPA.MeanChThroughput = {8}*[VS.HSUPA.MeanChThroughput.TotalBytes]/ [VS.HSUPA.MeanChThroughput.Times]
Unit
kbit/s
Related Features
Counter Name VS.HSUPA.MeanChThroughput Feature ID WRFD-010612 Feature Name HSUPA Introduction Package
Issue 01 (2013-05-04)
1348
1.12.13.27 Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow Counters
Counter ID 67192486 Counter Name VS.HSUPA.MeanChThroug hput.TotalBytes Counter Description Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow for Cell
Description
This counter provides the number of total bytes received in uplink of all the HSUPA MAC-d flows in a cell.For DC-HSUPA users, this counter is measured only in the primary cell based on the total number of bytes received on the primary and secondary carriers.
Measurement point
When data is received in HSUPA active cells, the RNC measures the number of total bytes received in the uplink (including data of different services) at the RLC layer for the MAC-d flow in the cell. The RLC header and the retransmitted data are excluded.In the case of a soft handover, the RNC measures the number of bits received after combining in all cells of the active set.
Formula
None
Unit
byte
Related Features
Counter Name VS.HSUPA.MeanChThroug hput.TotalBytes Feature ID WRFD-010612 Feature Name HSUPA Introduction Package
1.12.13.28 Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Golden Subscriber
Issue 01 (2013-05-04)
1349
Counters
Counter ID 67204513 Counter Name VS.HSUPA.GoldenBeMeanChThroughput Counter Description Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Golden Subscriber for Cell Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Silver Subscriber for Cell Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Copper Subscriber for Cell
67204514
VS.HSUPA.SilverBeMeanChThroughput
67204515
VS.HSUPA.CopperBeMeanChThroughput
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67194890 Counter Name VS.HSUPA.CopperBeMean ChThroughput.Times VS.HSUPA.GoldenBeMean ChThroughput.Times VS.HSUPA.SilverBeMeanC hThroughput.Times Counter Description Duration of Copper BE HSUPA MAC-D Flow Receiving Data for Cell Duration of Golden BE HSUPA MAC-D Flow Receiving Data for Cell Duration of Silver BE HSUPA MAC-D Flow Receiving Data for Cell
67194874
67194876
Description
These counters provide the average UL throughput of all the HSUPA MAC-d flows of differentpriority BE services in an HSUPA serving cell. For DC-HSUPA users, these counters are measured only in the primary cell based on the total number of bytes received on the primary and secondary carriers.
Measurement point
When BE services for golden, silver, and copper users are carried in an HSUPA serving cell, the RNC measures the number of total bytes received in the uplink of the MAC-d flow of the BE service at the RLC layer and the time for data transmission for different users. At the end of the measurement period, the average throughput of users of a priority, (for example, golden users) is obtained by dividing the number of total bytes for the golden users by the total transmission time for the golden users. RLC headers and retransmitted data are not considered.
Formula
VS.HSUPA.GoldenBeMeanChThroughput = {8}* [VS.HSUPA.GoldenBeMeanChThroughput.TotalBytes]/ [VS.HSUPA.GoldenBeMeanChThroughput.Times] VS.HSUPA.SilverBeMeanChThroughput = {8}* [VS.HSUPA.SilverBeMeanChThroughput.TotalBytes]/ [VS.HSUPA.SilverBeMeanChThroughput.Times] VS.HSUPA.CopperBeMeanChThroughput = {8}* [VS.HSUPA.CopperBeMeanChThroughput.TotalBytes]/ [VS.HSUPA.CopperBeMeanChThroughput.Times]
Unit
kbit/s
Related Features
Counter Name VS.HSUPA.GoldenBeMeanChThroughput Feature ID WRFD-01061008 WRFD-020806 Feature Name Interactive and Background Traffic Class on HSDPA Differentiated Service Based on SPI Weight VS.HSUPA.SilverBeMeanChThroughput WRFD-01061008 WRFD-020806 Interactive and Background Traffic Class on HSDPA Differentiated Service Based on SPI Weight VS.HSUPA.CopperBeMeanChThroughput WRFD-01061008 WRFD-020806 Interactive and Background Traffic Class on HSDPA Differentiated Service Based on SPI Weight
1.12.13.29 Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service for Golden Subscriber Counters
Counter ID 67194873 Counter Name VS.HSUPA.GoldenBeMean ChThroughput.TotalBytes Counter Description Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service for Golden Subscriber for Cell
1351
Issue 01 (2013-05-04)
Counter ID 67194875
Counter Name VS.HSUPA.SilverBeMeanC hThroughput.TotalBytes
Counter Description Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service for Silver Subscriber for Cell Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service for Copper Subscriber for Cell
67194889
VS.HSUPA.CopperBeMean ChThroughput.TotalBytes
Description
These counters provide the number of total bytes received in the uplink of all the HSUPA MACd flows of different-priority BE services in an HSUPA serving cell. For DC-HSUPA users, these counters are measured only in the primary cell based on the total number of bytes received on the primary and secondary carriers.
Measurement point
When BE services for golden, silver, and copper users are carried in an HSUPA serving cell, the RNC separately measures the number of total bytes received in the uplink of the MAC-d flow of different-priority BE service at the RLC layer. RLC headers and retransmitted data are not considered.
Formula
None
Unit
byte
Related Features
Counter Name VS.HSUPA.GoldenBeMean ChThroughput.TotalBytes Feature ID WRFD-01061008 WRFD-020806 Feature Name Interactive and Background Traffic Class on HSDPA Differentiated Service Based on SPI Weight VS.HSUPA.SilverBeMeanC hThroughput.TotalBytes WRFD-01061008 WRFD-020806 Interactive and Background Traffic Class on HSDPA Differentiated Service Based on SPI Weight
Counter Name VS.HSUPA.CopperBeMean ChThroughput.TotalBytes
Feature Name Interactive and Background Traffic Class on HSDPA Differentiated Service Based on SPI Weight
1.12.13.30 Number of inter-RNC HSUPA Hard Handover Attempts for Cell(EDCH to DCH) Counters
Counter ID 73403766 Counter Name VS.HSUPA.HHO.E2D.AttOutIur Counter Description Number of inter-RNC HSUPA Hard Handover Attempts for Cell(EDCH to DCH)
Description
This measurement item takes statistics of the number of requests for inter RNC hard handovers from the EDCH to the DCH in a cell. For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.The hard handover procedure can be triggered with the following messages:[1]RADIO BEARER RECONFIGURATION,[2]RADIO BEARER SETUP,[3] RADIO BEARER RELEASE message. Accordingly, UE may send [1]RADIO BEARER RECONFIGURATION COMPLETE,[2]RADIO BEARER RECONFIGURATION FAILURE,[3]RADIO BEARER SETUP COMPLETE,[4]RADIO BEARER SETUP FAILURE,[5]RADIO BEARER RELEASE COMPLETE,[6]RADIO BEARER RELEASE FAILURE message to RNC as a response.
Measurement point
The measurement is triggered at point A as shown in the figure, the procedure shown in the figure takes a RADIO BEARER RECONFIGURATION message as an example, when sending a RADIO BEARER RECONFIGURATION message to a UE, the RNC measures this item in the serving cell before hard handover if an inter RNC hard handover from the EDCH to the DCH is performed.
Issue 01 (2013-05-04)
1353
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.HHO.E2D.AttOutIur Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.31 Number of Successful inter-RNC HSUPA Hard Handovers for Cell (EDCH to DCH)
Issue 01 (2013-05-04)
1354
Counters
Counter ID 73403767 Counter Name VS.HSUPA.HHO.E2D.SuccOutIur Counter Description Number of Successful interRNC HSUPA Hard Handovers for Cell(EDCH to DCH)
Description
This measurement counter takes statistics of the number of inter RNC HSUPA Service HHO Success with E-DCH to DCH in a cell. For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.The hard handover procedure can be triggered with the following messages:[1]RADIO BEARER RECONFIGURATION,[2]RADIO BEARER SETUP,[3] RADIO BEARER RELEASE message. Accordingly, UE may send [1]RADIO BEARER RECONFIGURATION COMPLETE,[2]RADIO BEARER RECONFIGURATION FAILURE,[3]RADIO BEARER SETUP COMPLETE,[4]RADIO BEARER SETUP FAILURE,[5]RADIO BEARER RELEASE COMPLETE,[6]RADIO BEARER RELEASE FAILURE message to RNC as a response.
Measurement point
The measurement is triggered at point B as shown in the figure, the procedure shown in the figure takes a RADIO BEARER RECONFIGURATION message as an example, when receiving from a UE a RADIO BEARER RECONFIGURATION COMPLETE message, the RNC measures this item in the serving cell before hard handover if an inter RNC hard handover from the EDCH to the DCH is performed Figure 1-596 Dynamic channel configuration procedure (RB reconfiguration)
Issue 01 (2013-05-04)
1355
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.HHO.E2D.SuccOutIur Feature ID WRFD-01061204 Feature Name HSUPA Mobility Management
1.12.13.32 Number of Successful HSUPA 16QAM RAB Establishments for cell Counters
Counter ID 73403795 Counter Name VS.HSUPA.RAB. 16QAM.SuccEstab Counter Description Number of Successful HSUPA 16QAM RAB Establishments for cell
Description
This measurement item takes statistics of the number of successful HSUPA 16QAM RAB establishments for cell. For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point B as shown in the figure, when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the assignment is for establishing the HSUPA RABs, the RNC measures this item in the serving cell where the HSUPA RABs are set up using 16QAM.
Issue 01 (2013-05-04)
1356
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB. 16QAM.SuccEstab Feature ID WRFD-010694 Feature Name UL 16QAM
1.12.13.33 Number of HSUPA 16QAM RABs Abnormal Released for cell Counters
Counter ID 73403796 Counter Name VS.HSUPA.RAB.AbnormRel.16QAM Counter Description Number of HSUPA 16QAM RABs Abnormal Released Including RF Cause for cell
Issue 01 (2013-05-04)
1357
Description
This measurement item takes statistics of the number of HSUPA 16QAM RABs Abnormal Released including RF causes for cell. For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization" , reference to 3GPP TS 25.413),the RNC measures the items in the HSUPA serving cell if is a HSUPA service using 16QAM. Figure 1-598 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization" , reference to 3GPP TS 25.413),the RNC measures the items in the HSUPA serving cell if is a HSUPA service using 16QAM.
Issue 01 (2013-05-04)
1358
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization" , reference to 3GPP TS 25.413),the RNC measures the items in the HSUPA serving cell if is a HSUPA service using 16QAM.
Issue 01 (2013-05-04)
1359
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.AbnormRel.16QAM Feature ID WRFD-010694 Feature Name UL 16QAM
1.12.13.34 Number of HSUPA 16QAM RABs Normal Released for cell Counters
Counter ID 73403797 Counter Name VS.HSUPA.RAB.NormRel. 16QAM Counter Description Number of HSUPA 16QAM RABs Normal Released for cell
Issue 01 (2013-05-04)
1360
Description
This measurement item takes statistics of the number of HSUPA 16QAM Release due to normal cause for cell. For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization" , or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release", the RNC measures the item in the HSUPA serving cell if it is a HSUPA service using 16QAM. Figure 1-601 Iu release procedure
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization" , or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release" ,the RNC measures the item in the HSUPA serving cell if it is a HSUPA service using 16QAM.
Issue 01 (2013-05-04)
1361
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.NormRel. 16QAM Feature ID WRFD-010694 Feature Name UL 16QAM
1.12.13.35 Number of HSUPA 16QAM RAB Setup Attempts for cell Counters
Counter ID 73403794 Counter Name VS.HSUPA.RAB. 16QAM.AttEstab Counter Description Number of HSUPA 16QAM RAB Setup Attempts for cell
Issue 01 (2013-05-04)
1362
Description
This measurement item takes statistics of the number of HSUPA 16QAM RAB Setup Attempts for cell. For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN, and if the the RNC decides the HSUPA RABs, it measures this item in the HSUPA serving cell using 16QAM. Figure 1-603 RAB setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB. 16QAM.AttEstab Feature ID WRFD-010694 Feature Name UL 16QAM
Issue 01 (2013-05-04)
1363
1.12.13.36 Number of HSUPA RABs Abnormal Released due to RF Failures for Cell Counters
Counter ID 73391136 Counter Name VS.HSUPA.RAB.AbnormR el.RF Counter Description Number of HSUPA RABs Abnormal Released due to RF Failures for Cell
Description
This measurement item takes statistics of the number of abnormally released HSUPA services due to RF cause in a cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier. The cause value for RF exceptions on the Iu interface is "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure".
Measurement point
The measurement is triggered at point A as shown in the following figure. When an RF exception occurs (including SRB reset, TRB reset, radio link synchronization failures, or air interface process failures), the RNC sends the CN a RAB RELEASE REQUEST message with the cause value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure." If the RNC receives from the CN a RAB ASSIGNMENT REQUEST message with a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", this counter is measured in the HSUPA serving cell if HSUPA services are enabled. For details about the preceding cause values, see 3GPP TS 25.413. Figure 1-604 RAB release procedure
Issue 01 (2013-05-04)
1364
The measurement is triggered at point A as shown in the following figure. When an RF exception occurs (including SRB reset, TRB reset, radio link synchronization failures, or air interface process failures), the RNC sends the CN a RAB RELEASE REQUEST message with the cause value of "Radio Connection With UE Lost", or "Failure in the Radio Interface Procedure." If the RNC receives from the CN an IU RELEASE COMMAND message with a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", this counter is measured in the HSUPA serving cell if HSUPA services are enabled. For details about the preceding cause values, see 3GPP TS 25.413. Figure 1-605 RAB release IU REL procedure
The measurement is triggered at point A as shown in the following figure. When an RF exception occurs (including SRB reset, TRB reset, radio link synchronization failures, or air interface process failures), the RNC sends the CN an IU RELEASE REQUEST message with the cause value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure." If the RNC receives from the CN a RAB ASSIGNMENT REQUEST message with a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", this counter is measured in the HSUPA serving cell if HSUPA services are enabled. For details about the preceding cause values, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
1365
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.AbnormR el.RF Feature ID WRFD-01061206 WRFD-010632 Feature Name Interactive and Background Traffic Class on HSUPA Streaming Traffic Class on HSUPA
1.12.13.37 Number of HSUPA UEs with Various Categories in a Cell Counters

Counter ID 67204266 Counter Name VS.HSUPA.UE.Mean.CAT 1.4 Counter Description Average Number of HSUPA UEs with Category 1-4 in a Cell
1366
Issue 01 (2013-05-04)
Counter ID 67204267 67204268 67204269 67193599
Counter Name VS.HSUPA.UE.Mean.CAT 5 VS.HSUPA.UE.Mean.CAT 6 VS.HSUPA.UE.Mean.CAT 7 VS.HSUPA.UE.Max.CAT1. 4 VS.HSUPA.UE.Max.CAT5
Counter Description Average Number of HSUPA UEs with Category 5 in a Cell Average Number of HSUPA UEs with Category 6 in a Cell Average Number of HSUPA UEs with Category 7 in a Cell Maximum Number of HSUPA UEs with Category1-4 in a Cell Maximum Number of HSUPA UEs with Category 5 in a Cell Maximum Number of HSUPA UEs with Category 6 in a Cell Maximum Number of HSUPA UEs with Category 7 in a Cell Average Number of HSUPA UEs with Category 8 in a Cell Maximum Number of HSUPA UEs with Category 8 in a Cell Average Number of HSUPA UEs with Category 9 in a Cell Maximum Number of HSUPA UEs with Category 9 in a Cell
67193602
67193605
VS.HSUPA.UE.Max.CAT6
67193608
VS.HSUPA.UE.Max.CAT7
73441235 73424186
VS.HSUPA.UE.Mean.CAT 8 VS.HSUPA.UE.Max.CAT8
73441236 73424189
VS.HSUPA.UE.Mean.CAT 9 VS.HSUPA.UE.Max.CAT9
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73394367 Counter Name VS.HSUPA.UE.Mean.CAT 1.4.DENO VS.HSUPA.UE.Mean.CAT 1.4.NUM Counter Description Average Number of HSUPA UEs with Category 1-4 in a Cell(Denominator) Average Number of HSUPA UEs with Category 1-4 in a Cell(Numerator)
73394366
Issue 01 (2013-05-04)
1367
Counter ID 73394369
Counter Name VS.HSUPA.UE.Mean.CAT 5.DENO VS.HSUPA.UE.Mean.CAT 5.NUM VS.HSUPA.UE.Mean.CAT 6.DENO VS.HSUPA.UE.Mean.CAT 6.NUM VS.HSUPA.UE.Mean.CAT 7.DENO VS.HSUPA.UE.Mean.CAT 7.NUM VS.HSUPA.UE.Mean.CAT 8.DENO VS.HSUPA.UE.Mean.CAT 8.NUM VS.HSUPA.UE.Mean.CAT 9.DENO VS.HSUPA.UE.Mean.CAT 9.NUM
Counter Description Average Number of HSUPA UEs with Category 5 in a Cell (Denominator) Average Number of HSUPA UEs with Category 5 in a Cell (Numerator) Average Number of HSUPA UEs with Category 6 in a Cell (Denominator) Average Number of HSUPA UEs with Category 6 in a Cell (Numerator) Average Number of HSUPA UEs with Category 7 in a Cell (Denominator) Average Number of HSUPA UEs with Category 7 in a Cell (Numerator) Average Number of HSUPA UEs with Category 8 in a Cell (Denominator) Average Number of HSUPA UEs with Category 8 in a Cell (Numerator) Average Number of HSUPA UEs with Category 9 in a Cell (Denominator) Average Number of HSUPA UEs with Category 9 in a Cell (Numerator)
73394368
73394371
73394370
73394373
73394372
73424188
73424187
73424191
73424190
Description
These counters provide the average and maximum number of HSUPA UEs with various categories in a serving cell.The RNC calculates the mean and maximum numbers of HSUPA users of category 8 or 9 only for the cell with the primary carrier.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of the number of HSUPA UEs with various categories. At the end of the measurement period, by dividing the accumulated value of sample data in the period by the number of samples, the average number of HSUPA UEs with various categories in the measurement period is obtained; by selecting the
maximum value of sample data in the period, the maximum number of HSUPA UEs with various categories in the measurement period is obtained.
Formula
VS.HSUPA.UE.Mean.CAT1.4 = [VS.HSUPA.UE.Mean.CAT1.4.NUM]/ [VS.HSUPA.UE.Mean.CAT1.4.DENO] VS.HSUPA.UE.Mean.CAT5 = [VS.HSUPA.UE.Mean.CAT5.NUM]/ [VS.HSUPA.UE.Mean.CAT5.DENO] VS.HSUPA.UE.Mean.CAT6 = [VS.HSUPA.UE.Mean.CAT6.NUM]/ [VS.HSUPA.UE.Mean.CAT6.DENO] VS.HSUPA.UE.Mean.CAT7 = [VS.HSUPA.UE.Mean.CAT7.NUM]/ [VS.HSUPA.UE.Mean.CAT7.DENO] VS.HSUPA.UE.Mean.CAT8 = [VS.HSUPA.UE.Mean.CAT8.NUM]/ [VS.HSUPA.UE.Mean.CAT8.DENO] VS.HSUPA.UE.Mean.CAT9 = [VS.HSUPA.UE.Mean.CAT9.NUM]/ [VS.HSUPA.UE.Mean.CAT9.DENO]
Unit
None
Related Features
Counter Name VS.HSUPA.UE.Mean.CAT 1.4 VS.HSUPA.UE.Mean.CAT 5 VS.HSUPA.UE.Mean.CAT 6 VS.HSUPA.UE.Mean.CAT 7 VS.HSUPA.UE.Max.CAT1. 4 VS.HSUPA.UE.Max.CAT5 VS.HSUPA.UE.Max.CAT6 VS.HSUPA.UE.Max.CAT7 VS.HSUPA.UE.Mean.CAT 8
Issue 01 (2013-05-04)
Feature ID WRFD-01061201 WRFD-01061201 WRFD-01061201 WRFD-01061201 WRFD-01061201 WRFD-01061201 WRFD-01061201 WRFD-01061201 WRFD-01061201
Feature Name HSUPA UE Category Support HSUPA UE Category Support HSUPA UE Category Support HSUPA UE Category Support HSUPA UE Category Support HSUPA UE Category Support HSUPA UE Category Support HSUPA UE Category Support HSUPA UE Category Support
1369
Counter Name VS.HSUPA.UE.Max.CAT8 VS.HSUPA.UE.Mean.CAT 9 VS.HSUPA.UE.Max.CAT9
Feature Name HSUPA UE Category Support HSUPA UE Category Support HSUPA UE Category Support
1.12.13.38 Number of EDCH MAC-d Flow Setup Requests for Cell Counters
Counter ID 73393829 Counter Name VS.HSUPA.MACD.AttSetup Counter Description Number of EDCH MAC-d Flow Setup Requests for Cell
Description
This counter provides the number of EDCH MAC-d flow setup requests in the cell.For DCHSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement can be triggered at point A as shown in the figure. When the RNC sends the NodeB a RADIO LINK SETUP REQUEST message, this counter is measured in the HSUPA cell if the message contains the "E-DCH FDD Information" IE. Figure 1-607 Radio link setup procedure (successful operation)
Issue 01 (2013-05-04)
1370
The measurement can be triggered at point A as shown in the figure. When the RNC sends the NodeB a RADIO LINK RECONFIGURATION PREPARE message, this counter is measured in the HSUPA cell if the message contains the "E-DCH FDD Information" or "E-DCH MACd Flows To Add" IE. Figure 1-608 Synchronized RL reconfiguration commit procedure
The measurement can also be triggered at point A as shown in the figure. When the RNC sends the NodeB a RADIO LINK ADDITION REQUEST message, this counter is measured in the HSUPA cell where the new E-DCH RL is to be added if the message indicates that an E-DCH RL needs to be added.
Issue 01 (2013-05-04)
1371
Figure 1-609 Radio link add procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.MACD.AttSetup Feature ID WRFD-010612 Feature Name HSUPA Introduction Package
1.12.13.39 Number of Failed HSUPA Service Establishments Due to Insufficiency of Different Resources
Issue 01 (2013-05-04)
1372
Counters
Counter ID 73393832 Counter Name VS.HSUPA.RAB.FailEstab. ULPower.Cong Counter Description Number of Failed HSUPA Service Establishments Due to UL Power Insufficiency for Cell Number of Failed HSUPA Service Establishments Due to UL Iub Bandwidth Insufficiency for Cell Number of Failed HSUPA Service Establishments Due to UL CE Insufficiency for Cell
73393833
VS.HSUPA.RAB.FailEstab. ULIUBBand.Cong
73393834
VS.HSUPA.RAB.FailEstab. ULCE.Cong
Description
This counter provides the number of times that an HSUPA service fails to be established due to insufficiency of different resources in the HSUPA serving cell.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request, it requests related radio resources. This counter is measured in the HSUPA serving cell when the RAB is for a HSUPA service and the resource request fails. Figure 1-610 Failed RAB establishments due to resource insufficiency
Issue 01 (2013-05-04)
1373
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.FailEstab. ULPower.Cong Feature ID WRFD-01061206 WRFD-010632 Feature Name Interactive and Background Traffic Class on HSUPA Streaming Traffic Class on HSUPA VS.HSUPA.RAB.FailEstab. ULIUBBand.Cong WRFD-01061206 WRFD-010632 Interactive and Background Traffic Class on HSUPA Streaming Traffic Class on HSUPA VS.HSUPA.RAB.FailEstab. ULCE.Cong WRFD-01061206 WRFD-010632 Interactive and Background Traffic Class on HSUPA Streaming Traffic Class on HSUPA
1.12.13.40 Average uplink throughput of the Traffic PS Conversational beared on E-DCH for cell Counters
Counter ID 73410485 Counter Name VS.PS.Conv.Kbps.EDCH Counter Description Average uplink throughput of the Traffic PS Conversational beared on EDCH for cell
Issue 01 (2013-05-04)
1374
Counter ID 73393915
Counter Name VS.PS.Conv.Times.EDCH
Counter Description Duration of PS Conversational HSUPA MAC-D Flow Receiving Data for Cell
Description
This measurement item takes statistics of the average uplink throughput of the Traffic PS Conversational beared on E-DCH in the cell.
Measurement point
The RNC measures all UL traffic volume (the RLC headers and retransmitted data are not included) (unit: bit) and duration (unit: ms) of the PS conversational service beared on EDCH in the cell of the RLC layer. At the end of the measurement period, the RNC calculates average bit rate.
Formula
VS.PS.Conv.Kbps.EDCH = {8}*[VS.PS.Conv.Traffic.EDCH]/[VS.PS.Conv.Times.EDCH]
Unit
kbit/s
Related Features
Counter Name VS.PS.Conv.Kbps.EDCH Feature ID WRFD-010617 WRFD-010501 Feature Name VoIP over HSPA/HSPA+ Conversational QoS Class
1.12.13.41 Number of uplink bytes of Transport Blocks of Traffic PS Conversational beared on E-DCH for cell Counters
Counter ID 73393914 Counter Name VS.PS.Conv.Traffic.EDCH Counter Description Number of uplink bytes of Transport Blocks of Traffic PS Conversational beared on E-DCH for cell
Issue 01 (2013-05-04)
1375
Description
This measurement item takes statistics of the number of uplink bytes of Transport Blocks of traffic PS conversational beared on E-DCH in the cell.
Measurement point
The RNC measures the total UL volume of PS conversational service beared on EDCH in the cell of the RLC layer. Note that the RLC headers and retransmitted data are not included.
Formula
None
Unit
byte
Related Features
Counter Name VS.PS.Conv.Traffic.EDCH Feature ID WRFD-010617 WRFD-010501 Feature Name VoIP over HSPA/HSPA+ Conversational QoS Class
1.12.13.42 Counters Related to the Number of Transfers Between Small Retransmission and Large Retransmission for HSUPA 2ms TTI Users or HSUPA 10ms TTI Users Counters
Counter ID 73393956 Counter Name VS.HSUPA.RsnSmall2Larg e.TTI2ms Counter Description Number of Times that HSUPA 2ms TTI Users Transfer from Small Retransmission to Large Retransmission for Cell Number of Times that HSUPA 10ms TTI Users Transfer from Small Retransmission to Large Retransmission for Cell Number of Times that HSUPA 2ms TTI Users Transfer from Large Retransmission to Small Retransmission for Cell
1376
73393957
VS.HSUPA.RsnSmall2Larg e.TTI10ms
73393958
VS.HSUPA.RsnLarge2Smal l.TTI2ms
Issue 01 (2013-05-04)
Counter ID 73393959
Counter Name VS.HSUPA.RsnLarge2Smal l.TTI10ms
Counter Description Number of Times that HSUPA 10ms TTI Users Transfer from Large Retransmission to Small Retransmission for Cell
Description
These counters provide the number of times that HSUPA 2ms TTI Users or HSUPA 10ms TTI Users transfer between small retransmission and large retransmission in the serving cell. The RNC calculates the number of DC-HSUPA users for the cell with the primary carrier and that for the cell with the secondary carrier separately. HSUPA users allocated a 10-ms TTI do not support DC-HSUPA.
Measurement point
The measurement can be triggered at point A as shown in the figure. The NodeB informs the RNC of its retransmission state through the E-DCH UL DATA FRAME. After receiving the frame, the RNC L2 checks whether the retransmission state changes. If yes, the RNC L2 sends the inner message CMACD_EDCH_PDU_RETRANS_TAR_NUM_MODIFY to the RNC L3. The RNC L3 then measures the corresponding counter based on the TTI of the user. Figure 1-611 Adaptive retransmission procedure
The measurement can also be triggered at point B as shown in the figure. In the OLPC_MODIFY scenario, only small retransmission can be used. In this case, the corresponding counter is measured based on the TTI of the user when the user in large retransmission mode receives an OLPC_MODIFY message.
Figure 1-612 Retransmission of OLPC procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RsnSmall2Larg e.TTI2ms VS.HSUPA.RsnSmall2Larg e.TTI10ms VS.HSUPA.RsnLarge2Smal l.TTI2ms VS.HSUPA.RsnLarge2Smal l.TTI10ms Feature ID WRFD-010641 WRFD-010641 WRFD-010641 WRFD-010641 Feature Name HSUPA Adaptive Transmission HSUPA Adaptive Transmission HSUPA Adaptive Transmission HSUPA Adaptive Transmission
1.12.13.43 Number of TTI Switch Attempts During RB Reconfiguration for Cell

Counters
Counter ID 73393984 Counter Name VS.HSUPA.TTI2to10.Att Counter Description Number of TTI Switch Attempts During RB Reconfiguration for Cell (2ms to 10ms) Number of TTI Switch Attempts During RB Reconfiguration for Cell (10ms to 2ms)
73393986
VS.HSUPA.TTI10to2.Att
Description
This counter provides the number TTI switch attempts in the HSUPA serving cell. The measurement is triggered by the RADIO BEAR RECONFIGURATION message.For DCHSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends the UE a RADIO BEARER RECONFIGURATION message. In this case, this counter is measured in the best cell that the UE camps on. Figure 1-613 RB reconfiguration procedure (successful operation)
Issue 01 (2013-05-04)
1379
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.TTI2to10.Att Feature ID WRFD-010690 WRFD-01061404 Feature Name TTI Switch for BE Services Based on Coverage HSUPA 2ms/10ms TTI Handover VS.HSUPA.TTI10to2.Att WRFD-010690 WRFD-01061404 TTI Switch for BE Services Based on Coverage HSUPA 2ms/10ms TTI Handover
1.12.13.44 Number of Successful TTI Switches During RB Reconfiguration for Cell Counters
Counter ID 73393985 Counter Name VS.HSUPA.TTI2to10.Succ Counter Description Number of Successful TTI Switches During RB Reconfiguration for Cell (2ms to 10ms) Number of Successful TTI Switches During RB Reconfiguration for Cell (10ms to 2ms)
73393987
VS.HSUPA.TTI10to2.Succ
Description
This counter provides the number TTI switch attempts in the HSUPA serving cell. The measurement is triggered by the RADIO BEAR RECONFIGURATION COMPLETE message.For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message from the UE. In this case, this counter is measured in the best cell that the UE camps on.
Figure 1-614 RB reconfig procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.TTI2to10.Succ Feature ID WRFD-010690 WRFD-01061404 Feature Name TTI Switch for BE Services Based on Coverage HSUPA 2ms/10ms TTI Handover VS.HSUPA.TTI10to2.Succ WRFD-010690 WRFD-01061404 TTI Switch for BE Services Based on Coverage HSUPA 2ms/10ms TTI Handover
1.12.13.45 Number of HSUPA 16QAM UEs in a Cell

Counters
Counter ID 73410507 Counter Name VS.HSUPA. 16QAM.UE.Mean.Cell Counter Description Average Number of HSUPA 16QAM UEs in a Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73394088 Counter Name VS.HSUPA. 16QAM.UE.Mean.Cell.DENO VS.HSUPA. 16QAM.UE.Mean.Cell.NU M Counter Description Average Number of HSUPA 16QAM UEs in a Cell (Denominator) Average Number of HSUPA 16QAM UEs in a Cell (Numerator)
73394087
Description
This counter provides the average number of HSUPA 16QAM UEs in a serving cell.
Measurement point
The system periodically (the measurement period is 5 second) takes samples of the number of HSUPA 16QAM UEs. At the end of the measurement period, by dividing the accumulated value of sample data in the period by the number of samples, the average number of HSUPA 16QAM UEs in the measurement period is obtained. Intermediate counters: VS.HSUPA. 16QAM.UE.Mean.Cell.DENO: Sampling times in the measurement period (denominator) VS.HSUPA.16QAM.UE.Mean.Cell.NUM: Accumulated number of HSUPA 16QAM UEs at the sampling points in a cell in the measurement period (numerator)
Formula
VS.HSUPA.16QAM.UE.Mean.Cell = [VS.HSUPA.16QAM.UE.Mean.Cell.NUM]/ [VS.HSUPA.16QAM.UE.Mean.Cell.DENO]
Unit
None
Related Features
Counter Name VS.HSUPA. 16QAM.UE.Mean.Cell Feature ID WRFD-010694 Feature Name UL 16QAM
Issue 01 (2013-05-04)
1382
1.12.13.46 Number of HSUPA Boosting UEs in a Cell Counters

Counter ID 73441120 Counter Name VS.HSUPA.Boosting.UE.M ean.Cell Counter Description Number of UEs Supporting E-DPCCH Boosting for Cell
Description
This counter provides the average number of UEs in an active set of HSUPA E-DCH cells that support E-DPCCH boosting.
Measurement point
UEs supporting E-DPCCH boosting in an HSUPA cell are sampled (sampling periodicity is 5 seconds) at a certain interval. At the end of a measurement period, this counter measured at each sampling site is obtained by dividing the accumulated number of the UEs by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.Boosting.UE.M ean.Cell Feature ID WRFD-010697 Feature Name E-DPCCH Boosting
1.12.13.47 Number of UEs Supporting E-DPCCH Boosting and CPC for Cell Counters
Counter ID 73441121 Counter Name VS.HSUPA.BoostingCPC.U E.Mean.Cell Counter Description Number of UEs Supporting E-DPCCH Boosting and CPC for Cell
Issue 01 (2013-05-04)
1383
Description
This counter provides the average number of UEs in an active set of HSUPA E-DCH cells that support E-DPCCH boosting and Continuous Packet Connectivity (CPC).
Measurement point
UEs supporting E-DPCCH boosting and CPC in an HSUPA cell are sampled (sampling periodicity is 5 seconds) at a certain interval. At the end of a measurement period, this counter measured at each sampling site is obtained by dividing the accumulated number of the UEs by the number of samples
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.BoostingCPC.U E.Mean.Cell Feature ID WRFD-010697 Feature Name E-DPCCH Boosting
1.12.13.48 Number of RABs Abnormally Released for PS HSUPA Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell Counters
Counter ID 73422168 Counter Name VS.HSUPA.RAB.AbnormR el.E2P Counter Description Number of RABs Abnormally Released for PS HSUPA Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell
Description
This counter provides the number of RABs Abnormally Released for PS HSUPA Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH in the serving cell.For DCHSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
As shown in point A of the figure, when a failure occurs(Ex: SRB reset occurs after sent Radio Bear Reconfiguration Message to UE during the State Transition from CELL_DCH to CELL_PCH or URA_PCH), the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then this counter is measured in the serving cell that the UE camps on if the RAB is for a PS service. Figure 1-615 RAB release procedure
As shown in point A of the figure, when a failure occurs(Ex: SRB reset occurs after sent Radio Bear Reconfiguration Message to UE during the State Transition from CELL_DCH to CELL_PCH or URA_PCH), the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then this counter is measured in the serving cell that the UE camps on if the RAB is for a PS service.
Issue 01 (2013-05-04)
1385
As shown in point A of the figure, when a failure occurs(Ex: SRB reset occurs after sent Radio Bear Reconfiguration Message to UE during the State Transition from CELL_DCH to CELL_PCH or URA_PCH), the RNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then this counter is measured in the serving cell that the UE camps on if the RAB is for a PS service.
Issue 01 (2013-05-04)
1386
Figure 1-617 IU release procedure triggered by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.AbnormR el.E2P Feature ID WRFD-010202 WRFD-010612 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) HSUPA Introduction Package
1.12.13.49 Number of HSUPA Boosting RAB Setup Attempts for Cell
Issue 01 (2013-05-04)
1387
Counters
Counter ID 73423359 Counter Name VS.HSUPA.RAB.Boosting. AttEstab Counter Description Number of HSUPA Boosting RAB Setup Attempts for Cell
Description
This counter provides the number of setup attempts for HSUPA RABs with the E-DPCCH Boosting feature enabled in the serving cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives from the CN an RAB ASSIGNMENT REQUEST message, this counter is measured in the serving cell that the UE camps on if the RNC finds that the RAB is intended for HSUPA services and the E-DPCCH Boosting feature is enabled. Figure 1-618 RAB setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.Boosting. AttEstab Feature ID WRFD-010697 Feature Name E-DPCCH Boosting
1.12.13.50 Number of Successful HSUPA Boosting RAB Setups for Cell Counters
Counter ID 73423360 Counter Name VS.HSUPA.RAB.Boosting. SuccEstab Counter Description Number of Successful HSUPA Boosting RAB Setups for Cell
Description
This counter provides the number of times that an HSUPA RAB with the E-DPCCH Boosting feature enabled is set up successfully in the serving cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends the CN an RAB ASSIGNMENT RESPONSE message after receiving from the UE a RADIO BEARER SETUP COMPLETE message, this counter is measured in the serving cell that the UE camps on if the RAB is intended for HSUPA services and the E-DPCCH Boosting feature is enabled. Figure 1-619 RAB setup procedure (successful operation)
Issue 01 (2013-05-04)
1389
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.Boosting. SuccEstab Feature ID WRFD-010697 Feature Name E-DPCCH Boosting
1.12.13.51 Number of Abnormally Released HSUPA Boosting RABs for Cell Counters
Counter ID 73423361 Counter Name VS.HSUPA.RAB.AbnormR el.Boosting Counter Description Number of Abnormally Released HSUPA Boosting RABs for Cell
Description
This counter provides the number of times that an HSUPA RAB with the E-DPCCH Boosting feature enabled is released abnormally in the serving cell.
Measurement point
The measurement is triggered at point A as shown in Figure 1. When a failure occurs, the RNC sends the CN an RAB RELEASE REQUEST message. After receiving from the CN an RAB ASSIGNMENT REQUEST message, the RNC responds with an RAB ASSIGNMENT RESPONSE message. If the RAB ASSIGNMENT REQUEST message from the CN contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then this counter is measured in the HSUPA serving cell that the UE camps on if the RAB is intended for HSUPA services and the E-DPCCH Boosting feature is enabled.
Issue 01 (2013-05-04)
1390
The measurement is triggered at point A as shown in Figure 2. When a failure occurs, the RNC sends the CN an RAB RELEASE REQUEST message. After receiving from the CN an IU RELEASE COMMAND message, the RNC responds with an IU RELEASE COMPLETE message. If the IU RELEASE COMMAND message from the CN contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then this counter is measured in the HSUPA serving cell that the UE camps on if the RAB is intended for HSUPA services and the E-DPCCH Boosting feature is enabled.
Issue 01 (2013-05-04)
1391
The measurement is also triggered at point A as shown in Figure 3. When a failure occurs, the RNC sends the CN an IU RELEASE REQUEST message. After receiving from the CN an IU RELEASE COMMAND message, the RNC responds with an IU RELEASE COMPLETE message. If the IU RELEASE COMMAND message from the CN contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then this counter is measured in the HSUPA serving cell that the UE camps on if the RAB is intended for HSUPA services and the E-DPCCH Boosting feature is enabled.
Issue 01 (2013-05-04)
1392
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.AbnormR el.Boosting Feature ID WRFD-010697 Feature Name E-DPCCH Boosting
1.12.13.52 Number of Normally Released HSUPA Boosting RABs for Cell Counters
Counter ID 73423362 Counter Name VS.HSUPA.RAB.NormRel. Boosting Counter Description Number of Normally Released HSUPA Boosting RABs for Cell
Issue 01 (2013-05-04)
1393
Description
This counter provides the number of times that an HSUPA RAB with the E-DPCCH Boosting feature enabled is released normally in the serving cell.
Measurement point
The measurement is triggered at point A as shown in Figure 1. After receiving from the CN an IU RELEASE COMMAND message, the RNC releases the corresponding RAB, and then sends the CN an IU RELEASE COMPLETE message. If the release cause in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", or if the RNC has sent a release request with the cause of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before the RNC receives the IU RELEASE COMMAND message, then this counter is measured in the HSUPA serving cell that the UE camps on if the RAB is intended for HSUPA services and the E-DPCCH Boosting feature is enabled. Figure 1-623 Iu release procedure
The measurement is also triggered at point B as shown in Figure 2. After receiving from the CN an RAB ASSIGNMENT REQUEST message indicating that an RAB needs to be released, the RNC releases the corresponding RAB, and then sends the CN an RAB ASSIGNMENT RESPONSE message. If the release cause contained in the RAB ASSIGNMENT REQUEST message is "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", or if the RNC initiates a release request with the cause value of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before receiving the RAB ASSIGNMENT REQUEST message from the CN, then this counter is measured in the HSUPA serving cell that the UE camps on if the RAB is intended for HSUPA services and the E-DPCCH Boosting feature is enabled.
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.NormRel. Boosting Feature ID WRFD-010697 Feature Name E-DPCCH Boosting
1.12.13.53 Number of HARQ PO Reconfiguration Attempts of HSUPA Users with 10 ms TTI for Cell
Issue 01 (2013-05-04)
1395
Counters
Counter ID 73423567 Counter Name VS.HSUPA.HARQ.POReCf gAtt.TTI10ms Counter Description Number of HARQ PO Reconfiguration Attempts of HSUPA Users with 10 ms TTI for Cell
Description
This counter provides the number of HARQ PO reconfiguration attempts of HSUPA users with 10 ms TTI in a cell. The counter is used to evaluate the application of the Adaptive Configuration of Traffic Channel Power offset for HSUPA feature in a network.
Measurement point
At point A shown in the figure, when the RNC sends a RADIO BEAR RECONFIGURATION message during the HARQ PO reconfiguration, the measurement is triggered in the serving cell of HSUPA users. Figure 1-625 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.HARQ.POReCf gAtt.TTI10ms Feature ID WRFD-010712 Feature Name Adaptive Configuration of Traffic Channel Power offset for HSUPA
1.12.13.54 Number of Successful HARQ PO Reconfigurations of HSUPA Users with 10 ms TTI for Cell Counters
Counter ID 73423568 Counter Name VS.HSUPA.HARQ.POReCf gSucc.TTI10ms Counter Description Number of Successful HARQ PO Reconfigurations of HSUPA Users with 10 ms TTI for Cell
Description
This counter provides the number of successful HARQ PO reconfigurations of HSUPA users with 10 ms TTI in a cell. The counter is used to evaluate the application of the Adaptive Configuration of Traffic Channel Power offset for HSUPA feature in a network.
Measurement point
At point B shown in the figure, when the RNC receives a RADIO BEAR RECONFIGURATION COMPLETE message during the HARQ PO reconfiguration, the measurement is triggered in the serving cell of HSUPA users.
Issue 01 (2013-05-04)
1397
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.HARQ.POReCf gSucc.TTI10ms Feature ID WRFD-010712 Feature Name Adaptive Configuration of Traffic Channel Power offset for HSUPA
1.12.13.55 Number of DC-HSUPA RAB Setup Attempts for Cell Counters

Counter ID 73424115 Counter Name VS.HSUPA.RAB.DC.AttEstab Counter Description Number of DC-HSUPA RAB Setup Attempts for Cell
Issue 01 (2013-05-04)
1398
Description
This counter provides the number of DC-HSUPA RAB setup attempts in the serving cell where the DC-HSUPA feature is enabled. This counter is measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point A, as shown in the following figure. When the RNC receives an RAB ASSIGNMENT REQUEST message from the SGSN, this counter is incremented by one in the cell with the primary carrier, if the RNC finds that the RAB is intended for HSUPA services and the DC-HSUPA feature is enabled. Figure 1-627 RAB setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.DC.AttEstab
Issue 01 (2013-05-04)
Feature Name DC-HSUPA
1399
1.12.13.56 Number of Successful DC-HSUPA RAB Setups for Cell Counters

Counter ID 73424116 Counter Name VS.HSUPA.RAB.DC.SuccEstab Counter Description Number of Successful DCHSUPA RAB Setups for Cell
Description
This counter provides the number of successful DC-HSUPA RAB setups in the serving cell where the DC-HSUPA feature is enabled. This counter is measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point B, as shown in the following figure. When the RNC sends the CN an RAB ASSIGNMENT RESPONSE message after receiving from the UE a RADIO BEARER SETUP COMPLETE message, this counter is incremented by one in the cell with the primary carrier, if the RAB is intended for HSUPA services and the DC-HSUPA feature is enabled. Figure 1-628 RAB setup procedure (successful operation)
Issue 01 (2013-05-04)
1400
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.DC.SuccEstab Feature ID WRFD-140204 Feature Name DC-HSUPA
1.12.13.57 Number of DC-HSUPA RABs Normally Released for Cell Counters

Counter ID 73424117 Counter Name VS.HSUPA.RAB.DC.Norm Rel Counter Description Number of DC-HSUPA RABs Normally Released for Cell
Description
This counter provides the number of DC-HSUPA RABs normally released by the RNC in the serving cell where the DC-HSUPA feature is enabled. This counter is measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point A, as shown in the following figure. After receiving an IU RELEASE COMMAND message from the CN, the RNC releases the corresponding RAB and then sends an IU RELEASE COMPLETE message to the CN. In this case, this counter is incremented by one in the cell with the primary carrier if the following conditions are met: The cause in the IU RELEASE COMMAND message is User Inactivity, Normal Release, Successful Relocation, or Network Optimization, or the RNC has sent a release request with the cause of User Inactivity, Network Optimization, or UE Generated Signalling Connection Release before the RNC receives the IU RELEASE COMMAND message. The RAB carries DC-HSUPA services and the DC-HSUPA feature is enabled in the serving cell.
Issue 01 (2013-05-04)
1401
This measurement is triggered at point B, as shown in the following figure. After receiving an RAB ASSIGNMENT REQUEST message with an RAB release request from the CN, the RNC releases the corresponding RAB and then sends an RAB ASSIGNMENT RESPONSE message to the CN. This counter is incremented by one in the cell with the primary carrier if the following conditions are met: The cause in the RAB ASSIGNMENT REQUEST message is User Inactivity, Normal Release, Successful Relocation, or Network Optimization, or the RNC has sent a release request with the cause of User Inactivity, Network Optimization, or UE Generated Signalling Connection Release before the RNC receives the RAB ASSIGNMENT REQUEST message. The RAB carries DC-HSUPA services and the DC-HSUPA feature is enabled in the serving cell.
Issue 01 (2013-05-04)
1402
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.DC.Norm Rel Feature ID WRFD-140204 Feature Name DC-HSUPA
1.12.13.58 Number of DC-HSUPA RABs Abnormally Released for Cell Counters

Counter ID 73424118 Counter Name VS.HSUPA.RAB.DC.AbnormRel Counter Description Number of DC-HSUPA RABs Abnormally Released for Cell
Issue 01 (2013-05-04)
1403
Description
This counter provides the number of DC-HSUPA RABs abnormally released by the RNC in the serving cell where the DC-HSUPA feature is enabled. This counter is measured only in the cell with the primary carrier.
Measurement point
This measurement is triggered at point A, as shown in the following figure. When a failure occurs, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an RAB ASSIGNMENT REQUEST message with a cause other than User Inactivity, Normal Release, Successful Relocation, or Network Optimization and if the RAB carries DC-HSUPA services, then this counter is incremented by one in the cell with the primary carrier. Figure 1-631 RAB release procedure
This measurement is triggered at point A, as shown in the following figure. When a failure occurs, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message with a cause other than User Inactivity, Normal Release, Successful Relocation, or Network Optimization and if the RAB carries DCHSUPA services, then this counter is incremented by one in the cell with the primary carrier. For details about the causes indicating a normal RAB release, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
1404
This measurement is triggered at point A, as shown in the following figure. When a failure occurs, the RNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message with a cause other than User Inactivity, Normal Release, Successful Relocation, or Network Optimization and if the RAB carries DC-HSUPA services, then this counter is incremented by one in the cell with the primary carrier. For details about causes indicating a normal RAB release, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
1405
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.DC.AbnormRel Feature ID WRFD-140204 Feature Name DC-HSUPA
1.12.13.59 Number of HSUPA UEs in a Cell Counters

Counter ID 73424192 Counter Name VS.HSUPA.DC.PRIM.UE. Mean.Cell Counter Description Mean Number of DCHSUPA Users in the Cell with the Primary Carrier
1406
Issue 01 (2013-05-04)
Counter ID 73441238
Counter Name VS.HSUPA.DC.SEC.UE.M ean.Cell
Counter Description Mean Number of DCHSUPA Users in the Cell with the Secondary Carrier
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73424194 Counter Name VS.HSUPA.DC.PRIM.UE. Mean.Cell.DENO VS.HSUPA.DC.PRIM.UE. Mean.Cell.NUM VS.HSUPA.DC.SEC.UE.M ean.Cell.DENO VS.HSUPA.DC.SEC.UE.M ean.Cell.NUM Counter Description Average Number of HSUPA UEs in a primary Cell (Denominator) Average Number of HSUPA UEs in a primary Cell (Numerator) Average Number of HSUPA UEs in supplementary carrier Cell(Denominator) Average Number of HSUPA UEs in supplementary carrier Cell(Numerator)
73424193
73424196
73424195
Description
These counters provide the mean number of DC-HSUPA users in the cell with the primary carrier and the mean number of DC-HSUPA users in the cell with the secondary carrier, respectively.
Measurement point
The RNC takes samples every 5 seconds at each measurement point. At the end of each measurement period, the RNC divides the sum of sampling results by the number of samples. Intermediate counters: VS.HSUPA.DC.PRIM.UE.Mean.Cell.DENO: Sampling times in the measurement period (denominator) VS.HSUPA.DC.PRIM.UE.Mean.Cell.NUM: Accumulated Number of DC-HSUPA Users in the Cell with the Primary Carrier at the sampling points in the measurement period (numerator) VS.HSUPA.DC.SEC.UE.Mean.Cell.DENO: Sampling times in the measurement period (denominator) VS.HSUPA.DC.SEC.UE.Mean.Cell.NUM: Accumulated Number of DC-HSUPA Users in the Cell with the Secondary Carrier at the sampling points in the measurement period (numerator)
Formula
VS.HSUPA.DC.PRIM.UE.Mean.Cell = [VS.HSUPA.DC.PRIM.UE.Mean.Cell.NUM]/ [VS.HSUPA.DC.PRIM.UE.Mean.Cell.DENO] VS.HSUPA.DC.SEC.UE.Mean.Cell = [VS.HSUPA.DC.SEC.UE.Mean.Cell.NUM]/ [VS.HSUPA.DC.SEC.UE.Mean.Cell.DENO]
Unit
None
Related Features
Counter Name VS.HSUPA.DC.PRIM.UE. Mean.Cell VS.HSUPA.DC.SEC.UE.M ean.Cell Feature ID WRFD-140204 WRFD-140204 Feature Name DC-HSUPA DC-HSUPA
1.12.13.60 Number of HSUPA 2 ms TTI UEs in a Cell Counters

Counter ID 73441239 73424199 Counter Name VS.HSUPA.UE.Mean.TTI2 ms VS.HSUPA.UE.Max.TTI2m s Counter Description Average Number of HSUPA 2 ms TTI UEs in a Cell Maximum Number of HSUPA 2 ms TTI UEs in a Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73424198 Counter Name VS.HSUPA.UE.Mean.TTI2 ms.DENO VS.HSUPA.UE.Mean.TTI2 ms.NUM Counter Description Average Number of HSUPA 2 ms TTI UEs in a Cell (Denominator) Average Number of HSUPA 2 ms TTI UEs in a Cell (Numerator)
73424197
Description
These counters provide the average and maximum numbers of HSUPA 2 ms TTI UEs in a cell. For DC-HSUPA users, these counters are measured only in the cell with the primary carrier.
Measurement point
The RNC takes samples every 5 seconds at each measurement point. At the end of each measurement period, the RNC sums sample results and divides the sum by the number of
samples. The division result is the mean number of HSUPA 2 ms TTI UEs in a cell. Of the sample results, the maximum value is the maximum number of HSUPA 2 ms TTI UEs in the cell. Intermediate counters: VS.HSUPA.UE.Mean.TTI2ms.DENO: Sampling times in the measurement period (denominator) VS.HSUPA.UE.Mean.TTI2ms.NUM: Accumulated number of HSUPA 2 ms TTI UEs at the sampling points in a cell in the measurement period (numerator)
Formula
VS.HSUPA.UE.Mean.TTI2ms = [VS.HSUPA.UE.Mean.TTI2ms.NUM]/ [VS.HSUPA.UE.Mean.TTI2ms.DENO]
Unit
None
Related Features
Counter Name VS.HSUPA.UE.Mean.TTI2 ms Feature ID WRFD-010612 WRFD-01061403 WRFD-010612 WRFD-01061403 Feature Name HSUPA Introduction Package HSUPA 2ms TTI VS.HSUPA.UE.Max.TTI2m s HSUPA Introduction Package HSUPA 2ms TTI
1.12.13.61 Number of HSUPA 10 ms TTI UEs in a Cell Counters

Counter ID 73441240 73424202 Counter Name VS.HSUPA.UE.Mean.TTI1 0ms VS.HSUPA.UE.Max.TTI10 ms Counter Description Average number of HSUPA 10 ms TTI UEs in a Cell Maximum Number of HSUPA 10 ms TTI UEs in a Cell
Issue 01 (2013-05-04)
1409
Counter ID 73424201
Counter Name VS.HSUPA.UE.Mean.TTI1 0ms.DENO VS.HSUPA.UE.Mean.TTI1 0ms.NUM
Counter Description Average Number of HSUPA 10 ms TTI UEs in a Cell (Denominator) Average Number of HSUPA 10 ms TTI UEs in a Cell (Numerator)
73424200
Description
These counters provide the average and maximum numbers of HSUPA 10 ms TTI UEs in a cell.
Measurement point
The RNC takes samples every 5 seconds at each measurement point. At the end of each measurement period, the RNC sums sample results and divides the sum by the number of samples. The division result is the mean number of HSUPA 10 ms TTI UEs in a cell. Of the sample results, the maximum value is the maximum number of HSUPA 10 ms TTI UEs in the cell. Intermediate counters: VS.HSUPA.UE.Mean.TTI10ms.DENO: Sampling times in the measurement period (denominator) VS.HSUPA.UE.Mean.TTI10ms.NUM: Accumulated number of HSUPA 10 ms TTI UEs at the sampling points in a cell in the measurement period (numerator)
Formula
VS.HSUPA.UE.Mean.TTI10ms = [VS.HSUPA.UE.Mean.TTI10ms.NUM]/ [VS.HSUPA.UE.Mean.TTI10ms.DENO]
Unit
None
Related Features
Counter Name VS.HSUPA.UE.Mean.TTI1 0ms VS.HSUPA.UE.Max.TTI10 ms Feature ID WRFD-010612 WRFD-010612 Feature Name HSUPA Introduction Package HSUPA Introduction Package
1.12.13.62 Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI in a Cell with Various Causes
Issue 01 (2013-05-04)
1410
Counters
Counter ID 73424205 Counter Name VS.HSUPA.RABEstabTTI1 0ms.AdmCE.Succ Counter Description Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI Due to Congestion of Admitted CEs in a Cell Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI Due to RTWP Congestion in a Cell Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI Due to Congestion of Occupied CEs in a Cell Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI Due to Iub Resource Congestion in a Cell Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI Due to Limited Uplink Coverage
73424206
VS.HSUPA.RABEstabTTI1 0ms.ResRTWP.Succ
73424207
VS.HSUPA.RABEstabTTI1 0ms.ResUsedCE.Succ
73424208
VS.HSUPA.RABEstabTTI1 0ms.ResIUB.Succ
73424967
VS.HSUPA.RABEstabTTI1 0ms.Cover.Succ
Description
These counters provide the number of successful RAB establishments for HSUPA 2 ms UEs configured with a 10 ms TTI due to various causes.
Measurement point
At measurement point B shown in the following figure, the RNC receives an RAB ASSGINMENT REQUEST message from the CN and an HSUPA 2 ms UE is configured with a 10 ms TTI even though conditions on 2 ms TTI have been met. After an RB is set up and the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN, a specific counter in the serving cell is increased by one and this specific counter is determined by the congestion cause.
Issue 01 (2013-05-04)
1411
Formula
None
Unit
None
Related Features
None
1.12.13.63 Number of Abnormal RAB Releases for Cell During State Transition of HSUPA UEs to CELL/URA_PCH Counters
Counter ID 73425950 Counter Name VS.HSUPA.RAB.AbnormRel.16QAM2P Counter Description Number of Abnormal RAB Releases for Cell During State Transition of HSUPA +16QAM UEs to CELL/ URA_PCH
Issue 01 (2013-05-04)
1412
Counter ID 73425951
Counter Name VS.HSUPA.RAB.AbnormR el.DC2P
Counter Description Number of Abnormal RAB Releases for Cell During State Transition of DCHSUPA UEs to CELL/ URA_PCH
Description
These counters provide the number of abnormal RAB releases during the state transition of HSUPA UEs to CELL_PCH or URA_PCH in the serving cell. For DC-HSUPA UEs, this counter is measured only in the primary carrier cell.
Measurement point
As shown by point A in figure 1, when an exception occurs, the RNC sends the CN an RAB RELEASE REQUEST message. When the RNC receives from the CN an RAB ASSIGNMENT REQUEST message with the cause value being other than "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", this counter is increased by one in the serving cell where the UE camps. For details on cause values indicating RAB releases, see 3GPP TS 25.413. Figure 1-635 The release process of RAB
As shown by point A in figure 2, when an exception occurs, the RNC sends the CN a RAB RELEASE REQUEST message. When the RNC receives from the CN an IU RELEASE COMMAND message with the cause value being other than "User Inactivity", "Normal
Release", "Successful Relocation", or "Network Optimization", this counter is increased by one in the serving cell where the UE camps. For details on cause values indicating RAB releases, see 3GPP TS 25.413. Figure 1-636 The IU release process of RAB
As shown by point A in figure 3, when an exception occurs, the RNC sends the CN an IU RELEASE REQUEST message. When the RNC receives from the CN an IU RELEASE COMMAND message with the cause value being other than "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", this counter is increased by one in the serving cell where the UE camps. For details on cause values indicating RAB releases, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
1414
Figure 1-637 The IU release process launched by RNC
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.AbnormRel.16QAM2P VS.HSUPA.RAB.AbnormR el.DC2P Feature ID WRFD-010694 WRFD-140204 Feature Name UL 16QAM DC-HSUPA
1.12.13.64 Number of Normal RAB Releases of HSUPA UEs for Cell (All Scenarios)
Issue 01 (2013-05-04)
1415
Counters
Counter ID 73425952 Counter Name VS.HSUPA.RAB.NormRel. 16QAM.All Counter Description Number of Normal RAB Releases of HSUPA +16QAM UEs for Cell (All Scenarios) Number of Normal RAB Releases of DC-HSUPA UEs for Cell (All Scenarios)
73425953
VS.HSUPA.RAB.NormRel. DC.All
Description
These counters provide the number of normal RAB releases in a serving cell when HSUPA is applied. For DC-HSUPA users, this counter is measured only in the cell with the primary carrier. Note: The normal RAB releases on HSUPA channels include the RAB releases over the Iu interface and the switchover of the RAB from a technique to another one. The following uses DC-HSUPA as an example to describe a normal RAB release. (1) The DC-HSUPA RAB has been released over the Iu interface. (2) The RAB successfully falls back from DC-HSUPA to SC-HSUPA or R99 through a channel switchover procedure. In R99, the UE can be in the CELL_DCH, CELL_FACH, CELL_PCH, or URA_PCH state. (3) The RAB successfully falls back from DC-HSUPA to SC-HSUPA or to R99 in CELL_DCH state through an inter-cell hard handover procedure. The two cells can operate in either the same or different frequencies.
Measurement point
As shown by point A in figure 1 (HSUPA UEs enter the idle state), after receiving an IU RELEASE COMMAND message from the CN, the RNC releases the corresponding RAB and then sends an IU RELEASE COMPLETE message to the CN. This counter is increased by one in the serving cell where the UE camps when either of the following condition is met: The cause value in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization." Alternatively, the RNC has initiated a release request with the cause value "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before receiving the IU RELEASE COMMAND message.
Issue 01 (2013-05-04)
1416
As shown by point B in figure 2 (HSUPA UEs enter the idle state), after receiving an RAB ASSIGNMENT REQUEST message with an RAB release request from the CN, the RNC releases the corresponding RAB and then sends an RAB ASSIGNMENT RESPONSE message to the CN. This counter is increased by one in the serving cell where the UE camps when either of the following condition is met: The cause value in the RAB ASSIGNMENT REQUEST message is "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization." Alternatively, the RNC has initiated a release request with the cause value "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before receiving the RAB ASSIGNMENT REQUEST message.
Issue 01 (2013-05-04)
1417
As shown by point B in figure 3 (all types of hard handovers for HSUPA UEs), the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from a UE. If the UE is performing a hard handover on the RAB from HSUPA channel to channels of other types, this counter is increased by one in the serving cell of the UE. As shown by point B in figure 3 (all types of channel switchovers for HSUPA UEs), the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from a UE. If the UE is performing a switchover on the RAB from HSUPA channel to channels of other types, this counter is increased by one in the serving cell of the UE.
Issue 01 (2013-05-04)
1418
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.RAB.NormRel. 16QAM.All VS.HSUPA.RAB.NormRel. DC.All Feature ID WRFD-010694 WRFD-140204 Feature Name UL 16QAM DC-HSUPA
1.12.14 InterRAT Handover Measurement per cell (INTRAT.HO.Cell)

Overview
Inter-RAT handover is classified into CS inter-RAT handover and PS inter-RAT handover. PS inter-RAT handover is further classified into normal PS inter-RAT handover and enhanced PS
inter-RAT handover, where the procedure of the enhanced PS inter-RAT handover is the same as that of the CS inter-RAT handover. For the detailed inter-RAT handover procedure, see the function subset IRATHO.Cs.RNC or IRATHO.PS.RNC. The counters related to the number of failed handovers during different phases of outgoing handovers and incoming handovers are measured based on different handover causes. The causes for outgoing inter-RAT handover can be load, RF (coverage, QoS, or HCS), interRAT DRD, or service type. The cause inter-RAT DRD only exists in the inter-RAT CS handover. The following figure shows the measurement points in the inter-RAT CS handover measuremnt.
Figure 1-641 Flow chart of outgoing inter-RAT handover measurement procedure
Table 1 describes the measurement points shown in Figure1.

Measurement points A
Description VS.IRATHO.AttRelocPrepOutCS.DR, VS.IRATHO.AttRelocPrepOutCS.RF (These counters list here are only part examples. Other Specific counters are triggered based on other specific causes, please refer to this function subset.) VS.IRATHO.SuccRelocPrepOutCS.RF, VS.IRATHO.SuccRelocPrepOutCS.DR (These counters list here are only part examples. Other Specific counters are triggered based on other specific causes, please refer to this function subset.) IRATHO.AttOutCS IRATHO.SuccOutCS IRATHO.FailRelocPrepOutCS.UKnowRN C, IRATHO.FailRelocPrepOutCS.NoResAvail(These counters list here are only part examples. Other Specific counters are triggered based on other specific causes, please refer to this function subset.) IRATHO.FailOutCS.CfgUnsupp, IRATHO.FailOutCS.PhyChFail VS.IRATHO.FailOutCS.NoReply IRATHO.AttOutPSUTRAN IRATHO.SuccOutPSUTRAN IRATHO.FailOutPSUTRAN.CfgUnsupp,IR ATHO.FailOutPSUTRAN.PhyChFail VS.IRATHO.FailOutPSUTRAN.NoReply VS.IRATHO.AttOutPSUE IRATHO.SuccOutPSUE
C D E
F G H I J K L M
Issue 01 (2013-05-04)
1421
Figure 1-642 Flow chart of incoming inter-RAT handover measurement procedure
Table 2 describes the measurement points shown in Figure2. Measurement points A B C Description VS.IRATHO.AttRelocPrepInCS VS.IRATHO.SuccRelocPrepInCS VS.IRATHO.AttInCS
Issue 01 (2013-05-04)
1422
Measurement points D E
Description VS.IRATHO.SuccInCS VS.IRATHO.FailRelocPrepInCS.ResUnavail, VS.IRATHO.FailRelocPrepInCS.TgtHighLoad(These counters list here are only part examples. Other Specific counters are triggered based on other specific causes, please refer to this function subset.) VS.IRATHO.FailInCS.NoReply See counter "RRC.AttConnEstab.IRATCelRes" in function subset "RRC.Setup.Cell" See counter "RRC.SuccConnEstab.IRATCelRes" in function subset "RRC.Setup.Cell" See counter "RRC.AttConnEstab.IRATCCO" in function subset "RRC.Setup.Cell" See counter "RRC.SuccConnEstab.IRATCCO" in function subset "RRC.Setup.Cell"
F G H I J
Counters
Counter ID 67189729 Counter Name VS.IRATHO.Succ OutCS.DR Counter Description Number of Successful CS Outgoing Inter-RAT Handovers Based on Directed Retry for Cell Number of Preparation Attempts for CS Outgoing Inter-RAT Handover Based on Directed Retry for Cell Number of Successful Preparations for CS Outgoing Inter-RAT Handover Based on Directed Retry for Cell Original Release Earlier than V900R011
67189730
VS.IRATHO.AttRe locPrepOutCS.DR
67189732
VS.IRATHO.Succ RelocPrepOutCS.D R
Issue 01 (2013-05-04)
1423
Counter ID 67189739
Counter Name VS.IRATHO.AttRe locPrepOutCS.Loa d
Counter Description Number of Preparation Attempts for CS Outgoing Inter-RAT Handover Initiated by UTRAN Based on Load for Cell Number of Successful Preparations for CS Outgoing Inter-RAT Handover Initiated by UTRAN Based on Load for Cell Number of Successful CS Outgoing Inter-RAT Handovers Based on Load for Cell Number of PS Outgoing Inter-RAT Handover Attempts Initiated by UTRAN Based on Load for Cell Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UTRAN Based on Load for Cell Number of Preparation Attempts for CS Outgoing Inter-RAT Handover Based on RF (Coverage, QoS, or HCS) for Cell Number of Successful Preparations for CS Outgoing Inter-RAT Handover Based on RF (Coverage, QoS, or HCS) for Cell
67189740
VS.IRATHO.Succ RelocPrepOutCS.L oad
67189741
VS.IRATHO.Succ OutCS.Load
67189742
VS.IRATHO.AttO utPSUTRAN.Load
67189743
VS.IRATHO.Succ OutPSUTRAN.Loa d
67189744
VS.IRATHO.AttRe locPrepOutCS.RF
67189745
VS.IRATHO.Succ RelocPrepOutCS.R F
Issue 01 (2013-05-04)
1424
Counter ID 67189746
Counter Name VS.IRATHO.Succ OutCS.RF
Counter Description Number of Successful CS Outgoing Inter-RAT Handovers Based on RF (Coverage, QoS, or HCS) for Cell Number of PS Outgoing Inter-RAT Handover Attempts Initiated by the RNC Based on RF (Coverage, QoS, or HCS) for Cell Number of Successful PS Outgoing Inter-RAT Handovers Initiated by the RNC Based on RF (Coverage, QoS, or HCS) for Cell Number of Preparation Attempts for CS Outgoing Inter-RAT Handover for Cell Number of Successful Preparations for CS Outgoing Inter-RAT Handover for Cell Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (TRELOCalloc expiry) Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (Relocation Failure in Target CN/RNC or Target System)
67189747
VS.IRATHO.AttO utPSUTRAN.RF
67189748
VS.IRATHO.Succ OutPSUTRAN.RF
67189749
IRATHO.AttRelocPrepOutCS
67189750
IRATHO.SuccRelocPrepOutCS
67189751
IRATHO.FailReloc PrepOutCS.TAlEx p
67189752
IRATHO.FailReloc PrepOutCS.TgtFail
Issue 01 (2013-05-04)
1425
Counter ID 67189753
Counter Name IRATHO.FailReloc PrepOutCS.ReloNoSup
Counter Description Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (Relocation not supported in Target RNC or Target system) Number of CS Outgoing Inter-RAT Handover Attempts Number of Successful CS Outgoing Inter-RAT Handovers for Cell Number of Failed CS Outgoing Inter-RAT Handovers for Cell (Configuration Unsupported) Number of Failed CS Outgoing Inter-RAT Handovers for Cell (Physical Channel Failure) Number of Preparations for CS Incoming Inter-RAT Handover for Cell Number of Successful CS Incoming Inter-RAT Handovers for Cell Number of Failed Preparations for CS Incoming Inter-RAT Handover (Relocation failure in target CN/RNC or target system)
67189754
IRATHO.AttOutC S IRATHO.SuccOut CS
67189755
67189756
IRATHO.FailOutC S.CfgUnsupp
67189757
IRATHO.FailOutC S.PhyChFail
67189758
VS.IRATHO.AttRe locPrepInCS
67189759
VS.IRATHO.SuccInCS
67189760
VS.IRATHO.FailR elocPrepInCS.TRN CSysFailReloc
Issue 01 (2013-05-04)
1426
Counter ID 67189761
Counter Name VS.IRATHO.FailR elocPrepInCS.TRN CSysRelocUnsupp
Counter Description Number of Failed Preparations for CS Incoming Inter-RAT Handover (Relocation not supported in target RNC or target system) Number of Failed Preparations for CS Incoming Inter-RAT Handover (No resource available) Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE for Cell Number of Failed CS Inter-RAT Incoming Handovers Due to No Response from UE for Cell Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC for Cell Number of Successful PS Outgoing Inter-RAT Handovers Initiated by RNC for Cell Number of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC (Configuration unsupported) Number of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC (Physical Channel Failure)
67189762
VS.IRATHO.FailR elocPrepInCS.ResUnavail
67189763
IRATHO.SuccOutPSUE
67190410
VS.IRATHO.FailI nCS.NoReply
67190411
IRATHO.AttOutPSUTRAN
67190412
IRATHO.SuccOutPSUTRAN
67190476
IRATHO.FailOutP SUTRAN.CfgUnsu pp
67190477
IRATHO.FailOutP SUTRAN.PhyChFa il
Issue 01 (2013-05-04)
1427
Counter ID 67190413
Counter Name VS.IRATHO.AttOutPSUE
Counter Description Number of PS InterRAT Outgoing InterRAT Handover Requests Initiated by UE for Cell Number of Successful preparations for CS Incoming Inter-RAT Handovers for Cell Number of Preparation Attempts for CS Outgoing Inter-RAT Handover Based on Service Type for Cell Number of Successful Preparations for CS Outgoing Inter-RAT Handover Based on Service Type for Cell Number of Successful CS Outgoing Inter-RAT Handovers Based on Service Type for Cell Number of PS Outgoing Inter-RAT Handover Attempts Initiated by the RNC Based on Service Type for Cell Number of Successful PS Outgoing Inter-RAT Handovers Initiated by the RNC Based on Service Type for Cell Number of PS InterRAT Outgoing Handover Attempts for HSDPA Services for Cell
67190414
VS.IRATHO.SuccRelocPrepInCS
67190593
VS.IRATHO.AttRe locPrepOutCS.Serv ice
67190856
VS.IRATHO.Succ RelocPrepOutCS.S ervice
67190857
VS.IRATHO.Succ OutCS.Service
67190858
VS.IRATHO.AttO utPSUTRAN.Service
67190859
VS.IRATHO.Succ OutPSUTRAN.Ser vice
67191155
VS.IRATHO.HSD PA.AttOutPSUTR AN
Issue 01 (2013-05-04)
1428
Counter ID 67191156
Counter Name VS.IRATHO.HSD PA.SuccOutPSUTRAN
Counter Description Number of Successful PS Outgoing Inter-RAT Handovers for HSDPA Services for Cell Number of Successful PS Outgoing Inter-RAT Handovers for HSUPA Services for Cell Number of PS Outgoing Inter-RAT Handover Attempts for HSUPA Services for Cell Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (Traffic Load In The Target Cell Higher Than In The Source Cell) Number of Failed Preparations for CS Incoming Inter-RAT Handover (Traffic Load In The Target Cell Higher Than In The Source Cell) Number of Preparations for CS Outgoing Inter-RAT Handover When only Signaling Exists for Cell Number of Successful Preparations for CS Outgoing Inter-RAT Handover When only Signaling Exists for Cell
67192506
VS.IRATHO.HSU PA.SuccOutPSUTRAN
67192507
VS.IRATHO.HSU PA.AttOutPSUTR AN
67192186
IRATHO.FailReloc PrepOutCS.HigherTrafficLod
67192187
VS.IRATHO.FailR elocPrepInCS.Tgt HighLoad
67192654
VS.IRATHO.AttRe locPrepOutCS.Sig
67192655
VS.IRATHO.Succ RelocPrepOutCS.S ig
Issue 01 (2013-05-04)
1429
Counter ID 67192656
Counter Name VS.IRATHO.AttO utCS.Sig
Counter Description Number of CS Outgoing Inter-RAT Handover Attempts When only Signaling Exists for Cell Number of Successful CS Outgoing Inter-RAT Handovers When only Signaling Exists for Cell Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (No Resource Available) Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (Unknown Target RNC) Number of Times that the Timer Waiting for Iu Release Command Expires in CS Outgoing Inter-RAT Handover for Cell Number of Times that the Timer Waiting for Iu Release Command Expires in PS Outgoing Inter-RAT Handover Initiated by RNC for Cell Number of Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell
67192657
VS.IRATHO.Succ OutCS.Sig
67192658
IRATHO.FailReloc PrepOutCS.NoResAvail
67192659
IRATHO.FailReloc PrepOutCS.UKno wRNC
67192660
VS.IRATHO.FailO utCS.NoReply
67192661
VS.IRATHO.FailO utPSUTRAN.NoRe ply
67192662
VS.IRATHO.AttRe locPrepOutPS
Issue 01 (2013-05-04)
1430
Counter ID 67192663
Counter Name VS.IRATHO.SuccRelocPrepOutPS
Counter Description Number of Successful Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell Number of Enhanced PS Outgoing InterRAT Handover Attempts for Cell Number of Successful Enhanced PS Outgoing InterRAT Handovers for Cell Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (TRELOCalloc expiry) Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (Relocation Failure in Target CN/RNC or Target System) Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (Relocation not supported in Target RNC or Target system)
67192664
VS.IRATHO.AttRe locOutPS
67192665
VS.IRATHO.SuccRelocOutPS
67192666
VS.IRATHO.FailR elocPrepOutPS.TA lExp
67192667
VS.IRATHO.FailR elocPrepOutPS.Tgt Fail
67192668
VS.IRATHO.FailR elocPrepOutPS.ReloUnSupp
Issue 01 (2013-05-04)
1431
Counter ID 67192669
Counter Name VS.IRATHO.FailR elocPrepOutPS.Tgt HighLoad
Counter Description Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (Traffic Load In The Target Cell Higher Than In The Source Cell) Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (No Resource Available) Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (Unknown Target RNC) Number of Failed Enhanced PS Outgoing Inter-RAT Handovers for Cell (Configuration Unsupported) Number of Failed Enhanced PS Outgoing Inter-RAT Handovers for Cell (Physical Channel Failure) Number of Times that the Timer Waiting for Iu Release Command Expires in Enhanced PS Outgoing InterRAT Handover for Cell
67192670
VS.IRATHO.FailR elocPrepOutPS.No ResAvail
67192671
VS.IRATHO.FailR elocPrepOutPS.UnKnowRNC
67192672
VS.IRATHO.FailR elocOutPS.CfgUnSupp
67192673
VS.IRATHO.FailR elocOutPS.PhyChFail
67192674
VS.IRATHO.FailR elocOutPS.NoReply
Issue 01 (2013-05-04)
1432
Counter ID 67192675
Counter Name VS.IRATHO.AttRe locPrepInPS
Counter Description Number of Preparations for Enhanced PS Incoming Inter-RAT Handover for Cell Number of Successful Preparations for Enhanced PS Incoming Inter-RAT Handover for Cell Number of Successful Enhanced PS Incoming InterRAT Handovers for Cell Number of Failed Preparations for Enhanced PS Incoming Inter-RAT Handover for cell (Relocation failure in target CN/RNC or target system) Number of Failed Preparations for Enhanced PS Incoming Inter-RAT Handover for cell (Relocation not supported in target RNC or target system) Number of Failed Preparations for Enhanced PS Incoming Inter-RAT Handover for cell (No resource available)
67192676
VS.IRATHO.SuccRelocPrepInPS
67192677
VS.IRATHO.SuccRelocInPS
67192678
VS.IRATHO.FailR elocPrepInPS.TgtF ail
67192679
VS.IRATHO.FailR elocPrepInPS.ReloUnSupp
67192680
VS.IRATHO.FailR elocPrepInPS.ResUnavail
Issue 01 (2013-05-04)
1433
Counter ID 67192681
Counter Name VS.IRATHO.FailR elocPrepInPS.TgtH ighLoad
Counter Description Number of Failed Preparations for Enhanced PS Incoming Inter-RAT Handover for cell (Traffic Load In The Target Cell Higher Than In The Source Cell) Number of Failed Enhanced PS Incoming Inter-RAT Handovers Due to UE Response Timeout for Cell Number of CS InterRAT Measurement Expiry for Cell Number of PS InterRAT Measurement Expiry for Cell Number of CS InterRAT Handover Attempts Based on RSCP for Cell Number of CS InterRAT Handover Attempts Based on EcNo for Cell Number of PS InterRAT Handover Attempts Based on RSCP for Cell Number of PS InterRAT Handover Attempts Based on EcNo for Cell Number of CS Outgoing Inter-RAT Handover Attempts Based on Measurement for Cell
67192682
VS.IRATHO.FailR elocInPS.NoReply
67193399
VS.IRATHO.OutC S.MeasTimeOut VS.IRATHO.OutP S.MeasTimeOut VS.IRATHO.AttO utCS.TrigRscp
67193400
67193405
67193406
VS.IRATHO.AttO utCS.TrigEcNo
67193407
VS.IRATHO.AttO utPS.TrigRscp
67193408
VS.IRATHO.AttO utPS.TrigEcNo
67196299
VS.IRATHO.AttO utCS.MBDR
Issue 01 (2013-05-04)
1434
Counter ID 67196300
Counter Name VS.IRATHO.Succ OutCS.MBDR
Counter Description Number of Successful CS Outgoing Inter-RAT Handovers Based on Measurement for Cell Number of CS InterRAT Handover Attempts Based on UL Transmit Power of UE for Cell Number of CS InterRAT Handover Attempts Based on DL Code Power for Cell Number of PS InterRAT Handover Attempts Based on UL Transmit Power of UE for Cell Number of PS InterRAT Handover Attempts Based on DL Code Power for Cell Number of Successful CS InterRAT Handovers Based on RSCP for Cell Number of Successful CS InterRAT Handovers Based on EcNo for Cell Number of Successful CS InterRAT Handovers Based on UL Transmit Power of UE for Cell
73393922
VS.IRATHO.AttO utCS.TrigULTxp
V900R012
73393923
VS.IRATHO.AttO utCS.TrigDLTxp
V900R012
73393924
VS.IRATHO.AttO utPS.TrigULTxp
V900R012
73393925
VS.IRATHO.AttO utPS.TrigDLTxp
V900R012
73393926
VS.IRATHO.Succ OutCS.TrigRscp
V900R012
73393927
VS.IRATHO.Succ OutCS.TrigEcNo
V900R012
73393928
VS.IRATHO.Succ OutCS.TrigULTxp
V900R012
Issue 01 (2013-05-04)
1435
Counter ID 73393929
Counter Name VS.IRATHO.Succ OutCS.TrigDLTxp
Counter Description Number of Successful CS InterRAT Handovers Based on DL Code Power for Cell Number of Successful PS InterRAT Handovers Based on RSCP for Cell Number of Successful PS InterRAT Handovers Based on EcNo for Cell Number of Successful PS InterRAT Handovers Based on UL Transmit Power of UE for Cell Number of Successful PS InterRAT Handovers Based on DL Code Power for Cell Number of CS Incoming Inter-RAT Handover Attempts for Cell Number of Failed CS Outgoing Inter-RAT Handover Preparations for Cell (Relocation Cancelled) Number of Failed CS Outgoing Inter-RAT Handover Preparations for Cell (Relocation Command Wait Timeout)
73393930
VS.IRATHO.Succ OutPS.TrigRscp
V900R012
73393931
VS.IRATHO.Succ OutPS.TrigEcNo
V900R012
73393932
VS.IRATHO.Succ OutPS.TrigULTxp
V900R012
73393933
VS.IRATHO.Succ OutPS.TrigDLTxp
V900R012
73394014
VS.IRATHO.AttInCS
V900R012
73394015
VS.IRATHO.FailR elocPrepOutCS.Ca ncel
V900R012
73394016
VS.IRATHO.FailR elocPrepOutCS.CN NoReply
V900R012
Issue 01 (2013-05-04)
1436
Counter ID 73394017
Counter Name VS.IRATHO.FailR elocPrepInCS.Abor t
Counter Description Number of CS Incoming Inter-RAT Handover Preparation Failures for Cell (Iu RELEASE COMMAND Received) Number of Abnormally Terminated CS Outgoing Inter-RAT Handovers for Cell Number of CS Outgoing Inter-RAT Handover Preparation Failures for Cell (Iu RELEASE COMMAND Received) Number of Failed CS Outgoing Inter-RAT Handover Preparations for Cell (Requested Information Not Available) Number of Failed PS Outgoing Inter-RAT Handovers Initiated by the RNC for Cell Number of Abnormally Terminated PS Outgoing Inter-RAT Handovers for Cell Number of Failed Outgoing UMTS-toGSM PS Handovers due to UE Reselection Back to a UTRAN Cell
73394018
VS.IRATHO.FailO utCS.Abort
V900R012
73394019
VS.IRATHO.FailR elocPrepOutCS.Ab ort
V900R012
73394020
VS.IRATHO.FailR elocPrepOutCS.ReqInfoNotAvail
V900R012
73394021
VS.IRATHO.FailOutPS
V900R012
73394022
VS.IRATHO.FailO utPS.Abort
V900R012
73423107
VS.IRATHO.FailO utPS.UEGen
V900R013
Issue 01 (2013-05-04)
1437
Counter ID 73423288
Counter Name VS.SRVCC.U2GE RAN.AttRelocPrepOutPS
Counter Description Number of Outgoing Inter-RAT PS Handover Preparation Attempts Triggered by SRVCC for VoIP Services for Cell Number of Successful Outgoing Inter-RAT PS Handover Preparations Triggered by SRVCC for VoIP Services for Cell Number of Successful Outgoing Inter-RAT PS Handovers Triggered by SRVCC for VoIP Services for Cell Number of Failed CS Outgoing Inter-RAT Handovers for Cell (Signalling Connection Release Indication) Number of Failed PS Outgoing Inter-RAT Handovers for Cell (Signalling Connection Release Indication) Number of Failed PS Outgoing Inter-RAT Handovers for Cell (No SRNS DATA Forward cmd) Number of PS Outgoing Inter-RAT Handover Attempts When only Signaling Exists for Cell
73423289
VS.SRVCC.U2GE RAN.SuccRelocPrepOutPS
V900R013
73423290
VS.SRVCC.U2GE RAN.SuccRelocOutPS
V900R013
73425007
VS.IRATHO.FailO utCS.SCRI
V900R014
73425008
VS.IRATHO.FailO utPSUTRAN.SCRI
V900R014
73425009
VS.IRATHO.FailO utPSUTRAN.NoSR NSDataForwardC md VS.IRATHO.AttO utPSUTRAN.Sig
V900R014
73425010
V900R014
Issue 01 (2013-05-04)
1438
Counter ID 73425011
Counter Name VS.IRATHO.Succ OutPSUTRAN.Sig
Counter Description Number of Successful PS Outgoing Inter-RAT Handovers When only Signaling Exists for Cell Number of Failed CS Outgoing Inter-RAT Handovers for Cell (Failure in the Radio Interface Procedure) Number of Failed PS Outgoing Inter-RAT Handovers for Cell (Failure in the Radio Interface Procedure) Number of RL Reestablishment Attempts After UEs Failed to Receive the CS Outgoing InterRAT Handover Command for Cell Number of RL Reestablishment Attempts After UEs Failed to Receive the PS Outgoing InterRAT Handover Command for Cell Number of Attempts to Obtain GSM System Information during RIM-based NACCs Triggered by Inter-RAT PS Handovers for Cell
73425012
VS.IRATHO.FailO utCS.InterRatRF
V900R014
73425013
VS.IRATHO.FailO utPSUTRAN.InterRatRF
V900R014
73425926
VS.IRATHOCS.Ca ncel.ReEstab
V900R015
73425927
VS.IRATHOPS.Ca ncel.ReEstab
V900R015
73425954
VS.IRATHO.AttNACC
V900R015
Issue 01 (2013-05-04)
1439
Counter ID 73425955
Counter Name VS.IRATHO.SuccNACC
Counter Description Number of Successful That GSM System Information Is Obtained during RIM-based NACCs Triggered by InterRAT PS Handovers for Cell Number of Attempts to Obtain GSM System Information During Iur-g-based ENACCs Triggered by Inter-RAT PS Handovers for Cell Number of Successful Times That GSM System Information is Obtained During Iurg-based ENACCs Triggered by InterRAT PS Handovers for Cell Number of Attempts at Incoming PS LTEto-UMTS Handovers Triggered by CSFB for Cell Number of Successful Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell Number of Successful Preparations for Incoming PS LTEto-UMTS Handovers Triggered by CSFB for Cell
73425956
VS.IRATHO.AttENACC
V900R015
73425957
VS.IRATHO.Succ ENACC
V900R015
73426146
VS.L2U.AttRelocP repInPS.CS.CELL
V900R015
73426147
VS.L2U.SuccReloc InPS.CS.CELL
V900R015
73426148
VS.L2U.SuccReloc PrepInPS.CS.CEL L
V900R015
Issue 01 (2013-05-04)
1440
Counter ID 73425820
Counter Name VS.SRVCC.L2U.At tRelocPrepInCSPS
Counter Description Number of Preparation Attempts for Incoming LTE-toUMTS CS+PS Handovers Triggered by SRVCC for VoIP Services for Cell Number of Successful Preparations for Incoming LTE-toUMTS CS+PS Handovers Triggered by SRVCC for VoIP Services for Cell Number of Incoming LTE-to-UMTS CS +PS Handover Attempts Triggered by SRVCC for VoIP Services for Cell Number of Successful Incoming LTE-to-UMTS CS +PS Handovers Triggered by SRVCC for VoIP Services for Cell
73425821
VS.SRVCC.L2U.S uccRelocPrepInCSPS
V900R015
73425822
VS.SRVCC.L2U.At tInCSPS
V900R015
73425823
VS.SRVCC.L2U.S uccInCSPS
V900R015
Counter IRATHO.SuccOutCS Sub Counter VS.IRATHO.SuccOutCS.DR VS.IRATHO.SuccOutCS.Load VS.IRATHO.SuccOutCS.RF VS.IRATHO.SuccOutCS.Service VS.IRATHO.SuccOutCS.MBDR IRATHO.AttRelocPrepOutCS VS.IRATHO.AttRelocPrepOutCS.DR VS.IRATHO.AttRelocPrepOutCS.Load VS.IRATHO.AttRelocPrepOutCS.RF VS.IRATHO.AttRelocPrepOutCS.Service
Counter IRATHO.SuccRelocPrepOutCS
Sub Counter VS.IRATHO.SuccRelocPrepOutCS.DR VS.IRATHO.SuccRelocPrepOutCS.Load VS.IRATHO.SuccRelocPrepOutCS.RF VS.IRATHO.SuccRelocPrepOutCS.Service
VS.IRATHO.AttOutPSUTRAN.Load VS.IRATHO.AttOutPSUTRAN.RF VS.IRATHO.AttOutPSUTRAN.Service
VS.IRATHO.SuccOutPSUTRAN.Load VS.IRATHO.SuccOutPSUTRAN.RF VS.IRATHO.SuccOutPSUTRAN.Service
VS.IRATHO.AttRelocPrepOutPS VS.IRATHO.SuccRelocPrepOutPS VS.IRATHO.SuccRelocOutPS
VS.SRVCC.U2GERAN.AttRelocPrepOutPS VS.SRVCC.U2GERAN.SuccRelocPrepOutPS VS.SRVCC.U2GERAN.SuccRelocOutPS
1.12.14.1 Number of Successful CS or Enhanced PS Outgoing Inter-RAT Handovers for Cell Counters
Counter ID 67189729 Counter Name VS.IRATHO.SuccOutCS.D R Counter Description Number of Successful CS Outgoing Inter-RAT Handovers Based on Directed Retry for Cell Number of Successful CS Outgoing Inter-RAT Handovers Based on Load for Cell Number of Successful CS Outgoing Inter-RAT Handovers Based on RF (Coverage, QoS, or HCS) for Cell Number of Successful CS Outgoing Inter-RAT Handovers for Cell
67189741
VS.IRATHO.SuccOutCS.L oad
67189746
VS.IRATHO.SuccOutCS.R F
67189755
IRATHO.SuccOutCS
Issue 01 (2013-05-04)
1442
Counter ID 67190857
Counter Name VS.IRATHO.SuccOutCS.Se rvice
Counter Description Number of Successful CS Outgoing Inter-RAT Handovers Based on Service Type for Cell Number of Successful CS Outgoing Inter-RAT Handovers When only Signaling Exists for Cell Number of Successful Enhanced PS Outgoing InterRAT Handovers for Cell Number of Successful CS Outgoing Inter-RAT Handovers Based on Measurement for Cell Number of Successful CS Inter-RAT Handovers Based on RSCP for Cell Number of Successful CS Inter-RAT Handovers Based on EcNo for Cell Number of Successful CS Inter-RAT Handovers Based on UL Transmit Power of UE for Cell Number of Successful CS Inter-RAT Handovers Based on DL Code Power for Cell
67192657
VS.IRATHO.SuccOutCS.Si g
67192665
VS.IRATHO.SuccRelocOutPS VS.IRATHO.SuccOutCS.M BDR
67196300
73393926
VS.IRATHO.SuccOutCS.Tr igRscp VS.IRATHO.SuccOutCS.Tr igEcNo VS.IRATHO.SuccOutCS.Tr igULTxp
73393927
73393928
73393929
VS.IRATHO.SuccOutCS.Tr igDLTxp
Description
These counters provide the number of successful CS or Enhanced PS outgoing inter-RAT handovers in the best cell. The counter VS.IRATHO.SuccOutCS.Load is measured when the version of the CN is Release 5 or later.
Measurement point
The measurement is triggered at point D as shown in the figure, when the RNC receives an IU RELEASE COMMAND message with the cause value of "Successful Relocation", "Normal Release" or "Network Optimization" after sending a HANDOVER FROM UTRAN COMMAND message during the CS or the Enhanced PS outgoing inter-RAT handover. In this case, the outgoing handover succeeds and these counters are measured in the best cell that the UE camps on.
Figure 1-643 Normal CS or the Enhanced PS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccOutCS.D R VS.IRATHO.SuccOutCS.L oad VS.IRATHO.SuccOutCS.R F Feature ID WRFD-02040002 WRFD-020306 WRFD-020303 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Load Inter-RAT Handover Based on Coverage
Issue 01 (2013-05-04)
1444
Counter Name IRATHO.SuccOutCS
Feature Name Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
VS.IRATHO.SuccOutCS.Se rvice VS.IRATHO.SuccOutCS.Si g
Inter-RAT Handover Based on Service Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
VS.IRATHO.SuccRelocOutPS VS.IRATHO.SuccOutCS.M BDR
WRFD-02030802 WRFD-02040002 WRFD-020402 WRFD-020303 WRFD-020303 WRFD-020309 WRFD-020309
PS Handover Between UMTS and GPRS Inter System Direct Retry Measurement Based Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on DL QoS Inter-RAT Handover Based on DL QoS
VS.IRATHO.SuccOutCS.Tr igRscp VS.IRATHO.SuccOutCS.Tr igEcNo VS.IRATHO.SuccOutCS.Tr igULTxp VS.IRATHO.SuccOutCS.Tr igDLTxp
1.12.14.2 Number of Preparations for CS or Enhanced PS Outgoing Inter-RAT Handover for Cell Counters
Counter ID 67189730 Counter Name VS.IRATHO.AttRelocPrep OutCS.DR Counter Description Number of Preparation Attempts for CS Outgoing Inter-RAT Handover Based on Directed Retry for Cell
1445
Issue 01 (2013-05-04)
Counter ID 67189739
Counter Name VS.IRATHO.AttRelocPrep OutCS.Load
Counter Description Number of Preparation Attempts for CS Outgoing Inter-RAT Handover Initiated by UTRAN Based on Load for Cell Number of Preparation Attempts for CS Outgoing Inter-RAT Handover Based on RF (Coverage, QoS, or HCS) for Cell Number of Preparation Attempts for CS Outgoing Inter-RAT Handover for Cell Number of Preparation Attempts for CS Outgoing Inter-RAT Handover Based on Service Type for Cell Number of Preparations for CS Outgoing Inter-RAT Handover When only Signaling Exists for Cell Number of Preparations for Enhanced PS Outgoing InterRAT Handover for Cell Number of CS Outgoing Inter-RAT Handover Attempts Based on Measurement for Cell
67189744
VS.IRATHO.AttRelocPrep OutCS.RF
67189749
IRATHO.AttRelocPrepOutCS VS.IRATHO.AttRelocPrep OutCS.Service
67190593
67192654
VS.IRATHO.AttRelocPrep OutCS.Sig
67192662
VS.IRATHO.AttRelocPrepOutPS VS.IRATHO.AttOutCS.MB DR
67196299
Description
These counters provide the number of preparation attempts for CS or Enhanced PS outgoing inter-RAT handover in the best cell. The counter VS.IRATHO.AttRelocPrepOutCS.Load is measured when the version of the CN is Release 5 or later.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends the CN a RELOCATION REQUIRED message during the CS or Enhanced PS outgoing inter-RAT handover. In this case, the corresponding counters are measured in the best cell that the UE camps on .
Issue 01 (2013-05-04)
1446
Figure 1-644 Normal CS or Enhanced PS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttRelocPrep OutCS.DR VS.IRATHO.AttRelocPrep OutCS.Load VS.IRATHO.AttRelocPrep OutCS.RF Feature ID WRFD-02040002 WRFD-020306 WRFD-020303 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Load Inter-RAT Handover Based on Coverage
Issue 01 (2013-05-04)
1447
Counter Name IRATHO.AttRelocPrepOutCS
VS.IRATHO.AttRelocPrep OutCS.Service VS.IRATHO.AttRelocPrep OutCS.Sig
VS.IRATHO.AttRelocPrepOutPS VS.IRATHO.AttOutCS.MB DR
WRFD-02030802 WRFD-02040002 WRFD-020402
PS Handover Between UMTS and GPRS Inter System Direct Retry Measurement Based Direct Retry
1.12.14.3 Number of Successful Preparations for CS or Enhanced PS Outgoing InterRAT Handover for Cell Counters
Counter ID 67189732 Counter Name VS.IRATHO.SuccRelocPre pOutCS.DR Counter Description Number of Successful Preparations for CS Outgoing Inter-RAT Handover Based on Directed Retry for Cell Number of Successful Preparations for CS Outgoing Inter-RAT Handover Initiated by UTRAN Based on Load for Cell
67189740
VS.IRATHO.SuccRelocPre pOutCS.Load
Issue 01 (2013-05-04)
1448
Counter ID 67189745
Counter Name VS.IRATHO.SuccRelocPre pOutCS.RF
Counter Description Number of Successful Preparations for CS Outgoing Inter-RAT Handover Based on RF (Coverage, QoS, or HCS) for Cell Number of Successful Preparations for CS Outgoing Inter-RAT Handover for Cell Number of Successful Preparations for CS Outgoing Inter-RAT Handover Based on Service Type for Cell Number of Successful Preparations for CS Outgoing Inter-RAT Handover When only Signaling Exists for Cell Number of Successful Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell
67189750
IRATHO.SuccRelocPrepOutCS
67190856
VS.IRATHO.SuccRelocPre pOutCS.Service
67192655
VS.IRATHO.SuccRelocPre pOutCS.Sig
67192663
VS.IRATHO.SuccRelocPrepOutPS
Description
These counters provide the number of successful preparations for CS or enhanced PS outgoing inter-RAT handover in the best cell. The counter VS.IRATHO.SuccRelocPrepOutCS.Load is measured when the version of the CN is Release 5 or later.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives from the CN a RELOCATION COMMAND message during CS or Enhanced PS outgoing inter-RAT handover. In this case, these counters are measured in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1449
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccRelocPre pOutCS.DR VS.IRATHO.SuccRelocPre pOutCS.Load VS.IRATHO.SuccRelocPre pOutCS.RF Feature ID WRFD-02040002 WRFD-020306 WRFD-020303 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Load Inter-RAT Handover Based on Coverage
Issue 01 (2013-05-04)
1450
Counter Name IRATHO.SuccRelocPrepOutCS
VS.IRATHO.SuccRelocPre pOutCS.Service VS.IRATHO.SuccRelocPre pOutCS.Sig
VS.IRATHO.SuccRelocPrepOutPS
WRFD-02030802
PS Handover Between UMTS and GPRS
1.12.14.4 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC for Cell Counters
Counter ID 67189742 Counter Name VS.IRATHO.AttOutPSUTR AN.Load Counter Description Number of PS Outgoing Inter-RAT Handover Attempts Initiated by UTRAN Based on Load for Cell Number of PS Outgoing Inter-RAT Handover Attempts Initiated by the RNC Based on RF (Coverage, QoS, or HCS) for Cell Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC for Cell
67189747
VS.IRATHO.AttOutPSUTR AN.RF
67190411
Issue 01 (2013-05-04)
1451
Counter ID 67190858
Counter Name VS.IRATHO.AttOutPSUTR AN.Service
Counter Description Number of PS Outgoing Inter-RAT Handover Attempts Initiated by the RNC Based on Service Type for Cell Number of PS Inter-RAT Outgoing Handover Attempts for HSDPA Services for Cell Number of PS Outgoing Inter-RAT Handover Attempts for HSUPA Services for Cell Number of PS Outgoing Inter-RAT Handover Attempts When only Signaling Exists for Cell
67191155
VS.IRATHO.HSDPA.AttOutPSUTRAN
67192507
VS.IRATHO.HSUPA.AttOutPSUTRAN
73425010
VS.IRATHO.AttOutPSUTR AN.Sig
Description
These counters provide the number of preparation attempts for PS outgoing inter-RAT handover in the best cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends to the UE a CELL CHANGE ORDER FROM UTRAN message during the PS outgoing inter-RAT handover. In this case, the corresponding counters are measured in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1452
Figure 1-646 Successful PS outgoing inter-RAT handover initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttOutPSUTR AN.Load VS.IRATHO.AttOutPSUTR AN.RF IRATHO.AttOutPSUTRAN Feature ID WRFD-020306 WRFD-020303 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Load Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load VS.IRATHO.AttOutPSUTR AN.Service
Issue 01 (2013-05-04)
WRFD-020305
Inter-RAT Handover Based on Service

1453
Counter Name VS.IRATHO.HSDPA.AttOutPSUTRAN VS.IRATHO.HSUPA.AttOutPSUTRAN VS.IRATHO.AttOutPSUTR AN.Sig
Feature Name HSDPA Mobility Management HSUPA Mobility Management Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.5 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by RNC for Cell Counters
Counter ID 67189743 Counter Name VS.IRATHO.SuccOutPSUT RAN.Load Counter Description Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UTRAN Based on Load for Cell Number of Successful PS Outgoing Inter-RAT Handovers Initiated by the RNC Based on RF (Coverage, QoS, or HCS) for Cell Number of Successful PS Outgoing Inter-RAT Handovers Initiated by RNC for Cell Number of Successful PS Outgoing Inter-RAT Handovers Initiated by the RNC Based on Service Type for Cell Number of Successful PS Outgoing Inter-RAT Handovers for HSDPA Services for Cell
67189748
VS.IRATHO.SuccOutPSUT RAN.RF
67190412
67190859
VS.IRATHO.SuccOutPSUT RAN.Service
67191156
VS.IRATHO.HSDPA.SuccOutPSUTRAN
Issue 01 (2013-05-04)
1454
Counter ID 67192506
Counter Name VS.IRATHO.HSUPA.SuccOutPSUTRAN
Counter Description Number of Successful PS Outgoing Inter-RAT Handovers for HSUPA Services for Cell Number of Successful PS Outgoing Inter-RAT Handovers When only Signaling Exists for Cell
73425011
VS.IRATHO.SuccOutPSUT RAN.Sig
Description
These counters provide the number of successful PS outgoing inter-RAT handovers in the best cell initiated by the RNC due to different causes.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC receives from the CN an IU RELEASE COMMAND message with the cause value of "Successful Relocation," "Normal Release," or "Network Optimization," after sending a CELL CHANGE ORDER FROM UTRAN message to the UE during an outgoing inter-RAT PS handover. In this case, the corresponding counter is measured in the best cell that the UE camps on in the SRNC before the handover based on the cause value. Figure 1-647 Successful PS outgoing inter-RAT handover initiated by the RNC
Issue 01 (2013-05-04)
1455
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccOutPSUT RAN.Load VS.IRATHO.SuccOutPSUT RAN.RF IRATHO.SuccOutPSUTRAN Feature ID WRFD-020306 WRFD-020303 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Load Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load VS.IRATHO.SuccOutPSUT RAN.Service VS.IRATHO.HSDPA.SuccOutPSUTRAN VS.IRATHO.HSUPA.SuccOutPSUTRAN VS.IRATHO.SuccOutPSUT RAN.Sig WRFD-020305 WRFD-01061006 WRFD-01061204 WRFD-020303 WRFD-020305 WRFD-020306 Inter-RAT Handover Based on Service HSDPA Mobility Management HSUPA Mobility Management Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.6 Number of Failed Preparations for CS or Enhanced PS Outgoing InterRAT Handover for Different Causes for Cell
Issue 01 (2013-05-04)
1456
Counters
Counter ID 67189751 Counter Name IRATHO.FailRelocPrepOut CS.TAlExp Counter Description Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (TRELOCalloc expiry) Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (Relocation Failure in Target CN/RNC or Target System) Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (Relocation not supported in Target RNC or Target system) Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (Traffic Load In The Target Cell Higher Than In The Source Cell) Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (No Resource Available) Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (Unknown Target RNC) Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (TRELOCalloc expiry)
67189752
IRATHO.FailRelocPrepOut CS.TgtFail
67189753
IRATHO.FailRelocPrepOut CS.ReloNoSup
67192186
IRATHO.FailRelocPrepOut CS.HigherTrafficLod
67192658
IRATHO.FailRelocPrepOut CS.NoResAvail
67192659
IRATHO.FailRelocPrepOut CS.UKnowRNC
67192666
VS.IRATHO.FailRelocPrep OutPS.TAlExp
Issue 01 (2013-05-04)
1457
Counter ID 67192667
Counter Name VS.IRATHO.FailRelocPrep OutPS.TgtFail
Counter Description Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (Relocation Failure in Target CN/RNC or Target System) Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (Relocation not supported in Target RNC or Target system) Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (Traffic Load In The Target Cell Higher Than In The Source Cell) Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (No Resource Available) Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (Unknown Target RNC) Number of Failed CS Outgoing Inter-RAT Handover Preparations for Cell (Relocation Cancelled) Number of Failed CS Outgoing Inter-RAT Handover Preparations for Cell (Requested Information Not Available)
67192668
VS.IRATHO.FailRelocPrep OutPS.ReloUnSupp
67192669
VS.IRATHO.FailRelocPrep OutPS.TgtHighLoad
67192670
VS.IRATHO.FailRelocPrep OutPS.NoResAvail
67192671
VS.IRATHO.FailRelocPrep OutPS.UnKnowRNC
73394015
VS.IRATHO.FailRelocPrep OutCS.Cancel
73394020
VS.IRATHO.FailRelocPrep OutCS.ReqInfoNotAvail
Description
These counters provide the number of failed preparations for CS or Enhanced PS outgoing interRAT handover in the best cell due to different causes.
Issue 01 (2013-05-04)
1458
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the CN a RELOCATION PREPARATION FAILURE message after sending the CN a RELOCATION REQUIRED message during the CS or the Enhanced PS outgoing inter-RAT handover. In this case, the corresponding counters are measured in the best cell that the UE camps on based on the cause value. Figure 1-648 Failed relocation preparation for SRNC
Formula
None
Unit
None
Issue 01 (2013-05-04)
1459
Related Features
Counter Name IRATHO.FailRelocPrepOut CS.TAlExp Feature ID WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load IRATHO.FailRelocPrepOut CS.TgtFail WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load IRATHO.FailRelocPrepOut CS.ReloNoSup WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load IRATHO.FailRelocPrepOut CS.HigherTrafficLod WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load IRATHO.FailRelocPrepOut CS.NoResAvail WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
Issue 01 (2013-05-04)
1460
Counter Name IRATHO.FailRelocPrepOut CS.UKnowRNC
VS.IRATHO.FailRelocPrep OutPS.TAlExp VS.IRATHO.FailRelocPrep OutPS.TgtFail VS.IRATHO.FailRelocPrep OutPS.ReloUnSupp VS.IRATHO.FailRelocPrep OutPS.TgtHighLoad VS.IRATHO.FailRelocPrep OutPS.NoResAvail VS.IRATHO.FailRelocPrep OutPS.UnKnowRNC VS.IRATHO.FailRelocPrep OutCS.Cancel
WRFD-02030802 WRFD-02030802 WRFD-02030802 WRFD-02030802 WRFD-02030802 WRFD-02030802 WRFD-020303 WRFD-020305 WRFD-020306
PS Handover Between UMTS and GPRS PS Handover Between UMTS and GPRS PS Handover Between UMTS and GPRS PS Handover Between UMTS and GPRS PS Handover Between UMTS and GPRS PS Handover Between UMTS and GPRS Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
VS.IRATHO.FailRelocPrep OutCS.ReqInfoNotAvail
WRFD-020303 WRFD-020305 WRFD-020306
Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.7 Number of CS or Enhanced PS Outgoing Inter-RAT Handover Attempts for Cell
Issue 01 (2013-05-04)
1461
Counters
Counter ID 67189754 Counter Name IRATHO.AttOutCS Counter Description Number of CS Outgoing Inter-RAT Handover Attempts Number of CS Outgoing Inter-RAT Handover Attempts When only Signaling Exists for Cell Number of Enhanced PS Outgoing Inter-RAT Handover Attempts for Cell Number of CS Inter-RAT Handover Attempts Based on RSCP for Cell Number of CS Inter-RAT Handover Attempts Based on EcNo for Cell Number of CS Inter-RAT Handover Attempts Based on UL Transmit Power of UE for Cell Number of CS Inter-RAT Handover Attempts Based on DL Code Power for Cell
67192656
VS.IRATHO.AttOutCS.Sig
67192664
VS.IRATHO.AttRelocOutPS VS.IRATHO.AttOutCS.Trig Rscp VS.IRATHO.AttOutCS.TrigEcNo VS.IRATHO.AttOutCS.TrigULTxp
67193405
67193406
73393922
73393923
VS.IRATHO.AttOutCS.Trig DLTxp
Description
These counters provide the number of CS or Enhanced PS outgoing inter-RAT handover attempts in the best cell.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends the UE a HANDOVER FROM UTRAN COMMAND message during the CS or Enhanced PS outgoing inter-RAT handover. In this case, these counters are measured in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1462
Formula
None
Unit
None
Related Features
Counter Name IRATHO.AttOutCS Feature ID WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load VS.IRATHO.AttOutCS.Sig WRFD-020303 WRFD-020305 WRFD-020306 Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
Counter Name VS.IRATHO.AttRelocOutPS VS.IRATHO.AttOutCS.Trig Rscp VS.IRATHO.AttOutCS.TrigEcNo VS.IRATHO.AttOutCS.TrigULTxp VS.IRATHO.AttOutCS.Trig DLTxp
Feature Name PS Handover Between UMTS and GPRS Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on DL QoS Inter-RAT Handover Based on DL QoS
1.12.14.8 Number of Failed CS or Enhanced PS Outgoing Inter-RAT Handovers for Different Causes for Cell Counters
Counter ID 67189756 Counter Name IRATHO.FailOutCS.CfgUn supp Counter Description Number of Failed CS Outgoing Inter-RAT Handovers for Cell (Configuration Unsupported) Number of Failed CS Outgoing Inter-RAT Handovers for Cell (Physical Channel Failure) Number of Failed Enhanced PS Outgoing Inter-RAT Handovers for Cell (Configuration Unsupported) Number of Failed Enhanced PS Outgoing Inter-RAT Handovers for Cell (Physical Channel Failure)
67189757
IRATHO.FailOutCS.PhyCh Fail
67192672
VS.IRATHO.FailRelocOutP S.CfgUnSupp
67192673
VS.IRATHO.FailRelocOutP S.PhyChFail
Description
These counters provide the number of failed CS or Enhanced PS outgoing inter-RAT handovers in the best cell due to different causes.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the UE a HANDOVER FROM UTRAN FAILURE message during the CS or the Enhanced PS outgoing inter-RAT handover. In this case, the corresponding counters are measured in the best cell that the UE camps on based on the handover cause. Figure 1-650 Failed CS or the Enhanced PS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name IRATHO.FailOutCS.CfgUn supp Feature ID WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
Counter Name IRATHO.FailOutCS.PhyCh Fail
VS.IRATHO.FailRelocOutP S.CfgUnSupp VS.IRATHO.FailRelocOutP S.PhyChFail
WRFD-02030802 WRFD-02030802
PS Handover Between UMTS and GPRS PS Handover Between UMTS and GPRS
1.12.14.9 Number of Preparations for CS or Enhanced PS Incoming Inter-RAT Handover for Cell Counters
Counter ID 67189758 Counter Name VS.IRATHO.AttRelocPrepInCS VS.IRATHO.AttRelocPrepInPS Counter Description Number of Preparations for CS Incoming Inter-RAT Handover for Cell Number of Preparations for Enhanced PS Incoming InterRAT Handover for Cell
67192675
Description
These counters provide the number of preparation attempts for CS or Enhanced PS incoming inter-RAT handovers according to the target cell ID in the relocation request.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the CN a RELOCATION REQUEST message during the CS or the Enhanced PS incoming interRAT handover. In this case, the preparation for CS or Enhanced PS incoming inter-RAT handover is triggered and these counters are measured according to the value of TargetCellId in the RELOCATION REQUEST message.
Issue 01 (2013-05-04)
1466
Figure 1-651 Normal CS or the Enhanced PS incoming inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttRelocPrepInCS Feature ID WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load VS.IRATHO.AttRelocPrepInPS WRFD-02030802 PS Handover Between UMTS and GPRS
Issue 01 (2013-05-04)
1467
1.12.14.10 Number of Successful CS or Enhanced PS Incoming Inter-RAT Handovers for Cell Counters
Counter ID 67189759 Counter Name VS.IRATHO.SuccInCS Counter Description Number of Successful CS Incoming Inter-RAT Handovers for Cell Number of Successful Enhanced PS Incoming InterRAT Handovers for Cell
67192677
VS.IRATHO.SuccRelocInPS
Description
These counters provide the number of successful CS or Enhanced PS incoming inter-RAT handovers in the RNC according to the target cell ID in the relocation request.
Measurement point
The measurement is triggered at point D as shown in the figure, when the RNC sends the CN a RELOCATION COMPLETE message during the CS or the Enhanced PS incoming inter-RAT handover. In this case, these counters are measured according to the value of TargetCellId in the RELOCATION REQUEST message. Figure 1-652 Normal CS or the Enhanced PS incoming inter-RAT handover
Issue 01 (2013-05-04)
1468
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccInCS Feature ID WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load VS.IRATHO.SuccRelocInPS WRFD-02030802 PS Handover Between UMTS and GPRS
1.12.14.11 Number of Failed Preparations for CS or Enhanced PS Incoming InterRAT Handover for Different Causes for Cell Counters
Counter ID 67189760 Counter Name VS.IRATHO.FailRelocPrep InCS.TRNCSysFailReloc Counter Description Number of Failed Preparations for CS Incoming Inter-RAT Handover (Relocation failure in target CN/RNC or target system) Number of Failed Preparations for CS Incoming Inter-RAT Handover (Relocation not supported in target RNC or target system) Number of Failed Preparations for CS Incoming Inter-RAT Handover (No resource available)
1469
67189761
VS.IRATHO.FailRelocPrep InCS.TRNCSysRelocUnsupp
67189762
VS.IRATHO.FailRelocPrep InCS.ResUnavail
Issue 01 (2013-05-04)
Counter ID 67192187
Counter Name VS.IRATHO.FailRelocPrep InCS.TgtHighLoad
Counter Description Number of Failed Preparations for CS Incoming Inter-RAT Handover (Traffic Load In The Target Cell Higher Than In The Source Cell) Number of Failed Preparations for Enhanced PS Incoming Inter-RAT Handover for cell (Relocation failure in target CN/RNC or target system) Number of Failed Preparations for Enhanced PS Incoming Inter-RAT Handover for cell (Relocation not supported in target RNC or target system) Number of Failed Preparations for Enhanced PS Incoming Inter-RAT Handover for cell (No resource available) Number of Failed Preparations for Enhanced PS Incoming Inter-RAT Handover for cell (Traffic Load In The Target Cell Higher Than In The Source Cell)
67192678
VS.IRATHO.FailRelocPrep InPS.TgtFail
67192679
VS.IRATHO.FailRelocPrep InPS.ReloUnSupp
67192680
VS.IRATHO.FailRelocPrep InPS.ResUnavail
67192681
VS.IRATHO.FailRelocPrep InPS.TgtHighLoad
Description
These counters provide the number of failed preparations for CS or Enhanced PS incoming interRAT handover due to different causes according to the target cell ID in the relocation request.
Measurement point
The measurement is triggered at point B as shown in the figure, when the TRNC sends the CN a RELOCATION FAILURE message during the CS or the Enhanced PS incoming inter-RAT handover. In this case, the corresponding counter is measured according to the value of TargetCellId in the RELOCATION REQUEST message.
Issue 01 (2013-05-04)
1470
Figure 1-653 Failed incoming inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailRelocPrep InCS.TRNCSysFailReloc Feature ID WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
Issue 01 (2013-05-04)
1471
Counter Name VS.IRATHO.FailRelocPrep InCS.TRNCSysRelocUnsupp
VS.IRATHO.FailRelocPrep InCS.ResUnavail
Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
VS.IRATHO.FailRelocPrep InCS.TgtHighLoad
Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
VS.IRATHO.FailRelocPrep InPS.TgtFail VS.IRATHO.FailRelocPrep InPS.ReloUnSupp VS.IRATHO.FailRelocPrep InPS.ResUnavail VS.IRATHO.FailRelocPrep InPS.TgtHighLoad
PS Handover Between UMTS and GPRS PS Handover Between UMTS and GPRS PS Handover Between UMTS and GPRS PS Handover Between UMTS and GPRS
1.12.14.12 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE for Cell Counters
Counter ID 67189763 Counter Name IRATHO.SuccOutPSUE Counter Description Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE for Cell
1472
Issue 01 (2013-05-04)
Description
This counter provides the number of successful PS outgoing inter-RAT handovers initiated by the UE. If the UE is in CELL_FACH, CELL_PCH, or URA_PCH state after setting up PS services in the WCDMA system, it can reselect a GPRS network based on the cell reselection criteria. After the UE reselects the GPRS network, it sets up PS services again. During the PS service setup, the 2.5G SGSN try to obtain from the RNC the context of the PS RAB set up by the UE in the WCDMA system by sending the SRNS CONTEXT REQUEST message to the SRNC.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives from the CN an IU RELEASE COMMAND message with the cause value of "Normal Release", "Successful Relocation" or "Network Optimization",during a PS inter-RAT outgoing handover. In this case, this counter is measured in the cell that the UE camps on before handover. Figure 1-654 PS outgoing inter-RAT handover initiated by the UE
Formula
None
Unit
None
Related Features
Counter Name IRATHO.SuccOutPSUE Feature ID WRFD-02030802 Feature Name PS Handover Between UMTS and GPRS
1.12.14.13 Number of Failed CS or Enhanced PS Inter-RAT Incoming Handovers Due to No Response from UE for Cell Counters
Counter ID 67190410 Counter Name VS.IRATHO.FailInCS.NoR eply Counter Description Number of Failed CS InterRAT Incoming Handovers Due to No Response from UE for Cell Number of Failed Enhanced PS Incoming Inter-RAT Handovers Due to UE Response Timeout for Cell
67192682
VS.IRATHO.FailRelocInPS .NoReply
Description
These counters provide the number of failed CS or Enhanced PS incoming inter-RAT handovers due to no response from the UE according to the target cell ID in the relocation request.
Measurement point
The measurement is triggered at point A as shown in the figure. During the CS or the Enhanced PS inter-RAT handover, after sending the RELOCATION REQUEST ACKNOWLEDGE message, the TRNC starts the timer waiting for the response message. If no response is received from the UE before the timer expires, the incoming inter-RAT handover fails and the corresponding counter is measured according to the value of TargetCellId in the RELOCATION REQUEST message.
Issue 01 (2013-05-04)
1474
Figure 1-655 Failed CS Inter-RAT Incoming Handovers
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailInCS.NoR eply Feature ID WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load VS.IRATHO.FailRelocInPS .NoReply WRFD-02030802 PS Handover Between UMTS and GPRS
1.12.14.14 Number of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC for Different Causes for Cell
Counters
Counter ID 67190476 Counter Name IRATHO.FailOutPSUTRA N.CfgUnsupp Counter Description Number of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC (Configuration unsupported) Number of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC (Physical Channel Failure) Number of Failed PS Outgoing Inter-RAT Handovers Initiated by the RNC for Cell
67190477
IRATHO.FailOutPSUTRA N.PhyChFail
73394021
VS.IRATHO.FailOutPS
Description
These counters provide the number of failed PS outgoing inter-RAT handovers in the best cell due to different causes.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the UE a CELL CHANGE ORDER FROM UTRAN FAILURE message after sending the CELL CHANGE ORDER FROM UTRAN message to the UE during the PS outgoing inter-RAT handover. In this case, the corresponding counter is measured in the best cell that the UE camps on based on the handover cause. Figure 1-656 Failed PS outgoing inter-RAT handover initiated by the RNC
Issue 01 (2013-05-04)
1476
Formula
None
Unit
None
Related Features
Counter Name IRATHO.FailOutPSUTRA N.CfgUnsupp Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load IRATHO.FailOutPSUTRA N.PhyChFail WRFD-020303 WRFD-020305 WRFD-020306 Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load VS.IRATHO.FailOutPS WRFD-020303 WRFD-020305 WRFD-020306 Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.15 Number of PS Outgoing Inter-RAT Handover Requests Initiated by UE for Cell Counters
Counter ID 67190413 Counter Name VS.IRATHO.AttOutPSUE Counter Description Number of PS Inter-RAT Outgoing Inter-RAT Handover Requests Initiated by UE for Cell
Issue 01 (2013-05-04)
1477
Description
This counter provides the number of PS outgoing inter-RAT handover requests initiated by the UE. If the UE is in CELL_FACH, CELL_PCH, or URA_PCH state after setting up PS services in the WCDMA system, it can reselect a GPRS network based on the cell reselection criteria. After the UE reselects the GPRS network, it sets up PS services again. During the PS service setup, the 2.5G SGSN try to obtain from the RNC the context of the PS RAB set up by the UE in the WCDMA system by sending the SRNS CONTEXT REQUEST message to the SRNC.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives the SRNS CONTEXT REQUEST message from the CN during a PS inter-RAT outgoing handover, the counter is measured in the best cell that the UE camps on before the handover. Figure 1-657 PS outgoing inter-RAT handover initiated by the UE
Formula
None
Unit
None
Issue 01 (2013-05-04)
1478
Related Features
Counter Name VS.IRATHO.AttOutPSUE Feature ID WRFD-02030802 Feature Name PS Handover Between UMTS and GPRS
1.12.14.16 Number of Successful Preparations for CS or Enhanced PS Incoming Inter-RAT Handover for Cell Counters
Counter ID 67190414 Counter Name VS.IRATHO.SuccRelocPrepInCS Counter Description Number of Successful preparations for CS Incoming Inter-RAT Handovers for Cell Number of Successful Preparations for Enhanced PS Incoming Inter-RAT Handover for Cell
67192676
VS.IRATHO.SuccRelocPrepInPS
Description
These counters provide the number of successful preparations for CS or Enhanced PS incoming inter-RAT handover in the RNC according to the target cell ID in the relocation request.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RELOCATION REQUEST ACKNOWLEDGE message during the CS or the Enhanced PS incoming inter-RAT handover. In this case, these counters are measured according to the value of TargetCellId in the RELOCATION REQUEST message.
Issue 01 (2013-05-04)
1479
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccRelocPrepInCS Feature ID WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load VS.IRATHO.SuccRelocPrepInPS WRFD-02030802 PS Handover Between UMTS and GPRS
Issue 01 (2013-05-04)
1480
1.12.14.17 Number of Times that the Timer Waiting for Iu Release Command Expires in CS or Enhanced PS Outgoing Inter-RAT Handover for Cell Counters
Counter ID 67192660 Counter Name VS.IRATHO.FailOutCS.No Reply Counter Description Number of Times that the Timer Waiting for Iu Release Command Expires in CS Outgoing Inter-RAT Handover for Cell Number of Times that the Timer Waiting for Iu Release Command Expires in Enhanced PS Outgoing InterRAT Handover for Cell
67192674
VS.IRATHO.FailRelocOutP S.NoReply
Description
These counters provide the number of times that the timer waiting for the Iu release command expires in the CS or the Enhanced PS outgoing inter-RAT handover in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. During the CS or the Enhanced PS outgoing inter-RAT handover, after sending the HANDOVER FROM UTRAN COMMAND message, the RNC starts the timer waiting for the IU RELEASE COMMAND message from the CN. If no message is received from the CN before the timer expires, these counters are measured in the best cell that the UE camps on before the handover.
Issue 01 (2013-05-04)
1481
Figure 1-659 Timeout Waiting for Iu Release Command in CS or the Enhanced PS Outgoing Inter-RAT Handover
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailOutCS.No Reply Feature ID WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load VS.IRATHO.FailRelocOutP S.NoReply WRFD-02030802 PS Handover Between UMTS and GPRS
Issue 01 (2013-05-04)
1482
1.12.14.18 Number of Times that the Timer Waiting for Iu Release Command Expires in PS Outgoing Inter-RAT Handover Initiated by RNC for Cell Counters
Counter ID 67192661 Counter Name VS.IRATHO.FailOutPSUT RAN.NoReply Counter Description Number of Times that the Timer Waiting for Iu Release Command Expires in PS Outgoing Inter-RAT Handover Initiated by RNC for Cell
Description
This counter provides the number of times that the timer waiting for the IU RELEASE COMMAND message expires in the PS outgoing inter-RAT handover initiated by the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure. During the PS outgoing interRAT handover, if the RNC receives no CELL CHANGE ORDER FROM UTRAN FAILURE message from the UE after sending the CELL CHANGE ORDER FROM UTRAN message and the timer waiting for the IU RELEASE COMMAND message from the CN expires, this counter is measured in the best cell that the UE camps on before handover. Figure 1-660 Timeout waiting for Iu Release Command in PS Outgoing Inter-RAT Handover Initiated by RNC
Issue 01 (2013-05-04)
1483
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailOutPSUT RAN.NoReply Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.19 Counters Related to the Number of Inter-RAT Measurement Expiry for Cell Counters
Counter ID 67193399 67193400 Counter Name VS.IRATHO.OutCS.MeasTimeOut VS.IRATHO.OutPS.MeasTimeOut Counter Description Number of CS Inter-RAT Measurement Expiry for Cell Number of PS Inter-RAT Measurement Expiry for Cell
Description
These counters provide the number of times that the timer for inter-RAT measurement expires before which no inter-RAT cell is detected and inter-RAT handover fails to start.
Measurement point
After the inter-RAT measurement is started, if no inter-RAT handover is performed before the timer for inter-RAT measurement expires, the inter-RAT measurement and compressed mode (if activated) are stopped. In this case, this counter is measured in the best cell.
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.OutCS.MeasTimeOut Feature ID WRFD-020303 WRFD-020309 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on DL QoS VS.IRATHO.OutPS.MeasTimeOut WRFD-020303 WRFD-020309 Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on DL QoS
1.12.14.20 Counters Related to the Number of PS Outgoing Inter-RAT Handover Attempts Counters
Counter ID 67193407 Counter Name VS.IRATHO.AttOutPS.Trig Rscp VS.IRATHO.AttOutPS.TrigEcNo VS.IRATHO.AttOutPS.TrigULTxp Counter Description Number of PS Inter-RAT Handover Attempts Based on RSCP for Cell Number of PS Inter-RAT Handover Attempts Based on EcNo for Cell Number of PS Inter-RAT Handover Attempts Based on UL Transmit Power of UE for Cell Number of PS Inter-RAT Handover Attempts Based on DL Code Power for Cell
67193408
73393924
73393925
VS.IRATHO.AttOutPS.Trig DLTxp
Description
These counters provide the number of PS outgoing inter-RAT handover attempts in the best cell due to different causes.
Measurement point
The measurement can be triggered at point B as shown in the figure, when the RNC sends the CELL CHANGE ORDER FROM UTRAN message during the PS outgoing inter-RAT
handover. In this case, the corresponding counter is measured in the best cell that the UE camps on under the SRNC, based on the handover cause. Figure 1-661 Handover instruction
The measurement can also be triggered at point C as shown in the figure, when the RNC sends the UE a HANDOVER FROM UTRAN COMMAND message during the enhanced PS outgoing inter-RAT handover. In this case, the corresponding counter is measured in the best cell that the UE camps on under the SRNC, based on the handover cause.
Issue 01 (2013-05-04)
1486
Figure 1-662 Handover instruction
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttOutPS.Trig Rscp VS.IRATHO.AttOutPS.TrigEcNo VS.IRATHO.AttOutPS.TrigULTxp VS.IRATHO.AttOutPS.Trig DLTxp Feature ID WRFD-020303 WRFD-020303 WRFD-020309 WRFD-020309 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on DL QoS Inter-RAT Handover Based on DL QoS
1.12.14.21 Counters Related to the Number of Successful PS Outgoing Inter-RAT Handovers

Counters
Counter ID 73393930 Counter Name VS.IRATHO.SuccOutPS.Tr igRscp VS.IRATHO.SuccOutPS.Tr igEcNo VS.IRATHO.SuccOutPS.Tr igULTxp Counter Description Number of Successful PS Inter-RAT Handovers Based on RSCP for Cell Number of Successful PS Inter-RAT Handovers Based on EcNo for Cell Number of Successful PS Inter-RAT Handovers Based on UL Transmit Power of UE for Cell Number of Successful PS Inter-RAT Handovers Based on DL Code Power for Cell
73393931
73393932
73393933
VS.IRATHO.SuccOutPS.Tr igDLTxp
Description
These counters provide the number of successful PS outgoing inter-RAT handovers in the best cell due to different causes.
Measurement point
The measurement can be triggered at point C as shown in the figure, when the RNC receives an IU RELEASE COMMAND message with the cause value of "Successful Relocation", "Normal Release", or "Network Optimization" during the PS outgoing inter-RAT handover. In this case, the handover succeeds and the corresponding counter is measured in the best cell that the UE camps on under the SRNC, based on the cause value.
Issue 01 (2013-05-04)
1488
Figure 1-663 Handover Indication 1
The measurement can also be triggered at point D as shown in the figure, when the RNC receives from the CN an IU RELEASE COMMAND message with the cause value of "Successful Relocation", "Normal Release", or "Network Optimization" during the PS outgoing inter-RAT handover. In this case, the handover succeeds and the corresponding counter is measured in the best cell that the UE camps on under the SRNC, based on the cause value. Figure 1-664 Handover Indication 2
Issue 01 (2013-05-04)
1489
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccOutPS.Tr igRscp VS.IRATHO.SuccOutPS.Tr igEcNo VS.IRATHO.SuccOutPS.Tr igULTxp VS.IRATHO.SuccOutPS.Tr igDLTxp Feature ID WRFD-020303 WRFD-020303 WRFD-020309 WRFD-020309 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on DL QoS Inter-RAT Handover Based on DL QoS
1.12.14.22 Number of CS Incoming Inter-RAT Handover Attempts for Cell Counters

Counter ID 73394014 Counter Name VS.IRATHO.AttInCS Counter Description Number of CS Incoming Inter-RAT Handover Attempts for Cell
Description
This counter provides the number of CS incoming inter-RAT handover attempts according to the target cell ID in the relocation request.
Measurement point
The measurement is triggered at point C as shown in the figure. After the RNC sends to the CN a RELOCATION REQUEST ACKNOWLEDGE message indicating that the CS inter-RAT handover preparation succeeds, this counter is measured according to the value of TargetCellId in the RELOCATION REQUEST message if the RNC receives a HANDOVER TO UTRAN COMPLETE message from the UE or a RADIO LINK RESTORE INDICATION message from the NodeB during the CS incoming inter-RAT handover. The measurement is triggered only once if both the messages are received.
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttInCS Feature ID WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.23 Number of Failed CS Outgoing Inter-RAT Handover Preparations (Relocation Command Wait Timeout) for Cell
Counters
Counter ID 73394016 Counter Name VS.IRATHO.FailRelocPrep OutCS.CNNoReply Counter Description Number of Failed CS Outgoing Inter-RAT Handover Preparations for Cell (Relocation Command Wait Timeout)
Description
This counter provides the number of times that the CS outgoing inter-RAT handover preparation fails in the best cell because the timer waiting for the relocation command expires.
Measurement point
The measurement is triggered at point A as shown in the figure. After sending the CN a RELOCATION REQUIRED message, the RNC starts the timer to wait for the RELOCATION COMMAND message. If no RELOCATION COMMAND message is received before the timer expires, the RNC sends a RELOCATION CANCEL message and measures this counter. Figure 1-666 SRNC relocation preparation failure due to expiry of relocation command
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailRelocPrep OutCS.CNNoReply Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.24 Number of CS Incoming Inter-RAT Handover Preparation Failures (Iu RELEASE COMMAND Received) for Cell Counters
Counter ID 73394017 Counter Name VS.IRATHO.FailRelocPrep InCS.Abort Counter Description Number of CS Incoming Inter-RAT Handover Preparation Failures for Cell (Iu RELEASE COMMAND Received)
Description
This counter provides the number of times that the CS incoming inter-RAT handover preparation fails because an IU RELEASE COMMAND message is received according to the target cell ID in the relocation request.
Measurement point
The measurement is triggered at point A as shown in the figure. After the CN sends a RELOCATION REQUEST message to the RNC during the CS incoming inter-RAT handover, this counter is measured according to the value of TargetCellId in the RELOCATION REQUEST message if the RNC receives an IU RELEASE COMMAND message.
Issue 01 (2013-05-04)
1493
Figure 1-667 CS domain inter-RAT incoming handover preparation
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailRelocPrep InCS.Abort Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.25 Number of Abnormally Terminated CS Outgoing Inter-RAT Handovers for Cell
Issue 01 (2013-05-04)
1494
Counters
Counter ID 73394018 Counter Name VS.IRATHO.FailOutCS.Ab ort Counter Description Number of Abnormally Terminated CS Outgoing Inter-RAT Handovers for Cell
Description
This counter provides the number of times that the CS outgoing inter-RAT handover fails in the best cell because an IU RELEASE COMMAND message with a cause value of abnormal release, that is, a cause value except "Successful Relocation", "Normal Release", or "Network Optimization", is received.
Measurement point
The measurement is triggered at point D as shown in the figure, when the RNC receives an IU RELEASE COMMAND message with the cause value except "Successful Relocation", "Normal Release" or "Network Optimization" after sending a HANDOVER FROM UTRAN COMMAND message. In this case, this counter is measured in the SRNC best cell that the UE camps on before the handover. Figure 1-668 CS domain inter-RAT outgoing handover procedure
Issue 01 (2013-05-04)
1495
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailOutCS.Ab ort Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.26 Number of CS Outgoing Inter-RAT Handover Preparation Failures (Iu RELEASE COMMAND Received) for Cell Counters
Counter ID 73394019 Counter Name VS.IRATHO.FailRelocPrep OutCS.Abort Counter Description Number of CS Outgoing Inter-RAT Handover Preparation Failures for Cell (Iu RELEASE COMMAND Received)
Description
This counter provides the number of times that the CS outgoing inter-RAT handover preparation fails in the best cell because an IU RELEASE COMMAND message is received.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives an IU RELEASE COMMAND command after sending the CN a RELOCATION REQUIRED message during the CS outgoing inter-RAT handover.
Issue 01 (2013-05-04)
1496
Figure 1-669 RNC-initiated CS domain inter-RAT outgoing handover procedure (failed operation due to termination)
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailRelocPrep OutCS.Abort Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.27 Number of Abnormally Terminated PS Outgoing Inter-RAT Handovers for Cell
Issue 01 (2013-05-04)
1497
Counters
Counter ID 73394022 Counter Name VS.IRATHO.FailOutPS.Ab ort Counter Description Number of Abnormally Terminated PS Outgoing Inter-RAT Handovers for Cell
Description
This counter provides the number of times that the PS outgoing inter-RAT handover fails in the best cell because an IU RELEASE COMMON message with a cause value of abnormal release, that is, a cause value except "Successful Relocation", "Normal Release", or "Network Optimization", is received.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC receives an IU RELEASE COMMAND message in the PS domain with the cause value except "Successful Relocation", "Normal Release" or "Network Optimization" after sending a CELL CHANGE ORDER FORM UTRAN message. In this case, this counter is measured in the SRNC best cell that the UE camps on before the handover. Figure 1-670 PS domain inter-RAT outgoing handover procedure
Issue 01 (2013-05-04)
1498
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailOutPS.Ab ort Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.28 Number of Failed Outgoing UMTS-to-GSM PS Handovers due to UE Reselection Back to a UTRAN Cell Counters
Counter ID 73423107 Counter Name VS.IRATHO.FailOutPS.UE Gen Counter Description Number of Failed Outgoing UMTS-to-GSM PS Handovers due to UE Reselection Back to a UTRAN Cell
Description
This counter provides the number of times that a UE reselects a 3G cell and sends an RRC connection setup request or receive IU RELEASE COMMAND with cause of Release due to UE generated signalling connection release during the UMTS-to-GSM PS handover. This counter indicates that the UE accesses the UTRAN again during the UMTS-to-GSM PS handover. If a large proportion of inter-RAT handovers fail due to this reason, view the interRAT reselection parameters at the GSM and the handover parameters to check whether pingpong handovers exist.
Measurement point
The measurement is triggered at point A as shown in the following figure. After the RNC sends the UE a CELL CHANGE ORDER FROM UTRAN message, instructing the UE to hand over to a 2G cell, this counter is measured in the best cell that the UE camps on before the handover if the UE reselects a 3G cell and sends an RRC connection setup request before the RNC receives
from the CN an IU RELEASE COMMAND message or if the RNC receives from the CN an IU RELEASE COMMAND message with the cause value of "UE generated signaling connection release". Figure 1-671 inter-RAT handovers abnormal procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailOutPS.UE Gen Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
Issue 01 (2013-05-04)
1500
1.12.14.29 Number of Outgoing Inter-RAT PS Handover Preparation Attempts Triggered by SRVCC for VoIP Services for Cell Counters
Counter ID 73423288 Counter Name VS.SRVCC.U2GERAN.AttRelocPrepOutPS Counter Description Number of Outgoing InterRAT PS Handover Preparation Attempts Triggered by SRVCC for VoIP Services for Cell
Description
This counter provides the number of outgoing inter-RAT PS handover preparation attempts triggered by Single Radio Voice Call Continuity (SRVCC) for VoIP services in the best cell that the UE camps on. After SRVCC is enabled, a VoIP service carried on HSPA is processed as a PS service at the UTRAN and as a CS service at the GERAN during the UTRAN-to-GERAN handover to ensure the speech continuity.
Measurement point
The measurement is triggered at point A shown in the figure. When the RNC sends the CN a RELOCATION REQUIRED message during the SRVCC-triggered inter-RAT PS handover for a VoIP service, this counter is measured in the best cell that the UE camps on. Figure 1-672 VS.SRVCC.U2GERAN.AttRelocPrepOutPS
Issue 01 (2013-05-04)
1501
Formula
None
Unit
None
Related Features
Counter Name VS.SRVCC.U2GERAN.AttRelocPrepOutPS Feature ID WRFD-02030802 Feature Name PS Handover Between UMTS and GPRS
1.12.14.30 Number of Successful Outgoing Inter-RAT PS Handover Preparations Triggered by SRVCC for VoIP Services for Cell Counters
Counter ID 73423289 Counter Name VS.SRVCC.U2GERAN.Suc cRelocPrepOutPS Counter Description Number of Successful Outgoing Inter-RAT PS Handover Preparations Triggered by SRVCC for VoIP Services for Cell
Description
This counter provides the number of successful outgoing inter-RAT PS handover preparations triggered by Single Radio Voice Call Continuity (SRVCC) for VoIP services in the best cell that the UE camps on. After SRVCC is enabled, a VoIP service carried on HSPA is processed as a PS service at the UTRAN and as a CS service at the GERAN during the UTRAN-to-GERAN handover to ensure the speech continuity.
Measurement point
The measurement is triggered at point B shown in the figure. When the RNC receives from the CN a RELOCATION COMMAND message during the SRVCC-triggered inter-RAT PS handover for a VoIP service, this counter is measured in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1502
Figure 1-673 VS.SRVCC.U2GERAN.SuccRelocPrepOutPS
Formula
None
Unit
None
Related Features
Counter Name VS.SRVCC.U2GERAN.Suc cRelocPrepOutPS Feature ID WRFD-02030802 Feature Name PS Handover Between UMTS and GPRS
1.12.14.31 Number of Successful Outgoing Inter-RAT PS Handovers Triggered by SRVCC for VoIP Services for Cell
Issue 01 (2013-05-04)
1503
Counters
Counter ID 73423290 Counter Name VS.SRVCC.U2GERAN.Suc cRelocOutPS Counter Description Number of Successful Outgoing Inter-RAT PS Handovers Triggered by SRVCC for VoIP Services for Cell
Description
This counter provides the number of successful outgoing inter-RAT PS handovers triggered by Single Radio Voice Call Continuity (SRVCC) for VoIP services in the best cell that the UE camps on. After SRVCC is enabled, a VoIP service carried on HSPA is processed as a PS service at the UTRAN and as a CS service at the GERAN during the UTRAN-to-GERAN handover to ensure the speech continuity.
Measurement point
The measurement is triggered at point D shown in the figure. When the RNC receives an IU RELEASE COMMAND message with the cause value of "Successful Relocation", "Normal Release" or "Network Optimization" after sending a HANDOVER FROM UTRAN COMMAND message during the SRVCC-triggered inter-RAT PS handover for a VoIP service, the handover succeeds and this counter is measured in the best cell that the UE camps on under the SRNC before the handover. Figure 1-674 VS.SRVCC.U2GERAN.SuccRelocOutPS
Issue 01 (2013-05-04)
1504
Formula
None
Unit
None
Related Features
Counter Name VS.SRVCC.U2GERAN.Suc cRelocOutPS Feature ID WRFD-02030802 Feature Name PS Handover Between UMTS and GPRS
1.12.14.32 Number of Failed CS Outgoing Inter-RAT Handovers for Cell(Signalling Connection Release Indication) Counters
Counter ID 73425007 Counter Name VS.IRATHO.FailOutCS.SC RI Counter Description Number of Failed CS Outgoing Inter-RAT Handovers for Cell (Signalling Connection Release Indication)
Description
This counter provides the number of the CS outgoing inter-RAT handover fails in the best cell because the RNC receives SIGNALLING CONNECTION RELEASE INDICATION from the UE.
Measurement point
The measurement is triggered at point A as shown in the figure.During the CS outgoing interRAT handover, if the RNC receives a SIGNALLING CONNECTION RELEASE INDICATION message after sending the HANDOVER FROM UTRAN COMMAND message.In this case, this counter is increased by one in the best cell that the UE camps on before the handover.
Issue 01 (2013-05-04)
1505
Figure 1-675 Procedure for a failed outgoing inter-RAT handover in the CS domain
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailOutCS.SC RI Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.33 Number of Failed PS Outgoing Inter-RAT Handovers for Cell(Signalling Connection Release Indication)
Issue 01 (2013-05-04)
1506
Counters
Counter ID 73425008 Counter Name VS.IRATHO.FailOutPSUT RAN.SCRI Counter Description Number of Failed PS Outgoing Inter-RAT Handovers for Cell (Signalling Connection Release Indication)
Description
This counter provides the number of the CS outgoing inter-RAT handover fails in the best cell because the RNC receives SIGNALLING CONNECTION RELEASE INDICATION from the UE.
Measurement point
The measurement is triggered at point A as shown in the figure.During the PS outgoing interRAT handover, if the RNC receives a SIGNALLING CONNECTION RELEASE INDICATION message after sending the CELL CHANGE ORDER FROM UTRAN message.In this case, this counter is increased by one in the best cell that the UE camps on before the handover. Figure 1-676 Procedure for a failed outgoing inter-RAT handover in the PS domain
Issue 01 (2013-05-04)
1507
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailOutPSUT RAN.SCRI Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.34 Number of Failed PS Outgoing Inter-RAT Handovers for Cell(No SRNS DATA Forward cmd) Counters
Counter ID 73425009 Counter Name VS.IRATHO.FailOutPSUT RAN.NoSRNSDataForwardCmd Counter Description Number of Failed PS Outgoing Inter-RAT Handovers for Cell(No SRNS DATA Forward cmd)
Description
This counter provides the number of the PS outgoing inter-RAT handover fails in the best cell because the timer waiting for the SRNS DATA FORWARD COMMAND message from CN expires.
Measurement point
The measurement is triggered at point A as shown in the figure.If an SRNS context forwarding procedure is triggered in a PS inter-RAT handover and no SRNS DATA FORWARD COMMAND message is received, this counter is increased by one in the best cell before the handover.
Issue 01 (2013-05-04)
1508
Figure 1-677 Procedure for a failed outgoing inter-RAT handover in the PS domain
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailOutPSUT RAN.NoSRNSDataForwardCmd Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.35 Number of Failed CS Outgoing Inter-RAT Handovers for Cell(Failure in the Radio Interface Procedure)
Issue 01 (2013-05-04)
1509
Counters
Counter ID 73425012 Counter Name VS.IRATHO.FailOutCS.InterRatRF Counter Description Number of Failed CS Outgoing Inter-RAT Handovers for Cell(Failure in the Radio Interface Procedure)
Description
This counter provides the number of IU RELEASE COMMAND messages that are received by the RNC from the CN after the RNC sends HANDOVER FROM UTRAN COMMAND messages to the UE and that contain the reason value "Failure in the Radio Interface Procedure." This counter is measured in a CS inter-RAT handover and in the best cell before the handover.
Measurement point
The measurement is triggered at point D as shown in the figure.When the RNC receives a IU RELEASE COMMAND message,If the IU RELEASE COMMAND message indicate the reason"Failure in the Radio Interface Procedure",this counter is increased by one in the best cell that the UE camps on before the handover. Figure 1-678 Procedure for an outgoing inter-RAT handover in the CS domain
Issue 01 (2013-05-04)
1510
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailOutCS.InterRatRF Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.36 Number of Failed PS Outgoing Inter-RAT Handovers for Cell(Failure in the Radio Interface Procedure) Counters
Counter ID 73425013 Counter Name VS.IRATHO.FailOutPSUT RAN.InterRatRF Counter Description Number of Failed PS Outgoing Inter-RAT Handovers for Cell(Failure in the Radio Interface Procedure)
Description
This counter provides the number of IU RELEASE COMMAND messages that are received by the RNC from the CN after the RNC sends CELL CHANGE ORDER FROM UTRAN messages to the UE and that contain the reason value "Failure in the Radio Interface Procedure." This counter is measured in a PS inter-RAT handover and in the best cell before the handover.
Measurement point
The measurement is triggered at point C as shown in the figure.When the RNC receives a IU RELEASE COMMAND message,If the IU RELEASE COMMAND message indicate the reason"Failure in the Radio Interface Procedure",this counter is increased by one in the best cell that the UE camps on before the handover.
Issue 01 (2013-05-04)
1511
Figure 1-679 Procedure for an outgoing inter-RAT handover in the PS domain
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailOutPSUT RAN.InterRatRF Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.14.37 Number of RL Reestablishment Attempts After UEs Failed to Receive the CS Outgoing Inter-RAT Handover Command for Cell
Issue 01 (2013-05-04)
1512
Counters
Counter ID 73425926 Counter Name VS.IRATHOCS.Cancel.ReEstab Counter Description Number of RL Reestablishment Attempts After UEs Failed to Receive the CS Outgoing Inter-RAT Handover Command for Cell
Description
This counter measures the number of radio link (RL) reestablishment attempts in the best cell when a UE fails to receive a HANDOVER FROM UTRAN COMMAND message from the RNC during a CS outgoing inter-RAT handover.
Measurement point
The measurement is triggered at point A shown in the figure when both of the following conditions are met: The RNC has sent a HANDOVER FROM UTRAN COMMAND message to the UE, but fails to receive an ACK message from the UE. The RNC receives a CELL UPDATE message from the UE and attempts to reestablish the RL for the UE. In this case, the counter is measured in the best cell that the UE camps on under the SRNC. Figure 1-680 RL reestablishment during a CS or enhanced PS outgoing inter-RAT handover
Issue 01 (2013-05-04)
1513
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHOCS.Cancel.ReEstab Feature ID WRFD-020303 WRFD-020306 WRFD-020305 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Load Inter-RAT Handover Based on Service
1.12.14.38 Number of RL Reestablishment Attempts After UEs Failed to Receive the PS Outgoing Inter-RAT Handover Command for Cell Counters
Counter ID 73425927 Counter Name VS.IRATHOPS.Cancel.ReEstab Counter Description Number of RL Reestablishment Attempts After UEs Failed to Receive the PS Outgoing Inter-RAT Handover Command for Cell
Description
This counter measures the number of RL reestablishment attempts in the best cell after a UE fails to receive a CELL CHANGE ORDER FROM UTRAN message or a HANDOVER FROM UTRAN COMMAND message from the RNC during a PS outgoing inter-RAT handover.
Measurement point
The measurement is triggered at point A shown in the figure when both of the following conditions are met: The RNC has sent a CELL CHANGE ORDER FROM UTRAN message to the UE, but fails to receive an ACK message from the UE. The RNC receives a CELL UPDATE message from the UE and attempts to reestablish the RL for the UE. In this case, the counter is measured in the best cell that the UE camps on under the SRNC.
Figure 1-681 RL reestablishment during a PS outgoing inter-RAT handover
The measurement is triggered at point A shown in the figure when both of the following conditions are met: The RNC has sent a HANDOVER FROM UTRAN COMMAND message to the UE, but fails to receive an ACK message from the UE. The RNC receives a CELL UPDATE message from the UE and attempts to reestablish the RL for the UE. In this case, the counter is measured in the best cell that the UE camps on under the SRNC. Figure 1-682 RL reestablishment during a CS or enhanced PS outgoing inter-RAT handover
Issue 01 (2013-05-04)
1515
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHOPS.Cancel.ReEstab Feature ID WRFD-020303 WRFD-020306 WRFD-020305 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Load Inter-RAT Handover Based on Service
1.12.14.39 Number of Attempts to Obtain GSM System Information During RIMbased NACCs Triggered by Inter-RAT PS Handovers Counters
Counter ID 73425954 Counter Name VS.IRATHO.AttNACC Counter Description Number of Attempts to Obtain GSM System Information during RIMbased NACCs Triggered by Inter-RAT PS Handovers for Cell
Description
This counter provides the number of attempts to obtain GSM system information during RIMbased NACCs triggered by Inter-RAT PS handovers in the best cell where the UE camps. RIM is short for RAN information management and NACC is short for network assisted cell change.
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC sends the CN a DIRECT INFORMATION TRANSFER message which contains RAN INFORMATION REQUEST to initiate inter-RAT PS handovers. This counter is measured in the best cell under the SRNC where the UE is currently served.
Figure 1-683 Procedure for directly sending messages over the Iu interface
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttNACC Feature ID WRFD-02030801 Feature Name NACC(Network Assisted Cell Change)
1.12.14.40 Number of Successful That GSM System Information Is Obtained During RIM-based NACCs Triggered by Inter-RAT PS Handovers Counters
Counter ID 73425955 Counter Name VS.IRATHO.SuccNACC Counter Description Number of Successful That GSM System Information Is Obtained during RIM-based NACCs Triggered by InterRAT PS Handovers for Cell
Issue 01 (2013-05-04)
1517
Description
This counter provides the number of times that GSM system information is successfully obtained during RIM-based NACCs triggered by Inter-RAT PS handovers to obtain GSM system information in the best cell where the UE camps. RIM is short for RAN information management and NACC is short for network assisted cell change.
Measurement point
The measurement is triggered at point B shown in the following figure. After receiving a DIRECT INFORMATION TRANSFER message containing RAN INFORMATION from the CN, the RNC initiates inter-RAT PS handovers. This counter is measured in the best cell under the SRNC where the UE is currently served. Figure 1-684 Procedure for directly sending messages over the Iu interface
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccNACC Feature ID WRFD-02030801 Feature Name NACC(Network Assisted Cell Change)
Issue 01 (2013-05-04)
1518
1.12.14.41 Number of Attempts to Obtain GSM System Information During Iur-gbased ENACCs Triggered by Inter-RAT PS Handovers Counters
Counter ID 73425956 Counter Name VS.IRATHO.AttENACC Counter Description Number of Attempts to Obtain GSM System Information During Iur-gbased ENACCs Triggered by Inter-RAT PS Handovers for Cell
Description
This counter provides the number of attempts to obtain GSM system information during Iur-gbased ENACCs triggered by Inter-RAT PS handovers in the best cell where the UE camps. ENACC is short for evolved network assisted cell change.
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC sends the BSC an INFORMATION EXCHANGE INITIATION REQUEST message which contains NACC Related Data. This counter is measured in the best cell under the SRNC where the UE is served. Figure 1-685
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttENACC Feature ID WRFD-070005 Feature Name NACC Procedure Optimization Based on Iur-g
1.12.14.42 Number of Successful Times That GSM System Information Is Obtained During Iur-g-based ENACCs Triggered by Inter-RAT PS Handovers Counters
Counter ID 73425957 Counter Name VS.IRATHO.SuccENACC Counter Description Number of Successful Times That GSM System Information is Obtained During Iur-g-based ENACCs Triggered by Inter-RAT PS Handovers for Cell
Description
This counter provides the number of successful times that GSM system information is obtained during Iur-g-based ENACCs triggered by Inter-RAT PS handovers in the best cell where the UE camps. ENACC is short for evolved network assisted cell change.
Measurement point
The measurement is triggered at point B shown in the following figure when the RNC receives an INFORMATION EXCHANGE INITIATION REQUEST message which contains NACC Related Data from the BSC. This counter is measured in the best cell under the SRNC where the UE is served.
Issue 01 (2013-05-04)
1520
Figure 1-686
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccENACC Feature ID WRFD-070005 Feature Name NACC Procedure Optimization Based on Iur-g
1.12.14.43 Number of Attempts at Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell Counters
Counter ID 73426146 Counter Name VS.L2U.AttRelocPrepInPS. CS.CELL Counter Description Number of Attempts at Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell
Issue 01 (2013-05-04)
1521
Description
This counter provides the number of attempts at incoming PS L2U handovers triggered by CSFB in the cell that is specified by the related RELOCATION REQUEST message.
Measurement point
When the RNC receives a RELOCATION REQUEST message from the CN, this counter is increased by one in the cell that is specified by the TargetCellId IE in the message if the "Source RNC To Target RNC Transparent Container" IE in the RELOCATION REQUEST message carries a CSFB flag or the Cause IE in the message is set to "CS Fallback triggered." The measurement is triggered at point A, as shown in the following figure. Figure 1-687
Formula
None
Unit
None
Related Features
Counter Name VS.L2U.AttRelocPrepInPS. CS.CELL
Issue 01 (2013-05-04)
Feature Name CS Fallback Guarantee for LTE Emergency Calls

1522
1.12.14.44 Number of Successful Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell Counters
Counter ID 73426147 Counter Name VS.L2U.SuccRelocInPS.CS. CELL Counter Description Number of Successful Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell
Description
This counter provides the number of successful incoming PS L2U handovers triggered by CSFB in the cell that is specified by the related RELOCATION REQUEST message.
Measurement point
When the RNC sends the CN a RELOCATION COMPLETE message, this counter is increased by one in the cell that is specified by the TargetCellId IE in the corresponding RELOCATION REQUEST message if the "Source RNC To Target RNC Transparent Container" IE in the RELOCATION REQUEST message carries a CSFB flag or the Cause IE in the message is set to "CS Fallback triggered." The measurement is triggered at point D, as shown in the following figure. Figure 1-688
Issue 01 (2013-05-04)
1523
Formula
None
Unit
None
Related Features
Counter Name VS.L2U.SuccRelocInPS.CS. CELL Feature ID WRFD-140102 Feature Name CS Fallback Guarantee for LTE Emergency Calls
1.12.14.45 Number of Successful Preparations for Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell Counters
Counter ID 73426148 Counter Name VS.L2U.SuccRelocPrepInP S.CS.CELL Counter Description Number of Successful Preparations for Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell
Description
This counter provides the number of successful preparations for incoming PS L2U handovers triggered by CSFB in the cell that is specified in the related RELOCATION REQUEST message.
Measurement point
When the RNC sends the CN a RELOCATION REQUEST ACKNOWLEDGE message, this counter is increased by one in the cell that is specified by the TargetCellId IE in the corresponding RELOCATION REQUEST message if the "Source RNC To Target RNC Transparent Container" IE in the RELOCATION REQUEST message carries a CSFB flag or the Cause IE in the message is set to "CS Fallback triggered." The measurement is triggered at point B, as shown in the following figure.
Issue 01 (2013-05-04)
1524
Figure 1-689
Formula
None
Unit
None
Related Features
Counter Name VS.L2U.SuccRelocPrepInP S.CS.CELL Feature ID WRFD-140102 Feature Name CS Fallback Guarantee for LTE Emergency Calls
1.12.14.46 Number of Preparation Attempts for Incoming LTE-to-UMTS CS+PS Handovers Triggered by SRVCC for VoIP Services
Issue 01 (2013-05-04)
1525
Counters
Counter ID 73425820 Counter Name VS.SRVCC.L2U.AttRelocPrepInCSPS Counter Description Number of Preparation Attempts for Incoming LTEto-UMTS CS+PS Handovers Triggered by SRVCC for VoIP Services for Cell
Description
This counter provides the number of preparation attempts for incoming L2U CS+PS handovers triggered by Single Radio Voice Call Continuity (SRVCC) with PS Handover for VoIP services. This counter is measured according to the target cell ID in the RELOCATION REQUEST message. L2U refers to handovers from the LTE network to the UMTS network. With the SRVCC with PS Handover feature, the VoIP and PS services in an LTE network are handed over to the CS and PS domains of the UMTS network, respectively. As a result, speech continuity is ensured during the handover. On the RNC side, this process is an incoming inter-RAT CS+PS handover. RAT is short for radio access technology.
Measurement point
The measurement is triggered at point A shown in the following figure. After confirming that the two RELOCATION REQUEST messages from the CN are incoming CS+PS handover requests from an LTE cell, the RNC triggers the incoming inter-RAT CS+PS handover preparation procedure. This counter is measured according to the target cell ID in the two RELOCATION REQUEST messages.
Issue 01 (2013-05-04)
1526
Figure 1-690 Procedure of SRVCC inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name VS.SRVCC.L2U.AttRelocPrepInCSPS Feature ID WRFD-150215 Feature Name SRVCC from LTE to UMTS with PS Handover
Issue 01 (2013-05-04)
1527
1.12.14.47 Number of Successful Preparations for Incoming LTE-to-UMTS CS+PS Handovers Triggered by SRVCC for VoIP Services Counters
Counter ID 73425821 Counter Name VS.SRVCC.L2U.SuccRelocPrepInCSPS Counter Description Number of Successful Preparations for Incoming LTE-to-UMTS CS+PS Handovers Triggered by SRVCC for VoIP Services for Cell
Description
This counter provides the number of successful preparations for incoming L2U CS+PS handovers triggered by Single Radio Voice Call Continuity (SRVCC) with PS Handover for VoIP services. This counter is measured according to the target cell ID in the RELOCATION REQUEST message. L2U refers to handovers from the LTE network to the UMTS network. With the SRVCC with PS Handover feature, the VoIP and PS services in an LTE network are handed over to the CS and PS domains of the UMTS network, respectively. As a result, speech continuity is ensured during the handover. On the RNC side, this process is an incoming interRAT CS+PS handover. RAT is short for radio access technology.
Measurement point
The measurement is triggered at point B shown in the following figure. When the RNC sends two RELOCATION REQUEST ACKNOWLEDGE messages to the CN, this counter is measured according to the target cell ID in the two RELOCATION REQUEST messages.
Issue 01 (2013-05-04)
1528
Formula
None
Unit
None
Related Features
Counter Name VS.SRVCC.L2U.SuccRelocPrepInCSPS Feature ID WRFD-150215 Feature Name SRVCC from LTE to UMTS with PS Handover
Issue 01 (2013-05-04)
1529
1.12.14.48 Number of Incoming LTE-to-UMTS CS+PS Handover Attempts Triggered by SRVCC for VoIP Services Counters
Counter ID 73425822 Counter Name VS.SRVCC.L2U.AttInCSPS Counter Description Number of Incoming LTEto-UMTS CS+PS Handover Attempts Triggered by SRVCC for VoIP Services for Cell
Description
This counter provides the number of incoming L2U CS+PS handover attempts triggered by Single Radio Voice Call Continuity (SRVCC) with PS Handover for VoIP services. This counter is measured according to the target cell ID in the RELOCATION REQUEST message. L2U refers to handovers from the LTE network to the UMTS network. With the SRVCC with PS Handover feature, the VoIP and PS services in an LTE network are handed over to the CS and PS domains of the UMTS network, respectively. As a result, speech continuity is ensured during the handover. On the RNC side, this process is an incoming inter-RAT CS+PS handover. RAT is short for radio access technology.
Measurement point
The measurement is triggered at point C shown in the following figure. After the RNC sends the CN two RELOCATION REQUEST ACKNOWLEDGE messages indicating that the handover preparation process is completed, if the RNC receives a HANDOVER TO UTRAN COMPLETE message from the UE, this counter is measured according to the target cell ID in the RELOCATION REQUEST message.
Issue 01 (2013-05-04)
1530
Formula
None
Unit
None
Related Features
Counter Name VS.SRVCC.L2U.AttInCSPS Feature ID WRFD-150215 Feature Name SRVCC from LTE to UMTS with PS Handover
Issue 01 (2013-05-04)
1531
1.12.14.49 Number of Successful Incoming LTE-to-UMTS CS+PS Handovers Triggered by SRVCC for VoIP Services Counters
Counter ID 73425823 Counter Name VS.SRVCC.L2U.SuccInCSPS Counter Description Number of Successful Incoming LTE-to-UMTS CS +PS Handovers Triggered by SRVCC for VoIP Services for Cell
Description
This counter provides the number of successful incoming L2U CS+PS handovers triggered by Single Radio Voice Call Continuity (SRVCC) with PS Handover for VoIP services. This counter is measured according to the target cell ID in the RELOCATION REQUEST message. L2U refers to handovers from the LTE network to the UMTS network. With the SRVCC with PS Handover feature, the VoIP and PS services in an LTE network are handed over to the CS and PS domains of the UMTS network, respectively. As a result, speech continuity is ensured during the handover. On the RNC side, this process is an incoming inter-RAT CS+PS handover. RAT is short for radio access technology.
Measurement point
The measurement is triggered at point D shown in the following figure. When the RNC sends two RELOCATION COMPLETE messages to the CN, this counter is measured according to the target cell ID in the two RELOCATION REQUEST messages.
Issue 01 (2013-05-04)
1532
Formula
None
Unit
None
Related Features
Counter Name VS.SRVCC.L2U.SuccInCSPS Feature ID WRFD-150215 Feature Name SRVCC from LTE to UMTS with PS Handover
Issue 01 (2013-05-04)
1533
1.12.15 Measurement Related to the Release of Iu Signaling Connections (Without RAB) (Cell)(IU.Sig.Rel.Cell)
Overview
The RNC receives an RRC Connection Setup Complete message and returns an INITIAL UE MESSAGE to the CN. The signaling connection (without RAB) is released over the Iu interface. This function subset measures the number of Iu signaling connection releases in a cell based on the domain.
Counters
Counter ID 73426353 Counter Name VS.IU.Sig.Normal Rel.CS Counter Description Number of Iu CS Signaling Connections (Without RAB) Normally Released for Cell Number of Iu PS Signaling Connections (Without RAB) Normally Released for Cell Number of Iu CS Signaling Connections (Without RAB) Abnormally Released for Cell Number of Iu PS Signaling Connections (Without RAB) Abnormally Released for Cell Number of Iu CS Signaling Connections (Without RAB) Normally Released for Cell (Service Reasons) Original Release V900R015
73426354
VS.IU.Sig.Normal Rel.PS
V900R015
73426355
VS.IU.Sig.Abnorm alRel.CS
V900R015
73426356
VS.IU.Sig.Abnorm alRel.PS
V900R015
73426357
VS.IU.Sig.Normal Rel.CS.Service
V900R015
Issue 01 (2013-05-04)
1534
Counter ID 73426358
Counter Name VS.IU.Sig.Normal Rel.PS.Service
Counter Description Number of Iu PS Signaling Connections (Without RAB) Normally Released for Cell (Service Reasons) Number of Iu CS Signaling Connections (Without RAB) Abnormally Released for Cell (Service Reasons) Number of Iu PS Signaling Connections (Without RAB) Abnormally Released for Cell (Service Reasons) Number of Iu CS Signaling Connections (Without RAB) Abnormally Released Due to Security Mode Procedure Failures for Cell (Service Reasons) Number of Iu PS Signaling Connections (Without RAB) Abnormally Released Due to Security Mode Procedure Failures for Cell (Service Reasons)
73426359
VS.IU.Sig.Abnorm alRel.CS.Service
V900R015
73426360
VS.IU.Sig.Abnorm alRel.PS.Service
V900R015
73426361
VS.IU.Sig.Abnorm alRel.CS.Service.Se cModeFail
V900R015
73426362
VS.IU.Sig.Abnorm alRel.PS.Service.Se cModeFail
V900R015
None
1.12.15.1 Number of Iu CS Signaling Connections (Without RAB) Normally Released for Cell Counters
Counter ID 73426353 Counter Name VS.IU.Sig.NormalRel.CS Counter Description Number of Iu CS Signaling Connections (Without RAB) Normally Released for Cell
Description
This counter measures the number of Iu CS signaling connections (without RAB) normally released in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives an RRC Connection Setup Complete message from a UE and sends an INITIAL UE MESSAGE to the CN. Then, the signaling connection (without RAB) for the UE is released over the Iu interface. If the latest IU RELEASE COMMAND message received by the RNC carries the cause value "User Inactivity", "Normal Release", "Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message with the causes of "User Inactivity", "Network Optimization" or "UE Generated Signalling Connection Release", this counter is increased by one in the best cell of the UE based on the domain of the released signaling connection. Figure 1-694 Iu signaling connections normally released procedure
Issue 01 (2013-05-04)
1536
Formula
None
Unit
None
Related Features
Counter Name VS.IU.Sig.NormalRel.CS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.15.2 Number of Iu PS Signaling Connections (Without RAB) Normally Released for Cell Counters
Counter ID 73426354 Counter Name VS.IU.Sig.NormalRel.PS Counter Description Number of Iu PS Signaling Connections (Without RAB) Normally Released for Cell
Description
This counter measures the number of Iu PS signaling connections (without RAB) normally released in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives an RRC Connection Setup Complete message from a UE and sends an INITIAL UE MESSAGE to the CN. Then, the signaling connection (without RAB) for the UE is released over the Iu interface. If the latest IU RELEASE COMMAND message received by the RNC carries the cause value "User Inactivity", "Normal Release", "Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message with the causes of "User Inactivity", "Network Optimization" or "UE Generated Signalling Connection Release", this counter is increased by one in the best cell of the UE based on the domain of the released signaling connection. For details about the cause values indicating a normal release.
Issue 01 (2013-05-04)
1537
Figure 1-695 Iu signaling connections normally released procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IU.Sig.NormalRel.PS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.15.3 Number of Iu CS Signaling Connections (Without RAB) Abnormally Released for Cell Counters
Counter ID 73426355 Counter Name VS.IU.Sig.AbnormalRel.CS Counter Description Number of Iu CS Signaling Connections (Without RAB) Abnormally Released for Cell
1538
Issue 01 (2013-05-04)
Description
This counter measures the number of Iu CS signaling connections (without RAB) abnormally released in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives an RRC Connection Setup Complete message from a UE and sends an INITIAL UE MESSAGE to the CN. Then, the RNC sends an IU RELEASE REQUEST message to the CN. The signaling connection (without RAB) for the UE is released over the Iu interface. If the latest IU RELEASE COMMAND message received by the RNC carries a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", this counter is increased by one in the best cell of the UE based on the domain of the released signaling connection. For details about the cause values indicating an abnormal release, see 3GPP TS 25.413. Figure 1-696 Iu signaling connections abnormally released procedure
Formula
None
Unit
None
Issue 01 (2013-05-04)
1539
Related Features
Counter Name VS.IU.Sig.AbnormalRel.CS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.15.4 Number of Iu PS Signaling Connections (Without RAB) Abnormally Released for Cell Counters
Counter ID 73426356 Counter Name VS.IU.Sig.AbnormalRel.PS Counter Description Number of Iu PS Signaling Connections (Without RAB) Abnormally Released for Cell
Description
This counter measures the number of Iu PS signaling connections (without RAB) abnormally released in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives an RRC Connection Setup Complete message from a UE and sends an INITIAL UE MESSAGE to the CN. Then, the RNC sends an IU RELEASE REQUEST message to the CN. The signaling connection (without RAB) for the UE is released over the Iu interface. If the latest IU RELEASE COMMAND message received by the RNC carries a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", this counter is increased by one in the best cell of the UE based on the domain of the released signaling connection. For details about the cause values indicating an abnormal release, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
1540
Figure 1-697 Iu signaling connections abnormally released procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IU.Sig.AbnormalRel.PS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.15.5 Number of Iu CS Signaling Connections (Without RAB) Normally Released for Cell (Service Reasons) Counters
Counter ID 73426357 Counter Name VS.IU.Sig.NormalRel.CS.S ervice Counter Description Number of Iu CS Signaling Connections (Without RAB) Normally Released for Cell (Service Reasons)
1541
Issue 01 (2013-05-04)
Description
This counter measures the number of Iu CS signaling connections (without RAB) that are normally released due to service reasons. This counter is measured in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives an RRC Connection Setup Complete message from a UE and sends an INITIAL UE MESSAGE to the CN. Then, the signaling connection (without RAB) for the UE is released over the Iu interface. If the latest IU RELEASE COMMAND message received by the RNC carries the cause value "User Inactivity", "Normal Release", "Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message with the causes of "User Inactivity", "Network Optimization" or "UE Generated Signalling Connection Release", and if the RRC connection is set up due to originating conversational call, terminating conversational call, or emergency call, this counter is increased by one in the best cell of the UE based on the domain of the released signaling connection. For details about the cause values indicating a normal release . Figure 1-698 Iu signaling connections normally released procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IU.Sig.NormalRel.CS.S ervice Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.15.6 Number of Iu PS Signaling Connections (Without RAB) Normally Released for Cell (Service Reasons) Counters
Counter ID 73426358 Counter Name VS.IU.Sig.NormalRel.PS.Se rvice Counter Description Number of Iu PS Signaling Connections (Without RAB) Normally Released for Cell (Service Reasons)
Description
This counter measures the number of Iu PS signaling connections (without RAB) that are normally released due to service reasons. This counter is measured in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives an RRC Connection Setup Complete message from a UE and sends an INITIAL UE MESSAGE to the CN. Then, the signaling connection (without RAB) for the UE is released over the Iu interface. If the latest IU RELEASE COMMAND message received by the RNC carries the cause value "User Inactivity", "Normal Release", "Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message with the causes of "User Inactivity", "Network Optimization" or "UE Generated Signalling Connection Release", and if the RRC connection is set up due to originating interactive call, terminating interactive call, originating background call, or terminating background call, this counter is increased by one in the best cell of the UE based on the domain of the released signaling connection. For details about the cause values indicating a normal release, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
1543
Figure 1-699 Iu signaling connections normally released procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IU.Sig.NormalRel.PS.Se rvice Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.15.7 Number of Iu CS Signaling Connections (Without RAB) Abnormally Released for Cell (Service Reasons) Counters
Counter ID 73426359 Counter Name VS.IU.Sig.AbnormalRel.CS .Service Counter Description Number of Iu CS Signaling Connections (Without RAB) Abnormally Released for Cell (Service Reasons)
1544
Issue 01 (2013-05-04)
Description
This counter measures the number of Iu CS signaling connections (without RAB) that are abnormally released due to service reasons. This counter is measured in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives an RRC Connection Setup Complete message from a UE and sends an INITIAL UE MESSAGE to the CN. Then, the RNC sends the last IU RELEASE REQUEST message to the CN. The signaling connection (without RAB) for the UE is released over the Iu interface. If the IU RELEASE COMMAND message received by the RNC carries a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", and if the RRC connection is set up due to originating conversational call, terminating conversational call, or emergency call, this counter is increased by one in the best cell of the UE based on the domain of the released signaling connection. For details about the cause values indicating an abnormal release, see 3GPP TS 25.413. Figure 1-700 Iu signaling connections abnormally released procedure
Formula
None
Unit
None
Issue 01 (2013-05-04)
1545
Related Features
Counter Name VS.IU.Sig.AbnormalRel.CS .Service Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.15.8 Number of Iu PS Signaling Connections (Without RAB) Abnormally Released for Cell (Service Reasons) Counters
Counter ID 73426360 Counter Name VS.IU.Sig.AbnormalRel.PS. Service Counter Description Number of Iu PS Signaling Connections (Without RAB) Abnormally Released for Cell (Service Reasons)
Description
This counter measures the number of Iu PS signaling connections (without RAB) that are abnormally released due to service reasons. This counter is measured in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives an RRC Connection Setup Complete message from a UE and sends an INITIAL UE MESSAGE to the CN. Then, the RNC sends an IU RELEASE REQUEST message to the CN. The signaling connection (without RAB) for the UE is released over the Iu interface. If the latest IU RELEASE COMMAND message received by the RNC carries a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", and if the RRC connection is set up due to originating interactive call, terminating interactive call, originating background call, or terminating background call, this counter is increased by one in the best cell of the UE based on the domain of the released signaling connection. For details about the cause values indicating an abnormal release, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
1546
Figure 1-701 Iu signaling connections abnormally released procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IU.Sig.AbnormalRel.PS. Service Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.15.9 Number of Iu CS Signaling Connections (Without RAB) Abnormally Released Due to Security Mode Procedure Failures for Cell (Service Reasons)
Issue 01 (2013-05-04)
1547
Counters
Counter ID 73426361 Counter Name VS.IU.Sig.AbnormalRel.CS .Service.SecModeFail Counter Description Number of Iu CS Signaling Connections (Without RAB) Abnormally Released Due to Security Mode Procedure Failures for Cell (Service Reasons)
Description
This counter measures the number of Iu CS signaling connections (established because of service reasons; without RAB) that are abnormally released due to service reasons in the case of security mode procedure failures. This counter is measured in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives an RRC Connection Setup Complete message from a UE and sends an INITIAL UE MESSAGE to the CN. Then, the security mode procedure fails, and the RNC sends an IU RELEASE REQUEST message to the CN. The signaling connection (without RAB) for the UE is released over the Iu interface. If the latest IU RELEASE COMMAND message received by the RNC carries a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", and if the RRC connection is set up due to originating interactive call, terminating interactive call, originating background call, or terminating background call, this counter is increased by one in the best cell of the UE based on the domain of the released signaling connection. For details about the cause values indicating an abnormal release, see 3GPP TS 25.413. Figure 1-702 Iu signaling connections abnormally released due to security mode procedure
Issue 01 (2013-05-04)
1548
Formula
None
Unit
None
Related Features
Counter Name VS.IU.Sig.AbnormalRel.CS .Service.SecModeFail Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.15.10 Number of Iu PS Signaling Connections (Without RAB) Abnormally Released Due to Security Mode Procedure Failures for Cell (Service Reasons) Counters
Counter ID 73426362 Counter Name VS.IU.Sig.AbnormalRel.PS. Service.SecModeFail Counter Description Number of Iu PS Signaling Connections (Without RAB) Abnormally Released Due to Security Mode Procedure Failures for Cell (Service Reasons)
Description
This counter measures the number of Iu PS signaling connections (established because of service reasons; without RAB) that are abnormally released due to security mode procedure failures. This counter is measured in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives an RRC Connection Setup Complete message from a UE and sends an INITIAL UE MESSAGE to the CN. Then, the security mode procedure fails, and the RNC sends an IU RELEASE REQUEST message to the CN. The signaling connection (without RAB) for the UE is released over the Iu interface. If the latest IU RELEASE COMMAND message received by the RNC carries a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", and if the RRC connection is set up due to originating interactive call, terminating interactive call, originating background call, or terminating background call, this counter is increased by one in the best cell of the UE
based on the domain of the released signaling connection. For details about the cause values indicating an abnormal release, see 3GPP TS 25.413. Figure 1-703 Iu signaling connections abnormally released due to security mode procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IU.Sig.AbnormalRel.PS. Service.SecModeFail Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.16 Iub Interface Measurement per cell(IUB.Cell)

Overview
Iub Interface radio link (RL) procedures on the Iub interface are as follows: RL setup procedure, RL deletion procedure, Synchronized RL reconfiguration procedure, RL failure procedure, RL restoration procedure.
Counters
Counter ID 67180826 Counter Name VS.IUB.CancelRLRecfg Counter Description Number of Iub Interface RLs Whose Synchronized Reconfiguration Is Cancelled for Cell Number of Iub Interface RL Failures for Cell Number of Iub Interface Radio Link Failures for Cell (Configuration Unsupported) Number of Iub Interface Radio Link Failures for Cell (Device Fault) Number of Iub Interface Radio Link Synchronization Failures for Cell Number of Iub Interface Radio Link Failures for Cell (Synchronization Failure) Number of Iub Interface Radio Link Addition Failures for Cell (Configuration Unsupported) Number of Iub Interface Radio Link Addition Failures for Cell (Congestion) Number of Iub Interface Radio Link Addition Failures for Cell (Device Fault) Original Release Earlier than V900R011
67180827
VS.IUB.RLFailInd
67180831
VS.IUB.RLFailInd. CfgUnsupp
67180829
VS.IUB.RLFailInd. HW
67189772
VS.IUB.RLFailInd. SyncFail
67180830
VS.IUB.RLFailNoRestore
67180813
RLM.FailRLAddIu b.CfgUnsup
67180812
RLM.FailRLAddIu b.Cong
67180811
VS.SHO.FailRLAd dIub.HW
Issue 01 (2013-05-04)
1551
Counter ID 67180823
Counter Name VS.IUB.FailRLRec fg.CfgUnsupp
Counter Description Number of Iub Interface Radio Link Synchronous Reconfiguration Failures for Cell (Configuration Unsupported) Number of Iub Interface Radio Link Synchronous Reconfiguration Failures for Cell (Congestion) Number of Iub Interface Radio Link Synchronous Reconfiguration Failures for Cell (Device Fault) Number of Iub Interface RLs Unsuccessfully Reconfigured Due to No Response for Cell Number of Iub Interface Radio Link Setup Failures for Cell (Configuration Unsupported) Number of Iub Interface Radio Link Setup Failures for Cell (Congestion) Number of Iub Interface Radio Link Setup Failures for Cell (Device Fault) Number of Iub Interface RL Reconfiguration Attempts for Cell
67180822
VS.IUB.FailRLRec fg.Cong
67180821
VS.IUB.FailRLRec fg.HW
67180824
VS.IUB.FailRLRec fg.NoReply
67180806
RLM.FailRLSetup Iub.CfgUnsup
67180805
RLM.FailRLSetup Iub.Cong
67180804
VS.IUB.FailRLSet up.HW
67189775
VS.IUB.AttRLRecfg
Issue 01 (2013-05-04)
1552
Counter ID 67180808
Counter Name VS.IUB.AttRLAdd
Counter Description Number of Iub Interface RL Addition Requests for Cell Number of Iub Interface RL Deletion Requests for Cell Number of Iub Interface RL Establishment Requests for Cell Number of Iub Interface RL Restorations for Cell Number of Iub Interface RLs Successfully Added for Cell Number of Iub Interface RLs Successfully Deleted for Cell Number of Iub Interface RLs Successfully Synchronization Reconfigured for Cell Number of Iub Interface RLs Successfully Established for Cell Number of Iub Interface RLs Unsuccessfully Established Due to No Response for Cell
67180815
VS.IUB.AttRLDel
V900R012
67180801
VS.IUB.AttRLSetup
67180832
VS.IUB.RLRestore
67180809
VS.IUB.SuccRLAd d
67180816
VS.IUB.SuccRLDel
V900R012
67180819
VS.IUB.SuccRLRecfg
67180802
VS.IUB.SuccRLSetup
67180838
VS.IUB.FailRLSet up.NoReply
None
1.12.16.1 Number of RLs with Synchronized Reconfiguration Cancelled on Iub Interface Counters
Counter ID 67180826 Counter Name VS.IUB.CancelRLRecfg Counter Description Number of Iub Interface RLs Whose Synchronized Reconfiguration Is Cancelled for Cell
Description
This measurement counter takes statistics of the number of RLs whose synchronized reconfiguration is cancelled on the Iub interface in a cell.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends a RADIO LINK RECONFIGURATION CANCEL message to the NodeB. In this case, the RNC measures the counter in the cell of the RL whose reconfiguration is cancelled on the Iub interface. Figure 1-704 RL reconfiguration cancel procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.CancelRLRecfg Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.16.2 Number of RL Failures on Iub Interface Counters

Counter ID 67180827 67180831 Counter Name VS.IUB.RLFailInd VS.IUB.RLFailInd.CfgUnsupp Counter Description Number of Iub Interface RL Failures for Cell Number of Iub Interface Radio Link Failures for Cell (Configuration Unsupported) Number of Iub Interface Radio Link Failures for Cell (Device Fault) Number of Iub Interface Radio Link Synchronization Failures for Cell
67180829
VS.IUB.RLFailInd.HW
67189772
VS.IUB.RLFailInd.SyncFail
Description
This counter provides the number of the RADIO LINK FAILURE INDICATION messages that the RNC receives from the NodeB on the Iub interface in a cell. The following table describes the meaning of each counter.
Issue 01 (2013-05-04)
1555
Counter Name VS.IUB.RLFailInd.CfgUnsupp
Description Number of RL failures on Iub interface due to configuration unsupported (cause value: Power level not supported, Measurement not supported for the object, SIB Origination in Node B not Supported, Requested Tx Diversity Mode not supported, Number of DL codes not supported, S-CPICH not supported, Combining not supported, UL SF not supported, DL SF not supported, Common Transport Channel Type not supported, Dedicated Transport Channel Type not supported, Downlink Shared Channel Type not supported, Uplink Shared Channel Type not supported, CM not supported, Tx diversity no longer supported, or Number of UL codes not supported) Number of RL failures on Iub interface due to hardware failure (cause value: Hardware failure) Number of RL failures on Iub interface due to synchronization failure (cause value: Synchronization failure)
VS.IUB.RLFailInd.HW
VS.IUB.RLFailInd.SyncFail
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a RADIO LINK FAILURE INDICATION message from the NodeB, indicating that one or more radio links (RLs) are not available due to a synchronization failure or unsupported configurations. In this case, this counter is increased by one in the cell where the RL is unavailable.
Issue 01 (2013-05-04)
1556
Figure 1-705 RL failure procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.RLFailInd Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.IUB.RLFailInd.CfgUnsupp
WRFD-010510
VS.IUB.RLFailInd.HW
WRFD-010510
Issue 01 (2013-05-04)
1557
Counter Name VS.IUB.RLFailInd.SyncFail
1.12.16.3 Number of RLs Unsuccessfully Restored on Iub Interface due to No Response Counters
Counter ID 67180830 Counter Name VS.IUB.RLFailNoRestore Counter Description Number of Iub Interface Radio Link Failures for Cell (Synchronization Failure)
Description
This counter provides the number of radio links (RLs) that cannot be restored on the Iub interface in a cell because the NodeB fails to send the RADIO LINK RESTORE INDICATION message.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC allocates resources to a new RL and initiates an RL setup procedure, the RNC starts a timer to wait for the RADIO LINK RESTORE INDICATION message from the NodeB. If the RNC does not receive this message before the timer expires, this counter is increased by one in the cell where the RL is to be restored. Figure 1-706 RL restore time out procedure
Issue 01 (2013-05-04)
1558
The measurement is triggered at point A as shown in the figure. When the RNC receives a RADIO LINK FAILURE INDICATION message from the NodeB, the RNC starts a timer to wait for the RADIO LINK RESTORE INDICATION message from the NodeB. If the RNC does not receive the RADIO LINK RESTORE INDICATION message before the timer expires, this counter is increased by one in the cell where the RL is to be restored. Figure 1-707 RL restore time out procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.RLFailNoRestore Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
1559
1.12.16.4 Number of RLs Unsuccessfully Added on Iub Interface for Different Causes Counters
Counter ID 67180813 Counter Name RLM.FailRLAddIub.CfgUn sup Counter Description Number of Iub Interface Radio Link Addition Failures for Cell (Configuration Unsupported) Number of Iub Interface Radio Link Addition Failures for Cell (Congestion) Number of Iub Interface Radio Link Addition Failures for Cell (Device Fault)
67180812
RLM.FailRLAddIub.Cong
67180811
VS.SHO.FailRLAddIub.H W
Description
The measurement counters provide the number of RLs unsuccessfully added on the Iub interface in a cell for different causes. The following table describes the meaning of each counter. Counter Name RLM.FailRLAddIub.CfgUnsup Description Number of RLs unsuccessfully added on Iub interface due to configuration unsupported (cause value: Combining not supported, Requested Tx Diversity Mode not supported, UL SF not supported, DL SF not supported, or CM not supported) Number of RLs unsuccessfully added on Iub interface due to resources not available (cause value: Cell not available, DL radio resources not available, UL radio resources not available, RL Already Activated/allocated, Node B Resources Unavailable, Combining Resources not available, Transport resource unavailable, or Control processing overload) Number of RLs unsuccessfully added on Iub Interface due to hardware failure (cause value: Hardware failure)
VS.SHO.FailRLAddIub.HW
Issue 01 (2013-05-04)
1560
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends a RADIO LINK ADDITION REQUEST message to the NodeB and waits for the response. If the RNC receives a RADIO LINK ADDITION FAILURE message from the NodeB, it measures the counters in the cell where the RL are unsuccessfully added for different causes. Figure 1-708 RL addition procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name RLM.FailRLAddIub.CfgUn sup Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1561
WRFD-010510
Issue 01 (2013-05-04)
Counter Name VS.SHO.FailRLAddIub.H W
1.12.16.5 Number of RLs Unsuccessfully Synchronization Reconfigured on Iub Interface for Different Causes Counters
Counter ID 67180823 Counter Name VS.IUB.FailRLRecfg.CfgU nsupp Counter Description Number of Iub Interface Radio Link Synchronous Reconfiguration Failures for Cell (Configuration Unsupported) Number of Iub Interface Radio Link Synchronous Reconfiguration Failures for Cell (Congestion) Number of Iub Interface Radio Link Synchronous Reconfiguration Failures for Cell (Device Fault)
67180822
VS.IUB.FailRLRecfg.Cong
67180821
VS.IUB.FailRLRecfg.HW
Description
The measurement counters provide the number of RLs unsuccessfully reconfigured on the Iub interface in a cell for different causes. The following table describes the meaning of each counter. Counter Name VS.IUB.FailRLRecfg.CfgUnsupp Description Number of RLs unsuccessfully reconfigured on Iub interface due to configuration unsupported (cause value: UL SF not supported, DL SF not supported, Downlink Shared Channel Type not supported, Uplink Shared Channel Type not supported, CM not supported, Number of DL codes not supported, or Number of UL codes not supported)
1562
Issue 01 (2013-05-04)
Counter Name VS.IUB.FailRLRecfg.Cong
Description Number of RLs unsuccessfully reconfigured on Iub interface due to resources not available (cause value: Cell not available, DL radio resources not available, UL radio resources not available, RL Already Activated/ allocated, Node B Resources Unavailable, Combining Resources not available, Transport resource unavailable, or Control processing overload) Number of RLs unsuccessfully reconfigured on Iub Interface due to hardware failure (cause value: Hardware failure)
Measurement point
The measurement is triggered at point B as shown in the figure. The RNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB and waits for the response. If the RNC receives a RADIO LINK RECONFIGURATION FAILURE message from the NodeB, it measures the counters in the cell according to different causes. Figure 1-709 Synchronized RL reconfiguration procedure (failed operation)
Formula
None
Issue 01 (2013-05-04)
1563
Unit
None
Related Features
Counter Name VS.IUB.FailRLRecfg.CfgU nsupp Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.IUB.FailRLRecfg.Cong
WRFD-010510
WRFD-010510
1.12.16.6 Number of RLs Unsuccessfully Reconfigured on Iub Interface due to No Response Counters
Counter ID 67180824 Counter Name VS.IUB.FailRLRecfg.NoRe ply Counter Description Number of Iub Interface RLs Unsuccessfully Reconfigured Due to No Response for Cell
Description
This measurement counter takes statistics of the number of RLs unsuccessfully reconfigured on the Iub interface due to no response from the NodeB.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends a RADIO LINK RECONFIGURATION PREPARE message to a NodeB and starts a timer to wait for the response. If the RNC does not receive any response message from the NodeB upon expiry of the timer, it measures the counter in the cell where the RL is requested to reconfigure.
Issue 01 (2013-05-04)
1564
Figure 1-710 Sync RL reconfiguration procedure (NoReply)
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.FailRLRecfg.NoRe ply Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.16.7 Number of RLs Unsuccessfully Established on Iub Interface for Different Causes
Issue 01 (2013-05-04)
1565
Counters
Counter ID 67180806 Counter Name RLM.FailRLSetupIub.CfgU nsup Counter Description Number of Iub Interface Radio Link Setup Failures for Cell (Configuration Unsupported) Number of Iub Interface Radio Link Setup Failures for Cell (Congestion) Number of Iub Interface Radio Link Setup Failures for Cell (Device Fault)
67180805
RLM.FailRLSetupIub.Cong
67180804
VS.IUB.FailRLSetup.HW
Description
The measurement counters provide the number of RLs that fail to be established on the Iub interface in a cell according to different causes. The following table describes the meaning of each counter. Counter Name RLM.FailRLSetupIub.CfgUnsup Description Number of RLs unsuccessfully established on Iub Interface due to configuration unsupported (cause value: Combining not supported, Requested Tx Diversity Mode not supported, Number of DL codes not supported, Number of UL codes not supported, UL SF not supported, DL SF not supported, Dedicated Transport Channel Type not supported, Downlink Shared Channel Type not supported, Uplink Shared Channel Type not supported, or CM not supported) Number of RLs unsuccessfully established on Iub Interface due to no resource available (cause value: Cell not available, DL radio resources not available, UL radio resources not available, RL Already Activated/ allocated, Node B Resources Unavailable, Combining Resources not available, Transport resource unavailable, or Control processing overload) Number of RLs unsuccessfully established on Iub Interface due to hardware failure (cause value: Hardware failure)
VS.IUB.FailRLSetup.HW
Issue 01 (2013-05-04)
1566
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives a RADIO LINK SETUP FAILURE message from the NodeB after sending to the NodeB a RADIO LINK SETUP REQUEST message. The RNC measures the counters in the cell where the RLs are failed to be established for different causes. Figure 1-711 RL setup procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name RLM.FailRLSetupIub.CfgU nsup Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1567
WRFD-010510
Issue 01 (2013-05-04)
Counter Name VS.IUB.FailRLSetup.HW
1.12.16.8 Number of RLs Requested to Reconfigure with Synchronization on Iub Interface Counters
Counter ID 67189775 Counter Name VS.IUB.AttRLRecfg Counter Description Number of Iub Interface RL Reconfiguration Attempts for Cell
Description
This measurement counter takes statistics of the number of RLs requested to reconfigure with synchronization on the Iub interface in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB. In this case, the RNC measures the counter in the cell where the RLs are requested to reconfigure. Figure 1-712 Synchronized RL reconfiguration procedure (successful operation)
Issue 01 (2013-05-04)
1568
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.AttRLRecfg Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.16.9 Number of RLs Requested to Add on Iub Interface Counters

Counter ID 67180808 Counter Name VS.IUB.AttRLAdd Counter Description Number of Iub Interface RL Addition Requests for Cell
Description
The measurement counters provide the number of RLs requested to add on the Iub interface in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure. To add one or more RLs for a NodeB communication context, the RNC shall initiate a RL addition procedure by sending a RADIO LINK ADDITION REQUEST message to the NodeB. In this case, the RNC measures the counter in the cell where the RLs are requested to add.
Issue 01 (2013-05-04)
1569
Figure 1-713 RL addition procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.AttRLAdd Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.16.10 Number of RLs Requested to Delete on Iub Interface Counters

Counter ID 67180815 Counter Name VS.IUB.AttRLDel Counter Description Number of Iub Interface RL Deletion Requests for Cell
Issue 01 (2013-05-04)
1570
Description
This measurement item provides the number of RLs requested to delete on the Iub interface in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends the NodeB a RADIO LINK DELETION REQUEST message to delete one or more RLs of an UE from the NodeB. In this case, the RNC measures the item in the cell where the RLs are requested to delete. Figure 1-714 RL deletion procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.AttRLDel Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
1571
1.12.16.11 Number of RLs Requested to Establish on Iub Interface Counters

Counter ID 67180801 Counter Name VS.IUB.AttRLSetup Counter Description Number of Iub Interface RL Establishment Requests for Cell
Description
This measurement counter takes statistics of the number of RLs requested to establish on the Iub interface in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC needs to establish mandatory resources for a new communication context in the NodeB and initiates a RL setup procedure to the NodeB by sending a RADIO LINK SETUP REQUEST message. In this case, the RNC measures the counter in the cell where the RLs are requested to establish. Figure 1-715 RL setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.AttRLSetup Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.16.12 Number of RLs Restored on Iub Interface Counters

Counter ID 67180832 Counter Name VS.IUB.RLRestore Counter Description Number of Iub Interface RL Restorations for Cell
Description
This measurement counter takes statistics of the number of RLs restored on the Iub interface in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the Node B sends a RADIO LINK RESTORE INDICATION message to the RNC, notifying that the RNC has obtained or restored the synchronization of one or more uplinks on the Uu interface. In this case, the RNC measures the counter in the cell where the RLs are restored.
Issue 01 (2013-05-04)
1573
Figure 1-716 RL restoration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.RLRestore Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.16.13 Number of RLs Successfully Added on Iub Interface Counters

Counter ID 67180809 Counter Name VS.IUB.SuccRLAdd Counter Description Number of Iub Interface RLs Successfully Added for Cell
1574
Issue 01 (2013-05-04)
Description
The measurement counters provide the number of RLs successfully added on the Iub interface in a cell.
Measurement point
At point B as shown in the figure, the RNC sends a RADIO LINK ADDITION REQUEST message to the NodeB and starts a timer to wait for a response. After receiving a RADIO LINK ADDITION RESPONSE message from the NodeB, the RNC measures the counter in the cell where the RLs are successfully added. Figure 1-717 RL addition procedure (successful operation)
At point B as shown in the figure, the RNC sends the NodeB a RADIO LINK ADDITION REQUEST message and starts a timer to wait for a response. If there are successfully added RLs when the RNC receives a RADIO LINK ADDITION FAILURE message from the NodeB, the RNC measures the counter in the cell where the RLs are successfully added.
Issue 01 (2013-05-04)
1575
Figure 1-718 RL addition procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.SuccRLAdd Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.16.14 Number of RLs Successfully Deleted on Iub Interface Counters

Counter ID 67180816 Counter Name VS.IUB.SuccRLDel Counter Description Number of Iub Interface RLs Successfully Deleted for Cell
Issue 01 (2013-05-04)
1576
Description
This measurement item provides the number of RLs successfully deleted on the Iub interface in a cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends to the NodeB a RADIO LINK DELETION REQUEST message and waits for the response. If the RNC receives a RADIO LINK DELETION RESPONSE message from the NodeB, it measures the item in the cell where the RLs are successfully deleted. Figure 1-719 RL deletion procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.SuccRLDel Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
1577
1.12.16.15 Number of RLs Successfully Reconfigured with Synchronization on Iub Interface Counters
Counter ID 67180819 Counter Name VS.IUB.SuccRLRecfg Counter Description Number of Iub Interface RLs Successfully Synchronization Reconfigured for Cell
Description
This measurement counter takes statistics of the number of RLs successfully reconfigured on the Iub interface in a cell.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends a RADIO LINK RECONFIGURATION COMMIT message to the NodeB. In this case, the RNC measures the counter in the cell where the RLs are successfully reconfigured. Figure 1-720 Synchronized RL reconfiguration commit procedure
Issue 01 (2013-05-04)
1578
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.SuccRLRecfg Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.16.16 Number of RLs Successfully Established on Iub Interface Counters

Counter ID 67180802 Counter Name VS.IUB.SuccRLSetup Counter Description Number of Iub Interface RLs Successfully Established for Cell
Description
This measurement counter takes statistics of the number of RLs successfully established on Iub interface in a cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives a RADIO LINK SETUP RESPONSE message from the NodeB after sending a RADIO LINK SETUP REQUEST message to the NodeB. In this case, the RNC measures the counter in the cell where the RLs are successfully established.
Issue 01 (2013-05-04)
1579
Figure 1-721 Figure 7-33 RL setup procedure (successful operation)
The measurement is triggered at point A as shown in the figure, when the RNC sends a RADIO LINK SETUP REQUEST message to the NodeB and starts a timer to wait for a response. If there are successfully established RLs when the RNC receives a RADIO LINK SETUP FAILURE message from the NodeB, the RNC measures the counter in the cell where the RLs are successfully established. Figure 1-722 RL setup procedure (failed operation)
Issue 01 (2013-05-04)
1580
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.SuccRLSetup Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.16.17 Number of RLs Unsuccessfully Established on Iub Interface due to No Response Counters
Counter ID 67180838 Counter Name VS.IUB.FailRLSetup.NoReply Counter Description Number of Iub Interface RLs Unsuccessfully Established Due to No Response for Cell
Description
The measurement counter provides the number of RLs unsuccessfully established on the Iub interface due to no response from the NodeB.
Measurement point
The RNC sends a RADIO LINK SETUP REQUEST or RADIO LINK ADDITION REQUEST message to the NodeB and starts a timer to wait for the response. If the RNC does not receive a response upon expiry of the timer, it measures the counter in the cell where the RLs are unsuccessfully established.
Issue 01 (2013-05-04)
1581
Figure 1-723 RL setup procedure (failed operation)(no reply)
Formula
None
Unit
None
Related Features
Counter Name VS.IUB.FailRLSetup.NoReply Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.17 Measurement related to LCS service per cell(LCS.CELL)

Overview
This function subset mainly measures the number of positioning results that exceeds the coverage of UE reference cell through the UE ASSISTED AGPS, UE BASED AGPS, OTDOA, CELLID + RTT positioning methods.
Issue 01 (2013-05-04)
1582
Counters
Counter ID 67190670 Counter Name VS.LCS.OutCellCo ver.AgpsAss Counter Description Number of Positioning Results Out of the Reference Cell's Coverage in Case of UE ASSISTED AGPS Method for Cell Number of Positioning Results Out of the Reference Cell's Coverage in Case of UE Based AGPS Method for Cell Number of Positioning Results Out of the Reference Cell's Coverage in Case of OTDOA Method for Cell Number of Positioning Results Out of the Reference Cell's Coverage in Case of CELLID + RTT Method for Cell Original Release Earlier than V900R011
67190671
VS.LCS.OutCellCo ver.AgpsBas
67190672
VS.LCS.OutCellCo ver.Otdoa
67190673
VS.LCS.OutCellCo ver.CellIdRtt
None
1.12.17.1 Number of Positioning Results Beyond Coverage of UE Reference Cell in UE Assisted AGPS Method Counters
Counter ID 67190670 Counter Name VS.LCS.OutCellCover.AgpsAss Counter Description Number of Positioning Results Out of the Reference Cell's Coverage in Case of UE ASSISTED AGPS Method for Cell
Issue 01 (2013-05-04)
1583
Description
This measurement item provides the number of positioning results that exceed the coverage of UE reference cell through the UE ASSISTED AGPS method in a cell.
Measurement point
The measurement is triggered when the RNC receives a successful positioning result that exceeds the coverage of UE reference cell and the current positioning method is UE ASSISTED AGPS.
Formula
None
Unit
None
Related Features
Counter Name VS.LCS.OutCellCover.AgpsAss Feature ID WRFD-020803 Feature Name A-GPS Based LCS
1.12.17.2 Number of Positioning Results Beyond Coverage of UE Reference Cell in UE-based AGPS Method Counters
Counter ID 67190671 Counter Name VS.LCS.OutCellCover.Agp sBas Counter Description Number of Positioning Results Out of the Reference Cell's Coverage in Case of UE Based AGPS Method for Cell
Description
This measurement item provides the number of positioning results that exceed the coverage of UE reference cell through the UE BASED AGPS method in a cell.
Measurement point
The measurement is triggered when the RNC receives a successful positioning result that exceeds the coverage of UE reference cell and the current positioning method is UE BASED AGPS.
Formula
None
Unit
None
Related Features
Counter Name VS.LCS.OutCellCover.Agp sBas Feature ID WRFD-020803 Feature Name A-GPS Based LCS
1.12.17.3 Number of Positioning Results Beyond Coverage of UE Reference Cell in OTDOA Method Counters
Counter ID 67190672 Counter Name VS.LCS.OutCellCover.Otdoa Counter Description Number of Positioning Results Out of the Reference Cell's Coverage in Case of OTDOA Method for Cell
Description
This measurement item provides the number of positioning results that exceed the coverage of UE reference cell through the OTDOA method in a cell.
Measurement point
The measurement is triggered when the RNC receives a successful positioning result exceeds the coverage of UE reference cell and the current positioning method is OTDOA.
Formula
None
Unit
None
Issue 01 (2013-05-04)
1585
Related Features
Counter Name VS.LCS.OutCellCover.Otdoa Feature ID WRFD-020802 Feature Name OTDOA Based LCS
1.12.17.4 Number of Positioning Results Beyond Coverage of UE Reference Cell in CELLID + RTT method Counters
Counter ID 67190673 Counter Name VS.LCS.OutCellCover.CellIdRtt Counter Description Number of Positioning Results Out of the Reference Cell's Coverage in Case of CELLID + RTT Method for Cell
Description
This measurement item provides the number of positioning results that exceeds the coverage of UE reference cell through the CELLID + RTT method in a cell.
Measurement point
The measurement is triggered when the RNC receives a successful positioning result that exceeds the coverage of UE reference cell and the current positioning method is CELLID + RTT.
Formula
None
Unit
None
Related Features
Counter Name VS.LCS.OutCellCover.CellIdRtt Feature ID WRFD-020801 Feature Name Cell ID + RTT Function Based LCS
Issue 01 (2013-05-04)
1586
1.12.18 MBMS Measurement per cell(MBMS.Cell)

Overview
This function subset is used to measure the number of setups and releases of the MBMS traffic.
Counters
Counter ID 67194980 Counter Name VS.MBMS.InterCe ll.PTPtoPTM.Att VS.MBMS.RB.PTP .AttEstab VS.MBMS.RB.PTP .SuccEstab Counter Description Number of Handover Requests from PTP Cell to PTM Cell Number of MBMS Service PTP Setup Requests for Cell Number of Successful MBMS Service PTP Setups for Cell Number of Abnormal MBMS Service Releases in PTP Mode for Cell Number of Normal MBMS Service Releases in PTP Mode for Cell Number of Successful MTCH Setups for Cell Number of MTCH Setup Failures for Cell Number of Successful Transitions from PTM to PTP for Cell Number of Successful Transitions from PTP to PTM for Cell Number of PTP to PTM Transitions for Cell Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67194981
67194982
67194983
VS.MBMS.RB.PTP .Loss.Abnorm
67194984
VS.MBMS.RB.PTP .Loss.Norm
67192130
VS.MBMS.MTCH SetupSucc.Cell VS.MBMS.MTCH SetupFail.Cell VS.MBMS.PTMto PTP.Succ
67192131
67192615
67192616
VS.MBMS.PTPtoP TM.Succ
67192617
VS.MBMS.PTPtoP TM.Att
Issue 01 (2013-05-04)
1587
Counter ID 67204014 67192620 67192621
Counter Name VS.MBMS.PTM.R B.Mean.Cell VS.MBMS.PTM.R B.Max.Cell VS.MBMS.RB.PT M.AttEstab VS.MBMS.RB.PT M.SuccEstab VS.MBMS.PTP.UE .Channel0.Mean.C ell VS.MBMS.PTM.U E.Channel0.Mean. Cell VS.MBMS.PTP.UE .Channel1.Mean.C ell VS.MBMS.PTM.U E.Channel1.Mean. Cell VS.MBMS.PTP.UE .Channel2.Mean.C ell VS.MBMS.PTM.U E.Channel2.Mean. Cell VS.MBMS.PTP.UE .Channel3.Mean.C ell VS.MBMS.PTM.U E.Channel3.Mean. Cell VS.MBMS.PTP.UE .Channel4.Mean.C ell
Counter Description Mean Number of PTM RBs for Cell Maximum Number of PTM RBs for Cell Number of PTM Setup Requests for Cell Number of Successful PTM Setups for Cell Mean Number of PTP Users of MBMS Channel 0 for Cell Mean Number of PTM Users of MBMS Channel 0 for Cell Mean Number of PTP Users of MBMS Channel 1 for Cell Mean Number of PTM Users of MBMS Channel 1 for Cell Mean Number of PTP Users of MBMS Channel 2 for Cell Mean Number of PTM Users of MBMS Channel 2 for Cell Mean Number of PTP Users of MBMS Channel 3 for Cell Mean Number of PTM Users of MBMS Channel 3 for Cell Mean Number of PTP Users of MBMS Channel 4 for Cell
Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67192622
67204225
67204226
67204227
67204228
67204229
67204230
67204231
67204232
67204233
Issue 01 (2013-05-04)
1588
Counter ID 67204234
Counter Name VS.MBMS.PTM.U E.Channel4.Mean. Cell VS.MBMS.PTM.C hannel0.Dur.Cell VS.MBMS.PTP.Ch annel0.Dur.Cell VS.MBMS.PTM.C hannel1.Dur.Cell VS.MBMS.PTP.Ch annel1.Dur.Cell VS.MBMS.PTM.C hannel2.Dur.Cell VS.MBMS.PTP.Ch annel2.Dur.Cell VS.MBMS.PTM.C hannel3.Dur.Cell VS.MBMS.PTP.Ch annel3.Dur.Cell VS.MBMS.PTM.C hannel4.Dur.Cell VS.MBMS.PTP.Ch annel4.Dur.Cell
Counter Description Mean Number of PTM Users of MBMS Channel 4 for Cell Duration of MBMS Channel 0 in PTM Mode for Cell Duration of MBMS Channel 0 in PTP Mode for Cell Duration of MBMS Channel 1 in PTM Mode for Cell Duration of MBMS Channel 1 in PTP Mode for Cell Duration of MBMS Channel 2 in PTM Mode for Cell Duration of MBMS Channel 2 in PTP Mode for Cell Duration of MBMS Channel 3 in PTM Mode for Cell Duration of MBMS Channel 3 in PTP Mode for Cell Duration of MBMS Channel 4 in PTM Mode for Cell Duration of MBMS Channel 4 in PTP Mode for Cell
67204235
Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67204236
67204237
67204238
67204239
67204240
67204241
67204242
67204243
67204244
None
Issue 01 (2013-05-04)
1589
1.12.18.1 Number of Releases of PTP MBMS Services because the new best cell is on PTM mode Counters
Counter ID 67194980 Counter Name VS.MBMS.InterCell.PTPto PTM.Att Counter Description Number of Handover Requests from PTP Cell to PTM Cell
Description
This measurement item provides the number of releases of PTP MBMS Services because the new best cell is on PTM mode.
Measurement point
After a PTP RB is set up and there are several cells in the active set for UE, the release of the RB might be triggered if the best cell changes and the new best cell is on PTM mode. At that time, the RNC measures the item.
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.InterCell.PTPto PTM.Att Feature ID WRFD-010660 Feature Name MBMS Phase 2
1.12.18.2 Number of Requests for PTP MBMS Setup Counters

Counter ID 67194981 Counter Name VS.MBMS.RB.PTP.AttEstab Counter Description Number of MBMS Service PTP Setup Requests for Cell
Issue 01 (2013-05-04)
1590
Description
This measurement item provides the number of requests for setup of Point-to-Point (PTP) MBMS services in a cell.
Measurement point
After the UE initiates an MBMS setup request, the RNC measures the item when the RNC initiates PTP RB setup based on the request of the UE. If the UE applies for more than one service, the RNC measures the item once for each service.
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.RB.PTP.AttEstab Feature ID WRFD-010660 Feature Name MBMS Phase 2
1.12.18.3 Number of Successful PTP MBMS Setups Counters

Counter ID 67194982 Counter Name VS.MBMS.RB.PTP.SuccEstab Counter Description Number of Successful MBMS Service PTP Setups for Cell
Description
This measurement item provides the number of successful setups of Point-to-Point (PTP) MBMS services in a cell.
Measurement point
After the UE initiates an MBMS setup request, the RNC initiates PTP RB setup based on the request of the UE. When the PTP RB is successfully set up, the RNC measures the item. If the UE applies for more than one service, the RNC measures the item once for each service.
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.RB.PTP.SuccEstab Feature ID WRFD-010660 Feature Name MBMS Phase 2
1.12.18.4 Number of Abnormal Releases of PTP MBMS Services for Different Causes Counters
Counter ID 67194983 Counter Name VS.MBMS.RB.PTP.Loss.A bnorm Counter Description Number of Abnormal MBMS Service Releases in PTP Mode for Cell
Description
This measurement item provides the number of abnormal releases of PTP MBMS services for different causes in a cell.
Measurement point
If an unexpected event occurs, for example, for the RF reason on the air interface, the associated PTP RB is released. At that time, the RNC measures the item. If more than one RB (one RB for one service) is released at the same time, the RNC measures the item once for release of each RB.
Formula
None
Unit
None
Issue 01 (2013-05-04)
1592
Related Features
Counter Name VS.MBMS.RB.PTP.Loss.A bnorm Feature ID WRFD-010660 Feature Name MBMS Phase 2
1.12.18.5 Number of Normal Releases of PTP MBMS Services Counters

Counter ID 67194984 Counter Name VS.MBMS.RB.PTP.Loss.N orm Counter Description Number of Normal MBMS Service Releases in PTP Mode for Cell
Description
This measurement item provides the number of normal releases of PTP MBMS services in a cell.
Measurement point
After a PTP RB is set up, the RNC measures this item in the following conditions: the UE initiates the RB release, the RNC initiates the RB release for transition from PTP to PTM, the RB release is performed because the SGSN initiates MBMS SESSION STOP, and the RNC initiates the RB release because of relocation.
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.RB.PTP.Loss.N orm Feature ID WRFD-010660 Feature Name MBMS Phase 2
1.12.18.6 Number of Successful Setups of MBMS(PTM) Traffic Channel

Counters
Counter ID 67192130 Counter Name VS.MBMS.MTCHSetupSuc c.Cell Counter Description Number of Successful MTCH Setups for Cell
Description
This measurement item provides the number of successful attempts to set up the MBMS traffic channel in a cell.
Measurement point
As shown in Figure1,the RNC measures this item when a MBMS traffic channel of the cell is successfully set up. Figure 1-724 MBMS traffic channel set up procedure
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.MTCHSetupSuc c.Cell Feature ID WRFD-010616 Feature Name MBMS Introduction Package
1.12.18.7 Number of Unsuccessful Setups of MBMS(PTM) Traffic Channel Counters

Counter ID 67192131 Counter Name VS.MBMS.MTCHSetupFail .Cell Counter Description Number of MTCH Setup Failures for Cell
Description
This measurement item provides the number of unsuccessful setups of the MBMS(PTM) traffic channel in a cell.
Measurement point
The RNC measures this item when a MBMS(PTM) traffic channel in the cell fails to be set up.
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.MTCHSetupFail .Cell Feature ID WRFD-010616 Feature Name MBMS Introduction Package
1.12.18.8 Number of successful PTM to PTP transition in a cell
Issue 01 (2013-05-04)
1595
Counters
Counter ID 67192615 Counter Name VS.MBMS.PTMtoPTP.Succ Counter Description Number of Successful Transitions from PTM to PTP for Cell
Description
This measurement item provides the number of successful transition from PTM MBMS service to PTP MBMS service in a cell.
Measurement point
After a MBMS service is transited from PTM mode to PTP mode and a PTP MBMS RB is successful set up, the RNC measures the item. Figure 1-725 transmission of MBMS service from PTM to PTP
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.PTMtoPTP.Succ Feature ID WRFD-01066001 Feature Name MBMS Enhanced Broadcast Mode
1.12.18.9 Number of Successful Transitions from PTP MBMS Service to PTM MBMS Service Counters
Counter ID 67192616 Counter Name VS.MBMS.PTPtoPTM.Succ Counter Description Number of Successful Transitions from PTP to PTM for Cell
Description
This measurement item provides the number of successful transition from PTP MBMS service to PTM MBMS service in a cell.
Measurement point
After a MBMS service is transited from PTP mode to PTM mode and a PTM MBMS RB is successful set up, the RNC measures the item. Figure 1-726 Transmission of MBMS service from PTP to PTM
Issue 01 (2013-05-04)
1597
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.PTPtoPTM.Succ Feature ID WRFD-01066001 Feature Name MBMS Enhanced Broadcast Mode
1.12.18.10 Number of Transitions from PTP MBMS Service to PTM MBMS Service Counters
Counter ID 67192617 Counter Name VS.MBMS.PTPtoPTM.Att Counter Description Number of PTP to PTM Transitions for Cell
Description
This measurement item provides the number of transitions from PTP MBMS service to PTM MBMS service in a cell.
Measurement point
After the initiation of transition from PTP mode to PTM mode, the RNC measures the item.
Formula
None
Unit
None
Issue 01 (2013-05-04)
1598
Related Features
Counter Name VS.MBMS.PTPtoPTM.Att Feature ID WRFD-01066001 Feature Name MBMS Enhanced Broadcast Mode
1.12.18.11 Number of RBs in PTM MBMS Service Counters

Counter ID 67204014 67192620 Counter Name VS.MBMS.PTM.RB.Mean. Cell VS.MBMS.PTM.RB.Max.C ell Counter Description Mean Number of PTM RBs for Cell Maximum Number of PTM RBs for Cell
Description
These counters provide the mean number and maximum number of PTM MBMS RBs in a cell.
Measurement point
The RNC periodically takes a sample (sampling periodicity is 5 seconds) from the number of PTM MBMS RBs in a cell. At the end of the measurement period, the RNC obtains the maximum sampling value as the value of Maximum Number of PTM MBMS RBs for Cell. In addition, the RNC obtains the value of Mean Number of PTM MBMS RBs for Cell by dividing the accumulated number of RBs by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.PTM.RB.Mean. Cell VS.MBMS.PTM.RB.Max.C ell Feature ID WRFD-01061601 WRFD-01061601 Feature Name MBMS Broadcast Mode MBMS Broadcast Mode
Issue 01 (2013-05-04)
1599
1.12.18.12 Number of PTM setup request Counters

Counter ID 67192621 Counter Name VS.MBMS.RB.PTM.AttEstab Counter Description Number of PTM Setup Requests for Cell
Description
This measurement item provides the number of setups of PTM MBMS service in a cell.
Measurement point
When the RNC initiates the setup of PTM MBMS service ,the RNC measures the item. Figure 1-727 PTM MBMS service setup procedure
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.RB.PTM.AttEstab Feature ID WRFD-01061601 Feature Name MBMS Broadcast Mode
1.12.18.13 Number of Successful Setups of PTM MBMS Service Counters

Counter ID 67192622 Counter Name VS.MBMS.RB.PTM.SuccEstab Counter Description Number of Successful PTM Setups for Cell
Description
This measurement item provides the number of successful setups of PTM MBMS RB in a cell.
Measurement point
When the RB of PTM MBMS service is successful set up ,the RNC measures the item.
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.RB.PTM.SuccEstab Feature ID WRFD-01061601 Feature Name MBMS Broadcast Mode
1.12.18.14 Mean number of PTP users in a cell of MBMS Channel
Issue 01 (2013-05-04)
1601
Counters
Counter ID 67204225 67204227 67204229 67204231 67204233 Counter Name VS.MBMS.PTP.UE.Channe l0.Mean.Cell VS.MBMS.PTP.UE.Channe l1.Mean.Cell VS.MBMS.PTP.UE.Channe l2.Mean.Cell VS.MBMS.PTP.UE.Channe l3.Mean.Cell VS.MBMS.PTP.UE.Channe l4.Mean.Cell Counter Description Mean Number of PTP Users of MBMS Channel 0 for Cell Mean Number of PTP Users of MBMS Channel 1 for Cell Mean Number of PTP Users of MBMS Channel 2 for Cell Mean Number of PTP Users of MBMS Channel 3 for Cell Mean Number of PTP Users of MBMS Channel 4 for Cell
Description
The previous measurement counter provides the mean number of UEs that subscribe to MBMS channel in PTP mode in a cell.
Measurement point
If the MBMS channel is in PTP mode, the number of cell_MBMS UEs is reported when a connected UE orders or releases the program in the cell. When the MBMS channel switches from PTM to PTP, the number of UEs that currently order the program in the cell is reported. When the MBMS channel switches from PTP to PTM, the number of UEs that order the program in PTP mode is reported as 0.
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.PTP.UE.Channe l0.Mean.Cell VS.MBMS.PTP.UE.Channe l1.Mean.Cell VS.MBMS.PTP.UE.Channe l2.Mean.Cell
Issue 01 (2013-05-04)
Feature Name MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics
1602
Counter Name VS.MBMS.PTP.UE.Channe l3.Mean.Cell VS.MBMS.PTP.UE.Channe l4.Mean.Cell
Feature Name MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics
1.12.18.15 Mean number of PTM users in a cell of MBMS Channel Counters

Counter ID 67204226 67204228 67204230 67204232 67204234 Counter Name VS.MBMS.PTM.UE.Chann el0.Mean.Cell VS.MBMS.PTM.UE.Chann el1.Mean.Cell VS.MBMS.PTM.UE.Chann el2.Mean.Cell VS.MBMS.PTM.UE.Chann el3.Mean.Cell VS.MBMS.PTM.UE.Chann el4.Mean.Cell Counter Description Mean Number of PTM Users of MBMS Channel 0 for Cell Mean Number of PTM Users of MBMS Channel 1 for Cell Mean Number of PTM Users of MBMS Channel 2 for Cell Mean Number of PTM Users of MBMS Channel 3 for Cell Mean Number of PTM Users of MBMS Channel 4 for Cell
Description
The previous measurement counter provides the mean number of UEs that subscribe to MBMS channel in PTM mode in a cell.
Measurement point
If the MBMS channel is in PTM mode, the number of cell_MBMS UEs is reported when a connected UE orders or releases the MBMS program in the cell. When the MBMS channel switches from PTP to PTM, the number of connected UEs that currently order the program in the cell is reported. When the MBMS channel switches from PTM to PTP, the number of UEs that order the program in PTM mode is reported as 0.
Formula
None
Unit
None
Related Features
Counter Name VS.MBMS.PTM.UE.Chann el0.Mean.Cell VS.MBMS.PTM.UE.Chann el1.Mean.Cell VS.MBMS.PTM.UE.Chann el2.Mean.Cell VS.MBMS.PTM.UE.Chann el3.Mean.Cell VS.MBMS.PTM.UE.Chann el4.Mean.Cell Feature ID WRFD-010665 WRFD-010665 WRFD-010665 WRFD-010665 WRFD-010665 Feature Name MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics
1.12.18.16 A PTM Channel Duration in a cell MBMS service Channel Counters

Counter ID 67204235 67204237 67204239 67204241 67204243 Counter Name VS.MBMS.PTM.Channel0. Dur.Cell VS.MBMS.PTM.Channel1. Dur.Cell VS.MBMS.PTM.Channel2. Dur.Cell VS.MBMS.PTM.Channel3. Dur.Cell VS.MBMS.PTM.Channel4. Dur.Cell Counter Description Duration of MBMS Channel 0 in PTM Mode for Cell Duration of MBMS Channel 1 in PTM Mode for Cell Duration of MBMS Channel 2 in PTM Mode for Cell Duration of MBMS Channel 3 in PTM Mode for Cell Duration of MBMS Channel 4 in PTM Mode for Cell
Description
The previous measurement counter provides the duration in which MBMS channel is in PTM mode.
Measurement point
When the MBMS channel is initially decided to be in PTM mode or switches from PTP to PTM, the system records the time as T1. When the MBMS channel stops or switches to PTP, the system records the time as T2. The difference between T1 and T2 indicates a duration in which the MBMS channel is in PTM mode. Assume that T is the difference between T1 and T2. The sum
of all the Ts in the measurement period equals the total duration in which the MBMS channel is in PTM mode in the measurement period.
Formula
None
Unit
s
Related Features
Counter Name VS.MBMS.PTM.Channel0. Dur.Cell VS.MBMS.PTM.Channel1. Dur.Cell VS.MBMS.PTM.Channel2. Dur.Cell VS.MBMS.PTM.Channel3. Dur.Cell VS.MBMS.PTM.Channel4. Dur.Cell Feature ID WRFD-010665 WRFD-010665 WRFD-010665 WRFD-010665 WRFD-010665 Feature Name MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics
1.12.18.17 A PTP Channel Duration in a cell MBMS service Channel Counters

Counter ID 67204236 67204238 67204240 67204242 67204244 Counter Name VS.MBMS.PTP.Channel0.D ur.Cell VS.MBMS.PTP.Channel1.D ur.Cell VS.MBMS.PTP.Channel2.D ur.Cell VS.MBMS.PTP.Channel3.D ur.Cell VS.MBMS.PTP.Channel4.D ur.Cell Counter Description Duration of MBMS Channel 0 in PTP Mode for Cell Duration of MBMS Channel 1 in PTP Mode for Cell Duration of MBMS Channel 2 in PTP Mode for Cell Duration of MBMS Channel 3 in PTP Mode for Cell Duration of MBMS Channel 4 in PTP Mode for Cell
Issue 01 (2013-05-04)
1605
Description
The previous measurement counter provides the duration in which MBMS channel is in PTP mode.
Measurement point
When the MBMS channel is initially decided to be in PTP mode or switches from PTM to PTP, the system records the time as T1. When the MBMS channel stops or switches to PTM, the system records the time as T2. The difference between T1 and T2 indicates a duration in which the MBMS channel is in PTP mode. Assume that T is the difference between T1 and T2. The sum of all the Ts in the measurement period equals the total duration in which the MBMS channel is in PTP mode in the measurement period.
Formula
None
Unit
s
Related Features
Counter Name VS.MBMS.PTP.Channel0.D ur.Cell VS.MBMS.PTP.Channel1.D ur.Cell VS.MBMS.PTP.Channel2.D ur.Cell VS.MBMS.PTP.Channel3.D ur.Cell VS.MBMS.PTP.Channel4.D ur.Cell Feature ID WRFD-010665 WRFD-010665 WRFD-010665 WRFD-010665 WRFD-010665 Feature Name MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics MBMS Channel Audience Rating Statistics
1.12.19 RRC Reporting Measurement per cell(MEAR.Report.Cell)

Overview
The RRC measurement reports include the following events: Events 1A, 1B, 1C, 1D related to intra-frequency measurement. Events 2D and 2F related to active set measurement. Events 4A and 4B related to traffic measurement.
Issue 01 (2013-05-04)
1606
Counters
Counter ID 67180609 Counter Name VS.RRC.MrRpt.1A Counter Description Number of Event 1A Measurement Reports for Cell Number of Event 1B Measurement Reports for Cell Number of Event 1C Measurement Reports for Cell Number of Event 1D Measurement Reports for Cell Number of Event 2D Measurement Reports for Cell Number of Event 2F Measurement Reports for Cell Number of Uplink Event 4A Measurement Reports for Cell Number of Uplink Event 4B Measurement Reports for Cell Number of Downlink Event 4A Measurement Reports for Cell Number of Downlink Event 4B Measurement Reports for Cell Average RSCP for Cell Average Ec/No for Cell Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67180610
VS.RRC.MrRpt.1B
67180611
VS.RRC.MrRpt.1C
67180612
VS.RRC.MrRpt.1D
67180613
VS.RRC.MrRpt.2D
67180614
VS.RRC.MrRpt.2F
67180615
VS.RRC.MrRpt.4A
67180616
VS.RRC.MrRpt.4B
67192652
VS.Utran.MrRpt. 4A
67192653
VS.Utran.MrRpt. 4B
73440131 73440132
VS.RRC.MrRpt.S HO.RSCP VS.RRC.MrRpt.S HO.EcNo
V900R012 V900R012
Issue 01 (2013-05-04)
1607
None
1.12.19.1 Number of Event 1A Measurement Reports Counters

Counter ID 67180609 Counter Name VS.RRC.MrRpt.1A Counter Description Number of Event 1A Measurement Reports for Cell
Description
This measurement item provides the number of event 1A measurement reports about neighboring cells from UEs to the RNC in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a MEASUREMENT REPORT message from the UE with the event type as 1A and the measurement object as neighboring cells. In this case, the RNC measures the item in the best cell that the UE camps on. Figure 1-728 Measurement reporting procedure
Issue 01 (2013-05-04)
1608
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.MrRpt.1A Feature ID WRFD-020202 WRFD-020203 Feature Name Intra RNC Soft Handover Inter RNC Soft Handover
1.12.19.2 Number of Event 1B Measurement Reports Counters

Counter ID 67180610 Counter Name VS.RRC.MrRpt.1B Counter Description Number of Event 1B Measurement Reports for Cell
Description
This measurement item provides the number of event 1B measurement reports about neighboring cells from UEs to the RNC in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a MEASUREMENT REPORT message from a UE with the event type as 1B and the measurement object as neighboring cells. In this case, the RNC measures the item in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1609
Figure 1-729 Measurement reporting procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.MrRpt.1B Feature ID WRFD-020202 WRFD-020203 Feature Name Intra RNC Soft Handover Inter RNC Soft Handover
1.12.19.3 Number of Event 1C Measurement Reports Counters

Counter ID 67180611 Counter Name VS.RRC.MrRpt.1C Counter Description Number of Event 1C Measurement Reports for Cell
Issue 01 (2013-05-04)
1610
Description
This measurement item provide the number of event 1C measurement reports about neighboring cells from UEs to the RNC in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a MEASUREMENT REPORT message from the UE with the event type as 1C and the measurement object as neighboring cells. In this case, the RNC measures the item in the best cell that the UE camps on. Figure 1-730 Measurement reporting procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.MrRpt.1C Feature ID WRFD-020202 WRFD-020203 Feature Name Intra RNC Soft Handover Inter RNC Soft Handover
Issue 01 (2013-05-04)
1611
1.12.19.4 Number of Event 1D Measurement Reports Counters

Counter ID 67180612 Counter Name VS.RRC.MrRpt.1D Counter Description Number of Event 1D Measurement Reports for Cell
Description
This measurement item provides the number of event 1D measurement reports about neighboring cells from UEs to the RNC in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a MEASUREMENT REPORT message from the UE with the event type as 1D and the measurement object as neighboring cells. In this case, the RNC measures the item in the best cell that the UE camps on. Figure 1-731 Measurement reporting procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.MrRpt.1D Feature ID WRFD-020202 WRFD-020203 Feature Name Intra RNC Soft Handover Inter RNC Soft Handover
1.12.19.5 Number of Event 2D Measurement Reports Counters

Counter ID 67180613 Counter Name VS.RRC.MrRpt.2D Counter Description Number of Event 2D Measurement Reports for Cell
Description
This measurement item provides the number of event 2D measurement reports about cells in the active set from UEs to the RNC in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a MEASUREMENT REPORT message from the UE with the event type as 2D and the measurement object as active set cells. In this case, the RNC measures the item in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1613
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.MrRpt.2D Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.19.6 Number of Event 2F Measurement Reports
Issue 01 (2013-05-04)
1614
Counters
Counter ID 67180614 Counter Name VS.RRC.MrRpt.2F Counter Description Number of Event 2F Measurement Reports for Cell
Description
This measurement item provides the number of event 2F measurement reports about cells in the active set from UEs to the RNC in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a MEASUREMENT REPORT message from the UE with the event type as 2F and the measurement object as the cells in the active set. In this case, the RNC measures the item in the best cell that the UE camps on. Figure 1-733 Measurement reporting procedure
Formula
None
Issue 01 (2013-05-04)
1615
Unit
None
Related Features
Counter Name VS.RRC.MrRpt.2F Feature ID WRFD-020302 WRFD-020304 Feature Name Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.12.19.7 Number of Uplink Event 4A Measurement Reports Counters

Counter ID 67180615 Counter Name VS.RRC.MrRpt.4A Counter Description Number of Uplink Event 4A Measurement Reports for Cell
Description
This measurement item provides the number of event 4A measurement reports about cells in the active set from UEs to the RNC in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from a UE a Measurement Report message with the event type as 4A and the measurement object as cells in the active set. In this case, the RNC measures the item in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1616
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.MrRpt.4A Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.19.8 Number of Uplink Event 4B Measurement Reports Counters

Counter ID 67180616 Counter Name VS.RRC.MrRpt.4B Counter Description Number of Uplink Event 4B Measurement Reports for Cell
1617
Issue 01 (2013-05-04)
Description
This measurement item provides the number of event 4B measurement reports about cells in the active set from UEs to the RNC in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from a UE a Measurement Report message with the event type as 4B and the measurement object as cells in the active set. In this case, the RNC measures the item in the best cell that the UE camps on. Figure 1-735 Measurement reporting procedure
Formula
None
Unit
None
Issue 01 (2013-05-04)
1618
Related Features
Counter Name VS.RRC.MrRpt.4B Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.19.9 Number of Downlink Event 4A Measurement Reports Counters

Counter ID 67192652 Counter Name VS.Utran.MrRpt.4A Counter Description Number of Downlink Event 4A Measurement Reports for Cell
Description
This measurement item provides the number of event 4A measurement reports about DL traffic of the UE from the MACD to the RNC in a cell.
Measurement point
When the RNC receives a Measurement Report message from L2 to L3, if the event type of the message is 4A and the measurement object is DL traffic of the UE, the RNC measures the item in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Name VS.Utran.MrRpt.4A Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.19.10 Number of Downlink Event 4B Measurement Reports

Counters
Counter ID 67192653 Counter Name VS.Utran.MrRpt.4B Counter Description Number of Downlink Event 4B Measurement Reports for Cell
Description
This measurement item provides the number of event 4B measurement reports about DL traffic of the UE from the MACD to the RNC in a cell.
Measurement point
When the RNC receives a Measurement Report message from L2 to L3, if the event type of the message is 4B and the measurement object is the DL traffic of the UE, the RNC measures the item in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Name VS.Utran.MrRpt.4B Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.19.11 Average RSCP for Cell Counters

Counter ID 73440131 Counter Name VS.RRC.MrRpt.SHO.RSCP Counter Description Average RSCP for Cell
Counter ID 73422195 73422194
Counter Name VS.MrRpt.Cum.SHO VS.RSCP.Cum.SHO
Counter Description Number of 1A, 1B and 1C Measure Report from UE RSCPCum
Description
This counter provides the average received signal code power (RSCP) of the common pilot channel (CPICH) reported by UEs in a cell in measurement reports triggered by event 1A, 1B, or 1C.
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC receives from a UE a MEASUREMENT REPORT message with the event type being 1A, 1B, or 1C. The RNC measures the total number of event 1A, 1B, or 1C measurement reports and the total CPICH RSCP of the cell with the best signal quality in the active set of the UEs. At the end of each measurement period, this counter is calculated by dividing the total CPICH RSCP by the total number. Note that this counter is measured in the cell in the active set. Figure 1-736 UE sends an event 1A, 1B, or 1C measurement report
Formula
VS.RRC.MrRpt.SHO.RSCP = [VS.RSCP.Cum.SHO]/[VS.MrRpt.Cum.SHO]
Unit
None
Related Features
Counter Name VS.RRC.MrRpt.SHO.RSCP Feature ID WRFD-020201 WRFD-020202 WRFD-020203 Feature Name Intra Node B Softer Handover Intra RNC Soft Handover Inter RNC Soft Handover
1.12.19.12 Average Ec/No for Cell Counters

Counter ID 73440132 Counter Name VS.RRC.MrRpt.SHO.EcNo Counter Description Average Ec/No for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73422196 73422197 Counter Name VS.EcNo.Cum.SHO VS.EcNo.MrRpt.Cum.SHO Counter Description EcNoCum VS.EcNo.MrRpt.Cum.SHO
Description
This counter provides the average Ec/No of the common pilot channel (CPICH) reported by UEs in a cell in measurement reports triggered by event 1A, 1B, or 1C. Ec/No refers to the ratio of received energy per chip to noise spectral density
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC receives from a UE a MEASUREMENT REPORT message with the event type being 1A, 1B, or 1C. The RNC measures the total number of event 1A, 1B, or 1C measurement reports and the total CPICH Ec/No of the cell with the best signal quality in the active set of the UEs. At the end of each measurement period, this counter is calculated by dividing the total CPICH Ec/No by the total number. Note that this counter is measured in the cell in the active set.
Issue 01 (2013-05-04)
1622
Figure 1-737 UE sends an event 1A, 1B, or 1C measurement report
Formula
VS.RRC.MrRpt.SHO.EcNo = [VS.EcNo.Cum.SHO]/[VS.EcNo.MrRpt.Cum.SHO]
Unit
dB
Related Features
Counter Name VS.RRC.MrRpt.SHO.EcNo Feature ID WRFD-020201 WRFD-020202 WRFD-020203 Feature Name Intra Node B Softer Handover Intra RNC Soft Handover Inter RNC Soft Handover
1.12.20 Measurement related to Paging per cell(PAGE.CELL)

Overview
This function subset mainly measures the number of paging losses due to congestion and the number of paging times in a cell. If the paged UE is in idle mode, the CELL_PCH state, or URA_PCH state, the RNC sends a PAGING TYPE 1 message on the Paging Control Channel (PCCH) to the cells in the paging
area. If the UE is in the CELL_PCH state and both the network and the UE support EPCH, the RNC sends a PAGING TYPE 2 message to the cells in the paging area.
Counters
Counter ID 67190472 Counter Name VS.RRC.Paging1.L oss.PCHCong.Cell Counter Description Number of Paging Messages Discarded Due to PCH Congestion for Cell Number of Paging Messages Sent by RNC for Cell Number of Preemptions by CS Paging due to PCH Congestion per Cell Number of Successful Preemptions by CS Paging due to PCH Congestion per Cell Number of Level-1 Paging Attempts for UEs Processing Real-Time Services in the URA_PCH State for Cell Number of Successful Level-1 Paging Attempts for UEs Processing Real-Time Services in the URA_PCH State for Cell Number of Level-1 Paging Attempts for UEs Processing NonReal-Time Services in the URA_PCH State for Cell Original Release Earlier than V900R011
67190473
VS.UTRAN.AttPag ing1 VS.RRC.Paging1.P CHCong.CSPreem ptAtt VS.RRC.Paging1.P CHCong.CSPreem ptSucc
73422072
73422073
V900R012
73424293
VS.Paging1.Att1.U RA.RealTime.Cell
V900R014
73424294
VS.Paging1.Succ1. URA.RealTime.Cel l
V900R014
73424295
VS.Paging1.Att1.U RA.NoneRealTime. Cell
V900R014
Issue 01 (2013-05-04)
1624
Counter ID 73424296
Counter Name VS.Paging1.Succ1. URA.NoneRealTim e.Cell
Counter Description Number of Successful Level-1 Paging Attempts for UEs Processing NonReal-Time Services in the URA_PCH State for Cell Number of Successful Layered Paging Attempts for UEs Processing Real-Time Services in the URA_PCH State for Cell Number of Successful Layered Paging Attempts for UEs Processing NonReal-Time Services in the URA_PCH State for Cell Number of PAGING TYPE 1 Messages Sent by the RNC to UEs in the URA_PCH State for Cell Number of CS PAGING TYPE 1 Messages Sent by the RNC to UEs in the Idle State for Cell Number of PS PAGING TYPE 1 Messages Sent by the RNC to UEs in the Idle State for Cell Number of Level-1 Paging Attempts for UEs Performing Real-Time Services in Idle Mode for Cell
73424297
VS.Paging1.TotalS ucc.URA.RealTime .Cell
V900R014
73424298
VS.Paging1.TotalS ucc.URA.NoneReal Time.Cell
V900R014
73394912
VS.UTRAN.Paging 1.Att.UraPCH
V900R014
73394913
VS.UTRAN.Paging 1.Att.Idle.CS
V900R014
73394914
VS.UTRAN.Paging 1.Att.Idle.PS
V900R014
73425838
VS.Paging1.Att1.Id le.RealTime.Cell
V900R015
Issue 01 (2013-05-04)
1625
Counter ID 73425839
Counter Name VS.Paging1.Succ1.I dle.RealTime.Cell
Counter Description Number of Successful Level-1 Paging Attempts for UEs Performing Real-Time Services in Idle Mode for Cell Number of Level-1 Paging Attempts for UEs Performing Non-Real-Time Services in Idle Mode for Cell Number of Successful Level-1 Paging Attempts for UEs Performing Non-Real-Time Services in Idle Mode for Cell Number of Times a UE Processing SMS services Attempts to Preempt Resources to Be Allocated to Other UEs When the PCH Is Congested for Cell Number of Successful Preemptions by SMS Paging due to PCH Congestion per Cell Number of ETWSrelated PAGING TYPE 1 Messages Sent in a Cell
73425840
VS.Paging1.Att1.Id le.NoneRealTime.C ell
V900R015
73425841
VS.Paging1.Succ1.I dle.NoneRealTime. Cell
V900R015
73426165
VS.RRC.Paging1.P CHCong.SMSPree mptAtt
V900R015
73426166
VS.RRC.Paging1.P CHCong.SMSPree mptSucc
V900R015
73426313
VS.UTRAN.Paging 1.Att.Etws
V900R015
None
1.12.20.1 Number of Paging Losses due to PCH Congestion
Issue 01 (2013-05-04)
1626
Counters
Counter ID 67190472 Counter Name VS.RRC.Paging1.Loss.PCH Cong.Cell Counter Description Number of Paging Messages Discarded Due to PCH Congestion for Cell
Description
This counter provides the number of losses of PAGING TYPE 1 message due to PCH congestion in a cell.
Measurement point
The measurement is triggered when the RNC discards a paging message due to PCH congestion.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Paging1.Loss.PCH Cong.Cell Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
1.12.20.2 Number of Paging Type 1 Messages Counters

Counter ID 67190473 Counter Name VS.UTRAN.AttPaging1 Counter Description Number of Paging Messages Sent by RNC for Cell
Description
This counter provides the number of paging messages of PAGING TYPE 1 sent by the RNC in a cell.
Measurement point
The measurement is triggered at point B as shown in the figure when the RNC sends a message of PAGING TYPE 1. This counter also includes the number of PAGING TYPE 1 messages retransmitted by the RNC. Figure 1-738
Formula
None
Unit
None
Related Features
Counter Name VS.UTRAN.AttPaging1 Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
1.12.20.3 Number of Preemptions by CS Paging due to PCH Congestion per Cell Counters
Counter ID 73422072 Counter Name VS.RRC.Paging1.PCHCong .CSPreemptAtt Counter Description Number of Preemptions by CS Paging due to PCH Congestion per Cell
Issue 01 (2013-05-04)
1628
Description
This counter provides the number of times that CS conversational paging preempts the resources of other paging due to PCH congestion in a cell.
Measurement point
This counter is incremented by one at point A as shown in the figure each time the CS conversational paging preempts the resources of other paging (including CN originated streaming, interactive, background and SMS paging), due to PCH congestion. Figure 1-739 Sending Procedure of PAGING TYPE 1
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Paging1.PCHCong .CSPreemptAtt Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
1.12.20.4 Number of Successful Preemptions by CS Paging due to PCH Congestion per Cell
Issue 01 (2013-05-04)
1629
Counters
Counter ID 73422073 Counter Name VS.RRC.Paging1.PCHCong .CSPreemptSucc Counter Description Number of Successful Preemptions by CS Paging due to PCH Congestion per Cell
Description
This counter provides the number of times that CS conversational paging successfully preempts the resources of other paging due to PCH congestion in a cell.
Measurement point
This counter is incremented by one at point B as shown in the figure each time the CS conversational paging successfully preempts the resources of other paging (including CN originated streaming, interactive, background and SMS paging) due to PCH congestion and is successfully sent. Figure 1-740 Sending Procedure of PAGING TYPE 1
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Paging1.PCHCong .CSPreemptSucc Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
Issue 01 (2013-05-04)
1630
1.12.20.5 Number of Level-1 Paging Attempts for UEs Processing Real-Time or NonReal-Time Services in the URA_PCH State Counters
Counter ID 73424293 Counter Name VS.Paging1.Att1.URA.Real Time.Cell Counter Description Number of Level-1 Paging Attempts for UEs Processing Real-Time Services in the URA_PCH State for Cell Number of Level-1 Paging Attempts for UEs Processing Non-Real-Time Services in the URA_PCH State for Cell
73424295
VS.Paging1.Att1.URA.Non eRealTime.Cell
Description
These counters measure the number of level-1 paging attempts for UEs processing real-time or non-real-time services in the URA_PCH state in the cells on which the UEs camped recently. These counters does not measure the number of PAGING TYPE 1 messages that the RNC sent due to system information modifications or the number of retransmitted paging messages. NOTE:Real-time services are classified into CS conversational services, PS conversational services, and streaming services, without including push to talk (PTT) services. Non-real-time services are classified into PS interactive services, PS background services, and signaling radio bearer (SRB) services.
Measurement point
The measurement is triggered at point A as shown in the figure when the RNC sends PAGING TYPE 1 messages to the cells on which the UEs in the URA_PCH state camped recently and to their neighboring cells (level-1 paging).
Issue 01 (2013-05-04)
1631
Figure 1-741 Procedure of PAGING TYPE 1
Formula
None
Unit
None
Related Features
Counter Name VS.Paging1.Att1.URA.Real Time.Cell VS.Paging1.Att1.URA.Non eRealTime.Cell Feature ID WRFD-140206 WRFD-140206 Feature Name Layered Paging in URA_PCH Layered Paging in URA_PCH
1.12.20.6 Number of Successful Level-1 Paging Attempts for UEs Processing RealTime or Non-Real-Time Services in the URA_PCH State
Issue 01 (2013-05-04)
1632
Counters
Counter ID 73424294 Counter Name VS.Paging1.Succ1.URA.Re alTime.Cell Counter Description Number of Successful Level-1 Paging Attempts for UEs Processing Real-Time Services in the URA_PCH State for Cell Number of Successful Level-1 Paging Attempts for UEs Processing Non-RealTime Services in the URA_PCH State for Cell
73424296
VS.Paging1.Succ1.URA.No neRealTime.Cell
Description
These counters measure the number of successful level-1 paging attempts for UEs processing real-time or non-real-time services in the URA_PCH state in the cells on which the UEs camped recently.
Measurement point
The measurement is triggered at point B shown in the figure when both of the following conditions are met: The RNC has sent PAGING TYPE 1 messages to the cells on which UEs in the URA_PCH state camped recently and to their neighboring cells (level-1 paging) and starts a paging response timer. Before the timer expires, the RNC receives CELL UPDATE messages with the cause value of uplinkDataTransmission or a paging response from the UEs. Figure 1-742 Procedure of PAGING TYPE 1
Issue 01 (2013-05-04)
1633
Formula
None
Unit
None
Related Features
Counter Name VS.Paging1.Succ1.URA.Re alTime.Cell VS.Paging1.Succ1.URA.No neRealTime.Cell Feature ID WRFD-140206 WRFD-140206 Feature Name Layered Paging in URA_PCH Layered Paging in URA_PCH
1.12.20.7 Number of Successful Layered Paging Attempts for UEs Processing RealTime or Non-Real-Time Services in the URA_PCH State Counters
Counter ID 73424297 Counter Name VS.Paging1.TotalSucc.URA .RealTime.Cell Counter Description Number of Successful Layered Paging Attempts for UEs Processing Real-Time Services in the URA_PCH State for Cell Number of Successful Layered Paging Attempts for UEs Processing Non-RealTime Services in the URA_PCH State for Cell
73424298
VS.Paging1.TotalSucc.URA .NoneRealTime.Cell
Description
These counters measure the number of successful layered paging attempts for UEs processing real-time or non-real-time services in the URA_PCH state in the cells on which the UEs camped recently.
Measurement point
The measurement is triggered at point B shown in the figure when the RNC has sent paging messages and receives CELL UPDATE messages with the cause value of uplinkDataTransmission or a paging response from UEs in the URA_PCH state.
Figure 1-743 Procedure of PAGING TYPE 1
Formula
None
Unit
None
Related Features
Counter Name VS.Paging1.TotalSucc.URA .RealTime.Cell VS.Paging1.TotalSucc.URA .NoneRealTime.Cell Feature ID WRFD-140206 WRFD-140206 Feature Name Layered Paging in URA_PCH Layered Paging in URA_PCH
1.12.20.8 Number of PAGING TYPE 1 Messages Sent by the RNC to UEs in the URA_PCH State
Issue 01 (2013-05-04)
1635
Counters
Counter ID 73394912 Counter Name VS.UTRAN.Paging1.Att.Ur aPCH Counter Description Number of PAGING TYPE 1 Messages Sent by the RNC to UEs in the URA_PCH State for Cell
Description
This counter measures the number of PAGING TYPE 1 messages sent by the RNC to UEs in the URA_PCH state in a cell.
Measurement point
This counter is incremented at point B as shown in the figure by one each time the RNC sends a PAGING TYPE 1 message to a UE in the URA_PCH state in the cell. This counter also includes the retransmitted PAGING TYPE 1 messages. Figure 1-744
Formula
None
Unit
None
Issue 01 (2013-05-04)
1636
Related Features
Counter Name VS.UTRAN.Paging1.Att.Ur aPCH Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
1.12.20.9 Number of CS PAGING TYPE 1 Messages Sent by the RNC to UEs in the Idle State Counters
Counter ID 73394913 Counter Name VS.UTRAN.Paging1.Att.Idl e.CS Counter Description Number of CS PAGING TYPE 1 Messages Sent by the RNC to UEs in the Idle State for Cell
Description
This counter measures the number of PAGING TYPE 1 messages sent by the RNC in the CS domain to UEs in the idle state in a cell.
Measurement point
This counter is incremented at point B as shown in the figure by one each time the RNC sends a PAGING TYPE 1 message in the CS domain to a UE in the idle state in the cell. This counter also includes the retransmitted PAGING TYPE 1 messages. Figure 1-745
Issue 01 (2013-05-04)
1637
Formula
None
Unit
None
Related Features
Counter Name VS.UTRAN.Paging1.Att.Idl e.CS Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
1.12.20.10 Number of PS PAGING TYPE 1 Messages Sent by the RNC to UEs in the Idle State Counters
Counter ID 73394914 Counter Name VS.UTRAN.Paging1.Att.Idl e.PS Counter Description Number of PS PAGING TYPE 1 Messages Sent by the RNC to UEs in the Idle State for Cell
Description
This counter measures the number of PAGING TYPE 1 messages sent by the RNC in the PS domain to UEs in the idle state in a cell.
Measurement point
This counter is incremented at point B as shown in the figure by one each time the RNC sends a PAGING TYPE 1 message in the PS domain to a UE in the idle state in the cell. This counter also includes the retransmitted PAGING TYPE 1 messages. Figure 1-746
Issue 01 (2013-05-04)
1638
Formula
None
Unit
None
Related Features
Counter Name VS.UTRAN.Paging1.Att.Idl e.PS Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
1.12.20.11 Number of Level-1 Paging Attempts for UEs Performing Real-Time or Non-Real-Time Services in Idle Mode for Cell Counters
Counter ID 73425838 Counter Name VS.Paging1.Att1.Idle.RealT ime.Cell Counter Description Number of Level-1 Paging Attempts for UEs Performing Real-Time Services in Idle Mode for Cell Number of Level-1 Paging Attempts for UEs Performing Non-Real-Time Services in Idle Mode for Cell
73425840
VS.Paging1.Att1.Idle.None RealTime.Cell
Description
These counters measure the number of level-1 paging attempts for UEs performing real-time or non-real-time services in idle mode in the last camped-on cell.They do not measure the number of PAGING TYPE 1 messages that the RNC sent due to system information modifications or the number of retransmitted paging messages. Note that real-time services are classified into CS conversational services, PS conversational services, and streaming services. Push to talk (PTT) services are not included. Non-real-time services are classified into PS interactive services, PS background services, and signaling radio bearer (SRB) services.
Measurement point
The measurement is triggered at point A shown in the figure when the RNC sends PAGING TYPE 1 messages to the last cell that a UE is camped on and to its neighboring cells. If the UE
is performing real-time services, the VS.Paging1.Att1.Idle.RealTime.Cell counter is measured in the last camped-on cell. If the UE is performing non-real-time services, the VS.Paging1.Att1.Idle.NoneRealTime.Cell counter is measured in the last camped-on cell. Figure 1-747 How a UE in idle mode responds to the PAGING TYPE 1 message
Formula
None
Unit
None
Related Features
Counter Name VS.Paging1.Att1.Idle.RealT ime.Cell VS.Paging1.Att1.Idle.None RealTime.Cell Feature ID WRFD-150205 WRFD-150205 Feature Name Layered Paging in Idle Mode Layered Paging in Idle Mode
1.12.20.12 Number of Successful Level-1 Paging Attempts for UEs Performing RealTime or Non-Real-Time Services in Idle Mode for Cell
Issue 01 (2013-05-04)
1640
Counters
Counter ID 73425839 Counter Name VS.Paging1.Succ1.Idle.Real Time.Cell Counter Description Number of Successful Level-1 Paging Attempts for UEs Performing Real-Time Services in Idle Mode for Cell Number of Successful Level-1 Paging Attempts for UEs Performing Non-RealTime Services in Idle Mode for Cell
73425841
VS.Paging1.Succ1.Idle.Non eRealTime.Cell
Description
These counters measure the number of successful level-1 paging attempts for UEs performing real-time or non-real-time services in idle mode in the last camped-on cell.
Measurement point
The measurement is triggered at point B shown in the figure when all the following conditions are met: -The RNC has sent a PAGING TYPE 1 message to the last cell that a UE is camped on and to its neighboring cells. -The RNC receives an RRC Connection Request message from the UE before the layered paging response timer expires. -The RRC Connection Request message contains any of the following cause values: Terminating Conversational Call, Terminating Streaming Call, Terminating Interactive Call, Terminating Background Call, Terminating High Priority Signalling, Terminating Low Priority Signalling, and Terminating - cause unknown. If the UE is performing real-time services, the VS.Paging1.Succ1.Idle.RealTime. Cell counter is measured in the last camped-on cell. If the UE is performing non-real-time services, the VS.Paging1.Succ1.Idle.NoneRealTime.Cell counter is measured in the last camped-on cell. Figure 1-748 How a UE in idle mode responds to the PAGING TYPE 1 message
Issue 01 (2013-05-04)
1641
Formula
None
Unit
None
Related Features
Counter Name VS.Paging1.Succ1.Idle.Real Time.Cell VS.Paging1.Succ1.Idle.Non eRealTime.Cell Feature ID WRFD-150205 WRFD-150205 Feature Name Layered Paging in Idle Mode Layered Paging in Idle Mode
1.12.20.13 Number of Times a UE Processing SMS services Attempts to Preempt Resources to Be Allocated to Other UEs When the PCH Is Congested for Cell Counters
Counter ID 73426165 Counter Name VS.RRC.Paging1.PCHCong .SMSPreemptAtt Counter Description Number of Times a UE Processing SMS services Attempts to Preempt Resources to Be Allocated to Other UEs When the PCH Is Congested for Cell
Description
This counter provides the number of times that SMS paging preempts the resources of the other paging due to PCH congestion in a cell.
Measurement point
This counter is incremented by one at point A as shown in the figure each time the SMS paging preempts the resources of other paging (including CN originated streaming, interactive and background paging), due to PCH congestion. Figure 1-749 Sending Procedure of PAGING TYPE 1
Issue 01 (2013-05-04)
1642
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Paging1.PCHCong .SMSPreemptAtt Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
1.12.20.14 Number of Successful Preemptions by SMS Paging due to PCH Congestion per Cell Counters
Counter ID 73426166 Counter Name VS.RRC.Paging1.PCHCong .SMSPreemptSucc Counter Description Number of Successful Preemptions by SMS Paging due to PCH Congestion per Cell
Description
This counter provides the number of times that SMS paging successfully preempts the resources of other paging due to PCH congestion in a cell.
Measurement point
This counter is incremented by one at point B as shown in the figure each time the SMS paging successfully preempts the resources of other paging (including CN originated streaming, interactive, and background paging) due to PCH congestion and is successfully sent. Figure 1-750 Sending Procedure of PAGING TYPE 1
Issue 01 (2013-05-04)
1643
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Paging1.PCHCong .SMSPreemptSucc Feature ID WRFD-010301 Feature Name Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
1.12.20.15 Number of ETWS-related PAGING TYPE 1 Messages Sent in a Cell Counters

Counter ID 73426313 Counter Name VS.UTRAN.Paging1.Att.Et ws Counter Description Number of ETWS-related PAGING TYPE 1 Messages Sent in a Cell
Description
This counter provides the number of PAGING TYPE 1 messages sent in a cell that carry ETWSrelated information.
Measurement point
The measurement is triggered at point A as shown in the figure when the RNC sends PAGING TYPE 1 messages that carry ETWS-related information to UEs in the specified cell. The information indicates that the paging is initiated by an ETWS warning process.
Issue 01 (2013-05-04)
1644
Figure 1-751 Message interactions for paging type 1
Formula
None
Unit
None
Related Features
Counter Name VS.UTRAN.Paging1.Att.Et ws Feature ID WRFD-150234 Feature Name Earthquake and Tsunami Warning System (ETWS)
1.12.21 Measurement by Operator for Cell(PLMN.CELL)

Overview
This function subset provides counters measured by operator in a cell.
Counters
Counter ID 73441192 Counter Name VS.LC.ULCreditU sed.Mean.PLMN0 Counter Description Average Uplink Credit Consumption of Operator0 for Cell Original Release V900R013
Issue 01 (2013-05-04)
1645
Counter ID 73441193
Counter Name VS.LC.ULCreditU sed.Mean.PLMN1 VS.LC.ULCreditU sed.Mean.PLMN2 VS.LC.ULCreditU sed.Mean.PLMN3 VS.LC.ULCreditU sed.Min.PLMN0 VS.LC.ULCreditU sed.Min.PLMN1 VS.LC.ULCreditU sed.Min.PLMN2 VS.LC.ULCreditU sed.Min.PLMN3 VS.LC.ULCreditU sed.Max.PLMN0 VS.LC.ULCreditU sed.Max.PLMN1 VS.LC.ULCreditU sed.Max.PLMN2 VS.LC.ULCreditU sed.Max.PLMN3 VS.CSLoad.Erlang .Equiv.PLMN0
Counter Description Average Uplink Credit Consumption of Operator1 for Cell Average Uplink Credit Consumption of Operator2 for Cell Average Uplink Credit Consumption of Operator3 for Cell Minimum Uplink Credit Consumption of Operator0 for Cell Minimum Uplink Credit Consumption of Operator1 for Cell Minimum Uplink Credit Consumption of Operator2 for Cell Minimum Uplink Credit Consumption of Operator3 for Cell Maximum Uplink Credit Consumption of Operator0 for Cell Maximum Uplink Credit Consumption of Operator1 for Cell Maximum Uplink Credit Consumption of Operator2 for Cell Maximum Uplink Credit Consumption of Operator3 for Cell Average Equivalent Erlangs Consumed by CS Services of Operator0 for Cell Average Equivalent Erlangs Consumed by CS Services of Operator1 for Cell
73441194
V900R013
73441195
V900R013
73423831
V900R013
73423832
V900R013
73423833
V900R013
73423834
V900R013
73423835
V900R013
73423836
V900R013
73423837
V900R013
73423838
V900R013
73441196
V900R013
73441197
VS.CSLoad.Erlang .Equiv.PLMN1
V900R013
Issue 01 (2013-05-04)
1646
Counter ID 73441198
Counter Name VS.CSLoad.Erlang .Equiv.PLMN2
Counter Description Average Equivalent Erlangs Consumed by CS Services of Operator2 for Cell Average Equivalent Erlangs Consumed by CS Services of Operator3 for Cell Average Number of Spreading Codes Occupied by Operator0 for Cell Average Number of Spreading Codes Occupied by Operator1 for Cell Average Number of Spreading Codes Occupied by Operator2 for Cell Average Number of Spreading Codes Occupied by Operator3 for Cell Maximum Number of Spreading Codes Occupied by Operator0 for Cell Maximum Number of Spreading Codes Occupied by Operator1 for Cell Maximum Number of Spreading Codes Occupied by Operator2 for Cell Maximum Number of Spreading Codes Occupied by Operator3 for Cell
73441199
VS.CSLoad.Erlang .Equiv.PLMN3
V900R013
73441200
VS.RAB.SFOccupy .PLMN0
V900R013
73441201
V900R013
73441202
V900R013
73441203
V900R013
73423839
VS.RAB.SFOccupy .MAX.PLMN0
V900R013
73423840
V900R013
73423841
V900R013
73423842
V900R013
Issue 01 (2013-05-04)
1647
Counter ID 73424840
Counter Name VS.RAB.SFOccupy .MAX.SharedOper ator0
Counter Description Maximum Number of Spreading Codes Occupied by Shared Operator0 for MOCN Cell Average Number of Spreading Codes Occupied by Shared Operator0 for MOCN Cell Maximum Number of Spreading Codes Occupied by Shared Operator1 for MOCN Cell Average Number of Spreading Codes Occupied by Shared Operator1 for MOCN Cell Maximum Number of Spreading Codes Occupied by Shared Operator2 for MOCN Cell Average Number of Spreading Codes Occupied by Shared Operator2 for MOCN Cell Maximum Number of Spreading Codes Occupied by Shared Operator3 for MOCN Cell Average Number of Spreading Codes Occupied by Shared Operator3 for MOCN Cell
73441525
VS.RAB.SFOccupy .SharedOperator0
V900R014
73424843
VS.RAB.SFOccupy .MAX.SharedOper ator1
V900R014
73441526
V900R014
73424846
V900R014
73441527
V900R014
73424849
V900R014
73441528
V900R014
None
1.12.21.1 Credit Consumption of Operator0 Counters

Counter ID 73441192 Counter Name VS.LC.ULCreditUsed.Mean .PLMN0 VS.LC.ULCreditUsed.Min. PLMN0 VS.LC.ULCreditUsed.Max. PLMN0 Counter Description Average Uplink Credit Consumption of Operator0 for Cell Minimum Uplink Credit Consumption of Operator0 for Cell Maximum Uplink Credit Consumption of Operator0 for Cell
73423831
73423835
Description
These counters provide the average, minimum, and maximum uplink credit consumption of operator0 in a cell. This counter is measured only when ICR DL Resource Demarcation is enabled.
Measurement point
The uplink credit consumption of operator0 is sampled every 5 seconds from a cell in the active set. At the end of a measurement period, the maximum and minimum uplink credit consumption is obtained. The average uplink credit consumption is obtained by dividing the accumulated value in the period by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name VS.LC.ULCreditUsed.Mean .PLMN0 VS.LC.ULCreditUsed.Min. PLMN0 VS.LC.ULCreditUsed.Max. PLMN0 Feature ID WRFD-030005 WRFD-030005 WRFD-030005 Feature Name
Issue 01 (2013-05-04)
1649

73423832
73423836
Description
Measurement point
Formula
None
Unit
None
Related Features
Issue 01 (2013-05-04)
1650

73423833
73423837
Description
Measurement point
Formula
None
Unit
None
Related Features
Issue 01 (2013-05-04)
1651

73423834
73423838
Description
Measurement point
Formula
None
Unit
None
Related Features
Issue 01 (2013-05-04)
1652
1.12.21.5 Equivalent Erlangs Consumed by CS Services of Operator0 Counters

Counter ID 73441196 Counter Name VS.CSLoad.Erlang.Equiv.P LMN0 Counter Description Average Equivalent Erlangs Consumed by CS Services of Operator0 for Cell
Description
This counter provides the average equivalent Erlangs consumed by all CS services of operator0 in a cell. This counter is measured only when ICR DL Resource Demarcation is enabled.
Measurement point
The equivalent Erlangs consumed by operator0' UEs for all CS services are sampled every 5 seconds from a cell in the active set. Each time a CS service is admitted, its rate is converted to equivalent Erlangs and equivalent Erlangs consumed by CS services of operator0 in the cell are increased. Each time a CS service is released, its rate is converted to equivalent Erlangs and equivalent Erlangs consumed by CS services of operator0 in the cell are reduced. At the end of a measurement period, the average equivalent Erlangs consumed by all CS services of operator0 are obtained by dividing the accumulated value in the period by the number of samples.
Formula
None
Unit
Erl
Related Features
Counter Name VS.CSLoad.Erlang.Equiv.P LMN0 Feature ID WRFD-030005 Feature Name
1.12.21.6 Equivalent Erlangs Consumed by CS Services of Operator1
Issue 01 (2013-05-04)
1653
Counters
Description
Measurement point
Formula
None
Unit
Erl
Related Features

Issue 01 (2013-05-04)
1654
Description
Measurement point
Formula
None
Unit
Erl
Related Features

Description
Measurement point
The equivalent Erlangs consumed by operator3' UEs for all CS services are sampled every 5 seconds from a cell in the active set. Each time a CS service is admitted, its rate is converted to
equivalent Erlangs and equivalent Erlangs consumed by CS services of operator3 in the cell are increased. Each time a CS service is released, its rate is converted to equivalent Erlangs and equivalent Erlangs consumed by CS services of operator3 in the cell are reduced. At the end of a measurement period, the average equivalent Erlangs consumed by all CS services of operator3 are obtained by dividing the accumulated value in the period by the number of samples.
Formula
None
Unit
Erl
Related Features
1.12.21.9 Number of Spreading Codes Occupied by Operator0 Counters

Counter ID 73441200 Counter Name VS.RAB.SFOccupy.PLMN 0 VS.RAB.SFOccupy.MAX.P LMN0 Counter Description Average Number of Spreading Codes Occupied by Operator0 for Cell Maximum Number of Spreading Codes Occupied by Operator0 for Cell
73423839
Description
This counter provides the average and maximum number of spreading codes occupied by operator0 in a cell. This counter is measured only when ICR DL Resource Demarcation is enabled.
Measurement point
The RNC measures this counter for each operator on a per cell basis. The number of spreading codes occupied by operator0 is sampled every 5 seconds in a measurement period. Spreading codes occupied by all R99 users of operator0 are all converted to the spreading factor of 256 and their numbers are accumulated. At the end of a measurement period, the maximum number of spreading codes occupied by operator0's R99 users is obtained. The average number of
spreading codes occupied by operator0's R99 users is obtained by dividing the accumulated value in the period by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SFOccupy.PLMN 0 VS.RAB.SFOccupy.MAX.P LMN0 Feature ID WRFD-030005 WRFD-030005 Feature Name

73423840
Description
Measurement point
The RNC measures this counter for each operator on a per cell basis. The number of spreading codes occupied by operator1 is sampled every 5 seconds in a measurement period. Spreading codes occupied by all R99 users of operator1 are all converted to the spreading factor of 256 and their numbers are accumulated. At the end of a measurement period, the maximum number of spreading codes occupied by operator1's R99 users is obtained. The average number of spreading codes occupied by operator1's R99 users is obtained by dividing the accumulated value in the period by the number of samples.
Formula
None
Unit
None
Related Features

73423841
Description
Measurement point
Formula
None
Unit
None
Related Features

73423842
Description
Measurement point
Formula
None
Unit
None
Related Features
1.12.21.13 Number of Spreading Codes Occupied by Shared Operator for MOCN Cell Counters
Counter ID 73424840 Counter Name VS.RAB.SFOccupy.MAX.S haredOperator0 Counter Description Maximum Number of Spreading Codes Occupied by Shared Operator0 for MOCN Cell Average Number of Spreading Codes Occupied by Shared Operator0 for MOCN Cell Maximum Number of Spreading Codes Occupied by Shared Operator1 for MOCN Cell Average Number of Spreading Codes Occupied by Shared Operator1 for MOCN Cell Maximum Number of Spreading Codes Occupied by Shared Operator2 for MOCN Cell
73441525
VS.RAB.SFOccupy.SharedOperator0
73424843
VS.RAB.SFOccupy.MAX.S haredOperator1
73441526
73424846
Issue 01 (2013-05-04)
1660
Counter ID 73441527
Counter Name VS.RAB.SFOccupy.SharedOperator2
Counter Description Average Number of Spreading Codes Occupied by Shared Operator2 for MOCN Cell Maximum Number of Spreading Codes Occupied by Shared Operator3 for MOCN Cell Average Number of Spreading Codes Occupied by Shared Operator3 for MOCN Cell
73424849
73441528
Description
This counter provides the R99 code resource usage for operators in an MOCN cell.
Measurement point
The RNC measures this counter for each operator on a per cell basis. The number of spreading codes occupied by operators is sampled every 5 seconds in a measurement period. Spreading codes occupied by all R99 users of operators are converted to the SF 256 and their numbers are accumulated. At the end of a measurement period, the average number of occupied spreading codes is obtained by dividing the accumulated value in the period by the number of samples. The maximum sampling value is defined as the maximum number of occupied spreading codes in the measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SFOccupy.MAX.S haredOperator0 VS.RAB.SFOccupy.SharedOperator0 VS.RAB.SFOccupy.MAX.S haredOperator1
Issue 01 (2013-05-04)
Feature Name MOCN Introduction Package MOCN Introduction Package MOCN Introduction Package
1661
Counter Name VS.RAB.SFOccupy.SharedOperator1 VS.RAB.SFOccupy.MAX.S haredOperator2 VS.RAB.SFOccupy.SharedOperator2 VS.RAB.SFOccupy.MAX.S haredOperator3 VS.RAB.SFOccupy.SharedOperator3
Feature Name MOCN Introduction Package MOCN Introduction Package MOCN Introduction Package MOCN Introduction Package MOCN Introduction Package
1.12.22 Measurements related to PTT(PTT.Cell)

Overview
This function subset includes the counters for push to talk (PTT) service establishment, complete calls, handover, and traffic. The PTT service uses half-duplex mode to provide private calls (point-to-point) and group calls (point-to-multipoint). A PTT connection is set up instantly without ringing after a subscriber simply presses a key.
Counters
Counter ID 73423555 Counter Name VS.PTT.PCH.Singl eRAB.CallReq.Suc c Counter Description Number of Successful PTT Call Initiation Attempts or Responses of UEs Using Only the PTT Service in the CELL_PCH or URA_PCH State During the State Transition from CELL_PCH/ URA_PCH to CELL_DCH for Cell Original Release V900R013
Issue 01 (2013-05-04)
1662
Counter ID 73423556
Counter Name VS.PTT.FACH.Sin gleRAB.CallReq.At t
Counter Description Number of PTT Call Initiation or Response Attempts of UEs Using Only the PTT Service in the CELL_FACH State for Cell Number of Successful PTT Call Initiation Attempts or Responses of UEs Using Only the PTT Service in the CELL_FACH State for Cell Number of Successful PTT Call Initiation Attempts or Responses of UEs Using the PTT and Other Services in the CELL_FACH State for Cell Number of Complete PTT Calls for Cell Number of RABs Abnormally Released During PTT Calls for Cell Number of Successful State Transitions from CELL_PCH/ URA_PCH to CELL_DCH After the RNC Sends a CELL UPDATE CONFIRM Message for Cell
73423557
VS.PTT.FACH.Sin gleRAB.CallReq.S ucc
V900R013
73423558
VS.PTT.FACH.Mu ltRAB.CallReq.Suc c
V900R013
73423559 73423560
VS.PTT.NormalRe l VS.PTT.RAB.Abno rmRel.DCH
V900R013 V900R013
73423561
VS.PTT.SuccP2D.F irst
V900R013
Issue 01 (2013-05-04)
1663
Counter ID 73423562
Counter Name VS.PTT.SuccP2D.S econd
Counter Description Number of Successful State Transitions from CELL_PCH/ URA_PCH to CELL_DCH After the RNC Sends Two CELL UPDATE CONFIRM Messages for Cell Number of Successful State Transitions from CELL_PCH/ URA_PCH to CELL_DCH After the RNC Sends Three CELL UPDATE CONFIRM Messages for Cell Number of Successful PTT Paging Attempts After the RNC Sends a PAGING TYPE 1 Message for Cell Number of Successful PTT Paging Attempts After the RNC Sends Two PAGING TYPE 1 Messages for Cell Number of Successful PTT Paging Attempts After the RNC Sends Three PAGING TYPE 1 Messages for Cell
73423563
VS.PTT.SuccP2D. Third
V900R013
73423564
VS.PTT.SuccPagin g.First
V900R013
73423565
VS.PTT.SuccPagin g.Second
V900R013
73423566
VS.PTT.SuccPagin g.Third
V900R013
Issue 01 (2013-05-04)
1664
Counter ID 73423609
Counter Name VS.PTT.FACH.Mu ltRAB.CallReq.Att
Counter Description Number of PTT Call Initiation or Responses Attempts of UEs Using the PTT and Other Services in the CELL_FACH State for Cell Number of Failed PTT Call Initiation Attempts or Responses of a UE in the CELL_PCH or URA_PCH State Processing Only the PTT Service During P2D Due to Congestion for Cell Number of Failed PTT Call Initiation Attempts or Responses of a UE in the CELL_FACH State Processing Only the PTT Service Due to Congestion for Cell Number of Failed PTT Call Initiation Attempts or Responses of a UE in the CELL_FACH State Processing Multiple Services Due to Congestion for Cell Number of PTT Call Initiation or Response Attempts of UEs Using Only the PTT Service in the CELL_PCH State for Cell Uplink Traffic Volume of the PTT Service
73423610
VS.PTT.PCH.Singl eRAB.CallReq.Fail .Cong
V900R013
73423611
VS.PTT.FACH.Sin gleRAB.CallReq.F ail.Cong
V900R013
73423612
VS.PTT.FACH.Mu ltRAB.CallReq.Fail .Cong
V900R013
73423619
VS.PTT.PCH.Singl eRAB.CallReq.Att
V900R013
73441168
VS.PTT.UL.Traffic
V900R013
Issue 01 (2013-05-04)
1665
Counter ID 73441169
Counter Name VS.PTT.DL.Traffic
Counter Description Downlink Traffic Volume of the PTT Service Number of Successful Serving Cell Changes of PTT Service in Soft Handover Status for Cell Number of Serving Cell Change Attempts of PTT Service in Soft Handover Status for Cell Number of Successful Hard Handovers of PTT Service for Cell Number of Hard Handover Attempts of PTT Service for Cell
73424828
VS.PTT.SHO.Serv CellChg.SuccOut
V900R014
73424829
VS.PTT.SHO.Serv CellChg.AttOut
V900R014
73424830
VS.PTT.HHO.SuccOut
V900R014
73424831
VS.PTT.HHO.AttOut
V900R014
None
1.12.22.1 Number of Successful PTT Call Initiation Attempts or Responses During a P2D Procedure for UEs Processing PTT Services Counters
Counter ID 73423555 Counter Name VS.PTT.PCH.SingleRAB.C allReq.Succ Counter Description Number of Successful PTT Call Initiation Attempts or Responses of UEs Using Only the PTT Service in the CELL_PCH or URA_PCH State During the State Transition from CELL_PCH/URA_PCH to CELL_DCH for Cell
1666
Issue 01 (2013-05-04)
Description
This counter provides the number of successful state transitions from CELL_PCH or URA_PCH to CELL_DCH, which indicates the successful PTT call initiations or responses of the UE in the CELL_PCH or URA_PCH state. The state transition is triggered by PTT data transmission. This counter is measured on a per cell basis. The counter is used with the VS.PTT.PCH.SingleRAB.CallReq.Att counter to assess the success rate of PTT call initiations or responses of a UE in the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point B as shown in Figure 1 when the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message that transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to initiate to a PTT call. A calling UE transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to initiate a PTT call if the following conditions are met: The UE has set up a PTT service. The values of the IEs "Cell update cause", "Establishment cause", and "Traffic volume indicator" contained in the CELL UPDATE message are "Uplink Data Transmission", "Originating Conversational Call", and "True", respectively. The "CS Call Type" IE is not contained in this message. Figure 1-752 PTT call normal procedure(P2D)
Issue 01 (2013-05-04)
1667
The measurement is triggered at point B as shown in Figure 2 when the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message that transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to respond to a PTT call. A called UE transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to respond a PTT call if the following conditions are met: The UE has set up a PTT service. PTT has data to be transmitted in the downlink. The value of the "Cell update cause" IE contained in the CELL UPDATE message is "paging response." Figure 1-753 PTT call normal procedure(P2D)
Formula
None
Unit
None
Issue 01 (2013-05-04)
1668
Related Features
Counter Name VS.PTT.PCH.SingleRAB.C allReq.Succ Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.2 Number of PTT Call Initiation or Response Attempts of UEs Using Only the PTT Service in the CELL_FACH State for Cell Counters
Counter ID 73423556 Counter Name VS.PTT.FACH.SingleRAB. CallReq.Att Counter Description Number of PTT Call Initiation or Response Attempts of UEs Using Only the PTT Service in the CELL_FACH State for Cell
Description
This counter provides the number of UE state transition attempts from the CELL_FACH to CELL_DCH triggered by PTT data transmission of a UE processing only the PTT service, which indicates the number of PTT call initiation or response attempts of the UE in the CELL_FACH state. This counter is measured on a per cell basis. The counter is used with the VS.PTT.FACH.SingleRAB.CallReq.Succ counter to assess the success rate of PTT call initiations or responses of a UE processing only the PTT service in the CELL_FACH state.
Measurement point
The measurement is triggered at point A as shown in Figure 1, when a UE processing only the PTT service in the CELL_FACH state transfers to CELL_DCH state triggered by an event 4A measurement report.
Issue 01 (2013-05-04)
1669
Figure 1-754 PTT call normal procedure(F2D)
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.FACH.SingleRAB. CallReq.Att Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.3 Number of Successful PTT Call Initiation Attempts or Responses of UEs Using Only the PTT Service in the CELL_FACH State for Cell
Issue 01 (2013-05-04)
1670
Counters
Counter ID 73423557 Counter Name VS.PTT.FACH.SingleRAB. CallReq.Succ Counter Description Number of Successful PTT Call Initiation Attempts or Responses of UEs Using Only the PTT Service in the CELL_FACH State for Cell
Description
This counter provides the number of successful UE state transitions from CELL_FACH to CELL_DCH triggered by PTT data transmission of a UE processing only the PTT service, which indicates the number of successful PTT call initiations or responses of the UE in the CELL_FACH state. This counter is measured on a per cell basis. The counter is used with the VS.PTT.PCH.SingleRAB.CallReq.Att counter to assess the success rate of PTT call initiations or responses of a UE processing only the PTT service in the CELL_FACH state.
Measurement point
The measurement is triggered at point B as shown in Figure 1, when the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message during the UE state transition from CELL_FACH to CELL_DCH. The UE processes only the PTT service in the CELL_FACH state. The state transition is triggered by PTT data transmission. Figure 1-755 PTT call normal procedure(P2D)
Issue 01 (2013-05-04)
1671
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.FACH.SingleRAB. CallReq.Succ Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.4 Number of Successful PTT Call Initiation Attempts or Responses of UEs Using the PTT and Other Services in the CELL_FACH State for Cell Counters
Counter ID 73423558 Counter Name VS.PTT.FACH.MultRAB.C allReq.Succ Counter Description Number of Successful PTT Call Initiation Attempts or Responses of UEs Using the PTT and Other Services in the CELL_FACH State for Cell
Description
This counter provides the number of successful UE state transitions from CELL_FACH to CELL_DCH triggered by PTT data transmission of a UE processing PTT and other services, which indicates the number of successful PTT call initiations or responses of the UE in the CELL_FACH state. This counter is measured on a per cell basis. The counter is used with the VS.PTT.FACH.MultRAB.CallReq.Att counter to assess the success rate of PTT call initiations or responses of a UE processing PTT and other services in the CELL_FACH state.
Measurement point
The measurement is triggered at point B as shown in Figure 1, when the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message during the UE state transition from CELL_FACH to CELL_DCH. The UE processes PTT and other services in the CELL_FACH state. The state transition is triggered by PTT data transmission.
Figure 1-756 PTT call normal procedure(F2D)
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.FACH.MultRAB.C allReq.Succ Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.5 Number of Complete PTT Calls for Cell Counters

Counter ID 73423559 Counter Name VS.PTT.NormalRel Counter Description Number of Complete PTT Calls for Cell
Issue 01 (2013-05-04)
1673
Description
This counter provides number of UE state transitions from CELL_DCH to another RRC connection state of a UE when data transmission ends only if the UE state transition to CELL_DCH is triggered by PTT data transmission. This counter is measured on a per cell basis. The counter is used with the VS.PTT.RAB.AbnormRel.DCH counter to assess the PTT call drop rate.
Measurement point
The measurement is triggered at point A as shown in Figure 1. When a PTT call ends, the RNC sends the UE a RADIO BEARER RECONFIGURATION message to trigger the UE state transition from CELL_DCH to another RRC connection state. When the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message, the measurement is triggered in the cell that the UE camps on if RBs are reconfigured to transfer the UE to an RRC connection state other than CELL_DCH and the current the UE state transition to CELL_DCH is initiated by a PTT call. Figure 1-757 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.NormalRel Feature ID WRFD-020134 Feature Name Push to Talk
Issue 01 (2013-05-04)
1674
1.12.22.6 Number of RABs Abnormally Released During PTT Calls for Cell Counters
Counter ID 73423560 Counter Name VS.PTT.RAB.AbnormRel.D CH Counter Description Number of RABs Abnormally Released During PTT Calls for Cell
Description
This counter provides the number of times that RABs are abnormally released after a UE state transition to CELL_DCH due to PTT data transmission, which indicates the number of PTT call drops. This counter is measured on a per cell basis. The counter is used with the VS.PTT.NormalRel counter to access the PTT call drop rate.
Measurement point
At point A shown in the following figure, when a failure occurs, the RNC sends a RAB RELEASE REQUEST message to the CN. After the RNC receives from the CN a RAB ASSIGNMENT REQUEST message containing a cause value other than normal release values (such as "User Inactivity", "Normal Release", "Successful Relocation", and "Network Optimization", for details, see 3GPP TS 25.413), the RNC sends a RAB ASSIGNMENT RESPONSE message. When this happens, this counter is measured in the best cell that the UE camps on if the UE transfers to the current CELL_DCH state due to a PTT call. Figure 1-758 RAB release procedure
At point A shown in the following figure, when a failure occurs, the RNC sends a RAB RELEASE REQUEST message to the CN. After the RNC receives from the CN an IU RELEASE
COMMAND message containing a cause value other than normal release values (such as "User Inactivity", "Normal Release", "Successful Relocation", and "Network Optimization", for details, see 3GPP TS 25.413), the RNC sends an IU RELEASE COMPLETE message. When this happens, this counter is measured in the best cell that the UE camps on if the UE transfers to the current CELL_DCH state due to a PTT call. Figure 1-759 RAB release IU REL procedure
At point A shown in the following figure, when a failure occurs, the RNC an IU RELEASE REQUEST message to the CN. After the RNC receives from the CN an IU RELEASE COMMAND message containing a cause value other than normal release values (such as "User Inactivity", "Normal Release", "Successful Relocation", and "Network Optimization", for details, see 3GPP TS 25.413), the RNC sends a IU RELEASE COMPLETE message. When this happens, this counter is measured in the best cell that the UE camps on if the UE transfers to the current CELL_DCH state due to a PTT call. Figure 1-760 Iu connection release procedure
Issue 01 (2013-05-04)
1676
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.RAB.AbnormRel.D CH Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.7 Number of Successful State Transitions from CELL_PCH/URA_PCH to CELL_DCH After the RNC Sends the CELL UPDATE CONFIRM Message for Cell Counters
Counter ID 73423561 Counter Name VS.PTT.SuccP2D.First Counter Description Number of Successful State Transitions from CELL_PCH/URA_PCH to CELL_DCH After the RNC Sends a CELL UPDATE CONFIRM Message for Cell Number of Successful State Transitions from CELL_PCH/URA_PCH to CELL_DCH After the RNC Sends Two CELL UPDATE CONFIRM Messages for Cell Number of Successful State Transitions from CELL_PCH/URA_PCH to CELL_DCH After the RNC Sends Three CELL UPDATE CONFIRM Messages for Cell
73423562
VS.PTT.SuccP2D.Second
73423563
VS.PTT.SuccP2D.Third
Description
These counters provide the number of RADIO BEARER RECONFIGURATION COMPLETE messages received by the RNC during the UE state transition from CELL_PCH or URA_PCH
to CELL_DCH triggered by a PTT call. The counters are measured based on the number of CELL UPDATE CONFIRM messages sent by the RNC. These counters are measured on a per cell basis. The counters are used to analyze the impact on PTT call setup duration caused by the UE state transition from CELL_PCH or URA_PCH to CELL_DCH. If the value of the VS.PTT.SuccP2D.Second or VS.PTT.SuccP2D.Third counter is larger than that of the VS.PTT.SuccP2D.First counter, more UEs undergo a long duration during the UE state transition. In this case, check whether the UE fails to receive the downlink signaling in time due to Uu interface abnormality.
Measurement point
The VS.PTT.SuccP2D.First counter is measured at point B as shown in Figure 1. During the UE state transition from CELL_PCH or URA_PCH to CELL_DCH triggered by a PTT call, if the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message after the RNC sends the UE a first CELL UPDATE CONFIRM message, the counter is measured in the cell that the UE camps on. Figure 1-761 VS.PTT.SuccP2D.First
The VS.PTT.SuccP2D.Second counter is measured at point B as shown in Figure 2. During the UE state transition from CELL_PCH or URA_PCH to CELL_DCH triggered by a PTT call, if the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message after the RNC sends the UE a second CELL UPDATE CONFIRM message, the counter is measured in the cell that the UE camps on.
Issue 01 (2013-05-04)
1678
Figure 1-762 VS.PTT.SuccP2D.Second
The VS.PTT.SuccP2D.Third counter is measured at point B as shown in Figure 3. During the UE state transition from CELL_PCH or URA_PCH to CELL_DCH triggered by a PTT call, if the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message after the RNC sends the UE a third CELL UPDATE CONFIRM message, the counter is measured in the cell that the UE camps on.
Issue 01 (2013-05-04)
1679
Figure 1-763 VS.PTT.SuccP2D.Third
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.SuccP2D.First VS.PTT.SuccP2D.Second VS.PTT.SuccP2D.Third Feature ID WRFD-020134 WRFD-020134 WRFD-020134 Feature Name Push to Talk Push to Talk Push to Talk
Issue 01 (2013-05-04)
1680
1.12.22.8 Number of Successful PTT Paging Attempts After the RNC Sends the PAGING TYPE 1 Message for Cell Counters
Counter ID 73423564 Counter Name VS.PTT.SuccPaging.First Counter Description Number of Successful PTT Paging Attempts After the RNC Sends a PAGING TYPE 1 Message for Cell Number of Successful PTT Paging Attempts After the RNC Sends Two PAGING TYPE 1 Messages for Cell Number of Successful PTT Paging Attempts After the RNC Sends Three PAGING TYPE 1 Messages for Cell
73423565
VS.PTT.SuccPaging.Second
73423566
VS.PTT.SuccPaging.Third
Description
These counters provide the number of CELL UPDATE messages with the cause value of "paging response" sent by the UE due to PTT paging. The counters are measured based on the number of PAGING TYPE 1 messages sent by the RNC. These counters are measured on a per cell basis. The counters are used to analyze the impact on end-to-end duration caused by paging over the Uu interface of the called UE during the PTT call setup. If the value of the VS.PTT.SuccPaging.Second or VS.PTT.SuccPaging.Third counter is larger than that of the VS.PTT.SuccPaging.First counter, more UEs undergo a long paging duration. In this case, check whether the UE fails to receive the downlink signaling in time due to Uu interface abnormality.
Measurement point
The measurement is triggered at point A as shown in Figure 1. When the RNC detects downlink PTT data transmission, it sends the UE a first PAGING TYPE 1 message. When the RNC receives a CELL UPDATE message that carries the "Cell update cause" IE with the value of "paging response", the VS.PTT.SuccPaging.First counter is measured in the cell that the UE camps on.
Issue 01 (2013-05-04)
1681
Figure 1-764 Paging procedure trigged by RNC
The measurement is triggered at point A as shown in Figure 2. When the RNC detects downlink PTT data transmission, it sends the UE a second PAGING TYPE 1 message. When the RNC receives a CELL UPDATE message that carries the "Cell update cause" IE with the value of "paging response", the VS.PTT.SuccPaging.Second counter is measured in the cell that the UE camps on. Figure 1-765 Paging procedure trigged by RNC
The measurement is triggered at point A as shown in Figure 3. When the RNC detects downlink PTT data transmission, it sends the UE a third PAGING TYPE 1 message. When the RNC receives a CELL UPDATE message that carries the "Cell update cause" IE with the value of "paging response", the VS.PTT.SuccPaging.Third counter is measured in the cell that the UE camps on.
Figure 1-766 Paging procedure trigged by RNC
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.SuccPaging.First VS.PTT.SuccPaging.Second VS.PTT.SuccPaging.Third Feature ID WRFD-020134 WRFD-020134 WRFD-020134 Feature Name Push to Talk Push to Talk Push to Talk
1.12.22.9 Number of PTT Call Initiation or Response Attempts of UEs Using the PTT and Other Services in the CELL_FACH State for Cell
Issue 01 (2013-05-04)
1683
Counters
Counter ID 73423609 Counter Name VS.PTT.FACH.MultRAB.C allReq.Att Counter Description Number of PTT Call Initiation or Responses Attempts of UEs Using the PTT and Other Services in the CELL_FACH State for Cell
Description
This counter provides the number of UE state transition attempts from the CELL_FACH to CELL_DCH that is triggered by PTT data transmission of a UE processing PTT and other services, which indicates the number of initiation or response attempts of a UE in the CELL_FACH state. This counter is measured on a per cell basis. The counter is used with the VS.PTT.FACH.MultRAB.CallReq.Succ counter to assess the success rate of PTT call initiations or responses of a UE processing PTT and other services in the CELL_FACH state.
Measurement point
The measurement is triggered at point A as shown in Figure 1 in the cell that a UE camps on, when the UE setting up multiple RABs in the CELL_FACH state transfers to CELL_DCH state. The state transition is triggered when the RNC receives an event 4A measurement report from the UE processing PTT data transmission. Figure 1-767 PTT call normal procedure(F2D)
Issue 01 (2013-05-04)
1684
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.FACH.MultRAB.C allReq.Att Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.10 Number of Failed PTT Call Initiations or Responses Due to Resource Congestion During a P2D Procedure for UEs Processing PTT Services Counters
Counter ID 73423610 Counter Name VS.PTT.PCH.SingleRAB.C allReq.Fail.Cong Counter Description Number of Failed PTT Call Initiation Attempts or Responses of a UE in the CELL_PCH or URA_PCH State Processing Only the PTT Service During P2D Due to Congestion for Cell
Description
This counter provides the number of failed UE accesses during the state transition from CELL_PCH or URA_PCH to CELL_DCH, which indicates the failed number PTT call initiations or responses of a UE in the CELL_PCH or URA_PCH state due to resource congestion. This counter is measured on a per cell basis. Failed PTT calls increased due to cell resource congestion affect user experience, which can be improved by resource utilization optimization or capacity expansion.
Measurement point
The measurement is triggered at point A as shown in Figure 1. If the UE transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to initiate a PTT call, when the UE access fails, the counter is measured in the cell that the UE camps on. A calling UE transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to initiate a PTT call if the following conditions are met: The UE has set up a PTT service. The values of the IEs "Cell update cause", "Establishment cause", and "Traffic volume indicator"
contained in the CELL UPDATE message are "uplink data transmission", "Originating Conversational Call", and "True", respectively. The "CS Call Type" IE is not contained in this message. Figure 1-768 VS.PTT.PCH.SingleRAB.CallReq.Fail.Cong
The measurement is triggered at point A as shown in Figure 2. If the UE transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to respond a PTT call, when the UE access fails, the counter is measured in the cell that the UE camps on. A called UE transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to respond a PTT call if the following conditions are met: The UE has set up a PTT service. PTT has data to be transmitted in the downlink. The value of the "Cell update cause" IE contained in the CELL UPDATE message is "paging response."
Issue 01 (2013-05-04)
1686
Figure 1-769 VS.PTT.PCH.SingleRAB.CallReq.Fail.Cong
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.PCH.SingleRAB.C allReq.Fail.Cong Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.11 Number of Failed PTT Call Initiation Attempts or Responses of a UE in the CELL_FACH State Processing Only the PTT Service Due to Congestion for Cell
Counters
Counter ID 73423611 Counter Name VS.PTT.FACH.SingleRAB. CallReq.Fail.Cong Counter Description Number of Failed PTT Call Initiation Attempts or Responses of a UE in the CELL_FACH State Processing Only the PTT Service Due to Congestion for Cell
Description
This counter provides the number of failed PTT call initiations or responses of a UE processing only the PTT service during the state transition from CELL_FACH to CELL_DCH triggered by PTT data transmission, which indicates the number of failed PTT call initiations or responses of the UE in the CELL_FACH state due to resource congestion. This counter is measured on a per cell basis. Failed PTT calls increased due to cell resource congestion affect user experience, which can be improved by resource utilization optimization or capacity expansion.
Measurement point
If the UE state transition from CELL_FACH to CELL_DCH is triggered by PTT data transmission and only the PTT service is established, when the UE access fails during the state transition, the counter is measured in the cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.FACH.SingleRAB. CallReq.Fail.Cong Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.12 Number of Failed PTT Call Initiation Attempts or Responses of a UE in the CELL_FACH State Processing Multiple Services Due to Congestion for Cell
Issue 01 (2013-05-04)
1688
Counters
Counter ID 73423612 Counter Name VS.PTT.FACH.MultRAB.C allReq.Fail.Cong Counter Description Number of Failed PTT Call Initiation Attempts or Responses of a UE in the CELL_FACH State Processing Multiple Services Due to Congestion for Cell
Description
This counter provides the number of failed PTT call initiations or responses of a UE processing PTT and other services during the state transition from CELL_FACH to CELL_DCH triggered by PTT data transmission, which indicates the number of failed PTT call initiations or responses of the UE in the CELL_FACH state due to resource congestion. This counter is measured on a per cell basis. Failed PTT calls increased due to cell resource congestion affect user experience, which can be improved by resource utilization optimization or capacity expansion.
Measurement point
If the UE state transition from CELL_FACH to CELL_DCH is triggered by PTT data transmission and PTT and other services are established, when the UE access fails during the state transition, the counter is measured in the cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.FACH.MultRAB.C allReq.Fail.Cong Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.13 Number of PTT Call Initiation Attempts or Responses During a P2D Procedure for UEs Processing PTT Services
Issue 01 (2013-05-04)
1689
Counters
Counter ID 73423619 Counter Name VS.PTT.PCH.SingleRAB.C allReq.Att Counter Description Number of PTT Call Initiation or Response Attempts of UEs Using Only the PTT Service in the CELL_PCH State for Cell
Description
This counter provides the number of state transition attempts from CELL_PCH or URA_PCH to CELL_DCH triggered by PTT data transmission, which indicates the number of initiation or response attempts of a UE. This counter is measured on a per cell basis. The counter is used with the VS.PTT.PCH.SingleRAB.CallReq.Succ counter to assess the success rate of PTT call initiations or responses of the UE in the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point B as shown in Figure 1. If the UE transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to respond a PTT call, when the RNC receives from the UE a CELL UPDATE message, the counter is measured in the cell that the UE camps on. A calling UE transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to initiate a PTT call if the following conditions are met: The UE has set up a PTT service. The values of the IEs "Cell update cause", "Establishment cause", and "Traffic volume indicator" contained in the CELL UPDATE message are "uplink data transmission", "Originating Conversational Call", and "True", respectively. The "CS Call Type" IE is not contained in the CELL UPDATE message.
Issue 01 (2013-05-04)
1690
Figure 1-770 PTT call normal procedure(P2D)
The measurement is triggered at point B as shown in Figure 2. If the UE transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to respond a PTT call, when the RNC receives from the UE a CELL UPDATE message, the counter is measured in the cell that the UE camps on. A called UE transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to respond a PTT call if the following conditions are met: The UE has set up a PTT service. PTT has data to be transmitted in the downlink. The value of the "Cell update cause" IE contained in the CELL UPDATE message is "paging response."
Issue 01 (2013-05-04)
1691
Figure 1-771 PTT call normal procedure(P2D)
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.PCH.SingleRAB.C allReq.Att Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.14 Uplink Traffic Volume of the PTT Service
Issue 01 (2013-05-04)
1692
Counters
Counter ID 73441168 Counter Name VS.PTT.UL.Traffic Counter Description Uplink Traffic Volume of the PTT Service
Description
This counter provides the uplink PTT traffic volume (not including the RLC header) at the RLC layer of cells in the active set. This counter is measured on a per cell basis. This counter can be used to assess the proportion of the PTT traffic volume for all services in a cell. To obtain the total call duration, divide the value of this counter by the uplink PTT data rate.
Measurement point
In a measurement period, the accumulated uplink PTT traffic volume (not including the RLC header) at the RLC layer in a cell is the total uplink PTT traffic volume at the RLC layer in the cell.
Formula
None
Unit
bit
Related Features
Counter Name VS.PTT.UL.Traffic Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.15 Downlink Traffic Volume of the PTT Service Counters

Counter ID 73441169 Counter Name VS.PTT.DL.Traffic Counter Description Downlink Traffic Volume of the PTT Service
Issue 01 (2013-05-04)
1693
Description
This counter provides the downlink traffic volume of PTT services at the RLC layer of cells in the active set. This counter is measured on a per cell basis. This counter can be used to assess the proportion of PTT services for all services in a cell. To obtain the total call duration, divide the value of this counter by the downlink PTT data rate.
Measurement point
In a measurement period, the accumulated downlink PTT traffic volume (not including the RLC header) at the RLC layer in a cell is the total downlink PTT traffic volume at the RLC layer in the cell.
Formula
None
Unit
bit
Related Features
Counter Name VS.PTT.DL.Traffic Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.16 Number of Successful Serving Cell Changes of PTT Service in Soft Handover Status Counters
Counter ID 73424828 Counter Name VS.PTT.SHO.ServCellChg. SuccOut Counter Description Number of Successful Serving Cell Changes of PTT Service in Soft Handover Status for Cell
Description
This counter provides the number of successful serving cell changes of a PTT UE performing a soft handover. This counter is measured on a per cell basis. The counter is used with the VS.PTT.SHO.ServCellChg.AttOut counter to assess the success rate of serving cell changes of a PTT UE.
Measurement point
This counter is measured when the RNC receives from a PTT UE a message indicating that an HSDPA or HSUPA serving cell change has completed. The measurement is triggered at point B as shown in Figure 1. The counter is measured in the original serving cell of the UE when the following conditions are met: The UE has set up PTT services and is performing a soft handover. The RNC receives from the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message in responding to the PHYSICAL CHANNEL RECONFIGURATION message sent from the RNC. The RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message to initiate an HSDPA or HSUPA serving cell (intra- or inter-RNC) change. Figure 1-772 Physical Channel Reconfiguration Procedure
The measurement is triggered at point B as shown in Figure 2. The counter is measured in the original serving cell of the UE when the following conditions are met: The UE has set up PTT services and is performing a soft handover. The RNC receives from the UE a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message in responding to the TRANSPORT CHANNEL RECONFIGURATION message sent from the RNC. The RNC sends the UE a TRANSPORT CHANNEL RECONFIGURATION message to initiate an HSDPA or HSUPA serving cell (intra- or inter-RNC) change.
Issue 01 (2013-05-04)
1695
Figure 1-773 Transport Channel Reconfiguration Procedure
The measurement is triggered at point B as shown in Figure 3. The counter is measured in the original serving cell of the UE when the following conditions are met: The UE has set up PTT services and is performing a soft handover. The RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message in responding to the RADIO BEARER RECONFIGURATION message sent from the RNC. The RNC sends the UE a RADIO BEARER RECONFIGURATION message to initiate an HSDPA or HSUPA serving cell (intraor inter-RNC) change. Figure 1-774 Radio Bearer Reconfiguration Procedure
The measurement is triggered at point B as shown in Figure 4. The counter is measured in the original serving cell of the UE when the following conditions are met: The UE has set up PTT
services and is performing a soft handover. The RNC receives from the UE an ACTIVE SET UPDATE COMPLETE message in responding to the ACTIVE SET UPDATE message sent from the RNC. The RNC sends the UE an ACTIVE SET UPDATE message to initiate an HSDPA or HSUPA serving cell (intra- or inter-RNC) change. Figure 1-775 Active Set Update Procedure
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.SHO.ServCellChg. SuccOut Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.17 Number of Serving Cell Change Attempts of PTT Service in Soft Handover Status Counters
Counter ID 73424829 Counter Name VS.PTT.SHO.ServCellChg. AttOut Counter Description Number of Serving Cell Change Attempts of PTT Service in Soft Handover Status for Cell
Issue 01 (2013-05-04)
1697
Description
This counter provides the number of cell change attempts of a PTT UE performing a soft handover. This counter is measured on a per cell basis. The counter is used with the VS.PTT.SHO.ServCellChg.SuccOut counter to assess the success rate of serving cell changes of a PTT UE.
Measurement point
This counter is measured when the RNC sends the PTT UE a message to initiate an HSDPA or HSUPA serving cell change. The measurement is triggered at point A as shown in Figure 1. The counter is measured in the original serving cell of the UE when the following conditions are met: The UE has set up PTT services and is performing a soft handover. The RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message to initiate an HSDPA or HSUPA serving cell (intra- or interRNC) change. Figure 1-776 Physical Channel Reconfiguration Procedure
The measurement is triggered at point A as shown in Figure 2. The counter is measured in the original serving cell of the UE when the following conditions are met: The UE has set up PTT services and is performing a soft handover. The RNC sends the UE a TRANSPORT CHANNEL RECONFIGURATION message to initiate an HSDPA or HSUPA serving cell (intra- or interRNC) change.
Issue 01 (2013-05-04)
1698
Figure 1-777 Transport Channel Reconfiguration Procedure
The measurement is triggered at point A as shown in Figure 3. The counter is measured in the original serving cell of the UE when the following conditions are met: The UE has set up PTT services and is performing a soft handover. The RNC sends the UE a RADIO BEARER RECONFIGURATION message to initiate an HSDPA or HSUPA serving cell (intra- or interRNC) change. Figure 1-778 Radio Bearer Reconfiguration Procedure
The measurement is triggered at point A as shown in Figure 4. The counter is measured in the original serving cell of the UE when the following conditions are met: The UE has set up PTT
services and is performing a soft handover. The RNC sends the UE an ACTIVE SET UPDATE message to initiate an HSDPA or HSUPA serving cell (intra- or inter-RNC) change. Figure 1-779 Active Set Update Procedure
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.SHO.ServCellChg. AttOut Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.18 Number of Successful Hard Handovers of PTT Service Counters

Counter ID 73424830 Counter Name VS.PTT.HHO.SuccOut Counter Description Number of Successful Hard Handovers of PTT Service for Cell
Issue 01 (2013-05-04)
1700
Description
This counter provides the number of successful hard handovers of a PTT UE, including intrafrequency, inter-frequency, intra-RNC, and inter-RNC hard handovers. This counter is measured on a per cell basis. The counter is used with the VS.PTT.HHO.AttOut counter to assess the success rate of hard handovers of a PTT UE.
Measurement point
This counter is measured when the RNC receives from the PTT UE a message indicating that a hard handover has completed. The measurement is triggered at point B as shown in Figure 1. The counter is measured in the best cell before the hard handover when the following conditions are met: The UE has set up PTT services. The RNC receives from the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message in responding to the PHYSICAL CHANNEL RECONFIGURATION message sent from the RNC. The RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message to initiate a hard handover (including intra- and inter-frequency and intra- and inter-RNC hard handovers). Figure 1-780 Physical Channel reconfiguration procedure
The measurement is triggered at point B as shown in Figure 2. The counter is measured in the best cell before the hard handover when the following conditions are met: The UE has set up PTT services. The RNC receives from the UE a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message in responding to the TRANSPORT CHANNEL RECONFIGURATION message sent from the RNC. The RNC sends the UE a TRANSPORT CHANNEL RECONFIGURATION message to initiate a hard handover (including intra- and inter-frequency and intra- and inter-RNC hard handovers).
Issue 01 (2013-05-04)
1701
Figure 1-781 Transport Channel Reconfiguration procedure
The measurement is triggered at point B as shown in Figure 3. The counter is measured in the best cell before the hard handover when the following conditions are met: The UE has set up PTT services. The RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message in responding to the RADIO BEARER RECONFIGURATION message sent from the RNC. The RNC sends the UE a RADIO BEARER RECONFIGURATION message to initiate a hard handover (including intra- and inter-frequency and intra- and interRNC hard handovers). Figure 1-782 RB reconfiguration procedure
The measurement is triggered at point B as shown in Figure 4. The counter is measured in the best cell before the hard handover when the following conditions are met: The UE has set up
PTT services. The RNC receives from the UE a RADIO BEARER SETUP COMPLETE message in responding to the RADIO BEARER SETUP message sent from the RNC. The RNC sends the UE a RADIO BEARER SETUP message to initiate a hard handover (including intraand inter-frequency and intra- and inter-RNC hard handovers). Figure 1-783 Radio Bearer Setup procedure
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.HHO.SuccOut Feature ID WRFD-020134 Feature Name Push to Talk
1.12.22.19 Number of Hard Handover Attempts of PTT Service
Issue 01 (2013-05-04)
1703
Counters
Counter ID 73424831 Counter Name VS.PTT.HHO.AttOut Counter Description Number of Hard Handover Attempts of PTT Service for Cell
Description
This counter provides the number of hard handover attempts of a PTT UE, including intra- and inter-frequency and intra- and inter-RNC hard handovers. This counter is measured on a per cell basis. The counter is used with the VS.PTT.HHO.SuccOut counter to assess the success rate of hard handovers of a PTT UE.
Measurement point
This counter is measured when the RNC sends the PTT UE a message to initiate a hard handover. The measurement is triggered at point A as shown in Figure 1. The counter is measured in the best cell before the hard handover when the following conditions are met: The UE has set up PTT services. The RNC receives from the UE a PHYSICAL CHANNEL RECONFIGURATION message to initiate a hard handover (including intra- and inter-frequency and intra- and inter-RNC hard handovers). Figure 1-784 Physical Channel reconfiguration procedure
The measurement is triggered at point A as shown in Figure 2. The counter is measured in the best cell before the hard handover when the following conditions are met: The UE has set up PTT services. The RNC receives from the UE a TRANSPORT CHANNEL
RECONFIGURATION message to initiate a hard handover (including intra- and inter-frequency and intra- and inter-RNC hard handovers). Figure 1-785 Transport Channel Reconfiguration procedure
The measurement is triggered at point A as shown in Figure 3. The counter is measured in the best cell before the hard handover when the following conditions are met: The UE has set up PTT services. The RNC receives from the UE a RADIO BEARER RECONFIGURATION message to initiate a hard handover (including intra- and inter-frequency and intra- and interRNC hard handovers). Figure 1-786 RB reconfiguration procedure
Issue 01 (2013-05-04)
1705
The measurement is triggered at point A as shown in Figure 4. The counter is measured in the best cell before the hard handover when the following conditions are met: The UE has set up PTT services. The RNC receives from the UE a RADIO BEARER SETUP message to initiate a hard handover (including intra- and inter-frequency and intra- and inter-RNC hard handovers). Figure 1-787 Radio Bearer Setup procedure
Formula
None
Unit
None
Related Features
Counter Name VS.PTT.HHO.AttOut Feature ID WRFD-020134 Feature Name Push to Talk
1.12.23 Measurement related to QOS per cell(QOS.Cell)

Overview
This function subset contains the following contents:1)Delay from RRC establishment to completion of RAB establishment.2)Delay of service establishment by service types and CN domains.3)Mean throughput count by user class and HSDPA download throughput.4)Mean throughput count by user class and HSUPA upload throughput.
Counters
Counter ID 67195972 Counter Name VS.AMR.Estab.Ma xTime Counter Description Maximum Delay Between RRC Connection Establishment and AMR RAB Establishment Completion for Cell Mean Delay Between RRC Connection Establishment and AMR RAB Establishment Completion for Cell Minimum Delay Between RRC Connection Establishment and AMR RAB Establishment Completion for Cell Maximum Delay Between RRC Connection Establishment and 64kbit/s CS RAB Establishment Completion for Cell Mean Delay Between RRC Connection Establishment and 64kbit/s CS RAB Establishment Completion for Cell Minimum Delay Between RRC Connection Establishment and 64kbit/s CS RAB Establishment Completion for Cell Original Release Earlier than V900R011
67204785
VS.AMR.Estab.Me anTime
67195973
VS.AMR.Estab.Mi nTime
67195976
VS.CS64.Estab.Ma xTime
67204786
VS.CS64.Estab.Me anTime
67195977
VS.CS64.Estab.Mi nTime
Issue 01 (2013-05-04)
1707
Counter ID 67195980
Counter Name VS.PSR99.Estab.M axTime
Counter Description Maximum Delay Between RRC Connection Establishment and PS R99 RAB Establishment Completion for Cell Mean Delay Between RRC Connection Establishment and PS R99 RAB Establishment Completion for Cell Minimum Delay Between RRC Connection Establishment and PS R99 RAB Establishment Completion for Cell Maximum Delay Between RRC Connection Establishment and HSDPA RAB Establishment Completion for Cell Mean Delay Between RRC Connection Establishment and HSDPA RAB Establishment Completion for Cell Minimum Delay Between RRC Connection Establishment and HSDPA RAB Establishment Completion for Cell
67204787
VS.PSR99.Estab.M eanTime
67195981
VS.PSR99.Estab.M inTime
67195984
VS.HSDPA.Estab. MaxTime
67204788
VS.HSDPA.Estab. MeanTime
67195985
VS.HSDPA.Estab. MinTime
Issue 01 (2013-05-04)
1708
Counter ID 67195988
Counter Name VS.HSUPA.Estab. MaxTime
Counter Description Maximum Delay Between RRC Connection Establishment and HSUPA RAB Establishment Completion for Cell Mean Delay Between RRC Connection Establishment and HSUPA RAB Establishment Completion for Cell Minimum Delay Between RRC Connection Establishment and HSUPA RAB Establishment Completion for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 0 Kbit/s and 32 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 32 Kbit/s and 64 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 64 Kbit/s and 256 Kbit/s for Cell
67204789
VS.HSUPA.Estab. MeanTime
67195989
VS.HSUPA.Estab. MinTime
67196050
VS.HSDPA.Golden BeChThroughput.0
67196051
67196052
Issue 01 (2013-05-04)
1709
Counter ID 67196053
Counter Name VS.HSDPA.Golden BeChThroughput.3
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 256 Kbit/s and 512 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 512 Kbit/s and 768 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 768 Kbit/s and 1024 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 1024 Kbit/s and 1536 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 1536 Kbit/s and 2048 Kbit/s for Cell
67196054
67196055
67196056
67196057
Issue 01 (2013-05-04)
1710
Counter ID 67196058
Counter Name VS.HSDPA.Golden BeChThroughput.8
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 2048 Kbit/s and 3072 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 3072 Kbit/s and 4096 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 4096 Kbit/s and 6144 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 6144 Kbit/s and 8192 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 8192 Kbit/s and 12288 Kbit/s for Cell
67196059
67196060
VS.HSDPA.Golden BeChThroughput. 10
67196061
67196062
Issue 01 (2013-05-04)
1711
Counter ID 67196063
Counter Name VS.HSDPA.Golden BeChThroughput. 13
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Greater Than 12288 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 0 Kbit/s and 32 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 32 Kbit/s and 64 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 64 Kbit/s and 256 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 256 Kbit/s and 512 Kbit/s for Cell
67196064
VS.HSDPA.SilverBeChThroughput.0
67196065
67196066
67196067
Issue 01 (2013-05-04)
1712
Counter ID 67196068
Counter Name VS.HSDPA.SilverBeChThroughput.4
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 512 Kbit/s and 768 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 768 Kbit/s and 1024 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 1024 Kbit/s and 1536 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 1536 Kbit/s and 2048 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 2048 Kbit/s and 3072 Kbit/s for Cell
67196069
67196070
67196071
67196072
Issue 01 (2013-05-04)
1713
Counter ID 67196073
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 3072 Kbit/s and 4096 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 4096 Kbit/s and 6144 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 6144 Kbit/s and 8192 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 8192 Kbit/s and 12288 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Greater Than 12288 Kbit/s for Cell
67196074
VS.HSDPA.SilverBeChThroughput. 10
67196075
67196076
67196077
Issue 01 (2013-05-04)
1714
Counter ID 67196078
Counter Name VS.HSDPA.Copper BeChThroughput.0
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 0 Kbit/s and 32 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 32 Kbit/s and 64 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 64 Kbit/s and 256 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 256 Kbit/s and 512 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 512 Kbit/s and 768 Kbit/s for Cell
67196079
VS.HSDPA.Copper BeChThroughput.1
67196080
67196081
67196082
Issue 01 (2013-05-04)
1715
Counter ID 67196083
Counter Name VS.HSDPA.Copper BeChThroughput.5
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 768 Kbit/s and 1024 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 1024 Kbit/s and 1536 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 1536 Kbit/s and 2048 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 2048 Kbit/s and 3072 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 3072 Kbit/s and 4096 Kbit/s for Cell
67196084
67196085
67196086
67196087
Issue 01 (2013-05-04)
1716
Counter ID 67196088
Counter Name VS.HSDPA.Copper BeChThroughput. 10
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 4096 Kbit/s and 6144 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 6144 Kbit/s and 8192 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 8192 Kbit/s and 12288 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Greater Than 12288 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 0 Kbit/s and 32 Kbit/s for Cell
67196089
VS.HSDPA.Copper BeChThroughput. 11
67196090
67196091
67196092
VS.HSUPA.Golden BeChThroughput.0
Issue 01 (2013-05-04)
1717
Counter ID 67196093
Counter Name VS.HSUPA.Golden BeChThroughput.1
Counter Description Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 32 Kbit/s and 64 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 64 Kbit/s and 256 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 256 Kbit/s and 512 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 512 Kbit/s and 768 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 768 Kbit/s and 1024 Kbit/s for Cell
67196094
67196095
67196096
67196097
Issue 01 (2013-05-04)
1718
Counter ID 67196098
Counter Name VS.HSUPA.Golden BeChThroughput.6
Counter Description Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 1024 Kbit/s and 1536 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 1536 Kbit/s and 2048 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 2048 Kbit/s and 3072 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 3072 Kbit/s and 4096 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Greater Than 4096 Kbit/s for Cell
67196099
67196100
67196101
67196102
VS.HSUPA.Golden BeChThroughput. 10
Issue 01 (2013-05-04)
1719
Counter ID 67196103
Counter Name VS.HSUPA.SilverBeChThroughput.0
Counter Description Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 0 Kbit/s and 32 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 32 Kbit/s and 64 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 64 Kbit/s and 256 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 256 Kbit/s and 512 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 512 Kbit/s and 768 Kbit/s for Cell
67196104
VS.HSUPA.SilverBeChThroughput.1
67196105
67196106
67196107
Issue 01 (2013-05-04)
1720
Counter ID 67196108
Counter Description Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 768 Kbit/s and 1024 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 1024 Kbit/s and 1536 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 1536 Kbit/s and 2048 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 2048 Kbit/s and 3072 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 3072 Kbit/s and 4096 Kbit/s for Cell
67196109
67196110
67196111
67196112
Issue 01 (2013-05-04)
1721
Counter ID 67196113
Counter Name VS.HSUPA.SilverBeChThroughput. 10
Counter Description Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Greater Than 4096 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 0 Kbit/s and 32 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 32 Kbit/s and 64 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 64 Kbit/s and 256 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 256 Kbit/s and 512 Kbit/s for Cell
67196114
VS.HSUPA.Copper BeChThroughput.0
67196115
67196116
67196117
Issue 01 (2013-05-04)
1722
Counter ID 67196118
Counter Name VS.HSUPA.Copper BeChThroughput.4
Counter Description Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 512 Kbit/s and 768 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 768 Kbit/s and 1024 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 1024 Kbit/s and 1536 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 1536 Kbit/s and 2048 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 2048 Kbit/s and 3072 Kbit/s for Cell
67196119
67196120
67196121
67196122
Issue 01 (2013-05-04)
1723
Counter ID 67196123
Counter Name VS.HSUPA.Copper BeChThroughput.9
Counter Description Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 3072 Kbit/s and 4096 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Greater Than 4096 Kbit/s for Cell Maximum Service Setup Duration on an ERACH for Cell Average Service Setup Duration on an ERACH for Cell Minimum Service Setup Duration on an ERACH for Cell Maximum Service Setup Duration on an EFACH for Cell Average Service Setup Duration on an EFACH for Cell Minimum Service Setup Duration on an EFACH for Cell
67196124
VS.HSUPA.Copper BeChThroughput. 10
73423349
VS.ERACH.Estab. MaxTime VS.ERACH.Estab. MeanTime VS.ERACH.Estab. MinTime VS.EFACH.Estab. MaxTime VS.EFACH.Estab. MeanTime VS.EFACH.Estab. MinTime
V900R013
73441136
V900R013
73423352
V900R013
73423353
V900R013
73441137
V900R013
73423356
V900R013
None
1.12.23.1 Delay of Different Services
Issue 01 (2013-05-04)
1724
Counters
Counter ID 67204785 Counter Name VS.AMR.Estab.MeanTime Counter Description Mean Delay Between RRC Connection Establishment and AMR RAB Establishment Completion for Cell Maximum Delay Between RRC Connection Establishment and AMR RAB Establishment Completion for Cell Minimum Delay Between RRC Connection Establishment and AMR RAB Establishment Completion for Cell Maximum Delay Between RRC Connection Establishment and 64kbit/s CS RAB Establishment Completion for Cell Mean Delay Between RRC Connection Establishment and 64kbit/s CS RAB Establishment Completion for Cell Minimum Delay Between RRC Connection Establishment and 64kbit/s CS RAB Establishment Completion for Cell Maximum Delay Between RRC Connection Establishment and PS R99 RAB Establishment Completion for Cell Mean Delay Between RRC Connection Establishment and PS R99 RAB Establishment Completion for Cell
67195972
VS.AMR.Estab.MaxTime
67195973
VS.AMR.Estab.MinTime
67195976
VS.CS64.Estab.MaxTime
67204786
VS.CS64.Estab.MeanTime
67195977
VS.CS64.Estab.MinTime
67195980
VS.PSR99.Estab.MaxTime
67204787
VS.PSR99.Estab.MeanTime
Issue 01 (2013-05-04)
1725
Counter ID 67195981
Counter Name VS.PSR99.Estab.MinTime
Counter Description Minimum Delay Between RRC Connection Establishment and PS R99 RAB Establishment Completion for Cell Maximum Delay Between RRC Connection Establishment and HSDPA RAB Establishment Completion for Cell Mean Delay Between RRC Connection Establishment and HSDPA RAB Establishment Completion for Cell Minimum Delay Between RRC Connection Establishment and HSDPA RAB Establishment Completion for Cell Maximum Delay Between RRC Connection Establishment and HSUPA RAB Establishment Completion for Cell Mean Delay Between RRC Connection Establishment and HSUPA RAB Establishment Completion for Cell Minimum Delay Between RRC Connection Establishment and HSUPA RAB Establishment Completion for Cell
67195984
VS.HSDPA.Estab.MaxTime
67204788
VS.HSDPA.Estab.MeanTime
67195985
VS.HSDPA.Estab.MinTime
67195988
VS.HSUPA.Estab.MaxTime
67204789
VS.HSUPA.Estab.MeanTime
67195989
VS.HSUPA.Estab.MinTime
Issue 01 (2013-05-04)
1726
Counter ID 67195974
Counter Name VS.AMR.Estab.Cum
Counter Description Cumulative Delay Between RRC Connection Establishment and AMR RAB Establishment Completion for Cell Number of Samples of Accumulative Delay Between RRC Connection Establishment and AMR RAB Establishment Completion for Cell Cumulative Delay Between RRC Connection Establishment and 64kbit/s CS RAB Establishment Completion for Cell Number of Samples of Accumulative Delay Between RRC Connection Establishment and 64kbit/s CS RAB Establishment Completion for Cell Cumulative Delay Between RRC Connection Establishment and HSDPA RAB Establishment Completion for Cell Number of Samples of Accumulative Delay Between RRC Connection Establishment and HSDPA RAB Establishment Completion for Cell Cumulative Delay Between RRC Connection Establishment and HSUPA RAB Establishment Completion for Cell Number of Samples of Cumulative Delay Between RRC Connection Establishment and HSUPA RAB Establishment Completion for Cell
67195975
VS.AMR.Estab.Sample
67195978
VS.CS64.Estab.Cum
67195979
VS.CS64.Estab.Sample
67195986
VS.HSDPA.Estab.Cum
67195987
VS.HSDPA.Estab.Sample
67195990
VS.HSUPA.Estab.Cum
67195991
VS.HSUPA.Estab.Sample
Issue 01 (2013-05-04)
1727
Counter ID 67195982
Counter Name VS.PSR99.Estab.Cum
Counter Description Cumulative Delay Between RRC Connection Establishment and PS R99 RAB Establishment Completion for Cell Number of Samples of Accumulative Delay Between RRC Connection Establishment and PS R99 RAB Establishment Completion for Cell
67195983
VS.PSR99.Estab.Sample
Description
These counters provide the maximum, average, and minimum durations when services are established in the best cell based on the CN domain and service type. The durations cover the time starting from the RRC CONNECTION REQUEST message to the first RAB ASSIGNMENT RESPONSE message. For DC-HSUPA users, the corresponding counter is measured only in the primary cell. The counters VS.AMR.Estab.MeanTime, VS.AMR.Estab.MaxTime and VS.AMR.Estab.MinTime are measured for narrowband and wideband AMR services.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an RRC CONNECTION REQUEST message, the RNC records the time T1 at point A. When the RNC receives from the UE a RADIO BEARER SETUP COMPLETE message and sends a RAB ASSIGNMENT RESPONSE message to the CN, the RNC records the time T2 at point B. Assume that deltaT is the duration of this service establishment, it is calculated as follows: deltaT = T2-T1. The RNC takes samples of service establishment durations every 5 seconds in a measurement period. At the end of a measurement period, the RNC obtains the average duration by dividing the accumulated number by the sampling times. The maximum and minimum numbers among all sampling points in a measurement period are the maximum and minimum durations for establishing a service, respectively.
Issue 01 (2013-05-04)
1728
Figure 1-788 RAB establishment flow
Formula
VS.AMR.Estab.MeanTime = [VS.AMR.Estab.Cum]/[VS.AMR.Estab.Sample] VS.CS64.Estab.MeanTime = [VS.CS64.Estab.Cum]/[VS.CS64.Estab.Sample] VS.PSR99.Estab.MeanTime = [VS.PSR99.Estab.Cum]/[VS.PSR99.Estab.Sample] VS.HSDPA.Estab.MeanTime = [VS.HSDPA.Estab.Cum]/[VS.HSDPA.Estab.Sample] VS.HSUPA.Estab.MeanTime = [VS.HSUPA.Estab.Cum]/[VS.HSUPA.Estab.Sample]
Unit
ms
Related Features
Counter Name VS.AMR.Estab.MeanTime VS.AMR.Estab.MaxTime VS.AMR.Estab.MinTime VS.CS64.Estab.MaxTime VS.CS64.Estab.MeanTime
Issue 01 (2013-05-04)
Feature Name Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class
1729
Counter Name VS.CS64.Estab.MinTime VS.PSR99.Estab.MaxTime
Feature Name Conversational QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Interactive and Background Traffic Class on HSDPA Streaming Traffic Class on HSDPA
VS.PSR99.Estab.MeanTime
WRFD-010510
VS.PSR99.Estab.MinTime
WRFD-010510
VS.HSDPA.Estab.MaxTime
WRFD-01061008 WRFD-010630
VS.HSDPA.Estab.MeanTime
WRFD-01061008 WRFD-010630
Interactive and Background Traffic Class on HSDPA Streaming Traffic Class on HSDPA
VS.HSDPA.Estab.MinTime
WRFD-01061008 WRFD-010630
Interactive and Background Traffic Class on HSDPA Streaming Traffic Class on HSDPA
VS.HSUPA.Estab.MaxTime
WRFD-01061206 WRFD-010632
Interactive and Background Traffic Class on HSUPA Streaming Traffic Class on HSUPA
VS.HSUPA.Estab.MeanTime
WRFD-01061206 WRFD-010632
VS.HSUPA.Estab.MinTime
WRFD-01061206 WRFD-010632
1.12.23.2 Counters Related to the Number of Times that DL Throughput of HSDPA Services Within Each Range
Counters
Counter ID 67196050 Counter Name VS.HSDPA.GoldenBeChThroughput.0 Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 0 Kbit/s and 32 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 32 Kbit/s and 64 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 64 Kbit/s and 256 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 256 Kbit/s and 512 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 512 Kbit/s and 768 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 768 Kbit/s and 1024 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 1024 Kbit/s and 1536 Kbit/s for Cell
67196051
VS.HSDPA.GoldenBeChThroughput.1
67196052
67196053
67196054
67196055
67196056
Issue 01 (2013-05-04)
1731
Counter ID 67196057
Counter Name VS.HSDPA.GoldenBeChThroughput.7
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 1536 Kbit/s and 2048 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 2048 Kbit/s and 3072 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 3072 Kbit/s and 4096 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 4096 Kbit/s and 6144 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 6144 Kbit/s and 8192 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Between 8192 Kbit/s and 12288 Kbit/ s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Golden BE Services Greater Than 12288 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 0 Kbit/s and 32 Kbit/s for Cell
1732
67196058
67196059
67196060
67196061
67196062
67196063
67196064
Issue 01 (2013-05-04)
Counter ID 67196065
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 32 Kbit/s and 64 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 64 Kbit/s and 256 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 256 Kbit/s and 512 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 512 Kbit/s and 768 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 768 Kbit/s and 1024 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 1024 Kbit/s and 1536 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 1536 Kbit/s and 2048 Kbit/s for Cell
67196066
67196067
67196068
67196069
67196070
67196071
Issue 01 (2013-05-04)
1733
Counter ID 67196072
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 2048 Kbit/s and 3072 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 3072 Kbit/s and 4096 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 4096 Kbit/s and 6144 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 6144 Kbit/s and 8192 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Between 8192 Kbit/s and 12288 Kbit/ s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Silver BE Services Greater Than 12288 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 0 Kbit/s and 32 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 32 Kbit/s and 64 Kbit/s for Cell
1734
67196073
67196074
67196075
67196076
67196077
67196078
VS.HSDPA.CopperBeChThroughput.0
67196079
Issue 01 (2013-05-04)
Counter ID 67196080
Counter Name VS.HSDPA.CopperBeChThroughput.2
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 64 Kbit/s and 256 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 256 Kbit/s and 512 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 512 Kbit/s and 768 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 768 Kbit/s and 1024 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 1024 Kbit/s and 1536 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 1536 Kbit/s and 2048 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 2048 Kbit/s and 3072 Kbit/s for Cell
67196081
67196082
67196083
67196084
67196085
67196086
Issue 01 (2013-05-04)
1735
Counter ID 67196087
Counter Name VS.HSDPA.CopperBeChThroughput.9
Counter Description Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 3072 Kbit/s and 4096 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 4096 Kbit/s and 6144 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 6144 Kbit/s and 8192 Kbit/s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Between 8192 Kbit/s and 12288 Kbit/ s for Cell Number of Times that Average DL Throughput of MAC-d Flow of HSDPA Bronze BE Services Greater Than 12288 Kbit/s for Cell
67196088
67196089
67196090
67196091
Description
These counters provide the number of times that the average downlink throughput of the MACd flow carrying BE services at the RCL layer falls in the corresponding range based on the level of the service in an HSDPA serving cell. For DC-HSDPA users, these counters are measured only in the primary cell based on the total throughput on the primary and secondary carriers. These counters are measured only when the SPI measure function is activated using the SET UDPUCFGDATA command with CellCountersMeasOBJCtrlSwitch set to Qos or QosAndSpi.
Measurement point
In an HSDPA serving cell, the RNC takes samples of the average downlink throughput (the RLC header and retransmitted data are not measured) of the MAC-d flow carrying BE services at the RLC layer for gold, silver, and copper users every 20 seconds. When the throughput falls in a predefined range, the corresponding counter is incremented by one. At the end of a measurement period, the value of each counter is obtained.
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.GoldenBeChThroughput.0 VS.HSDPA.GoldenBeChThroughput.1 VS.HSDPA.GoldenBeChThroughput.2 VS.HSDPA.GoldenBeChThroughput.3 VS.HSDPA.GoldenBeChThroughput.4 VS.HSDPA.GoldenBeChThroughput.5 VS.HSDPA.GoldenBeChThroughput.6 VS.HSDPA.GoldenBeChThroughput.7 VS.HSDPA.GoldenBeChThroughput.8 VS.HSDPA.GoldenBeChThroughput.9 VS.HSDPA.GoldenBeChThroughput.10 VS.HSDPA.GoldenBeChThroughput.11 VS.HSDPA.GoldenBeChThroughput.12 VS.HSDPA.GoldenBeChThroughput.13 VS.HSDPA.SilverBeChThroughput.0 Feature ID WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 Feature Name Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA
Issue 01 (2013-05-04)
1737
Counter Name VS.HSDPA.SilverBeChThroughput.1 VS.HSDPA.SilverBeChThroughput.2 VS.HSDPA.SilverBeChThroughput.3 VS.HSDPA.SilverBeChThroughput.4 VS.HSDPA.SilverBeChThroughput.5 VS.HSDPA.SilverBeChThroughput.6 VS.HSDPA.SilverBeChThroughput.7 VS.HSDPA.SilverBeChThroughput.8 VS.HSDPA.SilverBeChThroughput.9 VS.HSDPA.SilverBeChThroughput.10 VS.HSDPA.SilverBeChThroughput.11 VS.HSDPA.SilverBeChThroughput.12 VS.HSDPA.SilverBeChThroughput.13 VS.HSDPA.CopperBeChThroughput.0 VS.HSDPA.CopperBeChThroughput.1 VS.HSDPA.CopperBeChThroughput.2 VS.HSDPA.CopperBeChThroughput.3 VS.HSDPA.CopperBeChThroughput.4 VS.HSDPA.CopperBeChThroughput.5
Feature Name Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA
Issue 01 (2013-05-04)
1738
Counter Name VS.HSDPA.CopperBeChThroughput.6 VS.HSDPA.CopperBeChThroughput.7 VS.HSDPA.CopperBeChThroughput.8 VS.HSDPA.CopperBeChThroughput.9 VS.HSDPA.CopperBeChThroughput.10 VS.HSDPA.CopperBeChThroughput.11 VS.HSDPA.CopperBeChThroughput.12 VS.HSDPA.CopperBeChThroughput.13
Feature Name Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA
1.12.23.3 Counters Related to the Number of Times that UL Throughput of HSUPA Services Within Each Range Counters
Counter ID 67196092 Counter Name VS.HSUPA.GoldenBeChThroughput.0 Counter Description Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 0 Kbit/s and 32 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 32 Kbit/s and 64 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 64 Kbit/s and 256 Kbit/s for Cell
67196093
VS.HSUPA.GoldenBeChThroughput.1
67196094
Issue 01 (2013-05-04)
1739
Counter ID 67196095
Counter Name VS.HSUPA.GoldenBeChThroughput.3
Counter Description Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 256 Kbit/s and 512 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 512 Kbit/s and 768 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 768 Kbit/s and 1024 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 1024 Kbit/s and 1536 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 1536 Kbit/s and 2048 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 2048 Kbit/s and 3072 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Between 3072 Kbit/s and 4096 Kbit/s for Cell
67196096
67196097
67196098
67196099
67196100
67196101
Issue 01 (2013-05-04)
1740
Counter ID 67196102
Counter Name VS.HSUPA.GoldenBeChThroughput.10
Counter Description Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Golden BE Services Greater Than 4096 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 0 Kbit/s and 32 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 32 Kbit/s and 64 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 64 Kbit/s and 256 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 256 Kbit/s and 512 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 512 Kbit/s and 768 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 768 Kbit/s and 1024 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 1024 Kbit/s and 1536 Kbit/s for Cell
1741
67196103
67196104
67196105
67196106
67196107
67196108
67196109
Issue 01 (2013-05-04)
Counter ID 67196110
Counter Description Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 1536 Kbit/s and 2048 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 2048 Kbit/s and 3072 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Between 3072 Kbit/s and 4096 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Silver BE Services Greater Than 4096 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 0 Kbit/s and 32 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 32 Kbit/s and 64 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 64 Kbit/s and 256 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 256 Kbit/s and 512 Kbit/s for Cell
1742
67196111
67196112
67196113
67196114
VS.HSUPA.CopperBeChThroughput.0
67196115
67196116
67196117
Issue 01 (2013-05-04)
Counter ID 67196118
Counter Name VS.HSUPA.CopperBeChThroughput.4
Counter Description Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 512 Kbit/s and 768 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 768 Kbit/s and 1024 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 1024 Kbit/s and 1536 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 1536 Kbit/s and 2048 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 2048 Kbit/s and 3072 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Between 3072 Kbit/s and 4096 Kbit/s for Cell Number of Times that Average UL Throughput of MAC-d Flow of HSUPA Bronze BE Services Greater Than 4096 Kbit/s for Cell
67196119
67196120
67196121
67196122
67196123
67196124
Description
These counters provide the number of times that the average UL throughput of the MAC-d flow of BE services is in each range based on the level of the service in the HSUPA cells in the active
set. The average throughput is reported by the DSP every 20 seconds.For DC-HSUPA users, this counter is measured only in the primary cell based on the total throughput on the primary and secondary carriers.The measurement item is measured only when the SPI measure function is activated using the SET UDPUCFGDATA command with CellCountersMeasOBJCtrlSwitch set to Qos or QosAndSpi.
Measurement point
In an HSUPA serving cell, the RNC takes samples of the average uplink throughput (the RLC header and retransmitted data are not measured) of the MAC-d flow carrying BE services at the RLC layer for gold, silver, and copper users every 20 seconds. When the throughput falls in a predefined range, the corresponding counter is incremented by one. At the end of a measurement period, the value of each counter is obtained.
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.GoldenBeChThroughput.0 VS.HSUPA.GoldenBeChThroughput.1 VS.HSUPA.GoldenBeChThroughput.2 VS.HSUPA.GoldenBeChThroughput.3 VS.HSUPA.GoldenBeChThroughput.4 VS.HSUPA.GoldenBeChThroughput.5 VS.HSUPA.GoldenBeChThroughput.6 VS.HSUPA.GoldenBeChThroughput.7 VS.HSUPA.GoldenBeChThroughput.8 VS.HSUPA.GoldenBeChThroughput.9
Issue 01 (2013-05-04)
Feature Name Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA
1744
Counter Name VS.HSUPA.GoldenBeChThroughput.10 VS.HSUPA.SilverBeChThroughput.0 VS.HSUPA.SilverBeChThroughput.1 VS.HSUPA.SilverBeChThroughput.2 VS.HSUPA.SilverBeChThroughput.3 VS.HSUPA.SilverBeChThroughput.4 VS.HSUPA.SilverBeChThroughput.5 VS.HSUPA.SilverBeChThroughput.6 VS.HSUPA.SilverBeChThroughput.7 VS.HSUPA.SilverBeChThroughput.8 VS.HSUPA.SilverBeChThroughput.9 VS.HSUPA.SilverBeChThroughput.10 VS.HSUPA.CopperBeChThroughput.0 VS.HSUPA.CopperBeChThroughput.1 VS.HSUPA.CopperBeChThroughput.2 VS.HSUPA.CopperBeChThroughput.3 VS.HSUPA.CopperBeChThroughput.4 VS.HSUPA.CopperBeChThroughput.5 VS.HSUPA.CopperBeChThroughput.6
Feature Name Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA
Issue 01 (2013-05-04)
1745
Counter Name VS.HSUPA.CopperBeChThroughput.7 VS.HSUPA.CopperBeChThroughput.8 VS.HSUPA.CopperBeChThroughput.9 VS.HSUPA.CopperBeChThroughput.10
Feature Name Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA
1.12.23.4 Service Setup Duration on an ERACH or EFACH for Cell Counters

Counter ID 73423349 Counter Name VS.ERACH.Estab.MaxTime VS.ERACH.Estab.MeanTime VS.ERACH.Estab.MinTime Counter Description Maximum Service Setup Duration on an ERACH for Cell Average Service Setup Duration on an ERACH for Cell Minimum Service Setup Duration on an ERACH for Cell Maximum Service Setup Duration on an EFACH for Cell Average Service Setup Duration on an EFACH for Cell Minimum Service Setup Duration on an EFACH for Cell
73441136
73423352
73423353
VS.EFACH.Estab.MaxTime
73441137
VS.EFACH.Estab.MeanTime VS.EFACH.Estab.MinTime
73423356
Issue 01 (2013-05-04)
1746
Counter ID 73423354
Counter Name VS.EFACH.Estab.Cum
Counter Description Cumulative Delay Between RRC Connection Establishment and EFACH RAB Establishment Completion for Cell Number of Samples of Cumulative Delay Between RRC Connection Establishment and EFACH RAB Establishment Completion for Cell Cumulative Delay Between RRC Connection Establishment and ERACH RAB Establishment Completion for Cell Number of Samples of Cumulative Delay Between RRC Connection Establishment and ERACH RAB Establishment Completion for Cell
73423355
VS.EFACH.Estab.Sample
73423350
VS.ERACH.Estab.Cum
73423351
VS.ERACH.Estab.Sample
Description
These counters provide the durations from the RRC connection setup to the first service setup on an ERACH or EFACH in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an RRC CONNECTION REQUEST message, the RNC records the time T1 at point A. When the RNC receives from the UE a RADIO BEARER SETUP COMPLETE message and sends a RAB ASSIGNMENT RESPONSE message to the CN, the RNC records the time T2 at point B. Assume that delta T is the duration of this service establishment, it is calculated as follows: delta T = T2-T1. The RNC takes samples of service establishment durations every 5 seconds in a measurement period. At the end of a measurement period, the RNC obtains the average duration by dividing the accumulated number by the sampling times. The maximum and minimum numbers among all sampling points in a measurement period are the maximum and minimum durations for establishing a service, respectively.
Issue 01 (2013-05-04)
1747
Figure 1-789 RAB establishment flow
Formula
VS.ERACH.Estab.MeanTime = [VS.ERACH.Estab.Cum]/[VS.ERACH.Estab.Sample] VS.EFACH.Estab.MeanTime = [VS.EFACH.Estab.Cum]/[VS.EFACH.Estab.Sample]
Unit
ms
Related Features
Counter Name VS.ERACH.Estab.MaxTime VS.ERACH.Estab.MeanTime VS.ERACH.Estab.MinTime VS.EFACH.Estab.MaxTime VS.EFACH.Estab.MeanTime
Issue 01 (2013-05-04)
Feature Name Uplink Enhanced CELL_FACH Uplink Enhanced CELL_FACH Uplink Enhanced CELL_FACH Downlink Enhanced CELL_FACH Downlink Enhanced CELL_FACH
1748
Counter Name VS.EFACH.Estab.MinTime
Feature Name Downlink Enhanced CELL_FACH
1.12.24 Measurement of CS RAB assignment setup per cell (RAB.EstabCS.Cell)

Overview
The CN in CS domain initiates the radio access bearer setup procedure by sending a RAB ASSIGNMENT REQUEST message to the RNC. After receiving the RAB ASSIGNMENT REQUEST message, the RNC selects an appropriate cell, allocates resources, and performs admission control based on the information in the message (such as service type, QoS, and priority), the traffic load of the system, and the networking strategy (such as DRD). The requirements of high-priority users are met preferentially(That is, when the resources are insufficient and the UEs with low-priority cannot set up the RAB, the RNC sends to the CN a RAB ASSGNMENT RESPONSE message if the queuing algorithm is enabled, indicating that the RAB is in the queue to wait for resources).If the admission of the RAB succeeds, the RNC starts the Iu transport connection setup procedure, the Iub radio bearer setup procedure, and the Uu radio bearer setup procedure. At last, the RNC sends to the CN a RAB ASSNMENT RESPONSE, indicating whether the RAB setup is successful. If DRD is enabled during the RAB setup, the RAB setup measurement is performed on the DRD target cell. Otherwise,if DRD is enabled after the RAB setup, the RAB setup measurement is performed on the DRD source cell. The RAB setup procedure is as follows:
Issue 01 (2013-05-04)
1749
Figure 1-790 Flow chart of RAB setup
Issue 01 (2013-05-04)
1750
Table 1 describes the measurement points shown in Figure1. Measurement points A B C~G Description VS.RAB.AttEstabCS.Conv,VS.RAB.AttEst abCS.Str VS.RAB.SuccEstabCS.Conv,VS.RAB.Succ EstabCS.Str See:RAB.EstFailCs.Cell
Counters
Counter ID 67179825 Counter Name VS.RAB.AttEstab CS.Conv Counter Description Number of CS Conversational RAB Establishment Requests for Cell Number of CS Streaming RAB Establishment Requests for Cell Number of Successful CS Conversational RAB Establishments for Cell Number of Successful CS Streaming RAB Establishments for Cell Number of CS 12.2kbit/s AMR Service RAB Establishment Attempts for Cell Number of CS 7.95kbit/s AMR Service RAB Establishment Attempts for Cell Original Release Earlier than V900R011
67179826
VS.RAB.AttEstab CS.Str
67179827
VS.RAB.SuccEstab CS.Conv
67179828
VS.RAB.SuccEstab CS.Str
67190457
VS.RAB.AttEstab CS.AMR.12.2
67190458
VS.RAB.AttEstCS. AMR.7.95
Issue 01 (2013-05-04)
1751
Counter ID 67190460
Counter Name VS.RAB.AttEstCS. AMR.4.75
Counter Description Number of CS 4.75kbit/s AMR Service RAB Establishment Attempts for Cell Number of Successful CS 12.2kbit/s AMR Service RAB Establishments for Cell Number of Successful CS 7.95kbit/s AMR Service RAB Establishments for Cell Number of Successful CS 4.75kbit/s AMR Service RAB Establishments for Cell Number of CS AMR Service RAB Establishment Attempts for Cell Number of CS Wideband AMR Service RAB Establishment Attempts for Cell Number of CS Conversational RAB Establishment Attempts for Cell (Max DL Bit Rate is 64 kbit/s) Number of Successful CS AMR RAB Establishments for Cell
67190461
VS.RAB.SuccEstab CS.AMR.12.2
67190462
VS.RAB.SuccEstC S.AMR.7.95
67190464
VS.RAB.SuccEstC S.AMR.4.75
67179858
VS.RAB.AttEstab. AMR
67192120
VS.RAB.AttEstab CS.AMRWB
67179859
VS.RAB.AttEstCS. Conv.64
67179860
VS.RAB.SuccEstab CS.AMR
Issue 01 (2013-05-04)
1752
Counter ID 67192121
Counter Name VS.RAB.SuccEstab CS.AMRWB
Counter Description Number of Successful CS Wideband AMR RAB Establishments for Cell Number of Successful CS RAB Establishments for Cell (Max DL Bit Rate is 64 kbit/s) Number of CS over HSPA RAB Establishment Attempts for Cell Number of Successful CS over HSPA RAB Establishments for Cell Number of 64kbit/s CS RAB Attempts Initiated in Cell Where 64kbit/s CS Conversational Service is Forbidden for Cell Number of CS over HSPA Users for Cell Number of Queuing Attempts Due to Insufficient Resource in the CS RAB Assignment Establishment Procedure for Cell Average Duration of a CS Queuing in the RAB Establishment Procedure for Cell Number of Successful CS Establishment After Queuing for Cell
67179861
VS.RAB.SuccEstC S.Conv.64
67196202
VS.HSPA.RAB.Att Estab.CS.Conv
67196203
VS.HSPA.RAB.Suc cEstab.CS.Conv
67196232
VS.RAB.AttEstab CS.VPLimit
67204853 73393916
VS.HSPA.UE.Mea n.CS.Conv.Cell VS.RAB.AttEstab CS.Queue
73393918
VS.RAB.Estab.Que ueTime.CS
V900R012
73393920
VS.RAB.SuccEstab CS.Queue
V900R012
Issue 01 (2013-05-04)
1753
Counter ID 73394277
Counter Name VS.RAB.AttEstab CS.AMRWB23.85
Counter Description Number of CS 23.85kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 23.05kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 19.85kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 18.25kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 15.85kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 14.25kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 12.65kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 8.85kbit/s AMRWB service RAB establishment Attempts for cell
73394278
VS.RAB.AttEstab CS.AMRWB23.05
V900R012
73394279
V900R012
73394280
V900R012
73394281
V900R012
73394282
V900R012
73394283
V900R012
73394284
V900R012
Issue 01 (2013-05-04)
1754
Counter ID 73394285
Counter Name VS.RAB.AttEstab CS.AMRWB6.60
Counter Description Number of CS 6.60kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 23.85kbit/s AMRWB service RAB successfully established for cell Number of CS 23.05kbit/s AMRWB service RAB successfully established for cell Number of CS 19.85kbit/s AMRWB service RAB successfully established for cell Number of CS 18.25kbit/s AMRWB service RAB successfully established for cell Number of CS 15.85kbit/s AMRWB service RAB successfully established for cell Number of CS 14.25kbit/s AMRWB service RAB successfully established for cell Number of CS 12.65kbit/s AMRWB service RAB successfully established for cell
73394286
VS.RAB.SuccEstab CS.AMRWB23.85
V900R012
73394287
V900R012
73394288
V900R012
73394289
V900R012
73394290
V900R012
73394291
V900R012
73394292
V900R012
Issue 01 (2013-05-04)
1755
Counter ID 73394293
Counter Name VS.RAB.SuccEstab CS.AMRWB8.85
Counter Description Number of CS 8.85kbit/s AMRWB service RAB successfully established for cell Number of CS 6.60kbit/s AMRWB service RAB successfully established for cell Number of CS RAB Setup Requests for Platinum UEs for Cell Number of Successful CS RAB Setups for Platinum UEs for Cell Number of CS RAB Setup Requests for Platinum UEs Performing Conversational Services for Cell Number of Successful CS RAB Setups for Platinum UEs Performing Conversational Services for Cell Number of CS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell
73394294
V900R012
73425918
VS.RAB.AttEstab CS.Platinum
V900R015
73425919
VS.RAB.SuccEstab CS.Platinum
V900R015
73425920
VS.RAB.AttEstab CS.Conv.Platinum
V900R015
73425921
VS.RAB.SuccEstab CS.Conv.Platinum
V900R015
73426335
VS.AttEstabCS.Aft erP2F
V900R015
Issue 01 (2013-05-04)
1756
Counter ID 73426336
Counter Name VS.AttEstabCS.Aft erP2D
Counter Description Number of CS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_DCH for Cell Number of Successful CS Service Setups Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell Number of Successful CS Service Setups Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_DCH for Cell
73426337
VS.SuccEstabCS.A fterP2F
V900R015
73426338
VS.SuccEstabCS.A fterP2D
V900R015
Counter VS.RAB.AttEstab.AMR Sub Counter VS.RAB.AttEstabCS.AMR.12.2 VS.RAB.AttEstCS.AMR.7.95 VS.RAB.AttEstCS.AMR.4.75 VS.RAB.SuccEstabCS.AMR VS.RAB.SuccEstabCS.AMR.12.2 VS.RAB.SuccEstCS.AMR.7.95 VS.RAB.SuccEstCS.AMR.4.75
Issue 01 (2013-05-04)
1757
Counter VS.RAB.AttEstabCS.AMRWB
Sub Counter VS.RAB.AttEstabCS.AMRWB23.85 VS.RAB.AttEstabCS.AMRWB23.05 VS.RAB.AttEstabCS.AMRWB19.85 VS.RAB.AttEstabCS.AMRWB18.25 VS.RAB.AttEstabCS.AMRWB15.85 VS.RAB.AttEstabCS.AMRWB14.25 VS.RAB.AttEstabCS.AMRWB12.65 VS.RAB.AttEstabCS.AMRWB8.85 VS.RAB.AttEstabCS.AMRWB6.60
VS.RAB.SuccEstabCS.AMRWB
VS.RAB.SuccEstabCS.AMRWB23.85 VS.RAB.SuccEstabCS.AMRWB23.05 VS.RAB.SuccEstabCS.AMRWB19.85 VS.RAB.SuccEstabCS.AMRWB18.25 VS.RAB.SuccEstabCS.AMRWB15.85 VS.RAB.SuccEstabCS.AMRWB14.25 VS.RAB.SuccEstabCS.AMRWB12.65 VS.RAB.SuccEstabCS.AMRWB8.85 VS.RAB.SuccEstabCS.AMRWB6.60
1.12.24.1 Number of CS RAB Setup Requests for Different Services Counters

Counter ID 67179825 Counter Name VS.RAB.AttEstabCS.Conv Counter Description Number of CS Conversational RAB Establishment Requests for Cell Number of CS Streaming RAB Establishment Requests for Cell Number of CS 12.2kbit/s AMR Service RAB Establishment Attempts for Cell Number of CS 7.95kbit/s AMR Service RAB Establishment Attempts for Cell
1758
67179826
VS.RAB.AttEstabCS.Str
67190457
VS.RAB.AttEstabCS.AMR. 12.2
67190458
VS.RAB.AttEstCS.AMR. 7.95
Issue 01 (2013-05-04)
Counter ID 67190460
Counter Name VS.RAB.AttEstCS.AMR. 4.75
Counter Description Number of CS 4.75kbit/s AMR Service RAB Establishment Attempts for Cell Number of CS AMR Service RAB Establishment Attempts for Cell Number of CS Wideband AMR Service RAB Establishment Attempts for Cell Number of CS Conversational RAB Establishment Attempts for Cell (Max DL Bit Rate is 64 kbit/s) Number of CS 23.85kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 23.05kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 19.85kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 18.25kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 15.85kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 14.25kbit/s AMRWB service RAB establishment Attempts for cell
67179858
VS.RAB.AttEstab.AMR
67192120
VS.RAB.AttEstabCS.AMR WB
67179859
VS.RAB.AttEstCS.Conv.64
73394277
VS.RAB.AttEstabCS.AMR WB23.85
73394278
73394279
73394280
73394281
73394282
Issue 01 (2013-05-04)
1759
Counter ID 73394283
Counter Name VS.RAB.AttEstabCS.AMR WB12.65
Counter Description Number of CS 12.65kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 8.85kbit/s AMRWB service RAB establishment Attempts for cell Number of CS 6.60kbit/s AMRWB service RAB establishment Attempts for cell Number of CS RAB Setup Requests for Platinum UEs for Cell Number of CS RAB Setup Requests for Platinum UEs Performing Conversational Services for Cell
73394284
73394285
73425918
VS.RAB.AttEstabCS.Platinum VS.RAB.AttEstabCS.Conv. Platinum
73425920
Description
These counters provide the number of CS RABs establishment requests in the best cell according to the service type or user grade.
Measurement point
ASSIGNMENT REQUEST message from the CN in the CS domain, it measures the corresponding counter in the best cell according to the type of the service to be set up, user grade, or maximum rate. The number of CS RAB setup requests for platinum UEs in the best cells is provided by the VS.RAB.AttEstabCS.Platinum counter.
Issue 01 (2013-05-04)
1760
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabCS.Conv VS.RAB.AttEstabCS.Str VS.RAB.AttEstabCS.AMR. 12.2 VS.RAB.AttEstCS.AMR. 7.95 VS.RAB.AttEstCS.AMR. 4.75 VS.RAB.AttEstab.AMR VS.RAB.AttEstabCS.AMR WB
Issue 01 (2013-05-04)
Feature ID WRFD-010501 WRFD-010502 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010613
Feature Name Conversational QoS Class Streaming QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class AMR-WB (Adaptive Multi Rate Wide Band)
1761
Counter Name VS.RAB.AttEstCS.Conv.64 VS.RAB.AttEstabCS.AMR WB23.85 VS.RAB.AttEstabCS.AMR WB23.05 VS.RAB.AttEstabCS.AMR WB19.85 VS.RAB.AttEstabCS.AMR WB18.25 VS.RAB.AttEstabCS.AMR WB15.85 VS.RAB.AttEstabCS.AMR WB14.25 VS.RAB.AttEstabCS.AMR WB12.65 VS.RAB.AttEstabCS.AMR WB8.85 VS.RAB.AttEstabCS.AMR WB6.60 VS.RAB.AttEstabCS.Platinum VS.RAB.AttEstabCS.Conv. Platinum
Feature ID WRFD-010501 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-150204 WRFD-150204
Feature Name Conversational QoS Class AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) Platinum User Prioritizing Platinum User Prioritizing
1.12.24.2 Number of Successful CS RAB Establishments in the Cell for Different Services Counters
Counter ID 67179827 Counter Name VS.RAB.SuccEstabCS.Con v VS.RAB.SuccEstabCS.Str Counter Description Number of Successful CS Conversational RAB Establishments for Cell Number of Successful CS Streaming RAB Establishments for Cell
67179828
Issue 01 (2013-05-04)
1762
Counter ID 67190461
Counter Name VS.RAB.SuccEstabCS.AM R.12.2 VS.RAB.SuccEstCS.AMR. 7.95 VS.RAB.SuccEstCS.AMR. 4.75 VS.RAB.SuccEstabCS.AM R VS.RAB.SuccEstabCS.AM RWB VS.RAB.SuccEstCS.Conv. 64
Counter Description Number of Successful CS 12.2kbit/s AMR Service RAB Establishments for Cell Number of Successful CS 7.95kbit/s AMR Service RAB Establishments for Cell Number of Successful CS 4.75kbit/s AMR Service RAB Establishments for Cell Number of Successful CS AMR RAB Establishments for Cell Number of Successful CS Wideband AMR RAB Establishments for Cell Number of Successful CS RAB Establishments for Cell (Max DL Bit Rate is 64 kbit/ s) Number of CS 23.85kbit/s AMRWB service RAB successfully established for cell Number of CS 23.05kbit/s AMRWB service RAB successfully established for cell Number of CS 19.85kbit/s AMRWB service RAB successfully established for cell Number of CS 18.25kbit/s AMRWB service RAB successfully established for cell Number of CS 15.85kbit/s AMRWB service RAB successfully established for cell Number of CS 14.25kbit/s AMRWB service RAB successfully established for cell
67190462
67190464
67179860
67192121
67179861
73394286
VS.RAB.SuccEstabCS.AM RWB23.85
73394287
73394288
73394289
73394290
73394291
Issue 01 (2013-05-04)
1763
Counter ID 73394292
Counter Name VS.RAB.SuccEstabCS.AM RWB12.65
Counter Description Number of CS 12.65kbit/s AMRWB service RAB successfully established for cell Number of CS 8.85kbit/s AMRWB service RAB successfully established for cell Number of CS 6.60kbit/s AMRWB service RAB successfully established for cell Number of Successful CS RAB Setups for Platinum UEs for Cell Number of Successful CS RAB Setups for Platinum UEs Performing Conversational Services for Cell
73394293
73394294
73425919
VS.RAB.SuccEstabCS.Platinum VS.RAB.SuccEstabCS.Con v.Platinum
73425921
Description
These counters provide the number of CS RABs that are successfully established in the best cell according to the service type or user grade.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message after receiving a RADIO BEARER SETUP COMPLETE message from the UE, it measures the corresponding counter in the best cell where the UE camps on according to the service type of the RAB, user grade, or maximum rate if the RAB is for the CS service. The number of successful CS RAB setups for platinum UEs in the best cells is provided by the VS.RAB.SuccEstabCS.Platinum counter.
Issue 01 (2013-05-04)
1764
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstabCS.Con v VS.RAB.SuccEstabCS.Str VS.RAB.SuccEstabCS.AM R.12.2 VS.RAB.SuccEstCS.AMR. 7.95 VS.RAB.SuccEstCS.AMR. 4.75 VS.RAB.SuccEstabCS.AM R
Issue 01 (2013-05-04)
Feature Name Conversational QoS Class Streaming QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class
1765
Counter Name VS.RAB.SuccEstabCS.AM RWB VS.RAB.SuccEstCS.Conv. 64 VS.RAB.SuccEstabCS.AM RWB23.85 VS.RAB.SuccEstabCS.AM RWB23.05 VS.RAB.SuccEstabCS.AM RWB19.85 VS.RAB.SuccEstabCS.AM RWB18.25 VS.RAB.SuccEstabCS.AM RWB15.85 VS.RAB.SuccEstabCS.AM RWB14.25 VS.RAB.SuccEstabCS.AM RWB12.65 VS.RAB.SuccEstabCS.AM RWB8.85 VS.RAB.SuccEstabCS.AM RWB6.60 VS.RAB.SuccEstabCS.Platinum VS.RAB.SuccEstabCS.Con v.Platinum
Feature ID WRFD-010613 WRFD-010501 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-010613 WRFD-150204 WRFD-150204
Feature Name AMR-WB (Adaptive Multi Rate Wide Band) Conversational QoS Class AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) AMR-WB (Adaptive Multi Rate Wide Band) Platinum User Prioritizing Platinum User Prioritizing
1.12.24.3 Number of RAB Setup Attempts for CS HSPA Voice Services Counters
Counter ID 67196202 Counter Name VS.HSPA.RAB.AttEstab.C S.Conv Counter Description Number of CS over HSPA RAB Establishment Attempts for Cell
Issue 01 (2013-05-04)
1766
Description
This counter provides the number of RAB setup attempts for CS HSPA voice services(including wideband AMR services and narrowband AMR services) in the serving cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN in the CS domain, it assigns a channel according to the network configuration. In this case, the RNC measures this counter in the serving cell where the UE camps on if the RAB is set up at an HSPA channel. Figure 1-793 RAB setup procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HSPA.RAB.AttEstab.C S.Conv Feature ID WRFD-010619 Feature Name CS voice over HSPA/HSPA +
Issue 01 (2013-05-04)
1767
1.12.24.4 Number of Successful RAB Setups for CS Conversational Services Counters

Counter ID 67196203 Counter Name VS.HSPA.RAB.SuccEstab. CS.Conv Counter Description Number of Successful CS over HSPA RAB Establishments for Cell
Description
This counter provides the number of times that the RAB is set up successfully on the HSPA channels for AMR service(narrowband and wideband AMR services)in the serving cell.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message after receiving a RADIO BEARER SETUP COMPLETE message from the UE, it measures the counter in the serving cell where the UE camps on if the RAB is for the CS conversational service and is carried on an HSPA channel. Figure 1-794 RAB setup procedure
Formula
None
Unit
None
Related Features
Counter Name VS.HSPA.RAB.SuccEstab. CS.Conv Feature ID WRFD-010619 Feature Name CS voice over HSPA/HSPA +
1.12.24.5 Number of RAB Setup Attempts for VP Services when VP Call Is Limited Counters
Counter ID 67196232 Counter Name VS.RAB.AttEstabCS.VPLimit Counter Description Number of 64kbit/s CS RAB Attempts Initiated in Cell Where 64kbit/s CS Conversational Service is Forbidden for Cell
Description
This counter provides the number of RAB setup requests for VP services when the VP call is limited in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN in the CS domain, it measures the counter in the best cell if the RAB is for the VP service.
Issue 01 (2013-05-04)
1769
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabCS.VPLimit Feature ID WRFD-020130 Feature Name Videophone Service Restriction
1.12.24.6 Number of CS Over HSPA in a Cell Counters

Counter ID 67204853 Counter Name VS.HSPA.UE.Mean.CS.Co nv.Cell Counter Description Number of CS over HSPA Users for Cell
Issue 01 (2013-05-04)
1770
Description
This counter provides the average number of CS over HSPA users in the serving cell.
Measurement point
The system periodically samples (sampling periodicity is 5 seconds) the number of CS Over HSPA users. At the end of a statistical period, the system divides the sampling number by the sum at each sampling point to obtain the average number of CS Over HSPA users during the period.
Formula
None
Unit
None
Related Features
Counter Name VS.HSPA.UE.Mean.CS.Co nv.Cell Feature ID WRFD-010619 Feature Name CS voice over HSPA/HSPA +
1.12.24.7 Number of Queuing Attempts Due to Insufficient Resource in the CS RAB Assignment Establishment Procedure Counters
Counter ID 73393916 Counter Name VS.RAB.AttEstabCS.Queue Counter Description Number of Queuing Attempts Due to Insufficient Resource in the CS RAB Assignment Establishment Procedure for Cell
Description
This counter provides the queuing attempts initiated by the RNC for the CS service that fails to be set up due to insufficient cell resources.
Measurement point
During the RAB establishment procedure, the RNC initiates queuing for the CS service if the cell has insufficient resources for the service. After a period of time, the RNC tries to assign
resources to the service again. The measurement is triggered when the service enters the queue,as shown of point A in Figure1. The counter is measured in the queued cells. Figure 1-796 Queue procedure for admission failure during the RAB establishment
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabCS.Queue Feature ID WRFD-010505 Feature Name Queuing and Pre-Emption
1.12.24.8 Average Duration of a CS Queuing in the RAB Establishment Procedure Counters

Counter ID 73393918 Counter Name VS.RAB.Estab.QueueTime. CS Counter Description Average Duration of a CS Queuing in the RAB Establishment Procedure for Cell
Issue 01 (2013-05-04)
1772
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73393966 Counter Name VS.RAB.Estab.QueueTime. CS.CUM Counter Description Duration of RAB queuing in CS domain during the RAB assignment in a cell (Numerator) Duration of RAB queuing in CS domain during the RAB assignment in a cell (Denominator)
73393967
VS.RAB.Estab.QueueTime. CS.SAMPLE
Description
This counter provides the queuing duration for the queued cells.
Measurement point
During the RAB establishment, the RNC initiates queuing for the CS service if the target cell does not have sufficient resources. After a certain period of time, the RNC attempts to allocate resources to the service again. If the service is allocated resources before the related timer expires, this counter measures the queuing duration of this service in the cell where the corresponding UE currently camps.
Formula
VS.RAB.Estab.QueueTime.CS = [VS.RAB.Estab.QueueTime.CS.CUM]/ [VS.RAB.Estab.QueueTime.CS.SAMPLE]
Unit
s
Related Features
Counter Name VS.RAB.Estab.QueueTime. CS Feature ID WRFD-010505 Feature Name Queuing and Pre-Emption
1.12.24.9 Number of Successful CS Establishment After Queuing
Issue 01 (2013-05-04)
1773
Counters
Counter ID 73393920 Counter Name VS.RAB.SuccEstabCS.Que ue Counter Description Number of Successful CS Establishment After Queuing for Cell
Description
This counter provides the number of successful establishment of the CS service after the service is queued when the RNC initiates queuing for the CS service that fails to be set up due to insufficient cell resources.
Measurement point
During the RAB establishment procedure, the RNC initiates queuing for the CS service if the cell has insufficient resources for the service. After a period of time, the RNC tries to assign resources to the service again. The measurement is triggered when the service is successfully set up after it is queued,as shown of point C in Figure1. The counter is measured in the queued cells. Figure 1-797 Queue procedure for admission failure during the RAB establishment
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstabCS.Que ue Feature ID WRFD-010505 Feature Name Queuing and Pre-Emption
1.12.24.10 Number of CS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell Counters
Counter ID 73426335 Counter Name VS.AttEstabCS.AfterP2F Counter Description Number of CS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell Number of CS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_DCH for Cell
73426336
VS.AttEstabCS.AfterP2D
Description
These counters measure the number of CS service setups initiated by UEs in the CELL_PCH or URA_PCH state in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. A UE in the CELL_PCH or URA_PCH state initiates CS services and transitions to another state. After the RNC receives a RAB ASSIGNMENT REQUEST message from the CS domain of the CN, the RNC calculates the number of CS service setup attempts in the best cell of the UE based on the UE state.
Issue 01 (2013-05-04)
1775
Figure 1-798 RAB setup procedure initiated by UEs in the CELL_PCH or URA_PCH state
The measurement is triggered at point A, as shown in the figure. A UE in the CELL_PCH or URA_PCH state initiates CS services and transitions to another state. After the RNC receives a RAB ASSIGNMENT REQUEST message from the CS domain of the CN, the RNC calculates the number of CS service setup attempts in the best cell of the UE based on the UE state. Figure 1-799 RAB setup procedure initiated by CN RAB assignment requests for UEs in the CELL_PCH or URA_PCH state
Issue 01 (2013-05-04)
1776
Formula
None
Unit
None
Related Features
Counter Name VS.AttEstabCS.AfterP2F Feature ID WRFD-010501 WRFD-010502 VS.AttEstabCS.AfterP2D WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class Conversational QoS Class Streaming QoS Class
1.12.24.11 Number of Successful CS Service Setups Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell Counters
Counter ID 73426337 Counter Name VS.SuccEstabCS.AfterP2F Counter Description Number of Successful CS Service Setups Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell Number of Successful CS Service Setups Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_DCH for Cell
73426338
VS.SuccEstabCS.AfterP2D
Description
These counters measure the number of CS service setups initiated by UEs in the CELL_PCH or URA_PCH state in the best cell.
Measurement point
The measurement is triggered at point B, as shown in the figure. A UE in the CELL_PCH or URA_PCH state initiates CS services and transitions to another state. After the RNC receives a
RAB ASSIGNMENT REQUEST message from the CS domain of the CN and return a RAB ASSIGNMENT RESPONSE message, the RNC calculates the number of successful CS service setups in the best cell of the UE based on the UE state. Figure 1-800 RAB setup procedure initiated by UEs in the CELL_PCH or URA_PCH state
The measurement is triggered at point B, as shown in the figure. A UE in the CELL_PCH or URA_PCH state initiates CS services and transitions to another state. After the RNC receives a RAB ASSIGNMENT REQUEST message from the CS domain of the CN and return a RAB ASSIGNMENT RESPONSE message, the RNC calculates the number of successful CS service setups in the best cell of the UE based on the UE state.
Issue 01 (2013-05-04)
1778
Figure 1-801 RAB setup procedure initiated by CN RAB assignment requests for UEs in the CELL_PCH or URA_PCH state
Formula
None
Unit
None
Related Features
Counter Name VS.SuccEstabCS.AfterP2F Feature ID WRFD-010501 WRFD-010502 VS.SuccEstabCS.AfterP2D WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class Conversational QoS Class Streaming QoS Class
Issue 01 (2013-05-04)
1779
1.12.25 Measurement of PS RAB assignment setup per cell (RAB.EstabPS.Cell)

Overview
The CN in PS domain initiates the radio access bearer setup procedure by sending a RAB ASSIGNMENT REQUEST message to the RNC. After receiving the RAB ASSIGNMENT REQUEST message, the RNC selects an appropriate cell, allocates resources, and performs admission control based on the information in the message (such as service type, QoS, and priority), the traffic load of the system, and the networking strategy (such as DRD). The requirements of high-priority users are met preferentially(That is, when the resources are insufficient and the UEs with low-priority cannot set up the RAB, the RNC sends to the CN a RAB ASSGNMENT RESPONSE message if the queuing algorithm is enabled, indicating that the RAB is in the queue to wait for resources). If the admission of the RAB succeeds, the RNC starts the Iu transport connection setup procedure, the Iub radio bearer setup procedure, and the Uu radio bearer setup procedure. At last, the RNC sends to the CN a RAB ASSNMENT RESPONSE, indicating whether the RAB setup is successful. If DRD is enabled during the RAB setup, the RAB setup measurement is performed on the DRD target cell. Otherwise,if DRD is enabled after the RAB setup, the RAB setup measurement is performed on the DRD source cell. The RAB setup procedure is as follows.
Issue 01 (2013-05-04)
1780
Issue 01 (2013-05-04)
1781
Table 1 describes the measurement points shown in Figure1. Measurement points A Description VS.RAB.AttEstabPS.Conv,VS.RAB.AttEst abPS.Str,VS.RAB.AttEstabPS.Int,VS.RAB. AttEstabPS.Bkg VS.RAB.SuccEstabPS.Conv,VS.RAB.Succ EstabPS.Str,VS.RAB.SuccEstabPS.Int,VS. RAB.SuccEstabPS.Bkg See:RAB.EstFailPs.Cell
C~G
Counters
Counter ID 67179924 Counter Name VS.RAB.AttEstabP S.Bkg Counter Description Number of PS Background RAB Establishment Attempts for Cell Number of PS Conversational RAB Establishment Attempts for Cell Number of PS Interactive RAB Establishment Attempts for Cell Number of PS Streaming RAB Establishment Attempts for Cell Number of Successful PS Background RAB Establishments for Cell Number of Successful PS Conversational RAB Establishments for Cell Original Release Earlier than V900R011
67179921
VS.RAB.AttEstabP S.Conv
67179923
VS.RAB.AttEstabP S.Int
67179922
VS.RAB.AttEstabP S.Str
67179928
VS.RAB.SuccEstab PS.Bkg
67179925
VS.RAB.SuccEstab PS.Conv
Issue 01 (2013-05-04)
1782
Counter ID 67179927
Counter Name VS.RAB.SuccEstab PS.Int
Counter Description Number of Successful PS Interactive RAB Establishments for Cell Number of Successful PS Streaming RAB Establishments for Cell Number of PS RABs Established Successfully at 0 kbit/s in the Best Cell Number of PS R99 RAB successfully established for cell Number of PS R99 RAB establishment Attempts for cell Number of Queuing Attempts Due to Insufficient Resource in the PS RAB Assignment Establishment Procedure for Cell Average Duration of a PS Queuing in the RAB Establishment Procedure for Cell Number of Successful PS Establishment After Queuing for Cell Number of Successful PTT Service Establishments for Cell
67179926
VS.RAB.SuccEstab PS.Str
67196301
VS.RAB.SuccEstabPS.0kbps
73403808
VS.RAB.SuccEstab .PSR99 VS.RAB.AttEstab. PSR99 VS.RAB.AttEstabP S.Queue
V900R012
73403809
V900R012
73393917
V900R012
73393919
VS.RAB.Estab.Que ueTime.PS
V900R012
73393921
VS.RAB.SuccEstab PS.Queue
V900R012
73394075
VS.RAB.SuccEstab PS.PTT
V900R012
Issue 01 (2013-05-04)
1783
Counter ID 73394076
Counter Name VS.RAB.AttEstabP S.PTT
Counter Description Number of PTT Service Establishment Attempts for Cell Number of PS Free RAB Setup Attempts for Cell Number of Successful PS Free RAB Setups for Cell Number of Successful PS RAB Setups for Platinum UEs for Cell Number of PS RAB Setup Requests for Platinum UEs Performing Conversational Services for Cell Number of Successful PS RAB Setups for Platinum UEs Performing Conversational Services for Cell Number of PS RAB Setup Requests for Platinum UEs for Cell Number of PS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell
73423517
VS.RAB.AttEstabP S.Free VS.RAB.SuccEstab PS.Free VS.RAB.SuccEstab PS.Platinum
V900R013
73423518
V900R013
73425923
V900R015
73425924
VS.RAB.AttEstabP S.Conv.Platinum
V900R015
73425925
VS.RAB.SuccEstab PS.Conv.Platinum
V900R015
73425922
VS.RAB.AttEstabP S.Platinum
V900R015
73426339
VS.AttEstabPS.Aft erP2F
V900R015
Issue 01 (2013-05-04)
1784
Counter ID 73426340
Counter Name VS.AttEstabPS.Aft erP2D
Counter Description Number of PS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_DCH for Cell Number of Successful PS Service Setups Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell Number of Successful PS Service Setups Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_DCH for Cell
73426341
VS.SuccEstabPS.A fterP2F
V900R015
73426342
VS.SuccEstabPS.A fterP2D
V900R015
None
1.12.25.1 Number of PS RAB Setup Requests for Different Services Counters

Counter ID 67179921 Counter Name VS.RAB.AttEstabPS.Conv Counter Description Number of PS Conversational RAB Establishment Attempts for Cell Number of PS Background RAB Establishment Attempts for Cell
1785
67179924
VS.RAB.AttEstabPS.Bkg
Issue 01 (2013-05-04)
Counter ID 67179923
Counter Name VS.RAB.AttEstabPS.Int
Counter Description Number of PS Interactive RAB Establishment Attempts for Cell Number of PS Streaming RAB Establishment Attempts for Cell Number of PS R99 RAB establishment Attempts for cell Number of PTT Service Establishment Attempts for Cell Number of PS Free RAB Setup Attempts for Cell Number of PS RAB Setup Requests for Platinum UEs for Cell
67179922
VS.RAB.AttEstabPS.Str
73403809
VS.RAB.AttEstab.PSR99
73394076
VS.RAB.AttEstabPS.PTT
73423517 73425922
VS.RAB.AttEstabPS.Free VS.RAB.AttEstabPS.Platinum
Description
These counters provide the number of PS RABs that are requested to be set up in the best cell according to the service type, user grade, or traffic channel type.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN in the PS domain, it measures the corresponding counter in the best cell that the UE camps on based on the service type, user grade, or traffic channel type. The number of PS RABs that are requested to be set up for platinum UEs in the best cells is provided by the VS.RAB.AttEstabPS.Platinum. The number of RABs that are requested to be set up for PS R99 services carried by a specific traffic channel in the best cell is provided by the VS.RAB.AttEstab.PSR99 counter. The number of PS free RABs that are requested to be set up in the best cell is provided by the VS.RAB.AttEstabPS.Free counter. This counter is measured only when the special handling for free access user algorithm is enabled.
Issue 01 (2013-05-04)
1786
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabPS.Conv VS.RAB.AttEstabPS.Bkg VS.RAB.AttEstabPS.Int VS.RAB.AttEstabPS.Str VS.RAB.AttEstab.PSR99 Feature ID WRFD-010501 WRFD-010504 WRFD-010503 WRFD-010502 WRFD-010510 Feature Name Conversational QoS Class Background QoS Class Interactive QoS Class Streaming QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Push to Talk
VS.RAB.AttEstabPS.PTT
WRFD-020134
Issue 01 (2013-05-04)
1787
Counter Name VS.RAB.AttEstabPS.Free
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Platinum User Prioritizing
VS.RAB.AttEstabPS.Platinum
WRFD-150204
1.12.25.2 Number of PS RABs Successfully Set Up in a Cell for Different Services Counters
Counter ID 67179925 Counter Name VS.RAB.SuccEstabPS.Conv Counter Description Number of Successful PS Conversational RAB Establishments for Cell Number of Successful PS Background RAB Establishments for Cell Number of Successful PS Interactive RAB Establishments for Cell Number of Successful PS Streaming RAB Establishments for Cell Number of PS R99 RAB successfully established for cell Number of Successful PTT Service Establishments for Cell Number of Successful PS Free RAB Setups for Cell Number of Successful PS RAB Setups for Platinum UEs for Cell Number of Successful PS RAB Setups for Platinum UEs Performing Conversational Services for Cell
67179928
VS.RAB.SuccEstabPS.Bkg
67179927
VS.RAB.SuccEstabPS.Int
67179926
VS.RAB.SuccEstabPS.Str
73403808
VS.RAB.SuccEstab.PSR99
73394075
VS.RAB.SuccEstabPS.PTT
73423518 73425923
VS.RAB.SuccEstabPS.Free VS.RAB.SuccEstabPS.Platinum VS.RAB.SuccEstabPS.Conv .Platinum
73425925
Issue 01 (2013-05-04)
1788
Description
These counters provide the number of PS RABs that are successfully established in the best cell according to the service type, user grade, and traffic channel type.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message after receiving a RADIO BEARER SETUP COMPLETE message from the UE, it measures the corresponding counter based on the service type of the RAB, user grade, or traffic channel carrying the RAB in the best cell where the UE camps on if the RAB is for the PS service. The number of PS RABs that are successfully set up for platinum UEs in the best cells is provided by the VS.RAB.SuccEstabPS.Platinum counter. The number of successful RABs that are successfully set up for PS R99 services in a specific traffic channel in the best cells is provided by the VS.RAB.SuccEstab.PSR99 counter. The number of PS free RABs that are successfully set up in the best cells is provided by the VS.RAB.AttEstabPS.Free counter. This counter is measured only when the special handling for free access user algorithm is enabled. Figure 1-804 RAB setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstabPS.Conv VS.RAB.SuccEstabPS.Bkg VS.RAB.SuccEstabPS.Int VS.RAB.SuccEstabPS.Str VS.RAB.SuccEstab.PSR99 Feature ID WRFD-010501 WRFD-010504 WRFD-010503 WRFD-010502 WRFD-010510 Feature Name Conversational QoS Class Background QoS Class Interactive QoS Class Streaming QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Push to Talk 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Platinum User Prioritizing Platinum User Prioritizing
VS.RAB.SuccEstabPS.PTT VS.RAB.SuccEstabPS.Free
WRFD-020134 WRFD-010510
VS.RAB.SuccEstabPS.Platinum VS.RAB.SuccEstabPS.Conv .Platinum
WRFD-150204 WRFD-150204
1.12.25.3 Number of PS RABs Set Up Successfully at 0 Kbit/s Counters

Counter ID 67196301 Counter Name VS.RAB.SuccEstabPS. 0kbps Counter Description Number of PS RABs Established Successfully at 0 kbit/s in the Best Cell
Description
This counter provides the number of times that an UE access the network successfully through the 0 Kbit/s RAB in the best cell during the procedures of RAB establishment, RAB modification, cell update, relocation (UE involved) and hard handover.
Measurement point
The measurement is triggered at point A as shown in the following figure 1. During a RAB setup procedure, when the RNC receives a RADIO BEARER SETUP COMPLETE message from UE, it measures this counter in the best cell if any of the following conditions is met: 1.The rate
of the RAB is 0 Kbit/s. 2.The existing PS service rate is reconfigured as 0 kbit/s because the UE establishes a CS service. Figure 1-805 RAB setup procedure
The measurement is triggered at point A as shown in the following figure 2. During a RAB modification procedure, when the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from UE, it measures this counter in the best cell if the rate of the RAB is 0 Kbit/s. Figure 1-806 RAB modification procedure
The measurement is triggered at point A as shown in the following figure 3. During a P2D procedure, when the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from UE, it measures this counter in the best cell if the rate of the RAB is 0 Kbit/s.
Issue 01 (2013-05-04)
1791
Figure 1-807 P2D procedure
The measurement is triggered at point A as shown in the following figure 4. During a relocation (UE involved) procedure, when the RNC sends a RELOCATION COMPLETE message to CN, it measures this counter in the best cell if the rate of the RAB is 0 Kbit/s. Figure 1-808 relocation (UE involved) procedure
The measurement is triggered at point A as shown in the following figure 5. During a hard handover procedure, when the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from UE, it measures this counter in the best cell if the rate of the RAB is 0 Kbit/s.
Issue 01 (2013-05-04)
1792
Figure 1-809 hard handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstabPS. 0kbps Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.25.4 Number of Queuing Attempts Due to Insufficient Resource in the PS RAB Assignment Establishment Procedure
Issue 01 (2013-05-04)
1793
Counters
Counter ID 73393917 Counter Name VS.RAB.AttEstabPS.Queue Counter Description Number of Queuing Attempts Due to Insufficient Resource in the PS RAB Assignment Establishment Procedure for Cell
Description
This counter provides the queuing attempts initiated by the RNC for the PS service that fails to be set up due to insufficient cell resources.
Measurement point
During the RAB establishment procedure, the RNC initiates queuing for the PS service if the cell has insufficient resources for the service. After a period of time, the RNC tries to assign resources to the service again. The measurement is triggered when the service enters the queue,as shown of point A in Figure1. The counter is measured in the queued cells. Figure 1-810 Queue procedure for admission failure during the RAB establishment
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabPS.Queue Feature ID WRFD-010505 Feature Name Queuing and Pre-Emption
1.12.25.5 Average Duration of a PS Queuing in the RAB Establishment Procedure Counters

Counter ID 73393919 Counter Name VS.RAB.Estab.QueueTime. PS Counter Description Average Duration of a PS Queuing in the RAB Establishment Procedure for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73393968 Counter Name VS.RAB.Estab.QueueTime. PS.CUM Counter Description Duration of RAB queuing in PS domain during the RAB assignment in a cell (Numerator) Duration of RAB queuing in PS domain during the RAB assignment in a cell (Denominator)
73393969
VS.RAB.Estab.QueueTime. PS.SAMPLE
Description
This counter provides the queuing duration for the queued cells. The RNC initiates queuing for the PS service if the cell has insufficient resources for the service. After a period of time, the RNC tries to assign resources to the service again.
Measurement point
During the RAB establishment procedure, the RNC initiates queuing for the PS service if the cell has insufficient resources for the service. After a period of time, the RNC tries to assign resources to the service again. If the service is allocated resources before the related timer expires, this counter measures the queuing duration of this service in the cell where the corresponding UE currently camps.
Issue 01 (2013-05-04)
1795
Formula
VS.RAB.Estab.QueueTime.PS = [VS.RAB.Estab.QueueTime.PS.CUM]/ [VS.RAB.Estab.QueueTime.PS.SAMPLE]
Unit
s
Related Features
Counter Name VS.RAB.Estab.QueueTime. PS Feature ID WRFD-010505 Feature Name Queuing and Pre-Emption
1.12.25.6 Number of Successful PS Establishment After Queuing Counters

Counter ID 73393921 Counter Name VS.RAB.SuccEstabPS.Queu e Counter Description Number of Successful PS Establishment After Queuing for Cell
Description
This counter provides the number of successful establishment of the PS service after the service is queued when the RNC initiates queuing for the PS service that fails to be set up due to insufficient cell resources.
Measurement point
During the RAB establishment procedure, the RNC initiates queuing for the PS service if the cell has insufficient resources for the service. After a period of time, the RNC tries to assign resources to the service again. The measurement is triggered when the service is successfully set up after it is queued,as shown of point C in Figure1. The counter is measured in the queued cells.
Issue 01 (2013-05-04)
1796
Figure 1-811 Queue procedure for admission failure during the RAB establishment
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccEstabPS.Queu e Feature ID WRFD-010505 Feature Name Queuing and Pre-Emption
1.12.25.7 Number of PS RAB Setup Requests for Platinum UEs Performing Conversational Services for Cell Counters
Counter ID 73425924 Counter Name VS.RAB.AttEstabPS.Conv. Platinum Counter Description Number of PS RAB Setup Requests for Platinum UEs Performing Conversational Services for Cell
Issue 01 (2013-05-04)
1797
Description
This counter measures the number of PS RAB setup requests for platinum UEs performing conversational services in the best cells.
Measurement point
The measurement is triggered at point A shown in the figure when the RNC receives from the PS CN a RAB ASSIGNMENT REQUEST message specific to a platinum UE performing conversational services. In this case, this counter is measured in the best cell that the UE camps on. Figure 1-812 RAB setup procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstabPS.Conv. Platinum Feature ID WRFD-150204 Feature Name Platinum User Prioritizing
Issue 01 (2013-05-04)
1798
1.12.25.8 Number of PS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell Counters
Counter ID 73426339 Counter Name VS.AttEstabPS.AfterP2F Counter Description Number of PS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell Number of PS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_DCH for Cell
73426340
VS.AttEstabPS.AfterP2D
Description
These counters measure the number of PS service setups initiated by UEs in the CELL_PCH or URA_PCH state in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. A UE in the CELL_PCH or URA_PCH state initiates PS services and transitions to another state. After the RNC receives a RAB ASSIGNMENT REQUEST message from the PS domain of the CN, the RNC calculates the number of PS service setups in the best cell of the UE based on the UE state. Figure 1-813 RAB setup procedure initiated by UEs in the CELL_PCH or URA_PCH state
Issue 01 (2013-05-04)
1799
The measurement is triggered at point A, as shown in the figure. A UE in the CELL_PCH or URA_PCH state initiates PS services and transitions to another state. After the RNC receives a RAB ASSIGNMENT REQUEST message from the PS domain of the CN, the RNC calculates the number of PS service setups in the best cell of the UE based on the UE state. Figure 1-814 RAB setup procedure initiated by CN RAB assignment requests for UEs in the CELL_PCH or URA_PCH state
Formula
None
Unit
None
Related Features
Counter Name VS.AttEstabPS.AfterP2F Feature ID WRFD-010501 WRFD-010502 VS.AttEstabPS.AfterP2D WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class Conversational QoS Class Streaming QoS Class
Issue 01 (2013-05-04)
1800
1.12.25.9 Number of Successful PS Service Setups Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell Counters
Counter ID 73426341 Counter Name VS.SuccEstabPS.AfterP2F Counter Description Number of Successful PS Service Setups Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell Number of Successful PS Service Setups Initiated by UEs During State Transition from CELL_PCH or URA_PCH to CELL_DCH for Cell
73426342
VS.SuccEstabPS.AfterP2D
Description
These counters measure the number of successful PS service setups initiated by UEs in the CELL_PCH or URA_PCH state in the best cell.
Measurement point
The measurement is triggered at point B, as shown in the figure. A UE in the CELL_PCH or URA_PCH state initiates PS services and transitions to another state. After the RNC receives a RAB ASSIGNMENT REQUEST message from the PS domain of the CN and return a RAB ASSIGNMENT RESPONSE message, the RNC calculates the number of successful PS service setups in the best cell of the UE based on the UE state.
Issue 01 (2013-05-04)
1801
Figure 1-815 RAB setup procedure initiated by UEs in the CELL_PCH or URA_PCH state
The measurement is triggered at point B, as shown in the figure. A UE in the CELL_PCH or URA_PCH state initiates PS services and transitions to another state. After the RNC receives a RAB ASSIGNMENT REQUEST message from the PS domain of the CN and return a RAB ASSIGNMENT RESPONSE message, the RNC calculates the number of successful PS service setups in the best cell of the UE based on the UE state.
Issue 01 (2013-05-04)
1802
Figure 1-816 RAB setup procedure initiated by CN RAB assignment request for UEs in the CELL_PCH or URA_PCH state
Formula
None
Unit
None
Related Features
Counter Name VS.SuccEstabPS.AfterP2F Feature ID WRFD-010501 WRFD-010502 WRFD-010503 WRFD-010504 VS.SuccEstabPS.AfterP2D WRFD-010501 WRFD-010502 WRFD-010503 WRFD-010504 Feature Name Conversational QoS Class Streaming QoS Class Interactive QoS Class Background QoS Class Conversational QoS Class Streaming QoS Class Interactive QoS Class Background QoS Class
Issue 01 (2013-05-04)
1803
1.12.26 Measurement of CS RAB assignment failure per cell (RAB.EstFailCs.Cell)

Overview
The CN in CS domain initiates the radio access bearer setup procedure by sending a RAB ASSIGNMENT REQUEST message to the RNC. After receiving the RAB ASSIGNMENT REQUEST message, the RNC selects an appropriate cell, allocates resources, and performs admission control based on the information in the message (such as service type, QoS, and priority), the traffic load of the system, and the networking strategy (such as DRD). The requirements of high-priority users are met preferentially(That is, when the resources are insufficient and the UEs with low-priority cannot set up the RAB, the RNC sends to the CN a RAB ASSGNMENT RESPONSE message if the queuing algorithm is enabled, indicating that the RAB is in the queue to wait for resources).If the admission of the RAB succeeds, the RNC starts the Iu transport connection setup procedure, the Iub radio bearer setup procedure, and the Uu radio bearer setup procedure. At last, the RNC sends to the CN a RAB ASSNMENT RESPONSE, indicating whether the RAB setup is successful. If DRD is enabled during the RAB setup, the RAB setup measurement is performed on the DRD target cell. Otherwise,if DRD is enabled after the RAB setup, the RAB setup measurement is performed on the DRD source cell. The RAB setup procedure is as follows:
Issue 01 (2013-05-04)
1804
Issue 01 (2013-05-04)
1805
Table 1 describes the measurement points shown in Figure1. Measurement points A~B C D E F Description See:RAB.EstabCS.Cell VS.RAB.FailEstabCS.Cong VS.RAB.FailEstabCS.TNL VS.RAB.FailEstabCS.IubFail VS.RAB.FailEstabCS.UuFail,VS.RAB.Fail EstabCS.RBIncCfg,VS.RAB.FailEstabCS.R BCfgUnsup,VS.RAB.FailEstabCS.UuNoRe ply,VS.RAB.FailEstabCS.PhyChFail,VS.R AB.FailEstabPS.SRBReset,VS.RAB.FailEst abPS.CellUpd VS.RAB.FailEstabCS.RNL
Counters
Counter ID 67189494 Counter Name VS.RAB.FailEstab CS.Cong VS.RAB.FailEstab CS.RNL Counter Description Number of Failed CS RAB Establishments for Cell (Congestion) Number of Failed CS RAB Establishments for Cell (Radio Network Layer Cause) Number of Failed CS RAB Establishments for Cell (Transmission Network Layer Cause) Number of Failed CS RAB Establishments for Cell (DL Iub Bandwidth Congestion) Original Release Earlier than V900R011 Earlier than V900R011
67189495
67189496
VS.RAB.FailEstab CS.TNL
67192610
VS.RAB.FailEstab CS.DLIUBBand.C ong
Issue 01 (2013-05-04)
1806
Counter ID 67192611
Counter Name VS.RAB.FailEstab CS.ULIUBBand.C ong
Counter Description Number of Failed CS RAB Establishments for Cell (UL Iub Bandwidth Congestion) Number of Failed CS RAB Establishments for Cell (UL CE Congestion) Number of Failed CS RAB Establishments for Cell (DL CE Congestion) Number of Failed CS RAB Establishments for Cell (Code Congestion) Number of Failed CS RAB Establishments for Cell(Invalid configuration of UE during the RB setup procedure) Number of Failed CS RAB Establishments for Cell (Configuration unsupported of UE during the RB setup procedure) Number of Failed CS RAB Establishments for Cell(No reply of UE during the RB setup procedure) Number of Failed CS RAB Establishments for Cell(Physical channel failure of UE during the RB setup procedure)
67190406
VS.RAB.FailEstab CS.ULCE.Cong
67190407
VS.RAB.FailEstab CS.DLCE.Cong
67179864
VS.RAB.FailEstab CS.Code.Cong
67193536
VS.RAB.FailEstab CS.RBIncCfg
V900R012
67193537
VS.RAB.FailEstab CS.RBCfgUnsup
V900R012
67193539
VS.RAB.FailEstab CS.UuNoReply
V900R012
67193538
VS.RAB.FailEstab CS.PhyChFail
V900R012
Issue 01 (2013-05-04)
1807
Counter ID 67193611
Counter Name VS.RAB.FailEstab CS.ULPower.Cong
Counter Description Number of Failed CS RAB Establishments for Cell (UL Power Congestion) Number of Failed CS RAB Establishments for Cell (DL Power Congestion) Number of Failed CS RAB Establishments for cell (Radio Link Configuration Failure) Number of Failed CS RAB Establishments for cell (Uu Interface Configuration Failure) Number of Failed CS RAB Establishments for Cell (Unsupported Capabilities) Number of Failed CS RAB Establishments for Cell (Signaling RLC Reset) Number of Failed CS RAB Establishments for Cell (Concurrent Procedures)
67193612
VS.RAB.FailEstab CS.DLPower.Cong
V900R012
73393835
VS.RAB.FailEstab CS.IubFail
V900R012
73393836
VS.RAB.FailEstab CS.UuFail
V900R012
67179830
VS.RAB.FailEstab CS.Unsp
73424884
VS.RAB.FailEstab CS.SRBReset
V900R014
73424885
VS.RAB.FailEstab CS.CellUpd
V900R014
Issue 01 (2013-05-04)
1808
Counter VS.RAB.FailEstabCS.RNL Sub Counter VS.RAB.FailEstabCS.DLIUBBand.Cong VS.RAB.FailEstabCS.ULIUBBand.Cong VS.RAB.FailEstabCS.ULCE.Cong VS.RAB.FailEstabCS.DLCE.Cong VS.RAB.FailEstabCS.Code.Cong VS.RAB.FailEstabCS.ULPower.Cong VS.RAB.FailEstabCS.DLPower.Cong VS.RAB.FailEstabCS.IubFail VS.RAB.FailEstabCS.UuFail VS.RAB.FailEstabCS.SRBReset VS.RAB.FailEstabCS.CellUpd VS.RAB.FailEstabCS.UuFail VS.RAB.FailEstabCS.RBIncCfg VS.RAB.FailEstabCS.RBCfgUnsup VS.RAB.FailEstabCS.UuNoReply VS.RAB.FailEstabCS.PhyChFail
1.12.26.1 Number of CS RABs Unsuccessfully Established due to Congestion Counters

Counter ID 67189494 Counter Name VS.RAB.FailEstabCS.Cong Counter Description Number of Failed CS RAB Establishments for Cell (Congestion) Number of Failed CS RAB Establishments for Cell (DL Iub Bandwidth Congestion) Number of Failed CS RAB Establishments for Cell (UL Iub Bandwidth Congestion) Number of Failed CS RAB Establishments for Cell (UL CE Congestion) Number of Failed CS RAB Establishments for Cell (DL CE Congestion)
67192610
VS.RAB.FailEstabCS.DLIU BBand.Cong VS.RAB.FailEstabCS.ULIU BBand.Cong VS.RAB.FailEstabCS.ULC E.Cong VS.RAB.FailEstabCS.DLC E.Cong
67192611
67190406
67190407
Issue 01 (2013-05-04)
1809
Counter ID 67179864
Counter Name VS.RAB.FailEstabCS.Code. Cong VS.RAB.FailEstabCS.ULPo wer.Cong VS.RAB.FailEstabCS.DLPo wer.Cong
Counter Description Number of Failed CS RAB Establishments for Cell (Code Congestion) Number of Failed CS RAB Establishments for Cell (UL Power Congestion) Number of Failed CS RAB Establishments for Cell (DL Power Congestion)
67193611
67193612
Description
These counters provide the number of failed CS RAB establishments due to congestion in the best cell according to the congestion cause. If congestion occurs both in the uplink and downlink, the counter is measured only in the downlink. For example, when CS RABs fail to be set up due to congestion in both the uplink and downlink power resources, the RNC measures only the VS.RAB.FailEstabCS.DLPower.Cong counter.
Measurement point
The measurement is triggered at point B as shown in the figure. After receiving from the CN an RAB ASSIGNMENT REQUEST message that contains the RAB to be set up, the RNC applies for corresponding radio resources. If the application fails, the RAB setup fails and the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails and the failure cause is any of the following: "No Radio Resources Available in Target cell","Requested Maximum Bit Rate not Available","Requested Maximum Bit Rate for UL not Available","Requested Guaranteed Bit Rate not Available","Requested Guaranteed Bit Rate for DL not Available","Requested Guaranteed Bit Rate for UL not Available","No resource available", and "TQUEUING Expiry". In this case, the RNC measures this counter based on the specific cause in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1810
Figure 1-818 RAB setup procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailEstabCS.Cong Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.FailEstabCS.DLIU BBand.Cong
WRFD-020101 WRFD-010510
Issue 01 (2013-05-04)
1811
Counter Name VS.RAB.FailEstabCS.ULIU BBand.Cong
Feature Name Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.FailEstabCS.ULC E.Cong
WRFD-020101 WRFD-010510
VS.RAB.FailEstabCS.DLC E.Cong
WRFD-020101 WRFD-010510
VS.RAB.FailEstabCS.Code. Cong
WRFD-020101 WRFD-010510
VS.RAB.FailEstabCS.ULPo wer.Cong
WRFD-020101 WRFD-010510
VS.RAB.FailEstabCS.DLPo wer.Cong
WRFD-020101 WRFD-010510
1.12.26.2 Number of Failed CS RABs due to Radio Network Layer Cause Counters
Counter ID 67189495 Counter Name VS.RAB.FailEstabCS.RNL Counter Description Number of Failed CS RAB Establishments for Cell (Radio Network Layer Cause)
Issue 01 (2013-05-04)
1812
Description
This measurement item provies the number of failed CS RABs due to the radio network layer cause in the best cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails due to transmission network connection failure (typical cause: radio resource admission failure). In this case, the RNC measures each item in the best cell that the UE camps on. Figure 1-819 RAB setup procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailEstabCS.RNL Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.26.3 Number of CS RABs Unsuccessfully Established due to Transport Network Layer Cause
Counters
Counter ID 67189496 Counter Name VS.RAB.FailEstabCS.TNL Counter Description Number of Failed CS RAB Establishments for Cell (Transmission Network Layer Cause)
Description
This measurement item provides the number of CS RABs unsuccessfully established due to transport connection setup failure on the Iu-CS interface in the best cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message with the failure cause of "Signalling Transport Resource Failure" or "Iu-CS Interface Transport Connection Failed to Establish", indicating that the RAB unsuccessfully established, this counter is measured in the best cell that the UE camps on. Figure 1-820 RAB setup procedure (failed operation)
Formula
None
Issue 01 (2013-05-04)
1814
Unit
None
Related Features
Counter Name VS.RAB.FailEstabCS.TNL Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.26.4 Number of CS RABs Unsuccessfully Established due to Different Reasons of UE During the RB Setup Procedure for Cell Counters
Counter ID 67193536 Counter Name VS.RAB.FailEstabCS.RBIn cCfg Counter Description Number of Failed CS RAB Establishments for Cell (Invalid configuration of UE during the RB setup procedure) Number of Failed CS RAB Establishments for Cell (Configuration unsupported of UE during the RB setup procedure) Number of Failed CS RAB Establishments for Cell(No reply of UE during the RB setup procedure) Number of Failed CS RAB Establishments for Cell (Physical channel failure of UE during the RB setup procedure) Number of Failed CS RAB Establishments for Cell (Signaling RLC Reset) Number of Failed CS RAB Establishments for Cell (Concurrent Procedures)
67193537
VS.RAB.FailEstabCS.RBCf gUnsup
67193539
VS.RAB.FailEstabCS.UuNoReply
67193538
VS.RAB.FailEstabCS.PhyC hFail
73424884
VS.RAB.FailEstabCS.SRB Reset VS.RAB.FailEstabCS.CellUpd
73424885
Issue 01 (2013-05-04)
1815
Description
This measurement item provides the number of CS RABs unsuccessfully established due to different reason of UE during the RB setup procedure in the best cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails and the failure causes are described below. In this case, the RNC measures each item in the best cell that the UE camps on. The failure causes may be the following: invalid configuration of UE, configuration unsupported of UE,UU interface physical channel failure. Figure 1-821 RAB setup procedure (failed operation)
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the UE response timeouts and the failure cause is no reply of UE. In this case, the RNC measures the item in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1816
Figure 1-822 RAB setup procedure (UE response timeouts)
The measurement is triggered at point B as shown in the figure. The RNC measures this counter in the best cell that the UE camps on when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails due to the reset of the RLC that carries the RADIO BEARER SETUP message. The cause value is "RB Setup and Cell Update Overlap". Figure 1-823 RAB setup procedure (RB Setup and Cell Update Overlap)
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails with the failure
cause of "RB Setup and Cell Update Overlap." In this case, the RNC measures this counter in the best cell that the UE camps on. Figure 1-824 RAB setup procedure (RB Setup and Cell Update Overlap)
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailEstabCS.RBIn cCfg Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.FailEstabCS.RBCf gUnsup
WRFD-010510
VS.RAB.FailEstabCS.UuNoReply
WRFD-010510
Issue 01 (2013-05-04)
1818
Counter Name VS.RAB.FailEstabCS.PhyC hFail
VS.RAB.FailEstabCS.SRB Reset
WRFD-010510
VS.RAB.FailEstabCS.CellUpd
WRFD-010510
1.12.26.5 Number of Failed CS RAB Establishments Due to Radio Link Configuration Failure Counters
Counter ID 73393835 Counter Name VS.RAB.FailEstabCS.IubFail Counter Description Number of Failed CS RAB Establishments for cell (Radio Link Configuration Failure)
Description
This counter provides the number of times RAB assignment fails in the CS domain when radio link configuration fails (because a timeout occurs in the wait for the NodeB to respond or the NodeB responds with a radio link configuration failure message) in the best cell or when a timeout occurs in the wait for a RADIO LINK RESTORE INDICATION message after a RADIO LINK FAIL INDICATION message is received from the NodeB.
Measurement point
Take the RADIO LINK RECONFIGURATION PREPARE message as an example, the measurement is triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request, it requests related radio resources and triggers radio link reconfiguration procedure (or radio link establishment procedure). This counter is measured in the best cell that the UE camps on when a radio link configuration failure message is received. Note that if the NodeB responses with a radio link configuration failure message with the cause of CE resource insufficiency, this counter is not measured, instead, a congestion counter is measured.
Issue 01 (2013-05-04)
1819
Figure 1-825 Failed RAB establishments due to radio link configuration failure
Take the RADIO LINK RECONFIGURATION PREPARE message as an example, the measurement is triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request, it requests related radio resources and triggers radio link reconfiguration procedure (or radio link establishment procedure). This counter is measured in the best cell that the UE camps on when the NodeB response timeouts. Figure 1-826 Failed RAB establishments due to radio link configuration failure
Issue 01 (2013-05-04)
1820
Take the RADIO LINK RECONFIGURATION PREPARE message as an example, the measurement is triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message that contains a RAB establishment request, it requests related radio resources and triggers a radio link reconfiguration procedure (or radio link establishment procedure). After the RNC sends the NodeB a RADIO LINK RECONFIGURATION COMMIT message and then receives a RADIO LINK FAIL INDICATION message from the NodeB, the RNC starts a timer to wait for a RADIO LINK RESTORE INDICATION message from the NodeB. This counter is measured in the best cell that the UE camps on when a RADIO LINK RESTORE INDICATION message is not received before the timer expires. Figure 1-827 Timeout for a RADIO LINK RESTORE INDICATION message after receiving a RADIO LINK FAIL INDICATION message
Formula
None
Unit
None
Issue 01 (2013-05-04)
1821
Related Features
Counter Name VS.RAB.FailEstabCS.IubFail Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.26.6 Number of Failed CS RAB Establishments Due to Uu Interface Configuration Failure Counters
Counter ID 73393836 Counter Name VS.RAB.FailEstabCS.UuFail Counter Description Number of Failed CS RAB Establishments for cell (Uu Interface Configuration Failure)
Description
This counter provides the number of times that a CS RAB establishment fails due to configuration failure on the Uu interface (UE no response or UE returns a failure message).
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request, it requests related radio resources and triggers Uu interface configuration procedure. This counter is measured in the best cell that the UE camps on when a RB configuration failure message is received.
Issue 01 (2013-05-04)
1822
Figure 1-828 Failed RAB establishments due to Uu interface configuration failure
The measurement is triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request, it requests related radio resources and triggers Uu interface configuration procedure. This counter is measured in the best cell that the UE camps on when the UE response timeouts. Figure 1-829 Failed RAB establishments due to Uu interface configuration failure
Issue 01 (2013-05-04)
1823
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailEstabCS.UuFail Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.26.7 Number of Failed CS RABs due to Unsupported Capabilities (Cell) Counters

Counter ID 67179830 Counter Name VS.RAB.FailEstabCS.Unsp Counter Description Number of Failed CS RAB Establishments for Cell (Unsupported Capabilities)
Description
This measurement item provides the number of failed CS RABs due to unsupported capabilities in the best cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails because of insufficient abilities (such as Resource Admission Failure, License Reject and so on.) and the failure cause is "Requested Traffic Class not Available","Requested Maximum Bit Rate not Available","Requested Maximum Bit Rate for DL not Available","Requested Maximum Bit Rate for UL not Available","Requested Guaranteed Bit Rate not Available","Requested Guaranteed Bit Rate for DL not Available","Requested Guaranteed Bit Rate for UL not Available","Requested Transfer Delay not Achievable" or "No Resource Available". In this case, the RNC measures each item in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1824
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailEstabCS.Unsp Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.27 Measurement of PS RAB assignment failure per cell (RAB.EstFailPs.Cell)

Overview
The CN in PS domain initiates the radio access bearer setup procedure by sending a RAB ASSIGNMENT REQUEST message to the RNC.
After receiving the RAB ASSIGNMENT REQUEST message, the RNC selects an appropriate cell, allocates resources, and performs admission control based on the information in the message (such as service type, QoS, and priority), the traffic load of the system, and the networking strategy (such as DRD). The requirements of high-priority users are met preferentially(That is, when the resources are insufficient and the UEs with low-priority cannot set up the RAB, the RNC sends to the CN a RAB ASSGNMENT RESPONSE message if the queuing algorithm is enabled, indicating that the RAB is in the queue to wait for resources). If the admission of the RAB succeeds, the RNC starts the Iu transport connection setup procedure, the Iub radio bearer setup procedure, and the Uu radio bearer setup procedure. At last, the RNC sends to the CN a RAB ASSNMENT RESPONSE, indicating whether the RAB setup is successful. If DRD is enabled during the RAB setup, the RAB setup measurement is performed on the DRD target cell. Otherwise,if DRD is enabled after the RAB setup, the RAB setup measurement is performed on the DRD source cell. The RAB setup procedure is as follows.
Issue 01 (2013-05-04)
1826
Issue 01 (2013-05-04)
1827
Table 1 describes the measurement points shown in Figure1. Measurement points A~B C D E F Description See:RAB.EstabPS.Cell VS.RAB.FailEstabPS.Cong VS.RAB.FailEstabPS.TNL VS.RAB.FailEstabPS.IubFail VS.RAB.FailEstabPS.UuFail,VS.RAB.Fail EstabPS.UuNoReply,VS.RAB.FailEstabPS. RBIncCfg,VS.RAB.FailEstabPS.RBCfgUns upp,VS.RAB.FailEstabPS.PhyChFail,VS.R AB.FailEstabPS.UuFail,VS.RAB.FailEstab PS.SRBReset,VS.RAB.FailEstabPS.CellUpd VS.RAB.FailEstabPS.RNL
Counters
Counter ID 67192612 Counter Name VS.RAB.FailEstab PS.DLIUBBand.Co ng Counter Description Number of Failed PS RAB Establishments for Cell (DL Iub Bandwidth Congestion) Number of Failed PS RAB Establishments for Cell (UL Iub Bandwidth Congestion) Number of Failed PS RAB Establishments for Cell (Radio Network Layer Cause) Number of Failed PS RAB Establishments for Cell (Transport Network Layer Cause) Original Release Earlier than V900R011
67192613
VS.RAB.FailEstab PS.ULIUBBand.Co ng
67189556
VS.RAB.FailEstab PS.RNL
67189557
VS.RAB.FailEstab PS.TNL
Issue 01 (2013-05-04)
1828
Counter ID 67190408
Counter Name VS.RAB.FailEstab PS.ULCE.Cong
Counter Description Number of Failed PS RAB Establishments for Cell (UL CE Congestion) Number of Failed PS RAB Establishments for Cell (DL CE Congestion) Number of Failed PS RAB Establishments for Cell (Code Congestion) Number of Failed PS RAB Establishments for Cell (UU interface invalid configuration) Number of Failed PS RAB Establishments for Cell (Configuration unsupported of UE during the RB setup procedure) Number of Failed PS RAB Establishments for Cell (No reply of UE during the RB setup procedure) Number of Failed PS RAB Establishments for Cell (Physical channel failure of UE during the RB setup procedure) Number of Failed PS RAB Establishments for Cell (UL Power Congestion) Number of Failed PS RAB Establishments for Cell (DL Power Congestion)
67190409
VS.RAB.FailEstab PS.DLCE.Cong
67179967
VS.RAB.FailEstab PS.Code.Cong
67193540
VS.RAB.FailEstab PS.RBIncCfg
V900R012
67193541
VS.RAB.FailEstab PS.RBCfgUnsupp
V900R012
67193543
VS.RAB.FailEstab PS.UuNoReply
V900R012
67193542
VS.RAB.FailEstab PS.PhyChFail
V900R012
67193613
VS.RAB.FailEstab PS.ULPower.Cong
V900R012
67193614
VS.RAB.FailEstab PS.DLPower.Cong
V900R012
Issue 01 (2013-05-04)
1829
Counter ID 73393837
Counter Name VS.RAB.FailEstab PS.IubFail
Counter Description Number of Failed PS RAB Establishments Due to Radio Link Configuration Failure for Cell Number of Failed PS RAB Establishments Due to Uu Interface Configuration Failure for Cell Number of Failed PS RAB Establishments for Cell (Unsupported Capabilities) Number of Failed PS RAB Establishments for Cell (Congestion) Number of PS Free RAB Setup Failures due to DL Power Resource Congestion for Cell Number of Failed PS RAB Establishments for Cell (Signaling RLC Reset) Number of Failed PS RAB Establishments for Cell (Concurrent Procedures) Number of Failed PS RAB Establishments for Cell (New RAB Setup Failures When the Maximum Number of HSUPA UEs Is Reached)
73393838
VS.RAB.FailEstab PS.UuFail
V900R012
67179930
VS.RAB.FailEstab PS.Unsp
73394298
VS.RAB.FailEstab PS.Cong VS.RAB.FailEstab PS.DLPower.Cong. Free
V900R012
73423519
V900R013
73424886
VS.RAB.FailEstab PS.SRBReset
V900R014
73424887
VS.RAB.FailEstab PS.CellUpd
V900R014
73424888
VS.RAB.FailEstab PS.HSUPAUser.Co ng
V900R014
Issue 01 (2013-05-04)
1830
Counter ID 73424889
Counter Name VS.RAB.FailEstab PS.HSDPAUser.Co ng
Counter Description Number of Failed PS RAB Establishments for Cell (New RAB Setup Failures When the Maximum Number of HSDPA UEs Is Reached)
Counter VS.RAB.FailEstabPS.RNL Sub Counter VS.RAB.FailEstabPS.DLIUBBand.Cong VS.RAB.FailEstabPS.ULIUBBand.Cong VS.RAB.FailEstabPS.ULCE.Cong VS.RAB.FailEstabPS.DLCE.Cong VS.RAB.FailEstabPS.Code.Cong VS.RAB.FailEstabPS.ULPower.Cong VS.RAB.FailEstabPS.DLPower.Cong VS.RAB.FailEstabPS.IubFail VS.RAB.FailEstabPS.UuFail VS.RAB.FailEstabPS.SRBReset VS.RAB.FailEstabPS.CellUpd VS.RAB.FailEstabPS.HSUPAUser.Cong VS.RAB.FailEstabPS.HSDPAUser.Cong VS.RAB.FailEstabPS.UuFail VS.RAB.FailEstabPS.RBIncCfg VS.RAB.FailEstabPS.RBCfgUnsupp VS.RAB.FailEstabPS.UuNoReply VS.RAB.FailEstabPS.PhyChFail VS.RAB.FailEstabPS.Unsp VS.RAB.FailEstabPS.Cong
1.12.27.1 Number of PS RABs Unsuccessfully Established due to Radio Network Layer Cause for Cell
Issue 01 (2013-05-04)
1831
Counters
Counter ID 67189556 Counter Name VS.RAB.FailEstabPS.RNL Counter Description Number of Failed PS RAB Establishments for Cell (Radio Network Layer Cause)
Description
The measurement items provide the number of PS RABs unsuccessfully established in the best cell due to radio network layer cause.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails and the failure cause is "Radio Network Layer Cause" (typical cause: radio resource admission failure). In this case, the RNC measures each item in the best cell that the UE camps on. Figure 1-832 PS RAB setup procedure (failed operation)
Formula
None
Unit
None
Issue 01 (2013-05-04)
1832
Related Features
Counter Name VS.RAB.FailEstabPS.RNL Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.27.2 Number of PS RABs Unsuccessfully Established due to Transport Network Layer Cause Counters
Counter ID 67189557 Counter Name VS.RAB.FailEstabPS.TNL Counter Description Number of Failed PS RAB Establishments for Cell (Transport Network Layer Cause)
Description
This counter provides the number of PS RAB setup failures due to failed transport network on the Iu-PS interface in the best cell that the UE camps on.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message with the failure cause of "Iu-PS Interface Transport Connection Failed to Establish", indicating that the RAB unsuccessfully established, this counter is measured in the best cell that the UE camps on. Figure 1-833 PS RAB setup procedure (failed operation)
Issue 01 (2013-05-04)
1833
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailEstabPS.TNL Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.27.3 Number of Failed PS RABs due to different reasons of UE During the RB Setup Procedure for cell Counters
Counter ID 67193540 Counter Name VS.RAB.FailEstabPS.RBIn cCfg Counter Description Number of Failed PS RAB Establishments for Cell (UU interface invalid configuration) Number of Failed PS RAB Establishments for Cell (Configuration unsupported of UE during the RB setup procedure) Number of Failed PS RAB Establishments for Cell (No reply of UE during the RB setup procedure) Number of Failed PS RAB Establishments for Cell (Physical channel failure of UE during the RB setup procedure) Number of Failed PS RAB Establishments for Cell (Signaling RLC Reset)
1834
67193541
VS.RAB.FailEstabPS.RBCf gUnsupp
67193543
VS.RAB.FailEstabPS.UuNoReply
67193542
VS.RAB.FailEstabPS.PhyC hFail
73424886
VS.RAB.FailEstabPS.SRBR eset
Issue 01 (2013-05-04)
Counter ID 73424887
Counter Name VS.RAB.FailEstabPS.CellUpd
Counter Description Number of Failed PS RAB Establishments for Cell (Concurrent Procedures)
Description
This measurement item provides the number of failed PS RABs due to different reasons of UE in the best cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails and the failure causes are described below. In this case, the RNC measures each item in the best cell that the UE camps on. The failure causes may be the following: invalid configuration of UE, configuration unsupported of UE, physical channel failure of UE. Figure 1-834 RAB setup procedure (failed operation)
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the UE response timeouts and the failure cause is no reply of UE. In this case, the RNC measures the item in the best cell that the UE camps on.
Figure 1-835 RAB setup procedure (UE response timeouts)
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails and the failure cause is "RB Setup and Cell Update Overlap." In this case, the RNC measures this counter in the best cell that the UE camps on. Figure 1-836 RAB setup procedure(RB Setup and Cell Update Overlap)
The measurement is triggered at point B as shown in the figure. The RNC measures this counter in the best cell that the UE camps on when the RNC sends the CN a RAB ASSIGNMENT
RESPONSE message indicating that the operation fails due to the reset of the RLC that carries the RADIO BEARER SETUP message. The cause value is "RB Setup and Cell Update Overlap". Figure 1-837 RAB setup procedure(RB Setup and Cell Update Overlap)
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailEstabPS.RBIn cCfg Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.FailEstabPS.RBCf gUnsupp
WRFD-010510
VS.RAB.FailEstabPS.UuNoReply
WRFD-010510
Issue 01 (2013-05-04)
1837
Counter Name VS.RAB.FailEstabPS.PhyC hFail
VS.RAB.FailEstabPS.SRBR eset
WRFD-010510
VS.RAB.FailEstabPS.CellUpd
WRFD-010510
1.12.27.4 Number of Failed PS RAB Establishments Due to Radio Link Configuration Failure Counters
Counter ID 73393837 Counter Name VS.RAB.FailEstabPS.IubFail Counter Description Number of Failed PS RAB Establishments Due to Radio Link Configuration Failure for Cell
Description
This counter provides the number of times RAB assignment fails in the PS domain when radio link configuration fails (because a timeout occurs in the wait for the NodeB to respond or the NodeB responds with a radio link configuration failure message) in the best cell or when a timeout occurs in the wait for a RADIO LINK RESTORE INDICATION message after a RADIO LINK FAIL INDICATION message is received from the NodeB.
Measurement point
Take the RADIO LINK RECONFIGURATION PREPARE message as an example, the measurement is triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request, it requests related radio resources and triggers radio link reconfiguration procedure (or radio link establishment procedure). This counter is measured in the best cell that the UE camps on when a radio link configuration failure message is received. Note that if the NodeB responses with a radio link configuration failure message with the cause of CE resource insufficiency, this counter is not measured, instead, a congestion counter is measured.
Issue 01 (2013-05-04)
1838
Figure 1-838 Failed RAB establishments due to radio link configuration failure
Take the RADIO LINK RECONFIGURATION PREPARE message as an example, the measurement is triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request, it requests related radio resources and triggers radio link reconfiguration procedure (or radio link establishment procedure). This counter is measured in the best cell that the UE camps on when the NodeB response timeouts. Figure 1-839 Failed RAB establishments due to radio link configuration failure
Issue 01 (2013-05-04)
1839
Take the RADIO LINK RECONFIGURATION PREPARE message as an example, the measurement is triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message that contains a RAB establishment request, it requests related radio resources and triggers a radio link reconfiguration procedure (or radio link establishment procedure). After the RNC sends the NodeB a RADIO LINK RECONFIGURATION COMMIT message and then receives a RADIO LINK FAIL INDICATION message from the NodeB, the RNC starts a timer to wait for a RADIO LINK RESTORE INDICATION message from the NodeB. This counter is measured in the best cell that the UE camps on when a RADIO LINK RESTORE INDICATION message is not received before the timer expires. Figure 1-840 Timeout for a RADIO LINK RESTORE INDICATION message after receiving a RADIO LINK FAIL INDICATION message
Formula
None
Unit
None
Issue 01 (2013-05-04)
1840
Related Features
Counter Name VS.RAB.FailEstabPS.IubFail Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.27.5 Number of Failed PS RAB Establishments Due to Uu Interface Configuration Failure Counters
Counter ID 73393838 Counter Name VS.RAB.FailEstabPS.UuFail Counter Description Number of Failed PS RAB Establishments Due to Uu Interface Configuration Failure for Cell
Description
This counter provides the number of times that a PS RAB establishment fails due to configuration failure on the Uu interface (UE no response, UE returns a failure message).
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request, it requests related radio resources and triggers Uu interface configuration procedure. This counter is measured in the best cell that the UE camps on when a RB configuration failure message is received.
Issue 01 (2013-05-04)
1841
Figure 1-841 Failed RAB establishments due to Uu interface configuration failure
The measurement is triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request, it requests related radio resources and triggers Uu interface configuration procedure. This counter is measured in the best cell that the UE camps on when the UE response timeouts. Figure 1-842 Failed RAB establishments due to Uu interface configuration failure
Issue 01 (2013-05-04)
1842
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailEstabPS.UuFail Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.27.6 Number of Failed PS RABs due to Unsupported Capabilities (Cell) Counters

Counter ID 67179930 Counter Name VS.RAB.FailEstabPS.Unsp Counter Description Number of Failed PS RAB Establishments for Cell (Unsupported Capabilities)
Description
This measurement item provides the number of failed PS RABs due to insufficient abilities in the best cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails because of insufficient abilities (such as Resource Admission Failure, License Reject and so on.) and the failure cause is "Requested Traffic Class not Available","Requested Maximum Bit Rate not Available","Requested Maximum Bit Rate for DL not Available","Requested Maximum Bit Rate for UL not Available","Requested Guaranteed Bit Rate not Available","Requested Guaranteed Bit Rate for DL not Available","Requested Guaranteed Bit Rate for UL not Available","Requested Transfer Delay not Achievable" or "No Resource Available". In this case, the RNC measures each item in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1843
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailEstabPS.Unsp Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.27.7 Number of PS RABs Unsuccessfully Established due to Congestion
Issue 01 (2013-05-04)
1844
Counters
Counter ID 73394298 Counter Name VS.RAB.FailEstabPS.Cong Counter Description Number of Failed PS RAB Establishments for Cell (Congestion) Number of Failed PS RAB Establishments for Cell (DL Iub Bandwidth Congestion) Number of Failed PS RAB Establishments for Cell (UL Iub Bandwidth Congestion) Number of Failed PS RAB Establishments for Cell (UL CE Congestion) Number of Failed PS RAB Establishments for Cell (DL CE Congestion) Number of Failed PS RAB Establishments for Cell (Code Congestion) Number of Failed PS RAB Establishments for Cell (UL Power Congestion) Number of Failed PS RAB Establishments for Cell (DL Power Congestion) Number of Failed PS RAB Establishments for Cell (New RAB Setup Failures When the Maximum Number of HSUPA UEs Is Reached) Number of Failed PS RAB Establishments for Cell (New RAB Setup Failures When the Maximum Number of HSDPA UEs Is Reached)
67192612
VS.RAB.FailEstabPS.DLIU BBand.Cong VS.RAB.FailEstabPS.ULIU BBand.Cong VS.RAB.FailEstabPS.ULC E.Cong VS.RAB.FailEstabPS.DLC E.Cong VS.RAB.FailEstabPS.Code. Cong VS.RAB.FailEstabPS.ULPo wer.Cong VS.RAB.FailEstabPS.DLPo wer.Cong VS.RAB.FailEstabPS.HSUP AUser.Cong
67192613
67190408
67190409
67179967
67193613
67193614
73424888
73424889
VS.RAB.FailEstabPS.HSDP AUser.Cong
Description
These counters provide the number of failed PS RAB establishments due to congestion caused by different reasons in the best cell. If congestion occurs both in the uplink and downlink, the counter is measured only in the downlink. For example, when PS RABs fail to be set up due to congestion in both the uplink and downlink power resources, the RNC measures only the VS.RAB.FailEstabPS.DLPower.Cong counter.
Measurement point
The measurement is triggered at point B as shown in the figure. After receiving from the CN an RAB ASSIGNMENT REQUEST message that contains the RAB to be set up, the RNC applies for corresponding radio resources. If the application fails, the RAB setup fails and the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails and the failure cause is any of the following: "No Radio Resources Available in Target cell","Requested Maximum Bit Rate not Available","Requested Maximum Bit Rate for UL not Available","Requested Guaranteed Bit Rate not Available","Requested Guaranteed Bit Rate for DL not Available","Requested Guaranteed Bit Rate for UL not Available","No resource available", and "TQUEUING Expiry". In this case, the RNC measures this counter based on the specific cause in the best cell that the UE camps on. Figure 1-844 RAB setup procedure (failed operation)
Formula
None
Unit
None
Issue 01 (2013-05-04)
1846
Related Features
Counter Name VS.RAB.FailEstabPS.Cong Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.FailEstabPS.DLIU BBand.Cong
WRFD-020101 WRFD-010510
VS.RAB.FailEstabPS.ULIU BBand.Cong
WRFD-020101 WRFD-010510
VS.RAB.FailEstabPS.ULC E.Cong
WRFD-020101 WRFD-010510
VS.RAB.FailEstabPS.DLC E.Cong
WRFD-020101 WRFD-010510
VS.RAB.FailEstabPS.Code. Cong
WRFD-020101 WRFD-010510
VS.RAB.FailEstabPS.ULPo wer.Cong
WRFD-020101 WRFD-010510
VS.RAB.FailEstabPS.DLPo wer.Cong
WRFD-020101 WRFD-010510
Issue 01 (2013-05-04)
1847
Counter Name VS.RAB.FailEstabPS.HSUP AUser.Cong
VS.RAB.FailEstabPS.HSDP AUser.Cong
WRFD-010510
1.12.27.8 Number of PS Free RAB Setup Failures due to DL Power Resource Congestion for Cell Counters
Counter ID 73423519 Counter Name VS.RAB.FailEstabPS.DLPo wer.Cong.Free Counter Description Number of PS Free RAB Setup Failures due to DL Power Resource Congestion for Cell
Description
This counter provides the number of PS free RAB setup failures in the best cell due to DL power resource congestion.
Measurement point
This measurement is triggered at point B as shown in the following figure. When the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message indicating a RAB setup failure, it measures this counter in the best cell on which the UE camps if the PS free RAB setup fails due to DL power resource congestion.
Issue 01 (2013-05-04)
1848
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailEstabPS.DLPo wer.Cong.Free Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.28 Measurement of CS RAB assignment modification per cell (RAB.ModCs.Cell)

Overview
If the parameters, such as QoS, of a CS service are changed after the RAB is set up, the CN sends to the RNC a RAB ASSIGNMENT REQUEST message. After receiving this message, the RNC initiates the RAB modification procedure. If the RAB modification succeeds, the RNC
sends to the CN a RAB ASSIGNMENT RESPONSE message indicating that the RAB modification succeeds. If the RAB modification fails, the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message indicating that the RAB modification fails. For details, see 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Counter ID 67179840 Counter Name VS.RAB.FailModC S.TNL Counter Description Number of Failed CS RAB Modifications Due to Iu Transport Connection Setup Failure for Cell Number of RAB Modification Requests for CS Conversational Services for Cell Number of RAB Modification Requests for CS Streaming Services for Cell Number of Successful CS RAB Modifications for Conversational Services for Cell Number of Successful CS RAB Modifications for Streaming Services for Cell Number of Failed CS RAB Modifications Due to Radio Network Layer Cause for Cell Original Release Earlier than V900R011
67179835
VS.RAB.AttEstMo dCS.Conv
67179836
VS.RAB.AttEstMo dCS.Str
67179837
VS.RAB.SuccMod CS.Conv
67179838
VS.RAB.SuccMod CS.Str
73393839
VS.RAB.FailModC S.RNL
V900R012
None
Issue 01 (2013-05-04)
1850
1.12.28.1 Number of Failed CS RAB Modifications Due to Transport Network Layer Cause Counters
Counter ID 67179840 Counter Name VS.RAB.FailModCS.TNL Counter Description Number of Failed CS RAB Modifications Due to Iu Transport Connection Setup Failure for Cell
Description
This counter provides the number of times that the modification of the CS RAB fails due to transport connection setup failure on the Iu interface in the best cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message with the failure cause of "Signalling Transport Resource Failure" or "Iu Transport Connection Failed to Establish", indicating that the RAB modification fails, this counter is measured in the best cell that the UE camps on. Figure 1-846 CS RAB modification procedure
Issue 01 (2013-05-04)
1851
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailModCS.TNL Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.28.2 Counters Related to the Number of CS RAB Modification Requests Counters

Counter ID 67179835 Counter Name VS.RAB.AttEstModCS.Con v Counter Description Number of RAB Modification Requests for CS Conversational Services for Cell Number of RAB Modification Requests for CS Streaming Services for Cell
67179836
VS.RAB.AttEstModCS.Str
Description
These counters provide the number of RAB modification requests for CS services in the best cell based on the service type.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN in the CS domain, it measures the corresponding counter in the best cell that the UE camps on based on the service type.
Issue 01 (2013-05-04)
1852
Figure 1-847 CS RAB modification procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstModCS.Con v VS.RAB.AttEstModCS.Str Feature ID WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class
1.12.28.3 Counters Related to the Number of Successful CS RAB Modifications
Issue 01 (2013-05-04)
1853
Counters
Counter ID 67179837 Counter Name VS.RAB.SuccModCS.Conv Counter Description Number of Successful CS RAB Modifications for Conversational Services for Cell Number of Successful CS RAB Modifications for Streaming Services for Cell
67179838
VS.RAB.SuccModCS.Str
Description
These counters provide the number of times that the RAB is modified successfully for CS services in the best cell based on the service type.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message, it measures the corresponding counter based on the service type of the RAB in the best cell that the UE camps on only if the RAB is for the CS service. Figure 1-848 RAB modification procedure (successful operation)
Issue 01 (2013-05-04)
1854
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccModCS.Conv VS.RAB.SuccModCS.Str Feature ID WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class
1.12.28.4 Number of Failed CS RAB Modifications Due to Radio Network Layer Cause Counters
Counter ID 73393839 Counter Name VS.RAB.FailModCS.RNL Counter Description Number of Failed CS RAB Modifications Due to Radio Network Layer Cause for Cell
Description
This counter provides the number of times that a CS RAB modifications fails due to radio network fault. The radio network fault can be Requested Maximum Bit Rate not Available, Requested Maximum Bit Rate for DL not Available, Requested Maximum Bit Rate for UL not Available, No Radio Resources Available in Target cell, No resource available or TQUEUING Expiry.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails due to radio network connection failure (typical cause: radio resource admission failure). In this case, the RNC measures each item in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1855
Figure 1-849 RAB assignment failure procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailModCS.RNL Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.29 Measurement of PS RAB assignment modification per cell (RAB.ModPs.Cell)

Overview
If the parameters, such as QoS, of a PS service are changed after the RAB is set up, the CN sends to the RNC a RAB ASSIGNMENT REQUEST message. After receiving this message, the RNC initiates the RAB modification procedure. If the RAB modification succeeds, the RNC sends to
the CN a RAB ASSIGNMENT RESPONSE message indicating that the RAB modification succeeds. If the RAB modification fails, the RNC sends to the CN a RAB ASSIGNMENT RESPONSE message indicating that the RAB modification fails. For details, see 3GPP TS 25.413.
Counters
Counter ID 67179943 Counter Name VS.RAB.FailModP S.TNL Counter Description Number of Failed PS RAB Modifications Due to Iu Transport Connection Failure for Cell Number of RAB Modification Requests for PS Background Services for Cell Number of RAB Modification Requests for PS Conversational Services for Cell Number of RAB Modification Requests for PS Interactive Services for Cell Number of RAB Modification Requests for PS Streaming Services for Cell Number of Successful RAB Modifications for PS Background Services for Cell Number of Successful RAB Modifications for PS Conversational Services for Cell Original Release Earlier than V900R011
67179937
VS.RAB.AttEstMo dPS.Bkg
67179934
VS.RAB.AttEstMo dPS.Conv
67179936
VS.RAB.AttEstMo dPS.Inter
67179935
VS.RAB.AttEstMo dPS.Str
67179941
VS.RAB.SuccMod PS.Bkg
67179938
VS.RAB.SuccMod PS.Conv
Issue 01 (2013-05-04)
1857
Counter ID 67179940
Counter Name VS.RAB.SuccMod PS.Inter
Counter Description Number of Successful RAB Modifications for PS Interactive Services for Cell Number of Successful RAB Modifications for PS Streaming Services for Cell Number of Failed PS RAB Modifications Due to Radio Network Fault for Cell
67179939
VS.RAB.SuccMod PS.Str
73393840
VS.RAB.FailModP S.RNL
V900R012
None
1.12.29.1 Number of Failed PS RAB Modifications Due to Iu Transport Connection Failure Counters
Counter ID 67179943 Counter Name VS.RAB.FailModPS.TNL Counter Description Number of Failed PS RAB Modifications Due to Iu Transport Connection Failure for Cell
Description
This counter provides the number of times that the modification of the PS RAB fails due to transport connection setup failure on the Iu interface in the best cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends to the SGSN a RAB ASSIGNMENT RESPONSE message with the failure cause of "Signalling Transport Resource Failure" or "Iu Transport Connection Failed to Establish", indicating that the RAB modification fails, this counter is measured in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailModPS.TNL Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.29.2 Number of PS RAB Modification Requests
Issue 01 (2013-05-04)
1859
Counters
Counter ID 67179934 Counter Name VS.RAB.AttEstModPS.Con v Counter Description Number of RAB Modification Requests for PS Conversational Services for Cell Number of RAB Modification Requests for PS Background Services for Cell Number of RAB Modification Requests for PS Interactive Services for Cell Number of RAB Modification Requests for PS Streaming Services for Cell
67179937
VS.RAB.AttEstModPS.Bkg
67179936
VS.RAB.AttEstModPS.Inter
67179935
VS.RAB.AttEstModPS.Str
Description
These counters provide the number of RAB modification requests for PS services in the best cell based on the service type.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN, it measures the corresponding counter in the best cell that the UE camps on based on the service type only if the RAB is for PS services. Figure 1-851 PS RAB modification procedure
Issue 01 (2013-05-04)
1860
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttEstModPS.Con v VS.RAB.AttEstModPS.Bkg VS.RAB.AttEstModPS.Inter VS.RAB.AttEstModPS.Str Feature ID WRFD-010501 WRFD-010504 WRFD-010503 WRFD-010502 Feature Name Conversational QoS Class Background QoS Class Interactive QoS Class Streaming QoS Class
1.12.29.3 Number of Successful PS RAB Modifications Counters

Counter ID 67179938 Counter Name VS.RAB.SuccModPS.Conv Counter Description Number of Successful RAB Modifications for PS Conversational Services for Cell Number of Successful RAB Modifications for PS Background Services for Cell Number of Successful RAB Modifications for PS Interactive Services for Cell Number of Successful RAB Modifications for PS Streaming Services for Cell
67179941
VS.RAB.SuccModPS.Bkg
67179940
VS.RAB.SuccModPS.Inter
67179939
VS.RAB.SuccModPS.Str
Description
These counters provide the number of times that the RAB is modified successfully for PS services in the best cell based on the service type.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message, it measures the corresponding counter based on the service type of the RAB in the best cell where the UE camps on only if the RAB is for the PS service. Figure 1-852 PS RAB modification procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SuccModPS.Conv VS.RAB.SuccModPS.Bkg VS.RAB.SuccModPS.Inter VS.RAB.SuccModPS.Str Feature ID WRFD-010501 WRFD-010504 WRFD-010503 WRFD-010502 Feature Name Conversational QoS Class Background QoS Class Interactive QoS Class Streaming QoS Class
Issue 01 (2013-05-04)
1862
1.12.29.4 Number of Failed PS RAB Modifications Due to Radio Network Fault Counters
Counter ID 73393840 Counter Name VS.RAB.FailModPS.RNL Counter Description Number of Failed PS RAB Modifications Due to Radio Network Fault for Cell
Description
This counter provides the number of times that a PS RAB modifications fails due to radio network fault. The radio network fault can be Requested Maximum Bit Rate not Available, Requested Maximum Bit Rate for DL not Available, Requested Maximum Bit Rate for UL not Available, No Radio Resources Available in Target cell, No resource available or TQUEUING Expiry.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails due to transmission network connection failure (typical cause: radio resource admission failure). In this case, the RNC measures each item in the best cell that the UE camps on. Figure 1-853 RAB assignment failure procedure
Issue 01 (2013-05-04)
1863
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.FailModPS.RNL Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.30 Measurement of multi-RAB service per cell (RAB.MultiRab.Cell)

Overview
These counters provide the number of UEs that occupy different types of spreading factors and times that combined services are set up and released.
Counters
Counter ID 67199698 Counter Name VS.SingleRAB.SF4 Counter Description Number of singleRAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 4 for Cell Number of singleRAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 8 for Cell Number of singleRAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 16 for Cell Original Release Earlier than V900R011
67199699
VS.SingleRAB.SF8
67199700
VS.SingleRAB.SF1 6
Issue 01 (2013-05-04)
1864
Counter ID 67199701
Counter Name VS.SingleRAB.SF3 2
Counter Description Number of singleRAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 32 for Cell Number of singleRAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 64 for Cell Number of singleRAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 128 for Cell Number of singleRAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 256 for Cell Number of multiRAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 4 for Cell Number of multiRAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 8 for Cell Number of multiRAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 16 for Cell
67199702
VS.SingleRAB.SF6 4
67199703
VS.SingleRAB.SF1 28
67199704
VS.SingleRAB.SF2 56
67202942
VS.MultRAB.SF4
67199691
VS.MultRAB.SF8
67199692
VS.MultRAB.SF16
Issue 01 (2013-05-04)
1865
Counter ID 67199693
Counter Name VS.MultRAB.SF32
Counter Description Number of multiRAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 32 for Cell Number of multiRAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 64 for Cell Number of multiRAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 128 for Cell Number of multiRAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 256 for Cell Maximum Number of SFs that Have Been Occupied (Let the SFs that Have Been Occupied a Unitary SF of 256) for Cell Mean Number of SFs that Have Been Occupied (Let the SFs that Have Been Occupied a Unitary SF of 256) for Cell Mean Throughput of a Single HSDPA MAC-d Flow in the Case of Multi-RAB Services for Cell
67199694
VS.MultRAB.SF64
67202943
VS.MultRAB.SF12 8
67202944
VS.MultRAB.SF25 6
67191657
VS.RAB.SFOccupy .MAX
67203416
VS.RAB.SFOccupy
73439942
VS.MultiRAB.Mea nThroughput.HSD PA
V900R012
Issue 01 (2013-05-04)
1866
Counter ID 73439943
Counter Name VS.MultiRAB.Mea nThroughput.HSUPA
Counter Description Mean Throughput of a Single HSUPA MAC-d Flow in the Case of Multi-RAB Services for Cell Mean Downlink Throughput of a Single PS R99 RB in the Case of MultiRAB Services for Cell Mean Uplink Throughput of a Single PS R99 RB in the Case of MultiRAB Services for Cell Number of CS+PS Combined Service Setup Requests for Cell Number of Successful CS+PS Combined Service Setups for Cell Number of PS+PS Combined Service Setup Requests for Cell Number of Successful PS+PS Combined Service Setups for Cell Number of Normal CS Service Releases of CS+PS Combined Services for Cell Number of Normal PS Service Releases of PS+PS Combined Services for Cell
73439944
VS.MultiRAB.Mea nThroughput.PSR9 9DL
V900R012
73439945
VS.MultiRAB.Mea nThroughput.PSR9 9UL
V900R012
73421828
VS.MultiRAB.AttE stab.CSPS
V900R012
73421829
VS.MultiRAB.Succ Estab.CSPS
V900R012
73421830
VS.MultiRAB.AttE stab.PSPS
V900R012
73421831
VS.MultiRAB.Succ Estab.PSPS
V900R012
73421832
VS.MultiRAB.CSN ormRel.CSPS
V900R012
73421834
VS.MultiRAB.PSNo rmRel.PSPS
V900R012
Issue 01 (2013-05-04)
1867
Counter ID 73421835
Counter Name VS.MultiRAB.CSA bnormRel.CSPS
Counter Description Number of Abnormal CS Service Releases of CS+PS Combined Services for Cell Number of Abnormal PS Service Releases of PS+PS Combined Services for Cell Number of Abnormal CS Service Releases During PS Service Setup for Cell Number of Abnormal CS Service Releases During PS Service Release for Cell Number of Normal PS Service Releases of CS+PS Combined Services for Cell Number of Abnormal PS Service Releases of CS+PS Combined Services for Cell Number of CS Service Setup Attempts of UEs with an Ongoing PS Service in the CELL_DCH state for Cell Number of Successful CS Service Setups of UEs with an Ongoing PS Service in the CELL_DCH state for Cell
73421837
VS.MultiRAB.PSA bnormRel.PSPS
V900R012
73421838
VS.MultiRAB.CSA bnormRel.PSAtt
V900R012
73421839
VS.MultiRAB.CSA bnormRel.PSRel
V900R012
73421840
VS.MultiRAB.PSN ormRel.CSPS
V900R012
73421841
VS.MultiRAB.PSA bnormRel.CSPS
V900R012
73424024
VS.AttEstabCS.PSi nDCH
V900R014
73424025
VS.SuccEstabCS.P SinDCH
V900R014
Issue 01 (2013-05-04)
1868
Counter ID 73424026
Counter Name VS.AttEstabCS.PSi nFACH
Counter Description Number of CS Service Setup Attempts of UEs with an Ongoing PS Service in the CELL_FACH state for Cell Number of Successful CS Service Setups of UEs with an Ongoing PS Service in the CELL_FACH state for Cell Number of State Transition Attempts from CELL_PCH or URA_PCH to CELL_DCH with the Cause Value of CS Service for Cell Number of Successful State Transitions from CELL_PCH or URA_PCH to CELL_DCH with the Cause Value of CS Service for Cell Number of Abnormal PS Service Releases in the Case of MultiRAB Services for Cell during an interRAT handover( PS Resume Timer Expiry) Number of Normally Released CS and PS Services in CS+PS Combined Services
73424027
VS.SuccEstabCS.P SinFACH
V900R014
73424028
VS.AttPSP2D.CSC onv
V900R014
73424029
VS.SuccPSP2D.CS Conv
V900R014
73425016
VS.MultiRAB.PSA bnormRel.ResumeExp
V900R014
73425977
VS.MultiRAB.CSP SNormRel.CSPS
V900R015
Issue 01 (2013-05-04)
1869
Counter ID 73425978
Counter Name VS.MultiRAB.CSP SAbnormRel.CSPS
Counter Description Number of Abnormally Released CS and PS Services in CS+PS Combined Services
None
1.12.30.1 Mean Number of Single-RAB UEs Occupy the Codes with Different Spreading Factors Counters
Counter ID 67199698 Counter Name VS.SingleRAB.SF4 Counter Description Number of single-RAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 4 for Cell Number of single-RAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 8 for Cell Number of single-RAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 16 for Cell Number of single-RAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 32 for Cell Number of single-RAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 64 for Cell Number of single-RAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 128 for Cell
67199699
VS.SingleRAB.SF8
67199700
VS.SingleRAB.SF16
67199701
VS.SingleRAB.SF32
67199702
VS.SingleRAB.SF64
67199703
VS.SingleRAB.SF128
Issue 01 (2013-05-04)
1870
Counter ID 67199704
Counter Name VS.SingleRAB.SF256
Counter Description Number of single-RAB UEs that Occupy the DL R99 Codes with Spreading Factor (SF) of 256 for Cell
Description
These counters provide the average number of single-RAB or multi-RAB UEs that use the spreading factor (SF) of 4/8/16/32/64/128/256 in a cell.
Measurement point
The RNC periodically takes a sample (sampling periodicity is 5 seconds) from the number of single-RAB and multi-RAT UEs that use the SF of 4/8/16/32/64/128/256 in a cell. At the end of the measurement period, the RNC divides the accumulated number of single-RAB UEs by the number of samples to get the average number of single-RAB and multi-RAT UEs that use the SF of 4/8/16/32/64/128/256 in a cell.
Formula
None
Unit
None
Related Features
Counter Name VS.SingleRAB.SF4 VS.SingleRAB.SF8 VS.SingleRAB.SF16 VS.SingleRAB.SF32 VS.SingleRAB.SF64 VS.SingleRAB.SF128 VS.SingleRAB.SF256 Feature ID WRFD-020108 WRFD-020108 WRFD-020108 WRFD-020108 WRFD-020108 WRFD-020108 WRFD-020108 Feature Name Code Resource Management Code Resource Management Code Resource Management Code Resource Management Code Resource Management Code Resource Management Code Resource Management
1.12.30.2 Mean Number of Multi-RAB UEs Occupy the Codes with Different Spreading Factors
Counters
Counter ID 67202942 Counter Name VS.MultRAB.SF4 Counter Description Number of multi-RAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 4 for Cell Number of multi-RAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 8 for Cell Number of multi-RAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 16 for Cell Number of multi-RAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 32 for Cell Number of multi-RAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 64 for Cell Number of multi-RAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 128 for Cell Number of multi-RAB UEs that Occupy the DL R99 Codes with the Spreading Factor (SF) of 256 for Cell
67199691
VS.MultRAB.SF8
67199692
VS.MultRAB.SF16
67199693
VS.MultRAB.SF32
67199694
VS.MultRAB.SF64
67202943
VS.MultRAB.SF128
67202944
VS.MultRAB.SF256
Description
These counters provide the average number of single-RAB or multi-RAB UEs that use the spreading factor (SF) of 4/8/16/32/64/128/256 in a cell.
Measurement point
The RNC periodically takes a sample (sampling periodicity is 5 seconds) from the number of single-RAB and multi-RAT UEs that use the SF of 4/8/16/32/64/128/256 in a cell. At the end of the measurement period, the RNC divides the accumulated number of single-RAB UEs by the number of samples to get the average number of single-RAB and multi-RAT UEs that use the SF of 4/8/16/32/64/128/256 in a cell.
Issue 01 (2013-05-04)
1872
Formula
None
Unit
None
Related Features
Counter Name VS.MultRAB.SF4 VS.MultRAB.SF8 VS.MultRAB.SF16 VS.MultRAB.SF32 VS.MultRAB.SF64 VS.MultRAB.SF128 VS.MultRAB.SF256 Feature ID WRFD-020108 WRFD-020108 WRFD-020108 WRFD-020108 WRFD-020108 WRFD-020108 WRFD-020108 Feature Name Code Resource Management Code Resource Management Code Resource Management Code Resource Management Code Resource Management Code Resource Management Code Resource Management
1.12.30.3 Max Count of SF which has been occupied Counters

Counter ID 67191657 Counter Name VS.RAB.SFOccupy.MAX Counter Description Maximum Number of SFs that Have Been Occupied (Let the SFs that Have Been Occupied a Unitary SF of 256) for Cell Mean Number of SFs that Have Been Occupied (Let the SFs that Have Been Occupied a Unitary SF of 256) for Cell
67203416
VS.RAB.SFOccupy
Description
The measurement items provide the mean number and the maximum number of occupied codes in a cell. The occupied codes are the codes occupied by the common channel, R99 user, and HSDSCH. The code number is normalized to SF = 256, that is, converted to the code number when SF = 256. The way of the normalization to SF = 256 is to multiply the number when SF = k by 256/k.
Measurement point
The RNC takes a sample from the number of occupied codes in a cell every five seconds and normalize the number to SF = 256. Then calculate the sum of the normalized numbers. At the end of the measurement period, the RNC divides the accumulated number by the number of samples to obtain the mean number of occupied codes in the cell within the measurement period. The maximum number of occupied codes that is reported to the RNC is defined as the maximum number of occupied codes in the cell within the measurement period..
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.SFOccupy.MAX VS.RAB.SFOccupy Feature ID WRFD-020108 WRFD-020108 Feature Name Code Resource Management Code Resource Management
1.12.30.4 Mean Throughput of a Single HSDPA MAC-d Flow in the Case of MultiRAB Services for Cell Counters
Counter ID 73439942 Counter Name VS.MultiRAB.MeanThroug hput.HSDPA Counter Description Mean Throughput of a Single HSDPA MAC-d Flow in the Case of Multi-RAB Services for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73421821 73421820 Counter Name VS.MultiRAB.MeanThroug hput.HSDPA.Times VS.MultiRAB.MeanThroug hput.HSDPA.Traffic Counter Description VS.MultiRAB.MeanThroug hput.HSDPA.Times VS.MultiRAB.MeanThroug hput.HSDPA.Traffic
Issue 01 (2013-05-04)
1874
Description
This counter provides the mean throughput of a single HSDPA MAC-d flow in the case of MultiRAB services in the HSDPA cell. For DC-HSDPA users, this counter is measured only in the primary cell based on the total throughput on the primary and secondary carriers.
Measurement point
When users initiate Multi-RAB services in an HSDPA cell and there is data transmission in the HSDPA cell, the total period of time used for transmitting data and the total number of bits transmitted in the HSDPA cell are calculated. At the end of the measurement period, the mean throughput of a single MAC-d flow at the RLC layer in a cell is calculated by dividing the total number of bits by the total period of time. Note that the total number of measured bits excludes RLC headers and retransmitted data.
Formula
VS.MultiRAB.MeanThroughput.HSDPA = {8}* [VS.MultiRAB.MeanThroughput.HSDPA.Traffic]/ [VS.MultiRAB.MeanThroughput.HSDPA.Times]
Unit
kbit/s
Related Features
Counter Name VS.MultiRAB.MeanThroug hput.HSDPA Feature ID WRFD-010609 WRFD-01061505 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services
1.12.30.5 Mean Throughput of a Single HSUPA MAC-d Flow in the Case of MultiRAB Services for Cell Counters
Counter ID 73439943 Counter Name VS.MultiRAB.MeanThroug hput.HSUPA Counter Description Mean Throughput of a Single HSUPA MAC-d Flow in the Case of Multi-RAB Services for Cell
Counter ID 73421823 73421822
Counter Name VS.MultiRAB.MeanThroug hput.HSUPA.Times VS.MultiRAB.MeanThroug hput.HSUPA.Traffic
Counter Description VS.MultiRAB.MeanThroug hput.HSUPA.Times VS.MultiRAB.MeanThroug hput.HSUPA.Traffic
Description
This counter provides the mean throughput of a single HSUPA MAC-d flow in the case of MultiRAB services in the HSUPA cells of the active set.For DC-HSUPA users, this counter is measured only in the primary cell based on the total throughput on the primary and secondary carriers.
Measurement point
When users initiate Multi-RAB services in HSUPA cells of the active set and there is data transmission in uplink in the HSUPA cells, the total period of time used for transmitting data and the total number of bits transmitted in the HSUPA cells of the active set are calculated. At the end of the measurement period, the mean uplink throughput of a single MAC-d flow at the RLC layer in a cell is calculated by dividing the total number of bits by the total period of time. Note that the total number of measured bits excludes RLC headers and retransmitted data.
Formula
VS.MultiRAB.MeanThroughput.HSUPA = {8}* [VS.MultiRAB.MeanThroughput.HSUPA.Traffic]/ [VS.MultiRAB.MeanThroughput.HSUPA.Times]
Unit
kbit/s
Related Features
Counter Name VS.MultiRAB.MeanThroug hput.HSUPA Feature ID WRFD-010609 WRFD-01061505 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services
1.12.30.6 Mean Downlink Throughput of a Single PS R99 RB in the Case of MultiRAB Services for Cell
Issue 01 (2013-05-04)
1876
Counters
Counter ID 73439944 Counter Name VS.MultiRAB.MeanThroug hput.PSR99DL Counter Description Mean Downlink Throughput of a Single PS R99 RB in the Case of Multi-RAB Services for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73421825 73421824 Counter Name VS.MultiRAB.MeanThroug hput.PSR99DL.Times VS.MultiRAB.MeanThroug hput.PSR99DL.Traffic Counter Description VS.MultiRAB.MeanThroug hput.PSR99DL.Times VS.MultiRAB.MeanThroug hput.PSR99DL.Traffic
Description
This counter provides the mean downlink throughput of a single PS R99 RB in the case of MultiRAB services in cells of the active set.
Measurement point
When users initiate Multi-RAB services and there is PS R99 data transmission in downlink in cells of the active set, the total period of time used for transmitting data and the total number of bits transmitted in the cells of the active set are calculated. At the end of the measurement period, the mean downlink throughput of a single PS R99 RB at the RLC layer in a cell is calculated by dividing the total number of bits by the total period of time. Note that the total number of measured bits excludes RLC headers and retransmitted data.
Formula
VS.MultiRAB.MeanThroughput.PSR99DL = {8}* [VS.MultiRAB.MeanThroughput.PSR99DL.Traffic]/ [VS.MultiRAB.MeanThroughput.PSR99DL.Times]
Unit
kbit/s
Issue 01 (2013-05-04)
1877
Related Features
Counter Name VS.MultiRAB.MeanThroug hput.PSR99DL Feature ID WRFD-010609 WRFD-01061505 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services
1.12.30.7 Mean Uplink Throughput of a Single PS R99 RB in the Case of Multi-RAB Services for Cell Counters
Counter ID 73439945 Counter Name VS.MultiRAB.MeanThroug hput.PSR99UL Counter Description Mean Uplink Throughput of a Single PS R99 RB in the Case of Multi-RAB Services for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73421827 73421826 Counter Name VS.MultiRAB.MeanThroug hput.PSR99UL.Times VS.MultiRAB.MeanThroug hput.PSR99UL.Traffic Counter Description VS.MultiRAB.MeanThroug hput.PSR99UL.Times VS.MultiRAB.MeanThroug hput.PSR99UL.Traffic
Description
This counter provides the mean uplink throughput of a single PS R99 RB in the case of MultiRAB services in cells of the active set.
Measurement point
When users initiate Multi-RAB services and there is PS R99 data transmission in uplink in cells of the active set, the total period of time used for transmitting data and the total number of bits transmitted in cells of the active set are calculated. At the end of the measurement period, the mean uplink throughput of a single PS R99 RB at the RLC layer in a cell is calculated by dividing the total number of bits by the total period of time. Note that the total number of measured bits excludes RLC headers and retransmitted data.
Formula
VS.MultiRAB.MeanThroughput.PSR99UL = {8}* [VS.MultiRAB.MeanThroughput.PSR99UL.Traffic]/ [VS.MultiRAB.MeanThroughput.PSR99UL.Times]
Unit
kbit/s
Related Features
Counter Name VS.MultiRAB.MeanThroug hput.PSR99UL Feature ID WRFD-010609 WRFD-01061505 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services
1.12.30.8 Number of CS+PS Combined Service Setup Requests for Cell Counters
Counter ID 73421828 Counter Name VS.MultiRAB.AttEstab.CS PS VS.MultiRAB.AttEstab.PSP S VS.AttEstabCS.PSinDCH Counter Description Number of CS+PS Combined Service Setup Requests for Cell Number of PS+PS Combined Service Setup Requests for Cell Number of CS Service Setup Attempts of UEs with an Ongoing PS Service in the CELL_DCH state for Cell Number of CS Service Setup Attempts of UEs with an Ongoing PS Service in the CELL_FACH state for Cell
73421830
73424024
73424026
VS.AttEstabCS.PSinFACH
Description
This counter provides the number of RAB setup requests for combined services in the best cell.
Measurement point
The measurement is triggered at point A as shown in the following figure if one or more RABs of a UE already exists in the cell. When receiving from the CN an RAB ASSIGNMENT
REQUEST message, the RNC checks the RAB type carried in the message and determines the combined service type based on the existing RAB type of the UE. The counter is measured in the best cell that the UE camps on if the combined service type is CS+PS. For the combined service type of CS+PS, CS+2PS, or CS+3PS, the counter of CS+PS combined service is measured. For the combined service type of 2PS, 3PS, or 4PS, the counter of PS+PS combined service is measured. VS.MultiRAB.AttEstab.CSPS and VS.MultiRAB.AttEstab.PSPS are measured in scenarios where service setup sequence is not considered. VS.AttEstabCS.PSinDCH and VS.AttEstabCS.PSinFACH are measured in scenarios where PS services are established before CS services. Figure 1-854 RAB setup for combined services
Formula
None
Issue 01 (2013-05-04)
1880
Unit
None
Related Features
Counter Name VS.MultiRAB.AttEstab.CS PS Feature ID WRFD-010609 WRFD-01061505 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services VS.MultiRAB.AttEstab.PSP S WRFD-010609 WRFD-01061505 Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services VS.AttEstabCS.PSinDCH WRFD-010609 WRFD-01061505 Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services VS.AttEstabCS.PSinFACH WRFD-010609 WRFD-01061505 Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services
1.12.30.9 Number of Successful CS+PS Combined Service Setups for Cell Counters
Counter ID 73421829 Counter Name VS.MultiRAB.SuccEstab.C SPS VS.MultiRAB.SuccEstab.P SPS VS.SuccEstabCS.PSinDCH Counter Description Number of Successful CS +PS Combined Service Setups for Cell Number of Successful PS +PS Combined Service Setups for Cell Number of Successful CS Service Setups of UEs with an Ongoing PS Service in the CELL_DCH state for Cell Number of Successful CS Service Setups of UEs with an Ongoing PS Service in the CELL_FACH state for Cell
1881
73421831
73424025
73424027
VS.SuccEstabCS.PSinFACH
Issue 01 (2013-05-04)
Description
This counter provides the number of successful RAB setup requests for combined services in the best cell.
Measurement point
The measurement is triggered at point B as shown in the following figure if one or more RABs of a UE already exists in the cell. When sending an RAB ASSIGNMENT RESPONSE message to the CN after receiving an RADIO BEARER SETUP COMPLETE message from the UE, the RNC checks the RAB type and determines the combined service type based on the existing RAB type of the UE. The counter is measured in the best cell that the UE camps on if the combined service type is CS+PS. For the combined service type of CS+PS, CS+2PS, or CS+3PS, the counter of CS+PS combined service is measured. For the combined service type of 2PS, 3PS, or 4PS, the counter of PS+PS combined service is measured. VS.MultiRAB.SuccEstab.CSPS and VS.MultiRAB.SuccEstab.PSPS are measured in scenarios where service setup sequence is not considered. VS.SuccEstabCS.PSinDCH and VS.SuccEstabCS.PSinFACH are measured in scenarios where PS services are established before CS services.
Issue 01 (2013-05-04)
1882
Figure 1-855 RAB setup for combined services
Formula
None
Unit
None
Issue 01 (2013-05-04)
1883
Related Features
Counter Name VS.MultiRAB.SuccEstab.C SPS Feature ID WRFD-010609 WRFD-01061505 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services VS.MultiRAB.SuccEstab.P SPS WRFD-010609 WRFD-01061505 Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services VS.SuccEstabCS.PSinDCH WRFD-010609 WRFD-01061505 Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services VS.SuccEstabCS.PSinFACH WRFD-010609 WRFD-01061505 Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services
1.12.30.10 Number of Normal CS Service Releases of CS+PS Combined Services for Cell Counters
Counter ID 73421832 Counter Name VS.MultiRAB.CSNormRel. CSPS VS.MultiRAB.CSPSNormR el.CSPS Counter Description Number of Normal CS Service Releases of CS+PS Combined Services for Cell Number of Normally Released CS and PS Services in CS+PS Combined Services
73425977
Description
This counter provides the number of normal combined service releases in the best cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. After receiving an IU RELEASE COMMAND message from the CN, the RNC releases the corresponding RAB and then sends an IU RELEASE COMPLETE message to the CN. If the release cause in the IU
RELEASE COMMAND message is User Inactivity, Normal Release, Successful Relocation, or Network Optimization, or if the RNC has sent a release request with the cause of User Inactivity, Network Optimization, or UE Generated Signalling Connection Release before the RNC receives the IU RELEASE COMMAND message, then the counter is measured in the best cell that the UE camps on according to the combined service type and the released service type. Figure 1-856 RAB release procedure for combined services
The measurement is also triggered at point B as shown in the following figure. After receiving an RAB ASSIGNMENT REQUEST message with an RAB release request from the CN, the RNC releases the corresponding RAB and then sends an RAB ASSIGNMENT RESPONSE message to the CN. If the release cause in the RAB ASSIGNMENT REQUEST message is User Inactivity, Normal Release, Successful Relocation, or Network Optimization, or if the RNC has sent a release request with the cause of User Inactivity, Network Optimization, or UE Generated Signalling Connection Release before the RNC receives the RAB ASSIGNMENT REQUEST message, then the counter is measured in the best cell that the UE camps on according to the combined service type and the released service type.
Issue 01 (2013-05-04)
1885
Figure 1-857 Successful RAB release procedure for combined services
Formula
None
Unit
None
Related Features
Counter Name VS.MultiRAB.CSNormRel. CSPS Feature ID WRFD-010609 WRFD-01061505 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services VS.MultiRAB.CSPSNormR el.CSPS WRFD-010609 WRFD-01061505 Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services
Issue 01 (2013-05-04)
1886
1.12.30.11 Number of Abnormal PS Service Releases of PS+PS Combined Services for Cell Counters
Counter ID 73421837 Counter Name VS.MultiRAB.PSAbnormR el.PSPS VS.MultiRAB.CSAbnormR el.CSPS VS.MultiRAB.CSPSAbnor mRel.CSPS Counter Description Number of Abnormal PS Service Releases of PS+PS Combined Services for Cell Number of Abnormal CS Service Releases of CS+PS Combined Services for Cell Number of Abnormally Released CS and PS Services in CS+PS Combined Services
73421835
73425978
Description
This counter provides the number of abnormal combined service releases in the best cell.
Measurement point
As shown in point A of the figure, when a failure occurs, the RNC sends the CN an IU RELEASE REQUEST message. After receiving the message, the CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE COMMAND message contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on according to the types of the combined service and released service.
Issue 01 (2013-05-04)
1887
Figure 1-858 RAB release procedure for combined services
As shown in point A of the figure, when a failure occurs, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on according to the types of the combined service and released service.
Issue 01 (2013-05-04)
1888
Figure 1-859 RAB release IU REL procedure for combined services
As shown in point A of the figure, when a failure occurs, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on according to the types of the combined service and released service.
Issue 01 (2013-05-04)
1889
Figure 1-860 Iu connection release procedure for combined services
Formula
None
Unit
None
Related Features
Counter Name VS.MultiRAB.PSAbnormR el.PSPS Feature ID WRFD-010609 WRFD-01061505 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services VS.MultiRAB.CSAbnormR el.CSPS WRFD-010609 WRFD-01061505 Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services VS.MultiRAB.CSPSAbnor mRel.CSPS WRFD-010609 WRFD-01061505 Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services
Issue 01 (2013-05-04)
1890
1.12.30.12 Number of Abnormal CS Service Releases During PS Service Setup for Cell Counters
Counter ID 73421838 Counter Name VS.MultiRAB.CSAbnormR el.PSAtt Counter Description Number of Abnormal CS Service Releases During PS Service Setup for Cell
Description
This counter provides the number of times that a CS service is released abnormally during the PS RAB setup in the best cell.
Measurement point
As shown in point A of the figure, when a CS RAB is released abnormally during PS RAB setup, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on. Figure 1-861 RAB release procedure for combined services
As shown in point A of the figure, when a CS RAB is released abnormally during PS RAB setup, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the
CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on. Figure 1-862 RAB release IU REL procedure for combined services
As shown in point A of the figure, when a CS RAB is released abnormally during PS RAB setup, the RNC sends the CN an IU RELEASE REQUEST message. After receiving the message, the CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE COMMAND message contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1892
Formula
None
Unit
None
Related Features
Counter Name VS.MultiRAB.CSAbnormR el.PSAtt Feature ID WRFD-010609 WRFD-01061505 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services
1.12.30.13 Number of Abnormal CS Service Releases During PS Service Release for Cell
Issue 01 (2013-05-04)
1893
Counters
Counter ID 73421839 Counter Name VS.MultiRAB.CSAbnormR el.PSRel Counter Description Number of Abnormal CS Service Releases During PS Service Release for Cell
Description
This counter provides the number of times that a CS service in the combined service is released due to PS service release in the best cell.
Measurement point
As shown in point A of the figure, when a CS RAB is released abnormally during PS RAB release, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on. Figure 1-864 RAB release procedure for combined services
As shown in point A of the figure, when a CS RAB is released abnormally (no response on the Uu interface or SRB reset) during PS RAB release, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (causes except "User Inactivity", "Normal
Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on. Figure 1-865 RAB release IU REL procedure for combined services
As shown in point A of the figure, when a CS RAB is released abnormally (no response on the Uu interface or SRB reset) during PS RAB release, the RNC sends the CN an RAB RELEASE REQUEST message. After receiving the message, the CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE COMMAND message contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1895
Formula
None
Unit
None
Related Features
Counter Name VS.MultiRAB.CSAbnormR el.PSRel Feature ID WRFD-010609 WRFD-01061505 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services
1.12.30.14 Number of Normal PS Service Releases of CS+PS Combined Services for Cell
Issue 01 (2013-05-04)
1896
Counters
Counter ID 73421840 Counter Name VS.MultiRAB.PSNormRel. CSPS Counter Description Number of Normal PS Service Releases of CS+PS Combined Services for Cell
Description
This counter provides the number of times that a PS service in the CS+PS combined service is released successfully in the best cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. After receiving an IU RELEASE COMMAND message from the CN, the RNC releases the corresponding RAB and then sends an IU RELEASE COMPLETE message to the CN. If the release cause in the IU RELEASE COMMAND message is User Inactivity, Normal Release, Successful Relocation, or Network Optimization, or if the RNC has sent a release request with the cause of User Inactivity, Network Optimization, or UE Generated Signalling Connection Release before the RNC receives the IU RELEASE COMMAND message, then the counter is measured in the best cell that the UE camps on according to the combined service type and the released service type. Figure 1-867 RAB release procedure for combined services
The measurement is also triggered at point B as shown in the following figure. After receiving an RAB ASSIGNMENT REQUEST message with an RAB release request from the CN, the RNC releases the corresponding RAB and then sends an RAB ASSIGNMENT RESPONSE
message to the CN. If the release cause in the RAB ASSIGNMENT REQUEST message is User Inactivity, Normal Release, Successful Relocation, or Network Optimization, or if the RNC has sent a release request with the cause of User Inactivity, Network Optimization, or UE Generated Signalling Connection Release before the RNC receives the RAB ASSIGNMENT REQUEST message, then the counter is measured in the best cell that the UE camps on according to the combined service type and the released service type. Figure 1-868 Successful RAB release procedure for combined services
Formula
None
Unit
None
Related Features
Counter Name VS.MultiRAB.PSNormRel. CSPS Feature ID WRFD-010609 WRFD-01061505 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services
1.12.30.15 Number of Abnormal PS Service Releases of CS+PS Combined Services for Cell Counters
Counter ID 73421841 Counter Name VS.MultiRAB.PSAbnormR el.CSPS Counter Description Number of Abnormal PS Service Releases of CS+PS Combined Services for Cell
Description
This counter provides the number of times that a PS service in the CS+PS combined service is released abnormally in the best cell.
Measurement point
As shown in point A of the figure, when a failure occurs, the RNC sends the CN an IU RELEASE REQUEST message. After receiving the message, the CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE COMMAND message contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on according to the types of the combined service and released service. Figure 1-869 RAB release procedure for combined services
Issue 01 (2013-05-04)
1899
As shown in point A of the figure, when a failure occurs, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on according to the types of the combined service and released service. Figure 1-870 RAB release IU REL procedure for combined services
As shown in point A of the figure, when a failure occurs, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on according to the types of the combined service and released service.
Issue 01 (2013-05-04)
1900
Formula
None
Unit
None
Related Features
Counter Name VS.MultiRAB.PSAbnormR el.CSPS Feature ID WRFD-010609 WRFD-01061505 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services
1.12.30.16 Number of State Transition Attempts from CELL_PCH or URA_PCH to CELL_DCH with the Cause Value of CS Service for Cell
Issue 01 (2013-05-04)
1901
Counters
Counter ID 73424028 Counter Name VS.AttPSP2D.CSConv Counter Description Number of State Transition Attempts from CELL_PCH or URA_PCH to CELL_DCH with the Cause Value of CS Service for Cell
Description
This counter measures the number of attempts to transit a UE from the CELL_PCH or URA_PCH to CELL_DCH state with the cause value of CS service in a cell.
Measurement point
The measurement is triggered at point B shown in the figure. When the RNC sends a CELL UPDATE CONFIRM message to a UE, this counter is incremented by one in the cell that the UE camps on when all the following conditions are met: 1. The UE attempts to transit from the CELL_PCH or URA_PCH to CELL_DCH state. 2. The CELL UPDATE message from UE contains the cause value of Originating Conversational Call, Terminating Conversational Call and Emergency Call in Establishment cause(IE). Figure 1-872 Cell update procedure
Issue 01 (2013-05-04)
1902
Formula
None
Unit
None
Related Features
Counter Name VS.AttPSP2D.CSConv Feature ID WRFD-010609 WRFD-01061505 WRFD-010202 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.30.17 Number of Successful State Transitions from CELL_PCH or URA_PCH to CELL_DCH with the Cause Value of CS Service for Cell Counters
Counter ID 73424029 Counter Name VS.SuccPSP2D.CSConv Counter Description Number of Successful State Transitions from CELL_PCH or URA_PCH to CELL_DCH with the Cause Value of CS Service for Cell
Description
This counter measures the number of successful UE state transitions from CELL_PCH or URA_PCH to CELL_DCH with the cause value of CS service in a cell.
Measurement point
The measurement is triggered at point C shown in the figure. When the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from the UE, this counter is incremented by one in the cell that the UE camps on when all the following conditions are met: 1. The UE transits from the CELL_PCH or URA_PCH to CELL_DCH state. 2. The CELL UPDATE message from UE contains the cause value of Originating Conversational Call, Terminating Conversational Call and Emergency Call in Establishment cause(IE).
Formula
None
Unit
None
Related Features
Counter Name VS.SuccPSP2D.CSConv Feature ID WRFD-010609 WRFD-01061505 WRFD-010202 Feature Name Multiple RAB Introduction Package (PS RAB < 2) Combination of Four PS Services UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.30.18 Number of Abnormal PS Service Releases in the Case of Multi-RAB Services for Cell during an inter-RAT handover( PS Resume Timer Expiry)
Issue 01 (2013-05-04)
1904
Counters
Counter ID 73425016 Counter Name VS.MultiRAB.PSAbnormR el.ResumeExp Counter Description Number of Abnormal PS Service Releases in the Case of Multi-RAB Services for Cell during an inter-RAT handover( PS Resume Timer Expiry)
Description
This counter provides the number of PS releases that a UE initiates on the RAN side in the best cell when it does not receive an IU RELEASE COMMAND message from the PS domain in the CN after the related timer expires. After the CS service in the Multi-RAB Services is successfully handed over to a cell which uses another RAT, the related timer starts and then this UE is supposed to receive this message from the PS domain in the CN before the timer expires.
Measurement point
The measurement is triggered at point A as shown in the figure. After the CS service of the UE is successfully handed over to a cell which uses another RAT, if the UE does not receive an IU RELEASE COMMAND message from the PS domain in the CN after the related timer expires, the RAN side sends the UE an IU RELEASE REQUEST message for PS release. This counter is increased by one in the best cell where the UE camps before the inter-RAT handover. Figure 1-874 Procedure for an outgoing inter-RAT handover
Issue 01 (2013-05-04)
1905
Formula
None
Unit
None
Related Features
Counter Name VS.MultiRAB.PSAbnormR el.ResumeExp Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.12.31 Measurement of RAB release per cell (RAB.RelAbnormal.Cell)

Overview
The RAB release can be classified into the following types: 1) The RAB release initiated by the RNC. When the RNC detects that the UE has no data to transmit for a long period or the RNC is faulty (for example, the SRB resets or the AAL2 link on the Iu interface is faulty), the RNC sends to the CN a RAB RELEASE REQUEST message to release the RAB or an IU RELEASE REQUEST message to release the Iu connection. If the cause value is "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", the RAB release is considered as normal release; otherwise, the RAB release is considered as abnormal release. For details, see the middle of the figure. 2) The RAB release initiated by the CN. The RNC initiates the RAB release by sending the RAB ASSIGNMENT REQUEST message and initiates the Iu connection release by sending the IU RELEASE COMMAND message. All the RAB releases initiated by the CN are considered as normal releases. For details, see the left part of the figure. 3) The RAB release initiated by the UE. The UE initiates the RAB release by sending the SIGNALING CONNECTION RELEASE INDICATION message. According to the domain information in the message, the RNC sends an IU RELEASE REQUEST message to the CN node (SGSN or MSC) to release the Iu connection. After the Iu connection is released, the RNC initiates the RRC release if no Iu connection exists in another domain. All the RAB releases initiated by the UE are considered as normal releases. For details, see the right part of the figure. Note: If the Iu interface is reset, released services will be regarded as being normally released. The sub procedures mentioned in figure 1 are as following.
Figure 1-875 Flow chart of call drop
The sub procedures mentioned in figure 1 are as following.
Issue 01 (2013-05-04)
1907
Figure 1-876 Sub flow chart of call drop
Table 2 describes the measurement points shown in Figure2. Measurement points A B C D Description VS.RAB.AbnormRel.CS VS.RAB.NormRel.CS VS.RAB.NormRel.PS VS.RAB.AbnormRel.PS
Issue 01 (2013-05-04)
1908
Counters
Counter ID 67189568 Counter Name VS.RAB.AbnormR el.CS.RF.ULSync Counter Description Number of CS RABs Abnormally Released Due to RF for Cell (Uplink Synchronization Fail) Number of CS Streaming RABs Abnormally Released for Cell Number of RABs Abnormally Released for PS Conversational Services for Cell Number of RABs Abnormally Released for PS Streaming Services for Cell Number of CS Streaming RABs Normally Released for Cell Number of RABs Normally Released for PS Conversational Services for Cell Number of RABs Normally Released for PS Streaming Services for Cell Number of PS RABs Abnormally Released for Cell (Uplink Synchronization Failure) Original Release Earlier than V900R011
67192597
VS.RAB.AbnormR el.CS.Str
67192598
VS.RAB.AbnormR el.PS.Conv
67192599
VS.RAB.AbnormR el.PS.Str
67192600
VS.RAB.NormRel. CS.Str
67192601
VS.RAB.NormRel. PS.Conv
67192602
VS.RAB.NormRel. PS.Str
67189572
VS.RAB.AbnormR el.PS.RF.ULSync
Issue 01 (2013-05-04)
1909
Counter ID 67190505
Counter Name VS.RAB.AbnormR el.CS.RF.UuNoReply
Counter Description Number of CS RABs Abnormally Released Due to RF for Cell (Failure in the Radio Interface Procedure) Number of PS RABs Abnormally Released Due to RF for Cell (Failure in the Radio Interface Procedure) Number of CS RABs Abnormally Released for Cell Number of CS RABs Abnormally Released Due to RF for Cell Number of CS RABs Normally Released for Cell Number of PS RABs Abnormally Released for Cell Number of PS RABs Normally Released for Cell Number of PS RABs Abnormally Released Due to RF for Cell Number of CS RAB Release Requests for Cell (O&M Intervention) Number of CS RAB Release Attempts for Cell (RAB Preemption)
67190506
VS.RAB.AbnormR el.PS.RF.UuNoReply
67179778
VS.RAB.AbnormR el.CS VS.RAB.AbnormR el.CS.RF
67179777
67179779
VS.RAB.NormRel. CS VS.RAB.AbnormR el.PS VS.RAB.NormRel. PS VS.RAB.AbnormR el.PS.RF
67179781
67179782
67179780
67180067
VS.RAB.AbnormR el.CS.OM
67180069
VS.RAB.AbnormR el.CS.Preempt
Issue 01 (2013-05-04)
1910
Counter ID 67180068
Counter Name VS.RAB.AbnormR el.CS.UTRANgen
Counter Description Number of CS RAB Abnormal Releases Triggered by RNC for Cell (UTRAN Cause) Number of PS RAB Abnormal Released Due to O&M Intervention for Cell Number of PS RAB Abnormal Released Due to RAB Preemption for Cell Number of CS 12.2kbit/s AMR RABs Abnormally Released for Cell Number of CS 7.95kbit/s AMR RABs Abnormally Released for Cell Number of CS 5.9kbit/s AMR RABs Abnormally Released for Cell Number of CS 4.75kbit/s AMR RABs Abnormally Released for Cell Number of CS 23.85kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 23.05kbit/s WB AMR RABs Abnormally Released for Cell
67180074
VS.RAB.AbnormR el.PS.OM
67180076
VS.RAB.AbnormR el.PS.Preempt
67190467
VS.RAB.AbnormR el.AMR.12.2
67190468
67190469
67190470
67192201
VS.RAB.AbnormR el.AMRWB.23.85
V900R012
67192202
V900R012
Issue 01 (2013-05-04)
1911
Counter ID 67192203
Counter Name VS.RAB.AbnormR el.AMRWB.19.85
Counter Description Number of CS 19.85kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 18.25kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 15.85kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 14.25kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 12.65kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 8.85kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 6.6kbit/s WB AMR RABs Abnormally Released for Cell Number of CS RABs Abnormally Released for Cell (Signaling RLC Reset) Number of CS RABs Abnormally Released for Cell (Iu Interface AAL2 Link Failure)
67192204
V900R012
67192205
V900R012
67192206
V900R012
67192207
67192208
67192209
V900R012
67180077
VS.RAB.AbnormR el.CS.RF.SRBReset
67180080
VS.RAB.AbnormR el.CS.IuAAL2
Issue 01 (2013-05-04)
1912
Counter ID 67180082
Counter Name VS.RAB.AbnormR el.AMR VS.RAB.NormRel. AMR
Counter Description Number of CS AMR RABs Abnormally Released for Cell Number of CS AMR RABs Normally Released for Cell(not including WBAMR) Number of PS RABs Abnormally Released Due to Signaling RLC Reset for Cell Number of PS RABs Abnormally Released for Cell (Traffic RLC Reset) Number of PS RABs Abnormally Released Due to GTPU Failure for Cell Number of PS Domain RABs Released Due to Congestion for Cell Number of CS Domain RABs Released Due to Congestion for Cell Number of HSDPA RABs Carrying Golden Users BE Traffic Released Due to Congestion for Cell Number of HSDPA RABs Carrying Silver Users BE Traffic Released Due to Congestion for Cell
67190518
67180078
VS.RAB.AbnormR el.PS.RF.SRBReset
67180079
VS.RAB.AbnormR el.PS.RF.TRBReset
67180081
VS.RAB.AbnormR el.PS.GTPULoss
67190840
VS.RAB.AbnormR el.PS.OLC
67190841
VS.RAB.AbnormR el.CS.OLC
67192975
VS.RAB.RelReqPS .BE.HSDPA.Cong. Golden
67192976
VS.RAB.RelReqPS .BE.HSDPA.Cong. Silver
Issue 01 (2013-05-04)
1913
Counter ID 67192977
Counter Name VS.RAB.RelReqPS .BE.HSDPA.Cong. Copper
Counter Description Number of HSDPA RABs Carrying Copper Users BE Traffic Released Due to Congestion for Cell Number of HSUPA RABs Carrying Golden Users BE Traffic Released Due to Congestion for Cell Number of HSUPA RABs Carrying Silver Users BE Traffic Released Due to Congestion for Cell Number of HSUPA RABs Carrying Copper Users BE Traffic Released Due to Congestion for Cell Number of CS 64 kbit/s Conversational RABs Normally Released for Cell Number of PS RABs Mapped on CCH Normally Released for Cell Number of PS RABs Mapped on CCH Abnormally Released for Cell Number of PS RABs Normally Released for Cell (UE Signaling Connection Release)
67192978
VS.RAB.RelReqPS .BE.HSUPA.Cong. Golden
67192979
VS.RAB.RelReqPS .BE.HSUPA.Cong. Silver
67192980
VS.RAB.RelReqPS .BE.HSUPA.Cong. Copper
67191786
VS.RAB.NormRel. CS64
67191791
VS.RAB.NormRel. PS.CCH
67191818
VS.RAB.AbnormR el.PS.CCH
67191835
VS.RAB.NormRel. PS.UEGen
Issue 01 (2013-05-04)
1914
Counter ID 67180083
Counter Name VS.RAB.AbnormR el.CS64
Counter Description Number of CS Conversational 64kbit/s RABs Abnormally Released for Cell Number of CS over HSPA RABs Abnormally Released for Cell Number of CS over HSPA RABs Normal Released for Cell Number of CS VP RABs Released Due to VP Forbiddance for Cell Number of PS RABs at 0 kbit/s Released for Failure to Rate up in the Best Cell Number of CS 23.85kbps AMRWB RABs Normally Released for cell Number of CS 23.05kbps AMRWB RABs Normally Released for cell Number of CS 19.85kbps AMRWB RABs Normally Released for cell Number of CS 18.25kbps AMRWB RABs Normally Released for cell Number of CS 15.85kbps AMRWB RABs Normally Released for cell
67196204
VS.RAB.AbnormR el.CS.HSPA.Conv
67196205
VS.RAB.NormRel. CS.HSPA.Conv VS.RAB.NormRel. VPLimit
67196233
67196302
VS.RAB.NormRel. PS.0kbps.Timeout
73403833
VS.RAB.NormRel. AMRWB.23.85
V900R012
73403834
V900R012
73403835
V900R012
73403836
V900R012
73403837
V900R012
Issue 01 (2013-05-04)
1915
Counter ID 73403838
Counter Name VS.RAB.NormRel. AMRWB.14.25
Counter Description Number of CS 14.25kbps AMRWB RABs Normally Released for cell Number of CS 12.65kbps AMRWB RABs Normally Released for cell Number of CS 8.85kbps AMRWB RABs Normally Released for cell Number of CS 6.60kbps AMRWB RABs Normally Released for cell Number of CS AMRWB RABs Abnormally Released for cell Number of CS AMRWB RABs Normally Released for cell Number of CS RABs Normally Released for Cell (UE Generated Signaling Connection Release) Number of RABs Normally Released for PS BE Services for Cell Number of RABs Abnormally Released for PS BE Services for Cell Number of CS AMR RABs abnormal release Due to RF Failure for cell
73403839
V900R012
73403840
V900R012
73403841
V900R012
73403842
VS.RAB.AbnormR el.AMRWB
V900R012
73403843
VS.RAB.NormRel. AMRWB
V900R012
73393843
VS.RAB.NormRel. CS.UEGen
V900R012
73393845
VS.RAB.NormRel. PS.BE
V900R012
73393846
VS.RAB.AbnormR el.PS.BE
V900R012
73394051
VS.RAB.AbnormR el.AMR.RF
V900R012
Issue 01 (2013-05-04)
1916
Counter ID 73394052
Counter Name VS.RAB.AbnormR el.CS64.RF
Counter Description Number of CS Conversational 64kbit/s RABs abnormal released due to RF failure for cell Number of RABs Abnormally Released for PTT Services for Cell Number of RABs Normally Released for PTT Services for Cell Number of PS R99 RABs abnormally released Due to RF Failure for cell Number of PS R99 RABs abnormally released for cell (Including RF Failure) Number of PS R99 RAB successfully released for cell Number of Normally Released PS RABs that Are in CELL_PCH or URA_PCH State for Cell Number of call drops During the F2P State Transition for Cell Number of Abnormally Released PS RABs that Are in CELL_PCH or URA_PCH State for Cell
73394073
VS.RAB.AbnormR elPS.PTT
V900R012
73394074
VS.RAB.NormRel PS.PTT
V900R012
73403805
VS.RAB.AbnormR el.PSR99.RF
V900R012
73403806
VS.RAB.AbnormR el.PSR99
V900R012
73403807
VS.RAB.NormRel. PSR99 VS.RAB.NormRel. PS.PCH
V900R012
73421882
V900R012
73421886
VS.RAB.AbnormR el.PS.F2P VS.RAB.AbnormR el.PS.PCH
V900R012
73421883
V900R012
Issue 01 (2013-05-04)
1917
Counter ID 73422166
Counter Name VS.RAB.AbnormR el.PS.D2P
Counter Description Number of RABs Abnormally Released for PS Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell Number of RABs Abnormally Released for PS R99 Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell Number of CS RABs Abnormally Released Due to Security Mode Procedure Failure for Cell Number of PS RABs Abnormally Released Due to Security Mode Procedure Failure for Cell Number of Released RABs Triggered by the Second RRC CONNECTION REQUEST Message from the Same UE in the CS Domain for Cell Number of RAB Releases Triggered by the Second RRC CONNECTION REQUEST Message from the Same UE in the PS Domain for Cell
73422169
VS.RAB.AbnormR el.PS.R99D2P
V900R012
73423939
VS.RAB.AbnormR el.CS.Security
V900R014
73423940
VS.RAB.AbnormR el.PS.Security
V900R014
73425979
VS.RAB.NormRel. CS.UEReEst
V900R015
73425980
VS.RAB.NormRel. PS.UEReEst
V900R015
Issue 01 (2013-05-04)
1918
Counter ID 73425981
Counter Name VS.RAB.NormRel. PS.UEReEst.CCH Related
Counter Description Number of RAB Releases Triggered by the Second RRC CONNECTION REQUEST Message from the Same UE in the PS Domain in Common Channelrelated Scenarios for Cell Number of Released PS RABs due to Network Optimization for Cell Number of Abnormally Released PS RABs Triggered by CN for Cell Number of Released CS RABs due to Network Optimization for Cell Number of Abnormally Released PS RABs Triggered by RNC for Cell Number of Abnormally Released CS RABs Triggered by CN for Cell
73426205
VS.RAB.NormRel. PS.NetOpt
V900R015
73426206
VS.RAB.AbnormR el.PS.CN
V900R015
73426207
VS.RAB.NormRel. CS.NetOpt
V900R015
73426209
VS.RAB.AbnormR el.PS.UTRANgen
V900R015
73426208
VS.RAB.AbnormR el.CS.CN
V900R015
Counter VS.RAB.AbnormRel.CS.RF Sub Counter VS.RAB.AbnormRel.CS.RF.ULSync VS.RAB.AbnormRel.CS.RF.UuNoReply VS.RAB.AbnormRel.CS.RF.SRBReset
Issue 01 (2013-05-04)
1919
Counter VS.RAB.AbnormRel.PS.RF
Sub Counter VS.RAB.AbnormRel.PS.RF.ULSync VS.RAB.AbnormRel.PS.RF.UuNoReply VS.RAB.AbnormRel.PS.RF.SRBReset VS.RAB.AbnormRel.PS.RF.TRBReset
VS.RAB.AbnormRel.CS
VS.RAB.AbnormRel.CS.RF VS.RAB.AbnormRel.CS.OM VS.RAB.AbnormRel.CS.Preempt VS.RAB.AbnormRel.CS.UTRANgen VS.RAB.AbnormRel.CS.IuAAL2 VS.RAB.AbnormRel.CS.OLC VS.RAB.AbnormRel.CS.Security
VS.RAB.AbnormRel.PS
VS.RAB.AbnormRel.PS.RF VS.RAB.AbnormRel.PS.OM VS.RAB.AbnormRel.PS.Preempt VS.RAB.AbnormRel.PS.GTPULoss VS.RAB.AbnormRel.PS.OLC VS.RAB.AbnormRel.PS.Security VS.RAB.AbnormRel.PS.UTRANgen
VS.RAB.AbnormRel.AMR
VS.RAB.AbnormRel.AMR.12.2 VS.RAB.AbnormRel.AMR.7.95 VS.RAB.AbnormRel.AMR.5.9 VS.RAB.AbnormRel.AMR.4.75
VS.RAB.AbnormRel.AMRWB
VS.RAB.AbnormRel.AMRWB.23.85 VS.RAB.AbnormRel.AMRWB.23.05 VS.RAB.AbnormRel.AMRWB.19.85 VS.RAB.AbnormRel.AMRWB.18.25 VS.RAB.AbnormRel.AMRWB.15.85 VS.RAB.AbnormRel.AMRWB.14.25 VS.RAB.AbnormRel.AMRWB.12.65 VS.RAB.AbnormRel.AMRWB.8.85 VS.RAB.AbnormRel.AMRWB.6.6
VS.RAB.NormRel.PSR99
VS.RAB.NormRel.PS.CCH
Issue 01 (2013-05-04)
1920
Counter VS.RAB.NormRel.AMRWB
Sub Counter VS.RAB.NormRel.AMRWB.23.85 VS.RAB.NormRel.AMRWB.23.05 VS.RAB.NormRel.AMRWB.19.85 VS.RAB.NormRel.AMRWB.18.25 VS.RAB.NormRel.AMRWB.15.85 VS.RAB.NormRel.AMRWB.14.25 VS.RAB.NormRel.AMRWB.12.65 VS.RAB.NormRel.AMRWB.8.85 VS.RAB.NormRel.AMRWB.6.60
VS.RAB.NormRel.PS.UEReEst
VS.RAB.NormRel.PS.UEReEst.CCHRelated
1.12.31.1 Number of CS RABs Abnormally Released Due to Different RF Causes for Cell Counters
Counter ID 67189568 Counter Name VS.RAB.AbnormRel.CS.RF .ULSync Counter Description Number of CS RABs Abnormally Released Due to RF for Cell (Uplink Synchronization Fail) Number of CS RABs Abnormally Released Due to RF for Cell (Failure in the Radio Interface Procedure) Number of CS RABs Abnormally Released for Cell (Signaling RLC Reset)
67190505
VS.RAB.AbnormRel.CS.RF .UuNoReply
67180077
VS.RAB.AbnormRel.CS.RF .SRBReset
Description
These measurement items provide the number of RABs abnormally released triggered by the RNC due to different RF failures in the best cell.The RF failure includes "Radio Connection With UE Lost" and "Failure in the Radio Interface Procedure".
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message with the cause value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure" (see 3GPP TS 25.413 for details) due to RF failure
(for example:SRB reset, radio link synchronous failure or UU interface no reply,etc.). If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items in the best cell that the UE camps on according to different RF failures if the released RABs belong to CS domain. Figure 1-877 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message with the cause value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure" (see 3GPP TS 25.413 for details) due to RF failure (for example:SRB reset, radio link synchronous failure or UU interface no reply,etc.). If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items in the best cell that the UE camps on according to different RF failures if the released RABs belong to CS domain.
Issue 01 (2013-05-04)
1922
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message with the cause value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure" (see 3GPP TS 25.413 for details) due to RF failure (for example:SRB reset, radio link synchronous failure or UU interface no reply,etc.). If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items in the best cell that the UE camps on according to different RF failures if the released RABs belong to CS domain.
Issue 01 (2013-05-04)
1923
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.CS.RF .ULSync Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AbnormRel.CS.RF .UuNoReply
WRFD-010510
VS.RAB.AbnormRel.CS.RF .SRBReset
WRFD-010510
Issue 01 (2013-05-04)
1924
1.12.31.2 Number of CS RABs Abnormally Released for Different Services Counters

Counter ID 67192597 Counter Name VS.RAB.AbnormRel.CS.Str Counter Description Number of CS Streaming RABs Abnormally Released for Cell Number of CS Conversational 64kbit/s RABs Abnormally Released for Cell Number of CS over HSPA RABs Abnormally Released for Cell
67180083
VS.RAB.AbnormRel.CS64
67196204
VS.RAB.AbnormRel.CS.HS PA.Conv
Description
These measurement items take statistics of the number of CS RABs abnormally released according to different types of service in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items according to the service types in the best cell that the UE camps on if the released RABs belong to CS domain.
Issue 01 (2013-05-04)
1925
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items according to the service types in the best cell that the UE camps on if the released RABs belong to CS domain.
Issue 01 (2013-05-04)
1926
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items according to the service types in the best cell that the UE camps on if the released RABs belong to CS domain.
Issue 01 (2013-05-04)
1927
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.CS.Str Feature ID WRFD-010502 WRFD-010510 Feature Name Streaming QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Conversational QoS Class CS voice over HSPA/HSPA +
VS.RAB.AbnormRel.CS64 VS.RAB.AbnormRel.CS.HS PA.Conv
WRFD-010501 WRFD-010619
1.12.31.3 Number of PS RABs Abnormally Released for Different Services

Counters
Counter ID 67192598 Counter Name VS.RAB.AbnormRel.PS.Co nv Counter Description Number of RABs Abnormally Released for PS Conversational Services for Cell Number of RABs Abnormally Released for PS Streaming Services for Cell Number of RABs Abnormally Released for PS BE Services for Cell
67192599
VS.RAB.AbnormRel.PS.Str
73393846
VS.RAB.AbnormRel.PS.BE
Description
These measurement items take statistics of the number of PS RABs abnormally released according to different types of service in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items according to the service types in the best cell that the UE camps on if the released RABs belong to PS domain. Figure 1-883 RAB release procedure
Issue 01 (2013-05-04)
1929
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items according to the service types in the best cell that the UE camps on if the released RABs belong to PS domain. Figure 1-884 RAB release IU REL procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items according to the service types in the best cell that the UE camps on if the released RABs belong to PS domain.
Issue 01 (2013-05-04)
1930
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.Co nv Feature ID WRFD-010501 WRFD-010510 Feature Name Conversational QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Streaming QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AbnormRel.PS.Str
WRFD-010502 WRFD-010510
Issue 01 (2013-05-04)
1931
Counter Name VS.RAB.AbnormRel.PS.BE
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Interactive QoS Class Background QoS Class
1.12.31.4 Number of CS RABs Normally Released for Different Services Counters

Counter ID 67192600 Counter Name VS.RAB.NormRel.CS.Str Counter Description Number of CS Streaming RABs Normally Released for Cell Number of CS AMR RABs Normally Released for Cell (not including WB-AMR) Number of CS 64 kbit/s Conversational RABs Normally Released for Cell
67190518
VS.RAB.NormRel.AMR
67191786
VS.RAB.NormRel.CS64
Description
The measurement items provide the number of RABs normally released according to different CS service type in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the items by the service type in the best cell which the UE camps on.
Issue 01 (2013-05-04)
1932
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the items by the service type in the best cell which the UE camps on.
Issue 01 (2013-05-04)
1933
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.CS.Str Feature ID WRFD-010502 WRFD-010510 Feature Name Streaming QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Conversational QoS Class Conversational QoS Class
VS.RAB.NormRel.AMR VS.RAB.NormRel.CS64
WRFD-010501 WRFD-010501
1.12.31.5 Number of PS RABs Normally Released for Different Services

Counters
Counter ID 67192601 Counter Name VS.RAB.NormRel.PS.Conv Counter Description Number of RABs Normally Released for PS Conversational Services for Cell Number of RABs Normally Released for PS Streaming Services for Cell Number of RABs Normally Released for PS BE Services for Cell
67192602
VS.RAB.NormRel.PS.Str
73393845
VS.RAB.NormRel.PS.BE
Description
The measurement items provide the number of PS RABs normally released in the best cell according to different PS service type.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the items in the best cell which the UE camps on according to diferent PS service type if the released RAB belongs to PS domain. Figure 1-888 Iu connection release procedure
Issue 01 (2013-05-04)
1935
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the items in the best cell which the UE camps on according to diferent PS service type if the released RAB belongs to PS domain. Figure 1-889 RAB release procedure (successful operation)
Formula
None
Unit
None
Issue 01 (2013-05-04)
1936
Related Features
Counter Name VS.RAB.NormRel.PS.Conv Feature ID WRFD-010501 WRFD-010510 Feature Name Conversational QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Streaming QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Background QoS Class Interactive QoS Class
VS.RAB.NormRel.PS.Str
WRFD-010502 WRFD-010510
VS.RAB.NormRel.PS.BE
WRFD-010510 WRFD-010504 WRFD-010503
1.12.31.6 Number of CS RABs Abnormally Released for Cell Counters

Counter ID 67179778 Counter Name VS.RAB.AbnormRel.CS Counter Description Number of CS RABs Abnormally Released for Cell
Description
This item provides of the number of CS RABs abnormally released in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release" (reference to 3GPP TS 25.413), the RNC measures the item in the best cell that the UE camps on if the released RABs belong to CS domain.
Issue 01 (2013-05-04)
1937
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release"(reference to 3GPP TS 25.413),the RNC measures the item in the best cell that the UE camps on if the released RABs belong to CS domain.
Issue 01 (2013-05-04)
1938
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release"(reference to 3GPP TS 25.413),the RNC measures the item in the best cell that the UE camps on if the released RABs belong to CS domain.
Issue 01 (2013-05-04)
1939
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.CS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.7 Number of CS RABs Normally Released for Cell Counters

Counter ID 67179779 Counter Name VS.RAB.NormRel.CS Counter Description Number of CS RABs Normally Released for Cell
1940
Issue 01 (2013-05-04)
Description
The measurement items provide the number of CS RABs normally released in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the item in the best cell which the UE camps on if the released RAB belongs to CS domain. Figure 1-893 Iu connection release procedure
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the item in the best cell which the UE camps on if the released RAB belongs to CS domain.
Issue 01 (2013-05-04)
1941
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.CS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.8 Number of PS RABs Abnormally Released for Cell
Issue 01 (2013-05-04)
1942
Counters
Counter ID 67179781 Counter Name VS.RAB.AbnormRel.PS Counter Description Number of PS RABs Abnormally Released for Cell
Description
This item provides of the number of PS RABs abnormally released in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release"(reference to 3GPP TS 25.413), the RNC measures the item in the best cell that the UE camps on if the released RABs belong to PS domain. Figure 1-895 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release"(reference to 3GPP TS 25.413),the RNC measures the item in the best cell that the UE camps on if the released RABs belong to PS domain.
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release"(reference to 3GPP TS 25.413),the RNC measures the item in the best cell that the UE camps on if the released RABs belong to PS domain.
Issue 01 (2013-05-04)
1944
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.9 Number of PS RABs Normally Released for Cell Counters

Counter ID 67179782 Counter Name VS.RAB.NormRel.PS Counter Description Number of PS RABs Normally Released for Cell
1945
Issue 01 (2013-05-04)
Description
The measurement items provide the number of PS RABs normally released in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the item in the best cell which the UE camps on if the released RAB belongs to PS domain. Figure 1-898 Iu connection release procedure
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the item in the best cell which the UE camps on if the released RAB belongs to PS domain.
Issue 01 (2013-05-04)
1946
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.10 Number of CS AMRWB RABs Abnormally Released
Issue 01 (2013-05-04)
1947
Counters
Counter ID 67192201 Counter Name VS.RAB.AbnormRel.AMR WB.23.85 Counter Description Number of CS 23.85kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 23.05kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 19.85kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 18.25kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 15.85kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 14.25kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 12.65kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 8.85kbit/s WB AMR RABs Abnormally Released for Cell Number of CS 6.6kbit/s WB AMR RABs Abnormally Released for Cell Number of CS AMRWB RABs Abnormally Released for cell
67192202
VS.RAB.AbnormRel.AMR WB.23.05
67192203
67192204
67192205
67192206
67192207
67192208
VS.RAB.AbnormRel.AMR WB.8.85 VS.RAB.AbnormRel.AMR WB.6.6 VS.RAB.AbnormRel.AMR WB
67192209
73403842
Description
The measurement items provide the number of RABs abnormally released triggered by the RNC according to different domains in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures measures the items in the best cell that the UE camps on. Figure 1-900 Iu connection release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items in the best cells that the UE camps on.
Issue 01 (2013-05-04)
1949
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1950
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.AMR WB.23.85 Feature ID WRFD-010613 WRFD-010510 Feature Name AMR-WB (Adaptive Multi Rate Wide Band) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release VS.RAB.AbnormRel.AMR WB.23.05 WRFD-010613 WRFD-010510 AMR-WB (Adaptive Multi Rate Wide Band) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
1951
Counter Name VS.RAB.AbnormRel.AMR WB.19.85
Feature Name AMR-WB (Adaptive Multi Rate Wide Band) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
WRFD-010613 WRFD-010510
AMR-WB (Adaptive Multi Rate Wide Band) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
Issue 01 (2013-05-04)
1952
Counter Name VS.RAB.AbnormRel.AMR WB
1.12.31.11 Number of CS RABs Abnormally Released Triggered by Different Causes Counters

Counter ID 67180080 Counter Name VS.RAB.AbnormRel.CS.Iu AAL2 Counter Description Number of CS RABs Abnormally Released for Cell (Iu Interface AAL2 Link Failure) Number of CS RABs Abnormally Released Due to RF for Cell Number of CS RAB Release Requests for Cell (O&M Intervention) Number of CS RAB Release Attempts for Cell (RAB Preemption) Number of CS RAB Abnormal Releases Triggered by RNC for Cell (UTRAN Cause) Number of CS Domain RABs Released Due to Congestion for Cell
67179777
VS.RAB.AbnormRel.CS.RF
67180067
VS.RAB.AbnormRel.CS.O M VS.RAB.AbnormRel.CS.Pr eempt VS.RAB.AbnormRel.CS.U TRANgen
67180069
67180068
67190841
VS.RAB.AbnormRel.CS.O LC
Description
This measurement item provides the number of CS RABs abnormally released triggered by different causes in the best cell. The following table describes the meaning of each counter.
Issue 01 (2013-05-04)
1953
Counter Name VS.RAB.AbnormRel.CS.IuAAL2
Description Number of CS RABs Abnormally Released Due to Iu Interface AAL2 Link Failure for Cell Number of CS RABs Abnormally Released Due to RF for Cell(The RF failure includes Radio Connection With UE Lost and Failure in the Radio Interface Procedure) Number of CS RAB Release Requests Due to OM Intervention for Cell Number of CS RAB Release Attempts Due to RAB Preemption for Cell Number of CS RAB Abnormal Releases Triggered by RNC Due to UTRAN Cause for Cell Number of CS RAB Release Attempts Due to Congestion for Cell
VS.RAB.AbnormRel.CS.OM VS.RAB.AbnormRel.CS.Preempt VS.RAB.AbnormRel.CS.UTRANgen
VS.RAB.AbnormRel.CS.OLC
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception after the CS RABs have been set up. If the RNC receives a RAB ASSIGNMENT REQUEST message which indicates releasing a RAB with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release"(reference to 3GPP TS 25.413),the RNC measures these items in the best cell that the UE camps on according to different causes.
Issue 01 (2013-05-04)
1954
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release"(reference to 3GPP TS 25.413),the RNC measures these items in the best cell that the UE camps on according to different causes.
Issue 01 (2013-05-04)
1955
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release"(reference to 3GPP TS 25.413),the RNC measures these items in the best cell that the UE camps on according to different causes.
Issue 01 (2013-05-04)
1956
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.CS.Iu AAL2 Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
WRFD-010510
VS.RAB.AbnormRel.CS.O M
WRFD-010510
Issue 01 (2013-05-04)
1957
Counter Name VS.RAB.AbnormRel.CS.Pr eempt
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Queuing and Pre-Emption
VS.RAB.AbnormRel.CS.U TRANgen
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Overload Control
VS.RAB.AbnormRel.CS.O LC
WRFD-010510 WRFD-020107
1.12.31.12 Number of CS AMR RABs Abnormally Released Counters

Counter ID 67180082 Counter Name VS.RAB.AbnormRel.AMR Counter Description Number of CS AMR RABs Abnormally Released for Cell Number of CS 12.2kbit/s AMR RABs Abnormally Released for Cell Number of CS 7.95kbit/s AMR RABs Abnormally Released for Cell Number of CS 5.9kbit/s AMR RABs Abnormally Released for Cell Number of CS 4.75kbit/s AMR RABs Abnormally Released for Cell
67190467
VS.RAB.AbnormRel.AMR. 12.2 VS.RAB.AbnormRel.AMR. 7.95 VS.RAB.AbnormRel.AMR. 5.9 VS.RAB.AbnormRel.AMR. 4.75
67190468
67190469
67190470
Description
The measurement items provide the number of CS AMR RABs abnormally released in the best cell.The counter VS.RAB.AbnormRel.AMR includes only narrowband AMR services.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items in the best cells that the UE camps on. Figure 1-906 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1959
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures measures the items in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1960
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.AMR VS.RAB.AbnormRel.AMR. 12.2 Feature ID WRFD-010501 WRFD-010501 WRFD-010510 Feature Name Conversational QoS Class Conversational QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Conversational QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AbnormRel.AMR. 7.95
WRFD-010501 WRFD-010510
Issue 01 (2013-05-04)
1961
Counter Name VS.RAB.AbnormRel.AMR. 5.9
Feature Name Conversational QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Conversational QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AbnormRel.AMR. 4.75
WRFD-010501 WRFD-010510
1.12.31.13 Number of PS RABs Abnormally Released Due to Different RF Causes for Cell Counters
Counter ID 67180078 Counter Name VS.RAB.AbnormRel.PS.RF .SRBReset VS.RAB.AbnormRel.PS.RF .ULSync Counter Description Number of PS RABs Abnormally Released Due to Signaling RLC Reset for Cell Number of PS RABs Abnormally Released for Cell (Uplink Synchronization Failure) Number of PS RABs Abnormally Released Due to RF for Cell (Failure in the Radio Interface Procedure) Number of PS RABs Abnormally Released for Cell (Traffic RLC Reset)
67189572
67190506
VS.RAB.AbnormRel.PS.RF .UuNoReply
67180079
VS.RAB.AbnormRel.PS.RF .TRBReset
Description
The measurement items provide the number of PS RABs abnormally released due to different RF failure.The RF failure includes "Radio Connection With UE Lost" and "Failure in the Radio Interface Procedure".
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to RF failure (for example:SRB reset, TRB reset radio
link synchronous failure or UU interface no reply,etc.). If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items in the best cell that the UE camps on according to different RF failures if the released RABs belong to PS domain. Figure 1-909 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to RF failure (for example:SRB reset, TRB reset radio link synchronous failure or UU interface no reply,etc.). If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items in the best cell that the UE camps on according to different RF failures if the released RABs belong to PS domain.
Issue 01 (2013-05-04)
1963
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to RF failure (for example:SRB reset, TRB reset radio link synchronous failure or UU interface no reply,etc.). If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items in the best cell that the UE camps on according to different RF failures if the released RABs belong to PS domain.
Issue 01 (2013-05-04)
1964
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.RF .SRBReset Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AbnormRel.PS.RF .ULSync
WRFD-010510
VS.RAB.AbnormRel.PS.RF .UuNoReply
WRFD-010510
Issue 01 (2013-05-04)
1965
Counter Name VS.RAB.AbnormRel.PS.RF .TRBReset
1.12.31.14 Number of PS RABs Abnormally Released Due to Different Causes Counters

Counter ID 67180081 Counter Name VS.RAB.AbnormRel.PS.GT PULoss VS.RAB.AbnormRel.PS.RF Counter Description Number of PS RABs Abnormally Released Due to GTPU Failure for Cell Number of PS RABs Abnormally Released Due to RF for Cell Number of PS RAB Abnormal Released Due to O&M Intervention for Cell Number of PS RAB Abnormal Released Due to RAB Preemption for Cell Number of PS Domain RABs Released Due to Congestion for Cell
67179780
67180074
VS.RAB.AbnormRel.PS.O M VS.RAB.AbnormRel.PS.Pre empt VS.RAB.AbnormRel.PS.OL C
67180076
67190840
Description
This measurement item provides the number of PS RABs abnormally released due to different causes in the best cell. The following table describes the meaning of each counter. Counter Name VS.RAB.AbnormRel.PS.GTPULoss VS.RAB.AbnormRel.PS.RF Description Number of PS RABs Abnormally Released Due to GTPU Failure for Cell Number of PS RABs Abnormally Released Due to RF for Cell(The RF failure includes Radio Connection With UE Lost and Failure in the Radio Interface Procedure)
Issue 01 (2013-05-04)
1966
Counter Name VS.RAB.AbnormRel.PS.OM VS.RAB.AbnormRel.PS.Preempt VS.RAB.AbnormRel.PS.OLC
Description Number of PS RAB Abnormal Released Due to OM Intervention for Cell Number of PS RAB Abnormal Released Due to RAB Preemption for Cell Number of PS Domain RABs Released Due to Congestion for Cell
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception after the PS RABs have been set up. If the RNC receives a RAB ASSIGNMENT REQUEST message which indicates releasing a RAB with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release"(reference to 3GPP TS 25.413),the RNC measures these items in the best cell that the UE camps on according to different causes. Figure 1-912 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception after the PS RABs have been set up.If the RNC receives an IU RELEASE COMMAND message with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release"(reference to 3GPP TS 25.413),the RNC measures these items in the best cell that the UE camps on according to different causes.
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to exception after the PS RABs have been set up.If the RNC receives an IU RELEASE COMMAND message with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release"(reference to 3GPP TS 25.413),the RNC measures these items in the best cell that the UE camps on according to different causes.
Issue 01 (2013-05-04)
1968
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.GT PULoss Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AbnormRel.PS.RF
WRFD-010510
VS.RAB.AbnormRel.PS.O M
WRFD-010510
Issue 01 (2013-05-04)
1969
Counter Name VS.RAB.AbnormRel.PS.Pre empt
VS.RAB.AbnormRel.PS.OL C
WRFD-020107
Overload Control
1.12.31.15 Number of PS BE RABs Beared on HSPA Released due to Cell Congestion Counters
Counter ID 67192975 Counter Name VS.RAB.RelReqPS.BE.HS DPA.Cong.Golden Counter Description Number of HSDPA RABs Carrying Golden Users BE Traffic Released Due to Congestion for Cell Number of HSDPA RABs Carrying Silver Users BE Traffic Released Due to Congestion for Cell Number of HSDPA RABs Carrying Copper Users BE Traffic Released Due to Congestion for Cell Number of HSUPA RABs Carrying Golden Users BE Traffic Released Due to Congestion for Cell Number of HSUPA RABs Carrying Silver Users BE Traffic Released Due to Congestion for Cell Number of HSUPA RABs Carrying Copper Users BE Traffic Released Due to Congestion for Cell
67192976
VS.RAB.RelReqPS.BE.HS DPA.Cong.Silver
67192977
VS.RAB.RelReqPS.BE.HS DPA.Cong.Copper
67192978
VS.RAB.RelReqPS.BE.HS UPA.Cong.Golden
67192979
VS.RAB.RelReqPS.BE.HS UPA.Cong.Silver
67192980
VS.RAB.RelReqPS.BE.HS UPA.Cong.Copper
Issue 01 (2013-05-04)
1970
Description
The measurement items provide the number of released PS BE RABs beared on HSPA triggered by the RNC in the best cell due to CELL congestion.For DC-HSUPA or DC-HSDPA users, this counter is measured only in the cell with the primary carrier. The following table describes the meaning of each counter. Counter Name VS.RAB.RelReqPS.BE.HSDPA.Cong.Silver VS.RAB.RelReqPS.BE.HSDPA.Cong.Copper VS.RAB.RelReqPS.BE.HSUPA.Cong.Gold en VS.RAB.RelReqPS.BE.HSUPA.Cong.Silver VS.RAB.RelReqPS.BE.HSUPA.Cong.Copper Description Number of released silver PS BE RABs beared on HSDPA triggered by the RNC due to CELL congestion Number of released copper users PS BE RABs beared on HSDPA triggered by the RNC due to CELL congestion Number of released golden users PS BE RABs beared on HSUPA triggered by the RNC due to CELL congestion Number of released silver users PS BE RABs beared on HSUPA triggered by the RNC due to CELL congestion Number of released copper users PS BE RABs beared on HSUPA triggered by the RNC due to CELL congestion
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a RAB RELEASE REQUEST message to the CN due to CELL congestion after the RABs have been set up. In this case, the RNC measures the items in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1971
Figure 1-915 RAB release request procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.RelReqPS.BE.HS DPA.Cong.Golden Feature ID WRFD-010610 WRFD-020107 WRFD-010610 WRFD-020107 WRFD-010610 WRFD-020107 WRFD-010612 WRFD-020107 Feature Name HSDPA Introduction Package Overload Control VS.RAB.RelReqPS.BE.HS DPA.Cong.Silver HSDPA Introduction Package Overload Control VS.RAB.RelReqPS.BE.HS DPA.Cong.Copper HSDPA Introduction Package Overload Control VS.RAB.RelReqPS.BE.HS UPA.Cong.Golden HSUPA Introduction Package Overload Control
Counter Name VS.RAB.RelReqPS.BE.HS UPA.Cong.Silver
Feature Name HSUPA Introduction Package Overload Control
VS.RAB.RelReqPS.BE.HS UPA.Cong.Copper
HSUPA Introduction Package Overload Control
1.12.31.16 Number of PS RABs Normally Released According to Different Channelbeared Type Counters
Counter ID 67191791 Counter Name VS.RAB.NormRel.PS.CCH Counter Description Number of PS RABs Mapped on CCH Normally Released for Cell Number of PS R99 RAB successfully released for cell
73403807
Description
The measurement items provide the number of RABs normally released according to different channel-beared type in the best cell that the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the items in the best cell which the UE camps on according to the channel-beared type if the released RAB belongs to PS domain.
Issue 01 (2013-05-04)
1973
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the items in the best cell which the UE camps on according to the channel-beared type if the released RAB belongs to PS domain.
Issue 01 (2013-05-04)
1974
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS.CCH Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
WRFD-010510
1.12.31.17 Number of PS RABs Normally Released due to UE Signaling Connection Release

Counters
Counter ID 67191835 Counter Name VS.RAB.NormRel.PS.UEGen Counter Description Number of PS RABs Normally Released for Cell (UE Signaling Connection Release)
Description
This measurement item provides the number of PS RABs normally released due to UE signaling connection release in the best cell that the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a SIGNALING CONNECTION RELEASE INDICATION message from the UE. the RNC sends an IU RELEASE REQUEST message to the CN. After receiving this message, the CN sends IU RELEASE COMMAND to the RNC. After receiving this command, the RNC releases the corresponding RAB and sends an IU RELEASE COMPLETE message to the CN. At this time, the RNC measures this item in the best cell that the UE camps on. Figure 1-918 UL signalling connection release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS.UEGen Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.18 Number of CS over HSPA RABs Normal Released for Cell Counters
Counter ID 67196205 Counter Name VS.RAB.NormRel.CS.HSP A.Conv Counter Description Number of CS over HSPA RABs Normal Released for Cell
Description
The measurement items provide the number of CS OVER HSPA RABs normal released in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the items by the service type in the best cell which the UE camps on if the released RAB is CS OVER HSPA.
Issue 01 (2013-05-04)
1977
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the item in the best cell which the UE camps on if the released RAB is CS OVER HSPA.
Issue 01 (2013-05-04)
1978
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.CS.HSP A.Conv Feature ID WRFD-010619 Feature Name CS voice over HSPA/HSPA +
1.12.31.19 Number of CS VP RABs Released Due to VP Forbiddance for Cell
Issue 01 (2013-05-04)
1979
Counters
Counter ID 67196233 Counter Name VS.RAB.NormRel.VPLimit Counter Description Number of CS VP RABs Released Due to VP Forbiddance for Cell
Description
The measurement items provide the number of RABs normally released Due to VP Forbiddance in the best cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC initiates an Iu connection release procedure with the cause value of "Network Optimization" and CS VP RABs are released due to VP forbiddance, this counter is measured in the best cell that the UE camps on. Figure 1-921 Iu connection release procedure
The measurement is triggered at point B as shown in the following figure. When the RNC initiates a RAB release procedure with the cause value of "Network Optimization" and CS VP RABs are released due to VP forbiddance, this counter is measured in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1980
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.VPLimit Feature ID WRFD-020130 Feature Name Videophone Service Restriction
1.12.31.20 Times of PS RAB of 0kbit/s released for failed to rate up
Issue 01 (2013-05-04)
1981
Counters
Counter ID 67196302 Counter Name VS.RAB.NormRel.PS. 0kbps.Timeout Counter Description Number of PS RABs at 0 kbit/s Released for Failure to Rate up in the Best Cell
Description
This measurement item provides the times of releasing RAB of 0kbit/s for failing to rate up before timer expiry in the best cell.
Measurement point
The measurement is triggered when a RAB of 0kbit/s released by RNC, due to failure of rating up before the timer of 0kbit/s expires. The measurement is triggered at point A in the figure. When the RNC initiates an Iu connection release procedure with the cause "Network Optimization" and PS services are released due to the failure of 0 kbit/s PS RAB rating up before timer expiry, it measures the number of times of releasing RAB of 0 kbit/s for failing to rate up before timer expiry in the best cell. Figure 1-923 Iu release procedure
The measurement is triggered at point B in the figure. When the RNC initiates a RAB assignment release procedure with the cause "Network Optimization" and PS services are released due to the failure of 0 kbit/s PS RAB rating up before timer expiry, it measures the number of times of releasing RAB of 0 kbit/s for failing to rate up before timer expiry in the best cell.
Issue 01 (2013-05-04)
1982
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS. 0kbps.Timeout Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.31.21 Number of AMRWB RABs Normally Released for Cell
Issue 01 (2013-05-04)
1983
Counters
Counter ID 73403833 Counter Name VS.RAB.NormRel.AMRW B.23.85 VS.RAB.NormRel.AMRW B.23.05 VS.RAB.NormRel.AMRW B.19.85 VS.RAB.NormRel.AMRW B.18.25 VS.RAB.NormRel.AMRW B.15.85 VS.RAB.NormRel.AMRW B.14.25 VS.RAB.NormRel.AMRW B.12.65 VS.RAB.NormRel.AMRW B.8.85 VS.RAB.NormRel.AMRW B.6.60 VS.RAB.NormRel.AMRW B Counter Description Number of CS 23.85kbps AMRWB RABs Normally Released for cell Number of CS 23.05kbps AMRWB RABs Normally Released for cell Number of CS 19.85kbps AMRWB RABs Normally Released for cell Number of CS 18.25kbps AMRWB RABs Normally Released for cell Number of CS 15.85kbps AMRWB RABs Normally Released for cell Number of CS 14.25kbps AMRWB RABs Normally Released for cell Number of CS 12.65kbps AMRWB RABs Normally Released for cell Number of CS 8.85kbps AMRWB RABs Normally Released for cell Number of CS 6.60kbps AMRWB RABs Normally Released for cell Number of CS AMRWB RABs Normally Released for cell
73403834
73403835
73403836
73403837
73403838
73403839
73403840
73403841
73403843
Description
The measurement item provides the number of CS AMRWB RABs of different rates normally released in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message, it releases the related RABs and sends an IU RELEASE COMPLETE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or
the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the items by the service type in the best cell which the UE camps on. Figure 1-925 Iu connection release procedure
The measurement is triggered at point B as shown in the figure.When the RNC receives a RAB ASSIGNMENT REQUEST message indicating that some RABs need to be released, the RNC releases the related RABs and sends a RAB ASSIGNMENT RESPONSE message to the CN. If the IU RELEASE COMMAND message indicate the reason is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or the RNC initiates the release procedure by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message with the causes of "User Inactivity","Network Optimization" or "UE Generated Signalling Connection Release",the RNC measures the items by the service type in the best cell which the UE camps on.
Issue 01 (2013-05-04)
1985
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.AMRW B.23.85 Feature ID WRFD-010613 WRFD-010510 Feature Name AMR-WB (Adaptive Multi Rate Wide Band) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release VS.RAB.NormRel.AMRW B.23.05 WRFD-010613 WRFD-010510 AMR-WB (Adaptive Multi Rate Wide Band) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Counter Name VS.RAB.NormRel.AMRW B.19.85
VS.RAB.NormRel.AMRW B.18.25
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
Issue 01 (2013-05-04)
1987
Counter Name VS.RAB.NormRel.AMRW B
1.12.31.22 Number of CS RABs Normally Released Due to Uplink Signaling Connection Release Counters
Counter ID 73393843 Counter Name VS.RAB.NormRel.CS.UEGen Counter Description Number of CS RABs Normally Released for Cell (UE Generated Signaling Connection Release)
Description
The measurement items provide the number of CS RABs normally released for uplink signaling connection release in the best cell which the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a SIGNALING CONNECTION RELEASE INDICATION message from the UE. the RNC sends an IU RELEASE REQUEST message to the CN. After receiving this message, the CN sends IU RELEASE COMMAND to the RNC. After receiving this command, the RNC releases the corresponding RAB and sends an IU RELEASE COMPLETE message to the CN. At this time, the RNC measures this item in the best cell that the UE camps on.
Issue 01 (2013-05-04)
1988
Figure 1-927 UL signalling connection release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.CS.UEGen Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.23 Number of CS RABs Abnormally Released due to RF Failure for Different Service
Issue 01 (2013-05-04)
1989
Counters
Counter ID 73394051 Counter Name VS.RAB.AbnormRel.AMR. RF VS.RAB.AbnormRel.CS64. RF Counter Description Number of CS AMR RABs abnormal release Due to RF Failure for cell Number of CS Conversational 64kbit/s RABs abnormal released due to RF failure for cell
73394052
Description
The measurement items provide Number of CS RABs abnormal released due to RF Failure in the best cell according to different service types.The counter VS.RAB.AbnormRel.AMR.RF includes narrowband and wideband AMR services.
Measurement point
The measurement is triggered at point A as shown in the figure. In the case of RF failure, the RNC sends to the CN an IU RELEASE REQUEST message (with release cause of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure", reference to 3GPP TS 25.413).If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items in the best cell that the UE camps on according to different service types if the released RABs belong to CS domain. Figure 1-928 Iu connection release procedure
Issue 01 (2013-05-04)
1990
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to RF failure (with release cause of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure", reference to 3GPP TS 25.413). If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items in the best cell that the UE camps on according to different service types if the released RABs belong to CS domain. Figure 1-929 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an IU RELEASE REQUEST message due to RF failure (with release cause of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure", reference to 3GPP TS 25.413).If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items in the best cell that the UE camps on according to different service types if the released RABs belong to CS domain.
Issue 01 (2013-05-04)
1991
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.AMR. RF Feature ID WRFD-010501 WRFD-010510 Feature Name Conversational QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Conversational QoS Class 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AbnormRel.CS64. RF
WRFD-010501 WRFD-010510
1.12.31.24 Number of RABs Abnormally Released for PTT Services

Counters
Counter ID 73394073 Counter Name VS.RAB.AbnormRelPS.PT T Counter Description Number of RABs Abnormally Released for PTT Services for Cell
Description
This counter provides the number of times that a RAB for PTT services is released abnormally in the best cell.
Measurement point
As shown in point A of the figure, when a failure occurs, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then this counter is measured in the best cell that the UE camps on if the RAB is for a PTT service. Figure 1-931 RAB release procedure
As shown in point A of the figure, when a failure occurs, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE
Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then this counter is measured in the best cell that the UE camps on if the RAB is for a PTT service. Figure 1-932 RAB release IU REL procedure
As shown in point A of the figure, when a failure occurs, the RNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then this counter is measured in the best cell that the UE camps on if the RAB is for a PTT service.
Issue 01 (2013-05-04)
1994
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRelPS.PT T Feature ID WRFD-020134 Feature Name Push to Talk
1.12.31.25 Number of RABs Normally Released for PTT Services Counters

Counter ID 73394074 Counter Name VS.RAB.NormRelPS.PTT Counter Description Number of RABs Normally Released for PTT Services for Cell
Issue 01 (2013-05-04)
1995
Description
This counter provides the number of times that a RAB for PTT services is released normally in the best cell.
Measurement point
The measurement can be triggered at point A as shown in the figure. When the RNC receives from the CN an IU RELEASE COMMAND message, it releases the corresponding RAB, and then sends to the CN an IU RELEASE COMPLETE message. If the release cause contained in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful Relocation" or "Network Optimization", or if the RNC initiates a release request with the cause value of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before receiving the IU RELEASE COMMAND message from the CN, then this counter is measured in the best cell that the UE camps on if the service is a PTT service. Figure 1-934 Iu release procedure
The measurement can also be triggered at point B as shown in the figure. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message indicating that a RAB needs to be released, it releases the corresponding RAB, and then sends to the CN a RAB ASSIGNMENT RESPONSE message. If the release cause contained in the RAB ASSIGNMENT REQUEST message is "User Inactivity", "Normal Release", "Successful Relocation" or "Network Optimization", or if the RNC initiates a release request with the cause value of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before receiving the IU RELEASE COMMAND message from the CN, then this counter is measured in the best cell that the UE camps on if the service is a PTT service.
Issue 01 (2013-05-04)
1996
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRelPS.PTT Feature ID WRFD-020134 Feature Name Push to Talk
1.12.31.26 Number of PS R99 RABs Abnormally Released Due to RF Failure Counters

Counter ID 73403805 Counter Name VS.RAB.AbnormRel.PSR9 9.RF Counter Description Number of PS R99 RABs abnormally released Due to RF Failure for cell
Issue 01 (2013-05-04)
1997
Description
This counter provides the number of PS R99 RABs abnormally released due to RF failure.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message with the cause value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure" (see 3GPP TS 25.413 for details) due to RF failure. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413), the RNC measures the items in the best cell that the UE camps on if the released RAB is for PS R99 service. Figure 1-936 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message with the cause value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure" (see 3GPP TS 25.413 for details) due to RF failure.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items in the best cell that the UE camps on if the released RAB is for PS R99 service.
Issue 01 (2013-05-04)
1998
The measurement is triggered at point A as shown in the figure. After receiving an IU RELEASE REQUEST message with the cause value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure" (see 3GPP TS 25.413 for details) sent by the RNC due to RFrelated reasons, the CN sends to the RNC an IU RELEASE COMMAND message. In this case, this counters is measured in the best cell that the UE camps on if the RAB is for PS R99 services and the release reason in the IU RELEASE COMMAND message is not an normal reason, that is, a reason except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release" (see 3GPP TS 25.413 for details).
Issue 01 (2013-05-04)
1999
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PSR9 9.RF Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.27 Number of PS RABs Abnormally Released According to Different Channel-beared Type
Issue 01 (2013-05-04)
2000
Counters
Counter ID 73403806 Counter Name VS.RAB.AbnormRel.PSR9 9 VS.RAB.AbnormRel.PS.CC H Counter Description Number of PS R99 RABs abnormally released for cell (Including RF Failure) Number of PS RABs Mapped on CCH Abnormally Released for Cell
67191818
Description
This counter provides the number of PS RABs abnormally released due to different causes according to different channel-beared type.
Measurement point
The measurement is triggered at point A as shown in the figure. After receiving an IU RELEASE REQUEST message from the RNC, the CN sends to the RNC an IU RELEASE COMMAND message. In this case, this counters is measured in the best cell that the UE camps on according to different channel-beared type if the release reason in the IU RELEASE COMMAND message is not an normal reason, that is, a reason except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release" (see 3GPP TS 25.413 for details). Figure 1-939 Iu connection release procedure
Issue 01 (2013-05-04)
2001
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception. If the RNC receives a RAB ASSIGNMENT REQUEST message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items in the best cell according to different channel-beared type. Figure 1-940 RAB release procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE COMMAND message(with the cause other than "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE Generated Signalling Connection Release", reference to 3GPP TS 25.413),the RNC measures the items in the best cell according to different channel-beared type.
Issue 01 (2013-05-04)
2002
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PSR9 9 Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AbnormRel.PS.CC H
WRFD-010510
1.12.31.28 Number of Normally Released PS RABs that Are in CELL_PCH or URA_PCH State for Cell
Counters
Counter ID 73421882 Counter Name VS.RAB.NormRel.PS.PCH Counter Description Number of Normally Released PS RABs that Are in CELL_PCH or URA_PCH State for Cell
Description
This counter provides the number of normally released PS RABs that are in CELL_PCH or URA_PCH state. The release of RABs in URA_PCH state is measured in the last cell that the UE camps on before entering the URA_PCH state.
Measurement point
The measurement is triggered at point A as shown in the following figure. After receiving an IU RELEASE COMMAND message from the CN, the RNC releases the corresponding RAB and then sends an IU RELEASE COMPLETE message to the CN. If the release cause in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", or if the RNC has sent a release request with the cause of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before the RNC receives the IU RELEASE COMMAND message, then a counter is measured in the cell that the UE camps on according to the channel type if the RAB is intended for PS services. Figure 1-942 Iu connection release procedure
Issue 01 (2013-05-04)
2004
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS.PCH Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.29 Number of call drops During the F2P State Transition for Cell Counters
Counter ID 73421886 Counter Name VS.RAB.AbnormRel.PS.F2 P Counter Description Number of call drops During the F2P State Transition for Cell
Description
This counter provides the number of call drops during CELL_FACH to CELL_PCH or to URA_PCH state transition.
Measurement point
If the RNC does not receive a RADIO BEARER RECONFIGURATION COMPLETE or PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from a UE after sending a RADIO BEARER RECONFIGURATION or PHYSICAL CHANNEL RECONFIGURATION message to the UE, this counter is incremented by one in the cell where the UE is camping. The measurement is triggered at point A as shown in the following figure. When an exception occurs, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN a RAB ASSIGNMENT REQUEST message with a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", this counter is measured in the best cell that the UE camps on if PS RABs are released. For details about cause values for a normal release, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
2005
The measurement is triggered at point A as shown in the following figure. When an exception occurs, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN a IU RELEASE COMMAND message with a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", this counter is measured in the best cell that the UE camps on if PS RABs are released. For details about cause values for a normal release, see 3GPP TS 25.413. Figure 1-944 RAB release IU REL procedure
The measurement is triggered at point A as shown in the following figure. When an exception occurs, the RNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from
the CN an IU RELEASE COMMAND message with a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", this counter is measured in the best cell that the UE camps on if PS RABs are released. For details about cause values for a normal release, see 3GPP TS 25.413. Figure 1-945 Iu connection release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.F2 P Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.30 Number of Abnormally Released PS RABs that Are in CELL_PCH or URA_PCH State for Cell
Issue 01 (2013-05-04)
2007
Counters
Counter ID 73421883 Counter Name VS.RAB.AbnormRel.PS.PC H Counter Description Number of Abnormally Released PS RABs that Are in CELL_PCH or URA_PCH State for Cell
Description
This counter provides the number of abnormally released PS RABs that are in CELL_PCH or URA_PCH state. The release of RABs in URA_PCH state is measured in the last cell that the UE camps on before entering the URA_PCH state.
Measurement point
The measurement is triggered at point A as shown in the following figure. When a failure occurs, the RNC sends the CN an IU RELEASE REQUEST message. After receiving the message, the CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE COMMAND message contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then a counter is measured in the best cell that the UE camps on according to the channel type if the RAB carries PS services. Figure 1-946 Iu connection release procedure
The measurement is triggered at point A as shown in the following figure. When a failure occurs, the RNC sends the CN an RAB RELEASE REQUEST message. After receiving the message,
the CN sends an RAB ASSIGNMENT REQUEST message to the RNC. If the RAB ASSIGNMENT REQUEST message contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then a counter is measured in the best cell that the UE camps on according to the channel type if the RAB carries PS services. Figure 1-947 RAB release procedure
The measurement is triggered at point A as shown in the following figure. When a failure occurs, the RNC sends the CN an RAB RELEASE REQUEST message. After receiving the message, the CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE COMMAND message contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then a counter is measured in the best cell that the UE camps on according to the channel type if the RAB carries PS services.
Issue 01 (2013-05-04)
2009
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.PC H Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.31 Number of RABs Abnormally Released for PS Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell
Issue 01 (2013-05-04)
2010
Counters
Counter ID 73422166 Counter Name VS.RAB.AbnormRel.PS.D2 P Counter Description Number of RABs Abnormally Released for PS Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell Number of RABs Abnormally Released for PS R99 Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell
73422169
VS.RAB.AbnormRel.PS.R9 9D2P
Description
This counter provides the number of RABs Abnormally Released for PS Services during the State Transition from CELL_DCH to CELL_PCH or URA_PCH in the best cell.
Measurement point
As shown in point A of the figure, when a failure occurs(Ex: SRB reset occurs after sent Radio Bear Reconfiguration Message to UE during the State Transition from CELL_DCH to CELL_PCH or URA_PCH), the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN a RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then this counter is measured in the best cell that the UE camps on if the RAB is for a PS service.
Issue 01 (2013-05-04)
2011
As shown in point A of the figure, when a failure occurs(Ex: SRB reset occurs after sent Radio Bear Reconfiguration Message to UE during the State Transition from CELL_DCH to CELL_PCH or URA_PCH), the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then this counter is measured in the best cell that the UE camps on if the RAB is for a PS service.
Issue 01 (2013-05-04)
2012
As shown in point A of the figure, when a failure occurs(Ex: SRB reset occurs after sent Radio Bear Reconfiguration Message to UE during the State Transition from CELL_DCH to CELL_PCH or URA_PCH), the RNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal release (a cause value except "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then this counter is measured in the best cell that the UE camps on if the RAB is for a PS service.
Issue 01 (2013-05-04)
2013
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.D2 P VS.RAB.AbnormRel.PS.R9 9D2P Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
WRFD-010202
1.12.31.32 Number of RABs Abnormally Released Due to Security Mode Procedure Failure
Issue 01 (2013-05-04)
2014
Counters
Counter ID 73423939 Counter Name VS.RAB.AbnormRel.CS.Se curity Counter Description Number of CS RABs Abnormally Released Due to Security Mode Procedure Failure for Cell Number of PS RABs Abnormally Released Due to Security Mode Procedure Failure for Cell
73423940
VS.RAB.AbnormRel.PS.Security
Description
This counter measures the number of RABs abnormally released due to a security mode procedure failure in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure, after a RAB is successfully set up, the RNC sends the CN an IU RELEASE REQUEST message due to a Security Mode procedure failure. The CN responds with an IU RELEASE COMMAND message. If the cause value carried in the IU RELEASE COMMAND message is a value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" and "UE Generated Signalling Connection Release" (for details about the cause values of the IU RELEASE COMMAND message, see 3GPP TS 25.413), then the counter is increased by one in the best cell where the UE camps according to different service type.
Issue 01 (2013-05-04)
2015
Figure 1-952 Release procedure due to security mode failure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.CS.Se curity Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AbnormRel.PS.Security
WRFD-010510
Issue 01 (2013-05-04)
2016
1.12.31.33 Number of Released RABs Triggered by the Second RRC CONNECTION REQUEST Message from the Same UE in the CS Domain Counters
Counter ID 73425979 Counter Name VS.RAB.NormRel.CS.UER eEst Counter Description Number of Released RABs Triggered by the Second RRC CONNECTION REQUEST Message from the Same UE in the CS Domain for Cell
Description
This counter provides the number of times that RABs are released because a UE initiates a second RRC CONNECTION REQUEST message in the CS domain in a cell when one RRC connection is still in progress. RAB is short for radio access bearer and RRC is short for radio resource control.
Measurement point
The measurement is triggered at point A shown in the following figure. After receiving the second RRC CONNECTION REQUEST message, the RNC determines based on the RANAP_COMMON_ID message that this RRC CONNECTION REQUEST message is sent by the same UE. Although the RABs requested by the first RRC CONNECTION REQUEST message are not released yet, the RNC still sends an IU RELEASE REQUEST message with a cause value of UE Generated Signaling Connection Release to the CS domain. Upon receiving this message, the CN responds with an IU RELEASE COMMAND message to instruct the RNC to release the corresponding RABs. After releasing the corresponding RABs, the RNC returns an IU RELEASE COMPLETE message to the CN. This counter is measured in the best cell where the UE camps. Figure 1-953
Issue 01 (2013-05-04)
2017
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.CS.UER eEst Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.34 Number of RAB Releases Triggered by the Second RRC CONNECTION REQUEST Message from the Same UE in the PS Domain Counters
Counter ID 73425980 Counter Name VS.RAB.NormRel.PS.UER eEst Counter Description Number of RAB Releases Triggered by the Second RRC CONNECTION REQUEST Message from the Same UE in the PS Domain for Cell
Description
This counter provides the number of times that RABs are released because a UE initiates a second RRC CONNECTION REQUEST message in the PS domain in a cell when one RRC connection is still in progress. RAB is short for radio access bearer and RRC is short for radio resource control.
Measurement point
The measurement is triggered at point A shown in the following figure. After receiving the second RRC CONNECTION REQUEST message, the RNC determines based on the RANAP_COMMON_ID message that this RRC CONNECTION REQUEST message is sent by the same UE. Although the RABs requested by the first RRC CONNECTION REQUEST message are not released yet, the RNC still sends an IU RELEASE REQUEST message with a cause value of UE Generated Signaling Connection Release to the PS domain. Upon receiving this message, the CN responds with an IU RELEASE COMMAND message to instruct the RNC
to release the corresponding RABs. After releasing the corresponding RABs, the RNC returns an IU RELEASE COMPLETE message to the CN. This counter is measured in the best cell where the UE camps. Figure 1-954
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS.UER eEst Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.35 Number of RAB Releases Triggered by the Second RRC CONNECTION REQUEST Message from the Same UE in the PS Domain in Common Channelrelated Scenarios for Cell
Issue 01 (2013-05-04)
2019
Counters
Counter ID 73425981 Counter Name VS.RAB.NormRel.PS.UER eEst.CCHRelated Counter Description Number of RAB Releases Triggered by the Second RRC CONNECTION REQUEST Message from the Same UE in the PS Domain in Common Channel-related Scenarios for Cell
Description
This counter provides the number of times that RABs are released because a UE initiates a second RRC CONNECTION REQUEST message in the PS Domain in Common Channel-related scenarios when one RRC connection is still in progress.
Measurement point
The measurement is triggered at point A shown in the following figure. After receiving the second RRC CONNECTION REQUEST message, the RNC determines based on the RANAP_COMMON_ID message that this RRC CONNECTION REQUEST message is sent by the same UE. Although the RABs requested by the first RRC CONNECTION REQUEST message are not released yet, the RNC still sends an IU RELEASE REQUEST message with a cause value of UE Generated Signaling Connection Release to the PS domain. Upon receiving this message, the CN responds with an IU RELEASE COMMAND message to instruct the RNC to release the corresponding RABs. After releasing the corresponding RABs, the RNC returns an IU RELEASE COMPLETE message to the CN. If the UE is experiencing a D2F or D2P transition, or if the UE is in CELL_FACH or CELL_PCH state (including CELL_PCH and URA_PCH), this counter is measured in the best cell where the UE camps. D2F refers to the process when a UE moves from the CELL_DCH state to the CELL_FACH state. D2P refers to the process when a UE moves from the CELL_DCH state to the CELL_PCH state. Figure 1-955
Issue 01 (2013-05-04)
2020
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS.UER eEst.CCHRelated Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.36 Number of Released PS RABs due to Network Optimization for Cell Counters
Counter ID 73426205 Counter Name VS.RAB.NormRel.PS.NetOpt Counter Description Number of Released PS RABs due to Network Optimization for Cell
Description
This counter measures the number of released PS radio access bearers (RABs) due to network optimization.
Measurement point
The measurement is triggered at point A shown in figure 1 when the RNC sends a RAB RELEASE REQUEST message to the CN and receives from the CN a RAB ASSIGNMENT REQUEST message containing the cause value Network Optimization. If the RAB to be released is for PS services, this counter is measured in the best cell that the UE camps on.
Issue 01 (2013-05-04)
2021
The measurement is triggered at point A shown in figure 2 when the RNC sends a RAB RELEASE REQUEST message to the CN and receives from the CN an IU RELEASE COMMAND message containing the cause value Network Optimization. If the RAB to be released is for PS services, this counter is measured in the best cell that the UE camps on. Figure 1-957 RAB release IU REL procedure
Issue 01 (2013-05-04)
2022
The measurement is triggered at point A shown in figure 3 when the RNC sends an IU RELEASE REQUEST message to the CN and receives from the CN an IU RELEASE COMMAND message containing the cause value Network Optimization. If the RAB to be released is for PS services, this counter is measured in the best cell that the UE camps on. Figure 1-958 Iu connection release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.PS.NetOpt Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.37 Number of Abnormally Released PS RABs Triggered by CN for Cell

Counters
Counter ID 73426206 Counter Name VS.RAB.AbnormRel.PS.CN Counter Description Number of Abnormally Released PS RABs Triggered by CN for Cell
Description
This counter measures the number of abnormally released PS RABs triggered by the CN.
Measurement point
The measurement is triggered at point B shown in figure 1 when both of the following conditions are met: The RNC receives from the PS CN a RAB ASSIGNMENT REQUEST message in which the cause value is not Normal Release, Successful Relocation, User Inactivity, or Network Optimization. The CN does not receive a RAB RELEASE REQUEST message from the RNC. In this case, this counter is incremented by one in the best cell that the UE camps on. Figure 1-959 RAB assignment release procedure
The measurement is triggered at point A shown in figure 2 when both of the following conditions are met: The RNC receives an IU RELEASE COMMAND message from the PS CN, and the cause value in it is not Normal Release, Successful Relocation, User Inactivity, or Network Optimization. The CN does not receive an IU RELEASE REQUEST or RAB RELEASE REQUEST message from the RNC. In this case, this counter is incremented by one in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.CN Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.38 Number of Released CS RABs due to Network Optimization for Cell
Issue 01 (2013-05-04)
2025
Counters
Counter ID 73426207 Counter Name VS.RAB.NormRel.CS.NetOpt Counter Description Number of Released CS RABs due to Network Optimization for Cell
Description
This counter measures the number of released CS RABs due to network optimization.
Measurement point
The measurement is triggered at point A shown in figure 1 when the RNC sends a RAB RELEASE REQUEST message to the CN and receives from the CN a RAB ASSIGNMENT REQUEST message containing the cause value Network Optimization. If the RAB to be released is for CS services, this counter is measured in the best cell that the UE camps on. Figure 1-961 RAB release procedure
The measurement is triggered at point A shown in figure 2 when the RNC sends a RAB RELEASE REQUEST message to the CN and receives from the CN a IU RELEASE COMMAND message containing the cause value Network Optimization. If the RAB to be released is for CS services, this counter is measured in the best cell that the UE camps on.
Issue 01 (2013-05-04)
2026
The measurement is triggered at point A shown in figure 3 when the RNC sends an IU RELEASE REQUEST message to the CN and receives from the CN an IU RELEASE COMMAND message containing the cause value Network Optimization. If the RAB to be released is for CS services, this counter is measured in the best cell that the UE camps on. Figure 1-963 Iu connection release procedure
Issue 01 (2013-05-04)
2027
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.NormRel.CS.NetOpt Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.39 Number of Abnormally Released PS RABs Triggered by RNC for Cell Counters
Counter ID 73426209 Counter Name VS.RAB.AbnormRel.PS.UT RANgen Counter Description Number of Abnormally Released PS RABs Triggered by RNC for Cell
Description
This counter measures the number of abnormally released PS RABs triggered by the RNC due to causes on the UTRAN side.
Measurement point
The measurement is triggered at point A shown in figure 1 when both of the following conditions are met: When an exception occurs after a PS RAB setup, the RNC sends a RAB RELEASE REQUEST message to the CN. The RNC receives a RAB ASSIGNMENT REQUEST message from the CN and the cause value in it is not User Inactivity, Normal Release, Successful Relocation, or Network Optimization. In this case, this counter is measured in the best cell that the UE camps on based on the cause value. For details about the cause values indicating RAB releases, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
2028
The measurement is triggered at point A shown in figure 2 when both of the following conditions are met: When an exception occurs after a PS RAB setup, the RNC sends a RAB RELEASE REQUEST message to the CN. The RNC receives an IU RELEASE COMMAND message from the CN and the cause value in it is not User Inactivity, Normal Release, Successful Relocation, or Network Optimization. In this case, this counter is measured in the best cell that the UE camps on based on the cause value. For details about the cause values indicating RAB releases, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
2029
The measurement is triggered at point A shown in figure 3 when both of the following conditions are met: When an exception occurs after a PS RAB setup, the RNC sends an IU RELEASE REQUEST message to the CN. The RNC receives an IU RELEASE COMMAND message from the CN and the cause value in it is not User Inactivity, Normal Release, Successful Relocation, or Network Optimization. In this case, this counter is measured in the best cell that the UE camps on based on the cause value. For details about the cause values indicating RAB releases, see 3GPP TS 25.413.
Issue 01 (2013-05-04)
2030
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.PS.UT RANgen Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.31.40 Number of Abnormally Released CS RABs Triggered by CN for Cell
Issue 01 (2013-05-04)
2031
Counters
Counter ID 73426208 Counter Name VS.RAB.AbnormRel.CS.C N Counter Description Number of Abnormally Released CS RABs Triggered by CN for Cell
Description
This counter measures the number of abnormally released CS RABs triggered by the CN.
Measurement point
The measurement is triggered at point B shown in figure 1 when both of the following conditions are met: The RNC receives a RAB ASSIGNMENT REQUEST message from the CS CN, and the cause value in it is not Normal Release, Successful Relocation, User Inactivity, or Network Optimization. The CN does not receive a RAB RELEASE REQUEST message from the RNC. In this case, this counter is incremented by one in the best cell that the UE camps on. Figure 1-967 RAB assignment release procedure
The measurement is triggered at point A shown in figure 2 when both of the following conditions are met: The RNC receives an IU RELEASE COMMAND message from the CS CN, and the cause value in it is not Normal Release, Successful Relocation, User Inactivity, or Network Optimization. The CN does not receive an IU RELEASE REQUEST or RAB RELEASE REQUEST message from the RNC. In this case, this counter is incremented by one in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AbnormRel.CS.C N Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.32 Measurement of CS RAB release per cell(RAB.RelCs.Cell)

Overview
This function subset measures the number of released CS RABs. If a CS RAB is not needed or an abnormal release occurs after a successful RAB setup, the CN sends a RAB ASSIGNMENT REQUEST message to the RNC, instructing the RNC to release the RAB. After receiving this message, the RNC releases the corresponding RAB and then sends a RADIO BEARER
RELEASE message to the UE. If the RB release succeeds, the UE sends a RADIO BEARER RELEASE COMPLETE message to the RNC. The RNC sends a RAB ASSIGNMENT RESPONSE message to the CN regardless of whether it receives a RADIO BEARER RELEASE COMPLETE message from the UE. For details, see 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Counter ID 67179850 Counter Name VS.RAB.AttRelCS. NetOpt Counter Description Number of CS RAB Release Requests for Cell (Network Optimization) Number of CS RAB Release Requests for Cell (Normal Release) Number of CS RAB Release Requests for Cell (OM Intervention) Number of CS RAB Release Requests for Cell (RAB Preempted) Number of CS RAB Release Requests for Cell (User Inactivity) Number of CS RAB Release Requests for Cell (Release due to UTRAN Generated Reason) Number of CS RAB Releases Triggered by CN for Cell Number of CS RABs Released in RAB Assignment for Cell Original Release Earlier than V900R011
67179845
VS.RAB.AttRelCS. NormRel
67179849
VS.RAB.AttRelCS. OM
67179848
VS.RAB.AttRelCS. Preempt
67179847
VS.RAB.AttRelCS. UEInact VS.RAB.AttRelCS. UTRANGen
67189500
67190745
VS.CN.RAB.Loss. CS VS.RAB.AttRelCS
73393841
None
1.12.32.1 Number of CS RABs Released Due to Different Causes in RAB Assignment for Cell Counters
Counter ID 67179850 Counter Name VS.RAB.AttRelCS.NetOpt Counter Description Number of CS RAB Release Requests for Cell (Network Optimization) Number of CS RAB Release Requests for Cell (Normal Release) Number of CS RAB Release Requests for Cell (OM Intervention) Number of CS RAB Release Requests for Cell (RAB Preempted) Number of CS RAB Release Requests for Cell (User Inactivity) Number of CS RAB Release Requests for Cell (Release due to UTRAN Generated Reason)
67179845
VS.RAB.AttRelCS.NormRel VS.RAB.AttRelCS.OM
67179849
67179848
VS.RAB.AttRelCS.Preempt
67179847
VS.RAB.AttRelCS.UEInact
67189500
VS.RAB.AttRelCS.UTRAN Gen
Description
These counters provide the number of RAB release requests for CS services in the best cell based on the release cause. Disuse Statement:This counter will be deleted in later versions. In the current version, the value of this counter is properly reported.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN and the RAB is for CS services, the corresponding counter is measured in the best cell that the UE camps on based on the release cause.
Issue 01 (2013-05-04)
2035
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttRelCS.NetOpt Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AttRelCS.NormRel
WRFD-010510
VS.RAB.AttRelCS.OM
WRFD-010510
Issue 01 (2013-05-04)
2036
Counter Name VS.RAB.AttRelCS.Preempt
Feature Name Queuing and Pre-Emption 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AttRelCS.UEInact
WRFD-010510
VS.RAB.AttRelCS.UTRAN Gen
WRFD-010510
1.12.32.2 Number of Abnormally Released CS RABs Triggered by CN Counters

Counter ID 67190745 Counter Name VS.CN.RAB.Loss.CS Counter Description Number of CS RAB Releases Triggered by CN for Cell
Description
This measurement item provides the number of CS RABs for the release triggered by the CN in the best cell only if the release cause is any other Iu interface cause except the following causes: Successful Relocation, User Inactivity, Normal Release. Disuse Statement:Counter VS.CN.RAB.Loss.CS will be replaced by counter VS.RAB.AbnormRel.CS.CN in later versions. In the current version, counters VS.CN.RAB.Loss.CS and VS.RAB.AbnormRel.CS.CN are both valid, and the value of counter VS.CN.RAB.Loss.CS is properly reported. Counter VS.CN.RAB.Loss.CS will be deleted in later versions. Using counter VS.CN.RAB.Loss.CS is not recommended.
Measurement point
The measurement is triggered at point A as shown in Figure 1. When the RNC from the CN receives a RAB ASSIGNMENT REQUEST message about the CS domain, if the RAB release cause value is not "Normal Release," "Successful Relocation," or "User Inactivity," and the RNC had not sent any RAB RELEASE REQUEST message about the CS domain before, the RNC measures this counter according to the number of RABs released.
Issue 01 (2013-05-04)
2037
The measurement is triggered at point A as shown in Figure 2. When the RNC receives from the CN an IU RELEASE COMMAND message about the CS domain, if the RAB release cause value is not "Normal Release", "Successful Relocation", or "User Inactivity", and the RNC had not sent any IU RELEASE REQUEST message about the CS domain before, the RNC measures this counter according to the number of RABs released. Figure 1-971 Iu connection release procedure
Issue 01 (2013-05-04)
2038
Formula
None
Unit
None
Related Features
Counter Name VS.CN.RAB.Loss.CS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.32.3 Number of CS RABs Released in RAB Assignment for Cell Counters

Counter ID 73393841 Counter Name VS.RAB.AttRelCS Counter Description Number of CS RABs Released in RAB Assignment for Cell
Description
This counter provides the number of CS RABs released in RAB assignment in the best cell. Disuse Statement:This counter will be deleted in later versions. In the current version, the value of this counter is properly reported.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the CN a RAB ASSIGNMENT REQUEST message indicating that a CS RAB needs to be released. In this case, this counter is measured in the best cell that the UE camps on.
Issue 01 (2013-05-04)
2039
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttRelCS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.33 Measurement of PS RAB release per cell(RAB.RelPs.Cell)

Overview
If an PS RAB is not needed or an abnormal release occurs after the RAB setup, the CN sends to the RNC a RAB ASSIGNMENT REQUEST message, indicating the RNC to release the RAB. After receiving this message, the RNC release the corresponding RAB and then sends to the CN a RAB ASSIGNMENT RESPONSE message.
For details, see 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Counter ID 67179955 Counter Name VS.RAB.AttRelPS. NetOptm Counter Description Number of PS RAB Release Requests for Cell (Network Optimization) Number of PS RAB Release Requests for Cell (Normal Release) Number of PS RAB Release Requests for Cell (OM Intervention) Number of PS RAB Release Requests for Cell (RAB Preempted) Number of PS RAB Release Requests for Cell (User Inactivity) Number of PS RAB Release Requests for Cell (Unspecified) Number of PS RAB Release Requests for Cell (Release due to UTRAN Generated Reason) Number of PS RAB Releases Triggered by CN for Cell Number of PS RABs Release Attempts for Cell Original Release Earlier than V900R011
67179950
VS.RAB.AttRelPS. NormRel
67179954
VS.RAB.AttRelPS. OM
67179953
VS.RAB.AttRelPS. RABPreempt
67179952
VS.RAB.AttRelPS. UeInact VS.RAB.AttRelPS. Unsp VS.RAB.AttRelPS. UtranGen
67189561
67179951
67190755
VS.CN.RAB.Loss.P S VS.RAB.AttRelPS
73393842
None
Issue 01 (2013-05-04)
2041
1.12.33.1 Number of PS RABs Released by RAB ASSIGNMENT REQUEST for Different Cause Counters
Counter ID 67179955 Counter Name VS.RAB.AttRelPS.NetOptm VS.RAB.AttRelPS.NormRel VS.RAB.AttRelPS.OM Counter Description Number of PS RAB Release Requests for Cell (Network Optimization) Number of PS RAB Release Requests for Cell (Normal Release) Number of PS RAB Release Requests for Cell (OM Intervention) Number of PS RAB Release Requests for Cell (RAB Preempted) Number of PS RAB Release Requests for Cell (User Inactivity) Number of PS RAB Release Requests for Cell (Unspecified) Number of PS RAB Release Requests for Cell (Release due to UTRAN Generated Reason)
67179950
67179954
67179953
VS.RAB.AttRelPS.RABPreempt VS.RAB.AttRelPS.UeInact
67179952
67189561
VS.RAB.AttRelPS.Unsp
67179951
VS.RAB.AttRelPS.UtranGen
Description
These counters provide the number of RAB release requests for PS services in the best cell according to different release causes. Disuse Statement:This counter will be deleted in later versions. In the current version, the value of this counter is properly reported.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message from the CN and the RAB is for PS services, the counters are measured in the best cell that the UE camps on according to different release causes.
Issue 01 (2013-05-04)
2042
Figure 1-973 PS RAB release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttRelPS.NetOptm Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AttRelPS.NormRel
WRFD-010510
VS.RAB.AttRelPS.OM
WRFD-010510
Issue 01 (2013-05-04)
2043
Counter Name VS.RAB.AttRelPS.RABPreempt
VS.RAB.AttRelPS.UeInact
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RAB.AttRelPS.Unsp
WRFD-010510
VS.RAB.AttRelPS.UtranGen
WRFD-010510
1.12.33.2 Number of PS RAB Releases Triggered by CN Counters

Counter ID 67190755 Counter Name VS.CN.RAB.Loss.PS Counter Description Number of PS RAB Releases Triggered by CN for Cell
Description
This measurement item provides the number of PS RAB releases triggered by the CN in the best cell. Disuse Statement:Counter VS.CN.RAB.Loss.PS will be replaced by counter VS.RAB.AbnormRel.PS.CN in later versions. In the current version, counters VS.CN.RAB.Loss.PS and VS.RAB.AbnormRel.PS.CN are both valid, and the value of counter VS.CN.RAB.Loss.PS is properly reported. Counter VS.CN.RAB.Loss.PS will be deleted in later versions. Using counter VS.CN.RAB.Loss.PS is not recommended.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RAB ASSIGNMENT REQUEST message about the PS domain from the CN, if the RAB release cause is not "Normal Release", "Successful Relocation" or "User Inactivity", and the RNC had not send the RAB RELEASE REQUEST message before, the RNC measures this item according to the number of RAB releases.
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU RELEASE COMMAND message about the PS domain from the CN, if the RAB release cause is not "Normal Release", "Successful Relocation" or "User Inactivity", and the RNC had not send the IU RELEASE REQUEST message before, the RNC measures this item according to the number of RAB releases. Figure 1-975 Iu connection release procedure
Issue 01 (2013-05-04)
2045
Formula
None
Unit
None
Related Features
Counter Name VS.CN.RAB.Loss.PS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.33.3 Number of PS RAB Release Attempts by RAB ASSIGNMENT REQUEST Counters

Counter ID 73393842 Counter Name VS.RAB.AttRelPS Counter Description Number of PS RABs Release Attempts for Cell
Description
The measurement item provides the number of PS RAB release attempts by RAB ASSIGNMENT REQUEST message in the best cell. Disuse Statement:This counter will be deleted in later versions. In the current version, the value of this counter is properly reported.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC measures the item after receiving a RAB ASSIGNMENT REQUEST message if there exists PS RABs to be released.
Issue 01 (2013-05-04)
2046
Formula
None
Unit
None
Related Features
Counter Name VS.RAB.AttRelPS Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.34 Measurement of RB Procedure per cell(RB.Cell)

Overview
Radio Bearer (RB) is the service provided by Layer 2 for transfer of user data between UE and UTRAN. The RB procedures include:RB setup procedures, RB reconfiguration procedures, RB release procedures, Transport channel reconfiguration procedures and Physical channel reconfiguration procedure.
Counters
Counter ID 67180113 67180114 Counter Name VS.AttRBSetup VS.SuccRBSetup Counter Description Number of RB Setup Attempts for Cell Number of Successful RB Setups for Cell Number of Failed RB Setups for Cell (configuration unsupported) Number of Failed RB Setups for Cell (physical channel failure) Number of Failed RB Setups for Cell (cell update occurred) Number of Failed RB Setups for Cell (invalid configuration) Number of Failed RB Setups for Cell (no reply) Number of RB Reconfiguration Attempts for Cell Number of Successful RB Reconfigurations for Cell Number of Failed RB Reconfigurations for Cell (configuration unsupported) Number of Failed RB Reconfigurations for Cell (physical channel failure) Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67180115
VS.FailRBSetup.Cf gUnsup
67180116
VS.FailRBSetup.P hyChFail
67180119
VS.FailRBSetup.C ellUpd VS.FailRBSetup.In cCfg
67180120
67180121
VS.FailRBSetup.N oReply VS.AttRBRecfg
67180122
67180123
VS.SuccRBRecfg
67180124
VS.FailRBRecfg.Cf gUnsup
67180125
VS.FailRBRecfg.P hyChFail
Issue 01 (2013-05-04)
2048
Counter ID 67180128
Counter Name VS.FailRBRecfg.C ellUpd
Counter Description Number of Failed RB Reconfigurations for Cell (cell update occurred) Number of Failed RB Reconfigurations for Cell (invalid configuration) Number of Failed RB Reconfigurations for Cell (no reply) Number of AMR Users with DL rate of 10.2 Kbit/s for Cell Number of AMR Users with DL rate of 12.2 Kbit/s for Cell Number of AMR Users with DL rate of 7.95 Kbit/s for Cell Number of AMR Users with DL rate of 7.4 Kbit/s for Cell Number of AMR Users with DL rate of 6.7 Kbit/s for Cell Number of AMR Users with DL rate of 5.9 Kbit/s for Cell Number of AMR Users with DL rate of 5.15 Kbit/s for Cell Number of AMR Users with DL rate of 4.75 Kbit/s for Cell Number of AMR Users with UL rate of 10.2 Kbit/s for Cell Number of AMR Users with UL rate of 12.2 Kbit/s for Cell
67180129
VS.FailRBRecfg.In cCfg
67180130
VS.FailRBRecfg.N oReply VS.RB.AMR.DL. 10.2 VS.RB.AMR.DL. 12.2 VS.RB.AMR.DL. 7.95 VS.RB.AMR.DL. 7.4 VS.RB.AMR.DL. 6.7 VS.RB.AMR.DL. 5.9 VS.RB.AMR.DL. 5.15 VS.RB.AMR.DL. 4.75 VS.RB.AMR.UL. 10.2 VS.RB.AMR.UL. 12.2
Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67199619
67199620
67199621
67199622
67199780
67199623
67199624
67199625
67199626
67199627
Issue 01 (2013-05-04)
2049
Counter ID 67199628
Counter Name VS.RB.AMR.UL. 7.95 VS.RB.AMR.UL. 7.4 VS.RB.AMR.UL. 6.7 VS.RB.AMR.UL. 5.9 VS.RB.AMR.UL. 5.15 VS.RB.AMR.UL. 4.75 VS.RB.PS.Conv.D L.64
Counter Description Number of AMR Users with UL rate of 7.95 Kbit/s for Cell Number of AMR Users with UL rate of 7.4 Kbit/s for Cell Number of AMR Users with UL rate of 6.7 Kbit/s for Cell Number of AMR Users with UL rate of 5.9 Kbit/s for Cell Number of AMR Users with UL rate of 5.15 Kbit/s for Cell Number of AMR Users with UL rate of 4.75 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with DL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with UL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 128 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 144 Kbit/s for Cell
Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 V900R012
67199629
67199781
67199630
67199631
67199632
67203430
67203434
VS.RB.PS.Conv.U L.64
V900R012
67199594
VS.RB.PS.Bkg.DL. 128
67199595
Issue 01 (2013-05-04)
2050
Counter ID 67199591
Counter Name VS.RB.PS.Bkg.DL. 16
Counter Description Average Number of RBs for PS R99 Background Services with DL Rate of 16 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 256 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 32 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 384 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 8 Kbit/s for Cell Average Number of RBs for CS Conversational Services with DL Rate of 64 Kbit/s for Cell
67199596
67199592
VS.RB.PS.Bkg.DL. 32
67199597
67199593
VS.RB.PS.Bkg.DL. 64
67199590
VS.RB.PS.Bkg.DL. 8
67199556
VS.RB.CS.Conv.D L.64
Issue 01 (2013-05-04)
2051
Counter ID 67203438
Counter Name VS.RB.CS.Conv.U L.64
Counter Description Average Number of RBs for CS Conversational Services with UL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 128 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 144 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 16 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 256 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 32 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 384 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 64 Kbit/s for Cell
67199578
VS.RB.PS.Int.DL. 128
67199579
67199575
VS.RB.PS.Int.DL. 16
67199580
67199576
VS.RB.PS.Int.DL. 32
67199581
67199577
VS.RB.PS.Int.DL. 64
Issue 01 (2013-05-04)
2052
Counter ID 67199574
Counter Name VS.RB.PS.Int.DL.8
Counter Description Average Number of RBs for PS R99 Interactive Services with DL Rate of 8 Kbit/s for Cell Average Number of RBs for CS Streaming Services with DL Rate of 57.6 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 128 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 144 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 32 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 8 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 16 Kbit/s for Cell
67199560
VS.RB.CS.Str.DL. 57.6
67199569
VS.RB.PS.Str.DL. 128
67199570
VS.RB.PS.Str.DL. 144
67199567
VS.RB.PS.Str.DL. 32
67199568
VS.RB.PS.Str.DL. 64
67203439
VS.RB.PS.Str.DL.8
67203440
VS.RB.PS.Str.DL. 16
Issue 01 (2013-05-04)
2053
Counter ID 67199602
Counter Name VS.RB.PS.Bkg.UL. 128
Counter Description Average Number of RBs for PS R99 Background Services with UL Rate of 128 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with UL Rate of 144 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with UL Rate of 16 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with UL Rate of 256 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with UL Rate of 32 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with UL Rate of 384 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with UL Rate of 64 Kbit/s for Cell
67199603
VS.RB.PS.Bkg.UL. 144
67199599
VS.RB.PS.Bkg.UL. 16
67199604
67199600
VS.RB.PS.Bkg.UL. 32
67199605
67199601
VS.RB.PS.Bkg.UL. 64
Issue 01 (2013-05-04)
2054
Counter ID 67199598
Counter Name VS.RB.PS.Bkg.UL. 8
Counter Description Average Number of RBs for PS R99 Background Services with UL Rate of 8 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 128 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 144 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 16 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 256 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 32 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 384 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 64 Kbit/s for Cell
67199586
VS.RB.PS.Int.UL. 128
67199587
67199583
VS.RB.PS.Int.UL. 16
67199588
67199584
VS.RB.PS.Int.UL. 32
67199589
67199585
VS.RB.PS.Int.UL. 64
Issue 01 (2013-05-04)
2055
Counter ID 67199582
Counter Name VS.RB.PS.Int.UL.8
Counter Description Average Number of RBs for PS R99 Interactive Services with UL Rate of 8 Kbit/s for Cell Average Number of RBs for CS Streaming Services with UL Rate of 57.6 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 16 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 32 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 8 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 128 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 144 Kbit/s for Cell
67203442
VS.RB.CS.Str.UL. 57.6
67199571
VS.RB.PS.Str.UL. 16
67199572
VS.RB.PS.Str.UL. 32
67199573
VS.RB.PS.Str.UL. 64
67203445
VS.RB.PS.Str.UL.8
67203446
VS.RB.PS.Str.UL. 128
67203447
VS.RB.PS.Str.UL. 144
Issue 01 (2013-05-04)
2056
Counter ID 67192389
Counter Name VS.DRD.RBSetup. AttOut
Counter Description Number of RB Setup Attempts for Outgoing InterFrequency Directed Retry for Cell Number of Successful RB Setup for Outgoing InterFrequency Directed Retry for Cell Number of RB Setup Attempts for Incoming InterFrequency Directed Retry for Cell Number of Successful RB Setup for Incoming InterFrequency Directed Retry for Cell Number of RB Reconfiguration Attempts for Outgoing InterFrequency Directed Retry for Cell Number of Successful RB Reconfiguration for Outgoing InterFrequency Directed Retry for Cell Number of RB Reconfiguration Attempts for Incoming InterFrequency Directed Retry for Cell Number of Successful RB Reconfiguration for Incoming InterFrequency Directed Retry for Cell
67192390
VS.DRD.RBSetup. SuccOut
67192391
VS.DRD.RBSetup. AttIn
67192392
VS.DRD.RBSetup. SuccIn
67192393
VS.DRD.RBRecfg. AttOut
67192394
VS.DRD.RBRecfg. SuccOut
67192395
VS.DRD.RBRecfg. AttIn
67192396
VS.DRD.RBRecfg. SuccIn
Issue 01 (2013-05-04)
2057
Counter ID 67192440
Counter Name VS.DRD.RB.D2H. AttOut
Counter Description Number of Outgoing DCH-to-HSDPA Directed Retry Attempts for Cell Number of Successful Outgoing DCH-to-HSDPA Directed Retry for Cell Number of Incoming DCH-to-HSDPA Directed Retry Attempts for Cell Number of Successful Incoming DCH-to-HSDPA Directed Retry for Cell Number of Outgoing DCH-to-HSUPA Directed Retry Attempts for Cell Number of Successful DCH-toHSUPA Directed Retry for Cell Number of Incoming DCH-to-HSUPA Directed Retry Attempts for Cell Number of Successful Incoming DCH-to-HSUPA Directed Retry for Cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 23.85 kbit/s in the cell
67192441
VS.DRD.RB.D2H.S uccOut
67192442
VS.DRD.RB.D2H. AttIn
67192443
VS.DRD.RB.D2H.S uccIn
67195503
VS.DRD.RB.D2E. AttOut
67195504
VS.DRD.RB.D2E.S uccOut
67195505
VS.DRD.RB.D2E. AttIn
67195506
VS.DRD.RB.D2E.S uccIn
67203803
VS.RB.AMRWB.D L.23.85
V900R012
Issue 01 (2013-05-04)
2058
Counter ID 67203804
Counter Name VS.RB.AMRWB.D L.23.05
Counter Description Number of UEs that use the CS AMR WB speech service at the DL bit rate of 23.05 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 19.85 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 18.25 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 15.85 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 14.25 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 12.65 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 8.85 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 6.60 kbit/s in the cell
67203805
V900R012
67203806
V900R012
67203807
V900R012
67203808
V900R012
67203809
67203810
67203811
V900R012
Issue 01 (2013-05-04)
2059
Counter ID 67203812
Counter Name VS.RB.AMRWB.U L.23.85
Counter Description Number of UEs that use the CS AMR WB speech service at the UL bit rate of 23.85 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 23.05 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 19.85 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 18.25 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 15.85 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 14.25 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 12.65 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 8.85 kbit/s in the cell
67203813
VS.RB.AMRWB.U L.23.05
V900R012
67203814
V900R012
67203815
V900R012
67203816
V900R012
67203817
V900R012
67203818
V900R012
67203819
Issue 01 (2013-05-04)
2060
Counter ID 67203820
Counter Name VS.RB.AMRWB.U L.6.60
Counter Description Number of UEs that use the CS AMR WB speech service at the UL bit rate of 6.60 kbit/s in the cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 256 Kbit/s or 384 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 256 Kbit/s or 384 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with DL Rate of 38.8 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with UL Rate of 38.8 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with DL Rate of 39.2 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with UL Rate of 39.2 Kbit/s for Cell
67203441
VS.RB.PS.Str.DL. 256.384
67203448
VS.RB.PS.Str.UL. 256.384
67204790
VS.RB.PS.Conv.D L.38.8
67204794
VS.RB.PS.Conv.U L.38.8
67204791
67204795
Issue 01 (2013-05-04)
2061
Counter ID 67204792
Counter Name VS.RB.PS.Conv.D L.40
Counter Description Average Number of RBs for PS R99 Conversational Services with DL Rate of 40 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with UL Rate of 40 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with DL Rate of 42.8 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with UL Rate of 42.8 Kbit/s for Cell Number of Successful CS Voice Directed Retry Based on Inter-Frequency Measurement for Cell Number of CS Voice Directed Retry Attempts Based on Inter-Frequency Measurement for Cell Number of PS R99 Directed Retry Attempts Based on Inter-Frequency Measurement for Cell
67204796
VS.RB.PS.Conv.U L.40
67204793
67204797
67196294
VS.DRD.IFREQ.C S.MBDR.RBSetup. SuccOut
67196293
VS.DRD.IFREQ.C S.MBDR.RBSetup. AttOut
67196295
VS.DRD.IFREQ.P S.MBDR.R99.RBS etup.AttOut
Issue 01 (2013-05-04)
2062
Counter ID 67196296
Counter Name VS.DRD.IFREQ.P S.MBDR.R99.RBS etup.SuccOut
Counter Description Number of Successful PS R99 Directed Retry Based on Inter-Frequency Measurement for Cell Number of HSDPA PS Directed Retry Attempts Based on Inter-Frequency Measurement for Cell Number of Successful HSDPA PS Directed Retry Based on InterFrequency Measurement for Cell Number of Times that PS Rate Downgrades to 0 Kbit/s in the Best Cell Number of PS Conversation UEs on HS-DSCH for Cell Number of PS Conversation UEs on EDCH for Cell Number of Outgoing DRD Attempts through Physical Channel Reconfiguration for Cell Number of Successful Outgoing DRDs through Physical Channel Reconfiguration for Cell
67196297
VS.DRD.IFREQ.P S.MBDR.HResCon g.RBSetup.AttOut
67196298
VS.DRD.IFREQ.P S.MBDR.HResCon g.RBSetup.SuccOut
67196303
VS.RB.RateDown. To.0kbps
73415857
VS.RB.PS.Conv.H SDSCH VS.RB.PS.Conv.E DCH VS.DRD.PhyRecfg. AttOut
V900R012
73415858
V900R012
73394053
V900R012
73394054
VS.DRD.PhyRecfg. SuccOut
V900R012
Issue 01 (2013-05-04)
2063
Counter ID 73394055
Counter Name VS.DRD.PhyRecfg. AttIn
Counter Description Number of Incoming DRD Attempts through Physical Channel Reconfiguration for Cell Number of Successful Incoming DRDs through Physical Channel Reconfiguration for Cell Number of RB Setup Attempts After the RB Setup DRD Rollback Number of successful RB Setups After the RB Setup DRD Rollback Number of RB Reconfiguration Attempts After the RB Reconfiguration DRD Rollback Number of Successful RB Reconfigurations After the RB Reconfiguration DRD Rollback Number of Physical Channel Reconfiguration Attempts After the Physical Channel Reconfiguration DRD Rollback
73394056
VS.DRD.PhyRecfg. SuccIn
V900R012
73421487
VS.DRD.RBSetup. AttEstab.RollBack
V900R012
73421488
VS.DRD.RBSetup. SuccEstab.RollBack VS.DRD.RBRecfg. AttEstab.RollBack
V900R012
73421489
V900R012
73421490
VS.DRD.RBRecfg. SuccEstab.RollBack
V900R012
73421491
VS.DRD.PhyRecfg. AttEstab.RollBack
V900R012
Issue 01 (2013-05-04)
2064
Counter ID 73421492
Counter Name VS.DRD.PhyRecfg. SuccEstab.RollBack
Counter Description Number of Successful Physical Channel Reconfigurations After the Physical Channel Reconfiguration DRD Rollback Number of Outgoing FACH-to-HSDPA Directed Retry Attempts for Cell Number of Successful Outgoing FACH-to-HSDPA Directed Retries for Cell Number of Outgoing FACH-to-HSUPA Directed Retry Attempts for Cell Number of Successful Outgoing FACH-to-HSUPA Directed Retries for Cell Number of Incoming FACH-to-HSDPA Directed Retry Attempts for Cell Number of Successful Incoming FACH-to-HSDPA Directed Retries for Cell Number of Incoming FACH-to-HSUPA Directed Retry Attempts for Cell Number of Successful Incoming FACH-to-HSUPA Directed Retries for Cell
73421842
VS.DRD.RB.F2H. AttOut
V900R012
73421843
VS.DRD.RB.F2H.S uccOut
V900R012
73421844
VS.DRD.RB.F2E.A ttOut
V900R012
73421845
VS.DRD.RB.F2E.S uccOut
V900R012
73421846
VS.DRD.RB.F2H. AttIn
V900R012
73421847
VS.DRD.RB.F2H.S uccIn
V900R012
73421848
VS.DRD.RB.F2E.A ttIn
V900R012
73421849
VS.DRD.RB.F2E.S uccIn
V900R012
Issue 01 (2013-05-04)
2065
Counter ID 73394177
Counter Name VS.AttPhyRecfg.F2 P
Counter Description Number of CELL_FACH to CELL_PCH Transition Attempts by Physical Channel Reconfiguration for Cell Number of Successful CELL_FACH to CELL_PCH Transitions by Physical Channel Reconfiguration for Cell Number of Incoming Inter-Frequency DRD Attempts Triggered by Multiband Direct Retry Based on UE Location for Cell Number of Successful Incoming Inter-Frequency DRDs Triggered by Multiband Direct Retry Based on UE Location for Cell Number of Outgoing Inter-Frequency DRD Attempts Triggered by Multiband Direct Retry Based on UE Location for Cell Number of Successful Outgoing Inter-Frequency DRDs Triggered by Multiband Direct Retry Based on UE Location for Cell
73394178
VS.SuccPhyRecfg. F2P
V900R014
73425827
VS.UELocation.M ultiBand.DRD.AttIn
V900R015
73425835
VS.UELocation.M ultiBand.DRD.SuccIn
V900R015
73425836
VS.UELocation.M ultiBand.DRD.AttOut
V900R015
73425837
VS.UELocation.M ultiBand.DRD.SuccOut
V900R015
Issue 01 (2013-05-04)
2066
Counter ID 73426249
Counter Name VS.MCDRD.Perio dic.AttOut
Counter Description Number of Periodic Inter-Frequency Outgoing Directed Retry Attempts based on Measurement for Cell Number of Successful Periodic Inter-Frequency Outgoing Directed Retries based on Measurement for Cell Number of Periodic Inter-Frequency Ingoing Directed Retry Attempts based on Measurement for Cell Number of Successful Periodic Inter-Frequency Ingoing Directed Retries based on Measurement for Cell
73426250
VS.MCDRD.Perio dic.SuccOut
V900R015
73426251
VS.MCDRD.Perio dic.AttIn
V900R015
73426252
VS.MCDRD.Perio dic.SuccIn
V900R015
None
1.12.34.1 Number of RB Setup Attempts Counters

Counter ID 67180113 Counter Name VS.AttRBSetup Counter Description Number of RB Setup Attempts for Cell
Issue 01 (2013-05-04)
2067
Description
This counter provides the number of times that the RNC sends to the UE a RADIO BEARER SETUP message in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a RADIO BEARER SETUP message to the UE. In this case, this counter is measured in the best cell that the UE camps on. Figure 1-977 RB setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.AttRBSetup Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
2068
Issue 01 (2013-05-04)
1.12.34.2 Number of Successful RB Setups Counters

Counter ID 67180114 Counter Name VS.SuccRBSetup Counter Description Number of Successful RB Setups for Cell
Description
This counter provides the number of times that the RNC receives from the UE a RADIO BEARER SETUP COMPLETE message in the best cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. In this case, this counter is measured in the best cell that the UE camps on. Figure 1-978 RB setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SuccRBSetup Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.34.3 Counters Related to the Number of Failed RB Setups for Different Causes Counters
Counter ID 67180115 Counter Name VS.FailRBSetup.CfgUnsup Counter Description Number of Failed RB Setups for Cell (configuration unsupported) Number of Failed RB Setups for Cell (physical channel failure) Number of Failed RB Setups for Cell (cell update occurred) Number of Failed RB Setups for Cell (invalid configuration) Number of Failed RB Setups for Cell (no reply)
67180116
VS.FailRBSetup.PhyChFail
67180119
VS.FailRBSetup.CellUpd
67180120
VS.FailRBSetup.IncCfg
67180121
VS.FailRBSetup.NoReply
Description
These counters provide the number of times that the RB setup fails in the best cell due to different causes.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a RADIO BEARER SETUP FAILURE message from the UE. In this case, the corresponding counter is measured in the best cell that the UE camps on based on the failure cause.
Figure 1-979 RB setup procedure (failed operation)
The measurement is triggered at point A as shown in the following figure. When the RNC fails to receive from the UE a RADIO BEARER SETUP COMPLETE message before the timer expires, the VS.FailRBSetup.NoReply counter is measured in the best cell that the UE camps on. Figure 1-980 RB setup procedure(no replay)
The measurement is triggered at point A as shown in the figure. The RNC receives a CELL UPDATE message while waiting for a RADIO BEARER SETUP COMPLETE message, and as a result the RB setup fails. Under this condition, this counter is increased by one in the best cell that the UE camps on.
Figure 1-981 RB setup procedure(cell update)
Formula
None
Unit
None
Related Features
Counter Name VS.FailRBSetup.CfgUnsup Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
2072
VS.FailRBSetup.PhyChFail
WRFD-010510
VS.FailRBSetup.CellUpd
WRFD-010510
VS.FailRBSetup.IncCfg
WRFD-010510
VS.FailRBSetup.NoReply
WRFD-010510
Issue 01 (2013-05-04)
1.12.34.4 Number of RB Reconfiguration Attempts Counters

Counter ID 67180122 Counter Name VS.AttRBRecfg Counter Description Number of RB Reconfiguration Attempts for Cell
Description
This counter provides the number of times that the RNC sends to the UE a RADIO BEARER RECONFIGURATION message in the best cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a RADIO BEARER RECONFIGURATION message to the UE. In this case, this counter is measured in the best cell that the UE camps on. Figure 1-982 RB reconfiguration procedure (successful operation)
Issue 01 (2013-05-04)
2073
Formula
None
Unit
None
Related Features
Counter Name VS.AttRBRecfg Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.34.5 Number of Successful RB Reconfigurations Counters

Counter ID 67180123 Counter Name VS.SuccRBRecfg Counter Description Number of Successful RB Reconfigurations for Cell
Description
This counter provides the number of times that the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message in the best cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from the UE. In this case, this counter is measured in the best cell that the UE camps on.
Issue 01 (2013-05-04)
2074
Figure 1-983 RB reconfiguration procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SuccRBRecfg Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.34.6 Counters Related to the Number of Failed RB Reconfigurations for Different Causes
Issue 01 (2013-05-04)
2075
Counters
Counter ID 67180124 Counter Name VS.FailRBRecfg.CfgUnsup Counter Description Number of Failed RB Reconfigurations for Cell (configuration unsupported) Number of Failed RB Reconfigurations for Cell (physical channel failure) Number of Failed RB Reconfigurations for Cell (cell update occurred) Number of Failed RB Reconfigurations for Cell (invalid configuration) Number of Failed RB Reconfigurations for Cell (no reply)
67180125
VS.FailRBRecfg.PhyChFail
67180128
VS.FailRBRecfg.CellUpd
67180129
VS.FailRBRecfg.IncCfg
67180130
VS.FailRBRecfg.NoReply
Description
These counters provide the number of times that the RB reconfiguration fails in the best cell due to different causes.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a RADIO BEARER RECONFIGURATION FAILURE message from the UE. In this case, the corresponding counter is measured in the best cell that the UE camps on based on the failure cause. Figure 1-984 RB reconfiguration procedure (failed operation)
Issue 01 (2013-05-04)
2076
The measurement is triggered at point A as shown in the following figure. When the RNC fails to receive from the UE a RADIO BEARER RECONFIGURATION COMPLETE message before the timer expires, the VS.FailRBRecfg.NoReply counter is measured in the best cell that the UE camps on. Figure 1-985 RB reconfiguration procedure (failed operation)(no reply)
The measurement is triggered at point A as shown in the figure. The RNC receives a CELL UPDATE message while waiting for a RADIO BEARER RECONFIGURATION COMPLETE message, and as a result the RB setup fails. Under this condition, this counter is increased by one in the best cell that the UE camps on. Figure 1-986 RB reconfiguration procedure(cell update)
Formula
None
Unit
None
Related Features
Counter Name VS.FailRBRecfg.CfgUnsup Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.FailRBRecfg.PhyChFail
WRFD-010510
VS.FailRBRecfg.CellUpd
WRFD-010510
VS.FailRBRecfg.IncCfg
WRFD-010510
VS.FailRBRecfg.NoReply
WRFD-010510
1.12.34.7 Number of AMR Users with Different UL and DL Rates for Cell Counters
Counter ID 67199625 Counter Name VS.RB.AMR.DL.4.75 Counter Description Number of AMR Users with DL rate of 4.75 Kbit/s for Cell Number of AMR Users with DL rate of 10.2 Kbit/s for Cell Number of AMR Users with DL rate of 12.2 Kbit/s for Cell
67199619
VS.RB.AMR.DL.10.2
67199620
VS.RB.AMR.DL.12.2
Issue 01 (2013-05-04)
2078
Counter ID 67199621
Counter Name VS.RB.AMR.DL.7.95
Counter Description Number of AMR Users with DL rate of 7.95 Kbit/s for Cell Number of AMR Users with DL rate of 7.4 Kbit/s for Cell Number of AMR Users with DL rate of 6.7 Kbit/s for Cell Number of AMR Users with DL rate of 5.9 Kbit/s for Cell Number of AMR Users with DL rate of 5.15 Kbit/s for Cell Number of AMR Users with UL rate of 10.2 Kbit/s for Cell Number of AMR Users with UL rate of 12.2 Kbit/s for Cell Number of AMR Users with UL rate of 7.95 Kbit/s for Cell Number of AMR Users with UL rate of 7.4 Kbit/s for Cell Number of AMR Users with UL rate of 6.7 Kbit/s for Cell Number of AMR Users with UL rate of 5.9 Kbit/s for Cell Number of AMR Users with UL rate of 5.15 Kbit/s for Cell Number of AMR Users with UL rate of 4.75 Kbit/s for Cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 23.85 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 23.05 kbit/s in the cell
2079
67199622 67199780 67199623 67199624
VS.RB.AMR.DL.7.4 VS.RB.AMR.DL.6.7 VS.RB.AMR.DL.5.9 VS.RB.AMR.DL.5.15
67199626
VS.RB.AMR.UL.10.2
67199627
VS.RB.AMR.UL.12.2
67199628
VS.RB.AMR.UL.7.95
67199629 67199781 67199630 67199631
VS.RB.AMR.UL.7.4 VS.RB.AMR.UL.6.7 VS.RB.AMR.UL.5.9 VS.RB.AMR.UL.5.15
67199632
VS.RB.AMR.UL.4.75
67203803
VS.RB.AMRWB.DL.23.85
67203804
Issue 01 (2013-05-04)
Counter ID 67203805
Counter Name VS.RB.AMRWB.DL.19.85
Counter Description Number of UEs that use the CS AMR WB speech service at the DL bit rate of 19.85 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 18.25 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 15.85 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 14.25 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 12.65 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 8.85 kbit/ s in the cell Number of UEs that use the CS AMR WB speech service at the DL bit rate of 6.60 kbit/ s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 23.85 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 23.05 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 19.85 kbit/s in the cell
67203806
67203807
67203808
67203809
67203810
VS.RB.AMRWB.DL.8.85
67203811
VS.RB.AMRWB.DL.6.60
67203812
VS.RB.AMRWB.UL.23.85
67203813
67203814
Issue 01 (2013-05-04)
2080
Counter ID 67203815
Counter Name VS.RB.AMRWB.UL.18.25
Counter Description Number of UEs that use the CS AMR WB speech service at the UL bit rate of 18.25 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 15.85 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 14.25 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 12.65 kbit/s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 8.85 kbit/ s in the cell Number of UEs that use the CS AMR WB speech service at the UL bit rate of 6.60 kbit/ s in the cell
67203816
67203817
67203818
67203819
VS.RB.AMRWB.UL.8.85
67203820
VS.RB.AMRWB.UL.6.60
Description
These counters provide the number of narrowband and wideband AMR users with different uplink and downlink rates in the cells in the active set.
Measurement point
The RNC takes samples of numbers of AMR users at different uplink and downlink bit rates for various types of services every 30 seconds. At the end of the measurement period, the RNC obtains the mean number of users for each type of service by dividing the accumulated number of users for each type of service at each bit rate by the sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.RB.AMR.DL.4.75 VS.RB.AMR.DL.10.2 VS.RB.AMR.DL.12.2 VS.RB.AMR.DL.7.95 VS.RB.AMR.DL.7.4 VS.RB.AMR.DL.6.7 VS.RB.AMR.DL.5.9 VS.RB.AMR.DL.5.15 VS.RB.AMR.UL.10.2 VS.RB.AMR.UL.12.2 VS.RB.AMR.UL.7.95 VS.RB.AMR.UL.7.4 VS.RB.AMR.UL.6.7 VS.RB.AMR.UL.5.9 VS.RB.AMR.UL.5.15 VS.RB.AMR.UL.4.75 VS.RB.AMRWB.DL.23.85 Feature ID WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010613 WRFD-010510 Feature Name Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class AMR-WB (Adaptive Multi Rate Wide Band) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release VS.RB.AMRWB.DL.23.05 WRFD-010613 WRFD-010510 AMR-WB (Adaptive Multi Rate Wide Band) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release VS.RB.AMRWB.DL.19.85 WRFD-010613 WRFD-010510 AMR-WB (Adaptive Multi Rate Wide Band) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
2082
Counter Name VS.RB.AMRWB.DL.18.25
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
VS.RB.AMRWB.DL.8.85
WRFD-010613 WRFD-010510
VS.RB.AMRWB.DL.6.60
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
Issue 01 (2013-05-04)
2083
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
WRFD-010613 WRFD-010510
VS.RB.AMRWB.UL.8.85
WRFD-010613 WRFD-010510
Issue 01 (2013-05-04)
2084
1.12.34.8 Average Number of CS Conversational or Streaming Service RBs for Cell Counters
Counter ID 67203438 Counter Name VS.RB.CS.Conv.UL.64 Counter Description Average Number of RBs for CS Conversational Services with UL Rate of 64 Kbit/s for Cell Average Number of RBs for CS Conversational Services with DL Rate of 64 Kbit/s for Cell Average Number of RBs for CS Streaming Services with DL Rate of 57.6 Kbit/s for Cell Average Number of RBs for CS Streaming Services with UL Rate of 57.6 Kbit/s for Cell
67199556
VS.RB.CS.Conv.DL.64
67199560
VS.RB.CS.Str.DL.57.6
67203442
VS.RB.CS.Str.UL.57.6
Description
These counters provide the average numbers of RBs for various types of CS services at different uplink and downlink bit rates in a cell of the active set.
Measurement point
The takes samples of numbers of RBs at different bit rates for various types of CS services every 5 seconds. At the end of the measurement period, the RNC obtains the mean number of RBs for each type of CS service by dividing the accumulated number of RBs for each type of CS service at each bit rate by the sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.RB.CS.Conv.UL.64 VS.RB.CS.Conv.DL.64 VS.RB.CS.Str.DL.57.6 VS.RB.CS.Str.UL.57.6 Feature ID WRFD-010501 WRFD-010501 WRFD-010502 WRFD-010502 Feature Name Conversational QoS Class Conversational QoS Class Streaming QoS Class Streaming QoS Class
1.12.34.9 Number of RBs for PS R99 Services with various Uplink and Downlink Rates for Cell Counters
Counter ID 67199598 Counter Name VS.RB.PS.Bkg.UL.8 Counter Description Average Number of RBs for PS R99 Background Services with UL Rate of 8 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with DL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with UL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 128 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 144 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 16 Kbit/s for Cell
2086
67203430
VS.RB.PS.Conv.DL.64
67203434
VS.RB.PS.Conv.UL.64
67199594
VS.RB.PS.Bkg.DL.128
67199595
VS.RB.PS.Bkg.DL.144
67199591
VS.RB.PS.Bkg.DL.16
Issue 01 (2013-05-04)
Counter ID 67199596
Counter Name VS.RB.PS.Bkg.DL.256
Counter Description Average Number of RBs for PS R99 Background Services with DL Rate of 256 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 32 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 384 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with DL Rate of 8 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 128 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 144 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 16 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 256 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 32 Kbit/s for Cell
67199592
VS.RB.PS.Bkg.DL.32
67199597
VS.RB.PS.Bkg.DL.384
67199593
VS.RB.PS.Bkg.DL.64
67199590
VS.RB.PS.Bkg.DL.8
67199578
VS.RB.PS.Int.DL.128
67199579
VS.RB.PS.Int.DL.144
67199575
VS.RB.PS.Int.DL.16
67199580
VS.RB.PS.Int.DL.256
67199576
VS.RB.PS.Int.DL.32
Issue 01 (2013-05-04)
2087
Counter ID 67199581
Counter Name VS.RB.PS.Int.DL.384
Counter Description Average Number of RBs for PS R99 Interactive Services with DL Rate of 384 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with DL Rate of 8 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 128 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 144 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 32 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 8 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with DL Rate of 16 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with UL Rate of 128 Kbit/s for Cell
67199577
VS.RB.PS.Int.DL.64
67199574
VS.RB.PS.Int.DL.8
67199569
VS.RB.PS.Str.DL.128
67199570
VS.RB.PS.Str.DL.144
67199567
VS.RB.PS.Str.DL.32
67199568
VS.RB.PS.Str.DL.64
67203439
VS.RB.PS.Str.DL.8
67203440
VS.RB.PS.Str.DL.16
67199602
VS.RB.PS.Bkg.UL.128
Issue 01 (2013-05-04)
2088
Counter ID 67199603
Counter Name VS.RB.PS.Bkg.UL.144
Counter Description Average Number of RBs for PS R99 Background Services with UL Rate of 144 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with UL Rate of 16 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with UL Rate of 256 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with UL Rate of 32 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with UL Rate of 384 Kbit/s for Cell Average Number of RBs for PS R99 Background Services with UL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 128 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 144 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 16 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 256 Kbit/s for Cell
67199599
VS.RB.PS.Bkg.UL.16
67199604
VS.RB.PS.Bkg.UL.256
67199600
VS.RB.PS.Bkg.UL.32
67199605
VS.RB.PS.Bkg.UL.384
67199601
VS.RB.PS.Bkg.UL.64
67199586
VS.RB.PS.Int.UL.128
67199587
VS.RB.PS.Int.UL.144
67199583
VS.RB.PS.Int.UL.16
67199588
VS.RB.PS.Int.UL.256
Issue 01 (2013-05-04)
2089
Counter ID 67199584
Counter Name VS.RB.PS.Int.UL.32
Counter Description Average Number of RBs for PS R99 Interactive Services with UL Rate of 32 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 384 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Interactive Services with UL Rate of 8 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 16 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 32 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 64 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 8 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 128 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 144 Kbit/s for Cell
67199589
VS.RB.PS.Int.UL.384
67199585
VS.RB.PS.Int.UL.64
67199582
VS.RB.PS.Int.UL.8
67199571
VS.RB.PS.Str.UL.16
67199572
VS.RB.PS.Str.UL.32
67199573
VS.RB.PS.Str.UL.64
67203445
VS.RB.PS.Str.UL.8
67203446
VS.RB.PS.Str.UL.128
67203447
VS.RB.PS.Str.UL.144
Issue 01 (2013-05-04)
2090
Counter ID 67203441
Counter Name VS.RB.PS.Str.DL.256.384
Counter Description Average Number of RBs for PS R99 Streaming Services with DL Rate of 256 Kbit/s or 384 Kbit/s for Cell Average Number of RBs for PS R99 Streaming Services with UL Rate of 256 Kbit/s or 384 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with DL Rate of 38.8 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with UL Rate of 38.8 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with DL Rate of 39.2 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with UL Rate of 39.2 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with DL Rate of 40 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with UL Rate of 40 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with DL Rate of 42.8 Kbit/s for Cell Average Number of RBs for PS R99 Conversational Services with UL Rate of 42.8 Kbit/s for Cell
67203448
VS.RB.PS.Str.UL.256.384
67204790
VS.RB.PS.Conv.DL.38.8
67204794
VS.RB.PS.Conv.UL.38.8
67204791
67204795
67204792
VS.RB.PS.Conv.DL.40
67204796
VS.RB.PS.Conv.UL.40
67204793
67204797
Issue 01 (2013-05-04)
2091
Description
These counters provide the average number of RBs for PS R99 services with different UL and DL rates in the cells in the active set.
Measurement point
The RNC takes samples of numbers of RBs at different bit rates for various types of services every 5 seconds. At the end of the measurement period, the RNC obtains the mean number of RBs for each type of service by dividing the accumulated number of RBs for each type of service at each bit rate by the sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.RB.PS.Bkg.UL.8 VS.RB.PS.Conv.DL.64 VS.RB.PS.Conv.UL.64 VS.RB.PS.Bkg.DL.128 VS.RB.PS.Bkg.DL.144 VS.RB.PS.Bkg.DL.16 VS.RB.PS.Bkg.DL.256 VS.RB.PS.Bkg.DL.32 VS.RB.PS.Bkg.DL.384 VS.RB.PS.Bkg.DL.64 VS.RB.PS.Bkg.DL.8 VS.RB.PS.Int.DL.128 VS.RB.PS.Int.DL.144 VS.RB.PS.Int.DL.16 VS.RB.PS.Int.DL.256 VS.RB.PS.Int.DL.32 VS.RB.PS.Int.DL.384
Issue 01 (2013-05-04)
Feature ID WRFD-010504 WRFD-010501 WRFD-010501 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503
Feature Name Background QoS Class Conversational QoS Class Conversational QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class
2092
Counter Name VS.RB.PS.Int.DL.64 VS.RB.PS.Int.DL.8 VS.RB.PS.Str.DL.128 VS.RB.PS.Str.DL.144 VS.RB.PS.Str.DL.32 VS.RB.PS.Str.DL.64 VS.RB.PS.Str.DL.8 VS.RB.PS.Str.DL.16 VS.RB.PS.Bkg.UL.128 VS.RB.PS.Bkg.UL.144 VS.RB.PS.Bkg.UL.16 VS.RB.PS.Bkg.UL.256 VS.RB.PS.Bkg.UL.32 VS.RB.PS.Bkg.UL.384 VS.RB.PS.Bkg.UL.64 VS.RB.PS.Int.UL.128 VS.RB.PS.Int.UL.144 VS.RB.PS.Int.UL.16 VS.RB.PS.Int.UL.256 VS.RB.PS.Int.UL.32 VS.RB.PS.Int.UL.384 VS.RB.PS.Int.UL.64 VS.RB.PS.Int.UL.8 VS.RB.PS.Str.UL.16 VS.RB.PS.Str.UL.32 VS.RB.PS.Str.UL.64 VS.RB.PS.Str.UL.8 VS.RB.PS.Str.UL.128 VS.RB.PS.Str.UL.144 VS.RB.PS.Str.DL.256.384
Feature ID WRFD-010503 WRFD-010503 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502
Feature Name Interactive QoS Class Interactive QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class
Issue 01 (2013-05-04)
2093
Counter Name VS.RB.PS.Str.UL.256.384 VS.RB.PS.Conv.DL.38.8 VS.RB.PS.Conv.UL.38.8 VS.RB.PS.Conv.DL.39.2 VS.RB.PS.Conv.UL.39.2 VS.RB.PS.Conv.DL.40 VS.RB.PS.Conv.UL.40 VS.RB.PS.Conv.DL.42.8 VS.RB.PS.Conv.UL.42.8
Feature ID WRFD-010502 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501 WRFD-010501
Feature Name Streaming QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class Conversational QoS Class
1.12.34.10 Number of RB Setup Attempts for Outgoing Inter-Frequency Directed Retry Counters
Counter ID 67192389 Counter Name VS.DRD.RBSetup.AttOut Counter Description Number of RB Setup Attempts for Outgoing InterFrequency Directed Retry for Cell
Description
This counter provides the number of RB setup attempts for the outgoing inter-frequency directed retry in the best cell that the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends to the UE a RADIO BEARER SETUP message, this counter is measured in the best cell that the UE camps on if the message is for the inter-frequency directed retry.
Issue 01 (2013-05-04)
2094
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RBSetup.AttOut Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.11 Number of Successful RB Setup for Outgoing Inter-Frequency Directed Retry
Issue 01 (2013-05-04)
2095
Counters
Counter ID 67192390 Counter Name VS.DRD.RBSetup.SuccOut Counter Description Number of Successful RB Setup for Outgoing InterFrequency Directed Retry for Cell
Description
This counter provides the number of times that the RB is set up successfully for the outgoing inter-frequency directed retry in the best cell that the UE camps on.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a RADIO BEARER SETUP COMPLETE message, this counter is measured in the best cell that the UE camps on if the message is for the inter-frequency directed retry. Figure 1-988 RB setup procedure (successful operation)
Formula
None
Issue 01 (2013-05-04)
2096
Unit
None
Related Features
Counter Name VS.DRD.RBSetup.SuccOut Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.12 Number of RB Setup Attempts for Incoming Inter-Frequency Directed Retry Counters
Counter ID 67192391 Counter Name VS.DRD.RBSetup.AttIn Counter Description Number of RB Setup Attempts for Incoming InterFrequency Directed Retry for Cell
Description
This counter provides the number of RB setup attempts for the incoming inter-frequency directed retry in the cell that the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends to the UE a RADIO BEARER SETUP message, this counter is measured in the target cell if the message is for the inter-frequency directed retry.
Issue 01 (2013-05-04)
2097
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RBSetup.AttIn Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.13 Number of Successful RB Setup for Incoming Inter-Frequency Directed Retry
Issue 01 (2013-05-04)
2098
Counters
Counter ID 67192392 Counter Name VS.DRD.RBSetup.SuccIn Counter Description Number of Successful RB Setup for Incoming InterFrequency Directed Retry for Cell
Description
This counter provides the number of times that the RB is set up successfully for the incoming inter-frequency directed retry in the best cell that the UE camps on.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a RADIO BEARER SETUP COMPLETE message, this counter is measured in the target cell if the message is for the inter-frequency directed retry. Figure 1-990 RB setup procedure (successful operation)
Formula
None
Unit
None
Issue 01 (2013-05-04)
2099
Related Features
Counter Name VS.DRD.RBSetup.SuccIn Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.14 Number of RB Reconfiguration Attempts for Outgoing Inter-Frequency Directed Retry Counters
Counter ID 67192393 Counter Name VS.DRD.RBRecfg.AttOut Counter Description Number of RB Reconfiguration Attempts for Outgoing InterFrequency Directed Retry for Cell
Description
This counter provides the number of RB reconfiguration attempts for the outgoing interfrequency directed retry in the best cell that the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends to the UE a RADIO BEARER RECONFIGURATION message, this counter is measured in the best cell that the UE camps on if the message is for the inter-frequency directed retry. Figure 1-991 RB reconfiguration procedure (successful operation)
Issue 01 (2013-05-04)
2100
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RBRecfg.AttOut Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.15 Number of Successful RB Reconfiguration for Outgoing Inter-Frequency Directed Retry Counters
Counter ID 67192394 Counter Name VS.DRD.RBRecfg.SuccOut Counter Description Number of Successful RB Reconfiguration for Outgoing Inter-Frequency Directed Retry for Cell
Description
This counter provides the number of times that the RB reconfiguration succeeds for the outgoing inter-frequency directed retry in the best cell that the UE camps on.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message, this counter is measured in the best cell that the UE camps on if the message is for the inter-frequency directed retry.
Issue 01 (2013-05-04)
2101
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RBRecfg.SuccOut Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.16 Number of RB Reconfiguration Attempts for Incoming Inter-Frequency Directed Retry
Issue 01 (2013-05-04)
2102
Counters
Counter ID 67192395 Counter Name VS.DRD.RBRecfg.AttIn Counter Description Number of RB Reconfiguration Attempts for Incoming InterFrequency Directed Retry for Cell
Description
This counter provides the number of RB reconfiguration attempts for the incoming interfrequency directed retry in the cell that the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends to the UE a RADIO BEARER RECONFIGURATION message, this counter is measured in the target cell if the message is for the inter-frequency directed retry. Figure 1-993 RB reconfigureation procedure
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RBRecfg.AttIn Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.17 Number of Successful RB Reconfiguration for Incoming Inter-Frequency Directed Retry Counters
Counter ID 67192396 Counter Name VS.DRD.RBRecfg.SuccIn Counter Description Number of Successful RB Reconfiguration for Incoming Inter-Frequency Directed Retry for Cell
Description
This counter provides the number of times that the RB reconfiguration succeeds for the incoming inter-frequency directed retry in the cell that the UE camps on.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message, this counter is measured in the target cell if the message is for the inter-frequency directed retry.
Issue 01 (2013-05-04)
2104
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RBRecfg.SuccIn Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.18 Number of Outgoing or Incoming DCH-to-HSDPA or DCH-to-HSUPA Directed Retry Attempts Counters
Counter ID 67192440 Counter Name VS.DRD.RB.D2H.AttOut Counter Description Number of Outgoing DCHto-HSDPA Directed Retry Attempts for Cell
2105
Issue 01 (2013-05-04)
Counter ID 67192442
Counter Name VS.DRD.RB.D2H.AttIn
Counter Description Number of Incoming DCHto-HSDPA Directed Retry Attempts for Cell Number of Outgoing DCHto-HSUPA Directed Retry Attempts for Cell Number of Incoming DCHto-HSUPA Directed Retry Attempts for Cell
67195503
VS.DRD.RB.D2E.AttOut
67195505
VS.DRD.RB.D2E.AttIn
Description
These counters provide the number of outgoing or incoming DCH-to-HSDPA or DCH-toHSUPA directed retry attempts in the best cell that the UE camps on. The outgoing directed retry attempts are measured in the best cell where the UE camps on, and the incoming directed retry attempts are measured in the target cell of the directed retry. For a DC-HSDPA or DCHSUPA UE, these counters are measured only in the cell configured with the primary cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends to the UE a RADIO BEARER SETUP message, this counter is measured in the best cell where the UE camps on if the message is for an outgoing DCH-to-HSDPA or DCH-to-HSUPA directed retry, or measured in the target cell of the directed retry if the message is for an incoming DCH-toHSDPA or DCH-to-HSUPA directed retry. Figure 1-995 RB setup procedure (successful operation)
Issue 01 (2013-05-04)
2106
The measurement is triggered at point A as shown in the figure. When the RNC sends the UE a RADIO BEARER RECONFIGURATION message, this counter is measured in the best cell where the UE camps on if the message is for an outgoing DCH-to-HSDPA or DCH-to-HSUPA directed retry, or measured in the target cell of the directed retry if the message is for an incoming DCH-to-HSDPA or DCH-to-HSUPA directed retry. Figure 1-996 RB reconfiguration procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RB.D2H.AttOut Feature ID WRFD-01061112 WRFD-02040001 VS.DRD.RB.D2H.AttIn WRFD-01061112 WRFD-02040001 VS.DRD.RB.D2E.AttOut
Issue 01 (2013-05-04)
Feature Name HSDPA DRD Intra System Direct Retry HSDPA DRD Intra System Direct Retry Intra System Direct Retry
2107
WRFD-02040001
Counter Name VS.DRD.RB.D2E.AttIn
Feature Name Intra System Direct Retry
1.12.34.19 Number of Successful Outgoing or Incoming DCH-to-HSDPA or DCHto-HSUPA Directed Retry for Cell Counters
Counter ID 67192441 Counter Name VS.DRD.RB.D2H.SuccOut Counter Description Number of Successful Outgoing DCH-to-HSDPA Directed Retry for Cell Number of Successful Incoming DCH-to-HSDPA Directed Retry for Cell Number of Successful DCHto-HSUPA Directed Retry for Cell Number of Successful Incoming DCH-to-HSUPA Directed Retry for Cell
67192443
VS.DRD.RB.D2H.SuccIn
67195504
VS.DRD.RB.D2E.SuccOut
67195506
VS.DRD.RB.D2E.SuccIn
Description
This counter provides the number of successful outgoing or incoming DCH-to-HSDPA or DCHto-HSUPA directed retry attempts in the best cell that the UE camps on. The outgoing directed retry attempts are measured in the best cells where the UE camps on, and the incoming directed retry attempts are measured in the target cell of the directed retry. For a DC-HSDPA or DCHSUPA UE, this counter is measured only in the primary cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a RADIO BEARER SETUP COMPLETE message, this counter is measured in the best cell where the UE camps on if the message is for an outgoing RB DCH-to-HSDPA or RB DCHto-HSUPA directed retry, or measured in the target cell of the directed retry if the message is for an incoming RB DCH-to-HSDPA or RB DCH-to-HSUPA directed retry.
Issue 01 (2013-05-04)
2108
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message, this counter is measured in the best cell where the UE camps on if the message is for an outgoing RB DCHto-HSDPA or RB DCH-to-HSUPA directed retry, or measured in the target cell of the directed retry if the message is for an incoming RB DCH-to-HSDPA or RB DCH-to-HSUPA directed retry.
Issue 01 (2013-05-04)
2109
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RB.D2H.SuccOut Feature ID WRFD-01061112 WRFD-02040001 VS.DRD.RB.D2H.SuccIn WRFD-01061112 WRFD-02040001 VS.DRD.RB.D2E.SuccOut VS.DRD.RB.D2E.SuccIn WRFD-02040001 WRFD-02040001 Feature Name HSDPA DRD Intra System Direct Retry HSDPA DRD Intra System Direct Retry Intra System Direct Retry Intra System Direct Retry
1.12.34.20 Number of Successful Directed Retry Attempts Based on InterFrequency Measurement for Cell
Counters
Counter ID 67196294 Counter Name VS.DRD.IFREQ.CS.MBDR .RBSetup.SuccOut Counter Description Number of Successful CS Voice Directed Retry Based on Inter-Frequency Measurement for Cell Number of Successful PS R99 Directed Retry Based on Inter-Frequency Measurement for Cell Number of Successful HSDPA PS Directed Retry Based on Inter-Frequency Measurement for Cell
67196296
VS.DRD.IFREQ.PS.MBDR .R99.RBSetup.SuccOut
67196298
VS.DRD.IFREQ.PS.MBDR .HResCong.RBSetup.SuccOut
Description
These counters provide the number of successful directed retry attempts of different services based on the inter-frequency measurement in the best cell. The number of successful directed retry attempts for the HSDPA service based on the inter-frequency measurement is measured in the serving cell of the HSDPA service.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a RADIO BEARER SETUP COMPLETE message, the number of successful outgoing directed retry attempts based on inter-frequency measurement is measured in the best cell where the UE camps on. These counters are measured in the serving cell of the HSDPA service of the UE if the message is for the PS directed retry based on inter-frequency measurement due to HSDPA resource insufficiency.
Issue 01 (2013-05-04)
2111
Figure 1-999 RB SetUp Process
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.IFREQ.CS.MBDR .RBSetup.SuccOut Feature ID WRFD-020103 WRFD-020402 Feature Name Inter Frequency Load Balance Measurement Based Direct Retry VS.DRD.IFREQ.PS.MBDR .R99.RBSetup.SuccOut WRFD-020103 WRFD-020402 Inter Frequency Load Balance Measurement Based Direct Retry VS.DRD.IFREQ.PS.MBDR .HResCong.RBSetup.SuccOut WRFD-020103 WRFD-020402 Inter Frequency Load Balance Measurement Based Direct Retry
Issue 01 (2013-05-04)
2112
1.12.34.21 Number of Directed Retry Attempts Based on Inter-Frequency Measurement for Cell Counters
Counter ID 67196293 Counter Name VS.DRD.IFREQ.CS.MBDR .RBSetup.AttOut Counter Description Number of CS Voice Directed Retry Attempts Based on Inter-Frequency Measurement for Cell Number of PS R99 Directed Retry Attempts Based on Inter-Frequency Measurement for Cell Number of HSDPA PS Directed Retry Attempts Based on Inter-Frequency Measurement for Cell
67196295
VS.DRD.IFREQ.PS.MBDR .R99.RBSetup.AttOut
67196297
VS.DRD.IFREQ.PS.MBDR .HResCong.RBSetup.AttOut
Description
These counters provide the number of directed retry attempts for different services based on the inter-frequency measurement in the best cell. The number of directed retry attempts for the HSDPA service based on the inter-frequency measurement is measured in the serving cell of the HSDPA service.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the UE a RADIO BEARER SETUP message, the number of outgoing directed retry attempts based on inter-frequency measurement is measured in the best cell where the UE camps on. These counters are measured in the serving cell of the HSDPA service of the UE if the message is for the PS directed retry based on inter-frequency measurement due to HSDPA resource insufficiency.
Issue 01 (2013-05-04)
2113
Figure 1-1000 RB SetUp Process
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.IFREQ.CS.MBDR .RBSetup.AttOut Feature ID WRFD-020103 WRFD-020402 Feature Name Inter Frequency Load Balance Measurement Based Direct Retry VS.DRD.IFREQ.PS.MBDR .R99.RBSetup.AttOut WRFD-020103 WRFD-020402 Inter Frequency Load Balance Measurement Based Direct Retry VS.DRD.IFREQ.PS.MBDR .HResCong.RBSetup.AttOut WRFD-020103 WRFD-020402 Inter Frequency Load Balance Measurement Based Direct Retry
Issue 01 (2013-05-04)
2114
1.12.34.22 Number of Times that PS Rate Downgrades to 0 Kbit/s Counters

Counter ID 67196303 Counter Name VS.RB.RateDown.To.0kbps Counter Description Number of Times that PS Rate Downgrades to 0 Kbit/s in the Best Cell
Description
This counter provides the number of times that the rate of PS R99 services downgrades to 0 Kbit/s.
Measurement point
The measurement is triggered when the rate of PS R99 services downgrades to 0 Kbit/s.
Formula
None
Unit
None
Related Features
Counter Name VS.RB.RateDown.To.0kbps Feature ID WRFD-021101 Feature Name Dynamic Channel Configuration Control (DCCC)
1.12.34.23 Average Number of PS Conversation RBs on EDCH or HS-DSCH for Cell Counters
Counter ID 73415857 73415858 Counter Name VS.RB.PS.Conv.HSDSCH VS.RB.PS.Conv.EDCH Counter Description Number of PS Conversation UEs on HS-DSCH for Cell Number of PS Conversation UEs on EDCH for Cell
Issue 01 (2013-05-04)
2115
Description
These counters provide the average number of PS Conversation RBs on EDCH or HS-DSCH in the cell. The downlink RBs on the HS-DSCH are measured in the serving cell, and the uplink RBs on the EDCH are measured in the cells of the HSUPA active set. For a DC-HSDPA or DCHSUPA UE, these counters are measured only in the primary cell.
Measurement point
The RNC takes samples of PS conversation RB numbers carried on EDCH in the cells of the HSUPA active set or PS conversation RB numbers carried on HS-DSCH in the serving cell of HSDPA services every 5 seconds. At the end of a sampling period, the RNC obtains the average number of PS conversation RBs carried on the EDCH or HS-DSCH by dividing the accumulated number by the sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.RB.PS.Conv.HSDSCH Feature ID WRFD-010617 WRFD-010501 VS.RB.PS.Conv.EDCH WRFD-010617 WRFD-010501 Feature Name VoIP over HSPA/HSPA+ Conversational QoS Class VoIP over HSPA/HSPA+ Conversational QoS Class
1.12.34.24 Number of Outgoing DRD Attempts through Physical Channel Reconfiguration(Cell) Counters
Counter ID 73394053 Counter Name VS.DRD.PhyRecfg.AttOut Counter Description Number of Outgoing DRD Attempts through Physical Channel Reconfiguration for Cell
Description
This counter provides the number of outgoing inter-frequency directed retry attempts through physical channel reconfiguration in the best cell that the UE camps on before directed retry.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message for inter-frequency directed retry, this counter is measured in the best cell that the UE camps on before directed retry. Figure 1-1001 Physical channel reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.PhyRecfg.AttOut Feature ID WRFD-020103 WRFD-02040001 Feature Name Inter Frequency Load Balance Intra System Direct Retry
1.12.34.25 Number of Successful Outgoing DRDs through Physical Channel Reconfiguration(Cell)

Counters
Counter ID 73394054 Counter Name VS.DRD.PhyRecfg.SuccOut Counter Description Number of Successful Outgoing DRDs through Physical Channel Reconfiguration for Cell
Description
This counter provides the number of successful outgoing inter-frequency directed retries through physical channel reconfiguration in the best cell that the UE camps on before directed retry.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message for interfrequency directed retry, this counter is measured in the best cell that the UE camps on before directed retry. Figure 1-1002 Physical Channel Reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.PhyRecfg.SuccOut Feature ID WRFD-020103 WRFD-02040001 Feature Name Inter Frequency Load Balance Intra System Direct Retry
1.12.34.26 Number of Incoming DRD Attempts through Physical Channel Reconfiguration (Cell) Counters
Counter ID 73394055 Counter Name VS.DRD.PhyRecfg.AttIn Counter Description Number of Incoming DRD Attempts through Physical Channel Reconfiguration for Cell
Description
This counter provides the number of incoming inter-frequency directed retry attempts through physical channel reconfiguration in the cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message for inter-frequency directed retry, this counter is measured in the target cell of the directed retry.
Issue 01 (2013-05-04)
2119
Figure 1-1003 Physical Channel Reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.PhyRecfg.AttIn Feature ID WRFD-020103 WRFD-02040001 Feature Name Inter Frequency Load Balance Intra System Direct Retry
1.12.34.27 Number of Successful Incoming DRDs through Physical Channel Reconfiguration (Cell)
Issue 01 (2013-05-04)
2120
Counters
Counter ID 73394056 Counter Name VS.DRD.PhyRecfg.SuccIn Counter Description Number of Successful Incoming DRDs through Physical Channel Reconfiguration for Cell
Description
This counter provides the number of successful incoming inter-frequency directed retries through physical channel reconfiguration in the cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message for interfrequency directed retry, this counter is measured in the target cell of the directed retry. Figure 1-1004 Physical Channel Reconfiguration procedure
Formula
None
Issue 01 (2013-05-04)
2121
Unit
None
Related Features
Counter Name VS.DRD.PhyRecfg.SuccIn Feature ID WRFD-020103 WRFD-02040001 Feature Name Inter Frequency Load Balance Intra System Direct Retry
1.12.34.28 Number of RB Setup Attempts After the RB Setup DRD Rollback Counters
Counter ID 73421487 Counter Name VS.DRD.RBSetup.AttEstab. RollBack Counter Description Number of RB Setup Attempts After the RB Setup DRD Rollback
Description
This counter provides the number that the UE attempts to set up an RB in a target cell after the UE fails to set up an RB through DRD and the RNC performs the rollback. This counter is measured in the target cell.
Measurement point
After the RNC receives an RADIO BEARER SETUP FAILURE message in an RB setup DRD procedure, it sends an RADIO BEARER SETUP message to a target cell if it determines that a rollback can be performed, as shown in point A of the figure. This counter is measured in the target cell when the RNC sends the RADIO BEARER SETUP message.
Issue 01 (2013-05-04)
2122
Figure 1-1005 RB Setup DRD
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RBSetup.AttEstab. RollBack Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.29 Number of successful RB Setups After the RB Setup DRD Rollback Counters
Counter ID 73421488 Counter Name VS.DRD.RBSetup.SuccEsta b.RollBack Counter Description Number of successful RB Setups After the RB Setup DRD Rollback
Issue 01 (2013-05-04)
2123
Description
This counter provides the number that the UE sets up an RB successfully in a cell after the UE fails to set up an RB through DRD and the RNC performs the rollback. This counter is measured in the target cell.
Measurement point
After the RNC receives an RADIO BEARER SETUP FAILURE message in an RB setup DRD procedure, it sends an RADIO BEARER SETUP message to a target cell if it determines that a rollback can be performed, as shown in point A of the figure. This counter is measured in the target cell when the RNC receives an RADIO BEARER SETUP COMPLETE message from the UE. Figure 1-1006 RB Setup DRD
Formula
None
Unit
None
Issue 01 (2013-05-04)
2124
Related Features
Counter Name VS.DRD.RBSetup.SuccEsta b.RollBack Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.30 Number of RB Reconfiguration Attempts After the RB Reconfiguration DRD Rollback Counters
Counter ID 73421489 Counter Name VS.DRD.RBRecfg.AttEstab .RollBack Counter Description Number of RB Reconfiguration Attempts After the RB Reconfiguration DRD Rollback
Description
This counter provides the number that the RNC attempts to reconfigure an RB in a cell after the RB reconfigure through DRD fails and the RNC performs the rollback. This counter is measured in the target cell.
Measurement point
After the RNC receives an RADIO BEARER RECONFIGURATION FAILURE message in an RB reconfiguration DRD procedure, it sends an RADIO BEARER RECONFIGURATION message to a target cell if it determines that a rollback can be performed, as shown in point A of the figure. This counter is measured in the target cell when the RNC sends the RADIO BEARER RECONFIGURATION message.
Issue 01 (2013-05-04)
2125
Figure 1-1007 RB Reconfiguration DRD
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RBRecfg.AttEstab .RollBack Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.31 Number of Successful RB Reconfigurations After the RB Reconfiguration DRD Rollback
Issue 01 (2013-05-04)
2126
Counters
Counter ID 73421490 Counter Name VS.DRD.RBRecfg.SuccEsta b.RollBack Counter Description Number of Successful RB Reconfigurations After the RB Reconfiguration DRD Rollback
Description
This counter provides the number that the RB reconfiguration succeeds in a cell after the RNC fails to reconfigure an RB through DRD and performs the rollback. This counter is measured in the target cell.
Measurement point
After the RNC receives an RADIO BEARER RECONFIGURATION FAILURE message in an RB reconfiguration DRD procedure, it sends an RADIO BEARER RECONFIGURATION message to a target cell if it determines that a rollback can be performed, as shown in point A of the figure. This counter is measured in the target cell when the RNC receives an RADIO BEARER RECONFIGURATION COMPLETE message from the UE. Figure 1-1008 RB Reconfiguration DRD
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RBRecfg.SuccEsta b.RollBack Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.32 Number of Physical Channel Reconfiguration Attempts After the Physical Channel Reconfiguration DRD Rollback Counters
Counter ID 73421491 Counter Name VS.DRD.PhyRecfg.AttEsta b.RollBack Counter Description Number of Physical Channel Reconfiguration Attempts After the Physical Channel Reconfiguration DRD Rollback
Description
This counter provides the number that the RNC attempts to perform physical channel reconfiguration in a cell after the physical channel reconfiguration through DRD fails and the RNC performs the rollback. This counter is measured in the target cell.
Measurement point
After the RNC receives a PHYSICAL CHANNEL RECONFIGURATION FAILURE message in a physical channel reconfiguration DRD procedure, it sends a PHYSICAL CHANNEL RECONFIGURATION message to a target cell if it determines that a rollback can be performed, as shown in point A of the figure. This counter is measured in the target cell when the RNC sends the PHYSICAL CHANNEL RECONFIGURATION message.
Issue 01 (2013-05-04)
2128
Figure 1-1009 Physical Channel Reconfiguration DRD
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.PhyRecfg.AttEsta b.RollBack Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.33 Number of Successful Physical Channel Reconfigurations After the Physical Channel Reconfiguration DRD Rollback
Issue 01 (2013-05-04)
2129
Counters
Counter ID 73421492 Counter Name VS.DRD.PhyRecfg.SuccEst ab.RollBack Counter Description Number of Successful Physical Channel Reconfigurations After the Physical Channel Reconfiguration DRD Rollback
Description
This counter provides the number that the physical channel reconfiguration succeeds in a cell after the RNC fails to reconfigure physical channels through DRD and performs the rollback. This counter is measured in the target cell.
Measurement point
After the RNC receives a PHYSICAL CHANNEL RECONFIGURATION FAILURE message in a physical channel reconfiguration DRD procedure, it sends a PHYSICAL CHANNEL RECONFIGURATION message to a target cell if it determines that a rollback can be performed, as shown in point A of the figure. This counter is measured in the target cell when the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE. Figure 1-1010 Physical Channel Reconfiguration DRD
Issue 01 (2013-05-04)
2130
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.PhyRecfg.SuccEst ab.RollBack Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.34.34 Number of Outgoing or Incoming FACH-to-HSDPA or FACH-HSUPA Directed Retry Attempts for Cell Counters
Counter ID 73421842 Counter Name VS.DRD.RB.F2H.AttOut Counter Description Number of Outgoing FACHto-HSDPA Directed Retry Attempts for Cell Number of Outgoing FACHto-HSUPA Directed Retry Attempts for Cell Number of Incoming FACHto-HSDPA Directed Retry Attempts for Cell Number of Incoming FACHto-HSUPA Directed Retry Attempts for Cell
73421844
VS.DRD.RB.F2E.AttOut
73421846
VS.DRD.RB.F2H.AttIn
73421848
VS.DRD.RB.F2E.AttIn
Description
These counters provide the number of outgoing or incoming FACH-to-HSDPA or FACHHSUPA directed retry attempts. The outgoing directed retry attempts are measured in the source cell of the directed retry, and the incoming directed retry attempts are measured in the target cell of the directed retry. For a DC-HSDPA or DC-HSUPA UE, these counters are measured only in the primary cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the UE a RADIO BEARER SETUP message, these counters are measured in the source or target cell
where the UE camps on if the message is for the FACH-to-HSDPA or FACH-to-HSUPA directed retry. Figure 1-1011 RB setup procedure
The measurement is triggered at point A as shown in the figure. When the RNC sends the UE a RADIO BEARER RECONFIGURATION message, these counters are measured in the source or target cell where the UE camps on if the message is for the FACH-to-HSDPA or FACH-toHSUPA directed retry.
Issue 01 (2013-05-04)
2132
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RB.F2H.AttOut Feature ID WRFD-01061112 WRFD-02040001 VS.DRD.RB.F2E.AttOut VS.DRD.RB.F2H.AttIn WRFD-02040001 WRFD-01061112 WRFD-02040001 VS.DRD.RB.F2E.AttIn WRFD-02040001 Feature Name HSDPA DRD Intra System Direct Retry Intra System Direct Retry HSDPA DRD Intra System Direct Retry Intra System Direct Retry
1.12.34.35 Number of Successful Outgoing or Incoming FACH-to-HSDPA or FACH-HSUPA Directed Retry Attempts for Cell
Counters
Counter ID 73421843 Counter Name VS.DRD.RB.F2H.SuccOut Counter Description Number of Successful Outgoing FACH-to-HSDPA Directed Retries for Cell Number of Successful Outgoing FACH-to-HSUPA Directed Retries for Cell Number of Successful Incoming FACH-to-HSDPA Directed Retries for Cell Number of Successful Incoming FACH-to-HSUPA Directed Retries for Cell
73421845
VS.DRD.RB.F2E.SuccOut
73421847
VS.DRD.RB.F2H.SuccIn
73421849
VS.DRD.RB.F2E.SuccIn
Description
These counters provide the number of successful outgoing FACH-to-HSDPA or FACH-toHSUPA directed retries in the source cell. The outgoing directed retry attempts are measured in the source cell of the directed retry, and the incoming directed retry attempts are measured in the target cell of the directed retry. For a DC-HSDPA or DC-HSUPA UE, these counters are measured only in the primary cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a RADIO BEARER SETUP COMPLETE message, these counters are measured in the source or target cell where the UE camps on if the message is for the FACH-to-HSDPA or FACH-to-HSUPA directed retry.
Issue 01 (2013-05-04)
2134
Figure 1-1013 RB setup procedure
The measurement is triggered at point B as shown in the figure. When the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message, these counters are measured in the source or target cell where the UE camps on if the message is for the FACHto-HSDPA or FACH-to-HSUPA directed retry. Figure 1-1014 RB reconfiguration procedure
Issue 01 (2013-05-04)
2135
Formula
None
Unit
None
Related Features
Counter Name VS.DRD.RB.F2H.SuccOut Feature ID WRFD-01061112 WRFD-02040001 VS.DRD.RB.F2E.SuccOut VS.DRD.RB.F2H.SuccIn WRFD-02040001 WRFD-01061112 WRFD-02040001 VS.DRD.RB.F2E.SuccIn WRFD-02040001 Feature Name HSDPA DRD Intra System Direct Retry Intra System Direct Retry HSDPA DRD Intra System Direct Retry Intra System Direct Retry
1.12.34.36 Number of CELL_FACH to CELL_PCH Transition Attempts by Physical Channel Reconfiguration for Cell Counters
Counter ID 73394177 Counter Name VS.AttPhyRecfg.F2P Counter Description Number of CELL_FACH to CELL_PCH Transition Attempts by Physical Channel Reconfiguration for Cell
Description
This counter provides the number of state transition attempts from CELL_FACH to CELL_PCH by physical channel reconfiguration in a cell.
Measurement point
The measurement is triggered at point A, as shown in the following figure. When the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to a UE, instructing the UE to transfer from the CELL_FACH state to the CELL_PCH state, this counter is incremented by one in the cell where the UE is camping.
Figure 1-1015 cd
Formula
None
Unit
None
Related Features
Counter Name VS.AttPhyRecfg.F2P Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.34.37 Number of SuccessfulCELL_FACH to CELL_PCH Transitions by Physical Channel Reconfiguration for Cell
Issue 01 (2013-05-04)
2137
Counters
Counter ID 73394178 Counter Name VS.SuccPhyRecfg.F2P Counter Description Number of Successful CELL_FACH to CELL_PCH Transitions by Physical Channel Reconfiguration for Cell
Description
This counter provides the number of successful state transitions from CELL_FACH to CELL_PCH by physical channel reconfiguration in a cell.
Measurement point
The measurement is triggered at point B, as shown in the following figure. When the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from a UE, indicating that the UE has transfered from the CELL_FACH state to the CELL_PCH state, this counter is incremented by one in the cell where the UE is camping. Figure 1-1016 physical channel reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.SuccPhyRecfg.F2P Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.34.38 Number of Outgoing or Incoming Inter-Frequency DRD Attempts Triggered by Multiband Directed Retry Based on UE Location for Cell Counters
Counter ID 73425827 Counter Name VS.UELocation.MultiBand. DRD.AttIn Counter Description Number of Incoming InterFrequency DRD Attempts Triggered by Multiband Direct Retry Based on UE Location for Cell Number of Outgoing InterFrequency DRD Attempts Triggered by Multiband Direct Retry Based on UE Location for Cell
73425836
VS.UELocation.MultiBand. DRD.AttOut
Description
These counters provide the number of outgoing or incoming inter-frequency directed retry attempts triggered by the Multiband Directed Retry Based on UE Location feature. The outgoing inter-frequency directed retry attempts are measured in the best cell where the UE camps on before the directed retry, and the incoming inter-frequency directed retry attempts are measured in the target cell of the directed retry.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends a RADIO BEARER SETUP message to the UE and a directed retry is triggered by the Multiband Directed Retry based on UE location, the number of outgoing inter-frequency directed retry attempts triggered by the Multiband Directed Retry based on UE location is measured in the best cell where the UE camps on before the directed retry, and the number of incoming inter-frequency directed retry attempts triggered by the Multiband Directed Retry based on UE location is measured in the target cell of the directed retry.
The measurement is triggered at point A as shown in the figure. When the RNC sends a RADIO BEARER RECONFIGURATION message to the UE and a directed retry is triggered by the Multiband Directed Retry based on UE location, the number of outgoing inter-frequency directed retry attempts triggered by the Multiband Directed Retry based on UE location is measured in the best cell where the UE camps on before the directed retry, and the number of incoming interfrequency directed retry attempts triggered by the Multiband Directed Retry based on UE location is measured in the target cell of the directed retry.
Issue 01 (2013-05-04)
2140
Formula
None
Unit
None
Related Features
Counter Name VS.UELocation.MultiBand. DRD.AttIn VS.UELocation.MultiBand. DRD.AttOut Feature ID WRFD-150232 WRFD-150232 Feature Name Multiband Direct Retry Based on UE Location Multiband Direct Retry Based on UE Location
1.12.34.39 Number of Successful Incoming Inter-Frequency DRDs Triggered by Multiband Directed Retry Based on UE Location for a Cell
Issue 01 (2013-05-04)
2141
Counters
Counter ID 73425835 Counter Name VS.UELocation.MultiBand. DRD.SuccIn Counter Description Number of Successful Incoming Inter-Frequency DRDs Triggered by Multiband Direct Retry Based on UE Location for Cell Number of Successful Outgoing Inter-Frequency DRDs Triggered by Multiband Direct Retry Based on UE Location for Cell
73425837
VS.UELocation.MultiBand. DRD.SuccOut
Description
These counters provide the number of successful outgoing or incoming inter-frequency directed retry attempts triggered by the Multiband Directed Retry Based on UE Location feature. The outgoing inter-frequency directed retry attempts are measured in the best cell where the UE camps on before the directed retry and the incoming inter-frequency directed retry attempts are measured in the target cell of the directed retry.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends a RADIO BEARER SETUP COMPLETE message to the UE and the directed retry is triggered by the Multiband Directed Retry based on UE location, the number of successful outgoing interfrequency directed retry attempts triggered by the Multiband Directed Retry based on UE location is measured in the best cell where the UE camps on before the directed retry, and the number of successful incoming inter-frequency directed retry attempts triggered by the Multiband Directed Retry based on UE location is measured in the target cell of the directed retry.
Issue 01 (2013-05-04)
2142
The measurement is triggered at point B as shown in the figure. When the RNC sends a RADIO BEARER RECONFIGURATION COMPLETE message to the UE and the directed retry is triggered by the Multiband Directed Retry based on UE location, the number of successful outgoing inter-frequency directed retry attempts triggered by the Multiband Directed Retry based on UE location is measured in the best cell where the UE camps on before the directed retry, and the number of successful incoming inter-frequency directed retry attempts triggered by the Multiband Directed Retry based on UE location is measured in the target cell of the directed retry.
Issue 01 (2013-05-04)
2143
Formula
None
Unit
None
Related Features
Counter Name VS.UELocation.MultiBand. DRD.SuccIn VS.UELocation.MultiBand. DRD.SuccOut Feature ID WRFD-150232 WRFD-150232 Feature Name Multiband Direct Retry Based on UE Location Multiband Direct Retry Based on UE Location
1.12.34.40 Number of Periodic Inter-Frequency Ingoing Directed Retry Attempts based on Measurement for Cell
Issue 01 (2013-05-04)
2144
Counters
Counter ID 73426249 Counter Name VS.MCDRD.Periodic.AttOut Counter Description Number of Periodic InterFrequency Outgoing Directed Retry Attempts based on Measurement for Cell Number of Periodic InterFrequency Ingoing Directed Retry Attempts based on Measurement for Cell
73426251
VS.MCDRD.Periodic.AttIn
Description
These counters provide the number of periodic inter-frequency outgoing or incoming directed retry attempts based on measurement. The outgoing inter-frequency directed retry attempts are measured in the best cell where the UE camps on before the directed retry, and the incoming inter-frequency directed retry attempts are measured in the target cell of the directed retry.
Measurement point
The measurement is triggered at point A as shown in Figure 1, when the RNC sends a RADIO BEARER RECONFIGURATION message to the UE. In this case, this counter measures the total number of periodic inter-frequency outgoing or incoming directed retries in the best cell where the UE camps on before the directed retry or the target cell of the directed retry when measurement-based periodic inter-frequency directed retry is enabled. Figure 1-1021 RB reconfiguration procedure
Issue 01 (2013-05-04)
2145
The measurement is triggered at point A as shown in Figure 2, when the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE. In this case, this counter measures the total number of periodic inter-frequency outgoing or incoming directed retries in the best cell where the UE camps on before the directed retry or the target cell of the directed retry when measurement-based periodic inter-frequency directed retry is enabled. Figure 1-1022 Physical Channel reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name VS.MCDRD.Periodic.AttOut Feature ID WRFD-02040004 WRFD-020160 Feature Name Traffic Steering and Load Sharing During RAB Setup Enhanced Multiband Management
Issue 01 (2013-05-04)
2146
Counter Name VS.MCDRD.Periodic.AttIn
Feature Name Traffic Steering and Load Sharing During RAB Setup Enhanced Multiband Management
1.12.34.41 Number of Successful Periodic Inter-Frequency Ingoing Directed Retry Attempts based on Measurement for Cell Counters
Counter ID 73426250 Counter Name VS.MCDRD.Periodic.SuccOut Counter Description Number of Successful Periodic Inter-Frequency Outgoing Directed Retries based on Measurement for Cell Number of Successful Periodic Inter-Frequency Ingoing Directed Retries based on Measurement for Cell
73426252
VS.MCDRD.Periodic.SuccIn
Description
These counters provide the number of successful periodic inter-frequency outgoing or incoming directed retry attempts based on measurement. The outgoing inter-frequency directed retry attempts are measured in the best cell where the UE camps on before the directed retry and the incoming inter-frequency directed retry attempts are measured in the target cell of the directed retry.
Measurement point
The measurement is triggered at point B as shown in Figure 1, when the RNC sends a RADIO BEARER RECONFIGURATION COMPLETE message to the UE. In this case, this counter measures the total number of successful periodic inter-frequency outgoing or incoming directed retries in the best cell where the UE camps on before the directed retry or the target cell of the directed retry when measurement-based periodic inter-frequency directed retry is enabled.
Issue 01 (2013-05-04)
2147
The measurement is triggered at point B as shown in Figure 2, when the RNC sends a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the UE. In this case, this counter measures the total number of successful periodic inter-frequency outgoing or incoming directed retries in the best cell where the UE camps on before the directed retry or the target cell of the directed retry when measurement-based periodic inter-frequency directed retry is enabled. Figure 1-1024 Physical Channel reconfiguration procedure
Issue 01 (2013-05-04)
2148
Formula
None
Unit
None
Related Features
Counter Name VS.MCDRD.Periodic.SuccOut Feature ID WRFD-02040004 WRFD-020160 Feature Name Traffic Steering and Load Sharing During RAB Setup Enhanced Multiband Management VS.MCDRD.Periodic.SuccIn WRFD-02040004 WRFD-020160 Traffic Steering and Load Sharing During RAB Setup Enhanced Multiband Management
1.12.35 Reserved counter for cell(RESERVE.Cell)

Overview
Reserved counter is used temporarily in patch versions and will be replaced with a new counter in later versions. For the detailed information about used reserved counters, see the "Used Reserved Counter List" of the corresponding version.
Counters
Counter ID 73423106 73423305 73423306 73423301 73423302 Counter Name VS.Reserve.Counter5 VS.Reserve.Counter8 VS.Reserve.Counter9 VS.Reserve.Counter10 VS.Reserve.Counter11 Counter Description Reserved counter 5 for cell Reserved counter 8 for cell Reserved counter 9 for cell Reserved counter 10 for cell Reserved counter 11 for cell Original Release V900R013 V900R013 V900R013 V900R013 V900R013
Issue 01 (2013-05-04)
2149
Counter ID 73423421 73423422 73423423 73423424 73423425 73423426 73423427 73423428 73423429 73423430 73423431 73423432 73423433 73423434 73423435 73423436 73423437 73423438
Counter Name VS.Reserve.Counter1 VS.Reserve.Counter2 VS.Reserve.Counter3 VS.Reserve.Counter4 VS.Reserve.Counter6 VS.Reserve.Counter7 VS.Reserve.Counter12 VS.Reserve.Counter13 VS.Reserve.Counter14 VS.Reserve.Counter15 VS.Reserve.Counter16 VS.Reserve.Counter17 VS.Reserve.Counter18 VS.Reserve.Counter19 VS.Reserve.Counter20 VS.Reserve.Counter21 VS.Reserve.Counter22 VS.Reserve.Counter23
Counter Description Reserved counter 1 for cell Reserved counter 2 for cell Reserved counter 3 for cell Reserved counter 4 for cell Reserved counter 6 for cell Reserved counter 7 for cell Reserved counter 12 for cell Reserved counter 13 for cell Reserved counter 14 for cell Reserved counter 15 for cell Reserved counter 16 for cell Reserved counter 17 for cell Reserved counter 18 for cell Reserved counter 19 for cell Reserved counter 20 for cell Reserved counter 21 for cell Reserved counter 22 for cell Reserved counter 23 for cell
Original Release V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013
Issue 01 (2013-05-04)
2150
Counter ID 73423439 73423440 73423441 73423442 73423443 73423444 73423445
Counter Name VS.Reserve.Counter24 VS.Reserve.Counter25 VS.Reserve.Counter26 VS.Reserve.Counter27 VS.Reserve.Counter28 VS.Reserve.Counter29 VS.Reserve.Counter30
Counter Description Reserved counter 24 for cell Reserved counter 25 for cell Reserved counter 26 for cell Reserved counter 27 for cell Reserved counter 28 for cell Reserved counter 29 for cell Reserved counter 30 for cell
Original Release V900R013 V900R013 V900R013 V900R013 V900R013 V900R013 V900R013
None
1.12.35.1 Reserved counters for cell Counters

Counter ID 73423421 73423106 73423305 73423306 73423301 73423302 73423422 73423423 73423424 73423425 73423426
Issue 01 (2013-05-04)
Counter Name VS.Reserve.Counter1 VS.Reserve.Counter5 VS.Reserve.Counter8 VS.Reserve.Counter9 VS.Reserve.Counter10 VS.Reserve.Counter11 VS.Reserve.Counter2 VS.Reserve.Counter3 VS.Reserve.Counter4 VS.Reserve.Counter6 VS.Reserve.Counter7
Counter Description Reserved counter 1 for cell Reserved counter 5 for cell Reserved counter 8 for cell Reserved counter 9 for cell Reserved counter 10 for cell Reserved counter 11 for cell Reserved counter 2 for cell Reserved counter 3 for cell Reserved counter 4 for cell Reserved counter 6 for cell Reserved counter 7 for cell
2151
Counter ID 73423427 73423428 73423429 73423430 73423431 73423432 73423433 73423434 73423435 73423436 73423437 73423438 73423439 73423440 73423441 73423442 73423443 73423444 73423445
Counter Name VS.Reserve.Counter12 VS.Reserve.Counter13 VS.Reserve.Counter14 VS.Reserve.Counter15 VS.Reserve.Counter16 VS.Reserve.Counter17 VS.Reserve.Counter18 VS.Reserve.Counter19 VS.Reserve.Counter20 VS.Reserve.Counter21 VS.Reserve.Counter22 VS.Reserve.Counter23 VS.Reserve.Counter24 VS.Reserve.Counter25 VS.Reserve.Counter26 VS.Reserve.Counter27 VS.Reserve.Counter28 VS.Reserve.Counter29 VS.Reserve.Counter30
Counter Description Reserved counter 12 for cell Reserved counter 13 for cell Reserved counter 14 for cell Reserved counter 15 for cell Reserved counter 16 for cell Reserved counter 17 for cell Reserved counter 18 for cell Reserved counter 19 for cell Reserved counter 20 for cell Reserved counter 21 for cell Reserved counter 22 for cell Reserved counter 23 for cell Reserved counter 24 for cell Reserved counter 25 for cell Reserved counter 26 for cell Reserved counter 27 for cell Reserved counter 28 for cell Reserved counter 29 for cell Reserved counter 30 for cell
Description
Reserved counters for cell.
Measurement point
Reserved counters for cell.
Formula
None
Unit
None
Related Features
None
1.12.36 Measurement related to RLC per cell(RLC.Cell)

Overview
Radio Link Control (RLC) measurement in a cell is to measure the number of RLC PDUs sent, retransmitted and discarded in a cell. These RLC PDUs include traffic RLC PDUs and signaling RLC PDUs.
Counters
Counter ID 67204177 Counter Name VS.RLC.AM.Rtx.T rf.PDU.1 Counter Description Number of Downlink Service PDUs Retransmitted on AM RLC that Are Smaller than 34% of the Maximum RLC PDU Size for Cell Number of Downlink Service PDUs Retransmitted on AM RLC that Are Between 34% and 66% of the Maximum PDU Size for Cell Number of Downlink Service PDUs Retransmitted on AM RLC that Are Greater than 66% of the Maximum RLC PDU Size for Cell Number of HSDPA Downlink Service PDUs Sent on AM RLC for Cell Number of R99 Downlink Service PDUs Sent on AM RLC for Cell Original Release Earlier than V900R011
67204178
VS.RLC.AM.Rtx.T rf.PDU.2
67204179
VS.RLC.AM.Rtx.T rf.PDU.3
67204860
VS.RLC.AM.Tx.Hs dpaTrf.PDU
67204806
VS.RLC.AM.Tx.R 99Trf.PDU
Issue 01 (2013-05-04)
2153
Counter ID 67204861
Counter Name VS.AM.RLC.Tx.Hs dpaSig.PDU
Counter Description Number of HSDPA Downlink Signaling PDUs Sent on AM RLC for Cell Number of R99 Downlink Signaling PDUs Sent on AM RLC for Cell Number of HSDPA Downlink Service PDUs Retransmitted on AM RLC for Cell Number of R99 Downlink Service PDUs Retransmitted on AM RLC for Cell Number of HSDPA Downlink Signaling PDUs Retransmitted on AM RLC for Cell Number of R99 Downlink Signaling PDUs Retransmitted on AM RLC for Cell Number of HSDPA Downlink Service PDUs Discarded on AM RLC for Cell Number of R99 Downlink Service PDUs Discarded on AM RLC for Cell Number of HSDPA Downlink Signaling PDUs Discarded on AM RLC for Cell Number of R99 Downlink Signaling PDUs Discarded on AM RLC for Cell
67204807
VS.AM.RLC.Tx.R 99Sig.PDU
67204808
VS.AM.RLC.Rtx.H sdpaTrf.PDU
67204809
VS.AM.RLC.Rtx.R 99Trf.PDU
67204862
VS.AM.RLC.Rtx.H sdpaSig.PDU
67204812
VS.AM.RLC.Rtx.R 99Sig.PDU
67204863
VS.RLC.AM.Disc. HsdpaTrfPDU
67204810
VS.RLC.AM.Disc. R99TrfPDU
67204864
VS.RLC.AM.Disc. HsdpaSig.PDU
67204811
VS.RLC.AM.Disc. R99Sig.PDU
Issue 01 (2013-05-04)
2154
None
1.12.36.1 Number of Downlink Service PDUs Retransmitted on AM RLC (L2 Enhancement) Counters
Counter ID 67204177 Counter Name VS.RLC.AM.Rtx.Trf.PDU.1 Counter Description Number of Downlink Service PDUs Retransmitted on AM RLC that Are Smaller than 34% of the Maximum RLC PDU Size for Cell Number of Downlink Service PDUs Retransmitted on AM RLC that Are Between 34% and 66% of the Maximum PDU Size for Cell Number of Downlink Service PDUs Retransmitted on AM RLC that Are Greater than 66% of the Maximum RLC PDU Size for Cell
67204178
VS.RLC.AM.Rtx.Trf.PDU.2
67204179
VS.RLC.AM.Rtx.Trf.PDU.3
Description
These counters provide the number of downlink PDUs that are retransmitted by the RLC in AM mode in a HSDPA cell enabled with the enhanced L2 feature. The number of PDUs is provided on a size basis. In addition, these counters exclude the number of downlink PDUs that are automatically retransmitted by the RLC.
Measurement point
When the AM RLC is configured with the DL L2 enhancement and a PDU is retransmitted, the RNC measures the corresponding counter based on the comparison of the actual retransmitted PDU size with the maximum PDU size.
Formula
None
Unit
packet
Related Features
Counter Name VS.RLC.AM.Rtx.Trf.PDU.1 VS.RLC.AM.Rtx.Trf.PDU.2 VS.RLC.AM.Rtx.Trf.PDU.3 Feature ID WRFD-010685 WRFD-010685 WRFD-010685 Feature Name Downlink Enhanced L2 Downlink Enhanced L2 Downlink Enhanced L2
1.12.36.2 Number of Downlink Service PDUs Sent on AM RLC Counters

Counter ID 67204860 Counter Name VS.RLC.AM.Tx.HsdpaTrf. PDU VS.RLC.AM.Tx.R99Trf.PD U Counter Description Number of HSDPA Downlink Service PDUs Sent on AM RLC for Cell Number of R99 Downlink Service PDUs Sent on AM RLC for Cell
67204806
Description
These counters provide the number of downlink service PDUs that are sent on the AM RLC for different types of service. Retransmitted PDUs are not included. Number of HSDPA Service PDUs Sent on AM RLC for Cell is measured for the HSDPA serving cell, and the counter Number of R99 Service PDUs Sent on AM RLC for Cell is measured for cells in the active set.
Measurement point
The measurement is triggered when a downlink service PDU is sent on the AM RLC.
Formula
None
Unit
packet
Issue 01 (2013-05-04)
2156
Related Features
Counter Name VS.RLC.AM.Tx.HsdpaTrf. PDU Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RLC.AM.Tx.R99Trf.PD U
WRFD-010510
1.12.36.3 Number of Downlink Signaling PDUs Sent on AM RLC Counters

Counter ID 67204861 Counter Name VS.AM.RLC.Tx.HsdpaSig. PDU VS.AM.RLC.Tx.R99Sig.PD U Counter Description Number of HSDPA Downlink Signaling PDUs Sent on AM RLC for Cell Number of R99 Downlink Signaling PDUs Sent on AM RLC for Cell
67204807
Description
These counters provide the number of downlink signaling PDUs that are sent on the AM RLC. Retransmitted PDUs are not included. The counter Number of HSDPA Signaling PDUs Sent on AM RLC for Cell is measured for the HSDPA serving cell, and the counter Number of R99 Signaling PDUs Sent on AM RLC for Cell is measured for cells in the active set.
Measurement point
The measurement is triggered when a downlink signaling PDU is sent on the AM RLC.
Formula
None
Unit
packet
Related Features
Counter Name VS.AM.RLC.Tx.HsdpaSig. PDU Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.AM.RLC.Tx.R99Sig.PD U
WRFD-010510
1.12.36.4 Number of Downlink Service PDUs Retransmitted on AM RLC Counters

Counter ID 67204808 Counter Name VS.AM.RLC.Rtx.HsdpaTrf. PDU Counter Description Number of HSDPA Downlink Service PDUs Retransmitted on AM RLC for Cell Number of R99 Downlink Service PDUs Retransmitted on AM RLC for Cell
67204809
VS.AM.RLC.Rtx.R99Trf.P DU
Description
These counters provide the number of downlink service PDUs that are retransmitted on the AM RLC. PDUs that are retransmitted by the RNC actively are not included. The counter Number of DL HSDPA Service PDUs Retransmitted on AM RLC for Cell is measured for the HSDPA serving cell, and the counter Number of DL R99 Service PDUs Retransmitted on AM RLC for Cell is measured for cells in the active set.
Measurement point
The measurement is triggered when a downlink service PDU is retransmitted on the AM RLC.
Formula
None
Unit
packet
Related Features
Counter Name VS.AM.RLC.Rtx.HsdpaTrf. PDU Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.AM.RLC.Rtx.R99Trf.P DU
WRFD-010510
1.12.36.5 Number of Downlink Signaling PDUs Retransmitted on AM RLC Counters

Counter ID 67204862 Counter Name VS.AM.RLC.Rtx.HsdpaSig. PDU Counter Description Number of HSDPA Downlink Signaling PDUs Retransmitted on AM RLC for Cell Number of R99 Downlink Signaling PDUs Retransmitted on AM RLC for Cell
67204812
VS.AM.RLC.Rtx.R99Sig.P DU
Description
These counters provide the number of downlink signaling PDUs that are retransmitted on the AM RLC. PDUs that are retransmitted by the RNC actively are not included. The Number of DL HSDPA Signaling PDUs Retransmitted on AM RLC for Cell is measured for the HSDPA serving cell, and the Number of DL R99 Signaling PDUs Retransmitted on AM RLC for Cell is measured for cells in the active set.
Measurement point
The measurement is triggered when a downlink signaling PDU is retransmitted on the AM RLC.
Formula
None
Unit
packet
Related Features
Counter Name VS.AM.RLC.Rtx.HsdpaSig. PDU Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.AM.RLC.Rtx.R99Sig.P DU
WRFD-010510
1.12.36.6 Number of Downlink Service PDUs Discarded on AM RLC Counters

Counter ID 67204863 Counter Name VS.RLC.AM.Disc.HsdpaTrf PDU Counter Description Number of HSDPA Downlink Service PDUs Discarded on AM RLC for Cell Number of R99 Downlink Service PDUs Discarded on AM RLC for Cell
67204810
VS.RLC.AM.Disc.R99TrfP DU
Description
These counters provide the number of downlink service PDUs that are discarded on the AM RLC. The counter Number of DL HSDPA Service PDUs Discarded on AM RLC for Cell is measured for the HSDPA serving cell, and the counter Number of DL R99 Service PDUs Discarded on AM RLC for Cell is measured for cells in the active set.
Measurement point
The measurement is triggered when a downlink service PDU is discarded on the AM RLC.
Formula
None
Unit
packet
Related Features
Counter Name VS.RLC.AM.Disc.HsdpaTrf PDU Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RLC.AM.Disc.R99TrfP DU
WRFD-010510
1.12.36.7 Number of Downlink Signaling PDUs Discarded on AM RLC Counters

Counter ID 67204864 Counter Name VS.RLC.AM.Disc.HsdpaSig .PDU Counter Description Number of HSDPA Downlink Signaling PDUs Discarded on AM RLC for Cell Number of R99 Downlink Signaling PDUs Discarded on AM RLC for Cell
67204811
VS.RLC.AM.Disc.R99Sig.P DU
Description
These counters provide the number of downlink signaling PDUs that are discarded on the AM RLC. The Number of DL HSDPA Signaling PDUs Discarded on AM RLC for Cell is measured for the HSDPA serving cell, and the Number of DL R99 Signaling PDUs Discarded on AM RLC for Cell is measured for cells in the active set.
Measurement point
The measurement is triggered when a downlink signaling PDU is discarded on the AM RLC.
Formula
None
Unit
packet
Related Features
Counter Name VS.RLC.AM.Disc.HsdpaSig .PDU Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RLC.AM.Disc.R99Sig.P DU
WRFD-010510
1.12.37 RRC connection release measurement per cell (RRC.Rel.Cell)

Overview
When the RNC releases a RRC connection, it sends a RRC CONNECTION RELEASE message to the UE to release the resources occupied by the UE. RRC connection release measurement provides the number of RRC connection release messages with different causes in a specified cell.
Counters
Counter ID 67189459 Counter Name RRC.AttConnRelD CCH.Cong Counter Description Number of RRC Connection Releases on DCCH due to Congestion for Cell Number of RRC Connection Releases on DCCH due to Preemption for Cell Number of RRC Connection Releases on DCCH due to Reestablishment Reject for Cell Original Release Earlier than V900R011
67189460
RRC.AttConnRelD CCH.Preempt
67189461
RRC.AttConnRelD CCH.ReEstRej
Issue 01 (2013-05-04)
2162
Counter ID 67189462
Counter Name RRC.AttConnRelD CCH.DSCR
Counter Description Number of RRC Connection Releases on DCCH due to Directed Signaling Connection Reestablishment for Cell Number of RRC Connection Releases on DCCH due to User Inactivity for Cell Number of RRC Connection Releases on DCCH due to Unspecified Causes for Cell Number of RRC Connection Releases on CCCH due to Congestion for Cell Number of RRC Connection Releases on CCCH due to Preemption for Cell Number of RRC Connection Releases on CCCH due to Reestablishment Reject for Cell Number of RRC Connection Releases on CCCH due to Directed Signaling Connection Reestablishment for Cell Number of RRC Connection Releases on DCCH due to Normal Event for Cell
67189463
RRC.AttConnRelD CCH.UsrInact
67189464
RRC.AttConnRelD CCH.Unspec
67189465
RRC.AttConnRelC CCH.Cong
67189466
RRC.AttConnRelC CCH.Preempt
67189467
RRC.AttConnRelC CCH.ReEstRej
67189468
RRC.AttConnRelC CCH.DSCR
67189469
RRC.AttConnRelD CCH.Norm
Issue 01 (2013-05-04)
2163
Counter ID 67189470
Counter Name RRC.AttConnRelC CCH.Norm
Counter Description Number of RRC Connection Releases on CCCH due to Normal Event for Cell Number of RRC Connection Releases on CCCH due to User Inactivity for Cell Number of RRC Connection Releases on CCCH due to Unspecified Causes for Cell Number of RRC Connection Releases due to Cell Update Failure in the Case of RL Failure for Cell Number of RRCs Release Due to Receiving SIGNALLING CONNECTION RELEASE INDICATION message with cause of "UE Requested PS Data session end" for cell
67189471
RRC.AttConnRelC CCH.UsrInact
67189472
RRC.AttConnRelC CCH.Unspec
67180387
VS.RRC.ConnRel. CellUpd
73391137
VS.RRC.SigConnR elInd.UEPSDataEnd
V900R012
None
1.12.37.1 Counters Related to the Number of RRC Connection Releases on DCCH due to Different Causes
Issue 01 (2013-05-04)
2164
Counters
Counter ID 67189469 Counter Name RRC.AttConnRelDCCH.No rm RRC.AttConnRelDCCH.Co ng RRC.AttConnRelDCCH.Pre empt RRC.AttConnRelDCCH.ReEstRej Counter Description Number of RRC Connection Releases on DCCH due to Normal Event for Cell Number of RRC Connection Releases on DCCH due to Congestion for Cell Number of RRC Connection Releases on DCCH due to Preemption for Cell Number of RRC Connection Releases on DCCH due to Re-establishment Reject for Cell Number of RRC Connection Releases on DCCH due to Directed Signaling Connection Reestablishment for Cell Number of RRC Connection Releases on DCCH due to User Inactivity for Cell Number of RRC Connection Releases on DCCH due to Unspecified Causes for Cell
67189459
67189460
67189461
67189462
RRC.AttConnRelDCCH.DS CR
67189463
RRC.AttConnRelDCCH.UsrInact RRC.AttConnRelDCCH.Un spec
67189464
Description
These counters provide the number of RRC CONNECTION RELEASE messages with different causes on DCCH sent by the RNC to the UE in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends a RRC CONNECTION RELEASE message with a certain cause to the UE to release a RRC connection, the corresponding counter is measured in the best cell that the UE camps on. For details on the different causes, see section 10.3.3.32 in 3GPP TS 25.331.
Issue 01 (2013-05-04)
2165
Figure 1-1025 RRC connection release procedure on the DCCH
Formula
None
Unit
None
Related Features
Counter Name RRC.AttConnRelDCCH.No rm Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Queuing and Pre-Emption 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
RRC.AttConnRelDCCH.Co ng
WRFD-010510
RRC.AttConnRelDCCH.Pre empt
WRFD-010505 WRFD-010510
RRC.AttConnRelDCCH.ReEstRej
WRFD-010510
Issue 01 (2013-05-04)
2166
Counter Name RRC.AttConnRelDCCH.DS CR
Feature Name Direct Signaling Connection Re-establishment (DSCR) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
RRC.AttConnRelDCCH.UsrInact
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
RRC.AttConnRelDCCH.Un spec
WRFD-010510
1.12.37.2 Counters Related to the Number of RRC Connection Releases on CCCH due to Different Causes Counters
Counter ID 67189470 Counter Name RRC.AttConnRelCCCH.No rm RRC.AttConnRelCCCH.Co ng RRC.AttConnRelCCCH.Pre empt RRC.AttConnRelCCCH.ReEstRej Counter Description Number of RRC Connection Releases on CCCH due to Normal Event for Cell Number of RRC Connection Releases on CCCH due to Congestion for Cell Number of RRC Connection Releases on CCCH due to Preemption for Cell Number of RRC Connection Releases on CCCH due to Re-establishment Reject for Cell Number of RRC Connection Releases on CCCH due to Directed Signaling Connection Reestablishment for Cell
67189465
67189466
67189467
67189468
RRC.AttConnRelCCCH.DS CR
Issue 01 (2013-05-04)
2167
Counter ID 67189471
Counter Name RRC.AttConnRelCCCH.UsrInact RRC.AttConnRelCCCH.Un spec
Counter Description Number of RRC Connection Releases on CCCH due to User Inactivity for Cell Number of RRC Connection Releases on CCCH due to Unspecified Causes for Cell
67189472
Description
These counters provide the number of RRC CONNECTION RELEASE messages with different causes on CCCH sent by the RNC to the UE.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends a RRC CONNECTION RELEASE message with a certain cause to the UE to release a RRC connection, the corresponding counter is measured in the cell that the UE camps on. For details on the different causes, see section 10.3.3.32 in 3GPP TS 25.331. Figure 1-1026 RRC connection release procedure on the CCCH
Issue 01 (2013-05-04)
2168
Formula
None
Unit
None
Related Features
Counter Name RRC.AttConnRelCCCH.No rm Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Queuing and Pre-Emption 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Direct Signaling Connection Re-establishment (DSCR) 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release RRC.AttConnRelCCCH.UsrInact WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
RRC.AttConnRelCCCH.Co ng
WRFD-010510
RRC.AttConnRelCCCH.Pre empt
WRFD-010505 WRFD-010510
RRC.AttConnRelCCCH.ReEstRej
WRFD-010510
RRC.AttConnRelCCCH.DS CR
WRFD-021400 WRFD-010510
RRC.AttConnRelCCCH.Un spec
WRFD-010510
Issue 01 (2013-05-04)
2169
1.12.37.3 Number of RRC Connection Releases due to Cell Update Failure in the Case of RL Failure Counters
Counter ID 67180387 Counter Name VS.RRC.ConnRel.CellUpd Counter Description Number of RRC Connection Releases due to Cell Update Failure in the Case of RL Failure for Cell
Description
This counter provides the number of RRC connection releases due to cell update failure in the case of radio link failure.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC fails in the cell update due to radio link failure, it sends the UE a RRC CONNECTION RELEASE message. In this case, this counter is measured in the target cell during cell update. Figure 1-1027 RRC connection release caused by cell update failure
Issue 01 (2013-05-04)
2170
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.ConnRel.CellUpd Feature ID WRFD-010510 WRFD-010801 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Intra RNC Cell Update
1.12.37.4 Number of RRCs Released due to PS Data session end Counters

Counter ID 73391137 Counter Name VS.RRC.SigConnRelInd.U EPSDataEnd Counter Description Number of RRCs Release Due to Receiving SIGNALLING CONNECTION RELEASE INDICATION message with cause of "UE Requested PS Data session end" for cell
Description
The measurement item takes statistics of the number of RRCs Released due to Receiving SIGNALLING CONNECTION RELEASE INDICATION message with cause of "UE Requested PS Data session end" in the best cell which the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the figure.After the UE checks that no PS data is transmitted, it sends to the RNC the SIGNALLING CONNECTION RELEASE INDICATION message with the cause value "UE Requested PS Data session end". This counter measures the numbers of RRCs Release on this situation.
Figure 1-1028 UL SIG connection release procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.SigConnRelInd.U EPSDataEnd Feature ID WRFD-020500 Feature Name Enhanced Fast Dormancy
1.12.38 RRC connection setup measurement per cell (RRC.Setup.Cell)

Overview
When an UE needs to access the network, setting up the RRC connection is the first step. From the cell where the UE is located, the UE sends a RRC CONNECTION REQUEST message to request network access. After receiving the RRC CONNECTION REQUEST message, the RNC initiates the admission procedure and allocates relevant resources to the UE. Following successful allocation of resources, the RNC sends a RRC CONNECTION SETUP message to the UE and waits for a RRC CONNECTION SETUP COMPLETE message, a response message from the UE. When
the RNC receives a RRC CONNECTION SETUP COMPLETE message, the procedure for RRC connection setup is finished. For more details, see 3GPP TS 25.331. The number of RRC connection setup attempts and rejects does not include service-based redirections, inter-RAT and inter-frequency distance-based redirections, and macro & micro joint inter-frequency redirections. During the resource admission and radio link setup process, if DRD is configured when resource admission and radio link setup fail and the configured DRD succeeds, the measurement is triggered in the target cell for the UE. If the configured DRD fails, the measurement is triggered in the source cell for the UE. Note that the measurement is not triggered for RRC CONNECTION REQUEST messages retransmitted by the UE. The following figure shows the measurement points of the counters.
Issue 01 (2013-05-04)
2173
Issue 01 (2013-05-04)
2174
Table 1 describes the measurement points shown in Figure1. Measurement points A B C D E~L Description VS.RRC.AttConnEstab.Sum VS.RRC.SetupConnEstab RRC.SuccConnEstab.sum VS.RRC.Estab.DRDOut.Att See:RRC.SetupFail.Cell
Counters
Counter ID 67189400 Counter Name VS.RRC.Estab.DR DOut.Att Counter Description Number of RRC Connection Setup Attempts with DRD out for Cell Number of Successful RRC Connection Setups with DRD out for Cell Number of RRC Connection Setup Attempts with DRD in for Cell Maximum Duration of RRC Connection Setup for Cell (UE Target State on CELL_DCH) Average Duration of RRC Connection Setup for Cell (UE Target State on CELL_DCH) Number of RRC Connection Requests for Cell (Originating Conversational Call) Original Release Earlier than V900R011
67189401
VS.RRC.Estab.DR DOut.Succ
67192607
VS.RRC.Estab.DR DIn
67179302
VS.RRC.ConnEsta bTimeMax.CellDC H
67199510
VS.RRC.ConnEsta bTimeMean.CellD CH
67179329
RRC.AttConnEsta b.OrgConvCall
Issue 01 (2013-05-04)
2175
Counter ID 67179330
Counter Name RRC.AttConnEsta b.OrgStrCall
Counter Description Number of RRC Connection Requests for Cell (Originating Streaming Call) Number of RRC Connection Requests for Cell (Originating Interactive Call) Number of RRC Connection Requests for Cell (Originating Background Call) Number of RRC Connection Requests for Cell (Terminating Conversational Call) Number of RRC Connection Requests for Cell (Terminating Streaming Call) Number of RRC Connection Requests for Cell (Terminating Interactive Call) Number of RRC Connection Requests for Cell (Terminating Background Call) Number of Successful RRC Connection Setups for Cell (Originating Conversational Call) Number of Successful RRC Connection Setups for Cell (Originating Streaming Call) Number of Successful RRC Connection Setups for Cell (Originating Interactive Call)
67179331
RRC.AttConnEsta b.OrgInterCall
67179332
RRC.AttConnEsta b.OrgBkgCall
67179334
RRC.AttConnEsta b.TmConvCall
67179335
RRC.AttConnEsta b.TmStrCall
67179336
RRC.AttConnEsta b.TmInterCall
67179337
RRC.AttConnEsta b.TmBkgCall
67179457
RRC.SuccConnEst ab.OrgConvCall
67179458
RRC.SuccConnEst ab.OrgStrCall
67179459
RRC.SuccConnEst ab.OrgInterCall
Issue 01 (2013-05-04)
2176
Counter ID 67179460
Counter Name RRC.SuccConnEst ab.OrgBkgCall
Counter Description Number of Successful RRC Connection Setups for Cell (Originating Background Call) Number of Successful RRC Connection Setups for Cell (Originating Subscribed traffic Call) Number of Successful RRC Connection Setups for Cell (Terminating Conversational Call) Number of Successful RRC Connection Setups for Cell (Terminating Streaming Call) Number of Successful RRC Connection Setups for Cell (Terminating Interactive Call) Number of Successful RRC Connection Setups for Cell (Terminating Background Call) Number of RRC Connection Setup Messages from RNC to UE for Cell Number of Successful RRC Connection Setups for Cell Number of RRC Connection Requests for Cell (Originating Subscribed Traffic Call)
67179461
RRC.SuccConnEst ab.OrgSubCall
67179462
RRC.SuccConnEst ab.TmConvCall
67179463
RRC.SuccConnEst ab.TmStrCall
67179464
RRC.SuccConnEst ab.TmItrCall
67179465
RRC.SuccConnEst ab.TmBkgCall
67179298
VS.RRC.SetupCon nEstab
67179299
RRC.SuccConnEst ab.sum
67179333
RRC.AttConnEsta b.OrgSubCall
Issue 01 (2013-05-04)
2177
Counter ID 67179338
Counter Name RRC.AttConnEsta b.EmgCall
Counter Description Number of RRC Connection Requests for Cell (Emergency Call) Number of RRC Connection Requests for Cell (Inter-RAT Cell Re-Selection) Number of RRC Connection Requests for Cell (Inter-RAT Cell Change Order) Number of RRC Connection Requests for Cell (Registration) Number of RRC Connection Requests for Cell (Detach) Number of RRC Connection Requests for Cell (Originating High Priority Signaling) Number of RRC Connection Requests for Cell (Originating Low Priority Signaling) Number of RRC Connection Requests for Cell (Call ReEstablishment) Number of RRC Connection Requests for Cell (Terminating High Priority Signaling) Number of RRC Connection Requests for Cell (Terminating Low Priority Signaling)
67179339
RRC.AttConnEsta b.IRATCelRes
67179340
RRC.AttConnEsta b.IRATCCO
67179341
RRC.AttConnEsta b.Reg
67179342
RRC.AttConnEsta b.Detach RRC.AttConnEsta b.OrgHhPrSig
67179343
67179344
RRC.AttConnEsta b.OrgLwPrSig
67179345
RRC.AttConnEsta b.CallReEst
67179346
RRC.AttConnEsta b.TmHhPrSig
67179347
RRC.AttConnEsta b.TmLwPrSig
Issue 01 (2013-05-04)
2178
Counter ID 67179348
Counter Name RRC.AttConnEsta b.Unknown
Counter Description Number of RRC Connection Requests for Cell (Terminating-Cause Unknown) Number of Successful RRC Connection Setups for Cell (Inter-RAT Cell Re-Selection) Number of Successful RRC Connection Setups for Cell (Inter-RAT Cell Change Order) Number of Successful RRC Connection Setups for Cell (Registration) Number of Successful RRC Connection Setups for Cell (Detach) Number of Successful RRC Connection Setups for Cell (Originating High Priority Signaling) Number of Successful RRC Connection Setups for Cell (Originating Low Priority Signaling) Number of Successful RRC Connection Setups for Cell (Call ReEstablishment)
67179467
RRC.SuccConnEst ab.IRATCelRes
67179468
RRC.SuccConnEst ab.IRATCCO
67179469
RRC.SuccConnEst ab.Reg
67179470
RRC.SuccConnEst ab.Detach
67179471
RRC.SuccConnEst ab.OrgHhPrSig
67179472
RRC.SuccConnEst ab.OrgLwPrSig
67179473
RRC.SuccConnEst ab.CallReEst
Issue 01 (2013-05-04)
2179
Counter ID 67179474
Counter Name RRC.SuccConnEst ab.TmHhPrSig
Counter Description Number of Successful RRC Connection Setups for Cell (Terminating High Priority Signaling) Number of Successful RRC Connection Setups for Cell (Terminating Low Priority Signaling) Number of Successful RRC Connection Setups for Cell (Terminating-Cause Unknown) Number of RRC Connection Requests for Cell (UE Target State of CELL_DCH) Number of Successful RRC Connection Setups for Cell (UE Target State of CELL_DCH) Number of RRC Connection Requests for Cell (UE Target State of CELL_FACH) Number of Successful RRC Connection Setups for Cell (UE Target State of CELL_FACH) Number of Successful RRC Connection Setups for Cell (Emergency Call)
67179475
RRC.SuccConnEst ab.TmLwPrSig
67179476
RRC.SuccConnEst ab.Unkown
67179633
VS.RRC.AttConnE stab.CellDCH
67179634
VS.RRC.SuccConn Estab.CellDCH
67179649
VS.RRC.AttConnE stab.CellFACH
67179650
VS.RRC.SuccConn Estab.CellFACH
67179466
RRC.SuccConnEst ab.EmgCall
Issue 01 (2013-05-04)
2180
Counter ID 67190586
Counter Name VS.RRC.AttConnE stab.Sum VS.RRC.SuccConn Estab.First
Counter Description Number of Processed RRC Connection Requests for Cell Number of Successful RRC Connection Setups with One RRC Connection Request Message from UE for Cell Number of Successful RRC Connection Setups with Two RRC Connection Request Messages from UE for Cell Number of Successful RRC Connection Setups with Three RRC Connection Request Messages from UE for Cell Number of Automatic DSACs Triggered by Congestion on Iu Interface for Cell Number of RRC Connection Requests for Cell (MBMS Reception) Number of RRC Connection Requests for Cell (MBMS PTP RB Request) Number of Successful RRC Connection Setups for Cell (MBMS Reception)
67190587
67190588
VS.RRC.SuccConn Estab.Second
67190589
VS.RRC.SuccConn Estab.Third
67195590
VS.RRC.AutoDsac. Num
67195964
RRC.AttConnEsta b.MBMSRep
67195965
RRC.AttConnEsta b.MBMSPtp
67195966
RRC.SuccConnEst ab.MBMSRep
Issue 01 (2013-05-04)
2181
Counter ID 67195967
Counter Name RRC.SuccConnEst ab.MBMSPtp
Counter Description Number of Successful RRC Connection Setups for Cell (MBMS PTP RB Request) Number of RRC Connection Attempts for UL Carried on E_DCH for Cell Number of RRC Connection Attempts for DL Carried on HS_DSCH for Cell Number of Successful RRC Connection Setups for Cell (UL Carried on E_DCH) Number of Successful RRC Connection Setups for Cell (DL Carried on HS_DSCH) Number of RRC Connection Requests sent by the UE for cell Number of PTT UEs in Cell with RRC Connection State of CELL_FACH Number of PTT UEs in Cell with RRC Connection State of CELL_DCH Maximum Duration of RRC Establishment Process on FACH for Cell
67196198
VS.RRC.AttConnE stab.EDCH
67196199
VS.RRC.AttConnE stab.HSDSCH
67196200
VS.RRC.SuccConn Estab.EDCH
67196201
VS.RRC.SuccConn Estab.HSDSCH
73403798
VS.RRC.AttConnE stab.Msg
V900R012
73410489
VS.CellFACHUEs. PTT
V900R012
73410490
VS.CellDCHUEs.P TT
V900R012
73421887
VS.RRC.ConnEsta bTimeMax.CellFACH
Issue 01 (2013-05-04)
2182
Counter ID 73439969
Counter Name VS.RRC.ConnEsta bTimeMean.CellFACH VS.CellPCHUEs.P TT
Counter Description Mean Duration of RRC Establishment Process on FACH for Cell Number of PTT UEs with RRC Connection State of CELL_PCH for Cell Number of Retransmitted RRC Connection Setup Requests for Cell (Originating Conversational Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Originating Streaming Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Originating Interactive Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Originating Background Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating Conversational Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating Streaming Call)
73410505
V900R012
73423388
RRC.AttConnEsta b.Rep.OrgConvCall
V900R013
73423389
RRC.AttConnEsta b.Rep.OrgStrCall
V900R013
73423390
RRC.AttConnEsta b.Rep.OrgInterCall
V900R013
73423391
RRC.AttConnEsta b.Rep.OrgBkgCall
V900R013
73423392
RRC.AttConnEsta b.Rep.TmConvCall
V900R013
73423393
RRC.AttConnEsta b.Rep.TmStrCall
V900R013
Issue 01 (2013-05-04)
2183
Counter ID 73423394
Counter Name RRC.AttConnEsta b.Rep.TmInterCall
Counter Description Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating Interactive Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating Background Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Originating Subscribed Traffic Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Emergency Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Inter-RAT Cell Reselection) Number of Retransmitted RRC Connection Setup Requests for Cell (Inter-RAT Cell Change Order) Number of Retransmitted RRC Connection Setup Requests for Cell (Registration)
73423395
RRC.AttConnEsta b.Rep.TmBkgCall
V900R013
73423396
RRC.AttConnEsta b.Rep.OrgSubCall
V900R013
73423397
RRC.AttConnEsta b.Rep.EmgCall
V900R013
73423398
RRC.AttConnEsta b.Rep.IRATCelRes
V900R013
73423399
RRC.AttConnEsta b.Rep.IRATCCO
V900R013
73423400
RRC.AttConnEsta b.Rep.Reg
V900R013
Issue 01 (2013-05-04)
2184
Counter ID 73423401
Counter Name RRC.AttConnEsta b.Rep.Detach
Counter Description Number of Retransmitted RRC Connection Setup Requests for Cell (Detach) Number of Retransmitted RRC Connection Setup Requests for Cell (Originating High Priority Signalling) Number of Retransmitted RRC Connection Setup Requests for Cell (Originating Low Priority Signalling) Number of Retransmitted RRC Connection Setup Requests for Cell (Call Reestablishment) Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating High Priority Signalling) Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating Low Priority Signalling) Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating-Cause Unknown)
73423402
RRC.AttConnEsta b.Rep.OrgHhPrSig
V900R013
73423403
RRC.AttConnEsta b.Rep.OrgLwPrSig
V900R013
73423404
RRC.AttConnEsta b.Rep.CallReEst
V900R013
73423405
RRC.AttConnEsta b.Rep.TmHhPrSig
V900R013
73423406
RRC.AttConnEsta b.Rep.TmLwPrSig
V900R013
73423407
RRC.AttConnEsta b.Rep.Unknown
V900R013
Issue 01 (2013-05-04)
2185
Counter ID 73441146
Counter Name VS.EcNo.Mean.TP 0
Counter Description Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 0 Number of RRC Connection Establishment Requests with Propagation Delay of 0 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 1 Number of RRC Connection Establishment Requests with Propagation Delay of 1 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 2 Number of RRC Connection Establishment Requests with Propagation Delay of 2
73423486
VS.TP.UE.0
V900R013
73441147
VS.EcNo.Mean.TP 1
V900R013
73423488
VS.TP.UE.1
V900R013
73441148
VS.EcNo.Mean.TP 2
V900R013
73423490
VS.TP.UE.2
V900R013
Issue 01 (2013-05-04)
2186
Counter ID 73441149
Counter Name VS.EcNo.Mean.TP 3
Counter Description Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 3 Number of RRC Connection Establishment Requests with Propagation Delay of 3 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 4 Number of RRC Connection Establishment Requests with Propagation Delay of 4 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 5 Number of RRC Connection Establishment Requests with Propagation Delay of 5
73423492
VS.TP.UE.3
V900R013
73441150
VS.EcNo.Mean.TP 4
V900R013
73423494
VS.TP.UE.4
V900R013
73441151
VS.EcNo.Mean.TP 5
V900R013
73423496
VS.TP.UE.5
V900R013
Issue 01 (2013-05-04)
2187
Counter ID 73441152
Counter Name VS.EcNo.Mean.TP 6.9
Counter Description Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 6~9 Number of RRC Connection Establishment Requests with Propagation Delay of 6~9 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 10~15 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 16~25 Number of RRC Connection Establishment Requests with Propagation Delay of 16~25 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 26~35
73423498
VS.TP.UE.6.9
V900R013
73441153
VS.EcNo.Mean.TP 10.15
V900R013
73441154
V900R013
73423502
VS.TP.UE.16.25
V900R013
73441155
V900R013
Issue 01 (2013-05-04)
2188
Counter ID 73423504
Counter Name VS.TP.UE.26.35
Counter Description Number of RRC Connection Establishment Requests with Propagation Delay of 26~35 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 36~55 Number of RRC Connection Establishment Requests with Propagation Delay of 36~55 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay Greater than 55 Number of RRC Connection Establishment Requests with Propagation Delay Greater than 55 Number of RRC Connection Establishment Requests with Propagation Delay of 10~15 Number of Received RRC CONNECTION REQUESTS for CS Services in a Cell
73441156
V900R013
73423506
VS.TP.UE.36.55
V900R013
73441157
VS.EcNo.Mean.TP. More55
V900R013
73423508
VS.TP.UE.More55
V900R013
73423510
VS.TP.UE.10.15
V900R013
73424223
VS.RRC.AttConnE stab.Msg.Conv
V900R014
Issue 01 (2013-05-04)
2189
Counter ID 73424224
Counter Name VS.RRC.FC.Num. CPU.OverLoad
Counter Description Number of RRC CONNECTION REQUESTS Under Flow Control Triggered by High CPU Usage for Cell Number of RRC CONNECTION REQUESTS Under Flow Control Triggered by RRC Queue Overflow for Cell Number of RRC CONNECTION REQUESTS Under Flow Control Triggered by MPU Overload for Cell Number of RRC CONNECTION REQUESTS Under Flow Control Triggered by Burst Traffic for Cell Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control Triggered by High CPU Usage for Cell Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control Triggered by RRC Queue Overflow for Cell
73424225
VS.RRC.FC.Num. RRCQueue
V900R014
73424226
VS.RRC.FC.Num. MPU.OverLoad
V900R014
73424227
VS.RRC.FC.Num. CallShock
V900R014
73424228
VS.RRC.CONV.F C.Num.CPU.OverLoad
V900R014
73424229
VS.RRC.CONV.F C.Num.RRCQueue
V900R014
Issue 01 (2013-05-04)
2190
Counter ID 73424230
Counter Name VS.RRC.CONV.F C.Num.MPU.OverLoad
Counter Description Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control Triggered by MPU Overload for Cell Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control Triggered by Burst Traffic for Cell Number of Cell Updates Under Flow Control Triggered by High CPU Usage for Cell Number of RRC CONNECTION REQUESTS Under E2E Flow Control Phase 2 for Cell Number of RRC CONNECTION REQUESTS for CS Voice Services Under E2E Flow Control Phase 2 for Cell Number of RRC Connection Setup Requests for Cell (PS Domain) Number of RRC Connection Setup Requests for Cell (CS Domain)
73424231
VS.RRC.CONV.F C.Num.CallShock
V900R014
73424232
VS.CU.FC.Num.C PU.OverLoad
V900R014
73424233
VS.RRC.FC.Num. RanFC.Ph2
V900R014
73424234
VS.RRC.CONV.F C.Num.RanFC.Ph2
V900R014
73424476
VS.RRC.AttConnE stab.PSDomain
V900R014
73424477
VS.RRC.AttConnE stab.CSDomain
V900R014
Issue 01 (2013-05-04)
2191
Counter ID 73424691
Counter Name VS.RRC.CONV.F C.Num.INT.OverLoad
Counter Description Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control Triggered by Interface-Board CPU Overload for Cell Number of RRC CONNECTION REQUESTS Under Flow Control Triggered by Interface-Board CPU Overload for Cell Number of RRC CONNECTION REQUESTS Under Flow Control Triggered by FACH Congestion for Cell Number of RRC CONNECTION REQUESTS for CS Voice Services Under E2E Flow Control Phase 1 for Cell Number of RRC CONNECTION REQUESTS Under E2E Flow Control Phase 1 for Cell Number of RRC CONNECTION REQUESTS in a Cell Under Cell Dynamic CAPS Flow Control Number of RRC CONNECTION REQUESTS for CS Services in a Cell Under Cell Dynamic CAPS Flow Control
73424692
VS.RRC.FC.Num.I NT.OverLoad
V900R014
73424693
VS.RRC.FC.Num. FACH.Cong
V900R014
73424694
VS.RRC.CONV.F C.Num.RanFC.Ph1
V900R014
73424695
VS.RRC.FC.Num. RanFC.Ph1
V900R014
73424968
VS.RRC.FC.Num. CAPS
V900R014
73424969
VS.RRC.CONV.F C.Num.CAPS
V900R014
Issue 01 (2013-05-04)
2192
Counter ID 73425017
Counter Name VS.RRC.AttConnE stab.WithSI.CsDomain
Counter Description Number of RRC Connection Setup Requests that carried System Information Container Stored Indication for CS services Number of Successful RRC Connection Setups for CS services (RRC Connection Setup Requests that carried System Information Container Stored Indication) Number of RRC Connection Setup Requests that carried System Information Container Stored Indication for PS services Number of Successful RRC Connection Setups for PS services (RRC Connection Setup Requests that carried System Information Container Stored Indication) Number of RRC Connection Setup Requests for Platinum UEs Performing Conversational Services for Cell Number of RRC Connection Setup Requests for Platinum UEs Performing Services for Cell
73425018
VS.RRC.SuccConn Estab.WithSI.CsDo main
V900R014
73425019
VS.RRC.AttConnE stab.WithSI.PsDomain
V900R014
73425020
VS.RRC.SuccConn Estab.WithSI.PsDo main
V900R014
73425914
RRC.AttConnEsta b.Conv.Platinum
V900R015
73425915
RRC.AttConnEsta b.Platinum
V900R015
Issue 01 (2013-05-04)
2193
Counter ID 73425916
Counter Name RRC.SuccConnEst ab.Conv.Platinum
Counter Description Number of Successful RRC Connection Setups for Platinum UEs Performing Conversational Services for Cell Number of Successful RRC Connection Setups for Platinum UEs for Cell
73425917
RRC.SuccConnEst ab.Platinum
V900R015
Counter VS.RRC.AttConnEstab.Sum Sub Counter RRC.AttConnEstab.OrgConvCall RRC.AttConnEstab.OrgStrCall RRC.AttConnEstab.OrgInterCall RRC.AttConnEstab.OrgBkgCall RRC.AttConnEstab.TmConvCall RRC.AttConnEstab.TmStrCall RRC.AttConnEstab.TmInterCall RRC.AttConnEstab.TmBkgCall RRC.AttConnEstab.OrgSubCall RRC.AttConnEstab.EmgCall RRC.AttConnEstab.IRATCelRes RRC.AttConnEstab.IRATCCO RRC.AttConnEstab.Reg RRC.AttConnEstab.Detach RRC.AttConnEstab.OrgHhPrSig RRC.AttConnEstab.OrgLwPrSig RRC.AttConnEstab.CallReEst RRC.AttConnEstab.TmHhPrSig RRC.AttConnEstab.TmLwPrSig RRC.AttConnEstab.Unknown RRC.AttConnEstab.MBMSRep RRC.AttConnEstab.MBMSPtp
Issue 01 (2013-05-04)
2194
Counter RRC.SuccConnEstab.sum
Sub Counter RRC.SuccConnEstab.OrgConvCall RRC.SuccConnEstab.OrgStrCall RRC.SuccConnEstab.OrgInterCall RRC.SuccConnEstab.OrgBkgCall RRC.SuccConnEstab.OrgSubCall RRC.SuccConnEstab.TmConvCall RRC.SuccConnEstab.TmStrCall RRC.SuccConnEstab.TmItrCall RRC.SuccConnEstab.TmBkgCall RRC.SuccConnEstab.IRATCelRes RRC.SuccConnEstab.IRATCCO RRC.SuccConnEstab.Reg RRC.SuccConnEstab.Detach RRC.SuccConnEstab.OrgHhPrSig RRC.SuccConnEstab.OrgLwPrSig RRC.SuccConnEstab.CallReEst RRC.SuccConnEstab.TmHhPrSig RRC.SuccConnEstab.TmLwPrSig RRC.SuccConnEstab.Unkown RRC.SuccConnEstab.EmgCall RRC.SuccConnEstab.MBMSRep RRC.SuccConnEstab.MBMSPtp
1.12.38.1 Number of RRC Connection Setup Attempts with DRD out Counters
Counter ID 67189400 Counter Name VS.RRC.Estab.DRDOut.Att Counter Description Number of RRC Connection Setup Attempts with DRD out for Cell
Description
This counter provides the number of RRC connection requests with RNC-initiated Directed Retry Decision (DRD) to a target cell during RRC connection setup. This counter is measured in the source cell.
Issue 01 (2013-05-04)
2195
Measurement point
The measurement is triggered at point A as shown in the figure, if the RNC initiates the RRC connection setup procedure with a DRD to the target cell after receiving a RRC CONNECTION REQUEST message from the UE. In this case, this counter is measured in the source cell. Figure 1-1030 Successful DRD Procedure in RRC Procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Estab.DRDOut.Att Feature ID WRFD-02040001 Feature Name Intra System Direct Retry
1.12.38.2 Number of Successful RRC Connection Setups with DRD Out
Issue 01 (2013-05-04)
2196
Counters
Counter ID 67189401 Counter Name VS.RRC.Estab.DRDOut.Su cc Counter Description Number of Successful RRC Connection Setups with DRD out for Cell
Description
This counter provides the number of successful RRC connection setups with RNC-initiated DRD to a target cell during RRC connection setup. This counter is measured in the DRD source cell.
Measurement point
The measurement is triggered at point B as shown in the figure. After receiving a RRC CONNECTION REQUEST message from the UE, the RNC initiates a DRD to the target cell in the RRC connection setup procedure and receives a RRC CONNECTION SETUP COMPLETE message from the UE. In this case, this counter is measured in the source cell. Figure 1-1031 Successful DRD in RRC Procedure
Formula
None
Issue 01 (2013-05-04)
2197
Unit
None
Related Features
Counter Name VS.RRC.Estab.DRDOut.Su cc Feature ID WRFD-02040001 WRFD-010510 Feature Name Intra System Direct Retry 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.38.3 Number of RRC Connection Setup Attempts with DRD in Counters

Counter ID 67192607 Counter Name VS.RRC.Estab.DRDIn Counter Description Number of RRC Connection Setup Attempts with DRD in for Cell
Description
This counter provides the number of RRC connection requests with RNC-initiated DRD to a target cell during RRC connection setup. This counter is measured in the DRD target cell when the RRC connection setup succeeds.
Measurement point
The measurement is triggered at point B as shown in the figure. After receiving a RRC CONNECTION REQUEST message from the UE, the RNC initiates the RRC connection setup procedure with a DRD to the target cell and the RRC connection setup succeeds. In this case, this counter is measured in the target cell.
Issue 01 (2013-05-04)
2198
Figure 1-1032 Successful DRD Procedure in RRC Procedure
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Estab.DRDIn Feature ID WRFD-02040001 WRFD-010510 Feature Name Intra System Direct Retry 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.38.4 Counters Related to Duration of RRC Connection Setup on CELL_DCH
Issue 01 (2013-05-04)
2199
Counters
Counter ID 67179302 Counter Name VS.RRC.ConnEstabTimeM ax.CellDCH Counter Description Maximum Duration of RRC Connection Setup for Cell (UE Target State on CELL_DCH) Average Duration of RRC Connection Setup for Cell (UE Target State on CELL_DCH)
67199510
VS.RRC.ConnEstabTimeM ean.CellDCH
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67179303 Counter Name VS.RRC.ConnEstab.TimeC um.CellDCH VS.RRC.ConnEstab.TimeSa mple.CellDCH Counter Description Cumulative Duration of RRC Connection Setup in CELL_DCH State for Cell Number of RRC Connection Setup in CELL_DCH State for Cell
67179304
Description
These counters provide the duration of RRC connection setup in the cell when the target state of the UE is CELL_DCH.
Measurement point
As shown in the figure, when the RNC receives a RRC CONNECTION REQUEST message, namely at point A, the time is recorded as T1. When the RNC receives a RRC CONNECTION SETUP COMPLETE message, namely at point C, the time is recorded as T2. As delta T=T2T1, delta T is the duration of the RRC connection setup.
Issue 01 (2013-05-04)
2200
Formula
VS.RRC.ConnEstabTimeMean.CellDCH = [VS.RRC.ConnEstab.TimeCum.CellDCH]/ [VS.RRC.ConnEstab.TimeSample.CellDCH]
Unit
ms
Related Features
Counter Name VS.RRC.ConnEstabTimeM ax.CellDCH Feature ID WRFD-010510 WRFD-010202 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
Issue 01 (2013-05-04)
2201
Counter Name VS.RRC.ConnEstabTimeM ean.CellDCH
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.38.5 Counters Related to the Number of RRC Connection Requests for Various Reasons Counters
Counter ID 67179329 Counter Name RRC.AttConnEstab.OrgConvCall Counter Description Number of RRC Connection Requests for Cell (Originating Conversational Call) Number of RRC Connection Requests for Cell (Originating Streaming Call) Number of RRC Connection Requests for Cell (Originating Interactive Call) Number of RRC Connection Requests for Cell (Originating Background Call) Number of RRC Connection Requests for Cell (Terminating Conversational Call) Number of RRC Connection Requests for Cell (Terminating Streaming Call) Number of RRC Connection Requests for Cell (Terminating Interactive Call)
67179330
RRC.AttConnEstab.OrgStrCall RRC.AttConnEstab.OrgInterCall RRC.AttConnEstab.OrgBkg Call
67179331
67179332
67179334
RRC.AttConnEstab.TmCon vCall
67179335
RRC.AttConnEstab.TmStrC all
67179336
RRC.AttConnEstab.TmInterCall
Issue 01 (2013-05-04)
2202
Counter ID 67179337
Counter Name RRC.AttConnEstab.TmBkg Call
Counter Description Number of RRC Connection Requests for Cell (Terminating Background Call) Number of RRC Connection Requests for Cell (Originating Subscribed Traffic Call) Number of RRC Connection Requests for Cell (Emergency Call) Number of RRC Connection Requests for Cell (Inter-RAT Cell Re-Selection) Number of RRC Connection Requests for Cell (Inter-RAT Cell Change Order) Number of RRC Connection Requests for Cell (Registration) Number of RRC Connection Requests for Cell (Detach) Number of RRC Connection Requests for Cell (Originating High Priority Signaling) Number of RRC Connection Requests for Cell (Originating Low Priority Signaling) Number of RRC Connection Requests for Cell (Call ReEstablishment) Number of RRC Connection Requests for Cell (Terminating High Priority Signaling) Number of RRC Connection Requests for Cell (Terminating Low Priority Signaling)
67179333
RRC.AttConnEstab.OrgSubCall
67179338
RRC.AttConnEstab.EmgCall RRC.AttConnEstab.IRATCelRes RRC.AttConnEstab.IRATCCO RRC.AttConnEstab.Reg
67179339
67179340
67179341
67179342 67179343
RRC.AttConnEstab.Detach RRC.AttConnEstab.OrgHhP rSig
67179344
RRC.AttConnEstab.OrgLw PrSig
67179345
RRC.AttConnEstab.CallReEst RRC.AttConnEstab.TmHhP rSig
67179346
67179347
RRC.AttConnEstab.TmLwP rSig
Issue 01 (2013-05-04)
2203
Counter ID 67179348
Counter Name RRC.AttConnEstab.Unknown
Counter Description Number of RRC Connection Requests for Cell (Terminating-Cause Unknown) Number of RRC Connection Requests for Cell (MBMS Reception) Number of RRC Connection Requests for Cell (MBMS PTP RB Request)
67195964
RRC.AttConnEstab.MBMS Rep RRC.AttConnEstab.MBMS Ptp
67195965
Description
These counters provide the number of RRC CONNECTION REQUEST messages sent from the UE to the RNC that are actually processed by the RNC according to various reasons for RRC connection requests. These counters exclude the number of rejected RRC connection requests caused by service-based redirection, inter-RAT and inter-frequency distance-based redirection, macro & micro joint inter-frequency redirection or flow control discarding.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a RRC CONNECTION REQUEST message from the UE. In this case, these counters are measured separately according to the reasons for RRC connection requests in the cell where the UE is located. These counters exclude the number of rejected RRC connection requests caused by service-based redirections, inter-RAT and inter-frequency distance-based redirections, and macro-and-micro-problematic-area-based inter-frequency redirections, and the number of RRC connection requests discarded during flow control. For more details on the reason types, see 3GPP TS 25.331. The measurement is not triggered for a RRC CONNECTION REQUEST message that is retransmitted by the UE.
Issue 01 (2013-05-04)
2204
Formula
None
Unit
None
Related Features
Counter Name RRC.AttConnEstab.OrgConvCall Feature ID WRFD-010510 WRFD-010501 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Conversational QoS Class RRC.AttConnEstab.OrgStrCall WRFD-010510 WRFD-010502 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Streaming QoS Class
Issue 01 (2013-05-04)
2205
Counter Name RRC.AttConnEstab.OrgInterCall
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Interactive QoS Class
RRC.AttConnEstab.OrgBkg Call
WRFD-010510 WRFD-010504
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Background QoS Class
RRC.AttConnEstab.TmCon vCall
WRFD-010510 WRFD-010501
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Conversational QoS Class
RRC.AttConnEstab.TmStrC all
WRFD-010510 WRFD-010502
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Streaming QoS Class
RRC.AttConnEstab.TmInterCall
WRFD-010510 WRFD-010503
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Interactive QoS Class
RRC.AttConnEstab.TmBkg Call
WRFD-010510 WRFD-010504
RRC.AttConnEstab.OrgSubCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Emergency Call 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
2206
RRC.AttConnEstab.EmgCall
WRFD-021104 WRFD-010510
RRC.AttConnEstab.IRATCelRes
WRFD-010510
Issue 01 (2013-05-04)
Counter Name RRC.AttConnEstab.IRATCCO
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release MBMS Enhanced Broadcast Mode 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
RRC.AttConnEstab.Reg
WRFD-010510
RRC.AttConnEstab.Detach
WRFD-010510
RRC.AttConnEstab.OrgHhP rSig
WRFD-010510
RRC.AttConnEstab.OrgLw PrSig
WRFD-010510
RRC.AttConnEstab.CallReEst
WRFD-010510
RRC.AttConnEstab.TmHhP rSig
WRFD-010510
RRC.AttConnEstab.TmLwP rSig
WRFD-010510
RRC.AttConnEstab.Unknown
WRFD-010510
RRC.AttConnEstab.MBMS Rep
WRFD-01066001 WRFD-010510
Issue 01 (2013-05-04)
2207
Counter Name RRC.AttConnEstab.MBMS Ptp
Feature Name MBMS Enhanced Broadcast Mode 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.38.6 Counters Related to the Number of Successful RRC Connection Setups for Various Reasons Counters
Counter ID 67179457 Counter Name RRC.SuccConnEstab.OrgConvCall Counter Description Number of Successful RRC Connection Setups for Cell (Originating Conversational Call) Number of Successful RRC Connection Setups for Cell (Originating Streaming Call) Number of Successful RRC Connection Setups for Cell (Originating Interactive Call) Number of Successful RRC Connection Setups for Cell (Originating Background Call) Number of Successful RRC Connection Setups for Cell (Originating Subscribed traffic Call) Number of Successful RRC Connection Setups for Cell (Terminating Conversational Call) Number of Successful RRC Connection Setups for Cell (Terminating Streaming Call)
67179458
RRC.SuccConnEstab.OrgStr Call RRC.SuccConnEstab.OrgInterCall RRC.SuccConnEstab.OrgBk gCall
67179459
67179460
67179461
RRC.SuccConnEstab.OrgSubCall
67179462
RRC.SuccConnEstab.TmCo nvCall
67179463
RRC.SuccConnEstab.TmStr Call
Issue 01 (2013-05-04)
2208
Counter ID 67179464
Counter Name RRC.SuccConnEstab.TmItrCall
Counter Description Number of Successful RRC Connection Setups for Cell (Terminating Interactive Call) Number of Successful RRC Connection Setups for Cell (Terminating Background Call) Number of Successful RRC Connection Setups for Cell (Inter-RAT Cell ReSelection) Number of Successful RRC Connection Setups for Cell (Inter-RAT Cell Change Order) Number of Successful RRC Connection Setups for Cell (Registration) Number of Successful RRC Connection Setups for Cell (Detach) Number of Successful RRC Connection Setups for Cell (Originating High Priority Signaling) Number of Successful RRC Connection Setups for Cell (Originating Low Priority Signaling) Number of Successful RRC Connection Setups for Cell (Call Re-Establishment) Number of Successful RRC Connection Setups for Cell (Terminating High Priority Signaling) Number of Successful RRC Connection Setups for Cell (Terminating Low Priority Signaling)
67179465
RRC.SuccConnEstab.TmBk gCall
67179467
RRC.SuccConnEstab.IRATCelRes
67179468
RRC.SuccConnEstab.IRAT CCO
67179469
RRC.SuccConnEstab.Reg
67179470
RRC.SuccConnEstab.Detach RRC.SuccConnEstab.OrgH hPrSig
67179471
67179472
RRC.SuccConnEstab.OrgL wPrSig
67179473
RRC.SuccConnEstab.CallReEst RRC.SuccConnEstab.TmHh PrSig
67179474
67179475
RRC.SuccConnEstab.TmLw PrSig
Issue 01 (2013-05-04)
2209
Counter ID 67179476
Counter Name RRC.SuccConnEstab.Unkown
Counter Description Number of Successful RRC Connection Setups for Cell (Terminating-Cause Unknown) Number of Successful RRC Connection Setups for Cell (Emergency Call) Number of Successful RRC Connection Setups for Cell (MBMS Reception) Number of Successful RRC Connection Setups for Cell (MBMS PTP RB Request)
67179466
RRC.SuccConnEstab.EmgCall RRC.SuccConnEstab.MBM SRep RRC.SuccConnEstab.MBM SPtp
67195966
67195967
Description
These counters provide the number of RRC CONNECTION SETUP COMPLETE messages from the UE to the RNC in the cell according to various reasons of RRC connection requests.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC receives a RRC CONNECTION SETUP COMPLETE message from the UE. In this case, these counters are measured separately according to the reasons for RRC connection requests in the cell where the UE is located. For details on the reason types, see section 10.3.3.11 in 3GPP TS 25.331. Figure 1-1035 Procedure for successful RRC connection setup
Issue 01 (2013-05-04)
2210
Formula
None
Unit
None
Related Features
Counter Name RRC.SuccConnEstab.OrgConvCall Feature ID WRFD-010510 WRFD-010501 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Conversational QoS Class RRC.SuccConnEstab.OrgStr Call WRFD-010510 WRFD-010502 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Streaming QoS Class RRC.SuccConnEstab.OrgInterCall WRFD-010510 WRFD-010503 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Interactive QoS Class RRC.SuccConnEstab.OrgBk gCall WRFD-010510 WRFD-010504 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Background QoS Class RRC.SuccConnEstab.OrgSubCall WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Conversational QoS Class
RRC.SuccConnEstab.TmCo nvCall
WRFD-010510 WRFD-010501
Issue 01 (2013-05-04)
2211
Counter Name RRC.SuccConnEstab.TmStr Call
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Streaming QoS Class
RRC.SuccConnEstab.TmItrCall
WRFD-010510 WRFD-010503
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Interactive QoS Class
RRC.SuccConnEstab.TmBk gCall
WRFD-010510 WRFD-010504
RRC.SuccConnEstab.IRATCelRes
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
RRC.SuccConnEstab.IRAT CCO
WRFD-010510
RRC.SuccConnEstab.Reg
WRFD-010510
RRC.SuccConnEstab.Detach
WRFD-010510
RRC.SuccConnEstab.OrgH hPrSig
WRFD-010510
RRC.SuccConnEstab.OrgL wPrSig
WRFD-010510
RRC.SuccConnEstab.CallReEst
WRFD-010510
Issue 01 (2013-05-04)
2212
Counter Name RRC.SuccConnEstab.TmHh PrSig
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Emergency Call 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release MBMS Enhanced Broadcast Mode 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
RRC.SuccConnEstab.TmLw PrSig
WRFD-010510
RRC.SuccConnEstab.Unkown
WRFD-010510
RRC.SuccConnEstab.EmgCall
WRFD-021104 WRFD-010510
RRC.SuccConnEstab.MBM SRep
WRFD-01066001 WRFD-010510
RRC.SuccConnEstab.MBM SPtp
WRFD-01066001 WRFD-010510
MBMS Enhanced Broadcast Mode 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.38.7 Number of RRC Connection Setup Messages Sent from RNC to UE Counters
Counter ID 67179298 Counter Name VS.RRC.SetupConnEstab Counter Description Number of RRC Connection Setup Messages from RNC to UE for Cell
Issue 01 (2013-05-04)
2213
Description
This counter measures the number of RRC CONNECTION SETUP messages from the RNC to the UE in the cell after the RNC receives a RRC CONNECTION REQUEST message from the UE.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends a RRC CONNECTION SETUP message to the UE after receiving a RRC CONNECTION REQUEST message from the UE. In this case, this counter is measured in the cell where the UE is located. Note that the measurement is not triggered for a RRC CONNECTION SETUP message that is retransmitted by the RNC to the UE. Figure 1-1036 Procedure for successful RRC connection setup
Formula
None
Unit
None
Issue 01 (2013-05-04)
2214
Related Features
Counter Name VS.RRC.SetupConnEstab Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.38.8 Counters Related to the Number of Successful RRC Connection Setups Counters
Counter ID 67179299 67179634 Counter Name RRC.SuccConnEstab.sum VS.RRC.SuccConnEstab.Ce llDCH Counter Description Number of Successful RRC Connection Setups for Cell Number of Successful RRC Connection Setups for Cell (UE Target State of CELL_DCH) Number of Successful RRC Connection Setups for Cell (UE Target State of CELL_FACH) Number of Successful RRC Connection Setups for Cell (UL Carried on E_DCH) Number of Successful RRC Connection Setups for Cell (DL Carried on HS_DSCH)
67179650
VS.RRC.SuccConnEstab.Ce llFACH
67196200
VS.RRC.SuccConnEstab.E DCH VS.RRC.SuccConnEstab.H SDSCH
67196201
Description
These counters provide the number of RRC CONNECTION SETUP COMPLETE messages sent by the UE to the RNC in the cell. Among them, the counter of VS.RRC.SuccConnEstab.HSDSCH includes both the case of SRB over HSDPA and the case of EFACH.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC receives a RRC CONNECTION SETUP COMPLETE message from the UE. In this case, these counters are measured in the cell where the UE is located.
Issue 01 (2013-05-04)
2215
Formula
None
Unit
None
Related Features
Counter Name RRC.SuccConnEstab.sum Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
VS.RRC.SuccConnEstab.Ce llDCH
WRFD-010510 WRFD-010202
Issue 01 (2013-05-04)
2216
Counter Name VS.RRC.SuccConnEstab.Ce llFACH
VS.RRC.SuccConnEstab.E DCH VS.RRC.SuccConnEstab.H SDSCH
WRFD-010636 WRFD-010652 WRFD-010688
SRB over HSUPA SRB over HSDPA Downlink Enhanced CELL_FACH
1.12.38.9 Counters Related to the Number of Processed RRC Connection Requests Counters
Counter ID 67190586 67179633 Counter Name VS.RRC.AttConnEstab.Sum VS.RRC.AttConnEstab.Cell DCH VS.RRC.AttConnEstab.Cell FACH VS.RRC.AttConnEstab.ED CH VS.RRC.AttConnEstab.HS DSCH Counter Description Number of Processed RRC Connection Requests for Cell Number of RRC Connection Requests for Cell (UE Target State of CELL_DCH) Number of RRC Connection Requests for Cell (UE Target State of CELL_FACH) Number of RRC Connection Attempts for UL Carried on E_DCH for Cell Number of RRC Connection Attempts for DL Carried on HS_DSCH for Cell
67179649
67196198
67196199
Description
These counters provide the number of RRC CONNECTION REQUEST messages from the UE to the RNC that are actually processed by the RNC. These counters exclude the number of rejected RRC connection requests caused by service-based redirection, inter-RAT and interfrequency distance-based redirection, macro & micro joint inter-frequency redirection or flow control discarding.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a RRC CONNECTION REQUEST message from the UE. In this case, these counters are measured separately in the cell where the UE is located. These counters exclude the number of rejected RRC connection requests caused by service-based redirection, inter-RAT and inter-frequency distance-based redirection, macro & micro joint inter-frequency redirection or flow control discarding. Note that the measurement is not triggered for a RRC CONNECTION REQUEST message that is retransmitted by the UE. Figure 1-1038 RRC connection setup success flow
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnEstab.Sum Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
2218
Issue 01 (2013-05-04)
Counter Name VS.RRC.AttConnEstab.Cell DCH
VS.RRC.AttConnEstab.Cell FACH
WRFD-010510 WRFD-010202
3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
VS.RRC.AttConnEstab.ED CH VS.RRC.AttConnEstab.HS DSCH
WRFD-010636 WRFD-010652 WRFD-010688
SRB over HSUPA SRB over HSDPA Downlink Enhanced CELL_FACH
1.12.38.10 Number of Successful RRC Connection Setups with Repeated RRC Connection Request Messages from UE Counters
Counter ID 67190587 Counter Name VS.RRC.SuccConnEstab.Fir st Counter Description Number of Successful RRC Connection Setups with One RRC Connection Request Message from UE for Cell Number of Successful RRC Connection Setups with Two RRC Connection Request Messages from UE for Cell Number of Successful RRC Connection Setups with Three RRC Connection Request Messages from UE for Cell
67190588
VS.RRC.SuccConnEstab.Se cond
67190589
VS.RRC.SuccConnEstab.Th ird
Issue 01 (2013-05-04)
2219
Description
These counters provide the number of RRC CONNECTION SETUP COMPLETE messages sent from the UE to the RNC in the cell. These counters are measured separately according to the number of RRC connection request messages.
Measurement point
The measurement is triggered at point C as shown in the following figure. When the RNC receives from the UE an RRC CONNECTION SETUP COMPLETE message and the RRC connection is established based on the first RRC CONNECTION REQUEST message sent by the UE, the VS.RRC.SuccConnEstab.First counter is measured in the cell that the UE camps on. Figure 1-1039 Successful RRC connection setup during first request
The measurement is triggered at point D as shown in the following figure. When the RNC receives from the UE an RRC CONNECTION SETUP COMPLETE message and the RRC connection is established based on the second RRC CONNECTION REQUEST message sent by the UE, the VS.RRC.SuccConnEstab.Second counter is measured in the cell that the UE camps on.
Issue 01 (2013-05-04)
2220
Figure 1-1040 Successful RRC connection setup during second request
The measurement is triggered at point E as shown in the following figure. When the RNC receives from the UE an RRC CONNECTION SETUP COMPLETE message and the RRC connection is established based on the third RRC CONNECTION REQUEST message sent by the UE, the VS.RRC.SuccConnEstab.Third counter is measured in the cell that the UE camps on. Figure 1-1041 Successful RRC connection setup during third request
Issue 01 (2013-05-04)
2221
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.SuccConnEstab.Fir st Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RRC.SuccConnEstab.Se cond
WRFD-010510
VS.RRC.SuccConnEstab.Th ird
WRFD-010510
1.12.38.11 Number of Automatic DSACs Triggered by Congestion on Iu Interface Counters

Counter ID 67195590 Counter Name VS.RRC.AutoDsac.Num Counter Description Number of Automatic DSACs Triggered by Congestion on Iu Interface for Cell
Description
When RANAP OVERLOAD occurs in the CN, the automatic DSAC is triggered in the scope of the RNC. This counter provides the number of triggered automatic DSACs in the cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an RANAP OVERLOAD message from the CN, the automatic DSAC is triggered in the cell. The number of triggered automatic DSACs is measured in the cell.
Figure 1-1042 Automatic domain-based access control triggered by core network overload
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AutoDsac.Num Feature ID WRFD-020114 Feature Name Domain Specific Access Control (DSAC)
1.12.38.12 Number of RRC Connection Requests sent by the UE for cell Counters
Counter ID 73403798 Counter Name VS.RRC.AttConnEstab.Msg Counter Description Number of RRC Connection Requests sent by the UE for cell
Issue 01 (2013-05-04)
2223
Description
The measurement item takes statistics of the total Number of RRC Connection Requests sent by the UE including first and repetitive times
Measurement point
The measurement is triggered at point A in the figure. This measurement counter is incremented by one when the RNC receives a RRC CONNECTION REQUEST message from an UE. To increase the possibility of successful connection, an UE may send the RRC CONNECTION REQUEST many times. The RNC counts the RRC connection requests repetitively sent by the UE. Figure 1-1043 RRC connection setup success flow
Formula
None
Unit
None
Issue 01 (2013-05-04)
2224
Related Features
Counter Name VS.RRC.AttConnEstab.Msg Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.38.13 Number of PTT UEs with RRC Connection State of CELL_FACH Counters
Counter ID 73410489 Counter Name VS.CellFACHUEs.PTT Counter Description Number of PTT UEs in Cell with RRC Connection State of CELL_FACH
Description
This counter provides the average number of PTT UEs with RRC Connection State of CELL_FACH in the cell.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of number of PTT UEs with RRC Connection State of CELL_FACH. At the end of the measurement period, by dividing the accumulated value of sample data in the period by the number of samples, the average number of PTT UEs carried on the CELL_FACH in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Name VS.CellFACHUEs.PTT Feature ID WRFD-020134 Feature Name Push to Talk
1.12.38.14 Number of PTT UEs with RRC Connection State of CELL_DCH

Counters
Counter ID 73410490 Counter Name VS.CellDCHUEs.PTT Counter Description Number of PTT UEs in Cell with RRC Connection State of CELL_DCH
Description
This counter provides the average number of PTT UEs with RRC Connection State of CELL_DCH in the cell.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of number of PTT UEs with RRC Connection State of CELL_DCH. At the end of the measurement period, by dividing the accumulated value of sample data in the period by the number of samples, the average number of PTT UEs carried on the CELL_DCH in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Name VS.CellDCHUEs.PTT Feature ID WRFD-020134 Feature Name Push to Talk
1.12.38.15 Duration of RRC Establishment Process on FACH for Cell Counters

Counter ID 73421887 Counter Name VS.RRC.ConnEstabTimeM ax.CellFACH VS.RRC.ConnEstabTimeM ean.CellFACH Counter Description Maximum Duration of RRC Establishment Process on FACH for Cell Mean Duration of RRC Establishment Process on FACH for Cell
73439969
Issue 01 (2013-05-04)
2226
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73421888 Counter Name VS.RRC.ConnEstabTime.C ellFACH.Cum VS.RRC.ConnEstabTime.C ellFACH.Sample Counter Description Cumulative Duration of RRC Establishment Process on FACH for Cell Number of Samples of Cumulative Duration of RRC Establishment Process on FACH for Cell
73421889
Description
These counters provide RRC signaling connection establishment in a cell after a UE transits to CELL_FACH. The following table describes the meaning of each counter. Counter Name VS.RRC.ConnEstabTimeMax.CellFACH VS.RRC.ConnEstabTimeMean.CellFACH Description Maximum delay of the RRC signaling on the FACH in a cell Mean delay of the RRC signaling on the FACH in a cell
Measurement point
As shown in the figure, when the RNC receives a RRC CONNECTION REQUEST message, namely at point A, the time is recorded as T1. When the RNC receives a RRC CONNECTION SETUP COMPLETE message, namely at point C, the time is recorded as T2. As delta T=T2T1, delta T is the duration of the RRC connection setup.
Issue 01 (2013-05-04)
2227
Formula
VS.RRC.ConnEstabTimeMean.CellFACH = [VS.RRC.ConnEstabTime.CellFACH.Cum]/ [VS.RRC.ConnEstabTime.CellFACH.Sample]
Unit
ms
Related Features
Counter Name VS.RRC.ConnEstabTimeM ax.CellFACH Feature ID WRFD-010688 WRFD-010202 Feature Name Downlink Enhanced CELL_FACH UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) VS.RRC.ConnEstabTimeM ean.CellFACH WRFD-010688 WRFD-010202 Downlink Enhanced CELL_FACH UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
Issue 01 (2013-05-04)
2228
1.12.38.16 Number of PTT UEs in CELL_PCH State Counters

Counter ID 73410505 Counter Name VS.CellPCHUEs.PTT Counter Description Number of PTT UEs with RRC Connection State of CELL_PCH for Cell
Description
This counter provides the average number of PTT UEs with RRC connection state of CELL_PCH in the Cell.
Measurement point
The system periodically takes samples of the number of PTT UEs in the RRC connection state of CELL_PCH every five seconds. At the end of the measurement period, the value of this counter is obtained by dividing the accumulated value of UE number by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.CellPCHUEs.PTT Feature ID WRFD-010202 WRFD-020134 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Push to Talk
1.12.38.17 Number of Retransmitted RRC Connection Setup Requests for Cell
Issue 01 (2013-05-04)
2229
Counters
Counter ID 73423388 Counter Name RRC.AttConnEstab.Rep.Or gConvCall Counter Description Number of Retransmitted RRC Connection Setup Requests for Cell (Originating Conversational Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Originating Streaming Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Originating Interactive Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Originating Background Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating Conversational Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating Streaming Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating Interactive Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating Background Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Originating Subscribed Traffic Call)
73423389
RRC.AttConnEstab.Rep.Or gStrCall
73423390
RRC.AttConnEstab.Rep.OrgInterCall
73423391
RRC.AttConnEstab.Rep.Or gBkgCall
73423392
RRC.AttConnEstab.Rep.Tm ConvCall
73423393
RRC.AttConnEstab.Rep.Tm StrCall
73423394
RRC.AttConnEstab.Rep.Tm InterCall
73423395
RRC.AttConnEstab.Rep.Tm BkgCall
73423396
RRC.AttConnEstab.Rep.Or gSubCall
Issue 01 (2013-05-04)
2230
Counter ID 73423397
Counter Name RRC.AttConnEstab.Rep.Em gCall
Counter Description Number of Retransmitted RRC Connection Setup Requests for Cell (Emergency Call) Number of Retransmitted RRC Connection Setup Requests for Cell (Inter-RAT Cell Re-selection) Number of Retransmitted RRC Connection Setup Requests for Cell (Inter-RAT Cell Change Order) Number of Retransmitted RRC Connection Setup Requests for Cell (Registration) Number of Retransmitted RRC Connection Setup Requests for Cell (Detach) Number of Retransmitted RRC Connection Setup Requests for Cell (Originating High Priority Signalling) Number of Retransmitted RRC Connection Setup Requests for Cell (Originating Low Priority Signalling) Number of Retransmitted RRC Connection Setup Requests for Cell (Call Reestablishment) Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating High Priority Signalling) Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating Low Priority Signalling)
73423398
RRC.AttConnEstab.Rep.IR ATCelRes
73423399
RRC.AttConnEstab.Rep.IR ATCCO
73423400
RRC.AttConnEstab.Rep.Re g
73423401
RRC.AttConnEstab.Rep.Detach RRC.AttConnEstab.Rep.Or gHhPrSig
73423402
73423403
RRC.AttConnEstab.Rep.Or gLwPrSig
73423404
RRC.AttConnEstab.Rep.Cal lReEst
73423405
RRC.AttConnEstab.Rep.Tm HhPrSig
73423406
RRC.AttConnEstab.Rep.Tm LwPrSig
Issue 01 (2013-05-04)
2231
Counter ID 73423407
Counter Name RRC.AttConnEstab.Rep.Un known
Counter Description Number of Retransmitted RRC Connection Setup Requests for Cell (Terminating-Cause Unknown)
Description
These counters provide the number of retransmitted RRC connection setup requests in the cell after an RRC connection request is rejected due to resource insufficiency. These counters indicate whether the resources are congested. A high counter value indicates that a large number of users have accessed the cell or the resources of the RNC or NodeB are insufficient, and the RRC connection setup fails.
Measurement point
The measurement is triggered at point B, C, D, and so on as shown in the figure. If an RRC Connection Request message sent by the UE is rejected because of resource insufficiency, the UE sends the RRC Connection Request message again. In this case, a counter is measured according to the request cause as shown in point B. If the request is rejected again, the UE sends another RRC Connection Request message, and a counter is measured again according to the request cause as shown in point C. That is, each time an RRC Connection Request message is retransmitted within (RRCWaitTime x N300 + 2) seconds after the last RRC Connection Request message is sent by the UE, a counter is measured. Figure 1-1045 RRC connection setup request resending and rejection
Issue 01 (2013-05-04)
2232
Formula
None
Unit
None
Related Features
Counter Name RRC.AttConnEstab.Rep.Or gConvCall Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
RRC.AttConnEstab.Rep.Or gStrCall
WRFD-010510
RRC.AttConnEstab.Rep.OrgInterCall
WRFD-010510
RRC.AttConnEstab.Rep.Or gBkgCall
WRFD-010510
RRC.AttConnEstab.Rep.Tm ConvCall
WRFD-010510
RRC.AttConnEstab.Rep.Tm StrCall
WRFD-010510
RRC.AttConnEstab.Rep.Tm InterCall
WRFD-010510
RRC.AttConnEstab.Rep.Tm BkgCall
WRFD-010510
Issue 01 (2013-05-04)
2233
Counter Name RRC.AttConnEstab.Rep.Or gSubCall
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
RRC.AttConnEstab.Rep.Em gCall
WRFD-010510
RRC.AttConnEstab.Rep.IR ATCelRes
WRFD-010510
RRC.AttConnEstab.Rep.IR ATCCO
WRFD-010510
RRC.AttConnEstab.Rep.Re g
WRFD-010510
RRC.AttConnEstab.Rep.Detach
WRFD-010510
RRC.AttConnEstab.Rep.Or gHhPrSig
WRFD-010510
RRC.AttConnEstab.Rep.Or gLwPrSig
WRFD-010510
RRC.AttConnEstab.Rep.Cal lReEst
WRFD-010510
RRC.AttConnEstab.Rep.Tm HhPrSig
WRFD-010510
Issue 01 (2013-05-04)
2234
Counter Name RRC.AttConnEstab.Rep.Tm LwPrSig
RRC.AttConnEstab.Rep.Un known
WRFD-010510
1.12.38.18 The average Ec/N0 at each propagation delay range in a cell Counters
Counter ID 73441146 Counter Name VS.EcNo.Mean.TP0 Counter Description Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 0 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 1 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 2 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 3 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 4 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 5 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 6~9
2235
73441147
VS.EcNo.Mean.TP1
73441148
VS.EcNo.Mean.TP2
73441149
VS.EcNo.Mean.TP3
73441150
VS.EcNo.Mean.TP4
73441151
VS.EcNo.Mean.TP5
73441152
VS.EcNo.Mean.TP6.9
Issue 01 (2013-05-04)
Counter ID 73441153
Counter Name VS.EcNo.Mean.TP10.15
Counter Description Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 10~15 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 16~25 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 26~35 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay of 36~55 Average Ec/N0 During RRC Connection Establishment Requests with Propagation Delay Greater than 55
73441154
VS.EcNo.Mean.TP16.25
73441155
73441156
73441157
VS.EcNo.Mean.TP.More55
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73423485 73423487 73423509 73423501 73423489 73423503 73423491 73423505 73423493 73423495 73423497 73423507 Counter Name VS.EcNo.Cum.TP0 VS.EcNo.Cum.TP1 VS.EcNo.Cum.TP10.15 VS.EcNo.Cum.TP16.25 VS.EcNo.Cum.TP2 VS.EcNo.Cum.TP26.35 VS.EcNo.Cum.TP3 VS.EcNo.Cum.TP36.55 VS.EcNo.Cum.TP4 VS.EcNo.Cum.TP5 VS.EcNo.Cum.TP6.9 VS.EcNo.Cum.TP.More55 Counter Description TP0Cum TP1Cum TP10~15Cum TP16~25Cum TP2Cum TP26~35Cum TP3Cum TP36~55Cum TP4Cum TP5Cum TP6~9Cum TPMore55Cum
Issue 01 (2013-05-04)
2236
Description
These counters provide the average Ec/N0 at each propagation delay range in a cell. The propagation delay is carried in the RACH DATA FRAME message sent from the NodeB to the RNC during an RRC connection establishment procedure.These counters are calculated based on the Ec/N0 value reported by the UE. As specified in 3GPP TS25.133, the mapping between the reported Ec/N0 value and the measured Ec/N0 value is: Measured Ec/N0 value = Round off ((Reported Ec/N0 value - 49)/2).
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an RRC CONNECTION REQUEST message from a cell, the RNC accumulates Ec/N0 according to the range of the propagation delay. At the end of each measurement period, the RNC divides the accumulated Ec/N0 by the number of RRC connection requests in each propagation delay range to obtain the average Ec/N0. Figure 1-1046 RRC connection establishment procedure
Formula
VS.EcNo.Mean.TP0 = [VS.EcNo.Cum.TP0]/[VS.TP.UE.0] VS.EcNo.Mean.TP1 = [VS.EcNo.Cum.TP1]/[VS.TP.UE.1] VS.EcNo.Mean.TP2 = [VS.EcNo.Cum.TP2]/[VS.TP.UE.2] VS.EcNo.Mean.TP3 = [VS.EcNo.Cum.TP3]/[VS.TP.UE.3] VS.EcNo.Mean.TP4 = [VS.EcNo.Cum.TP4]/[VS.TP.UE.4] VS.EcNo.Mean.TP5 = [VS.EcNo.Cum.TP5]/[VS.TP.UE.5]
VS.EcNo.Mean.TP6.9 = [VS.EcNo.Cum.TP6.9]/[VS.TP.UE.6.9] VS.EcNo.Mean.TP10.15 = [VS.EcNo.Cum.TP10.15]/[VS.TP.UE.10.15] VS.EcNo.Mean.TP16.25 = [VS.EcNo.Cum.TP16.25]/[VS.TP.UE.16.25] VS.EcNo.Mean.TP26.35 = [VS.EcNo.Cum.TP26.35]/[VS.TP.UE.26.35] VS.EcNo.Mean.TP36.55 = [VS.EcNo.Cum.TP36.55]/[VS.TP.UE.36.55] VS.EcNo.Mean.TP.More55 = [VS.EcNo.Cum.TP.More55]/[VS.TP.UE.More55]
Unit
dB
Related Features
Counter Name VS.EcNo.Mean.TP0 Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.EcNo.Mean.TP1
WRFD-010510
VS.EcNo.Mean.TP2
WRFD-010510
VS.EcNo.Mean.TP3
WRFD-010510
VS.EcNo.Mean.TP4
WRFD-010510
VS.EcNo.Mean.TP5
WRFD-010510
VS.EcNo.Mean.TP6.9
WRFD-010510
Issue 01 (2013-05-04)
2238
Counter Name VS.EcNo.Mean.TP10.15
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
WRFD-010510
WRFD-010510
WRFD-010510
VS.EcNo.Mean.TP.More55
WRFD-010510
1.12.38.19 Number of RRC Connection Establishment Requests that propagation delay falls into different value ranges in a cell Counters
Counter ID 73423486 Counter Name VS.TP.UE.0 Counter Description Number of RRC Connection Establishment Requests with Propagation Delay of 0 Number of RRC Connection Establishment Requests with Propagation Delay of 1 Number of RRC Connection Establishment Requests with Propagation Delay of 2 Number of RRC Connection Establishment Requests with Propagation Delay of 3
73423488
VS.TP.UE.1
73423490
VS.TP.UE.2
73423492
VS.TP.UE.3
Issue 01 (2013-05-04)
2239
Counter ID 73423494
Counter Name VS.TP.UE.4
Counter Description Number of RRC Connection Establishment Requests with Propagation Delay of 4 Number of RRC Connection Establishment Requests with Propagation Delay of 5 Number of RRC Connection Establishment Requests with Propagation Delay of 6~9 Number of RRC Connection Establishment Requests with Propagation Delay of 16~25 Number of RRC Connection Establishment Requests with Propagation Delay of 26~35 Number of RRC Connection Establishment Requests with Propagation Delay of 36~55 Number of RRC Connection Establishment Requests with Propagation Delay Greater than 55 Number of RRC Connection Establishment Requests with Propagation Delay of 10~15
73423496
VS.TP.UE.5
73423498
VS.TP.UE.6.9
73423502
VS.TP.UE.16.25
73423504
VS.TP.UE.26.35
73423506
VS.TP.UE.36.55
73423508
VS.TP.UE.More55
73423510
VS.TP.UE.10.15
Description
These counters provide the number of times that propagation delay falls into different value ranges in a cell. The propagation delay is carried in the RACH DATA FRAME message sent from the NodeB to the RNC during an RRC connection establishment procedure. These counters reflect the distribution of UEs in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RACH DATA FRAME message from a cell, the RNC increments the corresponding counter according to the range of the propagation delay carried in the message. At the end of each measurement period, the RNC calculates the total number of RRC connection establishments in each propagation delay range. Each propagation delay represents three chips. The propagation distance of one chip is 78 m. Therefore, one propagation delay corresponds to 234 m. When the propagation delay is 0, it indicates that the UE is 0-234 m away from the base station.
When the propagation delay is 1, it indicates that the UE is 234-468 m away from the base station. When the propagation delay is 2, it indicates that the UE is 468-702 m away from the base station. ...... When the propagation delay is 55, it indicates that the UE is 12870-13104 m away from the base station. Figure 1-1047 RRC connection establishment procedure
Formula
None
Unit
None
Related Features
Counter Name VS.TP.UE.0 Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
2241
Issue 01 (2013-05-04)
Counter Name VS.TP.UE.1
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.TP.UE.2
WRFD-010510
VS.TP.UE.3
WRFD-010510
VS.TP.UE.4
WRFD-010510
VS.TP.UE.5
WRFD-010510
VS.TP.UE.6.9
WRFD-010510
VS.TP.UE.16.25
WRFD-010510
VS.TP.UE.26.35
WRFD-010510
VS.TP.UE.36.55
WRFD-010510
VS.TP.UE.More55
WRFD-010510
Issue 01 (2013-05-04)
2242
Counter Name VS.TP.UE.10.15
1.12.38.20 Number of Received RRC CONNECTION REQUESTS for CS Services in a Cell Counters
Counter ID 73424223 Counter Name VS.RRC.AttConnEstab.Msg .Conv Counter Description Number of Received RRC CONNECTION REQUESTS for CS Services in a Cell
Description
This counter provides the total number of received RRC CONNECTION REQUEST messages for CS services in a cell, including repeatedly transmitted messages. If the establishment cause in these requests is UU_ORIGINATING_CONVERSATIONAL_CALL_ESTAB_CAUSE or UU_TERMNT_CONVERSATIONAL_CALL_ESTAB_CAUSE, the RNC determines that the current service is a CS service.
Measurement point
After the RNC receives an RRC CONNECTION REQUEST message from a UE, this counter is increased by one if the current service is a CS service. This counter calculates the repeatedly transmitted RRC CONNECTION REQUEST message.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnEstab.Msg .Conv Feature ID WRFD-040100 Feature Name Flow Control
Issue 01 (2013-05-04)
2243
1.12.38.21 Number of RRC CONNECTION REQUESTS Under Flow Control for Cell Counters
Counter ID 73424224 Counter Name VS.RRC.FC.Num.CPU.Ove rLoad Counter Description Number of RRC CONNECTION REQUESTS Under Flow Control Triggered by High CPU Usage for Cell Number of RRC CONNECTION REQUESTS Under Flow Control Triggered by RRC Queue Overflow for Cell Number of RRC CONNECTION REQUESTS Under Flow Control Triggered by MPU Overload for Cell Number of RRC CONNECTION REQUESTS Under Flow Control Triggered by Burst Traffic for Cell Number of RRC CONNECTION REQUESTS Under E2E Flow Control Phase 2 for Cell
73424225
VS.RRC.FC.Num.RRCQue ue
73424226
VS.RRC.FC.Num.MPU.Ov erLoad
73424227
VS.RRC.FC.Num.CallShock
73424233
VS.RRC.FC.Num.RanFC.P h2
Description
These counters provide the number of RRC CONNECTION REQUEST messages in a Cell under flow control.
Measurement point
After a CPUS subsystem under flow control receives an RRC CONNECTION REQUEST message from a UE, the RNC determines whether to agree to this request by calling up the flow control algorithm. If the RNC rejects the request and the number of rejected requests does not exceed the related threshold within the current second, the RNC sends the UE an RRC CONNECTION REJECT message. If the number of rejected requests exceeds the threshold within the current second, the RNC discards the request. These counters calculate all rejected and discarded requests in a cell.
Issue 01 (2013-05-04)
2244
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.FC.Num.CPU.Ove rLoad VS.RRC.FC.Num.RRCQue ue VS.RRC.FC.Num.MPU.Ov erLoad VS.RRC.FC.Num.CallShock VS.RRC.FC.Num.RanFC.P h2 Feature ID WRFD-040100 WRFD-040100 WRFD-040100 WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control Flow Control Flow Control Flow Control
1.12.38.22 Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control for Cell Counters
Counter ID 73424228 Counter Name VS.RRC.CONV.FC.Num.C PU.OverLoad Counter Description Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control Triggered by High CPU Usage for Cell Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control Triggered by RRC Queue Overflow for Cell
73424229
VS.RRC.CONV.FC.Num.R RCQueue
Issue 01 (2013-05-04)
2245
Counter ID 73424230
Counter Name VS.RRC.CONV.FC.Num.M PU.OverLoad
Counter Description Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control Triggered by MPU Overload for Cell Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control Triggered by Burst Traffic for Cell Number of RRC CONNECTION REQUESTS for CS Voice Services Under E2E Flow Control Phase 2 for Cell
73424231
VS.RRC.CONV.FC.Num.C allShock
73424234
VS.RRC.CONV.FC.Num.R anFC.Ph2
Description
These counters provide the number of RRC CONNECTION REQUEST messages for CS services in a cell under flow control. If the establishment cause in these requests is UU_ORIGINATING_CONVERSATIONAL_CALL_ESTAB_CAUSE or UU_TERMNT_CONVERSATIONAL_CALL_ESTAB_CAUSE, the RNC determines that the current service is a CS service.
Measurement point
After a CPUS subsystem under flow control receives an RRC CONNECTION REQUEST message from a UE, the RNC determines whether to agree to this request by calling up the flow control algorithm. If the RNC rejects the request and the number of rejected requests does not exceed the related threshold within the current second, the RNC sends the UE an RRC CONNECTION REJECT message. If the number of rejected requests exceeds the threshold within the current second, the RNC discards the request. These counters calculate all rejected and discarded requests in a cell.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2246
Related Features
Counter Name VS.RRC.CONV.FC.Num.C PU.OverLoad VS.RRC.CONV.FC.Num.R RCQueue VS.RRC.CONV.FC.Num.M PU.OverLoad VS.RRC.CONV.FC.Num.C allShock VS.RRC.CONV.FC.Num.R anFC.Ph2 Feature ID WRFD-040100 WRFD-040100 WRFD-040100 WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control Flow Control Flow Control Flow Control
1.12.38.23 Number of Cell Updates Under Flow Control Triggered by High CPU Usage for Cell Counters
Counter ID 73424232 Counter Name VS.CU.FC.Num.CPU.OverLoad Counter Description Number of Cell Updates Under Flow Control Triggered by High CPU Usage for Cell
Description
This counter provides the number of cell updates in a cell under flow control triggered by CPU usage. The flow control is performed on UEs that are in the CELL_PCH or URA_PCH state and require cell or URA updates.
Measurement point
This counter is increased by one when either of the following conditions is met: (1)The RNC receives a cell update message from a UE in the CELL_PCH or URA_PCH state, and the cell is under flow control triggered by CPU usage. (2)The RNC receives a URA update message from a UE in the URA_PCH state, and the cell is under flow control triggered by CPU usage.
Formula
None
Unit
None
Related Features
Counter Name VS.CU.FC.Num.CPU.OverLoad Feature ID WRFD-040100 Feature Name Flow Control
1.12.38.24 Number of RRC Connection Setup Requests for Cell (PS Domain) Counters
Counter ID 73424476 Counter Name VS.RRC.AttConnEstab.PSD omain Counter Description Number of RRC Connection Setup Requests for Cell (PS Domain)
Description
This counter measures the number of radio resource control (RRC) connection setup requests for PS services in a cell.
Measurement point
The measurement is triggered at point A shown in the figure when the RNC receives an RRC CONNECTION REQUEST message containing the information element (IE) Domain Indicator from a UE that is compliant with 3GPP Release 6 or later. This counter is not measured for RRC connection setup requests rejected due to service-based redirection or for RRC CONNECTION REQUEST messages retransmitted by the UE.
Issue 01 (2013-05-04)
2248
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnEstab.PSD omain Feature ID WRFD-010510 WRFD-140213 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Intelligent Access Class Control
1.12.38.25 Number of RRC Connection Setup Requests for Cell (CS Domain)
Issue 01 (2013-05-04)
2249
Counters
Counter ID 73424477 Counter Name VS.RRC.AttConnEstab.CS Domain Counter Description Number of RRC Connection Setup Requests for Cell (CS Domain)
Description
This counter measures the number of RRC connection setup requests for CS services in a cell.
Measurement point
The measurement is triggered at point A shown in the figure when the RNC receives an RRC CONNECTION REQUEST message containing the IE Domain Indicator from a UE that is compliant with 3GPP Release 6 or later. This counter is not measured for RRC connection setup requests rejected due to service-based redirection or for RRC CONNECTION REQUEST messages retransmitted by the UE. Figure 1-1049 Procedure for successful RRC connection setup
Formula
None
Issue 01 (2013-05-04)
2250
Unit
None
Related Features
Counter Name VS.RRC.AttConnEstab.CS Domain Feature ID WRFD-010510 WRFD-140213 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Intelligent Access Class Control
1.12.38.26 Number of Rejected RRC Connection Setup Requests for CS Voice Services During Flow Control Caused by Interface-Board CPU Overload for Cell Counters
Counter ID 73424691 Counter Name VS.RRC.CONV.FC.Num.I NT.OverLoad Counter Description Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control Triggered by Interface-Board CPU Overload for Cell
Description
This counter measures the number of rejected radio resource control (RRC) connection setup requests for CS Voice services during flow control caused by interface-board central processing unit (CPU) overload in a cell. If the cause value contained in an RRC CONNECTION REQUEST message is Originating Conversational Call or Terminating Conversational Call, the RRC connection is set up for a CS Voice service.
Measurement point
The measurement is triggered when all the following conditions are met: A CPUS receives an RRC CONNECTION REQUEST message from a UE. The CPUS rejects the UE's request because of interface-board CPU overload and failures in applying for transmission resources. This counter measures the number of rejected radio resource control (RRC) connection setup requests for CS Voice services during flow control caused by interface-board central processing unit (CPU) overload in a cell.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.CONV.FC.Num.I NT.OverLoad Feature ID WRFD-040100 Feature Name Flow Control
1.12.38.27 Number of Rejected RRC Connection Setup Requests During Flow Control Caused by Interface-Board CPU Overload for Cell Counters
Counter ID 73424692 Counter Name VS.RRC.FC.Num.INT.Over Load Counter Description Number of RRC CONNECTION REQUESTS Under Flow Control Triggered by Interface-Board CPU Overload for Cell
Description
This counter measures the number of rejected radio resource control (RRC) connection setup requests during flow control caused by interface-board central processing unit (CPU) overload in a cell.
Measurement point
The measurement is triggered when all the following conditions are met: A CPUS receives an RRC CONNECTION REQUEST message from a UE. The CPUS rejects the UE's request because of interface-board CPU overload and failures in applying for transmission resources. This counter measures the number of rejected radio resource control (RRC) connection setup requests during flow control caused by interface-board central processing unit (CPU) overload in a cell.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.FC.Num.INT.Over Load Feature ID WRFD-040100 Feature Name Flow Control
1.12.38.28 Number of Rejected RRC Connection Setup Requests During Flow Control Caused by FACH Congestion for Cell Counters
Counter ID 73424693 Counter Name VS.RRC.FC.Num.FACH.C ong Counter Description Number of RRC CONNECTION REQUESTS Under Flow Control Triggered by FACH Congestion for Cell
Description
This counter measures the number of rejected radio resource control (RRC) connection setup requests during flow control caused by FACH congestion in a cell.
Measurement point
The measurement is triggered when a CPUS receives an RRC CONNECTION REQUEST message from a UE and the MAC-c discards the message due to severe FACH congestion. This counter measures the number of rejected radio resource control (RRC) connection setup requests during flow control caused by FACH CCCH congestion in a cell.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.FC.Num.FACH.C ong Feature ID WRFD-040100 Feature Name Flow Control
Issue 01 (2013-05-04)
2253
1.12.38.29 Number of Rejected RRC Connection Setup Requests for CS Voice Services During E2E Flow Control Phase 1 for Cell Counters
Counter ID 73424694 Counter Name VS.RRC.CONV.FC.Num.R anFC.Ph1 Counter Description Number of RRC CONNECTION REQUESTS for CS Voice Services Under E2E Flow Control Phase 1 for Cell
Description
This counter measures the number of rejected radio resource control (RRC) connection setup requests for CS Voice services during E2E flow control phase 1 in a cell. If the cause value contained in an RRC CONNECTION SETUP REQUEST message is Originating Conversational Call or Terminating Conversational Call, the RRC connection is set up for a CS Voice service.
Measurement point
The measurement is triggered when a central processing unit subsystem (CPUS) receives an RRC CONNECTION REQUEST message from a UE and a RADIO LINK SETUP FAILURE message with the cause value of Control processing overload from the NodeB. This counter measures the number of rejected radio resource control (RRC) connection setup requests for CS Voice services during E2E flow control phase 1 in a cell.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.CONV.FC.Num.R anFC.Ph1 Feature ID WRFD-040100 Feature Name Flow Control
1.12.38.30 Number of Rejected RRC Connection Setup Requests During E2E Flow Control Phase 1 for Cell
Counters
Counter ID 73424695 Counter Name VS.RRC.FC.Num.RanFC.P h1 Counter Description Number of RRC CONNECTION REQUESTS Under E2E Flow Control Phase 1 for Cell
Description
This counter measures the number of rejected radio resource control (RRC) connection setup requests during E2E flow control phase 1 in a cell.
Measurement point
The measurement is triggered when a central processing unit subsystem (CPUS) receives an RRC CONNECTION REQUEST message from a UE and a RADIO LINK SETUP FAILURE message with the cause value of NodeB CPU overload from the NodeB. This counter measures the number of rejected radio resource control (RRC) connection setup requests during E2E flow control phase 1 in a cell.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.FC.Num.RanFC.P h1 Feature ID WRFD-040100 Feature Name Flow Control
1.12.38.31 Number of RRC CONNECTION REQUESTS in a Cell Under Cell Dynamic CAPS Flow Control
Issue 01 (2013-05-04)
2255
Counters
Counter ID 73424968 Counter Name VS.RRC.FC.Num.CAPS Counter Description Number of RRC CONNECTION REQUESTS in a Cell Under Cell Dynamic CAPS Flow Control
Description
This counter provides the number of RRC connection requests during the (call attempt per second) CAPS flow control algorithm. This algorithm considers the ratio of RRC connection setup failures, CPU usage of the SPU subsystem, and congestion status of the NCP link.
Measurement point
Upon receiving an RRC Connection Request message from a UE, the RNC determines whether to set up the RRC connection based on the flow control algorithm if dynamic CAPS flow control is being performed in the cell. If the RRC connection is not to be set up, the RNC checks whether the number of rejected RRC connection requests during the latest second is less than or equal to the preset maximum number of rejected RRC connection requests. If yes, the RNC responds the UE with an RRC Connection Reject message. If no, the RNC directly discards the RRC Connection Request message. This counter provides the number of rejected and discarded RRC connection requests during the dynamic CAPS flow control algorithm in the cell.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.FC.Num.CAPS Feature ID WRFD-040100 Feature Name Flow Control
1.12.38.32 Number of RRC CONNECTION REQUESTS for CS Services in a Cell Under Cell Dynamic CAPS Flow Control
Issue 01 (2013-05-04)
2256
Counters
Counter ID 73424969 Counter Name VS.RRC.CONV.FC.Num.C APS Counter Description Number of RRC CONNECTION REQUESTS for CS Services in a Cell Under Cell Dynamic CAPS Flow Control
Description
This counter provides the number of RRC connection requests for voice services during CAPS flow control. This algorithm considers the ratio of RRC connection setup failures, CPU usage of the SPU subsystem, and congestion status of the NCP link. If the cause of an RRC connection request is "Originating Conversational Call" or "Terminating Conversational Call", the RNC determines that the request is originated by a voice service.
Measurement point
Upon receiving an RRC Connection Request message from a UE, the RNC determines whether to set up the RRC connection based on the flow control algorithm if dynamic CAPS flow control is being performed in the cell. If the RRC connection is not to be set up, the RNC checks whether the number of rejected RRC connection requests during the latest second is less than or equal to the preset maximum number of rejected RRC connection requests. If yes, the RNC responds the UE with an RRC Connection Reject message. If no, the RNC directly discards the RRC Connection Request message. This counter provides the number of rejected and discarded RRC connection requests for voice services during dynamic CAPS flow control in the cell.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.CONV.FC.Num.C APS Feature ID WRFD-040100 Feature Name Flow Control
1.12.38.33 Number of RRC Connection Setup Requests that carried System Information Container Stored Indication for CS services
Counters
Counter ID 73425017 Counter Name VS.RRC.AttConnEstab.Wit hSI.CsDomain Counter Description Number of RRC Connection Setup Requests that carried System Information Container Stored Indication for CS services
Description
This counter provides the number of RRC CONNECTION REQUEST messages that are for PS services, are received by the RNC from the UE, and carry the value TRUE for "System Information Container Stored Indication".
Measurement point
The measurement is triggered at point A as shown in the figure.When the RNC receives an RRC CONNECTION REQUEST message from the UE, if the value of "System Information Container Stored Indication" is TRUE and the domain indication is the CS domain, this counter is increased by one in the cell where the UE is camping on. Note that this counter is not triggered for a RRC CONNECTION REQUEST message that is retransmitted by the UE. Figure 1-1050 Procedure for successful RRC setup
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnEstab.Wit hSI.CsDomain Feature ID WRFD-140224 Feature Name Fast CS Fallback Based on RIM
1.12.38.34 Number of Successful RRC Connection Setups for CS services (RRC Connection Setup Requests that carried System Information Container Stored Indication) Counters
Counter ID 73425018 Counter Name VS.RRC.SuccConnEstab.W ithSI.CsDomain Counter Description Number of Successful RRC Connection Setups for CS services (RRC Connection Setup Requests that carried System Information Container Stored Indication)
Description
This counter provides the number of RRC CONNECTION SETUP COMPLETE messages that the RNC receives from the UE after the RNC receives RRC CONNECTION REQUEST messages that are from the UE, for CS services, and carry the value TRUE for "System Information Container Stored Indication". This counter is measured in the cell.
Measurement point
The measurement is triggered at point C as shown in the figure.When the RNC receives an RRC CONNECTION REQUEST message from the UE, if the value of "System Information Container Stored Indication" is TRUE, the domain indication is the CS domain, and the UE sends an RRC CONNECTION SETUP COMPLETE message to the RNC, this counter is increased by one in the cell that the UE camps on.
Issue 01 (2013-05-04)
2259
Figure 1-1051 Procedure for successful RRC setup
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.SuccConnEstab.W ithSI.CsDomain Feature ID WRFD-140224 Feature Name Fast CS Fallback Based on RIM
1.12.38.35 Number of RRC Connection Setup Requests that carried System Information Container Stored Indication for PS services Counters
Counter ID 73425019 Counter Name VS.RRC.AttConnEstab.Wit hSI.PsDomain Counter Description Number of RRC Connection Setup Requests that carried System Information Container Stored Indication for PS services
Issue 01 (2013-05-04)
2260
Description
This counter provides the number of RRC CONNECTION REQUEST messages that are for PS services, are received by the RNC from the UE, and carry the value TRUE for "System Information Container Stored Indication".
Measurement point
The measurement is triggered at point A as shown in the figure.When the RNC receives an RRC CONNECTION REQUEST message from the UE, if the value of "System Information Container Stored Indication" is TRUE and the domain indication is the PS domain, this counter is increased by one in the cell where the UE is camping on. Note that this counter is not triggered for a RRC CONNECTION REQUEST message that is retransmitted by the UE. Figure 1-1052 Procedure for successful RRC setup
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.AttConnEstab.Wit hSI.PsDomain Feature ID WRFD-140224 Feature Name Fast CS Fallback Based on RIM
Issue 01 (2013-05-04)
2261
1.12.38.36 Number of Successful RRC Connection Setups for PS services (RRC Connection Setup Requests that carried System Information Container Stored Indication) Counters
Counter ID 73425020 Counter Name VS.RRC.SuccConnEstab.W ithSI.PsDomain Counter Description Number of Successful RRC Connection Setups for PS services (RRC Connection Setup Requests that carried System Information Container Stored Indication)
Description
This counter provides the number of RRC CONNECTION SETUP COMPLETE messages that the RNC receives from the UE after the RNC receives RRC CONNECTION REQUEST messages that are from the UE, for PS services, and carry the value TRUE for "System Information Container Stored Indication". This counter is measured in the cell.
Measurement point
The measurement is triggered at point C as shown in the figure.When the RNC receives an RRC CONNECTION REQUEST message from the UE, if the value of "System Information Container Stored Indication" is TRUE, the domain indication is the PS domain, and the UE sends an RRC CONNECTION SETUP COMPLETE message to the RNC, this counter is increased by one in the cell that the UE camps on. Figure 1-1053 Procedure for successful RRC setup
Issue 01 (2013-05-04)
2262
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.SuccConnEstab.W ithSI.PsDomain Feature ID WRFD-140224 Feature Name Fast CS Fallback Based on RIM
1.12.38.37 Number of RRC Connection Setup Requests for Platinum UEs Performing Conversational Services for Cell Counters
Counter ID 73425914 Counter Name RRC.AttConnEstab.Conv.Pl atinum Counter Description Number of RRC Connection Setup Requests for Platinum UEs Performing Conversational Services for Cell
Description
This counter measures the number of RRC CONNECTION REQUEST messages (containing the cause values "Originating Conversational Call" and "Terminating Conversational Call") received by the RNC from platinum UEs.
Measurement point
The measurement is triggered at point A shown in the figure when the RNC receives an RRC CONNECTION REQUEST message from a UE and determines that the UE is a platinum user. In this case, this counter is measured in the cell that the UE camps on. Note that the measurement is not triggered for RRC CONNECTION REQUEST messages retransmitted by the UE.
Issue 01 (2013-05-04)
2263
Figure 1-1054 Procedure for successful RRC setup
Formula
None
Unit
None
Related Features
Counter Name RRC.AttConnEstab.Conv.Pl atinum Feature ID WRFD-150204 Feature Name Platinum User Prioritizing
1.12.38.38 Number of RRC Connection Setup Requests for Platinum UEs Performing Services for Cell Counters
Counter ID 73425915 Counter Name RRC.AttConnEstab.Platinum Counter Description Number of RRC Connection Setup Requests for Platinum UEs Performing Services for Cell
Issue 01 (2013-05-04)
2264
Description
This counter measures the number of RRC CONNECTION REQUEST messages received by the RNC from platinum UEs (without differentiating between cause values).
Measurement point
The measurement is triggered at point A shown in the figure when the RNC receives an RRC CONNECTION REQUEST message from a UE and determines that the UE is a platinum user. In this case, this counter is measured in the cell that the UE camps on, but excluding the number of rejected RRC connection requests caused by service-based redirections. Note that the measurement is not triggered for RRC CONNECTION REQUEST messages retransmitted by the UE. Figure 1-1055 Procedure for successful RRC setup
Formula
None
Unit
None
Related Features
Counter Name RRC.AttConnEstab.Platinum Feature ID WRFD-150204 Feature Name Platinum User Prioritizing
Issue 01 (2013-05-04)
2265
1.12.38.39 Number of Successful RRC Connection Setups for Platinum UEs Performing Conversational Services for Cell Counters
Counter ID 73425916 Counter Name RRC.SuccConnEstab.Conv. Platinum Counter Description Number of Successful RRC Connection Setups for Platinum UEs Performing Conversational Services for Cell
Description
This counter measures the number of RRC CONNECTION SETUP COMPLETE messages received by the RNC from platinum UEs (without differentiating between cause values).
Measurement point
The measurement is triggered at point C shown in the figure when the RNC receives an RRC CONNECTION SETUP COMPLETE message from a platinum UE. In this case, this counter is measured in the cell that the UE camps on. Figure 1-1056 Procedure for successful RRC setup
Formula
None
Unit
None
Related Features
Counter Name RRC.SuccConnEstab.Conv. Platinum Feature ID WRFD-150204 Feature Name Platinum User Prioritizing
1.12.38.40 Number of Successful RRC Connection Setups for Platinum UEs for Cell Counters
Counter ID 73425917 Counter Name RRC.SuccConnEstab.Platinum Counter Description Number of Successful RRC Connection Setups for Platinum UEs for Cell
Description
This counter measures the number of RRC CONNECTION SETUP COMPLETE messages received by the RNC from platinum UEs (with the cause values "Originating Conversational Call" and "Terminating Conversational Call").
Measurement point
The measurement is triggered at point C in the figure when the RNC receives an RRC CONNECTION SETUP COMPLETE message from a platinum UE and the corresponding RRC CONNECTION REQUEST message contains the cause value "Originating Conversational Call" or "Terminating Conversational Call." In this case, this counter is measured in the cell that the UE camps on. Figure 1-1057 Procedure for successful RRC setup
Issue 01 (2013-05-04)
2267
Formula
None
Unit
None
Related Features
Counter Name RRC.SuccConnEstab.Platinum Feature ID WRFD-150204 Feature Name Platinum User Prioritizing
1.12.39 RRC connection reject measurement per cell (RRC.SetupFail.Cell)

Overview
This function subset measures the number of failed RRC connection setups in a cell based on failure causes.
Issue 01 (2013-05-04)
2268
Issue 01 (2013-05-04)
2269
Table 1 describes the measurement points shown in Figure1. Measurement points A~D E F G Description See:RRC.Setup.Cell VS.RRC.FailConnEstab.NoReply VS.RRC.FC.Disc.Num VS.RRC.Rej.Redir.Service,VS.RRC.Rej.Re dir.Dist,VS.RRC.Rej.Redir.Dist.IntraRat,V S.RRC.Rej.Redir.CoMacroMicro VS.RRC.FailConnEstab.Cong VS.RRC.Rej.RL.Fail VS.RRC.Rej.TNL.Fail VS.RRC.Rej.Redir.InterRat,VS.RRC.Rej.R edir.IntraRat VS.RRC.Rej.Sum
H I J K L
Counters
Counter ID 67193609 Counter Name VS.RRC.Rej.ULPo wer.Cong Counter Description Number of RRC Connection Rejects for Cell (UL Power Congestion) Number of RRC Connection Rejects for Cell (DL Power Congestion) Number of RRC Connection Rejects during redirection between interfrequency cells for cell Number of RRC Connection Rejects during redirection between inter-RAT cells for cell Original Release V900R012
67193610
VS.RRC.Rej.DLPo wer.Cong
V900R012
67189473
VS.RRC.Rej.Redir. IntraRat
67189474
VS.RRC.Rej.Redir. InterRat
Issue 01 (2013-05-04)
2270
Counter ID 67196031
Counter Name VS.RRC.Rej.Redir. Service
Counter Description Number of RRC Connection Rejects Due to Service-based RRC Redirection for Cell Number of RRC Connection Rejects Due to Network Congestion for Cell Number of RRC Connection Rejects for Cell (UL Iub Bandwidth Congestion) Number of RRC Connection Rejects for Cell (DL Iub Bandwidth Congestion) Number of RRC Connection Rejects Due to Timeout of RRC CONNECT SETUP COMPLETE for Cell Number of RRC Connection Rejects for Cell (UL CE Resource Congestion) Number of RRC Connection Rejects for Cell (DL CE Resource Congestion) Number of RRC Connection Rejects for Cell (Code Resource Congestion) Number of RRC Connection Rejects Due to Radio Link Setup Failure for Cell
67179521
VS.RRC.FailConn Estab.Cong
67192608
VS.RRC.Rej.ULIU BBand.Cong
67192609
VS.RRC.Rej.DLIU BBand.Cong
67190401
VS.RRC.FailConn Estab.NoReply
67190404
VS.RRC.Rej.ULC E.Cong
67190405
VS.RRC.Rej.DLC E.Cong
67179524
VS.RRC.Rej.Code. Cong
67179525
VS.RRC.Rej.RL.F ail
Issue 01 (2013-05-04)
2271
Counter ID 67179527
Counter Name VS.RRC.Rej.TNL. Fail
Counter Description Number of RRC Connection Rejects for Cell (Transmission Setup Failure on Iub Interface ) Number of RRC Connection Rejects for Cell Number of DistanceBased RRC Redirections for Cell Number of Discarded RRC Connection Requests Due to Various Flow Control Functions for Cell Number of LowPriority RRC Connection Setup Requests Discarded During RAN Integrated Flow Control for Cell Number of MiddlePriority RRC Connection Setup Requests Discarded During RAN Integrated Flow Control for Cell Number of HighPriority RRC Connection Setup Requests Discarded During RAN Integrated Flow Control for Cell Number of DistanceBased RRC Interfrequency Redirections for Cell
67179300
VS.RRC.Rej.Sum
73421493
VS.RRC.Rej.Redir. Dist VS.RRC.FC.Disc.N um
73423468
V900R013
73393776
VS.LowPriRRC.Ra nFC.Disc.Num
V900R013
73393777
VS.NormPriRRC. RanFC.Disc.Num
V900R013
73393778
VS.HighPriRRC.R anFC.Disc.Num
V900R013
73424972
VS.RRC.Rej.Redir. Dist.IntraRat
V900R014
Issue 01 (2013-05-04)
2272
Counter ID 73425032
Counter Name VS.RRC.Rej.NodeBResUnavail
Counter Description Number of RRC Connection Rejects Due to NodeB Resource Unavailable Number of Outgoing Macro & Micro Joint Inter-frequency Redirections
73425833
VS.RRC.Rej.Redir. CoMacroMicro
V900R015
Counter VS.RRC.FailConnEstab.Cong Sub Counter VS.RRC.Rej.ULPower.Cong VS.RRC.Rej.DLPower.Cong VS.RRC.Rej.ULIUBBand.Cong VS.RRC.Rej.DLIUBBand.Cong VS.RRC.Rej.ULCE.Cong VS.RRC.Rej.DLCE.Cong VS.RRC.Rej.Code.Cong VS.RRC.Rej.NodeBResUnavail VS.RRC.Rej.Sum VS.RRC.FailConnEstab.Cong VS.RRC.Rej.RL.Fail VS.RRC.Rej.TNL.Fail
1.12.39.1 Number of RRC Connection Rejects (RRC Redirection Triggered by Access Failure) Counters
Counter ID 67189473 Counter Name VS.RRC.Rej.Redir.IntraRat Counter Description Number of RRC Connection Rejects during redirection between inter-frequency cells for cell
Issue 01 (2013-05-04)
2273
Description
These counters provide the number of RRC CONNECTION REJECT messages with interfrequency redirection information triggered by RRC admission failures in the cell. The counters are measured only in the case of resource admission failure. They are not measured in the case of service-based redirection.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC fails to set up the RRC connection for the UE and sends to the UE a RRC CONNECTION REJECT message with redirection information. In this case, this counter is measured in the cell where the UE camps on. Figure 1-1059 Procedure of RRC connection rejects
Formula
None
Unit
None
Issue 01 (2013-05-04)
2274
Related Features
Counter Name VS.RRC.Rej.Redir.IntraRat Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.39.2 Number of RRC Connection Rejects during redirection between interRAT cells Counters
Counter ID 67189474 Counter Name VS.RRC.Rej.Redir.InterRat Counter Description Number of RRC Connection Rejects during redirection between inter-RAT cells for cell
Description
These counters provide the number of RRC connection reject messages with inter-RAT redirection information triggered by RRC admission failure in the cell. This counter only measures the case of resource admission failure. The case of service-based redirection is not measured.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC fails to set up the RRC connection for the UE and sends to the UE a RRC CONNECTION REJECT message with redirection information. In this case, this counter is measured in the cell where the UE camps on.
Issue 01 (2013-05-04)
2275
Figure 1-1060 Procedure of RRC connection rejects
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Rej.Redir.InterRat Feature ID WRFD-02040003 WRFD-010510 Feature Name Inter System Redirect 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.39.3 Number of RRC Connection Rejects Due to Service-based RRC Redirection
Issue 01 (2013-05-04)
2276
Counters
Counter ID 67196031 Counter Name VS.RRC.Rej.Redir.Service Counter Description Number of RRC Connection Rejects Due to Service-based RRC Redirection for Cell
Description
This counter provides the number of RRC connection rejects due to service-based redirection in the cell. VS.RRC.Rej.Redir.IntraRat and VS.RRC.Rej.Redir.InterRat are not measured when the rejection is due to service-based redirection.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC fails to set up the RRC connection for the UE and sends to the UE a RRC CONNECTION REJECT message with redirection information. In this case, this counter is measured in the cell where the UE is located. Figure 1-1061 Service-based RRC redirection
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Rej.Redir.Service Feature ID WRFD-020120 WRFD-010510 Feature Name Service Steering and Load Sharing in RRC Connection Setup 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.39.4 Number of RRC Connection Rejects Due to Congestion Counters

Counter ID 67179521 Counter Name VS.RRC.FailConnEstab.Co ng Counter Description Number of RRC Connection Rejects Due to Network Congestion for Cell
Description
This counter provides the number of RRC CONNECTION REJECT messages sent by the RNC to the UE due to network congestion after the RNC receives a RRC CONNECTION REQUEST message from the UE.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a RRC CONNECTION REJECT message to the UE with the reject cause of congestion.
Issue 01 (2013-05-04)
2278
Figure 1-1062 Procedure for RRC connection rejects
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.FailConnEstab.Co ng Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.39.5 Number of RRC Connection Rejects (Radio Resource Congestion)
Issue 01 (2013-05-04)
2279
Counters
Counter ID 67192608 Counter Name VS.RRC.Rej.ULIUBBand.C ong VS.RRC.Rej.ULPower.Con g VS.RRC.Rej.DLPower.Con g VS.RRC.Rej.DLIUBBand.C ong VS.RRC.Rej.ULCE.Cong Counter Description Number of RRC Connection Rejects for Cell (UL Iub Bandwidth Congestion) Number of RRC Connection Rejects for Cell (UL Power Congestion) Number of RRC Connection Rejects for Cell (DL Power Congestion) Number of RRC Connection Rejects for Cell (DL Iub Bandwidth Congestion) Number of RRC Connection Rejects for Cell (UL CE Resource Congestion) Number of RRC Connection Rejects for Cell (DL CE Resource Congestion) Number of RRC Connection Rejects for Cell (Code Resource Congestion)
67193609
67193610
67192609
67190404
67190405
VS.RRC.Rej.DLCE.Cong
67179524
VS.RRC.Rej.Code.Cong
Description
These counters provide the numbers of RRC CONNECTION REJECT messages sent by the RNC to the UE according to different congestion reasons in the cell.If congestion occurs on both the uplink and downlink, only the related downlink counter is measured. For example, if an RRC connection setup attempt is rejected due to the congestion on both the uplink and downlink, only the counter VS.RRC.Rej.DLPower.Cong is measured.
Measurement point
The measurement is triggered at point A as shown in the figure. After receiving a RRC CONNECTION REQUEST message from the UE, the RNC initiates admission procedures for resources of code, power, CE, and Iub bandwidth. If the resource admission fails, the RNC sends a RRC CONNECTION REJECT message to the UE. In this case, the corresponding counter is measured according to the reject reason in the cell where the UE is located.
Issue 01 (2013-05-04)
2280
Figure 1-1063 RRC resource admission failure
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Rej.ULIUBBand.C ong Feature ID WRFD-020101 WRFD-010510 Feature Name Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RRC.Rej.ULPower.Con g
WRFD-020101 WRFD-010510
Issue 01 (2013-05-04)
2281
Counter Name VS.RRC.Rej.DLPower.Con g
Feature Name Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Admission Control 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
VS.RRC.Rej.DLIUBBand.C ong
WRFD-020101 WRFD-010510
VS.RRC.Rej.ULCE.Cong
WRFD-020101 WRFD-010510
VS.RRC.Rej.DLCE.Cong
WRFD-020101 WRFD-010510
VS.RRC.Rej.Code.Cong
WRFD-020101 WRFD-010510
1.12.39.6 Number of RRC Connection Rejects Due to Timeout of RRC CONNECT SETUP COMPLETE Counters
Counter ID 67190401 Counter Name VS.RRC.FailConnEstab.No Reply Counter Description Number of RRC Connection Rejects Due to Timeout of RRC CONNECT SETUP COMPLETE for Cell
Issue 01 (2013-05-04)
2282
Description
This counter provides the number of RRC CONNECT SETUP COMPLETE messages that the RNC fails to receive from the UE before the timer expires after the RNC sends a RRC CONNECT SETUP message to the UE.
Measurement point
The measurement is triggered at point A as shown in the figure, if the RNC fails to receive a RRC CONNECT SETUP COMPLETE message from the UE before the timer expires after the RNC sends the RRC CONNECT SETUP message to the UE. In this case, this counter is measured in the cell where the UE is located. Figure 1-1064 Timeout of RRC connection setup completion
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.FailConnEstab.No Reply Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
2283
Issue 01 (2013-05-04)
1.12.39.7 Number of RRC Connection Rejects Due to Radio Link Setup Failure Counters
Counter ID 67179525 Counter Name VS.RRC.Rej.RL.Fail Counter Description Number of RRC Connection Rejects Due to Radio Link Setup Failure for Cell
Description
This counter provides the number of RRC CONNECTION REJECT messages sent by the RNC to the UE due to RL setup failures on the Iub interface after the RNC receives an RRC CONNECTION REQUEST message from the UE. Note that if the NodeB responds with a radio link configuration failure message with the cause of CE resource insufficiency, this counter is not measured. This counter is also not measured if phase 1 of E2E flow control is enabled and the cause value contained in the RADIO LINK SETUP FAIL message responded by the NodeB is "Control processing overload" or "NodeB Resources Unavailable". The mapped value of the two causes in the RRC CONNECTION REJECT message is congestion.
Measurement point
The measurement can be triggered at point B as shown in the figure. When the RNC receives a RRC CONNECTION REQUEST message from the UE, the RNC starts a radio link setup procedure. After receiving a RADIO LINK SETUP FAIL message from the NodeB, the RNC sends a RRC CONNECTION REJECT message to the UE. In this case, this counter is measured in the cell where the UE is located.
Issue 01 (2013-05-04)
2284
Figure 1-1065 Radio link setup failure
The measurement can be also triggered at point B as shown in the figure. When the RNC receives a RRC CONNECTION REQUEST message from the UE, the RNC starts a radio link setup procedure. If the RNC fails to receive a RADIO LINK SETUP RESPONSE message from the NodeB before the timer expires, the RNC sends a RRC CONNECTION REJECT to the UE. In this case, this counter is measured in the cell where the UE is located.
Issue 01 (2013-05-04)
2285
Figure 1-1066 Radio link setup timeout
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Rej.RL.Fail Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.39.8 Number of RRC Connection Rejects (Transmission Setup Failure on Iub Interface )
Issue 01 (2013-05-04)
2286
Counters
Counter ID 67179527 Counter Name VS.RRC.Rej.TNL.Fail Counter Description Number of RRC Connection Rejects for Cell (Transmission Setup Failure on Iub Interface )
Description
This counter provides the number of RRC CONNECTION REJECT messages sent by the RNC to the UE due to transmission setup failure on the Iub interface after the RNC receives a RRC CONNECTION REQUEST message from the UE.
Measurement point
The measurement is triggered at point B as shown in the figure. After the RNC and the NodeB complete the radio link setup procedure, the RNC starts an ALCAP transmission setup procedure on the Iub interface. If the ALCAP transmission setup fails, the RNC sends a RRC CONNECTION REJECT message to the UE. In this case, this counter is measured in the cell where the UE is located. Figure 1-1067 Procedure for RRC connection rejects
Issue 01 (2013-05-04)
2287
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Rej.TNL.Fail Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.39.9 Number of RRC Connection Rejects Counters

Counter ID 67179300 Counter Name VS.RRC.Rej.Sum Counter Description Number of RRC Connection Rejects for Cell
Description
This counter provides the number of RRC connection rejects in the cell. This counter excludes the number of RRC connection rejects caused by service-based redirection and distance-based redirection.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a RRC CONNECTION REJECT message to reject the RRC connection after receiving a RRC CONNECTION REQUEST message from the UE. In this case, this counter is measured according to the cell where the UE is located. This counter excludes the number of RRC connection rejects caused by service-based redirection and distance-based redirection.
Issue 01 (2013-05-04)
2288
Figure 1-1068 Procedure of RRC connection rejects
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Rej.Sum Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.39.10 Number of Distance-Based RRC Redirections for Cell Counters

Counter ID 73421493 Counter Name VS.RRC.Rej.Redir.Dist Counter Description Number of Distance-Based RRC Redirections for Cell
2289
Issue 01 (2013-05-04)
Counter ID 73424972
Counter Name VS.RRC.Rej.Redir.Dist.IntraRat
Counter Description Number of Distance-Based RRC Inter-frequency Redirections for Cell
Description
This counter provides the number of RRC connection rejects due to distance-based redirection in the cell. The VS.RRC.Rej.Redir.Dist counter provides the number of inter-RAT redirections and inter-frequency redirections. The VS.RRC.Rej.Redir.Dist.IntraRat counter provides only the number of inter-RAT redirections. VS.RRC.Rej.Redir.IntraRat and VS.RRC.Rej.Redir.InterRat are not measured when the rejection is triggered by distance-based redirection.
Measurement point
As shown by A in Figure 1, when the RNC determines that a distance-based inter-RAT or interfrequency redirection needs to be performed and the RNC sends the UE an RRC CONNECTION REJECT message that carries redirection information,this counter is increased by one in the cell where the UE is camping. Figure 1-1069 Distance-Based RRC redirection
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Rej.Redir.Dist Feature ID WRFD-02040003 WRFD-02040005 WRFD-020401 Feature Name Inter System Redirect Inter-Frequency Redirection Based on Distance Inter-RAT Redirection Based on Distance VS.RRC.Rej.Redir.Dist.IntraRat WRFD-02040005 Inter-Frequency Redirection Based on Distance
1.12.39.11 Number of Discarded RRC Connection Requests Due to Various Flow Control Functions Counters
Counter ID 73423468 Counter Name VS.RRC.FC.Disc.Num Counter Description Number of Discarded RRC Connection Requests Due to Various Flow Control Functions for Cell
Description
This counter provides the number of RRC connection requests discarded by various flow control functions such as CPU usage, MPU overload, RRC queuing, RAN integrated flow control, cell dynamic CAPS flow control in a cell.
Measurement point
The measurement is triggered when an RRC connection request is discarded in a cell. This counter measures only the discarded requests but does not measure the rejection messages sent due to flow control.
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.FC.Disc.Num Feature ID WRFD-040100 Feature Name Flow Control
1.12.39.12 Number of RRC Connection Requests of Different Priorities Discarded During RAN Integrated Flow Control for Cell Counters
Counter ID 73393776 Counter Name VS.LowPriRRC.RanFC.Dis c.Num Counter Description Number of Low-Priority RRC Connection Setup Requests Discarded During RAN Integrated Flow Control for Cell Number of Middle-Priority RRC Connection Setup Requests Discarded During RAN Integrated Flow Control for Cell Number of High-Priority RRC Connection Setup Requests Discarded During RAN Integrated Flow Control for Cell
73393777
VS.NormPriRRC.RanFC.Di sc.Num
73393778
VS.HighPriRRC.RanFC.Dis c.Num
Description
These counters provide the number of RRC connection requests of different priorities discarded in a cell in phase 2 of RAN integrated flow control. In this phase, the RNC performs RAN integrated flow control based on NodeB-reported CPU load information.
Measurement point
After receiving an RRC CONNECTION REQUEST message from a UE, the RNC determines whether to set up the RRC connection based on the flow control algorithm if RAN integrated flow control is being performed in the cell. If the RNC determines that the RRC connection will not be set up, the subsequent procedure is as follows: If the current number of RRC connection rejections does not exceed the configured RRC connection rejection threshold, the RNC responds to the UE with an RRC CONNECTION REJECT message.
Otherwise, the RNC discards the RRC CONNECTION REQUEST message directly and measures the number of discarded RRC connection requests.
Formula
None
Unit
None
Related Features
Counter Name VS.LowPriRRC.RanFC.Dis c.Num VS.NormPriRRC.RanFC.Di sc.Num VS.HighPriRRC.RanFC.Dis c.Num Feature ID WRFD-040100 WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control Flow Control
1.12.39.13 Number of RRC Connection Rejects Due to NodeB Resource Unavailable Counters
Counter ID 73425032 Counter Name VS.RRC.Rej.NodeBResUnavail Counter Description Number of RRC Connection Rejects Due to NodeB Resource Unavailable
Description
This counter provides the number of RRC CONNECTION REJECT messages sent by the RNC to the UE due to RL setup failures on the Iub interface after the RNC receives an RRC CONNECTION REQUEST message from the UE. Note that in this counter, the cause value for RL setup failures is "NodeB Resources Unavailable" and the cause value for the RRC CONNECTION REJECT message is congestion.
Measurement point
The measurement is triggered at point B shown in the following figure. When the RNC receives a RRC CONNECTION REQUEST message from the UE, the RNC starts a radio link setup procedure. After receiving a RADIO LINK SETUP FAIL message with the cause of NodeB Resources Unavailable from the NodeB, the RNC sends a RRC CONNECTION REJECT message to the UE and the cause value contained in this message is congestion.In this case, this counter is increased by one in the cell where the UE is located.
Figure 1-1070 Radio link setup failure
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Rej.NodeBResUnavail Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.12.39.14 Number of Outgoing Macro & Micro Joint Inter-frequency Redirections
Issue 01 (2013-05-04)
2294
Counters
Counter ID 73425833 Counter Name VS.RRC.Rej.Redir.CoMacroMicro Counter Description Number of Outgoing Macro & Micro Joint Interfrequency Redirections
Description
This counter provides the number of outgoing macro & micro joint inter-frequency redirections.
Measurement point
This measurement is triggered at point A in figure 2. The RNC determines that a UE is in the macro & micro joint inter-frequency handover area and triggers a macro & micro joint interfrequency redirection. This counter is increased by one in the serving cell where the UE camps each time the RNC sends an RRC CONNECTION REJECT message to the UE.
Issue 01 (2013-05-04)
2295
Figure 1-1072 Macro and micro joint inter-frequency RRC redirection
Formula
None
Unit
None
Related Features
Counter Name VS.RRC.Rej.Redir.CoMacroMicro Feature ID WRFD-150201 WRFD-15020101 Feature Name Macro & Micro Co-carrier Uplink Interference Control Macro & Micro Joint Interfrequency Redirection
1.12.40 RRC state measurement<Cell>(RRC.State.Cell)

Overview
This function subset provides the average number of UEs in different RRC connection states in the cell.
Issue 01 (2013-05-04)
2296
Counters
Counter ID 73410510 Counter Name VS.CellDCHUEs Counter Description Number of UEs in CELL_DCH State for Cell Number of UEs in CELL_FACH State for Cell Number of UEs in CELL_PCH State for Cell Maximum Count of UE in CELL_FACH Original Release Earlier than V900R011 Earlier than V900R011 V900R012
73410511
VS.CellFACHUEs
73410513
VS.CellPCHUEs
73426285
VS.CellFACHUEs. MAX
V900R015
None
1.12.40.1 Counters Related to the Number of UEs in Different RRC Connection States Counters
Counter ID 73410510 73410511 73410513 73426285 Counter Name VS.CellDCHUEs VS.CellFACHUEs VS.CellPCHUEs VS.CellFACHUEs.MAX Counter Description Number of UEs in CELL_DCH State for Cell Number of UEs in CELL_FACH State for Cell Number of UEs in CELL_PCH State for Cell Maximum Count of UE in CELL_FACH
Description
These counters provide the number of UEs in different RRC connection states.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of UEs in different RRC connection states. At the end of the measurement period, by dividing the accumulated value
of sample data in the period by the number of samples, the average and Maximum number of UEs in each RRC connection state in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Name VS.CellDCHUEs Feature ID WRFD-010202 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
VS.CellFACHUEs
WRFD-010202
VS.CellPCHUEs
WRFD-010202
VS.CellFACHUEs.MAX
WRFD-010202
1.12.41 UE Capability Measurement per cell(RRC.UECapab.Cell)

Overview
he RRC.UECapab.Cell counter provides the number of times that the RNC receives the RRC CONNECTION SETUP COMPLETE message from the UE in a cell. This counter is measured according to the UE capability information contained in the RRC CONNECTION SETUP COMPLETE message.
Issue 01 (2013-05-04)
2298
Counters
Counter ID 73425958 Counter Name RRC.SuccConnEst ab.HSDSCH.AllCA T Counter Description Number of Successful RRC Connection Setups for Cell (Including All the HS-DSCH Physical Layer Categories) Number of Successful RRC Connection Setups for Cell (including the HS-DSCH Physical Layer Categories 7 Through 10) Number of Successful RRC Connection Setups for Cell (including the HS-DSCH Physical Layer Categories 13 and 14) Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Categories 15 and 16) Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Categories 17 Through 20) Original Release V900R015
73425959
RRC.SuccConnEst ab.HSDSCH.CAT7 .10
V900R015
73425960
RRC.SuccConnEst ab.HSDSCH.CAT1 3.14
V900R015
73425961
V900R015
73425962
V900R015
Issue 01 (2013-05-04)
2299
Counter ID 73425963
Counter Name RRC.SuccConnEst ab.HSDSCH.CAT2 1.24
Counter Description Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Categories 21 Through 24) Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Categories 25 Through 28) Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Category 29) Number of Successful RRC Connection Establishments for Cell (Including the HS-DSCH Physical Layer Category 30) Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Category 31) Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Category 32)
73425964
V900R015
73425965
RRC.SuccConnEst ab.HSDSCH.CAT2 9
V900R015
73425966
V900R015
73425967
V900R015
73425968
V900R015
Issue 01 (2013-05-04)
2300
Counter ID 73425969
Counter Name RRC.SuccConnEst ab.EDCH.AllCAT
Counter Description Number of Successful RRC Connection Setups for Cell (Including All the E-DCH Physical Layer Categories) Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 2) Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 4) Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 5) Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 6) Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 7) Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 8)
73425970
RRC.SuccConnEst ab.EDCH.CAT2
V900R015
73425971
V900R015
73425972
V900R015
73425973
V900R015
73425974
V900R015
73425975
V900R015
Issue 01 (2013-05-04)
2301
Counter ID 73425976
Counter Name RRC.SuccConnEst ab.EDCH.CAT9
Counter Description Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 9)
Counter RRC.SuccConnEstab.HSDSCH.AllCAT Sub Counter RRC.SuccConnEstab.HSDSCH.CAT7.10 RRC.SuccConnEstab.HSDSCH.CAT13.14 RRC.SuccConnEstab.HSDSCH.CAT15.16 RRC.SuccConnEstab.HSDSCH.CAT17.20 RRC.SuccConnEstab.HSDSCH.CAT21.24 RRC.SuccConnEstab.HSDSCH.CAT25.28 RRC.SuccConnEstab.HSDSCH.CAT29 RRC.SuccConnEstab.HSDSCH.CAT30 RRC.SuccConnEstab.HSDSCH.CAT31 RRC.SuccConnEstab.HSDSCH.CAT32 RRC.SuccConnEstab.EDCH.AllCAT RRC.SuccConnEstab.EDCH.CAT2 RRC.SuccConnEstab.EDCH.CAT4 RRC.SuccConnEstab.EDCH.CAT5 RRC.SuccConnEstab.EDCH.CAT6 RRC.SuccConnEstab.EDCH.CAT7 RRC.SuccConnEstab.EDCH.CAT8 RRC.SuccConnEstab.EDCH.CAT9
1.12.41.1 Number of Successful RRC Connection Setups (Including All the HSDSCH Physical Layer Categories)
Issue 01 (2013-05-04)
2302
Counters
Counter ID 73425958 Counter Name RRC.SuccConnEstab.HSDS CH.AllCAT Counter Description Number of Successful RRC Connection Setups for Cell (Including All the HS-DSCH Physical Layer Categories) Number of Successful RRC Connection Setups for Cell (including the HS-DSCH Physical Layer Categories 7 Through 10) Number of Successful RRC Connection Setups for Cell (including the HS-DSCH Physical Layer Categories 13 and 14) Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Categories 15 and 16) Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Categories 17 Through 20) Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Categories 21 Through 24) Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Categories 25 Through 28) Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Category 29) Number of Successful RRC Connection Establishments for Cell (Including the HSDSCH Physical Layer Category 30)
73425959
RRC.SuccConnEstab.HSDS CH.CAT7.10
73425960
73425961
73425962
73425963
73425964
73425965
RRC.SuccConnEstab.HSDS CH.CAT29
73425966
Issue 01 (2013-05-04)
2303
Counter ID 73425967
Counter Name RRC.SuccConnEstab.HSDS CH.CAT31
Counter Description Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Category 31) Number of Successful RRC Connection Setups for Cell (Including the HS-DSCH Physical Layer Category 32)
73425968
Description
These counters provide the number of times that the RNC receives an RRC CONNECTION SETUP COMPLETE message from a UE. These counters are measured based on the value of the "HS-DSCH physical layer category" information element (IE) in the RRC CONNECTION SETUP COMPLETE message. 1) The RRC.SuccConnEstab.HSDSCH.AllCAT counter measures the number of successful RRC connection setups with the "HS-DSCH physical layer category" IE. 2) Other counters measure the number of successful RRC connection setups with different values of the "HS-DSCH physical layer category" IE. These values are the maximum values between basic IEs and extension IEs.
Measurement point
The measurement is triggered at point C as shown in the figure when the RNC receives an RRC CONNECTION SETUP COMPLETE message from the UE. These counters are measured in the cell where the UE camps based on the value of the "HS-DSCH physical layer category" IE in the RRC CONNECTION SETUP COMPLETE message. The value is the maximum value between the basic IE and extension IE. For details about HS-DSCH physical layer categories, see Table 5.1a: FDD HS-DSCH physical layer categories in 3GPP TS 25.306.
Issue 01 (2013-05-04)
2304
Formula
None
Unit
None
Related Features
Counter Name RRC.SuccConnEstab.HSDS CH.AllCAT Feature ID WRFD-01061002 WRFD-010699 WRFD-150207 WRFD-150223 RRC.SuccConnEstab.HSDS CH.CAT7.10 RRC.SuccConnEstab.HSDS CH.CAT13.14 RRC.SuccConnEstab.HSDS CH.CAT15.16 RRC.SuccConnEstab.HSDS CH.CAT17.20
Issue 01 (2013-05-04)
Feature Name HSDPA UE Category 1 to 28 DC-HSDPA+MIMO 4C-HSDPA 4C-HSDPA+MIMO HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28 HSDPA UE Category 1 to 28
2305
Counter Name RRC.SuccConnEstab.HSDS CH.CAT21.24 RRC.SuccConnEstab.HSDS CH.CAT25.28 RRC.SuccConnEstab.HSDS CH.CAT29 RRC.SuccConnEstab.HSDS CH.CAT30 RRC.SuccConnEstab.HSDS CH.CAT31 RRC.SuccConnEstab.HSDS CH.CAT32
Feature Name HSDPA UE Category 1 to 28 DC-HSDPA+MIMO 4C-HSDPA 4C-HSDPA+MIMO 4C-HSDPA 4C-HSDPA+MIMO
1.12.41.2 Number of Successful RRC Connection Setups for Cell (Including All the E-DCH Physical Layer Categories) Counters
Counter ID 73425969 Counter Name RRC.SuccConnEstab.EDCH .AllCAT Counter Description Number of Successful RRC Connection Setups for Cell (Including All the E-DCH Physical Layer Categories) Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 2) Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 4) Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 5) Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 6)
73425970
RRC.SuccConnEstab.EDCH .CAT2
73425971
73425972
73425973
Issue 01 (2013-05-04)
2306
Counter ID 73425974
Counter Name RRC.SuccConnEstab.EDCH .CAT7
Counter Description Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 7) Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 8) Number of Successful RRC Connection Setups for Cell (Including the E-DCH Physical Layer Category 9)
73425975
73425976
Description
These counters provide the number of times that the RNC receives an RRC CONNECTION SETUP COMPLETE message from a UE. These counters are measured based on the value of the "E-DCH physical layer category" information element (IE) in the RRC CONNECTION SETUP COMPLETE message. 1) The RRC.SuccConnEstab.HSDSCH.AllCAT counter measures the number of successful RRC connection setups with the "E-DCH physical layer category" IE. 2) Other counters measure the number of successful RRC connection setups with different values of the "E-DCH physical layer category" IE. These values are the maximum values between basic IEs and extension IEs.
Measurement point
The measurement is triggered at point C as shown in the figure when the RNC receives an RRC CONNECTION SETUP COMPLETE message from the UE. These counters are measured in the cell where the UE camps based on the value of the "E-DCH physical layer category" IE in the RRC CONNECTION SETUP COMPLETE message. The value is the maximum value between the basic IE and extension IE. For details about E-DCH physical layer categories, see Table 5.1g: FDD E-DCH physical layer categories in 3GPP TS 25.306.
Issue 01 (2013-05-04)
2307
Formula
None
Unit
None
Related Features
Counter Name RRC.SuccConnEstab.EDCH .AllCAT RRC.SuccConnEstab.EDCH .CAT2 RRC.SuccConnEstab.EDCH .CAT4 RRC.SuccConnEstab.EDCH .CAT5 RRC.SuccConnEstab.EDCH .CAT6 RRC.SuccConnEstab.EDCH .CAT7
Issue 01 (2013-05-04)
Feature Name HSUPA UE Category Support HSUPA UE Category Support HSUPA UE Category Support HSUPA UE Category Support HSUPA UE Category Support HSUPA UE Category Support
2308
Counter Name RRC.SuccConnEstab.EDCH .CAT8 RRC.SuccConnEstab.EDCH .CAT9
Feature Name HSUPA UE Category Support HSUPA UE Category Support
1.12.42 Cell TX and RX Power Measurement per cell (RTWPTCP.Cell)

Overview
The function subset provides the uplink interference and downlink power consumption of a cell, which are used to assess the cell load. After a cell is set up, the NodeB periodically sends the RNC RTWP-related COMMON MEASUREMENT REPORT messages and TCP-related COMMON MEASUREMENT REPORT messages if transmit power and receive power are required. After HSPA is introduced, the following HSPA-related measurements are added: nonHSPA power (Transmitted Carrier Power Of All Codes Not Used For HSTransmission in 3GPP TS 25.433), HSDPA required power (HS-DSCH Required Power in 3GPP TS 25.433), and power for HSUPA scheduling (Received Scheduled E-DCH Power Share in 3GPP TS 25.433). The RNC obtains measurement values through COMMON MEASUREMENT REPORT messages periodically send by the NodeB. You can run [CMD]SET ULDM[/CMD]to configure measurement periods.
Counters
Counter ID 67199680 Counter Name VS.MaxRTWP Counter Description Maximum Power of Totally Received Bandwidth for Cell Minimum Power of Totally Received Bandwidth for Cell Mean Power of Totally Received Bandwidth for Cell Maximum Transmitted Power of Carrier for Cell Minimum Transmitted Power of Carrier for Cell Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67199681
VS.MinRTWP
67199617
VS.MeanRTWP
67199682
VS.MaxTCP
67199683
VS.MinTCP
Issue 01 (2013-05-04)
2309
Counter ID 67199618
Counter Name VS.MeanTCP
Counter Description Mean Transmitted Power of Carrier for Cell Maximum NonHSDPA Transmitted Carrier Power for Cell Minimum NonHSDPA Transmitted Carrier Power for Cell Mean Non-HSDPA Transmitted Carrier Power for Cell Maximum Power Required by HSDSCH for Cell Minimum Power Required by HSDSCH for Cell Mean Power Required by HSDSCH for Cell Average Received Scheduled E-DCH Power Share for Cell Maximum Received Scheduled E-DCH Power Share for Cell Minimum Received Scheduled E-DCH Power Share for Cell Maximum Power Required for Free HSDPA Users for Cell Average Power Required for Free HSDPA Users for Cell
67202900
VS.MaxTCP.NonH S
67202901
VS.MinTCP.NonH S
67202902
VS.MeanTCP.Non HS VS.HSDPA.MaxRe quiredPwr VS.HSDPA.MinRe quiredPwr VS.HSDPA.MeanR equiredPwr VS.HSUPA.MeanRSEPS VS.HSUPA.MaxRSEPS VS.HSUPA.MinRSEPS VS.HSDPA.MaxRe quiredPwr.Free
Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 V900R012
67202982
67202983
67202984
73415859
73403758
V900R012
73403760
V900R012
73441143
V900R013
73441144
VS.HSDPA.MeanR equiredPwr.Free
V900R013
Issue 01 (2013-05-04)
2310
Counter ID 73425896
Counter Name VS.HSDPA.MC.M eanRequiredPwr
Counter Description Power Required by 4C-HSDPA/DBHSDPA/DCHSDPA UEs for Cell Maximum Power Required by 4CHSDPA/DBHSDPA/DCHSDPA UEs for Cell Minimum Power Required by 4CHSDPA/DBHSDPA/DCHSDPA UEs for Cell Average DL Transmit Power of 4C-HSDPA/DBHSDPA/DCHSDPA UEs for Cell Maximum DL Transmit Power of 4C-HSDPA/DBHSDPA/DCHSDPA UEs for Cell Minimum DL Transmit Power of 4C-HSDPA/DBHSDPA/DCHSDPA UEs for Cell
73425901
VS.HSDPA.MC.M axRequiredPwr
V900R015
73425903
VS.HSDPA.MC.Mi nRequiredPwr
V900R015
73425905
VS.MeanTCP.HSD PA.MC
V900R015
73425910
VS.MaxTCP.HSDP A.MC
V900R015
73425912
VS.MinTCP.HSDP A.MC
V900R015
Counter VS.MaxTCP VS.MinTCP VS.MeanTCP Sub Counter VS.MaxTCP.NonHS VS.MinTCP.NonHS VS.MeanTCP.NonHS
1.12.42.1 Received Total Wideband Power for cell
Issue 01 (2013-05-04)
2311
Counters
Counter ID 67199617 67199680 67199681 Counter Name VS.MeanRTWP VS.MaxRTWP VS.MinRTWP Counter Description Mean Power of Totally Received Bandwidth for Cell Maximum Power of Totally Received Bandwidth for Cell Minimum Power of Totally Received Bandwidth for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67180641 Counter Name VS.RTWP.CUM Counter Description Accumulated Totally Received Bandwidth Power for Cell Number of the Totally Received Bandwidth Power for Cell
67180642
VS.RTWP.SAMPLE
Description
These counters provide the received total wideband power (RTWP) measurement values of a cell for assessing the uplink interference level and uplink loads in the cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the NodeB a COMMON MEASUREMENT REPORT message about the RTWP of a cell every 1s. The RNC averages the reported measurement values every 5s to obtain the RTWP of the cell in which the measurement is performed. At the end of the measurement period, the RNC divides the accumulated numbers by the number of samples to obtain the value of VS.MeanRTWP in the measurement period. The maximum and minimum sampled values are taken as the values of VS.MaxRTWP and VS.MinRTWP.
Issue 01 (2013-05-04)
2312
Figure 1-1075 Common measurement report procedure
Formula
VS.MeanRTWP = ([VS.RTWP.CUM]/[VS.RTWP.SAMPLE]-{1121})/{10}
Unit
dBm
Related Features
Counter Name VS.MeanRTWP VS.MaxRTWP VS.MinRTWP Feature ID WRFD-020102 WRFD-020102 WRFD-020102 Feature Name Load Measurement Load Measurement Load Measurement
1.12.42.2 Transmitted Power of Carrier for Cell
Issue 01 (2013-05-04)
2313
Counters
Counter ID 67199618 67199682 67199683 Counter Name VS.MeanTCP VS.MaxTCP VS.MinTCP Counter Description Mean Transmitted Power of Carrier for Cell Maximum Transmitted Power of Carrier for Cell Minimum Transmitted Power of Carrier for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67204826 Counter Name VS.TCP.CUM.NoLog Counter Description Cumulated Transmitted Power of Carrier of Cell (Before Log Calculation) Number of Received Measurement Reports for Transmitted Power of Carrier for Cell
67180648
VS.TCP.SAMPLE
Description
These counters provide the transmitted carrier power (TCP) measurement values of a cell for assessing the downlink load state in the cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the NodeB a COMMON MEASUREMENT REPORT message about the RTWP of a cell every 1s. The RNC averages the reported measurement values every 5s to obtain the TCP at a sampling point. At the end of the measurement period, the RNC divides the accumulated numbers by the number of samples to obtain the value of VS.MeanTCP in the measurement period. The maximum and minimum sampled values are taken as the values of VS.MaxTCP and VS.MinTCP.
Issue 01 (2013-05-04)
2314
Formula
VS.MeanTCP = {10}*(log10[VS.TCP.CUM.NoLog]-log10[VS.TCP.SAMPLE])
Unit
dBm
Related Features
Counter Name VS.MeanTCP VS.MaxTCP VS.MinTCP Feature ID WRFD-020102 WRFD-020102 WRFD-020102 Feature Name Load Measurement Load Measurement Load Measurement
1.12.42.3 Transmitted Power of Non-HSDPA Carrier for Cell
Issue 01 (2013-05-04)
2315
Counters
Counter ID 67202902 Counter Name VS.MeanTCP.NonHS Counter Description Mean Non-HSDPA Transmitted Carrier Power for Cell Maximum Non-HSDPA Transmitted Carrier Power for Cell Minimum Non-HSDPA Transmitted Carrier Power for Cell
67202900
VS.MaxTCP.NonHS
67202901
VS.MinTCP.NonHS
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67204827 Counter Name VS.TCP.NonHS.CUM.NoLog VS.TCP.NonHS.SAMPLE Counter Description Non-HSDPA Transmitted Carrier Power for Cell (Before Log Calculation) Number of Received Measurement Reports of Non-HSDPA Transmitted Carrier Power for Cell
67190621
Description
These counters provide the downlink non-HSPA TCP measurement values of a cell for assessing downlink non-HSPA power load state in the cell. After HSPA is introduced, cell loads are classified into non-HSPA power loads and HSPA power loads. HSPA power is the power used to transmit data on the HS-PDSCH, HS-SCCH, E-AGCH, ERGCH, and E-HICH. Non-HSPA power is the power used to transmit data on the common channels, DPDCH, and DPCCH, including power consumed by loads on the DPCCH and DPDCH when HSDPA users use SRB over DCH.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the NodeB a COMMON MEASUREMENT REPORT message about the non-HSDPA TCP of a cell every 1s. The RNC averages the reported measurement values every 5s to obtain the nonHSDPA TCP at a sampling point. At the end of the measurement period, the RNC divides the accumulated numbers by the number of samples to obtain the value of VS.MeanNonTCP in the
measurement period. The maximum and minimum sampled values are taken as the values of VS.MaxNonTCP and VS.MinNonTCP. Figure 1-1077 Common measurement report procedure
Formula
VS.MeanTCP.NonHS = {10}*(log10[VS.TCP.NonHS.CUM.NoLog]-log10 [VS.TCP.NonHS.SAMPLE])
Unit
dBm
Related Features
Counter Name VS.MeanTCP.NonHS VS.MaxTCP.NonHS VS.MinTCP.NonHS Feature ID WRFD-020102 WRFD-020102 WRFD-020102 Feature Name Load Measurement Load Measurement Load Measurement
1.12.42.4 Power Required by HS-DSCH for Cell
Issue 01 (2013-05-04)
2317
Counters
Counter ID 67202984 67202982 67202983 Counter Name VS.HSDPA.MeanRequiredPwr VS.HSDPA.MaxRequiredPwr VS.HSDPA.MinRequiredPwr Counter Description Mean Power Required by HS-DSCH for Cell Maximum Power Required by HS-DSCH for Cell Minimum Power Required by HS-DSCH for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67204828 Counter Name VS.HSDPA.RequiredPwr.C UM.NoLog VS.HSDPA.RequiredPwr.S AMPLE Counter Description Cumulated Power Required by HS-DSCH for Cell (Before Log Calculation) Number of Received Measurement Reports for Power Required by HSDSCH in dBm for Cell
67191149
Description
These counters provide the measurement values of power required to meet the guaranteed bit rate (GBR) for HSDPA users in an HSDPA cell. For details, see 3GPP TS 25.433. These measurement values are used to assess downlink load state in the cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the NodeB a COMMON MEASUREMENT REPORT message about the power required to meet the GBR for HSDPA users in an HSDPA cell every 1s. The RNC averages the reported measurement values every 5s to obtain the value of the power at a sampling point. At the end of the measurement period, the RNC divides the accumulated numbers by the number of samples to obtain the value of VS.HSDPA.MeanRequiredPwr in the measurement period. The maximum and minimum sampled values are taken as the values of VS.HSDPA.MaxRequiredPwr and VS.HSDPA.MinRequiredPwr. Note: These counters can be measured only when data is transmitted on the HS-DSCH.
Issue 01 (2013-05-04)
2318
Formula
VS.HSDPA.MeanRequiredPwr = {10}*(log10[VS.HSDPA.RequiredPwr.CUM.NoLog]-log10 [VS.HSDPA.RequiredPwr.SAMPLE])
Unit
dBm
Related Features
Counter Name VS.HSDPA.MeanRequiredPwr VS.HSDPA.MaxRequiredPwr VS.HSDPA.MinRequiredPwr Feature ID WRFD-020102 WRFD-020102 WRFD-020102 Feature Name Load Measurement Load Measurement Load Measurement
1.12.42.5 Received Scheduled E-DCH Power Share in the Measurement Period for Cell
Counters
Counter ID 73415859 73403758 Counter Name VS.HSUPA.MeanRSEPS VS.HSUPA.MaxRSEPS Counter Description Average Received Scheduled E-DCH Power Share for Cell Maximum Received Scheduled E-DCH Power Share for Cell Minimum Received Scheduled E-DCH Power Share for Cell
73403760
VS.HSUPA.MinRSEPS
Description
Received scheduled E-DCH power share (RSEPS) is the ratio of E-DCH channel interference to the total interference of the cell, which is measured on the NodeB. For details, see section 5.2.17 in 3GPP TS 25.215. Values of these counters are used to calculate uplink uncontrollable loads and they serve as data input for the uplink admission algorithm and load reshuffling (LDR) algorithm.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the NodeB a COMMON MEASUREMENT REPORT message about the RSEPS value every 1s. Then, the RNC converts the received value to a value defined in 3GPP TS 25.133 by using the following formula: pow(10.0, (2.0 + (RSEPS value reported by NodeB - 151)/100.0))) The RNC averages the values complying with 3GPP TS 25.133 every 5s to obtain the RSEPS value at a sampling point. At the end of the measurement period, the RNC divides the accumulated numbers by the number of samples to obtain the value of VS.HSUPA.MeanRSEPS in the measurement period. The maximum and minimum sampled values are taken as the values of VS.HSUPA.MaxRSEPS and VS.HSUPA.MinRSEPS. Figure 1-1079 Common measurement report procedure
Issue 01 (2013-05-04)
2320
Formula
None
Unit
%
Related Features
Counter Name VS.HSUPA.MeanRSEPS VS.HSUPA.MaxRSEPS VS.HSUPA.MinRSEPS Feature ID WRFD-020102 WRFD-020102 WRFD-020102 Feature Name Load Measurement Load Measurement Load Measurement
1.12.42.6 Average Power Required for Free HSDPA Users for Cell Counters
Counter ID 73441144 73441143 Counter Name VS.HSDPA.MeanRequiredP wr.Free VS.HSDPA.MaxRequiredP wr.Free Counter Description Average Power Required for Free HSDPA Users for Cell Maximum Power Required for Free HSDPA Users for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73441145 Counter Name VS.HSDPA.RequiredPwr.Fr ee.CUM.NoLog Counter Description Cumulated Free Power Required by HS-DSCH for Cell (Before Log Calculation) Number of Received Measurement Reports for Free Power Required by HSDSCH in dBm for Cell
73423475
VS.HSDPA.RequiredPwr.Fr ee.SAMPLE
Issue 01 (2013-05-04)
2321
Description
These counters provide the maximum and mean measurement values of the transmit power of the TRX that is required for free HSDPA users to meet the GBR in an HSDPA cell. For details, see 3GPP TS 25.433. These measurement values are used to assess downlink loads of the free HSDPA users in the HSDPA cell. "Free HSDPA user" is a customized function.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the NodeB a COMMON MEASUREMENT REPORT message about the transmit power of the TRX that is required for free HSDPA users to meet the GBR in an HSDPA cell every 1s. The RNC averages the reported measurement values every 5s to obtain the value of the transmit power at a sampling point. At the end of the measurement period, the RNC divides the accumulated numbers by the number of samples to obtain the value of VS.HSDPA.MeanRequiredPwr.Free in the measurement period. The maximum sampled value is taken as the value of VS.HSDPA.MaxRequiredPwr.Free. Note: These counters can be measured only when data is transmitted on the HS-DSCH.
Formula
VS.HSDPA.MeanRequiredPwr.Free = {10}*(log10 [VS.HSDPA.RequiredPwr.Free.CUM.NoLog]-log10 [VS.HSDPA.RequiredPwr.Free.SAMPLE])
Unit
dBm
Related Features
Counter Name VS.HSDPA.MeanRequiredP wr.Free VS.HSDPA.MaxRequiredP wr.Free Feature ID WRFD-020102 WRFD-020102 Feature Name Load Measurement Load Measurement
1.12.42.7 Power Required by 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell Counters

Counter ID 73425896 Counter Name VS.HSDPA.MC.MeanRequiredPwr Counter Description Power Required by 4CHSDPA/DB-HSDPA/DCHSDPA UEs for Cell
Issue 01 (2013-05-04)
2322
Counter ID 73425901
Counter Name VS.HSDPA.MC.MaxRequiredPwr VS.HSDPA.MC.MinRequiredPwr
Counter Description Maximum Power Required by 4C-HSDPA/DB-HSDPA/ DC-HSDPA UEs for Cell Minimum Power Required by 4C-HSDPA/DB-HSDPA/ DC-HSDPA UEs for Cell
73425903
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73425900 73425899 Counter Name VS.HSDPA.MC.RequiredP wr.CUM.NoLog VS.HSDPA.MC.RequiredP wr.SAMPLE Counter Description VS_HSDPA_MC_Required Pwr_CUM_NoLog_smp1 VS_HSDPA_MC_Required Pwr_SAMPLE_smp1
Description
These counters provide the measurement values of the transmit power required by 4C-HSDPA, 3C-HSDPA, DB-HSDPA, and DC-HSDPA UEs in an HSDPA cell. For details, see 3GPP TS 25.433. These counters also include the transmit power required by 4C-HSDPA+MIMO UEs, 3C-HSDPA+MIMO UEs, DB-HSDPA+MIMO UEs, and DC-HSDPA+MIMO UEs. They are used to assess the ratio of GBP for multi-carrier UEs (VS.HSDPA.MC.MeanRequiredPwr) to the total GBP in the cell (VS.HSDPA.MeanRequiredPwr) and to evaluate the load balancing between cells after multi-carrier UEs are introduced. Multicarrier HSDPA implements load balancing among carriers.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the NodeB a COMMON MEASUREMENT REPORT message about the transmit power required by 4C-HSDPA, 3C-HSDPA, DB-HSDPA, and DC-HSDPA UEs in an HSDPA cell every 1s. The RNC averages the reported measurement values every 5s to obtain the value of the power at a sampling point. At the end of the measurement period, the RNC divides the accumulated numbers by the number of samples to obtain the value of VS.HSDPA.MC.MeanRequiredPwr in the measurement period. The maximum and minimum sampled values are taken as the values of VS.HSDPA.MC.MaxRequiredPwr and VS.HSDPA.MC.MinRequiredPwr. Note: These counters can be measured only when data is transmitted on the HS-DSCH.
Issue 01 (2013-05-04)
2323
Formula
VS.HSDPA.MC.MeanRequiredPwr = {10}*(log10 [VS.HSDPA.MC.RequiredPwr.CUM.NoLog]-log10 [VS.HSDPA.MC.RequiredPwr.SAMPLE])
Unit
dBm
Related Features
Counter Name VS.HSDPA.MC.MeanRequiredPwr Feature ID WRFD-150207 WRFD-150208 WRFD-150209 WRFD-010699 VS.HSDPA.MC.MaxRequiredPwr VS.HSDPA.MC.MinRequiredPwr WRFD-150207 WRFD-150207 Feature Name 4C-HSDPA Flexible DC/DB-HSDPA DB-HSDPA DC-HSDPA+MIMO 4C-HSDPA 4C-HSDPA
Issue 01 (2013-05-04)
2324
1.12.42.8 DL Transmit Power of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell Counters

Counter ID 73425905 Counter Name VS.MeanTCP.HSDPA.MC Counter Description Average DL Transmit Power of 4C-HSDPA/DB-HSDPA/ DC-HSDPA UEs for Cell Maximum DL Transmit Power of 4C-HSDPA/DBHSDPA/DC-HSDPA UEs for Cell Minimum DL Transmit Power of 4C-HSDPA/DBHSDPA/DC-HSDPA UEs for Cell
73425910
VS.MaxTCP.HSDPA.MC
73425912
VS.MinTCP.HSDPA.MC
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73425909 73425908 Counter Name VS.TCP.HSDPA.MC.CUM. NoLog VS.TCP.HSDPA.MC.SAMPLE Counter Description VS_TCP_HSDPA_MC_CU M_NoLog VS_TCP_HSDPA_MC_SA MPLE_smp1
Description
These counters provide the downlink transmitted carrier power (TCP) measurement values of 4C-HSDPA, 3C-HSDPA, DB-HSDPA, and DC-HSDPA UEs in a cell. These counters also include the TCP of 4C-HSDPA+MIMO UEs, 3C-HSDPA+MIMO UEs, DB-HSDPA+MIMO UEs, and DC-HSDPA+MIMO UEs. They are used to assess the downlink load of the cell and to evaluate the load balancing between cells after the multicarrier HSDPA is introduced.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the NodeB a COMMON MEASUREMENT REPORT message about the downlink TCP value of 4C-HSDPA, 3C-HSDPA, DB-HSDPA, and DC-HSDPA UEs in a cell every 1s. The RNC averages the reported measurement values every 5s to obtain the downlink TCP value at a sampling point. At the end of the measurement period, the RNC divides the accumulated numbers by the number of samples to obtain the value of VS.MeanTCP.HSDPA.MC in the measurement period. The maximum and minimum sampled values are taken as the values of VS.MaxTCP.HSDPA.MC and VS.MinTCP.HSDPA.MC. Note: These counters can be measured only when data is transmitted on the HS-DSCH.
Formula
VS.MeanTCP.HSDPA.MC = {10}*(log10[VS.TCP.HSDPA.MC.CUM.NoLog]-log10 [VS.TCP.HSDPA.MC.SAMPLE])
Unit
dBm
Related Features
Counter Name VS.MeanTCP.HSDPA.MC Feature ID WRFD-150207 WRFD-150208 WRFD-150209 WRFD-010699 VS.MaxTCP.HSDPA.MC VS.MinTCP.HSDPA.MC WRFD-150207 WRFD-150207 Feature Name 4C-HSDPA Flexible DC/DB-HSDPA DB-HSDPA DC-HSDPA+MIMO 4C-HSDPA 4C-HSDPA
Issue 01 (2013-05-04)
2326
1.12.43 Soft Handover Measurement per cell(SHO.Cell)

Overview
Soft handover is the procedure during which a radio link is added to or deleted from the active set. When an UE moves or the radio link quality fluctuates, the RNC adds a radio link to the active set if the RNC detects that the cell of the radio link is of good signal quality. If the quality of a radio link in a cell in the active set becomes lower than the predefined threshold, the RNC deletes this radio link from the active set. A soft handover is considered as a softer handover if the two radio links of the UE connection are established with cells belonging to the same NodeB. The RNC determines whether to perform soft handover based on the intra-frequency measurement of the UE. When the RNC receives a measurement report (MR) from the UE and determines that a soft handover is required, it sends an ACTIVE SET UPDATE message to the UE, and starts a timer to wait for the response from the UE. If the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE before the timer expires, the soft handover is considered successful. If the RNC receives an ACTIVE SET UPDATE FAILURE message from the UE or does not receive any message from the UE before the timer expires, the soft handover is considered as a failure. The following figure shows the soft handover procedure.
Issue 01 (2013-05-04)
2327
Figure 1-1082 Flow chart of Soft handover
Table 1 describes the measurement points shown in Figure1. Measurement points A B C Description VS.SHO.AMR.Att,VS.SHO.PS.Att,VS.SH O.AttRLAdd VS.SoHO.AttRLAdd VS.SoHO.SuccRLAdd
Issue 01 (2013-05-04)
2328
Measurement points D E F G H I J
Description VS.SHO.AMR.Succ,VS.SHO.PS.Succ,VS. SHO.SuccRLAdd VS.SoHO.FailRLAdd.CfgUnsupp,VS.SoH O.FailRLAdd.NoReply VS.SHO.FailRLAdd.CfgUnsupp,VS.SHO.F ailRLAdd.NoReply VS.SHO.AMR.Att,VS.SHO.PS.Att,VS.SH O.AttRLDel VS.SoHO.AttRLDel VS.SoHO.SuccRLDel VS.SHO.AMR.Succ,VS.SHO.PS.Succ,VS. SHO.SuccRLDel
Counters
Counter ID 67180483 Counter Name VS.SoHO.AttRLA dd Counter Description Number of Radio Link Addition Attempts in Softer Handover for Cell Number of Successful Radio Link Additions in Softer Handover for Cell Number of Failed Radio Link Additions in Softer Handover for Cell (Configuration Unsupported) Number of Failed Radio Link Additions in Softer Handover for Cell (Incompatible Simultaneous Reconfiguration) Original Release Earlier than V900R011
67180484
VS.SoHO.SuccRLAdd
67180485
VS.SoHO.FailRLA dd.CfgUnsupp
67180486
VS.SoHO.FailRLA dd.ISR
Issue 01 (2013-05-04)
2329
Counter ID 67180488
Counter Name VS.SoHO.FailRLA dd.InvCfg
Counter Description Number of Failed Radio Link Additions in Softer Handover for Cell (Invalid Configuration) Number of Failed Radio Link Additions in Softer Handover due to UE No Response for Cell Number of Radio Link Deletion Attempts in Softer Handover for Cell Number of Successful Radio Link Deletions in Softer Handover for Cell Number of Radio Link Addition Attempts in Soft Handover for Cell Number of Successful Radio Link Additions in Soft Handover for Cell Number of Failed Radio Link Additions in Soft Handover for Cell (Configuration Unsupported) Number of Failed Radio Link Additions in Soft Handover for Cell (Incompatible Simultaneous Reconfiguration)
67180489
VS.SoHO.FailRLA dd.NoReply
67180490
VS.SoHO.AttRLDe l
67180491
VS.SoHO.SuccRLDel
67180498
VS.SHO.AttRLAd d
67180499
VS.SHO.SuccRLA dd
67180500
VS.SHO.FailRLAd d.CfgUnsupp
67180501
VS.SHO.FailRLAd d.ISR
Issue 01 (2013-05-04)
2330
Counter ID 67180503
Counter Name VS.SHO.FailRLAd d.InvCfg
Counter Description Number of Failed Radio Link Additions in Soft Handover for Cell (Invalid Configuration) Number of Failed Radio Link Additions in Soft Handover due to UE No Response for Cell Number of Radio Link Deletion Attempts in Soft Handover for Cell Number of Successful Radio Link Deletions in Soft Handover for Cell Number of Soft Handover Attempts with only Signaling Connection for Cell Number of Successful Soft Handovers with only Signaling Connection for Cell Number of Soft Handover Decisions for Radio Link Addition for Cell Number of Soft Handover Attempts for Cell (AMR) Number of Successful Soft Handovers in CS Domain for Cell (AMR Service)
67180504
VS.SHO.FailRLAd d.NoReply
67180508
VS.SHO.AttRLDel
67180509
VS.SHO.SuccRLD el
67192562
VS.SHO.SigOnly.A tt
67193563
VS.SHO.SigOnly.S ucc
67193564
VS.SHO.AttRLAd d.Prep
67180519
VS.SHO.AMR.Att
67180520
VS.SHO.AMR.Suc c
Issue 01 (2013-05-04)
2331
Counter ID 67180521
Counter Name VS.SHO.CS64.Att
Counter Description Number of Soft Handover Attempts in CS Domain for Cell (64 kbit/s Conversational Service) Number of Successful Soft Handovers in CS Domain for Cell (64 kbit/s Conversational Service) Mean Number of UEs with One Radio Link for Cell Mean Number of UEs with Two Radio Links for Cell Mean Number of UEs with Three Radio Links for Cell Mean Number of UEs with Four Radio Links for Cell Mean Number of UEs with Five Radio Links for Cell Mean Number of UEs with Six Radio Links for Cell Number of Soft Handover Attempts for PS Services for Cell Number of Successful Soft Handovers for PS Services for Cell
67180522
VS.SHO.CS64.Succ
67203936
VS.SHO.AS.1RL
Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 V900R012
67203937
VS.SHO.AS.2RL
67203938
VS.SHO.AS.3RL
67203939
VS.SHO.AS.4RL
67203940
VS.SHO.AS.5RL
67203941
VS.SHO.AS.6RL
73393849
VS.SHO.PS.Att
73393850
VS.SHO.PS.Succ
V900R012
Issue 01 (2013-05-04)
2332
None
1.12.43.1 Number of Radio Link Addition Attempts in Softer Handover Counters

Counter ID 67180483 Counter Name VS.SoHO.AttRLAdd Counter Description Number of Radio Link Addition Attempts in Softer Handover for Cell
Description
This counter provides the number of radio link addition attempts in the softer handover. It is measured in the cell where a radio link is added.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends an ACTIVE SET UPDATE message to the UE during the soft handover, this counter is measured in every cell where a radio link is added if the soft handover is considered as a softer handover. Figure 1-1083 A successful softer handover (radio link addition)
Issue 01 (2013-05-04)
2333
Formula
None
Unit
None
Related Features
Counter Name VS.SoHO.AttRLAdd Feature ID WRFD-020201 Feature Name Intra Node B Softer Handover
1.12.43.2 Number of Successful Radio Link Additions in Softer Handover Counters

Counter ID 67180484 Counter Name VS.SoHO.SuccRLAdd Counter Description Number of Successful Radio Link Additions in Softer Handover for Cell
Description
This counter provides the number of successful radio link additions in the softer handover. It is measured in the cell where a radio link is added.
Measurement point
The measurement is triggered at point C, as shown in the figure. When the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover procedure , the RNC considers the soft handover as successful. If the soft handover is considered as a softer handover and a radio link is added, this counter is measured in every cell where a radio link is added.
Issue 01 (2013-05-04)
2334
Figure 1-1084 A successful softer handover (radio link addition)
Formula
None
Unit
None
Related Features
Counter Name VS.SoHO.SuccRLAdd Feature ID WRFD-020201 Feature Name Intra Node B Softer Handover
1.12.43.3 Counters Related to the Number of Failed Radio Link Additions in Softer Handover due to Different Causes
Issue 01 (2013-05-04)
2335
Counters
Counter ID 67180485 Counter Name VS.SoHO.FailRLAdd.CfgU nsupp Counter Description Number of Failed Radio Link Additions in Softer Handover for Cell (Configuration Unsupported) Number of Failed Radio Link Additions in Softer Handover for Cell (Incompatible Simultaneous Reconfiguration) Number of Failed Radio Link Additions in Softer Handover for Cell (Invalid Configuration)
67180486
VS.SoHO.FailRLAdd.ISR
67180488
VS.SoHO.FailRLAdd.InvCf g
Description
These counters provide the number of failed radio link additions in the softer handover due to different causes. They are measured in the cell where a radio link is added.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives an ACTIVE SET UPDATE FAILURE message from the UE during the softer handover procedure, the number of failed radio link additions is measured on the basis of the different causes carried in the message in the cell where a radio link is added. Figure 1-1085 Soft handover procedure (failed operation)
Issue 01 (2013-05-04)
2336
Formula
None
Unit
None
Related Features
Counter Name VS.SoHO.FailRLAdd.CfgU nsupp VS.SoHO.FailRLAdd.ISR VS.SoHO.FailRLAdd.InvCf g Feature ID WRFD-020201 WRFD-020201 WRFD-020201 Feature Name Intra Node B Softer Handover Intra Node B Softer Handover Intra Node B Softer Handover
1.12.43.4 Number of Failed Radio Link Additions in Softer Handover due to UE No Response Counters
Counter ID 67180489 Counter Name VS.SoHO.FailRLAdd.NoRe ply Counter Description Number of Failed Radio Link Additions in Softer Handover due to UE No Response for Cell
Description
This counter provides the number of failed radio link additions because there is no response from the UE in the softer handover. It is measured in the cell where a radio link is added.
Measurement point
The measurement is triggered at point A, as shown in the figure. During the softer handover, when the RNC sends an ACTIVE SET UPDATE message to the UE, it starts a timer to wait for the response from the UE. If the RNC does not receive a response from the UE before the timer expires, this counter is measured in every cell where a radio link is added.
Issue 01 (2013-05-04)
2337
Figure 1-1086 Soft handover procedure (failed operation due to timer expiry)
Formula
None
Unit
None
Related Features
Counter Name VS.SoHO.FailRLAdd.NoRe ply Feature ID WRFD-020201 Feature Name Intra Node B Softer Handover
1.12.43.5 Number of Radio Link Deletion Attempts in Softer Handover Counters

Counter ID 67180490 Counter Name VS.SoHO.AttRLDel Counter Description Number of Radio Link Deletion Attempts in Softer Handover for Cell
Issue 01 (2013-05-04)
2338
Description
This counter provides the number of radio link deletion attempts in the softer handover. It is measured in the cell where a radio link is deleted.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends an ACTIVE SET UPDATE message to the UE during the soft handover procedure , this counter is measured in every cell where a radio link is deleted if the soft handover is considered as a softer handover. Figure 1-1087 A successful soft handover (radio link deletion)
Formula
None
Unit
None
Issue 01 (2013-05-04)
2339
Related Features
Counter Name VS.SoHO.AttRLDel Feature ID WRFD-020201 Feature Name Intra Node B Softer Handover
1.12.43.6 Number of Successful Radio Link Deletions in Softer Handover Counters

Counter ID 67180491 Counter Name VS.SoHO.SuccRLDel Counter Description Number of Successful Radio Link Deletions in Softer Handover for Cell
Description
This counter provides the number of successful radio link deletions in the softer handover. It is measured in the cell where a radio link is deleted.
Measurement point
The measurement is triggered at point C, as shown in the figure. When the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover procedure, the RNC considers the soft handover as successful. If the soft handover is considered as a softer handover and a radio link is deleted, this counter is measured in every cell where a radio link is deleted.
Issue 01 (2013-05-04)
2340
Figure 1-1088 A successful soft handover (radio link deletion)
Formula
None
Unit
None
Related Features
Counter Name VS.SoHO.SuccRLDel Feature ID WRFD-020201 Feature Name Intra Node B Softer Handover
1.12.43.7 Number of Radio Link Addition Attempts in Soft Handover
Issue 01 (2013-05-04)
2341
Counters
Counter ID 67180498 Counter Name VS.SHO.AttRLAdd Counter Description Number of Radio Link Addition Attempts in Soft Handover for Cell
Description
This counter provides the number of radio link addition attempts in the soft handover (including the softer handover). It is measured in the cell where a radio link is added.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends an ACTIVE SET UPDATE message to the UE during the soft handover (including the softer handover) procedure, this counter is measured in every cell where a radio link is added. Figure 1-1089 A successful soft handover (radio link addition)
Issue 01 (2013-05-04)
2342
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AttRLAdd Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.12.43.8 Number of Successful Radio Link Additions in Soft Handover Counters

Counter ID 67180499 Counter Name VS.SHO.SuccRLAdd Counter Description Number of Successful Radio Link Additions in Soft Handover for Cell
Description
This counter provides the number of successful radio link additions in the soft handover (including the softer handover). It is measured in the cell where a radio link is added.
Measurement point
The measurement is triggered at point C, as shown in the figure. Each time the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover (including the softer handover) procedure, the soft handover is considered as successful. In this case, this counter is measured in every cell where a radio link is added.
Issue 01 (2013-05-04)
2343
Figure 1-1090 A successful soft handover (radio link addition)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SuccRLAdd Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
Issue 01 (2013-05-04)
2344
1.12.43.9 Counters Related to the Number of Failed Radio Link Additions in Soft Handover due to Different Causes Counters
Counter ID 67180500 Counter Name VS.SHO.FailRLAdd.CfgUn supp Counter Description Number of Failed Radio Link Additions in Soft Handover for Cell (Configuration Unsupported) Number of Failed Radio Link Additions in Soft Handover for Cell (Incompatible Simultaneous Reconfiguration) Number of Failed Radio Link Additions in Soft Handover for Cell (Invalid Configuration)
67180501
VS.SHO.FailRLAdd.ISR
67180503
VS.SHO.FailRLAdd.InvCfg
Description
These counters provide the number of failed radio link additions in the soft handover (including the softer handover) due to different causes. They are measured in the cell where a radio link is added.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives an ACTIVE SET UPDATE FAILURE message from the UE during the soft handover (including the softer handover) procedure, this counter is measured on the basis of the different causes carried in the message in every cell where a radio link is added.
Issue 01 (2013-05-04)
2345
Figure 1-1091 Soft handover procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.FailRLAdd.CfgUn supp Feature ID WRFD-020202 WRFD-020201 WRFD-020202 WRFD-020201 VS.SHO.FailRLAdd.InvCfg WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover Intra RNC Soft Handover Intra Node B Softer Handover Intra RNC Soft Handover Intra Node B Softer Handover
VS.SHO.FailRLAdd.ISR
1.12.43.10 Number of Failed Radio Link Additions in Soft Handover due to UE No Response
Counters
Counter ID 67180504 Counter Name VS.SHO.FailRLAdd.NoReply Counter Description Number of Failed Radio Link Additions in Soft Handover due to UE No Response for Cell
Description
This counter provides the number of failed radio link additions in the case that there is no response from the UE in the soft handover (including the softer handover). It is measured in the cell where a radio link is added.
Measurement point
The measurement is triggered at point A, as shown in the figure. During the soft handover (including the softer handover), when the RNC sends an ACTIVE SET UPDATE message to the UE, it starts a timer to wait for the response from the UE. If the RNC does not receive a response from the UE before the timer expires, this counter is measured in every cell where a radio link is added. Figure 1-1092 A failed soft handover (timer expiry)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.FailRLAdd.NoReply Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.12.43.11 Number of Radio Link Deletion Attempts in Soft Handover Counters

Counter ID 67180508 Counter Name VS.SHO.AttRLDel Counter Description Number of Radio Link Deletion Attempts in Soft Handover for Cell
Description
This counter provides the number of radio link deletion attempts in the soft handover (including the softer handover). It is measured in the cell where a radio link is deleted.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends an ACTIVE SET UPDATE message to the UE during the soft handover (including the softer handover) procedure, this counter is measured in every cell where a radio link is deleted.
Issue 01 (2013-05-04)
2348
Figure 1-1093 A successful soft handover (radio link deletion)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AttRLDel Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.12.43.12 Number of Successful Radio Link Deletions in Soft Handover
Issue 01 (2013-05-04)
2349
Counters
Counter ID 67180509 Counter Name VS.SHO.SuccRLDel Counter Description Number of Successful Radio Link Deletions in Soft Handover for Cell
Description
This counter provides the number of successful radio link deletions in the soft handover (including the softer handover). It is measured in the cell where a radio link is deleted.
Measurement point
The measurement is triggered at point C in the figure. Each time the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover (including the softer handover) procedure, the soft handover is considered as successful. In this case, this counter is measured in every cell where a radio link is deleted. Figure 1-1094 A successful soft handover (radio link deletion)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SuccRLDel Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.12.43.13 Number of Soft Handover Attempts with only Signaling Connection Counters
Counter ID 67192562 Counter Name VS.SHO.SigOnly.Att Counter Description Number of Soft Handover Attempts with only Signaling Connection for Cell
Description
This counter provides the number of soft handover attempts with only signaling connection in the target cell.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends an ACTIVE SET UPDATE message to the UE during the soft handover (including the softer handover) procedure, this counter is measured in every cell where a radio link is added or deleted if only signaling connection exists during the soft handover. Figure 1-1095 A successful soft handover
Issue 01 (2013-05-04)
2351
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SigOnly.Att Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.12.43.14 Number of Successful Soft Handovers with only Signaling Connection Counters
Counter ID 67193563 Counter Name VS.SHO.SigOnly.Succ Counter Description Number of Successful Soft Handovers with only Signaling Connection for Cell
Description
This counter provides the number of successful soft handovers with only signaling connection in the target cell.
Measurement point
The measurement is triggered at point C, as shown in the figure. Each time the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover (including the softer handover) procedure, the soft handover is considered as successful. In this case, if the UE has only signaling connection during the soft handover, this counter is measured in every cell where a radio link is added or deleted.
Issue 01 (2013-05-04)
2352
Figure 1-1096 A successful soft handover
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SigOnly.Succ Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.12.43.15 Number of Soft Handover Decisions for Radio Link Addition Initiated by RNC Counters
Counter ID 67193564 Counter Name VS.SHO.AttRLAdd.Prep Counter Description Number of Soft Handover Decisions for Radio Link Addition for Cell
Issue 01 (2013-05-04)
2353
Description
This counter provides the number of decisions determined by the RNC to trigger soft handovers (including softer handovers) with radio link addition. It is measured in the cell where a radio link is to be added.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC determines to add a radio link during the soft handover (including the softer handover) procedure, this counter is measured in every cell where a radio link is to be added. Figure 1-1097 A successful soft handover (radio link addition)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AttRLAdd.Prep Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.12.43.16 These counters provide the number of soft handover attempts in different service types in the target cell Counters
Counter ID 67180519 67180521 Counter Name VS.SHO.AMR.Att VS.SHO.CS64.Att Counter Description Number of Soft Handover Attempts for Cell (AMR) Number of Soft Handover Attempts in CS Domain for Cell (64 kbit/s Conversational Service)
Description
These counters provide the number of soft handover attempts in different service types in the target cell.The counter VS.SHO.AMR.Att includes narrowband and wideband AMR services.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends an ACTIVE SET UPDATE message to the UE during the soft handover (including the softer handover) procedure, the counter corresponding to the type of the service where the soft handover occurs is measured in every cell where a radio link is added or deleted.
Issue 01 (2013-05-04)
2355
Figure 1-1098 A successful soft handover
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AMR.Att Feature ID WRFD-020202 WRFD-020201 VS.SHO.CS64.Att WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover Intra RNC Soft Handover Intra Node B Softer Handover
1.12.43.17 Counters Related to the Number of Successful Soft Handovers in Different Service Types
Issue 01 (2013-05-04)
2356
Counters
Counter ID 67180520 Counter Name VS.SHO.AMR.Succ Counter Description Number of Successful Soft Handovers in CS Domain for Cell (AMR Service) Number of Successful Soft Handovers in CS Domain for Cell (64 kbit/s Conversational Service)
67180522
VS.SHO.CS64.Succ
Description
These counters provide the number of successful soft handovers in different service types in the target cell.The counter VS.SHO.AMR.Succ includes narrowband and wideband AMR services.
Measurement point
The measurement is triggered at point C, as shown in the figure. Each time the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover (including the softer handover) procedure, the soft handover is considered as successful. In this case, the counter corresponding to the type of the service where the soft handover occurs is measured in every cell where a radio link is added or deleted. Figure 1-1099 A successful soft handover
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AMR.Succ Feature ID WRFD-020202 WRFD-020201 VS.SHO.CS64.Succ WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover Intra RNC Soft Handover Intra Node B Softer Handover
1.12.43.18 Mean Number of UEs with One Radio Link Counters

Counter ID 67203936 Counter Name VS.SHO.AS.1RL Counter Description Mean Number of UEs with One Radio Link for Cell
Description
This counter provides the mean number of UEs with one radio link in a cell of the active set.
Measurement point
In a measurement period, the RNC periodically takes samples (sampling periodicity is 30 seconds) of the number of UEs with one radio link in a cell of the active set. At the end of the measurement period, the RNC divides the accumulated number by the number of sampling times to obtain the mean number of UEs with only one radio link in a cell of the active set in the measurement period.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2358
Related Features
Counter Name VS.SHO.AS.1RL Feature ID WRFD-020202 WRFD-020203 Feature Name Intra RNC Soft Handover Inter RNC Soft Handover
1.12.43.19 Mean Number of UEs with Two Radio Links Counters

Counter ID 67203937 Counter Name VS.SHO.AS.2RL Counter Description Mean Number of UEs with Two Radio Links for Cell
Description
This counter provides the mean number of UEs with two radio links in the cell of the active set.
Measurement point
In a measurement period, the RNC periodically takes samples (sampling periodicity is 30 seconds) of the number of UEs with two radio links in the cell of the active set. At the end of the measurement period, the RNC divides the accumulated number by the number of sampling times to obtain the mean number of UEs with two radio links in the cell of the active set in the measurement period.
Formula
None
Unit
None
Related Features
1.12.43.20 Mean Number of UEs with Three Radio Links

Counters
Counter ID 67203938 Counter Name VS.SHO.AS.3RL Counter Description Mean Number of UEs with Three Radio Links for Cell
Description
This counter provides the mean number of UEs with three radio links in the cell of the active set.
Measurement point
In a measurement period, the RNC periodically takes samples (sampling periodicity is 30 seconds) of the number of UEs with three radio links in the cell of the active set. At the end of the measurement period, the RNC divides the accumulated number by the number of sampling times to obtain the mean number of UEs with three radio links in the cell of the active set in the measurement period.
Formula
None
Unit
None
Related Features
1.12.43.21 Mean Number of UEs with Four Radio Links Counters

Counter ID 67203939 Counter Name VS.SHO.AS.4RL Counter Description Mean Number of UEs with Four Radio Links for Cell
Description
This counter provides the mean number of UEs with four radio links in the cell of the active set.
Measurement point
In a measurement period, the RNC periodically takes samples (sampling periodicity is 30 seconds) of the number of UEs with four radio links in the cell of the active set. At the end of the measurement period, the RNC divides the accumulated number by the number of sampling times to obtain the mean number of UEs with four radio links in the cell of the active set in the measurement period.
Formula
None
Unit
None
Related Features
1.12.43.22 Mean Number of UEs with Five Radio Links Counters

Counter ID 67203940 Counter Name VS.SHO.AS.5RL Counter Description Mean Number of UEs with Five Radio Links for Cell
Description
This counter provides the mean number of UEs with five radio links in the cell of the active set.
Measurement point
In a measurement period, the RNC periodically takes samples (sampling periodicity is 30 seconds) of the number of UEs with five radio links in the cell of the active set. At the end of the measurement period, the RNC divides the accumulated number by the number of sampling times to obtain the mean number of UEs with five radio links in the cell of the active set in the measurement period.
Formula
None
Unit
None
Related Features
1.12.43.23 Mean Number of UEs with Six Radio Links Counters

Counter ID 67203941 Counter Name VS.SHO.AS.6RL Counter Description Mean Number of UEs with Six Radio Links for Cell
Description
This counter provides the mean number of UEs with six radio links in the cell of the active set.
Measurement point
In a measurement period, the RNC periodically takes samples (sampling periodicity is 30 seconds) of the number of UEs with six radio links in the cell of the active set. At the end of the measurement period, the RNC divides the accumulated number by the number of sampling times to obtain the mean number of UEs with six radio links in the cell of the active set in the measurement period.
Formula
None
Unit
None
Related Features
Issue 01 (2013-05-04)
2362
1.12.43.24 Number of Soft Handover Attempts for PS Services for Cell Counters
Counter ID 73393849 Counter Name VS.SHO.PS.Att Counter Description Number of Soft Handover Attempts for PS Services for Cell
Description
This counter provides the number of RNC-initiated soft handover attempts for PS services in the cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the UE an ACTIVE SET UPDATE message during the soft handover or softer handover for PS services. In this case, the counter is measured in the cell where the RL is added or deleted, respectively. Figure 1-1100 Soft handover procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.PS.Att Feature ID WRFD-020201 WRFD-020202 Feature Name Intra Node B Softer Handover Intra RNC Soft Handover
1.12.43.25 Number of Successful Soft Handovers for PS Services for Cell Counters
Counter ID 73393850 Counter Name VS.SHO.PS.Succ Counter Description Number of Successful Soft Handovers for PS Services for Cell
Description
This counter provides the number of the successful RNC-initiated soft handovers for PS services in the cell.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends the UE an ACTIVE SET UPDATE COMPLETE message during the soft handover or softer handover for PS services. In this case, the counter is measured in the cell where the RL is added or deleted, respectively.
Issue 01 (2013-05-04)
2364
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.PS.Succ Feature ID WRFD-020201 WRFD-020202 Feature Name Intra Node B Softer Handover Intra RNC Soft Handover
1.12.44 Measurement related to SIRTARGET per cell(SIR.Cell)

Overview
The Signal-to-Interference Ratio (SIR) target value used in the uplink out loop power control on the DCH is adjusted dynamically based on the uplink Block Error Rate (BLER) or Bit Error Rate (BER). The uplink outer loop power control adjusts the transmit power of the UE to lower the interference on other UEs while ensuring the service quality of the UE.
Based on different service classes and traffic rates, this measurement indicates the ratio of the duration when the target SIR reaches the maximum value to the total period when the uplink outer loop power control is performed.
Counters
Counter ID 67199814 Counter Name VS.ULSirTarget.O ut.AMR Counter Description Rate of Duration that SIR Target of AMR Services Reaches Maximum Value Rate of Duration that SIR Target of CS 64 Kbit/s Conversational Services Reaches Maximum Value for cell Rate of Duration that SIR Target of PS 8 Kbit/s BE Services Reaches Maximum Value Rate of Duration that SIR Target of PS 16 Kbit/s BE Services Reaches Maximum Value Rate of Duration that SIR Target of PS 32 Kbit/s BE Services Reaches Maximum Value Rate of Duration that SIR Target of PS 64 Kbit/s BE Services Reaches Maximum Value Rate of Duration that SIR Target of PS 128 Kbit/s BE Services Reaches Maximum Value Original Release Earlier than V900R011
73394086
VS.ULSirTarget.O ut.CS64
V900R012
67199823
VS.ULSirTarget.O ut.PS.BE.DCH.8
67199824
67199825
67199826
67199827
Issue 01 (2013-05-04)
2366
Counter ID 67199828
Counter Name VS.ULSirTarget.O ut.PS.BE.DCH.144
Counter Description Rate of Duration that SIR Target of PS 144 Kbit/s BE Services Reaches Maximum Value Rate of Duration that SIR Target of PS 256 Kbit/s BE Services Reaches Maximum Value Rate of Duration that SIR Target of PS 384 Kbit/s BE Services Reaches Maximum Value
67199829
67199830
None
1.12.44.1 SIR Target Measurement for Different Services Counters

Counter ID 67199814 Counter Name VS.ULSirTarget.Out.AMR Counter Description Rate of Duration that SIR Target of AMR Services Reaches Maximum Value Rate of Duration that SIR Target of CS 64 Kbit/s Conversational Services Reaches Maximum Value for cell Rate of Duration that SIR Target of PS 8 Kbit/s BE Services Reaches Maximum Value Rate of Duration that SIR Target of PS 16 Kbit/s BE Services Reaches Maximum Value
73394086
VS.ULSirTarget.Out.CS64
67199823
VS.ULSirTarget.Out.PS.BE. DCH.8
67199824
Issue 01 (2013-05-04)
2367
Counter ID 67199825
Counter Name VS.ULSirTarget.Out.PS.BE. DCH.32
Counter Description Rate of Duration that SIR Target of PS 32 Kbit/s BE Services Reaches Maximum Value Rate of Duration that SIR Target of PS 64 Kbit/s BE Services Reaches Maximum Value Rate of Duration that SIR Target of PS 128 Kbit/s BE Services Reaches Maximum Value Rate of Duration that SIR Target of PS 144 Kbit/s BE Services Reaches Maximum Value Rate of Duration that SIR Target of PS 256 Kbit/s BE Services Reaches Maximum Value Rate of Duration that SIR Target of PS 384 Kbit/s BE Services Reaches Maximum Value
67199826
67199827
67199828
67199829
67199830
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67184436 Counter Name UlSirTarget.Out.AMR.Out Counter Description Duration of AMR Sir Target Exceeding the Maximum Value for Cell Duration of Total Elapsed Time of AMR for Cell Duration of CS 64 kbit/s Sir Target Exceeding the Maximum Value for Cell Duration of Total Elapsed Time of CS 64 kbit/s for Cell
67184489 67184440
UlSirTarget.Out.AMR.Total UlSirTarget.Out.CSRT. 64.Out UlSirTarget.Out.CSRT. 64.Total
67184493
Issue 01 (2013-05-04)
2368
Counter ID 67184449
Counter Name UlSirTarget.Out.PSNRT. 128.Out UlSirTarget.Out.PSNRT. 128.Total UlSirTarget.Out.PSNRT. 144.Out UlSirTarget.Out.PSNRT. 144.Total UlSirTarget.Out.PSNRT. 16.Out UlSirTarget.Out.PSNRT. 16.Total UlSirTarget.Out.PSNRT. 256.Out UlSirTarget.Out.PSNRT. 256.Total UlSirTarget.Out.PSNRT. 32.Out UlSirTarget.Out.PSNRT. 32.Total UlSirTarget.Out.PSNRT. 384.Out UlSirTarget.Out.PSNRT. 384.Total UlSirTarget.Out.PSNRT. 64.Out
Counter Description Duration of PSNRT 128 kbit/ s Sir Target Exceeding the Maximum Value for Cell Duration of Total Elapsed Time of PSNRT 128 kbit/s for Cell Duration of PSNRT 144 kbit/ s Sir Target Exceeding the Maximum Value for Cell Duration of Total Elapsed Time of PSNRT 144 kbit/s for Cell Duration of PSNRT 16 kbit/s Sir Target Exceeding the Maximum Value for Cell Duration of Total Elapsed Time of PSNRT 16 kbit/s for Cell Duration of PSNRT 256 kbit/ s Sir Target Exceeding the Maximum Value for Cell Duration of Total Elapsed Time of PSNRT 256 kbit/s for Cell Duration of PSNRT 32 kbit/s Sir Target Exceeding the Maximum Value for Cell Duration of Total Elapsed Time of PSNRT 32 kbit/s for Cell Duration of PSNRT 384 kbit/ s Sir Target Exceeding the Maximum Value for Cell Duration of Total Elapsed Time of PSNRT 384 kbit/s for Cell Duration of PSNRT 64 kbit/s Sir Target Exceeding the Maximum Value for Cell
67184502
67184450
67184503
67184446
67184499
67184451
67184504
67184447
67184500
67184452
67184505
67184448
Issue 01 (2013-05-04)
2369
Counter ID 67184501
Counter Name UlSirTarget.Out.PSNRT. 64.Total UlSirTarget.Out.PSNRT. 8.Out UlSirTarget.Out.PSNRT. 8.Total
Counter Description Duration of Total Elapsed Time of PSNRT 64 kbit/s for Cell Duration of PSNRT 8 kbit/s Sir Target Exceeding the Maximum Value for Cell Duration of Total Elapsed Time of PSNRT 8 kbit/s for Cell
67184445
67184498
Description
These counters provide the percentage of the duration when the signal-to-interference ratio (SIR) target of uplink outer-loop power control reaches its upper limit to the total duration of the uplink outer-loop power control for different services of all UEs in the best cell, such as the adaptive multirate (AMR) service, CS 64 kbit/s conversational service, and PS BE service. The VS.ULSirTarget.Out.AMR counter applies only to narrowband AMR service.
Measurement point
In a measurement period, the RNC periodically takes samples of the SIR target for different services of all UEs in the best cell, such as the AMR service, CS 64 kbit/s conversational service, and PS BE service in the best cell. When the SIR target of a UE reaches its upper limit, the duration when the SIR target reaches its upper limit is accumulated. At the end of the measurement period, this counter is calculated by dividing this duration by the total duration of outer-loop power control.
Formula
VS.ULSirTarget.Out.AMR = {100}*[UlSirTarget.Out.AMR.Out]/ [UlSirTarget.Out.AMR.Total] VS.ULSirTarget.Out.CS64 = {100}*[UlSirTarget.Out.CSRT.64.Out]/[UlSirTarget.Out.CSRT. 64.Total] VS.ULSirTarget.Out.PS.BE.DCH.8 = {100}*[UlSirTarget.Out.PSNRT.8.Out]/ [UlSirTarget.Out.PSNRT.8.Total] VS.ULSirTarget.Out.PS.BE.DCH.16 = {100}*[UlSirTarget.Out.PSNRT.16.Out]/ [UlSirTarget.Out.PSNRT.16.Total] VS.ULSirTarget.Out.PS.BE.DCH.32 = {100}*[UlSirTarget.Out.PSNRT.32.Out]/ [UlSirTarget.Out.PSNRT.32.Total] VS.ULSirTarget.Out.PS.BE.DCH.64 = {100}*[UlSirTarget.Out.PSNRT.64.Out]/ [UlSirTarget.Out.PSNRT.64.Total] VS.ULSirTarget.Out.PS.BE.DCH.128 = {100}*[UlSirTarget.Out.PSNRT.128.Out]/ [UlSirTarget.Out.PSNRT.128.Total]
VS.ULSirTarget.Out.PS.BE.DCH.144 = {100}*[UlSirTarget.Out.PSNRT.144.Out]/ [UlSirTarget.Out.PSNRT.144.Total] VS.ULSirTarget.Out.PS.BE.DCH.256 = {100}*[UlSirTarget.Out.PSNRT.256.Out]/ [UlSirTarget.Out.PSNRT.256.Total] VS.ULSirTarget.Out.PS.BE.DCH.384 = {100}*[UlSirTarget.Out.PSNRT.384.Out]/ [UlSirTarget.Out.PSNRT.384.Total]
Unit
%
Related Features
Counter Name VS.ULSirTarget.Out.AMR VS.ULSirTarget.Out.CS64 VS.ULSirTarget.Out.PS.BE. DCH.8 VS.ULSirTarget.Out.PS.BE. DCH.16 VS.ULSirTarget.Out.PS.BE. DCH.32 VS.ULSirTarget.Out.PS.BE. DCH.64 VS.ULSirTarget.Out.PS.BE. DCH.128 VS.ULSirTarget.Out.PS.BE. DCH.144 VS.ULSirTarget.Out.PS.BE. DCH.256 VS.ULSirTarget.Out.PS.BE. DCH.384 Feature ID WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 WRFD-020503 Feature Name Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control Outer Loop Power Control
1.12.45 Measurement related to SPI per cell(SPI.Cell)

Overview
This function subset is used to monitor and assess the performance of the feature of Differentiated Service Based on SPI Weight. It provides the following information: (1) Number of times that the downlink throughput of HSDPA services is within each range based on the service level. (2) Number of times that the uplink throughput of HSUPA services is within each range based on the service level. (3) Number of bytes sent in downlink on HSDPA MAC-d flows and the mean
downlink throughput of a single HSDPA MAC-d flow based on the service level. (4) Number of bytes received in uplink on HSUPA MAC-d flows and the mean uplink throughput of a single HSUPA MAC-d flow based on the service level.The measurement item is measured only when the SPI measure function is activated using the SET UDPUCFGDATA command with CellCountersMeasOBJCtrlSwitch set to Spi or QosAndSpi.
Counters
Counter ID 73421554 Counter Name VS.HSDPA.SPI8Be ChThroughput.0 Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 0 kbit/s and 32 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 32 kbit/s and 64 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 64 kbit/s and 256 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 256 kbit/s and 512 kbit/s in a Measurement Period for Cell Original Release V900R012
73421555
VS.HSDPA.SPI8Be ChThroughput.1
V900R012
73421556
V900R012
73421557
V900R012
Issue 01 (2013-05-04)
2372
Counter ID 73421558
Counter Name VS.HSDPA.SPI8Be ChThroughput.4
Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 512 kbit/s and 768 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 768 kbit/s and 1024 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 1024 kbit/s and 1536 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 1536 kbit/s and 2048 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 2048 kbit/s and 3072 kbit/s in a Measurement Period for Cell
73421559
V900R012
73421560
V900R012
73421561
V900R012
73421562
V900R012
Issue 01 (2013-05-04)
2373
Counter ID 73421563
Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 3072 kbit/s and 4096 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 4096 kbit/s and 6144 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 6144 kbit/s and 8192 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 8192 kbit/s and 12288 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 larger than 12288 kbit/s in a Measurement Period for Cell
73421564
V900R012
73421565
V900R012
73421566
V900R012
73421567
V900R012
Issue 01 (2013-05-04)
2374
Counter ID 73421568
73421569
V900R012
73421570
V900R012
73421571
V900R012
73421572
V900R012
Issue 01 (2013-05-04)
2375
Counter ID 73421573
73421574
V900R012
73421575
V900R012
73421576
V900R012
73421577
V900R012
Issue 01 (2013-05-04)
2376
Counter ID 73421578
Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 4096 kbit/s and 6144 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 6144 kbit/s and 8192 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 8192 kbit/s and 12288 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 larger than 12288 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 0 kbit/s and 32 kbit/s in a Measurement Period for Cell
73421579
V900R012
73421580
V900R012
73421581
V900R012
73421582
V900R012
Issue 01 (2013-05-04)
2377
Counter ID 73421583
73421584
V900R012
73421585
V900R012
73421586
V900R012
73421587
V900R012
Issue 01 (2013-05-04)
2378
Counter ID 73421588
73421589
V900R012
73421590
V900R012
73421591
V900R012
73421592
V900R012
Issue 01 (2013-05-04)
2379
Counter ID 73421593
Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 6144 kbit/s and 8192 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 8192 kbit/s and 12288 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 larger than 12288 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPANumber of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 0 kbit/s and 32 kbit/s in a Measurement Period for Cell
73421594
V900R012
73421595
V900R012
73421596
VS.HSUPA.SPI8Be ChThroughput.0
V900R012
Issue 01 (2013-05-04)
2380
Counter ID 73421597
Counter Name VS.HSUPA.SPI8Be ChThroughput.1
Counter Description Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 32 kbit/s and 64 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 64 kbit/s and 256 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 256 kbit/s and 512 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 512 kbit/s and 768 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 768 kbit/s and 1024 kbit/s in a Measurement Period for Cell
73421598
V900R012
73421599
V900R012
73421600
V900R012
73421601
V900R012
Issue 01 (2013-05-04)
2381
Counter ID 73421602
Counter Description Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 1024 kbit/s and 1536 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 1536 kbit/s and 2048 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 2048 kbit/s and 3072 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 3072 kbit/s and 4096 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 larger than 4096 kbit/ s in a Measurement Period for Cell
73421603
V900R012
73421604
V900R012
73421605
V900R012
73421606
V900R012
Issue 01 (2013-05-04)
2382
Counter ID 73421607
73421608
V900R012
73421609
V900R012
73421610
V900R012
73421611
V900R012
Issue 01 (2013-05-04)
2383
Counter ID 73421612
73421613
V900R012
73421614
V900R012
73421615
V900R012
73421616
V900R012
Issue 01 (2013-05-04)
2384
Counter ID 73421617
Counter Description Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 5 larger than 4096 kbit/ s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 0 kbit/s and 32 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 32 kbit/s and 64 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 64 kbit/s and 256 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 256 kbit/s and 512 kbit/s in a Measurement Period for Cell
73421618
V900R012
73421619
V900R012
73421620
V900R012
73421621
V900R012
Issue 01 (2013-05-04)
2385
Counter ID 73421622
73421623
V900R012
73421624
V900R012
73421625
V900R012
73421626
V900R012
Issue 01 (2013-05-04)
2386
Counter ID 73421627
Counter Description Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 3072 kbit/s and 4096 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 larger than 4096 kbit/ s in a Measurement Period for Cell Number of Bytes Sent in Downlink on HSDPA MAC-d flow of BE Services with SPI Set to 2 for Cell Number of Bytes Sent in Downlink on HSDPA MAC-d flow of BE Services with SPI Set to 3 for Cell Number of Bytes Sent in Downlink on HSDPA MAC-d flow of BE Services with SPI Set to 4 for Cell Number of Bytes Sent in Downlink on HSDPA MAC-d flow of BE Services with SPI Set to 5 for Cell
73421628
V900R012
73421629
VS.HSDPA.BeChT hroughput.TotalBy tes.SPI2
V900R012
73421630
V900R012
73421631
V900R012
73421632
V900R012
Issue 01 (2013-05-04)
2387
Counter ID 73421633
Counter Name VS.HSDPA.BeChT hroughput.TotalBy tes.SPI6
Counter Description Number of Bytes Sent in Downlink on HSDPA MAC-d flow of BE Services with SPI Set to 6 for Cell Number of Bytes Sent in Downlink on HSDPA MAC-d flow of BE Services with SPI Set to 7 for Cell Number of Bytes Sent in Downlink on HSDPA MAC-d flow of BE Services with SPI Set to 8 for Cell Number of Bytes Sent in Downlink on HSDPA MAC-d flow of BE Services with SPI Set to 9 for Cell Number of Bytes Sent in Downlink on HSDPA MAC-d flow of BE Services with SPI Set to 10 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 2 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 3 for Cell
73421634
V900R012
73421635
V900R012
73421636
V900R012
73421637
V900R012
73421638
VS.HSUPA.BeChT hroughput.TotalBy tes.SPI2
V900R012
73421639
V900R012
Issue 01 (2013-05-04)
2388
Counter ID 73421640
Counter Name VS.HSUPA.BeChT hroughput.TotalBy tes.SPI4
Counter Description Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 4 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 5 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 6 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 7 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 8 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 9 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 10 for Cell
73421641
V900R012
73421642
V900R012
73421643
V900R012
73421644
V900R012
73421645
V900R012
73421646
V900R012
Issue 01 (2013-05-04)
2389
Counter ID 73439855
Counter Name VS.HSDPA.BeChT hroughput.SPI2
Counter Description Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 2 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 3 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 4 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 5 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 6 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 7 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 8 for Cell
73439856
VS.HSDPA.BeChT hroughput.SPI3
V900R012
73439857
V900R012
73439858
V900R012
73439859
V900R012
73439860
V900R012
73439861
V900R012
Issue 01 (2013-05-04)
2390
Counter ID 73439862
Counter Name VS.HSDPA.BeChT hroughput.SPI9
Counter Description Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 9 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 10 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 2 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 3 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 4 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 5 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 6 for Cell
73439863
V900R012
73439864
VS.HSUPA.BeChT hroughput.SPI2
V900R012
73439865
V900R012
73439866
V900R012
73439867
V900R012
73439868
V900R012
Issue 01 (2013-05-04)
2391
Counter ID 73439869
Counter Name VS.HSUPA.BeChT hroughput.SPI7
Counter Description Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 7 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 8 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 9 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 10 for Cell
73439870
V900R012
73439871
V900R012
73439872
V900R012
None
1.12.45.1 Number of Times of Downlink Throughput of BE Services with SPI Set to 8 with a Certain Range in a Measurement Period for HSDPA Cell Counters
Counter ID 73421554 Counter Name VS.HSDPA.SPI8BeChThroughput.0 Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 0 kbit/s and 32 kbit/s in a Measurement Period for Cell
Issue 01 (2013-05-04)
2392
Counter ID 73421555
Counter Name VS.HSDPA.SPI8BeChThroughput.1
Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 32 kbit/ s and 64 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 64 kbit/ s and 256 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 256 kbit/s and 512 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 512 kbit/s and 768 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 768 kbit/s and 1024 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 1024 kbit/s and 1536 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 1536 kbit/s and 2048 kbit/s in a Measurement Period for Cell
73421556
VS.HSDPA.SPI8BeChThroughput.2
73421557
73421558
73421559
73421560
73421561
Issue 01 (2013-05-04)
2393
Counter ID 73421562
Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 2048 kbit/s and 3072 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 3072 kbit/s and 4096 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 4096 kbit/s and 6144 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 6144 kbit/s and 8192 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 Between 8192 kbit/s and 12288 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 8 larger than 12288 kbit/s in a Measurement Period for Cell
73421563
73421564
73421565
73421566
73421567
Description
These counters provide the number of times that the average downlink throughput of MAC-d flows carrying BE services whose SPIs are set to eight falls within each range in the HSDPA serving cell. For DC-HSDPA users, this counter is measured only in the primary cell based on the total throughput on the primary and secondary carriers.
Issue 01 (2013-05-04)
2394
Measurement point
In the HSDPA serving cell, the RNC samples the average downlink throughput of MAC-d flows carrying each BE service whose SPI is set to eight at the Radio Link Control (RLC) layer every 20s. The measured data excludes the RLC headers and retransmitted data. When the throughput falls within a certain range, the corresponding counter is increased by one. At the end of the measurement period, the number of times the throughput falls into each range is accumulated.
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.SPI8BeChThroughput.0 VS.HSDPA.SPI8BeChThroughput.1 VS.HSDPA.SPI8BeChThroughput.2 VS.HSDPA.SPI8BeChThroughput.3 VS.HSDPA.SPI8BeChThroughput.4 VS.HSDPA.SPI8BeChThroughput.5 VS.HSDPA.SPI8BeChThroughput.6 VS.HSDPA.SPI8BeChThroughput.7 VS.HSDPA.SPI8BeChThroughput.8 VS.HSDPA.SPI8BeChThroughput.9 VS.HSDPA.SPI8BeChThroughput.10 VS.HSDPA.SPI8BeChThroughput.11 Feature ID WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 Feature Name Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA
Issue 01 (2013-05-04)
2395
Counter Name VS.HSDPA.SPI8BeChThroughput.12 VS.HSDPA.SPI8BeChThroughput.13
Feature Name Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA
Counter ID 73421568 Counter Name VS.HSDPA.SPI5BeChThroughput.0 Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 0 kbit/s and 32 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 32 kbit/ s and 64 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 64 kbit/ s and 256 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 256 kbit/s and 512 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 512 kbit/s and 768 kbit/s in a Measurement Period for Cell
73421569
73421570
73421571
73421572
Issue 01 (2013-05-04)
2396
Counter ID 73421573
Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 768 kbit/s and 1024 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 1024 kbit/s and 1536 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 1536 kbit/s and 2048 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 2048 kbit/s and 3072 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 3072 kbit/s and 4096 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 4096 kbit/s and 6144 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 6144 kbit/s and 8192 kbit/s in a Measurement Period for Cell
73421574
73421575
73421576
73421577
73421578
73421579
Issue 01 (2013-05-04)
2397
Counter ID 73421580
Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 Between 8192 kbit/s and 12288 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 5 larger than 12288 kbit/s in a Measurement Period for Cell
73421581
Description
These counters provide the number of times that the average downlink throughput of MAC-d flows carrying BE services whose SPIs are set to five falls within each range. For DC-HSDPA users, this counter is measured only in the primary cell based on the total throughput on the primary and secondary carriers.
Measurement point
In the HSDPA serving cell, the RNC samples the average downlink throughput of MAC-d flows carrying each BE service whose SPI is set to five at the Radio Link Control (RLC) layer every 20s. The measured data excludes the RLC headers and retransmitted data. When the throughput falls within a certain range, the corresponding counter is increased by one. At the end of the measurement period, the number of times the throughput falls into each range is accumulated.
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.SPI5BeChThroughput.0 VS.HSDPA.SPI5BeChThroughput.1 VS.HSDPA.SPI5BeChThroughput.2
Issue 01 (2013-05-04)
Feature Name Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA
2398
Counter Name VS.HSDPA.SPI5BeChThroughput.3 VS.HSDPA.SPI5BeChThroughput.4 VS.HSDPA.SPI5BeChThroughput.5 VS.HSDPA.SPI5BeChThroughput.6 VS.HSDPA.SPI5BeChThroughput.7 VS.HSDPA.SPI5BeChThroughput.8 VS.HSDPA.SPI5BeChThroughput.9 VS.HSDPA.SPI5BeChThroughput.10 VS.HSDPA.SPI5BeChThroughput.11 VS.HSDPA.SPI5BeChThroughput.12 VS.HSDPA.SPI5BeChThroughput.13
Feature Name Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA
Counter ID 73421582 Counter Name VS.HSDPA.SPI2BeChThroughput.0 Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 0 kbit/s and 32 kbit/s in a Measurement Period for Cell
Issue 01 (2013-05-04)
2399
Counter ID 73421583
Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 32 kbit/ s and 64 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 64 kbit/ s and 256 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 256 kbit/s and 512 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 512 kbit/s and 768 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 768 kbit/s and 1024 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 1024 kbit/s and 1536 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 1536 kbit/s and 2048 kbit/s in a Measurement Period for Cell
73421584
73421585
73421586
73421587
73421588
73421589
Issue 01 (2013-05-04)
2400
Counter ID 73421590
Counter Description Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 2048 kbit/s and 3072 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 3072 kbit/s and 4096 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 4096 kbit/s and 6144 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 6144 kbit/s and 8192 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 Between 8192 kbit/s and 12288 kbit/s in a Measurement Period for Cell Number of Times of Mean Downlink Throughput of HSDPA BE Services with SPI Set to 2 larger than 12288 kbit/s in a Measurement Period for Cell
73421591
73421592
73421593
73421594
73421595
Description
These counters provide the number of times that the average downlink throughput of MAC-d flows carrying BE services whose SPIs are set to two falls within each range in the HSDPA serving cell. For DC-HSDPA users, this counter is measured only in the primary cell based on the total throughput on the primary and secondary carriers.
Issue 01 (2013-05-04)
2401
Measurement point
In the HSDPA serving cell, the RNC samples the average downlink throughput of MAC-d flows carrying each BE service whose SPI is set to two at the Radio Link Control (RLC) layer every 20s. The measured data excludes the RLC headers and retransmitted data. When the throughput falls within a certain range, the corresponding counter is increased by one. At the end of the measurement period, the number of times the throughput falls into each range is accumulated.
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.SPI2BeChThroughput.0 VS.HSDPA.SPI2BeChThroughput.1 VS.HSDPA.SPI2BeChThroughput.2 VS.HSDPA.SPI2BeChThroughput.3 VS.HSDPA.SPI2BeChThroughput.4 VS.HSDPA.SPI2BeChThroughput.5 VS.HSDPA.SPI2BeChThroughput.6 VS.HSDPA.SPI2BeChThroughput.7 VS.HSDPA.SPI2BeChThroughput.8 VS.HSDPA.SPI2BeChThroughput.9 VS.HSDPA.SPI2BeChThroughput.10 VS.HSDPA.SPI2BeChThroughput.11 Feature ID WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 Feature Name Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA
Issue 01 (2013-05-04)
2402
Counter Name VS.HSDPA.SPI2BeChThroughput.12 VS.HSDPA.SPI2BeChThroughput.13
Feature Name Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA
1.12.45.4 Number of Times of Uplink Throughput of BE Services with SPI Set to 8 with a Certain Range in a Measurement Period for HSUPA Cell Counters
Counter ID 73421596 Counter Name VS.HSUPA.SPI8BeChThroughput.0 Counter Description Number of Times of Mean Downlink Throughput of HSDPANumber of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 0 kbit/s and 32 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 32 kbit/ s and 64 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 64 kbit/ s and 256 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 256 kbit/s and 512 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 512 kbit/s and 768 kbit/s in a Measurement Period for Cell
2403
73421597
VS.HSUPA.SPI8BeChThroughput.1
73421598
73421599
73421600
Issue 01 (2013-05-04)
Counter ID 73421601
Counter Name VS.HSUPA.SPI8BeChThroughput.5
Counter Description Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 768 kbit/s and 1024 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 1024 kbit/s and 1536 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 1536 kbit/s and 2048 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 2048 kbit/s and 3072 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 Between 3072 kbit/s and 4096 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 8 larger than 4096 kbit/s in a Measurement Period for Cell
73421602
73421603
73421604
73421605
73421606
Description
These counters provide the number of times that the average uplink throughput of MAC-d flows carrying BE services whose SPIs are set to eight when the throughput falls within each range in the HSUPA serving cell. For DC-HSUPA users, these counters are measured only in the primary cell based on the total throughput on the primary and secondary carriers.
Issue 01 (2013-05-04)
2404
Measurement point
In the HSUPA serving cell, the RNC samples the average uplink throughput of MAC-d flows carrying each BE service whose SPI is set to eight at the Radio Link Control (RLC) layer every 20s. The measured data excludes the RLC headers and retransmitted data. When the throughput falls within a certain range, the corresponding counter is increased by one. At the end of the measurement period, the number of times the throughput falls into each range is accumulated.
Formula
None
Unit
None
Related Features
Counter Name VS.HSUPA.SPI8BeChThroughput.0 VS.HSUPA.SPI8BeChThroughput.1 VS.HSUPA.SPI8BeChThroughput.2 VS.HSUPA.SPI8BeChThroughput.3 VS.HSUPA.SPI8BeChThroughput.4 VS.HSUPA.SPI8BeChThroughput.5 VS.HSUPA.SPI8BeChThroughput.6 VS.HSUPA.SPI8BeChThroughput.7 VS.HSUPA.SPI8BeChThroughput.8 VS.HSUPA.SPI8BeChThroughput.9 VS.HSUPA.SPI8BeChThroughput.10 Feature ID WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 Feature Name Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA
Issue 01 (2013-05-04)
2405
1.12.45.5 Number of Times of Uplink Throughput of BE Services with SPI Set to 5 with a Certain Range in a Measurement Period for HSUPA Cell Counters
Counter ID 73421607 Counter Name VS.HSUPA.SPI5BeChThroughput.0 Counter Description Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 5 Between 0 kbit/s and 32 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 5 Between 32 kbit/ s and 64 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 5 Between 64 kbit/ s and 256 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 5 Between 256 kbit/s and 512 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 5 Between 512 kbit/s and 768 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 5 Between 768 kbit/s and 1024 kbit/s in a Measurement Period for Cell
73421608
73421609
73421610
73421611
73421612
Issue 01 (2013-05-04)
2406
Counter ID 73421613
Counter Description Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 5 Between 1024 kbit/s and 1536 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 5 Between 1536 kbit/s and 2048 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 5 Between 2048 kbit/s and 3072 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 5 Between 3072 kbit/s and 4096 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 5 larger than 4096 kbit/s in a Measurement Period for Cell
73421614
73421615
73421616
73421617
Description
These counters provide the number of times that the average uplink throughput of MAC-d flows carrying BE services whose SPIs are set to five when the throughput falls within each range in the HSUPA serving cell. For DC-HSUPA users, these counters are measured only in the primary cell based on the total throughput on the primary and secondary carriers.
Measurement point
In the HSUPA serving cell, the RNC samples the average uplink throughput of MAC-d flows carrying each BE service whose SPI is set to five at the Radio Link Control (RLC) layer every 20s. The measured data excludes the RLC headers and retransmitted data. When the throughput falls within a certain range, the corresponding counter is increased by one. At the end of the measurement period, the number of times the throughput falls into each range is accumulated.
Issue 01 (2013-05-04)
2407
Formula
None
Unit
None
Related Features
1.12.45.6 Number of Times of Uplink Throughput of BE Services with SPI Set to 2 with a Certain Range in a Measurement Period for HSUPA Cell
Issue 01 (2013-05-04)
2408
Counters
Counter ID 73421618 Counter Name VS.HSUPA.SPI2BeChThroughput.0 Counter Description Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 0 kbit/s and 32 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 32 kbit/ s and 64 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 64 kbit/ s and 256 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 256 kbit/s and 512 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 512 kbit/s and 768 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 768 kbit/s and 1024 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 1024 kbit/s and 1536 kbit/s in a Measurement Period for Cell
73421619
73421620
73421621
73421622
73421623
73421624
Issue 01 (2013-05-04)
2409
Counter ID 73421625
Counter Description Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 1536 kbit/s and 2048 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 2048 kbit/s and 3072 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 Between 3072 kbit/s and 4096 kbit/s in a Measurement Period for Cell Number of Times of Mean Uplink Throughput of HSUPA BE Services with SPI Set to 2 larger than 4096 kbit/s in a Measurement Period for Cell
73421626
73421627
73421628
Description
These counters provide the number of times that the average uplink throughput of MAC-d flows carrying BE services whose SPIs are set to two when the throughput falls within each range in the HSUPA serving cell. For DC-HSUPA users, these counters are measured only in the primary cell based on the total throughput on the primary and secondary carriers.
Measurement point
In the HSUPA serving cell, the RNC samples the average uplink throughput of MAC-d flows carrying each BE service whose SPI is set to two at the Radio Link Control (RLC) layer every 20s. The measured data excludes the RLC headers and retransmitted data. When the throughput falls within a certain range, the corresponding counter is increased by one. At the end of the measurement period, the number of times the throughput falls into each range is accumulated.
Formula
None
Unit
None
Related Features
1.12.45.7 Number of Bytes Sent on Downlink HSDPA Mac-d flow of BE Services with SPI Setting to Different Values Counters
Counter ID 73421629 Counter Name VS.HSDPA.BeChThroughp ut.TotalBytes.SPI2 Counter Description Number of Bytes Sent in Downlink on HSDPA MACd flow of BE Services with SPI Set to 2 for Cell Number of Bytes Sent in Downlink on HSDPA MACd flow of BE Services with SPI Set to 3 for Cell
73421630
VS.HSDPA.BeChThroughp ut.TotalBytes.SPI3
Issue 01 (2013-05-04)
2411
Counter ID 73421631
Counter Name VS.HSDPA.BeChThroughp ut.TotalBytes.SPI4
Counter Description Number of Bytes Sent in Downlink on HSDPA MACd flow of BE Services with SPI Set to 4 for Cell Number of Bytes Sent in Downlink on HSDPA MACd flow of BE Services with SPI Set to 5 for Cell Number of Bytes Sent in Downlink on HSDPA MACd flow of BE Services with SPI Set to 6 for Cell Number of Bytes Sent in Downlink on HSDPA MACd flow of BE Services with SPI Set to 7 for Cell Number of Bytes Sent in Downlink on HSDPA MACd flow of BE Services with SPI Set to 8 for Cell Number of Bytes Sent in Downlink on HSDPA MACd flow of BE Services with SPI Set to 9 for Cell Number of Bytes Sent in Downlink on HSDPA MACd flow of BE Services with SPI Set to 10 for Cell
73421632
73421633
73421634
73421635
73421636
73421637
Description
These counters provide the number of bytes that are sent on downlink HSDPA MAC-d flows carrying BE services with different SPIs. For DC-HSDPA users, this counter is measured only in the primary cell based on the total number of bytes sent on the primary and secondary carriers.
Measurement point
A counter is measured when the data of a BE service with the corresponding SPI is sent at the RLC layer on the downlink. The measured data excludes the RLC headers and retransmitted data.
Formula
None
Unit
byte
Related Features
Counter Name VS.HSDPA.BeChThroughp ut.TotalBytes.SPI2 VS.HSDPA.BeChThroughp ut.TotalBytes.SPI3 VS.HSDPA.BeChThroughp ut.TotalBytes.SPI4 VS.HSDPA.BeChThroughp ut.TotalBytes.SPI5 VS.HSDPA.BeChThroughp ut.TotalBytes.SPI6 VS.HSDPA.BeChThroughp ut.TotalBytes.SPI7 VS.HSDPA.BeChThroughp ut.TotalBytes.SPI8 VS.HSDPA.BeChThroughp ut.TotalBytes.SPI9 VS.HSDPA.BeChThroughp ut.TotalBytes.SPI10 Feature ID WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 Feature Name Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA
1.12.45.8 Number of Bytes Received on Uplink HSUPA Mac-d flow of BE Services with SPI Setting to Different Values Counters
Counter ID 73421638 Counter Name VS.HSUPA.BeChThroughp ut.TotalBytes.SPI2 Counter Description Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 2 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 3 for Cell
73421639
VS.HSUPA.BeChThroughp ut.TotalBytes.SPI3
Issue 01 (2013-05-04)
2413
Counter ID 73421640
Counter Name VS.HSUPA.BeChThroughp ut.TotalBytes.SPI4
Counter Description Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 4 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 5 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 6 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 7 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 8 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 9 for Cell Number of Bytes Received in Uplink on HSUPA MAC-d flow of BE Services with SPI Set to 10 for Cell
73421641
73421642
73421643
73421644
73421645
73421646
Description
These counters provide the number of bytes that are received on uplink HSUPA MAC-d flows carrying BE services with different SPIs.For DC-HSUPA users, this counter is measured only in the primary cell based on the total number of bytes received on the primary and secondary carriers.
Measurement point
A counter is measured when the data of a BE service with the corresponding SPI is sent at the RLC layer on the uplink. The measured data excludes the RLC headers and retransmitted data.
Formula
None
Unit
byte
Related Features
Counter Name VS.HSUPA.BeChThroughp ut.TotalBytes.SPI2 VS.HSUPA.BeChThroughp ut.TotalBytes.SPI3 VS.HSUPA.BeChThroughp ut.TotalBytes.SPI4 VS.HSUPA.BeChThroughp ut.TotalBytes.SPI5 VS.HSUPA.BeChThroughp ut.TotalBytes.SPI6 VS.HSUPA.BeChThroughp ut.TotalBytes.SPI7 VS.HSUPA.BeChThroughp ut.TotalBytes.SPI8 VS.HSUPA.BeChThroughp ut.TotalBytes.SPI9 VS.HSUPA.BeChThroughp ut.TotalBytes.SPI10 Feature ID WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 Feature Name Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA
1.12.45.9 Mean Downlink Throughput of HSDPA Mac-d flow of BE Services with SPI Setting to Different Values Counters
Counter ID 73439855 Counter Name VS.HSDPA.BeChThroughp ut.SPI2 Counter Description Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 2 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 3 for Cell
73439856
VS.HSDPA.BeChThroughp ut.SPI3
Issue 01 (2013-05-04)
2415
Counter ID 73439857
Counter Name VS.HSDPA.BeChThroughp ut.SPI4
Counter Description Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 4 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 5 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 6 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 7 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 8 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 9 for Cell Mean Downlink Throughput of HSDPA MAC-d flow of BE Services with SPI Set to 10 for Cell
73439858
73439859
73439860
73439861
73439862
73439863
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73421655 73421647 73421648 73421649 Counter Name VS.HSDPA.BeChThroughp ut.Times.SPI10 VS.HSDPA.BeChThroughp ut.Times.SPI2 VS.HSDPA.BeChThroughp ut.Times.SPI3 VS.HSDPA.BeChThroughp ut.Times.SPI4 Counter Description VS.HSDPA.BeChThroughp ut.Times.SPI10 VS.HSDPA.BeChThroughp ut.Times.SPI2 VS.HSDPA.BeChThroughp ut.Times.SPI3 VS.HSDPA.BeChThroughp ut.Times.SPI4
Issue 01 (2013-05-04)
2416
Counter ID 73421650 73421651 73421652 73421653 73421654
Counter Name VS.HSDPA.BeChThroughp ut.Times.SPI5 VS.HSDPA.BeChThroughp ut.Times.SPI6 VS.HSDPA.BeChThroughp ut.Times.SPI7 VS.HSDPA.BeChThroughp ut.Times.SPI8 VS.HSDPA.BeChThroughp ut.Times.SPI9
Counter Description VS.HSDPA.BeChThroughp ut.Times.SPI5 VS.HSDPA.BeChThroughp ut.Times.SPI6 VS.HSDPA.BeChThroughp ut.Times.SPI7 VS.HSDPA.BeChThroughp ut.Times.SPI8 VS.HSDPA.BeChThroughp ut.Times.SPI9
Description
These counters provide the downlink average throughput of HSDPA Mac-d flows carrying BE services with different SPIs. For DC-HSDPA users, this counter is measured only in the primary cell based on the total throughput on the primary and secondary carriers.
Measurement point
The duration and number of bits of BE services sent at the RLC layer are accumulated on the basis of different SPIs. At the end of the measurement period, the corresponding counters are calculated by dividing the total number of bits by the total period of time. The measured data excludes the RLC headers and retransmitted data.
Formula
VS.HSDPA.BeChThroughput.SPI2 = {8}* [VS.HSDPA.BeChThroughput.TotalBytes.SPI2]/ [VS.HSDPA.BeChThroughput.Times.SPI2] VS.HSDPA.BeChThroughput.SPI3 = {8}* [VS.HSDPA.BeChThroughput.TotalBytes.SPI3]/ [VS.HSDPA.BeChThroughput.Times.SPI3] VS.HSDPA.BeChThroughput.SPI4 = {8}* [VS.HSDPA.BeChThroughput.TotalBytes.SPI4]/ [VS.HSDPA.BeChThroughput.Times.SPI4] VS.HSDPA.BeChThroughput.SPI5 = {8}* [VS.HSDPA.BeChThroughput.TotalBytes.SPI5]/ [VS.HSDPA.BeChThroughput.Times.SPI5] VS.HSDPA.BeChThroughput.SPI6 = {8}* [VS.HSDPA.BeChThroughput.TotalBytes.SPI6]/ [VS.HSDPA.BeChThroughput.Times.SPI6] VS.HSDPA.BeChThroughput.SPI7 = {8}* [VS.HSDPA.BeChThroughput.TotalBytes.SPI7]/ [VS.HSDPA.BeChThroughput.Times.SPI7]
VS.HSDPA.BeChThroughput.SPI8 = {8}* [VS.HSDPA.BeChThroughput.TotalBytes.SPI8]/ [VS.HSDPA.BeChThroughput.Times.SPI8] VS.HSDPA.BeChThroughput.SPI9 = {8}* [VS.HSDPA.BeChThroughput.TotalBytes.SPI9]/ [VS.HSDPA.BeChThroughput.Times.SPI9] VS.HSDPA.BeChThroughput.SPI10 = {8}* [VS.HSDPA.BeChThroughput.TotalBytes.SPI10]/ [VS.HSDPA.BeChThroughput.Times.SPI10]
Unit
kbit/s
Related Features
Counter Name VS.HSDPA.BeChThroughp ut.SPI2 VS.HSDPA.BeChThroughp ut.SPI3 VS.HSDPA.BeChThroughp ut.SPI4 VS.HSDPA.BeChThroughp ut.SPI5 VS.HSDPA.BeChThroughp ut.SPI6 VS.HSDPA.BeChThroughp ut.SPI7 VS.HSDPA.BeChThroughp ut.SPI8 VS.HSDPA.BeChThroughp ut.SPI9 VS.HSDPA.BeChThroughp ut.SPI10 Feature ID WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 WRFD-01061008 Feature Name Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA Interactive and Background Traffic Class on HSDPA
1.12.45.10 Mean Downlink Throughput of HSUPA Mac-d flow of BE Services with SPI Setting to Different Values
Issue 01 (2013-05-04)
2418
Counters
Counter ID 73439864 Counter Name VS.HSUPA.BeChThroughp ut.SPI2 Counter Description Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 2 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 3 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 4 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 5 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 6 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 7 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 8 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 9 for Cell Mean Uplink Throughput of HSUPA MAC-d flow of BE Services with SPI Set to 10 for Cell
73439865
VS.HSUPA.BeChThroughp ut.SPI3
73439866
73439867
73439868
73439869
73439870
73439871
73439872
Issue 01 (2013-05-04)
2419
Counter ID 73421664 73421656 73421657 73421658 73421659 73421660 73421661 73421662 73421663
Counter Name VS.HSUPA.BeChThroughp ut.Times.SPI10 VS.HSUPA.BeChThroughp ut.Times.SPI2 VS.HSUPA.BeChThroughp ut.Times.SPI3 VS.HSUPA.BeChThroughp ut.Times.SPI4 VS.HSUPA.BeChThroughp ut.Times.SPI5 VS.HSUPA.BeChThroughp ut.Times.SPI6 VS.HSUPA.BeChThroughp ut.Times.SPI7 VS.HSUPA.BeChThroughp ut.Times.SPI8 VS.HSUPA.BeChThroughp ut.Times.SPI9
Counter Description VS.HSUPA.BeChThroughp ut.Times.SPI10 VS.HSUPA.BeChThroughp ut.Times.SPI2 VS.HSUPA.BeChThroughp ut.Times.SPI3 VS.HSUPA.BeChThroughp ut.Times.SPI4 VS.HSUPA.BeChThroughp ut.Times.SPI5 VS.HSUPA.BeChThroughp ut.Times.SPI6 VS.HSUPA.BeChThroughp ut.Times.SPI7 VS.HSUPA.BeChThroughp ut.Times.SPI8 VS.HSUPA.BeChThroughp ut.Times.SPI9
Description
These counters provide the uplink average throughput of HSUPA MAC-d flows carrying BE services with different SPIs. For DC-HSUPA users, these counters are measured only in the primary cell based on the total throughput on the primary and secondary carriers.
Measurement point
The duration and number of bits of BE services received at the Radio Link Control (RLC) layer are accumulated for different SPIs. At the end of the measurement period, these counters are calculated by dividing the corresponding total number of bits by the total period of time. The RLC headers and retransmitted data are excluded.
Formula
VS.HSUPA.BeChThroughput.SPI2 = {8}* [VS.HSUPA.BeChThroughput.TotalBytes.SPI2]/ [VS.HSUPA.BeChThroughput.Times.SPI2] VS.HSUPA.BeChThroughput.SPI3 = {8}* [VS.HSUPA.BeChThroughput.TotalBytes.SPI3]/ [VS.HSUPA.BeChThroughput.Times.SPI3] VS.HSUPA.BeChThroughput.SPI4 = {8}* [VS.HSUPA.BeChThroughput.TotalBytes.SPI4]/ [VS.HSUPA.BeChThroughput.Times.SPI4]
VS.HSUPA.BeChThroughput.SPI5 = {8}* [VS.HSUPA.BeChThroughput.TotalBytes.SPI5]/ [VS.HSUPA.BeChThroughput.Times.SPI5] VS.HSUPA.BeChThroughput.SPI6 = {8}* [VS.HSUPA.BeChThroughput.TotalBytes.SPI6]/ [VS.HSUPA.BeChThroughput.Times.SPI6] VS.HSUPA.BeChThroughput.SPI7 = {8}* [VS.HSUPA.BeChThroughput.TotalBytes.SPI7]/ [VS.HSUPA.BeChThroughput.Times.SPI7] VS.HSUPA.BeChThroughput.SPI8 = {8}* [VS.HSUPA.BeChThroughput.TotalBytes.SPI8]/ [VS.HSUPA.BeChThroughput.Times.SPI8] VS.HSUPA.BeChThroughput.SPI9 = {8}* [VS.HSUPA.BeChThroughput.TotalBytes.SPI9]/ [VS.HSUPA.BeChThroughput.Times.SPI9] VS.HSUPA.BeChThroughput.SPI10 = {8}* [VS.HSUPA.BeChThroughput.TotalBytes.SPI10]/ [VS.HSUPA.BeChThroughput.Times.SPI10]
Unit
kbit/s
Related Features
Counter Name VS.HSUPA.BeChThroughp ut.SPI2 VS.HSUPA.BeChThroughp ut.SPI3 VS.HSUPA.BeChThroughp ut.SPI4 VS.HSUPA.BeChThroughp ut.SPI5 VS.HSUPA.BeChThroughp ut.SPI6 VS.HSUPA.BeChThroughp ut.SPI7 VS.HSUPA.BeChThroughp ut.SPI8 VS.HSUPA.BeChThroughp ut.SPI9 Feature ID WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 WRFD-01061206 Feature Name Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA Interactive and Background Traffic Class on HSUPA
Issue 01 (2013-05-04)
2421
Counter Name VS.HSUPA.BeChThroughp ut.SPI10
Feature Name Interactive and Background Traffic Class on HSUPA
1.12.46 Measurement related to throughput and data rate per cell (THRUPUT.Cell)
Overview
The RNC traffic measurement is used to measure the traffic of the CS domain and PS domain in the RNC. Here, the traffic of the CS domain is indicated by equivalent Erlang while the traffic of the PS domain by kbit per second.
Counters
Counter ID 67202812 Counter Name VS.CS.Conv.Kbps. DL64 Counter Description Average DL Rate of 64 Kbit/s CS Conversational Services for Cell DL Traffic Volume of 64 Kbit/s CS Conversational Services for Cel Average DL Rate of 57.6 Kbit/s CS Streaming Services for Cell DL Traffic Volume of 57.6 Kbit/s CS Streaming Services for Cell Average DL Rate of 8 Kbit/s PS Background Services for Cell DL Traffic Volume of 8 Kbit/s PS Background Services for Cell Original Release Earlier than V900R011
67183986
VS.CS.Conv.DL. 64.Traffic
67202816
VS.CS.Str.Kbps.D L57.6
67183990
VS.CS.Str.DL. 57.6.Traffic
67202819
VS.PS.Bkg.Kbps.D L8
67183993
VS.PS.Bkg.DL. 8.Traffic
Issue 01 (2013-05-04)
2422
Counter ID 67202820
Counter Name VS.PS.Bkg.Kbps.D L16
Counter Description Average DL Rate of 16 Kbit/s PS Background Services for Cell DL Traffic Volume of 16 Kbit/s PS Background Services for Cell Average DL Rate of 32 Kbit/s PS Background Services for Cell DL Traffic Volume of 32 Kbit/s PS Background Services for Cell Average DL Rate of 64 Kbit/s PS Background Services for Cell DL Traffic Volume of 64 Kbit/s PS Background Services for Cell Average DL Rate of 128 Kbit/s PS Background Services for Cell DL Traffic Volume of 128 Kbit/s PS Background Services for Cell Average DL Rate of 144 Kbit/s PS Background Services for Cell DL Traffic Volume of 144 Kbit/s PS Background Services for Cell
67183994
67202821
VS.PS.Bkg.Kbps.D L32
67183995
67202822
67183996
67202823
67183997
67202824
67183998
Issue 01 (2013-05-04)
2423
Counter ID 67202825
Counter Name VS.PS.Bkg.Kbps.D L256
Counter Description Average DL Rate of 256 Kbit/s PS Background Services for Cell DL Traffic Volume of 256 Kbit/s PS Background Services for Cell Average DL Rate of 384 Kbit/s PS Background Services for Cell DL Traffic Volume of 384 Kbit/s PS Background Services for Cell Average DL Rate of 8 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 8 Kbit/s PS Interactive Services for Cell Average DL Rate of 16 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 16 Kbit/s PS Interactive Services for Cell Average DL Rate of 32 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 32 Kbit/s PS Interactive Services for Cell
67183999
67202826
67184000
67202827
VS.PS.Int.Kbps.DL 8
67184001
VS.PS.Int.DL. 8.Traffic
67202828
VS.PS.Int.Kbps.DL 16
67184002
67202829
67184003
Issue 01 (2013-05-04)
2424
Counter ID 67202830
Counter Name VS.PS.Int.Kbps.DL 64
Counter Description Average DL Rate of 64 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 64 Kbit/s PS Interactive Services for Cell Average DL Rate of 128 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 128 Kbit/s PS Interactive Services for Cell Average DL Rate of 144 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 144 Kbit/s PS Interactive Services for Cell Average DL Rate of 256 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 256 Kbit/s PS Interactive Services for Cell Average DL Rate of 384 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 384 Kbit/s PS Interactive Services for Cell
67184004
67202831
67184005
67202832
67184006
67202833
67184007
67202834
67184008
Issue 01 (2013-05-04)
2425
Counter ID 67202835
Counter Name VS.PS.Str.Kbps.D L32
Counter Description Average DL Rate of 32 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 32 Kbit/s PS Streaming Services for Cell Average DL Rate of 64 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 64 Kbit/s PS Streaming Services for Cell Average DL Rate of 128 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 128 Kbit/s PS Streaming Services for Cell Average DL Rate of 144 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 144 Kbit/s PS Streaming Services for Cell Average UL Rate of 8 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 8 Kbit/s PS R99 Background Services for Cell
67184009
VS.PS.Str.DL. 32.Traffic
67202836
VS.PS.Str.Kbps.D L64
67184010
67202837
67184011
67202838
67184012
67202840
VS.PS.Bkg.Kbps.U L8
67184014
VS.PS.Bkg.UL. 8.Traffic
Issue 01 (2013-05-04)
2426
Counter ID 67202841
Counter Name VS.PS.Bkg.Kbps.U L16
Counter Description Average UL Rate of 16 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 16 Kbit/s PS R99 Background Services for Cell Average UL Rate of 32 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 32 Kbit/s PS R99 Background Services for Cell Average UL Rate of 64 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 64 Kbit/s PS R99 Background Services for Cell Average UL Rate of 128 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 128 Kbit/s PS R99 Background Services for Cell Average UL Rate of 144 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 144 Kbit/s PS R99 Background Services for Cell
67184015
67202842
VS.PS.Bkg.Kbps.U L32
67184016
67202843
67184017
67202844
67184018
67202845
67184019
Issue 01 (2013-05-04)
2427
Counter ID 67202846
Counter Name VS.PS.Bkg.Kbps.U L256
Counter Description Average UL Rate of 256 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 256 Kbit/s PS R99 Background Services for Cell Average UL Rate of 384 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 384 Kbit/s PS R99 Background Services for Cell Average UL Rate of 8 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 8 Kbit/s PS R99 Interactive Services for Cell Average UL Rate of 16 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 16 Kbit/s PS R99 Interactive Services for Cell Average UL Rate of 32 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 32 Kbit/s PS R99 Interactive Services for Cell
67184020
67202847
67184021
67202848
VS.PS.Int.Kbps.UL 8
67184022
VS.PS.Int.UL. 8.Traffic
67202849
VS.PS.Int.Kbps.UL 16
67184023
67202850
67184024
Issue 01 (2013-05-04)
2428
Counter ID 67202851
Counter Name VS.PS.Int.Kbps.UL 64
Counter Description Average UL Rate of 64 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 64 Kbit/s PS R99 Interactive Services for Cell Average UL Rate of 128 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 128 Kbit/s PS R99 Interactive Services for Cell Average UL Rate of 144 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 144 Kbit/s PS R99 Interactive Services for Cell Average UL Rate of 256 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 256 Kbit/s PS R99 Interactive Services for Cell Average UL Rate of 384 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 384 Kbit/s PS R99 Interactive Services for Cell
67184025
67202852
67184026
67202853
67184027
67202854
67184028
67202855
67184029
Issue 01 (2013-05-04)
2429
Counter ID 67202856
Counter Name VS.PS.Str.Kbps.U L16
Counter Description Average UL Rate of 16 Kbit/s PS Streaming Services for Cell UL Traffic Volume of 16 Kbit/s PS Streaming Services for Cell Average UL Rate of 32 Kbit/s PS Streaming Services for Cell UL Traffic Volume of 32 Kbit/s PS Streaming Services for Cell Average UL Rate of 64 Kbit/s PS Streaming Services for Cell UL Traffic Volume of 64 Kbit/s PS Streaming Services for Cell Average UL Rate of Signaling on DCCH for Cell UL Traffic Volume of Signaling on DCCH for Cell Average DL Rate of Signaling on DCCH for Cell DL Traffic Volume of Signaling on DCCH for Cell UL Traffic Volume of AMR Services for Best Cell DL Traffic Volume of AMR Services for Best Cell
67184030
VS.PS.Str.UL. 16.Traffic
67202857
VS.PS.Str.Kbps.U L32
67184031
67202858
67184032
67202859
VS.DcchSrbKbps. Ul VS.DcchSRB.Ul.Tr affic VS.DcchSrbKbps. Dl VS.DcchSRB.Dl.Tr affic VS.AMR.UL.Traffi c.BestCell VS.AMR.DL.Traffi c.BestCell
67189903
67202860
67189905
67203449
67203450
Issue 01 (2013-05-04)
2430
Counter ID 67203451
Counter Name VS.VP.UL.Traffic. BestCell VS.VP.DL.Traffic. BestCell VS.PS.BE.kbits.UL .0.32.BestCell
Counter Description UL Traffic Volume of VP Services for Best Cell DL Traffic Volume of VP Services for Best Cell UL Traffic Volume of PS BE Services (0 Kbit/s < UL Bit Rate <= 32 Kbit/s) for Best Cell DL Traffic Volume of PS BE Services (0 Kbit/s < DL Bit Rate <= 32 Kbit/s) for Best Cell UL Traffic Volume of PS BE Services (32 Kbit/s < DL Bit Rate <= 64 Kbit/s) for Best Cell DL Traffic Volume of PS BE Services (32 Kbit/s < DL Bit Rate <= 64 Kbit/s) for Best Cell UL Traffic Volume of PS BE Services (64 Kbit/s < DL Bit Rate <= 144 Kbit/s) for Best Cell DL Traffic Volume of PS BE Services (64 Kbit/s < DL Bit Rate <= 144 Kbit/s) for Best Cell UL Traffic Volume of PS BE Services (144 Kbit/s < DL Bit Rate <= 384 Kbit/s) for Best Cell
67203452
67203453
67203454
VS.PS.BE.kbits.DL .0.32.BestCell
67203455
VS.PS.BE.kbits.UL .32.64.BestCell
67203456
67203457
67203458
67203459
Issue 01 (2013-05-04)
2431
Counter ID 67203460
Counter Name VS.PS.BE.kbits.DL .144.384.BestCell
Counter Description DL Traffic Volume of PS BE Services (144 Kbit/s < DL Bit Rate <= 384 Kbit/s) for Best Cell Equivalent Erlang for AMR Services for Best Cell Num Of Erlang of VP service in the best cell Average Throughput of PTM MBMS Services for Cell Average Throughput of PTP MBMS Services for Cell Average DL Rate of 8 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 8 Kbit/s PS Streaming Services for Cell Average DL Rate of 16 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 16 Kbit/s PS Streaming Services for Cell Average DL Rate of 256 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 256 Kbit/s PS Streaming Services for Cell
67192689
VS.AMR.Erlang.B estCell VS.VP.Erlang.Best Cell VS.MBMS.PTM.M eanThroughput VS.MBMS.PTP.Me anThroughput VS.PS.Str.Kbps.D L8
Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 V900R012
67192690
67204482
67204483
67204248
67193548
V900R012
67204249
V900R012
67193550
V900R012
67204250
V900R012
67193552
V900R012
Issue 01 (2013-05-04)
2432
Counter ID 67204251
Counter Name VS.PS.Str.Kbps.D L384
Counter Description Average DL Rate of 384 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 384 Kbit/s PS Streaming Services for Cell Average UL Rate of 8 Kbit/s PS Streaming Services for Cell UL Traffic Volume of 8 Kbit/s PS Streaming Services for Cell Average UL Rate of 128 Kbit/s PS Streaming Services for Cell UL Traffic Volume of 128 Kbit/s PS Streaming Services for Cell Average downlink throughput of the Traffic PS Conversational beared on DCH for cell Number of downlink Bit Size of Transport Blocks of Traffic PS Conversational beared on DCH for cell Average uplink throughput of the Traffic PS Conversational beared on DCH for cell
67193554
V900R012
67204252
VS.PS.Str.Kbps.U L8
V900R012
67193556
V900R012
67204253
V900R012
67193558
V900R012
73410482
VS.PS.Conv.Kbps. DL
V900R012
73393908
VS.PS.Conv.DL.Tr affic
V900R012
73410483
VS.PS.Conv.Kbps. UL
V900R012
Issue 01 (2013-05-04)
2433
Counter ID 73393910
Counter Name VS.PS.Conv.UL.Tr affic
Counter Description Number of uplink Bit Size of Transport Blocks of Traffic PS Conversational beared on DCH for cell Sum of Sampled Downlink BE Throughput of UEs with PS Services over DCHs Number of Times Downlink BE Throughput of UEs with PS Services over DCHs Is Sampled Sum of Sampled Uplink BE Throughput of UEs with PS Services over DCHs Number of Times Uplink BE Throughput of UEs with PS Services over DCHs Is Sampled Number of Erlangs for AMR Services for Cell
73426120
VS.PS.BE.DCH.DL .SumThroughput
V900R015
73426121
VS.PS.BE.DCH.DL .SamplesThroughput
V900R015
73426122
VS.PS.BE.DCH.UL .SumThroughput
V900R015
73426123
VS.PS.BE.DCH.UL .SamplesThroughput
V900R015
73426291
VS.RAB.AMR.Erla ng.cell
V900R015
None
1.12.46.1 Average DL Rate of 64 Kbit/s CS Conversational Services
Issue 01 (2013-05-04)
2434
Counters
Counter ID 67202812 Counter Name VS.CS.Conv.Kbps.DL64 Counter Description Average DL Rate of 64 Kbit/ s CS Conversational Services for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67184036 Counter Name VS.CS.Conv.DL.64.Times Counter Description Duration of Measuring Throughput of CS Downlink 64 kbit/s Conversational Service for Cell
Description
This counter provides the average downlink rate of 64 Kbit/s CS conversational services in the cells in the active set
Measurement point
The DL traffic (unit: bit) and the service duration (unit: ms) of the 64 Kbit/s CS conversational services in the cells in the active set are accumulated in the measurement period. At the end of a measurement period, this counter is calculated using the following formula:
Formula
VS.CS.Conv.Kbps.DL64 = [VS.CS.Conv.DL.64.Traffic]/[VS.CS.Conv.DL.64.Times]
Unit
kbit/s
Related Features
Counter Name VS.CS.Conv.Kbps.DL64 Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.12.46.2 DL Traffic Volume of 64 Kbit/s CS Conversational Services

Counters
Counter ID 67183986 Counter Name VS.CS.Conv.DL.64.Traffic Counter Description DL Traffic Volume of 64 Kbit/s CS Conversational Services for Cel
Description
This counter provides the downlink traffic volume of 64 Kbit/s CS conversational services in the cells in the active set.
Measurement point
The DL traffic volume of 64 Kbit/s CS conversational services over the RLC layer is accumulated for the cells that are under the SRNC and are in the active set
Formula
None
Unit
bit
Related Features
Counter Name VS.CS.Conv.DL.64.Traffic Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.12.46.3 Average DL Rate of 57.6 Kbit/s CS Streaming Services Counters

Counter ID 67202816 Counter Name VS.CS.Str.Kbps.DL57.6 Counter Description Average DL Rate of 57.6 Kbit/s CS Streaming Services for Cell
Counter ID 67184040
Counter Name VS.CS.Str.DL.57.6.Times
Counter Description Duration of Measuring Throughput of CS Downlink 57.6 kbit/s Streaming Service for Cell
Description
This counter provides the average downlink rate of 57.6 Kbit/s CS streaming services in the cells in the active set.
Measurement point
The DL traffic (unit: bit) and the service duration (unit: ms) of the 57.6 Kbit/s CS streaming services are accumulated in the measurement period for the cells that are under the SRNC and are in the active set. At the end of a measurement period, this counter is calculated using the following formula:
Formula
VS.CS.Str.Kbps.DL57.6 = [VS.CS.Str.DL.57.6.Traffic]/[VS.CS.Str.DL.57.6.Times]
Unit
kbit/s
Related Features
Counter Name VS.CS.Str.Kbps.DL57.6 Feature ID WRFD-010502 Feature Name Streaming QoS Class
1.12.46.4 DL Traffic Volume of 57.6 Kbit/s CS Streaming Services Counters

Counter ID 67183990 Counter Name VS.CS.Str.DL.57.6.Traffic Counter Description DL Traffic Volume of 57.6 Kbit/s CS Streaming Services for Cell
Description
This counter provides the downlink traffic volume of 57.6 Kbit/s CS streaming services in the cells in the active set.
Measurement point
The DL traffic volume of 57.6 Kbit/s CS streaming services over the RLC layer is accumulated for the cells that are under the SRNC and are in the active set.
Formula
None
Unit
bit
Related Features
Counter Name VS.CS.Str.DL.57.6.Traffic Feature ID WRFD-010502 Feature Name Streaming QoS Class
1.12.46.5 Counters Related to the Average DL Rates of Different PS R99 Background Services Counters
Counter ID 67202819 Counter Name VS.PS.Bkg.Kbps.DL8 Counter Description Average DL Rate of 8 Kbit/s PS Background Services for Cell Average DL Rate of 16 Kbit/ s PS Background Services for Cell Average DL Rate of 32 Kbit/ s PS Background Services for Cell Average DL Rate of 64 Kbit/ s PS Background Services for Cell Average DL Rate of 128 Kbit/s PS Background Services for Cell Average DL Rate of 144 Kbit/s PS Background Services for Cell
67202820
VS.PS.Bkg.Kbps.DL16
67202821
VS.PS.Bkg.Kbps.DL32
67202822
VS.PS.Bkg.Kbps.DL64
67202823
VS.PS.Bkg.Kbps.DL128
67202824
Issue 01 (2013-05-04)
2438
Counter ID 67202825
Counter Name VS.PS.Bkg.Kbps.DL256
Counter Description Average DL Rate of 256 Kbit/s PS Background Services for Cell Average DL Rate of 384 Kbit/s PS Background Services for Cell
67202826
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67184047 Counter Name VS.PS.Bkg.DL.128.Times Counter Description Duration of Measuring Throughput of PS Downlink 128 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Downlink 144 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Downlink 16 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Downlink 256 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Downlink 32 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Downlink 384 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Downlink 64 kbit/s Background Service for Cell
67184048
VS.PS.Bkg.DL.144.Times
67184044
67184049
67184045
67184050
67184046
Issue 01 (2013-05-04)
2439
Counter ID 67184043
Counter Name VS.PS.Bkg.DL.8.Times
Counter Description Duration of Measuring Throughput of PS Downlink 8 kbit/s Background Service for Cell
Description
These counters provide the average downlink rates of different PS R99 background services in the cells in the active set.
Measurement point
The DL traffic (not including the RLC header and the retransmitted data, unit: bit) and the actual duration (unit: ms) with data transmission of each kind of PS R99 background services are accumulated in the measurement period for the cells that are under the SRNC and are in the active set. At the end of a measurement period, this counter is calculated using the following formula:
Formula
VS.PS.Bkg.Kbps.DL8 = [VS.PS.Bkg.DL.8.Traffic]/[VS.PS.Bkg.DL.8.Times] VS.PS.Bkg.Kbps.DL16 = [VS.PS.Bkg.DL.16.Traffic]/[VS.PS.Bkg.DL.16.Times] VS.PS.Bkg.Kbps.DL32 = [VS.PS.Bkg.DL.32.Traffic]/[VS.PS.Bkg.DL.32.Times] VS.PS.Bkg.Kbps.DL64 = [VS.PS.Bkg.DL.64.Traffic]/[VS.PS.Bkg.DL.64.Times] VS.PS.Bkg.Kbps.DL128 = [VS.PS.Bkg.DL.128.Traffic]/[VS.PS.Bkg.DL.128.Times] VS.PS.Bkg.Kbps.DL144 = [VS.PS.Bkg.DL.144.Traffic]/[VS.PS.Bkg.DL.144.Times] VS.PS.Bkg.Kbps.DL256 = [VS.PS.Bkg.DL.256.Traffic]/[VS.PS.Bkg.DL.256.Times] VS.PS.Bkg.Kbps.DL384 = [VS.PS.Bkg.DL.384.Traffic]/[VS.PS.Bkg.DL.384.Times]
Unit
kbit/s
Related Features
Counter Name VS.PS.Bkg.Kbps.DL8 VS.PS.Bkg.Kbps.DL16 VS.PS.Bkg.Kbps.DL32 VS.PS.Bkg.Kbps.DL64
Issue 01 (2013-05-04)
Feature Name Background QoS Class Background QoS Class Background QoS Class Background QoS Class
2440
Counter Name VS.PS.Bkg.Kbps.DL128 VS.PS.Bkg.Kbps.DL144 VS.PS.Bkg.Kbps.DL256 VS.PS.Bkg.Kbps.DL384
Feature Name Background QoS Class Background QoS Class Background QoS Class Background QoS Class
1.12.46.6 Counters Related to the DL Traffic Volumes of Different PS R99 Background Services Counters
Counter ID 67183993 Counter Name VS.PS.Bkg.DL.8.Traffic Counter Description DL Traffic Volume of 8 Kbit/ s PS Background Services for Cell DL Traffic Volume of 16 Kbit/s PS Background Services for Cell DL Traffic Volume of 32 Kbit/s PS Background Services for Cell DL Traffic Volume of 64 Kbit/s PS Background Services for Cell DL Traffic Volume of 128 Kbit/s PS Background Services for Cell DL Traffic Volume of 144 Kbit/s PS Background Services for Cell DL Traffic Volume of 256 Kbit/s PS Background Services for Cell DL Traffic Volume of 384 Kbit/s PS Background Services for Cell
67183994
VS.PS.Bkg.DL.16.Traffic
67183995
67183996
67183997
67183998
67183999
67184000
Issue 01 (2013-05-04)
2441
Description
These counters provide the downlink traffic volumes of different PS R99 background services in the cells in the active set.
Measurement point
The DL traffic volumes (not including the RLC header and the retransmitted data) of each kind of PS R99 background services over the RLC layer are accumulated for the cells that are under the SRNC and are in the active set.
Formula
None
Unit
bit
Related Features
Counter Name VS.PS.Bkg.DL.8.Traffic VS.PS.Bkg.DL.16.Traffic VS.PS.Bkg.DL.32.Traffic VS.PS.Bkg.DL.64.Traffic VS.PS.Bkg.DL.128.Traffic VS.PS.Bkg.DL.144.Traffic VS.PS.Bkg.DL.256.Traffic VS.PS.Bkg.DL.384.Traffic Feature ID WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 Feature Name Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class
1.12.46.7 Counters Related to the Average DL Rates of Different PS R99 Interactive Services Counters
Counter ID 67202827 Counter Name VS.PS.Int.Kbps.DL8 Counter Description Average DL Rate of 8 Kbit/s PS Interactive Services for Cell
Issue 01 (2013-05-04)
2442
Counter ID 67202828
Counter Name VS.PS.Int.Kbps.DL16
Counter Description Average DL Rate of 16 Kbit/ s PS Interactive Services for Cell Average DL Rate of 32 Kbit/ s PS Interactive Services for Cell Average DL Rate of 64 Kbit/ s PS Interactive Services for Cell Average DL Rate of 128 Kbit/s PS Interactive Services for Cell Average DL Rate of 144 Kbit/s PS Interactive Services for Cell Average DL Rate of 256 Kbit/s PS Interactive Services for Cell Average DL Rate of 384 Kbit/s PS Interactive Services for Cell
67202829
VS.PS.Int.Kbps.DL32
67202830
VS.PS.Int.Kbps.DL64
67202831
VS.PS.Int.Kbps.DL128
67202832
67202833
67202834
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67184055 Counter Name VS.PS.Int.DL.128.Times Counter Description Duration of Measuring Throughput of PS Downlink 128 kbit/s Interactive Service for Cell Duration of Measuring Throughput of PS Downlink 144 kbit/s Interactive Service for Cell Duration of Measuring PS Downlink 16 kbit/s Interactive Service for Cell Duration of Measuring Throughput of PS Downlink 256 kbit/s Interactive Service for Cell
67184056
VS.PS.Int.DL.144.Times
67184052
67184057
Issue 01 (2013-05-04)
2443
Counter ID 67184053
Counter Name VS.PS.Int.DL.32.Times
Counter Description Duration of Measuring Throughput of PS Downlink 32 kbit/s Interactive Service for Cell Duration of Measuring Throughput of PS Downlink 384 kbit/s Interactive Service for Cell Duration of Measuring Throughput of PS Downlink 64 kbit/s Interactive Service for Cell Duration of Measuring Throughput of PS Downlink 8 kbit/s Interactive Service for Cell
67184058
67184054
67184051
Description
These counters provide the average downlink rates of different PS R99 interactive services in the cells in the active set.
Measurement point
The DL traffic (not including the RLC header and the retransmitted data, unit: bit) and the actual duration (unit: ms) with data transmission of each kind of PS R99 interactive services are accumulated in the measurement period for the cells that are under the SRNC and are in the active set. At the end of a measurement period, this counter is calculated using the following formula:
Formula
VS.PS.Int.Kbps.DL8 = [VS.PS.Int.DL.8.Traffic]/[VS.PS.Int.DL.8.Times] VS.PS.Int.Kbps.DL16 = [VS.PS.Int.DL.16.Traffic]/[VS.PS.Int.DL.16.Times] VS.PS.Int.Kbps.DL32 = [VS.PS.Int.DL.32.Traffic]/[VS.PS.Int.DL.32.Times] VS.PS.Int.Kbps.DL64 = [VS.PS.Int.DL.64.Traffic]/[VS.PS.Int.DL.64.Times] VS.PS.Int.Kbps.DL128 = [VS.PS.Int.DL.128.Traffic]/[VS.PS.Int.DL.128.Times] VS.PS.Int.Kbps.DL144 = [VS.PS.Int.DL.144.Traffic]/[VS.PS.Int.DL.144.Times] VS.PS.Int.Kbps.DL256 = [VS.PS.Int.DL.256.Traffic]/[VS.PS.Int.DL.256.Times] VS.PS.Int.Kbps.DL384 = [VS.PS.Int.DL.384.Traffic]/[VS.PS.Int.DL.384.Times]
Unit
kbit/s
Related Features
Counter Name VS.PS.Int.Kbps.DL8 VS.PS.Int.Kbps.DL16 VS.PS.Int.Kbps.DL32 VS.PS.Int.Kbps.DL64 VS.PS.Int.Kbps.DL128 VS.PS.Int.Kbps.DL144 VS.PS.Int.Kbps.DL256 VS.PS.Int.Kbps.DL384 Feature ID WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 Feature Name Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class
1.12.46.8 Counters Related to the DL Traffic Volumes of Different PS R99 Interactive Services Counters
Counter ID 67184001 Counter Name VS.PS.Int.DL.8.Traffic Counter Description DL Traffic Volume of 8 Kbit/ s PS Interactive Services for Cell DL Traffic Volume of 16 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 32 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 64 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 128 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 144 Kbit/s PS Interactive Services for Cell
2445
67184002
VS.PS.Int.DL.16.Traffic
67184003
67184004
67184005
67184006
Issue 01 (2013-05-04)
Counter ID 67184007
Counter Name VS.PS.Int.DL.256.Traffic
Counter Description DL Traffic Volume of 256 Kbit/s PS Interactive Services for Cell DL Traffic Volume of 384 Kbit/s PS Interactive Services for Cell
67184008
Description
These counters provide the downlink traffic volumes of different PS R99 interactive services in the cells in the active set.
Measurement point
The DL traffic volumes (not including the RLC header and the retransmitted data) of each kind of PS R99 interactive services over the RLC layer are accumulated for the cells that are under the SRNC and are in the active set.
Formula
None
Unit
bit
Related Features
Counter Name VS.PS.Int.DL.8.Traffic VS.PS.Int.DL.16.Traffic VS.PS.Int.DL.32.Traffic VS.PS.Int.DL.64.Traffic VS.PS.Int.DL.128.Traffic VS.PS.Int.DL.144.Traffic VS.PS.Int.DL.256.Traffic VS.PS.Int.DL.384.Traffic Feature ID WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 Feature Name Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class
Issue 01 (2013-05-04)
2446
1.12.46.9 Counters Related to the Average DL Rates of Different PS R99 Streaming Services Counters
Counter ID 67202835 Counter Name VS.PS.Str.Kbps.DL32 Counter Description Average DL Rate of 32 Kbit/ s PS Streaming Services for Cell Average DL Rate of 64 Kbit/ s PS Streaming Services for Cell Average DL Rate of 128 Kbit/s PS Streaming Services for Cell Average DL Rate of 144 Kbit/s PS Streaming Services for Cell Average DL Rate of 8 Kbit/s PS Streaming Services for Cell Average DL Rate of 16 Kbit/ s PS Streaming Services for Cell Average DL Rate of 256 Kbit/s PS Streaming Services for Cell Average DL Rate of 384 Kbit/s PS Streaming Services for Cell
67202836
VS.PS.Str.Kbps.DL64
67202837
VS.PS.Str.Kbps.DL128
67202838
67204248
VS.PS.Str.Kbps.DL8
67204249
VS.PS.Str.Kbps.DL16
67204250
67204251
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67184061 Counter Name VS.PS.Str.DL.128.Times Counter Description Duration of Measuring Throughput of PS Downlink 128 kbit/s Streaming Service for Cell
Issue 01 (2013-05-04)
2447
Counter ID 67184062
Counter Name VS.PS.Str.DL.144.Times
Counter Description Duration of Measuring Throughput of PS Downlink 144 kbit/s Streaming Service for Cell Duration of Stat Throughput of Traffic PS_STR_DL_16 for cell Duration of Stat Throughput of Traffic PS_STR_DL_256 for cell Duration of Measuring Throughput of PS Downlink 32 kbit/s Streaming Service for Cell Duration of Stat Throughput of Traffic PS_STR_DL_384 for cell Duration of Measuring Throughput of PS Downlink 64 kbit/s Streaming for Cell Duration of Stat Throughput of Traffic PS_STR_DL_8 for cell
67193551
VS.PS.Str.DL.16.Times
67193553
67184059
67193555
67184060
67193549
Description
These counters provide the average downlink rates of different PS R99 streaming services in the cells in the active set.
Measurement point
The DL traffic (not including the RLC header and the retransmitted data, unit: bit) and the actual duration (unit: ms) with data transmission of each kind of PS R99 streaming services are accumulated in the measurement period for the cells that are under the SRNC and are in the active set. At the end of a measurement period, this counter is calculated using the following formula:
Formula
VS.PS.Str.Kbps.DL32 = [VS.PS.Str.DL.32.Traffic]/[VS.PS.Str.DL.32.Times] VS.PS.Str.Kbps.DL64 = [VS.PS.Str.DL.64.Traffic]/[VS.PS.Str.DL.64.Times] VS.PS.Str.Kbps.DL128 = [VS.PS.Str.DL.128.Traffic]/[VS.PS.Str.DL.128.Times] VS.PS.Str.Kbps.DL144 = [VS.PS.Str.DL.144.Traffic]/[VS.PS.Str.DL.144.Times]
VS.PS.Str.Kbps.DL8 = [VS.PS.Str.DL.8.Traffic]/[VS.PS.Str.DL.8.Times] VS.PS.Str.Kbps.DL16 = [VS.PS.Str.DL.16.Traffic]/[VS.PS.Str.DL.16.Times] VS.PS.Str.Kbps.DL256 = [VS.PS.Str.DL.256.Traffic]/[VS.PS.Str.DL.256.Times] VS.PS.Str.Kbps.DL384 = [VS.PS.Str.DL.384.Traffic]/[VS.PS.Str.DL.384.Times]
Unit
kbit/s
Related Features
Counter Name VS.PS.Str.Kbps.DL32 VS.PS.Str.Kbps.DL64 VS.PS.Str.Kbps.DL128 VS.PS.Str.Kbps.DL144 VS.PS.Str.Kbps.DL8 VS.PS.Str.Kbps.DL16 VS.PS.Str.Kbps.DL256 VS.PS.Str.Kbps.DL384 Feature ID WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 Feature Name Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class
1.12.46.10 Counters Related to the DL Traffic Volumes of Different PS R99 Streaming Services Counters
Counter ID 67184009 Counter Name VS.PS.Str.DL.32.Traffic Counter Description DL Traffic Volume of 32 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 64 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 128 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 144 Kbit/s PS Streaming Services for Cell
2449
67184010
VS.PS.Str.DL.64.Traffic
67184011
67184012
Issue 01 (2013-05-04)
Counter ID 67193548
Counter Name VS.PS.Str.DL.8.Traffic
Counter Description DL Traffic Volume of 8 Kbit/ s PS Streaming Services for Cell DL Traffic Volume of 16 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 256 Kbit/s PS Streaming Services for Cell DL Traffic Volume of 384 Kbit/s PS Streaming Services for Cell
67193550
67193552
67193554
Description
These counters provide the downlink traffic volumes of different PS R99 streaming services in the cells in the active set.
Measurement point
The DL traffic volumes (not including the RLC header and the retransmitted data) of each kind of PS R99 streaming services over the RLC layer are accumulated for the cells that are under the SRNC and are in the active set.
Formula
None
Unit
bit
Related Features
Counter Name VS.PS.Str.DL.32.Traffic VS.PS.Str.DL.64.Traffic VS.PS.Str.DL.128.Traffic VS.PS.Str.DL.144.Traffic VS.PS.Str.DL.8.Traffic VS.PS.Str.DL.16.Traffic
Issue 01 (2013-05-04)
Feature Name Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class
2450
Counter Name VS.PS.Str.DL.256.Traffic VS.PS.Str.DL.384.Traffic
Feature Name Streaming QoS Class Streaming QoS Class
1.12.46.11 Counters Related to the Average UL Rates of Different PS R99 Background Services Counters
Counter ID 67202840 Counter Name VS.PS.Bkg.Kbps.UL8 Counter Description Average UL Rate of 8 Kbit/s PS R99 Background Services for Cell Average UL Rate of 16 Kbit/ s PS R99 Background Services for Cell Average UL Rate of 32 Kbit/ s PS R99 Background Services for Cell Average UL Rate of 64 Kbit/ s PS R99 Background Services for Cell Average UL Rate of 128 Kbit/s PS R99 Background Services for Cell Average UL Rate of 144 Kbit/s PS R99 Background Services for Cell Average UL Rate of 256 Kbit/s PS R99 Background Services for Cell Average UL Rate of 384 Kbit/s PS R99 Background Services for Cell
67202841
VS.PS.Bkg.Kbps.UL16
67202842
VS.PS.Bkg.Kbps.UL32
67202843
VS.PS.Bkg.Kbps.UL64
67202844
VS.PS.Bkg.Kbps.UL128
67202845
67202846
67202847
Issue 01 (2013-05-04)
2451
Counter ID 67184068
Counter Name VS.PS.Bkg.UL.128.Times
Counter Description Duration of Measuring Throughput of PS Uplink 128 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Uplink 144 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Uplink 16 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Uplink 256 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Uplink 32 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Uplink 384 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Uplink 64 kbit/s Background Service for Cell Duration of Measuring Throughput of PS Uplink 8 kbit/s Background Service for Cell
67184069
VS.PS.Bkg.UL.144.Times
67184065
67184070
67184066
67184071
67184067
67184064
Description
These counters provide the average uplink rates of different PS R99 background services in the cells in the active set.
Measurement point
The UL traffic (not including the RLC header and the retransmitted data, unit: bit) and the actual duration (unit: ms) with data transmission of each kind of PS R99 background services are accumulated in the measurement period for the cells that are under the SRNC and are in the active set. At the end of a measurement period, this counter is calculated using the following formula:
Formula
VS.PS.Bkg.Kbps.UL8 = [VS.PS.Bkg.UL.8.Traffic]/[VS.PS.Bkg.UL.8.Times] VS.PS.Bkg.Kbps.UL16 = [VS.PS.Bkg.UL.16.Traffic]/[VS.PS.Bkg.UL.16.Times] VS.PS.Bkg.Kbps.UL32 = [VS.PS.Bkg.UL.32.Traffic]/[VS.PS.Bkg.UL.32.Times] VS.PS.Bkg.Kbps.UL64 = [VS.PS.Bkg.UL.64.Traffic]/[VS.PS.Bkg.UL.64.Times] VS.PS.Bkg.Kbps.UL128 = [VS.PS.Bkg.UL.128.Traffic]/[VS.PS.Bkg.UL.128.Times] VS.PS.Bkg.Kbps.UL144 = [VS.PS.Bkg.UL.144.Traffic]/[VS.PS.Bkg.UL.144.Times] VS.PS.Bkg.Kbps.UL256 = [VS.PS.Bkg.UL.256.Traffic]/[VS.PS.Bkg.UL.256.Times] VS.PS.Bkg.Kbps.UL384 = [VS.PS.Bkg.UL.384.Traffic]/[VS.PS.Bkg.UL.384.Times]
Unit
kbit/s
Related Features
Counter Name VS.PS.Bkg.Kbps.UL8 VS.PS.Bkg.Kbps.UL16 VS.PS.Bkg.Kbps.UL32 VS.PS.Bkg.Kbps.UL64 VS.PS.Bkg.Kbps.UL128 VS.PS.Bkg.Kbps.UL144 VS.PS.Bkg.Kbps.UL256 VS.PS.Bkg.Kbps.UL384 Feature ID WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 Feature Name Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class
1.12.46.12 Counters Related to the UL Traffic Volumes of Different PS R99 Background Services Counters
Counter ID 67184014 Counter Name VS.PS.Bkg.UL.8.Traffic Counter Description UL Traffic Volume of 8 Kbit/ s PS R99 Background Services for Cell
Issue 01 (2013-05-04)
2453
Counter ID 67184015
Counter Name VS.PS.Bkg.UL.16.Traffic
Counter Description UL Traffic Volume of 16 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 32 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 64 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 128 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 144 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 256 Kbit/s PS R99 Background Services for Cell UL Traffic Volume of 384 Kbit/s PS R99 Background Services for Cell
67184016
VS.PS.Bkg.UL.32.Traffic
67184017
67184018
67184019
67184020
67184021
Description
These counters provide the uplink traffic volumes of different PS R99 background services in the cells in the active set.
Measurement point
The UL traffic volumes (not including the RLC header and the retransmitted data) of each kind of PS R99 background services over the RLC layer are accumulated for the cells that are under the SRNC and are in the active set.
Formula
None
Unit
bit
Issue 01 (2013-05-04)
2454
Related Features
Counter Name VS.PS.Bkg.UL.8.Traffic VS.PS.Bkg.UL.16.Traffic VS.PS.Bkg.UL.32.Traffic VS.PS.Bkg.UL.64.Traffic VS.PS.Bkg.UL.128.Traffic VS.PS.Bkg.UL.144.Traffic VS.PS.Bkg.UL.256.Traffic VS.PS.Bkg.UL.384.Traffic Feature ID WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 WRFD-010504 Feature Name Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class Background QoS Class
1.12.46.13 Counters Related to the Average UL Rates of Different PS R99 Interactive Services Counters
Counter ID 67202848 Counter Name VS.PS.Int.Kbps.UL8 Counter Description Average UL Rate of 8 Kbit/s PS R99 Interactive Services for Cell Average UL Rate of 16 Kbit/ s PS R99 Interactive Services for Cell Average UL Rate of 32 Kbit/ s PS R99 Interactive Services for Cell Average UL Rate of 64 Kbit/ s PS R99 Interactive Services for Cell Average UL Rate of 128 Kbit/s PS R99 Interactive Services for Cell Average UL Rate of 144 Kbit/s PS R99 Interactive Services for Cell Average UL Rate of 256 Kbit/s PS R99 Interactive Services for Cell
2455
67202849
VS.PS.Int.Kbps.UL16
67202850
VS.PS.Int.Kbps.UL32
67202851
VS.PS.Int.Kbps.UL64
67202852
VS.PS.Int.Kbps.UL128
67202853
67202854
Issue 01 (2013-05-04)
Counter ID 67202855
Counter Name VS.PS.Int.Kbps.UL384
Counter Description Average UL Rate of 384 Kbit/s PS R99 Interactive Services for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67184076 Counter Name VS.PS.Int.UL.128.Times Counter Description Duration of Measuring Throughput of PS Uplink 128 kbit/s Interactive Service for Cell Duration of Measuring Throughput of PS Uplink 144 kbit/s Interactive Service for Cell Duration of Measuring Throughput of PS Uplink 16 kbit/s Interactive Service for Cell Duration of Measuring Throughput of PS Uplink 256 kbit/s Interactive Service for Cell Duration of Measuring Throughput of PS Uplink 32 kbit/s Interactive Service for Cell Duration of Measuring Throughput of PS Uplink 384 kbit/s Interactive Service for Cell Duration of Measuring Throughput of PS Uplink 64 kbit/s Interactive Service for Cell Duration of Measuring Throughput of PS Uplink 8 kbit/s Interactive Service for Cell
67184077
VS.PS.Int.UL.144.Times
67184073
67184078
67184074
67184079
67184075
67184072
Issue 01 (2013-05-04)
2456
Description
These counters provide the average uplink rates of different PS R99 interactive services in the cells in the active set.
Measurement point
The UL traffic (not including the RLC header and the retransmitted data, unit: bit) and the actual duration (unit: ms) with data transmission of each kind of PS R99 interactive services are accumulated in the measurement period for the cells that are under the SRNC and are in the active set. At the end of a measurement period, this counter is calculated using the following formula:
Formula
VS.PS.Int.Kbps.UL8 = [VS.PS.Int.UL.8.Traffic]/[VS.PS.Int.UL.8.Times] VS.PS.Int.Kbps.UL16 = [VS.PS.Int.UL.16.Traffic]/[VS.PS.Int.UL.16.Times] VS.PS.Int.Kbps.UL32 = [VS.PS.Int.UL.32.Traffic]/[VS.PS.Int.UL.32.Times] VS.PS.Int.Kbps.UL64 = [VS.PS.Int.UL.64.Traffic]/[VS.PS.Int.UL.64.Times] VS.PS.Int.Kbps.UL128 = [VS.PS.Int.UL.128.Traffic]/[VS.PS.Int.UL.128.Times] VS.PS.Int.Kbps.UL144 = [VS.PS.Int.UL.144.Traffic]/[VS.PS.Int.UL.144.Times] VS.PS.Int.Kbps.UL256 = [VS.PS.Int.UL.256.Traffic]/[VS.PS.Int.UL.256.Times] VS.PS.Int.Kbps.UL384 = [VS.PS.Int.UL.384.Traffic]/[VS.PS.Int.UL.384.Times]
Unit
kbit/s
Related Features
Counter Name VS.PS.Int.Kbps.UL8 VS.PS.Int.Kbps.UL16 VS.PS.Int.Kbps.UL32 VS.PS.Int.Kbps.UL64 VS.PS.Int.Kbps.UL128 VS.PS.Int.Kbps.UL144 VS.PS.Int.Kbps.UL256 VS.PS.Int.Kbps.UL384 Feature ID WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 Feature Name Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class
Issue 01 (2013-05-04)
2457
1.12.46.14 Counters Related to the UL Traffic Volumes of Different PS R99 Interactive Services Counters
Counter ID 67184022 Counter Name VS.PS.Int.UL.8.Traffic Counter Description UL Traffic Volume of 8 Kbit/ s PS R99 Interactive Services for Cell UL Traffic Volume of 16 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 32 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 64 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 128 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 144 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 256 Kbit/s PS R99 Interactive Services for Cell UL Traffic Volume of 384 Kbit/s PS R99 Interactive Services for Cell
67184023
VS.PS.Int.UL.16.Traffic
67184024
67184025
67184026
67184027
67184028
67184029
Description
These counters provide the uplink traffic volumes of different PS R99 interactive services in the cells in the active set.
Measurement point
The UL traffic volumes (not including the RLC header and the retransmitted data) of each kind of PS R99 interactive services over the RLC layer are accumulated for the cells that are under the SRNC and are in the active set.
Formula
None
Unit
bit
Related Features
Counter Name VS.PS.Int.UL.8.Traffic VS.PS.Int.UL.16.Traffic VS.PS.Int.UL.32.Traffic VS.PS.Int.UL.64.Traffic VS.PS.Int.UL.128.Traffic VS.PS.Int.UL.144.Traffic VS.PS.Int.UL.256.Traffic VS.PS.Int.UL.384.Traffic Feature ID WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 WRFD-010503 Feature Name Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class Interactive QoS Class
1.12.46.15 Counters Related to the Average UL Rates of Different PS R99 Streaming Services Counters
Counter ID 67202856 Counter Name VS.PS.Str.Kbps.UL16 Counter Description Average UL Rate of 16 Kbit/ s PS Streaming Services for Cell Average UL Rate of 32 Kbit/ s PS Streaming Services for Cell Average UL Rate of 64 Kbit/ s PS Streaming Services for Cell Average UL Rate of 8 Kbit/s PS Streaming Services for Cell Average UL Rate of 128 Kbit/s PS Streaming Services for Cell
67202857
VS.PS.Str.Kbps.UL32
67202858
VS.PS.Str.Kbps.UL64
67204252
VS.PS.Str.Kbps.UL8
67204253
VS.PS.Str.Kbps.UL128
Issue 01 (2013-05-04)
2459
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67193559 Counter Name VS.PS.Str.UL.128.Times Counter Description Duration of Stat Throughput of Traffic PS_STR_UL_128 for cell Duration of Measuring Throughput of PS Uplink 16 kbit/s Streaming Service for Cell Duration of Measuring Throughput of PS Uplink 32 kbit/s Streaming Service for Cell Duration of Measuring Throughput of PS Uplink 64 kbit/s Streaming Service for Cell Duration of Stat Throughput of Traffic PS_STR_UL_8 for cell
67184080
VS.PS.Str.UL.16.Times
67184081
67184082
67193557
Description
These counters provide the average uplink rates of different PS R99 streaming services in the cells in the active set.
Measurement point
The UL traffic (not including the RLC header and the retransmitted data, unit: bit) and the actual duration (unit: ms) with data transmission of each kind of PS R99 streaming services are accumulated in the measurement period for the cells that are under the SRNC and are in the active set. At the end of a measurement period, this counter is calculated using the following formula:
Formula
VS.PS.Str.Kbps.UL16 = [VS.PS.Str.UL.16.Traffic]/[VS.PS.Str.UL.16.Times] VS.PS.Str.Kbps.UL32 = [VS.PS.Str.UL.32.Traffic]/[VS.PS.Str.UL.32.Times] VS.PS.Str.Kbps.UL64 = [VS.PS.Str.UL.64.Traffic]/[VS.PS.Str.UL.64.Times] VS.PS.Str.Kbps.UL8 = [VS.PS.Str.UL.8.Traffic]/[VS.PS.Str.UL.8.Times] VS.PS.Str.Kbps.UL128 = [VS.PS.Str.UL.128.Traffic]/[VS.PS.Str.UL.128.Times]
Unit
kbit/s
Related Features
Counter Name VS.PS.Str.Kbps.UL16 VS.PS.Str.Kbps.UL32 VS.PS.Str.Kbps.UL64 VS.PS.Str.Kbps.UL8 VS.PS.Str.Kbps.UL128 Feature ID WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 Feature Name Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class
1.12.46.16 Counters Related to the UL Traffic Volumes of Different PS R99 Streaming Services Counters
Counter ID 67184030 Counter Name VS.PS.Str.UL.16.Traffic Counter Description UL Traffic Volume of 16 Kbit/s PS Streaming Services for Cell UL Traffic Volume of 32 Kbit/s PS Streaming Services for Cell UL Traffic Volume of 64 Kbit/s PS Streaming Services for Cell UL Traffic Volume of 8 Kbit/ s PS Streaming Services for Cell UL Traffic Volume of 128 Kbit/s PS Streaming Services for Cell
67184031
VS.PS.Str.UL.32.Traffic
67184032
67193556
67193558
Description
These counters provide the uplink traffic volumes of different PS R99 streaming services in the cells in the active set.
Issue 01 (2013-05-04)
2461
Measurement point
The UL traffic volumes (not including the RLC header and the retransmitted data) of each kind of PS R99 streaming services over the RLC layer are accumulated for the cells that are under the SRNC and are in the active set.
Formula
None
Unit
bit
Related Features
Counter Name VS.PS.Str.UL.16.Traffic VS.PS.Str.UL.32.Traffic VS.PS.Str.UL.64.Traffic VS.PS.Str.UL.8.Traffic VS.PS.Str.UL.128.Traffic Feature ID WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 WRFD-010502 Feature Name Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class Streaming QoS Class
1.12.46.17 Average UL Rate of Signaling on DCCH Counters

Counter ID 67202859 Counter Name VS.DcchSrbKbps.Ul Counter Description Average UL Rate of Signaling on DCCH for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67189904 Counter Name VS.DcchSrbKbps.Ul.Times Counter Description Duration of Measuring UL Signaling on DCCH for Cell
Description
This counter provides the average uplink rate of signaling on the DCCH in the cells in the active set.
Measurement point
The UL traffic (not including the RLC header and the retransmitted data, unit: bit) and the transmit duration (unit: ms) of the signaling over the DCCH are accumulated in the measurement period for the cells that are under the SRNC and are in the active set. At the end of the measurement period, the value of this counter is calculated.
Formula
VS.DcchSrbKbps.Ul = [VS.DcchSRB.Ul.Traffic]/[VS.DcchSrbKbps.Ul.Times]
Unit
kbit/s
Related Features
Counter Name VS.DcchSrbKbps.Ul Feature ID WRFD-020900 Feature Name Logical Channel Management
1.12.46.18 UL Traffic Volume of Signaling on DCCH Counters

Counter ID 67189903 Counter Name VS.DcchSRB.Ul.Traffic Counter Description UL Traffic Volume of Signaling on DCCH for Cell
Description
This counter provides the uplink traffic volume of signaling on the DCCH in the cells in the active set.
Measurement point
The UL traffic volume (not including the RLC header and the retransmitted data) of signaling on the DCCH is accumulated for the cells that are under the SRNC and are in the active set.
Formula
None
Unit
bit
Related Features
Counter Name VS.DcchSRB.Ul.Traffic Feature ID WRFD-020900 Feature Name Logical Channel Management
1.12.46.19 Average DL Rate of Signaling on DCCH Counters

Counter ID 67202860 Counter Name VS.DcchSrbKbps.Dl Counter Description Average DL Rate of Signaling on DCCH for Cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67189906 Counter Name VS.DcchSrbKbps.Dl.Times Counter Description Duration of Measuring DL Signaling on DCCH for Cell
Description
This counter provides the average downlink rate of signaling on the DCCH in the cells in the active set.
Measurement point
The DL traffic (not including the RLC header and the retransmitted data, unit: bit) and the transmit duration (unit: ms) of the signaling over the DCCH are accumulated in the measurement period for the cells that are under the SRNC and are in the active set. At the end of the measurement period, the value of this counter is calculated.
Formula
VS.DcchSrbKbps.Dl = [VS.DcchSRB.Dl.Traffic]/[VS.DcchSrbKbps.Dl.Times]
Unit
kbit/s
Issue 01 (2013-05-04)
2464
Related Features
Counter Name VS.DcchSrbKbps.Dl Feature ID WRFD-020900 Feature Name Logical Channel Management
1.12.46.20 DL Traffic Volume of Signaling on DCCH Counters

Counter ID 67189905 Counter Name VS.DcchSRB.Dl.Traffic Counter Description DL Traffic Volume of Signaling on DCCH for Cell
Description
This counter provides the downlink traffic volume of signaling on the DCCH in the cells in the active set.
Measurement point
The DL traffic volume (not including the RLC header and the retransmitted data) of signaling on the DCCH is accumulated in the measurement period for the cells that are under the SRNC and are in the active set.
Formula
None
Unit
bit
Related Features
Counter Name VS.DcchSRB.Dl.Traffic Feature ID WRFD-020900 Feature Name Logical Channel Management
1.12.46.21 UL Traffic Volume of AMR Services for Best Cell
Issue 01 (2013-05-04)
2465
Counters
Counter ID 67203449 Counter Name VS.AMR.UL.Traffic.BestCell Counter Description UL Traffic Volume of AMR Services for Best Cell
Description
This counter provides the uplink traffic volume of AMR services(narrowband AMR services) in the best cell.
Measurement point
The UL traffic volume of AMR services is accumulated in the measurement period for the best cell under the SRNC.
Formula
None
Unit
kbit
Related Features
Counter Name VS.AMR.UL.Traffic.BestCell Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.12.46.22 DL Traffic Volume of AMR Services for Best Cell Counters

Counter ID 67203450 Counter Name VS.AMR.DL.Traffic.BestCell Counter Description DL Traffic Volume of AMR Services for Best Cell
Description
This counter provides the downlink traffic volume of AMR services(narrowband AMR services) in the best cell.
Measurement point
The DL traffic volume of AMR services is accumulated in the measurement period for the best cell under the SRNC.
Formula
None
Unit
kbit
Related Features
Counter Name VS.AMR.DL.Traffic.BestCell Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.12.46.23 UL Traffic Volume of VP Services for Best Cell Counters

Counter ID 67203451 Counter Name VS.VP.UL.Traffic.BestCell Counter Description UL Traffic Volume of VP Services for Best Cell
Description
This counter provides the uplink traffic volume of VP services in the best cell.
Measurement point
The UL traffic volume of VP services is accumulated in the measurement period for the best cell under the SRNC.
Formula
None
Unit
kbit
Related Features
Counter Name VS.VP.UL.Traffic.BestCell Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.12.46.24 DL Traffic Volume of VP Services for Best Cell Counters

Counter ID 67203452 Counter Name VS.VP.DL.Traffic.BestCell Counter Description DL Traffic Volume of VP Services for Best Cell
Description
This counter provides the downlink traffic volume of VP services in the best cell.
Measurement point
The DL traffic volume of VP services is accumulated in the measurement period for the best cell under the SRNC.
Formula
None
Unit
kbit
Related Features
Counter Name VS.VP.DL.Traffic.BestCell Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.12.46.25 UL Traffic of BE Services with Different PS Data Rates for Best Cell
Issue 01 (2013-05-04)
2468
Counters
Counter ID 67203453 Counter Name VS.PS.BE.kbits.UL. 0.32.BestCell Counter Description UL Traffic Volume of PS BE Services (0 Kbit/s < UL Bit Rate <= 32 Kbit/s) for Best Cell UL Traffic Volume of PS BE Services (32 Kbit/s < DL Bit Rate <= 64 Kbit/s) for Best Cell UL Traffic Volume of PS BE Services (64 Kbit/s < DL Bit Rate <= 144 Kbit/s) for Best Cell UL Traffic Volume of PS BE Services (144 Kbit/s < DL Bit Rate <= 384 Kbit/s) for Best Cell
67203455
VS.PS.BE.kbits.UL. 32.64.BestCell
67203457
67203459
Description
These counters provides the uplink traffic of BE services with different PS data rates in the best cell.
Measurement point
The uplink traffic of BE services with different PS data rates over the DCH and RACH is accumulated in the measurement period for the best cell under the SRNC.
Formula
None
Unit
kbit
Related Features
Counter Name VS.PS.BE.kbits.UL. 0.32.BestCell VS.PS.BE.kbits.UL. 32.64.BestCell Feature ID WRFD-010503 WRFD-010504 WRFD-010503 WRFD-010504 Feature Name Interactive QoS Class Background QoS Class Interactive QoS Class Background QoS Class
2469
Issue 01 (2013-05-04)
Counter Name VS.PS.BE.kbits.UL. 64.144.BestCell VS.PS.BE.kbits.UL. 144.384.BestCell
Feature Name Interactive QoS Class Background QoS Class Interactive QoS Class Background QoS Class
1.12.46.26 DL Traffic of BE Services with Different PS Data Rates for Best Cell Counters
Counter ID 67203454 Counter Name VS.PS.BE.kbits.DL. 0.32.BestCell Counter Description DL Traffic Volume of PS BE Services (0 Kbit/s < DL Bit Rate <= 32 Kbit/s) for Best Cell DL Traffic Volume of PS BE Services (32 Kbit/s < DL Bit Rate <= 64 Kbit/s) for Best Cell DL Traffic Volume of PS BE Services (64 Kbit/s < DL Bit Rate <= 144 Kbit/s) for Best Cell DL Traffic Volume of PS BE Services (144 Kbit/s < DL Bit Rate <= 384 Kbit/s) for Best Cell
67203456
VS.PS.BE.kbits.DL. 32.64.BestCell
67203458
67203460
Description
These counters provides the downlink traffic of BE services with different PS data rates in the best cell.
Measurement point
The downlink traffic of BE services with different PS data rates over the DCH and FACH is accumulated in the measurement period for the best cell under the SRNC.
Formula
None
Unit
kbit
Related Features
Counter Name VS.PS.BE.kbits.DL. 0.32.BestCell VS.PS.BE.kbits.DL. 32.64.BestCell VS.PS.BE.kbits.DL. 64.144.BestCell VS.PS.BE.kbits.DL. 144.384.BestCell Feature ID WRFD-010503 WRFD-010504 WRFD-010503 WRFD-010504 WRFD-010503 WRFD-010504 WRFD-010503 WRFD-010504 Feature Name Interactive QoS Class Background QoS Class Interactive QoS Class Background QoS Class Interactive QoS Class Background QoS Class Interactive QoS Class Background QoS Class
1.12.46.27 Mean Number of AMR service UEs in the best cell Counters
Counter ID 67192689 Counter Name VS.AMR.Erlang.BestCell Counter Description Equivalent Erlang for AMR Services for Best Cell
Description
This measurement item provides the mean number of UEs that use the AMR speech service (narrowband and wideband AMR services) in the best cell.
Measurement point
The RNC takes samples every 30 seconds in a measurement period. At the end of the measurement period, the RNC obtains the value of this counter by dividing the sum of sampling values by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.AMR.Erlang.BestCell Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.12.46.28 Mean Number of VP service UEs in the best cell Counters

Counter ID 67192690 Counter Name VS.VP.Erlang.BestCell Counter Description Num Of Erlang of VP service in the best cell
Description
This counter provides the mean number of UEs for all VP services in the best cell.
Measurement point
The RNC takes samples every 30 seconds in a measurement period. At the end of the measurement period, the RNC obtains the value of this counter by dividing the sum of sampling values by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.VP.Erlang.BestCell Feature ID WRFD-010502 Feature Name Streaming QoS Class
1.12.46.29 Average Throughput of PTM MBMS Services
Issue 01 (2013-05-04)
2472
Counters
Counter ID 67204482 Counter Name VS.MBMS.PTM.MeanThroughput Counter Description Average Throughput of PTM MBMS Services for Cell
Description
This counter provides the average downlink throughput of MBMS services with the transmission mode of PTM in the cell.
Measurement point
The RNC takes samples on the downlink throughput of MBMS services with the transmission mode of PTM periodically. At the end of the measurement period, the value of this counter is calculated.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.MBMS.PTM.MeanThroughput Feature ID WRFD-01061608 Feature Name 16/32/64/128Kbps Channel Rate on MBMS
1.12.46.30 Average Throughput of PTP MBMS Services Counters

Counter ID 67204483 Counter Name VS.MBMS.PTP.MeanThroughput Counter Description Average Throughput of PTP MBMS Services for Cell
Description
This counter provides the average downlink throughput of MBMS services with the transmission mode of PTP in the cell.
Measurement point
The RNC takes samples on the downlink throughput of MBMS services with the transmission mode of PTP periodically. At the end of the measurement period, the value of this counter is calculated.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.MBMS.PTP.MeanThroughput Feature ID WRFD-01061608 Feature Name 16/32/64/128Kbps Channel Rate on MBMS
1.12.46.31 Average DL Bit Rate of PS Conversational Service Counters

Counter ID 73410482 Counter Name VS.PS.Conv.Kbps.DL Counter Description Average downlink throughput of the Traffic PS Conversational beared on DCH for cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73393909 Counter Name VS.PS.Conv.DL.Times Counter Description Duration of Measuring Throughput of PS Downlink Conversational Service for Cell
Description
This measurement item takes statistics of the average downlink throughput of the traffic PS conversational beared on DCH in the active cell.
Measurement point
The RNC measures all DL traffic volume (unit: bit) and duration (unit: ms) of the PS conversational service in the SRNC cell of the RLC layer. At the end of a measurement period, this counter is calculated using the following formula:
Formula
VS.PS.Conv.Kbps.DL = [VS.PS.Conv.DL.Traffic]/[VS.PS.Conv.DL.Times]
Unit
kbit/s
Related Features
Counter Name VS.PS.Conv.Kbps.DL Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.12.46.32 DL Throughput of PS Conversational Service Counters

Counter ID 73393908 Counter Name VS.PS.Conv.DL.Traffic Counter Description Number of downlink Bit Size of Transport Blocks of Traffic PS Conversational beared on DCH for cell
Description
This measurement item takes statistics of the number of downlink Bit Size of Transport Blocks of traffic PS conversational beared on DCH in the active cell.
Measurement point
The RNC measures the total DL volume of PS conversational service by the SRNC cell in the RLC layer.
Formula
None
Unit
bit
Related Features
Counter Name VS.PS.Conv.DL.Traffic Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.12.46.33 Average UL Bit Rate of PS Conversational Service Counters

Counter ID 73410483 Counter Name VS.PS.Conv.Kbps.UL Counter Description Average uplink throughput of the Traffic PS Conversational beared on DCH for cell
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 73393911 Counter Name VS.PS.Conv.UL.Times Counter Description Duration of Measuring Throughput of PS uplink Conversational Service for Cell
Description
This measurement item takes statistics of the average uplink throughput of the traffic PS conversational beared on DCH in the active cell.
Measurement point
The RNC measures all UL traffic volume (unit: bit) and duration (unit: ms) of the PS conversational service in the SRNC cell of the RLC layer. At the end of a measurement period, this counter is calculated using the following formula:
Formula
VS.PS.Conv.Kbps.UL = [VS.PS.Conv.UL.Traffic]/[VS.PS.Conv.UL.Times]
Unit
kbit/s
Related Features
Counter Name VS.PS.Conv.Kbps.UL Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.12.46.34 UL Throughput of PS Conversational Service Counters

Counter ID 73393910 Counter Name VS.PS.Conv.UL.Traffic Counter Description Number of uplink Bit Size of Transport Blocks of Traffic PS Conversational beared on DCH for cell
Description
This measurement item takes statistics of the number of uplink Bit Size of Transport Blocks of traffic PS conversational beared on DCH in the active cell.
Measurement point
The RNC measures the total UL volume of PS conversational service by the SRNC cell in the RLC layer.
Formula
None
Unit
bit
Related Features
Counter Name VS.PS.Conv.UL.Traffic Feature ID WRFD-010501 Feature Name Conversational QoS Class
1.12.46.35 Sum of Sampled Downlink BE Throughput of UEs with PS Services over DCHs
Counters
Counter ID 73426120 Counter Name VS.PS.BE.DCH.DL.SumThroughput Counter Description Sum of Sampled Downlink BE Throughput of UEs with PS Services over DCHs
Description
This counter provides the sum of sampled downlink BE throughput of UEs whose PS services are carried over DCHs in the best cell. The unit of the counter is Kbit/s.
Measurement point
The system samples the downlink BE throughput of all the R99 UEs that are processing PS services at an interval of 500 ms. This counter then sums the sample values within each measurement period for the best cell. Note that the RLC headers and retransmitted data are excluded. For PS combined services, only one RAB is taken into account.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.PS.BE.DCH.DL.SumThroughput Feature ID WRFD-010503 WRFD-010504 Feature Name Interactive QoS Class Background QoS Class
1.12.46.36 Number of Times Downlink BE Throughput of UEs with PS Services over DCHs Is Sampled Counters
Counter ID 73426121 Counter Name VS.PS.BE.DCH.DL.SamplesThroughput Counter Description Number of Times Downlink BE Throughput of UEs with PS Services over DCHs Is Sampled
Issue 01 (2013-05-04)
2478
Description
This counter provides the number of times downlink BE throughput of UEs whose PS services are carried over DCHs is sampled in the best cell.
Measurement point
The system samples the downlink BE throughput of all the R99 UEs that are processing PS services at an interval of 500 ms. This counter then calculates the number of times the downlink BE throughput of such R99 PS UEs whose downlink BE throughput is not 0 is sampled within each measurement period for the best cell.
Formula
None
Unit
None
Related Features
Counter Name VS.PS.BE.DCH.DL.SamplesThroughput Feature ID WRFD-010503 WRFD-010504 Feature Name Interactive QoS Class Background QoS Class
1.12.46.37 Sum of Sampled Uplink BE Throughput of UEs with PS Services over DCHs Counters
Counter ID 73426122 Counter Name VS.PS.BE.DCH.UL.SumThroughput Counter Description Sum of Sampled Uplink BE Throughput of UEs with PS Services over DCHs
Description
This counter provides the sum of sampled uplink BE throughput of UEs whose PS services are carried over DCHs in the best cell. The unit of the counter is Kbit/s.
Measurement point
The system samples the uplink BE throughput of all the R99 UEs that are processing PS services at an interval of 500 ms. This counter then sums the sample values within each measurement period for the best cell. Note that the RLC headers and retransmitted data are excluded. For PS combined services, only one RAB is taken into account.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.PS.BE.DCH.UL.SumThroughput Feature ID WRFD-010503 WRFD-010504 Feature Name Interactive QoS Class Background QoS Class
1.12.46.38 Number of Times Uplink BE Throughput of UEs with PS Services over DCHs Is Sampled Counters
Counter ID 73426123 Counter Name VS.PS.BE.DCH.UL.SamplesThroughput Counter Description Number of Times Uplink BE Throughput of UEs with PS Services over DCHs Is Sampled
Description
This counter provides the number of times uplink BE throughput of UEs whose PS services are carried over DCHs is sampled in the best cell.
Measurement point
The system samples the uplink BE throughput of all the R99 UEs that are processing PS services at an interval of 500 ms. This counter then calculates the number of times uplink BE throughput of such R99 PS UEs whose uplink BE throughput is not 0 is sampled within each measurement period for the best cell.
Formula
None
Unit
None
Related Features
Counter Name VS.PS.BE.DCH.UL.SamplesThroughput Feature ID WRFD-010503 WRFD-010504 Feature Name Interactive QoS Class Background QoS Class
1.12.46.39 Number of Erlangs for AMR Services for Cell Counters

Counter ID 73426291 Counter Name VS.RAB.AMR.Erlang.cell Counter Description Number of Erlangs for AMR Services for Cell
Description
This counter provides the number of Erlangs for AMR services based on the holding time in a cell.
Measurement point
This counter is measured based on the actual holding time that is the time for releasing a RAB minus the time for establishing the RAB in a cell where the RAB is released. Within a measurement period, the number of Erlangs is calculated using the following formula: SUM(All AMR RAB Holding Time in minute)/60 min. If there are multiple cells in the active set when the RAB is released, this counter is measured in the best cell.
Formula
None
Unit
Erl
Related Features
Counter Name VS.RAB.AMR.Erlang.cell Feature ID MRFD-210403 Feature Name License Management
Issue 01 (2013-05-04)
2481
1.12.47 Traffic Measurement per cell(TRFFIC.Cell)

Overview
This function subset involves the items related to the traffic on the common transport channels (PCH, RACH, and FACH) and on the dedicated transport channels on the Iub Interface. The function subset also involves the items about soft handover. The traffic on the dedicated transport channels are measured on the basis of the service type.
Counters
Counter ID 67189782 67202807 67202808 67202422 Counter Name VS.BcchSrbKbps. Dl VS.CcchSrbKbps. Dl VS.CcchSrbKbps. Ul VS.DRNCIubBytes DCH.Rx Counter Description DL Signaling Rate over BCCH for Cell DL Signaling Rate over CCCH for Cell UL Signaling Rate over CCCH for Cell Number of UL Service Bytes over DRNC Iub DCH for Cell Number of DL Service Bytes over DRNC Iub DCH for Cell Number of UL Signaling Bytes on Iub Interface for Cell Number of DL Signaling Bytes on Iub Interface for Cell Number of UL Bytes of PS Conversational Services over Iub DCH for Cell Number of UL Bytes of PS R99 Streaming Services over Iub DCH for Cell Number of UL Bytes of PS R99 Interactive Services over Iub DCH for Cell Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67202423
VS.DRNCIubBytes DCH.Tx
67199640
VS.SRNCIubBytes DCHSig.Rx VS.SRNCIubBytes DCHSig.Tx VS.SRNCIubBytes PSR99Conv.Rx
67199641
67199650
67199651
VS.SRNCIubBytes PSR99Str.Rx
67199652
VS.SRNCIubBytes PSR99Int.Rx
Issue 01 (2013-05-04)
2482
Counter ID 67199653
Counter Name VS.SRNCIubBytes PSR99Bkg.Rx
Counter Description Number of UL Bytes of PS R99 Background Services over Iub DCH for Cell Number of DL Bytes of PS Conversational Services over Iub DCH for Cell Number of DL Bytes of PS R99 Streaming Services over Iub DCH for Cell Number of DL Bytes of PS R99 Interactive Services over Iub DCH for Cell Number of DL Bytes of PS R99 Background Services over Iub DCH for Cell Number of UL Bytes of CS Conversational Services over Iub DCH for Cell Number of UL Bytes of CS Streaming Services over Iub DCH for Cell Number of DL Bytes of CS Conversational Services over Iub DCH for Cell Number of DL Bytes of CS Streaming Services over Iub DCH for Cell Number of Bytes over Iub RACH for Cell
67199654
VS.SRNCIubBytes PSR99Conv.Tx
67199655
VS.SRNCIubBytes PSR99Str.Tx
67199656
VS.SRNCIubBytes PSR99Int.Tx
67199657
VS.SRNCIubBytes PSR99Bkg.Tx
67199642
VS.SRNCIubBytes CSConv.Rx
67199643
VS.SRNCIubBytes CSStr.Rx
67199646
VS.SRNCIubBytes CSConv.Tx
67199647
VS.SRNCIubBytes CSStr.Tx
67199639
VS.CRNCIubBytes RACH.Rx
Issue 01 (2013-05-04)
2483
Counter ID 67199638
Counter Name VS.CRNCIubBytes FACH.Tx VS.CRNCIubBytes PCH.Tx VS.CRNC.IUB.RA CH.Bandwidth VS.CRNC.IUB.FA CH.Bandwidth VS.CRNC.IUB.PC H.Bandwidth VS.MBMS.IUB.BA NDWIDTH VS.CRNCIubBytes PSR99.CCH.Rx VS.CRNCIubBytes PSR99.CCH.Tx VS.SRNCIubBytes HSDPA.Tx VS.SRNCIubBytes HSUPA.Rx
Counter Description Number of Bytes over Iub FACH for Cell Number of Bytes over Iub PCH for Cell RACH Bandwidth of CRNC for Cell FACH Bandwidth of CRNC for Cell PCH Bandwidth of CRNC for Cell Bandwidth of MBMS Services for Cell Number of Bytes of UL PS Services over Iub RACH for Cell Number of Bytes of DL PS Services over Iub FACH for Cell Number of DL Bytes over Iub HSDSCH for Cell Number of UL Bytes over Iub EDCH for Cell
Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 V900R012
67199637
67199739 67199740 67199741 67204155
67204753
67204754
73410499
73410500
V900R012
None
1.12.47.1 DL Signaling Rate over BCCH on Iub Interface Counters

Counter ID 67189782 Counter Name VS.BcchSrbKbps.Dl Counter Description DL Signaling Rate over BCCH for Cell
Issue 01 (2013-05-04)
2484
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67190392 Counter Name BCCH.SRB.KBPS.DL.Time s BCCH.SRB.KBPS.DL.Volume Counter Description Duration of Measuring the Bits of Transport Blocks on DL BCCH for Cell Number of DL Bits on BCCH for Cell
67190391
Description
This counter provides the average DL signaling rate of the CRNC over the BCCH on the Iub interface within the cell.
Measurement point
When sending the DL signaling over the BCCH on the Iub interface, the CRNC measures the data transmission period and the number of DL signaling bits (not including the FP header). At the end of the measurement period, the value of this counter is obtained as follows: dividing the total number of transmitted signaling bits by the transmission period.
Formula
VS.BcchSrbKbps.Dl = [BCCH.SRB.KBPS.DL.Volume]/[BCCH.SRB.KBPS.DL.Times]
Unit
kbit/s
Related Features
Counter Name VS.BcchSrbKbps.Dl Feature ID WRFD-020900 Feature Name Logical Channel Management
1.12.47.2 DL Signaling Rate over CCCH on Iub Interface Counters

Counter ID 67202807 Counter Name VS.CcchSrbKbps.Dl Counter Description DL Signaling Rate over CCCH for Cell
Issue 01 (2013-05-04)
2485
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67189784 Counter Name VS.CcchSrbKbps.Dl.Times Counter Description Duration of Measuring the Bits of Transport Blocks on DL CCCH for Cell Number of DL Signaling Bits on CCCH for Cell
67189783
VS.CcchSrbKbps.Dl.Volume
Description
This counter provides the average DL signaling rate of the CRNC over the CCCH on the Iub interface within the cell.
Measurement point
When sending the DL signaling over the CCCH on the Iub interface, the CRNC measures the data transmission period and the number of DL signaling bits (not including the FP header). At the end of the measurement period, the value of this counter is obtained as follows: dividing the total number of transmitted signaling bits by the transmission period.
Formula
VS.CcchSrbKbps.Dl = [VS.CcchSrbKbps.Dl.Volume]/[VS.CcchSrbKbps.Dl.Times]
Unit
kbit/s
Related Features
Counter Name VS.CcchSrbKbps.Dl Feature ID WRFD-020900 Feature Name Logical Channel Management
1.12.47.3 UL Signaling Rate over CCCH on Iub Interface Counters

Counter ID 67202808 Counter Name VS.CcchSrbKbps.Ul Counter Description UL Signaling Rate over CCCH for Cell
Issue 01 (2013-05-04)
2486
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67189786 Counter Name VS.CcchSrbKbps.Ul.Times Counter Description Duration of Measuring the Bits of Transport Blocks on UL CCCH for Cell Number of UL Signaling Bits on CCCH for Cell
67189785
VS.CcchSrbKbps.Ul.Volume
Description
This counter provides the average UL signaling rate of the CRNC over the CCCH on the Iub interface within the cell.
Measurement point
When receiving the UL signaling over the CCCH on the Iub interface, the CRNC measures the data transmission period and the number of UL signaling bits (not including the FP header). At the end of the measurement period, the value of this counter is obtained as follows: dividing the total number of transmitted signaling bits by the transmission period.
Formula
VS.CcchSrbKbps.Ul = [VS.CcchSrbKbps.Ul.Volume]/[VS.CcchSrbKbps.Ul.Times]
Unit
kbit/s
Related Features
Counter Name VS.CcchSrbKbps.Ul Feature ID WRFD-020900 Feature Name Logical Channel Management
1.12.47.4 UL Service Traffic over DCH on Iub Interface for DRNC Counters
Counter ID 67202422 Counter Name VS.DRNCIubBytesDCH.Rx Counter Description Number of UL Service Bytes over DRNC Iub DCH for Cell
Issue 01 (2013-05-04)
2487
Description
This counter provides the bytes of UL MAC PDUs for the SRNC received by the DRNC over the DCH FP that carries services on the Iub interface. The measurement involves the cells in the active set.
Measurement point
The measurement is triggered when the DRNC receives UL data that is for the SRNC over the DCH FP (not including the EDCH FP) that carries services on the Iub interface. The FP header is not included.
Formula
None
Unit
byte
Related Features
Counter Name VS.DRNCIubBytesDCH.Rx Feature ID WRFD-021000 Feature Name Transport Channel Management
1.12.47.5 DL Service Traffic over DCH on Iub Interface for DRNC Counters
Counter ID 67202423 Counter Name VS.DRNCIubBytesDCH.Tx Counter Description Number of DL Service Bytes over DRNC Iub DCH for Cell
Description
This counter provides the bytes of DL MAC PDUs from the SRNC sent by the DRNC over the DCH FP that carries services on the Iub interface. The measurement involves the cells in the active set.
Measurement point
The measurement is triggered when the DRNC sends DL data that is from the SRNC over the DCH FP (not including the HS-DSCH FP) that carries services on the Iub interface. The FP header is not included.
Formula
None
Unit
byte
Related Features
Counter Name VS.DRNCIubBytesDCH.Tx Feature ID WRFD-021000 Feature Name Transport Channel Management
1.12.47.6 UL Signaling Traffic on Iub Interface Counters

Counter ID 67199640 Counter Name VS.SRNCIubBytesDCHSig. Rx Counter Description Number of UL Signaling Bytes on Iub Interface for Cell
Description
This counter provides the bytes of UL MAC PDUs received by the SRNC over the DCH FP (exclude EDCH FP and RACH FP) that carry signaling on the Iub interface. The measurement involves the cells in the active set.
Measurement point
The measurement is triggered when the SRNC receives UL signaling over the DCH FP on the Iub interface. The FP header is not included.
Formula
None
Unit
byte
Issue 01 (2013-05-04)
2489
Related Features
Counter Name VS.SRNCIubBytesDCHSig. Rx Feature ID WRFD-021000 Feature Name Transport Channel Management
1.12.47.7 DL Signaling Traffic on Iub Interface Counters

Counter ID 67199641 Counter Name VS.SRNCIubBytesDCHSig. Tx Counter Description Number of DL Signaling Bytes on Iub Interface for Cell
Description
This counter provides the number of bytes of DL MAC PDUs sent by the SRNC over the DCH FP(exclude HS-DSCH FP and FACH FP) that carry signaling on the Iub interface. The measurement involves the cells in the active set.
Measurement point
The measurement is triggered when the SRNC sends DL signaling over the DCH FP on the Iub interface. The FP header is not included.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIubBytesDCHSig. Tx Feature ID WRFD-021000 Feature Name Transport Channel Management
1.12.47.8 UL PS R99 Traffic on Iub Interface

Counters
Counter ID 67199650 Counter Name VS.SRNCIubBytesPSR99C onv.Rx VS.SRNCIubBytesPSR99St r.Rx VS.SRNCIubBytesPSR99In t.Rx VS.SRNCIubBytesPSR99B kg.Rx Counter Description Number of UL Bytes of PS Conversational Services over Iub DCH for Cell Number of UL Bytes of PS R99 Streaming Services over Iub DCH for Cell Number of UL Bytes of PS R99 Interactive Services over Iub DCH for Cell Number of UL Bytes of PS R99 Background Services over Iub DCH for Cell
67199651
67199652
67199653
Description
These counters provide the number of uplink MAC PDU bytes received by the SRNC on the PS R99 service bearer DCH FP over the Iub interface in a cell in the active set.
Measurement point
The measurement is triggered when the SRNC receives uplink data carried on the PS R99 service bearer DCH FP over the Iub interface. The measured data excludes the FP header.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIubBytesPSR99C onv.Rx VS.SRNCIubBytesPSR99St r.Rx VS.SRNCIubBytesPSR99In t.Rx VS.SRNCIubBytesPSR99B kg.Rx
Issue 01 (2013-05-04)
Feature Name Conversational QoS Class Streaming QoS Class Interactive QoS Class Background QoS Class
2491
1.12.47.9 DL PS R99 Traffic on Iub Interface Counters

Counter ID 67199654 Counter Name VS.SRNCIubBytesPSR99C onv.Tx VS.SRNCIubBytesPSR99St r.Tx VS.SRNCIubBytesPSR99In t.Tx VS.SRNCIubBytesPSR99B kg.Tx Counter Description Number of DL Bytes of PS Conversational Services over Iub DCH for Cell Number of DL Bytes of PS R99 Streaming Services over Iub DCH for Cell Number of DL Bytes of PS R99 Interactive Services over Iub DCH for Cell Number of DL Bytes of PS R99 Background Services over Iub DCH for Cell
67199655
67199656
67199657
Description
These counters provide the number of downlink MAC PDU bytes sent by the SRNC on the PS R99 service bearer DCH FP over the Iub interface in a cell in the active set.
Measurement point
The measurement is triggered when the SRNC sends downlink data carried on the PS R99 service bearer DCH FP over the Iub interface. The measured data excludes the FP header.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIubBytesPSR99C onv.Tx VS.SRNCIubBytesPSR99St r.Tx
Issue 01 (2013-05-04)
Feature Name Conversational QoS Class Streaming QoS Class
2492
Counter Name VS.SRNCIubBytesPSR99In t.Tx VS.SRNCIubBytesPSR99B kg.Tx
Feature Name Interactive QoS Class Background QoS Class
1.12.47.10 UL CS Traffic on Iub Interface Counters

Counter ID 67199642 Counter Name VS.SRNCIubBytesCSConv. Rx VS.SRNCIubBytesCSStr.Rx Counter Description Number of UL Bytes of CS Conversational Services over Iub DCH for Cell Number of UL Bytes of CS Streaming Services over Iub DCH for Cell
67199643
Description
These counters provide the number of uplink MAC PDU bytes received by the SRNC on the CS service bearer DCH FP over the Iub interface in a cell in the active set.
Measurement point
The measurement is triggered when the SRNC receives uplink data carried on the CS service bearer DCH FP over the Iub interface. The measured data excludes the FP header.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIubBytesCSConv. Rx VS.SRNCIubBytesCSStr.Rx Feature ID WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class
Issue 01 (2013-05-04)
2493
1.12.47.11 DL CS Traffic on Iub Interface Counters

Counter ID 67199646 Counter Name VS.SRNCIubBytesCSConv. Tx VS.SRNCIubBytesCSStr.Tx Counter Description Number of DL Bytes of CS Conversational Services over Iub DCH for Cell Number of DL Bytes of CS Streaming Services over Iub DCH for Cell
67199647
Description
These counters provide the number of downlink MAC PDU bytes sent by the SRNC on the CS service bearer DCH FP over the Iub interface in a cell in the active set.
Measurement point
The measurement is triggered when the SRNC sends downlink data carried on the CS service bearer DCH FP over the Iub interface. The measured data excludes the FP header.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIubBytesCSConv. Tx VS.SRNCIubBytesCSStr.Tx Feature ID WRFD-010501 WRFD-010502 Feature Name Conversational QoS Class Streaming QoS Class
1.12.47.12 Traffic over RACH on Iub Interface
Issue 01 (2013-05-04)
2494
Counters
Counter ID 67199639 Counter Name VS.CRNCIubBytesRACH.R x Counter Description Number of Bytes over Iub RACH for Cell
Description
This counter provides the bytes of UL MAC PDUs (including the signaling data and the service data, not including the FP header) received by the CRNC over the RACH FP on the Iub interface. The measurement involves cells in the active set.
Measurement point
The measurement is triggered when the CRNC sends UL data over the RACH FP on the Iub interface.
Formula
None
Unit
byte
Related Features
Counter Name VS.CRNCIubBytesRACH.R x Feature ID WRFD-021000 Feature Name Transport Channel Management
1.12.47.13 Traffic over FACH on Iub Interface Counters

Counter ID 67199638 Counter Name VS.CRNCIubBytesFACH.T x Counter Description Number of Bytes over Iub FACH for Cell
Description
This counter provides the bytes of DL MAC PDUs (including the signaling data and the service data, not including the FP header) sent by the CRNC over the FACH FP on the Iub interface. The measurement involves cells in the active set.
Measurement point
The measurement is triggered when the CRNC sends DL data over the FACH FP on the Iub interface.
Formula
None
Unit
byte
Related Features
Counter Name VS.CRNCIubBytesFACH.T x Feature ID WRFD-021000 Feature Name Transport Channel Management
1.12.47.14 Traffic over PCH on Iub Interface Counters

Counter ID 67199637 Counter Name VS.CRNCIubBytesPCH.Tx Counter Description Number of Bytes over Iub PCH for Cell
Description
This counter provides the number of bytes in PI fields of headers and payload of the PCH FP packets transmitted over the Iub interface by the CRNC in a cell.
Measurement point
The measurement is triggered when the CRNC sends DL data over the PCH FP on the Iub interface.
Formula
None
Unit
byte
Related Features
Counter Name VS.CRNCIubBytesPCH.Tx Feature ID WRFD-021000 Feature Name Transport Channel Management
1.12.47.15 Counters Related to the Bandwidth of Common Channels on Iub Interface for CRNC Counters
Counter ID 67199739 67199740 67199741 Counter Name VS.CRNC.IUB.RACH.Ban dwidth VS.CRNC.IUB.FACH.Band width VS.CRNC.IUB.PCH.Bandwidth Counter Description RACH Bandwidth of CRNC for Cell FACH Bandwidth of CRNC for Cell PCH Bandwidth of CRNC for Cell
Description
These counters provide the bandwidth of common channels for the CRNC on the Iub interface in the unit of bytes per second. The measurement involves cells in the active set.
Measurement point
The measurement is triggered when the CRNC sets up or removes a common channel on the Iub interface.
Formula
None
Unit
byte/s
Related Features
Counter Name VS.CRNC.IUB.RACH.Ban dwidth
Issue 01 (2013-05-04)
Feature Name Transport Channel Management

2497
Counter Name VS.CRNC.IUB.FACH.Band width VS.CRNC.IUB.PCH.Bandwidth
Feature Name Transport Channel Management Transport Channel Management
1.12.47.16 Bandwidth of Channel for MBMS Services Counters

Counter ID 67204155 Counter Name VS.MBMS.IUB.BANDWIDTH Counter Description Bandwidth of MBMS Services for Cell
Description
This counter provides the bandwidth of the channel for MBMS services on the Iub interface in the cell.
Measurement point
The measurement is triggered when an MBMS service is set up successfully in the cell.
Formula
None
Unit
byte/s
Related Features
Counter Name VS.MBMS.IUB.BANDWIDTH Feature ID WRFD-010616 Feature Name MBMS Introduction Package
1.12.47.17 PS Traffic over RACH on Iub Interface
Issue 01 (2013-05-04)
2498
Counters
Counter ID 67204753 Counter Name VS.CRNCIubBytesPSR99.C CH.Rx Counter Description Number of Bytes of UL PS Services over Iub RACH for Cell
Description
This counter provides the bytes of UL MAC PDUs (not including the FP header) received by the CRNC over the RACH FP on the Iub interface. The measurement involves cells in the active set.
Measurement point
The measurement is triggered when the CRNC receives UL data over the RACH FP that carries PS services on the Iub interface.
Formula
None
Unit
byte
Related Features
Counter Name VS.CRNCIubBytesPSR99.C CH.Rx Feature ID WRFD-021000 Feature Name Transport Channel Management
1.12.47.18 PS Traffic over FACH on Iub Interface Counters

Counter ID 67204754 Counter Name VS.CRNCIubBytesPSR99.C CH.Tx Counter Description Number of Bytes of DL PS Services over Iub FACH for Cell
Issue 01 (2013-05-04)
2499
Description
This counter provides the bytes of DL MAC PDUs (not including the FP header) sent by the CRNC over the FACH FP on the Iub interface. The measurement involves cells in the active set.
Measurement point
The measurement is triggered when the CRNC sends DL data over the FACH FP that carries PS services on the Iub interface.
Formula
None
Unit
byte
Related Features
Counter Name VS.CRNCIubBytesPSR99.C CH.Tx Feature ID WRFD-021000 Feature Name Transport Channel Management
1.12.47.19 DL HSDPA Traffic on Iub Interface Counters

Counter ID 73410499 Counter Name VS.SRNCIubBytesHSDPA. Tx Counter Description Number of DL Bytes over Iub HSDSCH for Cell
Description
This counter provides the bytes of DL MAC PDUs sent by the SRNC over the HS-DSCH FP on the Iub interface(exclude DL signal data). The measurement involves HSDPA serving cells. For DC-HSDPA users, this counter is measured only in the primary cell based on the total number of bytes sent on the primary and secondary carriers.
Measurement point
The measurement is triggered when the SRNC sends DL data over the HS-DSCH FP on the Iub interface. The FP header is not included.
Formula
None
Unit
byte
Related Features
Counter Name VS.SRNCIubBytesHSDPA. Tx Feature ID WRFD-010610 Feature Name HSDPA Introduction Package
1.12.47.20 UL HSUPA Traffic on Iub Interface Counters

Counter ID 73410500 Counter Name VS.SRNCIubBytesHSUPA. Rx Counter Description Number of UL Bytes over Iub EDCH for Cell
Description
This counter provides the bytes of UL MAC PDUs received by the SRNC over the EDCH FP on the Iub interface(exclude UL signal data). The measurement involves HSUPA cells in active set.For DC-HSUPA users, this counter is measured only in the primary cell based on the total number of bytes received on the primary and secondary carriers.
Measurement point
The measurement is triggered when the SRNC receives UL data over the EDCH FP on the Iub interface. The FP header is not included.
Formula
None
Unit
byte
Issue 01 (2013-05-04)
2501
Related Features
Counter Name VS.SRNCIubBytesHSUPA. Rx Feature ID WRFD-010612 Feature Name HSUPA Introduction Package
1.12.48 Measurement related to U2L Handover per cell (U2LTE.HO.Cell)

Overview
According to handover methods, outgoing UMTS-to-LTE PS handovers can be classified into PS inter-RAT handovers and redirection triggered by RRC connection release. Counters related to the number of failed handovers during different phases of outgoing handovers are measured based on different handover causes.
Counters
Counter ID 73423386 Counter Name VS.U2LTEHO.Att OutPS.Service Counter Description Number of ServiceBased UMTS-toLTE PS Handover Attempts for Cell Number of Successful ServiceBased UMTS-toLTE PS Handovers for Cell Number of Failed UMTS-to-LTE PS Handovers Due to Iu Release Command Timeout for Cell Number of Failed UMTS-to-LTE PS Handovers for Cell (Configuration Unsupported) Number of Failed UMTS-to-LTE PS Handovers for Cell (Physical Channel Failure) Original Release V900R013
73423387
VS.U2LTEHO.Suc cOutPS.Service
V900R013
73423408
VS.U2LTEHO.Fail OutPS.NoReply
V900R013
73423409
VS.U2LTEHO.Fail OutPS.CfgUnSupp
V900R013
73423410
VS.U2LTEHO.Fail OutPS.PhyChFail
V900R013
Issue 01 (2013-05-04)
2502
Counter ID 73423411
Counter Name VS.U2LTEHO.Fail OutPS.Abort
Counter Description Number of Abnormally Terminated Outgoing UMTS-toLTE PS Handovers for Cell Number of Outgoing UMTS-to-LTE PS Handover Preparation Attempts for Cell Number of Successful Preparations for Outgoing UMTS-toLTE PS Handovers for Cell Number of Failed Preparations for Outgoing UMTS-toLTE PS Handovers for Cell (No Resource Available) Number of Failed Preparations for Outgoing UMTS-toLTE PS Handovers for Cell (Relocation Failure in Target CN/ RNC or Target System) Number of Failed Preparations for Outgoing UMTS-toLTE PS Handovers for Cell (Relocation not supported in Target RNC or Target system)
73423412
VS.U2LTEHO.AttRelocPrepOutPS
V900R013
73423413
VS.U2LTEHO.Suc cRelocPrepOutPS
V900R013
73423414
VS.U2LTEHO.Fail RelocPrepOutPS.N oResAvail
V900R013
73423415
VS.U2LTEHO.Fail RelocPrepOutPS.T gtFail
V900R013
73423416
VS.U2LTEHO.Fail RelocPrepOutPS.R eloUnSupp
V900R013
Issue 01 (2013-05-04)
2503
Counter ID 73423417
Counter Name VS.U2LTEHO.Fail RelocPrepOutPS.T gtHighLoad
Counter Description Number of Failed Preparations for Outgoing UMTS-toLTE PS Handovers for Cell (Traffic Load In The Target Cell Higher Than In The Source Cell) Number of Failed Preparations for Outgoing UMTS-toLTE PS Handovers for Cell (Unknown Target RNC) Number of ServiceBased Redirection to LTE Through RRC Connection Release for Cell Number of Failed Preparations for Outgoing UMTS-toLTE PS Handovers for Cell (TRELOCalloc expiry) Number of Measurement-based UMTS-to-LTE PS Handover Attempts Triggered by Poor Coverage for Cell Number of Successful Measurement-based UMTS-to-LTE PS Handovers Triggered by Poor Coverage for Cell
73423418
VS.U2LTEHO.Fail RelocPrepOutPS.U nKnowRNC
V900R013
73423419
VS.U2LTEHO.RR CRelease.Service
V900R013
73423420
VS.U2LTEHO.Fail RelocPrepOutPS.T AlExp
V900R013
73425851
VS.U2LHO.AttOut PS.Coverage
V900R015
73425852
VS.U2LHO.SuccO utPS.Coverage
V900R015
Issue 01 (2013-05-04)
2504
Counter ID 73425853
Counter Name VS.U2LHO.AttRel ocPrepOutPS.Coverage
Counter Description Number of Preparation Attempts for Outgoing Coveragetriggered UMTS-toLTE PS Handovers for Cell Number of Successful Preparations for Outgoing Coveragetriggered UMTS-toLTE PS Handovers for Cell Number of Coverage-based UMTS to LTE PS Redirections for Cell Number of Coverage-based UMTS to LTE PS Emergency Blind Redirections for Cell Number of LDRtriggered UMTS-toLTE PS Handover Attempts for Cell Number of Successful LDRtriggered UMTS-toLTE PS Handovers for Cell Number of Loadbased UMTS to LTE PS Redirections for Cell Number of Loadbased UMTS to LTE PS Blind Redirections for Cell Number of Servicebased UMTS to LTE PS Blind Redirections for Cell
73425854
VS.U2LHO.SuccRe locPrepOutPS.Coverage
V900R015
73425855
VS.U2LTEHO.RR CRelease.Coverage
V900R015
73425856
VS.U2LTEHO.RR CRelease.Coverage .EmergBlind
V900R015
73425857
VS.U2LTEHO.Att OutPS.Load
V900R015
73425858
VS.U2LTEHO.Suc cOutPS.Load
V900R015
73425859
VS.U2LTEHO.RR CRelease.Load
V900R015
73425860
VS.U2LTEHO.RR CRelease.Load.Bli nd VS.U2LTEHO.RR CRelease.Sevice.Bli nd
V900R015
73425819
V900R015
Issue 01 (2013-05-04)
2505
Counter VS.U2LTEHO.AttRelocPrepOutPS VS.U2LTEHO.SuccRelocPrepOutPS VS.U2LTEHO.RRCRelease.Coverage VS.U2LTEHO.RRCRelease.Load VS.U2LTEHO.RRCRelease.Service Sub Counter VS.U2LHO.AttRelocPrepOutPS.Coverage VS.U2LHO.SuccRelocPrepOutPS.Coverage VS.U2LTEHO.RRCRelease.Coverage.Eme rgBlind VS.U2LTEHO.RRCRelease.Load.Blind VS.U2LTEHO.RRCRelease.Sevice.Blind
1.12.48.1 Number of UMTS-to-LTE PS Handover Attempts Triggered by RNC for Cell Counters
Counter ID 73423386 Counter Name VS.U2LTEHO.AttOutPS.Se rvice VS.U2LHO.AttOutPS.Coverage Counter Description Number of Service-Based UMTS-to-LTE PS Handover Attempts for Cell Number of Measurementbased UMTS-to-LTE PS Handover Attempts Triggered by Poor Coverage for Cell Number of LDR-triggered UMTS-to-LTE PS Handover Attempts for Cell
73425851
73425857
VS.U2LTEHO.AttOutPS.Lo ad
Description
These counters provide the number of UMTS-to-LTE PS handover attempts in the best UMTS cell based on different handover causes (services, coverage, or load).
Measurement point
The measurement is triggered at point C shown in the figure, when the RNC sends the UE a HANDOVER FROM UTRAN COMMAND message during the UMTS-to-LTE PS handover triggered based on various causes. In this case, this counter is measured in the best cell that the UE camps on under the SRNC.
Figure 1-1102 Normal PS UMTS to LTE outgoing handover Procedure
Formula
None
Unit
None
Related Features
Counter Name VS.U2LTEHO.AttOutPS.Se rvice VS.U2LHO.AttOutPS.Coverage VS.U2LTEHO.AttOutPS.Lo ad Feature ID WRFD-140218 WRFD-150220 Feature Name Service-Based PS Handover from UMTS to LTE Coverage Based PS Handover from UMTS to LTE Load Based PS Handover from UMTS to LTE
WRFD-150217
1.12.48.2 Number of Successful UMTS-to-LTE PS Handovers for Cell
Issue 01 (2013-05-04)
2507
Counters
Counter ID 73423387 Counter Name VS.U2LTEHO.SuccOutPS. Service VS.U2LHO.SuccOutPS.Cov erage Counter Description Number of Successful Service-Based UMTS-toLTE PS Handovers for Cell Number of Successful Measurement-based UMTSto-LTE PS Handovers Triggered by Poor Coverage for Cell Number of Successful LDRtriggered UMTS-to-LTE PS Handovers for Cell
73425852
73425858
VS.U2LTEHO.SuccOutPS. Load
Description
These counters provide the number of successful UMTS-to-LTE PS handover attempts in the best UMTS cell based on different handover causes (services, coverage, or load).
Measurement point
The measurement is triggered at point D shown in the figure, when the RNC receives an IU RELEASE COMMAND message with the cause value of "Successful Relocation," "Normal Release," or "Network Optimization" after sending a HANDOVER FROM UTRAN COMMAND message during the UMTS-to-LTE PS handover triggered by different causes. In this case, this counter is measured in the best cell that the UE camps on under the SRNC. Figure 1-1103 Normal PS UMTS to LTE outgoing handover Procedure
Issue 01 (2013-05-04)
2508
Formula
None
Unit
None
Related Features
Counter Name VS.U2LTEHO.SuccOutPS. Service VS.U2LHO.SuccOutPS.Cov erage VS.U2LTEHO.SuccOutPS. Load Feature ID WRFD-140218 WRFD-150220 Feature Name Service-Based PS Handover from UMTS to LTE Coverage Based PS Handover from UMTS to LTE Load Based PS Handover from UMTS to LTE
WRFD-150217
1.12.48.3 Number of Failed UMTS-to-LTE PS Handovers Due to Iu Release Command Timeout for Cell Counters
Counter ID 73423408 Counter Name VS.U2LTEHO.FailOutPS.N oReply Counter Description Number of Failed UMTS-toLTE PS Handovers Due to Iu Release Command Timeout for Cell
Description
This counter provides the number of times that the UMTS-to-LTE PS handover fails in the best cell because the timer waiting for the IU RELEASE COMMAND message expires. This counter indicates that the UMTS-to-LTE PS handover fails. A higher value indicates a lower UMTS-toLTE PS handover success rate, and the failure cause should be checked at the LTE.
Measurement point
The measurement is triggered at point A shown in the figure. During the UMTS-to-LTE PS handover, after sending the HANDOVER FROM UTRAN COMMAND message, the RNC starts the timer waiting for the IU RELEASE COMMAND message from the CN. If no message
is received from the CN before the timer expires, this counter is measured in the best cell that the UE camps on under the SRNC before the handover. Figure 1-1104 PS UMTS to LTE outgoint handover Procedure(failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.U2LTEHO.FailOutPS.N oReply Feature ID WRFD-140218 WRFD-150220 WRFD-150217 Feature Name Service-Based PS Handover from UMTS to LTE Coverage Based PS Handover from UMTS to LTE Load Based PS Handover from UMTS to LTE
Issue 01 (2013-05-04)
2510
1.12.48.4 Number of Failed UMTS-to-LTE PS Handovers Due to Different Causes for Cell Counters
Counter ID 73423409 Counter Name VS.U2LTEHO.FailOutPS.C fgUnSupp Counter Description Number of Failed UMTS-toLTE PS Handovers for Cell (Configuration Unsupported) Number of Failed UMTS-toLTE PS Handovers for Cell (Physical Channel Failure)
73423410
VS.U2LTEHO.FailOutPS.P hyChFail
Description
These counters provide the number of failed UMTS-to-LTE PS handovers in the best cell due to different causes. These counters indicate that the UE fails to handle the HANDOVER FROM UTRAN COMMAND message. A high value of this counter indicates that the UE does not support the UMTS-to-LTE PS handover or the target LTE cell has poor LTE coverage.
Measurement point
The measurement is triggered at point A shown in the figure, when the RNC receives from the UE a HANDOVER FROM UTRAN FAILURE message during the outgoing UMTS-to-LTE PS handover. In this case, the corresponding counter is measured in the best cell that the UE camps on under the SRNC based on the failure cause. Figure 1-1105 PS UMTS to LTE outgoint handover Procedure(failed operation)
Issue 01 (2013-05-04)
2511
Formula
None
Unit
None
Related Features
Counter Name VS.U2LTEHO.FailOutPS.C fgUnSupp Feature ID WRFD-140218 WRFD-150220 WRFD-150217 Feature Name Service-Based PS Handover from UMTS to LTE Coverage Based PS Handover from UMTS to LTE Load Based PS Handover from UMTS to LTE VS.U2LTEHO.FailOutPS.P hyChFail WRFD-140218 WRFD-150220 WRFD-150217 Service-Based PS Handover from UMTS to LTE Coverage Based PS Handover from UMTS to LTE Load Based PS Handover from UMTS to LTE
1.12.48.5 Number of Abnormally Terminated Outgoing UMTS-to-LTE PS Handovers for Cell Counters
Counter ID 73423411 Counter Name VS.U2LTEHO.FailOutPS.A bort Counter Description Number of Abnormally Terminated Outgoing UMTS-to-LTE PS Handovers for Cell
Description
This counter provides the number of times that an outgoing UMTS-to-LTE PS handover is terminated abnormally in the best cell. This counter indicates that the UMTS-to-LTE PS handover is terminated abnormally due to some causes at the CN or LTE. If the value of this counter is high, check the detailed cause at the CN or LTE
Measurement point
The measurement is triggered at point D shown in the figure, when the RNC receives an IU RELEASE COMMAND message with a cause value other than "Successful Relocation", "Normal Release" or "Network Optimization" after sending a HANDOVER FROM UTRAN COMMAND message during the UMTS-to-LTE PS handover. In this case, this counter is measured in the best cell that the UE camps on under the SRNC. Figure 1-1106 PS UMTS to LTE outgoing handover Procedure
Formula
None
Unit
None
Related Features
Counter Name VS.U2LTEHO.FailOutPS.A bort Feature ID WRFD-140218 WRFD-150220 WRFD-150217 Feature Name Service-Based PS Handover from UMTS to LTE Coverage Based PS Handover from UMTS to LTE Load Based PS Handover from UMTS to LTE
1.12.48.6 Number of Outgoing UMTS-to-LTE PS Handover Preparation Attempts for Cell Counters
Counter ID 73423412 Counter Name VS.U2LTEHO.AttRelocPrepOutPS Counter Description Number of Outgoing UMTSto-LTE PS Handover Preparation Attempts for Cell
Description
This counter provides the number of attempts to prepare for an outgoing UMTS-to-LTE PS handover in the best cell.
Measurement point
The measurement is triggered at point A shown in the figure, when the RNC sends the CN a RELOCATION REQUIRED message during the outgoing UMTS-to-LTE PS handover. In this case, this counter is measured in the best cell that the UE camps on under the SRNC. Figure 1-1107 Normal PS UMTS to LTE outgoing handover Procedure
Issue 01 (2013-05-04)
2514
Formula
None
Unit
None
Related Features
Counter Name VS.U2LTEHO.AttRelocPrepOutPS Feature ID WRFD-140218 WRFD-150220 WRFD-150217 Feature Name Service-Based PS Handover from UMTS to LTE Coverage Based PS Handover from UMTS to LTE Load Based PS Handover from UMTS to LTE
1.12.48.7 Number of Successful Preparations for Outgoing UMTS-to-LTE PS Handovers for Cell Counters
Counter ID 73423413 Counter Name VS.U2LTEHO.SuccRelocPrepOutPS Counter Description Number of Successful Preparations for Outgoing UMTS-to-LTE PS Handovers for Cell
Description
This counter provides the number of times the preparation for an outgoing UMTS-to-LTE PS handover succeeds in the best cell.
Measurement point
The measurement is triggered at point B shown in the figure, when the RNC receives from the CN a RELOCATION COMMAND message during the outgoing UMTS-to-LTE PS handover. In this case, this counter is measured in the best cell that the UE camps on under the SRNC.
Issue 01 (2013-05-04)
2515
Formula
None
Unit
None
Related Features
Counter Name VS.U2LTEHO.SuccRelocPrepOutPS Feature ID WRFD-140218 WRFD-150220 WRFD-150217 Feature Name Service-Based PS Handover from UMTS to LTE Coverage Based PS Handover from UMTS to LTE Load Based PS Handover from UMTS to LTE
1.12.48.8 Number of Failed Preparations for Outgoing UMTS-to-LTE PS Handovers Due to Different Causes
Issue 01 (2013-05-04)
2516
Counters
Counter ID 73423414 Counter Name VS.U2LTEHO.FailRelocPre pOutPS.NoResAvail Counter Description Number of Failed Preparations for Outgoing UMTS-to-LTE PS Handovers for Cell (No Resource Available) Number of Failed Preparations for Outgoing UMTS-to-LTE PS Handovers for Cell (Relocation Failure in Target CN/RNC or Target System) Number of Failed Preparations for Outgoing UMTS-to-LTE PS Handovers for Cell (Relocation not supported in Target RNC or Target system) Number of Failed Preparations for Outgoing UMTS-to-LTE PS Handovers for Cell (Traffic Load In The Target Cell Higher Than In The Source Cell) Number of Failed Preparations for Outgoing UMTS-to-LTE PS Handovers for Cell (Unknown Target RNC) Number of Failed Preparations for Outgoing UMTS-to-LTE PS Handovers for Cell (TRELOCalloc expiry)
73423415
VS.U2LTEHO.FailRelocPre pOutPS.TgtFail
73423416
VS.U2LTEHO.FailRelocPre pOutPS.ReloUnSupp
73423417
VS.U2LTEHO.FailRelocPre pOutPS.TgtHighLoad
73423418
VS.U2LTEHO.FailRelocPre pOutPS.UnKnowRNC
73423420
VS.U2LTEHO.FailRelocPre pOutPS.TAlExp
Description
These counters indicate the failure of preparations for a UMTS-to-LTE PS handover due to different causes at the CN or LTE. For the detailed cause, see section 9.2.1.4 in 3GPP TS 25.413. If the value of this counter is high, check the detailed cause at the CN or LTE.
Issue 01 (2013-05-04)
2517
Measurement point
The measurement is triggered at point A shown in the figure, when the RNC receives from the CN a RELOCATION PREPARATION FAILURE message after sending the CN a RELOCATION REQUIRED message during the outgoing UMTS-to-LTE PS handover. In this case, the corresponding counter is measured in the best cell that the UE camps on under the SRNC based on the failure cause. Figure 1-1109 PS UMTS to LTE outgoing handover Prepareation Procedure(failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.U2LTEHO.FailRelocPre pOutPS.NoResAvail Feature ID WRFD-140218 WRFD-150220 WRFD-150217 Feature Name Service-Based PS Handover from UMTS to LTE Coverage Based PS Handover from UMTS to LTE Load Based PS Handover from UMTS to LTE
Counter Name VS.U2LTEHO.FailRelocPre pOutPS.TgtFail
Feature Name Service-Based PS Handover from UMTS to LTE Coverage Based PS Handover from UMTS to LTE Load Based PS Handover from UMTS to LTE
VS.U2LTEHO.FailRelocPre pOutPS.ReloUnSupp
WRFD-140218 WRFD-150220 WRFD-150217
Service-Based PS Handover from UMTS to LTE Coverage Based PS Handover from UMTS to LTE Load Based PS Handover from UMTS to LTE
VS.U2LTEHO.FailRelocPre pOutPS.TgtHighLoad
WRFD-140218 WRFD-150220 WRFD-150217
VS.U2LTEHO.FailRelocPre pOutPS.UnKnowRNC
WRFD-140218 WRFD-150220 WRFD-150217
VS.U2LTEHO.FailRelocPre pOutPS.TAlExp
WRFD-140218 WRFD-150220 WRFD-150217
1.12.48.9 Number of Redirection to LTE Through RRC Connection Release for Cell
Issue 01 (2013-05-04)
2519
Counters
Counter ID 73423419 Counter Name VS.U2LTEHO.RRCRelease .Service Counter Description Number of Service-Based Redirection to LTE Through RRC Connection Release for Cell Number of Coverage-based UMTS to LTE PS Redirections for Cell Number of Load-based UMTS to LTE PS Redirections for Cell
73425855
VS.U2LTEHO.RRCRelease .Coverage VS.U2LTEHO.RRCRelease .Load
73425859
Description
These counters provide the number RRC CONNECTION RELEASE messages sent by the RNC to instruct the UE in the best cell to redirect to the LTE network due to different causes (services, coverage, or load). These counters include the number of measurement-based redirections and blind redirections.
Measurement point
The measurement is triggered at point A shown in the figure, when the RNC sends an RRC Connection Release message to the UE, instructing the UE to redirect to the LTE cell. In this case, these counters are measured in the best cell under the SRNC. Figure 1-1110 UMTS Redirection to LTE Through RRC Connection Release Procedure
Issue 01 (2013-05-04)
2520
Formula
None
Unit
None
Related Features
Counter Name VS.U2LTEHO.RRCRelease .Service VS.U2LTEHO.RRCRelease .Coverage VS.U2LTEHO.RRCRelease .Load Feature ID WRFD-020129 Feature Name Service-Based PS Service Redirection from UMTS to LTE Coverage Based PS Redirection from UMTS to LTE Load Based PS Redirection from UMTS to LTE
WRFD-150219
WRFD-150216
1.12.48.10 Number of Preparation Attempts for Outgoing Coverage-triggered UMTS-to-LTE PS Handovers Counters
Counter ID 73425853 Counter Name VS.U2LHO.AttRelocPrepO utPS.Coverage Counter Description Number of Preparation Attempts for Outgoing Coverage-triggered UMTSto-LTE PS Handovers for Cell
Description
This counter provides the number of preparation attempts for outgoing U2L PS handovers triggered by poor coverage in the best cell where the UE camps. U2L refers to handovers from the UMTS network to the LTE network.
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC sends a RELOCATION REQUIRED message to the CN. This counter is measured in the best cell under the SRNC where the UE is currently served.
Formula
None
Unit
None
Related Features
Counter Name VS.U2LHO.AttRelocPrepO utPS.Coverage Feature ID WRFD-150220 Feature Name Coverage Based PS Handover from UMTS to LTE
1.12.48.11 Number of Successful Preparations for Outgoing Coverage-triggered UMTS-to-LTE PS Handovers
Issue 01 (2013-05-04)
2522
Counters
Counter ID 73425854 Counter Name VS.U2LHO.SuccRelocPrep OutPS.Coverage Counter Description Number of Successful Preparations for Outgoing Coverage-triggered UMTSto-LTE PS Handovers for Cell
Description
This counter provides the number of successful preparations for outgoing U2L PS handovers triggered by poor coverage in the best cell where the UE camps. U2L refers to handovers from the UMTS network to the LTE network.
Measurement point
The measurement is triggered at point B shown in the following figure when the RNC receives a RELOCATION COMMAND message from the CN. This counter is measured in the best cell under the SRNC where the UE is currently served. Figure 1-1112 Normal PS UMTS to LTE outgoing handover Procedure
Formula
None
Unit
None
Related Features
Counter Name VS.U2LHO.SuccRelocPrep OutPS.Coverage Feature ID WRFD-150220 Feature Name Coverage Based PS Handover from UMTS to LTE
1.12.48.12 Number of UMTS to LTE Blind Redirections Through RRC Connection Release for Cell Counters
Counter ID 73425856 Counter Name VS.U2LTEHO.RRCRelease .Coverage.EmergBlind Counter Description Number of Coverage-based UMTS to LTE PS Emergency Blind Redirections for Cell Number of Load-based UMTS to LTE PS Blind Redirections for Cell Number of Service-based UMTS to LTE PS Blind Redirections for Cell
73425860
VS.U2LTEHO.RRCRelease .Load.Blind VS.U2LTEHO.RRCRelease .Sevice.Blind
73425819
Description
These counters provide the number of RRC CONNECTION RELEASE messages sent by the RNC to instruct the UE to blindly redirect to the LTE cell due to different causes (service, coverage, or load) in the best UMTS cell where the UE camps on.
Measurement point
The measurement is triggered at point A shown in Figure 1, when the RNC sends an RRC CONNECTION RELEASE message to the UE due to different causes (service, coverage, or load), instructing the UE to blindly redirect to the LTE cell. These counters are measured in the best cell under the SRNC where the UE is served.
Issue 01 (2013-05-04)
2524
Figure 1-1113 UMTS Redirection to LTE Through RRC Connection Release Procedure
Formula
None
Unit
None
Related Features
Counter Name VS.U2LTEHO.RRCRelease .Coverage.EmergBlind VS.U2LTEHO.RRCRelease .Load.Blind VS.U2LTEHO.RRCRelease .Sevice.Blind Feature ID WRFD-150219 Feature Name Coverage Based PS Redirection from UMTS to LTE Load Based PS Redirection from UMTS to LTE Service-Based PS Handover from UMTS to LTE
WRFD-150216 WRFD-140218
Issue 01 (2013-05-04)
2525
1.12.49 URA Update Measurement per cell(URAUPDATE.Cell)

Overview
A UE in the URA_PCH state may send a URA UPDATE message to the RNC for different causes, such as "change of URA" and "periodic URA update." This function subset is used to assess the URA update procedure by measuring the number of periodically URA update attempts, number of successful periodically URA updates, number of URA update attempts caused by URA change, and number of successful URA updates caused by URA change.
Counters
Counter ID 67180452 Counter Name VS.AttURAUpd.Pr d Counter Description Number of URA Updates Due to Periodic URA Update for Cell Number of URA Updates Due to Change of URA for Cell Number of Successful URA Updates Due to Periodic URA Update for Cell Number of Successful URA Updates Due to Change of URA for Cell Original Release V900R012
67180451
VS.AttURAUpd.C hg
V900R012
67180454
VS.SuccURAUpd.P rd
67180453
VS.SuccURAUpd. Chg
None
1.12.49.1 Number of URA Updates due to Periodic URA Update Counters

Counter ID 67180452 Counter Name VS.AttURAUpd.Prd Counter Description Number of URA Updates Due to Periodic URA Update for Cell
Issue 01 (2013-05-04)
2526
Description
This measurement item provides the number of URA UPDATE messages with the cause value of "periodic URA update" received by the SRNC in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the SRNC receives a URA UPDATE message with the cause value of "periodic URA update" from an UE and the UE is not involved in the RRC connection release procedure. In this case, the RNC measures the item in the cell selected by the UE during the URA update procedure. Figure 1-1114 URA update procedure (successful operation)
Formula
None
Unit
None
Issue 01 (2013-05-04)
2527
Related Features
Counter Name VS.AttURAUpd.Prd Feature ID WRFD-010202 WRFD-010901 WRFD-010902 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Intra RNC URA Update Inter RNC URA Update
1.12.49.2 Number of URA Updates due to Change of URA Counters

Counter ID 67180451 Counter Name VS.AttURAUpd.Chg Counter Description Number of URA Updates Due to Change of URA for Cell
Description
This measurement item provides the number of URA UPDATE messages with the cause value of "change of URA" received by the SRNC.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a URA UPDATE message with the cause value of "change of URA" from an UE and the UE is not involved in the RRC connection release procedure. In this case, the RNC measures the item in the cell selected by the UE during the URA update procedure.
Issue 01 (2013-05-04)
2528
Figure 1-1115 URA update procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.AttURAUpd.Chg Feature ID WRFD-010202 WRFD-010901 WRFD-010902 Feature Name UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) Intra RNC URA Update Inter RNC URA Update
1.12.49.3 Number of Successful URA Updates due to Periodic URA Update
Issue 01 (2013-05-04)
2529
Counters
Counter ID 67180454 Counter Name VS.SuccURAUpd.Prd Counter Description Number of Successful URA Updates Due to Periodic URA Update for Cell
Description
This measurement item provides the number of URA UPDATE CONFIRM messages sent from the RNC to the UE after the RNC receives the URA UPDATE message with the cause value of "periodic URA update".
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC responds with a URA UPDATE CONFIRM message after receiving the URA UPDATE message with the cause value of "periodic URA update" from the UE. In this case, the RNC measures the item in the cell that the UE camps on after the URA update. Figure 1-1116 URA update procedure (successful operation)
Formula
None
Issue 01 (2013-05-04)
2530
Unit
None
Related Features
Counter Name VS.SuccURAUpd.Prd Feature ID WRFD-010901 WRFD-010902 WRFD-010202 Feature Name Intra RNC URA Update Inter RNC URA Update UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.49.4 Number of Successful URA Updates due to Change of URA Counters

Counter ID 67180453 Counter Name VS.SuccURAUpd.Chg Counter Description Number of Successful URA Updates Due to Change of URA for Cell
Description
This measurement item provides the number of URA UPDATE CONFIRM messages sent from the RNC to the UE after the RNC receives the URA UPDATE message with the cause value of "change of URA".
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC responds with a URA UPDATE CONFIRM message after receiving the URA UPDATE message with the cause value of "change of URA" from the UE. In this case, the RNC measures the item in the cell that the UE camps on after the URA update.
Issue 01 (2013-05-04)
2531
Figure 1-1117 URA update procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SuccURAUpd.Chg Feature ID WRFD-010901 WRFD-010902 WRFD-010202 Feature Name Intra RNC URA Update Inter RNC URA Update UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
1.12.50 WLAN Measurement per cell(WLAN.Cell)

Overview
WLAN Measurement per cell
Counters
Counter ID 73426126 Counter Name VS.WlanDistribute .attempt VS.WlanDistribute .Fail Counter Description Number of Wi-Fi Access Attempts for Cell Number of Wi-Fi Access Failures for Cell Original Release V900R015
73426127
V900R015
None
1.12.50.1 Number of Wi-Fi Access Attempts for Cell Counters

Counter ID 73426126 Counter Name VS.WlanDistribute.attempt Counter Description Number of Wi-Fi Access Attempts for Cell
Description
This counter provides the number of Wi-Fi access attempts in the best cell where the UE in question camps.
Measurement point
As shown by point A in figure 1, the RNC sends an ApDetect_Response message to the UE, and then this counter is increased by one in the best cell where the UE camps.
Issue 01 (2013-05-04)
2533
Figure 1-1118 WIFI detect in cell
As shown by point A in figure 2, the RNC sends the UE a WiFi_Register_Response message where "SSID List" is not set to NULL and "AccessFlag" is set to 1. Then, this counter is increased by one in the best cell where the UE camps. Figure 1-1119 WIFI regist in cell
Issue 01 (2013-05-04)
2534
Formula
None
Unit
None
Related Features
None
1.12.50.2 Number of Wi-Fi Access Failures for Cell Counters

Counter ID 73426127 Counter Name VS.WlanDistribute.Fail Counter Description Number of Wi-Fi Access Failures for Cell
Description
This counter provides the number of Wi-Fi access failures in the best cell where the UE in question camps.
Measurement point
As shown by point B in the following figure, the RNC receives from the UE a Wi-Fi access failure report, and then this counter is increased by one in the best cell where the UE camps. This cell must be under the SRNC to which the UE belongs. Figure 1-1120 WIFI access fail in cell
Issue 01 (2013-05-04)
2535
Formula
None
Unit
None
Related Features
None
1.13 Measurement between a cell and a neighbour interRAT cell Performance(UCELL_GCELL)

Overview
The measurement object type IRATHO.GCELL is used to measure the handovers between interRAT adjacent cells.
FunctionSubSets
FunctionSubSet IRATHO.Gcell FunctionSubSet Name Measurement between a cell and a intRAT cell
1.13.1 Measurement between a cell and a intRAT cell (IRATHO.Gcell)

Overview
This function subset is used to measure inter-RAT handovers between neighboring cells. For details about inter-RAT handover procedure, refer to the following sections in "RNC Performance Measurement (RNC)" : "CS Domain Inter-RAT Handover Measurement"; "PS Domain Inter-RAT Handover Measurement". The two cells involved in the inter-RAT handover are called source cell and target cell. They belong to different communication systems. For the source cell, the RNC measures each of the following items in the relationship of "source cell - target cell". Suppose the UE camps on CELL1 before an inter-RAT handover. After inter-RAT handover, the UE camps on CELL2. Then CELL1 is the source cell and CELL2 is the target cell. This indicates one inter-RAT handover between CELL1 and CELL2.
The RNC takes statistics for source cells that belong to the WCDMA system. Note: 1. Using scenes of this kind of items are usually described as follows: evaluate neighboring cell priority rationality, provide evidence for deleting redundant neighboring cell, which is generally used for network optimization. 2. The measurement of this kind of item needs to be started through the M2000. The measurement is not started by default.
Counters
Counter ID 67183495 Counter Name VS.IRATHO.AttO utCS.GCell Counter Description Number of CS InterRAT Outgoing Handover Attempts Between Neighboring Cells Number of Successful CS InterRAT Outgoing Handovers Between Neighboring Cells Number of Failed CS Inter-RAT HandoversBetween Neighboring Cells Due to UE Fault Number of PS InterRAT Outgoing Handover Attempts Between Neighboring Cells Number of Successful PS InterRAT Outgoing Handovers Between Neighboring Cells Number of Failed PS Inter-RAT Handovers Between Neighboring Cells Due to UE Fault Original Release Earlier than V900R011
67183496
VS.IRATHO.Succ OutCS.GCell
67189907
VS.IRATHO.FailO utCS.UEFail.GCell
67183497
VS.IRATHO.AttO utPSUTRAN.GCell
67183498
VS.IRATHO.Succ OutPSUTRAN.GC ell
67189908
VS.IRATHO.FaiO utPSUTRAN.UEFa il.GCell
Issue 01 (2013-05-04)
2537
Counter ID 73394034
Counter Name VS.IRATHO.AttRe locPrepOutCS.GCe ll
Counter Description Number of CS Outgoing Inter-RAT Handover Preparation Attempts Number of CS Outgoing Inter-RAT Handover Preparation Attempts (Directed retry) Number of Failed CS Outgoing Inter-RAT Handover Preparations (Relocation desirable for radio reasons) Number of Successful CS Outgoing Inter-RAT Handover Preparations Number of Failed CS Outgoing Inter-RAT Handover Preparations (TRELOCalloc expiry) Number of Failed CS Outgoing Inter-RAT Handover Preparations (Relocation Failure in Target CN/RNC or Target System)
73394035
VS.IRATHO.AttRe locPrepOutCS.DR. GCell
V900R012
73394036
VS.IRATHO.AttRe locPrepOutCS.RF. GCell
V900R012
73394037
VS.IRATHO.Succ RelocPrepOutCS.G Cell
V900R012
73394038
VS.IRATHO.FailR elocPrepOutCS.TA lExp.GCell
V900R012
73394039
VS.IRATHO.FailR elocPrepOutCS.Tgt Fail.GCell
V900R012
None
1.13.1.1 Number of CS Inter-RAT Outgoing Handover Attempts Between Neighboring Cells
Issue 01 (2013-05-04)
2538
Counters
Counter ID 67183495 Counter Name VS.IRATHO.AttOutCS.GC ell Counter Description Number of CS Inter-RAT Outgoing Handover Attempts Between Neighboring Cells
Description
This counter provides the number of attempts for CS outgoing inter-RAT handovers according to the neighbor relationships.
Measurement point
The measurement is triggered at point C, as shown in the figure. When the RNC sends a HANDOVER FROM UTRAN COMMAND message to the UE in the CS domain inter-RAT handover procedure, the RNC measures this item for each pair of source and target cells. Here, the best cell that the UE camps on before the inter-RAT handover is the source cell, and the cell that the UE wants to hand over to is the target cell. Figure 1-1121 CS inter-RAT outgoing handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttOutCS.GC ell Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.13.1.2 Number of Successful CS Inter-RAT Outgoing Handovers Between Neighboring Cells Counters
Counter ID 67183496 Counter Name VS.IRATHO.SuccOutCS.G Cell Counter Description Number of Successful CS Inter-RAT Outgoing Handovers Between Neighboring Cells
Description
This measurement item provides the number of successful CS inter-RAT outgoing handovers between neighboring cells.
Measurement point
The measurement is triggered at point D, as shown in the figure. After the RNC sends a HANDOVER FROM UTRAN COMMAND message during the CS domain inter-RAT handover, it receives from the CS domain an IU RELEASE COMMAND message with the cause of "Successful Relocation", "Normal Release" or "Network Optimization". At this time, the RNC measures this item for each pair of source and target cells. Here, the best cell that the UE camps on before the inter-RAT handover is the source cell, and the cell that the UE wants to hand over to is the target cell.
Issue 01 (2013-05-04)
2540
Figure 1-1122 CS inter-RAT outgoing handover procedure
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccOutCS.G Cell Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.13.1.3 Number of Failed CS Inter-RAT Outgoing Handovers Between Neighboring Cells
Issue 01 (2013-05-04)
2541
Counters
Counter ID 67189907 Counter Name VS.IRATHO.FailOutCS.UE Fail.GCell Counter Description Number of Failed CS InterRAT HandoversBetween Neighboring Cells Due to UE Fault
Description
This measurement item provides the number of unsuccessful CS inter-RAT outgoing handovers between neighboring cells.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives a HANDOVER FROM UTRAN FAILURE message from an UE, the RNC measure this item for each pair of source and target cells. Here, the best cell that the UE camps on before the interRAT handover is the source cell, and the cell that the UE wants to hand over to is the target cell. Figure 1-1123 CS inter-RAT outgoing handover procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailOutCS.UE Fail.GCell Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.13.1.4 Number of PS Inter-RAT Outgoing Handover Attempts Between Neighboring Cells Counters
Counter ID 67183497 Counter Name VS.IRATHO.AttOutPSUTR AN.GCell Counter Description Number of PS Inter-RAT Outgoing Handover Attempts Between Neighboring Cells
Description
This counter provides the number of attempts for PS outgoing inter-RAT handovers initiated by the RNC according to the neighbor relationships.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends the UE a CELL CHANGE ORDER FROM UTRAN message during the PS inter-RAT handover, it measures this item for each pair of source and target cells. Here, the best cell that the UE camps on before the inter-RAT handover is the source cell, and the cell that the UE wants to hand over to is the target cell.
Issue 01 (2013-05-04)
2543
Figure 1-1124 RNC-originated PS inter-RAT outgoing handover procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttOutPSUTR AN.GCell Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.13.1.5 Number of Successful PS Inter-RAT Outgoing Handovers Between Neighboring Cells
Issue 01 (2013-05-04)
2544
Counters
Counter ID 67183498 Counter Name VS.IRATHO.SuccOutPSUT RAN.GCell Counter Description Number of Successful PS Inter-RAT Outgoing Handovers Between Neighboring Cells
Description
This measurement item provides the number of successful PS inter-RAT outgoing handovers between neighboring cells.
Measurement point
The measurement is triggered at point C, as shown in the figure. After the RNC sends a CELL CHANGE ORDER FROM UTRAN message during the PS inter-RAT handover procedure, it receives from the CN an IU RELEASE COMMAND message with the cause of "Successful Relocation", "Normal Release" or "Network Optimization". At this time, the RNC measures this item for each pair of source and target cells. Here, the best cell that the UE camps on before the inter-RAT handover is the source cell, and the cell that the UE wants to hand over to is the target cell. Figure 1-1125 RNC-originated PS inter-RAT outgoing handover procedure (successful operation)
Issue 01 (2013-05-04)
2545
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccOutPSUT RAN.GCell Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.13.1.6 Number of Failed PS Inter-RAT Outgoing Handovers Between Neighboring Cells Counters
Counter ID 67189908 Counter Name VS.IRATHO.FaiOutPSUTR AN.UEFail.GCell Counter Description Number of Failed PS InterRAT Handovers Between Neighboring Cells Due to UE Fault
Description
This measurement item provides the number of unsuccessful PS inter-RAT outgoing handovers between neighboring cells.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends a CELL CHANGE ORDER FROM UTRAN message to an UE, it receives a CELL CHANGE ORDER FROM UTRAN FAILURE message from the UE. At this time, the RNC measures this item for each pair of source and target cells. Here, the best cell that the UE camps on before the interRAT handover is the source cell, and the cell that the UE wants to hand over to is the target cell.
Issue 01 (2013-05-04)
2546
Figure 1-1126 PS inter-RAT outgoing handover procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FaiOutPSUTR AN.UEFail.GCell Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.13.1.7 Number of CS Outgoing Inter-RAT Handover Preparation Attempts Between Neighboring Cells
Issue 01 (2013-05-04)
2547
Counters
Counter ID 73394034 Counter Name VS.IRATHO.AttRelocPrep OutCS.GCell Counter Description Number of CS Outgoing Inter-RAT Handover Preparation Attempts
Description
This counter provides the number of CS outgoing inter-RAT handover preparation attempts in the source cell and the target cell.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the CN a RELOCATION REQUIRED message during the CS outgoing inter-RAT handover, the RNC measures these items for each pair of source and target cells according to different causes. Here, the best cell that the UE camps on before the inter-RAT handover is the source cell, and the cell that the UE wants to hand over to is the target cell. Figure 1-1127 Normal CS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttRelocPrep OutCS.GCell Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.13.1.8 Number of CS Outgoing Inter-RAT Handover Preparation Attempts According to Different Causes Between Neighboring Cells Counters
Counter ID 73394035 Counter Name VS.IRATHO.AttRelocPrep OutCS.DR.GCell Counter Description Number of CS Outgoing Inter-RAT Handover Preparation Attempts (Directed retry) Number of Failed CS Outgoing Inter-RAT Handover Preparations (Relocation desirable for radio reasons)
73394036
VS.IRATHO.AttRelocPrep OutCS.RF.GCell
Description
These counters provide the number of CS outgoing inter-RAT handover preparation attempts in the source cell and the target cell according to the cause values.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the CN a RELOCATION REQUIRED message during the CS outgoing inter-RAT handover, the RNC measures these items for each pair of source and target cells according to different causes. Here, the best cell that the UE camps on before the inter-RAT handover is the source cell, and the cell that the UE wants to hand over to is the target cell.
Issue 01 (2013-05-04)
2549
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.AttRelocPrep OutCS.DR.GCell Feature ID WRFD-02040002 WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter System Direct Retry Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load VS.IRATHO.AttRelocPrep OutCS.RF.GCell WRFD-020303 Inter-RAT Handover Based on Coverage
Issue 01 (2013-05-04)
2550
1.13.1.9 Number of Successful CS Outgoing Inter-RAT Handover Preparations Between Neighboring Cells Counters
Counter ID 73394037 Counter Name VS.IRATHO.SuccRelocPre pOutCS.GCell Counter Description Number of Successful CS Outgoing Inter-RAT Handover Preparations
Description
This counter provides the number of Successful CS outgoing inter-RAT handover preparations.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives from the CN a RELOCATION COMMAND message during the CS outgoing inter-RAT handover. In this case, the RNC measures this item for each pair of source and target cells. Here, the best cell that the UE camps on before the inter-RAT handover is the source cell, and the cell that the UE wants to hand over to is the target cell. Figure 1-1129 Normal CS outgoing inter-RAT handover
Issue 01 (2013-05-04)
2551
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.SuccRelocPre pOutCS.GCell Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.13.1.10 Number of Failed CS Outgoing Inter-RAT Handover Preparations According to Different Causes Between Neighboring Cells Counters
Counter ID 73394038 Counter Name VS.IRATHO.FailRelocPrep OutCS.TAlExp.GCell Counter Description Number of Failed CS Outgoing Inter-RAT Handover Preparations (TRELOCalloc expiry) Number of Failed CS Outgoing Inter-RAT Handover Preparations (Relocation Failure in Target CN/RNC or Target System)
73394039
VS.IRATHO.FailRelocPrep OutCS.TgtFail.GCell
Description
This counter provides the number of failed CS outgoing inter-RAT handover preparations according to different causes.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from the CN a RELOCATION PREPARATION FAILURE message after it sends the CN a RELOCATION REQUIRED message during the CS outgoing inter-RAT handover. In this case, the RNC measures this item for each pair of source and target cells according to different causes.
Here, the best cell that the UE camps on before the inter-RAT handover is the source cell, and the cell that the UE wants to hand over to is the target cell. Figure 1-1130 SRNC relocation preparation procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.IRATHO.FailRelocPrep OutCS.TAlExp.GCell Feature ID WRFD-020303 WRFD-020305 WRFD-020306 Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
Issue 01 (2013-05-04)
2553
Counter Name VS.IRATHO.FailRelocPrep OutCS.TgtFail.GCell
Feature Name Inter-RAT Handover Based on Coverage Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load
1.14 Measurement between a cell and a neighbour UMTS cell(UCELL_NCELL)

Overview
The measurement object type of Neighboring Cell Measurement (CELL.NCELL) is used to measure the handovers between neighboring cells.
FunctionSubSets
FunctionSubSet CELL.Ncell FunctionSubSet Name Measurement between a cell and a UMTS cell
1.14.1 Measurement between a cell and a UMTS cell(CELL.Ncell)

Overview
This function subset measures handover procedures between neighboring cells. These procedures include soft handover and hard handover procedures. For details about these procedures, see function subsets SHO.RNC and HHO.RNC in section "Measurement of RNC Performance (RNC)". The two cells involved in neighboring cell measurement are called source cell and target cell. For the source cell, the RNC measures each of the following items in the relationship of "source cell - target cell". If there are several target cells, the RNC measures the items in "source cell target cell n". For example, the UE is in CELL1 before an inter-RAT handover, then moves to CELL2 and CELL3 after soft handover. In this scenario, CELL1 is the source cell, CELL2 and CELL3 are the target cells. You can measure the soft handovers as follows: one soft handover for "CELL1CELL2" and another for "CELL1-CELL3". Neighboring cell measurement is used to measure only the items with the source cell under a Source Radio Network Controller (SRNC) and the target cell under an SRNC or a Target Radio Network Controller (TRNC). Note:
1. Using scenes of this kind of items are usually described as follows: evaluate neighboring cell priority rationality, provide evidence for deleting redundant neighboring cell, which is generally used for network optimization. 2. The measurement of this kind of item needs to be started through the M2000. The measurement is not started by default. 3. In BSC6900 versions, there is no restriction on the number of measurement objects.
Counters
Counter ID 67189909 Counter Name VS.SHO.SuccASU. NCell Counter Description Number of Successful Soft Handovers Between Neighboring Cells Number of Soft Handover Attempts Between Neighboring Cells Number of Failed Soft Handovers Between Neighboring Cells Due to Waiting Active Set Update Response Timeout Number of Hard Handovers Attempts Between Neighboring Cells Number of Successful Hard Handovers Between Neighboring Cells Number of Failed Hard Handover Between Neighboring Cells Due to Timeout Number of RL Addition Attempts in Soft Handover Between Neighboring Cells Original Release Earlier than V900R011
67189910
VS.SHO.AttASU.N Cell
67189911
VS.SHO.FailASU. NoReply.NCell
67183489
VS.HHO.AttOut.N Cell
67183490
VS.HHO.SuccOut. NCell
67189912
VS.HHO.FailOut.N oReply.NCell
67183491
VS.SHO.AddRLAt t.NCell
Issue 01 (2013-05-04)
2555
Counter ID 67183492
Counter Name VS.SHO.AddRLSu cc.NCell
Counter Description Number of Successful RL Additions in Soft Handover Between Neighboring Cells Number of RL Deletion Attempts in Soft Handover Between Neighboring Cells Number of Successful RL Deletions in Soft Handover Between Neighboring Cells Number of HSDSCH-toHSDSCH hard Handover Requests Without Channel Change Between Neighboring Cells Number of Successful HSDSCH-toHSDSCH hard Handovers Without Channel Change Between Neighboring Cells Number of HSDPA Serving Cell Change Attempts Between Neighboring Cells Number of Successful HSDPA Serving Cell Changes Between Neighboring Cells Number of CS Outgoing IntraNodeB Inter-Cell Hard Handover Attempts
67183493
VS.SHO.DelRLAtt. NCell
67183494
VS.SHO.DelRLSuc c.NCell
67190708
VS.HSDPA.HHO. NoChR.Att.NCell
67190709
VS.HSDPA.HHO. NoChR.Succ.NCell
67190710
VS.HSDPA.ServCe llChg.Att.NCell
67190711
VS.HSDPA.ServCe llChg.Succ.NCell
73393988
VS.HHO.AttOutIn traNodeB.CS.NCell
V900R012
Issue 01 (2013-05-04)
2556
Counter ID 73393989
Counter Name VS.HHO.SuccOutI ntraNodeB.CS.NCe ll
Counter Description Number of Successful CS Outgoing IntraNodeB Inter-Cell Hard Handovers Number of Failed CS Outgoing IntraNodeB Inter-Cell Hard Handovers (UE No Response) Number of Failed CS Outgoing IntraNodeB Inter-Cell Hard Handovers (Physical Channel Failure) Number of PS Outgoing IntraNodeB Inter-Cell Hard Handover Attempts Number of Successful PS Outgoing IntraNodeB Inter-Cell Hard Handovers Number of Failed PS Outgoing IntraNodeB Inter-Cell Hard Handovers (UE No Response) Number of Failed PS Outgoing IntraNodeB Inter-Cell Hard Handovers (Physical Channel Failure) Number of CS Outgoing Intra-RNC Inter-NodeB InterCell Hard Handover Attempts
73393990
VS.HHO.FailOutIn traNodeB.NoReply. CS.NCell
V900R012
73393991
VS.HHO.FailOutIn traNodeB.PhyChF ail.CS.NCell
V900R012
73393992
VS.HHO.AttOutIn traNodeB.PS.NCell
V900R012
73393993
VS.HHO.SuccOutI ntraNodeB.PS.NCe ll
V900R012
73393994
VS.HHO.FailOutIn traNodeB.NoReply. PS.NCell
V900R012
73393995
VS.HHO.FailOutIn traNodeB.PhyChF ail.PS.NCell
V900R012
73393996
VS.HHO.AttOutIn terNodeBIntraRN C.CS.NCell
V900R012
Issue 01 (2013-05-04)
2557
Counter ID 73393997
Counter Name VS.HHO.SuccOutI nterNodeBIntraRN C.CS.NCell
Counter Description Number of Successful CS Outgoing Intra-RNC Inter-NodeB InterCell Hard Handovers Number of Failed CS Outgoing Intra-RNC Inter-NodeB InterCell Hard Handovers (UE No Response) Number of Failed CS Outgoing Intra-RNC Inter-NodeB InterCell Hard Handovers (Physical Channel Failure) Number of PS Outgoing Intra-RNC Inter-NodeB InterCell Hard Handover Attempts Number of Successful PS Outgoing Intra-RNC Inter-NodeB InterCell Hard Handovers Number of Failed PS Outgoing Intra-RNC Inter-NodeB InterCell Hard Handovers (UE No Response) Number of Failed PS Outgoing Intra-RNC Inter-NodeB InterCell Hard Handovers (Physical Channel Failure) Number of CS Outgoing Inter-RNC Inter-Cell Hard Handover Attempts
73393998
VS.HHO.FailOutIn terNodeBIntraRN C.NoReply.CS.NCe ll VS.HHO.FailOutIn terNodeBIntraRN C.PhyChFail.CS.N Cell
V900R012
73393999
V900R012
73394000
VS.HHO.AttOutIn terNodeBIntraRN C.PS.NCell
V900R012
73394001
VS.HHO.SuccOutI nterNodeBIntraRN C.PS.NCell
V900R012
73394002
VS.HHO.FailOutIn terNodeBIntraRN C.NoReply.PS.NCe ll VS.HHO.FailOutIn terNodeBIntraRN C.PhyChFail.PS.N Cell
V900R012
73394003
V900R012
73394004
VS.HHO.AttOutIn terRNCIur.CS.NC ell
V900R012
Issue 01 (2013-05-04)
2558
Counter ID 73394005
Counter Name VS.HHO.SuccOutI nterRNCIur.CS.N Cell
Counter Description Number of Successful CS Outgoing Inter-RNC Inter-Cell Hard Handovers Number of Failed CS Outgoing Inter-RNC Inter-Cell Hard Handovers (Configuration Unsupported) Number of Failed CS Outgoing Inter-RNC Inter-Cell Hard Handovers (Physical Channel Failure) Number of PS Outgoing Inter-RNC Inter-Cell Hard Handover Attempts Number of Successful PS Outgoing Inter-RNC Inter-Cell Hard Handovers Number of Failed PS Outgoing Inter-RNC Inter-Cell Hard Handovers (Configuration Unsupported) Number of Failed PS Outgoing Inter-RNC Inter-Cell Hard Handovers (Physical Channel Failure) Number of Outgoing UE-Involved SRNS Relocation Executions Triggered by CS HHO
73394006
VS.HHO.FailOutIn terRNCIur.CfgUns up.CS.NCell
V900R012
73394007
VS.HHO.FailOutIn terRNCIur.PhyCh Fail.CS.NCell
V900R012
73394008
VS.HHO.AttOutIn terRNCIur.PS.NCe ll VS.HHO.SuccOutI nterRNCIur.PS.N Cell
V900R012
73394009
V900R012
73394010
VS.HHO.FailOutIn terRNCIur.CfgUns up.PS.NCell
V900R012
73394011
VS.HHO.FailOutIn terRNCIur.PhyCh Fail.PS.NCell
V900R012
73394026
VS.HHO.AttOutIn terRNCCN.CS.NC ell
V900R012
Issue 01 (2013-05-04)
2559
Counter ID 73394027
Counter Name VS.HHO.SuccOutI nterRNCCN.CS.N Cell
Counter Description Number of Successful Outgoing UE-Involved SRNS Relocations Triggered by CS HHO Number of Failed Outgoing UEInvolved SRNS Relocation Preparations Triggered by CS HHO (TRELOCalloc Expiry) Number of Failed Outgoing UEInvolved SRNS Relocation Preparations Triggered by CS HHO (Relocation Failure in Target CN/ RNC or Target System) Number of Outgoing UE-Involved SRNS Relocation Executions Triggered by PS HHO Number of Successful Outgoing UE-Involved SRNS Relocation Executions Triggered by PS HHO
73394028
VS.HHO.FailReloc PrepOutInterRNC CN.TExp.CS.NCell
V900R012
73394029
VS.HHO.FailReloc PrepOutInterRNC CN.TgtF.CS.NCell
V900R012
73394030
VS.HHO.AttOutIn terRNCCN.PS.NCe ll
V900R012
73394031
VS.HHO.SuccOutI nterRNCCN.PS.N Cell
V900R012
Issue 01 (2013-05-04)
2560
Counter ID 73394032
Counter Name VS.HHO.FailReloc PrepOutInterRNC CN.TExp.PS.NCell
Counter Description Number of Failed Outgoing UEInvolved SRNS Relocation Preparations Triggered by PS HHO (TRELOCalloc Expiry) Number of Failed Outgoing UEInvolved SRNS Relocation Preparations Triggered by PS HHO (Relocation Failure in Target CN/ RNC or Target System)
73394033
VS.HHO.FailReloc PrepOutInterRNC CN.TgtF.PS.NCell
V900R012
None
1.14.1.1 Number of Successful Soft Handovers Between Neighboring Cells Counters

Counter ID 67189909 Counter Name VS.SHO.SuccASU.NCell Counter Description Number of Successful Soft Handovers Between Neighboring Cells
Description
This measurement item provides the number of successful soft handovers between neighboring cells.
Measurement point
The measurement is triggered at point C, as shown in the figure. When the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during a soft handover, the RNC measures this item for each pair of source and target cells. Here, the source cells refer to the best
cell that the UE camps on before the soft handover. The target cells refer to the cells whose RLs are added or the cell whose RL is released in this soft handover. Figure 1-1131 Soft handover procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.SuccASU.NCell Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.14.1.2 Number of Soft Handover Attempts Between Neighboring Cells
Issue 01 (2013-05-04)
2562
Counters
Counter ID 67189910 Counter Name VS.SHO.AttASU.NCell Counter Description Number of Soft Handover Attempts Between Neighboring Cells
Description
This measurement item provides the number of soft handover attempts between neighboring cells.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends an ACTIVE SET UPDATE message to the UE during a soft handover, the RNC measures this item for each pair of source and target cells. Here, the source cells refer to the best cell that the UE camps on before the soft handover. The target cells refer to the cells whose RLs are added or the cell whose RL is released in this soft handover. Figure 1-1132 Soft handover procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AttASU.NCell Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.14.1.3 Number of Failed Soft Handovers Between Neighboring Cells Due to No Response from UE Counters
Counter ID 67189911 Counter Name VS.SHO.FailASU.NoReply. NCell Counter Description Number of Failed Soft Handovers Between Neighboring Cells Due to Waiting Active Set Update Response Timeout
Description
This measurement item provides the number of unsuccessful soft handovers between neighboring cells due to no response from the UE.
Measurement point
During a soft handover, after the RNC sends an ACTIVE SET UPDATE message to the UE, it starts the timer to wait for the response from the UE. When the RNC receives no response until the timer expires, it measures this item for each pair of source and target cells. Here, the source cells refer to the best cell that the UE camps on before the soft handover. The target cells refer to the cells whose RLs are added or the cell whose RL is released in this soft handover.
Issue 01 (2013-05-04)
2564
Figure 1-1133 A failed soft handover (timer expiry)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.FailASU.NoReply. NCell Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.14.1.4 Number of Hard Handover Attempts Between Neighboring Cells Counters

Counter ID 67183489 Counter Name VS.HHO.AttOut.NCell Counter Description Number of Hard Handovers Attempts Between Neighboring Cells
Issue 01 (2013-05-04)
2565
Description
This measurement item provides the number of hard handover attempts between neighboring cells.
Measurement point
The measurement is triggered at point B, as shown in the figure. During the hard handover procedure, for example, when the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE, the best cell that the UE camps on before the hard handover is the source cell and the one that the UE camps on after the hard handover is the target cell. Figure 1-1134 Hard handover procedure (successful operation)
Formula
None
Unit
None
Issue 01 (2013-05-04)
2566
Related Features
Counter Name VS.HHO.AttOut.NCell Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.14.1.5 Number of Successful Hard Handovers Between Neighboring Cells Counters

Counter ID 67183490 Counter Name VS.HHO.SuccOut.NCell Counter Description Number of Successful Hard Handovers Between Neighboring Cells
Description
This measurement item provides the number of successful hard handovers between neighboring cells.
Measurement point
The measurement is triggered at point C, as shown in the figure. During the hard handover procedure, for example, when the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the RNC shall measure this item for each pair of source and target cells. Here, the best cell that the UE camps on before the hard handover is source cell and the one that the UE camps on after the hard handover is the target cell.
Issue 01 (2013-05-04)
2567
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccOut.NCell Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.14.1.6 Number of Failed Hard Handovers Between Neighboring Cells Due to No Response from UE
Issue 01 (2013-05-04)
2568
Counters
Counter ID 67189912 Counter Name VS.HHO.FailOut.NoReply. NCell Counter Description Number of Failed Hard Handover Between Neighboring Cells Due to Timeout
Description
This measurement item provides the number of soft handover attempts between neighboring cells.
Measurement point
During a hard handover, for example, when the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE, it starts the timer to wait for the response from the UE. When the RNC receives no response until the timer expires, it measures this item for each pair of source and target cells. Here, the source cells refer to the best cell that the UE camps on before the hard handover. The target cells refer to the cells that the UE camps on after the hard handover. Figure 1-1136 Failed hard handover procedure (timer expiry)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailOut.NoReply. NCell Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.14.1.7 Number of RL Addition Attempts in Soft Handover Between Neighboring Cells Counters
Counter ID 67183491 Counter Name VS.SHO.AddRLAtt.NCell Counter Description Number of RL Addition Attempts in Soft Handover Between Neighboring Cells
Description
This measurement item provides the number of radio link addition attempts in the soft handover between neighboring cells.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends an ACTIVE SET UPDATE message to the UE during the soft handover procedure, the RNC measures this item for each pair of source and target cells if there are radio link additions in this soft handover prodcedure. Here, the source cells refer to the best cell that the UE camps on before the soft handover. The target cells refer to the cells whose RLs are added in this soft handover.
Issue 01 (2013-05-04)
2570
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AddRLAtt.NCell Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.14.1.8 Number of Successful RL Additions in Soft Handover Between Neighboring Cells
Issue 01 (2013-05-04)
2571
Counters
Counter ID 67183492 Counter Name VS.SHO.AddRLSucc.NCell Counter Description Number of Successful RL Additions in Soft Handover Between Neighboring Cells
Description
This measurement item provides the number of successful RL additions in the soft handover between neighboring cells.
Measurement point
The measurement is triggered at point C, as shown in the figure. When the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover procedure, the RNC measures this item for each pair of source and target cells. Here, source cells refer to the best cell that the UE camps on before the soft handover. Target cells refer to the cells whose RLs are added in the soft handover. Figure 1-1138 Soft handover procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.AddRLSucc.NCell Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.14.1.9 Number of RL Deletion Attempts in Soft Handover Between Neighboring Cells Counters
Counter ID 67183493 Counter Name VS.SHO.DelRLAtt.NCell Counter Description Number of RL Deletion Attempts in Soft Handover Between Neighboring Cells
Description
This measurement item provides the number of attempts to delete RLs in the soft handover between neighboring cells.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends an ACTIVE SET UPDATE message to the UE during the soft handover procedure, the RNC measures this item for each pair of source and target cells. Here, source cells refer to the best cell that the UE camps on before the soft handover. Target cells refer to the cells whose RLs will be deleted in the soft handover.
Issue 01 (2013-05-04)
2573
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.DelRLAtt.NCell Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.14.1.10 Number of Successful RL Deletions in Soft Handover Between Neighboring Cells
Issue 01 (2013-05-04)
2574
Counters
Counter ID 67183494 Counter Name VS.SHO.DelRLSucc.NCell Counter Description Number of Successful RL Deletions in Soft Handover Between Neighboring Cells
Description
This measurement item provides the number of radio link deletion attempts in the soft handover between neighboring cells.
Measurement point
The measurement is triggered at point C, as shown in the figure. When the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover procedure, the RNC measures this item for each pair of source and target cells. Here, source cells refer to the best cell that the UE camps on before the soft handover. Target cells refer to the cells whose RLs will be deleted in the soft handover. Figure 1-1140 Soft handover procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.SHO.DelRLSucc.NCell Feature ID WRFD-020202 WRFD-020201 Feature Name Intra RNC Soft Handover Intra Node B Softer Handover
1.14.1.11 Number of Hard Handover Attempts from HS-DSCH to HS-DSCH Between Neighboring Cells Counters
Counter ID 67190708 Counter Name VS.HSDPA.HHO.NoChR.A tt.NCell Counter Description Number of HSDSCH-toHSDSCH hard Handover Requests Without Channel Change Between Neighboring Cells
Description
This measurement item provides the number of hard handover attempts from HS-DSCH to HSDSCH between neighboring cells.
Measurement point
The measurement is triggered at point B, as shown in the figure. During a hard handover, for example, when the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to an UE, the RNC measures this item for each pair of source and target cells. Here, source cell refers to the best cell that the UE camps on before the hard handover. Target cells refer to the cells that the UE camps on after the hard handover.
Issue 01 (2013-05-04)
2576
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.HHO.NoChR.A tt.NCell Feature ID WRFD-01061006 Feature Name HSDPA Mobility Management
1.14.1.12 Number of Successful Hard Handovers from HS-DSCH to HS-DSCH Between Neighboring Cells
Issue 01 (2013-05-04)
2577
Counters
Counter ID 67190709 Counter Name VS.HSDPA.HHO.NoChR.S ucc.NCell Counter Description Number of Successful HSDSCH-to-HSDSCH hard Handovers Without Channel Change Between Neighboring Cells
Description
This measurement item provides the number of successful hard handovers from HS-DSCH to HS-DSCH between neighboring cells.
Measurement point
The measurement is triggered at point C, as shown in the figure. During a hard handover, for example, when the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from an UE, the RNC measures this item for each pair of source and target cells if the HSDPA service is in use before and after the hard handover. Here, source cell refers to the best cell that the UE camps on before the hard handover. Target cells refer to the cells that the UE camps on after the hard handover. Figure 1-1142 Hard handover procedure (successful operation)
Issue 01 (2013-05-04)
2578
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.HHO.NoChR.S ucc.NCell Feature ID WRFD-01061006 Feature Name HSDPA Mobility Management
1.14.1.13 Number of HSDPA Serving Cell Change Attempts Between Neighboring Cells Counters
Counter ID 67190710 Counter Name VS.HSDPA.ServCellChg.At t.NCell Counter Description Number of HSDPA Serving Cell Change Attempts Between Neighboring Cells
Description
This measurement item provides the number of HSDPA serving cell change attempts.
Measurement point
This measurement item provides the number of HSDPA serving cell change attempts. This procedure can be triggered with the following messages: [1]PHYSICAL CHANNEL RECONFIGURATION, [2]TRANSPORT CHANNEL RECONFIGURATION, [3]RADIO BEARER RECONFIGURATION, [4]ACTIVE SET UPDATE message. Accordingly, UE may send [1]PHYSICAL CHANNEL RECONFIGURATION COMPLETE, [2]PHYSICAL CHANNEL RECONFIGURATION FAILURE, [3]TRANSPORT CHANNEL RECONFIGURATION COMPLETE, [4]TRANSPORT CHANNEL RECONFIGURATION FAILURE,
[5]RADIO BEARER RECONFIGURATION COMPLETE, [6]RADIO BEARER RECONFIGURATION FAILURE, [7]ACTIVE SET UPDATE COMPLETE, [8]ACTIVE SET UPDATE FAILURE message to RNC as a response. The measurement is triggered at point A, as shown in the figure. The procedure shown in the figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an example. When the RNC sends the UE a PHYSICAL CHANNLE RECONFIGRATION message indicating that the HSDPA serving cell changes, the RNC measures this item for each pair of source and target cells.Here, source cell refers to the serving cell before change and target cell refers to the serving cell after change. Figure 1-1143 Serving cell change procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.ServCellChg.At t.NCell
Issue 01 (2013-05-04)
Feature Name HSDPA Mobility Management

2580
1.14.1.14 Number of Successful HSDPA Serving Cell Changes Between Neighboring Cells Counters
Counter ID 67190711 Counter Name VS.HSDPA.ServCellChg.Su cc.NCell Counter Description Number of Successful HSDPA Serving Cell Changes Between Neighboring Cells
Description
This measurement item provides the number of successful HSDPA serving cell changes.
Measurement point
This measurement item provides the number of successful HSDPA serving cell changes. This procedure can be triggered with the following messages: [1]PHYSICAL CHANNEL RECONFIGURATION, [2]TRANSPORT CHANNEL RECONFIGURATION, [3]RADIO BEARER RECONFIGURATION, [4]ACTIVE SET UPDATE message. Accordingly, UE may send [1]PHYSICAL CHANNEL RECONFIGURATION COMPLETE, [2]PHYSICAL CHANNEL RECONFIGURATION FAILURE, [3]TRANSPORT CHANNEL RECONFIGURATION COMPLETE, [4]TRANSPORT CHANNEL RECONFIGURATION FAILURE, [5]RADIO BEARER RECONFIGURATION COMPLETE, [6]RADIO BEARER RECONFIGURATION FAILURE, [7]ACTIVE SET UPDATE COMPLETE, [8]ACTIVE SET UPDATE FAILURE message to RNC as a response. The measurement is triggered at point B, as shown in the figure. The procedure shown in the figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an example. When the RNC receives from the UE a PHYSICAL CHANNLE RECONFIGURATION COMPLETE message indicating that the HSDPA serving cell changes, the RNC measures this item for each pair of source and target cells. Here, source cell refers to the serving cell before change and target cell refers to the serving cell after change.
Formula
None
Unit
None
Related Features
Counter Name VS.HSDPA.ServCellChg.Su cc.NCell Feature ID WRFD-01061006 Feature Name HSDPA Mobility Management
1.14.1.15 Number of CS Domain Outgoing Inter-Cell Hard Handover Attempts Between Neighboring Cells
Issue 01 (2013-05-04)
2582
Counters
Counter ID 73393988 Counter Name VS.HHO.AttOutIntraNodeB .CS.NCell VS.HHO.AttOutInterNodeB IntraRNC.CS.NCell Counter Description Number of CS Outgoing Intra-NodeB Inter-Cell Hard Handover Attempts Number of CS Outgoing Intra-RNC Inter-NodeB Inter-Cell Hard Handover Attempts Number of CS Outgoing Inter-RNC Inter-Cell Hard Handover Attempts
73393996
73394004
VS.HHO.AttOutInterRNCIu r.CS.NCell
Description
This counter provides the number of CS domain outgoing inter-cell hard handover attempts between neighboring cells.
Measurement point
The measurement is triggered at point B as shown in the figure, taking the physical channel reconfiguration as an example. When the RNC determines to trigger a hard handover, it sends to the UE a PHYSICAL CHANNEL RECONFIGURATION message. In this case, the RNC measures this item for each pair of source and target cells if the HSDPA service is in use before and after the hard handover. Here, source cell refers to the best cell that the UE camps on before the hard handover. Target cells refer to the cells that the UE camps on after the hard handover.
Issue 01 (2013-05-04)
2583
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttOutIntraNodeB .CS.NCell Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
Issue 01 (2013-05-04)
2584
Counter Name VS.HHO.AttOutInterNodeB IntraRNC.CS.NCell
Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
VS.HHO.AttOutInterRNCIu r.CS.NCell
WRFD-020301 WRFD-020302 WRFD-020304
Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.14.1.16 Number of Successful CS Domain Outgoing Hard Handovers Between Neighboring Cells Counters
Counter ID 73393989 Counter Name VS.HHO.SuccOutIntraNode B.CS.NCell VS.HHO.SuccOutInterNode BIntraRNC.CS.NCell Counter Description Number of Successful CS Outgoing Intra-NodeB InterCell Hard Handovers Number of Successful CS Outgoing Intra-RNC InterNodeB Inter-Cell Hard Handovers Number of Successful CS Outgoing Inter-RNC InterCell Hard Handovers
73393997
73394005
VS.HHO.SuccOutInterRNC Iur.CS.NCell
Description
This counter provides the number of CS domain successful Outgoing inter-cell hard handovers between neighboring cells.
Measurement point
Take physical channel reconfiguration as an example, the measurement is triggered at point C as shown in the figure. When the RNC receives from the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message, the RNC measures this item for each pair of
source and target cells. Here, the source cells refer to the best cell that the UE camps on before the hard handover. The target cells refer to the cells that the UE camps on after the hard handover. Figure 1-1146 Hard handover procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccOutIntraNode B.CS.NCell Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
Issue 01 (2013-05-04)
2586
Counter Name VS.HHO.SuccOutInterNode BIntraRNC.CS.NCell
VS.HHO.SuccOutInterRNC Iur.CS.NCell
WRFD-020301 WRFD-020302 WRFD-020304
1.14.1.17 Number of Failed CS Domain Hard Handovers According to Different Causes Between Neighboring Cells Counters
Counter ID 73393991 Counter Name VS.HHO.FailOutIntraNode B.PhyChFail.CS.NCell Counter Description Number of Failed CS Outgoing Intra-NodeB InterCell Hard Handovers (Physical Channel Failure) Number of Failed CS Outgoing Intra-NodeB InterCell Hard Handovers (UE No Response) Number of Failed CS Outgoing Intra-RNC InterNodeB Inter-Cell Hard Handovers (UE No Response) Number of Failed CS Outgoing Intra-RNC InterNodeB Inter-Cell Hard Handovers (Physical Channel Failure)
73393990
VS.HHO.FailOutIntraNode B.NoReply.CS.NCell
73393998
VS.HHO.FailOutInterNode BIntraRNC.NoReply.CS.N Cell
73393999
VS.HHO.FailOutInterNode BIntraRNC.PhyChFail.CS. NCell
Issue 01 (2013-05-04)
2587
Counter ID 73394006
Counter Name VS.HHO.FailOutInterRNCI ur.CfgUnsup.CS.NCell
Counter Description Number of Failed CS Outgoing Inter-RNC InterCell Hard Handovers (Configuration Unsupported) Number of Failed CS Outgoing Inter-RNC InterCell Hard Handovers (Physical Channel Failure)
73394007
VS.HHO.FailOutInterRNCI ur.PhyChFail.CS.NCell
Description
These counters provide the number of failed CS domain hard handovers between neighboring cells according to different failure causes.
Measurement point
The measurement is triggered at point A as shown in the figure, taking PHYSICAL CHANNEL RECONFIGURATION as an example. When the RNC receives from the UE a PHYSICAL CHANNEL RECONFIGURATION FAILURE message, the RNC measures these items for each pair of source and target cells according to different failure causes. Here, the source cells refer to the best cell that the UE camps on before the hard handover. The target cells refer to the cells that the UE camps on after the hard handover. Figure 1-1147 Hard handover procedure (failed operation)
Issue 01 (2013-05-04)
2588
The measurement is triggered at point A as shown in the figure, taking PHYSICAL CHANNEL RECONFIGURATION as an example. When the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message, it starts a timer to wait for the response message from the UE. If no response is received from the UE before the timer expires, the hard handover is failed because of "UE No Response". In this case, the RNC measures the items for each pair of source and target cells according to different causes. Here, the source cells refer to the best cell that the UE camps on before the hard handover. The target cells refer to the cells that the UE camps on after the hard handover. Figure 1-1148 Hard handover procedure (failed operation for timer expiry)
Formula
None
Unit
None
Issue 01 (2013-05-04)
2589
Related Features
Counter Name VS.HHO.FailOutIntraNode B.PhyChFail.CS.NCell Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailOutIntraNode B.NoReply.CS.NCell WRFD-020301 WRFD-020302 WRFD-020304 Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailOutInterNode BIntraRNC.NoReply.CS.N Cell WRFD-020301 WRFD-020302 WRFD-020304 Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailOutInterNode BIntraRNC.PhyChFail.CS. NCell WRFD-020301 WRFD-020302 WRFD-020304 Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailOutInterRNCI ur.CfgUnsup.CS.NCell WRFD-020301 WRFD-020302 WRFD-020304 Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailOutInterRNCI ur.PhyChFail.CS.NCell WRFD-020301 WRFD-020302 WRFD-020304 Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.14.1.18 Number of PS Domain Outgoing Inter-Cell Hard Handover Attempts Between Neighboring Cells Counters
Counter ID 73393992 Counter Name VS.HHO.AttOutIntraNodeB .PS.NCell VS.HHO.AttOutInterNodeB IntraRNC.PS.NCell Counter Description Number of PS Outgoing Intra-NodeB Inter-Cell Hard Handover Attempts Number of PS Outgoing Intra-RNC Inter-NodeB Inter-Cell Hard Handover Attempts Number of PS Outgoing Inter-RNC Inter-Cell Hard Handover Attempts
73394000
73394008
VS.HHO.AttOutInterRNCIu r.PS.NCell
Description
This counter provides the number of PS domain outgoing inter-cell hard handover attempts between neighboring cells.
Measurement point
The measurement is triggered at point B as shown in the figure, taking the physical channel reconfiguration as an example. When the RNC determines to trigger a hard handover, it sends to the UE a PHYSICAL CHANNEL RECONFIGURATION message. In this case, the RNC measures this item for each pair of source and target cells if the HSDPA service is in use before and after the hard handover. Here, source cell refers to the best cell that the UE camps on before the hard handover. Target cells refer to the cells that the UE camps on after the hard handover.
Issue 01 (2013-05-04)
2591
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttOutIntraNodeB .PS.NCell Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
Issue 01 (2013-05-04)
2592
Counter Name VS.HHO.AttOutInterNodeB IntraRNC.PS.NCell
VS.HHO.AttOutInterRNCIu r.PS.NCell
WRFD-020301 WRFD-020302 WRFD-020304
1.14.1.19 Number of Successful PS Domain Outgoing Hard Handovers Between Neighboring Cells Counters
Counter ID 73393993 Counter Name VS.HHO.SuccOutIntraNode B.PS.NCell VS.HHO.SuccOutInterNode BIntraRNC.PS.NCell Counter Description Number of Successful PS Outgoing Intra-NodeB InterCell Hard Handovers Number of Successful PS Outgoing Intra-RNC InterNodeB Inter-Cell Hard Handovers Number of Successful PS Outgoing Inter-RNC InterCell Hard Handovers
73394001
73394009
VS.HHO.SuccOutInterRNC Iur.PS.NCell
Description
This counter provides the number of PS domain successful Outgoing inter-cell hard handovers between neighboring cells.
Measurement point
Take physical channel reconfiguration as an example, the measurement is triggered at point C as shown in the figure. When the RNC receives from the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message, the RNC measures this item for each pair of
source and target cells. Here, the source cells refer to the best cell that the UE camps on before the hard handover. The target cells refer to the cells that the UE camps on after the hard handover. Figure 1-1150 Hard handover procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccOutIntraNode B.PS.NCell Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
Issue 01 (2013-05-04)
2594
Counter Name VS.HHO.SuccOutInterNode BIntraRNC.PS.NCell
VS.HHO.SuccOutInterRNC Iur.PS.NCell
WRFD-020301 WRFD-020302 WRFD-020304
1.14.1.20 Number of Failed PS Domain Hard Handovers According to Different Causes Between Neighboring Cells Counters
Counter ID 73393995 Counter Name VS.HHO.FailOutIntraNode B.PhyChFail.PS.NCell Counter Description Number of Failed PS Outgoing Intra-NodeB InterCell Hard Handovers (Physical Channel Failure) Number of Failed PS Outgoing Intra-NodeB InterCell Hard Handovers (UE No Response) Number of Failed PS Outgoing Intra-RNC InterNodeB Inter-Cell Hard Handovers (UE No Response) Number of Failed PS Outgoing Intra-RNC InterNodeB Inter-Cell Hard Handovers (Physical Channel Failure)
73393994
VS.HHO.FailOutIntraNode B.NoReply.PS.NCell
73394002
VS.HHO.FailOutInterNode BIntraRNC.NoReply.PS.NC ell
73394003
VS.HHO.FailOutInterNode BIntraRNC.PhyChFail.PS.N Cell
Issue 01 (2013-05-04)
2595
Counter ID 73394010
Counter Name VS.HHO.FailOutInterRNCI ur.CfgUnsup.PS.NCell
Counter Description Number of Failed PS Outgoing Inter-RNC InterCell Hard Handovers (Configuration Unsupported) Number of Failed PS Outgoing Inter-RNC InterCell Hard Handovers (Physical Channel Failure)
73394011
VS.HHO.FailOutInterRNCI ur.PhyChFail.PS.NCell
Description
These counters provide the number of failed PS domain hard handovers between neighboring cells according to different failure causes.
Measurement point
The measurement is triggered at point A as shown in the figure, taking PHYSICAL CHANNEL RECONFIGURATION as an example. When the RNC receives from the UE a PHYSICAL CHANNEL RECONFIGURATION FAILURE message, the RNC measures these items for each pair of source and target cells according to different failure causes. Here, the source cells refer to the best cell that the UE camps on before the hard handover. The target cells refer to the cells that the UE camps on after the hard handover. Figure 1-1151 Hard handover procedure (failed operation)
Issue 01 (2013-05-04)
2596
The measurement is triggered at point A as shown in the figure, taking PHYSICAL CHANNEL RECONFIGURATION as an example. When the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message, it starts a timer to wait for the response message from the UE. If no response is received from the UE before the timer expires, the hard handover is failed because of "UE No Response". In this case, the RNC measures the items for each pair of source and target cells according to different causes. Here, the source cells refer to the best cell that the UE camps on before the hard handover. The target cells refer to the cells that the UE camps on after the hard handover. Figure 1-1152 Hard handover procedure (failed operation for timer expiry)
Formula
None
Unit
None
Issue 01 (2013-05-04)
2597
Related Features
Counter Name VS.HHO.FailOutIntraNode B.PhyChFail.PS.NCell Feature ID WRFD-020301 WRFD-020302 WRFD-020304 Feature Name Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailOutIntraNode B.NoReply.PS.NCell WRFD-020301 WRFD-020302 WRFD-020304 Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailOutInterNode BIntraRNC.NoReply.PS.NC ell WRFD-020301 WRFD-020302 WRFD-020304 Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailOutInterNode BIntraRNC.PhyChFail.PS.N Cell WRFD-020301 WRFD-020302 WRFD-020304 Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailOutInterRNCI ur.CfgUnsup.PS.NCell WRFD-020301 WRFD-020302 WRFD-020304 Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS VS.HHO.FailOutInterRNCI ur.PhyChFail.PS.NCell WRFD-020301 WRFD-020302 WRFD-020304 Intra Frequency Hard Handover Inter Frequency Hard Handover Based on Coverage Inter Frequency Hard Handover Based on DL QoS
1.14.1.21 Number of Outgoing SRNS Relocation Executions with HHO Between Neighboring Cells Counters
Counter ID 73394026 Counter Name VS.HHO.AttOutInterRNCC N.CS.NCell Counter Description Number of Outgoing UEInvolved SRNS Relocation Executions Triggered by CS HHO Number of Outgoing UEInvolved SRNS Relocation Executions Triggered by PS HHO
73394030
VS.HHO.AttOutInterRNCC N.PS.NCell
Description
These counters provide the number of outgoing UE-involved SRNS relocation execution attempts triggered by hard handover. Relocation execution is the process that the SRNC Sends to the UE reconfiguration messages after the SRNC relocation prepration succeeds. The reconfiguration involves the following messages: RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, TRANSPORT CHANNEL RECONFIGURATION, and PHYSICAL CHANNEL RECONFIGURATION. The originating cell and the target cell of the hard handover should under different RNCs.
Measurement point
Take the RADIO BEARER RECONFIGURATION message as an example, the measurement is triggered at point A as shown in the figure. When the SNRC sends the UE a RADIO BEARER RECONFIGURATION message during the UE-involved SRNS relocation triggered by hard handover, the counter is measured in both the best cells that the UE camps on before and after the hard handover if the originating cell and the target cell are under different RNCs.
Issue 01 (2013-05-04)
2599
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.AttOutInterRNCC N.CS.NCell VS.HHO.AttOutInterRNCC N.PS.NCell Feature ID WRFD-02060502 WRFD-02060502 Feature Name SRNS Relocation with Hard Handover SRNS Relocation with Hard Handover
1.14.1.22 Number of Successful Outgoing SRNS Relocations with HHO Between Neighboring Cells
Issue 01 (2013-05-04)
2600
Counters
Counter ID 73394027 Counter Name VS.HHO.SuccOutInterRNC CN.CS.NCell Counter Description Number of Successful Outgoing UE-Involved SRNS Relocations Triggered by CS HHO Number of Successful Outgoing UE-Involved SRNS Relocation Executions Triggered by PS HHO
73394031
VS.HHO.SuccOutInterRNC CN.PS.NCell
Description
This counters provide the number of successful outgoing UE-involved SRNS relocations triggered by the hard handover. The SRNC relocation succeeds when the CN sends an IU RELEASE COMMAND message with the cause value of "Successful Relocation", "Normal Release", or "Network Optimization".
Measurement point
The measurement is triggered at point A as shown in the figure. When the SNRC receives an IU RELEASE COMMAND message with the cause value of "Successful Relocation", "Normal Release", or "Network Optimization" during the UE-involved SRNS relocation triggered by hard handover, the counter is measured in both the best cells that the UE camps on before and after the hard handover if the originating cell and the target cell are under different RNCs. Figure 1-1154 Successful SRNC relocation procedure
Issue 01 (2013-05-04)
2601
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.SuccOutInterRNC CN.CS.NCell VS.HHO.SuccOutInterRNC CN.PS.NCell Feature ID WRFD-02060502 WRFD-02060502 Feature Name SRNS Relocation with Hard Handover SRNS Relocation with Hard Handover
1.14.1.23 Number of Failed CS Domain Outgoing SRNS Relocation with HHO Preparations According to Different Causes Between Neighboring Cells Counters
Counter ID 73394028 Counter Name VS.HHO.FailRelocPrepOutI nterRNCCN.TExp.CS.NCel l Counter Description Number of Failed Outgoing UE-Involved SRNS Relocation Preparations Triggered by CS HHO (TRELOCalloc Expiry) Number of Failed Outgoing UE-Involved SRNS Relocation Preparations Triggered by CS HHO (Relocation Failure in Target CN/RNC or Target System)
73394029
VS.HHO.FailRelocPrepOutI nterRNCCN.TgtF.CS.NCell
Description
These counters provide the number of CS domain failed outgoing UE-involved SRNS relocation preparations triggered by hard handover according to different failure causes between neighboring cells.
Measurement point
The measurement is triggered at point A as shown in the figure, when the SRNC receives a RELOCATION PREPARATION FAILURE message during the relocation triggered by a hard handover. In this case, the corresponding counter is measured in both best cells that the UE camps on before and after the hard handover according to different failure causes.
Figure 1-1155 SRNC relocation preparation procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailRelocPrepOutI nterRNCCN.TExp.CS.NCel l VS.HHO.FailRelocPrepOutI nterRNCCN.TgtF.CS.NCell Feature ID WRFD-02060502 Feature Name SRNS Relocation with Hard Handover SRNS Relocation with Hard Handover
WRFD-02060502
1.14.1.24 Number of Failed PS Domain Outgoing SRNS Relocation with HHO Preparations According to Different Causes Between Neighboring Cells
Issue 01 (2013-05-04)
2603
Counters
Counter ID 73394032 Counter Name VS.HHO.FailRelocPrepOutI nterRNCCN.TExp.PS.NCell Counter Description Number of Failed Outgoing UE-Involved SRNS Relocation Preparations Triggered by PS HHO (TRELOCalloc Expiry) Number of Failed Outgoing UE-Involved SRNS Relocation Preparations Triggered by PS HHO (Relocation Failure in Target CN/RNC or Target System)
73394033
VS.HHO.FailRelocPrepOutI nterRNCCN.TgtF.PS.NCell
Description
These counters provide the number of PS domain failed outgoing UE-involved SRNS relocation preparations triggered by hard handover according to different failure causes between neighboring cells.
Measurement point
The measurement is triggered at point A as shown in the figure, when the SRNC receives a RELOCATION PREPARATION FAILURE message during the relocation triggered by a hard handover. In this case, the corresponding counter is measured in both best cells that the UE camps on before and after the hard handover according to different failure causes. Figure 1-1156 SRNC relocation preparation procedure (failed operation)
Issue 01 (2013-05-04)
2604
Formula
None
Unit
None
Related Features
Counter Name VS.HHO.FailRelocPrepOutI nterRNCCN.TExp.PS.NCell VS.HHO.FailRelocPrepOutI nterRNCCN.TgtF.PS.NCell Feature ID WRFD-02060502 WRFD-02060502 Feature Name SRNS Relocation with Hard Handover SRNS Relocation with Hard Handover
1.15 Measurement of UMTS DSP Performance(UDSP)

Overview
The DSP Measurement indicates the running performance, such as the CPU usage and L2 instance setup times, of each DSP on the service board of the RNC.
FunctionSubSets
FunctionSubSet DSP FunctionSubSet Name Measurement related to DSP performance
1.15.1 Measurement related to DSP performance(DSP)

Overview
DSP is the core for the WCDMA RNC to handle the user plane protocol. During the system operation, the DSP usage can be measured for the analysis of the system load and stability of user plane handling so that the system runs in a reliable way.
Issue 01 (2013-05-04)
2605
Counters
Counter ID 73410488 73410487 73393960 73410486 Counter Name VS.DSP.PSULTraf fic VS.DSP.PSDLTraf fic VS.DSP.UsagePeak VS.DSP.UsageAvg Counter Description Number of UL PS Traffic for DSP Number of DL PS Traffic for DSP Peak DSP Usage in Period Mean DSP Usage in Period Original Release V900R012 V900R012 V900R012 V900R012
None
1.15.1.1 Uplink PS Traffic Handled by the DSP Counters

Counter ID 73410488 Counter Name VS.DSP.PSULTraffic Counter Description Number of UL PS Traffic for DSP
Description
This measurement counter provides the uplink PS traffic handled by a DSP.
Measurement point
The measurement is triggered when the DSP handles the uplink PS data. This measurement counter collects the information on the traffic at the RLC layer, excluding the RLC header. This measurement counter includes RLC retransmitted traffic and soft handover, and does not include softer handover.
Formula
None
Unit
byte
Related Features
Counter Name VS.DSP.PSULTraffic Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
1.15.1.2 Downlink PS Traffic Handled by the DSP Counters

Counter ID 73410487 Counter Name VS.DSP.PSDLTraffic Counter Description Number of DL PS Traffic for DSP
Description
This measurement counter provides the downlink PS traffic handled by a single DSP.
Measurement point
The measurement is triggered when the DSP handles the downlink PS data. This measurement counter collects the information on the traffic at the RLC layer, excluding the RLC header. This measurement counter includes RLC retransmitted traffic and soft handover, and does not include softer handover.
Formula
None
Unit
byte
Related Features
Counter Name VS.DSP.PSDLTraffic Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Issue 01 (2013-05-04)
2607
1.15.1.3 Measurement of the DSP Usage in a Period Counters

Counter ID 73393960 73410486 Counter Name VS.DSP.UsagePeak VS.DSP.UsageAvg Counter Description Peak DSP Usage in Period Mean DSP Usage in Period
The following intermediate counters are used for calculating preceding counters based on specific formulas. Counter ID 67196336 67196335 Counter Name VS.DSP.DSPUsageAvgCount VS.DSP.DSPUsageAvgValue Counter Description Number of mean DSP Usage Reports Mean Usage in 20 Seconds for DSP
Description
These counters provide the maximum DSP CPU usage and average DSP CPU usage within a measurement period.
Measurement point
The DSP CPU usage is sampled every five seconds. At the end of a measurement period, the maximum of these sampling results is used as the value of VS.DSP.UsagePeak, and the value of VS.DSP.UsageAvg is obtained by dividing the sum of these sampling results by the number of samples.
Formula
VS.DSP.UsageAvg = [VS.DSP.DSPUsageAvgValue]/[VS.DSP.DSPUsageAvgCount]
Unit
%
Related Features
Counter Name VS.DSP.UsagePeak Feature ID WRFD-010510 Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
2608
Issue 01 (2013-05-04)
Counter Name VS.DSP.UsageAvg
Issue 01 (2013-05-04)
2609
2 Transport Network Related Measurement
Transport Network Related Measurement
About This Chapter

The following table lists the relationship between object types and boards. x indicates the board from which the counters under the object type are collected. O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e A A L 2 P A T H U M T S B B o o a a r r d d O P I E U U a a B o a r d G O U a B B B B B B o o o o o o a a a a a a r r r r r r d d d d d d G F G F F S O G O G G C U 2 U 2 2 U c a d d c a B o a r d S C U b B o a r d X P U B o a r d A E U a B B B B o o o o a a a a r r r r d d d d U U P A O O O O I I U U a c a a B o a r d A O U c
Issue 01 (2013-05-04)
2610
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e A A L 2 P A T H _ P V C L A Y E R A N I _ I P A N I _ Q A A L 2 U M T S
B B o o a a r r d d O P I E U U a a
B o a r d G O U a
B B B B B B o o o o o o a a a a a a r r r r r r d d d d d d G F G F F S O G O G G C U 2 U 2 2 U c a d d c a
B o a r d S C U b
B o a r d X P U
B o a r d A E U a x
B B B B o o o o a a a a r r r r d d d d U U P A O O O O I I U U a c a a x x x
B o a r d A O U c x
G U
U M T S
Issue 01 (2013-05-04)
2611
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e A N I _ Q A A L 2 _ I P A T E R _ R E S A T M _ L O G I C _ P O R T B C U M T S
B o a r d G O U a
B o a r d S C U b
B o a r d X P U
B o a r d A E U a
B B B B o o o o a a a a r r r r d d d d U U P A O O O O I I U U a c a a
B o a r d A O U c
G S M
U M T S
G x S M
Issue 01 (2013-05-04)
2612
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e C H A N N E L I Z E D _ O P T I C A L _ P O R T D P C G R O U P E L E C T G U x
B B o o a a r r d d O P I E U U a a x
B o a r d G O U a
B o a r d S C U b
B o a r d X P U
B o a r d A E U a
B B B B o o o o a a a a r r r r d d d d U U P A O O O O I I U U a c a a x x
B o a r d A O U c x
G S M
G U
Issue 01 (2013-05-04)
2613
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e E 1 T 1 _ E S F E G E F R A C A T M L N K F R A C I M A L N K G U x x
B B o o a a r r d d O P I E U U a a x x
B o a r d G O U a
B o a r d S C U b
B o a r d X P U
B o a r d A E U a x
B o a r d A O U c x
G U
U M T S
U M T S
Issue 01 (2013-05-04)
2614
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e H D L C _ L I N K I M A G R P I M A L N K I P O A L N K I P P A T H G x S M
B o a r d G O U a
B o a r d S C U b
B o a r d X P U
B o a r d A E U a
B o a r d A O U c
U M T S
U M T S
U M T S
G U
Issue 01 (2013-05-04)
2615
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e I P P A T H _ I P L A Y E R G U x
B o a r d G O U a x
B B B B B B o o o o o o a a a a a a r r r r r r d d d d d d G F G F F S O G O G G C U 2 U 2 2 U c a d d c a x x x x x
B o a r d S C U b
B o a r d X P U
B o a r d A E U a
B B B B o o o o a a a a r r r r d d d d U U P A O O O O I I U U a c a a x x x
B o a r d A O U c
I G P U P A T H _ P M I P P A T H _ R T P G U
Issue 01 (2013-05-04)
2616
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e L A P D L I N K L O G I C _ P O R T L O G I C _ P O R T _ Q U E U E G x S M x
B o a r d G O U a
B o a r d S C U b
B o a r d X P U
B o a r d A E U a
B o a r d A O U c
G U
G U
Issue 01 (2013-05-04)
2617
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e M G 3 U U A _ D E M G 3 U U A _ L N K M G 3 U U A _ L N K _ S E T M G L U P P P x
B o a r d G O U a
B o a r d S C U b
B o a r d X P U
B o a r d A E U a
B o a r d A O U c
Issue 01 (2013-05-04)
2618
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e M G L U P P P _ Q U E U E x
B o a r d G O U a
B o a r d S C U b
B o a r d X P U
B o a r d A E U a
B B B B o o o o a a a a r r r r d d d d U U P A O O O O I I U U a c a a x
B o a r d A O U c
M G x T S P M 2 _ L N K M G T U P 3 _ D S P M G T U P 3 _ L N K _ S E T
Issue 01 (2013-05-04)
2619
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e M G T U P 3 _ L N K N O N _ C H A N N E L I Z E D _ O P T I C A L _ P O R T N S V C U M T S
B o a r d G O U a
B o a r d S C U b
B o a r d X P U
B o a r d A E U a
B o a r d A O U c
G x S M
Issue 01 (2013-05-04)
2620
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e N S V L O A M _ F L O W P C U P O R T _ A B I S P P P P P P _ Q U E U E G S M U x M T S
B o a r d G O U a
B B B B B B o o o o o o a a a a a a r r r r r r d d d d d d G F G F F S O G O G G C U 2 U 2 2 U c a d d c a x x x x x
B o a r d S C U b
B o a r d X P U
B o a r d A E U a
B o a r d A O U c
G S M G S M
G U G U
Issue 01 (2013-05-04)
2621
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e S A A L _ L N K S A A L L N K _ P V C L A Y E R S C C P S C C P D P C U M T S
B o a r d G O U a
B o a r d S C U b
B o a r d X P U
B o a r d A E U a
B o a r d A O U c
U M T S
G U
G S M
Issue 01 (2013-05-04)
2622
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e S C T P L N K S C T P L N K _ I P L A Y E R S D H T C _ R E S T R U N K G U
B o a r d G O U a
B o a r d S C U b
B o a r d X P U
B o a r d A E U a
B o a r d A O U c
G U
G U G S M
G U
Issue 01 (2013-05-04)
2623
O W B B b h o o j i a a e c r r c h d d t M P E t o O I y d U U p e c a e T S A L L O C U N I L N K V C A C R O S S G S M
B o a r d G O U a
B B B B B B o o o o o o a a a a a a r r r r r r d d d d d d G F G F F S O G O G G C U 2 U 2 2 U c a d d c a x
B o a r d S C U b x
B o a r d X P U
B o a r d A E U a
B o a r d A O U c
U M T S
U M T S
2.1 Measurement of AAL2PATH Performance(AAL2PATH) 2.2 Measurement of AAL2PATH ATM Layer Performance(AAL2PATH_PVCLAYER) 2.3 Measurement of VCL PM on an AAL2 Path(AAL2PATH_VCLPM) 2.4 Measurement of IP Transport Adjacent Node Connection Performance(ANI_IP) 2.5 Measurement of QAAL2 Adjacent Node Performance(ANI_QAAL2) 2.6 Measurement of Dual-Stack Transport Adjacent Node Performance(ANI_QAAL2_IP) 2.7 Measurement of ATM Logical Port Performance(ATM_LOGIC_PORT) 2.8 Measurement of Channelized Optical Port Performance (CHANNELIZED_OPTICAL_PORT) 2.9 Measuement of E1T1 port error code Performance(E1T1_ES) 2.10 Measurement of E1/T1 ELECT Port Performance(ELECT)
2.11 Measurement of FEGE Ethernet Port Performance(FEGE) 2.12 Measurement of Fractional ATM Link Performance(FRACATMLNK) 2.13 Measurement of Fractioanl IMA Link Performance(FRACIMALNK) 2.14 Measurement of IMA Group Performance(IMAGRP) 2.15 Measurement of IMA Link Performance(IMALNK) 2.16 Measurement of IPoA Link Performance(IPOALNK) 2.17 Measurement of VCL PM on an IPOAPVC link(IPOAPVC_VCLPM) 2.18 Measurement of IP Path Performance(IPPATH) 2.19 Measurement of IPPATH IP Layer Performance(IPPATH_IPLAYER) 2.20 Measurement of IPPATH PM Performance(IPPATH_PM) 2.21 Measurement of IP-Path-Based RTP Performance(IPPATH_RTP) 2.22 Measurement of Transmission Resource Pool Adjacent Node Connection Performance (IPPOOL_ADJNODE) 2.23 Measurement of Transmission Resource Pool IPPM Performance(IPPOOL_PM) 2.24 Measurement of Transmission Resource Pool IP Address RTP Performance (IPPOOL_RTP) 2.25 Measurement of Transmission Resource Pool Local IP Address Connection Performance (IPPOOL_SIP) 2.26 Measurement of IURP Link Performance(IURPLNK) 2.27 Measurement of Logic Port Performance(LOGIC_PORT) 2.28 Measurement of Logic Port Queue Performance(LOGIC_PORT_QUEUE) 2.29 Measurement of the M3UA Destination Entities Performance(M3UA_DE) 2.30 Measurement of the M3UA Link Performance(M3UA_LNK) 2.31 Measurement of M3UA Link Set Performance(M3UA_LNK_SET) 2.32 Measurement of MP Group Performance(MLPPP) 2.33 Measurement of MP Queue Performance(MLPPP_QUEUE) 2.34 Measurement of MTP3 Destination Signaling Point Performance(MTP3_DSP) 2.35 Measurement of MTP3 Signaling Link performance(MTP3_LNK) 2.36 Measurement of MTP3 Link Set Performance(MTP3_LNK_SET) 2.37 Measurement of Non-Channelized Optical Port Performance (NON_CHANNELIZED_OPTICAL_PORT) 2.38 Measurement of NODEB OAM Flow Performance(OAM_FLOW) 2.39 Measurement of PPP Link Performance(PPP) 2.40 Measurement of PPP Queue Performance(PPP_QUEUE)
2.41 Measurement of SAAL Link Performance(SAAL_LNK) 2.42 Measurement of SAAL Link ATM Layer Performance(SAALLNK_PVCLAYER) 2.43 Measurement of VCL PM on a SAAL link(SAALLNK_VCLPM) 2.44 Measurement of SCCP Based on OSP Performance(SCCP) 2.45 Measurement of SCTP Link Performance(SCTPLNK) 2.46 Measurement of SCTP Link IP Layer Performance(SCTPLNK_IPLAYER) 2.47 Measurement of SDH Performance(SDH) 2.48 Measurement of Trunk Group Performance(Trunk) 2.49 Measurement of UNI Link Performance(UNILNK) 2.50 Measurement of VC Cross Performance(VCACROSS)
Issue 01 (2013-05-04)
2626
2.1 Measurement of AAL2PATH Performance(AAL2PATH)

Overview
The measurement object type AAL2PATH indicates the performance of AAL2PATH.
FunctionSubSets
FunctionSubSet AAL2PATH FunctionSubSet Name AAL2 Path Measurement
2.1.1 AAL2 Path Measurement(AAL2PATH)

Overview
The AAL2 path measurement is used to measure the quality of transmission links directly affects the system performance. It is used to helps analyze system transmission quality so as to maintain system stability and reliability. AAL2 paths carry mainly FP and IUUP packets. AAL2 paths are logical paths which are carried by physical links, as shown in the following figure:
Figure 2-1 Physical bearer of the AAL2 path
Issue 01 (2013-05-04)
2627
Counters
Counter ID 67204206 Counter Name VS.AAL2PATH.Ac t.Con VS.AAL2PATH.F wd.Cong VS.AAL2PATH.F wd.Cong.Dur VS.AAL2PATH.B wd.Cong Counter Description Number of Active AAL2 Connections to an Adjacent Node Number of Forward Congestions on the AAL2 Path Duration of Forward Congestions on the AAL2 Path Number of Backward Congestions on the AAL2 Path Duration of Backward Congestions on the AAL2 Path Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67195595
67195596
67195597
67195598
VS.AAL2PATH.B wd.Cong.Dur
None
2.1.1.1 Number of Active AAL2 Connections to an Adjacent Node Counters

Counter ID 67204206 Counter Name VS.AAL2PATH.Act.Con Counter Description Number of Active AAL2 Connections to an Adjacent Node
Description
This counter provides the number of successful service admissions to an AAL2 path that is connected to an adjacent node in the specified measurement period.
Issue 01 (2013-05-04)
2628
Measurement point
The system takes samples of successful service admissions to an AAL2 path every 15 seconds. At the end of the measurement period, the system obtains the value of this counter by dividing the accumulated number of successful service admissions by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name VS.AAL2PATH.Act.Con Feature ID WRFD-05030106 Feature Name Call Admission Based on Used AAL2 Path Bandwidth
2.1.1.2 Counters Related to the Number of Congestions on the AAL2 Path Counters
Counter ID 67195595 Counter Name VS.AAL2PATH.Fwd.Cong Counter Description Number of Forward Congestions on the AAL2 Path Number of Backward Congestions on the AAL2 Path
67195597
VS.AAL2PATH.Bwd.Cong
Description
These counters provide the number of forward or backward congestions on the AAL2 path in the measurement period.Services will be affected if many AAL2 paths are congested forwardly or reversely. These counters can be used together with the duration of AAL2 path congestion to analyze the congestion.
Measurement point
The RNC checks the state of an AAL2 path each time a service is being admitted to that path. This counter is incremented by one when the state of the AAL2 path changes from noncongestion to forward or backward congestion, that is, the remaining bandwidth available becomes smaller than the congestion threshold.
Formula
None
Unit
None
Related Features
Counter Name VS.AAL2PATH.Fwd.Cong VS.AAL2PATH.Bwd.Cong Feature ID WRFD-05030106 WRFD-05030106 Feature Name Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth
2.1.1.3 Counters Related to the Duration of Congestions on the AAL2 Path Counters
Counter ID 67195596 Counter Name VS.AAL2PATH.Fwd.Cong. Dur VS.AAL2PATH.Bwd.Cong. Dur Counter Description Duration of Forward Congestions on the AAL2 Path Duration of Backward Congestions on the AAL2 Path
67195598
Description
These counters provide the duration of forward or backward congestion on the AAL2 path in the specified measurement period.
Measurement point
The RNC checks the state of an AAL2 path each time a service is being admitted to that path. The measurement of a forward (backward) congestion duration starts when a forward (backward) congestion is detected on an AAL2 path and stops when the forward (backward) congestion is cleared. The accumulated duration of forward (backward) congestion on the AAL2 path in the measurement period is taken as the value of this counter. Services will be affected if many AAL2 paths are congested.
Formula
None
Unit
s
Related Features
Counter Name VS.AAL2PATH.Fwd.Cong. Dur VS.AAL2PATH.Bwd.Cong. Dur Feature ID WRFD-05030106 WRFD-05030106 Feature Name Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth
2.2 Measurement of AAL2PATH ATM Layer Performance (AAL2PATH_PVCLAYER)

Overview
AAL2PATH ATM Layer performance measurement indicates the transmission quality of the AAL2PATH link ATM Layer on the AEUa, UOIa, AOUa, UOIc or AOUc board.
FunctionSubSets
FunctionSubSet AAL2PATH.PVCLAYER FunctionSubSet Name AAL2PATH ATM Layer Measurement
2.2.1 AAL2PATH ATM Layer Measurement (AAL2PATH.PVCLAYER)

Overview
The quality of transmission links directly affects the system performance. AAL2PATH ATM Layer measurement helps analyze system transmission quality so as to maintain system stability and reliability. Figure 1 shows the location of the ATM Layer in the procotol.
Issue 01 (2013-05-04)
2631
Figure 2-2 ATM Reference Model
Counters
Counter ID 67194097 Counter Name VS.AAL2PATH.P VCLAYER.RXCO RRECTCELLS VS.AAL2PATH.P VCLAYER.RXBY TES VS.AAL2PATH.P VCLAYER.PEAK. RXBYTES VS.AAL2PATH.P VCLAYER.TXCO RRECTCELLS Counter Description Number of Cells Received on the ATM Layer of the AAL2 Path Number of Bytes Received on the ATM Layer of the AAL2 Path Peak Number of Bytes Received on the ATM Layer of the AAL2 Path Number of Cells Transmitted on the ATM Layer of the AAL2 Path Original Release Earlier than V900R011
67194098
67194099
67194100
Issue 01 (2013-05-04)
2632
Counter ID 67194101
Counter Name VS.AAL2PATH.P VCLAYER.TXBY TES VS.AAL2PATH.P VCLAYER.PEAK. TXBYTES VS.AAL2PATH.P VCLAYER.RXBY TESOFAAL2CPSP KTS
Counter Description Number of Bytes Transmitted on the ATM Layer of the AAL2 Path Peak Number of Bytes Transmitted on the ATM Layer of the AAL2 Path Number of Bytes of AAL2 CPS (Common Part Sublayer) Packets Received on the ATM Layer of the AAL2 Path Number of Bytes of AAL2 CPS (Common Part Sublayer) Packets Transmitted on the ATM Layer of the AAL2 Path Number of Cells Discarded on the ATM Layer of the AAL2 Path Due to Incorrect Header Number of Cells Discarded on the ATM Layer of the AAL2 Path Due to Overflow of Receive Buffer Number of Cells Discarded on the ATM Layer of the AAL2 Path Due to Overflow of Transmit Buffer
67194102
67194103
67194104
VS.AAL2PATH.P VCLAYER.TXBY TESOFAAL2CPSP KTS
67194105
VS.AAL2PATH.P VCLAYER.DROP FORHEADCELLS
67194106
VS.AAL2PATH.P VCLAYER.DROPFORRXOVERFL OWCELLS
67194107
VS.AAL2PATH.P VCLAYER.DROPFORTXOVERFL OWCELLS
None
Issue 01 (2013-05-04)
2633
2.2.1.1 Counters Related to the Number of Cells Received, Transmitted or Dropped on an AAL2PATH Link ATM Layer Counters
Counter ID 67194097 Counter Name VS.AAL2PATH.PVCLAYE R.RXCORRECTCELLS VS.AAL2PATH.PVCLAYE R.TXCORRECTCELLS VS.AAL2PATH.PVCLAYE R.DROPFORHEADCELLS Counter Description Number of Cells Received on the ATM Layer of the AAL2 Path Number of Cells Transmitted on the ATM Layer of the AAL2 Path Number of Cells Discarded on the ATM Layer of the AAL2 Path Due to Incorrect Header Number of Cells Discarded on the ATM Layer of the AAL2 Path Due to Overflow of Receive Buffer Number of Cells Discarded on the ATM Layer of the AAL2 Path Due to Overflow of Transmit Buffer
67194100
67194105
67194106
VS.AAL2PATH.PVCLAYE R.DROPFORRXOVERFLOWCELLS VS.AAL2PATH.PVCLAYE R.DROPFORTXOVERFLOWCELLS
67194107
Description
These counters provide the number of cells received, transmitted or discarded on an AAL2PATH link ATM Layer in the measurement period. They indicate the traffic volume of the AAL2PATH link ATM Layer. The cells measured here are ATM cells. An ATM cell consists of 53 octets.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of IEs received, transmitted or discarded on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2634
Related Features
Counter Name VS.AAL2PATH.PVCLAYE R.RXCORRECTCELLS VS.AAL2PATH.PVCLAYE R.TXCORRECTCELLS VS.AAL2PATH.PVCLAYE R.DROPFORHEADCELLS VS.AAL2PATH.PVCLAYE R.DROPFORRXOVERFLOWCELLS VS.AAL2PATH.PVCLAYE R.DROPFORTXOVERFLOWCELLS Feature ID WRFD-05030104 WRFD-05030104 WRFD-05030104 WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
WRFD-05030104
2.2.1.2 Counters Related to the Number of Bytes Received or Transmitted on an AAL2PATH link ATM Layer Counters
Counter ID 67194098 Counter Name VS.AAL2PATH.PVCLAYE R.RXBYTES VS.AAL2PATH.PVCLAYE R.PEAK.RXBYTES VS.AAL2PATH.PVCLAYE R.TXBYTES VS.AAL2PATH.PVCLAYE R.PEAK.TXBYTES VS.AAL2PATH.PVCLAYE R.RXBYTESOFAAL2CPS PKTS Counter Description Number of Bytes Received on the ATM Layer of the AAL2 Path Peak Number of Bytes Received on the ATM Layer of the AAL2 Path Number of Bytes Transmitted on the ATM Layer of the AAL2 Path Peak Number of Bytes Transmitted on the ATM Layer of the AAL2 Path Number of Bytes of AAL2 CPS(Common Part Sublayer) Packets Received on the ATM Layer of the AAL2 Path
67194099
67194101
67194102
67194103
Issue 01 (2013-05-04)
2635
Counter ID 67194104
Counter Name VS.AAL2PATH.PVCLAYE R.TXBYTESOFAAL2CPS PKTS
Counter Description Number of Bytes of AAL2 CPS(Common Part Sublayer) Packets Transmitted on the ATM Layer of the AAL2 Path
Description
These counters provide the number of bytes received or transmitted on an AAL2PATH link ATM Layer in the measurement period. They indicate the traffic volume of the AAL2PATH link ATM Layer.
Measurement point
Samples are taken every five seconds in the a specific measurement period. The system obtains the number of bytes received and transmitted on the link once every five seconds and obtains the total number of one measurement period. The maximum numbers of bytes received and transmitted is calculated based on the maximum numbers of bytes received and transmitted in a sampling period within the measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.AAL2PATH.PVCLAYE R.RXBYTES VS.AAL2PATH.PVCLAYE R.PEAK.RXBYTES VS.AAL2PATH.PVCLAYE R.TXBYTES VS.AAL2PATH.PVCLAYE R.PEAK.TXBYTES VS.AAL2PATH.PVCLAYE R.RXBYTESOFAAL2CPS PKTS Feature ID WRFD-05030104 WRFD-05030104 WRFD-05030104 WRFD-05030104 WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
Issue 01 (2013-05-04)
2636
Counter Name VS.AAL2PATH.PVCLAYE R.TXBYTESOFAAL2CPS PKTS
Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.3 Measurement of VCL PM on an AAL2 Path (AAL2PATH_VCLPM)

Overview
The Measurement of VCL PM on an AAL2 Path provides the statistics of PM on the ATM layer of the AAL2 path for the AOUc and UOIc boards. The AAL2PATH PM function uses forward performance monitoring (FPM) and backward reporting (BR) cells to monitor the number of transmitted and received cells at both ends of the ATM layer on the AAL2 path. Before viewing the AAL2PATH PM result, run the ACT VCLPM command to activate the PM function on the AAL2 path. The PM function can be activated in three directions: SOURCE, SINK, and BOTH. In the source direction, the source endpoint sends FPM cells to calculate the transmitted cells. In the sink direction, the sink endpoint responds with BR cells to calculate the received cells. BOTH means that an endpoint serves both as a source endpoint and a sink endpoint to send and receive FPM cells. In BOTH mode, both the transmitted and received cells are calculated.
FunctionSubSets
FunctionSubSet AAL2PATH.VCLPM FunctionSubSet Name Measurement Related to VCL PM on an AAL2 Path
2.3.1 Measurement Related to VCL PM on an AAL2 Path (AAL2PATH.VCLPM)

Overview
This measurement uses FPM and BR cells to monitor the ATM transmission quality of a path. In the source direction, FPM cells are sent periodically to indicate the number of transmitted cells and the number of error cells that failed the Bit Interleaved Parity 16 (BIP16) check. In the sink direction, BR cells are transmitted as response to the FPM cells. The BR cells calculate the number of received cells and the number of error cells that fail the BIP16 check. In the source direction, BR cells are used to calculate the number of discarded cells and the number of cells that are inserted by mistake. In the sink direction, FPM cells are used to calculate the number of discarded cells and the number of cells that are inserted by mistake.
Issue 01 (2013-05-04)
2637
Figure 2-3 FPM and BR cells for VCL PM
Counters
Counter ID 73441401 Counter Name VS.AAL2PATH.V CLPM.RXCELL VS.AAL2PATH.V CLPM.TXCELL Counter Description Number of Received VCL PM Cells on an AAL2 Path Number of Transmitted VCL PM Cells on an AAL2 Path Maximum Receive Rate of VCL PM on an AAL2 Path Maximum Transmit Rate of VCL PM on an AAL2 Path Average VCL PM Cell Discard Rate in the Receive Direction of an AAL2 Path Original Release V900R014
73441402
V900R014
73441403
VS.AAL2PATH.V CLPM.PEAK.RXR ATE VS.AAL2PATH.V CLPM.PEAK.TXR ATE VS.AAL2PATH.V CLPM.RX.MEAN. LOSTCELLRATE
V900R014
73441404
V900R014
73441405
V900R014
Issue 01 (2013-05-04)
2638
Counter ID 73441406
Counter Name VS.AAL2PATH.V CLPM.RX.PEAK. LOSTCELLRATE
Counter Description Maximum VCL PM Cell Discard Rate in the Receive Direction of an AAL2 Path Average VCL PM Cell Discard Rate in the Transmit Direction of an AAL2 Path Maximum VCL PM Cell Discard Rate in the Transmit Direction of an AAL2 Path Average Rate of Incorrectly Inserted VCL PM Cells in the Receive Direction of an AAL2 Path Maximum Rate of Incorrectly Inserted VCL PM Cells in the Receive Direction of an AAL2 Path Average Rate of Incorrectly Inserted VCL PM Cells in the Transmit Direction of an AAL2 Path Maximum Rate of Incorrectly Inserted VCL PM Cells in the Transmit Direction of an AAL2 Path Number of VCL PM Error Cell Blocks Failed the BIP16 Check in the Source Direction of an AAL2 Path
73424531
VS.AAL2PATH.V CLPM.TX.MEAN. LOSTCELLRATE
V900R014
73441407
VS.AAL2PATH.V CLPM.TX.PEAK. LOSTCELLRATE
V900R014
73441408
VS.AAL2PATH.V CLPM.RX.MEAN. ERRINSERTCEL LRATE VS.AAL2PATH.V CLPM.RX.PEAK. ERRINSERTCEL LRATE VS.AAL2PATH.V CLPM.TX.MEAN. ERRINSERTCEL LRATE VS.AAL2PATH.V CLPM.TX.PEAK. ERRINSERTCEL LRATE VS.AAL2PATH.V CLPM.SOURCEBI P16CRCERRCEL L
V900R014
73441409
V900R014
73441410
V900R014
73441411
V900R014
73424538
V900R014
Issue 01 (2013-05-04)
2639
Counter ID 73424539
Counter Name VS.AAL2PATH.V CLPM.SINKBIP16 CRCERRCELL
Counter Description Number of VCL PM Error Cell Blocks Failed the BIP16 Check in the Sink Direction of an AAL2 Path
None
2.3.1.1 Number of VCL PM Cells on an AAL2 Path Counters

Counter ID 73441401 73441402 Counter Name VS.AAL2PATH.VCLPM.R XCELL VS.AAL2PATH.VCLPM.T XCELL Counter Description Number of Received VCL PM Cells on an AAL2 Path Number of Transmitted VCL PM Cells on an AAL2 Path
Description
These counters provide the number of received and transmitted cells at the ATM layer along an AAL2 path. Only ATM cells are calculated.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. The RNC measures the number of cells transmitted at the ATM layers along an AAL2 path every 5 seconds and measures the total number at the end of each measurement period.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2640
Related Features
Counter Name VS.AAL2PATH.VCLPM.R XCELL VS.AAL2PATH.VCLPM.T XCELL Feature ID WRFD-05030110 WRFD-05030110 Feature Name F5 F5
2.3.1.2 Maximum Data Rate of VCL PM on an AAL2 Path Counters

Counter ID 73441403 73441404 Counter Name VS.AAL2PATH.VCLPM.P EAK.RXRATE VS.AAL2PATH.VCLPM.P EAK.TXRATE Counter Description Maximum Receive Rate of VCL PM on an AAL2 Path Maximum Transmit Rate of VCL PM on an AAL2 Path
Description
These counters provide the maximum receive and transmit rates on an AAL2 path, indicating the maximum load in the receive and transmit directions on an AAL2 path.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. The RNC measures the number of cells received and transmitted at the ATM layer along an AAL2 path every 5 seconds. It compares and obtains the maximum number of received and transmitted cells per 5 seconds within a measurement period and accordingly calculates the maximum receive and transmit rates. The counters are in the unit of kbit/s, and are calculated with the following formula: Maximum receive and transmit rates = Maximum number of received/transmitted cells x 53 x 8/5/1000.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
2641
Related Features
Counter Name VS.AAL2PATH.VCLPM.P EAK.RXRATE VS.AAL2PATH.VCLPM.P EAK.TXRATE Feature ID WRFD-05030110 WRFD-05030110 Feature Name F5 F5
2.3.1.3 VCL PM Cell Discard Rate on an AAL2 Path Counters

Counter ID 73441405 Counter Name VS.AAL2PATH.VCLPM.R X.MEAN.LOSTCELLRATE VS.AAL2PATH.VCLPM.R X.PEAK.LOSTCELLRATE VS.AAL2PATH.VCLPM.T X.MEAN.LOSTCELLRATE VS.AAL2PATH.VCLPM.T X.PEAK.LOSTCELLRATE Counter Description Average VCL PM Cell Discard Rate in the Receive Direction of an AAL2 Path Maximum VCL PM Cell Discard Rate in the Receive Direction of an AAL2 Path Average VCL PM Cell Discard Rate in the Transmit Direction of an AAL2 Path Maximum VCL PM Cell Discard Rate in the Transmit Direction of an AAL2 Path
73441406
73424531
73441407
Description
These counters provide the average and maximum rates of cells that are discarded in the receive and transmit directions on an AAL2 path. They are used to monitor the error rate of transmission cells on an AAL2 path.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. Every 5 seconds within a measurement period, the RNC measures the number of cells that are discarded in the receive and transmit directions at the ATM layers along an AAL2 path and compares to obtain the maximum number. To obtain the maximum cell discard rates in the receive and transmit directions, in each direction, the RNC divides the maximum number of cells that are discarded within 5 seconds by the total number of cells measured in those directions during the same period. To obtain the average cell discard rates in the receive and transmit directions, in each direction, the RNC divides the number of cells discarded by the total number of cells measured in those directions.
Formula
None
Unit
%
Related Features
Counter Name VS.AAL2PATH.VCLPM.R X.MEAN.LOSTCELLRATE VS.AAL2PATH.VCLPM.R X.PEAK.LOSTCELLRATE VS.AAL2PATH.VCLPM.T X.MEAN.LOSTCELLRATE VS.AAL2PATH.VCLPM.T X.PEAK.LOSTCELLRATE Feature ID WRFD-05030110 Feature Name F5
WRFD-05030110 WRFD-05030110
F5 F5
WRFD-05030110
F5
2.3.1.4 Rate of Incorrectly Inserted VCL PM Cells on an AAL2 Path Counters

Counter ID 73441408 Counter Name VS.AAL2PATH.VCLPM.R X.MEAN.ERRINSERTCELLRATE VS.AAL2PATH.VCLPM.R X.PEAK.ERRINSERTCELLRATE VS.AAL2PATH.VCLPM.T X.MEAN.ERRINSERTCELLRATE VS.AAL2PATH.VCLPM.T X.PEAK.ERRINSERTCELLRATE Counter Description Average Rate of Incorrectly Inserted VCL PM Cells in the Receive Direction of an AAL2 Path Maximum Rate of Incorrectly Inserted VCL PM Cells in the Receive Direction of an AAL2 Path Average Rate of Incorrectly Inserted VCL PM Cells in the Transmit Direction of an AAL2 Path Maximum Rate of Incorrectly Inserted VCL PM Cells in the Transmit Direction of an AAL2 Path
73441409
73441410
73441411
Issue 01 (2013-05-04)
2643
Description
These counters provide the average and maximum rates of cells that are incorrectly inserted in the receive and transmit directions on an AAL2 path. They are used to monitor the error rate of transmission cells on an AAL2 path.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. Every 5 seconds within a measurement period, the RNC measures the number of cells that are incorrectly inserted in the receive and transmit directions at the ATM layers along an AAL2 path and compares to obtain the maximum number. To obtain the maximum rates of incorrectly inserted cells in the receive and transmit directions, in each direction, the RNC divides the maximum number of cells that are incorrectly inserted within 5 seconds by the total number of cells measured in those directions during the same period. To obtain the average rates of incorrectly inserted cells in the receive and transmit directions, in each direction, the RNC divides the total number of incorrectly inserted cells by the total number of measured cells in those directions during a measurement period.
Formula
None
Unit
%
Related Features
Counter Name VS.AAL2PATH.VCLPM.R X.MEAN.ERRINSERTCELLRATE VS.AAL2PATH.VCLPM.R X.PEAK.ERRINSERTCELLRATE VS.AAL2PATH.VCLPM.T X.MEAN.ERRINSERTCELLRATE VS.AAL2PATH.VCLPM.T X.PEAK.ERRINSERTCELLRATE Feature ID WRFD-05030110 Feature Name F5
WRFD-05030110
F5
WRFD-05030110
F5
WRFD-05030110
F5
2.3.1.5 Number of Error VCL PM Cell Blocks Failed BIP16 Check on an AAL2 Path
Issue 01 (2013-05-04)
2644
Counters
Counter ID 73424538 Counter Name VS.AAL2PATH.VCLPM.S OURCEBIP16CRCERRCELL VS.AAL2PATH.VCLPM.SI NKBIP16CRCERRCELL Counter Description Number of VCL PM Error Cell Blocks Failed the BIP16 Check in the Source Direction of an AAL2 Path Number of VCL PM Error Cell Blocks Failed the BIP16 Check in the Sink Direction of an AAL2 Path
73424539
Description
These counters provide the number of error cell blocks that fail the BIP16 check in the receive and transmit directions on an AAL2 path. They are used to monitor the error rate of transmission cells on an AAL2 path.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. The RNC measures the number of error cell blocks that fail the BIP16 check in the source and link directions at the ATM layer along an AAL2 path every 5 seconds and calculates the total number at the end of each measurement period. In each cell block measured for this counter, none of the cells is discarded or incorrectly inserted.
Formula
None
Unit
None
Related Features
Counter Name VS.AAL2PATH.VCLPM.S OURCEBIP16CRCERRCELL VS.AAL2PATH.VCLPM.SI NKBIP16CRCERRCELL Feature ID WRFD-05030110 Feature Name F5
WRFD-05030110
F5
Issue 01 (2013-05-04)
2645
2.4 Measurement of IP Transport Adjacent Node Connection Performance(ANI_IP)

Overview
IP transport adjacent node connection performance measurement indicates the performance of IP transport adjacent nodes.
FunctionSubSets
FunctionSubSet ANIIPCONN ANIIPTRM FunctionSubSet Name IP Transport Adjacent Node Connection Measurement IP Transport Adjacent Node Resource Operation Measurement
2.4.1 IP Transport Adjacent Node Connection Measurement (ANIIPCONN)

Overview
IP transport adjacent node connection measurement helps monitor the connections to IP transport adjacent nodes and analyze system transmission quality to maintain system stability and reliability. All counters of this function subset are not measured for the adjacent node over the IuPS interface. Figure 2-4 Physical bearer of the IP adjacent node
Issue 01 (2013-05-04)
2646
Counters
Counter ID 67194793 Counter Name VS.ANI.IP.Conn.E stab.Att Counter Description T6501:Number of Connection Setup Requests for IP Transport from the Transport Layer to the Radio Network Layer on the IP Transport Adjacent Node T6502:Number of Successful IP Connection Setups Initiated by the Transport Layer on IP Transport Adjacent Node T6503:Number of IP Connection Modifications T6504:Number of Successful IP Modifications Initiated by the Transport Layer on IP Transport Adjacent Node Original Release Earlier than V900R011
67194794
VS.ANI.IP.Conn.E stab.Succ
67194795
VS.ANI.IP.Conn.M odify.Att VS.ANI.IP.Conn.M odify.Succ
67194796
None
2.4.1.1 Number of IP Connection Setup Requests Received by IP Transport Adjacent Node
Issue 01 (2013-05-04)
2647
Counters
Counter ID 67194793 Counter Name VS.ANI.IP.Conn.Estab.Att Counter Description T6501:Number of Connection Setup Requests for IP Transport from the Transport Layer to the Radio Network Layer on the IP Transport Adjacent Node
Description
This counter provides the number of connection setup requests for IP transport that the transport layer receives from the radio network layer in the measurement period.
Measurement point
When the UE wants to set up services in an IP cell, the measurement value is incremented by one after the radio network layer sends an IP connection setup request message.
Formula
None
Unit
None
Related Features
Counter Name VS.ANI.IP.Conn.Estab.Att Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.4.1.2 Number of Successful IP Connections for IP Transport Adjacent Node
Issue 01 (2013-05-04)
2648
Counters
Counter ID 67194794 Counter Name VS.ANI.IP.Conn.Estab.Succ Counter Description T6502:Number of Successful IP Connection Setups Initiated by the Transport Layer on IP Transport Adjacent Node
Description
This counter provides the number of successful IP connection setups initiated by the transport layer in the measurement period.
Measurement point
If the user wants to set up services in an IP cell, the radio network layer sends an IP connection setup request message. The measurement value is incremented by one when the IP connection is successfully set up.
Formula
None
Unit
None
Related Features
Counter Name VS.ANI.IP.Conn.Estab.Succ Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.4.1.3 Number of IP Connection Modifications Counters

Counter ID 67194795 Counter Name VS.ANI.IP.Conn.Modify.At t Counter Description T6503:Number of IP Connection Modifications
Issue 01 (2013-05-04)
2649
Description
This counter provides the number of IP connection modification requests sent by the radio network layer to the transport layer in the measurement period.
Measurement point
This counter is incremented by one when the radio network layer initiates a request for modification of an IP connection.
Formula
None
Unit
None
Related Features
Counter Name VS.ANI.IP.Conn.Modify.At t Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.4.1.4 Number of Successful IP Connection Modifications for IP Transport Adjacent Node Counters
Counter ID 67194796 Counter Name VS.ANI.IP.Conn.Modify.Su cc Counter Description T6504:Number of Successful IP Modifications Initiated by the Transport Layer on IP Transport Adjacent Node
Description
This counter provides the number of successful IP transport bandwidth modifications performed by the transport layer in the measurement period.
Measurement point
The measurement value is incremented by one when the radio network layer initiates an IP transport bandwidth modification request and the modification is successful.
Formula
None
Unit
None
Related Features
Counter Name VS.ANI.IP.Conn.Modify.Su cc Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.4.2 IP Transport Adjacent Node Resource Operation Measurement(ANIIPTRM)

Overview
IP transport adjacent node resource operation measurement provides the counters related to the number of failed resource allocations due to insufficient bandwidth on the IP transport adjacent node, forward and backward bandwidth allocated to an IP adjacent node. The measurement also helps analyze the transmission quality to maintain the system stability and reliability.
Counters
Counter ID 67194787 Counter Name VS.ANI.IP.AttResAlloc Counter Description T6507:Number of Requests for Resource Allocation on the IP Transport Adjacent Node T6508:Number of Successful Resource Allocations on the IP Transport Adjacent Node T6509:IP Path Forward Bandwidth Allocated to IP Transport Adjacent Node Original Release V900R014
67194788
VS.ANI.IP.SuccResAlloc
V900R014
67204475
OS.ANI.IP.AllocedFwd
Issue 01 (2013-05-04)
2651
Counter ID 67204476
Counter Name OS.ANI.IP.AllocedBwd
Counter Description T6510:IP Path Backward Bandwidth Allocated to IP Transport Adjacent Node T6511:Number of Failed Resource Allocations Due to Insufficient Bandwidth on the IP Transport Adjacent Node
67196162
VS.ANI.IP.FailResAllocForBwLimit
None
2.4.2.1 Number of Requests for Resource Allocation on the IP Transport Adjacent Node Counters
Counter ID 67194787 Counter Name VS.ANI.IP.AttResAlloc Counter Description T6507:Number of Requests for Resource Allocation on the IP Transport Adjacent Node
Description
This counter provides the number of IP transport resource requests sent by the radio network layer to the transport layer in the measurement period.
Measurement point
This counter is incremented by one when the transport layer receives an IP transport resource request from the radio network layer.
Formula
None
Unit
None
Related Features
Counter Name VS.ANI.IP.AttResAlloc Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.4.2.2 Number of Successful Resource Allocations on the IP Transport Adjacent Node Counters
Counter ID 67194788 Counter Name VS.ANI.IP.SuccResAlloc Counter Description T6508:Number of Successful Resource Allocations on the IP Transport Adjacent Node
Description
This counter provides the number of successful IP transport resource requests sent by the radio network layer to the transport layer in the measurement period.
Measurement point
This counter is incremented by one when the transport layer receives an IP resource request from the radio network layer and the resource allocation is successful.
Formula
None
Unit
None
Related Features
Counter Name VS.ANI.IP.SuccResAlloc Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
Issue 01 (2013-05-04)
2653
2.4.2.3 IP Path Forward Bandwidth Allocated to IP Transport Adjacent Node Counters

Counter ID 67204475 Counter Name OS.ANI.IP.AllocedFwd Counter Description T6509:IP Path Forward Bandwidth Allocated to IP Transport Adjacent Node
Description
This counter provides the IP path forward bandwidth (physical layer bandwidth) allocated to an IP transport adjacent node, that is, the average forward bandwidth sampled in the measurement period.
Measurement point
In the measurement period, the system automatically samples the IP path forward bandwidth allocated to an adjacent node of the Iub, Iur, Iu, Abis, or A interface. The sampling period is 15 seconds. At the end of the measurement period, the system divides the accumulated IP path forward bandwidth by the number of samples to obtain the average IP path forward bandwidth allocated to an adjacent node of the Iub, Iur, or Iu interface.This counter is invalid when the real flow access control switch is turned on.
Formula
None
Unit
bit/s
Related Features
Counter Name OS.ANI.IP.AllocedFwd Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.4.2.4 IP Path Backward Bandwidth Allocated to IP Transport Adjacent Node
Issue 01 (2013-05-04)
2654
Counters
Counter ID 67204476 Counter Name OS.ANI.IP.AllocedBwd Counter Description T6510:IP Path Backward Bandwidth Allocated to IP Transport Adjacent Node
Description
This counter provides the IP path backward bandwidth (physical layer bandwidth) allocated to an IP transport adjacent node, that is, the average backward bandwidth sampled in the measurement period.
Measurement point
In the measurement period, the system automatically samples the IP path backward bandwidth allocated to an adjacent node of the Iub, Iur, Iu, Abis, or A interface. The sampling period is 15 seconds. At the end of the measurement period, the system divides the accumulated IP path backward bandwidth by the number of samples to obtain the average IP path backward bandwidth allocated to an adjacent node of the Iub, Iur, or Iu interface.This counter is invalid when the real flow access control switch is turned on.
Formula
None
Unit
bit/s
Related Features
Counter Name OS.ANI.IP.AllocedBwd Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.4.2.5 Number of Failed Resource Allocations Due to Insufficient Bandwidth on the IP Transport Adjacent Node
Issue 01 (2013-05-04)
2655
Counters
Counter ID 67196162 Counter Name VS.ANI.IP.FailResAllocForBwLimit Counter Description T6511:Number of Failed Resource Allocations Due to Insufficient Bandwidth on the IP Transport Adjacent Node
Description
This counter provides the number of failed resource allocation requests due to insufficient bandwidth after the transport layer receives resource allocation requests from the radio network layer.
Measurement point
The radio network layer initiates an IP resource allocation request. This counter is incremented by one if the request fails due to insufficient bandwidth.
Formula
None
Unit
None
Related Features
Counter Name VS.ANI.IP.FailResAllocForBwLimit Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.5 Measurement of QAAL2 Adjacent Node Performance (ANI_QAAL2)

Overview
The measurement object ANI_QAAL2 is used to measure the QAAL2 adjacent nodes.
Issue 01 (2013-05-04)
2656
FunctionSubSets
FunctionSubSet QAAL2 FunctionSubSet Name QAAL2 Measurement
2.5.1 QAAL2 Measurement(QAAL2)

Overview
The QAAL2 measurement helps monitor the ATM Adaptation Layer 2 (AAL2) connection and release to QAAL2 adjacent nodes. QAAL2 is the control plane protocol of AAL2 to control the setup and release of AAL2 connections. QAAL2 adjacent nodes of an RNC include NodeB, MSC and neighboring RNC (NRNC). Figure 2-5 Physical bearer of the QAAL2 adjacent node
Issue 01 (2013-05-04)
2657
Counters
Counter ID 67190053 Counter Name VS.AAL2.CAC.Att Counter Description Number of AAL2 Path Resource Admissions Number of Successful AAL2 Path Admissions Number of RLC Messages Received by the QAAL2 Due to No Route at the Remote End Number of RLC Messages Received by QAAL2 Due to No AAL2 Path Configued at the Remote End Number of RLC Messages Received by QAAL2 Due to No CID Available at the Remote End Number of RLC Messages Received by QAAL2 Due to Remote Network Fault, Remote Temporary Failure, or Remote Normal Releases Number of RLC Messages Received by QAAL2 Due to Switch Congestion at the Remote End Number of RLC Messages Received by QAAL2 Due to Timer Expiry at the Remote End Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67190054
VS.AAL2.CAC.Suc c VS.QAAL2.Est.RL C.NoRoute.Rx
67190055
67190056
VS.QAAL2.Est.RL C.NoPath.Rx
67190057
VS.QAAL2.Est.RL C.NoCID.Rx
67190058
VS.QAAL2.Est.RL C.Fail.Rx
67190059
VS.QAAL2.Est.RL C.Cong.Rx
67190060
VS.QAAL2.Est.RL C.RecovOut.Rx
Issue 01 (2013-05-04)
2658
Counter ID 67190061
Counter Name VS.QAAL2.Est.RL C.NoRoute.Tx
Counter Description Number of RLC Messages Sent by the QAAL2 Due to No Route at the Remote End Number of RLC Messages Sent by the QAAL2 Due to No AAL2 Path Configured Number of RLC Messages Sent by the QAAL2 Due to No CID Available Number of RLC Messages Sent by the QAAL2 Due to Network Failure, Unspecified Reason, or Temporary Failure Number of RLC Messages Sent by QAAL2 Due to Switch Congestion Number of RLC Messages Sent by QAAL2 Due to Timer Expiry Number of AAL2 Connection Establishment Requests Sent by the QAAL2 Number of AAL2 Connection Establishment Requests Received by the QAAL2
67190062
VS.QAAL2.Est.RL C.NoPath.Tx
67190063
VS.QAAL2.Est.RL C.NoCID.Tx
67190064
VS.QAAL2.Est.RL C.Fail.Tx
67190065
VS.QAAL2.Est.RL C.Cong.Tx
67190066
VS.QAAL2.Est.RL C.RecovOut.Tx
67183361
VS.QAAL2.ERQ.T x
67183362
VS.QAAL2.ERQ.R x
Issue 01 (2013-05-04)
2659
Counter ID 67183363
Counter Name VS.QAAL2.Est.RL C.Rx
Counter Description Number of AAL2 Connection Release Confirmations (RLCs) Received by the QAAL2 After the QAAL2 Sends the ERQ Message Number of ECF Messages Received by the QAAL2 After the QAAL2 Sends the ERQ Message Number of ECF Messages Sent by the QAAL2 After the QAAL2 Receives the ERQ Message Number of RLC Messages Sent by the QAAL2 After the QAAL2 Receives the ERQ Message Number of AAL2 Connection Release Requests (RELs) Sent by the QAAL2 Number of AAL2 Connection Release Requests (RELs) Received by the QAAL2 Number of AAL2 Connection Release Confirmations (RLCs) Received by the QAAL2 After the QAAL2 Sends the REL Message Number of RLC Messages Sent by the QAAL2 After the QAAL2 Receives the REL Message
67183364
VS.QAAL2.Est.EC F.Rx
67183365
VS.QAAL2.Est.EC F.Tx
67183366
VS.QAAL2.Est.RL C.Tx
67183367
VS.QAAL2.Rel.Tx
67183368
VS.QAAL2.Rel.Rx
67183369
VS.QAAL2.Rel.RL C.Rx
67183370
VS.QAAL2.Rel.RL C.Tx
Issue 01 (2013-05-04)
2660
Counter ID 67190067
Counter Name VS.QAAL2.RxModRej
Counter Description Number of AAL2 Connection Modification Rejections (MORs) Received by the QAAL2 Number of MOR Messages Sent by the QAAL2 After the QAAL2 Receives the MOD Message Number of AAL2 Connection Modification Requests (MODs) Sent by the QAAL2 Number of AAL2 Connection Modification Requests (MODs) Received by the QAAL2 Number of Active AAL2 Connections to an QAAL2 Adjacent Node Mean Forward Bandwidth of AAL2 Path Allocated to an Adjacent Node Mean Backward Bandwidth of AAL2 Path Allocated to an Adjacent Node Maximum Value of AAL2 Path Forward Bandwidth Allocated to an Adjacent Node
67190068
VS.QAAL2.TxModRej
67190553
VS.QAAL2.TxMod
67190554
VS.QAAL2.RxMod
67199677
VS.QAAL2.Act.Co n
67190555
VS.QAAL2.Alloced Fwd.AAL2BitRate
67190558
VS.QAAL2.Alloced Bwd.AAL2BitRate
67190562
VS.QAAL2.Alloced MaxFwd.AAL2Bit Rate.Value
Issue 01 (2013-05-04)
2661
Counter ID 67190565
Counter Name VS.QAAL2.Alloced MaxBwd.AAL2Bit Rate.Value
Counter Description Maximum Value of AAL2 Path Backward Bandwidth Allocated to an Adjacent Node Number of RLC Messages Sent by the QAAL2 Due to No Bandwidth Available
67196149
VS.QAAL2.Est.RL C.NoBitRate.Tx
None
2.5.1.1 Number of Resource Allocation Requests by QAAL2 Counters

Counter ID 67190053 Counter Name VS.AAL2.CAC.Att Counter Description Number of AAL2 Path Resource Admissions
Description
This counter provides the number of PATH and CID resource admissions and allocations when the QAAL2 receives AAL2 connection setup requests from the upper layer.
Measurement point
In the measurement period, the counter is incremented by one when the QAAL2 performs path and CID resource admission and allocation after the QAAL2 receives an AAL2 connection setup request from the upper layer.
Formula
None
Unit
None
Related Features
Counter Name VS.AAL2.CAC.Att Feature ID WRFD-05030106 Feature Name Call Admission Based on Used AAL2 Path Bandwidth
2.5.1.2 Number of Successful Resource Allocations by QAAL2 Counters

Counter ID 67190054 Counter Name VS.AAL2.CAC.Succ Counter Description Number of Successful AAL2 Path Admissions
Description
This counter provides the number of successful path and CID resource admissions and allocations when the QAAL2 receives AAL2 connection setup requests from the upper layer.
Measurement point
In the measurement period, the counter is incremented by one when the QAAL2 succeeds in performing path and CID resource admission and allocation after the QAAL2 receives an AAL2 connection setup request from the upper layer.
Formula
None
Unit
None
Related Features
Counter Name VS.AAL2.CAC.Succ Feature ID WRFD-05030106 Feature Name Call Admission Based on Used AAL2 Path Bandwidth
2.5.1.3 Number of RLC messages received by the QAAL2
Issue 01 (2013-05-04)
2663
Counters
Counter ID 67190055 Counter Name VS.QAAL2.Est.RLC.NoRo ute.Rx Counter Description Number of RLC Messages Received by the QAAL2 Due to No Route at the Remote End Number of RLC Messages Received by QAAL2 Due to No AAL2 Path Configued at the Remote End Number of RLC Messages Received by QAAL2 Due to No CID Available at the Remote End Number of RLC Messages Received by QAAL2 Due to Remote Network Fault, Remote Temporary Failure, or Remote Normal Releases Number of RLC Messages Received by QAAL2 Due to Switch Congestion at the Remote End Number of RLC Messages Received by QAAL2 Due to Timer Expiry at the Remote End
67190056
VS.QAAL2.Est.RLC.NoPat h.Rx
67190057
VS.QAAL2.Est.RLC.NoCI D.Rx
67190058
VS.QAAL2.Est.RLC.Fail.R x
67190059
VS.QAAL2.Est.RLC.Cong. Rx
67190060
VS.QAAL2.Est.RLC.Recov Out.Rx
Description
These counters provide the number of AAL2 connection release confirmations received by the RNC.
Measurement point
The measurement is triggered when the QAAL2 receives a release confirmation (RLC) message from the adjacent node.
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.Est.RLC.NoRo ute.Rx VS.QAAL2.Est.RLC.NoPat h.Rx VS.QAAL2.Est.RLC.NoCI D.Rx VS.QAAL2.Est.RLC.Fail.R x VS.QAAL2.Est.RLC.Cong. Rx VS.QAAL2.Est.RLC.Recov Out.Rx Feature ID WRFD-05030104 WRFD-05030104 WRFD-05030104 WRFD-05030104 WRFD-05030104 WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.4 Number of RLC messages sent by the QAAL2 Counters

Counter ID 67190061 Counter Name VS.QAAL2.Est.RLC.NoRo ute.Tx VS.QAAL2.Est.RLC.NoPat h.Tx VS.QAAL2.Est.RLC.NoCI D.Tx VS.QAAL2.Est.RLC.Fail.T x Counter Description Number of RLC Messages Sent by the QAAL2 Due to No Route at the Remote End Number of RLC Messages Sent by the QAAL2 Due to No AAL2 Path Configured Number of RLC Messages Sent by the QAAL2 Due to No CID Available Number of RLC Messages Sent by the QAAL2 Due to Network Failure, Unspecified Reason, or Temporary Failure Number of RLC Messages Sent by QAAL2 Due to Switch Congestion Number of RLC Messages Sent by QAAL2 Due to Timer Expiry
67190062
67190063
67190064
67190065
VS.QAAL2.Est.RLC.Cong. Tx VS.QAAL2.Est.RLC.Recov Out.Tx
67190066
Issue 01 (2013-05-04)
2665
Counter ID 67196149
Counter Name VS.QAAL2.Est.RLC.NoBit Rate.Tx
Counter Description Number of RLC Messages Sent by the QAAL2 Due to No Bandwidth Available
Description
These counters provide the number of AAL2 connection release confirmations sent by the QAAL2.
Measurement point
The measurement is triggered when the QAAL2 sends a release confirmation (RLC) message to an adjacent node.
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.Est.RLC.NoRo ute.Tx VS.QAAL2.Est.RLC.NoPat h.Tx VS.QAAL2.Est.RLC.NoCI D.Tx VS.QAAL2.Est.RLC.Fail.T x VS.QAAL2.Est.RLC.Cong. Tx VS.QAAL2.Est.RLC.Recov Out.Tx VS.QAAL2.Est.RLC.NoBit Rate.Tx Feature ID WRFD-05030104 WRFD-05030104 WRFD-05030104 WRFD-05030104 WRFD-05030104 WRFD-05030104 WRFD-05030106 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Call Admission Based on Used AAL2 Path Bandwidth
2.5.1.5 Number of AAL2 Connection Establishment Requests Sent by the QAAL2

Counters
Counter ID 67183361 Counter Name VS.QAAL2.ERQ.Tx Counter Description Number of AAL2 Connection Establishment Requests Sent by the QAAL2
Description
This counter provides the number of AAL2 connection establishment requests sent by the QAAL2.
Measurement point
In the measurement period, the counter is incremented by one at point A, as shown in Figure 1. When the RNC sends an AAL2 connection establishment request (ERQ) message to the adjacent node, for example, the NodeB, the RNC increments the measurement value of this item by one. Figure 2-6 Successful AAL2 connection establishment procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.ERQ.Tx Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.6 Number of AAL2 Connection Establishment Requests Received by the QAAL2 Counters
Counter ID 67183362 Counter Name VS.QAAL2.ERQ.Rx Counter Description Number of AAL2 Connection Establishment Requests Received by the QAAL2
Description
This counter provides the number of AAL2 connection establishment requests received by the QAAL2 from an adjacent node. Generally, the RNC receives an AAL2 connection establishment request on the Iur interface only. On the Iub and Iu interfaces, the RNC only sends an AAL2 connection establishment request.
Measurement point
In the measurement period, the counter is incremented by one at point A, as shown in Figure 1. When the RNC receives an AAL2 connection ERQ message from the adjacent node, for example, the adjacent RNC, the RNC increments the measurement value of this item by one.
Issue 01 (2013-05-04)
2668
Figure 2-7 Successful AAL2 connection establishment procedure initiated by an adjacent node
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.ERQ.Rx Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.7 Number of AAL2 Connection Establishment Request Rejections Received by the QAAL2
Issue 01 (2013-05-04)
2669
Counters
Counter ID 67183363 Counter Name VS.QAAL2.Est.RLC.Rx Counter Description Number of AAL2 Connection Release Confirmations (RLCs) Received by the QAAL2 After the QAAL2 Sends the ERQ Message
Description
This counter provides the number of AAL2 connection establishment request rejections received by the QAAL2 from an adjacent node.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When the RNC receives an AAL2 connection establishment rejection (RLC) message from the adjacent node, for example, the NodeB, after it sends the NodeB an AAL2 connection ERQ message, the RNC increments the measurement value of this counter by one. Figure 2-8 Failed AAL2 connection establishment procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.Est.RLC.Rx Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.8 Number of AAL2 Connection Establishment Confirmations Received by the QAAL2 Counters
Counter ID 67183364 Counter Name VS.QAAL2.Est.ECF.Rx Counter Description Number of ECF Messages Received by the QAAL2 After the QAAL2 Sends the ERQ Message
Description
This counter provides the number of AAL2 connection establishment confirmations that the QAAL2 receives from an adjacent node.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When the RNC receives an AAL2 connection establishment confirmation (ECF) message from the adjacent node for example, the NodeB, after it sends the NodeB an ERQ message, the RNC increments the measurement value of this counter by one.
Issue 01 (2013-05-04)
2671
Figure 2-9 Successful AAL2 connection establishment procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.Est.ECF.Rx Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.9 Number of AAL2 Connection Establishment Confirmations Sent by the QAAL2
Issue 01 (2013-05-04)
2672
Counters
Counter ID 67183365 Counter Name VS.QAAL2.Est.ECF.Tx Counter Description Number of ECF Messages Sent by the QAAL2 After the QAAL2 Receives the ERQ Message
Description
These counters provide the number of AAL2 connection establishment confirmations that the QAAL2 sends to an adjacent node.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When receiving an ERQ message from an adjacent node, for example, a neighboring RNC, the RNC responds with an ECF message. In this case, the measurement value of this counter is incremented by one. Figure 2-10 Successful AAL2 connection establishment procedure initiated by an adjacent node
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.Est.ECF.Tx Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.10 Number of AAL2 Connection Establishment Rejections Sent by the QAAL2 Counters
Counter ID 67183366 Counter Name VS.QAAL2.Est.RLC.Tx Counter Description Number of RLC Messages Sent by the QAAL2 After the QAAL2 Receives the ERQ Message
Description
These counters provide the number of AAL2 connection establishment rejections sent by the QAAL2.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When receiving an ERQ message from an adjacent node, for example, a neighboring RNC, the RNC responds with an RLC message. In this case, the measurement value of this counter is incremented by one.
Issue 01 (2013-05-04)
2674
Figure 2-11 Failed AAL2 connection establishment procedure initiated by an adjacent node
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.Est.RLC.Tx Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.11 Number of AAL2 Connection Releases Initiated by QAAL2 Counters

Counter ID 67183367 Counter Name VS.QAAL2.Rel.Tx Counter Description Number of AAL2 Connection Release Requests (RELs) Sent by the QAAL2
2675
Issue 01 (2013-05-04)
Description
This counter provides the number of AAL2 connection release requests sent by the QAAL2.
Measurement point
In the measurement period, the counter is incremented by one at point A, as shown in Figure 1. When the RNC sends an AAL2 connection release (REL) message to an adjacent node, for example, the NodeB, the RNC increments the measurement value of this counter by one. Figure 2-12 AAL2 connection release procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.Rel.Tx Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
Issue 01 (2013-05-04)
2676
2.5.1.12 Number of AAL2 Connection Releases Received by the QAAL2 Counters

Counter ID 67183368 Counter Name VS.QAAL2.Rel.Rx Counter Description Number of AAL2 Connection Release Requests (RELs) Received by the QAAL2
Description
Measurement point
In the measurement period, the counter is incremented by one at point A, as shown in Figure 1. When the RNC receives an AAL2 connection release (REL) message from an adjacent node, for example, the NodeB, the RNC increments the measurement value of this counter by one. Figure 2-13 AAL2 connection release procedure initiated by an adjacent node
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.Rel.Rx Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.13 Number of AAL2 Connection Confirmations Received by the QAAL2 Counters

Counter ID 67183369 Counter Name VS.QAAL2.Rel.RLC.Rx Counter Description Number of AAL2 Connection Release Confirmations (RLCs) Received by the QAAL2 After the QAAL2 Sends the REL Message
Description
This counter provides the number of AAL2 connection release confirmations received by the QAAL2.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When the RNC receives an AAL2 connection release confirmation (RLC) message from an adjacent node, for example, the NodeB, after it sends an AAL2 connection release (REL) message to the NodeB, the RNC increments the measurement value of this counter by one.
Issue 01 (2013-05-04)
2678
Figure 2-14 AAL2 connection release procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.Rel.RLC.Rx Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.14 Number of AAL2 Connection Releases Confirmation Initiated by the QAAL2
Issue 01 (2013-05-04)
2679
Counters
Counter ID 67183370 Counter Name VS.QAAL2.Rel.RLC.Tx Counter Description Number of RLC Messages Sent by the QAAL2 After the QAAL2 Receives the REL Message
Description
These counters provide the number of AAL2 connection release confirmations sent by the QAAL2 to an adjacent node.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When RNC the sends an AAL2 connection release confirmation (RLC) message to an adjacent node, for example, the NodeB, after it receives an AAL2 connection release (REL) message from the NodeB, the RNC increments the measurement value of this counter by one. Figure 2-15 AAL2 connection release procedure initiated by an adjacent node
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.Rel.RLC.Tx Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.15 Number of AAL2 Connection Modification Request Rejections Received by the QAAL2 Counters
Counter ID 67190067 Counter Name VS.QAAL2.RxModRej Counter Description Number of AAL2 Connection Modification Rejections (MORs) Received by the QAAL2
Description
This counter provides the number of AAL2 connection modification request rejections received by the QAAL2 from an adjacent node.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When the RNC receives from an adjacent node, for example, a NodeB, an MOR message (AAL2 connection modification rejection message) after it sends an MOD message (AAL2 connection modification request message) to the NodeB, the RNC increments the measurement value of this counter by one.
Issue 01 (2013-05-04)
2681
Figure 2-16 Failed AAL2 connection modification procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.RxModRej Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.16 Number of AAL2 Connection Modification Rejections Sent by the QAAL2 Counters
Counter ID 67190068 Counter Name VS.QAAL2.TxModRej Counter Description Number of MOR Messages Sent by the QAAL2 After the QAAL2 Receives the MOD Message
2682
Issue 01 (2013-05-04)
Description
This counter provides the number of AAL2 connection modification rejections sent by the QAAL2.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When the RNC sends an MOR message (AAL2 connection modification rejection message) to an adjacent node, for example, another RNC, after it receives an MOD message (AAL2 connection modification request) from another RNC, the RNC increments the measurement value of this counter by one. Figure 2-17 Failed AAL2 connection modification procedure initiated by the RNC
Formula
None
Unit
None
Issue 01 (2013-05-04)
2683
Related Features
Counter Name VS.QAAL2.TxModRej Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.17 Number of AAL2 Connection Modification Requests Sent by the QAAL2 Counters
Counter ID 67190553 Counter Name VS.QAAL2.TxMod Counter Description Number of AAL2 Connection Modification Requests (MODs) Sent by the QAAL2
Description
This counter provides the number of AAL2 connection modification requests sent by the QAAL2.
Measurement point
The counter is incremented by one after the RNC sends an MOD message (AAL connection modification request message) to an adjacent node.
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.TxMod Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.18 Number of AAL2 Connection Modification Requests Received by the QAAL2

Counters
Counter ID 67190554 Counter Name VS.QAAL2.RxMod Counter Description Number of AAL2 Connection Modification Requests (MODs) Received by the QAAL2
Description
This counter provides the number of AAL2 connection modification requests received by the QAAL2 from an adjacent node.
Measurement point
The counter is incremented by one when the RNC receives an MOD message (AAL connection modification request message) from an adjacent node.
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.RxMod Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.19 Average Number of Active AAL2 Connections to an QAAL2 Adjacent Node Counters
Counter ID 67199677 Counter Name VS.QAAL2.Act.Con Counter Description Number of Active AAL2 Connections to an QAAL2 Adjacent Node
Issue 01 (2013-05-04)
2685
Description
This counter provides the average number of active AAL2 connections to a QAAL2 adjacent node at all sampling points in a measurement period.
Measurement point
The system periodically takes samples from the number of active AAL2 connections to an adjacent node. The sampling period is 15 seconds. At the end of the measurement period, the system divides the accumulated number of active AAL2 connections to an adjacent node by the number of samples to obtain the average number.
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2.Act.Con Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.5.1.20 AAL2 Path Bandwidth Allocated to an Adjacent Node Counters

Counter ID 67190555 Counter Name VS.QAAL2.AllocedFwd.A AL2BitRate VS.QAAL2.AllocedBwd.A AL2BitRate VS.QAAL2.AllocedMaxFw d.AAL2BitRate.Value Counter Description Mean Forward Bandwidth of AAL2 Path Allocated to an Adjacent Node Mean Backward Bandwidth of AAL2 Path Allocated to an Adjacent Node Maximum Value of AAL2 Path Forward Bandwidth Allocated to an Adjacent Node Maximum Value of AAL2 Path Backward Bandwidth Allocated to an Adjacent Node
67190558
67190562
67190565
VS.QAAL2.AllocedMaxBw d.AAL2BitRate.Value
Issue 01 (2013-05-04)
2686
Description
These counters provide the average or maximum value of allocated forward or backward bit rate of AAL2 path to the QAAL2 adjacent node of an interface (Iub, Iur or Iu) at all the sampling points in a measurement period.
Measurement point
The RNC takes samples from the value of allocated forward or backward bit rate of AAL2 path to the QAAL2 adjacent node of an interface (Iub, Iur or Iu) every 15 seconds. At the end of the measurement period, the system divides the sum of the allocated forward or backward bit rate of AAL2 paths by the number of samples to obtain the average or maximum value.
Formula
None
Unit
bit
Related Features
Counter Name VS.QAAL2.AllocedFwd.A AL2BitRate VS.QAAL2.AllocedBwd.A AL2BitRate VS.QAAL2.AllocedMaxFw d.AAL2BitRate.Value VS.QAAL2.AllocedMaxBw d.AAL2BitRate.Value Feature ID WRFD-05030106 WRFD-05030106 WRFD-05030106 WRFD-05030106 Feature Name Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth
2.6 Measurement of Dual-Stack Transport Adjacent Node Performance(ANI_QAAL2_IP)

Overview
Dual-stack transport adjacent node performance measurement indicates the performance of the dual-stack transport adjacent node.
Issue 01 (2013-05-04)
2687
FunctionSubSets
FunctionSubSet IPPART QAAL2IP QAAL2PART FunctionSubSet Name Dual-Stack Transport Adjacent Node IP Part Measurement Dual-Stack Transport Adjacent Node Measurement Dual-Stack Transport Adjacent Node QAAL2 Part Measurement
2.6.1 Dual-Stack Transport Adjacent Node IP Part Measurement (IPPART)

Overview
Dual-stack transport adjacent node IP part measurement is used to measure the IP connections and allocate resources on a dual-stack adjacent node.
Counters
Counter ID 67194658 Counter Name VS.IPPART.Node. Conn.Estab.Att Counter Description Number of Connection Setup Requests for IP Transport from the Transport Layer to the Radio Network Layer on the DualStack Transport Adjacent Node Number of Successful IP Connection Setups Initiated by the Transport Layer on the Dual-Stack Transport Adjacent Node Number of IP Connection Modifications on the Dual-Stack Transport Adjacent Node Original Release Earlier than V900R011
67194659
VS.IPPART.Node. Conn.Estab.Succ
67194660
VS.IPPART.Node. Conn.Modify.Att
Issue 01 (2013-05-04)
2688
Counter ID 67192414
Counter Name VS.IPPART.Node. Conn.Modify.Succ
Counter Description Number of Successful IP Connection Modifications Initiated by the Transport Layer on the Dual-Stack Transport Adjacent Node Number of IP Connection Release Requests Sent from the Radio Network Layer to the Transport Layer on the Dual-Stack Transport Adjacent Node Mean Number of Active IP Connections to a Dual-Stack Transport Adjacent Node Forward Bandwidth of IP Path Allocated to a Dual-Stack Transport Adjacent Node Backward Bandwidth of IP Path Allocated to a DualStack Transport Adjacent Node
67192415
VS.IPPART.Node. Conn.Rel
67204200
VS.IPPART.Node. Act.Con
67204201
VS.IPPART.AllocedFwd
67204202
VS.IPPART.AllocedBwd
None
2.6.1.1 Number of IP Connection Setup Requests Received on Dual-Stack Transport Adjacent Node
Issue 01 (2013-05-04)
2689
Counters
Counter ID 67194658 Counter Name VS.IPPART.Node.Conn.Est ab.Att Counter Description Number of Connection Setup Requests for IP Transport from the Transport Layer to the Radio Network Layer on the Dual-Stack Transport Adjacent Node
Description
This counter provides the number of connection setup requests for IP transport that the transport layer receives from the dual-stack adjacent node on the radio network layer.
Measurement point
This counter is incremented by one when the radio network layer sends an IP connection setup request message to the transport layer for IP cell establishment.
Formula
None
Unit
None
Related Features
Counter Name VS.IPPART.Node.Conn.Est ab.Att Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.1.2 Number of Successful IP Connection Setups on the Dual-Stack Transport Adjacent Node Counters
Counter ID 67194659 Counter Name VS.IPPART.Node.Conn.Est ab.Succ Counter Description Number of Successful IP Connection Setups Initiated by the Transport Layer on the Dual-Stack Transport Adjacent Node
Issue 01 (2013-05-04)
2690
Description
This counter provides the number of successful IP connection setups on the dual-stack adjacent node initiated by the transport layer.
Measurement point
If an IP cell is to be established, the radio network layer sends an IP connection setup request message. This counter is incremented by one when the IP connection is successfully set up.
Formula
None
Unit
None
Related Features
Counter Name VS.IPPART.Node.Conn.Est ab.Succ Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.1.3 Number of IP Connection Modifications on the Dual-Stack Transport Adjacent Node Counters
Counter ID 67194660 Counter Name VS.IPPART.Node.Conn.Mo dify.Att Counter Description Number of IP Connection Modifications on the DualStack Transport Adjacent Node
Description
This counter provides the number of IP connection modification requests sent from the radio network layer to the transport layer.
Measurement point
This counter is incremented by one when the radio network layer initiates IP connection modification requests.
Formula
None
Unit
None
Related Features
Counter Name VS.IPPART.Node.Conn.Mo dify.Att Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.1.4 Number of Successful IP Connection Modifications on the Dual-Stack Transport Adjacent Node Counters
Counter ID 67192414 Counter Name VS.IPPART.Node.Conn.Mo dify.Succ Counter Description Number of Successful IP Connection Modifications Initiated by the Transport Layer on the Dual-Stack Transport Adjacent Node
Description
This counter provides the number of successful IP connection modifications initiated by the transport layer.
Measurement point
This counter is incremented by one when the radio network layer initiates an IP connection modification request and the modification is successful.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2692
Related Features
Counter Name VS.IPPART.Node.Conn.Mo dify.Succ Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.1.5 Number of IP Connection Releases on the Dual-Stack Transport Adjacent Node Counters
Counter ID 67192415 Counter Name VS.IPPART.Node.Conn.Rel Counter Description Number of IP Connection Release Requests Sent from the Radio Network Layer to the Transport Layer on the Dual-Stack Transport Adjacent Node
Description
This counter provides the number of IP connection release requests sent from the radio network layer to the transport layer.
Measurement point
When an IP cell or a IP service is released, the transport layer receives an IP connection release request from by the radio network layer. In this case, this counter is incremented by one.
Formula
None
Unit
None
Related Features
Counter Name VS.IPPART.Node.Conn.Rel Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
Issue 01 (2013-05-04)
2693
2.6.1.6 Number of Active IP Connections on the Dual-Stack Transport Adjacent Node Counters
Counter ID 67204200 Counter Name VS.IPPART.Node.Act.Con Counter Description Mean Number of Active IP Connections to a Dual-Stack Transport Adjacent Node
Description
This counter provides the average number of active IP connections on a dual-stack transport adjacent node. The number of IP connections is averaged at all sampling points in a measurement period.
Measurement point
The system automatically samples the number of the active IP connections to an IP node every 15 seconds. At the end of the measurement period, the system divides the accumulated number of active IP connections to the adjacent node by the number of samples to obtain the average number.
Formula
None
Unit
None
Related Features
Counter Name VS.IPPART.Node.Act.Con Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.1.7 IP Path Forward Bandwidth Allocated to a Dual-Stack Transport Adjacent Node
Issue 01 (2013-05-04)
2694
Counters
Counter ID 67204201 Counter Name VS.IPPART.AllocedFwd Counter Description Forward Bandwidth of IP Path Allocated to a DualStack Transport Adjacent Node
Description
This counter provides the IP path forward bandwidth allocated to a dual-stack adjacent node (physical bandwidth), that is, the average forward bandwidth taken from all sampling points in the measurement period.
Measurement point
The system takes samples from the value of allocated IP path forward bandwidth to the adjacent node of an interface (Iub, Iur or Iu) every 15 seconds. At the end of the measurement period, the system divides the accumulated IP path forward bandwidth by the number of samples to obtain the average IP path forward bandwidth allocated to an adjacent node of the Iub, Iur, or Iu interface.
Formula
None
Unit
bit/s
Related Features
Counter Name VS.IPPART.AllocedFwd Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.1.8 IP Path Backward Bandwidth Allocated to a Dual-Stack Transport Adjacent Node Counters
Counter ID 67204202 Counter Name VS.IPPART.AllocedBwd Counter Description Backward Bandwidth of IP Path Allocated to a DualStack Transport Adjacent Node
Issue 01 (2013-05-04)
2695
Description
This counter provides the IP path backward bandwidth allocated to a dual-stack node (physical bandwidth), that is, the average backward bandwidth taken from all sampling points in the measurement period.
Measurement point
The system takes samples from the value of allocated IP path backward bandwidth to the adjacent node of an interface (Iub, Iur or Iu) every 15 seconds. At the end of the measurement period, the RNC divides the accumulated IP path backward bandwidth by the number of samples to obtain the average IP path backward bandwidth allocated to an adjacent node of the Iub, Iur, or Iu interface.
Formula
None
Unit
bit/s
Related Features
Counter Name VS.IPPART.AllocedBwd Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.2 Dual-Stack Transport Adjacent Node Measurement (QAAL2IP)

Overview
Dual-stack transport adjacent node measurement (QAAL2IP measurement) is used to measure the QAAL2 and IP connections and allocate the resources on a dual-stack adjacent node.
Counters
Counter ID 67192422 Counter Name VS.QAAL2IP.AttResAlloc Counter Description Number of Resource Requests Sent from the Radio Network Layer to the Transport Layer on Dual-Stack Transport Adjacent Node Original Release Earlier than V900R011
Issue 01 (2013-05-04)
2696
Counter ID 67192423
Counter Name VS.QAAL2IP.SuccResAlloc
Counter Description Number of Successful Resource Allocations After the Transport Layer Receives the Resource Requests from the Radio Network Layer on Dual-Stack Transport Adjacent Node Number of Failed Resource Allocations Due to Insufficient Bandwidth on the Dual-Stack Transport Adjacent Node
67196160
VS.QAAL2IP.FailResAllocForBwLimit
None
2.6.2.1 Number of Requests for Resource Allocations by Dual-Stack Transport Adjacent Node Counters
Counter ID 67192422 Counter Name VS.QAAL2IP.AttResAlloc Counter Description Number of Resource Requests Sent from the Radio Network Layer to the Transport Layer on DualStack Transport Adjacent Node
Description
This counter provides the number of resource requests sent from the radio network layer to the transport layer.
Issue 01 (2013-05-04)
2697
Measurement point
This counter is incremented by one when the transport layer receives a resource request for a dual-stack adjacent node from the radio network layer.
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2IP.AttResAlloc Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.2.2 Number of Successful Resource Allocations to Dual-Stack Transport Adjacent Node Counters
Counter ID 67192423 Counter Name VS.QAAL2IP.SuccResAlloc Counter Description Number of Successful Resource Allocations After the Transport Layer Receives the Resource Requests from the Radio Network Layer on Dual-Stack Transport Adjacent Node
Description
This counter provides the number of successful resource allocations after the transport layer receives the resource requests from the radio network layer.
Measurement point
This counter is incremented by one when the transport layer receives a resource request for a dual-stack adjacent node from the radio network layer and the resource allocation is successful.
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2IP.SuccResAlloc Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.2.3 Number of Failed Resource Allocations Due to Insufficient Bandwidth on the Dual-Stack Transport Adjacent Node Counters
Counter ID 67196160 Counter Name VS.QAAL2IP.FailResAllocForBwLimit Counter Description Number of Failed Resource Allocations Due to Insufficient Bandwidth on the Dual-Stack Transport Adjacent Node
Description
This counter provides the number of failed resource allocation requests due to insufficient bandwidth after the transport layer receives resource allocation requests from the radio network layer.
Measurement point
The radio network layer initiates a request for the resources on a dual-stack adjacent node. This counter is incremented by one if the request fails due to insufficient bandwidth.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2699
Related Features
Counter Name VS.QAAL2IP.FailResAllocForBwLimit Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3 Dual-Stack Transport Adjacent Node QAAL2 Part Measurement(QAAL2PART)

Overview
Dual-stack transport adjacent node QAAL2 part measurement measures the QAAL2 and IP connections and allocates the resources on a dual-stack adjacent node.
Counters
Counter ID 67192424 Counter Name VS.QAAL2PART. Est.RLC.NoRoute. Rx Counter Description Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to No Route at the Remote End Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to No Path path Configured at the Remote End Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to No CID Available at the Remote End Original Release Earlier than V900R011
67192425
VS.QAAL2PART. Est.RLC.NoPath.R x
67194611
VS.QAAL2PART. Est.RLC.NoCID.R x
Issue 01 (2013-05-04)
2700
Counter ID 67194612
Counter Name VS.QAAL2PART. Est.RLC.Fail.Rx
Counter Description Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to Remote Network Fault, Remote Temporary Failure, or Remote Normal Releases Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to Switch Congestion at the Remote End Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to Timer Expiry at the Remote End Number of AAL2 Connection Release Confirmations Sent by QAAL2 on DualStack Adjacent Node Due to No Route Number of AAL2 Connection Release Confirmations Sent by QAAL2 on DualStack Adjacent Node Due to No Path Configured
67194661
VS.QAAL2PART. Est.RLC.Cong.Rx
67194662
VS.QAAL2PART. Est.RLC.RecovOut .Rx
67194663
VS.QAAL2PART. Est.RLC.NoRoute. Tx
67194664
VS.QAAL2PART. Est.RLC.NoPath.T x
Issue 01 (2013-05-04)
2701
Counter ID 67194665
Counter Name VS.QAAL2PART. Est.RLC.NoCID.T x
Counter Description Number of AAL2 Connection Release Confirmations Sent by QAAL2 on DualStack Adjacent Node Due to No CID Available Number of AAL2 Connection Release Confirmations Sent by QAAL2 on DualStack Adjacent Node Due to Network Failure, Unspecified Reason, or Temporary Failure Number of AAL2 Connection Release Confirmations Sent by QAAL2 on DualStack Adjacent Node Due to Switch Congestion Number of AAL2 Connection Release Confirmations Sent by QAAL2 on DualStack Adjacent Node Due to Timer Expiry Number of Connection Establishment Request (ERQ) Messages Sent by QAAL2 on DualStack Adjacent Node Number of Connection Establishment Requests Received by QAAL2 on the Dual-Stack Adjacent Node
67194666
VS.QAAL2PART. Est.RLC.Fail.Tx
67194626
VS.QAAL2PART. Est.RLC.Cong.Tx
67194627
VS.QAAL2PART. Est.RLC.RecovOut .Tx
67194628
VS.QAAL2PART. ERQ.Tx
67194629
VS.QAAL2PART. ERQ.Rx
Issue 01 (2013-05-04)
2702
Counter ID 67194630
Counter Name VS.QAAL2PART. Est.RLC.Rx
Counter Description Number of RLC Messages Received by QAAL2 on DualStack Adjacent Node After the QAAL2 Sends the Connection ERQ Messages Number of ECF Messages Received by QAAL2 on DualStack Adjacent Node After the QAAL2 Sends the Connection ERQ Messages Number of Connection ECF Messages Sent by QAAL2 on DualStack Adjacent Node After the QAAL2 Receives the Connection ERQ Message Number of RLC Messages Sent by QAAL2 on DualStack Adjacent Node After the QAAL2 Receives the Connection ERQ Message Number of Connection Release (REL) Messages Sent by QAAL2 on Dual-Stack Adjacent Node Number of Connection REL Messages Received by QAAL2 on DualStack Adjacent Node
67194631
VS.QAAL2PART. Est.ECF.Rx
67194620
VS.QAAL2PART. Est.ECF.Tx
67194621
VS.QAAL2PART. Est.RLC.Tx
67194622
VS.QAAL2PART. Rel.Tx
67194623
VS.QAAL2PART. Rel.Rx
Issue 01 (2013-05-04)
2703
Counter ID 67194632
Counter Name VS.QAAL2PART. Rel.RLC.Rx
Counter Description Number of RLC Messages Received by QAAL2 on DualStack Adjacent Node After the QAAL2 Sends REL Messages Number of RLC Messages Sent by QAAL2 on the DualStack Adjacent Node After the QAAL2 Receives Connection REL Messages Number of Modification Rejection (MOR) Messages Received by QAAL2 on DualStack Adjacent Node After the QAAL2 Sends Connection Modification Request (MOD) Messages Number of MOR Messages Sent by QAAL2 on the DualStack Adjacent Node After the QAAL2 Receives Connection MOD Messages Number of MOD Messages Sent by QAAL2 on DualStack Adjacent Node Number of MOD Messages Received by QAAL2 on DualStack Adjacent Node Number of Active AAL2 Connections to a Dual-Stack Transport Adjacent Node
67194633
VS.QAAL2PART. Rel.RLC.Tx
67192446
VS.QAAL2PART. RxModRej
67192447
VS.QAAL2PART. TxModRej
67192448
VS.QAAL2PART. TxMod
67192449
VS.QAAL2PART. RxMod
67204203
VS.QAAL2PART. Act.Con
Issue 01 (2013-05-04)
2704
Counter ID 67204204
Counter Name VS.QAAL2PART. AllocedFwd.AAL2 BitRate
Counter Description Mean Forward Bandwidth of AAL2 Path Allocated to a Dual-Stack Transport Adjacent Node Mean Backward Bandwidth of AAL2 Path Allocated to a Dual-Stack Transport Adjacent Node Number of AAL2 Connection Release Confirmations Sent by QAAL2 on DualStack Adjacent Node Due to No Bandwidth
67204205
VS.QAAL2PART. AllocedBwd.AAL2 BitRate
67196185
VS.QAAL2PART. Est.RLC.NoBitRat e.Tx
None
2.6.3.1 Number of RLC messages received by the QAAL2 on Dual-Stack Adjacent Node Counters
Counter ID 67192424 Counter Name VS.QAAL2PART.Est.RLC. NoRoute.Rx Counter Description Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to No Route at the Remote End Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to No Path path Configured at the Remote End
2705
67192425
VS.QAAL2PART.Est.RLC. NoPath.Rx
Issue 01 (2013-05-04)
Counter ID 67194611
Counter Name VS.QAAL2PART.Est.RLC. NoCID.Rx
Counter Description Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to No CID Available at the Remote End Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to Remote Network Fault, Remote Temporary Failure, or Remote Normal Releases Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to Switch Congestion at the Remote End Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to Timer Expiry at the Remote End
67194612
VS.QAAL2PART.Est.RLC. Fail.Rx
67194661
VS.QAAL2PART.Est.RLC. Cong.Rx
67194662
VS.QAAL2PART.Est.RLC. RecovOut.Rx
Description
These counters provide the number of AAL2 connection release confirmations received by the QAAL2.
Measurement point
The measurement is triggered when the QAAL2 receives a release confirmation (RLC) message from the adjacent node.
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.Est.RLC. NoRoute.Rx VS.QAAL2PART.Est.RLC. NoPath.Rx VS.QAAL2PART.Est.RLC. NoCID.Rx VS.QAAL2PART.Est.RLC. Fail.Rx VS.QAAL2PART.Est.RLC. Cong.Rx VS.QAAL2PART.Est.RLC. RecovOut.Rx Feature ID WRFD-050404 WRFD-050404 WRFD-050404 WRFD-05030104 WRFD-050404 WRFD-050404 Feature Name ATM/IP Dual Stack Node B ATM/IP Dual Stack Node B ATM/IP Dual Stack Node B Dynamic AAL2 Connections in Iub/IuCS/Iur Interface ATM/IP Dual Stack Node B ATM/IP Dual Stack Node B
2.6.3.2 Number of RLC messages sent by the QAAL2 on Dual-Stack Adjacent Node Counters
Counter ID 67194663 Counter Name VS.QAAL2PART.Est.RLC. NoRoute.Tx Counter Description Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to No Route Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to No Path Configured Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to No CID Available
67194664
VS.QAAL2PART.Est.RLC. NoPath.Tx
67194665
VS.QAAL2PART.Est.RLC. NoCID.Tx
Issue 01 (2013-05-04)
2707
Counter ID 67194666
Counter Name VS.QAAL2PART.Est.RLC. Fail.Tx
Counter Description Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to Network Failure, Unspecified Reason, or Temporary Failure Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to Switch Congestion Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to Timer Expiry Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to No Bandwidth
67194626
VS.QAAL2PART.Est.RLC. Cong.Tx
67194627
VS.QAAL2PART.Est.RLC. RecovOut.Tx
67196185
VS.QAAL2PART.Est.RLC. NoBitRate.Tx
Description
These counters provide the number of AAL2 connection release confirmations sent by the QAAL2.
Measurement point
The measurement is triggered when the QAAL2 sends a RLC message to an adjacent node.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2708
Related Features
Counter Name VS.QAAL2PART.Est.RLC. NoRoute.Tx VS.QAAL2PART.Est.RLC. NoPath.Tx VS.QAAL2PART.Est.RLC. NoCID.Tx VS.QAAL2PART.Est.RLC. Fail.Tx VS.QAAL2PART.Est.RLC. Cong.Tx VS.QAAL2PART.Est.RLC. RecovOut.Tx VS.QAAL2PART.Est.RLC. NoBitRate.Tx Feature ID WRFD-050404 WRFD-050404 WRFD-050404 WRFD-050404 WRFD-050404 WRFD-050404 WRFD-050404 Feature Name ATM/IP Dual Stack Node B ATM/IP Dual Stack Node B ATM/IP Dual Stack Node B ATM/IP Dual Stack Node B ATM/IP Dual Stack Node B ATM/IP Dual Stack Node B ATM/IP Dual Stack Node B
2.6.3.3 Number of AAL2 Connection Establishment Requests Sent by the QAAL2 on Dual-Stack Adjacent Node Counters
Counter ID 67194628 Counter Name VS.QAAL2PART.ERQ.Tx Counter Description Number of Connection Establishment Request (ERQ) Messages Sent by QAAL2 on Dual-Stack Adjacent Node
Description
This counter provides the number of AAL2 connection establishment requests sent by the QAAL2.
Measurement point
In the measurement period, the counter is incremented by one by one at point A, as shown in Figure 1. When the RNC sends an AAL2 connection ERQ message to the adjacent node, for example, the NodeB, the RNC increments this counter by one.
Issue 01 (2013-05-04)
2709
Figure 2-18 Successful AAL2 connection establishment procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.ERQ.Tx Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.4 Number of AAL2 Connection Establishment Requests Received by the QAAL2 on the Dual-Stack Adjacent Node Counters
Counter ID 67194629 Counter Name VS.QAAL2PART.ERQ.Rx Counter Description Number of Connection Establishment Requests Received by QAAL2 on the Dual-Stack Adjacent Node
Description
This counter provides the number of AAL2 connection establishment requests received by the QAAL2 from an adjacent node. Generally, the RNC receives an AAL2 connection establishment request on the Iur interface only. On the Iub and Iu interfaces, the RNC only sends an AAL2 connection establishment request.
Measurement point
In the measurement period, the counter is incremented by one at point A, as shown in Figure 1. When the RNC receives an AAL2 connection ERQ message from the adjacent node, for example, the adjacent RNC, the RNC increments this counter by one. Figure 2-19 Successful AAL2 connection establishment procedure initiated by an adjacent node
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.ERQ.Rx Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.5 Number of AAL2 Connection Establishment Request Rejections Received by the QAAL2 on the Dual-Stack Adjacent Node Counters
Counter ID 67194630 Counter Name VS.QAAL2PART.Est.RLC. Rx Counter Description Number of RLC Messages Received by QAAL2 on Dual-Stack Adjacent Node After the QAAL2 Sends the Connection ERQ Messages
Issue 01 (2013-05-04)
2711
Description
This counter provides the number of AAL2 connection establishment request rejections received by the QAAL2 from an adjacent node.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When the RNC receives an AAL2 connection establishment rejection (RLC) message from the adjacent node, for example, the NodeB, after it sends the NodeB an AAL2 connection ERQ message, the RNC increments this counter by one. Figure 2-20 Failed AAL2 connection establishment procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.Est.RLC. Rx Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.6 Number of AAL2 Connection Establishment Confirmations Received by the QAAL2 on Dual-Stack Adjacent Node
Issue 01 (2013-05-04)
2712
Counters
Counter ID 67194631 Counter Name VS.QAAL2PART.Est.ECF. Rx Counter Description Number of ECF Messages Received by QAAL2 on Dual-Stack Adjacent Node After the QAAL2 Sends the Connection ERQ Messages
Description
This counter provides the number of AAL2 connection establishment confirmations that the QAAL2 receives from an adjacent node.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When the RNC receives an ECF message from the adjacent node, for example the NodeB, after it sends the NodeB an AAL2 connection ERQ message, the RNC increments this counter by one. Figure 2-21 Successful AAL2 connection establishment procedure initiated by the RNC
Formula
None
Unit
None
Issue 01 (2013-05-04)
2713
Related Features
Counter Name VS.QAAL2PART.Est.ECF. Rx Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.7 Number of AAL2 Connection Establishment Confirmations Sent by the QAAL2 on Dual-Stack Adjacent Node Counters
Counter ID 67194620 Counter Name VS.QAAL2PART.Est.ECF. Tx Counter Description Number of Connection ECF Messages Sent by QAAL2 on Dual-Stack Adjacent Node After the QAAL2 Receives the Connection ERQ Message
Description
This counter provides the number of AAL2 connection establishment confirmations that the QAAL2 sends to an adjacent node.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When receiving an ERQ message from an adjacent node, for example, a neighboring RNC, the RNC responds with an ECF message. In this case, this counter is incremented by one. Figure 2-22 Successful AAL2 connection establishment procedure initiated by an adjacent node
Issue 01 (2013-05-04)
2714
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.Est.ECF. Tx Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.8 Number of RLC Messages Sent by QAAL2 on Dual-Stack Adjacent Node after the QAAL2 Receives the Connection ERQ Message Counters
Counter ID 67194621 Counter Name VS.QAAL2PART.Est.RLC. Tx Counter Description Number of RLC Messages Sent by QAAL2 on DualStack Adjacent Node After the QAAL2 Receives the Connection ERQ Message
Description
This counter provides the number of AAL2 connection establishment rejections sent by the QAAL2.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When receiving an AAL2 connection ERQ message from an adjacent node, for example, a neighboring RNC, the RNC responds with an RLC message. In this case, this counter is incremented by one.
Issue 01 (2013-05-04)
2715
Figure 2-23 Failed AAL2 connection establishment procedure initiated by an adjacent node
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.Est.RLC. Tx Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.9 Number of AAL2 Connection Releases Initiated by QAAL2 on Dual-Stack Adjacent Node Counters
Counter ID 67194622 Counter Name VS.QAAL2PART.Rel.Tx Counter Description Number of Connection Release (REL) Messages Sent by QAAL2 on DualStack Adjacent Node
Description
Measurement point
In the measurement period, the counter is incremented by one at point A, as shown in Figure 1. When the RNC sends an AAL2 connection REL message to an adjacent node, for example, the NodeB, the RNC increments this counter by one. Figure 2-24 AAL2 connection release procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.Rel.Tx Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.10 Number of AAL2 Connection Releases Received by the QAAL2 on DualStack Adjacent Node Counters
Counter ID 67194623 Counter Name VS.QAAL2PART.Rel.Rx Counter Description Number of Connection REL Messages Received by QAAL2 on Dual-Stack Adjacent Node
Issue 01 (2013-05-04)
2717
Description
This counter provides the number of AAL2 connection release requests sent by the dual-stack adjacent node.
Measurement point
In the measurement period, the counter is incremented by one at point A, as shown in Figure 1. When the RNC receives an AAL2 connection REL message from an adjacent node, for example, the NodeB, the RNC increments this counter by one. Figure 2-25 AAL2 connection release procedure initiated by an adjacent node
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.Rel.Rx Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
Issue 01 (2013-05-04)
2718
2.6.3.11 Number of AAL2 Connection Confirmations Received by the QAAL2 on Dual-Stack Adjacent Node Counters
Counter ID 67194632 Counter Name VS.QAAL2PART.Rel.RLC. Rx Counter Description Number of RLC Messages Received by QAAL2 on Dual-Stack Adjacent Node After the QAAL2 Sends REL Messages
Description
This counter provides the number of AAL2 connection release confirmations received by the QAAL2.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When the RNC receives an RLC message from an adjacent node, for example, the NodeB, after it sends an AAL2 connection REL message to the NodeB, the RNC increments this counter by one. Figure 2-26 AAL2 connection release procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.Rel.RLC. Rx Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.12 Number of AAL2 Connection Releases Confirmation Initiated by the QAAL2 on the Dual-Stack Adjacent Node Counters
Counter ID 67194633 Counter Name VS.QAAL2PART.Rel.RLC. Tx Counter Description Number of RLC Messages Sent by QAAL2 on the DualStack Adjacent Node After the QAAL2 Receives Connection REL Messages
Description
This counter provides the number of AAL2 connection release confirmations sent by the QAAL2 to an adjacent node.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When RNC the sends an RLC message to an adjacent node, for example, the NodeB, after it receives an AAL2 connection REL message from the NodeB, the RNC increments this counter by one.
Issue 01 (2013-05-04)
2720
Figure 2-27 AAL2 connection release procedure initiated by an adjacent node
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.Rel.RLC. Tx Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.13 Number of AAL2 Connection Modification Request Rejections Received by the QAAL2 on the Dual-Stack Adjacent Node
Issue 01 (2013-05-04)
2721
Counters
Counter ID 67192446 Counter Name VS.QAAL2PART.RxModRej Counter Description Number of Modification Rejection (MOR) Messages Received by QAAL2 on Dual-Stack Adjacent Node After the QAAL2 Sends Connection Modification Request (MOD) Messages
Description
This counter provides the number of AAL2 connection modification request rejections received by the QAAL2 from an adjacent node.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When the RNC receives an MOR message from an adjacent node, for example, a NodeB, after it sends an AAL2 connection MOD message to the NodeB, the RNC increments this counter by one. Figure 2-28 Failed AAL2 connection modification procedure initiated by the RNC
Issue 01 (2013-05-04)
2722
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.RxModRej Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.14 Number of AAL2 Connection Modification Rejections Sent by the QAAL2 on Dual-Stack Adjacent Node Counters
Counter ID 67192447 Counter Name VS.QAAL2PART.TxModRej Counter Description Number of MOR Messages Sent by QAAL2 on the DualStack Adjacent Node After the QAAL2 Receives Connection MOD Messages
Description
This counter provides the number of AAL2 connection modification rejections sent by the QAAL2.
Measurement point
In the measurement period, the counter is incremented by one at point B, as shown in Figure 1. When the RNC responds an MOR message to an adjacent node, for example, the neighboring RNC, after receiving an AAL2 connection MOD message, the RNC increments this counter by one.
Issue 01 (2013-05-04)
2723
Figure 2-29 Failed AAL2 connection modification procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.TxModRej Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.15 Number of AAL2 Connection Modification Requests Sent by the QAAL2 on Dual-Stack Adjacent Node
Issue 01 (2013-05-04)
2724
Counters
Counter ID 67192448 Counter Name VS.QAAL2PART.TxMod Counter Description Number of MOD Messages Sent by QAAL2 on DualStack Adjacent Node
Description
This counter provides the number of AAL2 connection modification requests sent by the QAAL2.
Measurement point
In the measurement period, the counter is incremented by one after the RNC sends an AAL2 connection MOD message to an adjacent node.
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.TxMod Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.16 Number of AAL2 Connection Modification Requests Received by the QAAL2 on Dual-Stack Adjacent Node Counters
Counter ID 67192449 Counter Name VS.QAAL2PART.RxMod Counter Description Number of MOD Messages Received by QAAL2 on Dual-Stack Adjacent Node
Description
This counter provides the number of AAL2 connection modification requests received by the QAAL2 from an adjacent node.
Measurement point
In the measurement period, the counter is incremented by one when the RNC receives an AAL connection MOD message from an adjacent node.
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.RxMod Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.17 Average Number of QAAL2 Connections to Dual-Stack Adjacent Node Counters

Counter ID 67204203 Counter Name VS.QAAL2PART.Act.Con Counter Description Number of Active AAL2 Connections to a Dual-Stack Transport Adjacent Node
Description
This counter provides the average number of active AAL2 connections to a QAAL2 adjacent node at all sampling points in a measurement period.
Measurement point
The system periodically takes samples from the number of active AAL2 connections to an adjacent node. The sampling period is 15 seconds. At the end of the measurement period, the system divides the accumulated number of active AAL2 connections to an adjacent node by the number of samples to obtain the average number.
Formula
None
Unit
None
Related Features
Counter Name VS.QAAL2PART.Act.Con Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.6.3.18 Counters Related to Average QAAL2 Bandwidth Allocated to Iub Adjacent Node on Dual-Stack Adjacent Node Counters
Counter ID 67204204 Counter Name VS.QAAL2PART.AllocedF wd.AAL2BitRate Counter Description Mean Forward Bandwidth of AAL2 Path Allocated to a Dual-Stack Transport Adjacent Node
Description
These counters provide the average forward or backward bandwidth of AAL2 path allocated to an adjacent node of the Iub interface, that is, the average forward or backward bandwidth taken from all sampling points in the measurement period at the aal2 layer of ATM.
Measurement point
In the measurement period, the system automatically takes a sample from the forward or backward bandwidth of AAL2 path allocated to an adjacent node of the Iub interface. The sampling period is 15 seconds. At the end of the measurement period, the system divides the accumulated forward or backward bandwidth of AAL2 path by the number of samples to obtain the average forward or backward bandwidth of AAL2 path allocated to an adjacent node of the Iub interface.
Formula
None
Unit
bit/s
Related Features
Counter Name VS.QAAL2PART.AllocedF wd.AAL2BitRate Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
Issue 01 (2013-05-04)
2727
2.6.3.19 Counters
Counter ID 67204205 Counter Name VS.QAAL2PART.AllocedB wd.AAL2BitRate Counter Description Mean Backward Bandwidth of AAL2 Path Allocated to a Dual-Stack Transport Adjacent Node
Description
This counter provide the average backward bandwidth of AAL2 path allocated to an adjacent node of the Iub interface, that is, the average backward bandwidth taken from all sampling points in the measurement period at the aal2 layer of ATM.
Measurement point
None
Formula
None
Unit
bit/s
Related Features
Counter Name VS.QAAL2PART.AllocedB wd.AAL2BitRate Feature ID WRFD-050404 Feature Name ATM/IP Dual Stack Node B
2.7 Measurement of ATM Logical Port Performance (ATM_LOGIC_PORT)

Overview
ATM logical port performance measurement indicates the transmission quality of the ATM logical port on the AEU, AOU, or UOI board.
Issue 01 (2013-05-04)
2728
FunctionSubSets
FunctionSubSet ATM.LOGIC.PORT FunctionSubSet Name ATM Logical Port Measurement
2.7.1 ATM Logical Port Measurement(ATM.LOGIC.PORT)

Overview
The ATM logic port measurement helps monitor the ATM logic port transmission quality of the running system and analyze system transmission quality to maintain system stability and reliability. Figure 2-30 Physical bearer of the ATM Logic Port
Issue 01 (2013-05-04)
2729
Counters
Counter ID 67204859 Counter Name VS.ATMLGCPRT. Alloced.Ave.Fwd Counter Description Mean Forward Bandwidth Assigned to the ATM Logical Port Mean Backward Bandwidth Assigned to the ATM Logical Port Maximum Forward Bandwidth Assigned to the ATM Logical Port Maximum Backward Bandwidth Assigned to the ATM Logical Port Number of Forward Congestions on the ATM Logical Port Duration of Forward Congestions on the ATM Logical Port Number of Backward Congestions on the ATM Logical Port Duration of Backward Congestions on the ATM Logical Port Original Release Earlier than V900R011
67204858
VS.ATMLGCPRT. Alloced.Ave.Bwd
67196319
VS.ATMLGCPRT. Alloced.Max.Fwd
67196320
VS.ATMLGCPRT. Alloced.Max.Bwd
67196321
VS.ATMLGCPRT. Fwd.Cong VS.ATMLGCPRT. Fwd.Cong.Dur VS.ATMLGCPRT. Bwd.Cong
67196322
67196323
67196324
VS.ATMLGCPRT. Bwd.Cong.Dur
None
2.7.1.1 Counters Related to the Bandwidth Assigned to an ATM Logical Port
Issue 01 (2013-05-04)
2730
Counters
Counter ID 67204859 Counter Name VS.ATMLGCPRT.Alloced. Ave.Fwd VS.ATMLGCPRT.Alloced. Ave.Bwd VS.ATMLGCPRT.Alloced. Max.Fwd VS.ATMLGCPRT.Alloced. Max.Bwd Counter Description Mean Forward Bandwidth Assigned to the ATM Logical Port Mean Backward Bandwidth Assigned to the ATM Logical Port Maximum Forward Bandwidth Assigned to the ATM Logical Port Maximum Backward Bandwidth Assigned to the ATM Logical Port
67204858
67196319
67196320
Description
These counters provide the mean or peak forward bandwidth or backward bandwidth assigned to an ATM logical port.
Measurement point
In the measurement period, the system automatically takes samples on the bandwidth assigned to an ATM logical port every 15 seconds. At the end of the measurement period, the maximum forward bandwidth and the maximum backward bandwidth assigned to an ATM logical port in the measurement period are obtained. The mean forward bandwidth assigned to an ATM logical port equals to the accumulated value of the forward bandwidth at the sampling points divided by the number of sampling times. The mean backward bandwidth assigned to an ATM logical port equals to the accumulated value of the backward bandwidth at the sampling points divided by the number of sampling times.
Formula
None
Unit
bit/s
Related Features
Counter Name VS.ATMLGCPRT.Alloced. Ave.Fwd Feature ID WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
Issue 01 (2013-05-04)
2731
Counter Name VS.ATMLGCPRT.Alloced. Ave.Bwd VS.ATMLGCPRT.Alloced. Max.Fwd VS.ATMLGCPRT.Alloced. Max.Bwd
Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.7.1.2 Counters Related to the Number of Congestions on the ATM Logical Port Counters
Counter ID 67196321 Counter Name VS.ATMLGCPRT.Fwd.Con g VS.ATMLGCPRT.Bwd.Co ng Counter Description Number of Forward Congestions on the ATM Logical Port Number of Backward Congestions on the ATM Logical Port
67196323
Description
These counters provide the number of of forward or backward congestions on the ATM logical port. Service access may be affected if many ATM logical ports are congested for a long period. They can be used together with the duration of ATM logical port congestion to analyze the congestion.
Measurement point
The RNC checks the state of an ATM logic port each time a service is being admitted to that port. The corresponding counter is incremented by one when the state of the ATM logic port changes from non-congestion to forward or backward congestion, that is, the remaining bandwidth available becomes smaller than the congestion threshold.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2732
Related Features
Counter Name VS.ATMLGCPRT.Fwd.Con g VS.ATMLGCPRT.Bwd.Co ng Feature ID WRFD-05030104 WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.7.1.3 Counters Related to the Duration of Congestions on the ATM Logical Port Counters
Counter ID 67196322 Counter Name VS.ATMLGCPRT.Fwd.Con g.Dur VS.ATMLGCPRT.Bwd.Co ng.Dur Counter Description Duration of Forward Congestions on the ATM Logical Port Duration of Backward Congestions on the ATM Logical Port
67196324
Description
These counters provide the duration of forward or backward congestions on the ATM logical port. Service access may be affected if many ATM logical ports are congested for a long period.
Measurement point
The measurement of the duration of forward (backward) congestion starts when a forward (backward) congestion is detected on a ATM logic port, that is, the remaining bandwidth available becomes smaller than the congestion threshold, and stops when the forward (backward) congestion is cleared. In the measurement period, the accumulated duration of forward (backward) congestion on the ATM logic port is taken as the value of this counter.
Formula
None
Unit
s
Issue 01 (2013-05-04)
2733
Related Features
Counter Name VS.ATMLGCPRT.Fwd.Con g.Dur VS.ATMLGCPRT.Bwd.Co ng.Dur Feature ID WRFD-05030104 WRFD-05030104 Feature Name Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
2.8 Measurement of Channelized Optical Port Performance (CHANNELIZED_OPTICAL_PORT)

Overview
Measurement of Channelized Optical Port Performance indicates the transmission quality of the optical ports on the AOUa, POUa, OIUa, OIUb, AOUc and POUc boards.
FunctionSubSets
FunctionSubSet CHANNELIZED.OPTICAL.PORT FunctionSubSet Name Channelized Optical Port Measurement
2.8.1 Channelized Optical Port Measurement (CHANNELIZED.OPTICAL.PORT)

Overview
Channelized optical ports are important resources of the Base Station Controller. Therefore, the optical ports can be measured for the analysis of the transmission quality of the running Base Station Controller so that the stable and reliable operation of the Base Station Controller can be maintained.
Counters
Counter ID 73404129 Counter Name VS.CHANNELIZE D.FAULTTIME Counter Description T7247:Duration of Faults on the Channelized Optical Port Original Release Earlier than V900R011
Issue 01 (2013-05-04)
2734
None
2.8.1.1 Duration of Faults in the optical port Counters

Counter ID 73404129 Counter Name VS.CHANNELIZED.FAUL TTIME Counter Description T7247:Duration of Faults on the Channelized Optical Port
Description
This counter provides the duration of faults in the optical port in the measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. If the system is in faulty state at the current sampling point, five seconds are added to the fault duration of the link.
Formula
None
Unit
s
Related Features
Counter Name VS.CHANNELIZED.FAUL TTIME Feature ID WRFD-050304 Feature Name IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface
2.9 Measuement of E1T1 port error code Performance (E1T1_ES)

Overview
ITU G.826 defines the links where data is transmitted through data blocks. It also defines the transmission bit error rate (BER) should be monitored when the links are in normal state. E1T1 Port Error Code Performance Measurement is used to monitor the physical transmission quality by measuring the E1T1 errored second and the BER.
FunctionSubSets
FunctionSubSet E1T1_ES FunctionSubSet Name E1T1 Port Bit Error Measurement
2.9.1 E1T1 Port Bit Error Measurement(E1T1_ES)

Overview
E1/T1 is a major resource for the base station controller. It indicates E1T1 electrical ports or channelized optical ports. E1T1 Port Bit Error Measurement is used to measure the E1T1 errored seconds and BER. In this way, the transmission quality can be monitored and the stable operation of the system is ensured. ITU G.826 defines the following monitoring items(a1,a2,d1,d2,d3) and HUAWEI defines the following monitoring(a3,d4,d5).Based on the items and their measurement rules, the E1T1 errored seconds and BER can be obtained. a1: an errored frame alignment signal. a2: an EB as indicated by an EDC. a3: E-Bit error, indicating that the CRC for the transmitted frames fails. d1: loss of signal. d2: alarm indication signal. d3: loss of frame alignment. d4: frame slip, indicating that frame slips occur in the receiving direction. d5: remote alarm indication, indicating that the peer end cannot receive frames properly.
Counters
Counter ID 73403242 73403243 Counter Name VS.E1T1.ES.ES VS.E1T1.ES.SES Counter Description T7001:E1/T1 Error Seconds T7002:E1/T1 Severely Error Seconds T7003:E1/T1 Unavailable Seconds Original Release V900R011 V900R011
73403244
VS.E1T1.ES.UAS
V900R011
Issue 01 (2013-05-04)
2736
Counter ID 73403245
Counter Name VS.E1T1.ES.BBE
Counter Description T7004:Number of E1/T1 Background Error Blocks T7005:E1/T1 Error Second Rate T7006:E1/T1 Severely Error Second Rate T7007:E1/T1 Unavailable Second Rate T7008:E1/T1 Background Block Error Rate T7010:Number of Seconds with Error Codes Transmitted over E1/T1 T7011:Number of Seconds with Severely Error Codes Transmitted over E1/ T1 T7012:Number of Background Error Blocks Transmitted over E1/T1 T7013:Second Rate with Error Codes Transmitted over E1/ T1 T7014:Second Rate with Severely Error Codes Transmitted over E1/T1 T7015:Error Rate of Background Block Transmitted over E1/ T1 T7077:E1/T1 Number of Unavailability
73415654 73415655
VS.E1T1.ES.ESR VS.E1T1.ES.SESR
V900R011 V900R011
73415656
VS.E1T1.ES.UASR
V900R011
73415657
VS.E1T1.ES.BBER
V900R011
73403645
VS.E1T1.ES.TES
V900R011
73403646
VS.E1T1.ES.TSES
V900R011
73403647
VS.E1T1.ES.TBBE
V900R011
73415827
VS.E1T1.ES.TESR
V900R011
73415828
VS.E1T1.ES.TSES R
V900R011
73415829
VS.E1T1.ES.TBBE R
V900R011
73426203
VS.E1T1.ES.NUV
V900R015
Issue 01 (2013-05-04)
2737
None
2.9.1.1 E1T1 Errored Second Counters

Counter ID 73403242 73403645 Counter Name VS.E1T1.ES.ES VS.E1T1.ES.TES Counter Description T7001:E1/T1 Error Seconds T7010:Number of Seconds with Error Codes Transmitted over E1/T1
Description
VS.E1T1.ES.ES: If any of the monitoring items a1, a2, d1, d2, d3 and d4 exists within one second, it is considered as a received errored second (ES). For the meanings of the monitoring items, see the definition of E1T1 Port Bit Error Measurement. VS.E1T1.ES.TES: If any of the monitoring items a3 and d5 exists within one second, it is considered as a transmitted errored second (TES).
Measurement point
VS.E1T1.ES.ES: Samples are taken every second in the specified measurement period. The counter is added by one, if the current second is a received errored second (ES). VS.E1T1.ES.TES: Samples are taken every second in the specified measurement period. The counter is added by one, if the current second is a transmitted errored second (TES).
Formula
None
Unit
s
Related Features
Counter Name VS.E1T1.ES.ES Feature ID WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface
2738
Issue 01 (2013-05-04)
Counter Name VS.E1T1.ES.TES
Feature Name ATM over E1T1 on Iub Interface
2.9.1.2 E1T1 Severely Errored Second Counters

Counter ID 73403243 73403646 Counter Name VS.E1T1.ES.SES VS.E1T1.ES.TSES Counter Description T7002:E1/T1 Severely Error Seconds T7011:Number of Seconds with Severely Error Codes Transmitted over E1/T1
Description
VS.E1T1.ES.SES: If any of the monitoring items d1, d2, d3, and d4 exists within one second or x a1 items or a2 items (x indicates 100 in T1 transmission mode and 300 in E1 transmission mode) exist within one second, it is considered as a received severely errored second (SES). For the meanings of the monitoring items, see the definition of E1T1 Port Bit Error Measurement. VS.E1T1.ES.TSES: If a monitoring item d5 exists within one second or x a3 items (x indicates 100 in T1 transmission mode and 300 in E1 transmission mode) exist within one second, it is considered as a transmitted severely errored second (TSES).
Measurement point
VS.E1T1.ES.SES: Samples are taken every second in the specified measurement period. The counter is added by one, if the current second is a received severely errored second (SES). VS.E1T1.ES.TSES: Samples are taken every second in the specified measurement period. The counter is added by one, if the current second is a transmitted severely errored second (TSES).
Formula
None
Unit
s
Issue 01 (2013-05-04)
2739
Related Features
Counter Name VS.E1T1.ES.SES VS.E1T1.ES.TSES Feature ID WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
2.9.1.3 E1T1 Unavailable Second Counters

Counter ID 73403244 73426203 Counter Name VS.E1T1.ES.UAS VS.E1T1.ES.NUV Counter Description T7003:E1/T1 Unavailable Seconds T7077:E1/T1 Number of Unavailability
Description
The link is considered unavailable after 10 received severely errored seconds (SESs) or 10 transmitted severely errored seconds (TSESs) appear continuously. These 10 seconds are also included in the unavailable time. The link is considered available when no SES appears within 10 seconds. These 10 seconds are also included in the available time. The unavailable seconds (UASs) are from the time when the link is unavailable to the time when the link is available.An unavailable second is not calculated as an errored second.The VS.E1T1.ES.NUV counter measures the number of times the measurement of the VS.E1T1.ES.UAS counter is triggered in a measurement period. This counter is increased by one each time an E1/T1 link becomes faulty.
Measurement point
Samples are taken every second in the specified measurement period.
Formula
None
Unit
s
Issue 01 (2013-05-04)
2740
Related Features
Counter Name VS.E1T1.ES.UAS VS.E1T1.ES.NUV Feature ID WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
2.9.1.4 E1T1 Background Error Block Counters

Counter ID 73403245 73403647 Counter Name VS.E1T1.ES.BBE VS.E1T1.ES.TBBE Counter Description T7004:Number of E1/T1 Background Error Blocks T7012:Number of Background Error Blocks Transmitted over E1/T1
Description
VS.E1T1.ES.BBE: This counter measures the number of received background error blocks that contain a1 or a2 items but do not occur in any received severely errored second (SES). For the meanings of the monitoring items, see the definition of E1T1 Port Bit Error Measurement. VS.E1T1.ES.TBBE: This counter measures the number of transmitted background error blocks that contain a3 items but do not occur in any transmitted severely errored second (TSES).
Measurement point
Formula
None
Unit
None
Issue 01 (2013-05-04)
2741
Related Features
Counter Name VS.E1T1.ES.BBE VS.E1T1.ES.TBBE Feature ID WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
2.9.1.5 E1T1 Errored Second Rate Counters

Counter ID 73415654 73415827 Counter Name VS.E1T1.ES.ESR VS.E1T1.ES.TESR Counter Description T7005:E1/T1 Error Second Rate T7013:Second Rate with Error Codes Transmitted over E1/T1
Description
VS.E1T1.ES.ESR: This counter measures the proportion of the received errored seconds (ESs) in the specified measurement period. VS.E1T1.ES.TESR: This counter measures the proportion of the transmitted errored seconds (TESs) in the specified measurement period.
Measurement point
Formula
None
Unit
%
Related Features
Counter Name VS.E1T1.ES.ESR Feature ID WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface
2742
Issue 01 (2013-05-04)
Counter Name VS.E1T1.ES.TESR
Feature Name ATM over E1T1 on Iub Interface
2.9.1.6 E1T1 Severely Errored Second Rate Counters

Counter ID 73415655 73415828 Counter Name VS.E1T1.ES.SESR VS.E1T1.ES.TSESR Counter Description T7006:E1/T1 Severely Error Second Rate T7014:Second Rate with Severely Error Codes Transmitted over E1/T1
Description
VS.E1T1.ES.SESR: This counter measures the proportion of the received severely errored seconds (SESs) in the specified measurement period. VS.E1T1.ES.TSESR: This counter measures the proportion of the transmitted severely errored seconds (TSESs) in the specified measurement period.
Measurement point
Formula
None
Unit
%
Related Features
Counter Name VS.E1T1.ES.SESR VS.E1T1.ES.TSESR Feature ID WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
Issue 01 (2013-05-04)
2743
2.9.1.7 E1T1 Unavailable Second Rate Counters

Counter ID 73415656 Counter Name VS.E1T1.ES.UASR Counter Description T7007:E1/T1 Unavailable Second Rate
Description
This counter provides the proportion of the unavailable seconds in the specified measurement period.
Measurement point
Formula
None
Unit
%
Related Features
Counter Name VS.E1T1.ES.UASR Feature ID WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface
2.9.1.8 E1T1 Background Block Error Rate Counters

Counter ID 73415657 73415829 Counter Name VS.E1T1.ES.BBER VS.E1T1.ES.TBBER Counter Description T7008:E1/T1 Background Block Error Rate T7015:Error Rate of Background Block Transmitted over E1/T1
Issue 01 (2013-05-04)
2744
Description
VS.E1T1.ES.BBER: This counter measures the proportion of the Received Background Error Blocks (BBEs) among all data blocks within the specified measurement period when the E1/T1 link is available. VS.E1T1.ES.TBBER: This counter measures the proportion of the Transmitted Background Error Blocks (TBBEs) among all data blocks within the specified measurement period when the E1/T1 link is available.
Measurement point
Formula
None
Unit
%
Related Features
Counter Name VS.E1T1.ES.BBER VS.E1T1.ES.TBBER Feature ID WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
2.10 Measurement of E1/T1 ELECT Port Performance (ELECT)

Overview
Measurement of E1/T1 ELECT Port Performance indicates the transmission quality of the E1/ T1 ELECT ports, that is, the electrical ports on the AEUa, PEUa, PEUc, EIUa or EIUb board.
FunctionSubSets
FunctionSubSet ELECT FunctionSubSet Name E1/T1 Electronical Port Measurement
Issue 01 (2013-05-04)
2745
2.10.1 E1/T1 Electronical Port Measurement(ELECT)

Overview
The E1/T1 Electronical Ports are important resources of the Base Station Controller system. Each E1/T1 electronical port is a measurement object of the ELECT. Therefore, the E1/T1 Electronical ports can be measured for the analysis of the transmission quality of the running Base Station Controller so that the stable and reliable operation of the Base Station Controller can be maintained.
Counters
Counter ID 67194334 Counter Name VS.ELECT.CODEVIOLATE Counter Description T7016:Number of Cells with Error Codes in the E1/T1 Electronical Port T7017:Rate of Cells with Error Codes in the E1/T1 Electronical Port T7020:Number of Cells with Error Frame Delimitation in the E1/T1 Electronical Port T7021:Rate of Cells with Frame Delimitation Error in the E1/T1 Electronical Port T7024:Number of Cells with CRC Error in the E1/T1 Electronical Port T7025:Rate of Cells with CRC Error in the E1/T1 Electronical Port T7028:Number of Cells with Ebit Error in the E1/T1 Electronical Port Original Release Earlier than V900R011
67204488
VS.ELECT.CODE VIOLATE.Rate.M ean VS.ELECT.FRAM INGERROR
67194335
67204489
VS.ELECT.FRAM INGERROR.Rate. Mean
67194336
VS.ELECT.CRCE RROR
67204490
VS.ELECT.CRCE RROR.Rate.Mean
67194337
VS.ELECT.EBITE RROR
Issue 01 (2013-05-04)
2746
Counter ID 67204491
Counter Name VS.ELECT.EBITE RROR.Rate.Mean
Counter Description T7029:Rate of Cells with Ebit Error in the E1/T1 Electronical Port T7032:Number of Cells with Sa6 Error in the E1/T1 Electronical Port T7035:Duration of Faults in the E1/T1 Electronical Port T7036:Number of Multiframes on the E1/T1 Electronical Port T7037:Traffic Received on the E1/ T1 Electronical Port T7038:Traffic Transmitted on the E1/T1 Electronical Port T7039:Number of Frame Alignment Changes of the E1/ T1 Electronical Port
67194338
VS.ELECT.SA6ER ROR
67194341
VS.ELECT.FAUL TTIME VS.ELECT.MULT IFRAME
67194342
67194343
VS.ELECT.RXFL OWCAPACITY VS.ELECT.TXFL OWCAPACITY
67194344
67194347
VS.ELECT.FRAM EALIGNCHANGE D
None
2.10.1.1 Counters Related to the Number of Cells with Error Codes in the E1/T1 electronical port Counters
Counter ID 67194334 Counter Name VS.ELECT.CODEVIOLATE Counter Description T7016:Number of Cells with Error Codes in the E1/T1 Electronical Port
Issue 01 (2013-05-04)
2747
Counter ID 67194335
Counter Name VS.ELECT.FRAMINGERROR VS.ELECT.CRCERROR
Counter Description T7020:Number of Cells with Error Frame Delimitation in the E1/T1 Electronical Port T7024:Number of Cells with CRC Error in the E1/T1 Electronical Port T7028:Number of Cells with Ebit Error in the E1/T1 Electronical Port T7032:Number of Cells with Sa6 Error in the E1/T1 Electronical Port
67194336
67194337
VS.ELECT.EBITERROR
67194338
VS.ELECT.SA6ERROR
Description
These counters provide the number of cells with error codes in the E1/T1 electronical port in the measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of cells with error codes on the E1/T1 electronical port once every five seconds and obtains the total number of cells with error codes on the E1/T1 electronical port in one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.ELECT.CODEVIOLATE VS.ELECT.FRAMINGERROR VS.ELECT.CRCERROR Feature ID WRFD-05030101 WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
Issue 01 (2013-05-04)
2748
Counter Name VS.ELECT.EBITERROR VS.ELECT.SA6ERROR
Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
2.10.1.2 Counters Related to the Rate of Cells in the E1/T1 electronical port Counters
Counter ID 67204488 Counter Name VS.ELECT.CODEVIOLAT E.Rate.Mean VS.ELECT.FRAMINGERR OR.Rate.Mean VS.ELECT.CRCERROR.R ate.Mean VS.ELECT.EBITERROR.R ate.Mean Counter Description T7017:Rate of Cells with Error Codes in the E1/T1 Electronical Port T7021:Rate of Cells with Frame Delimitation Error in the E1/T1 Electronical Port T7025:Rate of Cells with CRC Error in the E1/T1 Electronical Port T7029:Rate of Cells with Ebit Error in the E1/T1 Electronical Port
67204489
67204490
67204491
Description
These counters provide the rate of cells with error codes in the E1/T1 electronical port in the measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the error rate once every five seconds and calculates the mean value based on the collected statistics within one measurement period.
Formula
None
Unit
%
Related Features
Counter Name VS.ELECT.CODEVIOLAT E.Rate.Mean VS.ELECT.FRAMINGERR OR.Rate.Mean VS.ELECT.CRCERROR.R ate.Mean VS.ELECT.EBITERROR.R ate.Mean Feature ID WRFD-05030101 WRFD-05030101 WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
2.10.1.3 Duration of Faults in the E1/T1 electronical port Counters

Counter ID 67194341 Counter Name VS.ELECT.FAULTTIME Counter Description T7035:Duration of Faults in the E1/T1 Electronical Port
Description
This counter provides the duration of faults in the E1/T1 electronical port in the measurement period.
Measurement point
Formula
None
Unit
s
Related Features
Counter Name VS.ELECT.FAULTTIME Feature ID WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface
Issue 01 (2013-05-04)
2750
2.10.1.4 Number of Multiframes on the E1/T1 electronical port Counters

Counter ID 67194342 Counter Name VS.ELECT.MULTIFRAME Counter Description T7036:Number of Multiframes on the E1/T1 Electronical Port
Description
This counter provides the number of loss of multiframe alignment (LMFA) times over the E1/ T1 electrical port.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of LMFA times on the E1/T1 electronical port once every five seconds and obtains the total number of LMFA times in one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.ELECT.MULTIFRAME Feature ID WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface
2.10.1.5 Counters Related to the Traffic Received or Transmitted on the E1/T1 electronical port Counters
Counter ID 67194343 Counter Name VS.ELECT.RXFLOWCAPACITY
Counter Description T7037:Traffic Received on the E1/T1 Electronical Port

2751
Issue 01 (2013-05-04)
Counter ID 67194344
Counter Name VS.ELECT.TXFLOWCAPACITY
Counter Description T7038:Traffic Transmitted on the E1/T1 Electronical Port
Description
This counter provides the traffic received and transmitted on the E1/T1 electronical port in the measurement period.
Measurement point
Samples are taken every five seconds in the measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.ELECT.RXFLOWCAPACITY VS.ELECT.TXFLOWCAPACITY Feature ID WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
2.10.1.6 Number of Frame Alignment Changes of the E1/T1 electronical port Counters
Counter ID 67194347 Counter Name VS.ELECT.FRAMEALIGNCHANGED Counter Description T7039:Number of Frame Alignment Changes of the E1/T1 Electronical Port
Description
This counter provides the number of frame alignment changes of the E1/T1 electronical port in the measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of frame alignment changes on the E1/T1 electronical port once every five seconds and obtains the total number of frame alignment changes in one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.ELECT.FRAMEALIGNCHANGED Feature ID WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface
2.11 Measurement of FEGE Ethernet Port Performance (FEGE)

Overview
Measurement of FEGE Ethernet Port Performance indicates the transmission quality of the Ethernet ports on the FG2a, GOUa, FG2d, FG2c, GOUd and GOUc board.
FunctionSubSets
FunctionSubSet FEGE FunctionSubSet Name FEGE Ethernet Port Measurement
2.11.1 FEGE Ethernet Port Measurement(FEGE)

Overview
FEGE Ethernet ports are important resources of the Base Station Controller. Therefore, the FEGE Ethernet ports can be measured for the analysis of the transmission quality of the running Base Station Controller so that the stable and reliable operation of the Base Station Controller can be maintained. FEGE Ethernet port belongs to the Link layer of the TCP/IP protocol suite, as figure 1 shows.
Figure 2-31 The four layers of the TCP/IP protocol suite
In the configuration structure, FE/GE ports are physical ports, as shown in the figure 2. Figure 2-32 Physical bearer of the FEGE Ethernet Port
Counters
Counter ID 67204393 Counter Name VS.FEGE.RXBYT ES Counter Description T7101:Number of Bytes Received on the FEGE Ethernet Port Original Release Earlier than V900R011
Issue 01 (2013-05-04)
2754
Counter ID 67204394
Counter Name VS.FEGE.TXBYT ES
Counter Description T7104:Number of Bytes Transmitted on the FEGE Ethernet Port T7107:Number of frames Received on the FEGE Ethernet Port T7110:Number of frames Transmitted on the FEGE Ethernet Port T7113:Number of frames Discarded in Transmission on the FEGE Ethernet Port T7114:Number of FCS(Frame Check Sequence) Error frames Received on the FEGE Ethernet Port T7115:Frames Number of Unknown Protocol Received on the FEGE Ethernet Port T7118:Duration of Faults in the FEGE Ethernet Port T7121:Highest Receive Rate of the FEGE Ethernet Port T7122:Lowest Receive Rate of the FEGE Ethernet Port T7123:Mean Receive Rate of the FEGE Ethernet Port T7126:Highest Transmit Rate of the FEGE Ethernet Port
67204395
VS.FEGE.RXPAC KETS
67204396
VS.FEGE.TXPAC KETS
67194363
VS.FEGE.TXDRO PPEDPKTS
67194364
VS.FEGE.RXERRORPKTS
67194365
VS.FEGE.RXUNKNOWNPKTS
67194368
VS.FEGE.FAULTTIME VS.FEGE.RXMAX SPEED VS.FEGE.RXMINSPEED VS.FEGE.RXMEA NSPEED VS.FEGE.TXMAX SPEED
67194369
67194370
67194371
67194372
Issue 01 (2013-05-04)
2755
Counter ID 67194373
Counter Name VS.FEGE.TXMINSPEED VS.FEGE.TXMEA NSPEED VS.FEGE.RXPAU SEFRAMES
Counter Description T7127:Lowest Transmit Rate of the FEGE Ethernet Port T7128:Mean Transmit Rate of the FEGE Ethernet Port T7129:Number of the PAUSE Control Frames Received on the FEGE Ethernet Port T7130:Number of the PAUSE Control Frames Transmitted on the FEGE Ethernet Port T7137:Highest Receive Rate of the FEGE Ethernet Port (5-Minute) T7138:Highest Transmit Rate of the FEGE Ethernet Port (5-Minute)
67194374
67204764
67204765
VS.FEGE.TXPAU SEFRAMES
73441531
VS.FEGE.FIVE.M INUTES.RXMAXSPEED VS.FEGE.FIVE.M INUTES.TXMAXSPEED
V900R014
73441532
V900R014
None
2.11.1.1 Counters Related to the Number of Bytes Received or Transmitted on the FEGE Ethernet port Counters
Counter ID 67204393 Counter Name VS.FEGE.RXBYTES Counter Description T7101:Number of Bytes Received on the FEGE Ethernet Port T7104:Number of Bytes Transmitted on the FEGE Ethernet Port
67204394
VS.FEGE.TXBYTES
Issue 01 (2013-05-04)
2756
Description
These counters provide the number of bytes received or transmitted at the Link layer for the FE/ GE port in a specified measurement period. They indicate the traffic volume at the Link layer for the FE/GE port in the specified measurement period. The number of bytes measured includes the number of bytes in the header of the MAC frame and the payload. The measured bytes include the header, payload, and Frame Check Sequence (FCS)
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the port once every five seconds and obtains the total number of bytes in one measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.FEGE.RXBYTES Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.FEGE.TXBYTES WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.11.1.2 Counters Related to the Number of frames Received, Transmitted or Discarded on the FEGE Ethernet port
Issue 01 (2013-05-04)
2757
Counters
Counter ID 67204395 Counter Name VS.FEGE.RXPACKETS Counter Description T7107:Number of frames Received on the FEGE Ethernet Port T7110:Number of frames Transmitted on the FEGE Ethernet Port T7113:Number of frames Discarded in Transmission on the FEGE Ethernet Port T7114:Number of FCS (Frame Check Sequence) Error frames Received on the FEGE Ethernet Port T7115:Frames Number of Unknown Protocol Received on the FEGE Ethernet Port
67204396
VS.FEGE.TXPACKETS
67194363
VS.FEGE.TXDROPPEDPKTS VS.FEGE.RXERRORPKTS
67194364
67194365
VS.FEGE.RXUNKNOWNPKTS
Description
These counters provide the number of frames received, transmitted or discarded on the FEGE Ethernet port at the Link layer in the measurement period. They indicate the traffic volume of the FEGE Ethernet port at the Link layer. The frames measured here are MAC frames. "Frames Number of Unknown Protocol Received on the FEGE Ethernet Port" is available only when the interface board is FG2c, GOUc, FG2d or GOUd.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of frames received, transmitted and discarded on the port once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
frame
Issue 01 (2013-05-04)
2758
Related Features
Counter Name VS.FEGE.RXPACKETS Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.FEGE.TXPACKETS WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.FEGE.TXDROPPEDPKTS WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.FEGE.RXERRORPKTS WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.FEGE.RXUNKNOWNPKTS WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.11.1.3 Duration of Faults in the FEGE Ethernet port Counters

Counter ID 67194368 Counter Name VS.FEGE.FAULTTIME Counter Description T7118:Duration of Faults in the FEGE Ethernet Port
Issue 01 (2013-05-04)
2759
Description
This counter provides the duration of faults in the FEGE Ethernet port in the measurement period. This counter indicates the operation of an FE/GE Ethernet port in the measurement period.
Measurement point
Formula
None
Unit
s
Related Features
Counter Name VS.FEGE.FAULTTIME Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.11.1.4 Counters related to the Receive Rate or Transmit Rate of the FEGE Ethernet port Counters
Counter ID 67194369 67194370 67194371 67194372 Counter Name VS.FEGE.RXMAXSPEED VS.FEGE.RXMINSPEED VS.FEGE.RXMEANSPEED VS.FEGE.TXMAXSPEED Counter Description T7121:Highest Receive Rate of the FEGE Ethernet Port T7122:Lowest Receive Rate of the FEGE Ethernet Port T7123:Mean Receive Rate of the FEGE Ethernet Port T7126:Highest Transmit Rate of the FEGE Ethernet Port
Issue 01 (2013-05-04)
2760
Counter ID 67194373
Counter Name VS.FEGE.TXMINSPEED
Counter Description T7127:Lowest Transmit Rate of the FEGE Ethernet Port T7128:Mean Transmit Rate of the FEGE Ethernet Port
67194374
VS.FEGE.TXMEANSPEED
Description
These counters provide the receive rate or transmit rate of the FEGE Ethernet port at the Link layer in the measurement period. The rates measured here include the spending of the MAC header and the MAC payload of the MAC data.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the link once every five seconds. With this, the system obtains the maximum and the minimum number of bytes received or transmitted in five seconds, and the total number of bytes in one measurement period. The maximum and minimum speed is calculated with the maximum and minimum bytes in five seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.FEGE.RXMAXSPEED Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.FEGE.RXMINSPEED WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
Counter Name VS.FEGE.RXMEANSPEED
Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
VS.FEGE.TXMAXSPEED
WRFD-050402 WRFD-050409 WRFD-050410
IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
VS.FEGE.TXMINSPEED
WRFD-050402 WRFD-050409 WRFD-050410
VS.FEGE.TXMEANSPEED
WRFD-050402 WRFD-050409 WRFD-050410
2.11.1.5 Counters Related to the Number of the PAUSE Control Frames on the FEGE Ethernet port Counters
Counter ID 67204764 Counter Name VS.FEGE.RXPAUSEFRAMES Counter Description T7129:Number of the PAUSE Control Frames Received on the FEGE Ethernet Port T7130:Number of the PAUSE Control Frames Transmitted on the FEGE Ethernet Port
67204765
VS.FEGE.TXPAUSEFRAMES
Issue 01 (2013-05-04)
2762
Description
These counters provide the number of the PAUSE control frames received or transmitted on the FEGE Ethernet port in the measurement period. The PAUSE control frame is a type of 64-byte pause frame, which is defined in IEEE802.3X. When congestion occurs on the FE/GE Ethernet port, the local end sends a PAUSE control frame to the peer end, notifying the peer end of the congestion.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of pause frames once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
frame
Related Features
Counter Name VS.FEGE.RXPAUSEFRAMES Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.FEGE.TXPAUSEFRAMES WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.11.1.6 5-Minute Measurement of the Highest Transmit and Receive Rates of the FEGE Ethernet port
Issue 01 (2013-05-04)
2763
Counters
Counter ID 73441531 Counter Name VS.FEGE.FIVE.MINUTES. RXMAXSPEED VS.FEGE.FIVE.MINUTES. TXMAXSPEED Counter Description T7137:Highest Receive Rate of the FEGE Ethernet Port(5Minute) T7138:Highest Transmit Rate of the FEGE Ethernet Port(5-Minute)
73441532
Description
These counters provide the receive rate or transmit rate of the FEGE Ethernet port at the Link layer in the 5-Minute measurement period. The rates measured here include the spending of the MAC header and the MAC payload of the MAC data.
Measurement point
1.Within a specified measurement period, the system measures the number of transmitted and received bytes every 5 seconds and accumulates the number of bytes at the end of every 5-minute sampling period to obtain the total number of bytes transmitted or received within the sampling period. 2.The system calculates the transmit and receive rate within every 5-minute sampling period with the following formula: Transmit and receive rate within a 5-minute sampling period = Total number of bytes transmitted and received within a 5-minute sampling period/300 3.The system compares all of the collected transmit and receive rates to obtain the highest transmit and receive rate within the specified measurement period, which is the value of the corresponding counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.FEGE.FIVE.MINUTES. RXMAXSPEED Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
Counter Name VS.FEGE.FIVE.MINUTES. TXMAXSPEED
2.12 Measurement of Fractional ATM Link Performance (FRACATMLNK)

Overview
Measurement of Fractional ATM Link Performance indicates the transmission quality of the Fractional ATM links on the AEUa or AOUc board.
FunctionSubSets
FunctionSubSet FRACATMLNK FunctionSubSet Name Fractional ATM Link Measurement
2.12.1 Fractional ATM Link Measurement(FRACATMLNK)

Overview
The quality of transmission links directly affects the system performance. Fractional ATM link measurement helps analyze system transmission quality so as to maintain system stability and reliability. Fractional ATM link belongs to the physical layer of the ATM reference model, as figure 1 shows.
Issue 01 (2013-05-04)
2765
In the configuration structure, fractional ATM links are between physical ports and logical applications, as shown in the figure 2. Figure 2-34 Physical bearer of the Fractional ATM
Issue 01 (2013-05-04)
2766
Counters
Counter ID 67193989 Counter Name VS.FRACATMLN K.TXCELLS Counter Description Number of Cells Transmitted on an Fractional ATM Link Number of Cells Received on an Fractional ATM Link Number of Error Cells Received on an Fractional ATM Link Number of Cells Discarded on an Fractional ATM Link Maximum Transmit Rate of an Fractional ATM Link Minimum Transmit Rate of an Fractional ATM Link Mean Transmit Rate of an Fractional ATM Link Maximum Receive Rate of an Fractional ATM Link Minimum Receive Rate of an Fractional ATM Link Mean Receive Rate of an Fractional ATM Link Mean Occupied Forward Bandwidth of an FRA ATM Link Original Release Earlier than V900R011
67193991
VS.FRACATMLN K.RXCELLS
67193993
VS.FRACATMLN K.RXHCSERRCE LLS VS.FRACATMLN K.RXDROPPEDC ELLS VS.FRACATMLN K.TXMAXSPEED VS.FRACATMLN K.TXMINSPEED VS.FRACATMLN K.TXMEANSPEE D VS.FRACATMLN K.RXMAXSPEED VS.FRACATMLN K.RXMINSPEED VS.FRACATMLN K.RXMEANSPEE D VS.FRACATMLN K.Alloced.Ave.Fwd
67193994
67193995
Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67193996
67193997
67193998
67193999
67194000
67204779
Issue 01 (2013-05-04)
2767
Counter ID 67204780
Counter Name VS.FRACATMLN K.Alloced.Ave.Bwd
Counter Description Mean Occupied Backward Bandwidth of an FRA ATM Link Maximum Occupied Forward Bandwidth of an FRA ATM Link Maximum Occupied Backward Bandwidth of an FRA ATM Link Number of Forward Congestions on an FRA ATM Link Duration of Forward Congestions on an FRA ATM Link Number of Backward Congestions on an FRA ATM Link Duration of Backward Congestions on an FRA ATM Link
67195938
VS.FRACATMLN K.Alloced.Max.Fw d VS.FRACATMLN K.Alloced.Max.Bw d VS.FRACATMLN K.Fwd.Cong VS.FRACATMLN K.Fwd.Cong.Dur VS.FRACATMLN K.Bwd.Cong
67195939
67195940
67195941
67195942
67195943
VS.FRACATMLN K.Bwd.Cong.Dur
None
2.12.1.1 Counters Related to the Number of Cells Received, Transmitted or Discarded on an Fractional ATM link Counters
Counter ID 67193989 67193991 Counter Name VS.FRACATMLNK.TXCE LLS VS.FRACATMLNK.RXCE LLS
Counter Description Number of Cells Transmitted on an Fractional ATM Link Number of Cells Received on an Fractional ATM Link
2768
Issue 01 (2013-05-04)
Counter ID 67193993
Counter Name VS.FRACATMLNK.RXHC SERRCELLS VS.FRACATMLNK.RXDR OPPEDCELLS
Counter Description Number of Error Cells Received on an Fractional ATM Link Number of Cells Discarded on an Fractional ATM Link
67193994
Description
These counters provide the number of cells received, transmitted or discarded on an Fractional ATM link in the specified measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of IEs transmitted, received or discarded on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.FRACATMLNK.TXCE LLS VS.FRACATMLNK.RXCE LLS VS.FRACATMLNK.RXHC SERRCELLS VS.FRACATMLNK.RXDR OPPEDCELLS Feature ID WRFD-050302 WRFD-050302 WRFD-050302 WRFD-050302 Feature Name Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface
2.12.1.2 Counters Related to the Receive Rate or Transmit Rate of an Fractional ATM link
Issue 01 (2013-05-04)
2769
Counters
Counter ID 67193995 67193996 67193997 67193998 67193999 67194000 Counter Name VS.FRACATMLNK.TXM AXSPEED VS.FRACATMLNK.TXMI NSPEED VS.FRACATMLNK.TXME ANSPEED VS.FRACATMLNK.RXM AXSPEED VS.FRACATMLNK.RXMI NSPEED VS.FRACATMLNK.RXME ANSPEED Counter Description Maximum Transmit Rate of an Fractional ATM Link Minimum Transmit Rate of an Fractional ATM Link Mean Transmit Rate of an Fractional ATM Link Maximum Receive Rate of an Fractional ATM Link Minimum Receive Rate of an Fractional ATM Link Mean Receive Rate of an Fractional ATM Link
Description
These counters provide the receive rate or transmit rate of an Fractional ATM link in the specified measurement period from different perspectives.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the link once every five seconds. With this, the system obtains the maximum and the minimum number of bytes received or transmitted in five seconds, and the total number of one measurement period. The maximum and minimum speed is calculated with the maximum and minimum bytes in five seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.FRACATMLNK.TXM AXSPEED VS.FRACATMLNK.TXMI NSPEED
Issue 01 (2013-05-04)
Feature Name Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface
2770
Counter Name VS.FRACATMLNK.TXME ANSPEED VS.FRACATMLNK.RXM AXSPEED VS.FRACATMLNK.RXMI NSPEED VS.FRACATMLNK.RXME ANSPEED
Feature Name Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface
2.12.1.3 Counters Related to the Occupied Forward Bandwidth or Backward Bandwidth of an FRA ATM Link Counters
Counter ID 67204779 Counter Name VS.FRACATMLNK.Alloce d.Ave.Fwd VS.FRACATMLNK.Alloce d.Ave.Bwd VS.FRACATMLNK.Alloce d.Max.Fwd VS.FRACATMLNK.Alloce d.Max.Bwd Counter Description Mean Occupied Forward Bandwidth of an FRA ATM Link Mean Occupied Backward Bandwidth of an FRA ATM Link Maximum Occupied Forward Bandwidth of an FRA ATM Link Maximum Occupied Backward Bandwidth of an FRA ATM Link
67204780
67195938
67195939
Description
These counters provide the forward bandwidth or backward bandwidth assigned to the FRA ATM link in the specified measurement period from different perspectives.
Measurement point
In the measurement period, the system automatically takes samples on the occupied forward bandwidth and backward bandwidth of an FRA ATM link every 15 seconds. At the end of the measurement period, the maximum occupied forward bandwidth and the maximum occupied backward bandwidth of an FRA ATM link in the measurement period are obtained. The mean occupied forward bandwidth of an FRA ATM link equals to the accumulated value of the occupied forward bandwidth at the sampling points divided by the number of sampling times.
The mean occupied backward bandwidth of an FRA ATM link equals to the accumulated value of the occupied backward bandwidth at the sampling points divided by the number of sampling times.
Formula
None
Unit
bit/s
Related Features
Counter Name VS.FRACATMLNK.Alloce d.Ave.Fwd VS.FRACATMLNK.Alloce d.Ave.Bwd VS.FRACATMLNK.Alloce d.Max.Fwd VS.FRACATMLNK.Alloce d.Max.Bwd Feature ID WRFD-050302 WRFD-050302 WRFD-050302 WRFD-050302 Feature Name Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface
2.12.1.4 Counters Related to the Number of Congestions on an FRA ATM Link Counters
Counter ID 67195940 Counter Name VS.FRACATMLNK.Fwd.C ong VS.FRACATMLNK.Bwd.C ong Counter Description Number of Forward Congestions on an FRA ATM Link Number of Backward Congestions on an FRA ATM Link
67195942
Description
These counters provide the number of congestions on the FRA ATM link in the specified measurement period.
Issue 01 (2013-05-04)
2772
Measurement point
This counter is incremented by one when an FRA ATM link changes from the non-congestion state to the congestion state (the remaining bandwidth available smaller than the congestion threshold).
Formula
None
Unit
None
Related Features
Counter Name VS.FRACATMLNK.Fwd.C ong VS.FRACATMLNK.Bwd.C ong Feature ID WRFD-050302 WRFD-050302 Feature Name Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface
2.12.1.5 Counters Related to the Duration of Congestions on an FRA ATM Link Counters
Counter ID 67195941 Counter Name VS.FRACATMLNK.Fwd.C ong.Dur VS.FRACATMLNK.Bwd.C ong.Dur Counter Description Duration of Forward Congestions on an FRA ATM Link Duration of Backward Congestions on an FRA ATM Link
67195943
Description
These counters provide the duration of congestion on an FRA ATM link in the measurement period. The following table describes the meaning of each counter. Counter Name VS.FRACATMLNK.Bwd.Cong.Dur Description Duration of backward congestions on an FRA ATM link
Issue 01 (2013-05-04)
2773
Measurement point
The measurement of a forward(backward) congestion duration starts when a forward(backward) congestion is generated on an FRA ATM link and stops when the forward(backward) congestion is cleared. In the measurement period, the accumulated forward(backward) congestion time on the FRA ATM link is taken as the value of this counter.
Formula
None
Unit
s
Related Features
Counter Name VS.FRACATMLNK.Fwd.C ong.Dur VS.FRACATMLNK.Bwd.C ong.Dur Feature ID WRFD-050302 WRFD-050302 Feature Name Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface
2.13 Measurement of Fractioanl IMA Link Performance (FRACIMALNK)

Overview
Measurement of Fractioanl IMA Link Performance indicates the transmission quality of the Fractional IMA links on the AEUa or AOUc board. In fractional IMA mode, multiple fractional IMA links logically form a group to increase the transmission bandwidth.
FunctionSubSets
FunctionSubSet FRACIMALNK FunctionSubSet Name Fractional IMA Link Measurement
2.13.1 Fractional IMA Link Measurement(FRACIMALNK)

Overview
The quality of transmission links directly affects the system performance. Fractional IMA Link measurement helps analyze system transmission quality so as to maintain system stability and reliability.
In the configuration structure, Fractional IMA links are between physical ports and logical applications, as shown in the figure 1. Figure 2-35 Physical bearer of the Fractional IMA
Counters
Counter ID 67194002 Counter Name VS.FRACIMALN K.TXUSERCELLS Counter Description Number of User Cells Transmitted on an Fractional IMA Link Number of Filling Cells Transmitted on an Fractional IMA Link Number of Cells Received on an Fractional IMA Link Number of Filling Cells Received on an Fractional IMA Link Original Release Earlier than V900R011
67194003
VS.FRACIMALN K.TXSTUFFCELL S VS.FRACIMALN K.RXUSERCELLS VS.FRACIMALN K.RXSTUFFCELL S
67194005
67194006
Issue 01 (2013-05-04)
2775
Counter ID 67194008
Counter Name VS.FRACIMALN K.RXDROPPEDC ELLS VS.FRACIMALN K.RXHCSERRCE LLS VS.FRACIMALN K.TXMAXSPEED VS.FRACIMALN K.TXMINSPEED VS.FRACIMALN K.TXMEANSPEE D VS.FRACIMALN K.RXMAXSPEED VS.FRACIMALN K.RXMINSPEED VS.FRACIMALN K.RXMEANSPEE D
Counter Description Number of Cells Discarded on an Fractional IMA Link Number of Error Cells Received on an Fractional IMA Link Maximum Transmit Rate of an Fractional IMA Link Minimum Transmit Rate of an Fractional IMA Link Mean Transmit Rate of an Fractional IMA Link Maximum Receive Rate of an Fractional IMA Link Minimum Receive Rate of an Fractional IMA Link Mean Receive Rate of an Fractional IMA Link
Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67194009
67194010
67194011
67194012
67194013
67194014
67194015
None
2.13.1.1 Counters Related to the Number of Cells Received, Transmitted or Discarded on an Fractional IMA Link Counters
Counter ID 67194002 Counter Name VS.FRACIMALNK.TXUSERCELLS Counter Description Number of User Cells Transmitted on an Fractional IMA Link
Issue 01 (2013-05-04)
2776
Counter ID 67194003
Counter Name VS.FRACIMALNK.TXST UFFCELLS VS.FRACIMALNK.RXUSERCELLS VS.FRACIMALNK.RXST UFFCELLS VS.FRACIMALNK.RXDR OPPEDCELLS VS.FRACIMALNK.RXHC SERRCELLS
Counter Description Number of Filling Cells Transmitted on an Fractional IMA Link Number of Cells Received on an Fractional IMA Link Number of Filling Cells Received on an Fractional IMA Link Number of Cells Discarded on an Fractional IMA Link Number of Error Cells Received on an Fractional IMA Link
67194005 67194006
67194008 67194009
Description
These counters provide the number of user cells received, transmitted or Discarded on an Fractional IMA Link in the measurement period to indicate the traffic volume of the Fractional IMA Link. The following table describes the meaning of each counter. Counter Name VS.FRACIMALNK.TXUSERCELLS VS.FRACIMALNK.TXSTUFFCELLS VS.FRACIMALNK.RXUSERCELLS VS.FRACIMALNK.RXSTUFFCELLS VS.FRACIMALNK.RXDROPPEDCELLS VS.FRACIMALNK.RXHCSERRCELLS Description Number of user cells transmitted on an Fractional IMA Link Number of filling cells transmitted on an Fractional IMA Link Number of user cells received on an Fractional IMA Link Number of filling cells received on an Fractional IMA Link Number of received cells discarded on an Fractional IMA Link due to errors in the link Number of cells with error HCS (Header Check Sequence) received on an Fractional IMA Link
Issue 01 (2013-05-04)
2777
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of IEs transmitted, received or discarded on the link once every five seconds and obtains the total number of IEs in one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.FRACIMALNK.TXUSERCELLS VS.FRACIMALNK.TXST UFFCELLS VS.FRACIMALNK.RXUSERCELLS VS.FRACIMALNK.RXST UFFCELLS VS.FRACIMALNK.RXDR OPPEDCELLS VS.FRACIMALNK.RXHC SERRCELLS Feature ID WRFD-050302 WRFD-050302 WRFD-050302 WRFD-050302 WRFD-050302 WRFD-050302 Feature Name Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface
2.13.1.2 Counters Related to the Receive Rate or Transmit Rate of an Fractional IMA Link Counters
Counter ID 67194010 67194011 67194012 Counter Name VS.FRACIMALNK.TXMA XSPEED VS.FRACIMALNK.TXMI NSPEED VS.FRACIMALNK.TXME ANSPEED
Counter Description Maximum Transmit Rate of an Fractional IMA Link Minimum Transmit Rate of an Fractional IMA Link Mean Transmit Rate of an Fractional IMA Link
2778
Issue 01 (2013-05-04)
Counter ID 67194013 67194014 67194015
Counter Name VS.FRACIMALNK.RXMA XSPEED VS.FRACIMALNK.RXMI NSPEED VS.FRACIMALNK.RXME ANSPEED
Counter Description Maximum Receive Rate of an Fractional IMA Link Minimum Receive Rate of an Fractional IMA Link Mean Receive Rate of an Fractional IMA Link
Description
These counters provide the receive rate or transmit rate of an Fractional IMA Link in the measurement period to indicate the load on an Fractional IMA Link. The following table describes the meaning of each counter. Counter Name VS.FRACIMALNK.TXMAXSPEED VS.FRACIMALNK.TXMINSPEED VS.FRACIMALNK.TXMEANSPEED VS.FRACIMALNK.RXMAXSPEED VS.FRACIMALNK.RXMINSPEED VS.FRACIMALNK.RXMEANSPEED Description Maximum transmit rate of an Fractional IMA Link Minimum transmit rate of an Fractional IMA Link Mean transmit rate of an Fractional IMA Link Maximum receive rate of an Fractional IMA Link Minimum receive rate of an Fractional IMA Link Mean receive rate of an Fractional IMA Link
Measurement point
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.FRACIMALNK.TXMA XSPEED VS.FRACIMALNK.TXMI NSPEED VS.FRACIMALNK.TXME ANSPEED VS.FRACIMALNK.RXMA XSPEED VS.FRACIMALNK.RXMI NSPEED VS.FRACIMALNK.RXME ANSPEED Feature ID WRFD-050302 WRFD-050302 WRFD-050302 WRFD-050302 WRFD-050302 WRFD-050302 Feature Name Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface Fractional ATM Function on Iub Interface
2.14 Measurement of IMA Group Performance(IMAGRP)

Overview
Measurement of IMA Group Performance indicates the transmission quality of the IMA group on the AEUa, AOUa or AOUc board.
FunctionSubSets
FunctionSubSet IMAGRP FunctionSubSet Name IMA Group Measurement
2.14.1 IMA Group Measurement(IMAGRP)

Overview
The quality of transmission links directly affects the system performance. IMA group measurement helps analyze system transmission quality so as to maintain system stability and reliability. IMA group belongs to the physical layer of the ATM reference model, as figure 1 shows.
Issue 01 (2013-05-04)
2780
In the configuration structure, IMA groups are between physical ports and logical applications, as shown in the figure 2.
Issue 01 (2013-05-04)
2781
Figure 2-37 Physical bearer of the IMA Group
Counters
Counter ID 67194017 Counter Name VS.IMAGROUP.R XUSERCELLS VS.IMAGROUP.R XSTUFFCELLS VS.IMAGROUP.P EAK.RXRATE VS.IMAGROUP.R XFILLERCELLS Counter Description Number of User Cells Received on an IMA Group Number of Filling Cells Received on an IMA Group Maximum Receive Rate of an IMA GROUP Number of decoupling Cells (Idle Cells Received when There Is No Cell to Transmit) Received on an IMA Group Number of User Cells Transmitted on an IMA Group Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67194018
67204457
67194020
67194021
VS.IMAGROUP.T XUSERCELLS
Issue 01 (2013-05-04)
2782
Counter ID 67194022
Counter Name VS.IMAGROUP.T XSTUFFCELLS VS.IMAGROUP.P EAK.TXRATE VS.IMAGROUP.T XFILLERCELLS
Counter Description Number of Filling Cells Transmitted on an IMA Group Maximum Transmit Rate of an IMA Group Number of Decoupling Cells (Idle Cells Received when There Is No Cell to Transmit) Transmitted on an IMA Group Number of Cells Discarded in Transmission on an IMA Group Number of Cells Discarded in Reception on an IMA Group Number of Error Cells Transmitted on an IMA Group Number of Error Cells Received on an IMA Group Mean Receive Rate of an IMA Group Mean Transmit Rate of an IMA Group Mean Occupied Forward Bandwidth of an IMA Group Mean Occupied Backward Bandwidth of an IMA Group Maximum Occupied Forward Bandwidth of an IMA Group
67204458
67194024
67194025
VS.IMAGROUP.T XDISCARD
67194026
VS.IMAGROUP.R XDROP
67194027
VS.IMAGROUP.T XERRORCELLS VS.IMAGROUP.R XERRORCELLS VS.IMA.Grp.Mean Kbps.Rx VS.IMA.Grp.Mean Kbps.Tx VS.IMAGRP.Alloc ed.Ave.Fwd VS.IMAGRP.Alloc ed.Ave.Bwd
67194028
67202907 67202908 67204192
67204193
67193215
VS.IMAGRP.Alloc ed.Max.Fwd
Issue 01 (2013-05-04)
2783
Counter ID 67193216
Counter Name VS.IMAGRP.Alloc ed.Max.Bwd
Counter Description Maximum Occupied Backward Bandwidth of an IMA Group Number of Forward Congestions on an IMA Group Duration of Forward Congestions on an IMA Group Number of Backward Congestions on an IMA Group Duration of Backward Congestions on an IMA Group
67193217
VS.IMAGRP.Fwd. Cong VS.IMAGRP.Fwd. Cong.Dur VS.IMAGRP.Bwd. Cong
67193218
67193219
67193220
VS.IMAGRP.Bwd. Cong.Dur
None
2.14.1.1 Counters Related to the Number of Cells Received or Transmitted on an IMA Group Counters
Counter ID 67194017 67194018 67194020 Counter Name VS.IMAGROUP.RXUSERCELLS VS.IMAGROUP.RXSTUFF CELLS VS.IMAGROUP.RXFILLERCELLS Counter Description Number of User Cells Received on an IMA Group Number of Filling Cells Received on an IMA Group Number of decoupling Cells (Idle Cells Received when There Is No Cell to Transmit) Received on an IMA Group Number of User Cells Transmitted on an IMA Group
67194021
VS.IMAGROUP.TXUSERCELLS
Issue 01 (2013-05-04)
2784
Counter ID 67194022
Counter Name VS.IMAGROUP.TXSTUFF CELLS VS.IMAGROUP.TXFILLERCELLS
Counter Description Number of Filling Cells Transmitted on an IMA Group Number of Decoupling Cells (Idle Cells Received when There Is No Cell to Transmit) Transmitted on an IMA Group Number of Cells Discarded in Transmission on an IMA Group Number of Cells Discarded in Reception on an IMA Group
67194024
67194025
VS.IMAGROUP.TXDISCARD VS.IMAGROUP.RXDROP
67194026
Description
These counters provide the number of cells received or transmitted on an IMA group in the measurement period. They indicate the transmission condition of the IMA group.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of IEs transmitted on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.IMAGROUP.RXUSERCELLS VS.IMAGROUP.RXSTUFF CELLS Feature ID WRFD-050304 Feature Name IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface
WRFD-050304
Issue 01 (2013-05-04)
2785
Counter Name VS.IMAGROUP.RXFILLERCELLS VS.IMAGROUP.TXUSERCELLS VS.IMAGROUP.TXSTUFF CELLS VS.IMAGROUP.TXFILLERCELLS VS.IMAGROUP.TXDISCARD VS.IMAGROUP.RXDROP
Feature Name IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface
WRFD-050304
WRFD-050304
WRFD-050304
WRFD-050304
WRFD-050304
2.14.1.2 Counters Related to the Receive Rate or Transmit Rate of an IMA Group Counters
Counter ID 67204457 67204458 67202907 67202908 Counter Name VS.IMAGROUP.PEAK.RX RATE VS.IMAGROUP.PEAK.TX RATE VS.IMA.Grp.MeanKbps.Rx VS.IMA.Grp.MeanKbps.Tx Counter Description Maximum Receive Rate of an IMA GROUP Maximum Transmit Rate of an IMA Group Mean Receive Rate of an IMA Group Mean Transmit Rate of an IMA Group
Description
These counters provide the receive rate or transmit rate of an IMA group in the measurement period. They indicate the load on the IMA group.
Issue 01 (2013-05-04)
2786
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the link once every five seconds. With this, the system obtains the maximum number of bytes received or transmitted in five seconds, and the total number of one measurement period. The maximum speed is calculated with the maximum bytes in five seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.IMAGROUP.PEAK.RX RATE VS.IMAGROUP.PEAK.TX RATE VS.IMA.Grp.MeanKbps.Rx Feature ID WRFD-050304 Feature Name IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface
WRFD-050304
WRFD-050304
VS.IMA.Grp.MeanKbps.Tx
WRFD-050304
2.14.1.3 Counters Related to the Number of Error Cells Received or Transmitted on an IMA Group Counters
Counter ID 67194028 67194027 Counter Name VS.IMAGROUP.RXERRORCELLS VS.IMAGROUP.TXERRORCELLS Counter Description Number of Error Cells Received on an IMA Group Number of Error Cells Transmitted on an IMA Group
Issue 01 (2013-05-04)
2787
Description
These counters provide the number of error cells received or transmitted on an IMA group in the measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of errored IEs transmitted and received on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.IMAGROUP.RXERRORCELLS VS.IMAGROUP.TXERRORCELLS Feature ID WRFD-050304 Feature Name IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface
WRFD-050304
2.14.1.4 Counters related to the Occupied Forward Bandwidth or Occupied Backward Bandwidth of an IMA Group Counters
Counter ID 67204192 67204193 67193215 Counter Name VS.IMAGRP.Alloced.Ave.F wd VS.IMAGRP.Alloced.Ave. Bwd VS.IMAGRP.Alloced.Max. Fwd VS.IMAGRP.Alloced.Max. Bwd Counter Description Mean Occupied Forward Bandwidth of an IMA Group Mean Occupied Backward Bandwidth of an IMA Group Maximum Occupied Forward Bandwidth of an IMA Group Maximum Occupied Backward Bandwidth of an IMA Group
67193216
Issue 01 (2013-05-04)
2788
Description
These counters provide the occupied forward bandwidth or occupied backward bandwidth of an IMA group from different perspectives.
Measurement point
In the measurement period, the system automatically takes samples on the occupied forward bandwidth and occupied backward bandwidth of an IMA group every 15 seconds. At the end of the measurement period, the maximum occupied forward bandwidth and the maximum occupied backward bandwidth are obtained. The mean occupied forward bandwidth equals to the accumulated value of the occupied forward bandwidth at the sampling points divided by the number of sampling times. The mean occupied backward bandwidth equals to the accumulated value of the occupied backward bandwidth at the sampling points divided by the number of sampling times.
Formula
None
Unit
bit/s
Related Features
Counter Name VS.IMAGRP.Alloced.Ave.F wd VS.IMAGRP.Alloced.Ave. Bwd VS.IMAGRP.Alloced.Max. Fwd VS.IMAGRP.Alloced.Max. Bwd Feature ID WRFD-05030106 WRFD-05030106 WRFD-05030106 WRFD-05030106 Feature Name Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth
2.14.1.5 Counters Related to the Number of Congestions on an IMA Group Counters

Counter ID 67193217 Counter Name VS.IMAGRP.Fwd.Cong Counter Description Number of Forward Congestions on an IMA Group
Issue 01 (2013-05-04)
2789
Counter ID 67193219
Counter Name VS.IMAGRP.Bwd.Cong
Counter Description Number of Backward Congestions on an IMA Group
Description
These counters provide the number of forward or backward congestions on an IMA group in the measurement period.
Measurement point
This measurement is incremented by one when an IMA group changes from the non-congestion state to the congestion state in the forward or backward direction(the remaining bandwidth available smaller than the congestion threshold).
Formula
None
Unit
None
Related Features
Counter Name VS.IMAGRP.Fwd.Cong VS.IMAGRP.Bwd.Cong Feature ID WRFD-05030106 WRFD-05030106 Feature Name Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth
2.14.1.6 Counters Related to the Duration of Congestion on an IMA Group Counters

Counter ID 67193218 Counter Name VS.IMAGRP.Fwd.Cong.Du r VS.IMAGRP.Bwd.Cong.Du r Counter Description Duration of Forward Congestions on an IMA Group Duration of Backward Congestions on an IMA Group
67193220
Issue 01 (2013-05-04)
2790
Description
These counters provide the duration of congestions on an IMA group. The following table describes the meaning of each counter. Counter Name VS.IMAGRP.Bwd.Cong.Dur Description Duration of backward congestions on an IMA group
Measurement point
The measurement of a forward(backward) congestion duration starts when a forward(backward) congestion is generated on an IMA group and stops when the forward(backward) congestion is cleared. In the measurement period, the accumulated forward(backward) congestion time on the IMA group is taken as the value of this counter.
Formula
None
Unit
s
Related Features
Counter Name VS.IMAGRP.Fwd.Cong.Du r VS.IMAGRP.Bwd.Cong.Du r Feature ID WRFD-05030106 WRFD-05030106 Feature Name Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth
2.15 Measurement of IMA Link Performance(IMALNK)

Overview
Measurement of IMA Link Performance indicates the transmission quality of the IMA link on the AEUa, AOUa or AOUc board.
FunctionSubSets
FunctionSubSet IMALNK FunctionSubSet Name IMA Link Measurement
Issue 01 (2013-05-04)
2791
2.15.1 IMA Link Measurement(IMALNK)

Overview
The quality of transmission links directly affects the system performance. IMA link measurement helps analyze system transmission quality so as to maintain system stability and reliability. IMA Link belongs to the physical layer of the ATM reference model, as figure 1 shows. Figure 2-38 ATM Reference Model
In the configuration structure, IMA links are between physical ports and logical applications, as shown in the figure 2.
Issue 01 (2013-05-04)
2792
Figure 2-39 Physical bearer of the IMA Link
Counters
Counter ID 67194029 Counter Name VS.IMALNK.RXU SERCELLS VS.IMALNK.RXU STUFFCELLS VS.IMALNK.PEA K.RXRATE VS.IMALNK.RXIDLECELLS VS.IMALNK.TXU SERCELLS VS.IMALNK.TXU STUFFCELLS Counter Description Number of User Cells Received on an IMA Link Number of Filling Cells Received on an IMA Link Maximum Cell Receive Rate of an IMA Link Number of idle Cells Received on an IMA Link Number of User Cells Transmitted on an IMA Link Number of Filling Cells Transmitted on an IMA Link Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67194030
67203408
67194032
67194033
67194034
Issue 01 (2013-05-04)
2793
Counter ID 67203409
Counter Name VS.IMALNK.PEA K.TXRATE VS.IMALNK.RXF ILTERCELLS
Counter Description Maximum Cell Transmit Rate of an IMA Link Number of User Cells Discarded on an IMA Link Due to Errors in the Link Number of Cells with Frame synchronization Error on an IMA Link Number of Cells with Error ICP(IMA Control Protocol) Received on an IMA Link Number of Cells with valid ICP(IMA Control Protocol) Received on an IMA Link Number of Cells with HCS(Header Check Sum) Error Received on an IMA Link Number of decoupling Cells (Idle Cells Received when There Is No Cell to Transmit) Received on an IMA Link Number of Times that a Fault Occurs in an IMA Link Number of Times that a Fault is Cleared in an IMA Link Duration of Faults in an IMA Link
67194036
67194037
VS.IMALNK.RXA NOMALY
67194038
VS.IMALNK.RXI CPVIOLATE
67194039
VS.IMALNK.RXI CPCELLS
67194040
VS.IMALNK.RXH CSERROR
67194041
VS.IMALNK.RXF ILLERCELLS
67194042
VS.IMALNK.FAU LTEMIT VS.IMALNK.FAU LTCLEAR VS.IMALNK.FAU LTTIME
67194043
67194044
Issue 01 (2013-05-04)
2794
Counter ID 67202909 67202910
Counter Name VS.IMA.Lnk.Mean Kbps.Rx VS.IMA.Lnk.Mean Kbps.Tx
Counter Description Mean Receive Rate of an IMA Link Mean Transmit Rate of an IMA Link
None
2.15.1.1 Counters Related to the Number of Packets Received or Transmitted on an IMA Link Counters
Counter ID 67194029 67194030 67194032 67194033 67194034 67194036 Counter Name VS.IMALNK.RXUSERCELLS VS.IMALNK.RXUSTUFFCELLS VS.IMALNK.RXIDLECELLS VS.IMALNK.TXUSERCELLS VS.IMALNK.TXUSTUFFCELLS VS.IMALNK.RXFILTERCELLS VS.IMALNK.RXANOMALY VS.IMALNK.RXICPVIOLATE VS.IMALNK.RXICPCELLS Counter Description Number of User Cells Received on an IMA Link Number of Filling Cells Received on an IMA Link Number of idle Cells Received on an IMA Link Number of User Cells Transmitted on an IMA Link Number of Filling Cells Transmitted on an IMA Link Number of User Cells Discarded on an IMA Link Due to Errors in the Link Number of Cells with Frame synchronization Error on an IMA Link Number of Cells with Error ICP(IMA Control Protocol) Received on an IMA Link Number of Cells with valid ICP(IMA Control Protocol) Received on an IMA Link
67194037
67194038
67194039
Issue 01 (2013-05-04)
2795
Counter ID 67194040
Counter Name VS.IMALNK.RXHCSERROR VS.IMALNK.RXFILLERCELLS
Counter Description Number of Cells with HCS (Header Check Sum) Error Received on an IMA Link Number of decoupling Cells (Idle Cells Received when There Is No Cell to Transmit) Received on an IMA Link
67194041
Description
These counters provide the number of cells received or transmitted on an IMA link in the specified measurement period from different perspectives. They indicate the transmission condition of the IMA link.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of cells transmitted and received on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.IMALNK.RXUSERCELLS VS.IMALNK.RXUSTUFFCELLS VS.IMALNK.RXIDLECELLS VS.IMALNK.TXUSERCELLS Feature ID WRFD-050304 Feature Name IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface
WRFD-050304
WRFD-050304
WRFD-050304
Issue 01 (2013-05-04)
2796
Counter Name VS.IMALNK.TXUSTUFFCELLS VS.IMALNK.RXFILTERCELLS VS.IMALNK.RXANOMALY VS.IMALNK.RXICPVIOLATE VS.IMALNK.RXICPCELLS VS.IMALNK.RXHCSERROR VS.IMALNK.RXFILLERCELLS
Feature Name IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface
WRFD-050304
WRFD-050304
WRFD-050304
WRFD-050304
WRFD-050304
WRFD-050304
2.15.1.2 Counters Related to the Receive Rate or Transmit Rate of an IMA Link Counters
Counter ID 67203408 67203409 67202909 67202910 Counter Name VS.IMALNK.PEAK.RXRA TE VS.IMALNK.PEAK.TXRA TE VS.IMA.Lnk.MeanKbps.Rx VS.IMA.Lnk.MeanKbps.Tx Counter Description Maximum Cell Receive Rate of an IMA Link Maximum Cell Transmit Rate of an IMA Link Mean Receive Rate of an IMA Link Mean Transmit Rate of an IMA Link
Description
These counters provide the receive rate or transmit rate of an IMA link in the specified measurement period from different perspectives. They indicate the load on the IMA link.
Measurement point
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.IMALNK.PEAK.RXRA TE VS.IMALNK.PEAK.TXRA TE VS.IMA.Lnk.MeanKbps.Rx Feature ID WRFD-050304 Feature Name IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface
WRFD-050304
WRFD-050304
VS.IMA.Lnk.MeanKbps.Tx
WRFD-050304
2.15.1.3 Number of Times That a Fault Occurs in an IMA Link Counters

Counter ID 67194042 Counter Name VS.IMALNK.FAULTEMIT Counter Description Number of Times that a Fault Occurs in an IMA Link
Description
This counter provides the number of times that a fault occurs in an IMA Link in the specified measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. If the system is in faulty state at the current sampling point but in normal state at the previous sampling point, the number of faults is added by one.
Formula
None
Unit
None
Related Features
Counter Name VS.IMALNK.FAULTEMIT Feature ID WRFD-050304 Feature Name IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface
2.15.1.4 Number of Times That a Fault Is Cleared in an IMA Link Counters

Counter ID 67194043 Counter Name VS.IMALNK.FAULTCLEAR Counter Description Number of Times that a Fault is Cleared in an IMA Link
Description
This counter provides the number of times that a fault is cleared in an IMA link in the specified measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. If the system is in normal state at the current sampling point but in faulty state at the previous sampling point, the number of faults that are cleared is added by one.
Formula
None
Unit
None
Related Features
Counter Name VS.IMALNK.FAULTCLEAR Feature ID WRFD-050304 Feature Name IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface
2.15.1.5 Duration of Faults in an IMA Link Counters

Counter ID 67194044 Counter Name VS.IMALNK.FAULTTIME Counter Description Duration of Faults in an IMA Link
Description
This counter provides the duration of faults that occur in an IMA link in the specified measurement period.
Measurement point
Formula
None
Unit
s
Related Features
Counter Name VS.IMALNK.FAULTTIME Feature ID WRFD-050304 Feature Name IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface
Issue 01 (2013-05-04)
2800
2.16 Measurement of IPoA Link Performance(IPOALNK)

Overview
Measurement of IPoA Link Performance indicates the transmission quality of the IPoA links in the ATM layer on the AEUa, AOUa, UOIa, AOUc or UOIc.
FunctionSubSets
FunctionSubSet IPOALNK FunctionSubSet Name IPoA Link Measurement
2.16.1 IPoA Link Measurement(IPOALNK)

Overview
Transmission links are important resources of the Base Station Controller system. The quality of the transmission links directly affects the system performance. Therefore, you can take statistics of the traffic in the ATM layer on the transmission links based on the IPoA link measurement. This is to analyze the transmission quality of and maintain the stable and secure operation of the system. Figure 1 shows the location of the ATM Layer in the procotol. Figure 2-40 ATM Reference Model
Issue 01 (2013-05-04)
2801
The configuration structure is as shown in the figure 2. Figure 2-41 Physical bearer of the IPOA Link
Counters
Counter ID 67194073 Counter Name VS.IPOALNK.RX CORRECTCELLS VS.IPOALNK.RX BYTES VS.IPOALNK.PE AK.RXRATE VS.IPOALNK.TX CORRECTCELLS VS.IPOALNK.TX BYTES Counter Description Number of Correct Cells Received on the IPoA Link Number of Bytes Received on an IPoA Link Maximum Receive Rate of an IPoA Link Number of Correct Cells Transmitted on an IPoA Link Number of Bytes Transmitted on an IPoA Link Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67194074
67204471 67194076
67194077
Issue 01 (2013-05-04)
2802
Counter ID 67204472 67194079
Counter Name VS.IPOALNK.PE AK.TXRATE VS.IPOALNK.DR OPFORHEADCE LLS VS.IPOALNK.DR OPFORRXOVER FLOWCELLS
Counter Description Maximum Transmit Rate of an IPoA Link Number of Cells Discarded on an IPoA Link Due to Packet Header Error Number of Cells Discarded on an IPoA Link Due to the Overflow of the input Buffer Number of Cells Discarded on an IPoA Link Due to the Overflow of the output Buffer
67194080
67194081
VS.IPOALNK.DR OPFORTXOVERF LOWCELLS
None
2.16.1.1 Counters Related to the Number of Cells Received or Transmitted Correctly on An IPoA Link Counters
Counter ID 67194073 67194076 Counter Name VS.IPOALNK.RXCORRECTCELLS VS.IPOALNK.TXCORRECTCELLS Counter Description Number of Correct Cells Received on the IPoA Link Number of Correct Cells Transmitted on an IPoA Link
Description
These counters provide the number of cells received or transmitted correctly on an IPoA link at the ATM layer in the specified measurement period. They indicate the traffic volume of the IPoA link.
Issue 01 (2013-05-04)
2803
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of IEs successfully transmitted and received on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.IPOALNK.RXCORRECTCELLS VS.IPOALNK.TXCORRECTCELLS Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic Permanent AAL5 Connections for Control Plane Traffic
WRFD-05030105
2.16.1.2 Counters Related to the Number of Bytes Received or Transmitted on an IPoA Link Counters
Counter ID 67194074 67194077 Counter Name VS.IPOALNK.RXBYTES VS.IPOALNK.TXBYTES Counter Description Number of Bytes Received on an IPoA Link Number of Bytes Transmitted on an IPoA Link
Description
These counters provide the number of bytes received or transmitted on an IPoA link at the ATM layer in the specified measurement period. They indicate the traffic volume of the IPoA link.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes transmitted and received on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.IPOALNK.RXBYTES Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic Permanent AAL5 Connections for Control Plane Traffic
VS.IPOALNK.TXBYTES
WRFD-05030105
2.16.1.3 Counters Related to the Maximum Receive Rate or the Maximum Transmit Rate of an IPoA Link Counters
Counter ID 67204471 67204472 Counter Name VS.IPOALNK.PEAK.RXR ATE VS.IPOALNK.PEAK.TXR ATE Counter Description Maximum Receive Rate of an IPoA Link Maximum Transmit Rate of an IPoA Link
Description
These counters provide the maximum receive rate or the maximum transmit rate of an IPoA link at the ATM layer in the specified measurement period. They indicate the maximum load on the IPoA link.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the link once every five seconds. With this, the system obtains the maximum number of bytes received or transmitted in five seconds. The maximum speed is calculated with the maximum bytes in five seconds.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.IPOALNK.PEAK.RXR ATE VS.IPOALNK.PEAK.TXR ATE Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic Permanent AAL5 Connections for Control Plane Traffic
WRFD-05030105
2.16.1.4 Counters Related to the Number of Cells Discarded on an IPoA Link Counters
Counter ID 67194079 Counter Name VS.IPOALNK.DROPFORHEADCELLS VS.IPOALNK.DROPFORRXOVERFLOWCELLS VS.IPOALNK.DROPFORTXOVERFLOWCELLS Counter Description Number of Cells Discarded on an IPoA Link Due to Packet Header Error Number of Cells Discarded on an IPoA Link Due to the Overflow of the input Buffer Number of Cells Discarded on an IPoA Link Due to the Overflow of the output Buffer
67194080
67194081
Description
These counters provide the number of cells discarded on an IPoA link at the ATM layer in the specified measurement period from different perspectives. They indicate the transmission quality of the cells on the IPoA link.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of IEs discarded on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.IPOALNK.DROPFORHEADCELLS VS.IPOALNK.DROPFORRXOVERFLOWCELLS VS.IPOALNK.DROPFORTXOVERFLOWCELLS Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic Permanent AAL5 Connections for Control Plane Traffic Permanent AAL5 Connections for Control Plane Traffic
WRFD-05030105
WRFD-05030105
2.17 Measurement of VCL PM on an IPOAPVC link (IPOAPVC_VCLPM)

Overview
The Measurement of VCL PM on an IPOAPVC link provides the statistics of PM on the ATM layer of the IPOAPVC link for the AOUc and UOIc boards. The IPOAPVC PM function uses forward performance monitoring (FPM) and backward reporting (BR) cells to monitor the number of transmitted and received cells at both ends of the ATM layer on the IPOAPVC link. Before viewing the IPOAPVC PM result, run the ACT VCLPM command to activate the PM function on the IPOAPVC link. The PM function can be activated in three directions: SOURCE, SINK, and BOTH. In the source direction, the source endpoint sends FPM cells to calculate the transmitted cells. In the sink direction, the sink endpoint responds with BR cells to calculate the received cells. BOTH means that an endpoint serves both as a source endpoint and a sink endpoint to send and receive FPM cells. In BOTH mode, both the transmitted and received cells are calculated.
FunctionSubSets
FunctionSubSet IPOAPVC.VCLPM FunctionSubSet Name Measurement Related to VCL PM on an IPOAPVC link
Issue 01 (2013-05-04)
2807
2.17.1 Measurement Related to VCL PM on an IPOAPVC link (IPOAPVC.VCLPM)

Overview
This measurement uses FPM and BR cells to monitor the ATM transmission quality of a path. In the source direction, FPM cells are sent periodically to indicate the number of transmitted cells and the number of error cells that failed the Bit Interleaved Parity 16 (BIP16) check. In the sink direction, BR cells are transmitted as response to the FPM cells. The BR cells calculate the number of received cells and the number of error cells that fail the BIP16 check. In the source direction, BR cells are used to calculate the number of discarded cells and the number of cells that are inserted by mistake. In the sink direction, FPM cells are used to calculate the number of discarded cells and the number of cells that are inserted by mistake.
Counters
Counter ID 73441412 Counter Name VS.IPOAPVC.VC LPM.RXCELL VS.IPOAPVC.VC LPM.TXCELL Counter Description Number of Received VCL PM Cells on an IPOAPVC link Number of Transmitted VCL PM Cells on an IPOAPVC link Maximum Receive Rate of VCL PM on an IPOAPVC link Maximum Transmit Rate of VCL PM on an IPOAPVC link Average VCL PM Cell Discard Rate in the Receive Direction of an IPOAPVC link Maximum VCL PM Cell Discard Rate in the Receive Direction of an IPOAPVC link Average VCL PM Cell Discard Rate in the Transmit Direction of an IPOAPVC link Original Release V900R014
73441413
V900R014
73441414
VS.IPOAPVC.VC LPM.PEAK.RXRA TE VS.IPOAPVC.VC LPM.PEAK.TXRA TE VS.IPOAPVC.VC LPM.RX.MEAN.L OSTCELLRATE
V900R014
73441415
V900R014
73441416
V900R014
73441417
VS.IPOAPVC.VC LPM.RX.PEAK.L OSTCELLRATE
V900R014
73441418
VS.IPOAPVC.VC LPM.TX.MEAN.L OSTCELLRATE
V900R014
Issue 01 (2013-05-04)
2808
Counter ID 73441419
Counter Name VS.IPOAPVC.VC LPM.TX.PEAK.L OSTCELLRATE
Counter Description Maximum VCL PM Cell Discard Rate in the Transmit Direction of an IPOAPVC link Average Rate of Incorrectly Inserted VCL PM Cells in the Receive Direction of an IPOAPVC link Maximum Rate of Incorrectly Inserted VCL PM Cells in the Receive Direction of an IPOAPVC link Average Rate of Incorrectly Inserted VCL PM Cells in the Transmit Direction of an IPOAPVC link Maximum Rate of Incorrectly Inserted VCL PM Cells in the Transmit Direction of an IPOAPVC link Number of VCL PM Error Cell Blocks Failed the BIP16 Check in the Source Direction of an IPOAPVC link Number of VCL PM Error Cell Blocks Failed the BIP16 Check in the Sink Direction of an IPOAPVC link
73441420
VS.IPOAPVC.VC LPM.RX.MEAN.E RRINSERTCELL RATE VS.IPOAPVC.VC LPM.RX.PEAK.E RRINSERTCELL RATE VS.IPOAPVC.VC LPM.TX.MEAN.E RRINSERTCELL RATE VS.IPOAPVC.VC LPM.TX.PEAK.E RRINSERTCELL RATE VS.IPOAPVC.VC LPM.SOURCEBIP 16CRCERRCELL
V900R014
73441421
V900R014
73441422
V900R014
73441423
V900R014
73424558
V900R014
73424559
VS.IPOAPVC.VC LPM.SINKBIP16C RCERRCELL
V900R014
None
2.17.1.1 Number of VCL PM Cells on an IPOAPVC link

Counters
Counter ID 73441412 Counter Name VS.IPOAPVC.VCLPM.RX CELL VS.IPOAPVC.VCLPM.TX CELL Counter Description Number of Received VCL PM Cells on an IPOAPVC link Number of Transmitted VCL PM Cells on an IPOAPVC link
73441413
Description
These counters provide the number of received and transmitted cells at the ATM layer along an IPOAPVC link. Only ATM cells are calculated.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. The RNC measures the number of cells transmitted at the ATM layers along an IPOAPVC link every 5 seconds and measures the total number at the end of each measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.IPOAPVC.VCLPM.RX CELL VS.IPOAPVC.VCLPM.TX CELL Feature ID WRFD-05030110 WRFD-05030110 Feature Name F5 F5
2.17.1.2 Maximum Data Rate of VCL PM on an IPOAPVC link
Issue 01 (2013-05-04)
2810
Counters
Counter ID 73441414 Counter Name VS.IPOAPVC.VCLPM.PE AK.RXRATE VS.IPOAPVC.VCLPM.PE AK.TXRATE Counter Description Maximum Receive Rate of VCL PM on an IPOAPVC link Maximum Transmit Rate of VCL PM on an IPOAPVC link
73441415
Description
These counters provide the maximum receive and transmit rates on an IPOAPVC link, indicating the maximum load in the receive and transmit directions on an IPOAPVC link.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. The RNC measures the number of cells received and transmitted at the ATM layer along an IPOAPVC link every 5 seconds. It compares and obtains the maximum number of received and transmitted cells per 5 seconds within a measurement period and accordingly calculates the maximum receive and transmit rates. The counters are in the unit of kbit/s, and are calculated with the following formula: Maximum receive and transmit rates = Maximum number of received/transmitted cells x 53 x 8/5/1000.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.IPOAPVC.VCLPM.PE AK.RXRATE VS.IPOAPVC.VCLPM.PE AK.TXRATE Feature ID WRFD-05030110 WRFD-05030110 Feature Name F5 F5
2.17.1.3 VCL PM Cell Discard Rate on an IPOAPVC link
Issue 01 (2013-05-04)
2811
Counters
Counter ID 73441416 Counter Name VS.IPOAPVC.VCLPM.RX. MEAN.LOSTCELLRATE Counter Description Average VCL PM Cell Discard Rate in the Receive Direction of an IPOAPVC link Maximum VCL PM Cell Discard Rate in the Receive Direction of an IPOAPVC link Average VCL PM Cell Discard Rate in the Transmit Direction of an IPOAPVC link Maximum VCL PM Cell Discard Rate in the Transmit Direction of an IPOAPVC link
73441417
VS.IPOAPVC.VCLPM.RX. PEAK.LOSTCELLRATE
73441418
VS.IPOAPVC.VCLPM.TX. MEAN.LOSTCELLRATE
73441419
VS.IPOAPVC.VCLPM.TX. PEAK.LOSTCELLRATE
Description
These counters provide the average and maximum rates of cells that are discarded in the receive and transmit directions on an IPOAPVC link. They are used to monitor the error rate of transmission cells on an IPOAPVC link.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. Every 5 seconds within a measurement period, the RNC measures the number of cells that are discarded in the receive and transmit directions at the ATM layers along an IPOAPVC link and compares to obtain the maximum number. To obtain the maximum cell discard rates in the receive and transmit directions, in each direction, the RNC divides the maximum number of cells that are discarded within 5 seconds by the total number of cells measured in those directions during the same period. To obtain the average cell discard rates in the receive and transmit directions, in each direction, the RNC divides the number of cells discarded by the total number of cells measured in those directions.
Formula
None
Unit
%
Issue 01 (2013-05-04)
2812
Related Features
Counter Name VS.IPOAPVC.VCLPM.RX. MEAN.LOSTCELLRATE VS.IPOAPVC.VCLPM.RX. PEAK.LOSTCELLRATE VS.IPOAPVC.VCLPM.TX. MEAN.LOSTCELLRATE VS.IPOAPVC.VCLPM.TX. PEAK.LOSTCELLRATE Feature ID WRFD-05030110 WRFD-05030110 WRFD-05030110 WRFD-05030110 Feature Name F5 F5 F5 F5
2.17.1.4 Rate of Incorrectly Inserted VCL PM Cells on an IPOAPVC link Counters

Counter ID 73441420 Counter Name VS.IPOAPVC.VCLPM.RX. MEAN.ERRINSERTCELLRATE VS.IPOAPVC.VCLPM.RX. PEAK.ERRINSERTCELLRATE Counter Description Average Rate of Incorrectly Inserted VCL PM Cells in the Receive Direction of an IPOAPVC link Maximum Rate of Incorrectly Inserted VCL PM Cells in the Receive Direction of an IPOAPVC link Average Rate of Incorrectly Inserted VCL PM Cells in the Transmit Direction of an IPOAPVC link Maximum Rate of Incorrectly Inserted VCL PM Cells in the Transmit Direction of an IPOAPVC link
73441421
73441422
VS.IPOAPVC.VCLPM.TX. MEAN.ERRINSERTCELLRATE VS.IPOAPVC.VCLPM.TX. PEAK.ERRINSERTCELLRATE
73441423
Description
These counters provide the average and maximum rates of cells that are incorrectly inserted in the receive and transmit directions on an IPOAPVC link. They are used to monitor the error rate of transmission cells on an IPOAPVC link.
Issue 01 (2013-05-04)
2813
Measurement point
Samples are taken every 5 seconds in the specified measurement period. Every 5 seconds within a measurement period, the RNC measures the number of cells that are incorrectly inserted in the receive and transmit directions at the ATM layers along an IPOAPVC link and compares to obtain the maximum number. To obtain the maximum rates of incorrectly inserted cells in the receive and transmit directions, in each direction, the RNC divides the maximum number of cells that are incorrectly inserted within 5 seconds by the total number of cells measured in those directions during the same period. To obtain the average rates of incorrectly inserted cells in the receive and transmit directions, in each direction, the RNC divides the total number of incorrectly inserted cells by the total number of measured cells in those directions during a measurement period.
Formula
None
Unit
%
Related Features
Counter Name VS.IPOAPVC.VCLPM.RX. MEAN.ERRINSERTCELLRATE VS.IPOAPVC.VCLPM.RX. PEAK.ERRINSERTCELLRATE VS.IPOAPVC.VCLPM.TX. MEAN.ERRINSERTCELLRATE VS.IPOAPVC.VCLPM.TX. PEAK.ERRINSERTCELLRATE Feature ID WRFD-05030110 Feature Name F5
WRFD-05030110
F5
WRFD-05030110
F5
WRFD-05030110
F5
2.17.1.5 Number of Error VCL PM Cell Blocks Failed BIP16 Check on an IPOAPVC link
Issue 01 (2013-05-04)
2814
Counters
Counter ID 73424558 Counter Name VS.IPOAPVC.VCLPM.SO URCEBIP16CRCERRCELL Counter Description Number of VCL PM Error Cell Blocks Failed the BIP16 Check in the Source Direction of an IPOAPVC link Number of VCL PM Error Cell Blocks Failed the BIP16 Check in the Sink Direction of an IPOAPVC link
73424559
VS.IPOAPVC.VCLPM.SIN KBIP16CRCERRCELL
Description
These counters provide the number of error cell blocks that fail the BIP16 check in the receive and transmit directions on an IPOAPVC link. They are used to monitor the error rate of transmission cells on an IPOAPVC link.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. The RNC measures the number of error cell blocks that fail the BIP16 check in the source and link directions at the ATM layer along an IPOAPVC link every 5 seconds and calculates the total number at the end of each measurement period. In each cell block measured for this counter, none of the cells is discarded or incorrectly inserted.
Formula
None
Unit
None
Related Features
Counter Name VS.IPOAPVC.VCLPM.SO URCEBIP16CRCERRCELL VS.IPOAPVC.VCLPM.SIN KBIP16CRCERRCELL Feature ID WRFD-05030110 Feature Name F5
WRFD-05030110
F5
Issue 01 (2013-05-04)
2815
2.18 Measurement of IP Path Performance(IPPATH)

Overview
IP Path performance measurement indicates the IP transport link.
FunctionSubSets
FunctionSubSet IPPATH FunctionSubSet Name IP Path Link Measurement
2.18.1 IP Path Link Measurement(IPPATH)

Overview
The quality of transmission links directly affects the system performance. IP path measurement helps analyze system transmission quality so as to maintain system stability and reliability. Figure 2-42 Physical bearer of the IP path
Issue 01 (2013-05-04)
2816
Counters
Counter ID 67204207 Counter Name VS.IPPATH.Act.C on VS.IPPATH.PING. MeanDELAY VS.IPPATH.PING. MaxDELAY VS.IPPATH.PING. MeanJITTER VS.IPPATH.PING. MaxJITTER VS.IPPATH.PING. MeanLOST VS.IPPATH.PING. MaxLOST VS.IPPATH.Fwd.C ong Counter Description T6551:Number of Active Connections on an IP Path T6552:Average IP Path Ping Delay T6553:Maximum IP Path Ping Delay T6554:Average IP Path Ping Delay variation T6555:Maximum IP Path Ping Delay variation T6556:Average IP Path Ping Packet Loss Rate T6557:Maximum IP Path Ping Packet Loss Rate T6558:Number of Forward Congestions on the IP Path T6559:Duration of Forward Congestion on the IP Path T6560:Number of Backward Congestions on the IP Path T6561:Duration of Backward Congestion on the IP PATH Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67204390 67194636 67204391
67194639
67204392
67194642
67195599
67195600
VS.IPPATH.Fwd.C ong.Dur VS.IPPATH.Bwd. Cong
67195601
67195602
VS.IPPATH.Bwd. Cong.Dur
None
Issue 01 (2013-05-04)
2817
2.18.1.1 Number of Active Connections on an IP Path Counters

Counter ID 67204207 Counter Name VS.IPPATH.Act.Con Counter Description T6551:Number of Active Connections on an IP Path
Description
This counter provides the number of active connections on an IP path in a specified measurement period. This counter indicates the transmission on a single IP path.
Measurement point
In the specified measurement period, the system automatically samples the number of active connections on an IP path every 15 seconds. At the end of the specified measurement period, the system divides the accumulated active connections by the number of samples to obtain the average number of active connections.
Formula
None
Unit
None
Related Features
Counter Name VS.IPPATH.Act.Con Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.18.1.2 Average IP Path Ping Delay
Issue 01 (2013-05-04)
2818
Counters
Counter ID 67204390 Counter Name VS.IPPATH.PING.MeanDELAY Counter Description T6552:Average IP Path Ping Delay
Description
This counter provides the average ping delay of an IP path in a specified measurement period. It takes effect only when the IPPATH PING function is enabled. The formula is as follow: The n times ping delay = Receive time of packet n - Send time of packet n (unit:ms)
Measurement point
In the specified measurement period, the system automatically samples the IP path ping delay every 5 minutes. At the end of the specified measurement period, the system divides the accumulated IP path ping delay by the number of samples to obtain the average IP path ping delay.
Formula
None
Unit
ms
Related Features
Counter Name VS.IPPATH.PING.MeanDELAY Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.18.1.3 Maximum IP Path Ping Delay Counters

Counter ID 67194636 Counter Name VS.IPPATH.PING.MaxDELAY Counter Description T6553:Maximum IP Path Ping Delay
Issue 01 (2013-05-04)
2819
Description
This counter provides the maximum ping delay of an IP path in a specified measurement period. It takes effect only when the IPPATH PING function is enabled.
Measurement point
The system automatically samples the IP path ping delay every 5 minutes. In the specified measurement period, the maximum ping delay is set to be this counter.
Formula
None
Unit
ms
Related Features
Counter Name VS.IPPATH.PING.MaxDELAY Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.18.1.4 Average IP Path Ping Delay Variation Counters

Counter ID 67204391 Counter Name VS.IPPATH.PING.MeanJITTER Counter Description T6554:Average IP Path Ping Delay variation
Description
This counter provides the average ping delay variation of an IP path in the measurement period. It takes effect only when the IPPATH PING function is enabled. The definition of the delay variation is as follow (from RFC1889[Page 27]): If Si is the RTP timestamp from packet i, and Ri is the time of arrival in RTP timestamp units for packet i, then for two packets i and j, D may be expressed as D(i,j)=(Rj-Ri)-(Sj-Si)=(Rj-Sj)-(Ri-Si)
The interarrival jitter is calculated continuously as each data packet i is received from source SSRC_n, using this difference D for that packet and the previous packet i-1 in order of arrival (not necessarily in sequence), according to the formula J=J+(|D(i-1,i)|-J)/16 Whenever a reception report is issued, the current value of J is sampled. The jitter calculation is prescribed here to allow profile-independent monitors to make valid interpretations of reports coming from different implementations. This algorithm is the optimal first-order estimator and the gain parameter 1/16 gives a good noise reduction ratio while maintaining a reasonable rate of convergence.
Measurement point
In the specified measurement period, the system automatically samples the IP path ping delay variation every 5 minutes. At the end of the specified measurement period, the system divides the accumulated IP path ping delay variation by the number of samples to obtain the average IP path ping delay variation.
Formula
None
Unit
ms
Related Features
Counter Name VS.IPPATH.PING.MeanJITTER Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.18.1.5 Maximum IP Path Ping Delay Variation Counters

Counter ID 67194639 Counter Name VS.IPPATH.PING.MaxJITTER Counter Description T6555:Maximum IP Path Ping Delay variation
Issue 01 (2013-05-04)
2821
Description
This counter provides the maximum ping delay variation of an IP path in the specified measurement period. It takes effect only when the IPPATH PING function is enabled.
Measurement point
The system automatically samples the IP path ping delay every 5 minutes. In the specified measurement period, the max ping delay is set to be this counter.
Formula
None
Unit
ms
Related Features
Counter Name VS.IPPATH.PING.MaxJITTER Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.18.1.6 Average IP Path Ping Packet Loss Rate Counters

Counter ID 67204392 Counter Name VS.IPPATH.PING.MeanLOST Counter Description T6556:Average IP Path Ping Packet Loss Rate
Description
This counter provide the ping packet loss rate of an IP path in the specified measurement period. It takes effect only when the IPPATH PING function is enabled.Services will be affected if many IP paths have a high packet loss rate.
Measurement point
In the measurement period, the system automatically samples the number of IP path ping request packets and the number of IP path ping received packets every 5 minutes. At the end of the
measurement period, the system divides the accumulated received packets by the accumulated request packets to obtain the average IP path ping packet loss rate.
Formula
None
Unit
%
Related Features
Counter Name VS.IPPATH.PING.MeanLOST Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.18.1.7 Maximum IP Path Ping Packet Loss Rate Counters

Counter ID 67194642 Counter Name VS.IPPATH.PING.MaxLOST Counter Description T6557:Maximum IP Path Ping Packet Loss Rate
Description
This counter provides the maximum ping packet loss rate of an IP path in the specified measurement period. It takes effect only when the IPPATH PING function is enabled.
Measurement point
In the measurement period, the system automatically samples the number of IP path ping request packets and the number of IP path ping received packets every 5 minutes. At the end of the measurement period, the system divides the accumulated received packets by the accumulated request packets to obtain the average IP path ping packet loss rate. The max IP path ping packet loss rate is set to be this counter.
Formula
None
Unit
%
Related Features
Counter Name VS.IPPATH.PING.MaxLOST Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.18.1.8 Counters Related to the Number of Congestions on an IP Path Counters

Counter ID 67195599 67195601 Counter Name VS.IPPATH.Fwd.Cong VS.IPPATH.Bwd.Cong Counter Description T6558:Number of Forward Congestions on the IP Path T6560:Number of Backward Congestions on the IP Path
Description
These counters provide the number of forward and backward admission congestions on an IP path in a specified measurement period. The forward direction indicates the sending direction, and the backward direction indicates the receiving direction.These counters can be used together with the duration of IP path congestion to analyze the congestion. Services will be affected if many IP paths are congested for a long period.
Measurement point
The RNC checks the state of an IP path each time a service is being admitted to that path. The counter value is increased by one each time the state of the IP path changes from non-congestion to congestion(The remaining bandwidth available is smaller than the congestion remain threshold). This counter is invalid when the real flow access control switch is turned on.
Formula
None
Unit
None
Related Features
Counter Name VS.IPPATH.Fwd.Cong Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.IPPATH.Bwd.Cong WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.18.1.9 Counters Related to the Duration of Congestion on an IP Path Counters

Counter ID 67195600 67195602 Counter Name VS.IPPATH.Fwd.Cong.Dur VS.IPPATH.Bwd.Cong.Dur Counter Description T6559:Duration of Forward Congestion on the IP Path T6561:Duration of Backward Congestion on the IP PATH
Description
These counters provide the duration of forward and backward congestions on an IP path in the measurement period. The forward direction indicates the sending direction, and the backward direction indicates the receiving direction. The following table describes the meaning of each counter. Counter Name VS.IPPATH.Bwd.Cong.Dur Description Duration of backward congestion on the IP path
Measurement point
The RNC checks the state of an IP path each time a service is being admitted to that path. The measurement of a forward (backward) congestion duration starts when a forward (backward)
congestion is detected on an AAL2 path and stops when the forward (backward) congestion is cleared. In the measurement period, the accumulated duration of forward (backward) congestion on the IP path is taken as the value of this counter.This counter is invalid when the real flow access control switch is turned on.
Formula
None
Unit
s
Related Features
Counter Name VS.IPPATH.Fwd.Cong.Dur Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.IPPATH.Bwd.Cong.Dur WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.19 Measurement of IPPATH IP Layer Performance (IPPATH_IPLAYER)

Overview
Measurement of IPPATH IP Layer Performance indicates the transmission quality of the IPPATH IP layer on the FG2a, GOUa, PEUa, PEUc, UOIa, POUa, FG2d, FG2c, POUc, GOUd and GOUc board.When the IPMUX switch is enabled, the interface board measures the traffic on the IP path before performing IP packet multiplexing. Therefore, the counter values for the IP path are not affected by IP packet multiplexing.
FunctionSubSets
FunctionSubSet IPPATH.IPLAYER FunctionSubSet Name IPPATH IP Layer Measurement
Issue 01 (2013-05-04)
2826
2.19.1 IPPATH IP Layer Measurement(IPPATH.IPLAYER)

Overview
The quality of transmission links directly affects the system performance. IPPATH IP Layer Measurement helps analyze system transmission quality so as to maintain system stability and reliability. The figure1 shows the location of the IP Layer in the procotol. Figure 2-43 The four layers of the TCP/IP protocol suite
Figure 2-44 Physical bearer of the logical port for the IPPATH
Issue 01 (2013-05-04)
2827
The position of IP paths in the configuration structure is in figure2 and figure3: Figure 2-45 Physical bearer of the IPPATH
Counters
Counter ID 67195395 Counter Name VS.IPPATH.IPLA YER.TXPACKET S VS.IPPATH.IPLA YER.TXBYTES Counter Description T7401:Number of Packets Transmitted at the IP Layer of an IP Path T7402:Number of Bytes Transmitted at the IP Layer of an IP Path T7403:Number of Packets Discarded in Transmission at the IP Layer of an IP Path T7404:Number of Bytes Discarded in Transmission at the IP Layer of an IP Path T7405:Number of Packets Received at the IP Layer of an IP Path Original Release Earlier than V900R011
67195396
67195397
VS.IPPATH.IPLA YER.TXDROPPA CKETS VS.IPPATH.IPLA YER.TXDROPBY TES VS.IPPATH.IPLA YER.RXPACKET S
67195398
67195399
Issue 01 (2013-05-04)
2828
Counter ID 67195400
Counter Name VS.IPPATH.IPLA YER.RXBYTES VS.IPPATH.IPLA YER.RXDROPPA CKETS VS.IPPATH.IPLA YER.RXDROPBY TES VS.IPPATH.IPLA YER.PEAK.TXRA TE VS.IPPATH.IPLA YER.MEAN.TX
Counter Description T7406:Number of Bytes Received at the IP Layer of an IP Path T7407:Number of Packets Discarded in Reception at the IP Layer of an IP Path T7408:Number of Bytes Discarded in Reception at the IP Layer of an IP Path T7410:Maximum Transmit Rate of an IP Path at the IP Layer T7411:Mean Transmit Rate of an IP Path at the IP Layer T7413:Maximum Receive Rate of an IP Path at the IP Layer T7414:Mean Receive Rate of an IP Path at the IP Layer T7419:Maximum Transmit Rate of an IP Path at the IP Layer(5-Minute) T7420:Maximum Receive Rate of an IP Path at the IP Layer (5-Minute)
67195401
67195402
67204698
67204699
67204700
VS.IPPATH.IPLA YER.PEAK.RXRA TE VS.IPPATH.IPLA YER.MEAN.RX VS.IPPATH.IPLA YER.FIVE.MINU TES.PEAK.TXRA TE VS.IPPATH.IPLA YER.FIVE.MINU TES.PEAK.RXRA TE
Earlier than V900R011 Earlier than V900R011 V900R014
67204701
73441529
73441530
V900R014
None
2.19.1.1 Counters Related to the Number of Packets Received, Transmitted or Dropped at the IP Layer of an IPPATH
Issue 01 (2013-05-04)
2829
Counters
Counter ID 67195399 Counter Name VS.IPPATH.IPLAYER.RX PACKETS VS.IPPATH.IPLAYER.TX PACKETS VS.IPPATH.IPLAYER.TX DROPPACKETS VS.IPPATH.IPLAYER.RX DROPPACKETS Counter Description T7405:Number of Packets Received at the IP Layer of an IP Path T7401:Number of Packets Transmitted at the IP Layer of an IP Path T7403:Number of Packets Discarded in Transmission at the IP Layer of an IP Path T7407:Number of Packets Discarded in Reception at the IP Layer of an IP Path
67195395
67195397
67195401
Description
VS.IPPATH.IPLAYER.RXPACKETS and VS.IPPATH.IPLAYER.TXPACKETS provide the number of User Plane packets received or transmitted at the IP layer of an IPPATH in the measurement period. VS.IPPATH.IPLAYER.RXDROPPACKETS and VS.IPPATH.IPLAYER.TXDROPPACKETS provide the number of packets discarded over IP paths due to system internal faults. They indicate the traffic volume of the IPPATH at the IP layer.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of packets transmitted, received or discarded on the link once in every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
packet
Issue 01 (2013-05-04)
2830
Related Features
Counter Name VS.IPPATH.IPLAYER.RX PACKETS Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.IPPATH.IPLAYER.TX PACKETS WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.IPPATH.IPLAYER.TX DROPPACKETS WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.IPPATH.IPLAYER.RX DROPPACKETS WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.19.1.2 Counters Related to the Number of Bytes Received, Transmitted or Discarded at the IP Layer of an IPPATH Counters
Counter ID 67195400 Counter Name VS.IPPATH.IPLAYER.RX BYTES VS.IPPATH.IPLAYER.TX BYTES Counter Description T7406:Number of Bytes Received at the IP Layer of an IP Path T7402:Number of Bytes Transmitted at the IP Layer of an IP Path
67195396
Issue 01 (2013-05-04)
2831
Counter ID 67195398
Counter Name VS.IPPATH.IPLAYER.TX DROPBYTES VS.IPPATH.IPLAYER.RX DROPBYTES
Counter Description T7404:Number of Bytes Discarded in Transmission at the IP Layer of an IP Path T7408:Number of Bytes Discarded in Reception at the IP Layer of an IP Path
67195402
Description
VS.IPPATH.IPLAYER.RXBYTES and VS.IPPATH.IPLAYER.TXBYTES provide the number of User Plane bytes received or transmitted at the IP layer of an IPPATH. VS.IPPATH.IPLAYER.RXDROPBYTES and VS.IPPATH.IPLAYER.TXDROPBYTES provide the number of bytes discarded over IP paths due to system internal faults. They indicate the traffic volume of the IPPATH at the IP layer. The number of bytes measured includes the number of bytes in the header of the IP packet and the payload.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes transmitted, received or discarded on the link once in every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.IPPATH.IPLAYER.RX BYTES Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.IPPATH.IPLAYER.TX BYTES WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
Counter Name VS.IPPATH.IPLAYER.TX DROPBYTES
VS.IPPATH.IPLAYER.RX DROPBYTES
WRFD-050402 WRFD-050409 WRFD-050410
2.19.1.3 Counters Related to the Receive Rate or Transmit Rate of an IPPATH at the IP Layer Counters
Counter ID 67204698 Counter Name VS.IPPATH.IPLAYER.PE AK.TXRATE VS.IPPATH.IPLAYER.ME AN.TX VS.IPPATH.IPLAYER.PE AK.RXRATE VS.IPPATH.IPLAYER.ME AN.RX Counter Description T7410:Maximum Transmit Rate of an IP Path at the IP Layer T7411:Mean Transmit Rate of an IP Path at the IP Layer T7413:Maximum Receive Rate of an IP Path at the IP Layer T7414:Mean Receive Rate of an IP Path at the IP Layer
67204699 67204700
67204701
Description
These counters provide the receive rate or transmit rate of an IPPATH at the IP layer in the measurement period. The rates measured here include the spending of the IP header and the payload of the IP packet.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the link once every five seconds. With this, the system obtains the maximum number of bytes received or transmitted in five seconds, and the total number of one measurement period. The maximum speed is calculated with the maximum
bytes in five seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.IPPATH.IPLAYER.PE AK.TXRATE Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.IPPATH.IPLAYER.ME AN.TX WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.IPPATH.IPLAYER.PE AK.RXRATE WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.IPPATH.IPLAYER.ME AN.RX WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.19.1.4 5-Minute Measurement of the Highest Transmit and Receive Rates of an IPPATH at the IP Layer
Issue 01 (2013-05-04)
2834
Counters
Counter ID 73441529 Counter Name VS.IPPATH.IPLAYER.FIV E.MINUTES.PEAK.TXRA TE VS.IPPATH.IPLAYER.FIV E.MINUTES.PEAK.RXRA TE Counter Description T7419:Maximum Transmit Rate of an IP Path at the IP Layer(5-Minute) T7420:Maximum Receive Rate of an IP Path at the IP Layer(5-Minute)
73441530
Description
These counters provide the receive rate or transmit rate of an IPPATH at the IP layer in the 5Minute measurement period. The rates measured here include the spending of the IP header and the payload of the IP packet.
Measurement point
1.Within a specified measurement period, the system measures the number of transmitted and received bytes every 5 seconds and accumulates the number of bytes at the end of every 5-minute sampling period to obtain the total number of bytes transmitted or received within the sampling period. 2.The system calculates the transmit and receive rate within every 5-minute sampling period with the following formula: Transmit and receive rate within a 5-minute sampling period = Total number of bytes transmitted and received within a 5-minute sampling period/300 3.The system compares all of the collected transmit and receive rates to obtain the highest transmit and receive rate within the specified measurement period, which is the value of the corresponding counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.IPPATH.IPLAYER.FIV E.MINUTES.PEAK.TXRA TE Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
Counter Name VS.IPPATH.IPLAYER.FIV E.MINUTES.PEAK.RXRA TE
2.20 Measurement of IPPATH PM Performance (IPPATH_PM)

Overview
IP path Performance Monitor (PM) monitors the quality of the transmission network. To enable IP path PM, both the base station and the base station controller must support this function. Before viewing the result of IP path PM, activate this function by running a corresponding MML command, such as the ACT IPPM command in V900R013.
FunctionSubSets
FunctionSubSet IPPATH.PM FunctionSubSet Name Measurement Related to IPPM
2.20.1 Measurement Related to IPPM(IPPATH.PM)

Overview
The IPPATH Performance Monitor (PM) uses Forward Monitoring (FM) and Backward Reporting (BR) to check for packet loss over channels. For measurement on the BSC side, the BSC periodically sends FM messages to indicate the number of outgoing packets, the number of bytes, and sending time. The Base Station responds with BR messages after receiving the FM message to report the number of received packets, the number of received bytes, the receiving time of PM message, the sending time of BR response. The BSC calculates the packet loss rate, transmission delay and jitter according to the BR response returned from the Base Station. The numbers of packets and bytes listed in the FM and BR frames are the number of data packets and the number of bytes included in the data packets, exclusive of the number of FM and BR frames and the bytes included in the FM and BR frames. The following figure shows the relationship between IPPM detection packets and service packets.
Issue 01 (2013-05-04)
2836
Figure 2-46 Relationship between IPPM detection packets and service packets
Counters
Counter ID 67192968 67204117 67204118 67204119 67204120 67204121 67204122 Counter Name VS.IPPM.MaxRttDelay VS.IPPM.Bits.Mea nsTx VS.IPPM.Pkts.Mea nsTx VS.IPPM.Peak.Bits .RateTx VS.IPPM.Peak.Pkt s.RateTx VS.IPPM.Peer.Bits .MeansRx VS.IPPM.Peer.Pkts .MeansRx VS.IPPM.Peer.Pea k.Bits.RateRx VS.IPPM.Peer.Pea k.Pkts.RateRx Counter Description T7663:Maximum RTT Delay of IPPM T7668:Average TX Bit Rate of IPPM T7669:Average TX Packet Rate of IPPM T7670:Peak TX Bit Rate of IPPM T7671:Peak TX Packet Rate of IPPM T7672:Average RX Bit Rate of IPPM T7673:Average RX Packet Rate of Peer End of IPPM T7674:Peak RX Bit Rate of Peer End of IPPM T7675:Peak RX Packet Rate of Peer End of IPPM Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67204123
67204124
Issue 01 (2013-05-04)
2837
Counter ID 67204127
Counter Name VS.IPPM.Forword. DropMeans VS.IPPM.Forword. Peak.DropRates VS.IPPM.Forward. JitterStandardDeviation VS.IPPM.Back.JitterStandardDeviation VS.IPPM.Rtt.Mean s VS.IPPM.Forward. Precise.Peak.DropRates
Counter Description T7676:Average Forward Packet Loss Rate of IPPM T7677:Peak Forward Packet Loss Rate of IPPM T7678:Forward Jitter Standard Deviation of IPPM T7679:Backward Jitter Standard Deviation of IPPM T7680:Average RTT Delay of IPPM T7681:HighPrecision Peak Forward Packet Loss Rate of IPPM
Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 V900R014
67204128
67204131
67204731
67204132 73441211
None
2.20.1.1 Bit Rate of IPPM Counters

Counter ID 67204117 67204119 67204121 67204123 Counter Name VS.IPPM.Bits.MeansTx VS.IPPM.Peak.Bits.RateTx VS.IPPM.Peer.Bits.MeansR x VS.IPPM.Peer.Peak.Bits.Ra teRx Counter Description T7668:Average TX Bit Rate of IPPM T7670:Peak TX Bit Rate of IPPM T7672:Average RX Bit Rate of IPPM T7674:Peak RX Bit Rate of Peer End of IPPM
Issue 01 (2013-05-04)
2838
Description
These counters provide the bit rate of the data packets (including IP header and payload, but excluding FM and BR frames) on the IP path that is enabled with the Performance Monitor (PM) function in a specified measurement period. These counters are measured at the transport layer.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the link once every five seconds. With this, the system obtains the maximum number of bytes received or transmitted in five seconds, and the total number of packets in one measurement period. The maximum speed is calculated with the maximum bytes in five seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.IPPM.Bits.MeansTx VS.IPPM.Peak.Bits.RateTx VS.IPPM.Peer.Bits.MeansR x VS.IPPM.Peer.Peak.Bits.Ra teRx Feature ID WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.20.1.2 Packet TX and RX Rates of IPPM Counters

Counter ID 67204118 67204120 Counter Name VS.IPPM.Pkts.MeansTx VS.IPPM.Peak.Pkts.RateTx Counter Description T7669:Average TX Packet Rate of IPPM T7671:Peak TX Packet Rate of IPPM
2839
Issue 01 (2013-05-04)
Counter ID 67204122 67204124
Counter Name VS.IPPM.Peer.Pkts.MeansR x VS.IPPM.Peer.Peak.Pkts.Ra teRx
Counter Description T7673:Average RX Packet Rate of Peer End of IPPM T7675:Peak RX Packet Rate of Peer End of IPPM
Description
These counters provide the packet rate of the data packets (excluding FM and BR frames) on the IP path that is enabled with the Performance Monitor (PM) function in a specified measurement period. These counters are measured at the transport layer.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of packets received and transmitted on the link once every five seconds. With this, the system obtains the maximum number of packets received or transmitted in five seconds, and the total number of packets in one measurement period. The maximum speed is calculated with the maximum packets in five seconds, and the average speed is calculated with the total packets in one measurement period.
Formula
None
Unit
packet/s
Related Features
Counter Name VS.IPPM.Pkts.MeansTx VS.IPPM.Peak.Pkts.RateTx VS.IPPM.Peer.Pkts.MeansR x VS.IPPM.Peer.Peak.Pkts.Ra teRx Feature ID WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.20.1.3 Forward Packet Loss Rate of IPPM

Counters
Counter ID 67204127 67204128 73441211 Counter Name VS.IPPM.Forword.DropMeans VS.IPPM.Forword.Peak.Dro pRates VS.IPPM.Forward.Precise.P eak.DropRates Counter Description T7676:Average Forward Packet Loss Rate of IPPM T7677:Peak Forward Packet Loss Rate of IPPM T7681:High-Precision Peak Forward Packet Loss Rate of IPPM
Description
This counter provides the Forward Packet Loss Rate of the IPPATH in the specified measurement period.The packet loss rate is calculated as follows:(Number of Packets Sent Number of Packets Received by the Peer End)/Number of Packets Sent
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of discarded packtes once every five seconds. With this, the system obtains the total number of discarded packtes in one measurement period. The loss rate is calculated by dividing the discarded packtes with total packtes.
Formula
None
Unit
%
Related Features
Counter Name VS.IPPM.Forword.DropMeans VS.IPPM.Forword.Peak.Dro pRates VS.IPPM.Forward.Precise.P eak.DropRates Feature ID WRFD-050402 WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.20.1.4 Jitter Standard Deviation of IPPM

Counters
Counter ID 67204131 67204731 Counter Name VS.IPPM.Forward.JitterStandardDeviation VS.IPPM.Back.JitterStandardDeviation Counter Description T7678:Forward Jitter Standard Deviation of IPPM T7679:Backward Jitter Standard Deviation of IPPM
Description
This counter provides the jitter standard deviation of IPPM data packets in a measurement period. It indicates the stabilization of the transmission delay of the IP path. A large counter value indicates that the transmission delay varies significantly.
Measurement point
The system obtains the delay jitter of every packet and calculates the standard deviation of the IPPM data packet delay jitter based on the collected statistics within one measurement period.
Formula
None
Unit
ms
Related Features
Counter Name VS.IPPM.Forward.JitterStandardDeviation VS.IPPM.Back.JitterStandardDeviation Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.20.1.5 RTT Delay of IPPM Counters

Counter ID 67204132 Counter Name VS.IPPM.Rtt.Means Counter Description T7680:Average RTT Delay of IPPM
2842
Issue 01 (2013-05-04)
Counter ID 67192968
Counter Name VS.IPPM.MaxRttDelay
Counter Description T7663:Maximum RTT Delay of IPPM
Description
This counter provides the IPPM RTT delay in the specified measurement period to reflect the quality condition of IPPATH. The RTT here consists of the transmission delay caused by an FM frame traveling from the BSC to the Base Station and a BR frame traveling from the Base Station to the BSC.
Measurement point
As shown in the following figure, T1 indicates the time at which the BSC sends the FM packet, T2 indicates the time at which the BTS receives the FM packet from the BSC, T3 indicates the time at which the BTS sends the BR packet, and T4 indicates the time at which the BSC receives the BR packet from the BTS. The RTT delay is calculated as follows: RTT Delay = T4 - T1 - (T3 - T2) Figure 2-47 RTT Delay
Formula
None
Unit
ms
Related Features
Counter Name VS.IPPM.Rtt.Means VS.IPPM.MaxRttDelay Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
Issue 01 (2013-05-04)
2843
2.21 Measurement of IP-Path-Based RTP Performance (IPPATH_RTP)

Overview
The measurement object type IPPATH_RTP has only one function subset, that is, IPPATH.RTP.
FunctionSubSets
FunctionSubSet IPPATH.RTP FunctionSubSet Name Measurement related to RTP flux in IPPATH
2.21.1 Measurement related to RTP flux in IPPATH(IPPATH.RTP)

Overview
The support of IP-based Iu/A interface is an important feature. In order to control the transmission quality on the Iu/A interface, the performance of IP paths is measured on the basis of Real-time Transport Protocol (RTP) and Real-time Transport Control Protocol (RTCP) packets. The transmission quality of the IP paths is related to the measurement items such as Round Trip Time (RTT) of packets, delay jitter of packets, and packet loss rate, In order to increase the ability of surveillance.The item is measured only when the RTCP function is switched on.
Counters
Counter ID 67192702 67204003 67204004 67204005 67192708 67192709 Counter Name VS.IPPATH.RTP.P ktNum.Tx VS.IPPATH.RTP. BytesNum.Tx VS.IPPATH.RTP. BytesLen.Rx VS.IPPATH.RTP. LossPktRatio.Rx VS.IPPATH.RTP.P ktNum.Rx VS.IPPATH.RTP. AverageJitter Counter Description Number of TX RTP Packets at an IP Path Number of Bytes of TX RTP at an IP Path Number of Bytes of RX RTP at an IP Path Rate of lost Packet at Local End of IP Path Number of RX RTP Packets at an IP Path Delay Jitter at Local End of IP Path Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
Issue 01 (2013-05-04)
2844
Counter ID 67192710 67204006 67204007 67204008
Counter Name VS.IPPATH.RTP. AverageRtt VS.IPPATH.RTP. BandWidth.Rx VS.IPPATH.RTP. BandWidth.Tx VS.IPPATH.RTP.J itterOverrun.TimeRatio VS.IPPATH.RTP. RttOverrun.TimeRatio
Counter Description RTT at Local End of IP Path RX RTP bandwidth of IP Path TX RTP bandwidth of IP Path Rate of Duration that Delay Jitter Exceeds Threshold of IP Path Rate of Duration that RTT Exceeds Threshold of IP Path
Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67204009
None
2.21.1.1 Total Number of RTP Packets Transmitted over a Single IP Path Counters
Counter ID 67192702 Counter Name VS.IPPATH.RTP.PktNum.T x Counter Description Number of TX RTP Packets at an IP Path
Description
This measurement item takes statistics of the total number of RTP packets transmitted over a single IP path during a specified measurement period. This item is used for checking the status of packet transmission over a single IP path.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, this measurement item is incremented by 1 each time the Iu UP/AoIP transmits an uplink data packet or an in-band signaling packet during a specified measurement period.
Formula
None
Unit
packet
Related Features
Counter Name VS.IPPATH.RTP.PktNum.T x Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.21.1.2 Total Amount of RTP Data in KB Transmitted over a Single IP Path Counters
Counter ID 67204003 Counter Name VS.IPPATH.RTP.BytesNu m.Tx Counter Description Number of Bytes of TX RTP at an IP Path
Description
This measurement item takes statistics of the total amount of RTP data in kilobytes transmitted over a single IP path during a specified measurement period.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, this measurement item is incremented by the size of the RTP packet payload in kilobytes each time the Iu UP/ AoIP transmits an uplink user data packet or an in-band signaling packet during a specified measurement period.
Formula
None
Unit
kB
Related Features
Counter Name VS.IPPATH.RTP.BytesNu m.Tx Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
Issue 01 (2013-05-04)
2846
2.21.1.3 Total Amount of RTP Data in KB Received over a Single IP Path Counters
Counter ID 67204004 Counter Name VS.IPPATH.RTP.BytesLen. Rx Counter Description Number of Bytes of RX RTP at an IP Path
Description
This measurement item takes statistics of the total amount of RTP data in kilobytes received over a single IP path during a specified measurement period.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, this measurement item is incremented by the size of the RTP packet payload in kilobytes each time the Iu UP/ AoIP receives a downlink data packet during a specified measurement period. This measurement item is reset after each reporting.
Formula
None
Unit
kB
Related Features
Counter Name VS.IPPATH.RTP.BytesLen. Rx Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.21.1.4 Loss Rate of RTP Packets Received over a Single IP Path Counters
Counter ID 67204005 Counter Name VS.IPPATH.RTP.LossPktR atio.Rx Counter Description Rate of lost Packet at Local End of IP Path
Issue 01 (2013-05-04)
2847
Description
This measurement item takes statistics of the loss rate of RTP packets received over a single IP path during a specified measurement period.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, each time the Iu UP/ AoIP transmits an RTCP packet during a specified measurement period, the number of packets lost during the period increases by the number indicated in the RTCP packet. (Each RTCP packet needs to contain the number of packets lost during the period.) Then, based on the number of RTP packets received over the IP path, the RTP packet loss rate on the IP path can be calculated according to the following formula:Packet loss rate = number of packets lost/(number of packets lost + number of packets received)
Formula
None
Unit
%
Related Features
Counter Name VS.IPPATH.RTP.LossPktR atio.Rx Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.21.1.5 Total Number of RTP Packets Received over a Single IP Path Counters
Counter ID 67192708 Counter Name VS.IPPATH.RTP.PktNum. Rx Counter Description Number of RX RTP Packets at an IP Path
Description
This measurement item takes statistics of the total number of RTP packets received over a single IP path during a specified measurement period. This item is used to check the status of packet reception over a single IP path.
Issue 01 (2013-05-04)
2848
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, this measurement item is incremented by 1 each time the Iu UP/AoIP receives a downlink RTP data packet during a specified measurement period.
Formula
None
Unit
packet
Related Features
Counter Name VS.IPPATH.RTP.PktNum. Rx Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.21.1.6 Mean Delay Jitter of RTP Packets Received over a Single IP Path Counters
Counter ID 67192709 Counter Name VS.IPPATH.RTP.AverageJitter Counter Description Delay Jitter at Local End of IP Path
Description
This measurement item takes statistics of the average delay jitter of RTP packets received over a single IP path.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, each time an RTP packet is received in the downlink, the delay jitter of the packet is calculated on the basis of the local time when the packet is received and the value of Ts in the packet. Then, the average delay jitter can be calculated according to the following formula: Average delay jitter = Sum of delay jitter /Total times
Formula
None
Unit
ms
Related Features
Counter Name VS.IPPATH.RTP.AverageJitter Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.21.1.7 Mean RTT of Packets Received over a Single IP Path Counters

Counter ID 67192710 Counter Name VS.IPPATH.RTP.AverageRtt Counter Description RTT at Local End of IP Path
Description
This measurement item takes statistics of the Round Trip Time (RTT) of packets received over a single IP path.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, after an RTCP packet is transmitted from the local end, RTT of the received RTCP packet can be calculated each time an RTCP packet with Reception Report Block is received in the downlink. The RTT is calculated on the basis of the time of transmitting that RTCP packet, the time of receiving this RTCP packet, and the DLSR field of the received RTCP packet. The formula is as follows: RTT = the time of receiving this RTCP packet - the time of transmitting that RTCP packet - DLSR in the received RTCP packet Then, the average RTT is calculated as follows: Average RTT =Sum of RTT/ Total times
Formula
None
Unit
ms
Issue 01 (2013-05-04)
2850
Related Features
Counter Name VS.IPPATH.RTP.AverageRtt Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.21.1.8 Local Received Bandwidth of a Single IP Path Counters

Counter ID 67204006 Counter Name VS.IPPATH.RTP.BandWidt h.Rx Counter Description RX RTP bandwidth of IP Path
Description
This measurement item takes statistics of the local received bandwidth of a single IP path during a specified measurement period.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, the local received bandwidth of a single IP path during a specified measurement period can be calculated according to the following formula:Local received bandwidth = total amount of RTP data in KB received over the IP path/length of the measurement period
Formula
None
Unit
kB/s
Related Features
Counter Name VS.IPPATH.RTP.BandWidt h.Rx Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.21.1.9 Local Transmitted Bandwidth of a Single IP Path

Counters
Counter ID 67204007 Counter Name VS.IPPATH.RTP.BandWidt h.Tx Counter Description TX RTP bandwidth of IP Path
Description
This measurement item takes statistics of the local transmitted bandwidth of a single IP path during a specified measurement period.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, the local transmitted bandwidth of a single IP path during a specified measurement period can be calculated according to the following formula:Local transmitted bandwidth = total amount of RTP data in KB transmitted over the IP path/length of the measurement period
Formula
None
Unit
kB/s
Related Features
Counter Name VS.IPPATH.RTP.BandWidt h.Tx Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.21.1.10 Ratio of Duration of RTP Delay Jitter Exceeding Threshold to Total Active Duration Counters
Counter ID 67204008 Counter Name VS.IPPATH.RTP.JitterOver run.TimeRatio Counter Description Rate of Duration that Delay Jitter Exceeds Threshold of IP Path
Issue 01 (2013-05-04)
2852
Description
This measurement item takes statistics of the ratio of the time during which the RTP delay jitter exceeds the threshold to the total time during which an IP path is active. This measurement is specific to the single IP path during a specified measurement period.
Measurement point
When IP transport is applied to the Iu/A interface and Real-time Transport Control Protocol (RTCP) is supported, during a specified measurement period, the ratio is calculated according to the following formula: Ratio = duration of RTP delay jitter exceeding threshold/total active duration. Total active duration indicates the sum of intervals between two consecutive Real-time Transport Protocol (RTP) packets received at the local end over an IP path. Duration of RTP delay jitter exceeding threshold indicates the length of time during which the delay jitter exceeds the related threshold for RTP packets received at the local end over an IP path. The RTP delay equals the elapsed time for a packet transmitted by the peer end to reach the local end.
Formula
None
Unit
%
Related Features
Counter Name VS.IPPATH.RTP.JitterOver run.TimeRatio Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.21.1.11 Ratio of Duration of RTT Exceeding Threshold to Total Active Duration Counters
Counter ID 67204009 Counter Name VS.IPPATH.RTP.RttOverru n.TimeRatio Counter Description Rate of Duration that RTT Exceeds Threshold of IP Path
Description
This measurement item takes statistics of the ratio of the time during which the Round Trip Time (RTT) exceeds the threshold to the total time during which an IP path is active. This measurement is specific to the single IP path during a specified measurement period.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, during a specified measurement period, the ratio is calculated according to the following formula: Ratio = duration of RTT exceeding threshold/total active duration. Total active duration indicates the sum of intervals between two consecutive Real-time Transport Protocol (RTP) packets received at the local end over an IP path. Duration of RTT exceeding threshold indicates the length of time during which the RTT exceeds the related threshold over an IP path. The RTT indicates the length of time it takes from the transit of one RTCP pakcet from the local end to the receiving of the response from the peer end.
Formula
None
Unit
%
Related Features
Counter Name VS.IPPATH.RTP.RttOverru n.TimeRatio Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.22 Measurement of Transmission Resource Pool Adjacent Node Connection Performance(IPPOOL_ADJNODE)

Overview
Measurement of Transmission Resource Pool Adjacent Node Connection Performance indicates the transmission quality and IP layer transmission performance of each adjacent node that communicates with the IP addresses in a transmission resource pool.
FunctionSubSets
FunctionSubSet IPPOOL.ADJNODE.IPLAYER IPPOOL.ADJNODE FunctionSubSet Name Measurement of IP Layer on User Plane of Transmission Resource Pool Adjacent Node Measurement of IP Transmission Quality of Transmission Resource Pool Adjacent Node
Issue 01 (2013-05-04)
2854
2.22.1 Measurement of IP Layer on User Plane of Transmission Resource Pool Adjacent Node(IPPOOL.ADJNODE.IPLAYER)
Overview
Measurement of IP Layer on User Plane of Transmission Resource Pool Adjacent Node indicates the user-plane traffic of each adjacent node that communicates with the IP addresses in a transmission resource pool. This measurement helps analyze the transmission quality of the system.
Counters
Counter ID 73441279 Counter Name VS.IPPOOL.ANI.I PLAYER.TXPAC KETS Counter Description T7909:Number of Packets Transmitted at the IP Layer on Adjacent Node User Plane T7910:Number of Bytes Transmitted at the IP Layer on Adjacent Node User Plane T7911:Number of Packets Received at the IP Layer on Adjacent Node User Plane T7912:Number of Bytes Received at the IP Layer on Adjacent Node User Plane T7913:Maximum Transmit Rate at the IP Layer on Adjacent Node User Plane per Interface Board T7914:Mean Transmit Rate at the IP Layer on Adjacent Node User Plane Original Release V900R014
73441248
VS.IPPOOL.ANI.I PLAYER.TXBYT ES
V900R014
73441249
VS.IPPOOL.ANI.I PLAYER.RXPAC KETS
V900R014
73441250
VS.IPPOOL.ANI.I PLAYER.RXBYT ES VS.IPPOOL.ANI.I PLAYER.PEAK.T XRATE
V900R014
73441251
V900R014
73441252
VS.IPPOOL.ANI.I PLAYER.MEAN.T X
V900R014
Issue 01 (2013-05-04)
2855
Counter ID 73441253
Counter Name VS.IPPOOL.ANI.I PLAYER.PEAK.R XRATE
Counter Description T7915:Maximum Receive Rate at the IP Layer on Adjacent Node User Plane per Interface Board T7916:Mean Receive Rate at the IP Layer on Adjacent Node User Plane
73441254
VS.IPPOOL.ANI.I PLAYER.MEAN.R X
V900R014
None
2.22.1.1 Counters Related to the Number of Packets Received or Transmitted at the IP Layer on Adjacent Node User Plane Counters
Counter ID 73441279 Counter Name VS.IPPOOL.ANI.IPLAYER .TXPACKETS VS.IPPOOL.ANI.IPLAYER .RXPACKETS Counter Description T7909:Number of Packets Transmitted at the IP Layer on Adjacent Node User Plane T7911:Number of Packets Received at the IP Layer on Adjacent Node User Plane
73441249
Description
These counters provide the number of received and transmitted IP packets on the user plane by each adjacent node that communicates with the IP addresses of a transmission resource pool. These counters indicate the traffic on the IP layer of an adjacent node in the transmission resource pool.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system measures the number of IP packets received and transmitted on the user plane of the IP layer once every five seconds and obtains the total number at the end of every measurement period.
Formula
None
Unit
packet
Related Features
Counter Name VS.IPPOOL.ANI.IPLAYER .TXPACKETS Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC VS.IPPOOL.ANI.IPLAYER .RXPACKETS WRFD-140207 WRFD-140208 Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.22.1.2 Counters Related to the Number of Bytes Received or Transmitted at the IP Layer on Adjacent Node User Plane Counters
Counter ID 73441248 Counter Name VS.IPPOOL.ANI.IPLAYER .TXBYTES VS.IPPOOL.ANI.IPLAYER .RXBYTES Counter Description T7910:Number of Bytes Transmitted at the IP Layer on Adjacent Node User Plane T7912:Number of Bytes Received at the IP Layer on Adjacent Node User Plane
73441250
Description
These counters provide the number of received and transmitted IP bytes on the user plane by each adjacent node that communicates with the IP addresses of a transmission resource pool. The number of bytes measured includes the number of bytes in the header of the IP packet and the payload.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system measures the number of bytes received and transmitted on the user plane of the IP layer once every five seconds and obtains the total number at the end of every measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.IPPOOL.ANI.IPLAYER .TXBYTES Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC VS.IPPOOL.ANI.IPLAYER .RXBYTES WRFD-140207 WRFD-140208 Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.22.1.3 Counters Related to the Receive Rate or Transmit Rate at the IP Layer on Adjacent Node User Plane Counters
Counter ID 73441251 Counter Name VS.IPPOOL.ANI.IPLAYER .PEAK.TXRATE Counter Description T7913:Maximum Transmit Rate at the IP Layer on Adjacent Node User Plane per Interface Board T7914:Mean Transmit Rate at the IP Layer on Adjacent Node User Plane T7915:Maximum Receive Rate at the IP Layer on Adjacent Node User Plane per Interface Board T7916:Mean Receive Rate at the IP Layer on Adjacent Node User Plane
73441252
VS.IPPOOL.ANI.IPLAYER .MEAN.TX VS.IPPOOL.ANI.IPLAYER .PEAK.RXRATE
73441253
73441254
VS.IPPOOL.ANI.IPLAYER .MEAN.RX
Description
These counters provide the receive rate or transmit rate on the user plane by each adjacent node in the measurement period. The rates measured here include the spending of the IP header and the payload of the IP packet. The Maximum Receive and Transmit Rate indicate the receive and transmit rate of Adjacent Node on single Interface Board.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the user plane of the IP layer once every five seconds. With this, the system obtains the maximum number of bytes received or transmitted in five seconds, and the total number of one measurement period. The maximum speed is calculated with the maximum bytes in five seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.IPPOOL.ANI.IPLAYER .PEAK.TXRATE Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC VS.IPPOOL.ANI.IPLAYER .MEAN.TX WRFD-140207 WRFD-140208 Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC VS.IPPOOL.ANI.IPLAYER .PEAK.RXRATE WRFD-140207 WRFD-140208 Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC VS.IPPOOL.ANI.IPLAYER .MEAN.RX WRFD-140207 WRFD-140208 Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.22.2 Measurement of IP Transmission Quality of Transmission Resource Pool Adjacent Node(IPPOOL.ADJNODE)

Overview
Measurement of IP Transmission Quality of Transmission Resource Pool Adjacent Node indicates the transmission quality of each adjacent node that communicates with the IP addresses in a transmission resource pool. This measurement helps analyze the transmission quality of the system.
Counters
Counter ID 73424310 Counter Name VS.IPPOOL.ADJN ODE.Fwd.Cong Counter Description T7917:Number of Forward Congestions of Adjacent Node T7918:Duration of Forward Congestion of Adjacent Node T7919:Number of Backward Congestions of Adjacent Node T7920:Duration of Backward Congestion of Adjacent Node T7812:Average Ping Delay of Adjacent Node T7813:Maximum Ping Delay of Adjacent Node T7814:Average Ping Delay Variation of Adjacent Node T7815:Maximum Ping Delay Variation of Adjacent Node T7816:Average Ping Packet Loss Rate of Adjacent Node T7817:Maximum Ping Packet Loss Rate of Adjacent Node Original Release V900R014
73441255
VS.IPPOOL.ADJN ODE.Fwd.Cong.Du r VS.IPPOOL.ADJN ODE.Bwd.Cong
V900R014
73424313
V900R014
73441256
VS.IPPOOL.ADJN ODE.Bwd.Cong.Du r VS.IPPOOL.ADJN ODE.PING.MeanD ELAY VS.IPPOOL.ADJN ODE.PING.MaxD ELAY VS.IPPOOL.ADJN ODE.PING.MeanJITTER VS.IPPOOL.ADJN ODE.PING.MaxJI TTER VS.IPPOOL.ADJN ODE.PING.MeanLOST VS.IPPOOL.ADJN ODE.PING.MaxL OST
V900R014
73441496
V900R014
73424743
V900R014
73441497
V900R014
73424745
V900R014
73441498
V900R014
73424747
V900R014
None
Issue 01 (2013-05-04)
2860
2.22.2.1 Counters Related to the Number of Congestions of Adjacent Node Counters

Counter ID 73424310 Counter Name VS.IPPOOL.ADJNODE.Fw d.Cong VS.IPPOOL.ADJNODE.Bw d.Cong Counter Description T7917:Number of Forward Congestions of Adjacent Node T7919:Number of Backward Congestions of Adjacent Node
73424313
Description
This counter provides the number of forward bandwidth congestion occurances and backward bandwidth congestion occurances for an adjacent node in IP transmission mode within a specified measurement period. The forward direction indicates the sending direction, and the backward direction indicates the receiving direction. Based on this counter and the VS.IPPOOL.ADJNODE.Cong.Dur counter, the state of adjacent nodes in IP transmission mode is checked. If a large number of such adjacent nodes are congested for a long time, services may be affected.
Measurement point
The RNC checks the state of an adjacent node in IP transmission mode each time a service is being admitted to that node. This counter is incremented by one when the state of the adjacent node changes from non-congestion to congestion, that is, the remaining bandwidth available becomes smaller than the bandwidth congestion threshold.This counter of backward direction is invalid when the real flow access control switch is turned on.
Formula
None
Unit
None
Related Features
Counter Name VS.IPPOOL.ADJNODE.Fw d.Cong VS.IPPOOL.ADJNODE.Bw d.Cong Feature ID WRFD-140208 WRFD-140208 Feature Name Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
Issue 01 (2013-05-04)
2861
2.22.2.2 Counters Related to the Duration of Congestion of Adjacent Node Counters

Counter ID 73441255 Counter Name VS.IPPOOL.ADJNODE.Fw d.Cong.Dur VS.IPPOOL.ADJNODE.Bw d.Cong.Dur Counter Description T7918:Duration of Forward Congestion of Adjacent Node T7920:Duration of Backward Congestion of Adjacent Node
73441256
Description
This counter provides the duration of forward or backward congestion occurances over an adjacent node in IP transmission mode within the measurement period. The forward direction indicates the sending direction, and the backward direction indicates the receiving direction.
Measurement point
The RNC checks the state of an adjacent node in IP transmission mode each time a service is being admitted to the node. The measurement of a forward or backward congestion duration starts when forward or backward congestion is detected on an adjacent node in IP transmission mode and stops when forward or backward congestion is cleared. In the measurement period, the accumulated duration of forward or backward congestion on the node is taken as the value of this counter.This counter of backward direction is invalid when the real flow access control switch is turned on.
Formula
None
Unit
s
Related Features
Counter Name VS.IPPOOL.ADJNODE.Fw d.Cong.Dur VS.IPPOOL.ADJNODE.Bw d.Cong.Dur Feature ID WRFD-140208 WRFD-140208 Feature Name Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
Issue 01 (2013-05-04)
2862
2.22.2.3 Average Ping Delay of Adjacent Node Counters

Counter ID 73441496 Counter Name VS.IPPOOL.ADJNODE.PI NG.MeanDELAY Counter Description T7812:Average Ping Delay of Adjacent Node
Description
This counter provides the average ping delay of an Adjacent Node in a specified measurement period. It takes effect only when the PING function is enabled. The formula is as follow: The n times ping delay = Receive time of packet n - Send time of packet n (unit:ms)
Measurement point
In the specified measurement period, the system automatically samples the Adjacent Node ping delay every 1.5 minutes. At the end of the specified measurement period, the system divides the accumulated Adjacent Node ping delay by the number of samples to obtain the average ping delay.
Formula
None
Unit
ms
Related Features
Counter Name VS.IPPOOL.ADJNODE.PI NG.MeanDELAY Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.22.2.4 Maximum Ping Delay of Adjacent Node
Issue 01 (2013-05-04)
2863
Counters
Counter ID 73424743 Counter Name VS.IPPOOL.ADJNODE.PI NG.MaxDELAY Counter Description T7813:Maximum Ping Delay of Adjacent Node
Description
This counter provides the maximum ping delay of an Adjacent Node in a specified measurement period. It takes effect only when the PING function is enabled.
Measurement point
The system samples the maximum ping delay of an adjacent node every 1.5 minutes. The counter value equals the maximum ping delay of all the ping delay sampled in a specified measurement period.
Formula
None
Unit
ms
Related Features
Counter Name VS.IPPOOL.ADJNODE.PI NG.MaxDELAY Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.22.2.5 Average Ping Delay Variation of Adjacent Node Counters

Counter ID 73441497 Counter Name VS.IPPOOL.ADJNODE.PI NG.MeanJITTER Counter Description T7814:Average Ping Delay Variation of Adjacent Node
Issue 01 (2013-05-04)
2864
Description
This counter provides the average ping delay variation of an Adjacent Node in the measurement period. It takes effect only when the PING function is enabled. The definition of the delay variation is as follow (from RFC1889[Page 27]): If Si is the RTP timestamp from packet i, and Ri is the time of arrival in RTP timestamp units for packet i, then for two packets i and j, D may be expressed as D(i,j)=(Rj-Ri)-(Sj-Si)=(Rj-Sj)-(Ri-Si) The interarrival jitter is calculated continuously as each data packet i is received from source SSRC_n, using this difference D for that packet and the previous packet i-1 in order of arrival (not necessarily in sequence), according to the formula J=J+(|D(i-1,i)|-J)/16 Whenever a reception report is issued, the current value of J is sampled. The jitter calculation is prescribed here to allow profile-independent monitors to make valid interpretations of reports coming from different implementations. This algorithm is the optimal first-order estimator and the gain parameter 1/16 gives a good noise reduction ratio while maintaining a reasonable rate of convergence.
Measurement point
In the specified measurement period, the system automatically samples the Adjacent Node ping delay variation every 5 minutes. At the end of the specified measurement period, the system divides the accumulated Adjacent Node ping delay variation by the number of samples to obtain the average Adjacent Node ping delay variation.
Formula
None
Unit
ms
Related Features
Counter Name VS.IPPOOL.ADJNODE.PI NG.MeanJITTER Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.22.2.6 Maximum Ping Delay Variation of Adjacent Node

Counters
Counter ID 73424745 Counter Name VS.IPPOOL.ADJNODE.PI NG.MaxJITTER Counter Description T7815:Maximum Ping Delay Variation of Adjacent Node
Description
This counter provides the maximum ping delay variation of an Adjacent Node in the specified measurement period. It takes effect only when the PING function is enabled.
Measurement point
The system samples the maximum ping delay variation of an adjacent node every 1.5 minutes. The counter value equals the maximum ping delay variation of all the ping delay variations sampled in a specified measurement period.
Formula
None
Unit
ms
Related Features
Counter Name VS.IPPOOL.ADJNODE.PI NG.MaxJITTER Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.22.2.7 Average Ping Packet Loss Rate of Adjacent Node Counters

Counter ID 73441498 Counter Name VS.IPPOOL.ADJNODE.PI NG.MeanLOST Counter Description T7816:Average Ping Packet Loss Rate of Adjacent Node
Issue 01 (2013-05-04)
2866
Description
This counter provide the ping packet loss rate of an Adjacent Node in the specified measurement period. It takes effect only when the PING function is enabled. Services will be affected if many Adjacent Nodes have a high packet loss rate. This counter only calculates the packets that are lost during successful PING detection sessions.
Measurement point
In the measurement period, the system automatically samples the number of Adjacent Node ping request packets and the number of Adjacent Node ping received packets every 1.5 minutes. At the end of the measurement period, the system divides the accumulated received packets by the accumulated request packets to obtain the average ping packet loss rate.
Formula
None
Unit
%
Related Features
Counter Name VS.IPPOOL.ADJNODE.PI NG.MeanLOST Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.22.2.8 Maximum Ping Packet Loss Rate of Adjacent Node Counters

Counter ID 73424747 Counter Name VS.IPPOOL.ADJNODE.PI NG.MaxLOST Counter Description T7817:Maximum Ping Packet Loss Rate of Adjacent Node
Description
This counter provides the maximum ping packet loss rate of an Adjacent Node in the specified measurement period. It takes effect only when the PING function is enabled. This counter only calculates the packets that are lost during successful PING detection sessions.
Measurement point
In the measurement period, the system automatically samples the number Adjacent Node ping request packets and the number of Adjacent Node ping received packets every 5 minutes. At the end of the measurement period, the system divides the accumulated received packets by the accumulated request packets to obtain the average Adjacent Node ping packet loss rate. The max Adjacent Node ping packet loss rate is set to be this counter.
Formula
None
Unit
%
Related Features
Counter Name VS.IPPOOL.ADJNODE.PI NG.MaxLOST Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.23 Measurement of Transmission Resource Pool IPPM Performance(IPPOOL_PM)

Overview
Measurement of Transmission Resource Pool IPPM Performance monitors the quality of the transmission network. To enable Transmission Resource Pool IPPM, both the base station and the base station controller must support this function. Before viewing the result of Transmission Resource Pool IPPM, activate this function by running a corresponding MML command, such as the ACT IPPOOLPM command.
FunctionSubSets
FunctionSubSet IPPOOL.PM FunctionSubSet Name Transmission Resource Pool IPPM Performance Measurement
Issue 01 (2013-05-04)
2868
2.23.1 Transmission Resource Pool IPPM Performance Measurement(IPPOOL.PM)

Overview
The Transmission Resource Pool IPPM Performance Measurement uses Forward Monitoring (FM) and Backward Reporting (BR) to monitor transmission quality. The BSC support both forward measurement and backward mesurement. The forward direction indicates the sending direction, and the backward direction indicates the receiving direction. For forward measurement, the BSC periodically sends FM messages to indicate the number of outgoing packets, the number of bytes, and sending time. The Base Station responds with BR messages after receiving the FM message to report the number of received packets, the number of received bytes, the receiving time of PM message, the sending time of BR response. For backward measurement, the Base Station periodically sends FM messages and the BSC responds with BR messages. The BSC calculates the packet loss rate, transmission delay and jitter according to the FM and BR messages. The numbers of packets and bytes listed in the FM and BR frames are the number of data packets and the number of bytes included in the data packets, exclusive of the number of FM and BR frames and the bytes included in the FM and BR frames. The following figure shows the relationship between IPPM detection packets and service packets.
Figure 2-48 Relationship between IPPM detection packets and service packets
Counters
Counter ID 73441257 Counter Name VS.IPPOOL.IPPM. ForwardBits.Mean sTx Counter Description T7819:Average Forward Transmit Bit Rate of Transmission Resource Pool IPPM Original Release V900R014
Issue 01 (2013-05-04)
2869
Counter ID 73441258
Counter Name VS.IPPOOL.IPPM. ForwardPkts.Mean sTx
Counter Description T7820:Average Forward Transmit Packet Rate of Transmission Resource Pool IPPM T7821:Maximum Forward Transmit Bit Rate of Transmission Resource Pool IPPM T7822:Maximum Forward Transmit Packet Rate of Transmission Resource Pool IPPM T7823:Average Forward Packet Loss Rate of Transmission Resource Pool IPPM T7824:Maximum Forward Packet Loss Rate of Transmission Resource Pool IPPM T7825:Maximum Forward Jitter of Transmission Resource Pool IPPM T7826:Forward Jitter Standard Deviation of Transmission Resource Pool IPPM T7827:Average RTT Delay of Transmission Resource Pool IPPM T7828:Maximum RTT Delay of Transmission Resource Pool IPPM
73441259
VS.IPPOOL.IPPM. Peak.ForwardBits. RateTx
V900R014
73441260
VS.IPPOOL.IPPM. Peak.ForwardPkts. RateTx
V900R014
73441261
VS.IPPOOL.IPPM. Forward.DropMeans VS.IPPOOL.IPPM. Forward.Peak.Dro pRates VS.IPPOOL.IPPM. Forward.JitterMax
V900R014
73441522
V900R014
73424341
V900R014
73441262
VS.IPPOOL.IPPM. Forward.JitterStandardDeviation
V900R014
73441263
VS.IPPOOL.IPPM. Rtt.Means
V900R014
73424342
VS.IPPOOL.IPPM. MaxRttDelay
V900R014
Issue 01 (2013-05-04)
2870
Counter ID 73441264
Counter Name VS.IPPOOL.IPPM. BackwardBits.Mea nsTx
Counter Description T7829:Average Backward Transmit Bit Rate of Transmission Resource Pool IPPM T7830:Average Backward Transmit Packet Rate of Transmission Resource Pool IPPM T7831:Maximum Backward Transmit Bit Rate of Transmission Resource Pool IPPM T7832:Maximum Backward Transmit Packet Rate of Transmission Resource Pool IPPM T7833:Average Backward Packet Loss Rate of Transmission Resource Pool IPPM T7834:Maximum Backward Packet Loss Rate of Transmission Resource Pool IPPM
73441265
VS.IPPOOL.IPPM. BackwardPkts.Mea nsTx
V900R014
73441266
VS.IPPOOL.IPPM. Peak.BackwardBits .RateTx
V900R014
73441267
VS.IPPOOL.IPPM. Peak.BackwardPkt s.RateTx
V900R014
73441268
VS.IPPOOL.IPPM. Backward.DropMeans
V900R014
73441523
VS.IPPOOL.IPPM. Backward.Peak.Dr opRates
V900R014
None
2.23.1.1 Bit Rate of Transmission Resource Pool IPPM
Issue 01 (2013-05-04)
2871
Counters
Counter ID 73441257 Counter Name VS.IPPOOL.IPPM.Forward Bits.MeansTx Counter Description T7819:Average Forward Transmit Bit Rate of Transmission Resource Pool IPPM T7821:Maximum Forward Transmit Bit Rate of Transmission Resource Pool IPPM T7829:Average Backward Transmit Bit Rate of Transmission Resource Pool IPPM T7831:Maximum Backward Transmit Bit Rate of Transmission Resource Pool IPPM
73441259
VS.IPPOOL.IPPM.Peak.For wardBits.RateTx
73441264
VS.IPPOOL.IPPM.Backwar dBits.MeansTx
73441266
VS.IPPOOL.IPPM.Peak.Ba ckwardBits.RateTx
Description
These counters provide the bit rate of the data packets (including IP header and payload, but excluding FM and BR frames) in a specified measurement period. These counters are measured at the transport layer.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the link once every five seconds. With this, the system obtains the maximum number of bytes received or transmitted in five seconds, and the total number of packets in one measurement period. The maximum speed is calculated with the maximum bytes in five seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
2872
Related Features
Counter Name VS.IPPOOL.IPPM.Forward Bits.MeansTx VS.IPPOOL.IPPM.Peak.For wardBits.RateTx VS.IPPOOL.IPPM.Backwar dBits.MeansTx VS.IPPOOL.IPPM.Peak.Ba ckwardBits.RateTx Feature ID WRFD-140208 WRFD-140208 WRFD-140208 WRFD-140208 Feature Name Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.23.1.2 VS.IPPOOL.IPPM.ForwardPkts.MeansTx Counters

Counter ID 73441258 Counter Name VS.IPPOOL.IPPM.Forward Pkts.MeansTx Counter Description T7820:Average Forward Transmit Packet Rate of Transmission Resource Pool IPPM T7822:Maximum Forward Transmit Packet Rate of Transmission Resource Pool IPPM T7830:Average Backward Transmit Packet Rate of Transmission Resource Pool IPPM T7832:Maximum Backward Transmit Packet Rate of Transmission Resource Pool IPPM
73441260
VS.IPPOOL.IPPM.Peak.For wardPkts.RateTx
73441265
VS.IPPOOL.IPPM.Backwar dPkts.MeansTx
73441267
VS.IPPOOL.IPPM.Peak.Ba ckwardPkts.RateTx
Description
These counters provide the packet rate of the data packets (excluding FM and BR frames) in a specified measurement period. These counters are measured at the transport layer.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of packets received and transmitted on the link once every five seconds. With this,
the system obtains the maximum number of packets received or transmitted in five seconds, and the total number of packets in one measurement period. The maximum speed is calculated with the maximum packets in five seconds, and the average speed is calculated with the total packets in one measurement period.
Formula
None
Unit
packet/s
Related Features
Counter Name VS.IPPOOL.IPPM.Forward Pkts.MeansTx VS.IPPOOL.IPPM.Peak.For wardPkts.RateTx VS.IPPOOL.IPPM.Backwar dPkts.MeansTx VS.IPPOOL.IPPM.Peak.Ba ckwardPkts.RateTx Feature ID WRFD-140208 WRFD-140208 WRFD-140208 WRFD-140208 Feature Name Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.23.1.3 VS.IPPOOL.IPPM.Forward.DropMeans Counters

Counter ID 73441261 Counter Name VS.IPPOOL.IPPM.Forward. DropMeans Counter Description T7823:Average Forward Packet Loss Rate of Transmission Resource Pool IPPM T7824:Maximum Forward Packet Loss Rate of Transmission Resource Pool IPPM T7833:Average Backward Packet Loss Rate of Transmission Resource Pool IPPM
73441522
VS.IPPOOL.IPPM.Forward. Peak.DropRates
73441268
VS.IPPOOL.IPPM.Backwar d.DropMeans
Issue 01 (2013-05-04)
2874
Counter ID 73441523
Counter Name VS.IPPOOL.IPPM.Backwar d.Peak.DropRates
Counter Description T7834:Maximum Backward Packet Loss Rate of Transmission Resource Pool IPPM
Description
This counter provides the Forward Packet Loss Rate in the specified measurement period. The forward packet loss rate is calculated as follows: (Number of packets transmitted by BSC - Number of packets received by Base Station) / Number of packets transmitted by BSC The backward packet loss rate is calculated as follows: (Number of packets transmitted by Base Station - Number of packets received by BSC) / Number of packets transmitted by Base Station
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of discarded packtes once every five seconds. With this, the system obtains the total number of discarded packtes in one measurement period. The loss rate is calculated by dividing the discarded packtes with total packtes.
Formula
None
Unit
%
Related Features
Counter Name VS.IPPOOL.IPPM.Forward. DropMeans VS.IPPOOL.IPPM.Forward. Peak.DropRates VS.IPPOOL.IPPM.Backwar d.DropMeans VS.IPPOOL.IPPM.Backwar d.Peak.DropRates Feature ID WRFD-140208 WRFD-140208 WRFD-140208 WRFD-140208 Feature Name Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
Issue 01 (2013-05-04)
2875
2.23.1.4 Forward Jitter of Transmission Resource Pool IPPM Counters

Counter ID 73424341 Counter Name VS.IPPOOL.IPPM.Forward. JitterMax VS.IPPOOL.IPPM.Forward. JitterStandardDeviation Counter Description T7825:Maximum Forward Jitter of Transmission Resource Pool IPPM T7826:Forward Jitter Standard Deviation of Transmission Resource Pool IPPM
73441262
Description
This counter provides the jitter standard deviation of IPPM data packets in a measurement period. It indicates the stabilization of the transmission delay of the Transmission Resource Pool. A large counter value indicates that the transmission delay varies significantly. The Jitter Standard Deviation is calculated as follows: Jitter Standard Deviation = (((Jitter 1 - Mean Jitter)^2+(Jitter 2 - Mean Jitter)^2+......(Jitter n Mean Jitter)^2)/n)^0.5
Measurement point
The system obtains the delay jitter of every packet and calculates the standard deviation of the IPPM data packet delay jitter based on the collected statistics within one measurement period.
Formula
None
Unit
microsecond
Related Features
Counter Name VS.IPPOOL.IPPM.Forward. JitterMax VS.IPPOOL.IPPM.Forward. JitterStandardDeviation Feature ID WRFD-140208 WRFD-140208 Feature Name Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.23.1.5 RTT Delay of Transmission Resource Pool IPPM

Counters
Counter ID 73441263 Counter Name VS.IPPOOL.IPPM.Rtt.Mea ns VS.IPPOOL.IPPM.MaxRttDelay Counter Description T7827:Average RTT Delay of Transmission Resource Pool IPPM T7828:Maximum RTT Delay of Transmission Resource Pool IPPM
73424342
Description
This counter provides the IPPM RTT delay in the specified measurement period. The RTT here consists of the transmission delay caused by an FM frame traveling from the BSC to the Base Station and a BR frame traveling from the Base Station to the BSC.
Measurement point
As shown in the following figure, T1 indicates the time at which the BSC sends the FM packet, T2 indicates the time at which the BTS receives the FM packet from the BSC, T3 indicates the time at which the BTS sends the BR packet, and T4 indicates the time at which the BSC receives the BR packet from the BTS. The delay measured here is the interval between T4 and T1. The RTT delay is calculated as follows: RTT Delay = T4 - T1 - (T3 - T2) Figure 2-49 RTT Delay
Formula
None
Unit
ms
Issue 01 (2013-05-04)
2877
Related Features
Counter Name VS.IPPOOL.IPPM.Rtt.Mea ns VS.IPPOOL.IPPM.MaxRttDelay Feature ID WRFD-140208 WRFD-140208 Feature Name Iub Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.24 Measurement of Transmission Resource Pool IP Address RTP Performance(IPPOOL_RTP)

Overview
This counter provides the RTP performance measurement in transmission resource pool networking mode. The IPPATH_RTP measurement object provides the RTP performance measurement in other networking modes. The measurement object type IPPOOL_RTP has only one function subset, that is, IPPOOL.RTP.
FunctionSubSets
FunctionSubSet IPPOOL.RTP FunctionSubSet Name Measurement of Transmission Resource Pool IP Address RTP Performance
2.24.1 Measurement of Transmission Resource Pool IP Address RTP Performance(IPPOOL.RTP)

Overview
The support of IP-based IuCS/A interface is an important feature. In order to control the transmission quality on the Iu/A interface, the performance of IP paths is measured on the basis of Real-time Transport Protocol (RTP) and Real-time Transport Control Protocol (RTCP) packets. The transmission quality of the Source and Destination IP Addresses(IP Address Pair) is related to the measurement items such as Round Trip Time (RTT) of packets, delay jitter of packets, and packet loss rate, In order to increase the ability of surveillance.
Issue 01 (2013-05-04)
2878
Counters
Counter ID 73424358 Counter Name VS.IPPOOL.RTP. PktNum.Tx Counter Description P14101:Number of RTP Packets Sent Between an IP Address Pair P14102:Number of Bytes in RTP Packets Sent Between an IP Address Pair P14105:Number of Bytes in RTP Packets Received Between an IP Address Pair P14108:Downlink Loss Rate of RTP Packets Between an IP Address Pair P141010:Number of RTP Packets Received Between an IP Address Pair P141011:Mean Delay Jitter for Receiving RTP Packets Between an IP Address Pair P141012:Mean RTT for RTP Packets Received Between an IP Address Pair P141013:Receive Bandwidth for RTP Packets Received Between an IP Address Pair P141014:Transmit Bandwidth for RTP Packets Sent Between an IP Address Pair Original Release V900R014
73441280
VS.IPPOOL.RTP. BytesNum.Tx
V900R014
73441281
VS.IPPOOL.RTP. BytesLen.Rx
V900R014
73441282
VS.IPPOOL.RTP. LossPktRatio.Rx
V900R014
73424363
VS.IPPOOL.RTP. PktNum.Rx
V900R014
73441283
VS.IPPOOL.RTP. AverageJitter
V900R014
73441284
VS.IPPOOL.RTP. AverageRtt
V900R014
73441285
VS.IPPOOL.RTP. BandWidth.Rx
V900R014
73441286
VS.IPPOOL.RTP. BandWidth.Tx
V900R014
Issue 01 (2013-05-04)
2879
Counter ID 73441287
Counter Name VS.IPPOOL.RTP.J itterOverrun.TimeRatio
Counter Description P141016:Percentage of Duration When Delay Jitter of RTP Packets Exceeds the Threshold to Total Activation Duration P141018:Percentage of Duration When RTT of RTP Packets Exceeds the Threshold to Total Activation Duration
73441288
VS.IPPOOL.RTP. RttOverrun.TimeRatio
V900R014
None
2.24.1.1 Number of RTP Packets Sent Between an IP Address Pair Counters

Counter ID 73424358 Counter Name VS.IPPOOL.RTP.PktNum.T x Counter Description P14101:Number of RTP Packets Sent Between an IP Address Pair
Description
This counter provides the number of uplink RTP packets sent over the Iu/A interface between a specific pair of IP addresses in a measurement period.
Measurement point
This counter is incremented by one when an uplink RTP packet is sent over the Iu/A interface between a specific pair of IP addresses in scenarios where Iu/A over IP is applied and RTCP is supported.
Formula
None
Unit
packet
Related Features
Counter Name VS.IPPOOL.RTP.PktNum.T x Feature ID WRFD-140207 Feature Name Iu/Iur Transmission Resource Pool of RNC
2.24.1.2 Number of Bytes in RTP Packets Sent Between an IP Address Pair Counters
Counter ID 73441280 Counter Name VS.IPPOOL.RTP.BytesNu m.Tx Counter Description P14102:Number of Bytes in RTP Packets Sent Between an IP Address Pair
Description
This counter provides the number of bytes in uplink RTP packets sent over the Iu/A interface between a certain pair of IP addresses in a measurement period.
Measurement point
This counter is incremented by the bytes of the packet payload when an uplink RTP packet is sent over the Iu/A interface between a certain pair of IP addresses in scenarios where Iu/A over IP is applied and RTCP is supported.
Formula
None
Unit
kB
Related Features
Counter Name VS.IPPOOL.RTP.BytesNu m.Tx Feature ID WRFD-140207 Feature Name Iu/Iur Transmission Resource Pool of RNC
2.24.1.3 Number of Bytes in RTP Packets Received Between an IP Address Pair

Counters
Counter ID 73441281 Counter Name VS.IPPOOL.RTP.BytesLen. Rx Counter Description P14105:Number of Bytes in RTP Packets Received Between an IP Address Pair
Description
This counter provides the number of bytes in downlink RTP packets received over the Iu/A interface between a certain pair of IP addresses in a measurement period.
Measurement point
This counter is incremented by the bytes of the packet payload when a downlink RTP packet is received over the Iu/A interface between a certain pair of IP addresses in scenarios where Iu/A over IP is applied and RTCP is supported.
Formula
None
Unit
kB
Related Features
Counter Name VS.IPPOOL.RTP.BytesLen. Rx Feature ID WRFD-140207 Feature Name Iu/Iur Transmission Resource Pool of RNC
2.24.1.4 Downlink Loss Rate of RTP Packets Between an IP Address Pair Counters
Counter ID 73441282 Counter Name VS.IPPOOL.RTP.LossPktR atio.Rx Counter Description P14108:Downlink Loss Rate of RTP Packets Between an IP Address Pair
Issue 01 (2013-05-04)
2882
Description
This counter provides the downlink loss rate of RTP packets over the Iu/A interface between a certain pair of IP addresses in a measurement period.
Measurement point
This counter is calculated by using the following formula in scenarios where Iu/A over IP is applied and RTCP is supported: Downlink loss rate of packets between an IP address pair = Number of downlink packets lost between an IP address pair/(Number of downlink packets lost between an IP address pair + Number of packets received between an IP address pair).
Formula
None
Unit
%
Related Features
Counter Name VS.IPPOOL.RTP.LossPktR atio.Rx Feature ID WRFD-140207 Feature Name Iu/Iur Transmission Resource Pool of RNC
2.24.1.5 Number of RTP Packets Received Between an IP Address Pair Counters

Counter ID 73424363 Counter Name VS.IPPOOL.RTP.PktNum. Rx Counter Description P141010:Number of RTP Packets Received Between an IP Address Pair
Description
This counter provides the number of downlink packets received over the Iu/A interface between a certain pair of IP addresses in a measurement period.
Measurement point
This counter is incremented by one when a downlink packet is received over the Iu/A interface between a certain pair of IP addresses in scenarios where Iu/A over IP is applied and RTCP is supported.
Formula
None
Unit
packet
Related Features
Counter Name VS.IPPOOL.RTP.PktNum. Rx Feature ID WRFD-140207 Feature Name Iu/Iur Transmission Resource Pool of RNC
2.24.1.6 Mean Delay Jitter for Receiving RTP Packets Between an IP Address Pair Counters
Counter ID 73441283 Counter Name VS.IPPOOL.RTP.AverageJitter Counter Description P141011:Mean Delay Jitter for Receiving RTP Packets Between an IP Address Pair
Description
This counter provides the mean delay jitter for receiving RTP packets over the Iu/A interface between a certain pair of IP addresses in a measurement period.
Measurement point
This counter is calculated by using the following formula in scenarios where Iu/A over IP is applied and RTCP is supported: Mean delay jitter for receiving RTP packets = Total delay jitter for receiving RTP packets/Number of RTP traffic statistic reporting times
Formula
None
Unit
ms
Issue 01 (2013-05-04)
2884
Related Features
Counter Name VS.IPPOOL.RTP.AverageJitter Feature ID WRFD-140207 Feature Name Iu/Iur Transmission Resource Pool of RNC
2.24.1.7 Mean RTT for RTP Packets Received Between an IP Address Pair Counters
Counter ID 73441284 Counter Name VS.IPPOOL.RTP.AverageRtt Counter Description P141012:Mean RTT for RTP Packets Received Between an IP Address Pair
Description
This counter provides the mean Round Trip Time (RTT) for packets received over the Iu/A interface between a certain pair of IP addresses in a measurement period.
Measurement point
This counter is calculated by using the following formula in scenarios where Iu/A over IP is applied and RTCP is supported: Mean RTT = Sum of RTT/Number of RTP traffic statistic reporting times
Formula
None
Unit
ms
Related Features
Counter Name VS.IPPOOL.RTP.AverageRtt Feature ID WRFD-140207 Feature Name Iu/Iur Transmission Resource Pool of RNC
2.24.1.8 Receive Bandwidth for RTP Packets Received Between an IP Address Pair
Counters
Counter ID 73441285 Counter Name VS.IPPOOL.RTP.BandWidt h.Rx Counter Description P141013:Receive Bandwidth for RTP Packets Received Between an IP Address Pair
Description
This counter provides the receive bandwidth for RTP packets received over the Iu/A interface between a certain pair of IP addresses in a measurement period.
Measurement point
This counter is calculated by using the following formula in scenarios where Iu/A over IP is applied and RTCP is supported: Transmit bandwidth for RTP packets = Number of bytes of RTP packets sent between an IP address pair/Duration of a measurement period
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.IPPOOL.RTP.BandWidt h.Rx Feature ID WRFD-140207 Feature Name Iu/Iur Transmission Resource Pool of RNC
2.24.1.9 Transmit Bandwidth for RTP Packets Sent Between an IP Address Pair Counters
Counter ID 73441286 Counter Name VS.IPPOOL.RTP.BandWidt h.Tx Counter Description P141014:Transmit Bandwidth for RTP Packets Sent Between an IP Address Pair
Issue 01 (2013-05-04)
2886
Description
This counter provides the transmit bandwidth for RTP packets sent over the Iu/A interface between a certain pair of IP addresses in a measurement period.
Measurement point
This counter is calculated by using the following formula in scenarios where Iu/A over IP is applied and RTCP is supported: Transmit bandwidth for RTP packets = Number of bytes of RTP packets sent between an IP address pair/Duration of a measurement period
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.IPPOOL.RTP.BandWidt h.Tx Feature ID WRFD-140207 Feature Name Iu/Iur Transmission Resource Pool of RNC
2.24.1.10 Percentage of Duration When Delay Jitter of RTP Packets Exceeds the Threshold to Total Activation Duration Counters
Counter ID 73441287 Counter Name VS.IPPOOL.RTP.JitterOver run.TimeRatio Counter Description P141016:Percentage of Duration When Delay Jitter of RTP Packets Exceeds the Threshold to Total Activation Duration
Description
This counter provides the percentage of the duration when the delay jitter of RTP packets received over the Iu/A interface between a certain pair of IP addresses exceeds the threshold to the total activation duration in a measurement period.
Measurement point
This counter is calculated by using the following formula in scenarios where Iu/A over IP is applied and RTCP is supported: Percentage of duration when delay jitter for receiving RTP
packets exceeds threshold = Duration when delay jitter for receiving RTP packets exceeds threshold/Total activation duration where, "Total activation duration" is the sum of activation periods of all services processed between the IP address pair. "Duration when delay jitter for receiving RTP packets exceeds threshold" is the total duration when the delay jitters for receiving RTP packets between the IP address pair exceeds the threshold. The delay for receiving an RTP packet refers to the duration from the time when the RTP packet is sent by the peer end to the time when the RTP packet is received at the local end.
Formula
None
Unit
per mill
Related Features
Counter Name VS.IPPOOL.RTP.JitterOver run.TimeRatio Feature ID WRFD-140207 Feature Name Iu/Iur Transmission Resource Pool of RNC
2.24.1.11 Percentage of Duration When RTT of RTP Packets Exceeds the Threshold to Total Activation Duration Counters
Counter ID 73441288 Counter Name VS.IPPOOL.RTP.RttOverru n.TimeRatio Counter Description P141018:Percentage of Duration When RTT of RTP Packets Exceeds the Threshold to Total Activation Duration
Description
This counter provides the percentage of the duration when the RTT of RTP packets received over the Iu/A interface between a certain pair of IP addresses exceeds the threshold to the total activation duration in a measurement period.
Measurement point
This counter is calculated by using the following formula in scenarios where Iu/A over IP is applied and RTCP is supported: Percentage of duration when RTT of RTP packets exceeds threshold = Duration when RTT of RTP packets exceeds threshold/Total activation duration where, "Total activation duration" is the sum of activation periods of all services processed between the IP address pair. "Duration when RTT of RTP packets exceeds threshold" is the total
duration when the RTT of RTP packets between the IP address pair exceeds the threshold. The RTT of an RTP packet refers to the sum of the duration from the time when the RTP packet is sent by the local end to the time when the RTP packet is received at the peer end and the duration from the time when the RTP packet is sent by the peer end to the time when the RTP packet is received at the local end.
Formula
None
Unit
per mill
Related Features
Counter Name VS.IPPOOL.RTP.RttOverru n.TimeRatio Feature ID WRFD-140207 Feature Name Iu/Iur Transmission Resource Pool of RNC
2.25 Measurement of Transmission Resource Pool Local IP Address Connection Performance(IPPOOL_SIP)

Overview
Measurement of Transmission Resource Pool Local IP Address Connection Performance indicates the transmission quality and IP layer transmission performance of each local IP address in the transmission resource pool.The statistics based on SIP involves control plane and user plane data, but does not involve the maintenance plane data.
FunctionSubSets
FunctionSubSet IPPOOL.SIP.IPLAYER IPPOOL.SIP FunctionSubSet Name Transmission Resource Pool Local IP Address IP Layer Measurement Transmission Resource Pool Local IP Address Transmission Quality Measurement
Issue 01 (2013-05-04)
2889
2.25.1 Transmission Resource Pool Local IP Address IP Layer Measurement(IPPOOL.SIP.IPLAYER)

Overview
Transmission Resource Pool Local IP Address IP Layer Measurement indicates the IP layer traffic of each Local IP address that communicates with the IP addresses in a transmission resource pool. This measurement helps analyze the transmission quality of the system.
Counters
Counter ID 73441269 Counter Name VS.IPPOOL.SIP.IP LAYER.TXPACK ETS VS.IPPOOL.SIP.IP LAYER.TXBYTES Counter Description T7900:Number of Packets Transmitted at the IP Layer on Local IP Address T7901:Number of Bytes Transmitted at the IP Layer on Local IP Address T7902:Number of Packets Received at the IP Layer on Local IP Address T7903:Number of Bytes Received at the IP Layer on Local IP Address T7904:Maximum Transmit Rate at the IP Layer on Local IP Address T7905:Mean Transmit Rate at the IP Layer on Local IP Address T7906:Maximum Receive Rate at the IP Layer on Local IP Address T7907:Mean Receive Rate at the IP Layer on Local IP Address Original Release V900R014
73441270
V900R014
73441271
VS.IPPOOL.SIP.IP LAYER.RXPACK ETS VS.IPPOOL.SIP.IP LAYER.RXBYTE S VS.IPPOOL.SIP.IP LAYER.PEAK.TX RATE VS.IPPOOL.SIP.IP LAYER.MEAN.T X VS.IPPOOL.SIP.IP LAYER.PEAK.RX RATE VS.IPPOOL.SIP.IP LAYER.MEAN.R X
V900R014
73441272
V900R014
73441273
V900R014
73441274
V900R014
73441276
V900R014
73441277
V900R014
Issue 01 (2013-05-04)
2890
None
2.25.1.1 Counters Related to the Number of Packets Received or Transmitted at the IP Layer on Local IP Address Counters
Counter ID 73441269 Counter Name VS.IPPOOL.SIP.IPLAYER. TXPACKETS VS.IPPOOL.SIP.IPLAYER. RXPACKETS Counter Description T7900:Number of Packets Transmitted at the IP Layer on Local IP Address T7902:Number of Packets Received at the IP Layer on Local IP Address
73441271
Description
These counters provide the number of received and transmitted IP packets on the Local IP Address that communicates with the IP addresses of a transmission resource pool. These counters indicate the traffic on the IP layer of a Local IP Address in the transmission resource pool.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system measures the number of IP packets received and transmitted once every five seconds and obtains the total number at the end of every measurement period.
Formula
None
Unit
packet
Related Features
Counter Name VS.IPPOOL.SIP.IPLAYER. TXPACKETS Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
Issue 01 (2013-05-04)
2891
Counter Name VS.IPPOOL.SIP.IPLAYER. RXPACKETS
Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.25.1.2 Counters Related to the Number of Bytes Received or Transmitted at the IP Layer on Local IP Address Counters
Counter ID 73441270 Counter Name VS.IPPOOL.SIP.IPLAYER. TXBYTES VS.IPPOOL.SIP.IPLAYER. RXBYTES Counter Description T7901:Number of Bytes Transmitted at the IP Layer on Local IP Address T7903:Number of Bytes Received at the IP Layer on Local IP Address
73441272
Description
These counters provide the number of received and transmitted IP bytes on the Local IP Address that communicates with the IP addresses of a transmission resource pool. The number of bytes measured includes the number of bytes in the header of the IP packet and the payload.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system measures the number of bytes received and transmitted once every five seconds and obtains the total number at the end of every measurement period.
Formula
None
Unit
byte
Issue 01 (2013-05-04)
2892
Related Features
Counter Name VS.IPPOOL.SIP.IPLAYER. TXBYTES Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC VS.IPPOOL.SIP.IPLAYER. RXBYTES WRFD-140207 WRFD-140208 Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.25.1.3 Counters Related to the Receive Rate or Transmit Rate at the IP Layer on Local IP Address Counters
Counter ID 73441273 Counter Name VS.IPPOOL.SIP.IPLAYER. PEAK.TXRATE VS.IPPOOL.SIP.IPLAYER. MEAN.TX VS.IPPOOL.SIP.IPLAYER. PEAK.RXRATE VS.IPPOOL.SIP.IPLAYER. MEAN.RX Counter Description T7904:Maximum Transmit Rate at the IP Layer on Local IP Address T7905:Mean Transmit Rate at the IP Layer on Local IP Address T7906:Maximum Receive Rate at the IP Layer on Local IP Address T7907:Mean Receive Rate at the IP Layer on Local IP Address
73441274
73441276
73441277
Description
These counters provide the receive rate or transmit rate on the Local IP Address in the measurement period. The rates measured here include the spending of the IP header and the payload of the IP packet.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted once every five seconds. With this, the system obtains the maximum number of bytes received or transmitted in five seconds, and the total number of one measurement period. The maximum speed is calculated with the maximum bytes
in five seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.IPPOOL.SIP.IPLAYER. PEAK.TXRATE Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC VS.IPPOOL.SIP.IPLAYER. MEAN.TX WRFD-140207 WRFD-140208 Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC VS.IPPOOL.SIP.IPLAYER. PEAK.RXRATE WRFD-140207 WRFD-140208 Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC VS.IPPOOL.SIP.IPLAYER. MEAN.RX WRFD-140207 WRFD-140208 Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.25.2 Transmission Resource Pool Local IP Address Transmission Quality Measurement(IPPOOL.SIP)

Overview
Measurement of Transmission Resource Pool Local IP Address Transmission Quality indicates the transmission quality of each Local IP address that communicates with the IP addresses in a transmission resource pool. This measurement helps analyze the transmission quality of the system.
Issue 01 (2013-05-04)
2894
Counters
Counter ID 73441500 Counter Name VS.IPPOOL.SIP.PI NG.MeanLOST Counter Description T7908:Average Ping Packet Loss Rate of Local IP Address Original Release V900R014
None
2.25.2.1 Average Ping Packet Loss Rate of Local IP Address Counters

Counter ID 73441500 Counter Name VS.IPPOOL.SIP.PING.Mea nLOST Counter Description T7908:Average Ping Packet Loss Rate of Local IP Address
Description
This counter provide the ping packet loss rate of a Local IP Address in the specified measurement period. It takes effect only when the PING function is enabled. Services will be affected if many Local IP Addresses have a high packet loss rate. This counter only calculates the packets that are lost during successful PING detection sessions. To query the status of adjacent node PING detection, run the DSP ADJNODEPING command.
Measurement point
In the measurement period, the system automatically samples the number of transmitted local IP address ping request packets and the number of local IP address ping packets that do not have a response every 1.5 minutes, and calculates the ping packet loss rate by dividing the former by the latter. At the end of the measurement period, the system divides the accumulated packet loss rate by sampling times to obtain the average ping packet loss rate.
Formula
None
Unit
%
Related Features
Counter Name VS.IPPOOL.SIP.PING.Mea nLOST Feature ID WRFD-140207 WRFD-140208 Feature Name Iu/Iur Transmission Resource Pool of RNC Iub Transmission Resource Pool of RNC
2.26 Measurement of IURP Link Performance(IURPLNK)

Overview
Measurement of IURP Link Performance
FunctionSubSets
FunctionSubSet IURPLNK FunctionSubSet Name IURP Link Measurement
2.26.1 IURP Link Measurement(IURPLNK)

Overview
Measurement of IURP Link Performance
Counters
Counter ID 73426255 Counter Name VS.IURPLNK.TX. PKGNUM VS.IURPLNK.RX. PKGNUM VS.IURPLNK.TX. MAXPKGNUM VS.IURPLNK.RX. MAXPKGNUM Counter Description Number of Packets Sent on the IURP Link Number of Packets Received on the IURP Link Maximum Number of Packets Sent on the IURP Link Maximum Number of Packets Received on the IURP Link Original Release V900R015
73426256
V900R015
73426257
V900R015
73426258
V900R015
Issue 01 (2013-05-04)
2896
Counter ID 73426259
Counter Name VS.IURPLNK.TX. BYTES VS.IURPLNK.RX. BYTES VS.IURPLNK.TX. MAXBYTES VS.IURPLNK.RX. MAXBYTES VS.IURPLNK.SER VICE.INTERVAL VS.IURPLNK.CO NGESTION VS.IURPLNK.CO NGESTION.INTE RVAL VS.IURPLNK.OV ERLOAD VS.IURPLNK.OV ERLOAD.INTERV AL VS.IURPLNK.RE TX.PKGNUM
Counter Description Number of IP Bytes Sent on the IURP Link Number of IP Bytes Received on the IURP Link Maximum Number of IP Bytes Sent on the IURP Link Maximum Number of IP Bytes Received on the IURP Link Service Duration of the IURP Link Number of Congestions on the IURP Link Congestion Duration of the IURP Link Number of Overloads on the IURP Link Overload Duration of the IURP Link Number of Packets Resent on the IURP Link
73426260
V900R015
73426261
V900R015
73426262
V900R015
73426263 73426264
V900R015 V900R015
73426265
V900R015
73426267
V900R015
73426268
V900R015
73426271
V900R015
None
2.26.1.1 Number of Packets Sent on the IURP Link
Issue 01 (2013-05-04)
2897
Counters
Counter ID 73426255 Counter Name VS.IURPLNK.TX.PKGNU M Counter Description Number of Packets Sent on the IURP Link
Description
This counter measures the number of data blocks an Iur-p link transmits to the lower layer.
Measurement point
In a measurement period, the number of data blocks (including only user data) an Iur-p link transmits to the lower layer is sampled every five seconds.
Formula
None
Unit
packet
Related Features
Counter Name VS.IURPLNK.TX.PKGNU M Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
2.26.1.2 Number of Packets Received on the IURP Link Counters

Counter ID 73426256 Counter Name VS.IURPLNK.RX.PKGNU M Counter Description Number of Packets Received on the IURP Link
Description
This counter measures the number of data blocks an Iur-p link receives from the lower layer.
Measurement point
In a measurement period, the number of data blocks (including only user data) an Iur-p link receives from the lower layer is sampled every five seconds.
Formula
None
Unit
packet
Related Features
Counter Name VS.IURPLNK.RX.PKGNU M Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
2.26.1.3 Maximum Number of Packets Sent on the IURP Link Counters

Counter ID 73426257 Counter Name VS.IURPLNK.TX.MAXPK GNUM Counter Description Maximum Number of Packets Sent on the IURP Link
Description
This counter measures the maximum number of data blocks an Iur-p link transmits to the lower layer.
Measurement point
In a measurement period, the number of data blocks (including only user data) an Iur-p link transmits to the lower layer is sampled every five seconds. At the end of the measurement period, the maximum sampled value is taken as the maximum number of data blocks an Iur-p link transmits or receives.
Formula
None
Unit
packet
Related Features
Counter Name VS.IURPLNK.TX.MAXPK GNUM Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
2.26.1.4 Maximum Number of Packets Received on the IURP Link Counters

Counter ID 73426258 Counter Name VS.IURPLNK.RX.MAXPK GNUM Counter Description Maximum Number of Packets Received on the IURP Link
Description
This counter measures the maximum number of data blocks an Iur-p link receives from the lower layer.
Measurement point
In a measurement period, the number of data blocks (including only user data) an Iur-p link receives from the lower layer is sampled every five seconds. At the end of the measurement period, the maximum sampled value is taken as the maximum number of data blocks an Iur-p link transmits or receives.
Formula
None
Unit
packet
Issue 01 (2013-05-04)
2900
Related Features
Counter Name VS.IURPLNK.RX.MAXPK GNUM Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
2.26.1.5 Number of IP Bytes Sent on the IURP Link Counters

Counter ID 73426259 Counter Name VS.IURPLNK.TX.BYTES Counter Description Number of IP Bytes Sent on the IURP Link
Description
This counter measures the number of payload bytes of user data packets at the application layer an Iur-p link transmits to the lower layer.
Measurement point
In a measurement period, the number of data blocks (including only user data) an Iur-p link transmits to the lower layer is sampled every five seconds.
Formula
None
Unit
byte
Related Features
Counter Name VS.IURPLNK.TX.BYTES Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
2.26.1.6 Number of IP Bytes Received on the IURP Link

Counters
Counter ID 73426260 Counter Name VS.IURPLNK.RX.BYTES Counter Description Number of IP Bytes Received on the IURP Link
Description
This counter measures the number of payload bytes of user data packets at the application layer an Iur-p link receives from the lower layer.
Measurement point
In a measurement period, the number of bytes (including only user data) an Iur-p link receives from the lower layer is sampled every five seconds.
Formula
None
Unit
byte
Related Features
Counter Name VS.IURPLNK.RX.BYTES Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
2.26.1.7 Maximum Number of IP Bytes Sent on the IURP Link Counters

Counter ID 73426261 Counter Name VS.IURPLNK.TX.MAXBYTES Counter Description Maximum Number of IP Bytes Sent on the IURP Link
Description
This counter measures the maximum number of payload bytes of user data packets at the application layer an Iur-p link transmits to or receives from the lower layer.
Measurement point
In a measurement period, the number of bytes (including only user data) an Iur-p link transmits to the lower layer is sampled every five seconds. At the end of the measurement period, the maximum sampled value is taken as the maximum number of payload bytes an Iur-p link transmits or receives.
Formula
None
Unit
byte
Related Features
Counter Name VS.IURPLNK.TX.MAXBYTES Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
2.26.1.8 Maximum Number of IP Bytes Received on the IURP Link Counters

Counter ID 73426262 Counter Name VS.IURPLNK.RX.MAXBYTES Counter Description Maximum Number of IP Bytes Received on the IURP Link
Description
This counter measures the maximum number of payload bytes of user data packets at the application layer an Iur-p link transmits to or receives from the lower layer.
Measurement point
In a measurement period, the number of bytes (including only user data) an Iur-p link receives from the lower layer is sampled every five seconds. At the end of the measurement period, the maximum sampled value is taken as the maximum number of payload bytes an Iur-p link transmits or receives.
Formula
None
Unit
byte
Related Features
Counter Name VS.IURPLNK.RX.MAXBYTES Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
2.26.1.9 Service Duration of the IURP Link Counters

Counter ID 73426263 Counter Name VS.IURPLNK.SERVICE.I NTERVAL Counter Description Service Duration of the IURP Link
Description
This counter measures the service duration of an Iur-p link.
Measurement point
In a measurement period, the status of an Iur-p link is sampled every five seconds. The instantaneous link status is considered as the link status in the sampling period. If the link status is normal, congestion, or overload in a sampling period, the sampling period is calculated into the service duration.
Formula
None
Unit
s
Related Features
Counter Name VS.IURPLNK.SERVICE.I NTERVAL Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
Issue 01 (2013-05-04)
2904
2.26.1.10 Number of Congestions on the IURP Link Counters

Counter ID 73426264 Counter Name VS.IURPLNK.CONGESTION Counter Description Number of Congestions on the IURP Link
Description
This counter measures the number of congestion occurrences on an Iur-p link in a measurement period.
Measurement point
In a measurement period, this counter is increased by one each time the Iur-p link status changes from normal to congestion.
Formula
None
Unit
None
Related Features
Counter Name VS.IURPLNK.CONGESTION Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
2.26.1.11 Congestion Duration of the IURP Link Counters

Counter ID 73426265 Counter Name VS.IURPLNK.CONGESTI ON.INTERVAL Counter Description Congestion Duration of the IURP Link
Issue 01 (2013-05-04)
2905
Description
This counter measures the total duration of congestion status of an Iur-p link in a measurement period.
Measurement point
In a measurement period, the status of an Iur-p link is sampled every five seconds. The instantaneous link status is considered as the link status in the sampling period. If the link status is congestion in a sampling period, the sampling period is calculated into the congestion duration.
Formula
None
Unit
s
Related Features
Counter Name VS.IURPLNK.CONGESTI ON.INTERVAL Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
2.26.1.12 Number of Overloads on the IURP Link Counters

Counter ID 73426267 Counter Name VS.IURPLNK.OVERLOAD Counter Description Number of Overloads on the IURP Link
Description
This counter measures the number of overload occurrences on an Iur-p link in a measurement period.
Measurement point
In a measurement period, this counter is increased by one each time the Iur-p link status changes to overload.
Formula
None
Unit
None
Related Features
Counter Name VS.IURPLNK.OVERLOAD Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
2.26.1.13 Overload Duration of the IURP Link Counters

Counter ID 73426268 Counter Name VS.IURPLNK.OVERLOA D.INTERVAL Counter Description Overload Duration of the IURP Link
Description
This counter measures the total duration of overload occurrences of an Iur-p link in a measurement period.
Measurement point
In a measurement period, the status of an Iur-p link is sampled every five seconds. The instantaneous link status is considered as the link status in the sampling period. If the link status is overload in a sampling period, the sampling period is calculated into the overload duration.
Formula
None
Unit
s
Related Features
Counter Name VS.IURPLNK.OVERLOA D.INTERVAL Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
Issue 01 (2013-05-04)
2907
2.26.1.14 Number of Packets Resent on the IURP Link Counters

Counter ID 73426271 Counter Name VS.IURPLNK.RETX.PKG NUM Counter Description Number of Packets Resent on the IURP Link
Description
This counter measures the number of packets an Iur-p link retransmits in a measurement period.
Measurement point
In a measurement period, this counter is increased by one each time the packet retransmission occurs on an Iur-p link.
Formula
None
Unit
packet
Related Features
Counter Name VS.IURPLNK.RETX.PKG NUM Feature ID WRFD-150211 WRFD-150212 Feature Name RNC in Pool Load Sharing RNC in Pool Node Redundancy
2.27 Measurement of Logic Port Performance (LOGIC_PORT)

Overview
Measurement of Logic Port Performance indicates the transmission quality of the logical port on the FG2a, GOUa, UOIa, FG2d, FG2c, GOUd, GOUc and POUc board.
Issue 01 (2013-05-04)
2908
FunctionSubSets
FunctionSubSet LOGIC.PORT FunctionSubSet Name Logical Port Measurement
2.27.1 Logical Port Measurement(LOGIC.PORT)

Overview
The logic ports measurement helps monitor the transmission quality of the running system and analyze system transmission quality to maintain system stability and reliability. A logical port performs shaping and reverse pressure on the frames at the data link layer, including MAC frames, PPP frames, and MP frames. Thus, the logical port belongs to the data link layer. The figure 2 shows the position of the data link layer in the TCP/IP protocol suite. Figure 2-50 The four layers of the TCP/IP protocol suite
The position of the Logic Port in the configuration structure is in the figure 2.
Issue 01 (2013-05-04)
2909
Figure 2-51 Physical bearer of the Logic Port
Counters
Counter ID 67195360 Counter Name VS.LGCPRT.TXP ACKETS VS.LGCPRT.TXB YTES VS.LGCPRT.TXD ROPPACKETS Counter Description T7501:Number of frames Transmitted over Logical Port T7502:Number of Bytes Transmitted over Logical Port T7503:Number of frames Discarded in Transmission over Logical Port T7504:Number of Bytes Discarded in Transmission over a Logical Port T7506:Maximum Transmit Rate of Logical Port Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67195361
67195362
67195363
VS.LGCPRT.TXD ROPBYTES
67204684
VS.LGCPRT.PEA K.TXRATE
Issue 01 (2013-05-04)
2910
Counter ID 67204685
Counter Name VS.LGCPRT.MEA N.TXRATE VS.LGCPRT.Alloc ed.Ave.Fwd
Counter Description T7507:Average Transmit Rate of Logical Port T7508:Mean Forward Bandwidth Allocated on Logical Port T7561:Mean Backward Bandwidth Allocated on Logical Port T7564:Maximum Forward Bandwidth Allocated on Logical Port T7565:Maximum Backward Bandwidth Allocated on Logical Port T7566:Number of Forward Congestions on Logical Port T7567:Duration of Forward Congestions on Logical Port T7568:Number of Backward Congestions on Logical Port T7569:Duration of Backward Congestions on Logical Port T7540:Maximum Transmit Rate of Logical Port(5Minute)
67204783
67204784
VS.LGCPRT.Alloc ed.Ave.Bwd
67195958
VS.LGCPRT.Alloc ed.Max.Fwd
67195959
VS.LGCPRT.Alloc ed.Max.Bwd
67195960
VS.LGCPRT.Fwd. Cong
67195961
VS.LGCPRT.Fwd. Cong.Dur
67195962
VS.LGCPRT.Bwd. Cong
67195963
VS.LGCPRT.Bwd. Cong.Dur
73441533
VS.LGCPRT.FIVE .MINUTES.PEAK. TXRATE
V900R014
Issue 01 (2013-05-04)
2911
None
2.27.1.1 Number of frames transmitted or discarded over a logical port Counters

Counter ID 67195360 Counter Name VS.LGCPRT.TXPACKETS Counter Description T7501:Number of frames Transmitted over Logical Port T7503:Number of frames Discarded in Transmission over Logical Port
67195362
VS.LGCPRT.TXDROPPACKETS
Description
These counters provide the number of frames transmitted or discarded over a logical port in the specified measurement period. The measured frames can be MAC frames, PPP frames, or MP frames, depending on the bearer type of the logical port.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of frames transmitted or discarded on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
frame
Related Features
Counter Name VS.LGCPRT.TXPACKETS VS.LGCPRT.TXDROPPACKETS Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
Issue 01 (2013-05-04)
2912
2.27.1.2 Number of bytes of data transmitted or discarded over a logical port Counters
Counter ID 67195361 Counter Name VS.LGCPRT.TXBYTES Counter Description T7502:Number of Bytes Transmitted over Logical Port T7504:Number of Bytes Discarded in Transmission over a Logical Port
67195363
VS.LGCPRT.TXDROPBYTES
Description
These counters provide the number of bytes transmitted or discarded over a logical port in the specified measurement period. They reflect the traffic load of the logical port at the data link layer. The measured bytes can be the bytes of MAC frames, PPP frames, or MP frames, depending on the bearer type of the logical port.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes transmitted or discarded on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.LGCPRT.TXBYTES VS.LGCPRT.TXDROPBYTES Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.27.1.3 Measurement of the Transmit Rate of the Logic Port

Counters
Counter ID 67204684 67204685 Counter Name VS.LGCPRT.PEAK.TXRA TE VS.LGCPRT.MEAN.TXRA TE Counter Description T7506:Maximum Transmit Rate of Logical Port T7507:Average Transmit Rate of Logical Port
Description
These measurement counters provide the transmission rate of the logic port in the specified measurement period. The rates measured here include the spending of the header of the Link layer frame(could be MAC, PPP or MP frame depending on the bearing type of the logic port) and the payload.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the logic port once every five seconds. With this, the system obtains the maximum number of bytes received or transmitted in five seconds, and the total number of one measurement period. The maximum speed is calculated with the maximum bytes in five seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.LGCPRT.PEAK.TXRA TE VS.LGCPRT.MEAN.TXRA TE Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.27.1.4 Mean Forward Bandwidth Allocated on Logical Port
Issue 01 (2013-05-04)
2914
Counters
Counter ID 67204783 Counter Name VS.LGCPRT.Alloced.Ave.F wd Counter Description T7508:Mean Forward Bandwidth Allocated on Logical Port
Description
This counter provides the average value of forward bandwidth of ip logic port allocated at the link layer of ip transmission in the measurement period.
Measurement point
In the measurement period, the system automatically takes samples on the bandwidth assigned to logic port every 15 seconds. At the end of the measurement period, the mean forward bandwidth assigned to the logic port equals to the accumulated value of the forward bandwidth at the sampling points divided by the number of sampling times.
Formula
None
Unit
bit/s
Related Features
Counter Name VS.LGCPRT.Alloced.Ave.F wd Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.27.1.5 Mean Backward Bandwidth Allocated on Logical Port Counters

Counter ID 67204784 Counter Name VS.LGCPRT.Alloced.Ave. Bwd Counter Description T7561:Mean Backward Bandwidth Allocated on Logical Port
Issue 01 (2013-05-04)
2915
Description
This counter provides the average value of backward bandwidth of ip logic port allocated at the link layer of ip transmission in the measurement period.
Measurement point
In the measurement period, the system automatically takes samples on the bandwidth assigned to logic port every 15 seconds. At the end of the measurement period, the mean backward bandwidth assigned to the logic port equals to the accumulated value of the backward bandwidth at the sampling points divided by the number of sampling times.This counter of backward direction is invalid when the real flow access control switch is turned on.
Formula
None
Unit
bit/s
Related Features
Counter Name VS.LGCPRT.Alloced.Ave. Bwd Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.27.1.6 Maximum Forward Bandwidth Allocated on Logical Port Counters

Counter ID 67195958 Counter Name VS.LGCPRT.Alloced.Max. Fwd Counter Description T7564:Maximum Forward Bandwidth Allocated on Logical Port
Description
This counter provides the max value of forward bandwidth of ip logic port allocated at the link layer of ip transmission in the measurement period.
Measurement point
In the measurement period, the system automatically takes samples on the bandwidth assigned to logic port every 15 seconds. At the end of the measurement period, the maximum forward bandwidth assigned to the logic port in the measurement period are obtained.
Formula
None
Unit
bit/s
Related Features
Counter Name VS.LGCPRT.Alloced.Max. Fwd Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.27.1.7 Maximum Backward Bandwidth Allocated on Logical Port Counters

Counter ID 67195959 Counter Name VS.LGCPRT.Alloced.Max. Bwd Counter Description T7565:Maximum Backward Bandwidth Allocated on Logical Port
Description
This counter provides the max value of backward bandwidth of ip logic port allocated at the link layer of ip transmission in the measurement period.
Measurement point
In the measurement period, the system automatically takes samples on the bandwidth assigned to logic port every 15 seconds. At the end of the measurement period, the maximum backward bandwidth assigned to the logic port in the measurement period are obtained. This counter of backward direction is invalid when the real flow access control switch is turned on.
Formula
None
Unit
bit/s
Issue 01 (2013-05-04)
2917
Related Features
Counter Name VS.LGCPRT.Alloced.Max. Bwd Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.27.1.8 Measurement of the Number of Congestions on the Logic Port Counters

Counter ID 67195960 67195962 Counter Name VS.LGCPRT.Fwd.Cong VS.LGCPRT.Bwd.Cong Counter Description T7566:Number of Forward Congestions on Logical Port T7568:Number of Backward Congestions on Logical Port
Description
These counters provide the number of forward or backward congestions on the logic port in the specified measurement period.
Measurement point
The counter value is increased by one each time the state of the logic port changes from noncongestion to congestion in the forward or backward direction(The remaining available bandwidth is below the congestion remain threshold). This counter of backward direction is invalid when the real flow access control switch is turned on.
Formula
None
Unit
None
Related Features
Counter Name VS.LGCPRT.Fwd.Cong VS.LGCPRT.Bwd.Cong Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
Issue 01 (2013-05-04)
2918
2.27.1.9 Measurement of Congestion Duration on the Logic Port Counters

Counter ID 67195961 67195963 Counter Name VS.LGCPRT.Fwd.Cong.Du r VS.LGCPRT.Bwd.Cong.Du r Counter Description T7567:Duration of Forward Congestions on Logical Port T7569:Duration of Backward Congestions on Logical Port
Description
These counters provide the duration of congestion on the logic port.
Measurement point
The measurement of a forward(backward) congestion duration starts when a forward(backward) congestion is generated on a logic port and stops when the forward(backward) congestion is cleared. In the measurement period, the accumulated forward(backward) congestion time on the logic port is taken as the value of this counter.This counter of backward direction is invalid when the real flow access control switch is turned on.
Formula
None
Unit
s
Related Features
Counter Name VS.LGCPRT.Fwd.Cong.Du r VS.LGCPRT.Bwd.Cong.Du r Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.27.1.10 5-Minute Measurement of the Highest Transmit Rates of of the Logic Port
Issue 01 (2013-05-04)
2919
Counters
Counter ID 73441533 Counter Name VS.LGCPRT.FIVE.MINUT ES.PEAK.TXRATE Counter Description T7540:Maximum Transmit Rate of Logical Port(5Minute)
Description
These measurement counters provide the transmission rate of the logic port in the 5-Minute measurement period. The rates measured here include the spending of the header of the Link layer frame(could be MAC, PPP or MP frame depending on the bearing type of the logic port) and the payload.
Measurement point
1.Within a specified measurement period, the system measures the number of transmitted bytes every 5 seconds and accumulates the number of bytes at the end of every 5-minute sampling period to obtain the total number of bytes transmitted within the sampling period. 2.The system calculates the transmit rate within every 5-minute sampling period with the following formula: Transmit rate within a 5-minute sampling period = Total number of bytes transmitted within a 5-minute sampling period/300 3.The system compares all of the collected transmit rates to obtain the highest transmit rate within the specified measurement period, which is the value of the corresponding counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.LGCPRT.FIVE.MINUT ES.PEAK.TXRATE Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
Issue 01 (2013-05-04)
2920
2.28 Measurement of Logic Port Queue Performance (LOGIC_PORT_QUEUE)

Overview
Measurement of Logic Port Queue Performance indicates the transmission quality of the logical port queue on the FG2a, GOUa, UOIa, FG2d, FG2c, GOUd, GOUc and POUc board.
FunctionSubSets
FunctionSubSet LOGIC.PORT.QUEUE FunctionSubSet Name Logical Port Queue Measurement
2.28.1 Logical Port Queue Measurement(LOGIC.PORT.QUEUE)

Overview
Logical ports are important resources of the Base Station Controller. Each logical port has eight logical port queues. These queues are identified by different DSCP. A logical port can transmit the services of different types. That is, the services of different types can be transmitted through different queues according to certain rules, and the logical port schedules the data in different queues according to Differentiated Service Code Point (DSCP). You can run the following commands to query the correspondence between service types and DSCP: 1. You can run the LST TRMMAP command to query the correspondence between service types and the Per-Hop Behavior (PHB). 2. You can run the LST PHBMAP command to query the correspondence between PHB and DSCP. Logical port queues belong to the data link layer. The following figure shows the position of the data link layer in the TCP/IP protocol suite. Figure 2-52 The four layers of the TCP/IP protocol suite
Issue 01 (2013-05-04)
2921
Counters
Counter ID 67195365 Counter Name VS.LGCPRT.QUE UE.TXPACKETS Counter Description T7531:Number of Packets Transmitted over Logical Port Queue T7532:Number of Bytes Transmitted over Logical Port Queue T7533:Number of Packets Discarded in Transmission over Logical Port Queue T7534:Number of Bytes Discarded in Transmission over Logical Port Queue T7536:Maximum Transmit Rate of Logical Port Queue Original Release Earlier than V900R011
67195366
VS.LGCPRT.QUE UE.TXBYTES
67195367
VS.LGCPRT.QUE UE.TXDROPPAC KETS VS.LGCPRT.QUE UE.TXDROPBYT ES VS.LGCPRT.QUE UE.PEAK.TXRAT E
67195368
67204686
None
2.28.1.1 Measurement of the Transmitted and Discarded Packets over a logical port queue Counters
Counter ID 67195365 Counter Name VS.LGCPRT.QUEUE.TXP ACKETS VS.LGCPRT.QUEUE.TXD ROPPACKETS Counter Description T7531:Number of Packets Transmitted over Logical Port Queue T7533:Number of Packets Discarded in Transmission over Logical Port Queue
67195367
Description
These counters provide the number of frames transmitted or discarded in transmission over a logical port queue in the specified measurement period. They indicate the transmit traffic volume
of the logical port queue. The frame measured could be MAC, PPP or MP frame depending on the bearing type of the logic port.
Measurement point
Samples are taken every five seconds in the specified measurement period. When the logical port queue sends data to the circuit side, the data frames may be discarded due to the congestion of the logical port queue. The system obtains the number of transmitted frames and discarded frames once every five seconds. The number is accumulated in one measurement period. In this way, the system obtains the total number of transmitted frames and discarded frames in the measurement period.
Formula
None
Unit
frame
Related Features
Counter Name VS.LGCPRT.QUEUE.TXP ACKETS VS.LGCPRT.QUEUE.TXD ROPPACKETS Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.28.1.2 Measurement of the Transmitted and Discarded Bytes over a logical port queue Counters
Counter ID 67195366 Counter Name VS.LGCPRT.QUEUE.TXB YTES VS.LGCPRT.QUEUE.TXD ROPBYTES Counter Description T7532:Number of Bytes Transmitted over Logical Port Queue T7534:Number of Bytes Discarded in Transmission over Logical Port Queue
67195368
Issue 01 (2013-05-04)
2923
Description
These counters provide the number of bytes transmitted or discarded over a logical port queue in the specified measurement period. The measured bytes can be the header and payload of MAC frames, PPP frames, or MP frames, depending on the bearer type of the logical port.
Measurement point
Samples are taken every five seconds in the specified measurement period. The logical port queue sends data to the circuit side. The system obtains the number of transmitted bytes and discarded bytes once every five seconds. The number is accumulated in one measurement period. In this way, the system obtains the total number of transmitted bytes and discarded bytes in the measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.LGCPRT.QUEUE.TXB YTES VS.LGCPRT.QUEUE.TXD ROPBYTES Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.28.1.3 Measurement of the Transmit Rate of logical port queue Counters

Counter ID 67204686 Counter Name VS.LGCPRT.QUEUE.PEA K.TXRATE Counter Description T7536:Maximum Transmit Rate of Logical Port Queue
Description
These counters provide the transmit rate of a logical port queue in the specified measurement period from different perspectives. The rates measured here include the spending of the header of the Link layer frame(could be MAC, PPP or MP frame depending on the bearing type of the logic port) and the payload.
Measurement point
Samples are taken every five seconds in the specified measurement period. The logical port queue sends data to the circuit side. The system obtains the number of transmitted bytes once every five seconds. The number is accumulated in one measurement period. The maximum transmit rate can be obtained by dividing the maximum number of transmitted bytes in five seconds by five. The mean transmit rate can be obtained by dividing the total number of transmitted bytes in one measurement period by the number of sampling times.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.LGCPRT.QUEUE.PEA K.TXRATE Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.29 Measurement of the M3UA Destination Entities Performance(M3UA_DE)

Overview
The measurement object M3UA_DE is used to measure the M3UA destination entities.
FunctionSubSets
FunctionSubSet M3UA.DE FunctionSubSet Name M3UA Destination Entity Measurement
2.29.1 M3UA Destination Entity Measurement(M3UA.DE)

Overview
M3UA destination entity measurement provides the counters related to the number of M3UA destination entity changes to unavailable state and the duration of M3UA destination entity in unavailable state. For details about the M3UA function, see the protocol RFC4666.
Issue 01 (2013-05-04)
2925
Counters
Counter ID 67194647 Counter Name OS.M3UA.DE.Unavail Counter Description T6151:Number of Times that M3UA Destination Entity in Unavailable State T6152:Duration of M3UA Destination Entity in Unavailable State Original Release Earlier than V900R011
67194648
OS.M3UA.DE.Una vail.Dur
None
2.29.1.1 Number of M3UA Destination Entity Changes to Unavailable State Counters

Counter ID 67194647 Counter Name OS.M3UA.DE.Unavail Counter Description T6151:Number of Times that M3UA Destination Entity in Unavailable State
Description
This counter provides the number of times that the status of M3UA destination entity changes from available to unavailable.
Measurement point
In the measurement period, the counter is incremented by one when the last route to a destination entity fails and the destination signaling point becomes unavailable.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2926
Related Features
Counter Name OS.M3UA.DE.Unavail Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.29.1.2 Duration of M3UA Destination Entity in Unavailable State Counters

Counter ID 67194648 Counter Name OS.M3UA.DE.Unavail.Dur Counter Description T6152:Duration of M3UA Destination Entity in Unavailable State
Description
This counter provides the duration during which the M3UA destination entity is unavailable.
Measurement point
In the measurement period, the system takes samples from the status of an M3UA destination entity every five seconds. If the MTP3 destination entity is out of service, this counter is incremented by five.
Formula
None
Unit
s
Related Features
Counter Name OS.M3UA.DE.Unavail.Dur Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
Issue 01 (2013-05-04)
2927
2.30 Measurement of the M3UA Link Performance (M3UA_LNK)

Overview
The measurement object M3UA_LNK is used to measure the Message Transfer Part-broadband User Adaptation (M3UA) links.
FunctionSubSets
FunctionSubSet M3UA.LNK FunctionSubSet Name M3UA Link Measurement
2.30.1 M3UA Link Measurement(M3UA.LNK)

Overview
M3UA link measurement provides the counters related to signaling transmission on the M3UA link between two M3UA entities. For details about the M3UA function, see the protocol RFC4666.
Counters
Counter ID 67194651 67194652 67194653 Counter Name OS.M3UA.Lnk.Fail OS.M3UA.Lnk.Fail .Dur OS.M3UA.Lnk.Co ng.Dur OS.M3UA.Lnk.Tx. Msg OS.M3UA.Lnk.Rx. Msg Counter Description T6161:Number of M3UA Link Failures T6162:Duration of M3UA Link Failure T6163:Duration of M3UA Link Congestion T6164:Number of Message Units Sent on M3UA Link T6165:Number of Messages Units Received on M3UA Link Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67194654
67194655
Issue 01 (2013-05-04)
2928
Counter ID 67194656
Counter Name OS.M3UA.Lnk.AS PM.Tx.Msg OS.M3UA.Lnk.AS PM.Rx.Msg
Counter Description T6166:Number of ASPM Messages Sent on M3UA Link T6167:Number of ASPM Messages Received on M3UA Link
67194657
None
2.30.1.1 Number of M3UA Link Failures Counters

Counter ID 67194651 Counter Name OS.M3UA.Lnk.Fail Counter Description T6161:Number of M3UA Link Failures
Description
This counter provides the number of times that the status of M3UA link changes from available to unavailable.
Measurement point
In the measurement period, the counter is incremented by one when the status of M3UA link changes from available to unavailable.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2929
Related Features
Counter Name OS.M3UA.Lnk.Fail Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.30.1.2 Duration of M3UA Link Failure Counters

Counter ID 67194652 Counter Name OS.M3UA.Lnk.Fail.Dur Counter Description T6162:Duration of M3UA Link Failure
Description
This counter provides the duration during which the M3UA link is unavailable.
Measurement point
In the measurement period, the system takes samples from the status of an M3UA link every five seconds. If the M3UA link is unavailable, this counter is incremented by five.
Formula
None
Unit
s
Related Features
Counter Name OS.M3UA.Lnk.Fail.Dur Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.30.1.3 Duration of M3UA Link Congestion
Issue 01 (2013-05-04)
2930
Counters
Counter ID 67194653 Counter Name OS.M3UA.Lnk.Cong.Dur Counter Description T6163:Duration of M3UA Link Congestion
Description
This counter provides the duration of M3UA link congestion. An M3UA link is congested if the length of the idle section in the message sending queue is lower than the congestion threshold. Packet loss may occur in a congested M3UA link, and services may be affected if multiple M3UA links are congested.
Measurement point
In the measurement period, the system takes samples from the status of an M3UA link every five seconds. If the MTP3 link is congested, this counter is incremented by five.
Formula
None
Unit
s
Related Features
Counter Name OS.M3UA.Lnk.Cong.Dur Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.30.1.4 Counters Related to the Number of Message Units Sent and Received on M3UA Link Counters
Counter ID 67194654 67194655 Counter Name OS.M3UA.Lnk.Tx.Msg OS.M3UA.Lnk.Rx.Msg Counter Description T6164:Number of Message Units Sent on M3UA Link T6165:Number of Messages Units Received on M3UA Link
2931
Issue 01 (2013-05-04)
Counter ID 67194656
Counter Name OS.M3UA.Lnk.ASPM.Tx. Msg OS.M3UA.Lnk.ASPM.Rx. Msg
Counter Description T6166:Number of ASPM Messages Sent on M3UA Link T6167:Number of ASPM Messages Received on M3UA Link
67194657
Description
These counters provide the number of message signaling units (MSUs) sent and received on the M3UA link. The following table describes the meaning of each counter. Counter Name OS.M3UA.Lnk.Tx.Msg Description This counter provides the number of message signaling units (MSUs) sent on the M3UA link. This counter provides the number of message signaling units (MSUs) received on the M3UA link. This counter provides the number of ASPM messages sent on the M3UA link. This counter provides the number of ASPM messages received on the M3UA link.
OS.M3UA.Lnk.Rx.Msg
OS.M3UA.Lnk.ASPM.Tx.Msg OS.M3UA.Lnk.ASPM.Rx.Msg
Measurement point
The measurement is triggered when the M3UA link sends the upper layer signaling message to the peer end or receives the message from the peer end.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2932
Related Features
Counter Name OS.M3UA.Lnk.Tx.Msg OS.M3UA.Lnk.Rx.Msg OS.M3UA.Lnk.ASPM.Tx. Msg OS.M3UA.Lnk.ASPM.Rx. Msg Feature ID WRFD-050409 WRFD-050409 WRFD-050409 WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iu Interface
2.31 Measurement of M3UA Link Set Performance (M3UA_LNK_SET)

Overview
The measurement object M3UA_LNK_SET is used to measure the link set of the MTP3 User Adaptation (M3UA).
FunctionSubSets
FunctionSubSet M3UA.LNKSET FunctionSubSet Name M3UA Link Set Measurement
2.31.1 M3UA Link Set Measurement(M3UA.LNKSET)

Overview
M3UA link set measurement provides the counters related to the configuration of the M3UA link set between the local entity (OSP) and destination entity (DSP). It provides the functions of signaling transport network layer for the Base Station Control. One link set only has up to 16 M3UA links, and one destination entity has only one M3UA signaling link set. For details about the M3UA protocol, see the protocol RFC4666.
Issue 01 (2013-05-04)
2933
Counters
Counter ID 67194649 Counter Name OS.M3UA.Lnkset. Unavail OS.M3UA.Lnkset. Unavail.Dur Counter Description T6156:Number of M3UA Link Set Failures T6157:Duration of M3UA Link Set Failure Original Release Earlier than V900R011 Earlier than V900R011
67194650
None
2.31.1.1 Number of M3UA Link Set Failures Counters

Counter ID 67194649 Counter Name OS.M3UA.Lnkset.Unavail Counter Description T6156:Number of M3UA Link Set Failures
Description
This counter provides the number of times that the status of M3UA link set changes from available to unavailable.
Measurement point
In the measurement period, the counter is incremented by one when the last available M3UA link becomes unavailable.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2934
Related Features
Counter Name OS.M3UA.Lnkset.Unavail Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
2.31.1.2 Duration of M3UA Link Set Failure Counters

Counter ID 67194650 Counter Name OS.M3UA.Lnkset.Unavail. Dur Counter Description T6157:Duration of M3UA Link Set Failure
Description
This counter provides the duration during which the M3UA link set is unavailable.
Measurement point
In the measurement period, the system takes samples on the status of an M3UA link set every five seconds. If the M3UA link set is unavailable, this counter is incremented by five.
Formula
None
Unit
s
Related Features
Counter Name OS.M3UA.Lnkset.Unavail. Dur Feature ID WRFD-050409 Feature Name IP Transmission Introduction on Iu Interface
Issue 01 (2013-05-04)
2935
2.32 Measurement of MP Group Performance(MLPPP)

Overview
Measurement of MP Performance indicates the transmission quality of the MP group on the PEUa, PEUc, POUa or POUc board. Multi-Link Point-to-Point Protocol (MLPPP) enables multiple PPP links to be grouped to increase the bandwidth.
FunctionSubSets
FunctionSubSet MLPPP FunctionSubSet Name MP Group Measurement
2.32.1 MP Group Measurement(MLPPP)

Overview
Transmission links are important resources of the system. The transmission quality of the transmission links directly affects the operation of any function of the system. Therefore, the traffic on MP groups can be measured for the analysis of the transmission quality of the running system so that the stable and reliable operation of the system can be maintained. MP group belongs to the Link layer of the TCP/IP protocol suite, as figure 1 shows. Figure 2-53 The four layers of the TCP/IP protocol suite
In the configuration structure, MLPPP links are between physical ports and logical applications, as shown in the figure 2.
Issue 01 (2013-05-04)
2936
Figure 2-54 Physical bearer of the MP Group
Counters
Counter ID 67194401 Counter Name VS.MLPPP.TXPA CKETS VS.MLPPP.RXPA CKETS VS.MLPPP.BYTESTXTOTAL Counter Description T7300:Number of frames Transmitted on an MP Group T7301:Number of frames Received on an MP Group T7302:Number of Bytes of Frames (Including Frame Header) Transmitted on an MP Group T7303:Number of Bytes of Frames (Including Frame Header) Received on an MP Group Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67194402
67194403
67194404
VS.MLPPP.BYTESRXTOTAL
Issue 01 (2013-05-04)
2937
Counter ID 67194405
Counter Name VS.MLPPP.TXDR OPPEDPKTS
Counter Description T7304:Number of Frames Discarded in Transmission on an MP Group T7305:Number of Error Frames Received on an MP Group T7308:Duration of Faults in an MP Group T7311:Maximum Transmit Rate of an MP Group T7312:Minimum Transmit Rate of an MP Group T7313:Mean Transmit Rate of an MP Group T7316:Maximum Receive Rate of an MP Group T7317:Minimum Receive Rate of an MP Group T7318:Mean Receive Rate of an MP Group T7320:Mean forward bandwidth assigned to an MLPPP group T7323:Mean backward bandwidth assigned to an MLPPP group T7326:Maximum Forward bandwidth assigned to an MLPPP group
67194406
VS.MLPPP.RXERRORPKTS
67194409
VS.MLPPP.FAUL TTIME VS.MLPPP.TXMA XSPEED VS.MLPPP.TXMI NSPEED VS.MLPPP.TXME ANSPEED VS.MLPPP.RXMA XSPEED VS.MLPPP.RXMI NSPEED VS.MLPPP.RXME ANSPEED VS.MLPPP.Alloce d.Ave.Fwd
67194410
67194411
67194412
67194413
67194414
67194415
67204781
67204782
VS.MLPPP.Alloce d.Ave.Bwd
67195948
VS.MLPPP.Alloce d.Max.Fwd
Issue 01 (2013-05-04)
2938
Counter ID 67195949
Counter Name VS.MLPPP.Alloce d.Max.Bwd
Counter Description T7327:Maximum Backward bandwidth assigned to an MLPPP group T7328:Number of forward congestions on an MLPPP group T7329:Duration of forward congestion on an MLPPP group T7330:Number of backward congestions on an MLPPP group T7391:Duration of backward congestion on an MLPPP group
67195950
VS.MLPPP.Fwd.C ong VS.MLPPP.Fwd.C ong.Dur VS.MLPPP.Bwd.C ong
67195951
67195952
67195953
VS.MLPPP.Bwd.C ong.Dur
None
2.32.1.1 Counters Related to the Number of frames Received, Transmitted or Discarded on an MP Group Counters
Counter ID 67194402 67194401 67194405 Counter Name VS.MLPPP.RXPACKETS VS.MLPPP.TXPACKETS VS.MLPPP.TXDROPPEDPKTS VS.MLPPP.RXERRORPKTS Counter Description T7301:Number of frames Received on an MP Group T7300:Number of frames Transmitted on an MP Group T7304:Number of Frames Discarded in Transmission on an MP Group T7305:Number of Error Frames Received on an MP Group
67194406
Issue 01 (2013-05-04)
2939
Description
These counters provide the number of frames Received, Transmitted or Discarded on an MP group in the specified measurement period from different perspectives. They indicate the traffic volume of the MP group. The frames measured here are MP frames.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of frames transmitted, received or discarded on the MP group once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
frame
Related Features
Counter Name VS.MLPPP.RXPACKETS VS.MLPPP.TXPACKETS VS.MLPPP.TXDROPPEDPKTS VS.MLPPP.RXERRORPKTS Feature ID WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.32.1.2 Counters Related to the Number of Bytes of Data Received or Transmitted on an MP Group Counters
Counter ID 67194404 Counter Name VS.MLPPP.BYTESRXTOTAL Counter Description T7303:Number of Bytes of Frames (Including Frame Header) Received on an MP Group
Issue 01 (2013-05-04)
2940
Counter ID 67194403
Counter Name VS.MLPPP.BYTESTXTOTAL
Counter Description T7302:Number of Bytes of Frames (Including Frame Header) Transmitted on an MP Group
Description
These counters provide the number of bytes received or transmitted on an MP group in the specified measurement period. They indicate the traffic volume of the MP group. The number of bytes measured includes the number of bytes in the header of the MP frame and the payload.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes transmitted or received on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.MLPPP.BYTESRXTOTAL VS.MLPPP.BYTESTXTOTAL Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.32.1.3 Duration of Faults in an MP Group Counters

Counter ID 67194409 Counter Name VS.MLPPP.FAULTTIME Counter Description T7308:Duration of Faults in an MP Group
Issue 01 (2013-05-04)
2941
Description
This counter provides the duration of faults occur in an MP group in the specified measurement period. This counter indicates the operation of a single MP group.
Measurement point
Samples are taken every five seconds in the specified measurement period. If the MP group is in faulty state at the current sampling point, five seconds are added to the fault duration of the link.
Formula
None
Unit
s
Related Features
Counter Name VS.MLPPP.FAULTTIME Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.32.1.4 Counters Related to the Receive Rate or Transmit Rate of an MP Group Counters
Counter ID 67194410 67194411 67194412 67194413 67194414 67194415 Counter Name VS.MLPPP.TXMAXSPEED VS.MLPPP.TXMINSPEED VS.MLPPP.TXMEANSPEED VS.MLPPP.RXMAXSPEED VS.MLPPP.RXMINSPEED VS.MLPPP.RXMEANSPEED Counter Description T7311:Maximum Transmit Rate of an MP Group T7312:Minimum Transmit Rate of an MP Group T7313:Mean Transmit Rate of an MP Group T7316:Maximum Receive Rate of an MP Group T7317:Minimum Receive Rate of an MP Group T7318:Mean Receive Rate of an MP Group
Issue 01 (2013-05-04)
2942
Description
These counters provide the receive rate or transmit rate of an MP group in the specified measurement period from different perspectives. The rates measured here include the header and the payload of the MP frame. They indicate the transmit rate of a single MP queue.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the link once every five seconds. With this, the system obtains the maximum and the minimum number of bytes received or transmitted in five seconds, and the total number of bytes in one measurement period. The maximum and minimum speed is calculated with the maximum and minimum bytes in five seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.MLPPP.TXMAXSPEED VS.MLPPP.TXMINSPEED VS.MLPPP.TXMEANSPEED VS.MLPPP.RXMAXSPEED VS.MLPPP.RXMINSPEED VS.MLPPP.RXMEANSPEED Feature ID WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.32.1.5 Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to an MLPPP Group
Issue 01 (2013-05-04)
2943
Counters
Counter ID 67204781 Counter Name VS.MLPPP.Alloced.Ave.Fw d VS.MLPPP.Alloced.Ave.B wd VS.MLPPP.Alloced.Max.F wd VS.MLPPP.Alloced.Max.B wd Counter Description T7320:Mean forward bandwidth assigned to an MLPPP group T7323:Mean backward bandwidth assigned to an MLPPP group T7326:Maximum Forward bandwidth assigned to an MLPPP group T7327:Maximum Backward bandwidth assigned to an MLPPP group
67204782
67195948
67195949
Description
These counters provide the forward bandwidth or backward bandwidth assigned to an MLPPP group from different perspectives.
Measurement point
In the measurement period, the system automatically takes samples on the forward bandwidth and backward bandwidth assigned to an MLPPP group every 15 seconds. At the end of the measurement period, the maximum forward bandwidth and the maximum backward bandwidth assigned to an MLPPP group in the measurement period are obtained. The mean forward bandwidth assigned to an MLPPP group equals to the accumulated value of the forward bandwidth at the sampling points divided by the number of sampling times. The mean backward bandwidth assigned to an MLPPP group equals to the accumulated value of the backward bandwidth at the sampling points divided by the number of sampling times.
Formula
None
Unit
bit/s
Related Features
Counter Name VS.MLPPP.Alloced.Ave.Fw d Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
Issue 01 (2013-05-04)
2944
Counter Name VS.MLPPP.Alloced.Ave.B wd VS.MLPPP.Alloced.Max.F wd VS.MLPPP.Alloced.Max.B wd
Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.32.1.6 Measurement of the Number of Congestions on an MLPPP Group Counters

Counter ID 67195950 Counter Name VS.MLPPP.Fwd.Cong Counter Description T7328:Number of forward congestions on an MLPPP group T7330:Number of backward congestions on an MLPPP group
67195952
VS.MLPPP.Bwd.Cong
Description
These counters provide the number of forward or backward congestions on an MLPPP group in the measurement period.
Measurement point
The counter value is increased by one each time the state of an MLPPP group changes from noncongestion to congestion in the forward or backward direction(The remaining bandwidth available is smaller than the congestion remain threshold).
Formula
None
Unit
None
Issue 01 (2013-05-04)
2945
Related Features
Counter Name VS.MLPPP.Fwd.Cong VS.MLPPP.Bwd.Cong Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.32.1.7 Measurement of the Duration of Congestion on an MLPPP Group Counters

Counter ID 67195951 Counter Name VS.MLPPP.Fwd.Cong.Dur Counter Description T7329:Duration of forward congestion on an MLPPP group T7391:Duration of backward congestion on an MLPPP group
67195953
VS.MLPPP.Bwd.Cong.Dur
Description
These counters provide the duration of congestion on an MLPPP group.
Measurement point
The measurement of a forward(backward) congestion duration starts when a forward(backward) congestion is generated in an MLPPP group and stops when the forward(backward) congestion is cleared. In the measurement period, the accumulated forward(backward) congestion time in the MLPPP group is taken as the value of this counter.
Formula
None
Unit
s
Related Features
Counter Name VS.MLPPP.Fwd.Cong.Dur Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2946
Issue 01 (2013-05-04)
Counter Name VS.MLPPP.Bwd.Cong.Dur
Feature Name IP Transmission Introduction on Iub Interface
2.33 Measurement of MP Queue Performance (MLPPP_QUEUE)

Overview
Measurement of MP Queue Performance indicates the transmission quality of the MP queue on the PEUa, PEUc, POUa or POUc board.
FunctionSubSets
FunctionSubSet MLPPP.QUEUE FunctionSubSet Name MP Queue Measurement
2.33.1 MP Queue Measurement(MLPPP.QUEUE)

Overview
MP groups are important resources of the Base Station Controller. The transmission quality of MP groups affects the availability of system functions. Packets carried on MP groups are mapped onto four or eight queues based on their Differentiated Service Code Point (DSCP). The MHF parameter determines the number of queues. A MP group can transmit the services of different types. That is, the services of different types can be transmitted through different queues according to certain rules, and the MP group schedules the data in different queues according to priorities. You can run the following commands to query the correspondence between service types and queues: 1. You can run the LST TRMMAP command to query the correspondence between service types and the Per-Hop Behavior (PHB). 2. You can run the LST PHBMAP command to query the correspondence between PHB and DSCP. 3. You can run the LST PHBMAP command to query the correspondence between DSCP and queues. MP group queues belong to the data link layer. The figure 1 shows the position of the data link layer in the TCP/IP protocol suite.
Issue 01 (2013-05-04)
2947
In the configuration structure, MLPPP links are between physical ports and logical applications, as shown in the figure 2. Figure 2-56 Physical bearer of the MP Queue
Issue 01 (2013-05-04)
2948
Counters
Counter ID 67195132 Counter Name VS.MLPPP.QUEU E.TXPACKETS VS.MLPPP.QUEU E.TXBYTES VS.MLPPP.QUEU E.TXDROPPACK ETS VS.MLPPP.QUEU E.TXDROPBYTES Counter Description T7331:Number of Packets Transmitted on an MP Queue T7332:Number of Bytes Transmitted on an MP Queue T7333:Number of Packets Discarded in Transmission on an MP Queue T7334:Number of Bytes Discarded in Transmission on an MP Queue T7336:Maximum Transmit Rate of an MP Queue T7337:Mean Transmit Rate of an MP Queue Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67195133
67195134
67195135
67204558
VS.MLPPP.QUEU E.PEAK.TXRATE VS.MLPPP.QUEU E.MEAN.TX
67204559
None
2.33.1.1 Counters Related to the Transmitted and Discarded Packets on an MP Queue Counters
Counter ID 67195132 67195134 Counter Name VS.MLPPP.QUEUE.TXPA CKETS VS.MLPPP.QUEUE.TXDR OPPACKETS Counter Description T7331:Number of Packets Transmitted on an MP Queue T7333:Number of Packets Discarded in Transmission on an MP Queue
Issue 01 (2013-05-04)
2949
Description
These counters provide the number of frames transmitted on an MP queue or the number of transmitted frames discarded on an MP queue in the specified measurement period to indicate the transmit traffic volume of the MP queue. The frames measured here are MP frames.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of frames transmitted and discarded on the link once every five seconds and obtains the total number of one measurement period. The frames measured here are MP frames.
Formula
None
Unit
frame
Related Features
Counter Name VS.MLPPP.QUEUE.TXPA CKETS VS.MLPPP.QUEUE.TXDR OPPACKETS Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.33.1.2 Counters Related to the Number of Bytes Transmitted or Discarded on an MP Queue Counters
Counter ID 67195133 67195135 Counter Name VS.MLPPP.QUEUE.TXBY TES VS.MLPPP.QUEUE.TXDR OPBYTES Counter Description T7332:Number of Bytes Transmitted on an MP Queue T7334:Number of Bytes Discarded in Transmission on an MP Queue
Description
These counters provide the number of bytes transmitted on an MP queue or the number of transmitted bytes discarded on an MP queue in the specified measurement period to indicate the transmit traffic volume of the MP queue. The number of bytes measured includes the number of bytes in the header of the MP frame and the payload.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes transmitted or discarded on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.MLPPP.QUEUE.TXBY TES VS.MLPPP.QUEUE.TXDR OPBYTES Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.33.1.3 Measurement Counters Related to the Transmit Rate of an MP Queue Counters

Counter ID 67204558 67204559 Counter Name VS.MLPPP.QUEUE.PEAK. TXRATE VS.MLPPP.QUEUE.MEAN .TX Counter Description T7336:Maximum Transmit Rate of an MP Queue T7337:Mean Transmit Rate of an MP Queue
Description
These counters provide the transmit rate of an MP queue in the specified measurement period from different perspectives. These counters include the MP frames and payload. They indicate the transmit rate of a single MP queue.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes transmitted on the link once every five seconds. With this, the system obtains the maximum number of bytes transmitted in five seconds, and the total number of one measurement period. The maximum speed is calculated with the maximum bytes in five seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.MLPPP.QUEUE.PEAK. TXRATE VS.MLPPP.QUEUE.MEAN .TX Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.34 Measurement of MTP3 Destination Signaling Point Performance(MTP3_DSP)

Overview
The measurement object of MTP3 DSP Measurement (MTP3_DSP) is used to measure MTP3 destination signaling points (DSPs).
FunctionSubSets
FunctionSubSet MTP3.DSP FunctionSubSet Name MTP3 Destination Signaling Point Measurement
2.34.1 MTP3 Destination Signaling Point Measurement (MTP3.DSP)

Overview
MTP3 destination signaling point measurement provides the counters related to MTP3 destination signaling point. MTP3 destination signaling point is a node in SS7 signaling network. The DSPs for an BTS include Serving GPRS Support Node (SGSN), Media Gateway (MGW), MSC, MSC SERVER (Mobile Switching Center Server), and neighboring Base Station Control. For details about the M3UA function, see the protocol ITU-T Q.704.
Issue 01 (2013-05-04)
2952
Counters
Counter ID 67196163 Counter Name OS.MTP3.DSP.Unavail Counter Description T6101:Number of MTP3 Destination Signaling point Failures T6102:Duration of MTP3 Destination Signaling point Failure Original Release Earlier than V900R011
67196164
OS.MTP3.DSP.Un avail.Dur
None
2.34.1.1 Number of MTP3 Destination Signaling Point Failures Counters

Counter ID 67196163 Counter Name OS.MTP3.DSP.Unavail Counter Description T6101:Number of MTP3 Destination Signaling point Failures
Description
This counter provides the number of times that the status of MTP3 destination signaling point changes from available to unavailable.If an MTP3 destination signaling point (DSP) is unavailable, no signaling can be received by this DSP.
Measurement point
In the measurement period, the counter is incremented by one when the last available MTP3 destination signaling point becomes unavailable because the last available route to the destination signaling point is faulty.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.DSP.Unavail Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.34.1.2 Duration of MTP3 Destination Signaling Point Failure Counters

Counter ID 67196164 Counter Name OS.MTP3.DSP.Unavail.Dur Counter Description T6102:Duration of MTP3 Destination Signaling point Failure
Description
This counter provides the duration in which the MTP3 destination signaling point is unavailable.
Measurement point
In the measurement period, the system takes samples from the status of an MTP3 destination signaling point every five seconds. If the MTP3 destination signaling point is unavailable, this counter is incremented by five.
Formula
None
Unit
s
Related Features
Counter Name OS.MTP3.DSP.Unavail.Dur Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
Issue 01 (2013-05-04)
2954
2.35 Measurement of MTP3 Signaling Link performance (MTP3_LNK)

Overview
The measurement object of MTP3 Link Measurement (MTP3.LNK) is used to measure the MTP3 (Message Transfer Part) links.
FunctionSubSets
FunctionSubSet MTP3.LNK FunctionSubSet Name MTP3 Link Measurement
2.35.1 MTP3 Link Measurement(MTP3.LNK)

Overview
MTP3 link measurement provides the counters related to MTP3(Message Transfer Part) link. The MTP3 serves as the signaling transport network layer for an Base Station Control. It is a signaling transport link between two signaling points in direct connection. There are up to 16 MTP3 links between two signaling points. For details about the M3UA function, see the protocol ITU-T Q.704.
Counters
Counter ID 67196165 Counter Name OS.MTP3.Lnk.Ser vice.Dur OS.MTP3.Lnk.Fail OS.MTP3.Lnk.Fail .Dur OS.MTP3.Lnk.Con g.Dur OS.MTP3.Lnk.LocalInhibit Counter Description T6111:Service Duration of MTP3 Link T6112:Number of MTP3 Link Failures T6113:Out-ofService Duration of MTP3 Link T6114:Duration of MTP3 Link Congestion T6115:Number of Local Inhibitions on MTP3 Link Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67196166 67196167
67196168
67196169
Issue 01 (2013-05-04)
2955
Counter ID 67196170
Counter Name OS.MTP3.Lnk.Loc alInh.Dur OS.MTP3.Lnk.Rm tInhibit OS.MTP3.Lnk.Rm tInhibit.Dur OS.MTP3.Lnk.Cho
Counter Description T6116:Duration of Local Inhibition on MTP3 Link T6117:Number of Remote Inhibitions on MTP3 Link T6118:Duration of Remote Inhibition on MTP3 Link T6119:Number of MTP3 Link Changeovers T6120:Number of Signaling Units Sent on MTP3 Link T6121:Number of Signaling Units Received on MTP3 Link T6122:Number of MTP3 Link Congestions T6123:Number of Bytes of SIO and SIF Sent on MTP3 Link T6124:Number of Bytes of SIO and SIF Received by MTP3 Link T6125:Number of MTP3 Link Remote Processor Failures T6126:Number of Messages Discarded on MTP3 Link Due to Link Congestion T6127:Number of Transfer-Prohibited Signals Received on MTP3 Link
Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67196171
67196172
67196173
67196174
OS.MTP3.Lnk.Tx. Msg OS.MTP3.Lnk.Rx. Msg
67196175
67196176
OS.MTP3.Lnk.Con G OS.MTP3.Lnk.SIO .SIF.Tx OS.MTP3.Lnk.SIO .SIF.Rx
67196177
67196178
67184091
OS.MTP3.Lnk.Rpo s OS.MTP3.Lnk.Disc ard.Msg.Cong
67196179
67196180
OS.MTP3.Lnk.Rx. TFP
Issue 01 (2013-05-04)
2956
Counter ID 67196181
Counter Name OS.MTP3.Lnk.Disc ard.Msg.RouteFail
Counter Description T6128:Number of Messages Discarded on MTP3 Link Due to Route Fail T6129:Number of Transfer-Controlled Signals Received on MTP3 Link T6130:Duration of MTP3 Link Remote Processor Fault
67196182
OS.MTP3.Lnk.Rx. TFC
73403527
OS.MTP3.Lnk.Rpo .Dur
None
2.35.1.1 Service Duration of MTP3 Link Counters

Counter ID 67196165 Counter Name OS.MTP3.Lnk.Service.Dur Counter Description T6111:Service Duration of MTP3 Link
Description
This counter provides the service duration of the MTP3 link.
Measurement point
In the measurement period, the system takes samples from the status of the MTP3 link every five seconds. If the link is "In Service", the item increases by five.
Formula
None
Unit
s
Related Features
Counter Name OS.MTP3.Lnk.Service.Dur Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.2 Number of MTP3 Link Failures Counters

Counter ID 67196166 Counter Name OS.MTP3.Lnk.Fail Counter Description T6112:Number of MTP3 Link Failures
Description
This counter provides the total number of MTP3 link failures for reasons such as MTP3 transition from available state to unavailable state and link test failure.
Measurement point
In a measurement period, this counter is incremented by one when the MTP3 link is in service but its underlying link enters the out of service state, when the MTP3 link is deactivated at the local end, or when the MTP3 link test fails.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.Lnk.Fail Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.3 Duration of Out-of-Service MTP3 Link
Issue 01 (2013-05-04)
2958
Counters
Counter ID 67196167 Counter Name OS.MTP3.Lnk.Fail.Dur Counter Description T6113:Out-of-Service Duration of MTP3 Link
Description
This counter provides the duration of the out-of-service MTP3 link.
Measurement point
In the measurement period, the system takes samples from the status of the MTP3 link every five seconds. If the link is "Out of Service", the item increases by five.
Formula
None
Unit
s
Related Features
Counter Name OS.MTP3.Lnk.Fail.Dur Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.4 Duration of MTP3 Link Congestion Counters

Counter ID 67196168 Counter Name OS.MTP3.Lnk.Cong.Dur Counter Description T6114:Duration of MTP3 Link Congestion
Description
This counter provides the duration of MTP3 link congestion.The RNC reports that an MTP3 link is congested if the message sending queue usage of the MTP3 link exceeds the congestion threshold.
Measurement point
In the measurement period, the system takes samples from the congestion status of the MTP3 link every five seconds. If the link is congested, the item increases by five.Packet loss may occur in a congested MTP3 link, and services may be affected if multiple MTP3 links are congested.
Formula
None
Unit
s
Related Features
Counter Name OS.MTP3.Lnk.Cong.Dur Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.5 Number of Local Inhibitions on MTP3 Link Counters

Counter ID 67196169 Counter Name OS.MTP3.Lnk.LocalInhibit Counter Description T6115:Number of Local Inhibitions on MTP3 Link
Description
This counter provides the number of inhibitions on the MTP3 link at the local end.An inhibited MTP3 link fails to transmit any signaling messages.
Measurement point
In the measurement period, the counter is incremented by one when the local end successfully inhibits the MTP3 link.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.Lnk.LocalInhibit Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.6 Duration of Local Inhibition on MTP3 Link Counters

Counter ID 67196170 Counter Name OS.MTP3.Lnk.LocalInh.Du r Counter Description T6116:Duration of Local Inhibition on MTP3 Link
Description
This counter provides the duration when the MTP3 link stays locally inhibited after being inhibited at the local end.An inhibited MTP3 link fails to transmit any signaling messages.
Measurement point
In the measurement period, the system takes samples from the local management status of the MTP3 link every five seconds. If the link is inhibited, the item increases by five.
Formula
None
Unit
s
Related Features
Counter Name OS.MTP3.Lnk.LocalInh.Du r Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.7 Number of Remote Inhibitions on MTP3 Link
Issue 01 (2013-05-04)
2961
Counters
Counter ID 67196171 Counter Name OS.MTP3.Lnk.RmtInhibit Counter Description T6117:Number of Remote Inhibitions on MTP3 Link
Description
This counter provides the number of inhibitions on the MTP3 link at the remote signaling point.An inhibited MTP3 link fails to transmit any signaling messages.
Measurement point
In the measurement period, the counter is incremented by one when the MTP3 link receives an INH message from the remote signaling point.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.Lnk.RmtInhibit Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.8 Duration of Remote Inhibition on MTP3 Link Counters

Counter ID 67196172 Counter Name OS.MTP3.Lnk.RmtInhibit.D ur Counter Description T6118:Duration of Remote Inhibition on MTP3 Link
Description
This counter provides the duration of the MTP3 link in inhibited state after it is successfully inhibited by the remote signaling point.An inhibited MTP3 link fails to transmit any signaling messages.
Measurement point
In the measurement period, the system takes samples from the remote management status of the MTP3 link every five seconds. If the link is inhibited, the item increases by five.
Formula
None
Unit
s
Related Features
Counter Name OS.MTP3.Lnk.RmtInhibit.D ur Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.9 Number of MTP3 Link Changeovers Counters

Counter ID 67196173 Counter Name OS.MTP3.Lnk.Cho Counter Description T6119:Number of MTP3 Link Changeovers
Description
This counter provides the number of changeovers from one MTP3 link to other MTP3 links for some reason.After the changeover, the original MPT3 link becomes unavailable.
Measurement point
In the measurement period, the counter is incremented by one in any of the following conditions: the state of one MTP3 link changes from "In Service" state to "Out of Service" state; the MTP3 link is operated or maintained by the local end; or the MTP3 link is prohibited by the peer end.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.Lnk.Cho Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.10 Number of Message Signal Units Sent by MTP3 Link Counters

Counter ID 67196174 Counter Name OS.MTP3.Lnk.Tx.Msg Counter Description T6120:Number of Signaling Units Sent on MTP3 Link
Description
This counter provides the number of message signaling units (MSUs) sent by the MTP3 Link.
Measurement point
In the measurement period, the counter is incremented by one when the MTP3 link sends any of the following messages to the peer end: signaling network management message, signaling link test message, or upper-layer signaling message.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.Lnk.Tx.Msg Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.11 Number of Message Signal Units Received by MTP3 Link
Issue 01 (2013-05-04)
2964
Counters
Counter ID 67196175 Counter Name OS.MTP3.Lnk.Rx.Msg Counter Description T6121:Number of Signaling Units Received on MTP3 Link
Description
Number of message signaling units (MSU) received on the MTP3 link.
Measurement point
In the measurement period, the counter is incremented by one when the MTP3 link receives any of the following messages from the peer end: signaling network management message, signaling link test message, or upper-layer signaling message.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.Lnk.Rx.Msg Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.12 Number of MTP3 Link Congestions Counters

Counter ID 67196176 Counter Name OS.MTP3.Lnk.ConG Counter Description T6122:Number of MTP3 Link Congestions
Description
This counter provides the number of MTP3 link congestions.The RNC reports that an MTP3 link is congested if the message sending queue usage of the MTP3 link exceeds the congestion threshold.
Measurement point
In the measurement period, the counter is incremented by one when the MTP3 link changes from the non-congestion state to congestion state.Packet loss may occur in a congested MTP3 link, and services may be affected if multiple MTP3 links are congested.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.Lnk.ConG Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.13 Number of MSU Bytes Sent by MTP3 Link Counters

Counter ID 67196177 Counter Name OS.MTP3.Lnk.SIO.SIF.Tx Counter Description T6123:Number of Bytes of SIO and SIF Sent on MTP3 Link
Description
This counter provides the number of MSU bytes sent by the MTP3 link. The bytes include signaling information field (SIF) and service information octet (SIO). The SIF includes upper layer signaling content and routing label. The SIO includes network indicator and service indicator.
Measurement point
The measurement is triggered when the MTP3 link sends any of the following messages to the peer end: signaling network management message, signaling link test message, or upper-layer signaling message.
Formula
None
Unit
byte
Related Features
Counter Name OS.MTP3.Lnk.SIO.SIF.Tx Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.14 Number of MSU Bytes Received by MTP3 Link Counters

Counter ID 67196178 Counter Name OS.MTP3.Lnk.SIO.SIF.Rx Counter Description T6124:Number of Bytes of SIO and SIF Received by MTP3 Link
Description
This counter provides the number of MSU bytes received by the MTP3 link. The bytes include signaling information field (SIF) and service information octet (SIO). SIF includes upper layer signaling content and routing label. SIO includes network indicator and service indicator.
Measurement point
The measurement is triggered when the MTP3 link receives any of following messages: signaling network management message, signaling link test message, or upper-layer signaling message.
Formula
None
Unit
byte
Related Features
Counter Name OS.MTP3.Lnk.SIO.SIF.Rx Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
Issue 01 (2013-05-04)
2967
2.35.1.15 MTP3 Link Remote Processor Failures Counters

Counter ID 67184091 Counter Name OS.MTP3.Lnk.Rpos Counter Description T6125:Number of MTP3 Link Remote Processor Failures
Description
This measurement provides the number of failures of the MTP3 link remote processor. The failures of the MTP3 link remote processor specifies the messages on the Base Station Control side cannot be sent to the MTP3 and upper layer protocols on the peer end.If the remote processor of an MTP3 link fails, the signaling transmitted on this link fails to be processed at the remote end. The remote processor failure of multiple MTP3 links may affect the services.
Measurement point
In the measurement period, the counter is incremented by one when the MTP3 link remote processor is faulty.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.Lnk.Rpos Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.16 Number of Messages Discarded on MTP3 Link Due to Link Congestion Counters
Counter ID 67196179 Counter Name OS.MTP3.Lnk.Discard.Msg .Cong Counter Description T6126:Number of Messages Discarded on MTP3 Link Due to Link Congestion
Issue 01 (2013-05-04)
2968
Description
This counter provides the number of messages discarded due to MTP3 link congestion.An MTP3 link is congested if the message sending queue usage of the MTP3 link exceeds the congestion threshold. Services may be affected if multiple MTP3 links are congested.
Measurement point
In the measurement period, the counter is incremented by one when a message is discarded on the MTP3 link due to link congestion.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.Lnk.Discard.Msg .Cong Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.17 Number of Transfer-Prohibited Signals Received on MTP3 Link Counters

Counter ID 67196180 Counter Name OS.MTP3.Lnk.Rx.TFP Counter Description T6127:Number of TransferProhibited Signals Received on MTP3 Link
Description
This counter provides the number of transfer-prohibited signals received on the MTP3 link.If a transfer-prohibited (TFP) signal is received on an MTP3 link, the MTP3 link becomes unavailable.
Measurement point
In the measurement period, the counter is incremented by one when a transfer-prohibited signal is received on the MTP3 link.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.Lnk.Rx.TFP Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.18 Number of Messages Discarded on MTP3 Link Due to Route Fail Counters
Counter ID 67196181 Counter Name OS.MTP3.Lnk.Discard.Msg .RouteFail Counter Description T6128:Number of Messages Discarded on MTP3 Link Due to Route Fail
Description
This counter provides the number of messages discarded on the MTP3 link due to route fail.Signaling loss occurs in an MTP3 link that has an incorrect route, and services may be affected if multiple MTP3 links have incorrect routes.
Measurement point
In the measurement period, the counter is incremented by one when a message is discarded on the MTP3 link due to route fail.
Formula
None
Unit
None
Issue 01 (2013-05-04)
2970
Related Features
Counter Name OS.MTP3.Lnk.Discard.Msg .RouteFail Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.19 Number of Transfer-Controlled Signals Received on MTP3 Link Counters

Counter ID 67196182 Counter Name OS.MTP3.Lnk.Rx.TFC Counter Description T6129:Number of TransferControlled Signals Received on MTP3 Link
Description
This counter provides the number of transfer-controlled signals received on the MTP3 link.If a transfer-controlled (TFC) signal is received on an MTP3 link, the related sianling point may be in an abnormal state such as under congestion.
Measurement point
In the measurement period, the counter is incremented by one when a transfer-controlled signal is received on the MTP3 link.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.Lnk.Rx.TFC Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.35.1.20 Duration of MTP3 Link Remote Processor Fault

Counters
Counter ID 73403527 Counter Name OS.MTP3.Lnk.Rpo.Dur Counter Description T6130:Duration of MTP3 Link Remote Processor Fault
Description
This counter provides the duration of MTP3 link remote processor in fault state.If the remote processor of an MTP3 link fails, the signaling transmitted on this link fails to be processed at the remote end. The remote processor failure of multiple MTP3 links may affect the services.
Measurement point
In the measurement period, the system takes samples from the remote processor status of the MTP3 link every five seconds. If remote processor is faulty, the item increases by five.
Formula
None
Unit
s
Related Features
Counter Name OS.MTP3.Lnk.Rpo.Dur Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.36 Measurement of MTP3 Link Set Performance (MTP3_LNK_SET)

Overview
The measurement object of MTP3 Link Set Measurement (MTP3_LNK_SET) is used to measure the MTP3 link set.
FunctionSubSets
FunctionSubSet MTP3.LNKSET FunctionSubSet Name MTP3 Link Set Measurement
Issue 01 (2013-05-04)
2972
2.36.1 MTP3 Link Set Measurement(MTP3.LNKSET)

Overview
MTP3 link set measurement provides the counters related to MTP3(Message Transfer Part) link set. The MTP3 serves as the signaling transport network layer for an Base Station Control. The MTP3 link set refers to a set of MTP3 links between two signaling points in direct connection. There is one MTP3 link set between two signalling points.Each MTP3 link set contains a maximum of 16 MTP3 links. For details about the M3UA function, see the protocol ITU-T Q.704.
Counters
Counter ID 67196183 Counter Name OS.MTP3.Lnkset. Unavail OS.MTP3.Lnkset. Unavail.Dur Counter Description T6106:Number of MTP3 Link Set Failures T6107:Duration of MTP3 Link Set Failure Original Release Earlier than V900R011 Earlier than V900R011
67196184
None
2.36.1.1 Number of MTP3 Link Set Failures Counters

Counter ID 67196183 Counter Name OS.MTP3.Lnkset.Unavail Counter Description T6106:Number of MTP3 Link Set Failures
Description
This counter provides the number of MTP3 link set failures. The MTP3 link set fails when it changes from the available state to the unavailable state.
Measurement point
In the measurement period, the counter is incremented by one when the last available MTP3 link in the MTP3 link set is faulty.
Formula
None
Unit
None
Related Features
Counter Name OS.MTP3.Lnkset.Unavail Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.36.1.2 Duration of MTP3 Link Set in Unavailable State Counters

Counter ID 67196184 Counter Name OS.MTP3.Lnkset.Unavail.D ur Counter Description T6107:Duration of MTP3 Link Set Failure
Description
This counter provides the duration of the MTP3 link set in unavailable state.
Measurement point
In the measurement period, the system takes samples from system checks the status of the MTP3 link set every five seconds. If the link set is unavailable, the item increases by five.
Formula
None
Unit
s
Related Features
Counter Name OS.MTP3.Lnkset.Unavail.D ur Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
Issue 01 (2013-05-04)
2974
2.37 Measurement of Non-Channelized Optical Port Performance(NON_CHANNELIZED_OPTICAL_PORT)

Overview
Measurement of Non-channelized Optical Port Performance indicates the transmission quality of the optical ports on the UOIa and UOIc boards.
FunctionSubSets
FunctionSubSet NON.CHANNELIZED.OPTICAL.PORT UOI.BOARD FunctionSubSet Name Non Channelized Optical Port Measurement Maximum flux of UOI board
2.37.1 Non Channelized Optical Port Measurement (NON.CHANNELIZED.OPTICAL.PORT)

Overview
Optical ports are important resources of the Base Station Controller. Therefore, the optical ports can be measured for the analysis of the transmission quality of the running Base Station Controller so that the stable and reliable operation of the Base Station Controller can be maintained.
Counters
Counter ID 73416121 Counter Name VS.NONCHANNE LIZED.RXCELLS VS.NONCHANNE LIZED.TXCELLS VS.NONCHANNE LIZED.FAULTTI ME VS.NONCHANNE LIZED.TXMAXSP EED Counter Description T7214:Number of Cells Received on the Optical Port T7217:Number of Cells Transmitted on the Optical Port T7222:Duration of Faults on the Optical Port T7225:Highest Transmit Rate over the Optical Port Original Release V900R012
73416122
V900R012
73404139
V900R012
73416123
V900R012
Issue 01 (2013-05-04)
2975
Counter ID 73416124
Counter Name VS.NONCHANNE LIZED.TXMINSP EED VS.NONCHANNE LIZED.TXMEANSPEED VS.NONCHANNE LIZED.RXMAXSP EED VS.NONCHANNE LIZED.RXMINSP EED VS.NONCHANNE LIZED.RXMEANSPEED
Counter Description T7226:Lowest Transmit Rate over the Optical Port T7227:Mean Transmit Rate over the Optical Port T7230:Highest Receive Rate over the Optical Port T7231:Lowest Receive Rate over the Optical Port T7232:Mean Receive Rate over the Optical Port
73416125
V900R012
73416126
V900R012
73416127
V900R012
73416128
V900R012
None
2.37.1.1 Counters Related to the Number of Cells Received or Transmitted on the optical port Counters
Counter ID 73416121 73416122 Counter Name VS.NONCHANNELIZED. RXCELLS VS.NONCHANNELIZED. TXCELLS Counter Description T7214:Number of Cells Received on the Optical Port T7217:Number of Cells Transmitted on the Optical Port
Description
These counters provide the number of cells received or transmitted on the optical port in the measurement period.
Issue 01 (2013-05-04)
2976
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of IEs transmitted on the port once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.NONCHANNELIZED. RXCELLS VS.NONCHANNELIZED. TXCELLS Feature ID WRFD-05030103 Feature Name ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface
WRFD-05030103
2.37.1.2 Duration of Faults in the optical port Counters

Counter ID 73404139 Counter Name VS.NONCHANNELIZED.F AULTTIME Counter Description T7222:Duration of Faults on the Optical Port
Description
This counter provides the duration of faults in the optical port in the measurement period.
Measurement point
Formula
None
Unit
s
Related Features
Counter Name VS.NONCHANNELIZED.F AULTTIME Feature ID WRFD-05030103 Feature Name ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface
2.37.1.3 Counters Related to the Receive Rate or Transmit Rate over the optical port Counters
Counter ID 73416123 73416124 73416125 73416126 73416127 73416128 Counter Name VS.NONCHANNELIZED. TXMAXSPEED VS.NONCHANNELIZED. TXMINSPEED VS.NONCHANNELIZED. TXMEANSPEED VS.NONCHANNELIZED. RXMAXSPEED VS.NONCHANNELIZED. RXMINSPEED VS.NONCHANNELIZED. RXMEANSPEED Counter Description T7225:Highest Transmit Rate over the Optical Port T7226:Lowest Transmit Rate over the Optical Port T7227:Mean Transmit Rate over the Optical Port T7230:Highest Receive Rate over the Optical Port T7231:Lowest Receive Rate over the Optical Port T7232:Mean Receive Rate over the Optical Port
Description
These counters provide the transmit rate over the optical port in the measurement period.
Measurement point
Issue 01 (2013-05-04)
2978
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.NONCHANNELIZED. TXMAXSPEED VS.NONCHANNELIZED. TXMINSPEED VS.NONCHANNELIZED. TXMEANSPEED VS.NONCHANNELIZED. RXMAXSPEED VS.NONCHANNELIZED. RXMINSPEED VS.NONCHANNELIZED. RXMEANSPEED Feature ID WRFD-05030103 Feature Name ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface
WRFD-05030103
WRFD-05030103
WRFD-05030103
WRFD-05030103
WRFD-05030103
2.37.2 Maximum flux of UOI board(UOI.BOARD)

Overview
The measuerment indicates the flux of all the UOI board.
Counters
Counter ID 73416129 Counter Name VS.UOI.RXMAXSPEED Counter Description T7236:Maximum Receive Rate of UOI board Original Release V900R012
Issue 01 (2013-05-04)
2979
Counter ID 73416130
Counter Name VS.UOI.TXMAXSPEED
Counter Description T7237:Maximum Transmit Rate of UOI board
None
2.37.2.1 Maximum receiving and transmitting rate of UOI board Counters

Counter ID 73416129 73416130 Counter Name VS.UOI.RXMAXSPEED VS.UOI.TXMAXSPEED Counter Description T7236:Maximum Receive Rate of UOI board T7237:Maximum Transmit Rate of UOI board
Description
These counters provide the maximum receive rate or transmit rate of an UOI board in the measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the board once every five seconds. The maximum speed is calculated with the maximum bytes in five seconds.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
2980
Related Features
Counter Name VS.UOI.RXMAXSPEED Feature ID WRFD-05030103 Feature Name ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface
VS.UOI.TXMAXSPEED
WRFD-05030103
2.38 Measurement of NODEB OAM Flow Performance (OAM_FLOW)

Overview
The Measurement of NODEB OAM Flow Performance (OAM_FLOW) measurement object measures the transmission quality of the NodeB OAM flows at the IP layer and the transmission quality of NodeB OAM flows using ATM/IP dual stack transmission at the IP layer.
FunctionSubSets
FunctionSubSet OAM.FLOW FunctionSubSet Name NODEB OAM FLOW Measurement
2.38.1 NODEB OAM FLOW Measurement(OAM.FLOW)

Overview
The operation and maintenance (OM) of the NodeB is performed through the OM channel between the RNC and the NodeB. The OM flow measurement at the IP layer indicates the transmission quality of the OM channel. Figure 1 shows the location of the IP Layer in the procotol. Figure 2-57 The four layers of the TCP/IP protocol suite
Issue 01 (2013-05-04)
2981
Figure 2-58 Physical bearer of the logical port for the NodeB OAM
The position of the OAM flow in the configuration structure is in figure 2 and figure 3. Figure 2-59 Physical bearer of the NodeB OAM
Issue 01 (2013-05-04)
2982
Counters
Counter ID 67195465 Counter Name VS.OAM.FLOW.T XPACKETS VS.OAM.FLOW.T XBYTES VS.OAM.FLOW.T XDROPPACKETS Counter Description Number of Packets Transmitted on OM Flow Number of Bytes Transmitted on OM Flow Number of Packets Discarded in Transmission on OM Flow Number of Bytes Discarded in Transmission on OM Flow Number of Packets Received on OM Flow Number of Bytes Received on OM Flow Number of Packets Discarded in Reception on OM Flow Number of Bytes Discarded in Reception on OM Flow Maximum Number of Bytes Transmitted on OM Flow Maximum Transmit Rate on OM Flow Average Transmit Rate on OM Flow Maximum Number of Bytes Received on OM Flow Maximum Receive Rate on OM Flow Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67195466
67195467
67195468
VS.OAM.FLOW.T XDROPBYTES
67195469
VS.OAM.FLOW.R XPACKETS VS.OAM.FLOW.R XBYTES VS.OAM.FLOW.R XDROPPACKETS
67195470
67195471
67195472
VS.OAM.FLOW.R XDROPBYTES
67195473
VS.OAM.FLOW.P EAK.TXBYTES VS.OAM.FLOW.P EAK.TXRATE VS.OAM.FLOW. MEANS.TX VS.OAM.FLOW.P EAK.RXBYTES VS.OAM.FLOW.P EAK.RXRATE
2983
67204726 67204727 67195474
67204728
Issue 01 (2013-05-04)
Counter ID 67204729
Counter Name VS.OAM.FLOW. MEANS.RX
Counter Description Average Receive Rate on OM Flow
None
2.38.1.1 Counters Related to the Number of Packets Received or Transmitted in the OAM FLOW Counters
Counter ID 67195469 67195465 67195467 Counter Name VS.OAM.FLOW.RXPACK ETS VS.OAM.FLOW.TXPACKETS VS.OAM.FLOW.TXDROPPACKETS VS.OAM.FLOW.RXDROP PACKETS Counter Description Number of Packets Received on OM Flow Number of Packets Transmitted on OM Flow Number of Packets Discarded in Transmission on OM Flow Number of Packets Discarded in Reception on OM Flow
67195471
Description
These counters provide the number of packets received or transmitted in the OAM FLOW at the IP layer in the specified measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of packets transmitted, received or discarded on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
packet
Related Features
Counter Name VS.OAM.FLOW.RXPACK ETS VS.OAM.FLOW.TXPACKETS VS.OAM.FLOW.TXDROPPACKETS VS.OAM.FLOW.RXDROP PACKETS Feature ID WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.38.1.2 Counters Related to the Number of Bytes Received or Transmitted in the OAM FLOW Counters
Counter ID 67195470 67195466 67195468 67195472 67195473 67195474 Counter Name VS.OAM.FLOW.RXBYTE S VS.OAM.FLOW.TXBYTE S VS.OAM.FLOW.TXDROPBYTES VS.OAM.FLOW.RXDROP BYTES VS.OAM.FLOW.PEAK.TX BYTES VS.OAM.FLOW.PEAK.RX BYTES Counter Description Number of Bytes Received on OM Flow Number of Bytes Transmitted on OM Flow Number of Bytes Discarded in Transmission on OM Flow Number of Bytes Discarded in Reception on OM Flow Maximum Number of Bytes Transmitted on OM Flow Maximum Number of Bytes Received on OM Flow
Description
These counters provide the number of bytes received or transmitted in the OAM FLOW at the IP layer in the specified measurement period. The number of bytes measured includes the number of bytes in the header of the IP packet and the payload.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes transmitted, received or discarded on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.OAM.FLOW.RXBYTE S VS.OAM.FLOW.TXBYTE S VS.OAM.FLOW.TXDROPBYTES VS.OAM.FLOW.RXDROP BYTES VS.OAM.FLOW.PEAK.TX BYTES VS.OAM.FLOW.PEAK.RX BYTES Feature ID WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.38.1.3 Counters Related to the Receive Rate or Transmit Rate of the OAM FLOW Counters
Counter ID 67204728 67204726 67204727 67204729 Counter Name VS.OAM.FLOW.PEAK.RX RATE VS.OAM.FLOW.PEAK.TX RATE VS.OAM.FLOW.MEANS.T X VS.OAM.FLOW.MEANS. RX Counter Description Maximum Receive Rate on OM Flow Maximum Transmit Rate on OM Flow Average Transmit Rate on OM Flow Average Receive Rate on OM Flow
Issue 01 (2013-05-04)
2986
Description
These counters provide the receive rate or transmit rate of the OAM FLOW at the IP layer in the specified measurement period. The rates measured here include the spending of the IP header and the payload of the IP packet.
Measurement point
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.OAM.FLOW.PEAK.RX RATE VS.OAM.FLOW.PEAK.TX RATE VS.OAM.FLOW.MEANS.T X VS.OAM.FLOW.MEANS. RX Feature ID WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.39 Measurement of PPP Link Performance(PPP)

Overview
Measurement of PPP Link Performance indicates the transmission quality of a PPP link on the PEUa, PEUc, POUa, POUc or UOIa board.
FunctionSubSets
FunctionSubSet PPP
Issue 01 (2013-05-04)
FunctionSubSet Name PPP Link Measurement
2987
2.39.1 PPP Link Measurement(PPP)

Overview
The quality of transmission links directly affects the system performance. The PPP link measurement helps analyze system transmission quality so as to maintain system stability and reliability. PPP link belongs to the Link layer of the TCP/IP protocol suite, as figure 1 shows. Figure 2-60 The four layers of the TCP/IP protocol suite
In the configuration structure, PPP links are between physical ports and logical applications, as shown in the figure 2. Figure 2-61 Physical bearer of the PPP Link
Issue 01 (2013-05-04)
2988
Counters
Counter ID 67194417 Counter Name VS.PPP.TXPACK ETS VS.PPP.TXBYTES Counter Description T7345:Number of Frames Transmitted on a PPP Link T7346:Number of Bytes Transmitted on a PPP Link. T7347:Number of Frames Discarded in Transmission on a PPP Link T7348:Number of Frames Successfully Received on a PPP Link T7349:Number of Bytes Received on a PPP Link T7350:Number of Frames Discarded in Reception on a PPP Link T7353:Duration of Faults on a PPP Link T7356:Maximum Transmit Rate of a PPP Link T7357:Minimum Transmit Rate of a PPP Link T7358:Average Transmit Rate of a PPP Link T7361:Maximum Receive Rate of a PPP Link T7362:Minimum Receive Rate of a PPP Link Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67194418
67194419
VS.PPP.TXDROPS
67194420
VS.PPP.RXPACK ETS
67194421
VS.PPP.RXBYTES
67194422
VS.PPP.RXDROP S
67194425 67194426
VS.PPP.FAULTTI ME VS.PPP.TXMAXSPEED VS.PPP.TXMINSPEED VS.PPP.TXMEANSPEED VS.PPP.RXMAXSPEED VS.PPP.RXMINSPEED
67194427
67194428
67194429
67194430
Issue 01 (2013-05-04)
2989
Counter ID 67194431
Counter Name VS.PPP.RXMEAN SPEED VS.PPP.Alloced.Av e.Fwd
Counter Description T7363:Average Receive Rate of a PPP Link T7365:Mean forward bandwidth assigned to a PPP link T7368:Mean backward Bandwidth Assigned to a PPP Link T7371:Maximum forward bandwidth assigned to a PPP link T7372:Maximum backward bandwidth assigned to a PPP link T7373:Number of forward congestions on a PPP link T7374:Duration of forward congestion on a PPP link T7375:Number of backward congestions on a PPP link T7376:Duration of backward congestion on a PPP link
67204198
67204199
VS.PPP.Alloced.Av e.Bwd
67193245
VS.PPP.Alloced.M ax.Fwd
67193246
VS.PPP.Alloced.M ax.Bwd
67193247
VS.PPP.Fwd.Cong
67193248
VS.PPP.Fwd.Cong. Dur VS.PPP.Bwd.Cong
67193249
67193250
VS.PPP.Bwd.Cong. Dur
None
2.39.1.1 Number of Frames Received, Transmitted or Discarded on a PPP Link
Issue 01 (2013-05-04)
2990
Counters
Counter ID 67194420 Counter Name VS.PPP.RXPACKETS Counter Description T7348:Number of Frames Successfully Received on a PPP Link T7345:Number of Frames Transmitted on a PPP Link T7347:Number of Frames Discarded in Transmission on a PPP Link T7350:Number of Frames Discarded in Reception on a PPP Link
67194417 67194419
VS.PPP.TXPACKETS VS.PPP.TXDROPS
67194422
VS.PPP.RXDROPS
Description
These counters provide the number of frames received or transmitted on a PPP link in the specified measurement period. The frames measured here are PPP frames.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of frames transmitted, received or discarded on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
frame
Related Features
Counter Name VS.PPP.RXPACKETS VS.PPP.TXPACKETS VS.PPP.TXDROPS VS.PPP.RXDROPS Feature ID WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2991
Issue 01 (2013-05-04)
2.39.1.2 Number of Bytes Received or Transmitted on a PPP Link Counters

Counter ID 67194421 67194418 Counter Name VS.PPP.RXBYTES VS.PPP.TXBYTES Counter Description T7349:Number of Bytes Received on a PPP Link T7346:Number of Bytes Transmitted on a PPP Link.
Description
These counters provide the number of bytes received or transmitted on a PPP link in the specified measurement period. The number of bytes measured includes the number of bytes in the header of the PPP frame and the payload.
Measurement point
Formula
None
Unit
byte
Related Features
Counter Name VS.PPP.RXBYTES VS.PPP.TXBYTES Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.39.1.3 Duration of Faults on a PPP Link
Issue 01 (2013-05-04)
2992
Counters
Counter ID 67194425 Counter Name VS.PPP.FAULTTIME Counter Description T7353:Duration of Faults on a PPP Link
Description
This counter provides the duration of faults on a PPP link in the specified measurement period.
Measurement point
Formula
None
Unit
s
Related Features
Counter Name VS.PPP.FAULTTIME Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2.39.1.4 Counters Related to the Receive Rate or Transmit Rate of a PPP Link Counters
Counter ID 67194426 67194427 67194428 67194429 Counter Name VS.PPP.TXMAXSPEED VS.PPP.TXMINSPEED VS.PPP.TXMEANSPEED VS.PPP.RXMAXSPEED Counter Description T7356:Maximum Transmit Rate of a PPP Link T7357:Minimum Transmit Rate of a PPP Link T7358:Average Transmit Rate of a PPP Link T7361:Maximum Receive Rate of a PPP Link
2993
Issue 01 (2013-05-04)
Counter ID 67194430 67194431
Counter Name VS.PPP.RXMINSPEED VS.PPP.RXMEANSPEED
Counter Description T7362:Minimum Receive Rate of a PPP Link T7363:Average Receive Rate of a PPP Link
Description
These counters provide the receive rate or transmit rate of a PPP link in the specified measurement period. The rates measured here include the spending of the header and the payload of the PPP frame.
Measurement point
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.PPP.TXMAXSPEED VS.PPP.TXMINSPEED VS.PPP.TXMEANSPEED VS.PPP.RXMAXSPEED VS.PPP.RXMINSPEED VS.PPP.RXMEANSPEED Feature ID WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
Issue 01 (2013-05-04)
2994
2.39.1.5 Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to a PPP Link Counters
Counter ID 67204198 Counter Name VS.PPP.Alloced.Ave.Fwd Counter Description T7365:Mean forward bandwidth assigned to a PPP link T7368:Mean backward Bandwidth Assigned to a PPP Link T7371:Maximum forward bandwidth assigned to a PPP link T7372:Maximum backward bandwidth assigned to a PPP link
67204199
VS.PPP.Alloced.Ave.Bwd
67193245
VS.PPP.Alloced.Max.Fwd
67193246
VS.PPP.Alloced.Max.Bwd
Description
These counters provide the forward bandwidth or backward bandwidth assigned to a PPP link from different perspectives.
Measurement point
In the measurement period, the system automatically takes samples on the forward bandwidth and backward bandwidth assigned to a PPP link every 15 seconds. At the end of the measurement period, the maximum forward bandwidth and the maximum backward bandwidth assigned to a PPP link in the measurement period are obtained. The mean forward bandwidth assigned to a PPP link equals to the accumulated value of the forward bandwidth at the sampling points divided by the number of sampling times. The mean backward bandwidth assigned to a PPP link equals to the accumulated value of the backward bandwidth at the sampling points divided by the number of sampling times.
Formula
None
Unit
bit/s
Issue 01 (2013-05-04)
2995
Related Features
Counter Name VS.PPP.Alloced.Ave.Fwd VS.PPP.Alloced.Ave.Bwd VS.PPP.Alloced.Max.Fwd VS.PPP.Alloced.Max.Bwd Feature ID WRFD-050402 WRFD-050402 WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.39.1.6 Measurement of the Number of Congestions on a PPP Link Counters

Counter ID 67193247 67193249 Counter Name VS.PPP.Fwd.Cong VS.PPP.Bwd.Cong Counter Description T7373:Number of forward congestions on a PPP link T7375:Number of backward congestions on a PPP link
Description
These counters provide the number of congestions on a PPP link in the measurement period.
Measurement point
The counter value is increased by one each time the state of a PPP link changes from noncongestion to congestion(The remaining bandwidth available is smaller than the congestion remain threshold).
Formula
None
Unit
None
Issue 01 (2013-05-04)
2996
Related Features
Counter Name VS.PPP.Fwd.Cong VS.PPP.Bwd.Cong Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.39.1.7 Measurement of the Duration of Congestion on a PPP Link Counters

Counter ID 67193248 67193250 Counter Name VS.PPP.Fwd.Cong.Dur VS.PPP.Bwd.Cong.Dur Counter Description T7374:Duration of forward congestion on a PPP link T7376:Duration of backward congestion on a PPP link
Description
These counters provide the duration of congestion on a PPP link in the measurement period.
Measurement point
The measurement of a forward(backward) congestion duration starts when a forward(backward) congestion is generated on a PPP link and stops when the forward(backward) congestion is cleared. In the measurement period, the accumulated forward(backward) congestion time on the PPP link is taken as the value of this counter.
Formula
None
Unit
s
Related Features
Counter Name VS.PPP.Fwd.Cong.Dur Feature ID WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface
2997
Issue 01 (2013-05-04)
Counter Name VS.PPP.Bwd.Cong.Dur
Feature Name IP Transmission Introduction on Iub Interface
2.40 Measurement of PPP Queue Performance (PPP_QUEUE)

Overview
Measurement of PPP Queue Performance indicates the transmission quality of a PPP link queue on the PEUa, PEUc, UOIa or POUc board.
FunctionSubSets
FunctionSubSet PPP.QUEUE FunctionSubSet Name PPP Link Queue Measurement
2.40.1 PPP Link Queue Measurement(PPP.QUEUE)

Overview
PPP links are important resources of the Base Station Controller. The transmission quality of PPP links affects the availability of system functions. One PPP message enters one of six services data queues separately by Differentiated Service Code Point (DSCP). That is, the services of different types can be transmitted through different queues according to certain rules, and the PPP link schedules the data in different queues according to priorities. You can run the following commands to query the correspondence between service types and queues: 1. You can run the LST TRMMAP command to query the correspondence between service types and the Per-Hop Behavior (PHB). 2. You can run the LST PHBMAP command to query the correspondence between PHB and DSCP. 3. You can run the LST PHBMAP command to query the correspondence between DSCP and queues. PPP link queues belong to the data link layer. The figure 1 shows the position of the data link layer in the TCP/IP protocol suite.
Issue 01 (2013-05-04)
2998
In the configuration structure, PPP links are between physical ports and logical applications, as shown in the figure 2. Figure 2-63 Physical bearer of the PPP Link Queue
Counters
Counter ID 67195192 Counter Name VS.PPP.QUEUE.T XPACKETS Counter Description T7381:Number of Packets Transmitted in a PPP Link Queue Original Release Earlier than V900R011
Issue 01 (2013-05-04)
2999
Counter ID 67195193
Counter Name VS.PPP.QUEUE.T XBYTES VS.PPP.QUEUE.T XDROPPACKETS
Counter Description T7382:Number of Bytes Transmitted in a PPP Link Queue T7383:Number of Packets Discarded in Transmission on a PPP Link Queue T7384:Number of Bytes Discarded in Transmission on a PPP Link Queue T7386:Maximum Transmit Rate of a PPP Link Queue T7387:Average Transmit Rate of a PPP Link Queue
67195194
67195195
VS.PPP.QUEUE.T XDROPBYTES
67204582
VS.PPP.QUEUE.P EAK.TXRATE VS.PPP.QUEUE.M EAN.TX
67204583
None
2.40.1.1 Counters Related to the Number of Packets Transmitted in a PPP Link Queue or Discarded in the Transmitting Direction of a PPP Link Queue Counters
Counter ID 67195192 Counter Name VS.PPP.QUEUE.TXPACKETS VS.PPP.QUEUE.TXDROPPACKETS Counter Description T7381:Number of Packets Transmitted in a PPP Link Queue T7383:Number of Packets Discarded in Transmission on a PPP Link Queue
67195194
Description
These counters provide the number of frames transmitted in a PPP link queue and the number of frames discarded in the transmitting direction of the PPP link queue. The frames measured here are PPP frames.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of frames transmitted or discarded on the link once every five seconds and obtains the total number of frames in one measurement period.
Formula
None
Unit
frame
Related Features
Counter Name VS.PPP.QUEUE.TXPACKETS VS.PPP.QUEUE.TXDROPPACKETS Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.40.1.2 Counters Related to the Number of Bytes Transmitted in a PPP Link Queue or Discarded in the Transmitting Direction of a PPP Link Queue Counters
Counter ID 67195193 Counter Name VS.PPP.QUEUE.TXBYTE S VS.PPP.QUEUE.TXDROPBYTES Counter Description T7382:Number of Bytes Transmitted in a PPP Link Queue T7384:Number of Bytes Discarded in Transmission on a PPP Link Queue
67195195
Description
These counters provide the number of bytes transmitted in a PPP link queue and the number of bytes discarded in the transmitting direction of the PPP link queue.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes transmitted or discarded on the link once every five seconds and obtains the total number of bytes in one measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.PPP.QUEUE.TXBYTE S VS.PPP.QUEUE.TXDROPBYTES Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.40.1.3 Counters Related to the Transmit Rate of a PPP Link Queue Counters
Counter ID 67204582 67204583 Counter Name VS.PPP.QUEUE.PEAK.TX RATE VS.PPP.QUEUE.MEAN.T X Counter Description T7386:Maximum Transmit Rate of a PPP Link Queue T7387:Average Transmit Rate of a PPP Link Queue
Description
These counters provide the transmit rate of a PPP link queue in the specified measurement period. The rates measured here include the spending of the header and the payload of the PPP frame.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes transmitted on the link once every five seconds. With this, the system obtains the maximum number of bytes transmitted in five seconds, and the total number of one measurement period. The maximum speed is calculated with the maximum bytes in five seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.PPP.QUEUE.PEAK.TX RATE VS.PPP.QUEUE.MEAN.T X Feature ID WRFD-050402 WRFD-050402 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iub Interface
2.41 Measurement of SAAL Link Performance(SAAL_LNK)

Overview
The measurement object of SAAL Link Measurement (SAAL_LNK) is used to measure the SAAL links or SAAL PVC. It includes two function subsets, namely SAAL_LNK and SAAL_PVC.
FunctionSubSets
FunctionSubSet SAAL.LNK FunctionSubSet Name SAAL Link Measurement
2.41.1 SAAL Link Measurement(SAAL.LNK)

Overview
The SAAL link measurement provides the reliable function of transmitting the signaling message in point-to-point mode for the RNC. The signaling messages from the RNC to a NodeB, CN, or neighboring RNC (NRNC) are all transmitted through the SAAL link. The SAAL link to a NodeB is called User-to-Network Interface (UNI) SAAL link. The SAAL link to the CN or an NRNC is called Network-to-Network Interface (NNI) SAAL link. For details about the M3UA function, see the protocol ITU-T Q.2110.
Counters
Counter ID 67182593 67182594 Counter Name VS.SAAL.LnkServ Dur.Time VS.SAAL.FailLnk. AllReasons Counter Description In-Service Duration of SAAL Link Number of SAAL Link Failures (All Causes) Original Release Earlier than V900R011 Earlier than V900R011
Issue 01 (2013-05-04)
3003
Counter ID 67182595
Counter Name VS.SAAL.FailLnk. NoRspTimExp VS.SAAL.FailLnk. ExcesErr.Rat VS.SAAL.FailLnk. ExcesNoCred VS.SAAL.FailLnk. AlignFail VS.SAAL.LnkErr. SDRetransTx
Counter Description Number of SAAL Failures (Timer Expires) Number of SAAL Failures (Over-High BER) Number of SAAL Link Failures (Congestion) Number of SAAL Link Alignment Failures Number of SAAL Link MAA-ERROR Indications (SDLOSS_TX) Number of SAAL Link MAA-ERROR Indications (Invalid PDU) Number of SAAL Link MAA-ERROR Indications (Others) Number of SAAL Link MAA-ERROR Indications Received (Unsuccessful Retransmission) Number of Bytes Received by SAAL Link Number of Bytes Sent by SAAL Link Number of Packets Discarded by SAAL Link Due to Buffer Congestion Number of SAAL Link MAA-ERROR Indications (SDLOSS_RX)
67182596
67182597
67182598
67182599
67182600
VS.SAAL.LnkErr. PDUInval
67182601
VS.SAAL.LnkErr. OthReasons VS.SAAL.LnkErr. RetransFail
67182602
67190615
VS.AAL5.SAALLn k.BytesRx VS.AAL5.SAALLn k.BytesTx VS.SAAL.LnkErr. BufferLoss
67190616 67196153
73421684
VS.SAAL.LnkErr. SDRetransRx
V900R012
Issue 01 (2013-05-04)
3004
None
2.41.1.1 In-Service Duration of SAAL Link Counters

Counter ID 67182593 Counter Name VS.SAAL.LnkServDur.Tim e Counter Description In-Service Duration of SAAL Link
Description
The measurement is triggered when an unavailabel SAAL link becomes available, and is stopped when the SAAL link becomes unavailable again. At the end of the measurement period, the RNC accumulates the total duration when the SAAL link is available and restarts the measurement.
Measurement point
In the measurement period, the measurement is triggered when the SAAL link changes from the unavailable state to the available state, and is stopped when the SAAL link returns to the unavailable state. The duration of this available time is calculated. At the end of the measurement period, the durations of available periods of the SAAL link are accumulated and the measurement is restarted.
Formula
None
Unit
s
Related Features
Counter Name VS.SAAL.LnkServDur.Tim e Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.41.1.2 Number of SAAL Link Failures

Counters
Counter ID 67182594 Counter Name VS.SAAL.FailLnk.AllReasons Counter Description Number of SAAL Link Failures (All Causes)
Description
This counter provides the number of SAAL link failures. The failures include the SAAL disconnection due to various causes and the location failure in the link setup process.
Measurement point
In the measurement period, the counter is incremented by one when the SAAL link changes from "In Service" state to "Out of Service" state or when the SAAL link location fails.
Formula
None
Unit
None
Related Features
Counter Name VS.SAAL.FailLnk.AllReasons Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.41.1.3 Number of Link Failures Due to No Response of SAAL Link Counters

Counter ID 67182595 Counter Name VS.SAAL.FailLnk.NoRspTimExp Counter Description Number of SAAL Failures (Timer Expires)
Description
This counter provides the number of SAAL link failures due to no peer response.
Measurement point
As shown in Figure 1, the RNC sends the POLL message to the peer end but does not receive the state report (STAT) from the peer end. As a result, the local Timer-No_Response expires. Then, the counter is incremented by one. Figure 2-64 SAAL link procedure failure due to no response from the peer end (taking the Iu interface as an example)
Formula
None
Unit
None
Related Features
Counter Name VS.SAAL.FailLnk.NoRspTimExp Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.41.1.4 Number of SAAL Link Failures Due to Excessive Errors

Counters
Counter ID 67182596 Counter Name VS.SAAL.FailLnk.ExcesErr .Rat Counter Description Number of SAAL Failures (Over-High BER)
Description
This counter provides the number of SAAL link failures due to excessive errors. This counter measures the NNI SAAL link only.
Measurement point
In the measurement period, the counter is incremented by one when the SAAL-layer management module releases the SAAL link because too many packets on this link are lost.
Formula
None
Unit
None
Related Features
Counter Name VS.SAAL.FailLnk.ExcesErr .Rat Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.41.1.5 Number of SAAL Link Failures Due to No Credit Counters

Counter ID 67182597 Counter Name VS.SAAL.FailLnk.ExcesNoCred Counter Description Number of SAAL Link Failures (Congestion)
Description
This counter measures the number of SAAL link failures due to no credit for a long time. This counter measures the NNI SAAL link only. The SAAL link controls flow through sliding
window. The credit refers to the size of the sliding window, which indicates the data transmit capacity of the local end.
Measurement point
In the measurement period, the counter is incremented by one when Timer-No_Credit expires.
Formula
None
Unit
None
Related Features
Counter Name VS.SAAL.FailLnk.ExcesNoCred Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.41.1.6 Number of SAAL Link Location Failures Counters

Counter ID 67182598 Counter Name VS.SAAL.FailLnk.AlignFail Counter Description Number of SAAL Link Alignment Failures
Description
This counter provides the number of SAAL link location failures. This counter measures the NNI SAAL link only.
Measurement point
In the measurement period, the counter is incremented by one when the location of the NNI SAAL link fails during the link re-establishment process.
Formula
None
Unit
None
Related Features
Counter Name VS.SAAL.FailLnk.AlignFail Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.41.1.7 Number of Retransmissions of the downlink Lost Packet on the SAAL Link Counters
Counter ID 67182599 Counter Name VS.SAAL.LnkErr.SDRetransTx Counter Description Number of SAAL Link MAA-ERROR Indications (SDLOSS_TX)
Description
This counter provides the number of retransmissions of the downlink lost packet on the SAAL link. The SAAL link provides the reliable signaling transmission for the upper layer. When a packet is lost on the SAAL link, the SAAL link retransmits the lost packet. This counter provides the number of retransmissions of the lost packet on the SAAL link.Services may be affected if many packets are lost and retransmitted on multiple SAAL links.
Measurement point
In the measurement period, the counter is incremented by one when the SAAL link receives a USTAT or STAT message indicating the request for packet retransmission.
Formula
None
Unit
None
Related Features
Counter Name VS.SAAL.LnkErr.SDRetransTx Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
Issue 01 (2013-05-04)
3010
2.41.1.8 Number of Unexpected PDUs Received by SAAL Link Counters

Counter ID 67182600 Counter Name VS.SAAL.LnkErr.PDUInval Counter Description Number of SAAL Link MAA-ERROR Indications (Invalid PDU)
Description
This counter provides the number of unexpected protocol data units (PDUs) received by the SAAL link, that is, the number of error PDUs with error codes A to M received by the SAAL link. For details of the SAAL error codes, see TABLE A.1/Q.2110.
Measurement point
In the measurement period, the counter is incremented by one when the SAAL link receives the unexpected PDU. For example: The idle SAAL link receives the SD packet.
Formula
None
Unit
None
Related Features
Counter Name VS.SAAL.LnkErr.PDUInval Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.41.1.9 Number of Errors of Other Types on SAAL Link Counters

Counter ID 67182601 Counter Name VS.SAAL.LnkErr.OthReasons Counter Description Number of SAAL Link MAA-ERROR Indications (Others)
Issue 01 (2013-05-04)
3011
Description
This counter provides the number of PDUs with error codes Q, R, S, or T received by the SAAL link. For details of the SAAL error codes, see TABLE A.1/Q.2110.
Measurement point
In the measurement period, the counter is incremented by one when the SAAL link receives the error PDU with error codes of Q, R, S, or T.
Formula
None
Unit
None
Related Features
Counter Name VS.SAAL.LnkErr.OthReasons Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.41.1.10 Number of Retransmission Failures of Connection Control Message on SAAL Link Counters
Counter ID 67182602 Counter Name VS.SAAL.LnkErr.RetransFail Counter Description Number of SAAL Link MAA-ERROR Indications Received (Unsuccessful Retransmission)
Description
This counter provides the number of retransmission failures of the connection control messages (including BGN, END, RS, and ER) on the SAAL link. For example: If the peer response cannot be received after the BGN message is sent for certain repeated times during the SAAL link establishment process, it indicates that the retransmission fails.
Measurement point
After the SAAL link sends the connection control message (including BGN, END, RS, and ER), if the peer response message is not received, the TIMER_CC expires and the connection control
message is resent. In the measurement period, the counter is incremented by one when the response message is not received after several transmissions (pre-specified number of transmissions).
Formula
None
Unit
None
Related Features
Counter Name VS.SAAL.LnkErr.RetransFail Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.41.1.11 Number of Bytes Received by SAAL Link Counters

Counter ID 67190615 Counter Name VS.AAL5.SAALLnk.Bytes Rx Counter Description Number of Bytes Received by SAAL Link
Description
This counter provides the number of bytes received by the SAAL link in the specified measurement period.
Measurement point
In the measurement period, this measurement is triggered when the SAAL link receives the data from AAL5.
Formula
None
Unit
byte
Related Features
Counter Name VS.AAL5.SAALLnk.Bytes Rx Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.41.1.12 Number of Bytes Sent by SAAL Link Counters

Counter ID 67190616 Counter Name VS.AAL5.SAALLnk.Bytes Tx Counter Description Number of Bytes Sent by SAAL Link
Description
This counter provides the number of bytes sent by the SAAL link in the specified measurement period.
Measurement point
In the measurement period, this measurement is triggered when the SAAL link sends the data to AAL5.
Formula
None
Unit
byte
Related Features
Counter Name VS.AAL5.SAALLnk.Bytes Tx Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.41.1.13 Number of Packets Discarded by SAAL Link Due to Buffer Congestion

Counters
Counter ID 67196153 Counter Name VS.SAAL.LnkErr.BufferLoss Counter Description Number of Packets Discarded by SAAL Link Due to Buffer Congestion
Description
This counter provides the number of packets discarded by the SAAL link due to buffer full in the specified measurement period.Services wiil be affected if packets are discarded on multiple SAAL links due to a full buffer.
Measurement point
In the measurement period, this measurement is triggered when the SAAL link discards the data due to buffer full.
Formula
None
Unit
None
Related Features
Counter Name VS.SAAL.LnkErr.BufferLoss Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.41.1.14 Number of Retransmissions of the uplink Lost Packet on the SAAL Link Counters
Counter ID 73421684 Counter Name VS.SAAL.LnkErr.SDRetransRx Counter Description Number of SAAL Link MAA-ERROR Indications (SDLOSS_RX)
Issue 01 (2013-05-04)
3015
Description
This counter provides the number of retransmissions of the uplink lost packet on the SAAL link. The SAAL link provides the reliable signaling transmission for the upper layer. When a packet is lost on the SAAL link, the SAAL link retransmits the lost packet. This counter provides the number of retransmissions of the lost packet on the SAAL link.Services may be affected if many packets are lost and retransmitted on multiple SAAL links.
Measurement point
In the measurement period, the counter is incremented by one when the SAAL link sends a USTAT or STAT message indicating the request for packet retransmission.
Formula
None
Unit
None
Related Features
Counter Name VS.SAAL.LnkErr.SDRetransRx Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
2.42 Measurement of SAAL Link ATM Layer Performance (SAALLNK_PVCLAYER)

Overview
Measurement of SAAL Link ATM Layer Performance indicates the transmission quality of an SAAL PVC link on the AEUa, UOIa, AOUa, UOIc or AOUc board.
FunctionSubSets
FunctionSubSet SAALLNK.PVCLAYER FunctionSubSet Name SAAL link ATM Layer Measurement
Issue 01 (2013-05-04)
3016
2.42.1 SAAL link ATM Layer Measurement (SAALLNK.PVCLAYER)

Overview
The quality of transmission links directly affects the system performance. The SAAL link ATM Layer measurement helps analyze system transmission quality so as to maintain system stability and reliability. Figure 1 shows the location of the ATM Layer in the procotol. Figure 2-65 ATM Reference Model
The position of SAAL links in the configuration structure is in figure 2.
Issue 01 (2013-05-04)
3017
Figure 2-66 Physical bearer of the SAAL Link
Counters
Counter ID 67194771 Counter Name VS.SAALLNK.PV CLAYER.TXBYT ES VS.SAALLNK.PV CLAYER.PEAK.T XRATE VS.SAALLNK.PV CLAYER.RXBYT ES VS.SAALLNK.PV CLAYER.PEAK.R XRATE VS.SAALLNK.PV CLAYER.RXCOR RECTPKTS Counter Description Number of Bytes Transmitted on an SAAL Link ATM Layer Maximum Transmit Rate of SAAL Link ATM Layer Number of Bytes Received on an SAAL Link ATM Layer Maximum Receive Rate of an SAAL Link ATM Layer Number of Correct Packets Received on an SAAL Link ATM Layer Original Release Earlier than V900R011
67204473
67194773
67204474
67194775
Issue 01 (2013-05-04)
3018
Counter ID 67194776
Counter Name VS.SAALLNK.PV CLAYER.TXCORRECTPKTS VS.SAALLNK.PV CLAYER.DROPFORCNTERRCEL LS VS.SAALLNK.PV CLAYER.DROPF ORLENERRCELL S
Counter Description Number of Correct Packets Transmitted on an SAAL Link ATM Layer Number of Cells Discarded on an SAAL Link ATM Layer Due to Incorrect content Number of Cells Discarded on an SAAL Link ATM Layer Due to Incorrect Packet length Number of Bytes in Correct AAL2 CPS Packets Received on an SAAL Link ATM Layer Number of Bytes in Correct AAL2 CPS Packets Transmitted on an SAAL Link ATM Layer Number of Cells Discarded on an SAAL Link ATM Layer Due to the Overflow of the Receiving Buffer Number of Cells Discarded on an SAAL Link ATM Layer Due to the Overflow of the Transmitting Buffer
67194777
67194778
67194779
VS.SAALLNK.PV CLAYER.RXBYT ESOFAAL5CPSP KTS VS.SAALLNK.PV CLAYER.TXBYT ESOFAAL5CPSP KTS VS.SAALLNK.PV CLAYER.RXOVE RFLOWDROPPE DCELLS
67194780
67194781
67194782
VS.SAALLNK.PV CLAYER.TXOVE RFLOWDROPPE DCELLS
None
Issue 01 (2013-05-04)
3019
2.42.1.1 Counters Related to the Number of Bytes Received or Transmitted on an SAAL link ATM Layer Counters
Counter ID 67194773 Counter Name VS.SAALLNK.PVCLAYE R.RXBYTES VS.SAALLNK.PVCLAYE R.TXBYTES VS.SAALLNK.PVCLAYE R.RXBYTESOFAAL5CPS PKTS VS.SAALLNK.PVCLAYE R.TXBYTESOFAAL5CPS PKTS Counter Description Number of Bytes Received on an SAAL Link ATM Layer Number of Bytes Transmitted on an SAAL Link ATM Layer Number of Bytes in Correct AAL2 CPS Packets Received on an SAAL Link ATM Layer Number of Bytes in Correct AAL2 CPS Packets Transmitted on an SAAL Link ATM Layer
67194771
67194779
67194780
Description
These counters provide the number of bytes received or transmitted on an SAAL link ATM Layer in the specified measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes transmitted or received on the link once every five seconds and obtains the total number of bytes in one measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.SAALLNK.PVCLAYE R.RXBYTES Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic
3020
Issue 01 (2013-05-04)
Counter Name VS.SAALLNK.PVCLAYE R.TXBYTES VS.SAALLNK.PVCLAYE R.RXBYTESOFAAL5CPS PKTS VS.SAALLNK.PVCLAYE R.TXBYTESOFAAL5CPS PKTS
Feature Name Permanent AAL5 Connections for Control Plane Traffic Permanent AAL5 Connections for Control Plane Traffic Permanent AAL5 Connections for Control Plane Traffic
WRFD-05030105
WRFD-05030105
2.42.1.2 Counters Related to the Maximum Receive Rate or Maximum Transmit Rate of an SAAL link ATM Layer Counters
Counter ID 67204474 67204473 Counter Name VS.SAALLNK.PVCLAYE R.PEAK.RXRATE VS.SAALLNK.PVCLAYE R.PEAK.TXRATE Counter Description Maximum Receive Rate of an SAAL Link ATM Layer Maximum Transmit Rate of SAAL Link ATM Layer
Description
These counters provide the maximum receive rate or the maximum transmit rate of an SAAL link ATM Layer in the specified measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the link once every five seconds. With this, the system obtains the maximum number of bytes received or transmitted in five seconds. The maximum speed is calculated with the maximum bytes in five seconds.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
3021
Related Features
Counter Name VS.SAALLNK.PVCLAYE R.PEAK.RXRATE VS.SAALLNK.PVCLAYE R.PEAK.TXRATE Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic Permanent AAL5 Connections for Control Plane Traffic
WRFD-05030105
2.42.1.3 Counters Related to the Number of Correct Packets Received or Transmitted on an SAAL link ATM Layer Counters
Counter ID 67194775 Counter Name VS.SAALLNK.PVCLAYE R.RXCORRECTPKTS VS.SAALLNK.PVCLAYE R.TXCORRECTPKTS Counter Description Number of Correct Packets Received on an SAAL Link ATM Layer Number of Correct Packets Transmitted on an SAAL Link ATM Layer
67194776
Description
These counters provide the number of correct packets received or transmitted on an SAAL link ATM Layer in the specified measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of packets transmitted or received on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
packet
Issue 01 (2013-05-04)
3022
Related Features
Counter Name VS.SAALLNK.PVCLAYE R.RXCORRECTPKTS VS.SAALLNK.PVCLAYE R.TXCORRECTPKTS Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic Permanent AAL5 Connections for Control Plane Traffic
WRFD-05030105
2.42.1.4 Counters Related to the Number of Cells Discarded on an SAAL link ATM Layer Counters
Counter ID 67194777 Counter Name VS.SAALLNK.PVCLAYE R.DROPFORCNTERRCELLS VS.SAALLNK.PVCLAYE R.DROPFORLENERRCELLS VS.SAALLNK.PVCLAYE R.RXOVERFLOWDROPPEDCELLS VS.SAALLNK.PVCLAYE R.TXOVERFLOWDROPPEDCELLS Counter Description Number of Cells Discarded on an SAAL Link ATM Layer Due to Incorrect content Number of Cells Discarded on an SAAL Link ATM Layer Due to Incorrect Packet length Number of Cells Discarded on an SAAL Link ATM Layer Due to the Overflow of the Receiving Buffer Number of Cells Discarded on an SAAL Link ATM Layer Due to the Overflow of the Transmitting Buffer
67194778
67194781
67194782
Description
These counters provide the number of cells discarded on an SAAL link ATM Layer in the specified measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of IEs discarded on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.SAALLNK.PVCLAYE R.DROPFORCNTERRCELLS VS.SAALLNK.PVCLAYE R.DROPFORLENERRCELLS VS.SAALLNK.PVCLAYE R.RXOVERFLOWDROPPEDCELLS VS.SAALLNK.PVCLAYE R.TXOVERFLOWDROPPEDCELLS Feature ID WRFD-05030105 Feature Name Permanent AAL5 Connections for Control Plane Traffic Permanent AAL5 Connections for Control Plane Traffic Permanent AAL5 Connections for Control Plane Traffic Permanent AAL5 Connections for Control Plane Traffic
WRFD-05030105
WRFD-05030105
WRFD-05030105
2.43 Measurement of VCL PM on a SAAL link (SAALLNK_VCLPM)

Overview
The Measurement of VCL PM on a SAAL link provides the statistics of PM on the ATM layer of the SAAL link for the AOUc and UOIc boards. The SAAL PM function uses forward performance monitoring (FPM) and backward reporting (BR) cells to monitor the number of transmitted and received cells at both ends of the ATM layer on the SAAL link. Before viewing the SAAL PM result, run the ACT VCLPM command to activate the PM function on the SAAL link. The PM function can be activated in three directions: SOURCE, SINK, and BOTH. In the source direction, the source endpoint sends FPM cells to calculate the transmitted cells. In the sink direction, the sink endpoint responds with BR cells to calculate the received cells. BOTH means that an endpoint serves both as a source endpoint and a sink endpoint to send and receive FPM cells. In BOTH mode, both the transmitted and received cells are calculated.
Issue 01 (2013-05-04)
3024
FunctionSubSets
FunctionSubSet SAALLNK.VCLPM FunctionSubSet Name Measurement Related to VCL PM on a SAAL link
2.43.1 Measurement Related to VCL PM on a SAAL link (SAALLNK.VCLPM)

Overview
This measurement uses FPM and BR cells to monitor the ATM transmission quality of a SAAL link. In the source direction, FPM cells are sent periodically to indicate the number of transmitted cells and the number of error cells that failed the Bit Interleaved Parity 16 (BIP16) check. In the sink direction, BR cells are transmitted as response to the FPM cells. The BR cells calculate the number of received cells and the number of error cells that fail the BIP16 check. In the source direction, BR cells are used to calculate the number of discarded cells and the number of cells that are inserted by mistake. In the sink direction, FPM cells are used to calculate the number of discarded cells and the number of cells that are inserted by mistake.
Counters
Counter ID 73441389 Counter Name VS.SAAL.VCLPM. RXCELL VS.SAAL.VCLPM. TXCELL Counter Description Number of Received VCL PM Cells on a SAAL link Number of Transmitted VCL PM Cells on a SAAL link Maximum Receive Rate of VCL PM on a SAAL link Maximum Transmit Rate of VCL PM on a SAAL link Average VCL PM Cell Discard Rate in the Receive Direction of a SAAL link Original Release V900R014
73441390
V900R014
73441391
VS.SAAL.VCLPM. PEAK.RXRATE VS.SAAL.VCLPM. PEAK.TXRATE VS.SAAL.VCLPM. RX.MEAN.LOSTCELLRATE
V900R014
73441392
V900R014
73441393
V900R014
Issue 01 (2013-05-04)
3025
Counter ID 73441397
Counter Name VS.SAAL.VCLPM. RX.PEAK.LOSTCELLRATE
Counter Description Maximum VCL PM Cell Discard Rate in the Receive Direction of a SAAL link Average VCL PM Cell Discard Rate in the Transmit Direction of a SAAL link Maximum VCL PM Cell Discard Rate in the Transmit Direction of a SAAL link Average Rate of Incorrectly Inserted VCL PM Cells in the Receive Direction of a SAAL link Maximum Rate of Incorrectly Inserted VCL PM Cells in the Receive Direction of a SAAL link Average Rate of Incorrectly Inserted VCL PM Cells in the Transmit Direction of a SAAL link Maximum Rate of Incorrectly Inserted VCL PM Cells in the Transmit Direction of a SAAL link Number of VCL PM Error Cell Blocks Failed the BIP16 Check in the Source Direction of a SAAL link
73441394
VS.SAAL.VCLPM. TX.MEAN.LOSTCELLRATE
V900R014
73441398
VS.SAAL.VCLPM. TX.PEAK.LOSTCELLRATE
V900R014
73441395
VS.SAAL.VCLPM. RX.MEAN.ERRIN SERTCELLRATE
V900R014
73441399
VS.SAAL.VCLPM. RX.PEAK.ERRINSERTCELLRATE
V900R014
73441396
VS.SAAL.VCLPM. TX.MEAN.ERRIN SERTCELLRATE
V900R014
73441400
VS.SAAL.VCLPM. TX.PEAK.ERRINSERTCELLRATE
V900R014
73424515
VS.SAAL.VCLPM. SOURCEBIP16CR CERRCELL
V900R014
Issue 01 (2013-05-04)
3026
Counter ID 73424516
Counter Name VS.SAAL.VCLPM. SINKBIP16CRCE RRCELL
Counter Description Number of VCL PM Error Cell Blocks Failed the BIP16 Check in the Sink Direction of a SAAL link
None
2.43.1.1 Number of VCL PM Cells on a SAAL link Counters

Counter ID 73441389 73441390 Counter Name VS.SAAL.VCLPM.RXCEL L VS.SAAL.VCLPM.TXCEL L Counter Description Number of Received VCL PM Cells on a SAAL link Number of Transmitted VCL PM Cells on a SAAL link
Description
These counters provide the number of received and transmitted cells at the ATM layer along a SAAL link. Only ATM cells are calculated.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. The RNC measures the number of cells transmitted at the ATM layers along a SAAL link every 5 seconds and measures the total number at the end of each measurement period.
Formula
None
Unit
None
Issue 01 (2013-05-04)
3027
Related Features
Counter Name VS.SAAL.VCLPM.RXCEL L VS.SAAL.VCLPM.TXCEL L Feature ID WRFD-05030110 WRFD-05030110 Feature Name F5 F5
2.43.1.2 Maximum Data Rate of VCL PM on a SAAL link Counters

Counter ID 73441391 73441392 Counter Name VS.SAAL.VCLPM.PEAK. RXRATE VS.SAAL.VCLPM.PEAK.T XRATE Counter Description Maximum Receive Rate of VCL PM on a SAAL link Maximum Transmit Rate of VCL PM on a SAAL link
Description
These counters provide the maximum receive and transmit rates on a SAAL link, indicating the maximum load in the receive and transmit directions on a SAAL link.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. The RNC measures the number of cells received and transmitted at the ATM layer along a SAAL link every 5 seconds. It compares and obtains the maximum number of received and transmitted cells per 5 seconds within a measurement period and accordingly calculates the maximum receive and transmit rates. The counters are in the unit of kbit/s, and are calculated with the following formula: Maximum receive and transmit rates = Maximum number of received/transmitted cells x 53 x 8/5/1000.
Formula
None
Unit
kbit/s
Issue 01 (2013-05-04)
3028
Related Features
Counter Name VS.SAAL.VCLPM.PEAK. RXRATE VS.SAAL.VCLPM.PEAK.T XRATE Feature ID WRFD-05030110 WRFD-05030110 Feature Name F5 F5
2.43.1.3 VCL PM Cell Discard Rate on a SAAL link Counters

Counter ID 73441393 Counter Name VS.SAAL.VCLPM.RX.ME AN.LOSTCELLRATE VS.SAAL.VCLPM.RX.PE AK.LOSTCELLRATE VS.SAAL.VCLPM.TX.ME AN.LOSTCELLRATE VS.SAAL.VCLPM.TX.PEA K.LOSTCELLRATE Counter Description Average VCL PM Cell Discard Rate in the Receive Direction of a SAAL link Maximum VCL PM Cell Discard Rate in the Receive Direction of a SAAL link Average VCL PM Cell Discard Rate in the Transmit Direction of a SAAL link Maximum VCL PM Cell Discard Rate in the Transmit Direction of a SAAL link
73441397
73441394
73441398
Description
These counters provide the average and maximum rates of cells that are discarded in the receive and transmit directions on a SAAL link. They are used to monitor the error rate of transmission cells on a SAAL link.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. Every 5 seconds within a measurement period, the RNC measures the number of cells that are discarded in the receive and transmit directions at the ATM layers along a SAAL link and compares to obtain the maximum number. To obtain the maximum cell discard rates in the receive and transmit directions, in each direction, the RNC divides the maximum number of cells that are discarded within 5 seconds by the total number of cells measured in those directions during the same period. To obtain the average cell discard rates in the receive and transmit directions, in each direction, the RNC divides the number of cells discarded by the total number of cells measured in those directions.
Formula
None
Unit
%
Related Features
Counter Name VS.SAAL.VCLPM.RX.ME AN.LOSTCELLRATE VS.SAAL.VCLPM.RX.PE AK.LOSTCELLRATE VS.SAAL.VCLPM.TX.ME AN.LOSTCELLRATE VS.SAAL.VCLPM.TX.PEA K.LOSTCELLRATE Feature ID WRFD-05030110 WRFD-05030110 WRFD-05030110 WRFD-05030110 Feature Name F5 F5 F5 F5
2.43.1.4 Rate of Incorrectly Inserted VCL PM Cells on a SAAL link Counters

Counter ID 73441395 Counter Name VS.SAAL.VCLPM.RX.ME AN.ERRINSERTCELLRATE VS.SAAL.VCLPM.RX.PE AK.ERRINSERTCELLRATE VS.SAAL.VCLPM.TX.ME AN.ERRINSERTCELLRATE VS.SAAL.VCLPM.TX.PEA K.ERRINSERTCELLRATE Counter Description Average Rate of Incorrectly Inserted VCL PM Cells in the Receive Direction of a SAAL link Maximum Rate of Incorrectly Inserted VCL PM Cells in the Receive Direction of a SAAL link Average Rate of Incorrectly Inserted VCL PM Cells in the Transmit Direction of a SAAL link Maximum Rate of Incorrectly Inserted VCL PM Cells in the Transmit Direction of a SAAL link
73441399
73441396
73441400
Issue 01 (2013-05-04)
3030
Description
These counters provide the average and maximum rates of cells that are incorrectly inserted in the receive and transmit directions on a SAAL link. They are used to monitor the error rate of transmission cells on a SAAL link.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. Every 5 seconds within a measurement period, the RNC measures the number of cells that are incorrectly inserted in the receive and transmit directions at the ATM layers along a SAAL link and compares to obtain the maximum number. To obtain the maximum rates of incorrectly inserted cells in the receive and transmit directions, in each direction, the RNC divides the maximum number of cells that are incorrectly inserted within 5 seconds by the total number of cells measured in those directions during the same period. To obtain the average rates of incorrectly inserted cells in the receive and transmit directions, in each direction, the RNC divides the total number of incorrectly inserted cells by the total number of measured cells in those directions during a measurement period.
Formula
None
Unit
%
Related Features
Counter Name VS.SAAL.VCLPM.RX.ME AN.ERRINSERTCELLRATE VS.SAAL.VCLPM.RX.PE AK.ERRINSERTCELLRATE VS.SAAL.VCLPM.TX.ME AN.ERRINSERTCELLRATE VS.SAAL.VCLPM.TX.PEA K.ERRINSERTCELLRATE Feature ID WRFD-05030110 Feature Name F5
WRFD-05030110
F5
WRFD-05030110
F5
WRFD-05030110
F5
2.43.1.5 Number of Error VCL PM Cell Blocks Failed BIP16 Check on a SAAL link
Issue 01 (2013-05-04)
3031
Counters
Counter ID 73424515 Counter Name VS.SAAL.VCLPM.SOURC EBIP16CRCERRCELL Counter Description Number of VCL PM Error Cell Blocks Failed the BIP16 Check in the Source Direction of a SAAL link Number of VCL PM Error Cell Blocks Failed the BIP16 Check in the Sink Direction of a SAAL link
73424516
VS.SAAL.VCLPM.SINKBI P16CRCERRCELL
Description
These counters provide the number of error cell blocks that fail the BIP16 check in the receive and transmit directions on an SAAL link. They are used to monitor the error rate of transmission cells on a SAAL link.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. The RNC measures the number of error cell blocks that fail the BIP16 check in the source and link directions at the ATM layer along a SAAL link every 5 seconds and calculates the total number at the end of each measurement period. In each cell block measured for this counter, none of the cells is discarded or incorrectly inserted.
Formula
None
Unit
None
Related Features
Counter Name VS.SAAL.VCLPM.SOURC EBIP16CRCERRCELL VS.SAAL.VCLPM.SINKBI P16CRCERRCELL Feature ID WRFD-05030110 WRFD-05030110 Feature Name F5 F5
Issue 01 (2013-05-04)
3032
2.44 Measurement of SCCP Based on OSP Performance (SCCP)

Overview
SCCP Measurement (SCCP) is used to measure the Signaling Connection and Control Part (SCCP) based on OSP.
FunctionSubSets
FunctionSubSet SCCP FunctionSubSet Name SCCP Measurement
2.44.1 SCCP Measurement(SCCP)

Overview
SCCP measurement provides the counters related to the SCCP originating signaling point. The SCCP provides connection-oriented and connectionless signaling transmission functions. Therefore, SCCP measurement provides the counters related to the number of connectionoriented and connectionless messages received or sent by the SCCP. It also provides the counters related to the errors and failures handled by the SCCP. For details about the SCCP function, see the protocol ITU-T Q.704.
Counters
Counter ID 67178881 Counter Name OS.SCCP.Fail.Rel. Cmp OS.SCCP.TiarTimeout Counter Description T6201:Number of SCCP Connection Release Expiry T6202:Number of SCCP Connection Releases Due to SCCP Inactivity Test Timeout T6203:Number of NSP-Initiated SCCP Connection Releases Received by SCCP Original Release Earlier than V900R011 Earlier than V900R011
67178882
67178883
OS.SCCP.ProvInitRel
Issue 01 (2013-05-04)
3033
Counter ID 67178884
Counter Name OS.SCCP.SegmenFail
Counter Description T6204:Number of SCCP XUDT segmentation Failures T6205:Number of Connection Release (RLSD) Messages Received by SCCP with the Cause of Subsystem Faults T6206:Number of RLSD Messages Received by SCCP with the Cause of MTP Faults T6207:Number of RLSD Messages Received by SCCP with the Cause of Network Congestion T6208:Number of RLSD Messages Received by the SCCP for Other Abnormal Causes except for Subsystem Faults, MTP Faults, and Network Congestion T6209:Number of RLSD Messages Received by the SCCP for Normal Causes T6211:Number of XUDTS Messages Received by SCCP with the Cause of Transmission Error
67178885
VS.SCCP.Rx.RLS D.SubsFail
67178886
VS.SCCP.Rx.RLS D.MtpFail
67178887
VS.SCCP.Rx.RLS D.Cong
67178888
VS.SCCP.Rx.RLS D.Other
67195059
VS.SCCP.RX.RLS D.NORMAL
67178890
VS.SCCP.Rx.XUD TS.ErrorMsg
Issue 01 (2013-05-04)
3034
Counter ID 67178891
Counter Name VS.SCCP.Rx.UDT S.FragFail
Counter Description T6212:Number of UDTS and XUDTS Messages Received by SCCP with the Cause of Segmentation Failure T6214:Number of ERROR PDU Messages Received by SCCP T6215:Number of ERROR PDU Messages Sent by SCCP T6219:Number of SCCP Routing Failures (Destination Signaling Point Inaccessible) T6220:Number of SCCP Routing Failures (Subsystem Faults) T6221:Number of SCCP Routing Failures (Subsystem Uninstalled) T6227:Number of SCCP Routing Failures (Unknown Causes) T6228:Number of UDTS Messages Sent by the SCCP T6229:Number of UDTS Messages Received by the SCCP
67190756
VS.SCCP.Rx.ErrPDU
67190757
VS.SCCP.Tx.ErrPDU
67178896
OS.SCCP.RouteFai l.DSP.Unavai
67178897
OS.SCCP.RouteFai l.SSNFail
67178898
OS.SCCP.RouteFai l.SSNUnequip
67178899
OS.SCCP.RouteFai l.Unkown
67178833
OS.SCCP.Tx.UDT S.Msg OS.SCCP.Rx.UDT S.Msg
67178834
Issue 01 (2013-05-04)
3035
Counter ID 67178835
Counter Name OS.SCCP.HandleTotalMsg
Counter Description T6230:Number of Messages Handled by the SCCP from the Local or Remote End T6231:Number of Messages Sent by the SCCP to the Local Subsystem T6232:Number of Connectionless Messages Sent by SCCP T6233:Number of Connectionless Messages Received by SCCP T6234:Number of Class 2 Messages Received by SCCP T6235:Number of Class 2 Messages Sent by SCCP T6236:Number of CR Messages Sent by SCCP T6237:Number of CR Messages Received by SCCP T6238:Number of CREF Messages Sent by SCCP T6239:Number of CREF Messages Received by SCCP T6240:Ratio of the CREF Messages from the Peer SCCP T6241:Ratio of the CREF Messages from the Local SCCP
67178836
OS.SCCP.HandleLocalSSNMsg
67178837
OS.SCCP.Tx.Msg. 0.1
67178838
OS.SCCP.Rx.Msg. 0.1
67178840
OS.SCCP.Rx.Msg. 2 OS.SCCP.Tx.Msg. 2 OS.SCCP.CR.Tx
67178839
73403248
73403249
OS.SCCP.CR.Rx
73403250
OS.SCCP.CREF.T x OS.SCCP.CREF.R x OS.SCCP.REJ.Remote OS.SCCP.REJ.Local
73403251
73415658
73415659
Issue 01 (2013-05-04)
3036
Counter ID 73403252
Counter Name OS.SCCP.CC.Tx
Counter Description T6242:Number of CC Messages Sent by SCCP T6243:Number of CC Messages Received by SCCP T6244:Number of RLSD Messages Sent by SCCP T6245:Number of RLC Messages Sent by SCCP T6246:Number of RLC Messages Received by SCCP
73403253
OS.SCCP.CC.Rx
73403254
OS.SCCP.RLSD.T x OS.SCCP.RLC.Tx
73403255
73403256
OS.SCCP.RLC.RX
None
2.44.1.1 Number of SCCP Connection Release Expiry Counters

Counter ID 67178881 Counter Name OS.SCCP.Fail.Rel.Cmp Counter Description T6201:Number of SCCP Connection Release Expiry
Description
This counter provides the number of SCCP connection release expiry.
Measurement point
The SCCP starts the release protection timer after sending a connection release (RLSD) message. The timer stops when the SCCP receives the release confirmation (RLC) message from the peer end. This counter is incremented by one when the SCCP does not receive the RLC message until the timer expires within the specific time.
Formula
None
Unit
None
Related Features
Counter Name OS.SCCP.Fail.Rel.Cmp Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.2 Number of SCCP Connection Releases Due to SCCP Inactivity Test Counters
Counter ID 67178882 Counter Name OS.SCCP.TiarTimeout Counter Description T6202:Number of SCCP Connection Releases Due to SCCP Inactivity Test Timeout
Description
This counter provides the connection releases due to the SCCP inactivity test. The SCCP inactivity receive timer (TIAR) and the SCCP inactivity send timer (TIAS) start after the SCCP connection establishment. The TIAS restarts each time the SCCP sends a connection-oriented message. If no connection-oriented message is sent until the TIAS expires, the SCCP sends the inactivity test message (IT). The TIAR restarts each time the SCCP receives a connectionoriented message. If no connection-oriented message is received until the TIAR expires, the SCCP releases the connection.
Measurement point
In the measurement period, the counter is incremented by one when the TIAR expires and the SCCP sends the connection release message.
Formula
None
Unit
None
Issue 01 (2013-05-04)
3038
Related Features
Counter Name OS.SCCP.TiarTimeout Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.3 Number of NSP-initiated SCCP Connection Releases Received by SCCP Counters

Counter ID 67178883 Counter Name OS.SCCP.ProvInitRel Counter Description T6203:Number of NSPInitiated SCCP Connection Releases Received by SCCP
Description
This counter provides the number of SCCP connection releases initiated by the network service provider (NSP).
Measurement point
In the measurement period, the counter is incremented by one when the SCCP receives or sends a connection release message (RLSD) with the cause of "NSP".
Formula
None
Unit
None
Related Features
Counter Name OS.SCCP.ProvInitRel Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.4 Number of SCCP XUDT Segmentation Failures
Issue 01 (2013-05-04)
3039
Counters
Counter ID 67178884 Counter Name OS.SCCP.SegmenFail Counter Description T6204:Number of SCCP XUDT segmentation Failures
Description
This counter provides the number of SCCP XUDT segmentation failures.
Measurement point
In the measurement period, the counter is incremented by one when the size of the connectionless message from the upper layer exceeds the maximum capability (3360 bytes) or the SCCP fails to request a segmentation reference number.
Formula
None
Unit
None
Related Features
Counter Name OS.SCCP.SegmenFail Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.5 Number of RLSD Messages Received by the SCCP Counters

Counter ID 67178885 Counter Name VS.SCCP.Rx.RLSD.SubsFail Counter Description T6205:Number of Connection Release (RLSD) Messages Received by SCCP with the Cause of Subsystem Faults T6206:Number of RLSD Messages Received by SCCP with the Cause of MTP Faults
3040
67178886
VS.SCCP.Rx.RLSD.MtpFai l
Issue 01 (2013-05-04)
Counter ID 67178887
Counter Name VS.SCCP.Rx.RLSD.Cong
Counter Description T6207:Number of RLSD Messages Received by SCCP with the Cause of Network Congestion T6208:Number of RLSD Messages Received by the SCCP for Other Abnormal Causes except for Subsystem Faults, MTP Faults, and Network Congestion T6209:Number of RLSD Messages Received by the SCCP for Normal Causes
67178888
VS.SCCP.Rx.RLSD.Other
67195059
VS.SCCP.RX.RLSD.NORMAL
Description
These counters provide the number of RLSD messages received by the SCCP with different causes.Services may be affected if multiple connections are abnormally released. The following table describes the meaning of each counter. Counter Name VS.SCCP.Rx.RLSD.SubsFail Description This counter provides the number of RLSD messages received by the SCCP with the cause of subsystem faults. This counter provides the number of RLSD messages received by the SCCP with the cause of message transfer part (MTP) faults. This counter provides the number of RLSD messages received by the SCCP with the cause of network congestion. This counter provides the number of RLSD messages received by the SCCP for other abnormal causes except for subsystem faults, MTP faults, and network congestion. This counter provides the number of RLSD messages for normal causes.
VS.SCCP.Rx.RLSD.MtpFail
VS.SCCP.Rx.RLSD.Cong
VS.SCCP.Rx.RLSD.Other
VS.SCCP.RX.RLSD.NORMAL
Measurement point
In the measurement period, these counters are incremented by one when the SCCP receives the RLSD messages with different causes.
Formula
None
Unit
None
Related Features
Counter Name VS.SCCP.Rx.RLSD.SubsFail VS.SCCP.Rx.RLSD.MtpFai l VS.SCCP.Rx.RLSD.Cong VS.SCCP.Rx.RLSD.Other VS.SCCP.RX.RLSD.NORMAL Feature ID WRFD-010101 WRFD-010101 WRFD-010101 WRFD-010101 WRFD-010101 Feature Name Compliance with 3GPP Specifications Compliance with 3GPP Specifications Compliance with 3GPP Specifications Compliance with 3GPP Specifications Compliance with 3GPP Specifications
2.44.1.6 Number of XUDTS Messages Received by the SCCP with the Cause of Transmission Error Counters
Counter ID 67178890 Counter Name VS.SCCP.Rx.XUDTS.ErrorMsg Counter Description T6211:Number of XUDTS Messages Received by SCCP with the Cause of Transmission Error
Description
This counter provides the number of XUDTS messages received by the SCCP with the cause of transmission error.
Measurement point
In the measurement period, the counter is incremented by one when the SCCP receives the XUDTS messages with the cause of transmission error.
Formula
None
Unit
None
Related Features
Counter Name VS.SCCP.Rx.XUDTS.ErrorMsg Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.7 Number of UDTS Messages Received by the SCCP with the Cause of Segmentation Failure Counters
Counter ID 67178891 Counter Name VS.SCCP.Rx.UDTS.FragFail Counter Description T6212:Number of UDTS and XUDTS Messages Received by SCCP with the Cause of Segmentation Failure
Description
This counter provides the number of UDTS messages received by the SCCP with the cause of "segmentation failure".
Measurement point
In the measurement period, the counter is incremented by one when the SCCP receives the UDTS messages with the cause of "segmentation failure".
Formula
None
Unit
None
Issue 01 (2013-05-04)
3043
Related Features
Counter Name VS.SCCP.Rx.UDTS.FragFail Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.8 Number of ERROR PDU Messages Received by the SCCP Counters

Counter ID 67190756 Counter Name VS.SCCP.Rx.ErrPDU Counter Description T6214:Number of ERROR PDU Messages Received by SCCP
Description
This counter provides the number of ERROR PDU messages received by the SCCP.
Measurement point
In the measurement period, the counter is incremented by one when the SCCP receives an ERROR PDU message.
Formula
None
Unit
None
Related Features
Counter Name VS.SCCP.Rx.ErrPDU Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.9 Number of ERROR PDU Messages Sent by the SCCP
Issue 01 (2013-05-04)
3044
Counters
Counter ID 67190757 Counter Name VS.SCCP.Tx.ErrPDU Counter Description T6215:Number of ERROR PDU Messages Sent by SCCP
Description
This counter provides the number of ERROR PDU messages sent by the SCCP.
Measurement point
In the measurement period, the counter is incremented by one when the SCCP sends an ERROR PDU message.
Formula
None
Unit
None
Related Features
Counter Name VS.SCCP.Tx.ErrPDU Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.10 Number of SCCP Routing Failures Counters

Counter ID 67178896 Counter Name OS.SCCP.RouteFail.DSP.U navai Counter Description T6219:Number of SCCP Routing Failures (Destination Signaling Point Inaccessible) T6220:Number of SCCP Routing Failures (Subsystem Faults)
67178897
OS.SCCP.RouteFail.SSNFai l
Issue 01 (2013-05-04)
3045
Counter ID 67178898
Counter Name OS.SCCP.RouteFail.SSNUnequip OS.SCCP.RouteFail.Unkown
Counter Description T6221:Number of SCCP Routing Failures (Subsystem Uninstalled) T6227:Number of SCCP Routing Failures (Unknown Causes)
67178899
Description
These counters provide the number of routing failures for different causes.The routing failure leads to the data transmission failure between the SCCP and the DSP, and services may be affected. The following table describes the meaning of each counter. Counter Name OS.SCCP.RouteFail.DSP.Unavai Description This counter provides the number of SCCP routing failures because the destination signaling point is not accessible or does not exit. This counter provides the number of SCCP routing failures due to subsystem faults. This counter provides the number of SCCP routing failures because the subsystem is not installed. This counter provides the SCCP routing failures for the causes except "destination signaling point failure, subsystem failure, and subsystem uninstalled.
OS.SCCP.RouteFail.SSNFail OS.SCCP.RouteFail.SSNUnequip
OS.SCCP.RouteFail.Unkown
Measurement point
In the measurement period, these counters are incremented by one when the SCCP routing failure occurs.
Formula
None
Unit
None
Related Features
Counter Name OS.SCCP.RouteFail.DSP.U navai OS.SCCP.RouteFail.SSNFai l OS.SCCP.RouteFail.SSNUnequip OS.SCCP.RouteFail.Unkown Feature ID WRFD-010101 WRFD-010101 WRFD-010101 WRFD-010101 Feature Name Compliance with 3GPP Specifications Compliance with 3GPP Specifications Compliance with 3GPP Specifications Compliance with 3GPP Specifications
2.44.1.11 Counters Related to Number of Messages Sent by the SCCP Counters

Counter ID 67178833 67178837 Counter Name OS.SCCP.Tx.UDTS.Msg OS.SCCP.Tx.Msg.0.1 Counter Description T6228:Number of UDTS Messages Sent by the SCCP T6232:Number of Connectionless Messages Sent by SCCP T6235:Number of Class 2 Messages Sent by SCCP
67178839
OS.SCCP.Tx.Msg.2
Description
These counters provide the number of messages sent by the SCCP. The following table describes the meaning of each counter. Counter Name OS.SCCP.Tx.UDTS.Msg OS.SCCP.Tx.Msg.0.1 Description This counter provides the number of unit data service (UDTS) messages sent by the SCCP. This counter provides the number of classes 0 and 1 messages sent by the SCCP, that is, the number of connectionless messages sent by the SCCP. SCCP connectionless messages include the UDT, XUDT, LUDT, UDTS, XUDTS, and LUDTS messages.
Issue 01 (2013-05-04)
3047
Counter Name OS.SCCP.Tx.Msg.2
Description This counter provides the number of class 2 messages sent by the SCCP, that is, the number of connection-oriented messages sent by the SCCP. SCCP connection-oriented messages include the CR, CC, CREF, RLSD, RLC, DT1, and IT messages.
Measurement point
These counters are incremented by one when the SCCP sends the preceding messages.
Formula
None
Unit
None
Related Features
Counter Name OS.SCCP.Tx.UDTS.Msg OS.SCCP.Tx.Msg.0.1 OS.SCCP.Tx.Msg.2 Feature ID WRFD-010101 WRFD-010101 WRFD-010101 Feature Name Compliance with 3GPP Specifications Compliance with 3GPP Specifications Compliance with 3GPP Specifications
2.44.1.12 Counters Related to Number of Messages Received by the SCCP Counters

Counter ID 67178834 Counter Name OS.SCCP.Rx.UDTS.Msg Counter Description T6229:Number of UDTS Messages Received by the SCCP T6233:Number of Connectionless Messages Received by SCCP
67178838
OS.SCCP.Rx.Msg.0.1
Issue 01 (2013-05-04)
3048
Counter ID 67178840
Counter Name OS.SCCP.Rx.Msg.2
Counter Description T6234:Number of Class 2 Messages Received by SCCP
Description
These counters provide the number of messages received by the SCCP. The following table describes the meaning of each counter. Counter Name OS.SCCP.Rx.UDTS.Msg OS.SCCP.Rx.Msg.0.1 Description This counter provides the number of UDTS messages received by the SCCP. This counter provides the number of classes 0 and 1 messages received by the SCCP, that is, the number of connectionless messages received by the SCCP. SCCP connectionless messages include the UDT, XUDT, LUDT, UDTS, XUDTS, and LUDTS messages. This counter provides the number of class 2 messages received by the SCCP, that is, the number of connection-oriented messages received by the SCCP. SCCP connectionoriented messages include the CR, CC, CREF, RLSD, RLC, DT1, and IT messages.
OS.SCCP.Rx.Msg.2
Measurement point
These counters are incremented by one when the SCCP receives the preceding messages.
Formula
None
Unit
None
Related Features
Counter Name OS.SCCP.Rx.UDTS.Msg Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
3049
Issue 01 (2013-05-04)
Counter Name OS.SCCP.Rx.Msg.0.1 OS.SCCP.Rx.Msg.2
Feature Name Compliance with 3GPP Specifications Compliance with 3GPP Specifications
2.44.1.13 Number of Messages Handled by the SCCP Counters

Counter ID 67178835 Counter Name OS.SCCP.HandleTotalMsg Counter Description T6230:Number of Messages Handled by the SCCP from the Local or Remote End
Description
This counter provides the total number of local-end or remote-end messages handled by the SCCP.
Measurement point
This measurement is triggered when the SCCP sends or receives a messages.
Formula
None
Unit
None
Related Features
Counter Name OS.SCCP.HandleTotalMsg Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.14 Number of Messages Sent by the SCCP to the Local Subsystem

Counters
Counter ID 67178836 Counter Name OS.SCCP.HandleLocalSSNMsg Counter Description T6231:Number of Messages Sent by the SCCP to the Local Subsystem
Description
This counter provides the number of messages that the SCCP sends to the local subsystem.
Measurement point
In the measurement period, the counter is incremented by one when the SCCP sends a message to the local subsystem.
Formula
None
Unit
None
Related Features
Counter Name OS.SCCP.HandleLocalSSNMsg Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.15 Number of CR Messages Sent and Received by the SCCP Counters

Counter ID 73403248 73403249 Counter Name OS.SCCP.CR.Tx OS.SCCP.CR.Rx Counter Description T6236:Number of CR Messages Sent by SCCP T6237:Number of CR Messages Received by SCCP
Description
These counters provide the number of CR messages sent and received by the SCCP.
The following table describes the meaning of each counter. Counter Name OS.SCCP.CR.Tx OS.SCCP.CR.Rx Description This counter provides the number of CR messages sent by the SCCP. This counter provides the number of CR messages received by the SCCP.
Measurement point
In the measurement period, these counters are incremented by one when the SCCP sends or receives a CR message.
Formula
None
Unit
None
Related Features
Counter Name OS.SCCP.CR.Tx OS.SCCP.CR.Rx Feature ID WRFD-010101 WRFD-010101 Feature Name Compliance with 3GPP Specifications Compliance with 3GPP Specifications
2.44.1.16 Number of CREF Messages Sent and Received by the SCCP Counters
Counter ID 73403250 73403251 Counter Name OS.SCCP.CREF.Tx OS.SCCP.CREF.Rx Counter Description T6238:Number of CREF Messages Sent by SCCP T6239:Number of CREF Messages Received by SCCP
Issue 01 (2013-05-04)
3052
Description
These counters provide the number of CREF messages sent and received by the SCCP.Services will be affected if many Connection Refused (CREF) messages are sent or received by the SCCP module. The following table describes the meaning of each counter. Counter Name OS.SCCP.CREF.Tx OS.SCCP.CREF.Rx Description This counter provides the number of CREF messages sent by the SCCP. This counter provides the number of CREF messages received by the SCCP.
Measurement point
In the measurement period, these counters are incremented by one when the SCCP sends or receives a CREF message.
Formula
None
Unit
None
Related Features
Counter Name OS.SCCP.CREF.Tx OS.SCCP.CREF.Rx Feature ID WRFD-010101 WRFD-010101 Feature Name Compliance with 3GPP Specifications Compliance with 3GPP Specifications
2.44.1.17 Ratio of the CREF Messages from the Peer SCCP Counters
Counter ID 73415658 Counter Name OS.SCCP.REJ.Remote Counter Description T6240:Ratio of the CREF Messages from the Peer SCCP
Issue 01 (2013-05-04)
3053
Description
This counter provide the ratio of the CREF messages from the peer SCCP to the local SCCP.Services will be affected if the SCCP rejection rate is high.
Measurement point
At the end of each measurement period, this counter is measured by using the following formula: Ratio of CREF by Peer SCCP (%) = [Number of Received CREF Messages] *100/ [Number of Sent CR Messages]
Formula
OS.SCCP.REJ.Remote = [Number of Received CREF Messages] *100/ [Number of Sent CR Messages]
Unit
%
Related Features
Counter Name OS.SCCP.REJ.Remote Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.18 Ratio of the CREF Messages from the Local SCCP Counters
Counter ID 73415659 Counter Name OS.SCCP.REJ.Local Counter Description T6241:Ratio of the CREF Messages from the Local SCCP
Description
This counter provide the ratio of the CREF messages from the local SCCP to the peer SCCP.Services will be affected if many connection setup requests are rejected.
Measurement point
At the end of each measurement period, this counter is measured by using the following formula: Ratio of CREF by Local SCCP (%) = [Number of Sent CREF Messages] *100/ [Number of Received CR Messages]
Formula
OS.SCCP.REJ.Local = [Number of Sent CREF Messages] *100/ [Number of Received CR Messages]
Unit
%
Related Features
Counter Name OS.SCCP.REJ.Local Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.19 Number of CC Messages Sent and Received by the SCCP Counters

Counter ID 73403252 73403253 Counter Name OS.SCCP.CC.Tx OS.SCCP.CC.Rx Counter Description T6242:Number of CC Messages Sent by SCCP T6243:Number of CC Messages Received by SCCP
Description
These counters provide the number of CC messages sent and received by the SCCP. The following table describes the meaning of each counter. Counter Name OS.SCCP.CC.Tx OS.SCCP.CC.Rx Description This counter provides the number of CC messages sent by the SCCP. This counter provides the number of CC messages received by the SCCP.
Measurement point
In the measurement period, these counters are incremented by one when the SCCP sends or receives a CC message.
Formula
None
Unit
None
Related Features
Counter Name OS.SCCP.CC.Tx OS.SCCP.CC.Rx Feature ID WRFD-010101 WRFD-010101 Feature Name Compliance with 3GPP Specifications Compliance with 3GPP Specifications
2.44.1.20 Number of RLSD Messages Sent by the SCCP Counters

Counter ID 73403254 Counter Name OS.SCCP.RLSD.Tx Counter Description T6244:Number of RLSD Messages Sent by SCCP
Description
This counter provides the number of RLSD messages sent by the SCCP.
Measurement point
In the measurement period, the counter is incremented by one when the SCCP sends a RLSD message.
Formula
None
Unit
None
Issue 01 (2013-05-04)
3056
Related Features
Counter Name OS.SCCP.RLSD.Tx Feature ID WRFD-010101 Feature Name Compliance with 3GPP Specifications
2.44.1.21 Number of RLC Messages Sent and Received by the SCCP Counters
Counter ID 73403255 73403256 Counter Name OS.SCCP.RLC.Tx OS.SCCP.RLC.RX Counter Description T6245:Number of RLC Messages Sent by SCCP T6246:Number of RLC Messages Received by SCCP
Description
These counters provide the number of RLC messages sent and received by the SCCP. The following table describes the meaning of each counter. Counter Name OS.SCCP.RLC.Tx OS.SCCP.RLC.RX Description This counter provides the number of RLC messages sent by the SCCP. This counter provides the number of RLC messages received by the SCCP.
Measurement point
In the measurement period, these counters are incremented by one when the SCCP sends or receives a RLC message.
Formula
None
Unit
None
Issue 01 (2013-05-04)
3057
Related Features
Counter Name OS.SCCP.RLC.Tx OS.SCCP.RLC.RX Feature ID WRFD-010101 WRFD-010101 Feature Name Compliance with 3GPP Specifications Compliance with 3GPP Specifications
2.45 Measurement of SCTP Link Performance(SCTPLNK)

Overview
The measurement object SCTPLNK is used to measure the Stream Control Transmission Protocol (SCTP) link.
FunctionSubSets
FunctionSubSet SCTPIP SCTPLNK FunctionSubSet Name SCTPIP Measurement SCTP Link Measurement
2.45.1 SCTPIP Measurement(SCTPIP)

Overview
Based on the IP protocol, the SCTP link provides reliable point-to-point transmission of signaling messages for the Base Station Control. SCTPIP measurement provides the counters related to the traffic on the SCTPIP link. For details about the SCTP protocol, see the protocol RFC4960.
Counters
Counter ID 67191610 Counter Name VS.SCTP.RX.BYT ES VS.SCTP.TX.BYT ES Counter Description T6001:Number of IP Bytes Received on the SCTP Link T6002:Number of IP Bytes Transmitted on the SCTP Link Original Release Earlier than V900R011 Earlier than V900R011
67191611
Issue 01 (2013-05-04)
3058
Counter ID 67191612
Counter Name VS.SCTP.RX.PKG NUM VS.SCTP.TX.PKG NUM VS.SCTP.RX.MAX BYTES
Counter Description T6003:Number of IP Packets Received on the SCTP Link T6004:Number of IP Packets Transmitted on the SCTP Link T6005:Maximum Number of IP Bytes Received on the SCTP Link T6006:Maximum Number of IP Bytes Transmitted on the SCTP Link T6007:Number of Packets Resent on the SCTP Link T6008:Maximum Number of IP Packets Received on the SCTP Link T6009:Maximum Number of IP Packets Transmitted on the SCTP Link T6010:Number of Error Packets Received on SCTP Link T6016:Number of Retransmit Request Sent on the SCTP Link
67191613
67191614
67191615
VS.SCTP.TX.MAX BYTES
67192144
VS.SCTP.RETX.P KGNUM VS.SCTP.RX.MAX PKGNUM
67191616
67191617
VS.SCTP.TX.MAX PKGNUM
67184352
VS.SCTP.RX.ERR PKGNUM
73423484
VS.SCTP.REQ.RE TX.NUM
V900R013
None
2.45.1.1 Counters Related to Number of Bytes That the SCTP Link Receives from or Transmits to the IP Layer
Issue 01 (2013-05-04)
3059
Counters
Counter ID 67191610 67191611 Counter Name VS.SCTP.RX.BYTES VS.SCTP.TX.BYTES Counter Description T6001:Number of IP Bytes Received on the SCTP Link T6002:Number of IP Bytes Transmitted on the SCTP Link T6005:Maximum Number of IP Bytes Received on the SCTP Link T6006:Maximum Number of IP Bytes Transmitted on the SCTP Link
67191614
VS.SCTP.RX.MAXBYTES
67191615
VS.SCTP.TX.MAXBYTES
Description
These counters provide the number of payload bytes of data packets that the SCTP link receives from or transmits to the IP layer in the specified measurement period. The following table describes the meaning of each counter. Counter Name VS.SCTP.RX.BYTES Description This counter provides the number of payload bytes of data packets that the SCTP link receives from the IP layer This counter provides the number of payload bytes of data packets that the SCTP link transmits to the IP layer This counter provides the maximum number of payload bytes of data packets that the SCTP link receives from the IP layer This counter provides the maximum number of payload bytes of data packets that the SCTP link transmits to the IP layer
VS.SCTP.TX.BYTES
VS.SCTP.RX.MAXBYTES
VS.SCTP.TX.MAXBYTES
Measurement point
Number of payload bytes of data packets that the SCTP link receives from or transmits to the IP layer is sampled every five seconds. In the measurement period, the maximum sample is taken as the maximum value of this counter.At the end of the measurement period, the maximum sampling value is taken as the maximum payload and the accumulated sampling value is taken as the total payload.
Formula
None
Unit
byte
Related Features
Counter Name VS.SCTP.RX.BYTES Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.SCTP.TX.BYTES WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.SCTP.RX.MAXBYTES WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.SCTP.TX.MAXBYTES WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.45.1.2 Counters Related to the Number of IP Packets Received or Transmitted on the SCTP Link
Issue 01 (2013-05-04)
3061
Counters
Counter ID 67191612 67191613 Counter Name VS.SCTP.RX.PKGNUM VS.SCTP.TX.PKGNUM Counter Description T6003:Number of IP Packets Received on the SCTP Link T6004:Number of IP Packets Transmitted on the SCTP Link T6008:Maximum Number of IP Packets Received on the SCTP Link T6009:Maximum Number of IP Packets Transmitted on the SCTP Link
67191616
VS.SCTP.RX.MAXPKGNUM VS.SCTP.TX.MAXPKGNUM
67191617
Description
These counters provide the number of all packets that the SCTP link receives from or transmits to the IP layer in the specified measurement period. The following table describes the meaning of each counter. Counter Name VS.SCTP.RX.PKGNUM Description This counter provides the number of all packets that the SCTP link receives from the IP layer This counter provides the number of all packets that the SCTP link transmits to the IP layer This counter provides the maximum number of all packets that the SCTP link receives from the IP layer This counter provides the maximum number of all packets that the SCTP link transmits to the IP layer
VS.SCTP.TX.PKGNUM
VS.SCTP.RX.MAXPKGNUM
VS.SCTP.TX.MAXPKGNUM
Measurement point
Number of all packets that the SCTP link receives from or transmits to the IP layer is sampled every five seconds. If the sampling SCTP link in a failed state, the value of this counter will be 0 in this sampling period. If the SCTP link frequent failure, the value of this counter will be a long time to 0. In the measurement period, the maximum sample is taken as the maximum value of this counter.
Formula
None
Unit
packet
Related Features
Counter Name VS.SCTP.RX.PKGNUM Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.SCTP.TX.PKGNUM WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.SCTP.RX.MAXPKGNUM WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.SCTP.TX.MAXPKGNUM WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.45.1.3 Number of Packets Resent on the SCTP Link Counters

Counter ID 67192144 Counter Name VS.SCTP.RETX.PKGNUM Counter Description T6007:Number of Packets Resent on the SCTP Link
Issue 01 (2013-05-04)
3063
Description
This counter provides the number of packets resent on the SCTP link in the specified measurement period.
Measurement point
In the measurement period, the counter is incremented by one when the packet is resent on the SCTP link.
Formula
None
Unit
packet
Related Features
Counter Name VS.SCTP.RETX.PKGNUM Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.45.1.4 Number of Error Packets Received on SCTP Link Counters

Counter ID 67184352 Counter Name VS.SCTP.RX.ERRPKGNUM Counter Description T6010:Number of Error Packets Received on SCTP Link
Description
All the packets transferred on the SCTP links are assembled from data blocks. Error packets will occur with respect to network performance or upper-layer application. This counter provides the number of error packets received over SCTP links.
Measurement point
In the measurement period, the counter is incremented by one when the error packets are received on the SCTP link.
Formula
None
Unit
packet
Related Features
Counter Name VS.SCTP.RX.ERRPKGNUM Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.45.1.5 Number of Retransmit Request Sent on the SCTP Link Counters

Counter ID 73423484 Counter Name VS.SCTP.REQ.RETX.NU M Counter Description T6016:Number of Retransmit Request Sent on the SCTP Link
Description
This counter provide the number of transmit request sent on SCTP link in the specified measurement.
Measurement point
In the measurement period, the counter is incremented by one when one SACK packet contained Gap Ack Blocks is sent on the SCTP link.
Formula
None
Unit
None
Related Features
Counter Name VS.SCTP.REQ.RETX.NU M Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.45.2 SCTP Link Measurement(SCTPLNK)

Overview
SCTP link measurement provides the counters related to the number of in-service duration and congestion duration of the SCTP link. It also provides the counters related to the number of data packets sent and received on the SCTP link.
Counters
Counter ID 67191618 Counter Name VS.SCTP.SERVIC E.INTERVAL VS.SCTP.CONGE STION.INTERVA L UPUSER.SEND.M SG.NUM UPUSER.RECEIV E.MSG.NUM Counter Description T6011:Service Duration of the SCTP Link T6012:Congestion Duration of the SCTP Link T6014:Number of Packets Sent on the SCTP Link T6015:Number of Packets Received on SCTP Link Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67191619
73403174
73403175
None
2.45.2.1 Service Duration of the SCTP Link
Issue 01 (2013-05-04)
3066
Counters
Counter ID 67191618 Counter Name VS.SCTP.SERVICE.INTERVAL Counter Description T6011:Service Duration of the SCTP Link
Description
This counter provides the in-service duration of an SCTP link.
Measurement point
In the measurement period, the system checks the status of the SCTP link every five seconds. If the link is available, this counter is incremented by five.
Formula
None
Unit
s
Related Features
Counter Name VS.SCTP.SERVICE.INTERVAL Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.45.2.2 Congestion Duration of the SCTP Link Counters

Counter ID 67191619 Counter Name VS.SCTP.CONGESTION.I NTERVAL Counter Description T6012:Congestion Duration of the SCTP Link
Description
This counter provides the congestion duration of the SCTP link.
Measurement point
In the measurement period, the system checks status of the SCTP link every five seconds. If the link is congested, that is, the message sending queue usage of the SCTP link exceeds the congestion threshold, this counter is incremented by five.
Formula
None
Unit
s
Related Features
Counter Name VS.SCTP.CONGESTION.I NTERVAL Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.45.2.3 Number of Packets Sent on the SCTP Link Counters

Counter ID 73403174 Counter Name UPUSER.SEND.MSG.NU M Counter Description T6014:Number of Packets Sent on the SCTP Link
Description
This counter provides the number of data chunks that the SCTP link transmits to the bearing layer in the specified measurement period.
Measurement point
In the measurement period, the sum of data chunks transmitted to the bearing layer on the SCTP link is taken as the value of this counter (a data chunk contains only user data).
Formula
None
Unit
packet
Related Features
Counter Name UPUSER.SEND.MSG.NU M Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.45.2.4 Number of Packets Received on SCTP Link Counters

Counter ID 73403175 Counter Name UPUSER.RECEIVE.MSG. NUM Counter Description T6015:Number of Packets Received on SCTP Link
Description
This counter provides the number of data chunks that the SCTP link receives from the bearing layer in the specified measurement period.
Measurement point
In the measurement period, the sum of data chunks received from the bearing layer on the SCTP link is taken as the value of this counter (a data chunk contains only user data).
Formula
None
Unit
packet
Issue 01 (2013-05-04)
3069
Related Features
Counter Name UPUSER.RECEIVE.MSG. NUM Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
2.46 Measurement of SCTP Link IP Layer Performance (SCTPLNK_IPLAYER)

Overview
Measurement of SCTP Link IP Layer Performance indicates the transmission quality of the IP layer of an SCTP link on the FG2a, GOUa, PEUa, PEUc, UOIa, POUa, FG2d, FG2c, GOUd, GOUc and POUc board.
FunctionSubSets
FunctionSubSet SCTPLNK.IPLAYER FunctionSubSet Name Measurement related to SCTP link IP layer
2.46.1 Measurement related to SCTP link IP layer (SCTPLNK.IPLAYER)

Overview
The quality of transmission links directly affects the system performance. Measurement related to SCTP link IP layer helps analyze system transmission quality so as to maintain system stability and reliability. Figure 1 shows the location of the IP Layer in the procotol. Figure 2-67 The four layers of the TCP/IP protocol suite
Issue 01 (2013-05-04)
3070
Figure 2-68 Physical bearer of the logical port for the SCTP Link
The position of SCTP links in the configuration structure is figure 2 and figure 3. Figure 2-69 Physical bearer of the SCTP Link
Issue 01 (2013-05-04)
3071
Counters
Counter ID 67194090 Counter Name VS.SCTP.IPLAYE R.TXMAXSPEED VS.SCTP.IPLAYE R.TXMINSPEED VS.SCTP.IPLAYE R.TXMEANSPEE D VS.SCTP.IPLAYE R.RXMAXSPEED VS.SCTP.IPLAYE R.RXMINSPEED VS.SCTP.IPLAYE R.RXMEANSPEE D Counter Description T7261:Maximum Transmit Rate of an SCTP Link IP Layer T7262:Minimum Transmit Rate of an SCTP Link IP Layer T7263:Average Transmit Rate of an SCTP Link IP Layer T7266:Maximum Receive Rate of an SCTP Link IP Layer T7267:Minimum Receive Rate of an SCTP Link IP Layer T7268:Average Receive Rate of an SCTP Link IP Layer Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67194091
67194092
67194093
67194094
67194095
None
2.46.1.1 Counters related to the Receive Rate or Transmit Rate of an SCTP link IP layer Counters
Counter ID 67194090 Counter Name VS.SCTP.IPLAYER.TXM AXSPEED VS.SCTP.IPLAYER.TXMI NSPEED VS.SCTP.IPLAYER.TXME ANSPEED Counter Description T7261:Maximum Transmit Rate of an SCTP Link IP Layer T7262:Minimum Transmit Rate of an SCTP Link IP Layer T7263:Average Transmit Rate of an SCTP Link IP Layer
67194091
67194092
Issue 01 (2013-05-04)
3072
Counter ID 67194093
Counter Name VS.SCTP.IPLAYER.RXM AXSPEED VS.SCTP.IPLAYER.RXMI NSPEED VS.SCTP.IPLAYER.RXME ANSPEED
Counter Description T7266:Maximum Receive Rate of an SCTP Link IP Layer T7267:Minimum Receive Rate of an SCTP Link IP Layer T7268:Average Receive Rate of an SCTP Link IP Layer
67194094
67194095
Description
These counters provide the receive rate or transmit rate of an SCTP link IP layer in the specified measurement period. The rates measured here include the spending of the IP header and the payload of the IP packet.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. The system obtains the number of bytes received and sent on the link once every 5 seconds. With this, the system obtains the maximum and the minimum number of bytes received or sent in 5 seconds, and the total number of bytes in one measurement period. A Stream Control Transmission Protocol (SCTP) link can be configured for one or multiple boards as follows: l l l l A standalone board Two standalone boards One or two pairs of active and standby boards A pair of active and standby boards and a standalone board
If an SCTP link is configured for multiple boards, the system calculates the number of bytes received from and sent to each of the boards every 5 seconds and compares to obtain the maximum and minimum numbers of bytes received from and sent to each board every 5 seconds. Then the system compares the maximum and minimum numbers obtained for all the boards to obtain the maximum and minimum numbers of bytes received and sent on the SCTP link every 5 seconds. The maximum and minimum speed is calculated with the maximum and minimum bytes in 5 seconds, and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.SCTP.IPLAYER.TXM AXSPEED Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.SCTP.IPLAYER.TXMI NSPEED WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.SCTP.IPLAYER.TXME ANSPEED WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.SCTP.IPLAYER.RXM AXSPEED WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.SCTP.IPLAYER.RXMI NSPEED WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface VS.SCTP.IPLAYER.RXME ANSPEED WRFD-050402 WRFD-050409 WRFD-050410 IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
Issue 01 (2013-05-04)
3074
2.47 Measurement of SDH Performance(SDH)

Overview
Measurement of SDH Performance indicates the transmission quality of optical port pairs between the master and slave boards. The Synchronous Digital Hierarchy (SDH) protocol defines digital transmission in terms of the frame structure, multiplexing mode, transmission rate, and coding rate of the interface.
FunctionSubSets
FunctionSubSet SDH FunctionSubSet Name SDH Measurement
2.47.1 SDH Measurement(SDH)

Overview
SDH ports are important resources of the Base Station Controller. By measuring the SDH ports, you can analyze the transmission quality and maintain the stable and secure operation of the Base Station Controller.
Counters
Counter ID 67194469 Counter Name VS.SDH.SWAP.RE ASON.REQUEST. COUNTS Counter Description T7041:Number of SDH Port Switchovers on Conditional Requests T7042:Number of SDH Port Switchovers on K byte Requests T7043:Number of SDH Port Switchovers on external Requests T7044:Number of SDH Protection Channel Failures Original Release Earlier than V900R011
67194470
VS.SDH.SWAP.RE ASON.KBYTE.CO UNTS VS.SDH.SWAP.RE ASON.EXTERNA L.COUNTS VS.SDH.FAULT.C HANNEL.PROTE CT.COUNTS
67194471
67194472
Issue 01 (2013-05-04)
3075
Counter ID 67194473
Counter Name VS.SDH.FAULT.C HANNEL.WORK. COUNTS
Counter Description T7045:Number of SDH Working Channel Failures
None
2.47.1.1 Counters Related to the Number of SDH Port Switchovers Counters

Counter ID 67194469 Counter Name VS.SDH.SWAP.REASON. REQUEST.COUNTS VS.SDH.SWAP.REASON. KBYTE.COUNTS VS.SDH.SWAP.REASON. EXTERNAL.COUNTS Counter Description T7041:Number of SDH Port Switchovers on Conditional Requests T7042:Number of SDH Port Switchovers on K byte Requests T7043:Number of SDH Port Switchovers on external Requests
67194470
67194471
Description
These counters provide the number of switchovers of an SDH port pair in the specified measurement period. SDH port pair switchover complies to the protocol ITU-T Recommendation G.841<TYPES AND CHARACTERISTICS OF SDH NETWORK PROTECTION ARCHITECTURES>.
Measurement point
The measurement is triggered when SDH optical ports are switched over.
Formula
None
Unit
None
Related Features
Counter Name VS.SDH.SWAP.REASON. REQUEST.COUNTS VS.SDH.SWAP.REASON. KBYTE.COUNTS VS.SDH.SWAP.REASON. EXTERNAL.COUNTS Feature ID MRFD-210101 MRFD-210101 MRFD-210101 Feature Name System Redundancy System Redundancy System Redundancy
2.47.1.2 Number of SDH Channel Failures Counters

Counter ID 67194472 67194473 Counter Name VS.SDH.FAULT.CHANNE L.PROTECT.COUNTS VS.SDH.FAULT.CHANNE L.WORK.COUNTS Counter Description T7044:Number of SDH Protection Channel Failures T7045:Number of SDH Working Channel Failures
Description
These counters provide the number of failures on an optical port pair in the specified measurement period. Run MML command DSP MSP to query the slot No. of the protection channel and the working channel.
Measurement point
The measurement is triggered when a fault occurs in the protection or working channel.
Formula
None
Unit
None
Related Features
Counter Name VS.SDH.FAULT.CHANNE L.PROTECT.COUNTS
Issue 01 (2013-05-04)
Feature ID MRFD-210101
Feature Name System Redundancy
3077
Counter Name VS.SDH.FAULT.CHANNE L.WORK.COUNTS
Feature ID MRFD-210101
Feature Name System Redundancy
2.48 Measurement of Trunk Group Performance(Trunk)

Overview
Measurement of Trunk Group Performance provides the transmission quality of the Trunk groups carried on boards FG2a, GOUa, FG2d, FG2c, GOUd and GOUc.
FunctionSubSets
FunctionSubSet TRUNK FunctionSubSet Name Measurement of Trunk Group Performance
2.48.1 Measurement of Trunk Group Performance(Trunk)

Overview
Trunk groups are important resources of the Base Station Controller. Therefore, the Trunk groups can be measured for the analysis of the transmission quality of the running Base Station Controller so that the stable and reliable operation of the Base Station Controller can be maintained. Trunk group belongs to the Link layer of the TCP/IP protocol suite, as figure 1 shows. Figure 2-70 The four layers of the TCP/IP protocol suite
In the configuration structure, trunks are between physical ports and logical applications, as shown in the figure 2.
Figure 2-71 Physical bearer of the TRUNK
Counters
Counter ID 73439873 Counter Name VS.TRUNK.RXBY TES VS.TRUNK.RXBY TESTOTALBAD VS.TRUNK.TXBY TES VS.TRUNK.TXBY TESTOTALBAD VS.TRUNK.RXM AXSPEED VS.TRUNK.RXMI NSPEED VS.TRUNK.RXM EANSPEED Counter Description T7840:Number of Bytes Received on the Trunk Group T7843:Bytes of Error Frames Received on the Trunk Group T7851:Number of Bytes Transmitted on the Trunk Group T7854:Bytes of Error Frames Transmitted on the Trunk Group T7863:Maximum Receive Rate of the Trunk Group T7864:Minimum Receive Rate of the Trunk Group T7865:Average Receive Rate of the Trunk Group Original Release V900R012
73439874
V900R012
73439875
V900R012
73439876
V900R012
73439881
V900R012
73439882
V900R012
73439883
V900R012
Issue 01 (2013-05-04)
3079
Counter ID 73439884
Counter Name VS.TRUNK.TXM AXSPEED VS.TRUNK.TXMI NSPEED VS.TRUNK.TXME ANSPEED VS.TRUNK.RX.E RR.RATIO VS.TRUNK.TX.ER R.RATIO VS.TRUNK.RXUC PKTS
Counter Description T7868:Maximum Transmitted Rate of the Trunk Group T7869:Minimum Transmitted Rate of the Trunk Group T7870:Average Transmitted Rate of the Trunk Group T7871:BER of the Data Received on the Trunk Group T7872:BER of the Data Transmitted on the Trunk Group T7876:Number of Unicast Frames Received on the Trunk Group T7878:Number of Multicast Frames Received on the Trunk Group T7880:Number of Broadcast Frames Received on the Trunk Group T7882:Number of CRC Error Frames with Legal Length Received on the Trunk Group T7884:Number of Frames with VLAN Flags Received on the Trunk Group T7886:Number of Unicast Frames Transmitted on the Trunk Group
73439885
V900R012
73439886
V900R012
73439887
V900R012
73439888
V900R012
73439889
V900R012
73439890
VS.TRUNK.RXM CPKTS
V900R012
73439891
VS.TRUNK.RXBC PKTS
V900R012
73439892
VS.TRUNK.RXFC SERRORS
V900R012
73439893
VS.TRUNK.RXTA GGED
V900R012
73439894
VS.TRUNK.TXUC PKTS
V900R012
Issue 01 (2013-05-04)
3080
Counter ID 73439895
Counter Name VS.TRUNK.TXM CPKTS
Counter Description T7888:Number of Multicast Frames Transmitted on the Trunk Group T7890:Number of Broadcast Frames Transmitted on the Trunk Group T7892:Number of Frames with VLAN Flags Transmitted on the Trunk Group T7894:Number of Frames Received on the Trunk Group T7896:Number of Frames Transmitted on the Trunk Group
73439896
VS.TRUNK.TXBC PKTS
V900R012
73439897
VS.TRUNK.TXTA GGED
V900R012
73439898
VS.TRUNK.RXPK TS VS.TRUNK.TXPK TS
V900R012
73439899
V900R012
None
2.48.1.1 Number of Bytes That Are Transmitted and Received by Trunk Group Counters
Counter ID 73439873 73439874 73439875 Counter Name VS.TRUNK.RXBYTES VS.TRUNK.RXBYTESTOTALBAD VS.TRUNK.TXBYTES Counter Description T7840:Number of Bytes Received on the Trunk Group T7843:Bytes of Error Frames Received on the Trunk Group T7851:Number of Bytes Transmitted on the Trunk Group T7854:Bytes of Error Frames Transmitted on the Trunk Group
73439876
VS.TRUNK.TXBYTESTOTALBAD
Issue 01 (2013-05-04)
3081
Description
These counters provide the number of bytes received or transmitted at the data link layer for the trunk group in a specified measurement period. They indicate the traffic volume at the data link layer for the trunk group in the specified measurement period. The number of bytes measured includes the MAC header, payload, and Frame Check Sequence (FCS). Normally, if the networking scenario remains unchanged, the traffic carried on the trunk group is constant at the same period every day. Also, values of these counters are constant. If the number of received and transmitted bytes decreases drastically and the number of bytes incorrectly received and transmitted increases sharply, you can infer that a transmission fault occurs. Related counters: Receive Rate and Transmit Rate of Trunk Group, BER of Data Transmitted and Received by Trunk group
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes received and transmitted on the port once every five seconds, and calculates the total number of bytes that are received, transmitted, or discarded in one measurement period.
Formula
None
Unit
byte
Related Features
Counter Name VS.TRUNK.RXBYTES VS.TRUNK.RXBYTESTOTALBAD VS.TRUNK.TXBYTES VS.TRUNK.TXBYTESTOTALBAD Feature ID MRFD-210103 MRFD-210103 MRFD-210103 MRFD-210103 Feature Name Link aggregation Link aggregation Link aggregation Link aggregation
2.48.1.2 Receive Rate and Transmit Rate of Trunk Group
Issue 01 (2013-05-04)
3082
Counters
Counter ID 73439883 73439881 73439882 73439884 Counter Name VS.TRUNK.RXMEANSPEED VS.TRUNK.RXMAXSPEED VS.TRUNK.RXMINSPEED VS.TRUNK.TXMAXSPEED VS.TRUNK.TXMINSPEED Counter Description T7865:Average Receive Rate of the Trunk Group T7863:Maximum Receive Rate of the Trunk Group T7864:Minimum Receive Rate of the Trunk Group T7868:Maximum Transmitted Rate of the Trunk Group T7869:Minimum Transmitted Rate of the Trunk Group T7870:Average Transmitted Rate of the Trunk Group
73439885
73439886
VS.TRUNK.TXMEANSPEED
Description
These counters provide the receive rate and transmit rate of the trunk group at the data link layer in a specified measurement period. They indicate the traffic volume at the data link layer for the trunk group in the specified measurement period. The number of bytes measured includes the number of bytes in the header of the MAC frame and the payload. The values of these counters are displayed as integers with decimals rounded down. For example, if the value of one of these counters is 9.9 kbit/s, the value is displayed as 9 kbit/s. Normally, if the networking scenario remains unchanged, the traffic carried on the trunk group is constant at the same period every day. Also, values of these counters are constant. If both the receive rate and transmit rate of the trunk group decrease greatly, you can infer that a transmission fault occurs. Related counters: Number of Bytes That Are Transmitted and Received by Trunk Group, BER of Data Transmitted and Received by Trunk Group
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes that are transmitted by the trunk group and the number of bytes that are received by the trunk group every five seconds. The maximum transmit rate can be obtained by dividing the maximum number of transmitted bytes in five seconds by five. The minimum transmit rate can be obtained by dividing the minimum number of transmitted bytes in five seconds by five. The maximum receive rate and the minimum receive rate can also be calculated in this method. The mean transmit rate can be calculated by dividing the total number of transmitted bytes by the measurement period. The mean receive rate can also be calculated in this method.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.TRUNK.RXMEANSPEED VS.TRUNK.RXMAXSPEED VS.TRUNK.RXMINSPEED VS.TRUNK.TXMAXSPEED VS.TRUNK.TXMINSPEED VS.TRUNK.TXMEANSPEED Feature ID MRFD-210103 MRFD-210103 MRFD-210103 MRFD-210103 MRFD-210103 MRFD-210103 Feature Name Link aggregation Link aggregation Link aggregation Link aggregation Link aggregation Link aggregation
2.48.1.3 BER of Data Transmitted and Received by Trunk Group Counters

Counter ID 73439887 73439888 Counter Name VS.TRUNK.RX.ERR.RATIO VS.TRUNK.TX.ERR.RATIO Counter Description T7871:BER of the Data Received on the Trunk Group T7872:BER of the Data Transmitted on the Trunk Group
Description
These counters provide the bit error rate (BER) the data that are transmitted and received by the trunk group in a specified measurement period. These counters indicate the BER of the trunk group. If the BER of the data that is received and transmitted by the trunk group decrease greatly, you can infer that a transmission fault occurs.
Related counters: Number of Bytes That Are Transmitted and Received by Trunk Group
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the BER of the data that is received and transmitted on the port every five seconds. The mean BER can be obtained by dividing the sum of sampled BERs by the number of sampling times.
Formula
None
Unit
%
Related Features
Counter Name VS.TRUNK.RX.ERR.RATIO VS.TRUNK.TX.ERR.RATIO Feature ID MRFD-210103 MRFD-210103 Feature Name Link aggregation Link aggregation
2.48.1.4 Number of Frames That Are Transmitted, Received, or Discarded by the Trunk Group Counters
Counter ID 73439898 73439889 Counter Name VS.TRUNK.RXPKTS VS.TRUNK.RXUCPKTS Counter Description T7894:Number of Frames Received on the Trunk Group T7876:Number of Unicast Frames Received on the Trunk Group T7878:Number of Multicast Frames Received on the Trunk Group T7880:Number of Broadcast Frames Received on the Trunk Group T7882:Number of CRC Error Frames with Legal Length Received on the Trunk Group
3085
73439890
VS.TRUNK.RXMCPKTS
73439891
VS.TRUNK.RXBCPKTS
73439892
VS.TRUNK.RXFCSERRORS
Issue 01 (2013-05-04)
Counter ID 73439893
Counter Name VS.TRUNK.RXTAGGED
Counter Description T7884:Number of Frames with VLAN Flags Received on the Trunk Group T7886:Number of Unicast Frames Transmitted on the Trunk Group T7888:Number of Multicast Frames Transmitted on the Trunk Group T7890:Number of Broadcast Frames Transmitted on the Trunk Group T7892:Number of Frames with VLAN Flags Transmitted on the Trunk Group T7896:Number of Frames Transmitted on the Trunk Group
73439894
VS.TRUNK.TXUCPKTS
73439895
VS.TRUNK.TXMCPKTS
73439896
VS.TRUNK.TXBCPKTS
73439897
VS.TRUNK.TXTAGGED
73439899
VS.TRUNK.TXPKTS
Description
These counters provide the number of frames that are transmitted, received, or discarded by the trunk group in the measurement period. They indicate the traffic volume on the trunk group. The frames measured here are MAC frames
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of frames that are received, transmitted, and discarded on the port every five seconds, calculates the total number of frames that are received, transmitted, or discarded in one measurement period.
Formula
None
Unit
frame
Issue 01 (2013-05-04)
3086
Related Features
Counter Name VS.TRUNK.RXPKTS VS.TRUNK.RXUCPKTS VS.TRUNK.RXMCPKTS VS.TRUNK.RXBCPKTS VS.TRUNK.RXFCSERRORS VS.TRUNK.RXTAGGED VS.TRUNK.TXUCPKTS VS.TRUNK.TXMCPKTS VS.TRUNK.TXBCPKTS VS.TRUNK.TXTAGGED VS.TRUNK.TXPKTS Feature ID MRFD-210103 MRFD-210103 MRFD-210103 MRFD-210103 MRFD-210103 MRFD-210103 MRFD-210103 MRFD-210103 MRFD-210103 MRFD-210103 MRFD-210103 Feature Name Link aggregation Link aggregation Link aggregation Link aggregation Link aggregation Link aggregation Link aggregation Link aggregation Link aggregation Link aggregation Link aggregation
2.49 Measurement of UNI Link Performance(UNILNK)

Overview
The UNILNK performance measurement indicates the transmission quality of a UNI link on the AEUa, AOUa or AOUc board.
FunctionSubSets
FunctionSubSet UNILNK FunctionSubSet Name Measurement related to UNI link
2.49.1 Measurement related to UNI link(UNILNK)

Overview
The quality of transmission links directly affects the system performance. The UNI link measurement helps analyze system transmission quality so as to maintain system stability and reliability. UNI Link belongs to the physical layer of the ATM reference model, as figure 1 shows.
Issue 01 (2013-05-04)
3087
In the configuration structure, UNI links are between physical ports and logical applications, as shown in the figure 2. Figure 2-73 Physical bearer of the UNI Link
Issue 01 (2013-05-04)
3088
Counters
Counter ID 67190491 Counter Name VS.UNILNK.TXC ELLS VS.UNILNK.PEA K.TXRATE VS.UNILNK.RXC ELLS VS.UNILNK.PEA K.RXRATE VS.UNILNK.RXH CSERRCELLS VS.UNILNK.RXD ROPS VS.UNI.Lnk.Mean Kbps.Rx VS.UNI.Lnk.Mean Kbps.Tx VS.UNILNK.Alloc ed.Ave.Fwd Counter Description Number of Cells Transmitted on a UNI Link Maximum Rate of Transmitting Cells on a UNI Link Number of Cells Received on a UNI Link Maximum Rate of Receiving Cells on a UNI Link Number of Error Cells Received on a UNI Link Number of Cells Discarded on a UNI Link Average Rate of Receiving Cells a UNI Link Average Rate of Transmitting Cells on a UNI Link Mean Forward Bandwidth Allocated for UNI Link Mean Backward Bandwidth Allocated for UNI Link Maximum Forward Bandwidth Allocated for UNI Link Maximum Backward Bandwidth Allocated for UNI Link Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67202977
67190490
67202976
67194049
67194050
67202915
67202916
67204196
67204197
VS.UNILNK.Alloc ed.Ave.Bwd
67193235
VS.UNILNK.Alloc ed.Max.Fwd
67193236
VS.UNILNK.Alloc ed.Max.Bwd
Issue 01 (2013-05-04)
3089
Counter ID 67193237
Counter Name VS.UNILNK.Fwd. Cong VS.UNILNK.Fwd. Cong.Dur VS.UNILNK.Bwd. Cong VS.UNILNK.Bwd. Cong.Dur
Counter Description Number of UNI Link Forward Congestions Duration of UNI Link Forward Congestions Number of UNI Link Backward Congestions Duration of UNI Link Backward Congestions
Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67193238
67193239
67193240
None
2.49.1.1 Counters Related to the Number of Cells Received or Transmitted on a UNI Link Counters
Counter ID 67190490 67190491 67194049 67194050 Counter Name VS.UNILNK.RXCELLS VS.UNILNK.TXCELLS VS.UNILNK.RXHCSERRCELLS VS.UNILNK.RXDROPS Counter Description Number of Cells Received on a UNI Link Number of Cells Transmitted on a UNI Link Number of Error Cells Received on a UNI Link Number of Cells Discarded on a UNI Link
Description
These counters provide the number of cells received or transmitted on a UNI link in the specified measurement period.
Issue 01 (2013-05-04)
3090
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of cells transmitted, received or discarded on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.UNILNK.RXCELLS VS.UNILNK.TXCELLS VS.UNILNK.RXHCSERRCELLS VS.UNILNK.RXDROPS Feature ID WRFD-05030101 WRFD-05030101 WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
2.49.1.2 Counters Related to the Receive Rate or Transmit Rate of a UNI Link Counters
Counter ID 67202976 67202977 Counter Name VS.UNILNK.PEAK.RXRA TE VS.UNILNK.PEAK.TXRA TE VS.UNI.Lnk.MeanKbps.Rx VS.UNI.Lnk.MeanKbps.Tx Counter Description Maximum Rate of Receiving Cells on a UNI Link Maximum Rate of Transmitting Cells on a UNI Link Average Rate of Receiving Cells a UNI Link Average Rate of Transmitting Cells on a UNI Link
67202915 67202916
Issue 01 (2013-05-04)
3091
Description
These counters provide the receive rate or transmit rate of a UNI link in the specified measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of bytes transmitted, received or discarded on the link once every five seconds and obtains the total number of bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.UNILNK.PEAK.RXRA TE VS.UNILNK.PEAK.TXRA TE VS.UNI.Lnk.MeanKbps.Rx VS.UNI.Lnk.MeanKbps.Tx Feature ID WRFD-05030101 WRFD-05030101 WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
2.49.1.3 Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to a UNI Link Counters
Counter ID 67204196 67204197 67193235 Counter Name VS.UNILNK.Alloced.Ave.F wd VS.UNILNK.Alloced.Ave. Bwd VS.UNILNK.Alloced.Max. Fwd Counter Description Mean Forward Bandwidth Allocated for UNI Link Mean Backward Bandwidth Allocated for UNI Link Maximum Forward Bandwidth Allocated for UNI Link
3092
Issue 01 (2013-05-04)
Counter ID 67193236
Counter Name VS.UNILNK.Alloced.Max. Bwd
Counter Description Maximum Backward Bandwidth Allocated for UNI Link
Description
These counters provide the forward bandwidth or backward bandwidth assigned to the UNI link in the specified measurement period from different perspectives.
Measurement point
In the measurement period, the system automatically takes samples on the forward bandwidth and backward bandwidth assigned to a UNI link every 15 seconds. At the end of the measurement period, the maximum forward bandwidth and the maximum backward bandwidth assigned to a UNI link in the measurement period are obtained. The mean forward bandwidth assigned to a UNI link equals to the accumulated value of the forward bandwidth at the sampling points divided by the number of sampling times. The mean backward bandwidth assigned to a UNI link equals to the accumulated value of the backward bandwidth at the sampling points divided by the number of sampling times.
Formula
None
Unit
bit/s
Related Features
Counter Name VS.UNILNK.Alloced.Ave.F wd VS.UNILNK.Alloced.Ave. Bwd VS.UNILNK.Alloced.Max. Fwd VS.UNILNK.Alloced.Max. Bwd Feature ID WRFD-05030106 WRFD-05030106 WRFD-05030106 WRFD-05030106 Feature Name Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth
2.49.1.4 Measurement of the Number of Congestions on a UNI Link

Counters
Counter ID 67193237 67193239 Counter Name VS.UNILNK.Fwd.Cong VS.UNILNK.Bwd.Cong Counter Description Number of UNI Link Forward Congestions Number of UNI Link Backward Congestions
Description
These counters provide the number of congestions on a UNI link in the measurement period.
Measurement point
This measurement is incremented by one when a UNI link changes from the non-congestion state to the congestion state (the remaining bandwidth available smaller than the congestion threshold).
Formula
None
Unit
None
Related Features
Counter Name VS.UNILNK.Fwd.Cong VS.UNILNK.Bwd.Cong Feature ID WRFD-05030106 WRFD-05030106 Feature Name Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth
2.49.1.5 Measurement of the Duration of Congestion on an UNI Link Counters

Counter ID 67193238 67193240 Counter Name VS.UNILNK.Fwd.Cong.Du r VS.UNILNK.Bwd.Cong.Du r Counter Description Duration of UNI Link Forward Congestions Duration of UNI Link Backward Congestions
Issue 01 (2013-05-04)
3094
Description
These counters provide the duration of congestion on a UNI link.
Measurement point
The measurement of a forward(backward) congestion duration starts when a forward(backward) congestion is generated on a UNI link and stops when the forward(backward) congestion is cleared. In the measurement period, the accumulated forward(backward) congestion time on the UNI link is taken as the value of this counter.
Formula
None
Unit
s
Related Features
Counter Name VS.UNILNK.Fwd.Cong.Du r VS.UNILNK.Bwd.Cong.Du r Feature ID WRFD-05030106 WRFD-05030106 Feature Name Call Admission Based on Used AAL2 Path Bandwidth Call Admission Based on Used AAL2 Path Bandwidth
2.50 Measurement of VC Cross Performance(VCACROSS)

Overview
The VCACROSS performance measurement indicates the transmission quality in the ATM layer of a VC cross connection on the AEUa , AOUa, or UOIa board.
FunctionSubSets
FunctionSubSet VCACROSS FunctionSubSet Name VCACROSS Measurement
2.50.1 VCACROSS Measurement(VCACROSS)

Overview
The VCACROSS measurement collect statistics on the traffic volume of the VC connection in both the receiving and transmitting directions to indicate the QoS in ATM layer of the connection.
Figure 1 shows the location of the ATM Layer in the procotol. Figure 2-74 ATM Reference Model
The position of the VC corss in the configuration structure is in figure 2.
Issue 01 (2013-05-04)
3096
Figure 2-75 Physical bearer of the VCL Cross
Counters
Counter ID 67194494 Counter Name VS.VCCROSS.RX BYTES VS.VCCROSS.TX BYTES VS.VCCROSS.RX CELLS VS.VCCROSS.TX CELLS VS.VCCROSS.RX HCSERRCELLS Counter Description Number of Bytes Received on a VC Cross Connection Number of Bytes Transmitted on a VC Cross Connection Number of Cells Received on a VC Cross Connection Number of Cells Transmitted on a VC Cross Connection Number of Cells with HCS(Header Check Sum) Errors Received on a VC Cross Connection Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67194495
67194496
67194497
67194498
Issue 01 (2013-05-04)
3097
Counter ID 67194499
Counter Name VS.VCCROSS.RX DROPCELLS
Counter Description Number of Cells Discarded in the Receiving Direction of a VC Cross Connection Due to the Congestion of the ATM Layer Number of Cells Discarded on a VC Cross Connection Due to the Overflow of the Receiving Buffer Number of Cells with rectifiable HEC Errors Received on a VC Cross Connection Number of Cells with Unrectifiable HEC Errors Received on a VC Cross Connection Number of Cells Discarded Because of Sending Buffer Overflow on a VC Cross Connection Number of Cells Abnormally Discarded on a VC Cross Connection Number of Overflow Cells on a VC Cross Connection Maximum Transmit Rate of a VC Cross Connection Minimum Transmit Rate of a VC Cross Connection
67194500
VS.VCCROSS.RX OVERFLOWDRO PCELLS
67194501
VS.VCCROSS.RX RECTIFIABLEHE CERRCELLS
67194502
VS.VCCROSS.RX UNRECTIFIABLE HECERRCELLS
67194503
VS.VCCROSS.TX OVERFLOWDRO PCELLS
67194504
VS.VCCROSS.TX DROPCELLS
67194505
VS.VCCROSS.TX OVERFLOWCEL LS VS.VCCROSS.TX MAXSPEED VS.VCCROSS.TX MINSPEED
67194506
67194507
Issue 01 (2013-05-04)
3098
Counter ID 67194508
Counter Name VS.VCCROSS.TX MEANSPEED VS.VCCROSS.RX MAXSPEED VS.VCCROSS.RX MINSPEED VS.VCCROSS.RX MEANSPEED
Counter Description Average Transmit Rate of a VC Cross Connection Maximum Receive Rate of a VC Cross Connection Minimum Receive Rate of a VC Cross Connection Average Receive Rate of a VC Cross Connection
Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67194509
67194510
67194511
None
2.50.1.1 Measurement of the Number of Bytes Received or Transmitted on a VCCROSS Link Counters
Counter ID 67194494 67194495 Counter Name VS.VCCROSS.RXBYTES VS.VCCROSS.TXBYTES Counter Description Number of Bytes Received on a VC Cross Connection Number of Bytes Transmitted on a VC Cross Connection
Description
These counters provide the number of bytes received or transmitted on a VC cross connection at the ATM layer in the specified measurement period.
Measurement point
Issue 01 (2013-05-04)
3099
Formula
None
Unit
byte
Related Features
Counter Name VS.VCCROSS.RXBYTES VS.VCCROSS.TXBYTES Feature ID WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
2.50.1.2 Measurement of the Number of Cells Received or Transmitted on a VCCROSS Link Counters
Counter ID 67194496 67194497 67194498 Counter Name VS.VCCROSS.RXCELLS VS.VCCROSS.TXCELLS VS.VCCROSS.RXHCSER RCELLS Counter Description Number of Cells Received on a VC Cross Connection Number of Cells Transmitted on a VC Cross Connection Number of Cells with HCS (Header Check Sum) Errors Received on a VC Cross Connection Number of Cells Discarded in the Receiving Direction of a VC Cross Connection Due to the Congestion of the ATM Layer Number of Cells Discarded on a VC Cross Connection Due to the Overflow of the Receiving Buffer Number of Cells with rectifiable HEC Errors Received on a VC Cross Connection
3100
67194499
VS.VCCROSS.RXDROPCELLS
67194500
VS.VCCROSS.RXOVERFLOWDROPCELLS
67194501
VS.VCCROSS.RXRECTIFIABLEHECERRCELLS
Issue 01 (2013-05-04)
Counter ID 67194502
Counter Name VS.VCCROSS.RXUNRECTIFIABLEHECERRCELLS
Counter Description Number of Cells with Unrectifiable HEC Errors Received on a VC Cross Connection Number of Cells Discarded Because of Sending Buffer Overflow on a VC Cross Connection Number of Cells Abnormally Discarded on a VC Cross Connection Number of Overflow Cells on a VC Cross Connection
67194503
VS.VCCROSS.TXOVERFLOWDROPCELLS
67194504
VS.VCCROSS.TXDROPCELLS VS.VCCROSS.TXOVERFLOWCELLS
67194505
Description
These counters provide the number of cells received or transmitted on a VC cross connection at the ATM layer in the specified measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains the number of cells transmitted, received or discarded on the link once every five seconds and obtains the total number of one measurement period.
Formula
None
Unit
None
Related Features
Counter Name VS.VCCROSS.RXCELLS VS.VCCROSS.TXCELLS VS.VCCROSS.RXHCSER RCELLS Feature ID WRFD-05030101 WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
Issue 01 (2013-05-04)
3101
Counter Name VS.VCCROSS.RXDROPCELLS VS.VCCROSS.RXOVERFLOWDROPCELLS VS.VCCROSS.RXRECTIFIABLEHECERRCELLS VS.VCCROSS.RXUNRECTIFIABLEHECERRCELLS VS.VCCROSS.TXOVERFLOWDROPCELLS VS.VCCROSS.TXDROPCELLS VS.VCCROSS.TXOVERFLOWCELLS
Feature ID WRFD-05030101 WRFD-05030101 WRFD-05030101 WRFD-05030101 WRFD-05030101 WRFD-05030101 WRFD-05030101
Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
2.50.1.3 Counters Related to the Receive Rate or Transmit Rate of a VC Cross Connection Counters
Counter ID 67194506 67194507 67194508 67194509 67194510 67194511 Counter Name VS.VCCROSS.TXMAXSPEED VS.VCCROSS.TXMINSPEED VS.VCCROSS.TXMEANSPEED VS.VCCROSS.RXMAXSPEED VS.VCCROSS.RXMINSPEED VS.VCCROSS.RXMEANSPEED Counter Description Maximum Transmit Rate of a VC Cross Connection Minimum Transmit Rate of a VC Cross Connection Average Transmit Rate of a VC Cross Connection Maximum Receive Rate of a VC Cross Connection Minimum Receive Rate of a VC Cross Connection Average Receive Rate of a VC Cross Connection
Description
These counters provide the receive rate or transmit rate of a VC cross connection at the ATM layer in the specified measurement period.
Measurement point
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.VCCROSS.TXMAXSPEED VS.VCCROSS.TXMINSPEED VS.VCCROSS.TXMEANSPEED VS.VCCROSS.RXMAXSPEED VS.VCCROSS.RXMINSPEED VS.VCCROSS.RXMEANSPEED Feature ID WRFD-05030101 WRFD-05030101 WRFD-05030101 WRFD-05030101 WRFD-05030101 WRFD-05030101 Feature Name ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface ATM over E1T1 on Iub Interface
Issue 01 (2013-05-04)
3103
3 Hardware Platform Related Measurement
Hardware Platform Related Measurement
About This Chapter

The following measurements are Hardware Platform Related Measurement. 3.1 Measurement of DPU Performance(DPU) 3.2 Measurement of Inter-Subrack Traffic Performance(FRAME_FLUX) 3.3 Measurement of GCU Performance(GCU) 3.4 Measurement of INT Performance(INT) 3.5 Measurement of NIU DSP Performance(NDSP) 3.6 Measurement of NIU Performance(NIU) 3.7 Measurement of SCU Performance(SCU) 3.8 Measurement of XPU Performance(XPU)
Issue 01 (2013-05-04)
3104
3.1 Measurement of DPU Performance(DPU)

Overview
DPU performance measurement indicates the operating status, such as the CPU usage, of a single DPU in a subrack.
FunctionSubSets
FunctionSubSet DPU FunctionSubSet Name DPU Measurement
3.1.1 DPU Measurement(DPU)

Overview
DPU measurement indicates the operating state, such as the CPU usage, of a single DPU system.
Counters
Counter ID 67194743 Counter Name VS.DPU.CPULOA D.MAX VS.DPU.CPULOA D.MEAN VS.DPU.CPULOA D.OVER Counter Description HR9760:Maximum CPU Usage of the DPU AR9760:Average CPU Usage of the DPU TR9760a:Rate of the Period in Which the CPU Usage of the DPU Exceeds the Alarm Threshold TR9760b:Rate of the Period in Which the CPU Usage of the DPU is Lower than the Alarm Threshold Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67204463
67204464
67204465
VS.DPU.CPULOA D.LESS
None
3.1.1.1 Maximum CPU Usage of the DPU Counters

Counter ID 67194743 Counter Name VS.DPU.CPULOAD.MAX Counter Description HR9760:Maximum CPU Usage of the DPU
Description
This counter provides the maximum CPU usage of the DPU in a measurement period. It indicates the load and operating performance of the CPU on the DPU in the measurement period.
Measurement point
The CPU usage of the DPU is sampled every second in the measurement period. Then, the maximum usage is taken as the value of this counter.
Formula
None
Unit
%
Related Features
Counter Name VS.DPU.CPULOAD.MAX Feature ID WRFD-040100 Feature Name Flow Control
3.1.1.2 Average CPU Usage of the DPU Counters

Counter ID 67204463 Counter Name VS.DPU.CPULOAD.MEA N Counter Description AR9760:Average CPU Usage of the DPU
Description
This counter provides the average CPU usage of the DPU in a measurement period.
Measurement point
The CPU usage of the DPU is sampled and accumulated every second in the measurement period. Then, the average CPU usage of the DPU is the accumulated value divided by the number of sampling times.
Formula
None
Unit
%
Related Features
Counter Name VS.DPU.CPULOAD.MEA N Feature ID WRFD-040100 Feature Name Flow Control
3.1.1.3 Rate of the Period in Which the CPU Usage of the DPU Exceeds the Alarm Threshold Counters
Counter ID 67204464 Counter Name VS.DPU.CPULOAD.OVER Counter Description TR9760a:Rate of the Period in Which the CPU Usage of the DPU Exceeds the Alarm Threshold
Description
This counter provides the rate of the period in which the CPU usage of the DPU exceeds the alarm threshold to the entire measurement period. It indicates the load and operating performance of the CPU on the DPU in the measurement period.
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the DPU exceeds the alarm threshold is divided by the number of sampling times for a rate. The sampling period is 1s.
Formula
None
Unit
%
Related Features
Counter Name VS.DPU.CPULOAD.OVER Feature ID WRFD-040100 Feature Name Flow Control
3.1.1.4 Rate of the Period in Which the CPU Usage of the DPU Is Lower Than the Alarm Threshold Counters
Counter ID 67204465 Counter Name VS.DPU.CPULOAD.LESS Counter Description TR9760b:Rate of the Period in Which the CPU Usage of the DPU is Lower than the Alarm Threshold
Description
This counter provides the rate of the sampling times in which the CPU usage of the DPU is lower than the alarm threshold to the sampling times in the entire measurement period. It indicates the load and operating performance of the CPU on the DPU in the measurement period.
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the DPU is lower than the alarm threshold is divided by the number of sampling times for a rate. The sampling period is 1s.
Formula
None
Unit
%
Related Features
Counter Name VS.DPU.CPULOAD.LESS Feature ID WRFD-040100 Feature Name Flow Control
Issue 01 (2013-05-04)
3108
3.2 Measurement of Inter-Subrack Traffic Performance (FRAME_FLUX)

Overview
The FRAME_FLUX measurement object indicates the inter-subrack traffic.
FunctionSubSets
FunctionSubSet FRAME.FLUX FunctionSubSet Name Inter-Subrack Traffic Measurement
3.2.1 Inter-Subrack Traffic Measurement(FRAME.FLUX)

Overview
The FRAME_FLUX function subset indicates the traffic between SCU boards in two subracks.
Counters
Counter ID 73436939 Counter Name VS.Frame.Flux.Pea k.TxRate VS.Frame.Flux.Me an.TxRate VS.Frame.Flux.Dr opPackets VS.Frame.Flux.Tx Packets Counter Description HR9732a:Peak Inter-Subrack Transmitting Traffic AR9732a:Average Inter-Subrack Transmitting Traffic R9732a:Number of Discarded InterSubrack Packets R9732b:Number of Sent Inter-Subrack Packets Original Release V900R014
73436941
V900R014
73441493
V900R014
73441494
V900R014
None
3.2.1.1 Peak Inter-Subrack Transmitting Traffic

Counters
Counter ID 73436939 Counter Name VS.Frame.Flux.Peak.TxRate Counter Description HR9732a:Peak InterSubrack Transmitting Traffic
Description
This counter provides the maximum number of packets sent from the transmission from the source subrack to the target subrack in 5 seconds in a measurement period. It reflects the intersubrack traffic volume and quality in a measurement period.
Measurement point
The BSC samples the number of packets and their bytes sent from the SCU boards in the source subrack to the SCU boards in the target subrack every 5 seconds. At the end of a measurement period, the maximum sampled value is taken as the value of this counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.Frame.Flux.Peak.TxRate Feature ID MRFD-210104 Feature Name BSC/RNC Resource Sharing
3.2.1.2 Average Inter-Subrack Transmitting Traffic Counters

Counter ID 73436941 Counter Name VS.Frame.Flux.Mean.TxRat e Counter Description AR9732a:Average InterSubrack Transmitting Traffic
Description
This counter provides the average number of packets sent from the source subrack to the target subrack in 5 seconds in a measurement period. It reflects the inter-subrack traffic volume and quality in a measurement period.
Measurement point
The BSC samples the number of packets and their bytes sent from the SCU boards in the source subrack to the SCU boards in the target subrack every 5 seconds and accumulates the sampled values. At the end of a measurement period, the value of this counter is calculated by dividing the accumulated value by the number of sampling times.
Formula
None
Unit
kbit/s
Related Features
Counter Name VS.Frame.Flux.Mean.TxRat e Feature ID MRFD-210104 Feature Name BSC/RNC Resource Sharing
3.2.1.3 Number of Discarded Inter-Subrack Packets Counters

Counter ID 73441493 Counter Name VS.Frame.Flux.DropPackets Counter Description R9732a:Number of Discarded Inter-Subrack Packets
Description
This counter provides the number of packets lost during transmission from the source subrack to the target subrack in a measurement period. It reflects the inter-subrack traffic volume and quality in a measurement period.
Measurement point
The BSC samples the number of packets lost during transmission from the SCU boards in the source subrack to the SCU boards in the target subrack every 5 seconds and accumulates the sampled values. At the end of a measurement period, the accumulated value is taken as the value of this counter.
Formula
None
Unit
packet
Related Features
Counter Name VS.Frame.Flux.DropPackets Feature ID MRFD-210104 Feature Name BSC/RNC Resource Sharing
3.2.1.4 Number of Sent Inter-Subrack Packets Counters

Counter ID 73441494 Counter Name VS.Frame.Flux.TxPackets Counter Description R9732b:Number of Sent Inter-Subrack Packets
Description
This counter provides the number of packets sent from the source subrack to the target subrack in a measurement period. It reflects the inter-subrack traffic volume and quality in a measurement period.
Measurement point
The BSC samples the number of packets sent from the SCU boards in the source subrack to the SCU boards in the target subrack every 5 seconds and accumulates the sampled values. At the end of a measurement period, the accumulated value is taken as the value of this counter.
Formula
None
Unit
packet
Related Features
Counter Name VS.Frame.Flux.TxPackets Feature ID MRFD-210104 Feature Name BSC/RNC Resource Sharing
Issue 01 (2013-05-04)
3112
3.3 Measurement of GCU Performance(GCU)

Overview
GCU performance measurement indicates the operating status, such as the CPU usage, of a single GCU or GCG in a subrack.
FunctionSubSets
FunctionSubSet GCU FunctionSubSet Name GCU Measurement
3.3.1 GCU Measurement(GCU)

Overview
GCU measurement indicates the operating state, such as the CPU usage, of a single GCU system.
Counters
Counter ID 67194447 Counter Name VS.GCU.CPULOA D.MAX VS.GCU.CPULOA D.MEAN VS.GCU.CPULOA D.OVER Counter Description HR9750:Maximum CPU Usage of the GCU AR9750:Average CPU Usage of the GCU TR9750a:Rate of the Period in Which the CPU Usage of the GCU Exceeds the Alarm Threshold TR9750b:Rate of the Period in Which the CPU Usage of the GCU is Lower than the Alarm Threshold Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67204336
67204337
67204338
VS.GCU.CPULOA D.LESS
None
3.3.1.1 Maximum CPU Usage of the GCU Counters

Counter ID 67194447 Counter Name VS.GCU.CPULOAD.MAX Counter Description HR9750:Maximum CPU Usage of the GCU
Description
This counter provides the maximum CPU usage of the GCU in a measurement period. It indicates the load and operating performance of the CPU on the GCU in the measurement period.
Measurement point
The CPU usage of the GCU is sampled every second in the measurement period. Then, the maximum usage is taken as the value of this counter.
Formula
None
Unit
%
Related Features
Counter Name VS.GCU.CPULOAD.MAX Feature ID WRFD-040100 Feature Name Flow Control
3.3.1.2 Average CPU Usage of the GCU Counters

Counter ID 67204336 Counter Name VS.GCU.CPULOAD.MEA N Counter Description AR9750:Average CPU Usage of the GCU
Description
This counter provides the average CPU usage of the GCU in a measurement period.
Measurement point
The CPU usage of the GCU is sampled and accumulated every second in the measurement period. Then, the average CPU usage of the GCU is the accumulated value divided by the number of sampling times.
Formula
None
Unit
%
Related Features
Counter Name VS.GCU.CPULOAD.MEA N Feature ID WRFD-040100 Feature Name Flow Control
3.3.1.3 Rate of the Period in Which the CPU Usage of the GCU Exceeds the Alarm Threshold Counters
Counter ID 67204337 Counter Name VS.GCU.CPULOAD.OVE R Counter Description TR9750a:Rate of the Period in Which the CPU Usage of the GCU Exceeds the Alarm Threshold
Description
This counter provides the rate of the period in which the CPU usage of the GCU exceeds the alarm threshold to the entire measurement period. It indicates the load and operating performance of the CPU on the GCU in the measurement period.
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the GCU exceeds the alarm threshold is divided by the number of sampling times for a rate. The sampling period is 1s.
Formula
None
Unit
%
Related Features
Counter Name VS.GCU.CPULOAD.OVE R Feature ID WRFD-040100 Feature Name Flow Control
3.3.1.4 Rate of the Period in Which the CPU Usage of the GCU Is Lower Than the Alarm Threshold Counters
Counter ID 67204338 Counter Name VS.GCU.CPULOAD.LESS Counter Description TR9750b:Rate of the Period in Which the CPU Usage of the GCU is Lower than the Alarm Threshold
Description
This counter provides the rate of the sampling times in which the CPU usage of the GCU is lower than the alarm threshold to the sampling times in the entire measurement period. It indicates the load and operating performance of the CPU on the GCU in the measurement period.
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the GCU is lower than the alarm threshold is divided by the number of sampling times for a rate. The sampling period is 1s.
Formula
None
Unit
%
Related Features
Counter Name VS.GCU.CPULOAD.LESS
Issue 01 (2013-05-04)
Feature Name Flow Control

3116
3.4 Measurement of INT Performance(INT)

Overview
INT performance measurement indicates the operating status, such as the CPU usage, of a single INT(Interface board) system in a subrack.
FunctionSubSets
FunctionSubSet INT FunctionSubSet Name Measurement related to INT
3.4.1 Measurement related to INT(INT)

Overview
INT measurement indicates the operating state, such as the CPU usage, of a single INT system.
Counters
Counter ID 73403674 Counter Name VS.INT.CPULOA D.MAX VS.INT.CPULOA D.MEAN VS.INT.CPULOA D.OVER Counter Description HR9700:Maximum CPU Usage of the INT AR9700:Average CPU Usage of the INT TR9700a:Rate of the Period in Which the CPU Usage of the INT Exceeds the Alarm Threshold TR9700b:Rate of the Period in Which the CPU Usage of the INT is Lower than the Alarm Threshold HR9705a:Maximum Forwarding Ratio of Interface Boards Original Release V900R011
73415843
V900R011
73415844
V900R011
73415845
VS.INT.CPULOA D.LESS
V900R011
73422157
VS.INT.TRANSLO AD.RATIO.MAX
V900R012
Issue 01 (2013-05-04)
3117
Counter ID 73440118
Counter Name VS.INT.TRANSLO AD.RATIO.MEAN VS.INT.CFG.INTE RWORKING.NU M VS.INT.CFG.INTE RWORKING.FAI L.NUM
Counter Description AR9705a:Average Forwarding Ratio of Interface Boards T6900:Number of Call Establishment Attempts on an Interface Board T6920:Number of Call Establishment Failures on an Interface Board
73423829
V900R013
73423830
V900R013
None
3.4.1.1 Maximum CPU usage of the INT Counters

Counter ID 73403674 Counter Name VS.INT.CPULOAD.MAX Counter Description HR9700:Maximum CPU Usage of the INT
Description
This counter provides the maximum CPU usage of the INT in a measurement period. It indicates the load and operating performance of the CPU on the INT in the measurement period.
Measurement point
The CPU usage of the INT is sampled every second in the measurement period. Then, the maximum usage is taken as the value of this counter.
Formula
None
Unit
%
Related Features
Counter Name VS.INT.CPULOAD.MAX Feature ID WRFD-040100 Feature Name Flow Control
3.4.1.2 Average CPU Usage of the INT Counters

Counter ID 73415843 Counter Name VS.INT.CPULOAD.MEAN Counter Description AR9700:Average CPU Usage of the INT
Description
This counter provides the average CPU usage of the INT in a measurement period. It indicates the load and operating performance of the CPU on the INT in the measurement period.
Measurement point
The CPU usage of the INT is sampled and accumulated every second in the measurement period. Then, the average CPU usage of the INT is the accumulated value divided by the number of sampling times.
Formula
None
Unit
%
Related Features
Counter Name VS.INT.CPULOAD.MEAN Feature ID WRFD-040100 Feature Name Flow Control
3.4.1.3 Rate of the Period in Which the CPU Usage of the INT Exceeds the Alarm Threshold
Issue 01 (2013-05-04)
3119
Counters
Counter ID 73415844 Counter Name VS.INT.CPULOAD.OVER Counter Description TR9700a:Rate of the Period in Which the CPU Usage of the INT Exceeds the Alarm Threshold
Description
This counter provides the rate of the period in which the CPU usage of the INT exceeds the alarm threshold to the entire measurement period. It indicates the load and operating performance of the CPU on the INT in the measurement period.
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the INT exceeds the alarm threshold is divided by the number of sampling times for a rate. The sampling period is 1s.
Formula
None
Unit
%
Related Features
Counter Name VS.INT.CPULOAD.OVER Feature ID WRFD-040100 Feature Name Flow Control
3.4.1.4 Rate of the Period in Which the CPU Usage of the INT Is Lower Than the Alarm Threshold Counters
Counter ID 73415845 Counter Name VS.INT.CPULOAD.LESS Counter Description TR9700b:Rate of the Period in Which the CPU Usage of the INT is Lower than the Alarm Threshold
Issue 01 (2013-05-04)
3120
Description
This counter provides the rate of the sampling times in which the CPU usage of the INT is lower than the alarm threshold to the sampling times in the entire measurement period. It indicates the load and operating performance of the CPU on the INT in the measurement period.
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the INT is lower than the alarm threshold is divided by the number of sampling times for a rate. The sampling period is 1s.
Formula
None
Unit
%
Related Features
Counter Name VS.INT.CPULOAD.LESS Feature ID WRFD-040100 Feature Name Flow Control
3.4.1.5 Maximum Forwarding Ratio of Interface Boards Counters

Counter ID 73422157 Counter Name VS.INT.TRANSLOAD.RA TIO.MAX Counter Description HR9705a:Maximum Forwarding Ratio of Interface Boards
Description
This counter provides the maximum forwarding ratio of interface boards in a measurement period. Forwarding ratio refers to the ratio of the actual forwarding rate to the maximum designed forwarding rate of interface boards. It indicates the traffic load and operating quality of the interface boards in the measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. At the end of the measurement period, the maximum forwarding ratio is obtained.
Formula
None
Unit
%
Related Features
Counter Name VS.INT.TRANSLOAD.RA TIO.MAX Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
3.4.1.6 Average Forwarding Ratio of Interface Boards Counters

Counter ID 73440118 Counter Name VS.INT.TRANSLOAD.RA TIO.MEAN Counter Description AR9705a:Average Forwarding Ratio of Interface Boards
Description
This counter provides the average forwarding ratio of interface boards in a measurement period. Forwarding ratio refers to the ratio of the actual forwarding rate to the maximum designed forwarding rate of interface boards. It indicates the traffic load and operating quality of the interface boards in the measurement period.
Measurement point
Samples are taken every five seconds in the specified measurement period. At the end of the measurement period, the accumulated sampling value is divided by the number of samples to obtain the average forwarding ratio.
Formula
None
Unit
%
Related Features
Counter Name VS.INT.TRANSLOAD.RA TIO.MEAN Feature ID WRFD-050402 WRFD-050409 WRFD-050410 Feature Name IP Transmission Introduction on Iub Interface IP Transmission Introduction on Iu Interface IP Transmission Introduction on Iur Interface
3.4.1.7 Number of Call Establishment Attempts And Number of Call Establishment Failures on an Interface Board Counters
Counter ID 73423829 Counter Name VS.INT.CFG.INTERWOR KING.NUM VS.INT.CFG.INTERWOR KING.FAIL.NUM Counter Description T6900:Number of Call Establishment Attempts on an Interface Board T6920:Number of Call Establishment Failures on an Interface Board
73423830
Description
This counter provides the number of call establishment attempts and the number of call establishment failures on an Interface Board.
Measurement point
The BSC6900 samples the number of call establishment attempts and the number of call establishment failures on an Interface Board every 10 seconds. At the end of each measurement period, the accumulated sampling value is taken as the value of this counter.
Formula
None
Unit
None
Issue 01 (2013-05-04)
3123
Related Features
Counter Name VS.INT.CFG.INTERWOR KING.NUM VS.INT.CFG.INTERWOR KING.FAIL.NUM Feature ID WRFD-040100 WRFD-040100 Feature Name Flow Control Flow Control
3.5 Measurement of NIU DSP Performance(NDSP)

Overview
NDSP performance measurement indicates the operating status, such as the CPU usage, of each DSP on the NIU board.
FunctionSubSets
FunctionSubSet NDSP FunctionSubSet Name Measurement related to NIU DSP performance
3.5.1 Measurement related to NIU DSP performance(NDSP)

Overview
NDSP is the core for the NIU. During the system operation, the NDSP usage can be measured for the analysis of the load of Packet Inspection(PI) function.
Counters
Counter ID 73424564 Counter Name VS.NDSP.UsagePeak VS.NDSP.UsageAv g Counter Description R9901:Maximum CPU Usage of the NIU DSP R9904:Average CPU Usage of the NIU DSP Original Release V900R014
73441424
V900R014
None
3.5.1.1 Maximum CPU Usage of the NIU DSP Counters

Counter ID 73424564 Counter Name VS.NDSP.UsagePeak Counter Description R9901:Maximum CPU Usage of the NIU DSP
Description
This counter provides the maximum CPU usage of the NIU DSP in a measurement period. It indicates the load and operating performance of the NIU DSP in the measurement period.
Measurement point
The CPU usage of the NIU DSP is sampled every five seconds in the measurement period. Then, the maximum CPU usage is taken as the value of this counter.
Formula
None
Unit
%
Related Features
Counter Name VS.NDSP.UsagePeak Feature ID WRFD-020132 WRFD-020133 Feature Name Web browsing acceleration P2P Downloading Rate Control during Busy Hour
3.5.1.2 Average CPU Usage of the NIU DSP Counters

Counter ID 73441424 Counter Name VS.NDSP.UsageAvg Counter Description R9904:Average CPU Usage of the NIU DSP
Counter ID 73424566 73424565
Counter Name VS.NDSP.DSPUsageAvgCount VS.NDSP.DSPUsageAvgValue
Counter Description R9903:Number of mean NIU DSP Usage Reports R9902:Mean Usage in 20 Seconds for NIU DSP
Description
This counter provides the average CPU usage of the NIU DSP in a measurement period.It indicates the load and operating performance of the NIU DSP in the measurement period.
Measurement point
The CPU usage of the NIU DSP is sampled and accumulated every five seconds in the measurement period. Then, the average CPU usage of the NIU DSP is the accumulated value divided by the number of sampling times.
Formula
VS.NDSP.UsageAvg = [VS.NDSP.DSPUsageAvgValue]/[VS.NDSP.DSPUsageAvgCount]
Unit
%
Related Features
Counter Name VS.NDSP.UsageAvg Feature ID WRFD-020132 WRFD-020133 Feature Name Web browsing acceleration P2P Downloading Rate Control during Busy Hour
3.6 Measurement of NIU Performance(NIU)

Overview
NIU performance measurement indicates the operating status, such as the CPU usage, of a single NIU in a subrack.
FunctionSubSets
FunctionSubSet NIU FunctionSubSet Name NIU Measurement
Issue 01 (2013-05-04)
3126
3.6.1 NIU Measurement(NIU)

Overview
NIU measurement indicates the operating state, such as the CPU usage, of a single NIU system.
Counters
Counter ID 73424737 Counter Name VS.NIU.CPULOA D.MAX VS.NIU.CPULOA D.MEAN Counter Description HR9790:Maximum CPU Usage of the NIU AR9790:Average CPU Usage of the NIU Original Release V900R014
73441495
V900R014
None
3.6.1.1 Maximum CPU Usage of the NIU Counters

Counter ID 73424737 Counter Name VS.NIU.CPULOAD.MAX Counter Description HR9790:Maximum CPU Usage of the NIU
Description
This counter provides the maximum CPU usage of the NIU in a measurement period. It indicates the load and operating performance of the CPU on the NIU in the measurement period.
Measurement point
The CPU usage of the NIU is sampled every second in the measurement period. Then, the maximum usage is taken as the value of this counter.
Formula
None
Unit
%
Related Features
Counter Name VS.NIU.CPULOAD.MAX Feature ID WRFD-020132 WRFD-020133 Feature Name Web browsing acceleration P2P Downloading Rate Control during Busy Hour
3.6.1.2 Average CPU Usage of the NIU Counters

Counter ID 73441495 Counter Name VS.NIU.CPULOAD.MEAN Counter Description AR9790:Average CPU Usage of the NIU
Description
This counter provides the average CPU usage of the NIU in a measurement period.
Measurement point
The CPU usage of the NIU is sampled and accumulated every second in the measurement period. Then, the average CPU usage of the NIU is the accumulated value divided by the number of sampling times.
Formula
None
Unit
%
Related Features
Counter Name VS.NIU.CPULOAD.MEAN Feature ID WRFD-020132 WRFD-020133 Feature Name Web browsing acceleration P2P Downloading Rate Control during Busy Hour
Issue 01 (2013-05-04)
3128
3.7 Measurement of SCU Performance(SCU)

Overview
SCU performance measurement indicates the operating status, such as the CPU usage, of a single SCU in a subrack.
FunctionSubSets
FunctionSubSet SCU FunctionSubSet Name SCU Measurement
3.7.1 SCU Measurement(SCU)

Overview
SCU measurement indicates the operating state, such as the CPU usage, of a single SCU system.
Counters
Counter ID 67194751 Counter Name VS.SCU.CPULOA D.MAX VS.SCU.CPULOA D.MEAN VS.SCU.CPULOA D.OVER Counter Description HR9730:Maximum CPU Usage of the SCU AR9730:Average CPU Usage of the SCU TR9730a:Rate of the Period in Which the CPU Usage of the SCU Exceeds the Alarm Threshold TR9730b:Rate of the Period in Which the CPU Usage of the SCU is Lower than the Alarm Threshold Original Release Earlier than V900R011 Earlier than V900R011 Earlier than V900R011
67204467
67204468
67204469
VS.SCU.CPULOA D.LESS
None
3.7.1.1 Maximum CPU Usage of the SCU Counters

Counter ID 67194751 Counter Name VS.SCU.CPULOAD.MAX Counter Description HR9730:Maximum CPU Usage of the SCU
Description
This counter provides the maximum CPU usage of the SCU in a measurement period. It indicates the load and operating performance of the CPU on the SCU in the measurement period.
Measurement point
The CPU usage of the SCU is sampled every second in the measurement period. Then, the maximum usage is taken as the value of this counter.
Formula
None
Unit
%
Related Features
Counter Name VS.SCU.CPULOAD.MAX Feature ID WRFD-040100 Feature Name Flow Control
3.7.1.2 Average CPU Usage of the SCU Counters

Counter ID 67204467 Counter Name VS.SCU.CPULOAD.MEA N Counter Description AR9730:Average CPU Usage of the SCU
Description
This counter provides the average CPU usage of the SCU in a measurement period.
Measurement point
The CPU usage of the SCU is sampled and accumulated every second in the measurement period. Then, the average CPU usage of the SCU is the accumulated value divided by the number of sampling times.
Formula
None
Unit
%
Related Features
Counter Name VS.SCU.CPULOAD.MEA N Feature ID WRFD-040100 Feature Name Flow Control
3.7.1.3 Rate of the Period in Which the CPU Usage of the SCU Exceeds the Alarm Threshold Counters
Counter ID 67204468 Counter Name VS.SCU.CPULOAD.OVER Counter Description TR9730a:Rate of the Period in Which the CPU Usage of the SCU Exceeds the Alarm Threshold
Description
This counter provides the rate of the period in which the CPU usage of the SCU exceeds the alarm threshold to the entire measurement period. It indicates the load and operating performance of the CPU on the SCU in the measurement period.
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the SCU exceeds the alarm threshold is divided by the number of sampling times for a rate. The sampling period is 1s.
Formula
None
Unit
%
Related Features
Counter Name VS.SCU.CPULOAD.OVER Feature ID WRFD-040100 Feature Name Flow Control
3.7.1.4 Rate of the Period in Which the CPU Usage of the SCU Is Lower Than the Alarm Threshold Counters
Counter ID 67204469 Counter Name VS.SCU.CPULOAD.LESS Counter Description TR9730b:Rate of the Period in Which the CPU Usage of the SCU is Lower than the Alarm Threshold
Description
This counter provides the rate of the sampling times in which the CPU usage of the SCU is lower than the alarm threshold to the sampling times in the entire measurement period. It indicates the load and operating performance of the CPU on the SCU in the measurement period.
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the SCU is lower than the alarm threshold is divided by the number of sampling times for a rate. The sampling period is 1s.
Formula
None
Unit
%
Related Features
Counter Name VS.SCU.CPULOAD.LESS Feature ID WRFD-040100 Feature Name Flow Control
Issue 01 (2013-05-04)
3132
3.8 Measurement of XPU Performance(XPU)

Overview
XPU performance measurement indicates the operating status of a single XPU in a subrack. In the GSM Mode, the counters related to the service processing subsystems of the XPU board. In the UMTS Mode, the counters related to the service processing subsystems of the SPU board. In the BSC6900, the counters related to the service processing subsystems of the GSM and the UMTS are unified. The measurement units contain the CPU usage.
FunctionSubSets
FunctionSubSet XPU FunctionSubSet Name XPU Measurement
3.8.1 XPU Measurement(XPU)

Overview
XPU measurement indicates the operating status, such as the CPU usage, packet usage, of a single XPU.
Counters
Counter ID 73390062 Counter Name VS.XPU.CPULOA D.MAX VS.XPU.CPULOA D.MEAN VS.XPU.CPULOA D.OVER Counter Description HR9780:Maximum CPU Usage of the XPU AR9780:Average CPU Usage of the XPU TR9780a:Rate of the Period in Which the CPU Usage of the XPU Exceeds the Alarm Threshold TR9780b:Rate of the Period in Which the CPU Usage of the XPU is Lower than the Alarm Threshold Original Release V900R011
73415210
V900R011
73415211
V900R011
73415212
VS.XPU.CPULOA D.LESS
V900R011
Issue 01 (2013-05-04)
3133
Counter ID 73390070
Counter Name VS.XPU.MSGLOA D.MAX VS.XPU.MSGLOA D.MEAN
Counter Description HR9782:Maximum Packet Usage of the XPU AR9782:Average Packet Usage of the XPU
73415214
None
3.8.1.1 Maximum CPU Usage of the XPU Counters

Counter ID 73390062 Counter Name VS.XPU.CPULOAD.MAX Counter Description HR9780:Maximum CPU Usage of the XPU
Description
This counter provides the maximum CPU usage of the XPU in a measurement period. It indicates the operating load and performance of the CPU on the XPU in the measurement period.
Measurement point
The CPU usage of the XPU is sampled every second in the measurement period. Then, the maximum usage is taken as the value of this counter.
Formula
None
Unit
%
Related Features
Counter Name VS.XPU.CPULOAD.MAX Feature ID WRFD-040100 Feature Name Flow Control
Issue 01 (2013-05-04)
3134
3.8.1.2 Average CPU Usage of the XPU Counters

Counter ID 73415210 Counter Name VS.XPU.CPULOAD.MEA N Counter Description AR9780:Average CPU Usage of the XPU
Description
This counter provides the average CPU usage of each XPU subsystem. It indicates the load and operating performance of the CPU on the XPU subsystem in the measurement period.
Measurement point
The CPU usage of the XPU subsystem is sampled and accumulated every second in the measurement period. Then, the average CPU usage of the XPU subsystem is the accumulated value divided by the number of sampling times.
Formula
None
Unit
%
Related Features
Counter Name VS.XPU.CPULOAD.MEA N Feature ID WRFD-040100 Feature Name Flow Control
3.8.1.3 Rate of the Period in Which the CPU Usage of the XPU Exceeds the Alarm Threshold Counters
Counter ID 73415211 Counter Name VS.XPU.CPULOAD.OVER Counter Description TR9780a:Rate of the Period in Which the CPU Usage of the XPU Exceeds the Alarm Threshold
Issue 01 (2013-05-04)
3135
Description
This counter provides the rate of the period in which the CPU usage of the XPU exceeds the alarm threshold to the entire measurement period. It indicates the load and operating performance of the CPU on the XPU in the measurement period.
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the XPU exceeds the alarm threshold is divided by the number of sampling times for a rate. The sampling period is 1s.
Formula
None
Unit
%
Related Features
Counter Name VS.XPU.CPULOAD.OVER Feature ID WRFD-040100 Feature Name Flow Control
3.8.1.4 Rate of the Period in Which the CPU Usage of the XPU Is Lower Than the Alarm Threshold Counters
Counter ID 73415212 Counter Name VS.XPU.CPULOAD.LESS Counter Description TR9780b:Rate of the Period in Which the CPU Usage of the XPU is Lower than the Alarm Threshold
Description
This counter provides the rate of the sampling times in which the CPU usage of the XPU is lower than the alarm threshold to the sampling times in the entire measurement period. It indicates the load and operating performance of the CPU on the XPU in the measurement period.
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the XPU is lower than the alarm threshold is divided by the number of sampling times for a rate. The sampling period is 1s.
Formula
None
Unit
%
Related Features
Counter Name VS.XPU.CPULOAD.LESS Feature ID WRFD-040100 Feature Name Flow Control
3.8.1.5 Maximum Packet Usage of the XPU Counters

Counter ID 73390070 Counter Name VS.XPU.MSGLOAD.MAX Counter Description HR9782:Maximum Packet Usage of the XPU
Description
This counter provides the maximum packet usage of the XPU in a measurement period. It indicates the packet traffic of the XPU in the specified period.
Measurement point
The packet usage of the XPU is sampled every second in the measurement period. Then, the maximum usage is taken as the value of this counter.
Formula
None
Unit
%
Related Features
Counter Name VS.XPU.MSGLOAD.MAX Feature ID WRFD-040100 Feature Name Flow Control
Issue 01 (2013-05-04)
3137
3.8.1.6 Average Packet Usage of the XPU Counters

Counter ID 73415214 Counter Name VS.XPU.MSGLOAD.MEA N Counter Description AR9782:Average Packet Usage of the XPU
Description
This counter provides the average packet usage of the XPU in a measurement period. It indicates the packet traffic of the XPU in the specified period.
Measurement point
The packet usage of the XPU is sampled and accumulated every second in the measurement period. Then, average packet usage of the XPU is the accumulated value divided by the number of sampling times.
Formula
None
Unit
%
Related Features
Counter Name VS.XPU.MSGLOAD.MEA N Feature ID WRFD-040100 Feature Name Flow Control
Issue 01 (2013-05-04)
3138

BSC6900 UMTS Performance Counter Reference (V900R015C00 - 01) (PDF) - en

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

BSC6900 UMTS Performance Counter Reference (V900R015C00 - 01) (PDF) - en

Diunggah oleh

Hak Cipta:

Format Tersedia

BSC6900 UMTS V900R015C00

Performance Counter Reference

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.