Академический Документы
Профессиональный Документы
Культура Документы
V900R014C00
Issue 06
Date 2013-06-28
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.
Website: http://www.huawei.com
Email: support@huawei.com
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.
BSC6900 V900R014C00
Intended Audience
This document is intended for:
l Network planners
l System engineers
l Field engineers
l Shift operators
l Site maintainers
l Network operators
Change History
For detailed performance counter changes, see the release notes.
Document Structure
Figure 1 shows the document structure.
Table 1 Terms
Term Explanation
Item Description
Item Description
Counter A table that lists parent counters and their child counters in a
Relationship 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.
Contents
1.4.5.10 Number of Authentication Requests Received by the RNC from the CN.........................................................142
1.4.5.11 Number of Authentication Responses Forwarded by the RNC to the CN.........................................................143
1.4.5.12 Number of SECURITY MODE COMMAND Messages Received by the RNC from the CN.........................144
1.4.5.13 Number of SECURITY MODE COMPLETE Messages Forwarded by the RNC to the CN............................144
1.4.5.14 Number of Routing Area Update Requests Forwarded by the RNC to the CN.................................................145
1.4.6 Measurement related to PS Iu interface signalling(PS.SIG.IU)..............................................................................146
1.4.6.1 Number of RESET Messages Initiated by RNC to PS Domain...........................................................................150
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.7 Measurement related to PS traffic(PS.TRF.IU).......................................................................................................170
1.4.7.1 Number of UL Bytes of PS Conversational Service on Iu Interface....................................................................172
1.4.7.2 Number of UL Bytes of PS Streaming Service on Iu Interface............................................................................173
1.4.7.3 Number of UL Bytes of PS Interactive Service on Iu Interface...........................................................................173
1.4.7.4 Number of UL Bytes of PS Background Service on Iu Interface.........................................................................174
1.4.7.5 Number of DL Bytes of PS Conversational Service on Iu Interface....................................................................175
1.4.7.6 Number of DL Bytes of PS Streaming Service on Iu Interface............................................................................176
1.4.7.7 Number of DL Bytes of PS Interactive Service on Iu Interface...........................................................................177
1.4.7.8 Number of DL Bytes of PS Background Service on Iu Interface.........................................................................177
1.4.7.9 Number of UL Bytes of PS BE Service for Golden Subscriber on Iu Interface..................................................178
1.4.7.10 Number of UL Bytes of PS BE Service for Silver Subscriber on Iu Interface...................................................179
1.4.7.11 Number of UL Bytes of PS BE Service for Copper Subscriber on Iu Interface................................................180
1.4.7.12 Number of DL Bytes of PS BE Service for Golden Subscriber on Iu Interface................................................181
1.4.7.13 Number of DL Bytes of PS BE Service for Silver Subscriber on Iu Interface...................................................181
1.4.7.14 Number of DL Bytes of PS BE Service for Copper Subscriber on Iu Interface................................................182
1.4.7.15 Total HTTP Traffic Volume on the RNC...........................................................................................................183
1.4.7.16 Total P2P Traffic Volume on the RNC..............................................................................................................184
1.4.7.17 Total Traffic Volume of all Subscribed Services on the RNC...........................................................................185
1.4.7.18 Total Traffic Volume of Undefined Services on the RNC.................................................................................185
1.4.8 Measurement Related to SCCP for Iu Interface(SIG.SCCP.IU).............................................................................186
1.4.8.1 Number of SCCP Connection Requests Sent by the RNC to the CN Through the Iu Interface..........................187
1.4.8.2 Number of Successful SCCP Connection Requests Sent by the RNC to the CN Through the Iu Interface........188
1.4.8.3 Number of SCCP Connection Requests Received by the RNC from the CN Through the Iu Interface..............189
1.4.8.4 Number of Successful SCCP Connection Requests Received by the RNC from the CN Through the Iu Interface
..........................................................................................................................................................................................190
1.8.9.1 Counters Related to the Number of PS RAB Setup Requests for Different Services..........................................444
1.8.9.2 Signaling Delay of PS RAB Setup.......................................................................................................................446
1.8.9.3 Counters Related to the Number of PS RAB Setup Requests for Different Maximum Downlink Bit rates........448
1.8.9.4 Counters Related to the Number of Successful PS RAB Setups for Different Maximum Downlink Bit Rates
..........................................................................................................................................................................................451
1.8.9.5 Mean Number of PS RABs..................................................................................................................................455
1.8.9.6 Times of PS RAB established successfully with 0kbps for RNC........................................................................456
1.8.9.7 Number of Successful RAB Establishments for PS Services...............................................................................457
1.8.10 Measurement of CS RAB assignment modification per RNC(RAB.ModCs.RNC).............................................459
1.8.10.1 Number of CS RAB Modification Requests......................................................................................................460
1.8.10.2 Number of VP Services Fallen Back to AMR Services.....................................................................................461
1.8.10.3 Number of Successful CS RAB Modifications..................................................................................................463
1.8.11 Measurement of PS RAB assignment modification per RNC(RAB.ModPs.RNC)..............................................464
1.8.11.1 Number of PS RAB Modification Requests.......................................................................................................466
1.8.11.2 Number of Successful PS RAB Modifications...................................................................................................467
1.8.12 Measurement of multi-RAB service per RNC(RAB.MultiRab.RNC)..................................................................470
1.8.12.1 Mean Number of UEs with Multi-RABs in RNC..............................................................................................470
1.8.13 Measurement of RAB release per RNC(RAB.RelAbnormal.RNC)......................................................................472
1.8.13.1 Number of Released RABs due to RF cause......................................................................................................476
1.8.13.2 Number of RABs Abnormally Released for RNC.............................................................................................479
1.8.13.3 Number of Normally Released RABs................................................................................................................482
1.8.13.4 Number of Released RABs Triggered by RNC Due to UE Signaling Connection Release..............................485
1.8.13.5 Number of Abnormally Released CS RABs......................................................................................................488
1.8.13.6 Times of PS RAB of 0kbps released for failing to rate up before timer expiry.................................................491
1.8.14 Measurement of CS RAB release per RNC(RAB.RelCs.RNC)............................................................................492
1.8.14.1 Number of CS RABs Requested to Release.......................................................................................................493
1.8.14.2 Number of Successful CS RAB Releases...........................................................................................................494
1.8.15 Measurement of PS RAB release per RNC(RAB.RelPs.RNC).............................................................................496
1.8.15.1 Number of Successful PS RAB Releases...........................................................................................................496
1.8.15.2 Number of PS RABs Requested to Release.......................................................................................................498
1.8.16 Measurement of RB Procedure per RNC(RB.RNC).............................................................................................499
1.8.16.1 Counters Related to the Average Number of RBs for PS R99 Conversational Services...................................508
1.8.16.2 Counters Related to the Average Number of PS R99 Interactive Service RBs..................................................511
1.8.16.3 Counters Related to the Average Number of PS R99 Backgroud Service RBs.................................................514
1.8.16.4 Counters Related to the Average Number of CS Streaming Service RBs.........................................................517
1.8.16.5 Counters Related to the Average Number of CS Conversational Service RBs..................................................518
1.8.16.6 Number of DCH-to-HSDPA Directed Retry Attempts......................................................................................519
1.8.16.7 Number of Successful DCH-to-HSDPA Directed Retry....................................................................................520
1.8.16.8 Counters Related to the Average Number of PS R99 Streaming Service RBs..................................................520
1.8.17 Measurement of relocation per DRNC(Relocation.Drnc.RNC)............................................................................523
1.8.17.1 Counters Related to the Number of Failed Relocation Executions for Different Causes for TRNC.................528
1.8.17.2 Number of Failed Relocation Resource Allocations Due to Reception of IU Release Command for TRNC
..........................................................................................................................................................................................529
1.8.17.3 Counters Related to the Number of Failed Relocation Resource Allocations for Different Causes for TRNC
..........................................................................................................................................................................................531
1.8.17.4 Number of Reconfiguration Completions During Relocation for TRNC (UE Involved)..................................532
1.8.17.5 Number of Relocation Execution Attempts for TRNC (UE Not Involved).......................................................534
1.8.17.6 Number of Successful Relocation Executions for TRNC (UE Not Involved)...................................................535
1.8.17.7 Number of Successful Relocation Executions for TRNC (UE Involved)..........................................................536
1.8.17.8 Counters Related to the Number of PS Relocation Resource Allocation Attempts for TRNC..........................538
1.8.17.9 Counters Related to the Number of Successful PS Relocation Resource Allocations for TRNC......................539
1.8.17.10 Counters Related to the Number of Failed PS Relocation Preparations for Different Causes for TRNC (UE
Involved)...........................................................................................................................................................................541
1.8.17.11 Counters Related to the Number of Failed PS Relocation Preparations for Different Causes for TRNC (UE Not
Involved)...........................................................................................................................................................................542
1.8.17.12 Counters Related to the Number of CS Relocation Resource Allocation Attempts for TRNC.......................544
1.8.17.13 Counters Related to the Number of Successful CS Relocation Resource Allocations for TRNC...................545
1.8.17.14 Number of Failed CS Relocation Preparations Due to Ciphering Failure for TRNC (UE Involved)..............547
1.8.17.15 Counters Related to the Number of Failed CS Relocation Preparations for Different Causes for TRNC (UE Not
Involved)...........................................................................................................................................................................548
1.8.17.16 Number of Successful TRNC Relocations in the CS Domain and PS Domain (UE Involved).......................550
1.8.17.17 Number of Successful TRNC Relocations in the CS Domain and PS Domain (UE Not Involved)................551
1.8.18 Measurement of relocation per SRNC(Relocation.Srnc.RNC).............................................................................553
1.8.18.1 Counters Related to the Number of CS Relocation Preparation Attempts for Different Causes for SRNC (UE
Involved)...........................................................................................................................................................................564
1.8.18.2 Counters Related to the Number of CS Relocation Preparation Attempts for SRNC........................................565
1.8.18.3 Counters Related to the Number of Successful CS Relocation Preparations for Different Causes for SRNC (UE
Involved)...........................................................................................................................................................................567
1.8.18.4 Counters Related to the Number of Successful CS Relocation Preparations for SRNC....................................568
1.8.18.5 Counters Related to the Number of Failed CS Relocation Preparations for Different Causes for SRNC (UE
Involved)...........................................................................................................................................................................570
1.8.18.6 Counters Related to the Number of Failed Relocation Executions During Reconfiguration for Different Causes
for SRNC..........................................................................................................................................................................572
1.8.18.7 Counters Related to the Number of Failed SRNC Relocation Executions Due to Timer Expiry for IU Release
Command for SRNC........................................................................................................................................................574
1.8.18.8 Counters Related to the Number of Relocation Execution Attempts for SRNC (UE Not Involved).................576
1.8.18.9 Number of Failed Relocation Executions Due to Reception of IU Release Command for SRNC....................578
1.8.18.10 Counters Related to the Number of CS Relocation Preparation Attempts for Different Causes for SRNC (UE
Not Involved)....................................................................................................................................................................579
1.8.18.11 Counters Related to the Number of Successful CS Relocation Preparations for Different Causes for SRNC (UE
Not Involved)....................................................................................................................................................................581
1.8.18.12 Counters Related to the Number of Failed CS Relocation Preparations for Different Causes for SRNC (UE Not
Involved)...........................................................................................................................................................................582
1.8.18.13 Counters Related to the Number of PS Relocation Preparation Attempts for Different Causes for SRNC (UE
Involved)...........................................................................................................................................................................585
1.8.18.14 Counters Related to the Number of PS Relocation Preparation Attempts for Different Causes for SRNC (UE
Not Involved)....................................................................................................................................................................586
1.8.18.15 Counters Related to the Number of PS Relocation Preparation Attempts for SRNC......................................587
1.8.18.16 Counters Related to the Number of Successful PS Relocation Preparations for Different Causes for SRNC (UE
Involved)...........................................................................................................................................................................589
1.8.18.17 Counters Related to the Number of Successful PS Relocation Preparations for Different Causes for SRNC (UE
Not Involved)....................................................................................................................................................................590
1.8.18.18 Counters Related to the Number of Successful PS Relocation Preparations for SRNC..................................592
1.8.18.19 Counters Related to the Number of Failed PS Relocation Preparations for Different Causes for SRNC (UE
Involved)...........................................................................................................................................................................593
1.8.18.20 Counters Related to the Number of Failed PS Relocation Preparations for Different Causes for SRNC (UE Not
Involved)...........................................................................................................................................................................596
1.8.18.21 Counters Related to the Number of Reconfiguration Attempts During Relocation Execution for SRNC ( UE
Involved)...........................................................................................................................................................................598
1.8.18.22 Counters Related to the Number of Successful Relocation Executions for SRNC (UE Involved)..................599
1.8.18.23 Counters Related to the Number of Successful Relocation Executions for SRNC (UE Not Involved)...........601
1.8.19 RLC measurement per RNC(RLC.RNC)..............................................................................................................602
1.8.19.1 Number of Packets Sent by All RLCs in TM Mode in RNC.............................................................................604
1.8.19.2 Number of Packets Sent by All RLCs in AM Mode in RNC.............................................................................604
1.8.19.3 Number of Packets Sent by All RLCs in UM Mode in RNC.............................................................................605
1.8.19.4 Number of Packets Received by All RLCs in TM Mode in RNC.....................................................................606
1.8.19.5 Number of Packets Received by All RLCs in AM Mode in RNC.....................................................................607
1.8.19.6 Number of Packets Received by All RLCs in UM Mode in RNC.....................................................................607
1.8.19.7 Number of Packets Discarded by All RLCs in RNC..........................................................................................608
1.8.19.8 Number of Packets Retransmitted by All RLCs in AM Mode in RNC.............................................................609
1.8.19.9 Number of PDUs with the Size Smaller than 336 bit Received by RLCs In Acknowledged Mode Carried by TRB
..........................................................................................................................................................................................610
1.8.19.10 Number of PDUs with the Size Greater than or Equal to 336 bit Received by RLCs In Acknowledged Mode
Carried by TRB................................................................................................................................................................610
1.8.20 Measurement related to IMS(RNC.IMS)..............................................................................................................611
1.8.20.1 Mean Number of UEs Setting Up Different IMS Services................................................................................613
1.8.20.2 Number of UEs Setting Up IMS Services..........................................................................................................615
1.8.21 RRC connection release measurement per RNC(RRC.Rel.RNC)........................................................................615
1.8.21.1 Number of RRC Connection Releases...............................................................................................................617
1.8.21.2 Counters Related to the Number of RRC Connection Releases due to Different Causes..................................618
1.8.21.3 Number of RRC Releases Due to Failure in the UE State Transition to CELL_PCH Triggered by Signaling
Connection Release Indication.........................................................................................................................................621
1.8.21.4 Number of RRC Connection Releases Triggered by SRNC Due to DSCR.......................................................622
1.8.21.5 Number of RRC Connection Releases Triggered by DRNC Due to DSCR......................................................624
1.8.22 RRC connection setup measurement per RNC(RRC.Setup.RNC)........................................................................625
1.8.22.1 Counters Related to the Number of RRC Connection Requests Processed by RNC.........................................628
1.8.22.2 Total Number of RRC Connection Requests Received by RNC.......................................................................630
1.8.22.3 Counters Related to the Number of Successful RRC Connection Establishments............................................631
1.8.23 RRC state measurement(RRC.STATE)................................................................................................................633
1.8.23.1 Counters Related to the Number of UEs in Different RRC Connection States for RNC...................................634
1.8.23.2 Number of PTT UEs in URA_PCH State for RNC............................................................................................635
1.8.23.3 Average Number of UEs in the URA_PCH State and Carried on the EPCH for RNC.....................................636
1.10.1.8 Counters Related to the Number of Downlink DCH DCCC Downsizing Attempts Based on Different Strategies
..........................................................................................................................................................................................705
1.10.1.9 Counters Related to the Number of Successful DL DCH DCCC Downsizings Based on Different DCCC Strategies
..........................................................................................................................................................................................707
1.10.1.10 Counters Related to the Number of UL or DL Overload Congestion..............................................................708
1.10.1.11 Counters Related to the Duration of UL or DL Overload Congestion.............................................................710
1.10.1.12 Number of UEs Transferring BE Service to Common Channel in Overload Congestion...............................711
1.10.1.13 Counters Related to the Duration of Cell in LDR State Due to Congestion of Various Resources.................711
1.10.1.14 Counters Related to the Number of Times a Cell Is in LDR State Due to Congestion of Various Resources
..........................................................................................................................................................................................713
1.10.1.15 Number of HSUPA UEs Performing PS Inter-RAT Handover in Basic Congestion......................................714
1.10.1.16 Counters Related to the Number of UEs Performing BE Service TF Control in Overload Congestion..........715
1.10.1.17 Counters Related to the Number of UEs Released Due to Overload Congestion............................................716
1.10.1.18 Number of Preemptions During RAB Establishment.......................................................................................718
1.10.1.19 Counters Related to the Number of Failed Requests for Different Resources During Channel Type Switch
..........................................................................................................................................................................................719
1.10.1.20 Number of Preemptions During HHO..............................................................................................................720
1.10.1.21 Number of MBMS PTM Service Releases in Overload Congestion...............................................................721
1.10.1.22 Number of MBMS PTP Service Releases in Overload Congestion.................................................................722
1.10.1.23 Counters Related to the Number of UEs Performing Inter-Frequency Load Handovers in Basic Congestion
..........................................................................................................................................................................................723
1.10.1.24 Counters Related to the Number of UEs Performing BE Service Downsizing in Basic Congestion..............724
1.10.1.25 Counters Related to the Number of UEs Performing Uncontrollable Real-Time Service QoS Renegotiation in
Basic Congestion..............................................................................................................................................................725
1.10.1.26 Counters Related to the Number of UEs Performing CS Inter-RAT Handovers in Basic Congestion............727
1.10.1.27 Counters Related to the Number of UEs Performing PS Inter-RAT Handovers in Basic Congestion............728
1.10.1.28 Counters Related to the Number of UEs Performing AMR Rate Decrease in Basic Congestion....................729
1.10.1.29 Number of UEs Performing Code Adjustment Attempts in DL Basic Congestion for Cell............................730
1.10.1.30 Number of MBMS Services Performing Power Decreasing in Basic Congestion...........................................731
1.10.1.31 Counters Related to the Number of Qoffset Updates Due to Load Level Change...........................................732
1.10.1.32 Counters Related to the Number of Sintersearch Updates Due to Cell Load Change.....................................733
1.10.1.33 Number of Successful Cell Resource Requests During HHO..........................................................................735
1.10.1.34 Number of Cell Resource Requests During HHO............................................................................................737
1.10.1.35 Number of Successful Cell Resource Requests During RAB Establishment..................................................738
1.10.1.36 Number of Cell Resource Requests During RAB Establishment.....................................................................739
1.10.1.37 Number of Successful Cell Resource Requests due to UE Service Reconfiguration (Cell)............................741
1.10.1.38 Number of Cell Resource Requests due to UE Service Reconfiguration (Cell)..............................................742
1.10.1.39 Number of Successful Cell Resource Requests During SHO..........................................................................744
1.10.1.40 Number of Cell Resource Requests During SHO............................................................................................745
1.10.1.41 Number of Successful Cell Resource Requests During Channel Type Switch................................................746
1.10.1.42 Number of Cell Resource Requests During Channel Type Switch..................................................................747
1.10.1.43 Counters Related to the Mean Number of Equivalent Voice UEs in CEL_DCH State...................................748
1.10.1.44 Duration of Cell Dynamic Shutdown Due to Automatic Shutdown................................................................748
1.10.1.45 Cell Unavailability Duration caused by O&M (Cell).......................................................................................749
1.10.1.84 Number of Attempts to transfer state from CELL_PCH to CELL_DCH for cell............................................802
1.10.1.85 Number of Successful state transfer from CELL_PCH to CELL_DCH for cell..............................................804
1.10.1.86 Number of Attempts to transfer state from URA_PCH to CELL_DCH for cell..............................................805
1.10.1.87 Number of successful state transfer from URA_PCH to CELL_DCH in the best cell....................................806
1.10.1.88 Number of Attempts of CELL_PCH/URA_PCH-to-CELL_DCH State Transition Together with DRD for Cell
..........................................................................................................................................................................................808
1.10.1.89 Number of Successful CELL_PCH/URA_PCH-to-CELL_DCH State Transitions Together with DRDs for Cell
..........................................................................................................................................................................................809
1.10.1.90 Number of CPICH Power Adjustments Based on RTWP for Cell..................................................................811
1.10.1.91 Duration of PCPICH Power Under Minimum RTWP Threshold....................................................................812
1.10.1.92 Number of State Transfer Attempts from CELL_DCH to CELL_PCH or URA_PCH for Cell for HSDPA service
..........................................................................................................................................................................................813
1.10.1.93 Number of Successful Times That a UE Performing HSDPA Services Transits to CELL_PCH or URA_PCH
State for cell......................................................................................................................................................................814
1.10.1.94 Number of Attempts for a UE Performing HSUPA Services to Transit to CELL_PCH or URA_PCH State for
Cell....................................................................................................................................................................................816
1.10.1.95 Number of Successful Times That a UE Performing HSUPA Services Transits to CELL_PCH or URA_PCH
State for cell......................................................................................................................................................................817
1.10.1.96 Number of Attempts for a UE Performing PS R99 Services to Transit to CELL_PCH or URA_PCH State for
Cell....................................................................................................................................................................................819
1.10.1.97 Number of Successful Times That a UE Performing PS R99 Services Transits to CELL_PCH or URA_PCH
State for cell......................................................................................................................................................................820
1.10.1.98 Number of Times That PS R99 Service Rate Is Found to Be Higher than HSUPA Service Rate...................822
1.10.1.99 Number of PS R99 BE Rate Reduction Requests Triggered by Unfairness Between PS R99 Service Rate and
HSUPA Service Rate........................................................................................................................................................823
1.10.1.100 Duration of CPU Resource Insufficiency Reported by NodeB......................................................................824
1.10.1.101 Congestion Duration of DCCHs, DTCHs and CCCHs Carried over FACHs for Cell..................................825
1.10.2 Algorithm Measurement2 for Cell(ALGO2.Cell).................................................................................................826
1.10.2.1 Average Number of UEs Using OLPC Enhancement Based on SIRerror Distribution.....................................830
1.10.2.2 Average and Maximum Uplink Background Noise...........................................................................................831
1.10.2.3 Number of Automatic Uplink Background Noise Updates................................................................................832
1.10.2.4 Counters Related to the Number of Failed in Channal Transfering Process......................................................833
1.10.2.5 Number of RoT adjustments in an HSUPA cell.................................................................................................834
1.10.2.6 Number of Successful TTI Switchovers with Various Causes During RB Reconfiguration in a Cell(2ms to 10ms)
..........................................................................................................................................................................................835
1.10.2.7 Number of Times HSUPA UEs Processing BE Services Succeed in Setting Up RABs over the DCH in Case of
Weak Coverage.................................................................................................................................................................837
1.10.2.8 Mean Number of Access Classes Restricted Due to Cell Resource Congestion................................................838
1.10.2.9 Duration of Access Class Restriction Triggered by Cell Resource Congestion.................................................840
1.10.2.10 Number of UEs Involved in Inter-Frequency Load-based Handovers in a CLB Cell......................................840
1.10.2.11 Number of Attempts to Configure CQI Feedback Period for a Cell................................................................842
1.10.2.12 Number of Attempts to Configure BLER in a Congested or Normal Cell.......................................................843
1.10.2.13 Number of CS RABs Abnormally Released for Special UEs for Cell.............................................................843
1.10.2.14 Number of CS RABs Normally Released for Special UEs for Cell.................................................................846
1.10.2.15 Uplink Actual Cell Load...................................................................................................................................848
1.10.11.43 Number of Successful Outgoing Inter-Frequency Hard Handovers Between Different NodeBs of RNC
........................................................................................................................................................................................1066
1.10.11.44 Number of Outgoing Inter-Frequency Hard Handovers Attempts Between RNCs.....................................1068
1.10.11.45 Number of Successful Outgoing Inter-Frequency Hard Handovers Between RNCs...................................1069
1.10.11.46 Number of Relocation Execution Attempts with Outgoing Inter-Frequency Hard Handovers...................1071
1.10.11.47 Number of Successful Relocation Executions with Outgoing Inter-Frequency Hard Handovers...............1072
1.10.11.48 Number of Outgoing Emergency Blind Handover Attempts.......................................................................1074
1.10.11.49 Number of Successful Outgoing Emergency Blind Hard Handovers..........................................................1075
1.10.11.50 Counters Related to the Number of Handovers Not Performed Due to Inter-Frequency Measurement Expiry
........................................................................................................................................................................................1077
1.10.11.51 Number of Requests for Incoming Inter-Frequency Hard Handovers (Cell)...............................................1078
1.10.11.52 Number of Requests for Outgoing Inter-Frequency Hard Handovers (Cell)...............................................1080
1.10.11.53 Number of Successful for Incoming Inter-Frequency Hard Handovers (Cell)............................................1082
1.10.11.54 Number of Successful for Outgoing Inter-Frequency Hard Handovers (Cell).............................................1084
1.10.11.55 Number of Call Drops due to Unsuccessful Outgoing Inter-Frequency Hard Handovers (Cell).................1086
1.10.11.56 Number of Failed Outgoing Intra-Frequency Hard Handovers Between the RNCs Due to No Response from
the UE.............................................................................................................................................................................1088
1.10.11.57 Counters Related to the Number of Failed Outgoing Inter-Frequency Hard Handovers Between the RNCs for
Different Causes.............................................................................................................................................................1089
1.10.11.58 Number of Failed Outgoing Inter-Frequency Hard Handovers Between the RNCs Due to No Response from
the UE.............................................................................................................................................................................1092
1.10.11.59 Counters Related to the Number of Outgoing Inter-Frequency Hard Handover Attempts..........................1093
1.10.11.60 Counters Related to the Number of Successful Outgoing Inter-Frequency Hard Handovers......................1098
1.10.11.61 Number of Inter-Frequency Hard Handover Attempts When only Signaling Exists for Cell......................1103
1.10.11.62 Number of Successful Inter-Frequency Hard Handover Attempts When only Signaling Exists for Cell
........................................................................................................................................................................................1105
1.10.12 HSDPA Measurement per cell(HSDPA.Cell)...................................................................................................1106
1.10.12.1 Number of Successful Channel Reconfigurations..........................................................................................1119
1.10.12.2 Number of Successful HSDPA MAC-d Flow Establishments for Cell.........................................................1121
1.10.12.3 Number of HSDPA UEs in a Cell..................................................................................................................1122
1.10.12.4 Number of MAC-d Flows in a Cell................................................................................................................1123
1.10.12.5 Mean Downlink Throughput of single HSDPA MAC-d Flows.....................................................................1124
1.10.12.6 Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow.............................................................1125
1.10.12.7 Mean Downlink Throughput of HSDPA MAC-d Flow of BE Service for Golden Subscriber.....................1126
1.10.12.8 Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow of BE Service for Golden Subscriber
........................................................................................................................................................................................1127
1.10.12.9 Mean Downlink Throughput of HSDPA MAC-d Flow of BE Service for Silver Subscriber.......................1128
1.10.12.10 Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow of BE Service for Silver Subscriber
........................................................................................................................................................................................1128
1.10.12.11 Mean Downlink Throughput of HSDPA MAC-d Flow of BE Service for Copper Subscriber...................1129
1.10.12.12 Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow of BE Service for Copper Subscriber
........................................................................................................................................................................................1130
1.10.12.13 Number of Handover Attempts Between Channels of Different Types.......................................................1131
1.10.12.14 Number of HSDPA Serving Cell Change Attempts for Cell.......................................................................1133
1.10.12.15 Number of Successful HSDPA Serving Cell Changes for Cell...................................................................1134
1.10.12.16 Number of inter-RNC HSDPA Serving Cell Change Attempts for Cell.....................................................1136
1.10.12.17 Number of Successful Inter-RNC HSDPA Serving Cell Changes for Cell.................................................1137
1.10.12.18 Number of Inter-RNC HSDPA Hard Handover Attempts Without Channel Change for Cell....................1139
1.10.12.19 Number of Successful Inter-RNC HSDPA Hard Handovers Without Channel Change for Cell................1140
1.10.12.20 Number of Intra-Frequency HSDPA Hard Handover Attempts without Channel Change for Cell............1142
1.10.12.21 Number of Successful Intra-Frequency HSDPA Hard Handovers Without Channel Change for Cell........1143
1.10.12.22 Number of Inter-Frequency HSDPA Hard Handover Attempts Without Channel Change for Cell............1145
1.10.12.23 Number of Successful Inter-Frequency HSDPA Hard Handovers Without Channel Change for Cell........1147
1.10.12.24 Number of Intra-Frequency HSDPA Hard Handover Attempts for Cell(HSDPA to DCH)........................1149
1.10.12.25 Number of Successful Intra-Frequency HSDPA Hard Handovers for Cell(HSDPA to DCH)....................1151
1.10.12.26 Number of Inter-Frequency Hard Handover Attempts for Cell(HSDPA to DCH)......................................1152
1.10.12.27 Number of Successful Inter-Frequency Hard Handovers for Cell(HSDPA to DCH)..................................1154
1.10.12.28 Number of HSDPA RAB Establishment Attempts for Cell.........................................................................1155
1.10.12.29 Number of HSDPA RAB Establishment Attempts of BE Service for Different Prior Level Users............1157
1.10.12.30 Number of Successful HSDPA RAB Establishments for Cell.....................................................................1158
1.10.12.31 Number of Successful HSDPA RAB Establishments of BE Service for different prior Level Users.........1160
1.10.12.32 Number of RAB Releases due to User Inactivity.........................................................................................1161
1.10.12.33 Number of HSDPA RABs Abnormal Released for Cell..............................................................................1164
1.10.12.34 Number of HSDPA RABs Abnormal Released Due to RF Cause for Cell.................................................1167
1.10.12.35 Number of HSDPA RABs Normal Released for Cell..................................................................................1169
1.10.12.36 Number of Inter-RNC HSDPA Hard Handover Attempts for Cell(HSDPA to DCH)................................1172
1.10.12.37 Number of Successful inter-RNC HSDPA Hard Handovers for Cell(HSDPA to DCH).............................1173
1.10.12.38 Number of HSDPA 64QAM RABs Setup Request for cell.........................................................................1174
1.10.12.39 Number of HSDPA 64QAM RABs Setup Successfully for cell..................................................................1176
1.10.12.40 Number of HSDPA 64QAM RABs Abnormal Released for cell................................................................1177
1.10.12.41 Number of HSDPA 64QAM RABs Normal Released for Cell....................................................................1179
1.10.12.42 Number of HSDPA MIMO RABs Setup Request for Cell..........................................................................1181
1.10.12.43 Number of HSDPA MIMO RABs Setup Successfully for cell....................................................................1183
1.10.12.44 Number of HSDPA MIMO RABs Normal Released for cell......................................................................1184
1.10.12.45 Number of HSDPA MIMO+64QAM RABs Setup Request for cell............................................................1186
1.10.12.46 Number of HSDPA MIMO+64QAM RABs Setup Successfully for cell....................................................1188
1.10.12.47 Number of HSDPA MIMO+64QAM RABs Abnormal Released for cell...................................................1189
1.10.12.48 Number of HSDPA MIMO+64QAM RABs Normal Released for cell.......................................................1191
1.10.12.49 Number of DC-HSDPA RABs Setup Request in the primary carrier of DC-HSDPA counted for cell.......1193
1.10.12.50 Number of DC-HSDPA RABs Setup Successfully in the primary carrier of DC-HSDPA counted for cell
........................................................................................................................................................................................1195
1.10.12.51 Number of DC-HSDPA RABs Abnormal Released in the primary carrier of DC counted for Cell...........1196
1.10.12.52 Number of DC-HSDPA RABs Normal Released in the primary carrier of DC counted for Cell...............1199
1.10.12.53 Number of HSDPA MIMO RABs Abnormal Released for cell..................................................................1201
1.10.12.54 Number of HSDPA UEs with Various Categories in a Cell........................................................................1204
1.10.12.55 Number of HSDPA MAC-d Flow Establishment Requests for Cell............................................................1207
1.10.12.56 Number of Failed HSDPA Service Establishments Due to Insufficiency of Different Resources..............1209
1.10.12.57 Average downlink throughput of the Traffic PS Conversational beared on HSDSCH for cell...................1211
1.10.12.58 Number of downlink bytes of Transport Blocks of Traffic PS Conversational beared on HSDSCH for cell
........................................................................................................................................................................................1212
1.10.12.59 Number of 64QAM UEs in a Cell................................................................................................................1213
1.10.12.60 Number of MIMO UEs in a Cell..................................................................................................................1213
1.10.12.61 Number of MIMO+64QAM UEs in a Cell..................................................................................................1214
1.10.12.62 Number of DC-HSDPA UEs in a Cell.........................................................................................................1215
1.10.12.63 Number of Outgoing DRD Attempts for HSDPA Users Through Intelligent User Recognition for Cell
........................................................................................................................................................................................1216
1.10.12.64 Number of Successful Outgoing DRDs for HSDPA Users Through Intelligent User Recognition for Cell
........................................................................................................................................................................................1217
1.10.12.65 Number of Incoming DRD Attempts for HSDPA Users Through Intelligent User Recognition for Cell
........................................................................................................................................................................................1219
1.10.12.66 Number of Successful Incoming DRDs for HSDPA Users Through Intelligent User Recognition for Cell
........................................................................................................................................................................................1220
1.10.12.67 Number of RABs Abnormally Released for PS HSDPA Services during the State Transition from CELL_DCH
to CELL_PCH or URA_PCH for Cell...........................................................................................................................1222
1.10.12.68 Number of DC-HSDPA+MIMO RAB Setup Requests in the Primary Carrier of DC-HSDPA for Cell
........................................................................................................................................................................................1225
1.10.12.69 Number of Successful DC-HSDPA+MIMO RAB Setups in the Primary Carrier of DC-HSDPA for cell
........................................................................................................................................................................................1227
1.10.12.70 Number of Normal DC-HSDPA+MIMO RAB Releases in the Primary Carrier of DC-HSDPA for cell
........................................................................................................................................................................................1228
1.10.12.71 Number of Abnormal DC-HSDPA+MIMO RAB Releases in the Primary Carrier of DC-HSDPA for cell
........................................................................................................................................................................................1231
1.10.12.72 Average Throughput on HSDPA MAC-d Flow for Cell (Excluding the Data of Low-Traffic Users)........1233
1.10.12.73 Number of Bytes Sent on HSDPA MAC-d Flow for Cell (Excluding the Bytes of Low-Traffic Users)
........................................................................................................................................................................................1234
1.10.12.74 Average Number of Free HSDPA Users in a Cell.......................................................................................1235
1.10.12.75 Maximum Number of Free HSDPA Users in a Cell....................................................................................1236
1.10.12.76 Number of Serving Cell Change Attempts Triggered by Unbalanced Iub Resources.................................1237
1.10.12.77 Number of Successful Serving Cell Changes Triggered by Unbalanced Iub Resources.............................1238
1.10.13 HSUPA Measurement per cell(HSUPA.Cell)...................................................................................................1240
1.10.13.1 Number of HSUPA UEs in a Cell..................................................................................................................1253
1.10.13.2 Number of Successful EDCH MAC-d Flow Establishments for Cell............................................................1254
1.10.13.3 Number of HSUPA RAB Establishment Attempts for Cell...........................................................................1256
1.10.13.4 Number of Successful HSUPA RAB Establishments for Cell.......................................................................1258
1.10.13.5 Number of HSUPA RAB establish attempts of BE Service for different prior Level Users (Cell)...............1259
1.10.13.6 Number of Successful HSUPA RAB Establishments of BE Service for different prior Level Users (Cell)
........................................................................................................................................................................................1261
1.10.13.7 Number of HSUPA RABs Abnormal Released for Cell................................................................................1262
1.10.13.8 Number of HSUPA RABs Normal Released for Cell....................................................................................1265
1.10.13.9 Number of HSUPA RAB Released due to UE Signaling Connection failure for Cell..................................1267
1.10.13.10 Number of EDCH RL Addition and Deletion Attempts by Soft Handover for Cell....................................1270
1.10.13.11 Number of Successful EDCH RL Additions and Deletions by Soft Handover for Cell..............................1271
1.10.13.12 Number of Successful HSUPA Serving Cell Changes in Soft Handover Status for Cell............................1273
1.10.13.13 Number of HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell................................1275
1.10.13.14 Number of inter-RNC HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell..............1277
1.10.13.15 Number of Successful inter-RNC HSUPA Serving Cell Changes in Soft Handover Status for Cell..........1279
1.10.13.16 Number of Successful HSUPA Serving Cell Changes Due to inter-RNC Hard Handover without Channel
Change for Cell...............................................................................................................................................................1282
1.10.13.17 Number of HSUPA Serving Cell Change Attempts Due to inter-RNC Hard Handover without Channel Change
for Cell............................................................................................................................................................................1283
1.10.13.18 Number of Successful HSUPA Serving Cell Changes Due to Intra-Frequency Hard Handover without Channel
Change for Cell...............................................................................................................................................................1285
1.10.13.19 Number of HSUPA Serving Cell Change Attempts Due to Intra-Frequency Hard Handover without Channel
Change for Cell...............................................................................................................................................................1287
1.10.13.20 Number of Successful HSUPA Serving Cell Changes Due to Inter-Frequency Hard Handover without Channel
Change for Cell...............................................................................................................................................................1288
1.10.13.21 Number of HSUPA Serving Cell Change Attempts Due to Inter-Frequency Hard Handover without Channel
Change for Cell...............................................................................................................................................................1290
1.10.13.22 Number of Successful HSUPA Intra-Frequency Hard Handovers for Cell(EDCH to DCH)......................1291
1.10.13.23 Number of HSUPA Intra-Frequency Hard Handover Attempts for Cell(EDCH to DCH)..........................1293
1.10.13.24 Number of Successful HSUPA Inter-Frequency Hard Handovers for Cell(EDCH to DCH)......................1294
1.10.13.25 Number of HSUPA Inter-Frequency Hard Handover Attempts for Cell(EDCH to DCH)..........................1296
1.10.13.26 Number of Channel Conversion Attempts According to Different Channel Switch Type for Cell.............1297
1.10.13.27 Number of Successful Handovers Between Different Channel Types for Cell...........................................1299
1.10.13.28 Mean Uplink Throughput of single HSUPA MAC-d Flow.........................................................................1301
1.10.13.29 Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow........................................................1302
1.10.13.30 Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Golden Subscriber........................1303
1.10.13.31 Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service for Golden Subscriber
........................................................................................................................................................................................1304
1.10.13.32 Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Silver Subscriber..........................1305
1.10.13.33 Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service for Silver Subscriber
........................................................................................................................................................................................1306
1.10.13.34 Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Copper Subscriber........................1307
1.10.13.35 Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service for Copper Subscriber
........................................................................................................................................................................................1307
1.10.13.36 Number of inter-RNC HSUPA Hard Handover Attempts for Cell(EDCH to DCH)...................................1308
1.10.13.37 Number of Successful inter-RNC HSUPA Hard Handovers for Cell(EDCH to DCH)...............................1310
1.10.13.38 Number of Successful HSUPA 16QAM RAB Establishments for cell.......................................................1311
1.10.13.39 Number of HSUPA 16QAM RABs Abnormal Released for cell................................................................1313
1.10.13.40 Number of HSUPA 16QAM RABs Normal Released for cell....................................................................1315
1.10.13.41 Number of HSUPA 16QAM RAB Setup Attempts for cell.........................................................................1317
1.10.13.42 Number of HSUPA RABs Abnormal Released due to RF Failures for Cell...............................................1319
1.10.13.43 Number of HSUPA UEs with Various Categories in a Cell........................................................................1320
1.10.13.44 Number of EDCH MAC-d Flow Setup Requests for Cell...........................................................................1322
1.10.13.45 Number of Failed HSUPA Service Establishments Due to Insufficiency of Different Resources..............1324
1.10.13.46 Average uplink throughput of the Traffic PS Conversational beared on E-DCH for cell............................1326
1.10.13.47 Number of uplink bytes of Transport Blocks of Traffic PS Conversational beared on E-DCH for cell
........................................................................................................................................................................................1327
1.10.13.48 Counters Related to the Number of Transfers Between Small Retransmission and Large Retransmission for
HSUPA 2ms TTI Users or HSUPA 10ms TTI Users.....................................................................................................1328
1.10.13.49 Number of TTI Switch Attempts During RB Reconfiguration for Cell.......................................................1330
1.10.13.50 Number of Successful TTI Switches During RB Reconfiguration for Cell.................................................1332
1.10.13.51 Number of HSUPA 16QAM UEs in a Cell..................................................................................................1333
1.10.13.52 Number of HSUPA Boosting UEs in a Cell.................................................................................................1334
1.10.13.53 Number of UEs Supporting E-DPCCH Boosting and CPC for Cell............................................................1335
1.10.13.54 Number of RABs Abnormally Released for PS HSUPA Services during the State Transition from CELL_DCH
to CELL_PCH or URA_PCH for Cell...........................................................................................................................1336
1.10.13.55 Number of HSUPA Boosting RAB Setup Attempts for Cell.......................................................................1339
1.10.13.56 Number of Successful HSUPA Boosting RAB Setups for Cell...................................................................1341
1.10.13.57 Number of Abnormally Released HSUPA Boosting RABs for Cell...........................................................1342
1.10.13.58 Number of Normally Released HSUPA Boosting RABs for Cell...............................................................1345
1.10.13.59 Number of HARQ PO Reconfiguration Attempts of HSUPA Users with 10 ms TTI for Cell....................1347
1.10.13.60 Number of Successful HARQ PO Reconfigurations of HSUPA Users with 10 ms TTI for Cell................1349
1.10.13.61 Number of DC-HSUPA RAB Setup Attempts for Cell...............................................................................1350
1.10.13.62 Number of Successful DC-HSUPA RAB Setups for Cell...........................................................................1352
1.10.13.63 Number of DC-HSUPA RABs Normally Released for Cell........................................................................1353
1.10.13.64 Number of DC-HSUPA RABs Abnormally Released for Cell....................................................................1355
1.10.13.65 Number of HSUPA UEs in a Cell................................................................................................................1358
1.10.13.66 Number of HSUPA 2 ms TTI UEs in a Cell................................................................................................1359
1.10.13.67 Number of HSUPA 10 ms TTI UEs in a Cell..............................................................................................1360
1.10.13.68 Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI in a Cell with
Various Causes...............................................................................................................................................................1361
1.10.14 InterRAT Handover Measurement per cell(INTRAT.HO.Cell)........................................................................1363
1.10.14.1 Number of Successful CS or Enhanced PS Outgoing Inter-RAT Handovers for Cell...................................1383
1.10.14.2 Number of Preparations for CS or Enhanced PS Outgoing Inter-RAT Handover for Cell............................1386
1.10.14.3 Number of Successful Preparations for CS or Enhanced PS Outgoing Inter-RAT Handover for Cell..........1389
1.10.14.4 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC for Cell.....................................1392
1.10.14.5 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by the RNC for Different Causes for Cell
........................................................................................................................................................................................1395
1.10.14.6 Number of Failed Preparations for CS or Enhanced PS Outgoing Inter-RAT Handover for Different Causes for
Cell..................................................................................................................................................................................1397
1.10.14.7 Number of CS or Enhanced PS Outgoing Inter-RAT Handover Attempts for Cell.......................................1402
1.10.14.8 Number of Failed CS or Enhanced PS Outgoing Inter-RAT Handovers for Different Causes for Cell
........................................................................................................................................................................................1404
1.10.14.9 Number of Preparations for CS or Enhanced PS Incoming Inter-RAT Handover for Cell...........................1406
1.10.14.10 Number of Successful CS or Enhanced PS Incoming Inter-RAT Handovers for Cell................................1408
1.10.14.11 Number of Failed Preparations for CS or Enhanced PS Incoming Inter-RAT Handover for Different Causes
for Cell............................................................................................................................................................................1409
1.10.14.12 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE for Cell..................................1412
1.10.14.13 Number of Failed CS or Enhanced PS Inter-RAT Incoming Handovers Due to No Response from UE for Cell
........................................................................................................................................................................................1414
1.10.14.14 Number of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC for Different Causes for Cell
........................................................................................................................................................................................1415
1.10.21.8 Number of Successful PTT Paging Attempts After the RNC Sends the PAGING TYPE 1 Message for Cell
........................................................................................................................................................................................1573
1.10.21.9 Number of PTT Call Initiation or Response Attempts of UEs Using the PTT and Other Services in the
CELL_FACH State for Cell...........................................................................................................................................1574
1.10.21.10 Number of Failed PTT Call Initiations or Responses Due to Resource Congestion During a P2D Procedure for
UEs Processing PTT Services........................................................................................................................................1576
1.10.21.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.........................................................................................................1577
1.10.21.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................................................................................................................1578
1.10.21.13 Number of PTT Call Initiation Attempts or Responses During a P2D Procedure for UEs Processing PTT
Services...........................................................................................................................................................................1579
1.10.21.14 Uplink Traffic Volume of the PTT Service..................................................................................................1580
1.10.21.15 Downlink Traffic Volume of the PTT Service.............................................................................................1581
1.10.21.16 Number of Successful Serving Cell Changes of PTT Service in Soft Handover Status..............................1582
1.10.21.17 Number of Serving Cell Change Attempts of PTT Service in Soft Handover Status..................................1584
1.10.21.18 Number of Successful Hard Handovers of PTT Service..............................................................................1585
1.10.21.19 Number of Hard Handover Attempts of PTT Service..................................................................................1587
1.10.22 Measurement related to QOS per cell(QOS.Cell).............................................................................................1589
1.10.22.1 Delay of Different Services............................................................................................................................1607
1.10.22.2 Counters Related to the Number of Times that DL Throughput of HSDPA Services Within Each Range
........................................................................................................................................................................................1612
1.10.22.3 Counters Related to the Number of Times that UL Throughput of HSUPA Services Within Each Range
........................................................................................................................................................................................1620
1.10.22.4 Service Setup Duration on an ERACH for Cell.............................................................................................1627
1.10.22.5 Service Setup Duration on an EFACH for Cell..............................................................................................1628
1.10.23 Measurement of CS RAB assignment setup per cell(RAB.EstabCS.Cell).......................................................1630
1.10.23.1 Counters Related to the Number of CS RAB Setup Requests for Different Services....................................1637
1.10.23.2 Counters Related to the Number of Successful CS RAB Setups for Different Services...............................1638
1.10.23.3 Number of RAB Setup Attempts for CS AMR Services................................................................................1640
1.10.23.4 Number of RAB Setup Attempts for CS WB AMR Services........................................................................1641
1.10.23.5 Number of RAB Setup Attempts for CS 64 Kbit/s Conversational Services.................................................1644
1.10.23.6 Number of Successful RAB Setups for CS AMR Services............................................................................1645
1.10.23.7 Number of Successful RAB Setups for CS WB AMR Services....................................................................1647
1.10.23.8 Number of Successful RAB Setups for CS 64 Kbit/s Conversational Services.............................................1650
1.10.23.9 Number of RAB Setup Attempts for CS HSPA Voice Services....................................................................1651
1.10.23.10 Number of Successful RAB Setups for CS Conversational Services..........................................................1653
1.10.23.11 Number of RAB Setup Attempts for VP Services when VP Call Is Limited..............................................1654
1.10.23.12 Number of CS Over HSPA in a Cell............................................................................................................1655
1.10.23.13 Number of Queuing Attempts Due to Insufficient Resource in the CS RAB Assignment Establishment
Procedure........................................................................................................................................................................1656
1.10.23.14 Average Duration of a CS Queuing in the RAB Establishment Procedure..................................................1657
1.10.23.15 Number of Successful CS Establishment After Queuing.............................................................................1658
1.10.24 Measurement of PS RAB assignment setup per cell(RAB.EstabPS.Cell)........................................................1659
1.10.24.1 Counters Related to the Number of RAB Setup Requests for Different PS Services....................................1664
1.10.24.2 Counters Related to the Number of Successful RAB Setups for Different PS Services................................1666
1.10.24.3 Number of PS RABs Set Up Successfully at 0 Kbit/s....................................................................................1667
1.10.24.4 Number of Successful RAB Setups for PS R99 Services..............................................................................1669
1.10.24.5 Number of RAB Setup Requests for PS R99 Services...................................................................................1670
1.10.24.6 Number of Queuing Attempts Due to Insufficient Resource in the PS RAB Assignment Establishment Procedure
........................................................................................................................................................................................1672
1.10.24.7 Average Duration of a PS Queuing in the RAB Establishment Procedure....................................................1673
1.10.24.8 Number of Successful PS Establishment After Queuing...............................................................................1674
1.10.24.9 Number of PS RABs Successfully Set Up for PTT Services.........................................................................1675
1.10.24.10 Number of PS RAB Setup Requests for PTT Services................................................................................1676
1.10.24.11 Number of PS Free RAB Setup Attempts for Cell.......................................................................................1677
1.10.24.12 Number of Successful PS Free RAB Setups for Cell...................................................................................1679
1.10.25 Measurement of CS RAB assignment failure per cell(RAB.EstFailCs.Cell)....................................................1680
1.10.25.1 Number of CS RABs Unsuccessfully Established due to Congestion...........................................................1685
1.10.25.2 Number of Failed CS RABs due to Radio Network Layer Cause..................................................................1687
1.10.25.3 Number of CS RABs Unsuccessfully Established due to Iu Transport Connection Failure..........................1688
1.10.25.4 Number of CS RABs Unsuccessfully Established due to Different Reasons of UE During the RB Setup Procedure
for Cell............................................................................................................................................................................1689
1.10.25.5 Number of Failed CS RAB due to Radio Resource Congestion....................................................................1692
1.10.25.6 Number of Failed CS RAB Establishments Due to Radio Link Configuration Failure.................................1695
1.10.25.7 Number of Failed CS RAB Establishments Due to Uu Interface Configuration Failure...............................1698
1.10.25.8 Number of Failed CS RABs due to Unsupported Capabilities (Cell)............................................................1700
1.10.26 Measurement of PS RAB assignment failure per cell(RAB.EstFailPs.Cell)....................................................1702
1.10.26.1 Number of PS RABs Unsuccessfully Established due to Radio Network Layer Cause for Cell...................1708
1.10.26.2 Number of PS RABs Unsuccessfully Established due to Iu Transport Connection Failure..........................1709
1.10.26.3 Number of Failed PS RABs due to different reasons of UE During the RB Setup Procedure for cell..........1710
1.10.26.4 Number of Failed PS RABs due to Radio Resource Congestion...................................................................1713
1.10.26.5 Number of Failed PS RAB Establishments Due to Radio Link Configuration Failure.................................1716
1.10.26.6 Number of Failed PS RAB Establishments Due to Uu Interface Configuration Failure...............................1719
1.10.26.7 Number of Failed PS RABs due to Unsupported Capabilities (Cell).............................................................1721
1.10.26.8 Number of PS RABs Unsuccessfully Established due to Congestion............................................................1723
1.10.26.9 Number of PS Free RAB Setup Failures due to DL Power Resource Congestion for Cell...........................1724
1.10.27 Measurement of CS RAB assignment modification per cell(RAB.ModCs.Cell).............................................1726
1.10.27.1 Number of Failed CS RAB Modifications Due to Transport Network Layer Cause.....................................1727
1.10.27.2 Counters Related to the Number of CS RAB Modification Requests............................................................1728
1.10.27.3 Counters Related to the Number of Successful CS RAB Modifications.......................................................1730
1.10.27.4 Number of Failed CS RAB Modifications Due to Radio Network Layer Cause...........................................1731
1.10.28 Measurement of PS RAB assignment modification per cell(RAB.ModPs.Cell)..............................................1733
1.10.28.1 Number of Failed PS RAB Modifications Due to Iu Transport Connection Failure.....................................1735
1.10.28.2 Number of PS RAB Modification Requests...................................................................................................1736
1.10.28.3 Number of Successful PS RAB Modifications...............................................................................................1737
1.10.28.4 Number of Failed PS RAB Modifications Due to Radio Network Fault.......................................................1739
1.10.29 Measurement of multi-RAB service per cell(RAB.MultiRab.Cell)..................................................................1741
1.10.29.1 Mean Number of Single-RAB UEs Occupy the Codes with Different Spreading Factors............................1746
1.10.29.2 Mean Number of Multi-RAB UEs Occupy the Codes with Different Spreading Factors.............................1748
1.10.29.3 Max Count of SF which has been occupied...................................................................................................1750
1.10.29.4 Mean Throughput of a Single HSDPA MAC-d Flow in the Case of Multi-RAB Services for Cell..............1751
1.10.29.5 Mean Throughput of a Single HSUPA MAC-d Flow in the Case of Multi-RAB Services for Cell..............1752
1.10.29.6 Mean Downlink Throughput of a Single PS R99 RB in the Case of Multi-RAB Services for Cell..............1752
1.10.29.7 Mean Uplink Throughput of a Single PS R99 RB in the Case of Multi-RAB Services for Cell...................1753
1.10.29.8 Number of CS+PS Combined Service Setup Requests for Cell.....................................................................1754
1.10.29.9 Number of Successful CS+PS Combined Service Setups for Cell................................................................1757
1.10.29.10 Number of PS+PS Combined Service Setup Requests for Cell...................................................................1759
1.10.29.11 Number of Successful PS+PS Combined Service Setups for Cell...............................................................1761
1.10.29.12 Number of Normal CS Service Releases of CS+PS Combined Services for Cell.......................................1763
1.10.29.13 Number of Normal PS Service Releases of PS+PS Combined Services for Cell........................................1765
1.10.29.14 Number of Abnormal CS Service Releases of CS+PS Combined Services for Cell...................................1768
1.10.29.15 Number of Abnormal PS Service Releases of PS+PS Combined Services for Cell....................................1770
1.10.29.16 Number of Abnormal CS Service Releases During PS Service Setup for Cell............................................1773
1.10.29.17 Number of Abnormal CS Service Releases During PS Service Release for Cell........................................1776
1.10.29.18 Number of Normal PS Service Releases of CS+PS Combined Services for Cell........................................1779
1.10.29.19 Number of Abnormal PS Service Releases of CS+PS Combined Services for Cell....................................1782
1.10.29.20 Number of CS Service Setup Attempts of UEs with an Ongoing PS Service for Cell................................1784
1.10.29.21 Number of Successful CS Service Setups of UEs with an Ongoing PS Service for Cell............................1787
1.10.29.22 Number of State Transition Attempts from CELL_PCH or URA_PCH to CELL_DCH with the Cause Value
of CS Service for Cell.....................................................................................................................................................1789
1.10.29.23 Number of Successful State Transitions from CELL_PCH or URA_PCH to CELL_DCH with the Cause Value
of CS Service for Cell.....................................................................................................................................................1790
1.10.29.24 Number of Abnormal PS Service Releases in the Case of Multi-RAB Services for Cell during an inter-RAT
handover( PS Resume Timer Expiry).............................................................................................................................1792
1.10.30 Measurement of RAB release per cell(RAB.RelAbnormal.Cell)......................................................................1794
1.10.30.1 Number of CS RABs Abnormally Released Due to Different RF Causes for Cell.......................................1808
1.10.30.2 Number of CS RABs Abnormally Released for Different Services...............................................................1812
1.10.30.3 Number of PS RABs Abnormally Released for Different Services...............................................................1815
1.10.30.4 Number of CS RABs Normally Released for Different Services...................................................................1819
1.10.30.5 Number of PS RABs Normally Released for Different Services...................................................................1821
1.10.30.6 Number of CS RABs Abnormally Released for Cell.....................................................................................1825
1.10.30.7 Number of CS RABs Normally Released for Cell.........................................................................................1828
1.10.30.8 Number of PS RABs Abnormally Released for Cell.....................................................................................1830
1.10.30.9 Number of PS RABs Normally Released for Cell.........................................................................................1833
1.10.30.10 Number of CS AMRWB RABs Abnormally Released................................................................................1835
1.10.30.11 Number of CS RABs Abnormally Released Triggered by Different Causes...............................................1841
1.10.30.12 Number of CS AMR RABs Abnormally Released......................................................................................1846
1.10.30.13 Number of PS RABs Abnormally Released Due to Different RF Causes for Cell......................................1850
1.10.30.14 Number of PS RABs Abnormally Released Due to Different Causes.........................................................1854
1.10.30.15 Number of PS BE RABs carried on HSPA released due to cell congestion or preemption.........................1858
1.10.33.58 Number of CELL_FACH to CELL_PCH Transition Attempts by Physical Channel Reconfiguration for Cell
........................................................................................................................................................................................2034
1.10.33.59 Number of SuccessfulCELL_FACH to CELL_PCH Transitions by Physical Channel Reconfiguration for Cell
........................................................................................................................................................................................2035
1.10.34 Reserved counter for cell(RESERVE.Cell).......................................................................................................2037
1.10.34.1 Number of Concurrent Abnormal CS and PS Service Releases of CS+PS Combined Services for Cell
........................................................................................................................................................................................2039
1.10.34.2 Number of RABs Released with the Cause of Network Optimization for Cell.............................................2042
1.10.34.3 Reserved counter for cell................................................................................................................................2047
1.10.34.4 Number of CS or PS Service Releases Caused by the Second RRC Connection Setup Request from the same
UE for Cell......................................................................................................................................................................2048
1.10.34.5 This counter provides the number of times that the CS and PS services in the CS+PS combined service are
normally released at the same time in the best cell........................................................................................................2050
1.10.34.6 Sum of Sampled Values of Downlink BE Service Throughputs for All DCH PS UEs for a Best Cell
........................................................................................................................................................................................2052
1.10.34.7 Total Number of Times Sampled Values of Downlink BE Service Throughputs for All DCH PS UEs for a Best
Cell Are Not 0.................................................................................................................................................................2053
1.10.34.8 Erlang of CS Services for Cell.......................................................................................................................2054
1.10.35 Measurement related to RLC per cell(RLC.Cell)..............................................................................................2055
1.10.35.1 Number of Downlink Service PDUs Retransmitted on AM RLC (L2 Enhancement)...................................2057
1.10.35.2 Number of Downlink Service PDUs Sent on AM RLC.................................................................................2058
1.10.35.3 Number of Downlink Signaling PDUs Sent on AM RLC..............................................................................2059
1.10.35.4 Number of Downlink Service PDUs Retransmitted on AM RLC..................................................................2060
1.10.35.5 Number of Downlink Signaling PDUs Retransmitted on AM RLC..............................................................2061
1.10.35.6 Number of Downlink Service PDUs Discarded on AM RLC........................................................................2062
1.10.35.7 Number of Downlink Signaling PDUs Discarded on AM RLC....................................................................2063
1.10.36 RRC connection release measurement per cell(RRC.Rel.Cell).........................................................................2064
1.10.36.1 Counters Related to the Number of RRC Connection Releases on DCCH due to Different Causes.............2066
1.10.36.2 Counters Related to the Number of RRC Connection Releases on CCCH due to Different Causes.............2069
1.10.36.3 Number of RRC Connection Releases due to Cell Update Failure in the Case of RL Failure......................2071
1.10.36.4 Number of RRCs Released due to PS Data session end.................................................................................2073
1.10.37 RRC connection setup measurement per cell(RRC.Setup.Cell)........................................................................2074
1.10.37.1 Number of RRC Connection Setup Attempts with DRD out.........................................................................2095
1.10.37.2 Number of Successful RRC Connection Setups with DRD Out....................................................................2096
1.10.37.3 Number of RRC Connection Setup Attempts with DRD in...........................................................................2098
1.10.37.4 Counters Related to Duration of RRC Connection Setup on CELL_DCH....................................................2099
1.10.37.5 Counters Related to the Number of RRC Connection Requests for Various Reasons...................................2101
1.10.37.6 Counters Related to the Number of Successful RRC Connection Setups for Various Reasons....................2107
1.10.37.7 Number of RRC Connection Setup Messages Sent from RNC to UE...........................................................2112
1.10.37.8 Counters Related to the Number of Successful RRC Connection Setups......................................................2114
1.10.37.9 Counters Related to the Number of Processed RRC Connection Requests...................................................2116
1.10.37.10 Number of Successful RRC Connection Setups with Repeated RRC Connection Request Messages from UE
........................................................................................................................................................................................2118
1.10.37.11 Number of Automatic DSACs Triggered by Congestion on Iu Interface....................................................2120
1.10.38.8 Number of RRC Connection Rejects (Transmission Setup Failure on Iub Interface )..................................2177
1.10.38.9 Number of RRC Connection Rejects..............................................................................................................2178
1.10.38.10 Number of Distance-Based RRC Redirections for Cell...............................................................................2179
1.10.38.11 Number of Discarded RRC Connection Requests Due to Various Flow Control Functions.......................2181
1.10.38.12 Number of RRC Connection Requests of Different Priorities Discarded During RAN Integrated Flow Control
for Cell............................................................................................................................................................................2181
1.10.38.13 Number of Distance-Based RRC Inter-frequency Redirections for Cell.....................................................2183
1.10.38.14 Number of RRC Connection Rejects Due to NodeB Resource Unavailable...............................................2184
1.10.39 RRC state measurement<Cell>(RRC.State.Cell)..............................................................................................2186
1.10.39.1 Counters Related to the Number of UEs in Different RRC Connection States..............................................2186
1.10.40 Cell TX and RX Power Measurement per cell(RTWPTCP.Cell).....................................................................2187
1.10.40.1 Received Total Wideband Power for cell.......................................................................................................2189
1.10.40.2 Transmitted Power of Carrier for Cell............................................................................................................2190
1.10.40.3 Transmitted Power of Non-HSDPA Carrier for Cell.....................................................................................2192
1.10.40.4 Power Required by HS-DSCH for Cell..........................................................................................................2193
1.10.40.5 Received Scheduled E-DCH Power Share in the Measurement Period for Cell............................................2195
1.10.40.6 Maximum Power Required for Free HSDPA Users for Cell.........................................................................2196
1.10.40.7 Average Power Required for Free HSDPA Users for Cell.............................................................................2197
1.10.41 Soft Handover Measurement per cell(SHO.Cell)..............................................................................................2198
1.10.41.1 Number of Radio Link Addition Attempts in Softer Handover.....................................................................2204
1.10.41.2 Number of Successful Radio Link Additions in Softer Handover.................................................................2205
1.10.41.3 Counters Related to the Number of Failed Radio Link Additions in Softer Handover due to Different Causes
........................................................................................................................................................................................2206
1.10.41.4 Number of Failed Radio Link Additions in Softer Handover due to UE No Response.................................2208
1.10.41.5 Number of Radio Link Deletion Attempts in Softer Handover......................................................................2209
1.10.41.6 Number of Successful Radio Link Deletions in Softer Handover..................................................................2211
1.10.41.7 Number of Radio Link Addition Attempts in Soft Handover........................................................................2212
1.10.41.8 Number of Successful Radio Link Additions in Soft Handover....................................................................2214
1.10.41.9 Counters Related to the Number of Failed Radio Link Additions in Soft Handover due to Different Causes
........................................................................................................................................................................................2216
1.10.41.10 Number of Failed Radio Link Additions in Soft Handover due to UE No Response..................................2217
1.10.41.11 Number of Radio Link Deletion Attempts in Soft Handover.......................................................................2219
1.10.41.12 Number of Successful Radio Link Deletions in Soft Handover...................................................................2220
1.10.41.13 Number of Soft Handover Attempts with only Signaling Connection.........................................................2222
1.10.41.14 Number of Successful Soft Handovers with only Signaling Connection.....................................................2223
1.10.41.15 Number of Soft Handover Decisions for Radio Link Addition Initiated by RNC.......................................2225
1.10.41.16 These counters provide the number of soft handover attempts in different service types in the target cell
........................................................................................................................................................................................2227
1.10.41.17 Counters Related to the Number of Successful Soft Handovers in Different Service Types.......................2229
1.10.41.18 Mean Number of UEs with One Radio Link................................................................................................2231
1.10.41.19 Mean Number of UEs with Two Radio Links..............................................................................................2231
1.10.41.20 Mean Number of UEs with Three Radio Links............................................................................................2232
1.10.41.21 Mean Number of UEs with Four Radio Links.............................................................................................2233
1.12.1.3 Number of Failed Soft Handovers Between Neighboring Cells Due to No Response from UE.....................2416
1.12.1.4 Number of Hard Handover Attempts Between Neighboring Cells..................................................................2417
1.12.1.5 Number of Successful Hard Handovers Between Neighboring Cells..............................................................2419
1.12.1.6 Number of Failed Hard Handovers Between Neighboring Cells Due to No Response from UE....................2420
1.12.1.7 Number of RL Addition Attempts in Soft Handover Between Neighboring Cells..........................................2421
1.12.1.8 Number of Successful RL Additions in Soft Handover Between Neighboring Cells......................................2423
1.12.1.9 Number of RL Deletion Attempts in Soft Handover Between Neighboring Cells..........................................2424
1.12.1.10 Number of Successful RL Deletions in Soft Handover Between Neighboring Cells....................................2426
1.12.1.11 Number of Hard Handover Attempts from HS-DSCH to HS-DSCH Between Neighboring Cells...............2427
1.12.1.12 Number of Successful Hard Handovers from HS-DSCH to HS-DSCH Between Neighboring Cells...........2429
1.12.1.13 Number of HSDPA Serving Cell Change Attempts Between Neighboring Cells.........................................2430
1.12.1.14 Number of Successful HSDPA Serving Cell Changes Between Neighboring Cells.....................................2432
1.12.1.15 Number of CS Domain Outgoing Inter-Cell Hard Handover Attempts Between Neighboring Cells............2434
1.12.1.16 Number of Successful CS Domain Outgoing Hard Handovers Between Neighboring Cells........................2437
1.12.1.17 Number of Failed CS Domain Hard Handovers According to Different Causes Between Neighboring Cells
........................................................................................................................................................................................2439
1.12.1.18 Number of PS Domain Outgoing Inter-Cell Hard Handover Attempts Between Neighboring Cells............2443
1.12.1.19 Number of Successful PS Domain Outgoing Hard Handovers Between Neighboring Cells.........................2445
1.12.1.20 Number of Failed PS Domain Hard Handovers According to Different Causes Between Neighboring Cells
........................................................................................................................................................................................2447
1.12.1.21 Number of Outgoing SRNS Relocation Executions with HHO Between Neighboring Cells.......................2451
1.12.1.22 Number of Successful Outgoing SRNS Relocations with HHO Between Neighboring Cells......................2452
1.12.1.23 Number of Failed CS Domain Outgoing SRNS Relocation with HHO Preparations According to Different Causes
Between Neighboring Cells............................................................................................................................................2454
1.12.1.24 Number of Failed PS Domain Outgoing SRNS Relocation with HHO Preparations According to Different Causes
Between Neighboring Cells............................................................................................................................................2455
1.13 Measurement of UMTS DSP Performance(UDSP)...............................................................................................2457
1.13.1 Measurement related to DSP performance(DSP)................................................................................................2457
1.13.1.1 Uplink PS Traffic Handled by the DSP............................................................................................................2458
1.13.1.2 Downlink PS Traffic Handled by the DSP.......................................................................................................2459
1.13.1.3 Measurement of the DSP Usage in a Period.....................................................................................................2460
2.6.1.1 Number of IP Connection Setup Requests Received on Dual-Stack Transport Adjacent Node........................2530
2.6.1.2 Number of Successful IP Connection Setups on the Dual-Stack Transport Adjacent Node..............................2531
2.6.1.3 Number of IP Connection Modifications on the Dual-Stack Transport Adjacent Node....................................2532
2.6.1.4 Number of Successful IP Connection Modifications on the Dual-Stack Transport Adjacent Node..................2532
2.6.1.5 Number of IP Connection Releases on the Dual-Stack Transport Adjacent Node............................................2533
2.6.1.6 Number of Active IP Connections on the Dual-Stack Transport Adjacent Node..............................................2534
2.6.1.7 IP Path Forward Bandwidth Allocated to a Dual-Stack Transport Adjacent Node...........................................2535
2.6.1.8 IP Path Backward Bandwidth Allocated to a Dual-Stack Transport Adjacent Node.........................................2536
2.6.2 Dual-Stack Transport Adjacent Node Measurement(QAAL2IP)..........................................................................2537
2.6.2.1 Number of Requests for Resource Allocations by Dual-Stack Transport Adjacent Node.................................2537
2.6.2.2 Number of Successful Resource Allocations to Dual-Stack Transport Adjacent Node.....................................2538
2.6.2.3 Number of Failed Resource Allocations Due to Insufficient Bandwidth on the Dual-Stack Transport Adjacent Node
........................................................................................................................................................................................2539
2.6.3 Dual-Stack Transport Adjacent Node QAAL2 Part Measurement(QAAL2PART).............................................2540
2.6.3.1 Number of RLC messages received by the QAAL2 on Dual-Stack Adjacent Node.........................................2546
2.6.3.2 Number of RLC messages sent by the QAAL2 on Dual-Stack Adjacent Node................................................2547
2.6.3.3 Number of AAL2 Connection Establishment Requests Sent by the QAAL2 on Dual-Stack Adjacent Node
........................................................................................................................................................................................2549
2.6.3.4 Number of AAL2 Connection Establishment Requests Received by the QAAL2 on the Dual-Stack Adjacent Node
........................................................................................................................................................................................2551
2.6.3.5 Number of AAL2 Connection Establishment Request Rejections Received by the QAAL2 on the Dual-Stack
Adjacent Node................................................................................................................................................................2552
2.6.3.6 Number of AAL2 Connection Establishment Confirmations Received by the QAAL2 on Dual-Stack Adjacent
Node................................................................................................................................................................................2553
2.6.3.7 Number of AAL2 Connection Establishment Confirmations Sent by the QAAL2 on Dual-Stack Adjacent Node
........................................................................................................................................................................................2555
2.6.3.8 Number of RLC Messages Sent by QAAL2 on Dual-Stack Adjacent Node after the QAAL2 Receives the
Connection ERQ Message..............................................................................................................................................2556
2.6.3.9 Number of AAL2 Connection Releases Initiated by QAAL2 on Dual-Stack Adjacent Node...........................2558
2.6.3.10 Number of AAL2 Connection Releases Received by the QAAL2 on Dual-Stack Adjacent Node.................2559
2.6.3.11 Number of AAL2 Connection Confirmations Received by the QAAL2 on Dual-Stack Adjacent Node........2561
2.6.3.12 Number of AAL2 Connection Releases Confirmation Initiated by the QAAL2 on the Dual-Stack Adjacent Node
........................................................................................................................................................................................2562
2.6.3.13 Number of AAL2 Connection Modification Request Rejections Received by the QAAL2 on the Dual-Stack
Adjacent Node................................................................................................................................................................2564
2.6.3.14 Number of AAL2 Connection Modification Rejections Sent by the QAAL2 on Dual-Stack Adjacent Node
........................................................................................................................................................................................2565
2.6.3.15 Number of AAL2 Connection Modification Requests Sent by the QAAL2 on Dual-Stack Adjacent Node
........................................................................................................................................................................................2567
2.6.3.16 Number of AAL2 Connection Modification Requests Received by the QAAL2 on Dual-Stack Adjacent Node
........................................................................................................................................................................................2568
2.6.3.17 Average Number of QAAL2 Connections to Dual-Stack Adjacent Node.......................................................2568
2.6.3.18 Counters Related to Average QAAL2 Bandwidth Allocated to Iub Adjacent Node on Dual-Stack Adjacent Node
........................................................................................................................................................................................2569
2.7 Measurement of ATM Logical Port Performance(ATM_LOGIC_PORT)..............................................................2570
2.7.1 ATM Logical Port Measurement(ATM.LOGIC.PORT).......................................................................................2570
2.13.1.1 Counters Related to the Number of Cells Received, Transmitted or Discarded on an Fractional IMA Link
........................................................................................................................................................................................2617
2.13.1.2 Counters Related to the Receive Rate or Transmit Rate of an Fractional IMA Link.......................................2619
2.14 Measurement of IMA Group Performance(IMAGRP)...........................................................................................2621
2.14.1 IMA Group Measurement(IMAGRP).................................................................................................................2621
2.14.1.1 Counters Related to the Number of Cells Received or Transmitted on an IMA Group...................................2625
2.14.1.2 Counters Related to the Receive Rate or Transmit Rate of an IMA Group.....................................................2626
2.14.1.3 Counters Related to the Number of Error Cells Received or Transmitted on an IMA Group.........................2628
2.14.1.4 Counters related to the Occupied Forward Bandwidth or Occupied Backward Bandwidth of an IMA Group
........................................................................................................................................................................................2629
2.14.1.5 Counters Related to the Number of Congestions on an IMA Group................................................................2630
2.14.1.6 Counters Related to the Duration of Congestion on an IMA Group................................................................2631
2.15 Measurement of IMA Link Performance(IMALNK).............................................................................................2632
2.15.1 IMA Link Measurement(IMALNK)...................................................................................................................2632
2.15.1.1 Counters Related to the Number of Packets Received or Transmitted on an IMA Link.................................2635
2.15.1.2 Counters Related to the Receive Rate or Transmit Rate of an IMA Link........................................................2637
2.15.1.3 Number of Times That a Fault Occurs in an IMA Link...................................................................................2639
2.15.1.4 Number of Times That a Fault Is Cleared in an IMA Link..............................................................................2640
2.15.1.5 Duration of Faults in an IMA Link...................................................................................................................2640
2.16 Measurement of IPoA Link Performance(IPOALNK)...........................................................................................2641
2.16.1 IPoA Link Measurement(IPOALNK).................................................................................................................2641
2.16.1.1 Counters Related to the Number of Cells Received or Transmitted Correctly on An IPoA Link...................2644
2.16.1.2 Counters Related to the Number of Bytes Received or Transmitted on an IPoA Link....................................2645
2.16.1.3 Counters Related to the Maximum Receive Rate or the Maximum Transmit Rate of an IPoA Link..............2646
2.16.1.4 Counters Related to the Number of Cells Discarded on an IPoA Link............................................................2647
2.17 Measurement of VCL PM on an IPOAPVC link(IPOAPVC_VCLPM)................................................................2648
2.17.1 Measurement Related to VCL PM on an IPOAPVC link(IPOAPVC.VCLPM).................................................2648
2.17.1.1 Number of VCL PM Cells on an IPOAPVC link.............................................................................................2650
2.17.1.2 Maximum Data Rate of VCL PM on an IPOAPVC link.................................................................................2651
2.17.1.3 VCL PM Cell Discard Rate on an IPOAPVC link...........................................................................................2652
2.17.1.4 Rate of Incorrectly Inserted VCL PM Cells on an IPOAPVC link..................................................................2654
2.17.1.5 Number of Error VCL PM Cell Blocks Failed BIP16 Check on an IPOAPVC link.......................................2655
2.18 Measurement of IP Path Performance(IPPATH)...................................................................................................2657
2.18.1 IP Path Link Measurement(IPPATH)..................................................................................................................2657
2.18.1.1 Number of Active Connections on an IP Path..................................................................................................2658
2.18.1.2 Average IP Path Ping Delay.............................................................................................................................2659
2.18.1.3 Maximum IP Path Ping Delay..........................................................................................................................2660
2.18.1.4 Average IP Path Ping Delay Variation.............................................................................................................2661
2.18.1.5 Maximum IP Path Ping Delay Variation..........................................................................................................2662
2.18.1.6 Average IP Path Ping Packet Loss Rate...........................................................................................................2663
2.18.1.7 Maximum IP Path Ping Packet Loss Rate........................................................................................................2664
2.18.1.8 Counters Related to the Number of Congestions on an IP Path.......................................................................2665
2.18.1.9 Counters Related to the Duration of Congestion on an IP Path.......................................................................2666
2.47.1.4 Number of Frames That Are Transmitted, Received, or Discarded by the Trunk Group................................2909
2.48 Measurement of UNI Link Performance(UNILNK)..............................................................................................2911
2.48.1 Measurement related to UNI link(UNILNK)......................................................................................................2911
2.48.1.1 Counters Related to the Number of Cells Received or Transmitted on a UNI Link........................................2914
2.48.1.2 Counters Related to the Receive Rate or Transmit Rate of a UNI Link...........................................................2915
2.48.1.3 Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to a UNI Link..........................2916
2.48.1.4 Measurement of the Number of Congestions on a UNI Link...........................................................................2917
2.48.1.5 Measurement of the Duration of Congestion on an UNI Link.........................................................................2918
2.49 Measurement of VC Cross Performance(VCACROSS)........................................................................................2919
2.49.1 VCACROSS Measurement(VCACROSS)..........................................................................................................2919
2.49.1.1 Measurement of the Number of Bytes Received or Transmitted on a VCCROSS Link..................................2923
2.49.1.2 Measurement of the Number of Cells Received or Transmitted on a VCCROSS Link...................................2924
2.49.1.3 Counters Related to the Receive Rate or Transmit Rate of a VC Cross Connection.......................................2926
Measurement Units
Unit Description
Overview
Measurement is used to measure active algorithm of RNC for each Operator.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
1.1.1.1 Number of TRBs of HSDPA Service on Which Packet Inspection (PI) Takes
Effect for RNC
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
ID Counter Description
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 Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Overview
This measurement unit 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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement items take statistics of the number of normally released RABs of different
type services for each Operator.
Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
1.1.4.4 Maximum Uplink Traffic of R99 PS Domain of RNC for each Operator
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
1.1.4.6 Maximum Downlink Traffic of R99 PS Domain of RNC for each Operator
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
1.1.4.10 Maximum Uplink Traffic of HSUPA PS Domain of RNC for each Operator
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
1.1.4.11 Downlink Traffic of MBMS or IMB PS Domain of RNC for each Operator
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
1.1.4.12 Maximum Downlink Traffic of MBMS or IMB PS Domain of RNC for each
Operator
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
1.1.4.13 Equivalent Erlang of CS Domain AMR Service of RNC for each Operator
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
1.1.4.17 Average Total Throughput of UL and DL PS Services per Operator for RNC
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
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.
Measurement Units
Unit Description
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 CS-
domain 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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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,
the measurement is triggered in the CPUS subsystem.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.2.1.8 Number of CBS Requests Discarded Due to Flow Control for CPUS
Subsystem
Measurement Counters
ID Counter Description
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
times
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
1.2.1.10 Number of Paging Messages Discarded Due to Flow Control for CPUS
Subsystem
Measurement Counters
ID Counter Description
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
times
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
1.2.1.12 Number of Cell Update Requests Discarded Due to Flow Control for CPUS
Subsystem
Measurement Counters
ID Counter Description
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
times
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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 Feature ID Feature Name
1.2.1.15 Number of Various Priority RRC Requests Discarded Due to Flow Control
for CPUS Subsystem
Measurement Counters
ID Counter Description
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
times
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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
1. 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. 2. Measurement of the counter
VS.Traffic.Report4A.CellDch.Disc.Num.DownLink.FC is triggered when the RNC discards the
event 4A measurement report received from MAC-d on PS BE traffic in the CELL_DCH state.
The measurement report is discarded if flow control is performed on DCCC.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
1. 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. 2. Measurement of the counter
VS.Traffic.Report4A.CellFach.Disc.Num.DownLink.FC is triggered when the RNC discards
the event 4A measurement report received from MAC-d on traffic produced by 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of RRC CONNECTION REQUEST messages in a CPUS
subsystem 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 CPUS subsystem.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
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 CPUS subsystem.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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). This counter is incremented by one 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 from neighboring RNC and discards the message due to CPU overload in the CPUS:
RADIO LINK SETUP REQUEST,PAGING REQUEST,COMMON TRANSPORT
CHANNEL RESOURCES REQUEST. this counter is incremented by one if the downlink
signaling messages discarded during flow control caused by central processing unit (CPU)
overload in a CPUS.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Units
Unit Description
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
This counter provides the number of data packets sent by the GTP-U at the local end.
Measurement point
This counter is incremented by one each time the GTP-U at the local end sends a data packet to
the GTP-U at the peer end.
Formula
None
Unit
packet
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the total number of data packets and control packets received by the GTP-
U at the local end.
Measurement point
This counter is incremented by one each time the GTP-U at the local end receives a data packet
or control packet from the GTP-U at the peer end.
Formula
None
Unit
packet
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of bytes in the data packets sent by the GTP-U at the local
end.
Measurement point
This counter is measured when the GTP-U at the local end sends a data packet to the GTP-U at
the peer end.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the total number of bytes in the data packets and control packets received
by the GTP-U at the local end.
Measurement point
This counter is measured when the GTP-U at the local end receives a data packet or control
packet from the GTP-U at the peer end.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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
None
Related Features
None
Measurement Counters
ID Counter Description
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
None
Related Features
None
Measurement Counters
ID Counter Description
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
None
Related Features
None
Measurement Counters
ID Counter Description
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
None
Related Features
None
Measurement Counters
ID Counter Description
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
None
Related Features
None
Measurement Counters
ID Counter Description
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
None
Related Features
None
Measurement Units
Unit Description
Unit Description
Overview
This measurement unit 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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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-21 CS domain reset procedure initiated by the RNC (successful operation)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter takes statistics of the number of RESET messages that the CS 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 a
RESET message from the CS domain, it measures this counter.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter takes statistics of the number of IU RELEASE COMMAND
messages that the CS domain sends to the RNC. The RNC measures this counter according to
the CN nodes. The Iu release procedure of the CS 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 CS domain,
the RNC measures this counter.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter takes statistics of the number of ERROR INDICATION messages
that the CS 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 CS domain, it measures this counter according to the
CN nodes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
These measurement counters take statistics of the number of IU RELEASE COMMAND
messages that the RNC receives from the CS domain for different Iu connection release causes
according to respective CN nodes.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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 Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter provides the number of initial UE messages discarded under the flow
control when the Iu interface receives the CS initial UE 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter provides the number of PAGING messages that the CS 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 CS domain.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of RAN INFORMATION REQUEST messages received by
the RNC.
Measurement point
The measurement is triggered at point A shown in the following figure. This counter is increased
by one when the RNC receives a RAN INFORMATION REQUEST message from the CN.
Figure 1-35 Procedure for directly sending messages over the Iu interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of RAN INFORMATION messages sent by the RNC.
Measurement point
The measurement is triggered at point B shown in the following figure. This counter is increased
by one when the RNC sends a RAN INFORMATION message to the CN.
Figure 1-36 Procedure for directly sending messages over the Iu interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
This counter provides the number of DL payload bytes of CS Conversational service data on the
Iu-CS interface received by the RNC.
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. The value of the counter does not include
the number of bytes of IUUP headers.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of DL payload bytes of CS streaming service data on the Iu-
CS interface received by the RNC.
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. The value of the counter does not include
the number of bytes of IUUP headers.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of UL payload bytes of CS Conversational service data on the
Iu-CS interface sent by the RNC.
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. The value of the counter does not
include the number of bytes of IUUP headers.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of UL payload bytes of CS streaming service data on the Iu-
CS interface received by the RNC.
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. The value of the counter does not include
the number of bytes of IUUP headers.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.4.3.3 Number of MBMS or IMB Service Setup Failures on the Iu Interface Due to
Different Causes
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Overview
This measurement unit of "Iu interface MOCN measurement" is used to measure the number of
Redirect when the RAN supports the multiple operator core network (MOCN).
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
1.4.5.1 Number of Location Area Update Requests Forwarded by the RNC to the
CN
Measurement Counters
ID Counter Description
Description
This counter provides the number of location area update requests forwarded by the RNC to the
CN.
Measurement point
The measurement is triggered when the RNC forwards to the CN an INITIAL UE MESSAGE
or DIRECT TRANSFER message from a UE and determines that this message is a location area
update request based on the message decoding result. In this case, this counter is incremented
by one in the corresponding CN node.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.4.5.2 Number of Accepted Location Area Update Requests Received by the RNC
from the CN
Measurement Counters
ID Counter Description
Description
This counter provides the number of accepted location area update requests received by the RNC
from the CN.
Measurement point
The measurement is triggered when the RNC forwards to a UE a DIRECT TRANSFER message
sent by the CN and determines that this is a location area update accept message based on the
message decoding result. In this case, this counter is incremented by one in the corresponding
CN node.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.4.5.3 Number of Accepted Routing Area Update Requests Received by the RNC
from the CN
Measurement Counters
ID Counter Description
Description
This counter provides the number of accepted routing area update requests received by the RNC
from the CN.
Measurement point
The measurement is triggered when the RNC forwards to a UE a DIRECT TRANSFER message
sent by the CN and determines that this is a routing area update accept message based on the
message decoding result. In this case, this counter is incremented by one in the corresponding
CN node.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of attach requests forwarded by the RNC to the CN.
Measurement point
The measurement is triggered when the RNC forwards to the CN an INITIAL UE MESSAGE
or DIRECT TRANSFER message from a UE and determines that this message is an attach
request based on the message decoding result. In this case, this counter is incremented by one
in the corresponding CN node.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.4.5.5 Number of Accepted Attach Requests Received by the RNC from the CN
Measurement Counters
ID Counter Description
Description
This counter provides the number of accepted attach requests received by the RNC from the CN.
Measurement point
The measurement is triggered when the RNC forwards to a UE a DIRECT TRANSFER message
sent by the CN and determines that this is an attach accept message based on the message
decoding result. In this case, this counter is incremented by one in the corresponding CN node.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of PDP activation requests forwarded by the RNC to the CN.
Measurement point
The measurement is triggered when the RNC forwards to the CN an INITIAL UE MESSAGE
or DIRECT TRANSFER message from a UE and determines that this message is a packet data
protocol (PDP) activation request based on the message decoding result. In this case, this counter
is incremented by one in the corresponding CN node.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.4.5.7 Number of Accepted PDP Activation Requests Received by the RNC from
the CN
Measurement Counters
ID Counter Description
Description
This counter provides the number of accepted PDP activation requests received by the RNC
from the CN.
Measurement point
The measurement is triggered when the RNC forwards to a UE a DIRECT TRANSFER message
sent by the CN and determines that this is a packet data protocol (PDP) activation accept message
based on the message decoding result. In this case, this counter is incremented by one in the
corresponding CN node.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of service setup requests forwarded by the RNC to the CN.
Measurement point
The measurement is triggered when the RNC forwards to the CN an INITIAL UE MESSAGE
or DIRECT TRANSFER message sent by a UE and determines that this message is a service
setup request based on the message decoding result. In this case, this counter is incremented by
one in the corresponding CN node.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.4.5.9 Number of Rejected Service Setup Requests Received by the RNC from the
CN
Measurement Counters
ID Counter Description
Description
This counter provides the number of rejected service setup requests received by the RNC from
the CN.
Measurement point
The measurement is triggered when the RNC forwards to a UE a DIRECT TRANSFER message
sent by the CN and determines that the CN has rejected the service setup request based on the
message decoding result. In this case, this counter is incremented by one in the corresponding
CN node.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of authentication requests received by the RNC from the CN.
Measurement point
The measurement is triggered when the RNC forwards to a UE 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of authentication responses forwarded by the RNC to the CN.
Measurement point
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of SECURITY MODE COMMAND messages received by
the RNC from the CN.
Measurement point
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of SECURITY MODE COMPLETE messages forwarded by
the RNC to the CN.
Measurement point
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.4.5.14 Number of Routing Area Update Requests Forwarded by the RNC to the
CN
Measurement Counters
ID Counter Description
Description
This counter provides the number of routing area update requests forwarded by the RNC to the
CN.
Measurement point
The measurement is triggered when the RNC forwards to the CN an INITIAL UE MESSAGE
or DIRECT TRANSFER message from a UE and determines that this message is a routing area
update request based on the message decoding result. In this case, this counter is incremented
by one in the corresponding CN node.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Overview
This measurement unit 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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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-41 PS domain reset procedure initiated by the RNC (successful operation)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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 Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter provides the number of initial UE messages discarded under the
SCCP flow control when the Iu interface receives the PS initial UE 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-PS interface
is under flow control. Then, the RNC does not send the INITIAL UE MESSAGE message to
the CN.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of UL payload bytes of PS streaming 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 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of UL payload bytes of PS interactive 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 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of UL payload bytes of PS background 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 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of DL payload bytes of PS streaming 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 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of DL payload bytes of PS interactive 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 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of DL payload bytes of PS background 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 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the total number of bytes of downlink HTTP traffic data received on the
Iu-PS interface of the RNC. The value of this counter includes the bytes of application layer data
without GTPU head.
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the total number of bytes of downlink P2P traffic data received on the Iu-
PS interface of the RNC. The value of this counter includes the bytes of application layer data
without GTPU head.
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the total number of bytes of all downlink subscribed service data received
on the Iu-PS interface of the RNC. The value of this counter includes the bytes of application
layer data without GTPU head.
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the total number of bytes of all downlink undefined service data received
on the Iu-PS interface of the RNC. The value of this counter includes the bytes of application
layer data without GTPU head.
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 Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
1.4.8.1 Number of SCCP Connection Requests Sent by the RNC to the CN Through
the Iu Interface
Measurement Counters
ID Counter Description
Description
This counter provides the number of SCCP connection requests sent by the RNC to the CN.
Measurement point
In the measurement period, the counter is incremented by one when the RNC RANAP sends a
SCCP connection request (CR) message to the CN.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.4.8.2 Number of Successful SCCP Connection Requests Sent by the RNC to the
CN Through the Iu Interface
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful SCCP connection requests sent by the RNC to
the CN.
Measurement point
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.4.8.3 Number of SCCP Connection Requests Received by the RNC from the CN
Through the Iu Interface
Measurement Counters
ID Counter Description
Description
This counter provides the number of SCCP connection requests received by the RNC from the
CN.
Measurement point
In the measurement period, the counter is incremented by one when the RNC RANAP receives
a SCCP CR message from the CN.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful SCCP connection requests received by the RNC
from the CN.
Measurement point
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Units
Unit Description
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of ERROR INDICATION messages
received by the RNC on the Iur interface.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of ERROR INDICATION messages sent
by the RNC on the Iur interface.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Figure 1-57 Radio Link setup procedure on the Iur interface (successful operation)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-58 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.
Figure 1-59 Radio Link setup procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Description
Counter Description
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-60 Radio Link setup procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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..
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-65 Radio Link addition procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.1.10 Number of Failed Radio Links Additions by DRNC on Iur Interface for
Different Causes
Measurement Counters
ID Counter Description
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 Description
Counter Description
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.
Figure 1-66 Radio Link addition procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Description
Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.1.14 Number of Radio Links with Reconfiguration Canceled by the DRNC over
Iur
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.1.16 Number of Failed Radio Links on Iur Interface for Different Causes
Measurement Counters
ID Counter Description
ID Counter Description
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 Description
Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-74 Common transport channel resources initialization procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Figure 1-75 Common transport channel resources initialization procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-76 Common transport channel resources failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Figure 1-77 Common transport channel resources release procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
ID Counter Description
Description
Reserved counters for Iur interface.
Measurement point
Reserved counters for Iur interface.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
1.5.3.1 Number of SCCP Connection Requests Sent by the Local RNC to the Peer
RNC Through the Iur Interface
Measurement Counters
ID Counter Description
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-78 SCCP connection requests sent by the local RNC to the peer RNC
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.3.2 Number of Successful SCCP Connection Requests Sent by the Local RNC
to the Peer RNC Through the Iur Interface
Measurement Counters
ID Counter Description
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-79 Successful SCCP connection requests sent by the local RNC to the peer RNC
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.3.3 Number of SCCP Connection Requests Received by the Local RNC from the
Peer RNC Through the Iur Interface
Measurement Counters
ID Counter Description
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.
Figure 1-80 SCCP connection requests received by the local RNC from the peer RNC
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-81 Successful SCCP connection requests received by the local RNC from the peer
RNC
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
VS.SHO.FailRLSetupIur.Cong.Rx VS.SHO.FailRLSetupIur.TransCong.Rx
VS.SHO.FailRLAddIur.Cong.Rx VS.SHO.FailRLAddIur.TransCong.Rx
Measurement Counters
ID Counter Description
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.
Figure 1-82 Radio Link setup procedure on the Iur interface (successful operation)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-83 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.
Figure 1-84 Radio Link setup failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.4.3 Number of Failed Radio Link Establishments by SRNC on Iur Interface for
Different Causes
Measurement Counters
ID Counter Description
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 Description
Counter Description
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-85 Radio Link setup failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.4.5 Number of Successful deleted Radio Links on Iur Interface for SRNC
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-88 Radio Link addition procedure on the Iur interface (successful operation)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-89 Radio Link addition 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 ADDITION FAILURE message from the DRNC and if there are successfully
added radio links, the SRNC measures this item on each Iur interface.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.4.8 Number of Failed Radio Link Additions for Different Causes on Iur
Interface for SRNC
Measurement Counters
ID Counter Description
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 Description
Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-92 Synchronized radio link reconfiguration procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Figure 1-93 Synchronized radio link reconfiguration commit procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Description
Counter Description
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-94 Synchronized radio link reconfiguration procedure on the Iur interface (failed
operation)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.4.14 Number of Failed Radio Links of SRNC on Iur Interface for Different
Causes
Measurement Counters
ID Counter Description
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 Description
Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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. When the SRNC sends a
COMMON TRANSPORT CHANNEL RESOURCES REQUEST message on the Iur interface,
the SRNC measures this item on each Iur interface.
Figure 1-100 Initialization procedure of common transport channel resources on the Iur interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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. When the SRNC receives a
COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message on the Iur
interface, the SRNC measures this item on each Iur interface.
Figure 1-101 Initialization procedure of common transport channel resources on the Iur interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-102 Common transport channel resource failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Figure 1-103 Common transport channel resource release procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.4.22 Number of PS RABs Normally Released on CCH (FACH or PCH) for SRNC
(Iur Interface)
Measurement Counters
ID Counter Description
Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.4.27 Number of Normally Released HSPA RABs on Iur Interface for SRNC
Measurement Counters
ID Counter Description
Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.4.30 Number of RLs with Reconfiguration Canceled by the SRNC over Iur
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.4.35 Number of RRC Connection Releases (CCCH) Sent by the SRNC over the
Iur Interface due to DSCR
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.5.4.36 Number of RRC Connection Releases (DCCH) Sent by the SRNC over the
Iur Interface due to DSCR
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
1.5.5.6 Number of Bytes of DL CS Services Sent by SRNC over DCH on Iur Interface
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Units
Unit Description
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Units
Unit Description
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
These counters provide the number of uplink or downlink congestions on the Iub Interface of
the NodeB.
Measurement point
The RNC measures the corresponding counter when it detects that the Iub interface of a NodeB
changes from non-congested to congested on the uplink or downlink in a measurement period.
Note: When the residual bandwidth on the Iub interface is smaller than the reserved congestion
bandwidth threshold, it indicates that congestion occurs on the Iub interface.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the duration for which the Iub interface of a NodeB is congested on the
uplink or downlink.
Measurement point
The durations for which the Iub interface is congested on the uplink and downlink are
accumulated in the measurement period separately.
Formula
None
Unit
s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item 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: (1) The NodeB fails;
(2) NodeB is blocked.
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the duration for which Dynamic Spectrum Sharing (DSS) is activated for
a NodeB.
Measurement point
In a measurement period, measurement of a DSS activation duration starts when a NodeB
receives a spectrum activation command that instructs it in DSS and stops when the NodeB
receives a spectrum deactivation command. At the end of the measurement period, DSS
activation durations are accumulated for a total DSS activation duration.
Formula
None
Unit
s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 every measurement period of 5 seconds when
CE Overbooking is enabled. At the end of each measurement period, the RNC obtains the
maximum and minimum NodeB credit usage. In addition, the RNC divides the accumulated
NodeB credit usage by the number of samples to obtain the average NodeB credit usage in this
measurement period.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Units
Unit Description
Unit Description
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
1.8.1.1 The Average Number of AMR Users with Different UL and DL Rates
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
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 Feature ID Feature Name
1.8.1.2 Number of Times That Silence Is Detected in Downlink for AMR Calls per
RNC
Measurement Counters
ID Counter Description
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
times
Related Features
Counter Feature ID Feature Name
1.8.1.3 Number of Times That Silence Is Detected in Uplink for AMR Calls per
RNC
Measurement Counters
ID Counter Description
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
times
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 intra-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
A VS.IRATHO.AttRelocPrepOutCS.RNC
B VS.IRATHO.SuccRelocPrepOutCS.RNC
C VS.IRATHO.AttOutCS.RNC
D VS.IRATHO.SuccOutCS.RNC
A VS.IRATHO.AttRelocPrepInCS.RNC
B VS.IRATHO.SuccRelocPrepInCS.RNC
C VS.IRATHO.SuccInCS.RNC
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
RAT handover.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 D 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the number of LTE-to-UMTS PS handover 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
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:
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:
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Description
Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.8.5.5 Number of the positioning attempt of the different location method for RNC
Measurement Counters
ID Counter Description
Description
The measurement items take statistics of the number of the positioning attempt 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 determines a positioning
method.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.8.5.6 Number of the successful positioning of the different location method for
RNC
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.8.5.7 Number of the times that the location in SAS centric mode is used in the
RNC
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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".
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.8.6.10 Number of CELL UPDATE Messages from PTT UEs as Paging Response
Received by RNC
Measurement Counters
ID Counter Description
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".
Figure 1-174 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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-175 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 Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 measurement unit and resets the two items. Then the performance measurement
unit 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 measurement unit and resets the two items. Then
the performance measurement unit 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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
measurement unit and resets the two items. Then, the performance measurement unit 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 Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
VS.RAB.AttEstabPS.Bkg.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.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
VS.RAB.AttEstabPS.Str.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.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.8.9.1 Counters Related to the Number of PS RAB Setup Requests for Different
Services
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
ms
Related Features
Counter Feature ID Feature Name
1.8.9.3 Counters Related to the Number of PS RAB Setup Requests for Different
Maximum Downlink Bit rates
Measurement Counters
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.8.9.4 Counters Related to the Number of Successful PS RAB Setups for Different
Maximum Downlink Bit Rates
Measurement Counters
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the average number of PS RABs in the RNC within a measurement period.
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
UE establishes with 0kbps when resource is limited. This measurement item takes statistics of
the times that RAB established successfully with 0kbps for RNC.
Measurement point
The measurement is triggered when a new RAB established successfully with 0kbps.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Overview
Multi-RAB measurement includes:
Measurement of the number of UEs with multiple RABs, Measurement of multi-RAB soft
handover procedures, Measurement of multi-RAB hard handover procedures.
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
A VS.RAB.NormRel.CS.RNC
B VS.RAB.NormRel.CS.UEGen.RNC
C VS.RAB.NormRel.VPLimit.RNC
D VS.RAB.AbnormRel.CS.RNC
E VS.RAB.AbnormRel.CS.RF.RNC
F VS.RAB.AbnormRel.AMR.RNC,
VS.RAB.AbnormRel.CS64.RNC
J VS.RAB.NormRel.PS.RNC
K VS.RAB.NormRel.PS.UEGen.RNC
L VS.RAB.NormRel.PS.0kbps.Timeout.RNC
G VS.RAB.AbnormRel.PS.RNC
H VS.RAB.AbnormRel.PS.RF.RNC
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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
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" or "Network Optimization","UE Generated Signalling
Connection Release ", reference to 3GPP TS 25.413), the RNC measures the items by the CN
domains.
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" or "Network Optimization","UE Generated Signalling
Connection Release ", reference to 3GPP TS 25.413), the RNC measures the items by the CN
domains.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 (with the cause other than
"User Inactivity","Normal Release","Successful Relocation" or "Network Optimization","UE
Generated Signalling Connection Release ", reference to 3GPP TS 25.413), then the
corresponding counter is measured according to the domain types.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These measurement items take statistics of the number of normally released RABs according to
different domains.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These measurement items provide the number of RAB releases due to UE signaling connection
release and the second RRC connection setup for a UE in the RNC according to different
domains.
Note: Second RRC Connection Request: The UE sends a second RRC CONNECTION
REQUEST message to the RNC before releasing the previously assigned RAB.
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 after RABs have
been set up. 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). Upon
reception of the IU RELEASE REQUEST message, the CN sends an IU RELEASE
COMMAND message to the RNC. After receiving this message, the RNC releases the
corresponding RAB and sends an IU RELEASE COMPLETE message to the CN. In this case,
the RNC measures the items based on the service type.
The measurement is triggered at point A as shown in the figure, after receiving an RRC
CONNECTION REQUEST message from a UE, the RNC determines that the message is sent
by the same UE with RAB using a COMMAND ID message sent by the CN,and then 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).Upon reception of the IU
RELEASE REQUEST message, the CN sends an IU RELEASE COMMAND message to the
RNC. After receiving this message, the RNC releases the corresponding RAB and sends an IU
RELEASE COMPLETE message to the CN. In this case, the RNC measures the items based on
the service type.
Figure 1-200 RAB release procedure caused by the second RRC connection setup request from
the same UE
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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" or "Network Optimization","UE Generated Signalling
Connection Release ", reference to 3GPP TS 25.413),the RNC measures the items by the types
of services.
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","UE Generated Signalling
Connection Release ", reference to 3GPP TS 25.413),the RNC measures the items by the types
of services.
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","UE Generated Signalling
Connection Release ", reference to 3GPP TS 25.413),the RNC measures the items by the types
of services.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.8.13.6 Times of PS RAB of 0kbps released for failing to rate up before timer expiry
Measurement Counters
ID Counter Description
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 0kbps expires.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
1.8.16.1 Counters Related to the Average Number of RBs for PS R99 Conversational
Services
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
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 Feature ID Feature Name
1.8.16.2 Counters Related to the Average Number of PS R99 Interactive Service RBs
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
Description
These counters provide the average number of RBs for PS P99 interactive services with different
UL and DL rates.
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 Feature ID Feature Name
1.8.16.3 Counters Related to the Average Number of PS R99 Backgroud Service RBs
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
Description
These counters provide the average number of RBs for PS P99 backgroud services with different
UL and DL rates.
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of directed retry attempts from DCH to HSDPA in the RNC.
Measurement point
The measurement is triggered when the RNC sends the UE a RADIO BEARER SETUP message
or a RADIO BEARER RECONFIGURATION message during the RAB assignment procedure
for the directed retry from DCH to HSDPA.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 when the RNC receives from the UE a RADIO BEARER SETUP
COMMPLETE message or a RADIO BEARER RECONFIGURATION COMMPLETE
message during the RAB assignment procedure for the directed retry from DCH to HSDPA.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.8.16.8 Counters Related to the Average Number of PS R99 Streaming Service RBs
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the average number of RBs for PS P99 streaming services with different
UL and DL rates.
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 Feature ID Feature Name
Overview
TRNC relocation involves two stages: TRNC relocation preparation and TRNC relocation
execution.
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 .
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Figure 1-209 Failed resource allocation for TRNC relocation due to reception of IU release
command
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of failed resource allocations for TRNC relocation according
to different failure causes.
Measurement point
The measurement is triggered at point A as shown in the following figure. During the relocation
preparation, when the resource allocation for TRNC relocation fails, the TRNC sends a
RELOCATION FAILURE message to the CN. In this case, the TRNC measures the related
counter according to different failure causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-211 Reconfiguration procedure during the TRNC relocation (UE involved)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.8.17.5 Number of Relocation Execution Attempts for TRNC (UE Not Involved)
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.8.17.6 Number of Successful Relocation Executions for TRNC (UE Not Involved)
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-214 Reconfiguration procedure during the TRNC relocation (UE involved)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of PS relocation resource allocation attempts initiated by the
TRNC according to different relocation types.
Measurement point
The measurement is triggered at point A as shown in the following figure. When receiving a
RELOCATION REQUEST message from the CN in the PS domain, the TRNC measures the
related counter according to different relocation types.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful PS relocation resource allocations initiated by
the TRNC according to different relocation types.
Measurement point
The measurement is triggered at point B as shown in the following figure. When the resource
allocation for TRNC relocation is complete, the TRNC sends a RELOCATION REQUEST
ACKNOWLEDGE message to the CN in the PS domain. In this case, the TRNC measures the
related counter according to different relocation types.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of failed PS relocation preparations (UE involved) initiated
by the TRNC according to different failure causes.
Measurement point
The measurement is triggered at point A as shown in the following figure. During the PS
relocation preparation (UE involved), when the resource allocation for TRNC relocation fails,
the TRNC sends a RELOCATION FAILURE message to the CN. In this case, the TRNC
measures the related counter according to different failure causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of failed PS relocation preparations (UE not involved)
initiated by the TRNC according to different failure causes.
Measurement point
The measurement is triggered at point A as shown in the following figure. During the PS
relocation preparation (UE not involved), when the resource allocation for TRNC relocation
fails, the TRNC sends a RELOCATION FAILURE message to the CN. In this case, the TRNC
measures the related counter according to different failure causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of CS relocation resource allocation attempts initiated by
the TRNC according to different relocation types.
Measurement point
The measurement is triggered at point A as shown in the following figure. When receiving a
RELOCATION REQUEST message from the CN in the CS domain, the TRNC measures the
related counter according to different relocation types.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful CS relocation resource allocations initiated by
the TRNC according to different relocation types.
Measurement point
The measurement is triggered at point B as shown in the following figure. When the resource
allocation for TRNC relocation is complete, the TRNC sends a RELOCATION REQUEST
ACKNOWLEDGE message to the CN in the CS domain. In this case, the TRNC measures the
related counter according to different relocation types.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of failed CS relocation preparations due to ciphering failure
for the TRNC.
Measurement point
This measurement is triggered at point A as shown in the following figure. During the CS
relocation preparation (UE involved), when the resource allocation for the TRNC relocation
fails, the TRNC sends a RELOCATION FAILURE message to the CN. If the cause value
contained in the message is "Requested Ciphering and/or Integrity Protection Algorithms not
Supported", the TRNC measures this counter.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of failed CS relocation preparations (UE not involved)
initiated by the TRNC according to different failure causes.
Measurement point
The measurement is triggered at point A as shown in the following figure. During the CS
relocation preparation (UE not involved), when the resource allocation for TRNC relocation
fails, the TRNC sends a RELOCATION FAILURE message to the CN. In this case, the TRNC
measures the related counters according to different failure causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
These counters provide the number of CS relocation preparation attempts (UE involved) initiated
by the SRNC according to different triggering 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 domain, if the relocation
request type is "UE Involved", the SRNC measures the related counter according to different
triggering causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of CS relocation preparation attempts initiated by the SRNC
according to the relocation type.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending a
RELOCATION REQUIRED message to the CN in the CS domain, the SRNC measures the
related counter according to different relocation types.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful CS relocations (UE involved) initiated by the
SRNC according to different relocation triggering causes.
Measurement point
The measurement is triggered at point B as shown in the following figure. After the SRNC
initiates a relocation (UE involved), the relocation preparation succeeds if the SRNC receives a
RELOCATION COMMAND message from the CN in the CS domain. In this case, the SRNC
measures the related counter according to different relocation causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful CS relocation preparations initiated by the
SRNC according to the relocation type.
Measurement point
The measurement is triggered at point B as shown in the following figure. After the SRNC
initiates a relocation, the relocation preparation succeeds if the SRNC receives a RELOCATION
COMMAND message from the CN in the CS domain. In this case, the SRNC measures the
related counter according to different relocation types.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the number of failed CS relocation preparations (UE involved) initiated
by the SRNC according to different failure causes.
Measurement point
The measurement is triggered at point A as shown in the following figure. After the SRNC
initiates a relocation (UE involved), the outgoing relocation preparation fails if the SRNC
receives the RELOCATION PREPARATION FAILURE message from the CN in the CS
domain. In this case, the SRNC measures the related counter according to different failure causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the number of failed relocation 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-230 Failed SRNC relocation procedure during the reconfiguration (UE involved)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Figure 1-231 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.
Figure 1-232 Failed SRNC relocation execution procedure due to timer expiry for IU release
command (UE involved)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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."
Figure 1-234 Failed SRNC relocation execution procedure (reception of IU release command)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of CS relocation preparation attempts (UE not involved)
initiated by the SRNC according to different relocation triggering 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 domain, if the relocation
request type is "UE Not Involved", the SRNC measures the related counter according to different
triggering causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful CS relocation preparations (UE not involved)
initiated by the SRNC according to different relocation triggering causes.
Measurement point
The measurement is triggered at point B as shown in the following figure. After the SRNC
initiates a relocation (UE not involved), the relocation preparation succeeds if the SRNC receives
a RELOCATION COMMAND message from the CN in the CS domain. In this case, the SRNC
measures the related counter according to different relocation causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of failed CS relocation preparations (UE not involved)
initiated by the SRNC according to different failure causes.
Measurement point
The measurement is triggered at point A as shown in the following figure. After the SRNC
initiates a relocation (UE not involved), the outgoing relocation preparation fails if the SRNC
receives a RELOCATION PREPARATION FAILURE message from the CN in the CS domain.
In this case, the SRNC measures the related counter according to different failure causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of PS relocation preparation attempts (UE involved) initiated
by the SRNC according to different relocation triggering 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 PS domain, if the relocation
request type is "UE Involved", the SRNC measures the related counter according to different
triggering causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of PS relocation preparation attempts (UE not involved)
initiated by the SRNC according to different relocation triggering 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 PS domain, if the relocation
request type is "UE Not Involved", the SRNC measures the related counter according to different
triggering causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of PS relocation preparation attempts initiated by the SRNC
according to the relocation type.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending a
RELOCATION REQUIRED message to the CN in the PS domain, the SRNC measures the
related counter according to different relocation types.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful PS relocation preparations (UE involved)
initiated by the SRNC according to different relocation triggering causes.
Measurement point
The measurement is triggered at point B as shown in the following figure. If the SRNC receives
a RELOCATION COMMAND message from the CN in the PS domain after initiating a
relocation (UE involved), the relocation preparation succeeds. In this case, the SRNC measures
the related counter according to different relocation causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful PS relocation preparations (UE not involved)
initiated by the SRNC according to different relocation triggering causes.
Measurement point
The measurement is triggered at point B as shown in the following figure. If the SRNC receives
a RELOCATION COMMAND message from the CN in the PS domain after initiating a
relocation (UE not involved), the relocation preparation succeeds. In this case, the SRNC
measures the related counter according to different relocation causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful PS relocation preparations initiated by the
SRNC according to the relocation type.
Measurement point
The measurement is triggered at point B as shown in the following figure. If the SRNC receives
a RELOCATION COMMAND message from the CN in the PS domain after initiating a
relocation, the relocation preparation succeeds. In this case, the SRNC measures the related
counter according to different relocation types.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of failed PS relocation preparations (UE involved) initiated
by the SRNC according to different failure causes.
Measurement point
The measurement is triggered at point A as shown in the following figure. After the SRNC
initiates a relocation (UE involved), the outgoing relocation preparation fails if the SRNC
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of failed PS relocation preparations (UE not involved)
initiated by the SRNC according to different failure causes.
Measurement point
The measurement is triggered at point A as shown in the following figure. After the SRNC
initiates a relocation (UE not involved), the outgoing relocation preparation fails if the SRNC
receives a RELOCATION PREPARATION FAILURE message from the CN in the PS domain.
In this case, the SRNC measures the related counter according to different failure causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-246 Reconfiguration procedure during the SRNC relocation (UE involved)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful relocation executions (UE involved) initiated
by the SRNC according to different CN domains.
Measurement point
The measurement is triggered at point A as shown in the following figure. During the relocation
(UE involved), when the SRNC receives an IU RELEASE COMMAND message with the cause
value of "Successful Relocation", "Normal Release", or "Network Optimization", the relocation
succeeds. In this case, the SRNC measures the related counter according to the CN domain.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful relocation executions (UE not involved)
initiated by the SRNC according to different CN domains.
Measurement point
The measurement is triggered at point A as shown in the following figure. During the relocation
(UE not involved), when the SRNC receives an IU RELEASE COMMAND message with the
cause value of "Successful Relocation", "Normal Release", or "Network Optimization", the
relocation succeeds. In this case, the SRNC measures the related counter according to the CN
domain.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Overview
RLC measurement is a measurement unit used to measure the RLC on the RNC basis.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of packets sent by all the RLCs in TM
mode in the RNC.
Measurement point
The measurement is triggered when an RLC in TM mode sends a packet.
Formula
None
Unit
packet
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of packets sent by all the RLCs in AM
mode in the RNC.
Measurement point
The measurement is triggered when an RLC in AM mode sends a packet.
Formula
None
Unit
packet
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of packets sent by all the RLCs in UM
mode in the RNC.
Measurement point
The measurement is triggered when an RLC in UM mode sends a packet.
Formula
None
Unit
packet
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of packets received by all the RLCs in TM
mode in the RNC.
Measurement point
The measurement is triggered when an RLC in TM mode receives a packet.
Formula
None
Unit
packet
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of packets received by all the RLCs in AM
mode in the RNC.
Measurement point
The measurement is triggered when an RLC in AM mode receives a packet.
Formula
None
Unit
packet
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of packets received by all the RLCs in UM
mode in the RNC.
Measurement point
The measurement is triggered when an RLC in UM mode receives a packet.
Formula
None
Unit
packet
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
1.8.19.9 Number of PDUs with the Size Smaller than 336 bit Received by RLCs In
Acknowledged Mode Carried by TRB
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
1.8.19.10 Number of PDUs with the Size Greater than or Equal to 336 bit Received
by RLCs In Acknowledged Mode Carried by TRB
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
counts the RRC connection release messages of the entire RNC by the RRC connection release
cause.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
A VS.RRC.AttConnEstab.RNC,VS.RRC.AttC
onnEstab.Msg.RNC
B VS.RRC.AttConnEstab.CellDCH.RNC,VS.
RRC.AttConnEstab.CellFACH.RNC
J VS.RRC.SuccConnEstab.RNC,VS.RRC.Su
ccConnEstab.CellFACH.RNC,VS.RRC.Suc
cConnEstab.CellDCH.RNC
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
VS.RRC.AttConnEstab.Msg.RNC VS.RRC.AttConnEstab.RNC
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
Measurement Counters
ID Counter Description
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.
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. Note that the
measurement is not triggered for a RRC CONNECTION REQUEST message that is
retransmitted by the UE.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Overview
This measurement unit provides the average number of UEs in different RRC connection states
in the RNC.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
1.8.23.1 Counters Related to the Number of UEs in Different RRC Connection States
for RNC
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
1.8.23.3 Average Number of UEs in the URA_PCH State and Carried on the EPCH
for RNC
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Units
Unit Description
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
1.9.1.1 Number of Roaming UEs that Is Registered In Local Operator Under MOCN
for the First Time
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Units
Unit Description
Unit Description
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
VS.LCC.LDR.InterFreq VS.LCC.LDR.HSUPA.InterFreq
VS.LCC.LDR.HSDPA.InterFreq
VS.LCC.LDR.InterRATPS VS.LCC.LDR.HSDPA.InterRATPS
VS.LCC.LDR.InterRATCS VS.LCC.LDR.HSUPA.InterRATCS
VS.LCC.LDR.HSDPA.InterRATCS
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the DL rate of AMR services(narrowband AMR
services) is increased in a cell.
Measurement point
The measurement is triggered at point B as shown in the following figure. After the RNC sends
the RATE CONTROL control frame to the CN through the IUUP layer, the DL rate of AMR
services successfully increases if the RNC receives the RATE CONTROL ACK control frame
from the CN. In this case, the RNC measures the counter in the best cell where the UE camps
on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the DL rate of AMR services(narrowband AMR
services) is decreased in a cell.
Measurement point
The measurement is triggered at point B as shown in the following figure. After the RNC sends
the RATE CONTROL control frame to the CN through the IUUP layer, the DL rate of AMR
services successfully decreases if the RNC receives the RATE CONTROL ACK control frame
from the CN. In this case, the RNC measures the counter in the best cell where the UE camps
on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the UL rate of AMR services(narrowband AMR
services) is increased in a cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. After the RNC sends
the TRANSPORT FORMAT COMBINATION CONTROL message to the UE, the UL rate of
AMR services successfully increases if the RNC does not receive the TRANSPORT FORMAT
COMBINATION CONTROL FAILURE message from the UE. In this case, the RNC measures
the counter in the best cell where the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the UL rate of AMR services(narrowband AMR
services) is decreased in a cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. After the RNC sends
the TRANSPORT FORMAT COMBINATION CONTROL message to the UE, the UL rate of
AMR services successfully decreases if the RNC does not receive the TRANSPORT FORMAT
COMBINATION CONTROL FAILURE message from the UE. In this case, the RNC measures
the counter in the best cell where the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful dynamic channel conversions from DCH to
FACH or from FACH to DCH for R99 service in a cell during the RAB modification procedure
and DCCC procedure. The number of successful dynamic channel conversions from DCH to
FACH is measured in the best cell where the UE camps on before channel conversion.
Measurement point
The measurement is triggered at point B as shown in the following figure. In the process of
dynamic channel conversion, when the RNC receives the RADIO BEARER
RECONFIGURATION COMPLETE message from the UE, if the DCH is converted to the
FACH, the RNC measures the related counter in the best cell where the UE camps on before
channel conversion. If the FACH is converted to the DCH, the RNC measures the related counter
in the cell where the UE camps on after channel conversion.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of state transfer 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful state transfers 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
service is carried on the DCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 B as shown in the following figure. When receiving the
RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the RNC
measures the related counter based on different DCCC strategies in the best cell where the UE
camps on if downlink service is carried on the DCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 the durations of UL or DL overload congestion in the
cell in a measurement period.
Formula
None
Unit
s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 cell where the UE
camps on every time a UE performing BE services is transferred to CCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.1.13 Counters Related to the Duration of Cell in LDR State Due to Congestion
of Various Resources
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
1.10.1.14 Counters Related to the Number of Times a Cell Is in LDR State Due to
Congestion of Various Resources
Measurement Counters
ID Counter Description
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of HSUPA UEs performing PS inter-RAT handovers when
the cell is in LDR state.
Measurement point
When the cell is in LDR state, every time the RNC selects a PS HSUPA UE to perform inter-
RAT handover, the RNC measures the counter in the cell where the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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. These counters provide the number of UEs performing BE service
TF control.
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 cell where the UE camps on according
to the UL or DL overload congestion.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of failed requests for different resources in a cell during the
channel type switch according to the limited resource type.
Measurement point
During the channel type change, the RNC initiates the admission procedure to request resources.
If the resource request fails, the RNC measures the related 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 switch is measured.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of service preemptions in a cell during the hard handover.
Measurement point
During the hard handover, 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that 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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of RB releases of 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency handovers. VS.LCC.LDR.HSDPA.InterFreq is used to measure the number of
HSDPA UEs performing inter-frequency handovers. VS.LCC.LDR.HSUPA.InterFreq is used
to measure the number of HSUPA UEs performing inter-frequency 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.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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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. These counters provide the
number of UEs performing uncontrollable real-time service QoS renegotiation according to the
UL or DL congestion.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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. VS.LCC.LDR.HSUPA.InterRATCS is used
to measure the number of HSUPA UEs performing CS 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.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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.1.28 Counters Related to the Number of UEs Performing AMR Rate Decrease
in Basic Congestion
Measurement Counters
ID Counter Description
Description
When the cell is in basic congestion, the RNC selects certain UEs to perform AMR rate decrease.
These counters provide the number of UEs performing AMR(narrowband and wideband AMR
services) rate decrease according to the UL or DL congestion.
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
When the cell is in DL 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.
Measurement point
When the cell is in DL 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
1.10.1.31 Counters Related to the Number of Qoffset Updates Due to Load Level
Change
Measurement Counters
ID Counter Description
Description
The selection/reselection parameter Qoffset in system information block (SIB) 11 defines the
selection/reselection offset between two cells. By Qoffset, the network can direct a UE to camp
on one of the cells. When the load of the serving cell is light, the RNC can set greater values for
Qoffset between the serving cell and the neighboring cells by updating system information. Thus,
the UE in idle mode is not apt to reselect another cell in heavy load. When the load of the serving
cell is heavy, the RNC can set smaller values for Qoffset between the serving cell and the
neighboring cells by updating system information. Thus, the UE in idle mode is apt to reselect
another cell in light load, which can reduce the potential load of the current cell. These counters
provide the number of Qoffset updates when the load of the serving cell becomes light, normal,
and heavy respectively.
Measurement point
The measurement is triggered at point A as shown in the following figure. When updating Qoffset
in SIB 11 according to the change in the cell load level in the common measurement report, the
RNC measures the related counter.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.1.32 Counters Related to the Number of Sintersearch Updates Due to Cell Load
Change
Measurement Counters
ID Counter Description
Description
The selection/reselection parameter Sintersearch in SIB 3 defines the quality requirement of
starting an inter-frequency measurement for cell reselection. If the UE finds that the quality of
the serving cell is lower than Sintersearch, it starts the inter-frequency measurement so that UE
can reselect to another cell. When the load of the serving cell is light, the RNC can set a greater
value for Sintersearch by updating system information. Thus, 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 smaller value
for Sintersearch by updating system information. Thus, the UE in idle mode is apt to start cell
reselection, which can reduce the potential load of the current cell. These counters provide the
number of Sintersearch updates when the load of the serving cell becomes light, normal, and
heavy respectively.
Measurement point
The measurement is triggered at point A as shown in the following figure. When updating
Sintersearch in SIB 3 according to the change in the cell load level in the common measurement
report, the RNC measures the related counter.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of successful cell resource requests due to UE
service RAB reconfiguration.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of cell resource requests due to UE service
RAB reconfiguration.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
When the type of the channel where the UE occupies in a cell switches, the RNC requests cell
resources for the UE again. In this case, the involved channel types are D2H, H2D, D2F, H2F,
E2D, D2E, E2F and F2E. This counter provides the number of successful cell resource requests
for the UE in a cell during the channel type switch. In addition, only the number of successful
cell resource requests in a cell during the channel type switch is measured.
Measurement point
When the type of channel where the UE occupies in a cell switches, the RNC measures the
counter in the cell where the UE camps on if the cell resource request succeeds.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
When the type of the channel where the UE occupies in a cell switches, the RNC requests cell
resources for the UE again. In this case, the involved channel types are D2H, H2D, D2F, H2F,
E2D, D2E, E2F and F2E. This counter provides the number of cell resource requests for the UE
in a cell during the channel type switch. In addition, only the number of cell resource requests
in a cell during the channel type switch is measured.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the mean number of UL and DL equivalent voice UEs in CELL_DCH
state in a cell.
Measurement point
In a measurement period, the number of equivalent voice UEs in CELL_DCH state at UL and
DL is sampled every five 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the duration of cell dynamic shutdown.
Measurement point
After a cell is set up, the RNC measures the duration of cell dynamic shutdown in a measurement
period and accumulates the values to obtain the value of this counter.
Formula
None
Unit
s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the unavailability duration of a cell caused by O&M in the
RNC.
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the mean, maximum, and minimum credit usages in a cell.The uplink
credit number is twice the number of uplink CEs, and the downlink credit number is equal to
the number of downlink CEs.
Measurement point
The RNC periodically takes samples from the UL credit usage and DL credit usage in the cell.
At the end of the measurement period, the RNC calculates the maximum and minimum usages
of credit resources, and divides the accumulated usages by the number of samples to obtain the
mean usage of both UL and DL credit resources in the measurement period.
Note that the CE-related counters measured at the RNC have different usage 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 measurement period of the CE-related counters measured at the RNC is 5
seconds, 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.1.47 Counters Related to the Duration of Max and Min Values of CPICH Power
Due to Cell Breathing
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the duration of maximum and minimum values of CPICH power due to
the cell breathing in a cell of the RNC.
Measurement point
When the transmit carrier power (TCP) is greater than the upper threshold configured for cell
breathing, the RNC needs to adjust the power of common pilot channel (CPICH). However, if
the power of CPICH reaches its maximum value, the RNC cannot adjust it. The RNC measures
the duration of the maximum values of CPICH power in a measurement period on a cell basis.
When the TCP is smaller than the lower threshold configured for cell breathing, the RNC needs
to adjust the power of CPICH. However, if the power of CPICH reaches its minimum value, the
RNC cannot adjust it. The RNC measures the duration of the minimum values of CPICH power
in a measurement period on a cell basis. Note: If the cell breathing algorithm switch is disabled
in the measurement period, the values of these counters are zero.
Formula
None
Unit
s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of CPICH power adjustments due to the cell breathing in a
cell of the RNC.
Measurement point
When the TCP is greater than the upper threshold configured for cell breathing or is smaller than
the lower threshold configured for cell breathing, the RNC needs to adjust the power of CPICH.
The RNC measures the number of increases and decreases in the CPICH power in a measurement
period on a cell basis. Note: If the cell breathing algorithm switch is disabled in the measurement
period, the values of these counters are zero.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the overload and underload duration of transmit carrier power (TCP)
through comparison with the upper and lower thresholds configured for cell breathing in a cell
of the RNC.
Measurement point
The RNC measures the accumulated duration in which the TCP is greater than the upper
threshold configured for cell breathing and the accumulated duration in which the TCP is smaller
than the lower threshold configured for cell breathing in a measurement period on a cell basis.
Note: The values of these counters are not affected if the cell breathing algorithm switch is
disabled in the measurement period.
Formula
None
Unit
s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the average CPICH power in a cell.
Measurement point
The RNC periodically samples (sampling periodicity is 5 seconds) CPICH power in a cell. At
the end of a measurement period, the average CPICH power is obtained by dividing the
accumulated CPICH power by the number of samples. The RNC adjusts CPICH power based
on load in the cell when uplink intra-frequency load balancing based on RTWP is started or
intra-frequency load balancing of TRX transmit power in the cell is started.
Formula
None
Unit
dBm
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of dynamic channel conversion attempts from DCHs to
FACHs or from FACHs to DCHs for R99 service in a cell during the RAB modification
procedure and DCCC procedure. The number of dynamic channel conversion attempts from
DCHs to FACHs is measured in the best cell where the UE camps on before channel conversion.
Measurement point
The measurement is triggered at point A as shown in the following figure. In the process of
dynamic channel conversion, when the RNC sends the RADIO BEARER
RECONFIGURATION message to the UE, if the DCH is converted to the FACH, the RNC
measures the related counter in the best cell where the UE camps on before channel conversion.
If the FACH is converted to the DCH, the RNC measures the related counter in the cell where
the UE camps on after channel conversion.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the DL rate of the AMR WB services is increased
in a cell.
Measurement point
The measurement is triggered at point B as shown in the following figure. After the RNC sends
the RATE CONTROL control frame to the CN through the IUUP layer to request the IUUP to
increase the DL rate of the AMR WB services, the DL rate successfully increases if the RNC
receives the RATE CONTROL ACK control frame from the CN. In this case, the RNC measures
the counter in the best cell where the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of decreases of the DL bit rate for the AMR WB
speech service in a cell.
Measurement point
The measurement is triggered at point B as shown in the following figure. After the RNC sends
the RATE CONTROL control frame to the CN through the IUUP layer to request the IUUP to
decrease the DL rate of the AMR WB services, the DL rate successfully decreases if the RNC
receives the RATE CONTROL ACK control frame from the CN. In this case, the RNC measures
the counter in the best cell where the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of increases of the UL bit rate for the AMR WB
speech service in a cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. After the RNC sends
the TRANSPORT FORMAT COMBINATION CONTROL message to the UE, the UL rate of
AMR services successfully increases if the RNC does not receive the TRANSPORT FORMAT
COMBINATION CONTROL FAILURE message from the UE. In this case, the RNC measures
the counter in the best cell where the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of decreases of the DL bit rate for the AMR WB
speech service in a cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. After the RNC sends
the TRANSPORT FORMAT COMBINATION CONTROL message to the UE, the UL rate of
AMR services successfully decreases if the RNC does not receive the TRANSPORT FORMAT
COMBINATION CONTROL FAILURE message from the UE. In this case, the RNC measures
the counter in the best cell where the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of failed requests for different resources in a cell in the DCCC
procedure according to the limited resource type.
Measurement point
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the number of failed requests for different resources in a cell during the
soft handover according to the limited resource type.
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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the number of failed requests for different resources in a cell during the
hard handover according to the limited resource type.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. 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 hard 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the failed requests for different resources in the RAB setup procedure.
These counters will be measured in the cells that fail to request the resources.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 Figure1.After the CN delivers the RAB
ASSIGNMENT REQUEST message, if the RNC fails to request the resources, this counter will
be measured in the cells that fail to request the resources according to different failure causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of UL EDCH-EDCH dynamic channel configuration control
(DCCC) attempts based on the throughput or RLC BO in the HSUPA serving cell. These counters
are measured according to the UL EDCH-EDCH DCCC upsizing and downsizing.
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 HSUPA serving cell if the uplink service is
carried on the EDCH before and after the channel reconfiguration.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful UL EDCH-EDCH DCCC operations based on
the throughput or RLC BO in the HSUPA serving cell. These counters are measured according
to the UL EDCH-EDCH DCCC upsizing and downsizing.
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 related counter based on different DCCC strategies in the HSUPA serving cell if
the uplink service is carried on the EDCH before and after the channel reconfiguration.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
In order to get more available HSDPA codes, the RNC shall select certain UEs to perform code
adjustment. This counter provides the number of UEs that perform code adjustment 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
In order to get more available HSDPA codes, the RNC shall select certain UEs to perform code
adjustment. When selecting an UE to perform code adjustment, the RNC measures the counter
in the cell where the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of downlink DCH DCCC upsizing attempts based on the
throughput or RLC BO 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 the throughput or RLC BO in the best cell where the UE camps on if downlink service
is carried on the DCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful downlink DCH DCCC upsizings based on the
throughput or RLC BO in the best cell where the UE camps on.
Measurement point
The measurement is triggered at point B as shown in the following figure. During the DCCC
upsizing, when receiving the RADIO BEARER RECONFIGURATION COMPLETE message
from the UE, the RNC measures the counter based on the throughput or RLC BO in the best cell
where the UE camps on if downlink service is carried on the DCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of UL DCH DCCC upsizing attempts based on the throughput
or RLC BO in the best cell where the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the following figure. During the DCCC
upsizing, when sending the RADIO BEARER RECONFIGURATION message to the UE, the
RNC measures the counter based on the throughput or RLC BO in the best cell where the UE
camps on if uplink service is carried on the DCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful UL DCH DCCC upsizings based on the
throughput or RLC BO in the best cell where the UE camps on.
Measurement point
The measurement is triggered at point B as shown in the following figure. During the DCCC
upsizing, 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 service is carried on the DCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of UL 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
service is carried on the DCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful UL DCH DCCC downsizings 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 COMPLETE message from the UE, the RNC
measures the related counter based on different DCCC strategies in the best cell where the UE
camps on if uplink service is carried on the DCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
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. This counter provides the number of UEs that has performed code adjustment
successfully in a cell.
Measurement point
After detecting a basic congestion of downlink code resources, the RNC selects some UEs in
the cell and checks whether the congestion can be eliminated by performing code adjustment
on these UEs. If the congestion cannot be eliminated, the RNC periodically selects other UEs
in the cell and checks whether the congestion can be eliminated until it has successfully selected
certain UEs.
Then, the RNC performs code adjustment on the selected UEs. This counter is measured after
the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message
from the UE. The RNC determines that the code adjustment is successful after receiving this
message.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
In order to get more available HSDPA codes, the RNC shall select certain UEs to perform code
adjustment. This counter provides the number of UEs that perform successful code
adjustment.For DC-HSDPA users, this counter is measured only in the cell with the primary
carrier.
Measurement point
In order to get more available HSDPA codes, the RNC shall select certain UEs to perform code
adjustment. If the UE perform code adjustment, the RNC measures the counter in the cell where
the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the duration of cell unavailability. It is not measured if a cell is blocked
through the LMT or deleted by the dynamic shutdown algorithm. A cell becomes unavailable
when the cell is not set up, the common transport channel (CCH) or the equipment is faulty after
the cell is set up, or the NCP or CCP is faulty. When a cell is unavailable, all services carried
on the cell are interrupted.
Measurement point
After a cell becomes unavailable, the RNC measures the duration of cell unavailability. At the
end of a measurement period, the RNC accumulates the unavailability duration of each cell in
the cell range to obtain the value of this counter.
Formula
None
Unit
s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the duration of HSDPA service unavailability due to system faults (the
HSDPA channel fails to be set up or the state of the HSDPA channel changes from available to
unavailable) 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 cell with the primary
carrier.
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the duration of HSUPA service unavailability due to system faults of the
RNC in a 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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of attempts to transfer state from CELL_PCH to CELL_FACH
in the 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, if UE try to transfer state from CELL_PCH to
CELL_FACH, the RNC measures the item in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful state transfer 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 UTRAN MOBILITY INFORMATION CONFIRM or PHYSICAL CHANNEL
RECONFIGURATION COMPLETE or TRANSPORT CHANNEL RECONFIGURATION
COMPLETE or RADIO BEARER RECONFIGURATION COMPLETE message, if UE
transfer state from CELL_PCH to CELL_FACH, the RNC measures the item in the best cell
that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of attempts to transfer state from CELL_PCH to URA_PCH
in the 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, if UE try to transfer state from CELL_PCH to URA_PCH,
the RNC measures the item in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of attempts to transfer state from URA_PCH to CELL_FACH
in the 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, if UE try to transfer state from URA_PCH to
CELL_FACH, the RNC measures the item in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful state transfer 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 received from
the UE a UTRAN MOBILITY INFORMATION CONFIRM or PHYSICAL CHANNEL
RECONFIGURATION COMPLETE or TRANSPORT CHANNEL RECONFIGURATION
COMPLETE or RADIO BEARER RECONFIGURATION COMPLETE message, if UE
transfer state from URA_PCH to CELL_FACH, the RNC measures the item in the best cell that
the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of cell deletions or establishments due to dynamic cell
shutdown in the cell.
Measurement point
If the conditions of dynamic cell shutdown are met and the action of shutdown or power-on is
triggered, this counter will be measured when the cell is deleted or set up.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of state transfer attempts from CELL_DCH to CELL_PCH
or URA_PCH in a 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 counter
in the best cell where the UE camps on if the state is transferred from CELL_DCH to CELL_PCH
or URA_PCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful state transfers from CELL_DCH to CELL_PCH
or URA_PCH in a 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 counter in the best cell where the UE camps on if the state is transferred from
CELL_DCH to CELL_PCH or URA_PCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of state transfer attempts from CELL_DCH or CELL_FACH
to CELL_PCH or URA_PCH for Fast Dormancy user 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 supporting the fast dormancy function, instructing the
UE to transfer 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful state transfers from CELL_DCH or
CELL_FACH to CELL_PCH or URA_PCH for Fast Dormancy user 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 supporting the fast
dormancy feature, indicating that the UE has transfered 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of attempts to transfer state from CELL_PCH to CELL_DCH
in the 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, if UE try to transfer state from CELL_PCH to
CELL_DCH, the RNC measures the item in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful state transfer from CELL_PCH to CELL_DCH
in the best 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, if UE transfer state from
CELL_PCH to CELL_DCH, the RNC measures the item in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of attempts to transfer state from URA_PCH to CELL_DCH
in the 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, if UE try to transfer state from URA_PCH to
CELL_DCH, the RNC measures the item in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful state transfer from URA_PCH to CELL_DCH
in the best 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, if UE transfer state from
URA_PCH to CELL_DCH, the RNC measures the item in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a UE successfully transfer 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that power of the Common Pilot Channel (CPICH)
is adjusted on the basis of Received Total Wideband Power (RTWP) to achieve uplink intra-
frequency load balancing.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the duration of CPICH power being Min Transmit Power of PCPICH
when power of the CPICH is adjusted on the basis of RTWP to achieve uplink intra-frequency
load balancing.
Measurement point
A measurement starts when CPICH power is adjusted to Min Transmit Power of PCPICH and
ends when CPICH power is adjusted to be higher than Min Transmit Power of PCPICH. This
counter is the accumulative value of such durations in a measurement period.
Formula
None
Unit
s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a UE performing HSDPA services attempts to
transit from CELL_DCH state to CELL_PCH or URA_PCH state.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 figure. When the RNC sends the UE
an RADIO BEARER RECONFIGURATION message, instructing the UE performing HSDPA
services to transit from CELL_DCH state to CELL_PCH or URA_PCH state, this counter is
measured at the serving cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a UE performing HSDPA services transits from
CELL_DCH state to CELL_PCH or URA_PCH state successfully.For DC-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 figure. When the RNC receives RADIO
BEARER RECONFIGURATION COMPLETE message from the UE, indicating that the UE
performing HSDPA 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a UE performing HSUPA services attempts to
transit from CELL_DCH state to CELL_PCH or URA_PCH state.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 sends the UE
RADIO BEARER RECONFIGURATION message, instructing the UE performing HSDPA
services to transit from CELL_DCH state to CELL_PCH or URA_PCH state, this counter is
measured at the serving cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a UE performing HSUPA services transits from
CELL_DCH state to CELL_PCH or URA_PCH state successfully.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 RADIO
BEARER RECONFIGURATION COMPLETE message from the UE, indicating that the UE
performing HSUPA 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a UE performing PS R99 services attempts to
transit from CELL_DCH state to 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
RADIO BEARER RECONFIGURATION message, instructing the UE performing PS R99
services to transit from CELL_DCH state to CELL_PCH or URA_PCH state, this counter is
measured at the serving cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a UE performing PS R99 services transits from
CELL_DCH state to CELL_PCH or URA_PCH state successfully.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.1.98 Number of Times That PS R99 Service Rate Is Found to Be Higher than
HSUPA Service Rate
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
When the PS R99 BE service rate is found to be higher than the HSUPA service rate in an
HSUPA cell, this counter provides the number of times the PS R99 BE users are selected for
rate reduction. This counter is calculated in the best cell for the PS R99 BE users.
Measurement point
The measurement is triggered at point A, as 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 some PS R99 BE users. The measurement is triggered when the RNC sends
a Radio Bearer Reconfiguration message to a UE.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
dBm
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters measure the number of failed resource applications during a channel conversion.
Measurement point
The measurement is triggered when a UE fails to obtain resources for admission during a channel
conversion. In this case, the corresponding counter is measured in the cell that the UE fails to
access based on the cause of resource congestion.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful TTI switchovers from 2 ms to 10 ms during
RB reconfiguration in an HSUPA serving cell. For DC-HSUPA UEs, the RNC calculates the
number of such successful switchovers in the cells with the primary carriers.
Measurement point
At measurement 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 by the specific TTI switchover cause.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the mean number of PS access classes restricted due to cell resource
congestion for UEs of R6 or later, mean number of access classes restricted due to cell resource
congestion for UEs of R5 or earlier, and mean number of CS access classes restricted due to cell
resource congestion for UEs of R6 or later, 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 during which PS or CS accesses of UEs are restricted.
Formula
None
Unit
s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 where signal quality is poor, 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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
1.10.2.13 Number of CS RABs Abnormally Released for Special UEs for Cell
Measurement Counters
ID Counter Description
Description
This counter measures the number of CS radio access bearers (RABs) abnormally released for
special UEs in the best cells.
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.2.14 Number of CS RABs Normally Released for Special UEs for Cell
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
This counter measures the average, maximum, and minimum values of uplink actual cell load
in the measurement period. The counter value is a 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 the figure 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.
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the number of CELL_FACH to URA_PCH state transition attempts in a
cell.
Measurement point
The measurement is triggered when the RNC sends a RADIO BEARER RECONFIGURATION
(point A shown in the figure) or PHYSICAL CHANNEL RECONFIGURATION message to
instruct a UE to move from the CELL_FACH to URA_PCH state. In this case, the counter is
increased by one in the cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the number of successful CELL_FACH to URA_PCH state transitions
in a cell.
Measurement point
The measurement is triggered when the RNC receives a RADIO BEARER
RECONFIGURATION COMPLETE (point B shown in the figure) or PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message from a UE. This message indicates that the UE
has moved from the CELL_FACH to URA_PCH state. In this case, the counter is increased by
one in the cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the number of CELL_DCH to URA_PCH state transition attempts in a
cell.
Measurement point
The measurement is triggered at point A shown in the figure when the RNC sends a RADIO
BEARER RECONFIGURATION message to instruct a UE to move from the CELL_DCH to
URA_PCH state. In this case, the counter is increased by one in the cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the number of successful CELL_DCH to URA_PCH state transitions in
a cell.
Measurement point
The measurement is triggered at point B shown in the figure when the RNC receives a RADIO
BEARER RECONFIGURATION COMPLETE message from a UE. This message indicates
that the UE has moved from the CELL_DCH to URA_PCH state. In this case, this counter is
increased by one in the cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
This counter provides the UL BLER of AMR services(narrowband AMR services) on the DCH
in the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying AMR services
on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
1.10.3.2 Number of TBs with UL CRCI Error for AMR Services for Cell
Measurement Counters
ID Counter Description
Description
This counter provides the number of TBs with UL CRCI error for AMR services(narrowband
AMR services) on the DCH in the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying AMR services
on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
Numbers
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of BLER samplings for AMR services(narrowband AMR
services) on the DCH in the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying AMR services
on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
times
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the UL BLER of CS 64 Kbit/s conversational services on the DCH in the
best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying CS 64 Kbit/
s conversational services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of TBs with UL CRCI error for the CS 64 Kbit/s conversational
services on the DCH in the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying CS 64 Kbit/
s conversational services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
Numbers
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of UL BLER samplings for CS 64 Kbit/s conversational
services on the DCH in the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying CS 64 Kbit/
s conversational services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
times
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the UL BLER of PS BE services on the DCH in the best cell based on
the service rate.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying PS BE
services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
1.10.3.8 Counters Related to the Number of TBs with UL CRCI Error for PS BE
Services on DCH
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the number of TBs with UL CRCI error for PS BE services on the DCH
in the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying PS BE
services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
Numbers
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the sampling times of BLER for PS BE services on the DCH in the best
cell based on the service rate.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying PS BE
services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
times
Related Features
Counter Feature ID Feature Name
1.10.3.10 Rate of Duration that UL BLER of AMR Services on DCH Exceeds Target
Value for Cell
Measurement Counters
ID Counter Description
Description
This counter provides the rate of duration that the UL BLER of AMR services(narrowband AMR
services) on DCH exceeds the target value in the best cell.
Measurement point
The UL BLER of AMR services on DCH is measured when the number of TBs reaches the
sampling window (500 TBs) in the best cell. At the end of the measurement period, the value
of this counter is obtained as follows: dividing the number of times that the measured BLER is
higher than the target value by the total number of sampling times.
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the rate of duration that the UL BLER of the CS 64 Kbit/s conversational
services on the DCH exceeds the target value in the best cell.
Measurement point
The UL BLER of CS 64 Kbit/s conversational services on the DCH is measured when the number
of TBs reaches the sampling window (500 TBs) in the best cell. At the end of the measurement
period, the value of this counter is obtained as follows: dividing the number of times that the
measured BLER is higher than the target value by the total number of sampling times.
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the rate of duration that UL BLER of PS BE services on the DCH in the
best cell based on the service rate.
Measurement point
The UL BLER of PS BE services on the DCH is measured when the number of TBs reaches the
sampling window (500 TBs) in the best cell. At the end of the measurement period, the value
of this counter is obtained as follows: dividing the number of times that the measured BLER is
higher than the target value by the total number of sampling times.
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the UL BLER of PS BE services on the RACH in the best cell.
Measurement point
The measurement is triggered on the best cell basis when the number of UL TBs carrying AMR
services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
1.10.3.14 Number of TBs with UL CRCI Error for PS 8 Kbit/s BE Services on RACH
for Cell
Measurement Counters
ID Counter Description
Description
These counters provide the number of TBs with UL CRCI error for PS 8 kbit/s BE services on
RACH in the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying PS 8kbit/s
BE services on the RACH reaches the defined sampling window (500 TBs).
Formula
None
Unit
Numbers
Related Features
Counter Feature ID Feature Name
1.10.3.15 Number of BLER Samplings for PS 8kbit/s BE Services on the RACH for
Cell
Measurement Counters
ID Counter Description
Description
This counter provides the number of BLER samplings for PS 8kbit/s BE services on the RACH
in the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying PS 8kbit/s
BE services on the RACH reaches the defined sampling window (500 TBs).
Formula
None
Unit
times
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the rate of the duration that the AMR speech quality(narrowband and
wideband AMR services) is GOOD to the total call duration in the best cell.
Measurement point
In a measurement period, the duration that the AMR UL speech quality is assessed as GOOD is
accumulated. At the end of the measurement period, this counter is obtained as follows: dividing
the accumulated time by the total call duration in the best cell.
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the rate of duration that the AMR speech quality(narrowband and
wideband AMR services) is ACCEPT to the total call duration in the best cell.
Measurement point
In a measurement period, the duration that the AMR UL speech quality is assessed as ACCEPT
is accumulated. At the end of the measurement period, this counter is obtained as follows:
dividing the accumulated time by the total call duration in the best cell.
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the rate of duration that the AMR speech quality(narrowband and
wideband AMR services) is BAD to the total call duration in the best cell.
Measurement point
In a measurement period, the duration that the AMR UL speech quality is assessed as BAD is
accumulated. At the end of the measurement period, this counter is obtained as follows: dividing
the accumulated time by the total call duration in the best cell.
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the UL BLER of PS Conversational services on the DCH in the best
cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying PS
Conversational services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
1.10.3.20 Counters Related to the Number of TBs with UL CRCI Error for PS
Conversational Services on DCH
Measurement Counters
ID Counter Description
Description
These counters provide the number of TBs with UL CRCI error for PS Conversational services
on the DCH in the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying PS
Conversational services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
Numbers
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the sampling times of BLER for PS Conversational services on the DCH
in the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying PS
Conversational services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
times
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the UL BLER of PS Streaming services on the DCH in the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying PS Streaming
services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
1.10.3.23 Counters Related to the Number of TBs with UL CRCI Error for PS
Streaming Services on DCH
Measurement Counters
ID Counter Description
Description
These counters provide the number of TBs with UL CRCI error for PS Streaming services on
the DCH in the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying PS Streaming
services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
Numbers
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the sampling times of BLER for PS Streaming services on the DCH in
the best cell.
Measurement point
The measurement is triggered in the best cell when the number of UL TBs carrying PS Streaming
services on the DCH reaches the defined sampling window (500 TBs).
Formula
None
Unit
times
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the rate of duration that UL BLER of PS Conversational services on the
DCH in the best cell.
Measurement point
The UL BLER of PS Conversational services on the DCH is measured when the number of TBs
reaches the sampling window (500 TBs) in the best cell. At the end of the measurement period,
the value of this counter is obtained as follows: dividing the number of times that the measured
BLER is higher than the target value by the total number of sampling times.
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the rate of duration that UL BLER of PS Streaming services on the DCH
in the best cell.
Measurement point
The UL BLER of PS Streaming services on the DCH is measured when the number of TBs
reaches the sampling window (500 TBs) in the best cell. At the end of the measurement period,
the value of this counter is obtained as follows: dividing the number of times that the measured
BLER is higher than the target value by the total number of sampling times.
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the rate of the duration that the AMR speech quality(narrowband and
wideband AMR services) is POOR to the total call duration in the best cell.
Measurement point
In a measurement period, the duration that the AMR UL speech quality is assessed as POOR is
accumulated. At the end of the measurement period, this counter is obtained as follows: dividing
the accumulated time by the total call duration in the best cell.
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the rate of the duration that the AMR speech quality(narrowband and
wideband AMR services) is EXCELLENT to the total call duration in the best cell.
Measurement point
In a measurement period, the duration that the AMR UL speech quality is assessed as
EXCELLENT is accumulated. At the end of the measurement period, this counter is obtained
as follows: dividing the accumulated time by the total call duration in the best cell.
Formula
None
Unit
%
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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
Measurement Counters
ID Counter Description
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
None
Unit
kbit/s
Related Features
None
Measurement Counters
ID Counter Description
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
Measurement Counters
ID Counter Description
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
None
Unit
kbit/s
Related Features
None
Measurement Counters
ID Counter Description
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
Measurement Counters
ID Counter Description
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
None
Unit
kbit/s
Related Features
None
Measurement Counters
ID Counter Description
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
Measurement Counters
ID Counter Description
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
None
Unit
kbit/s
Related Features
None
Measurement Counters
ID Counter Description
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
Measurement Counters
ID Counter Description
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
None
Unit
kbit/s
Related Features
None
Measurement Counters
ID Counter Description
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
Measurement Counters
ID Counter Description
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
None
Unit
kbit/s
Related Features
None
Measurement Counters
ID Counter Description
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
Measurement Counters
ID Counter Description
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
None
Unit
kbit/s
Related Features
None
Measurement Counters
ID Counter Description
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
Measurement Counters
ID Counter Description
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
None
Unit
kbit/s
Related Features
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful UU BOOST setups in the best cell.
Measurement point
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.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
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".
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
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-349 IU
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
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
Measurement Counters
ID Counter Description
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
Overview
This measurement unit 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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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-350 Cell update procedure (failed operation due to timer expiry)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.6.6 Number of Cell Update Failures due to No Response from UEs in the
CELL_FACH State
Measurement Counters
ID Counter Description
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-357 Cell update procedure (failed operation due to timer expiry)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
1.10.6.9 Number of Cell Updates that Are Under CPU Usage-Based Flow Control
and Are Triggered by CS Service Establishments in a Cell
Measurement Counters
ID Counter Description
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.
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 Feature ID Feature Name
1.10.6.10 Number of Cell Updates that Are Under RRC Queuing-Based Flow
Control and Are Triggered by CS Service Establishments in a Cell
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
1.10.6.11 Number of Cell Updates that Are Under RRC Queuing-Based Flow
Control in a Cell
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Overview
This measurement unit is used to measure the number of Compressed Mode Activation Attempts
and the number of Compressed Mode Activation fails.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of Up Link SF-2 Compressed Mode Activation
Attempts in a cell.
Measurement point
The RNC measures the number of Up Link SF-2 Compressed Mode Activation Attempts in one
counting period.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of Up Link HLS Compressed Mode Activation
Attempts in a cell.
Measurement point
The RNC measures the number of Up Link HLS Compressed Mode Activation Attempts in one
counting period.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of Up Link SF-2 Compressed Mode Activation
Fails in a cell.
Measurement point
The RNC measures the number of Up Link SF-2 Compressed Mode Activation Fails in one
counting period. The RNC sends MEASURE CONTROL message to UE for Up Link SF-2
Compressed Mode Activation. If the RNC receives corresponding MEASURE CONTROL
FAIL message from UE or not receives ACK, the RNC measures the item.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of Up Link HLS Compressed Mode Activation
Fails in a cell.
Measurement point
The RNC measures the number of Up Link HLS Compressed Mode Activation Fails in one
counting period. The RNC sends MEASURE CONTROL message to UE for Up Link HLS
Compressed Mode Activation. If the RNC receives corresponding MEASURE CONTROL
FAIL message from UE or not receives ACK, the RNC measures the item.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of Down Link SF-2 Compressed Mode Activation
Attempts in a cell.
Measurement point
The RNC measures the number of Down Link SF-2 Compressed Mode Activation Attempts in
one counting period.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of Down Link HLS Compressed Mode Activation
Attempts in a cell.
Measurement point
The RNC measures the number of Down Link HLS Compressed Mode Activation Attempts in
one counting period.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of Down Link SF-2 Compressed Mode Activation
Fails in a cell.
Measurement point
The RNC measures the number of Down Link SF-2 Compressed Mode Activation Fails in one
counting period. The RNC sends MEASURE CONTROL message to UE for Down Link SF-2
Compressed Mode Activation. If the RNC receives corresponding MEASURE CONTROL
FAIL message from UE or not receives ACK, the RNC measures the item.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of Down Link HLS Compressed Mode Activation
Fails in a cell.
Measurement point
The RNC measures the number of Down Link HLS Compressed Mode Activation Fails in one
counting period. The RNC sends MEASURE CONTROL message to UE for Down Link HLS
Compressed Mode Activation. If the RNC receives corresponding MEASURE CONTROL
FAIL message from UE or not receives ACK, the RNC measures the item.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Overview
CELL_FACH state user can use HSDSCH channel as transfer channel after R7 protocol.
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 measurement unit EFACH Measurement
(Cell) is used to measure this technology related services on the basis of Cell.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
VS.RRC.AttConnEstab.CellFACH VS.RRC.AttConnEstab.EFACH
VS.RRC.SuccConnEstab.CellFACH VS.RRC.SuccConnEstab.EFACH
VS.RAB.AbnormRel.PS.CCH VS.RAB.AbnormRel.PS.EFACH
VS.RAB.NormRel.PS.CCH VS.RAB.NormRel.PS.EFACH
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of successful RRC connection setups on the
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of PS RAB setup attempts on the EFACH when
the best cell is under the SRNC.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of successful PS RAB setups on the EFACH when
the best cell is under the SRNC.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement items provide the signaling delay of PS RAB setup of the UE in CELL_FACH
status when the best cell is under the SRNC.
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.
Formula
None
Unit
ms
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of abnormally released PS RABs on the EFACH
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" 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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of normally released PS RABs on the EFACH 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 when the released PS RAB is carried on the EFACH.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.8.8 Number of Downlink MAC PDU Bytes on the EFACH over the Iub
Interface
Measurement Counters
ID Counter Description
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.
Measurement point
The measurement is triggered when the CRNC sends downlink data on the EFACH over the Iub
interface.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the average number of UEs carried on the EFACH in the cell.
Measurement point
The system periodically (sampling periodicity is 5 seconds) takes samples of UEs carried on the
EFACH. 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 carried on the EFACH
in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement items provide the delay of RRC signaling on the EFACH in a cell under the
RNC.
Measurement point
The measurement is triggered at points A and C, as shown in the figure: At point A, the RNC
records the time (T1) when it receives a RRC CONNECTION REQUEST message. At point C,
the RNC records the time (T2) when it receives a RRC CONNECTION SETUP COMPLETE
message. Suppose delta T represents the signaling delay of the RRC signaling connection setup
on the EFACH in a cell. Then, delta T = T2 - T1.
Formula
None
Unit
ms
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the average number of UEs that are carried on the Enhanced Forward
Access Channel (EFACH) and use the Enhanced Discontinuous Reception (E-DRX) function
in a cell.
Measurement point
UEs carried on the EFACH and using the E-DRX function in a 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 calculated by dividing the accumulated number of the UEs by
the number of samples.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Overview
The EPCH state is the CELL_PCH or URA_PCH state of UEs using the RACH or EDCH
transport channel in the uplink or using the HS-DSCH transport channel in the downlink.
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 HS-
DSCH. 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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
This counter provides the average number of UEs that are in the CELL_PCH state and use the
EPCH function in a cell.
Measurement point
UEs that are in the CELL_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 Feature ID Feature Name
1.10.9.2 Number of UEs Carried on the EPCH and Allocated Dedicated H-RNTI for
Cell
Measurement Counters
ID Counter Description
Description
This counter provides the average number of UEs in the CELL_PCH state that use the EPCH
function and are allocated dedicated HS-DSCH Radio Network Temporary Identifier (H-RNTI)
in a cell.
Measurement point
UEs in the CELL_PCH state using the EPCH function and allocated dedicated H-RNTI 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 Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
This counter provides the average number of UEs that are carried on the ERACH in a cell.
Measurement point
The number of UEs carried on the ERACH in a cell is 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 calculated by dividing the accumulated number of the UEs by the number of samples.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of requests for setting up an RRC connection on an 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that an RRC connection is set up successfully on an
ERACH.
Together with "Number of Requests for Setting Up RRC Connections on ERACHs for Cell",
this counter reflects the RRC setup success rate on an 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of requests for setting up a PS RAB on an ERACH in the cell
that the UE camps on.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a PS RAB is successfully set up on an ERACH
in the cell that the UE camps on. Together with "Number of PS RAB Setup Requests on ERACH
for Cell", this counter reflects the PS RAB setup success rate on an 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a PS RAB is normally released on an ERACH
in the cell that the UE camps on.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a PS RAB is abnormally released on an ERACH
in the cell that the UE camps on. Together with "Number of PS RABs Normally Released on
ERACHs for Cell", this counter reflects the ratio of abnormal PS RAB releases on ERACHs.
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
This counter provides the duration taken by an RRC connection setup on an ERACH in the 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 an ERACH if the RRC connection is set up on an ERACH.
Formula
None
Unit
ms
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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. The measurement involves cells in the active set.
Measurement point
The measurement is triggered when the CRNC sends UL data over the ERACH FP on the Iub
interface.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Figure 1-379 Flow chart of hard handover and hard handover with relocation
A VS.HHO.EvalOut,VS.HHO.EvalIn
B VS.HHO.FailIntraFreqOut.RLSetupFail,
VS.HHO.FailInterFreqOut.RLSetupFail
C VS.HHO.FailIntraFreqOut.PrepFail,
VS.HHO.FailInterFreqOut.PrepFail
D VS.HHO.AttInterFreqOut,VS.HHO.AttInter
FreqOut.CS
E VS.HHO.AttIntraFreqOut.IntraNodeB,VS.
HHO.AttInterFreqOut.IntraNodeB
F VS.HHO.AttIntraFreqOut.InterNodeBIntra
RNC,VS.HHO.AttInterFreqOut.InterNode-
BIntraRNC
G VS.HHO.AttIntraFreqOut.InterRNC,VS.HH
O.AttInterFreqOut.InterRNC
H VS.HHO.SuccIntraFreqOut.IntraNodeB,
VS.HHO.SuccInterFreqOut.IntraNodeB
I VS.HHO.SuccInterFreqOut,
VS.HHO.SuccInterFreqOut.CS
J VS.HHO.SuccIntraFreqOut.InterNodeBIn-
traRNC, VS.HHO.SuccInterFreqOut.Inter-
NodeBIntraRNC
K VS.HHO.SuccIntraFreqOut.InterRNC,
VS.HHO.SuccInterFreqOut.InterRNC
L VS.HHO.FailIntraFreqOut.InvCfg,
VS.HHO.FailInterFreqOut.CfgUnsupp
M VS.HHO.FailIntraFreqOut.InterRNC.CfgU
nsupp,
VS.HHO.FailInterFreqOut.InterRNC.CfgU
nsupp
N VS.HHO.AttIntraFreqRelocPrep,
VS.HHO.AttInterFreqRelocPrep
O VS.HHO.SuccIntraFreqRelocPrep,
VS.HHO.SuccInterFreqRelocPrep
P VS.HHO.AttIntraFreqRelocExec,
VS.HHO.AttInterFreqRelocExec
Q VS.HHO.SuccIntraFreqRelocExec,
VS.HHO.SuccInterFreqRelocExec
R HHO.FailRelocPrepOut.NoResAvail,
HHO.FailRelocPrepOut.Texp
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 following figure, taking the PHYSICAL
CHANNEL RECONFIGURATION message as an example. When sending the PHYSICAL
CHANNEL RECONFIGURATION message to the UE, the RNC measures the counter in the
target cell of incoming hard handover.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of relocation preparation attempts with outgoing intra-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful relocation preparations with outgoing intra-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of relocation preparation attempts with outgoing inter-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful relocation preparations with outgoing inter-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 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 the handover are
fulfilled. Then, if the preparation for the handover fails before the RNC sends the PHYSICAL
CHANNEL RECONFIGURATION message to the UE, for example the failure in the RL
establishment on the Iub, 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-387 Failed hard handover procedure (failure in the RL establishment on the Iub
interface)
The measurement is triggered at point A 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 the handover are
fulfilled. Then, if the preparation for the handover fails before the RNC sends the PHYSICAL
CHANNEL RECONFIGURATION message to the UE, for example the failure in the RL
establishment on the Iur, 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-388 Failed hard handover procedure (failure in the RL establishment on the Iur
interface)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 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 before the RNC sends the PHYSICAL
CHANNEL RECONFIGURATION message to the UE, for example the failure in the RL
establishment on the Iub, 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-389 Failed hard handover procedure (failure in the RL establishment on the Iub
interface)
The measurement is triggered at point A 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 before the RNC sends the PHYSICAL
CHANNEL RECONFIGURATION message to the UE, for example the failure in the RL
establishment on the Iur, 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-390 Failed hard handover procedure (failure in the RL establishment on the Iur
interface)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-391 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 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-392 Failed hard handover procedure (failure in the RL establishment on the Iur
interface)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 or 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-393 Failed hard handover procedure (failure in the RL establishment on the Iub
interface)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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 intra-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 intra-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 intra-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 intra-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 intra-
frequency 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 intra-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 intra-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 intra-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 intra-
frequency 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.
Figure 1-407 Reconfiguration procedure during SRNC relocation with hard handover
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The counter provides the number of successful relocation executions with outgoing intra-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-413 Successful hard handover procedure due to the load balancing
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-414 Successful hard handover procedure due to the load balancing
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency 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.
Figure 1-429 Reconfiguration procedure during SRNC relocation with hard handover
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful relocation executions 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.
Measurement point
The measurement is triggered at point A as shown in the following figure. During the relocation
with inter-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
must be controlled by the SRNC.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency 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
times
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement items take statistics of the number of requests for incoming 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, the procedure shown in the
figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an example, 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 target cell of the UE in the hard handover procedure.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement items take statistics of the number of successful incoming inter-frequency
hard handovers initiated by the RNC according to different domain types.
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 target cell of the UE in the hard
handover procedure.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of successful for CS or PS Outgoing inter-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 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 inter-frequency hard handover.
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 inter-
frequency hard handover.
Figure 1-438 Hard handover procedure (failed operation for timer expiry)
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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 inter-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
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 inter-
frequency 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency hard handover.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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 measurement unit HSDPA Measurement(Cell) is used to measure the related
HSDPA service on the basis of Cell.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
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.SuccEstab VS.HSDPA.RAB.SuccEstab.BE.Golden
VS.HSDPA.RAB.SuccEstab.BE.Silver
VS.HSDPA.RAB.SuccEstab.BE.Copper
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of successful channel reconfiguration from
HS-DSCH service by channel reconfiguration type in the HSDPA serving 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 figure, when the RNC receives from
the UE a RADIO BEARER RECONFIGURATION COMPLETE message indicating a channel
reconfiguration for HSDPA service in the DCCC or RAB MODIFY procedure, the RNC
measures the item in the HSDPA serving cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
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, the RNC measures this item
in the cell of the RL. 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.
As shown at point B in the figure, when the RNC receives from a NodeB a RADIO LINK SETUP
RESPONSE message after sending the RADIO LINK SETUP REQUEST message, and if the
RL is set up for HSDPA service, the RNC measures this item in the cell of the RL. During the
RL setup, if the RADIO LINK SETUP REQUEST message contains an IE "HSDSCH FDD
Information", it indicates that the RL is set up for HSDPA service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the average and maximum number of HSDPA UEs in a serving cell.
The DC-HSDPA UE is only sampled in anchor carrier.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of the number of
HSDPA 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 HSDPA UEs in the
measurement period is obtained; by selecting the maximum value of sample data in the period,
the maximum number of HSDPA UEs in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 periodically takes samples (sampling periodicity is 5 seconds) of the number of
MAC-d flows. 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 MAC-d flows in the
measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the mean downlink throughput of single MAC-d flows in a 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 data is sent in an HSDPA serving cell, the RNC measures the data transfer time of all the
UEs and the total bytes sent in the cell. At the end of the measurement period, the RNC divides
the total bytes by the total data transfer time to obtain the mean downlink throughput of MAC-
d flow in the cell. The RLC header and the retransmitted data are excluded.
Formula
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of total bytes sent in downlink of all the HSDPA MAC-d
flows in a cell.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
When data is sent in an HSDPA serving cell, the RNC measures the number of total bytes sent
in the downlink (including data of all types of services) at the RLC layer for the MAC-d flow
in the cell. The RLC header and the retransmitted data are excluded.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the mean downlink throughput of HSDPA MAC-d flow of BE service for
golden subscriber in a 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 data of BE service for golden subscriber is sent in an HSDPA serving cell, the RNC
measures the total data transfer time of the BE service for golden subscriber and the total bytes
sent at the RLC layer in the HSDPA serving cell. At the end of the measurement period, the
RNC divides the total bytes by the total data transfer time of the BE service for golden subscriber
to obtain the mean downlink throughput of HSDPA MAC-d flows at the RLC layer of the BE
service for golden subscriber. The RLC header and the retransmitted data are excluded.
Formula
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of total bytes sent in the downlink of all the HSDPA MAC-
d flows of BE service for golden subscriber in a cell.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
When data of BE service for golden subscriber is sent in an HSDPA serving cell, the RNC
measures the number of total bytes sent in the downlink of the MAC-d flow of the BE service
at the RLC layer for golden subscriber.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the mean downlink throughput of HSDPA MAC-d flow of BE service for
silver subscriber in a 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 data of BE service for silver subscriber is sent in an HSDPA serving cell, the RNC
measures the total data transfer time of the BE service for silver subscriber and the total bytes
sent at the RLC layer in the HSDPA serving cell. At the end of the measurement period, the
RNC divides the total bytes by the total data transfer time of the BE service for silver subscriber
to obtain the mean downlink throughput of HSDPA MAC-d flows at the RLC layer of the BE
service for silver subscriber. The RLC header and the retransmitted data are excluded.
Formula
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of total bytes sent in the downlink of all the HSDPA MAC-
d flows of BE service for silver subscriber in a cell.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
When data of BE service for silver subscriber is sent in an HSDPA serving cell, the RNC
measures the number of total bytes sent in the downlink of the MAC-d flow of the BE service
at the RLC layer for silver subscriber.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the mean downlink throughput of HSDPA MAC-d flow of BE service for
copper subscriber in a 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 data of BE service for copper subscriber is sent in an HSDPA serving cell, the RNC
measures the total data transfer time of the BE service for copper subscriber and the total bytes
sent at the RLC layer in the HSDPA serving cell. At the end of the measurement period, the
RNC divides the total bytes by the total data transfer time of the BE service for copper subscriber
to obtain the mean downlink throughput of HSDPA MAC-d flows at the RLC layer of the BE
service for copper subscriber. The RLC header and the retransmitted data are excluded.
Formula
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of total bytes sent in the downlink of all the HSDPA MAC-
d flows of BE service for copper subscriber in a cell.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
When data of BE service for copper subscriber is sent in an HSDPA serving cell, the RNC
measures the number of total bytes sent in the downlink of the MAC-d flow of the BE service
at the RLC layer for copper subscriber.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement items provide the number of handover attempts between channels of different
types in a cell, as shown below.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 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. In this case, the RNC measures the items
in the serving cell of the HSDPA service according to the transport channels of UEs before and
after the reconfiguration. The RNC performs the handover of transport channels in the same cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA serving cell change attempts for cell.For
DC-HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement item provides the number of attempts to change HSDPA serving cells. 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 sending a PHYSICAL CHANNEL
RECONFIGURATION message to a UE, the RNC measures this item in the original serving
cell if the HSDPA serving cell changes. This item is used to measure changes of HSDPA serving
cells in soft handover procedure instead of hard handover procedure.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of successful HSDPA serving cell changes for
cell.For DC-HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
This measurement item provides the number of successful changes of serving cells. 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 receiving from a UE a PHYSICAL
CHANNEL RECONFIGURATION COMPLETE message, the RNC measures this item in the
original serving cell if the serving cell changes. This item is used to measure changes of serving
cells in soft handover procedure instead of hard handover procedure.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.12.16 Number of inter-RNC HSDPA Serving Cell Change Attempts for Cell
Measurement Counters
ID Counter Description
Description
This measurement counter provides the number of inter-RNC HSDPA serving cell change
attempts.It is measured in a serving cell.For DC-HSDPA users, this counter is measured only in
the cell with the primary carrier.
Measurement point
This measurement counter provides the number of inter-RNC HS-DSCH serving cell change
attempts. It is measured 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,[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 a PHYSICAL CHANNEL
RECONFIGURATION message the UE, the RNC measures this item in the original serving
cell on condition that the serving cell is changed and the target cell is in the DRNC. In this case,
the RNC only measures the item in serving cell change when the UE is during a soft handover.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.12.17 Number of Successful Inter-RNC HSDPA Serving Cell Changes for Cell
Measurement Counters
ID Counter Description
Description
This measurement counter provides the number of successful inter-RNC HSDPA serving cell
changes.It is measured in a serving cell.For DC-HSDPA users, this counter is measured only in
the cell with the primary carrier.
Measurement point
This measurement counter provides the number of successful inter-RNC HS-DSCH serving cell
changes.It is measured 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,[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 receiving from a UE a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message, the RNC measures this item in the original
serving cell on condition that the serving cell is changed and the target cell is in the DRNC.In
this case,the RNC only measures the item in serving cell change when the UE is during a soft
handover.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter provides the number of inter-RNC HSDPA hard handover attempts
without channel change.It is measured in a serving 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 figure.When the RNC sends a
PHYSICAL CHANNEL RECONFIGURATION message or a TRANSPORT CHANNEL
RECONFIGURATION message or a RADIO BEARER RECONFIGURATION message or a
RADIO BEARER SETUP message or a RADIO BEARER RELEASE message to the UE, the
RNC measures this item in the best cell before the hard handover procedure on condition that
the HSDPA hard handover is performed over Iur interface without channel change.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter provides the number of successful inter-RNC HSDPA hard
handovers without channel change.It is measured in a serving 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 B as shown in the figure.When the RNC receives a
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message or a TRANSPORT
CHANNEL RECONFIGURATION COMPLETE message or a RADIO BEARER
RECONFIGURATION COMPLETE message or a RADIO BEARER SETUP COMPLETE
message or a RADIO BEARER RELEASE COMPLETE messge from the UE, the RNC
measures this item in the best cell before the hard handover procedure on condition that the
HSDPA hard handover is performed over Iur without channel change.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of requests for intra-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.
Measurement point
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
sending a UE a PHYSICAL CHANNEL RECONFIGURATION message, the RNC measures
this item in the best cell from which the UE is handed over if an intra-frequency HSDPA hard
handover without channel change is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of successful intra-frequency HSDPA hard
handovers without channel change 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.
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
receiving from a UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message,
the RNC measures this item in the best cell from which the UE is handed over if an intra-
frequency HSDPA hard handover without channel change is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of inter-frequency HSDPA hard handover attempts
without channel change 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.
Measurement point
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
sending a UE a PHYSICAL CHANNEL RECONFIGURATION message,the RNC measures
this item in the best cell from which the UE is handed over if an inter-frequency HSDPA hard
handover without channel change is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of requests for intra-frequency hard handovers from
the HS-DSCH to the DCH in a cell. 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.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 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 best cell from which the UE is handed over if an intra-frequency hard handover from the
HSDPA to the DCH is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of successful intra-frequency hard handovers from
the HSDPA to the DCH in a cell. 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.For DC-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 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 best cell from which the UE is handed over if an intra-frequency
hard handover from the HSDPA to the DCH is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of requests for inter-frequency hard handovers from
the HSDPA to the DCH in a cell. 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.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 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 best cell from which the UE is handed over if an inter-frequency hard handover from the
HSDPA to the DCH is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of successful inter-frequency hard handovers from
the HSDPA to the DCH in a cell. 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.For DC-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 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 best cell from which the UE is handed over if an inter-frequency
hard handover from the HSDPA to the DCH is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA RAB establishment attempts 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 figure, when the RNC receives from
the CN a RAB ASSIGNMENT REQUEST message for setting up the HSDPA service. In this
case, the RNC measures this item in the HSDPA serving cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA RAB establishment attempts of BE
service for different prior level users in the HSDPA serving 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 figure, when the RNC receives from
the CN a RAB ASSIGNMENT REQUEST message for setting up the HSDPA service,the RNC
measures the items by the prior lever in the serving cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of successful HSDPA RAB establishments for
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 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 HSDPA service, the RNC
measures this item in the HSDPA serving cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement items provides the number of successful HSDPA RAB establishments of BE
service for different prior level users in the HSDPA serving 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 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 HSDPA service, the RNC
measures the items by the prior lever in the serving cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of RAB releases for the HSDPA service due to
user inactivity 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 figure. The RNC sends to the CN a
RAB RELEASE REQUEST message due to user inactivity. When the RNC receives a RAB
ASSIGNMENT REQUEST message,the RNC measures the items if there is a HSDPA service.
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 user inactivity.When the RNC receives an IU
RELEASE COMMAND message,the RNC measures the items if there is a HSDPA 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 user inactivity.When the RNC receives an IU
RELEASE COMMAND message,the RNC measures the items if there is a HSDPA service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of HSDPA RABs abnormal released for cell.For DC-HSDPA
users, this counter is measured only in the cell with the primary carrier.
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", for
details, see 3GPP TS 25.413), then this counter is measured in the HSDPA serving cell.
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", for
details, see 3GPP TS 25.413), then this counter is measured in the HSDPA serving cell.
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", for
details, see 3GPP TS 25.413), then this counter is measured in the HSDPA serving cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.12.34 Number of HSDPA RABs Abnormal Released Due to RF Cause for Cell
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that an HSDPA service is abnormally released in the
cell due to RF cause.For DC-HSDPA 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 RF 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 of "Radio
Connection With UE Lost" or "Failure in the Radio Interface Procedure", for details, see 3GPP
TS 25.413), then this counter is measured in the HSDPA serving cell that the UE camps on if
the RAB is for a HSDPA service.
As shown in point A of the figure, when a RF 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 of "Radio
Connection With UE Lost" or "Failure in the Radio Interface Procedure", for details, see 3GPP
TS 25.413), then this counter is measured in the HSDPA serving cell that the UE camps on if
the RAB is for a HSDPA service.
As shown in point A of the figure, when a RF 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 of "Radio
Connection With UE Lost" or "Failure in the Radio Interface Procedure", for details, see 3GPP
TS 25.413), then this counter is measured in the HSDPA serving cell that the UE camps on if
the RAB is for a HSDPA service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of normally released HSDPA RABs 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 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 this item
in the HSDPA serving cell if it is a HSDPA service.
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
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter provides the number of inter-RNC hard handover from HSDPA to
DCH attempts in a cell. 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.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 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 best cell before the hard handover if an inter-RNC hard handover from the HSDPA to the
DCH is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter provides the number of successful inter-RNC hard handovers from
HSDPA to DCH in a cell. 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.For DC-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 figure, the procedure shown in the
figure takes a RADIO BEARER RECONFIGURATION message as an example, when
receiving from an UE a RADIO BEARER RECONFIGURATION COMPLETE message, the
RNC measures this item in the best cell before the hard handover if an inter RNC hard handover
from HSDPA to DCH is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the Number of HSDPA 64QAM RAB Setup Requests for
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 figure, when the RNC receives from
the CN a RAB ASSIGNMENT REQUEST message for setting up the HSDPA service using
64QAM. In this case, the RNC measures this item in the serving cell of the HSDPA service
using 64QAM .
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA 64QAM RABs Setup Successfully for
cell
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 HSDPA service using
64QAM, the RNC measures this item in the serving cell of the HSDPA service using 64QAM.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA 64QAM Abnormal Release(RF
included) for 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 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.
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 if is a HSDPA service using 64QAM.
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 if is a HSDPA service using 64QAM.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA 64QAM RABs Normal Released.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 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 this item
in the HSDPA cell if it is a HSDPA service using 64QAM.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA MIMO RABs Setup Request.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 figure, when the RNC receives from
the CN a RAB ASSIGNMENT REQUEST message for setting up the HSDPA service. In this
case, the RNC measures this item in the serving cell of the HSDPA service using MIMO.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA MIMO RABs Setup Successfully for
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 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 HSDPA service, the RNC
measures this item in the serving cell of the HSDPA service using MIMO.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA MIMO RAB Release due to normal
cause for 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 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 this item
in the HSDPA cell if it is a HSDPA service using MIMO.
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 this item in the HSDPA cell if it is a HSDPA
service using MIMO.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA MIMO+64QAM RABs Setup Request
for 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 figure, when the RNC receives from
the CN a RAB ASSIGNMENT REQUEST message for setting up the HSDPA service. In this
case, the RNC measures this item in the serving cell of the HSDPA service using MIMO
+64QAM.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA MIMO+64QAM RAB Setup Success
for 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 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 HSDPA service, the RNC
measures this item in the serving cell of the HSDPA service using MIMO+64QAM.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA MIMO+64QAM RAB Release due to
abnormal cause for cell(including RF Cause).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 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 if is a HSDPA service using MIMO+64QAM.
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 if is a HSDPA service using MIMO+64QAM.
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 if is a HSDPA service using MIMO+64QAM.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA MIMO+64QAM RABs normal released
for 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 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 this item
in the HSDPA cell if it is a HSDPA service using MIMO+64QAM.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of DC-HSDPA RAB Setup Request, only the
primary carrier of DC-HSDPA counted for cell.
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 HSDPA service. In this
case, the RNC measures this item in the serving cell of the HSDPA service using DC-HSDPA.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of DC-HSDPA RAB Setup Success, only the
primary carrier of DC-HSDPA counted for cell.
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 HSDPA service using
DC-HSDPA, the RNC measures this item in the serving cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDSCH RAB of DC Abnormal Release(RF
included), only the primary carrier of DC counted.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 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 if is a HSDPA service using DC.
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
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 if is a HSDPA service using DC.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDSCH RAB of DC Release due to normal
cause, only the primary carrier of DC counted.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 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 this item
in the HSDPA cell if it is a HSDPA service using DC.
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 this item in the HSDPA cell if it is a HSDPA
service using DC.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of HSDPA MIMO RABs Abnormal Release(RF
included) for 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 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 HSDPA serving cell if it is a HSDPA service using
MIMO.
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 HSDPA serving cell if it is a HSDPA service using
MIMO.
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 HSDPA serving cell if it is a HSDPA service using
MIMO.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
Description
These counters provide the average and maximum number of HSDPA UEs with various
categories in a serving cell. The HSDPA UEs with categoriy 21-28 using the DC-HSDPA feature
are only sampled in anchor carriers.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of the number of
HSDPA 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 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
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of HSDPA RABs failed to be established due to insufficiency
of different resources in the HSDPA serving 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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the average downlink throughput of the Traffic PS
Conversational beared on HSDSCH in the 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
The RNC measures all DL traffic volume (unit: bit) and duration (unit: ms) of the PS
conversational service beared on HSDSCH in the cell of the RLC layer. At the end of the
measurement period, the RNC calculates average bit rate.
Formula
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of downlink bytes of Transport Blocks of traffic
PS conversational beared on HSDSCH in the cell.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 RNC measures the total DL volume of PS conversational service beared on HSDSCH in
the cell of the RLC layer.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the average number of 64QAM 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 of the number of 64QAM 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 64QAM UEs in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 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
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the average number of MIMO+64QAM 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 of the number of MIMO+64QAM 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+64QAM UEs in the measurement period is
obtained.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the average number of DC-HSDPA UEs whose anchor or supplementary
carrier is the current cell in a serving cell.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of the number of DC-
HSDPA UEs, whose anchor or supplementary carrier being the current cell. 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 DC-HSDPA UEs whose anchor or supplementary
carrier being the current cell in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that 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.For DC-HSDPA users, this counter is measured only in the cell with
the primary carrier.
Measurement point
As shown in the figure, the measurement is triggered at point A. 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that 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.For DC-HSDPA users, this counter is measured only in the cell with
the primary carrier.
Measurement point
As shown in the figure, the measurement is triggered at point B. When the RNC receives a
PHYSICAL CHANNEL RECONFIG COMPLETE message from the UE, if an inter-frequency
handover is to be performed on HSDPA users through the DRD procedure according to the
intelligent user recognition algorithm, the RNC takes statistics of the number of times that
HSDPA users in connected mode are successfully switched out of the serving cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the RNC attempts to switch HSDPA users in
connected mode into the target cell through the DRD procedure according to the intelligent user
recognition algorithm.For DC-HSDPA users, this counter is measured only in the cell with the
primary carrier.
Measurement point
As shown in the figure, the measurement is triggered at point A. According to the intelligent
user recognition algorithm, after the RNC receives a CQI measurement report from the NodeB,
the RNC selects a proper target cell and then initiates an inter-frequency handover. In the target
cell, 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the RNC successfully switches HSDPA users in
connected mode into the target cell through the DRD procedure according to the intelligent user
recognition algorithm.For DC-HSDPA users, this counter is measured only in the cell with the
primary carrier.
Measurement point
As shown in the figure, the measurement is triggered at point B. When the RNC receives a
PHYSICAL CHANNEL RECONFIG COMPLETE message from the UE, if an inter-frequency
handover is to be performed on HSDPA users through the DRD procedure according to the
intelligent user recognition algorithm, the RNC takes statistics of the number of times that
HSDPA users in connected mode are successfully switched into the target cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of RABs Abnormally Released for PS HSDPA Services during
the State Transition from CELL_DCH to CELL_PCH or URA_PCH in the serving cell.For DC-
HSDPA 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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of DC-HSDPA+MIMO RAB Setup Request, only
the primary carrier of DC-HSDPA counted for cell.
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 HSDPA service. In this
case, the RNC measures this item in the serving cell of the HSDPA service using DC-HSDPA
+MIMO.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of DC-HSDPA+MIMO RAB Setup Success, only
the primary carrier of DC-HSDPA counted for cell.
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 HSDPA service, the RNC
measures this item in the serving cell of the HSDPA service using DC-HSDPA+MIMO.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of DC-HSDPA+MIMO RAB Release due to
normal cause, only the primary carrier of DC counted.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 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 this item
in the HSDPA cell if it is a HSDPA service using DC-HSDPA+MIMO.
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 this item in the HSDPA cell if it is a HSDPA
service using DC-HSDPA+MIMO.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of DC-HSDPA+MIMO RAB Abnormal Release
(RF included), only the primary carrier of DC counted.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 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 if is a HSDPA service using DC-HSDPA+MIMO.
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 if is a HSDPA service using DC-HSDPA+MIMO.
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 if is a HSDPA service using DC-HSDPA+MIMO.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.12.72 Average Throughput on HSDPA MAC-d Flow for Cell (Excluding the
Data of Low-Traffic Users)
Measurement Counters
ID Counter Description
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
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
1.10.12.73 Number of Bytes Sent on HSDPA MAC-d Flow for Cell (Excluding the
Bytes of Low-Traffic Users)
Measurement Counters
ID Counter Description
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 low-
traffic users at the RLC layer.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the average number of free HSDPA users in a serving cell.For DC-HSDPA
users, this counter is measured only in the cell with the primary carrier.This counter takes effect
only when the "free HSDPA user" feature has been activated.
Measurement point
The system periodically takes samples from the number of free HSDPA users and then obtains
the average value at the end of the measurement period.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the maximum number of free HSDPA users in a serving cell.For DC-
HSDPA users, this counter is measured only in the cell with the primary carrier.This counter
takes effect only when the "free HSDPA user feature" has been activated.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) from the number of
free HSDPA users and then obtains the maximum value at the end of the measurement period.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of HSDPA serving cell change attempts that are triggered by
unbalanced Iub resources between NodeBs.For DC-HSDPA users, this counter is measured only
in the cell with the primary carrier.
Measurement point
When initiating an HSDPA serving cell change based on Iub resource usage, the RNC sends the
UE one of the following messages:[1]PHYSICAL CHANNEL RECONFIGURATION, [2]
TRANSPORT CHANNEL RECONFIGURATION. The UE responds with one of the following
messages: [1]PHYSICAL CHANNEL RECONFIGURATION COMPLETE, [2]PHYSICAL
CHANNEL RECONFIGURATION FAILURE, [3]TRANSPORT CHANNEL
RECONFIGURATION COMPLETE, [4]TRANSPORT CHANNEL RECONFIGURATION
FAILURE.
Assume that the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message
when initiating such an HSDPA serving cell change. The measurement is triggered in the original
serving cell at point A after the RNC sends this message, as shown in the following figure. This
counter measures only the serving cell changes initiated when there is more than one cell in the
active set.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful HSDPA serving cell changes that are triggered
by unbalanced Iub resources between NodeBs.For DC-HSDPA users, this counter is measured
only in the cell with the primary carrier.
Measurement point
When initiating an HSDPA serving cell change based on Iub resource usage, the RNC sends the
UE one of the following messages: [1]PHYSICAL CHANNEL RECONFIGURATION, [2]
TRANSPORT CHANNEL RECONFIGURATION. The UE responds with one of the following
messages: [1]PHYSICAL CHANNEL RECONFIGURATION COMPLETE, [2]PHYSICAL
CHANNEL RECONFIGURATION FAILURE, [3]TRANSPORT CHANNEL
RECONFIGURATION COMPLETE, [4]TRANSPORT CHANNEL RECONFIGURATION
FAILURE.
Assume that the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message
when initiating such an HSDPA serving cell change. The measurement is triggered in the original
serving cell at point B after the RNC receives a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from the UE, as shown in the following figure. This counter measures
only the serving cell changes initiated when there is more than one cell in the active set.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
VS.HSUPA.RAB.AttEstab 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
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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 or if the RNC receives a RADIO LINK SETUP
FAILURE/RADIO LINK ADDITION FAILURE 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement items takes statistics of the number of HSUPA RAB establishment attempts
of BE service for different prior level users 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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement items takes statistics of the number of successful HSUPA RAB
establishments of BE service for different prior level users 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. 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter provides the number of HSUPA RABs released due to UE signaling
connection release and the second RRC connection for a UE in a cell.
Note: Second RRC Connection Request: The UE sends a second RRC CONNECTION
REQUEST message to the RNC before releasing the previously assigned RAB.
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 after RABs have
been set up. 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). Upon
reception of the IU RELEASE REQUEST message, the CN sends an IU RELEASE
COMMAND message to the RNC. After receiving this message, the RNC releases the
corresponding RAB and sends an IU RELEASE COMPLETE message to the CN. In this case,
the RNC measures the item in the HSUPA serving cell if the released RAB is HSUPA service.
The measurement is triggered at point A as shown in the figure, after receiving an RRC
CONNECTION REQUEST message from a UE, the RNC determines that the message is sent
by the same UE with RAB using a COMMAND ID message sent by the CN,and then 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). Upon reception of the IU
RELEASE REQUEST message, the CN sends an IU RELEASE COMMAND message to the
RNC. After receiving this message, the RNC releases the corresponding RAB and sends an IU
RELEASE COMPLETE message to the CN. In this case, the RNC measures the item in the
HSUPA serving cell if the released RAB is HSUPA service.
Figure 1-540 RAB release procedure caused by the second RRC connection setup request from
the same UE
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of successful HSUPA serving cell changes
due to intra-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 B shown in the figure. When the RNC receives a
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message or a TRANSPORT
CHANNEL RECONFIGURATION COMPLETE message or a RADIO BEARER
RECONFIGURATION COMPLETE message or a RADIO BEARER SETUP COMPLETE
message or a RADIO BEARER RELEASE COMPLETE message from the UE, the RNC
measures this item in the HSUPA serving cell before the hard handover if an EDCH-to-EDCH
intra-frequency hard handover is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of HSUPA serving cell changes due to
intra-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
RECONFIGURATION message or a RADIO BEARER RECONFIGURATION message or a
RADIO BEARER SETUP message or a RADIO BEARER RELEASE message to the UE, the
RNC measures this item in the HSUPA serving cell before the hard handover if an EDCH-to-
EDCH intra-frequency hard handover is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of successful HSUPA serving cell changes
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 B shown in the figure. When the RNC receives a
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message or a TRANSPORT
CHANNEL RECONFIGURATION COMPLETE message or a RADIO BEARER
RECONFIGURATION COMPLETE message or a RADIO BEARER SETUP COMPLETE
message or a RADIO BEARER RELEASE COMPLETE message from the UE, the RNC
measures this item in the HSUPA serving cell before the hard handover if an EDCH-to-EDCH
inter-frequency hard handover is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-to-
EDCH inter-frequency hard handover is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of successful HSUPA intra-Frequency
hard handovers 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 B shown in the figure. When the RNC receives a RADIO
BEARER RECONFIGURATION COMPLETE message from the UE, the RNC measures this
item in the HSUPA serving cell before the hard handover if an EDCH-to-DCH intra-frequency
hard handover is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of attempts to switch the channel type from
EDCH to DCH due to the intra-frequency hard 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 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 intra-frequency hard
handover is performed.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of successful HSUPA Inter-Frequency
Hard Handovers 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 B shown in the figure. When the RNC receives a RADIO
BEARER RECONFIGURATION COMPLETE message from 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement items take statistics of 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, this counter is 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of times that the handover between different channels
succeeds in the 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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the mean uplink throughput of HSUPA MAC-d flow of BE service for
golden subscriber in a cell.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 of BE service for golden subscriber is received in an HSUPA serving cell, the RNC
measures the total data transfer time of the BE service for golden subscriber and the total bytes
received in the uplink at the RLC layer in the HSUPA serving cell. At the end of the measurement
period, the RNC divides the total bytes by the total data transfer time of the BE service for golden
subscriber to obtain the mean uplink throughput of HSUPA MAC-d flows at the RLC layer of
the BE service for golden subscriber. The RLC header and the retransmitted data are excluded.
Formula
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of total bytes received in the uplink of all the HSUPA MAC-
d flows of BE service for golden subscriber 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 of BE service for golden subscriber is received 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 for golden subscriber.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the mean uplink throughput of HSUPA MAC-d flow of BE service for
silver subscriber in a cell.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 of BE service for silver subscriber is received in an HSUPA serving cell, the RNC
measures the total data transfer time of the BE service for silver subscriber and the total bytes
received in the uplink at the RLC layer in the HSUPA serving cell. At the end of the measurement
period, the RNC divides the total bytes by the total data transfer time of the BE service for silver
subscriber to obtain the mean uplink throughput of HSUPA MAC-d flows at the RLC layer of
the BE service for silver subscriber. The RLC header and the retransmitted data are excluded.
Formula
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of total bytes received in the uplink of all the HSUPA MAC-
d flows of BE service for silver subscriber 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 of BE service for silver subscriber is received 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 for silver subscriber.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the mean uplink throughput of HSUPA MAC-d flow of BE service for
copper subscriber in a cell.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 of BE service for copper subscriber is received in an HSUPA serving cell, the RNC
measures the total data transfer time of the BE service for copper subscriber and the total bytes
received in the uplink at the RLC layer in the HSUPA serving cell. At the end of the measurement
period, the RNC divides the total bytes by the total data transfer time of the BE service for copper
subscriber to obtain the mean uplink throughput of HSUPA MAC-d flows at the RLC layer of
the BE service for copper subscriber. The RLC header and the retransmitted data are excluded.
Formula
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of total bytes received in the uplink of all the HSUPA MAC-
d flows of BE service for copper subscriber 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 of BE service for copper subscriber is received 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 for copper subscriber.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of successful HSUPA 16QAM RAB
establishments for cell.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of HSUPA 16QAM RABs Abnormal
Released including RF causes 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. 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.
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
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of HSUPA 16QAM Release due to normal
cause for 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 HSUPA serving cell if it is a HSUPA service using 16QAM.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item takes statistics of the number of HSUPA 16QAM RAB Setup Attempts
for 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, and if the the RNC decides the HSUPA
RABs, it measures this item in the HSUPA serving cell using 16QAM.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.13.42 Number of HSUPA RABs Abnormal Released due to RF Failures for Cell
Measurement Counters
ID Counter Description
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.
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" ,
reference to 3GPP TS 25.413),the RNC measures the items if is a HSUPA service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of EDCH MAC-d flow setup requests in the cell.For DC-
HSUPA 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.
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 MAC-
d Flows To Add" IE.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 (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
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
byte
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 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 sends the UE a
RADIO BEARER RECONFIGURATION message. In this case, this counter is measured in the
best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the average number of HSUPA 16QAM UEs in a serving cell.
Measurement point
The system periodically 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
1.10.13.53 Number of UEs Supporting E-DPCCH Boosting and CPC for Cell
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 DC-
HSUPA 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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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 DC-
HSUPA 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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the mean and maximum numbers of HSUPA 2 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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the mean 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
None
A 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 measurement unit.)
B 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 measurement unit.)
C IRATHO.AttOutCS
D IRATHO.SuccOutCS,
VS.IRATHO.SuccOutCS.RF
E IRATHO.FailRelocPrepOutCS.UKnowRN
C, IRATHO.FailRelocPrepOutCS.NoResA-
vail(These counters list here are only part
examples. Other Specific counters are
triggered based on other specific causes,
please refer to this measurement unit.)
F IRATHO.FailOutCS.CfgUnsupp,
IRATHO.FailOutCS.PhyChFail
G VS.IRATHO.FailOutCS.NoReply
H VS.IRATHO.AttOutPSUE
I IRATHO.SuccOutPSUTRAN,
IRATHO.SuccOutPSUE
J VS.IRATHO.FailOutPSUTRAN.NoReply
K IRATHO.AttOutPSUTRAN,
VS.IRATHO.AttOutPSUTRAN.RF
L IRATHO.FailOutPSUTRAN.CfgUnsupp,
IRATHO.FailOutPSUTRAN.PhyChFail
A VS.IRATHO.AttRelocPrepInCS
B VS.IRATHO.SuccRelocPrepInCS
C VS.IRATHO.AttInCS
D VS.IRATHO.SuccInCS
E VS.IRATHO.FailRelocPrepInCS.ResUna-
vail,
VS.IRATHO.FailRelocPrepInCS.TgtHigh-
Load
F VS.IRATHO.FailInCS.NoReply
G RRC.AttConnEstab.IRATCelRes
H RRC.SuccConnEstab.IRATCelRes
I RRC.AttConnEstab.IRATCCO
J RRC.SuccConnEstab.IRATCCO
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
VS.IRATHO.AttRelocPrepOutPS VS.SRVCC.U2GERAN.AttRelocPre-
pOutPS
VS.IRATHO.SuccRelocPrepOutPS VS.SRVCC.U2GERAN.SuccRelocPre-
pOutPS
VS.IRATHO.SuccRelocOutPS VS.SRVCC.U2GERAN.SuccRelocOutPS
Measurement Counters
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful preparation attempts for PS outgoing inter-
RAT handover in the best cell 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 "Normal Release",
"Successful Relocation" or "Network Optimization". In this case, the corresponding counters
are measured in the best cell that the UE camps on based on the cause value.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
Description
These counters provide the number of failed preparations for CS or Enhanced PS outgoing inter-
RAT handover 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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of 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 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 inter-
RAT 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the number of failed preparations for CS or Enhanced PS incoming inter-
RAT 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 counters are measured according to the value of
TargetCellId in the RELOCATION REQUEST message.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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". In this case, this counter is measured in
the cell that the UE camps on before handover.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 these counters
are measured according to the value of TargetCellId in the RELOCATION REQUEST message.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 counters are measured in the best cell that the UE
camps on based on the handover cause.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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. In this case, this counter is measured in
the cell that the UE camps on before handover.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful PS outgoing inter-RAT handovers initiated by
the RNC in the best cell that the UE camps on before the handover.
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" and sends an IU RELEASE COMPLETE message during
the PS outgoing inter-RAT handover. In this case, the PS outgoing handover succeeds and these
counters are measured in the best cell that the UE camps on before the handover.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.14.18 Number of Times that the Timer Waiting for Iu Release Command
Expires in CS or Enhanced PS Outgoing Inter-RAT Handover for Cell
Measurement Counters
ID Counter Description
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.
Figure 1-620 Timeout Waiting for Iu Release Command in CS or Enhanced PS Outgoing Inter-
RAT Handover
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.14.19 Number of Times that the Timer Waiting for Iu Release Command
Expires in PS Outgoing Inter-RAT Handover Initiated by RNC for Cell
Measurement Counters
ID Counter Description
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 inter-
RAT 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-621 Timeout waiting for Iu Release Command in PS Outgoing Inter-RAT Handover
Initiated by RNC
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of PS outgoing inter-RAT handover attempts in the best cell
due to different causes. These counters do not count the number of PS outgoing inter-RAT
handovers in the signaling-only scenario.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of successful PS outgoing inter-RAT handovers in the best
cell due to different causes. These counters do not count the number of PS outgoing inter-RAT
handovers in the signaling-only scenario.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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-627 SRNC relocation preparation failure due to expiry of relocation command
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
RAT reselection parameters at the GSM and the handover parameters to check whether ping-
pong handovers exist.
Measurement point
The measurement is triggered at point A as shown in the 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
RAT 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.
Figure 1-636 Procedure for a failed outgoing inter-RAT handover in the CS domain
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
RAT 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-637 Procedure for a failed outgoing inter-RAT handover in the PS domain
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Figure 1-638 Procedure for a failed outgoing inter-RAT handover in the PS domain
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter takes statistics of the number of RLs that are unavailable on the Iub
interface in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the NodeB sends a RADIO
LINK FAILURE INDICATION message to the RNC, indicating that one or morel RLs are not
available. In this case, the RNC measures the counter in the cell where the RL is unavailable.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement counters provide the number of RLs that are unavailable on the Iub interface
in a cell.
The following table describes the meaning of each counter.
Counter Description
Measurement point
The measurement is triggered at point A as shown in the figure, when the NodeB sends a RADIO
LINK FAILURE INDICATION message to the RNC, indicating that one or more RLs are not
available. In this case, the RNC measures the counters in the cell where the RLs are not available
for different failure causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement counter takes statistics of the number of RLs unsuccessfully restored on the
Iub interface due to no response from the NodeB.
Measurement point
After allocating resources to a new RL or having received a RL FAIL IND message, the RNC
will start 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 upon
expiry of the timer, it measures the counter in the cell where the RLs are to be restored.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement counters provide the number of RLs unsuccessfully reconfigured on the Iub
interface in a cell for different causes.
Counter Description
Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Overview
This measurement unit is used to measure the number of setups and releases of the MBMS traffic.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
1.10.17.1 Number of Releases of PTP MBMS Services because the new best cell is
on PTM mode
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.17.10 Number of Transitions from PTP MBMS Service to PTM MBMS Service
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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. This counter is calculated based on the RSCP value reported by the UE. As specified in
3GPP TS25.133, the mapping between the reported RSCP value and the measured RSCP value
is: Measured RSCP value = Reported RSCP value - 115.
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 with the best signal quality in the
active set.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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. This counter is 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 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 with the best signal quality in the
active set.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 when the RNC sends a message of PAGING TYPE 1.This counter
includes the retransmitted paging messages.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that CS paging preempts the resources of PS paging
due to PCH congestion in a cell.
Measurement point
This counter is incremented by one each time the CS paging preempts the resources of PS paging
due to PCH congestion.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that CS paging successfully preempts the resources
of PS paging due to PCH congestion in a cell.
Measurement point
This counter is incremented by one each time the CS paging successfully preempts the resources
of PS paging due to PCH congestion and is successfully sent.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.19.5 Number of Level-1 Paging Attempts for UEs Processing Real-Time or Non-
Real-Time Services in the URA_PCH State
Measurement Counters
ID Counter Description
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).
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.19.6 Number of Successful Level-1 Paging Attempts for UEs Processing Real-
Time or Non-Real-Time Services in the URA_PCH State
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.19.7 Number of Successful Layered Paging Attempts for UEs Processing Real-
Time or Non-Real-Time Services in the URA_PCH State
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.19.8 Number of PAGING TYPE 1 Messages Sent by the RNC to UEs in the
URA_PCH State
Measurement Counters
ID Counter Description
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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.19.9 Number of CS PAGING TYPE 1 Messages Sent by the RNC to UEs in the
Idle State
Measurement Counters
ID Counter Description
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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.19.10 Number of PS PAGING TYPE 1 Messages Sent by the RNC to UEs in the
Idle State
Measurement Counters
ID Counter Description
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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Overview
This measurement unit provides counters measured by operator in a cell.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
These counters provide the average, minimum, and maximum uplink credit consumption of
operator0 in a cell. These counters are measured only when the ICR Demarcation function takes
effect for a cell.
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
None
Measurement Counters
ID Counter Description
Description
These counters provide the average, minimum, and maximum uplink credit consumption of
operator1 in a cell. These counters are measured only when the ICR Demarcation function takes
effect for a cell.
Measurement point
The uplink credit consumption of operator1 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
None
Measurement Counters
ID Counter Description
Description
These counters provide the average, minimum, and maximum uplink credit consumption of
operator2 in a cell. These counters are measured only when the ICR Demarcation function takes
effect for a cell.
Measurement point
The uplink credit consumption of operator2 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
None
Measurement Counters
ID Counter Description
Description
These counters provide the average, minimum, and maximum uplink credit consumption of
operator3 in a cell. These counters are measured only when the ICR Demarcation function takes
effect for a cell.
Measurement point
The uplink credit consumption of operator3 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
None
Measurement Counters
ID Counter Description
Description
This counter provides the average equivalent Erlangs consumed by all CS services of operator0
in a cell. This counter is measured only when the ICR Demarcation function takes effect for a
cell.
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
None
Measurement Counters
ID Counter Description
Description
This counter provides the average equivalent Erlangs consumed by all CS services of operator1
in a cell. This counter is measured only when the ICR Demarcation function takes effect for a
cell.
Measurement point
The equivalent Erlangs consumed by operator1' 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 operator1 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 operator1 in the cell are reduced. At the end of
a measurement period, the average equivalent Erlangs consumed by all CS services of operator1
are obtained by dividing the accumulated value in the period by the number of samples.
Formula
None
Unit
Erl
Related Features
None
Measurement Counters
ID Counter Description
Description
This counter provides the average equivalent Erlangs consumed by all CS services of operator2
in a cell. This counter is measured only when the ICR Demarcation function takes effect for a
cell.
Measurement point
The equivalent Erlangs consumed by operator2' 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 operator2 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 operator2 in the cell are reduced. At the end of
a measurement period, the average equivalent Erlangs consumed by all CS services of operator2
are obtained by dividing the accumulated value in the period by the number of samples.
Formula
None
Unit
Erl
Related Features
None
Measurement Counters
ID Counter Description
Description
This counter provides the average equivalent Erlangs consumed by all CS services of operator3
in a cell. This counter is measured only when the ICR Demarcation function takes effect for a
cell.
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
None
Measurement Counters
ID Counter Description
Description
These counters provide the average and maximum number of spreading codes occupied by
operator0 in a cell. These counters are measured only when the ICR Demarcation function takes
effect for a cell.
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
None
Measurement Counters
ID Counter Description
Description
These counters provide the average and maximum number of spreading codes occupied by
operator1 in a cell. These counters are measured only when the ICR Demarcation function takes
effect for a cell.
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
None
Measurement Counters
ID Counter Description
Description
These counters provide the average and maximum number of spreading codes occupied by
operator2 in a cell. These counters are measured only when the ICR Demarcation function takes
effect for a cell.
Measurement point
The RNC measures this counter for each operator on a per cell basis. The number of spreading
codes occupied by operator2 is sampled every 5 seconds in a measurement period. Spreading
codes occupied by all R99 users of operator2 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 operator2's R99 users is obtained. The average number of
spreading codes occupied by operator2's R99 users is obtained by dividing the accumulated
value in the period by the number of samples.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
Description
These counters provide the average and maximum number of spreading codes occupied by
operator3 in a cell. These counters are measured only when the ICR Demarcation function takes
effect for a cell.
Measurement point
The RNC measures this counter for each operator on a per cell basis. The number of spreading
codes occupied by operator3 is sampled every 5 seconds in a measurement period. Spreading
codes occupied by all R99 users of operator3 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 operator3's R99 users is obtained. The average number of
spreading codes occupied by operator3's R99 users is obtained by dividing the accumulated
value in the period by the number of samples.
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
This counter measures the number of successful PTT call initiation attempts or responses during
a P2D procedure in a cell. This counter is used to analyze PTT service establishment of UEs that
send CELL UPDATE messages to initiate or respond to PTT calls.
Measurement point
A UE in the CELL_PCH or URA_PCH state can initiate or respond to a PTT call by sending a
CELL UPDATE message during a P2D procedure. The measurement is triggered at point B
shown in Figure 1 when the RNC receives a RADIO BEARER RECONFIGURATION
COMPLETE message from the UE that initiates or responds to a PTT call during a P2D
procedure. A UE sends a CELL UPDATE message to initiate a PTT call when all 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 this message are uplink data
transmission, Originating Conversational Call, and TRUE, respectively. This message does not
contain the IE CS Call Type. A UE sends a CELL UPDATE message to respond to a PTT call
when all the following conditions are met: The UE has set up a PTT service. There is data to be
transmitted for PTT services in the downlink. The value of the IE Cell update cause contained
in this message is paging response.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.21.2 Number of PTT Call Initiation or Response Attempts of UEs Using Only
the PTT Service in the CELL_FACH State for Cell
Measurement Counters
ID Counter Description
Description
This counter provides the number of PTT call initiation or response attempts of a UE in the
CELL_FACH state processing only the PTT service in the cell. This counter is used to analyze
PTT service access of the UE in the CELL_FACH state.
Measurement point
At point A shown in the following figure, the calling or called UE in the CELL_FACH state
performs a state transition triggered by an event 4a measurement report. Note that if a UE enabled
with E-PCH transits to CELL_FACH after sending an MEASUREMENT REPORT message
not carrying event 4a measurement, it is counted in the UE in the CELL_FACH state. The
measurement is incremented by one in the cell serving the UE each time the RNC receives an
event 4a measurement report from the UE processing only the PTT service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful PTT call initiation attempts or responses of UEs
using only the PTT service in the CELL_FACH state in a cell.
The counter is used with the counter "Number of PTT Call Initiation or Response Attempts of
UEs Using Only the PTT Service in the CELL_FACH State for Cell" to analyze the success rate
of UEs initiating a PTT call in the CELL_FACH state.
Measurement point
At point B shown in the following figure, either the calling or called UE in the CELL_FACH
state, including the UE supporting E-PCH that transfers to the CELL_FACH state after sending
a MEASUREMENT REPORT message not containing an event 4A report, triggers state
transition using a downlink event 4A report. During the process, when the RNC receives a
RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the
measurement is triggered in the cell that the UE camps on if the UE uses only the PTT service
and RBs are reconfigured because of increased PTT traffic and UE state transition to
CELL_DCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful PTT call initiation attempts or responses of UEs
using the PTT and other services in the CELL_FACH state in a cell.
The counter is used with the counter "Number of PTT Call Initiation Attempts or Responses of
UEs Using the PTT and Other Services in the CELL_FACH State for Cell" to analyze the success
rate of PTT calls in the CELL_FACH state.
Measurement point
At point B shown in the following figure, either the calling or called UE in the CELL_FACH
state, including the UE supporting E-PCH that transfers to the CELL_FACH state after sending
a MEASUREMENT REPORT message not containing an event 4A report, triggers state
transition using a downlink event 4A report. During the process, when the RNC receives a
RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the
measurement is triggered in the cell that the UE camps on if the UE uses the PTT and other
services and RBs are reconfigured because of increased PTT traffic and UE state transition to
CELL_DCH.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of complete PTT calls in a cell. If UE state transition to
CELL_DCH is triggered by PTT data transmission, it is considered that a PTT call ends properly
when the UE state transfers from CELL_DCH to another RRC connection state.
The counter is used with the counter "Number of RABs Abnormally Released During PTT Calls
for Cell" to analyze the call drop rate of PTT services.
Measurement point
At point A shown in the following figure, when a PTT call ends, the RNC sends a RADIO
BEARER RECONFIGURATION message to the UE to trigger the UE state transition from
CELL_DCH to another RRC connection state. When the RNC receives a RADIO BEARER
RECONFIGURATION COMPLETE message from the UE, 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 UE state transition to CELL_DCH is caused by a PTT
call.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.21.6 Number of RABs Abnormally Released During PTT Calls for Cell
Measurement Counters
ID Counter Description
Description
This counter provides the number of RABs abnormally released during PTT calls in a cell.
The counter is used with the counter "Number of Complete PTT Calls for Cell" to analyze the
call drop rate of PTT services.
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of CELL UPDATE CONFIRM messages sent by the RNC
before RADIO BEARER RECONFIGURATION COMPLETE message received by RNC
during the state transitions from CELL_PCH/URA_PCH to CELL_DCH triggered by cell
update in a cell. This counter is measured on the basis of the number of CELL UPDATE
CONFIRM messages indicating state transition from CELL_PCH/URA_PCH to CELL_DCH
that are sent from the RNC.
The counter is used to analyze the impact of cell update on end-to-end delay of PTT services.
Measurement point
At point B shown in the following figure, when the RNC receives a RADIO BEARER
RECONFIGURATION COMPLETE message indicating UE state transition completion during
the state transition from CELL_PCH/URA_PCH to CELL_DCH of a UE using PTT services,
this counter is measured in the cell that the UE camps on based on the number of CELL UPDATE
CONFIRM messages indicating state transition from CELL_PCH/URA_PCH to CELL_DCH
sent from the RNC.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.21.8 Number of Successful PTT Paging Attempts After the RNC Sends the
PAGING TYPE 1 Message for Cell
Measurement Counters
ID Counter Description
Description
This counter provides the number of PAGING TYPE 1 messages sent by RNC before CELL
UPDATE messages received by RNC and containing the cause value of "paging response" in a
cell that are sent from the UE to the RNC due to PTT paging. This counter is measured on the
basis of the number of PAGING TYPE 1 messages sent by the RNC due to PTT services.
The counter is used to analyze the impact of paging on end-to-end delay of PTT services.
Measurement point
At point A shown in the following figure, when the RNC detects downlink data transmission of
PTT services, it sends a PAGING TYPE 1 message to the corresponding UE. When the RNC
receives a CELL UPDATE message containing a cause value of "paging response", this counter
is measured in the cell that the UE camps on based on the number of PAGING TYPE 1 messages
sent from the RNC.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.21.9 Number of PTT Call Initiation or Response Attempts of UEs Using the
PTT and Other Services in the CELL_FACH State for Cell
Measurement Counters
ID Counter Description
Description
This counter provides the number of PTT call initiation or response attempts of a UE in the
CELL_FACH state processing multiple services in the cell.
Measurement point
At point A shown in the following figure, the calling or called UE in the CELL_FACH state
performs a state transition triggered by an event 4a measurement report. Note that if a UE enabled
with E-PCH transits to CELL_FACH after sending an MEASUREMENT REPORT message
not carrying event 4a measurement, it is counted in the UE in the CELL_FACH state. The
measurement is incremented by one in the cell serving the UE each time the RNC receives an
event 4a measurement report from the UE processing PTT and other services.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the number of failed PTT call initiations or responses due to resource
congestion during a P2D procedure in a cell.This counter is used to analyze PTT service
establishment of UEs that send CELL UPDATE messages to initiate or respond to PTT calls.
Measurement point
A UE in the CELL_PCH or URA_PCH state can initiate or respond to a PTT call by sending a
CELL UPDATE message during a P2D procedure. The measurement is triggered at point A
shown in Figure 1 when the RNC determines that a UE fails to be admitted during a P2D
procedure for PTT calls. A UE sends a CELL UPDATE message to initiate a PTT call when all
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 this message are
uplink data transmission, Originating Conversational Call, and TRUE, respectively. This
message does not contain the IE CS Call Type. A UE sends a CELL UPDATE message to
respond to a PTT call when all the following conditions are met: The UE has set up a PTT service.
There is data to be transmitted for PTT services in the downlink. The value of the IE Cell update
cause contained in this message is paging response. This counter measures the number of failed
PTT call initiations or responses due to resource congestion during a P2D procedure in a cell.This
counter is used to analyze PTT service establishment of UEs that send CELL UPDATE messages
to initiate or respond to PTT calls.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of failed PTT call initiations or responses of a UE in the
CELL_FACH state processing only the PTT service caused by congestion in the cell. This
counter is used to analyze PTT service access of the UE in the CELL_FACH state.
Measurement point
The calling or called UE in the CELL_FACH state performs a state transition triggered by an
event 4a measurement report. Note that P2D state transition of a UE enabled with E-PCH is
counted in this state transition. During the state transition, the measurement is incremented by
one in the cell serving the UE each time the RNC makes a decision on a failed admission of the
UE processing only the PTT service based on event 4a measurement.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of failed PTT call initiations or responses of a UE in the
CELL_FACH state processing multiple PTT services caused by congestion in the cell.
Measurement point
The calling or called UE in the CELL_FACH state performs a state transition triggered by an
event 4a measurement report. Note that P2D state transition of a UE enabled with E-PCH is
counted in this state transition. During the state transition, the measurement is incremented by
one in the cell serving the UE each time the RNC makes a decision on a failed admission of the
UE processing PTT and other services based on event 4a measurement.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the number of push to talk (PTT) call initiation attempts or responses
during a CELL_PCH/URA_PCH-to-CELL_DCH (P2D) procedure in a cell. This counter is used
to analyze PTT service establishment of UEs that send CELL UPDATE messages to initiate or
respond to PTT calls.
Measurement point
A UE in the CELL_PCH or URA_PCH state can initiate or respond to a PTT call by sending a
CELL UPDATE message during a P2D procedure. The measurement is triggered at point A
shown in Figure 1 when the RNC receive a CELL UPDATE message from the UE that initiates
or responds to a PTT call during a P2D procedure. A UE sends a CELL UPDATE message to
initiate a PTT call when all the following conditions are met: The UE has set up a PTT service.
The values of the information elements (IEs) Cell update cause, Establishment cause, and Traffic
volume indicator contained in this message are uplink data transmission, Originating
Conversational Call, and TRUE, respectively. This message does not contain the IE CS Call
Type. A UE sends a CELL UPDATE message to respond to a PTT call when all the following
conditions are met: The UE has set up a PTT service. There is data to be transmitted for PTT
services in the downlink. The value of the IE Cell update cause contained in this message is
paging response.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the uplink traffic volume of the Push to Talk (PTT) service in cells in the
active set.
Measurement point
Uplink traffic volume of all PTT services in the RLC layer in cells in the active set under the
SRNC (not including the RLC header) .
Formula
None
Unit
bit
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the downlink traffic volume of the Push to Talk (PTT) service in cells in
the active set.
Measurement point
Downlink traffic volume of all PTT services in the RLC layer in cells in the active set under the
SRNC (not including the RLC header) .
Formula
None
Unit
bit
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the number of successful HSDPA or HSUPA serving cell changes
(regardless of whether the new serving cell is under the same RNC or under another RNC) for
PTT service in soft handover status in a cell. If a UE performs both HSDPA and HSUPA services,
this counter counts the serving cell change of the UE only once.
Measurement point
During an HSDPA or HSUPA serving cell change, the RNC may send any of the following
messages to a UE:
[1]PHYSICAL CHANNEL RECONFIGURATION,
[2]TRANSPORT CHANNEL RECONFIGURATION,
[3]RADIO BEARER RECONFIGURATION,
[4]ACTIVE SET UPDATE.
The UE may send one of the following messages to the RNC accordingly:
[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,
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the number of HSDPA or HSUPA serving cell change attempts
(regardless of whether the new serving cell is under the same RNC or under another RNC) for
PTT service in soft handover status in a cell. If a UE performs both HSDPA and HSUPA services,
this counter counts the serving cell change attempts of the UE only once.
Measurement point
During an HSDPA or HSUPA serving cell change, the RNC may send any of the following
messages to a UE:
[1]PHYSICAL CHANNEL RECONFIGURATION,
[2]TRANSPORT CHANNEL RECONFIGURATION,
[3]RADIO BEARER RECONFIGURATION,
[4]ACTIVE SET UPDATE.
The UE may send one of the following messages to the RNC accordingly:
[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,
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the number of successful hard handovers (including intra-frequency
handovers, inter-frequency handovers, and handovers under the same RNC or between RNCs)
for the PTT service in a cell.
Measurement point
During a hard handover, the RNC may send any of the following messages to a UE:
The UE may send one of the following messages to the RNC accordingly:
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter measures the number of hard handover attempts (including intra-frequency
handovers, inter-frequency handovers, and handovers under the same RNC or between RNCs)
for the PTT service in a cell.
Measurement point
During a hard handover, the RNC may send any of the following messages to a UE:
[1]PHYSICAL CHANNEL RECONFIGURATION,
[2]TRANSPORT CHANNEL RECONFIGURATION,
[3]RADIO BEARER RECONFIGURATION,
[4]RADIO BEARER SETUP,
[5]RADIO BEARER RELEASE.
The UE may send one of the following messages to the RNC accordingly:
[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.
Use the RADIO BEARER RECONFIGURATION message as an example. The measurement
is triggered at point A shown in the figure when the RNC sends a RADIO BEARER
RECONFIGURATION message to a UE during a hard handover. In this case, this counter is
increased by one in the best cell of this UE before the hard handover.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Overview
This measurement unit 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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
ID Counter Description
Description
The preceding measurement items provide the delay of establishing all types of services in the
best cell according to the CN domains.The delay covers the time starting from the RRC
CONNECTION REQUEST message to the First RAB ASSIGNMENT RESPONSE
message.For DC-HSUPA users, this counter is measured only in the cell configured with the
primary carrier.These counters VS.AMR.Estab.MeanTime,VS.AMR.Estab.MaxTime and
VS.AMR.Estab.MinTime include narrowband and wideband AMR services.
Measurement point
The measurement is triggered at point A in the Figure. When the RNC receives a RRC
CONNECTION REQUEST message, the RNC records the time T1. 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 records the time T2 at point B. Suppose deltaT=T2-
T1. Then, deltaT is the delay of this service establishment. The best cell where the UE is located
measures the items according to the CN domains and service types. Note: The delay of
establishing the first RAB is calculated.
Formula
None
Unit
ms
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
ID Counter Description
ID Counter Description
ID Counter Description
Description
These counters provide the number of times that the average throughput of the MAC-d flow of
BE services is in each range based on the level of the service in the HSDPA serving cell. The
average throughput is reported by the DSP every 20 seconds. For DC-HSDPA 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 the HSDPA serving cell, the DSP reports the average downlink throughput of each type of
BE services every 20 seconds. When the throughput is within a predefined range, the
corresponding counter is incremented by one. At the end of the measurement period, the value
of each counter is obtained
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
ID Counter Description
ID Counter Description
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
For the HSUPA cells in the active set, the DSP reports the average uplink throughput of each
type of BE services every 20 seconds. When the throughput is within a certain range, the
corresponding counter is incremented by one. At the end of the measurement period, the value
of each counter is obtained.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the duration from the RRC connection setup to the service setup on an
ERACH in the 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 sends the CN an RAB ASSIGNMENT
RESPONSE message at point B after receiving from the UE a RADIO BEARER SETUP
COMPLETE message, the time is recorded T2. The RNC uses delta T=T2-T1 as the service
setup duration on an ERACH if the service is set up on an ERACH. In this case, the corresponding
counter is measured in the best cell that the UE camps on according to the service mode and
type.
Formula
None
Unit
ms
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the duration from the RRC connection setup to the service setup on an
EFACH in the 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 sends the CN an RAB ASSIGNMENT
RESPONSE message at point B after receiving from the UE a RADIO BEARER SETUP
COMPLETE message, the time is recorded as T2. The RNC uses delta T=T2-T1 as the service
setup duration on an ERACH if the service is set up on an ERACH. In this case, the corresponding
counter is measured in the best cell that the UE camps on according to the service mode and
type.
Formula
None
Unit
ms
Related Features
Counter Feature ID Feature Name
A VS.RAB.AttEstabCS.Conv,
VS.RAB.AttEstabCS.Str
B VS.RAB.AttEstab.AMR,
VS.RAB.AttEstabCS.AMRWB,
VS.RAB.AttEstCS.Conv.64
C VS.HSPA.RAB.AttEstab.CS.Conv,
VS.RAB.AttEstabCS.VPLimit
H VS.RAB.SuccEstabCS.Conv,
VS.RAB.SuccEstabCS.Str
I VS.RAB.SuccEstabCS.AMR,
VS.RAB.SuccEstabCS.AMRWB,
VS.RAB.SuccEstCS.Conv.64
J VS.HSPA.RAB.SuccEstab.CS.Conv
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
VS.RAB.AttEstab.AMR 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
1.10.23.1 Counters Related to the Number of CS RAB Setup Requests for Different
Services
Measurement Counters
ID Counter Description
Description
The measurement items take statistics of the number of CS RABs establishment requests in the
best cell according to different services.
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 according to the type of the service to be set up in the best cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters provide the number of times that the CS RAB is set up successfully for different
services 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 after receiving a RADIO BEARER SETUP
COMPLETE message from the UE, it measures the corresponding counter according to the
service type of the RAB in the best cell where the UE camps on if the RAB is for the CS service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the RAB is set up successfully for CS narrowband
AMR services 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 narrowband AMR service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the RAB is set up successfully for CS wideband
AMR services 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 wideband AMR service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of RAB setup requests for CS 64 Kbit/s conversational services
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 CS 64 Kbit/s conversational service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the number of times that the RAB is set up successfully for CS
narrowband AMR services with different rates 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 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 if the RAB is for the CS narrowband AMR services.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
This counter provides the number of times that the RAB is set up successfully for CS wideband
AMR services 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 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 if the RAB is for the WB AMR service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the RAB is set up successfully for CS 64 Kbit/
s conversational services 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 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 if the RAB is for the VP service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of RAB setup attempts for CS HSPA voice 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.23.11 Number of RAB Setup Attempts for VP Services when VP Call Is Limited
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the average number of CS over HSPA users in the 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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-708 Queue procedure for admission failure during the RAB establishment
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the queuing duration for the queued cells.
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.
The counter is measured in the queued cells.
Formula
None
Unit
s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 B in Figure1. The counter is measured in the queued
cells.
Figure 1-709 Queue procedure for admission failure during the RAB establishment
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
A VS.RAB.AttEstabPS.Bkg,
VS.RAB.AttEstabPS.Conv,
VS.RAB.AttEstabPS.Int,
VS.RAB.AttEstabPS.Str
B VS.RAB.AttEstab.PSR99
H VS.RAB.SuccEstabPS.Bkg,
VS.RAB.SuccEstabPS.Conv,
VS.RAB.SuccEstabPS.Int,
VS.RAB.SuccEstabPS.Str
I VS.RAB.SuccEstab.PSR99
J VS.RAB.SuccEstabPS.0kbps
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
1.10.24.1 Counters Related to the Number of RAB Setup Requests for Different PS
Services
Measurement Counters
ID Counter Description
Description
These counters provide the number of RAB setup 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 in the PS domain, it measures the
corresponding counter in the best cell that the UE camps on based on the service type.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.24.2 Counters Related to the Number of Successful RAB Setups for Different
PS Services
Measurement Counters
ID Counter Description
Description
These counters provide the number of times that the RAB is set up successfully for different 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 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 in the best cell where the UE camps on if the RAB is for the PS service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Measurement point
As shown in point B in Figure 1, when the RNC sends a RAB ASSIGNMENT RESPONSE
message to the CN upon receipt of the RADIO BEARER SETUP COMPLETE message sent
from the UE, the measurement is triggered in the best cell if any of the following conditions is
met: 1.The UE has established a 0 kbit/s PS service. 2.The existing PS service rate is reconfigured
as 0 kbit/s because the UE establishes a CS service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the RAB is set up successfully for PS R99 services
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 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 if the RAB is for the PS R99 service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of RAB setup attempts for PS R99 services 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 PS domain, it assigns a channel
according to the network configuration. In this case, the RNC measures this counter in the best
cell where the UE camps on .
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-716 Queue procedure for admission failure during the RAB establishment
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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. The measurement is triggered when the service enters the queue.
The counter is measured in the queued cells.
Formula
None
Unit
s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 B in Figure1. The counter is measured in the queued
cells.
Figure 1-717 Queue procedure for admission failure during the RAB establishment
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the PTT service is set up successfully 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 after receiving from the UE a RADIO BEARER
SETUP COMPLETE message, it measures the counter in the best cell that the UE camps on if
the RAB is for the PTT service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of RAB setup requests for PTT services in the best cell.
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. In this case, the counter is measured in the
best cell that the UE camps on if the request is for the PTT service.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of PS free RAB setup attempts in the best cell. This counter
takes effect only when the "free HSDPA user feature" has been activated.
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 in the PS domain, it measures
this counter in the best cell if the RAB is for the PS free services.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the PS free RAB is set up successfully in the best
cell. This counter takes effect only when the "free HSDPA user feature" has been activated.
Measurement point
The measurement is triggered at point B as shown in the following figure. When the RNC sends
a RAB ASSIGNMENT RESPONSE message to the CN after receiving a RADIO BEARER
SETUP COMPLETE message from the UE, it measures this counter in the best cell on which
the UE camps if the RAB is for the PS free services.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
E VS.RAB.FailEstabCS.DLIUBBand.Cong,
VS.RAB.FailEstabCS.ULIUBBand.Cong,
VS.RAB.FailEstabCS.ULCE.Cong,
VS.RAB.FailEstabCS.DLCE.Cong,
VS.RAB.FailEstabCS.ULPower.Cong,
VS.RAB.FailEstabCS.DLPower.Cong,
VS.RAB.FailEstabCS.Code.Cong
N VS.RAB.FailEstabCS.TNL
F VS.RAB.FailEstabCS.IubFail,VS.RAB.Fail
EstabCS.ULCE.Cong,VS.RAB.FailEstabCS
.DLCE.Cong
G VS.RAB.FailEstabCS.UuFail,
VS.RAB.FailEstabCS.RBIncCfg,
VS.RAB.FailEstabCS.RBCfgUnsup,
VS.RAB.FailEstabCS.UuNoReply,
VS.RAB.FailEstabCS.PhyChFail
K VS.RAB.FailEstabCS.RNL
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
VS.RAB.FailEstabCS.Unsp VS.RAB.FailEstabCS.Cong
VS.RAB.FailEstabCS.Cong 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.RNL 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
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of CS RABs unsuccessfully established due to
congestion 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
cause is "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". In this case, the
RNC measures each item in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of CS RABs unsuccessfully established 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
unsuccessfully established, this counter is measured in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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, physical channel failure of UE, no reply of UE.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement items provide the number of failed CS RABs due to radio resource congestion
in the best cell.If congestion occurs on both the uplink and downlink, only the related downlink
counter is measured. For example, if a CS RAB connection setup fails due to the congestion on
both the uplink and downlink, only the counter VS.RAB.FailEstabCS.DLPower.Cong is
measured.
Measurement point
The measurement is triggered at point B as shown in the figure, If the RNC detects a request to
set up RABs in the RAB ASSIGNMENT REQUEST message from the CN, it requests related
radio resources. If the request for radio resources fails, the RNC regards the setup of RABs as
a failure and sends a RAB ASSIGNMENT RESPONSE message to the CN(With failure cause
of "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" or "Requested
Guaranteed Bit Rate for UL not Available"). In this case, the RNC measures each item in the
best cell according to different causes of radio resource congestion.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Figure 1-729 Failed RAB establishments due to radio link configuration failure
Figure 1-730 Failed RAB establishments due to radio link configuration failure
Figure 1-731 Timeout for a RADIO LINK RESTORE INDICATION message after receiving
a RADIO LINK FAIL INDICATION message
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
E 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
N VS.RAB.FailEstabPS.TNL
F VS.RAB.FailEstabPS.IubFail,VS.RAB.Fail
EstabPS.ULCE.Cong,VS.RAB.FailEstabPS.
DLCE.Cong
G VS.RAB.FailEstabPS.UuFail,
VS.RAB.FailEstabPS.UuNoReply,
VS.RAB.FailEstabPS.RBIncCfg,
VS.RAB.FailEstabPS.RBCfgUnsupp,
VS.RAB.FailEstabPS.PhyChFail
K VS.RAB.FailEstabPS.RNL
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
VS.RAB.FailEstabPS.Cong 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.HSUPAUser.Cong
VS.RAB.FailEstabPS.HSDPAUser.Cong
VS.RAB.FailEstabPS.RNL 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
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of PS RABs unsuccessfully established 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
unsuccessfully established, this counter is measured in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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, no reply of UE.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
Description
The measurement items provide the number of failed PS RABs in the best cell due to radio
resource congestion for different causes.If congestion occurs on both the uplink and downlink,
only the related downlink counter is measured. For example, if a PS RAB connection setup fails
due to the congestion on both the uplink and downlink, only the counter
VS.RAB.FailEstabPS.DLPower.Cong is measured.
Measurement point
The measurement is triggered at point B as shown in the figure. After the RNC receives a RAB
ASSIGNMENT REQUEST message from the CN, if the message contains a request to set up a
RAB, the RNC requests for the corresponding radio resources. If the requests fails, the RNC
considers the RAB setup as a failure and sends a RAB ASSIGNMENT RESPONSE message
to the SGSN(With failure cause of "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" or "Requested Guaranteed Bit Rate for UL not Available"). In this case, the
RNC measures the items in the best cell according to the failure causes.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Figure 1-740 Failed RAB establishments due to radio link configuration failure
Figure 1-741 Failed RAB establishments due to radio link configuration failure
Figure 1-742 Timeout for a RADIO LINK RESTORE INDICATION message after receiving
a RADIO LINK FAIL INDICATION message
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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","No Radio Resources Available in
Target cell" or "No Resource Available". In this case, the RNC measures each item in the best
cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of CS RABs unsuccessfully established due to
congestion 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
cause is "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". In this case, the
RNC measures each item in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of PS free RAB setup failures in the best cell due to DL power
resource congestion. This counter takes effect only when the "free HSDPA user feature" has
been activated.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
1.10.29.1 Mean Number of Single-RAB UEs Occupy the Codes with Different
Spreading Factors
Measurement Counters
ID Counter Description
Description
These counters provide the average number of single-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 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 UEs that use the SF of 4/8/16/32/64/128/256 in a cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.29.2 Mean Number of Multi-RAB UEs Occupy the Codes with Different
Spreading Factors
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the mean number of multi-RAB UEs that occupy the codes with the
spreading factor (SF) of 4/8/16/32/64/128/256 in a cell.
Measurement point
The RNC takes a sample from the number of multi-RAB UEs that occupy the codes with the SF
of 4/8/16/32/64/128/256 in a cell every five seconds. At the end of the measurement period, the
RNC divides the accumulated number of multi-RAB UEs by the number of samples to obtain
the mean number of multi-RAB UEs that occupy the codes with the SF of 4/8/16/32/64/128/256
in a cell.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 HS-
DSCH. 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. When the NodeB dynamic code switch is turned on, the RNC cannot count the extra SF
codes beyond the range of reserved codes that are used by the NodeB. Otherwise, the preceding
counters are not reported as expected.
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 Feature ID Feature Name
1.10.29.4 Mean Throughput of a Single HSDPA MAC-d Flow in the Case of Multi-
RAB Services for Cell
Measurement Counters
ID Counter Description
Description
This counter provides the mean throughput of a single HSDPA MAC-d flow in the case of Multi-
RAB 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
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
1.10.29.5 Mean Throughput of a Single HSUPA MAC-d Flow in the Case of Multi-
RAB Services for Cell
Measurement Counters
ID Counter Description
Description
This counter provides the mean throughput of a single HSUPA MAC-d flow in the case of Multi-
RAB 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
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the mean downlink throughput of a single PS R99 RB in the case of Multi-
RAB 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
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the mean uplink throughput of a single PS R99 RB in the case of Multi-
RAB 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
None
Unit
kbit/s
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of RAB setup requests for CS+PS 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. The service setup sequence is not considered.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful RAB setups for CS+PS 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. The service setup sequence is not
considered.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of RAB setup requests for PS+PS 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 PS+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. The service setup sequence is not considered.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful RAB setups for PS+PS 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 PS+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. The service setup sequence is not
considered.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a CS service in the CS+PS combined service is
released normally 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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a PS service in the PS+PS combined service is
released normally 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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a CS 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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a PS service in the PS+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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that a CS service is released abnormally during the
PS service 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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 (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 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.
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
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters measure the number of CS service setup attempts of UEs processing PS services
in the best cell.
Measurement point
The measurement is triggered at point A shown in the figure. This counter is incremented by
one in the best cell that a UE camps on according to different UE state when all the following
conditions are met: 1. The UE has one or multiple PS radio access bearers (RABs). 2. The RNC
receives from the CN CS domain a RAB ASSIGNMENT REQUEST message and sends the
UE an RB SETUP message.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These counters measure the number of successful CS service setups of UEs processing PS
services in the best cell.
Measurement point
The measurement is triggered at point B shown in the figure. This counter is incremented by
one in the best cell that a UE camps on according to different UE state when all the following
conditions are met: 1. The UE has one or multiple PS RABs. 2. The RNC receives from the CN
CS domain a RAB ASSIGNMENT REQUEST message and sends the CN a RAB
ASSIGNMENT RESPONSE message.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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).
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times a UE 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,
this counter is increased by one in the best cell where the UE camps before the inter-RAT
handover.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
A VS.RAB.NormRel.CS
B VS.RAB.NormRel.AMR,VS.RAB.NormRe
l.CS64,VS.RAB.NormRel.CS.Str
C VS.RAB.NormRel.CS.HSPA.Conv
D VS.RAB.AbnormRel.CS
E VS.RAB.AbnormRel.AMR,VS.Abnorm.Rel
.CS.Str
F VS.RAB.AbnormRel.CS.HSPA.Conv
G VS.RAB.NormRel.PS
H VS.RAB.NormRel.PS.Conv,
VS.RAB.NormRel.PS.Str
I VS.RAB.NormRel.PS.CCH
J VS.RAB.AbnormRel.PS
K VS.RAB.AbnormRel.PS.Conv,
VS.RAB.AbnormRel.PS.Str
L VS.RAB.AbnormRel.PS.CCH
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
VS.RAB.AbnormRel.CS.RF VS.RAB.AbnormRel.CS.RF.ULSync
VS.RAB.AbnormRel.CS.RF.UuNoReply
VS.RAB.AbnormRel.CS.RF.SRBReset
VS.RAB.AbnormRel.PS.RF 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.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.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
VS.RAB.AbnormRel.PSR99 VS.RAB.AbnormRel.PS.CCH
VS.RAB.NormRel.AMRWB 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
Measurement Counters
ID Counter Description
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" or "Network Optimization","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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 "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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of PS RABs abnormally released due to different
causes in the best cell.
Counter Description
Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement items provide the number of released PS BE RABs carried on HSPA triggered
by the RNC in the best cell due to cell congestion or preemption. For DC-HSUPA or 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 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.
The measurement is triggered at point A as shown in the figure, when the RNC sends a IU
RELEASE REQUEST message to the CN due to preemption after the RABs have been set up.
In this case, the RNC measures the items in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 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 there exsit released CS VP RAB Due to VP Forbiddance.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
These measurement items provide the number of CS or PS RABs released due to UE uplink
signaling connection release and the second RRC connection setup for a UE in the best cell.
Note: Second RRC Connection Request: The UE sends a second RRC CONNECTION
REQUEST message to the RNC before releasing the previously assigned RAB.
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 after RABs have
been set up. 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). After
receiving this message, the CN sends an IU RELEASE COMMAND message to the RNC. After
receiving this message, the RNC releases the corresponding RAB and sends an IU RELEASE
COMPLETE message to the CN. In this case, the items are measured based on the service type
in the best cell that the UE camps on.
The measurement is triggered at point A as shown in the figure, after receiving an RRC
CONNECTION REQUEST message from a UE, the RNC determines that the message is sent
by the same UE with RAB using a COMMAND ID message sent by the CN,and then 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). Upon reception of the IU
RELEASE REQUEST message, the CN sends an IU RELEASE COMMAND message to the
RNC. After receiving this message, the RNC releases the corresponding RAB and sends an IU
RELEASE COMPLETE message to the CN. In this case, the items are measured based on the
service type in the best cell that the UE camps on.
Figure 1-837 RAB release procedure caused by the second RRC connection setup request from
the same UE
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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 RF-
related 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).
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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).
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.30.28 Number of call drops During the F2P State Transition for Cell
Measurement Counters
ID Counter Description
Description
This counter provides the number of call drops during CELL_FACH to CELL_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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.30.30 Number of RABs Abnormally Released for PS Services during the State
Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell
Measurement Counters
ID Counter Description
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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Overview
If a CS 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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
These counters provide the number of RAB release requests for CS services in the best cell based
on the release cause.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
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 CS domain from the CN, if the RAB release
cause is not "Normal Release", "Successful Relocation","User Inactivity","Network
Optimization" or "UE Generated Signalling Connection Release", and the RNC had not sent any
RAB RELEASE REQUEST messages before, the RNC measures this item according to the
number of RAB released.
The measurement is triggered at point A as shown in the figure. When the RNC receives an IU
RELEASE COMMAND message about the CS domain from the CN, if the RAB release cause
is not "Normal Release", "Successful Relocation","User Inactivity","Network Optimization" or
"UE Generated Signalling Connection Release", and the RNC had not sent any IU RELEASE
REQUEST messages before, the RNC measures this item according to the number of RAB
released.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of CS RABs released in RAB assignment in the best cell.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the number of RAB release requests for PS services in the best cell
according to different release causes.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This measurement item provides the number of PS RAB releases triggered by the CN 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 about the PS domain from the CN, if the RAB release
cause is not "Normal Release", "Successful Relocation","User Inactivity","Network
Optimization" or "UE Generated Signalling Connection Release", 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","User Inactivity","Network Optimization" or
"UE Generated Signalling Connection Release", and the RNC had not send the IU RELEASE
REQUEST message before, the RNC measures this item according to the number of RAB
releases.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement item provides the number of PS RAB release attempts by RAB
ASSIGNMENT REQUEST message in the best cell.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.33.3 Counters Related to the Number of Failed RB Setups for Different Causes
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.33.7 Counters Related to the Number of AMR Users with Different UL and DL
Rates
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the number of AMR users with different UL and DL rates in the cells
in the active set.
Measurement point
The number of AMR users with each UL or DL rate is sampled every 30 seconds in the cells in
the active set. 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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
The measurement items provide the mean number of CS conversational service RBs at various
bit rates in a cell, that is, the mean number of uplink and downlink RBs obtained at the sampling
points in the cell in the measurement period, as listed below:
Measurement point
The RNC takes a sample every 5 seconds from the number of CS conversational service RBs at
different bit rates. At the end of the measurement period, the RNC divides the accumulated
number of conversational service RBs at each bit rate by the number of samples to obtain the
mean number of CS conversational service RBs. In this case, the RNC measures the item in each
cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.33.9 Number of RBs for PS R99 Background Services with various Uplink and
Downlink Rates for Cell
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
Description
These counters provide the average number of RBs for PS R99 Background services with
different UL and DL rates in the cells in the active set.
Measurement point
The RNC takes a sample every 5 seconds from the number of PS background service RBs at
different bit rates. At the end of the measurement period, the RNC divides the accumulated
number of background service RBs at each bit rate by the number of samples to obtain the mean
number of PS background service RBs. In this case, the RNC measures the item in each cell that
the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.33.10 Number of RBs for PS R99 Interactive Services with various Uplink and
Downlink Rates for Cell
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
Description
These counters provide the average number of RBs for PS R99 interactive services with different
UL and DL rates in the cells in the active set.
Measurement point
The RNC takes a sample every 5 seconds from the number of PS interactive service RBs at
different bit rates. At the end of the measurement period, the RNC divides the accumulated
number of interactive service RBs at each bit rate by the number of samples to obtain the mean
number of PS interactive service RBs. In this case, the RNC measures the item in each cell that
the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.33.11 Number of RBs for CS Streaming Services with Uplink and Downlink
Rate of 57.6 Kbit/s for Cell
Measurement Counters
ID Counter Description
Description
These counters provide the average number of RBs for CS streaming services with uplink and
downlink rate of 57.6 Kbit/s in the cells of the active set.
Measurement point
The RNC takes a sample every 5 seconds from the number of CS streaming service RBs at
different bit rates. At the end of the measurement period, the RNC divides the accumulated
number of streaming service RBs at each bit rate by the number of samples to obtain the mean
number of CS streaming service RBs. In this case, the RNC measures the item in each cell that
the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.33.12 Number of RBs for PS R99 Streaming Services with various Uplink and
Downlink Rates for Cell
Measurement Counters
ID Counter Description
ID Counter Description
Description
These counters provide the average number of RBs for PS R99 streaming services with different
UL and DL rates in the cells in the active set.
Measurement point
The RNC takes a sample every 5 seconds from the number of PS streaming service RBs at
different bit rates. At the end of the measurement period, the RNC divides the accumulated
number of streaming service RBs at each bit rate by the number of samples to obtain the mean
number of PS streaming service RBs. In this case, the RNC measures the item in each cell that
the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of RB reconfiguration 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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of RB reconfiguration 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 RECONFIGURATION message, this counter is measured in the target cell
if the message is for the inter-frequency directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of outgoing DCH-to-HSDPA directed retry attempts in the
best cell that the UE camps on.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 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 DCH-to-HSDPA directed retry.
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 DCH-to-HSDPA directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the outgoing DCH-to-HSDPA directed retry
succeeds in the best cell that the UE camps on.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 B as shown in the following 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 DCH-to-HSDPA directed
retry.
The measurement can be triggered at point B as shown in the following 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 DCH-to-
HSDPA directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of incoming DCH-to-HSDPA directed retry attempts in the
best cell that the UE camps on.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 following 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 DCH-to-HSDPA directed retry.
The measurement can also be triggered at point A as shown in the following 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 DCH-to-HSDPA directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the incoming DCH-to-HSDPA directed retry
succeeds in the best cell that the UE camps on.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 B as shown in the following 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 DCH-to-HSDPA directed retry.
The measurement can also be triggered at point B as shown in the following 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 DCH-to-HSDPA directed
retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of outgoing DCH-to-HSUPA directed retry attempts in the
best cell that the UE camps on.For DC-HSUPA 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 following 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 DCH-to-HSUPA directed retry.
The measurement be also be triggered at point A as shown in the following 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 DCH-to-HSUPA directed
retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the outgoing DCH-to-HSUPA directed retry
succeeds in the best cell that the UE camps on.For DC-HSUPA users, this counter is measured
only in the cell with the primary carrier.
Measurement point
The measurement can be triggered at point B as shown in the following 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 DCH-to-HSUPA directed
retry.
The measurement can also be triggered at point B as shown in the following 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 DCH-to-
HSUPA directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of incoming DCH-to-HSUPA directed retry attempts in the
best cell that the UE camps on.For DC-HSUPA 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 following 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 DCH-to-HSUPA directed retry.
The measurement can also be triggered at point A as shown in the following 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 DCH-to-HSUPA directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the incoming DCH-to-HSUPA directed retry
succeeds in the best cell that the UE camps on.For DC-HSUPA users, this counter is measured
only in the cell with the primary carrier.
Measurement point
The measurement can be triggered at point B as shown in the following 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 DCH-to-HSUPA directed retry.
The measurement can also be triggered at point B as shown in the following 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 DCH-to-HSUPA directed
retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
Description
These counters provide the number of AMR WB users with different UL and DL rates in the
cells in the active set.
Measurement point
The number of AMR WB users with each UL or DL rate is sampled every 30 seconds in the
cells in the active set. 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 Feature ID Feature Name
1.10.33.30 Number of RBs for PS R99 Conversational Services with Various Uplink
and Downlink Rates for Cell
Measurement Counters
ID Counter Description
ID Counter Description
Description
The measurement items provide the mean number of PS conversational service R99 RBs at
various bit rates, that is, the mean number of R99 RBs obtained at the sampling points in the
cell of the active set in the measurement period, as listed in Table.
Measurement point
The RNC takes a sample every 5 seconds from the number of PS conversational service RBs at
different bit rates. At the end of the measurement period, the RNC divides the accumulated
number of conversational service RBs at each bit rate by the number of samples to obtain the
mean number of PS conversational service RBs. In this case, the RNC measures the item in each
cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful directed retry of CS voice services based on the
inter-frequency measurement in the best 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 cell
that the UE camps on if the message is for the CS directed retry based on inter-frequency
measurement.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of directed retry attempts of CS voice services based on the
inter-frequency measurement in the best 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 cell that the UE camps on
if the message is for the CS directed retry based on inter-frequency measurement.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of directed retry attempts of PS R99 services based on inter-
frequency measurement in the best 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 cell that the UE camps on
if the message is for the PS R99 directed retry based on inter-frequency measurement.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the directed retry of PS R99 services based on
inter-frequency measurement succeeds in the best 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 that the UE camps on if the message is for the PS R99 directed retry based on the inter-
frequency measurement.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of directed retry attempts of HSDPA PS services based on
inter-frequency measurement in the HSDPA serving 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 HSDPA serving cell that
the UE camps on if the message is for the HSDPA PS directed retry based on inter-frequency
measurement.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the directed retry of HSDPA PS services based
on inter-frequency measurement succeeds in the HSDPA serving 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
HSDPA serving cell that the UE camps on if the message is for the HSDPA PS directed retry
based on inter-frequency measurement.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the average number of PS Conversation UEs on HS-DSCH in the 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 PS Conversation
UEs numbers carried on HS-DSCH. 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 PS Conversation UEs carried on the HS-DSCH in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the average number of PS Conversation UEs on EDCH in the cell.
Measurement point
The system takes samples of PS Conversation UEs numbers carried on EDCH every 5 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 PS Conversation UEs carried on the
EDCH in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency directed retry, this counter is measured in the best cell that the UE camps on before
directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 inter-
frequency directed retry, this counter is measured in the target cell of the directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of outgoing FACH-to-HSDPA directed retry attempts in the
cell that the UE camps on.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. When the RNC sends
the UE a RADIO BEARER SETUP message, this counter is measured in the cell that the UE
camps on if the message is for the FACH-to-HSDPA directed retry.
The measurement is also triggered at point A as shown in the following figure. When the RNC
sends the UE a RADIO BEARER RECONFIGURATION message, this counter is measured in
the cell that the UE camps on if the message is for the FACH-to-HSDPA directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful outgoing FACH-to-HSDPA directed retries in
the originating 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 B as shown in the following figure. When the RNC
receives from the UE a RADIO BEARER SETUP COMPLETE message, this counter is
measured in the cell that the UE camps on if the message is for the FACH-to-HSDPA directed
retry.
The measurement is also triggered at point B as shown in the following figure. When the RNC
receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message, this
counter is measured in the cell that the UE camps on if the message is for the FACH-to-HSDPA
directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of outgoing FACH-to-HSUPA directed retry attempts in the
originating cell that the UE camps on.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 following figure. When the RNC sends
the UE a RADIO BEARER SETUP message, this counter is measured in the cell that the UE
camps on if the message is for the FACH-to-HSUPA directed retry.
The measurement is also triggered at point A as shown in the following figure. When the RNC
sends the UE a RADIO BEARER RECONFIGURATION message, this counter is measured in
the cell that the UE camps on if the message is for the FACH-to-HSUPA directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful outgoing FACH-to-HSUPA directed retries in
the originating 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 following figure. When the RNC
receives from the UE a RADIO BEARER SETUP COMPLETE message, this counter is
measured in the cell that the UE camps on if the message is for the FACH-to-HSUPA directed
retry.
The measurement is also triggered at point B as shown in the following figure. When the RNC
receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message, this
counter is measured in the cell that the UE camps on if the message is for the FACH-to-HSUPA
directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of incoming FACH-to-HSDPA directed retry attempts in the
target 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. When the RNC sends
the UE a RADIO BEARER SETUP message, this counter is measured in the target cell if the
message is for the FACH-to-HSDPA directed retry.
The measurement is also triggered at point A as shown in the following figure. When the RNC
sends the UE a RADIO BEARER RECONFIGURATION message, this counter is measured in
the target cell if the message is for the FACH-to-HSDPA directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful incoming FACH-to-HSDPA directed retries in
the target 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 B as shown in the following 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 FACH-to-HSDPA directed retry.
The measurement is also triggered at point B as shown in the following 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 FACH-to-HSDPA directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of incoming FACH-to-HSUPA directed retry attempts in the
target 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 following figure. When the RNC sends
the UE a RADIO BEARER SETUP message, this counter is measured in the target cell if the
message is for the FACH-to-HSUPA directed retry.
The measurement is also triggered at point A as shown in the following figure. When the RNC
sends the UE a RADIO BEARER RECONFIGURATION message, this counter is measured in
the target cell if the message is for the FACH-to-HSUPA directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the number of successful incoming FACH-to-HSUPA directed retries in
the target 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 following 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 FACH-to-HSUPA directed retry.
The measurement is also triggered at point B as shown in the following 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 FACH-to-HSUPA directed retry.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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-930 cd
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the CS and PS services in the CS+PS combined
service are abnormally released at the same time 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.
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.34.2 Number of RABs Released with the Cause of Network Optimization for
Cell
Measurement Counters
ID Counter Description
Description
These measurement items provide the number of RABs released with the cause of Network
Optimization in the best cell according to different domains.
VS.Reserve.Counter8: provides the number of CS RABs released with the cause of Network
Optimization.
VS.Reserve.Counter9: provides the number of PS RABs released with the cause of Network
Optimization.
Measurement point
The measurement is triggered at point A as shown in the following figure. The RNC sends to
the CN a RAB RELEASE REQUEST message. If the RNC receives a RAB ASSIGNMENT
REQUEST message(with release cause of "Network Optimization"), the items are measured
according to the domain types in the best cell that the UE camps on.
The measurement is triggered at point A as shown in the following figure. The RNC sends to
the CN a RAB RELEASE REQUEST message. If the RNC receives a IU RELEASE
COMMAND message(with release cause of "Network Optimization"), the items are measured
according to the domain types in the best cell that the UE camps on.
The measurement is triggered at point A as shown in the following figure. The RNC sends to
the CN a IU RELEASE REQUEST message. If the RNC receives a IU RELEASE COMMAND
message(with release cause of "Network Optimization"), the items are measured according to
the domain types in the best cell that the UE camps on.
The measurement is triggered at point A as shown in the following 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 that the cause value is "Network Optimization", the items are measured according to
the domain types in the best cell that the UE camps on.
The measurement is triggered at point B as shown in the following 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 that the cause value is "Network
Optimization", the items are measured according to the domain types in the best cell that the UE
camps on.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
VS.Reserve.Counter10
Measurement point
None
Formula
None
Unit
None
Related Features
None
Measurement Counters
ID Counter Description
Description
These measurement items provides the number of times that CS or PS Service Releases Caused
by the second RRC Connection Request from the same UE for Cell.
VS.Reserve.Counter1: provides the number of times that CS Service Releases Caused by the
second RRC Connection Request from the same UE for Cell.
VS.Reserve.Counter2: provides the number of times that PS Service Releases Caused by the
second RRC Connection Request from the same UE for Cell.
VS.Reserve.Counter3: provides the number of times that PS Service Releases Caused by the
second RRC Connection Request from the same UE in a Cell when PS services are carried over
common channels.
Note: Second RRC Connection Request: The UE sends a second RRC CONNECTION
REQUEST message to the RNC before releasing the previously assigned RAB.
Measurement point
As shown in point A of the figure, after receiving an RRC CONNECTION REQUEST message
from a UE, the RNC determines that the message is sent by the same UE with RAB using a
COMMAND ID message sent by the CN, and then the RNC sends an IU RELEASE REQUEST
message with the cause value of "UE Generated Signaling Connection Release". Upon reception
of the IU RELEASE REQUEST message, the CN sends an IU RELEASE COMMAND message
to the RNC. After receiving this message, the RNC releases the corresponding RAB and sends
an IU RELEASE COMPLETE message to the CN. In this case, the value of counter
VS.Reserve.Counter1 or VS.Reserve.Counter2 is measured based on the service type in the best
cell that the UE camps on. When UE's channel transition (including D2P,D2F) succeeds, or UE
is in the CELL_FACH state, CELL_PCH state, the value of counter VS.Reserve.Counter3 is
measured in the best cell that the UE camps on.
Figure 1-940 RAB release procedure caused by the second RRC connection setup request from
the same UE
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.34.5 This counter provides the number of times that the CS and PS services in
the CS+PS combined service are normally released at the same time in the best cell.
Measurement Counters
ID Counter Description
Description
This counter provides the number of times that the CS and PS services in the CS+PS combined
service are normally released at the same time 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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the sum of sampled values of the downlink BE service throughputs for
all DCH PS UEs within a best cell, in the unit of kbit/s.
Measurement point
The RNC periodically samples the downlink throughputs for BE services for all DCH PS UEs
within the sampling period of 500 ms. In the statistical period, the sum of sampled values of the
downlink BE service throughputs for all DCH PS UEs in a best cell is obtained by accumulating
the throughputs whose sampled values are not 0. RLC header data and retransmission data are
excluded during calculation of the sampled downlink throughput values. When some UEs initiate
multiple BE services, the RNC uses only one RAB for each UE to measure this counter.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the total number of times for sampling the BE service throughputs for all
DCH PS UEs in a best cell.
Measurement point
The RNC periodically samples the number of times sampled values of the downlink BE service
throughputs for all DCH PS UEs are not 0. At the end of the measurement period, the system
obtains the total number of times sampled values of the downlink BE service throughputs for
all DCH PS UEs in a best cell are not 0 by accumulating the sample times.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
Description
This counter provides the Erlang of CS services according to the call duration in the best cell.
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. When the RAB is released ,the counter is measured in the best cell that
the UE camps on.
Formula
None
Unit
Erl
Related Features
Counter Feature ID Feature Name
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.
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description
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 Feature ID Feature Name
Measurement Counters
ID Counter Description Original Release
Counter Relationship
None
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
1.10.36.3 Number of RRC Connection Releases due to Cell Update Failure in the
Case of RL Failure
Measurement Counters
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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.
Note: This counter is not used in this version but will be reused in the R15 version.
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.
Formula
None
Unit
None
Related Features
None
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.
A RRC.AttConnEstab.OrgConvCall
B VS.RRC.AttConnEstab.CellDCH,
VS.RRC.AttConnEstab.CellFACH
D VS.RRC.Estab.DRDOut.Att,
VS.RRC.Estab.DRDIn
I VS.RRC.SetupConnEstab
J RRC.SuccConnEstab.sum
Measurement Counters
ID Counter Description Original Release
Counter Relationship
Counter Sub Counter
VS.RRC.AttConnEstab.Sum 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
RRC.SuccConnEstab.sum 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
Measurement Counters
ID Counter Description
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.
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
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=T2-
T1, delta T is the duration of the RRC connection setup.
Formula
None
Unit
ms
Related Features
Counter Feature ID Feature Name
1.10.37.5 Counters Related to the Number of RRC Connection Requests for Various
Reasons
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
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.
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 redirection. 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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name
Measurement Counters
ID Counter Description
ID Counter Description
ID Counter Description
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.
Formula
None
Unit
None
Related Features
Counter Feature ID Feature Name