BSC6900 UMTS V900R015C00SPC529 Performance Counter Reference

BSC6900 UMTS
V900R015C00
Performance Counter Reference
Issue 06
Date 2014-01-20
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 06 (2014-01-20) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
BSC6900 UMTS
Performance Counter Reference About This Document
About This Document
Purpose
This document describes all the performance counters related to the BSC6900.
Product Version
The following table lists the product versions related to this document.
Product Name Product Version
BSC6900 V900R015C00
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.
Issue 06 (2014-01-20) Huawei Proprietary and Confidential ii

BSC6900 UMTS
Figure 1 Document structure
Table 1 explains the terms shown in Figure 1.
Table 1 Terms
Term Explanation
Classification of object type On the top level, object types are classified
into three categories: Radio Network Related
Measurement, Transport Network Related
Measurement, Hardware Platform Related
Measurement.
Object type Object types are located at the second level of

the document structure.
One object type contains one or more
function subsets.
Function Subset Function Subsets are located at the third level

of the document structure.
One function subset contains one or more
counters but belongs to only one object type.
Counter Counters are located at the fourth level of the

document structure.
Counters are the basic elements of
performance measurement. One counter can
belong to only one function subset.
Counter Item Description

Table 2 lists the description of each counter item.
Table 2 Description of each counter item
Item Description
Obj Overvi Definition and function of a object type.

ect ew
typ
e
Issue 06 (2014-01-20) Huawei Proprietary and Confidential iii

BSC6900 UMTS
Item Description
Functio Function subsets contained in a object type.

n
SubSet
s
Fun Functio Name of the function set.

ctio nSet One function set contains one or more function subsets.
n Name
Set
Fun Overvi Definition of a function subset and the flowchart for measuring related
ctio ew counters.
n
Sub Counte Counters contained in a function subset.
set rs
Counte A table that lists parent counters and their child counters in a table. Note that
r the child counters listed in the table cover only typical scenarios. That is,
Relatio some scenarios are not covered by any counter. Therefore, the value of a
nship 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.
Co Counte A string of digits that uniquely Related intermediate counters are

unt r ID identifies a counter. described in Counter ID, Counter
er Name and Counter Description.
Counte Name of a counter. It is composed of
Intermediate counter is invisible on
r Name a string of uppercase letters,
the M2000 GUI. Invisible counters
lowercase letters, and dots.
are internal sampling points used for
Counte A phrase that provides a simple calculating the visible counters
r description about a counter. inside the M2000.
Descri
ption
Descri Detailed description about a counter.

ption
Measur Condition for triggering counter measurement.

ement
Point
Formul Relationship among counters.

a
Unit Unit of a counter.
Related Features related to a counter. The "-" in Related Features stands for not
Feature involved, such as intermediate counters.
s
Issue 06 (2014-01-20) Huawei Proprietary and Confidential iv

BSC6900 UMTS
Performance Counter Reference Contents
Contents
About This Document.....................................................................................................................ii

1 UMTS Radio Network Related Measurement.........................................................................1
1.1 Measurement of CNOPERATOR Performance(CNOPERATOR)................................................................................2
1.1.1 Measurement of active algorithm per PLMN(ALGO.PLMN.RNC)...........................................................................2
1.1.1.1 Number of TRBs of HSDPA Service on Which Packet Inspection (PI) Takes Effect for RNC..............................3
1.1.2 Measurement of RAB assignment setup per PLMN(RAB.Estab.PLMN.RNC).........................................................4
1.1.2.1 Number of RABs Requested to Establish for each Operator...................................................................................5
1.1.2.2 Number of Successfully Established RABs for each Operator................................................................................7
1.1.3 Measurement of RAB assignment release per PLMN(RAB.Rel.PLMN.RNC)..........................................................9
1.1.3.1 Number of Abnormally Released RABs for each Operator...................................................................................10
1.1.3.2 Number of Normally Released RABs for each Operator.......................................................................................14
1.1.4 Traffic Measurement of CN Operator per RNC(TRAFF.LOAD.PLMN.RNC).......................................................17
1.1.4.1 Equivalent Erlang of CS Domain of RNC for each Operator................................................................................19
1.1.4.2 Maximum Equivalent Erlang of CS Domain of RNC for each Operator...............................................................20
1.1.4.3 Uplink Traffic of R99 PS Domain of RNC for each Operator...............................................................................21
1.1.4.4 Maximum Uplink Traffic of R99 PS Domain of RNC for each Operator.............................................................22
1.1.4.5 Downlink Traffic of R99 PS Domain of RNC for each Operator..........................................................................23
1.1.4.6 Maximum Downlink Traffic of R99 PS Domain of RNC for each Operator........................................................24
1.1.4.7 Downlink Traffic of HSDPA PS Domain of RNC for each Operator....................................................................25
1.1.4.8 Maximum Downlink Traffic of HSDPA PS Domain of RNC for each Operator..................................................26
1.1.4.9 Uplink Traffic of HSUPA PS Domain of RNC for each Operator........................................................................27
1.1.4.10 Maximum Uplink Traffic of HSUPA PS Domain of RNC for each Operator.....................................................28
1.1.4.11 Downlink Traffic of MBMS or IMB PS Domain of RNC for each Operator......................................................29
1.1.4.12 Maximum Downlink Traffic of MBMS or IMB PS Domain of RNC for each Operator....................................30
1.1.4.13 Equivalent Erlang of CS Domain AMR Service of RNC for each Operator.......................................................31
1.1.4.14 Equivalent Erlang of CS Domain CS 64kbit/s Conversational Service of RNC for each Operator....................32
1.1.4.15 The Number of Cell_DCH UEs in PS Domain in RNC.......................................................................................33
1.1.4.16 Maximum Total Throughout of UL and DL PS Services per Operator for RNC................................................34
1.1.4.17 Average Total Throughput of UL and DL PS Services per Operator for RNC...................................................35
1.1.4.18 The Number of Cell_FACH UEs in PS Domain in RNC.....................................................................................36
1.2 Measurement of CPUS Performance(CPUS)...............................................................................................................37
1.2.1 Measurement related to CPUS(CPUS)......................................................................................................................37
Issue 06 (2014-01-20) Huawei Proprietary and Confidential v

BSC6900 UMTS
1.2.1.1 Measurement of CS-Domain Equivalent Erlang of Each Subsystem in the RNC.................................................46

1.2.1.2 Number of RRC Connection Requests in the CPUS subsystem............................................................................47
1.2.1.3 Number of Successful RRC Connection Setups in the CPUS subsystem..............................................................48
1.2.1.4 Number of CS RAB Requests in the CPUS subsystem..........................................................................................50
1.2.1.5 Number of CS RABs successfully established in the CPUS subsystem................................................................52
1.2.1.6 Number of RABs Abnormally Released in the CPUS subsystem..........................................................................54
1.2.1.7 Number of RABs Normally Released in the CPUS subsystem..............................................................................57
1.2.1.8 Number of CBS Requests Discarded Due to Flow Control for CPUS Subsystem................................................61
1.2.1.9 Duration of CBS Flow Control for CPUS Subsystem............................................................................................61
1.2.1.10 Number of Paging Messages Discarded Due to Flow Control for CPUS Subsystem..........................................62
1.2.1.11 Duration of Paging Message Flow Control for CPUS Subsystem.......................................................................63
1.2.1.12 Number of Cell Update Requests Discarded Due to Flow Control for CPUS Subsystem...................................64
1.2.1.13 Duration of Cell Update Flow Control for CPUS Subsystem..............................................................................64
1.2.1.14 Number of Discarded RRC Connection Requests Due to Various Flow Control Functions...............................65
1.2.1.15 Number of Various Priority RRC Requests Discarded Due to Flow Control for CPUS Subsystem...................67
1.2.1.16 Duration of Rejection of Various Priority RRC Requests Due to Flow Control for CPUS Subsystem..............68
1.2.1.17 Number of Various Priority CELL_UPDATE Messages Discarded Because CPU Usage Exceeds the Threshold
in a CPUS...........................................................................................................................................................................69
1.2.1.18 Number of Various Priority CELL_UPDATE Messages Discarded Due to Queue-based Shaping in a CPUS
............................................................................................................................................................................................71
1.2.1.19 Number of Discarded Event 4A Measurement Reports on PS BE Traffic in the CELL_DCH State..................73
1.2.1.20 Number of Discarded UL Event 4A Measurement Reports on Throughput for UEs in the CELL_DCH State
............................................................................................................................................................................................74
1.2.1.21 Number of Discarded Event 4A Measurement Reports on PS BE Traffic in the CELL_FACH State................76
1.2.1.22 Number of FlowControl RRC Connection Requests Due to FlowControl for CPUS Subsystem.......................77
1.2.1.23 Number of FlowControl RT RRC Connection Requests Due to FlowControl for CPUS Subsystem.................79
1.2.1.24 Number of RRC CONNECTION REQUESTS for CS Services in a CPUS Subsystem Under Flow Control
Triggered by Interface-Board CPU Overload.....................................................................................................................80
1.2.1.25 Number of RRC CONNECTION REQUESTS in a CPUS Subsystem Under Flow Control Triggered by Interface-
Board CPU Overload..........................................................................................................................................................81
1.2.1.26 Number of Discarded Iur-Interface Uplink Signalling Messages in a CPUS Subsystem Under Flow Control
Triggered by CPU Overload...............................................................................................................................................82
1.2.1.27 Number of Discarded Iur-Interface Downlink Signalling Messages in a CPUS Subsystem Under Flow Control
Triggered by CPU Overload...............................................................................................................................................83
1.3 Measurement of GTPU Performance(GTPU)..............................................................................................................84
1.3.1 Measurement related to GTPU(GTPU).....................................................................................................................85
1.3.1.1 Number of UL Packets Sent by GTP-U.................................................................................................................87
1.3.1.2 Number of DL Packets Received by GTP-U..........................................................................................................88
1.3.1.3 Number of UL Bytes Sent by GTP-U....................................................................................................................89
1.3.1.4 Number of DL Bytes Received by GTP-U.............................................................................................................90
1.3.1.5 Counters Related to the Number of Service PDUs Sent by GTP-U.......................................................................90
1.3.1.6 Counters Related to the Number of Service PDUs Received by GTP-U...............................................................91
1.3.1.7 Number of MBMS or IMB Service Bytes Received by GTP-U............................................................................92
Issue 06 (2014-01-20) Huawei Proprietary and Confidential vi

BSC6900 UMTS
1.3.1.8 Number of Echo Response Packets Sent by the GTP-U........................................................................................93

1.3.1.9 Number of Echo Response Packets Received by the GTP-U.................................................................................94
1.3.1.10 Number of Echo Request Packets Sent by the GTP-U.........................................................................................95
1.3.1.11 Number of Echo Request Packets Received by the GTP-U.................................................................................95
1.3.1.12 Number of Error Indication Packets Sent by the GTP-U.....................................................................................96
1.3.1.13 Number of Error Indication Packets Received by the GTP-U.............................................................................97
1.4 Measurement of IU Interface Performance(IU)...........................................................................................................97
1.4.1 Measurement related to CS Iu interface signalling(CS.SIG.IU)...............................................................................98
1.4.1.1 Number of RESET Messages Initiated by RNC to CS Domain...........................................................................102
1.4.1.2 Number of RESET Messages Received by RNC from CS Domain....................................................................103
1.4.1.3 Number of INITIAL UE MESSAGE Messages from RNC to CS Domain.........................................................105
1.4.1.4 Number of IU RELEASE REQUEST Messages from RNC to CS Domain........................................................106
1.4.1.5 Number of IU RELEASE COMMAND Messages from CS Domain to RNC....................................................107
1.4.1.6 Number of ERROR INDICATION Messages from RNC to CS Domain...........................................................109
1.4.1.7 Number of ERROR INDICATION Messages from CS Domain to RNC...........................................................111
1.4.1.8 Number of IU RELEASE REQUEST Messages from RNC to CS Domain for Different Causes......................112
1.4.1.9 Number of IU RELEASE COMMAND Messages from CS Domain to RNC for Different Causes...................115
1.4.1.10 Load Balancing of the MSC Pool on the CS Domain........................................................................................118
1.4.1.11 Number of Discarded Initial UE messages Under Iu Signaling Flow Control (CS Domain)............................120
1.4.1.12 Number of Paging Messages Received by RNC from CN in CS Domain.........................................................121
1.4.1.13 Number of RAN INFORMATION REQUEST Messages Received by RNC from CN...................................123
1.4.1.14 Number of RAN INFORMATION Messages Sent by RNC to CN...................................................................124
1.4.2 Measurement related to CS traffic(CS.TRF.IU)......................................................................................................125
1.4.2.1 Number of DL Bytes of CS Conversational Service on Iu Interface...................................................................126
1.4.2.2 Number of DL Bytes of CS Streaming Service on Iu Interface...........................................................................126
1.4.2.3 Number of UL Bytes of CS Conversational Service on Iu Interface...................................................................127
1.4.2.4 Number of UL Bytes of CS Streaming Service on Iu Interface...........................................................................128
1.4.3 Measurement related to Iu interface(MBMS)(MBMS.IU)......................................................................................129
1.4.3.1 Total Number of MBMS or IMB Service............................................................................................................130
1.4.3.2 Number of Successful MBMS or IMB Service....................................................................................................131
1.4.3.3 Number of MBMS or IMB Service Setup Failures on the Iu Interface Due to Different Causes........................133
1.4.4 Measurement related to Iu interface(MOCN)(MOCN.IU)......................................................................................135
1.4.4.1 Number of Redirect for Different Causes.............................................................................................................136
1.4.5 Measurement related to NAS signaling(NAS.IU)...................................................................................................138
1.4.5.1 Number of Messages Forwarded by the RNC to the CN.....................................................................................140
1.4.5.2 Number of Messages Forwarded by the RNC from the CN.................................................................................142
1.4.5.3 Number of Authentication Requests Received by the RNC from the CN...........................................................144
1.4.5.4 Number of Authentication Responses Forwarded by the RNC to the CN...........................................................145
1.4.5.5 Number of SECURITY MODE COMMAND Messages Received by the RNC from the CN...........................147
1.4.5.6 Number of SECURITY MODE COMPLETE Messages Forwarded by the RNC to the CN..............................148
1.4.6 Measurement related to PS Iu interface signalling(PS.SIG.IU)..............................................................................150
Issue 06 (2014-01-20) Huawei Proprietary and Confidential vii

BSC6900 UMTS
1.4.6.1 Number of RESET Messages Initiated by RNC to PS Domain...........................................................................154

1.4.6.2 Number of RESET Messages Received by RNC from PS Domain.....................................................................156
1.4.6.3 Number of INITIAL UE MESSAGE Messages from RNC to PS Domain.........................................................157
1.4.6.4 Number of IU RELEASE REQUEST Messages from RNC to PS Domain........................................................159
1.4.6.5 Number of IU RELEASE COMMAND Messages from PS Domain to RNC.....................................................160
1.4.6.6 Number of ERROR INDICATION Messages from RNC to PS Domain............................................................162
1.4.6.7 Number of ERROR INDICATION Messages from PS Domain to RNC............................................................164
1.4.6.8 Number of IU RELEASE REQUEST Messages from RNC to PS Domain for Different Causes......................165
1.4.6.9 Number of IU RELEASE COMMAND Messages from PS Domain to RNC for Different Causes...................168
1.4.6.10 Load Balancing of the MSC Pool on the PS Domain.........................................................................................171
1.4.6.11 Number of Discarded Initial UE messages Under Iu Signaling Flow Control (PS Domain).............................173
1.4.6.12 Number of Paging Messages Received by RNC from CN in PS Domain.........................................................174
1.4.6.13 Number of RIM Requests from the eNodeB to the RNC (System Information)...............................................176
1.4.6.14 Number of RIM Response Messages from the RNC to the eNodeB (System Information)..............................177
1.4.6.15 Number of RIM Update Messages from the RNC to the eNodeB (System Information)..................................179
1.4.6.16 Number of RIM acknowledgement messages from the eNodeB to the RNC (System Information).................181
1.4.6.17 Number of RIM Requests from the eNodeB to the RNC (Load Information)...................................................182
1.4.6.18 Number of RIM Response Messages from the RNC to the eNodeB (Load Information).................................184
1.4.6.19 Number of RIM Update Messages from the RNC to the eNodeB (Load Information).....................................186
1.4.6.20 Number of RIM Acknowledgement Messages from the eNodeB to the RNC (Load Information)...................188
1.4.7 Measurement related to PS traffic(PS.TRF.IU).......................................................................................................189
1.4.7.1 Number of UL Bytes of PS Conversational Service on Iu Interface....................................................................191
1.4.7.2 Number of UL Bytes of PS Streaming Service on Iu Interface............................................................................192
1.4.7.3 Number of UL Bytes of PS Interactive Service on Iu Interface...........................................................................193
1.4.7.4 Number of UL Bytes of PS Background Service on Iu Interface.........................................................................194
1.4.7.5 Number of DL Bytes of PS Conversational Service on Iu Interface....................................................................195
1.4.7.6 Number of DL Bytes of PS Streaming Service on Iu Interface............................................................................195
1.4.7.7 Number of DL Bytes of PS Interactive Service on Iu Interface...........................................................................196
1.4.7.8 Number of DL Bytes of PS Background Service on Iu Interface.........................................................................197
1.4.7.9 Number of UL Bytes of PS BE Service for Golden Subscriber on Iu Interface..................................................198
1.4.7.10 Number of UL Bytes of PS BE Service for Silver Subscriber on Iu Interface...................................................199
1.4.7.11 Number of UL Bytes of PS BE Service for Copper Subscriber on Iu Interface................................................199
1.4.7.12 Number of DL Bytes of PS BE Service for Golden Subscriber on Iu Interface................................................200
1.4.7.13 Number of DL Bytes of PS BE Service for Silver Subscriber on Iu Interface...................................................201
1.4.7.14 Number of DL Bytes of PS BE Service for Copper Subscriber on Iu Interface................................................202
1.4.7.15 Total HTTP Traffic Volume on the RNC...........................................................................................................203
1.4.7.16 Total P2P Traffic Volume on the RNC..............................................................................................................203
1.4.7.17 Total Traffic Volume of all Subscribed Services on the RNC...........................................................................204
1.4.7.18 Total Traffic Volume of Undefined Services on the RNC.................................................................................205
1.4.7.19 Traffic Volume of Services Cannot Be Identified by the RNC on Downlink....................................................206
1.4.8 Measurement Related to SCCP for Iu Interface(SIG.SCCP.IU).............................................................................207
Issue 06 (2014-01-20) Huawei Proprietary and Confidential viii

BSC6900 UMTS
1.4.8.1 Number of SCCP Connection Requests Sent by the RNC to the CN Through the Iu Interface..........................208
1.4.8.2 Number of Successful SCCP Connection Requests Sent by the RNC to the CN Through the Iu Interface........209
1.4.8.3 Number of SCCP Connection Requests Received by the RNC from the CN Through the Iu Interface..............210
1.4.8.4 Number of Successful SCCP Connection Requests Received by the RNC from the CN Through the Iu Interface
..........................................................................................................................................................................................212
1.5 Measurement of IUR Interface Performance(IUR)....................................................................................................213
1.5.1 Measurement related to DRNC in Iur interface(DRNC.IUR).................................................................................214
1.5.1.1 Number of ERROR INDICATION Messages Received by the RNC on Iur Interface........................................219
1.5.1.2 Number of ERROR INDICATION Messages Sent by the RNC on Iur Interface...............................................221
1.5.1.3 Number of Requests to Establish a Radio Link Received by DRNC on Iur Interface.........................................222
1.5.1.4 Number of Successful Radio Link Establishments by DRNC on Iur Interface...................................................223
1.5.1.5 Number of Radio Links Unsuccessfully Established by DRNC on Iur Interface for Different Causes...............225
1.5.1.6 Number of Radio Links to Be Deleted by DRNC on Iur Interface......................................................................228
1.5.1.7 Number of Successful Radio Link Deletions by DRNC on Iur Interface............................................................229
1.5.1.8 Number of Radio Link Addition Requests by DRNC on Iur Interface................................................................231
1.5.1.9 Number of Successful Radio Link Additions on DRNC Iur Interface.................................................................232
1.5.1.10 Number of Failed Radio Links Additions by DRNC on Iur Interface for Different Causes..............................234
1.5.1.11 Number of Radio Links to Be Reconfigured by DRNC.....................................................................................237
1.5.1.12 Number of Radio Links Successfully Reconfigured by DRNC on Iur Interface...............................................238
1.5.1.13 Number of Failed Radio Link Synchronous Reconfigurations by DRNC on Iur Interface for Different Causes
..........................................................................................................................................................................................239
1.5.1.14 Number of Radio Links with Reconfiguration Canceled by the DRNC over Iur..............................................243
1.5.1.15 Number of Radio Link Failures on Iur Interface................................................................................................244
1.5.1.16 Number of Failed Radio Links on Iur Interface for Different Causes................................................................245
1.5.1.17 Number of RADIO LINK RESTORE INDICATION Messages sent by DRNC on Iur Interface....................248
1.5.1.18 Number of COMMON TRANSPORT CHANNEL RESOURCES REQUEST Messages Received by DRNC on
Iur Interface......................................................................................................................................................................249
1.5.1.19 Number of COMMON TRANSPORT CHANNEL RESOURCES RESPONSE Messages Sent by DRNC on Iur
Interface............................................................................................................................................................................251
1.5.1.20 Number of COMMON TRANSPORT CHANNEL RESOURCES FAILURE Messages sent by DRNC on the Iur
Interface due to Transport Resource Unavailable............................................................................................................252
1.5.1.21 Number of COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST Messages Received by
DRNC on Iur Interface.....................................................................................................................................................254
1.5.2 Reserved counter for Iur interface(RESERVE.IUR)...............................................................................................255
1.5.2.1 Reserved counters for Iur interface.......................................................................................................................256
1.5.3 Measurement Related to SCCP for Iur Interface(SIG.SCCP.IUR).........................................................................258
1.5.3.1 Number of SCCP Connection Requests Sent by the Local RNC to the Peer RNC Through the Iur Interface
..........................................................................................................................................................................................258
1.5.3.2 Number of Successful SCCP Connection Requests Sent by the Local RNC to the Peer RNC Through the Iur
Interface............................................................................................................................................................................260
1.5.3.3 Number of SCCP Connection Requests Received by the Local RNC from the Peer RNC Through the Iur Interface
..........................................................................................................................................................................................261
1.5.3.4 Number of Successful SCCP Connection Requests Received by the Local RNC from the Peer RNC Through the
Iur Interface......................................................................................................................................................................263
Issue 06 (2014-01-20) Huawei Proprietary and Confidential ix

BSC6900 UMTS
1.5.4 Measurement related to SRNC in Iur interface(SRNC.IUR)..................................................................................264

1.5.4.1 Number of Radio Links Requested to Establish by SRNC on Iur Interface........................................................273
1.5.4.2 Number of Radio Links Successfully Established by SRNC on Iur Interface.....................................................274
1.5.4.3 Number of Failed Radio Link Establishments by SRNC on Iur Interface for Different Causes..........................276
1.5.4.4 Number of Radio Links Deleted on Iur Interface for SRNC................................................................................279
1.5.4.5 Number of Successful deleted Radio Links on Iur Interface for SRNC...............................................................280
1.5.4.6 Number of Radio Links Requested to Add by SRNC on Iur Interface................................................................282
1.5.4.7 Number of Radio Links Successfully Added by SRNC on Iur Interface.............................................................283
1.5.4.8 Number of Failed Radio Link Additions for Different Causes on Iur Interface for SRNC.................................285
1.5.4.9 Number of Radio Links Requested to Reconfigure by SRNC on Iur Interface...................................................288
1.5.4.10 Number of Radio Links Successfully Reconfigured by SRNC on Iur Interface................................................289
1.5.4.11 Number of Radio Links Unsuccessfully Reconfigured by SRNC on Iur Interface for Different Causes..........290
1.5.4.12 Number of Radio Links Unsuccessfully Reconfigured by SRNC on Iur Interface for No Response................293
1.5.4.13 Number of Failed Radio Links of SRNC on Iur Interface.................................................................................294
1.5.4.14 Number of Failed Radio Links of SRNC on Iur Interface for Different Causes................................................296
1.5.4.15 Number of Radio Links Restored by SRNC on Iur Interface.............................................................................298
1.5.4.16 Number of Soft Handovers Initiated by SRNC on Iur Interface........................................................................299
1.5.4.17 Number of Successful Soft Handovers Initiated by SRNC on Iur Interface......................................................301
1.5.4.18 Number of COMMON TRANSPORT CHANNEL RESOURCES REQUEST Messages Sent by SRNC on Iur
Interface............................................................................................................................................................................302
1.5.4.19 Number of COMMON TRANSPORT CHANNEL RESOURCES RESPONSE Messages Received by SRNC on
Iur Interface......................................................................................................................................................................303
1.5.4.20 Number of COMMON TRANSPORT CHANNEL RESOURCES FAILURE Messages Received by SRNC on
Iur Interface Due to Transport Resource Unavailable......................................................................................................305
1.5.4.21 Number of COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST Messages of SRNC on
Iur Interface......................................................................................................................................................................306
1.5.4.22 Number of PS RABs Normally Released on CCH (FACH or PCH) for SRNC (Iur Interface)........................308
1.5.4.23 Number of Normally Released CS RABs According to Different Service on the IUR interface......................310
1.5.4.24 Number of Abnormally Released CS RABs According to Different Service on SRNC Iur Interface..............314
1.5.4.25 Number of PS RABs Abnormally Released on CCH (FACH or PCH) for SRNC (Iur Interface)....................318
1.5.4.26 Number of Normally Released PS RABs According to Different Service on the IUR interface......................320
1.5.4.27 Number of Normally Released HSPA RABs on Iur Interface for SRNC..........................................................324
1.5.4.28 Number of Abnormally Released PS RABs According to Different Service Type on SRNC Iur Interface......326
1.5.4.29 Number of Abnormally Released HSPA-Carried RABs on SRNC Iur Interface..............................................330
1.5.4.30 Number of RLs with Reconfiguration Canceled by the SRNC over Iur............................................................332
1.5.4.31 Number of CS Conversational RABs carried on HSPA Normally Released on Iur Interface for SRNC..........334
1.5.4.32 Number of CS Conversational RABs carried on HSPA Abnormally Released on Iur Interface for SRNC......336
1.5.4.33 Number of Normally Released PS RABs that Are in CELL_PCH or URA_PCH State on Iur Interface for SRNC
..........................................................................................................................................................................................339
1.5.4.34 Number of Abnormally Released PS RABs that Are in CELL_PCH or URA_PCH State on Iur Interface for SRNC
..........................................................................................................................................................................................341
1.5.4.35 Number of RRC Connection Releases (CCCH) Sent by the SRNC over the Iur Interface due to DSCR.........344
1.5.4.36 Number of RRC Connection Releases (DCCH) Sent by the SRNC over the Iur Interface due to DSCR.........346
Issue 06 (2014-01-20) Huawei Proprietary and Confidential x

BSC6900 UMTS
1.5.5 Measurement related to traffic for Iur Interface(TRFFIC.IUR)..............................................................................347

1.5.5.1 Number of UL Bytes of Signaling Data Received by SRNC on DCH of Iur Interface.......................................351
1.5.5.2 Number of DL Bytes of Signaling Data Sent by SRNC on DCH of Iur Interface...............................................352
1.5.5.3 Number of Bytes of UL PS R99 Services Received by SRNC on Iur Interface..................................................353
1.5.5.4 Number of Bytes of DL PS R99 Services Sent by SRNC on Iur Interface..........................................................354
1.5.5.5 Number of Bytes of UL CS Services Received by SRNC over DCH on Iur Interface........................................355
1.5.5.6 Number of Bytes of DL CS Services Sent by SRNC over DCH on Iur Interface................................................356
1.5.5.7 Number of UL Bytes Sent by DRNC on DCH of Iur Interface...........................................................................357
1.5.5.8 Number of DL Bytes Received by DRNC on DCH of Iur Interface....................................................................358
1.5.5.9 Number of Bytes of PS HSUPA Services Received by SRNC on Iur Interface..................................................359
1.5.5.10 Number of Bytes of PS HSDPA Services Received by SRNC on Iur Interface................................................360
1.5.5.11 Number of bytes of CS HSDPA conversational service in SRNC for IUR.......................................................361
1.5.5.12 Number of bytes of HSDPA services in DRNC for IUR...................................................................................362
1.5.5.13 Number of HSDPA Signaling Bytes on Iur Interface in SRNC.........................................................................362
1.5.5.14 Number of HSUPA Signaling Bytes on Iur Interface in SRNC.........................................................................363
1.5.5.15 Number of bytes of CS HSUPA conversational service in SRNC for IUR.......................................................364
1.6 Measurement of MPU Performance(MPU)................................................................................................................365
1.6.1 Measurement related to MPU(MPU)......................................................................................................................366
1.6.1.1 Throughput of PS Uplink Data for MPU..............................................................................................................366
1.6.1.2 Throughput of PS Downlink Data for MPU.........................................................................................................367
1.7 Measurement of NODEB Performance(NODEB)......................................................................................................368
1.7.1 Measurement related to Algorithm per NodeB(ALGO.NODEB)...........................................................................368
1.7.1.1 Number of UL or DL Congestions on Iub Interface.............................................................................................370
1.7.1.2 Time of UL or DL Congestions on Iub Interface.................................................................................................371
1.7.1.3 NodeB Unavailability Time..................................................................................................................................372
1.7.1.4 Total Dynamic Spectrum Sharing (DSS) Activation Duration............................................................................372
1.7.1.5 Number of Received Dynamic Spectrum Sharing (DSS)....................................................................................373
1.7.1.6 Number of Normal Spectrum Withdrawals..........................................................................................................374
1.7.1.7 Number of Urgent Spectrum Withdrawals...........................................................................................................375
1.7.1.8 Number of Abnormal Spectrum Withdrawals......................................................................................................375
1.7.1.9 NodeB Credit Usage When CE Overbooking Is Enabled....................................................................................376
1.8 Measurement of Physical RNC Node(NODESHARE)..............................................................................................378
1.8.1 Radio Access Bearer (RAB) Measurement for Physical RNC Nodes(RAB.NODESHARE)................................378
1.8.1.1 Number of CS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes
(Conversational Service)..................................................................................................................................................381
1.8.1.2 Number of Successful CS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC
Nodes (Conversational Service).......................................................................................................................................382
1.8.1.3 Number of PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes......383
1.8.1.4 Number of Successful PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC
Nodes................................................................................................................................................................................385
1.8.1.5 Number of RABs Released Abnormally due to Radio Link Failure for UEs Whose Load Is Shared Between Physical
RNC Nodes.......................................................................................................................................................................386
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xi

BSC6900 UMTS
1.8.1.6 Number of RABs Released Abnormally for UEs Whose Load Is Shared Between Physical RNC Nodes.........390
1.8.1.7 Number of RABs Released Normally for UEs Whose Load Is Shared Between Physical RNC Nodes.............393
1.8.2 Radio Resource Control (RRC) Measurement for Physical RNC Nodes(RRC.NODESHARE)............................396
1.8.2.1 Number of RRC Connection Requests Sent by UEs Whose Load Is Shared Between Physical RNC Nodes
..........................................................................................................................................................................................397
1.8.2.2 Number of Successful RRC Connection Requests Sent by UEs Whose Load Is Shared Between Physical RNC
Nodes................................................................................................................................................................................399
1.8.2.3 Delay in Setting Up RRC Connection for UEs in CELL_DCH State Whose Load Is Shared Between Physical RNC
Nodes................................................................................................................................................................................400
1.8.2.4 Delay in Setting Up RRC Connection for UEs in CELL_FACH State Whose Load Is Shared Between Physical
RNC Nodes.......................................................................................................................................................................402
1.8.2.5 Number of UEs Whose Load Is Shared Between Physical RNC Nodes..............................................................404
1.9 Measurement of Operator Performance at the NodeB Level(PLMN_NodeB)..........................................................405
1.9.1 Measurement Related to Operators at the NodeB Level(PLMN.NodeB)...............................................................406
1.9.1.1 Number of UEs With Decreased BE Service Rate in the Case of UL Credit Resource Congestion for Operator
..........................................................................................................................................................................................407
1.9.1.2 Average NodeB Credit Consumption of an Operator in the Uplink....................................................................407
1.9.1.3 Maximum NodeB Credit Consumption of an Operator in the Uplink.................................................................408
1.9.1.4 Average NodeB Credit Consumption of an Operator in the Downlink................................................................409
1.9.1.5 Maximum NodeB Credit Consumption of an Operator in the Downlinke1.........................................................410
1.10 Measurement of RNC Performance(RNC)...............................................................................................................411
1.10.1 Measurement related to AMR service(AMR.RNC)..............................................................................................412
1.10.1.1 The Average Number of AMR Users with Different UL and DL Rates............................................................414
1.10.1.2 Number of Times That Silence Is Detected in Downlink for AMR Calls per RNC..........................................417
1.10.1.3 Number of Times That Silence Is Detected in Uplink for AMR Calls per RNC...............................................418
1.10.2 Measurement related to CBS per RNC(CBS.RNC)..............................................................................................419
1.10.2.1 Number of ETWS-related WRITE-REPLACE Messages Received by the RNC.............................................419
1.10.2.2 Number of ETWS-related WRITE-REPLACE FAILURE Messages Sent by the RNC...................................421
1.10.3 Hard Handover Measurement per RNC(HHO.RNC)............................................................................................423
1.10.3.1 Number of Hard Handover Requests..................................................................................................................424
1.10.3.2 Number of Successful Hard Handovers.............................................................................................................426
1.10.4 Measurement related to CS Inter-RAT handover per RNC(IRATHO.Cs.RNC)..................................................428
1.10.4.1 Number of CS Outgoing Inter-RAT Handover Preparation Attempts...............................................................432
1.10.4.2 Number of Successful Preparations for CS Outgoing Inter-RAT Handover.....................................................433
1.10.4.3 Number of CS Outgoing Inter-RAT Handover Attempts..................................................................................435
1.10.4.4 Number of Successful CS Outgoing Inter-RAT Handovers..............................................................................436
1.10.4.5 Number of CS Incoming Inter-RAT Handover Preparation Attempts...............................................................438
1.10.4.6 Number of Successful Preparations for CS Incoming Inter-RAT Handover.....................................................439
1.10.4.7 Number of CS Incoming Inter-RAT Handover Attempts..................................................................................441
1.10.4.8 Number of Successful CS Incoming Inter-RAT Handovers..............................................................................442
1.10.5 Measurement related to PS Inter-RAT handover per RNC(IRATHO.PS.RNC)...................................................444
1.10.5.1 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC......................................................445
1.10.5.2 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by RNC..................................................447
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xii

BSC6900 UMTS
1.10.5.3 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by UE.........................................................448

1.10.5.4 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE.....................................................450
1.10.5.5 Number of LTE-to-UMTS PS Handover Attempts Caused by the CSFB of an LTE Emergency Call for RNC
..........................................................................................................................................................................................451
1.10.5.6 Number of Successful LTE-to-UMTS PS Handovers Caused by the CSFB of an LTE Emergency Call for RNC
..........................................................................................................................................................................................453
1.10.5.7 Number of Successful LTE-to-UMTS PS Handover Preparations Caused by the CSFB of LTE Emergency Calls
for RNC............................................................................................................................................................................454
1.10.6 Measurement related to LCS service(LCS.RNC)..................................................................................................456
1.10.6.1 Number of Successful Provisions of GPS Assistance Data...............................................................................459
1.10.6.2 Number of Positioning Reports Meeting Accuracy Requirement......................................................................460
1.10.6.3 Number of Positioning Requests with Different Event Types...........................................................................462
1.10.6.4 Number of Successful Positioning Reports with Different Event Types...........................................................463
1.10.6.5 Number of the positioning attempt of the different location method for RNC..................................................465
1.10.6.6 Number of the successful positioning of the different location method for RNC..............................................467
1.10.6.7 Number of the times that the location in SAS centric mode is used in the RNC...............................................469
1.10.6.8 Number of U-TDOA Positioning Attempts........................................................................................................470
1.10.6.9 Number of Successful U-TDOA Positionings....................................................................................................472
1.10.7 Measurement related to Paging per RNC(PAGE.RNC)........................................................................................473
1.10.7.1 Number of Paging Messages to UE....................................................................................................................475
1.10.7.2 Number of Successful Paging Messages to UE..................................................................................................476
1.10.7.3 Number of RNC-Originated PAGING TYPE 1 Messages................................................................................478
1.10.7.4 Number of PAGING TYPE 2 Messages............................................................................................................479
1.10.7.5 Number of Successful Responses to PAGING TYPE 1 Messages....................................................................481
1.10.7.6 Number of CS-Oriented PAGING Messages from the CN................................................................................482
1.10.7.7 Number of PS-Oriented PAGING Messages from the CN................................................................................484
1.10.7.8 Number of Failures to Respond to CS-Oriented PAGING Messages from the CN...........................................485
1.10.7.9 Number of Failures to Respond to PS-Oriented PAGING Messages from the CN...........................................487
1.10.7.10 Number of CELL UPDATE Messages from PTT UEs as Paging Response Received by RNC.....................488
1.10.7.11 Number of RNC-Originated PAGING TYPE 1 Messages to PTT UEs in CELL_PCH or URA_PCH state
..........................................................................................................................................................................................490
1.10.8 Measurement related to PDCP(PDCPGTPU.RNC)..............................................................................................491
1.10.8.1 Compression Ratio of DL Packet Headers Under ROHC..................................................................................492
1.10.8.2 Compression Ratio of DL Packets Under ROHC..............................................................................................493
1.10.8.3 Ratio of UL ROHC Decompression Failures to Total UL ROHC Decompression Operations.........................494
1.10.9 Measurement of CS RAB assignment setup per RNC(RAB.EstabCS.RNC).......................................................495
1.10.9.1 Number of CS RABs Requested to Establish.....................................................................................................496
1.10.9.2 Mean Number of CS RABs................................................................................................................................498
1.10.9.3 Number of CS VP RABs requested to establish in cell where VP is forbidden.................................................498
1.10.9.4 Number of Successful RAB Establishments for CS Services............................................................................500
1.10.10 Measurement of PS RAB assignment setup per RNC(RAB.EstabPS.RNC)......................................................501
1.10.10.1 Counters Related to the Number of PS RAB Setup Requests for Different Services......................................510
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xiii

BSC6900 UMTS
1.10.10.2 Signaling Delay of PS RAB Setup...................................................................................................................512

1.10.10.3 Counters Related to the Number of PS RAB Setup Requests for Different Maximum Downlink Bit rates
..........................................................................................................................................................................................514
1.10.10.4 Counters Related to the Number of Successful PS RAB Setups for Different Maximum Downlink Bit Rates
..........................................................................................................................................................................................518
1.10.10.5 Mean Number of PS RABs..............................................................................................................................522
1.10.10.6 Times of PS RAB established successfully with 0kbps for RNC....................................................................523
1.10.10.7 Number of Successful RAB Establishments for PS Services...........................................................................526
1.10.11 Measurement of CS RAB assignment modification per RNC(RAB.ModCs.RNC)...........................................529
1.10.11.1 Number of CS RAB Modification Requests....................................................................................................530
1.10.11.2 Number of VP Services Fallen Back to AMR Services...................................................................................531
1.10.11.3 Number of Successful CS RAB Modifications................................................................................................532
1.10.12 Measurement of PS RAB assignment modification per RNC(RAB.ModPs.RNC)............................................534
1.10.12.1 Number of PS RAB Modification Requests.....................................................................................................535
1.10.12.2 Number of Successful PS RAB Modifications.................................................................................................537
1.10.13 Measurement of multi-RAB service per RNC(RAB.MultiRab.RNC)................................................................540
1.10.13.1 Mean Number of UEs with Multi-RABs in RNC............................................................................................541
1.10.14 Measurement of RAB release per RNC(RAB.RelAbnormal.RNC)....................................................................542
1.10.14.1 Number of RABs Abnormally Released for RNC...........................................................................................546
1.10.14.2 Number of Released RABs due to RF cause....................................................................................................549
1.10.14.3 Number of Abnormally Released CS RABs....................................................................................................552
1.10.14.4 Number of Normally Released RABs..............................................................................................................555
1.10.14.5 Number of Released RABs Triggered by RNC Due to UE Signaling Connection Release............................559
1.10.14.6 Times of PS RAB of 0kbps released for failing to rate up before timer expiry...............................................560
1.10.15 Measurement of CS RAB release per RNC(RAB.RelCs.RNC)..........................................................................562
1.10.15.1 Number of CS RABs Requested to Release.....................................................................................................562
1.10.15.2 Number of Successful CS RAB Releases.........................................................................................................564
1.10.16 Measurement of PS RAB release per RNC(RAB.RelPs.RNC)...........................................................................566
1.10.16.1 Number of Successful PS RAB Releases.........................................................................................................566
1.10.16.2 Number of PS RABs Requested to Release.....................................................................................................568
1.10.17 Measurement of RB Procedure per RNC(RB.RNC)...........................................................................................569
1.10.17.1 Counters Related to the Average Number of RBs for PS R99 Conversational Services.................................579
1.10.17.2 Counters Related to the Average Number of PS R99 Interactive Service RBs................................................582
1.10.17.3 Counters Related to the Average Number of PS R99 Backgroud Service RBs...............................................584
1.10.17.4 Counters Related to the Average Number of CS Streaming Service RBs.......................................................587
1.10.17.5 Counters Related to the Average Number of CS Conversational Service RBs................................................588
1.10.17.6 Number of DCH-to-HSDPA Directed Retry Attempts....................................................................................589
1.10.17.7 Number of Successful DCH-to-HSDPA Directed Retry..................................................................................591
1.10.17.8 Counters Related to the Average Number of PS R99 Streaming Service RBs................................................593
1.10.18 Measurement of relocation per DRNC(Relocation.Drnc.RNC)..........................................................................596
1.10.18.1 Counters Related to the Number of Failed Relocation Executions for Different Causes for TRNC...............601
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xiv

BSC6900 UMTS
1.10.18.2 Number of Failed Relocation Resource Allocations Due to Reception of IU Release Command for TRNC
..........................................................................................................................................................................................603
1.10.18.3 Number of Failed Relocation Resource Allocations for TRNC.......................................................................604
1.10.18.4 Number of Reconfiguration Completions During Relocation for TRNC (UE Involved)................................607
1.10.18.5 Number of Relocation Execution Attempts for TRNC (UE Not Involved).....................................................608
1.10.18.6 Number of Successful Relocation Executions for TRNC (UE Not Involved).................................................610
1.10.18.7 Number of Successful Relocation Executions for TRNC (UE Involved)........................................................611
1.10.18.8 Number of Relocation Resource Allocation Attempts for TRNC....................................................................612
1.10.18.9 Number of Successful Relocation Resource Allocations for TRNC................................................................614
1.10.18.10 Number of Successful TRNC Relocations in the CS Domain and PS Domain (UE Involved).....................617
1.10.18.11 Number of Successful TRNC Relocations in the CS Domain and PS Domain (UE Not Involved)..............618
1.10.19 Measurement of relocation per SRNC(Relocation.Srnc.RNC)...........................................................................619
1.10.19.1 Number of Relocation Preparation Attempts Due to Different Causes for SRNC...........................................631
1.10.19.2 Number of Relocation Preparation Attempts for SRNC..................................................................................634
1.10.19.3 Number of Successful Relocation Preparations Due to Different Causes for SRNC.......................................635
1.10.19.4 Number of Successful Relocation Preparations for SRNC..............................................................................638
1.10.19.5 Number of Failed Relocation Preparations Due to Different Causes for SRNC..............................................639
1.10.19.6 Counters Related to the Number of Failed Relocation Executions During Reconfiguration for Different Causes
for SRNC..........................................................................................................................................................................645
1.10.19.7 Counters Related to the Number of Failed SRNC Relocation Executions Due to Timer Expiry for IU Release
Command for SRNC........................................................................................................................................................647
1.10.19.8 Counters Related to the Number of Relocation Execution Attempts for SRNC (UE Not Involved)...............649
1.10.19.9 Number of Failed Relocation Executions Due to Reception of IU Release Command for SRNC..................651
1.10.19.10 Counters Related to the Number of Reconfiguration Attempts During Relocation Execution for SRNC ( UE
Involved)...........................................................................................................................................................................652
1.10.19.11 Number of Successful Relocation Executions for SRNC..............................................................................654
1.10.20 RLC measurement per RNC(RLC.RNC)............................................................................................................656
1.10.20.1 Number of Packets Sent at the RLC Layer.......................................................................................................657
1.10.20.2 Number of Packets Received at the RLC Layer...............................................................................................658
1.10.20.3 Number of Packets Discarded by All RLCs in RNC........................................................................................659
1.10.20.4 Number of Packets Retransmitted by All RLCs in AM Mode in RNC...........................................................660
1.10.20.5 Number of PDUs with the Size Smaller than 336 bit Received by RLCs In Acknowledged Mode Carried by
TRB..................................................................................................................................................................................661
1.10.20.6 Number of PDUs with the Size Greater than or Equal to 336 bit Received by RLCs In Acknowledged Mode
Carried by TRB................................................................................................................................................................661
1.10.21 Measurement related to IMS(RNC.IMS)............................................................................................................662
1.10.21.1 Mean Number of UEs Setting Up Different IMS Services..............................................................................664
1.10.21.2 Number of UEs Setting Up IMS Services........................................................................................................666
1.10.22 RRC connection release measurement per RNC(RRC.Rel.RNC)......................................................................667
1.10.22.1 Number of RRC Connection Releases.............................................................................................................668
1.10.22.2 Counters Related to the Number of RRC Connection Releases due to Different Causes................................669
1.10.22.3 Number of RRC Releases Due to Failure in the UE State Transition to CELL_PCH Triggered by Signaling
Connection Release Indication.........................................................................................................................................672
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xv

BSC6900 UMTS
1.10.22.4 Number of RRC Connection Releases Triggered by SRNC Due to DSCR.....................................................673

1.10.22.5 Number of RRC Connection Releases Triggered by DRNC Due to DSCR....................................................675
1.10.23 RRC connection setup measurement per RNC(RRC.Setup.RNC)......................................................................677
1.10.23.1 Counters Related to the Number of RRC Connection Requests Processed by RNC.......................................680
1.10.23.2 Total Number of RRC Connection Requests Received by RNC.....................................................................682
1.10.23.3 Counters Related to the Number of Successful RRC Connection Establishments..........................................683
1.10.24 RRC state measurement(RRC.STATE)..............................................................................................................685
1.10.24.1 Counters Related to the Number of UEs in Different RRC Connection States for RNC.................................686
1.10.24.2 Number of PTT UEs in URA_PCH State for RNC..........................................................................................687
1.10.24.3 Average Number of UEs in the URA_PCH State and Carried on the EPCH for RNC...................................688
1.10.25 Soft Handover Measurement per RNC(SHO.RNC)............................................................................................689
1.10.25.1 Number of Soft and Softer Handover Attempts...............................................................................................691
1.10.25.2 Number of Successful Soft Handovers.............................................................................................................692
1.10.25.3 Mean Number of UEs with One to Six Radio Link.........................................................................................694
1.10.25.4 Number of Call Drops due to Soft Handover Failures.....................................................................................696
1.10.26 Measurement related to Security mode per RNC(SM.RNC)..............................................................................698
1.10.26.1 Number of SECURITY MODE COMMAND Messages Received by RNC from CN...................................699
1.10.26.2 Number of SECURITY MODE COMPLETE Messages Sent from RNC to CN............................................700
1.10.26.3 Number of SECURITY MODE REJECT Messages Sent from RNC to CN for Different Causes.................702
1.10.26.4 Number of SECURITY MODE COMMAND Messages Sent from RNC to UE............................................703
1.10.26.5 Number of SECURITY MODE COMPLETE Messages Received by RNC from UE....................................705
1.10.27 Traffic Measurement per RNC(TRAFF.LOAD.RNC)........................................................................................706
1.10.27.1 Equivalent Erlang of CS Domain in RNC........................................................................................................708
1.10.27.2 Maximum Equivalent Erlang of CS Domain in RNC......................................................................................708
1.10.27.3 UL Traffic of R99 PS Domain in RNC............................................................................................................709
1.10.27.4 Maximum UL Traffic of R99 PS Domain in RNC..........................................................................................710
1.10.27.5 DL Traffic of R99 PS Domain in RNC............................................................................................................711
1.10.27.6 Maximum DL Traffic of R99 PS Domain in RNC..........................................................................................712
1.10.27.7 DL Traffic of HSDPA PS Domain in RNC......................................................................................................713
1.10.27.8 Maximum DL Traffic of HSDPA PS Domain in RNC....................................................................................714
1.10.27.9 UL Traffic of HSUPA PS Domain in RNC......................................................................................................714
1.10.27.10 Maximum UL Traffic of HSUPA PS Domain in RNC..................................................................................715
1.10.27.11 DL Traffic of MBMS or IMB PS Domain in RNC........................................................................................716
1.10.27.12 Maximum DL Traffic of MBMS or IMB PS Domain in RNC......................................................................717
1.10.27.13 Average Total Throughout of UL and DL PS Services for RNC...................................................................718
1.10.27.14 Maximum Total Throughout of UL and DL PS Services..............................................................................718
1.10.27.15 Erlang of CS Services for RNC......................................................................................................................719
1.11 Measurement of ROAMCNOPERATOR Performance(ROAM_CNOPERATOR)................................................720
1.11.1 Roaming UE Registration Measurement Under MOCN(MOCN.ROAM.CNOPERATOR)................................721
1.11.1.1 Number of Roaming UEs that Is Registered In Local Operator Under MOCN for the First Time...................721
1.12 Measurement of Radio Cell Performance(UCELL).................................................................................................723
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xvi

BSC6900 UMTS
1.12.1 Measurement related to Algorithm per cell(ALGO.Cell)......................................................................................725

1.12.1.1 Number of DL Rate Adjustments for AMR Services.........................................................................................748
1.12.1.2 Counters Related to the Number of Successful Dynamic Channel Conversions Between DCH and FACH
..........................................................................................................................................................................................750
1.12.1.3 Number of State Transfer Attempts from CELL_FACH to CELL_PCH..........................................................751
1.12.1.4 Number of Successful State Transfers from CELL_FACH to CELL_PCH......................................................752
1.12.1.5 Counters Related to the Number of Downlink DCH DCCC Downsizing Attempts Based on Different Strategies
..........................................................................................................................................................................................754
1.12.1.6 Counters Related to the Number of Successful DL DCH DCCC Downsizings Based on Different DCCC Strategies
..........................................................................................................................................................................................756
1.12.1.7 Counters Related to the Number of UL or DL Overload Congestion................................................................757
1.12.1.8 Counters Related to the Duration of UL or DL Overload Congestion...............................................................759
1.12.1.9 Number of UEs Transferring BE Service to Common Channel in Overload Congestion.................................760
1.12.1.10 Counters Related to the Duration of Cell in LDR State Due to Congestion of Various Resources.................761
1.12.1.11 Counters Related to the Number of Times a Cell Is in LDR State Due to Congestion of Various Resources
..........................................................................................................................................................................................762
1.12.1.12 Counters Related to the Number of UEs Performing BE Service TF Control in Overload Congestion..........764
1.12.1.13 Counters Related to the Number of UEs Released Due to Overload Congestion............................................764
1.12.1.14 Number of Failed Admissions Due to HSPA User Number Exceeding Threshold During RAB Establishment
for Cell..............................................................................................................................................................................766
1.12.1.15 Number of Preemptions During RAB Establishment.......................................................................................769
1.12.1.16 Number of Failed Requests for various Resources During SHO for Cell........................................................770
1.12.1.17 Number of Failed Requests for various Resources During DCCC for Cell.....................................................773
1.12.1.18 Counters Related to the Number of Failed Requests for Different Resources During Channel Type Switch
..........................................................................................................................................................................................774
1.12.1.19 Number of Failed Requests for various Resources During HHO for Cell.......................................................777
1.12.1.20 Number of Preemptions During HHO..............................................................................................................780
1.12.1.21 Number of MBMS PTM Service Releases in Overload Congestion...............................................................781
1.12.1.22 Number of MBMS PTP Service Releases in Overload Congestion.................................................................782
1.12.1.23 Counters Related to the Number of UEs Performing Inter-Frequency Load Handovers in Basic Congestion
..........................................................................................................................................................................................782
1.12.1.24 Counters Related to the Number of UEs Performing BE Service Downsizing in Basic Congestion..............784
1.12.1.25 Counters Related to the Number of UEs Performing Uncontrollable Real-Time Service QoS Renegotiation in
Basic Congestion..............................................................................................................................................................785
1.12.1.26 Counters Related to the Number of UEs Performing CS Inter-RAT Handovers in Basic Congestion............786
1.12.1.27 Counters Related to the Number of UEs Performing PS Inter-RAT Handovers in Basic Congestion............788
1.12.1.28 Counters Related to the Number of UEs Performing AMR Rate Decrease in Basic Congestion....................789
1.12.1.29 Number of UEs Performing Code Adjustment Attempts in DL Basic Congestion for Cell............................790
1.12.1.30 Number of MBMS Services Performing Power Decreasing in Basic Congestion...........................................791
1.12.1.31 Counters Related to the Number of Qoffset Updates Due to Load Level Change...........................................792
1.12.1.32 Counters Related to the Number of Sintersearch Updates Due to Cell Load Change.....................................793
1.12.1.33 Number of Successful Cell Resource Requests During HHO..........................................................................795
1.12.1.34 Number of Cell Resource Requests During HHO............................................................................................797
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xvii

BSC6900 UMTS
1.12.1.35 Number of Successful Cell Resource Requests During RAB Establishment..................................................798

1.12.1.36 Number of Cell Resource Requests During RAB Establishment.....................................................................799
1.12.1.37 Number of Successful Cell Resource Requests due to UE Service Reconfiguration (Cell)............................801
1.12.1.38 Number of Cell Resource Requests due to UE Service Reconfiguration (Cell)..............................................802
1.12.1.39 Number of Successful Cell Resource Requests During SHO..........................................................................803
1.12.1.40 Number of Cell Resource Requests During SHO............................................................................................804
1.12.1.41 Number of Successful Cell Resource Requests During Channel Type Switch................................................805
1.12.1.42 Number of Cell Resource Requests During Channel Type Switch..................................................................807
1.12.1.43 Counters Related to the Mean Number of Equivalent Voice UEs in CEL_DCH State...................................808
1.12.1.44 Duration of Cell Dynamic Shutdown Due to Automatic Shutdown................................................................809
1.12.1.45 Cell Unavailability Duration caused by O&M (Cell).......................................................................................810
1.12.1.46 Counters Related to the Cell Credit Usage.......................................................................................................810
1.12.1.47 Counters Related to the Duration of Max and Min Values of CPICH Power Due to Cell Breathing..............812
1.12.1.48 Counters Related to the Number of CPICH Power Adjustments Due to Cell Breathing.................................813
1.12.1.49 Counters Related to the Duration of TCP Underload and Overload................................................................814
1.12.1.50 Average CPICH Power for Cell.......................................................................................................................815
1.12.1.51 Counters Related to the Number of Dynamic Channel Conversion Attempts Between DCHs and FACHs
..........................................................................................................................................................................................816
1.12.1.52 Number of UL Rate Adjustments for AMR Services.......................................................................................817
1.12.1.53 Counters Related to the Number of UL EDCH DCCC Attempts Based on Throughput or RLC BO.............819
1.12.1.54 Counters Related to the Number of Successful UL EDCH DCCC Operations Based on Throughput or RLC BO
..........................................................................................................................................................................................820
1.12.1.55 Number of UEs Performing Code Adjustment Based on HSDPA...................................................................822
1.12.1.56 Number of DL DCH DCCC Upsizing Attempts Based on Throughput or RLC BO.......................................823
1.12.1.57 Number of Successful DL DCH DCCC Upsizings Based on Throughput or RLC BO...................................825
1.12.1.58 Number of UL DCH DCCC Upsizing Attempts Based on Throughput or RLC BO.......................................826
1.12.1.59 Number of Successful UL DCH DCCC Upsizings Based on Throughput or RLC BO...................................828
1.12.1.60 Counters Related to the Number of UL DCH DCCC Downsizing Attempts Based on Different Strategies
..........................................................................................................................................................................................829
1.12.1.61 Counters Related to the Number of Successful UL DCH DCCC Downsizings Based on Different Strategies
..........................................................................................................................................................................................831
1.12.1.62 Number of UEs Performing Successful Code Adjustment in DL Basic Congestion.......................................833
1.12.1.63 Number of UEs Performing Successful Code Adjustment Based on HSDPA.................................................834
1.12.1.64 Duration of Cell Unavailability Due to System Faults.....................................................................................835
1.12.1.65 Duration of HSDPA Service Unavailability Due to System Fault...................................................................836
1.12.1.66 Duration of HSUPA Service Unavailability Due to System Fault...................................................................837
1.12.1.67 Number of Attempts to transfer state from CELL_PCH to CELL_FACH for cell..........................................838
1.12.1.68 Number of Successful state transfer from CELL_PCH to CELL_FACH for cell...........................................839
1.12.1.69 Number of state transfer from CELL_PCH to URA_PCH for cell..................................................................842
1.12.1.70 Number of Attempts to transfer state from URA_PCH to CELL_FACH for cell...........................................843
1.12.1.71 Number of successful state transfer from URA_PCH to CELL_FACH in the best cell..................................845
1.12.1.72 Number of Cell Deletions or Establishments Due to Dynamic Cell Shutdown...............................................848
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xviii

BSC6900 UMTS
1.12.1.73 Number of State Transfer Attempts from CELL_DCH to CELL_PCH for Cell.............................................849
1.12.1.74 Number of Successful State Transfers from CELL_DCH to CELL_PCH for Cell.........................................850
1.12.1.75 Number of State Transfer Attempts from CELL_DCH or CELL_FACH to CELL_PCH for FAST DORMANCY
user for Cell......................................................................................................................................................................852
1.12.1.76 Number of Successful State Transfers from CELL_DCH or CELL_FACH to CELL_PCH for FAST
DORMANCY user...........................................................................................................................................................854
1.12.1.77 Number of Attempts to transfer state from CELL_PCH to CELL_DCH for cell............................................856
1.12.1.78 Number of Successful state transfer from CELL_PCH to CELL_DCH for cell..............................................857
1.12.1.79 Number of Attempts to transfer state from URA_PCH to CELL_DCH for cell..............................................859
1.12.1.80 Number of successful state transfer from URA_PCH to CELL_DCH in the best cell....................................860
1.12.1.81 Number of Attempts of CELL_PCH/URA_PCH-to-CELL_DCH State Transition Together with DRD for Cell
..........................................................................................................................................................................................862
1.12.1.82 Number of Successful CELL_PCH/URA_PCH-to-CELL_DCH State Transitions Together with DRDs for Cell
..........................................................................................................................................................................................863
1.12.1.83 Number of CPICH Power Adjustments Based on RTWP for Cell..................................................................865
1.12.1.84 Duration of PCPICH Power Under Minimum RTWP Threshold....................................................................866
1.12.1.85 Number of State Transfer Attempts from CELL_DCH to CELL_PCH or URA_PCH for Cell for HSDPA service
..........................................................................................................................................................................................867
1.12.1.86 Number of Successful Times That a UE Performing HSDPA Services Transits to CELL_PCH or URA_PCH
State for cell......................................................................................................................................................................868
1.12.1.87 Number of Attempts for a UE Performing HSUPA Services to Transit to CELL_PCH or URA_PCH State for
Cell....................................................................................................................................................................................870
1.12.1.88 Number of Successful Times That a UE Performing HSUPA Services Transits to CELL_PCH or URA_PCH
State for cell......................................................................................................................................................................871
1.12.1.89 Number of Attempts for a UE Performing PS R99 Services to Transit to CELL_PCH or URA_PCH State for
Cell....................................................................................................................................................................................873
1.12.1.90 Number of Successful Times That a UE Performing PS R99 Services Transits to CELL_PCH or URA_PCH
State for cell......................................................................................................................................................................874
1.12.1.91 Number of Times That PS R99 Service Rate Is Found to Be Higher than HSUPA Service Rate...................876
1.12.1.92 Number of PS R99 BE Rate Reduction Requests Triggered by Unfairness Between PS R99 Service Rate and
HSUPA Service Rate........................................................................................................................................................877
1.12.1.93 Duration of CPU Resource Insufficiency Reported by NodeB........................................................................878
1.12.1.94 Congestion Duration of DCCHs, DTCHs and CCCHs Carried over FACHs for Cell....................................879
1.12.2 Algorithm Measurement2 for Cell(ALGO2.Cell).................................................................................................880
1.12.2.1 Average Number of UEs Using OLPC Enhancement Based on SIRerror Distribution.....................................886
1.12.2.2 Average and Maximum Uplink Background Noise...........................................................................................887
1.12.2.3 Number of Automatic Uplink Background Noise Updates................................................................................888
1.12.2.4 Counters Related to the Number of Failed in Channal Transfering Process......................................................889
1.12.2.5 Number of RoT adjustments in an HSUPA cell.................................................................................................890
1.12.2.6 Number of Successful TTI Switchovers with Various Causes During RB Reconfiguration in a Cell(2ms to 10ms)
..........................................................................................................................................................................................891
1.12.2.7 Number of Times HSUPA UEs Processing BE Services Succeed in Setting Up RABs over the DCH in Case of
Weak Coverage.................................................................................................................................................................893
1.12.2.8 Mean Number of Access Classes Restricted Due to Cell Resource Congestion................................................894
1.12.2.9 Duration of Access Class Restriction Triggered by Cell Resource Congestion.................................................896
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xix

BSC6900 UMTS
1.12.2.10 Number of UEs Involved in Inter-Frequency Load-based Handovers in a CLB Cell......................................897

1.12.2.11 Number of Attempts to Configure CQI Feedback Period for a Cell................................................................898
1.12.2.12 Number of Attempts to Configure BLER in a Congested or Normal Cell.......................................................899
1.12.2.13 Number of CS RABs Abnormally Released for Special UEs for Cell.............................................................900
1.12.2.14 Number of CS RABs Normally Released for Special UEs for Cell.................................................................903
1.12.2.15 Uplink Actual Cell Load...................................................................................................................................905
1.12.2.16 Number of CELL_FACH to URA_PCH State Transition Attempts................................................................907
1.12.2.17 Number of Successful CELL_FACH to URA_PCH State Transitions............................................................909
1.12.2.18 Number of CELL_DCH to URA_PCH State Transition Attempts..................................................................911
1.12.2.19 Number of Successful CELL_DCH to URA_PCH State Transitions..............................................................912
1.12.2.20 Number of Pilot PO Optimization Attempts in the DL DPCH for Cell...........................................................914
1.12.2.21 Number of Normal Pilot PO Attempts in the DL DPCH for Cell....................................................................915
1.12.2.22 Total number of times a micro cell transits to the total desensitization state...................................................916
1.12.2.23 Total time periods of the total desensitization state for a micro cell................................................................916
1.12.2.24 Average desensitization intensity for a micro cell............................................................................................917
1.12.2.25 Average and Maximum Uplink Credit Usage of LCG for Cell........................................................................918
1.12.2.26 Number of State Transition Attempts from CELL_PCH or URA_PCH to CELL_FACH and then to CELL_DCH
Due to Data Transmission Requirements for Cell............................................................................................................919
1.12.2.27 Number of Successful State Transitions from CELL_PCH or URA_PCH to CELL_FACH and then to
CELL_DCH Due to Data Transmission Requirements for Cell......................................................................................921
1.12.3 Measurement related to BLER per cell(BLER.Cell).............................................................................................922
1.12.3.1 Percentage of Duration When UL BLER on DCH Exceeds Target Value for Cell...........................................928
1.12.3.2 UL BLER of Services on RACH or DCH for Cell.............................................................................................933
1.12.3.3 Number of TBs with UL CRCI Errors for Services on RACH or DCH for Cell...............................................936
1.12.3.4 Number of UL BLER Samplings for Services on the RACH or DCH for Cell.................................................938
1.12.3.5 Percentage of Duration for AMR Voice Quality Being at A Level to Total Call Duration for Cell..................940
1.12.3.6 Average VQI for AMR Services........................................................................................................................942
1.12.4 Cell Measurement on BOOST(BOOST.CELL)....................................................................................................943
1.12.4.1 Number of R99 Downlink Bytes of UU BOOST Anchor for Cell....................................................................946
1.12.4.2 Mean Throughput of R99 Downlink of UU BOOST Anchor for Cell...............................................................947
1.12.4.3 Number of HSDPA Downlink Bytes of UU BOOST Anchor for Cell..............................................................948
1.12.4.4 Mean Throughput of HSDPA Downlink of UU BOOST Anchor for Cell........................................................948
1.12.4.5 Number of R99 Uplink Bytes of UU BOOST Anchor for Cell.........................................................................949
1.12.4.6 Mean Throughput of R99 Uplink of UU BOOST Anchor for Cell....................................................................950
1.12.4.7 Number of HSUPA Uplink Bytes of UU BOOST Anchor for Cell...................................................................951
1.12.4.8 Mean Throughput of HSUPA Uplink of UU BOOST Anchor for Cell.............................................................952
1.12.4.9 Number of R99 Downlink Bytes of UU BOOST Branch for Cell.....................................................................953
1.12.4.10 Mean Throughput of R99 Downlink of UU BOOST Branch for Cell.............................................................953
1.12.4.11 Number of HSDPA Downlink Bytes of UU BOOST Branch for Cell............................................................954
1.12.4.12 Mean Throughput of HSDPA Downlink of UU BOOST Branch for Cell.......................................................955
1.12.4.13 Number of R99 Uplink Bytes of UU BOOST Branch for Cell........................................................................956
1.12.4.14 Mean Throughput of R99 Uplink of UU BOOST Branch for Cell..................................................................957
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xx

BSC6900 UMTS
1.12.4.15 Number of HSUPA Uplink Bytes of UU BOOST Branch for Cell.................................................................958

1.12.4.16 Mean Throughput of HSUPA Uplink of UU BOOST Branch for Cell............................................................959
1.12.4.17 Number of UU BOOST BPL Capability Indication Messages Received for Cell...........................................960
1.12.4.18 Number of Successful Responses to UU BOOST BPL Capability Indication Messages Transmitted for Cell
..........................................................................................................................................................................................961
1.12.4.19 Number of UU BOOST BPL User Information Indication Messages Received for Cell................................962
1.12.4.20 Number of Successful Responses to UU BOOST BPL User Information Indication Messages Transmitted for
Cell....................................................................................................................................................................................963
1.12.4.21 Number of UU BOOST BPL Release Messages Transmitted for Cell............................................................964
1.12.4.22 Number of Successful UU BOOST Setups for Cell.........................................................................................965
1.12.4.23 Number of Normal UU BOOST Anchor Releases for Cell.............................................................................966
1.12.4.24 Number of Normal UU BOOST Branch Releases for Cell..............................................................................967
1.12.4.25 Average Number of UU BOOST Anchor UEs for Cell...................................................................................969
1.12.4.26 Average Number of UU BOOST Branch UEs for Cell....................................................................................969
1.12.5 Common Channel Measurement per Cell(CCH.Cell)...........................................................................................970
1.12.5.1 Number of TBs That Contain only TRB Data on FACHs.................................................................................971
1.12.5.2 Number of TBs That Contain SRB Data on FACHs..........................................................................................972
1.12.5.3 Number of TTIs During Which One SRB TB Is Transmitted on FACHs.........................................................972
1.12.5.4 Number of TRB TBs Received on RACHs........................................................................................................973
1.12.6 Cell Update Measurement per cell(CELLUPDATE.Cell)....................................................................................974
1.12.6.1 Number of Unsuccessful Cell Updates due to RL Failure (No Response).........................................................979
1.12.6.2 Number of Confirmation Messages from SRNC...............................................................................................980
1.12.6.3 Number of Cell Update Attempts for Different Causes.....................................................................................982
1.12.6.4 Number of Successful Cell Updates for Different Causes.................................................................................984
1.12.6.5 Number of RRC Connection Releases due to Cell Update Failure....................................................................989
1.12.6.6 Number of Cell Update Failures due to No Response from UEs in the CELL_FACH State for Cell...............990
1.12.6.7 Number of Cell Updates in a Cell......................................................................................................................991
1.12.6.8 Number of Cell Updates Triggered by CS Service Establishments in a Cell.....................................................992
1.12.6.9 Number of Cell Updates that Are Under CPU Usage-Based Flow Control and Are Triggered by CS Service
Establishments in a Cell...................................................................................................................................................993
1.12.6.10 Number of Cell Updates that Are Under RRC Queuing-Based Flow Control and Are Triggered by CS Service
Establishments in a Cell...................................................................................................................................................994
1.12.6.11 Number of Cell Updates that Are Under RRC Queuing-Based Flow Control in a Cell..................................995
1.12.6.12 Number of Cell Update Attempts for Cell (Originating Conversational Call).................................................996
1.12.6.13 Number of Successful Cell Updates for Cell (Originating Conversational Call).............................................997
1.12.6.14 Number of Outgoing P2F Redirections for Cell...............................................................................................999
1.12.6.15 Number of Incoming P2F Redirections for Cell (Cell Update)......................................................................1001
1.12.6.16 Number of P2F Redirection Failures Caused by UE Not Accessing the Target Frequency for Cell.............1003
1.12.6.17 Number of P2F Redirection Failures Caused by UE No Response for Cell..................................................1004
1.12.7 Measurement of Compressed Mode per cell(CM.Cell).......................................................................................1007
1.12.7.1 Number of Up Link SF-2 Compressed Mode Activation Attempts.................................................................1008
1.12.7.2 Number of Up Link HLS Compressed Mode Activation Attempts.................................................................1009
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxi

BSC6900 UMTS
1.12.7.3 Number of Up Link SF-2 Compressed Mode Activation Fails........................................................................1010

1.12.7.4 Number of Up Link HLS Compressed Mode Activation Fails........................................................................1011
1.12.7.5 Number of Down Link SF-2 Compressed Mode Activation Attempts............................................................1012
1.12.7.6 Number of Down Link HLS Compressed Mode Activation Attempts............................................................1014
1.12.7.7 Number of Down Link SF-2 Compressed Mode Activation Fails...................................................................1015
1.12.7.8 Number of Down Link HLS Compressed Mode Activation Fails...................................................................1016
1.12.8 EFACH Measurement per cell(EFACH.Cell).....................................................................................................1018
1.12.8.1 Number of RRC Connection Requests in a Cell (EFACH)..............................................................................1021
1.12.8.2 Number of Successful RRC Connection Setups in a Cell (EFACH)...............................................................1023
1.12.8.3 Number of PS RAB Setup Attempts on EFACH in a Cell...............................................................................1024
1.12.8.4 Number of Successful PS RAB Setup on EFACH in a Cell............................................................................1025
1.12.8.5 Signaling Delay of PS RAB Established on CCH in a Cell.............................................................................1027
1.12.8.6 Number of Abnormally Released PS RABs on the EFACH in a Cell.............................................................1028
1.12.8.7 Number of Normal Released PS RABs on the EFACH in a Cell....................................................................1031
1.12.8.8 Number of Downlink MAC PDU Bytes on the EFACH over the Iub Interface..............................................1033
1.12.8.9 Signaling Delay of RRC Established on EFACH in a Cell..............................................................................1034
1.12.8.10 Number of UEs Carried on the EFACH or Those Carried on the EFACH and Using E-DRX.....................1036
1.12.8.11 Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_DCH (DCH) for Cell
........................................................................................................................................................................................1038
1.12.8.12 Number of Successful State Transitions from Enhanced CELL_FACH to CELL_DCH (DCH) for Cell
........................................................................................................................................................................................1039
1.12.8.13 Number of Successful State Transitions from Enhanced CELL_FACH to CELL_DCH (HS-DSCH) for Cell
........................................................................................................................................................................................1041
1.12.8.14 Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_DCH (HS-DSCH) for Cell
........................................................................................................................................................................................1042
1.12.8.15 Number of Successful State Transitions from CELL_PCH or URA_PCH to Enhanced CELL_FACH for Cell
........................................................................................................................................................................................1044
1.12.8.16 Number of Attempts at State Transitions from CELL_PCH or URA_PCH to Enhanced CELL_FACH for Cell
........................................................................................................................................................................................1045
1.12.8.17 Number of Successful State Transitions from Enhanced CELL_FACH to CELL_PCH or URA_PCH for Cell
........................................................................................................................................................................................1047
1.12.8.18 Number of Attempts at State Transitions from Enhanced CELL_FACH to CELL_PCH or URA_PCH for Cell
........................................................................................................................................................................................1048
1.12.9 EPCH Measurement per cell(EPCH.Cell)...........................................................................................................1050
1.12.9.1 Average Number of UEs Carried on the EPCH or Those Carried on the EPCH and Allocated Dedicated H-RNTI
for Cell............................................................................................................................................................................1050
1.12.10 ERACH Measurement per cell(ERACH.Cell)..................................................................................................1051
1.12.10.1 Number of UEs Carried on ERACH for Cell.................................................................................................1053
1.12.10.2 Number of Requests for Setting Up RRC Connections on an ERACH for Cell............................................1054
1.12.10.3 Number of Successful RRC Connection Setups on an ERACH for Cell.......................................................1056
1.12.10.4 Number of PS RAB Setup Requests on an ERACH for Cell.........................................................................1057
1.12.10.5 Number of Successful PS RAB Setups on an ERACH for Cell.....................................................................1059
1.12.10.6 Number of PS RABs Normally Released on an ERACH for Cell.................................................................1060
1.12.10.7 Number of PS RABs Abnormally Released on an ERACH for Cell.............................................................1062
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxii

BSC6900 UMTS
1.12.10.8 RRC Connection Setup Duration on an ERACH for Cell..............................................................................1065

1.12.10.9 Traffic over ERACH on Iub Interface............................................................................................................1067
1.12.10.10 Number of Successful State Transitions from CELL_DCH (E-DCH) to Enhanced CELL_FACH (E-DCH) for
Cell..................................................................................................................................................................................1068
1.12.10.11 Number of Attempts at State Transitions from CELL_DCH (E-DCH) to Enhanced CELL_FACH (E-DCH) for
Cell..................................................................................................................................................................................1070
1.12.11 Hard Handover Measurement per cell(HHO.Cell)............................................................................................1072
1.12.11.1 Number of Decisions for Outgoing Hard Handovers.....................................................................................1097
1.12.11.2 Number of Decisions for Incoming Hard Handovers.....................................................................................1099
1.12.11.3 Number of Outgoing Inter-Frequency Hard Handover Attempts...................................................................1101
1.12.11.4 Number of Incoming Hard Handover Attempts.............................................................................................1104
1.12.11.5 Number of Outgoing Inter-Band Hard Handover Attempts for Different Services.......................................1106
1.12.11.6 Number of Outgoing Emergency Blind Handover Attempts.........................................................................1108
1.12.11.7 Counters Related to the Number of Outgoing Inter-Frequency Hard Handover Attempts............................1109
1.12.11.8 Number of Outgoing Macro & Micro Joint Inter-frequency Handover Attempts in PS Domain for Cell
........................................................................................................................................................................................1114
1.12.11.9 Number of Outgoing Hard Handover Attempts in NodeB.............................................................................1117
1.12.11.10 Number of Successful Outgoing Hard Handovers in NodeB.......................................................................1119
1.12.11.11 Number of Outgoing Hard Handover Attempts Between Different NodeBs of RNC.................................1121
1.12.11.12 Number of Successful Outgoing Hard Handovers Between Different NodeBs of RNC.............................1123
1.12.11.13 Number of Outgoing Hard Handover Attempts Between RNCs.................................................................1124
1.12.11.14 Number of Successful Outgoing Hard Handovers Between RNCs.............................................................1126
1.12.11.15 Number of Successful Outgoing Inter-Frequency Hard Handovers.............................................................1128
1.12.11.16 Number of Successful Outgoing Inter-Band Hard Handovers for Different Services.................................1131
1.12.11.17 Number of Successful Outgoing Emergency Blind Hard Handovers..........................................................1133
1.12.11.18 Counters Related to the Number of Successful Outgoing Inter-Frequency Hard Handovers......................1134
1.12.11.19 Number of Successful Outgoing Macro & Micro Joint Inter-frequency Handovers in PS Domain for Cell
........................................................................................................................................................................................1139
1.12.11.20 Number of Successful Incoming Hard Handovers.......................................................................................1142
1.12.11.21 Number of Failed Outgoing Hard Handovers Between RNCs for Different Causes...................................1145
1.12.11.22 Number of Failed Outgoing Hard Handovers Between the RNCs Due to No Response from the UE........1148
1.12.11.23 Number of Failed Outgoing Inter-RNC Hard Handovers for Cell (Concurrent Procedures).......................1150
1.12.11.24 Number of Failed Outgoing Hard Handovers in RNC for Different Causes...............................................1151
1.12.11.25 Number of Failed Outgoing Hard Handovers in RNC Due to No Response from the UE..........................1154
1.12.11.26 Number of Failed Outgoing Intra-RNC Hard Handovers for Cell (Concurrent Procedures).......................1156
1.12.11.27 Number of Call Drops due to Unsuccessful Outgoing Hard Handovers for cell.........................................1157
1.12.11.28 Number of Failed Preparations for Outgoing Hard Handovers Due to Radio Link Establishment Failure
........................................................................................................................................................................................1160
1.12.11.29 Number of Failed Preparations for Outgoing Hard Handovers....................................................................1162
1.12.11.30 Number of Relocation Preparation Attempts with Outgoing Hard Handovers............................................1165
1.12.11.31 Number of Successful Relocation Preparations with Outgoing Hard Handovers........................................1166
1.12.11.32 Number of Relocation Execution Attempts with Outgoing Hard Handovers..............................................1168
1.12.11.33 Number of Successful Relocation Executions with Outgoing Hard Handovers..........................................1169
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxiii

BSC6900 UMTS
1.12.11.34 Counters Related to the Number of Failed Relocation Preparations with Outgoing Hard Handovers for Different
Causes.............................................................................................................................................................................1171
1.12.11.35 Counters Related to the Number of Handovers Not Performed Due to Inter-Frequency Measurement Expiry
........................................................................................................................................................................................1173
1.12.12 HSDPA Measurement per cell(HSDPA.Cell)...................................................................................................1175
1.12.12.1 Number of Successful Channel Reconfigurations..........................................................................................1200
1.12.12.2 Number of Successful HSDPA MAC-d Flow Establishments for Cell.........................................................1202
1.12.12.3 Number of HSDPA UEs in a Cell..................................................................................................................1204
1.12.12.4 Number of MAC-d Flows in a Cell................................................................................................................1207
1.12.12.5 Mean Downlink Throughput of single HSDPA MAC-d Flows.....................................................................1208
1.12.12.6 Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow.............................................................1212
1.12.12.7 Number of Handover Attempts Between Channels of Different Types.........................................................1213
1.12.12.8 Number of HSDPA Serving Cell Change Attempts for Cell.........................................................................1215
1.12.12.9 Number of Successful HSDPA Serving Cell Changes for Cell.....................................................................1217
1.12.12.10 Number of Inter-RNC HSDPA Hard Handover Attempts Without Channel Change for Cell....................1219
1.12.12.11 Number of Successful Inter-RNC HSDPA Hard Handovers Without Channel Change for Cell................1222
1.12.12.12 Number of Successful Inter-Frequency HSDPA Hard Handovers Without Channel Change for Cell........1223
1.12.12.13 Number of HSDPA RAB Establishment Attempts for Cell.........................................................................1225
1.12.12.14 Number of Successful HSDPA RAB Establishments for Cell.....................................................................1229
1.12.12.15 Number of HSDPA RABs Abnormal Released for Cell..............................................................................1232
1.12.12.16 Number of HSDPA RABs Normal Released for Cell..................................................................................1237
1.12.12.17 Number of Inter-RNC HSDPA Hard Handover Attempts for Cell(HSDPA to DCH)................................1241
1.12.12.18 Number of Successful inter-RNC HSDPA Hard Handovers for Cell(HSDPA to DCH).............................1243
1.12.12.19 Number of HSDPA UEs with Various Categories in a Cell........................................................................1245
1.12.12.20 Number of HSDPA MAC-d Flow Establishment Requests for Cell............................................................1251
1.12.12.21 Number of Failed HSDPA Service Establishments Due to Insufficiency of Different Resources..............1253
1.12.12.22 Number of MIMO UEs in a Cell..................................................................................................................1254
1.12.12.23 Number of Outgoing DRD Attempts for HSDPA Users Through Intelligent User Recognition for Cell
........................................................................................................................................................................................1256
1.12.12.24 Number of Successful Outgoing DRDs for HSDPA Users Through Intelligent User Recognition for Cell
........................................................................................................................................................................................1258
1.12.12.25 Number of RABs Abnormally Released for PS HSDPA Services during the State Transition from CELL_DCH
to CELL_PCH or URA_PCH for Cell...........................................................................................................................1260
1.12.12.26 Average Throughput on HSDPA MAC-d Flow for Cell (Excluding the Data of Low-Traffic Users)........1265
1.12.12.27 Number of Bytes Sent on HSDPA MAC-d Flow for Cell (Excluding the Bytes of Low-Traffic Users)
........................................................................................................................................................................................1266
1.12.12.28 Number of Normal RAB Releases of HSDPA UEs for Cell (All Scenarios)..............................................1267
1.12.12.29 Number of Abnormal Released RABs for Cell When DB-HSDPA with MIMO Applied (RF Exceptions
Considered).....................................................................................................................................................................1272
1.12.13 HSUPA Measurement per cell(HSUPA.Cell)...................................................................................................1275
1.12.13.1 Average Number of HSUPA UEs in a Cell....................................................................................................1290
1.12.13.2 Number of Successful EDCH MAC-d Flow Establishments for Cell............................................................1291
1.12.13.3 Number of HSUPA RAB Establishment Attempts for Cell...........................................................................1293
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxiv

BSC6900 UMTS
1.12.13.4 Number of Successful HSUPA RAB Establishments for Cell.......................................................................1294

1.12.13.5 Number of HSUPA RAB establish attempts of BE Service for different prior Level Users (Cell)...............1295
1.12.13.6 Number of Successful HSUPA RAB Establishments of BE Service for different prior Level Users (Cell)
........................................................................................................................................................................................1297
1.12.13.7 Number of HSUPA RABs Abnormal Released for Cell................................................................................1299
1.12.13.8 Number of HSUPA RABs Normal Released for Cell....................................................................................1302
1.12.13.9 Number of HSUPA RAB Released due to UE Signaling Connection failure for Cell..................................1304
1.12.13.10 Number of EDCH RL Addition and Deletion Attempts by Soft Handover for Cell....................................1305
1.12.13.11 Number of Successful EDCH RL Additions and Deletions by Soft Handover for Cell..............................1306
1.12.13.12 Number of Successful HSUPA Serving Cell Changes in Soft Handover Status for Cell............................1308
1.12.13.13 Number of HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell................................1310
1.12.13.14 Number of inter-RNC HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell..............1312
1.12.13.15 Number of Successful inter-RNC HSUPA Serving Cell Changes in Soft Handover Status for Cell..........1315
1.12.13.16 Number of Successful HSUPA Serving Cell Changes Due to inter-RNC Hard Handover without Channel
Change for Cell...............................................................................................................................................................1317
1.12.13.17 Number of HSUPA Serving Cell Change Attempts Due to inter-RNC Hard Handover without Channel Change
for Cell............................................................................................................................................................................1319
1.12.13.18 Number of Successful HSUPA Serving Cell Changes Due to Intra-Frequency Hard Handover without Channel
Change for Cell...............................................................................................................................................................1321
1.12.13.19 Number of HSUPA Serving Cell Change Attempts Due to Intra-Frequency Hard Handover without Channel
Change for Cell...............................................................................................................................................................1323
1.12.13.20 Number of HSUPA Serving Cell Change Attempts Due to Inter-Frequency Hard Handover without Channel
Change for Cell...............................................................................................................................................................1325
1.12.13.21 Number of Successful HSUPA Intra-Frequency Hard Handovers for Cell(EDCH to DCH)......................1326
1.12.13.22 Number of HSUPA Hard Handover Attempts for Cell(EDCH to DCH).....................................................1328
1.12.13.23 Number of Channel Conversion Attempts According to Different Channel Switch Type for Cell.............1329
1.12.13.24 Number of Successful Handovers Between Different Channel Types for Cell...........................................1331
1.12.13.25 Mean Uplink Throughput of single HSUPA MAC-d Flow.........................................................................1332
1.12.13.26 Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow........................................................1334
1.12.13.27 Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Golden Subscriber........................1334
1.12.13.28 Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service for Golden Subscriber
........................................................................................................................................................................................1336
1.12.13.29 Number of inter-RNC HSUPA Hard Handover Attempts for Cell(EDCH to DCH)...................................1338
1.12.13.30 Number of Successful inter-RNC HSUPA Hard Handovers for Cell(EDCH to DCH)...............................1339
1.12.13.31 Number of Successful HSUPA 16QAM RAB Establishments for cell.......................................................1341
1.12.13.32 Number of HSUPA 16QAM RABs Abnormal Released for cell................................................................1342
1.12.13.33 Number of HSUPA 16QAM RABs Normal Released for cell....................................................................1345
1.12.13.34 Number of HSUPA 16QAM RAB Setup Attempts for cell.........................................................................1347
1.12.13.35 Number of HSUPA RABs Abnormal Released due to RF Failures for Cell...............................................1349
1.12.13.36 Number of HSUPA UEs with Various Categories in a Cell........................................................................1352
1.12.13.37 Number of EDCH MAC-d Flow Setup Requests for Cell...........................................................................1355
1.12.13.38 Number of Failed HSUPA Service Establishments Due to Insufficiency of Different Resources..............1357
1.12.13.39 Average uplink throughput of the Traffic PS Conversational beared on E-DCH for cell............................1359
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxv

BSC6900 UMTS
1.12.13.40 Number of uplink bytes of Transport Blocks of Traffic PS Conversational beared on E-DCH for cell
........................................................................................................................................................................................1360
1.12.13.41 Counters Related to the Number of Transfers Between Small Retransmission and Large Retransmission for
HSUPA 2ms TTI Users or HSUPA 10ms TTI Users.....................................................................................................1361
1.12.13.42 Number of TTI Switch Attempts During RB Reconfiguration for Cell.......................................................1363
1.12.13.43 Number of Successful TTI Switches During RB Reconfiguration for Cell.................................................1365
1.12.13.44 Number of HSUPA 16QAM UEs in a Cell..................................................................................................1367
1.12.13.45 Number of HSUPA Boosting UEs in a Cell.................................................................................................1368
1.12.13.46 Number of UEs Supporting E-DPCCH Boosting and CPC for Cell............................................................1369
1.12.13.47 Number of RABs Abnormally Released for PS HSUPA Services during the State Transition from CELL_DCH
to CELL_PCH or URA_PCH for Cell...........................................................................................................................1370
1.12.13.48 Number of HSUPA Boosting RAB Setup Attempts for Cell.......................................................................1373
1.12.13.49 Number of Successful HSUPA Boosting RAB Setups for Cell...................................................................1375
1.12.13.50 Number of Abnormally Released HSUPA Boosting RABs for Cell...........................................................1376
1.12.13.51 Number of Normally Released HSUPA Boosting RABs for Cell...............................................................1379
1.12.13.52 Number of HARQ PO Reconfiguration Attempts of HSUPA Users with 10 ms TTI for Cell....................1381
1.12.13.53 Number of Successful HARQ PO Reconfigurations of HSUPA Users with 10 ms TTI for Cell................1383
1.12.13.54 Number of DC-HSUPA RAB Setup Attempts for Cell...............................................................................1384
1.12.13.55 Number of Successful DC-HSUPA RAB Setups for Cell...........................................................................1386
1.12.13.56 Number of DC-HSUPA RABs Normally Released for Cell........................................................................1387
1.12.13.57 Number of DC-HSUPA RABs Abnormally Released for Cell....................................................................1389
1.12.13.58 Mean Number of DC-HSUPA Users in the Cell with the Primary Carrier..................................................1392
1.12.13.59 Number of HSUPA 2 ms TTI UEs in a Cell................................................................................................1394
1.12.13.60 Number of HSUPA 10 ms TTI UEs in a Cell..............................................................................................1395
1.12.13.61 Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a 10 ms TTI in a Cell with
Various Causes...............................................................................................................................................................1396
1.12.13.62 Number of Abnormal RAB Releases for Cell During State Transition of HSUPA UEs to CELL/URA_PCH
........................................................................................................................................................................................1398
1.12.13.63 Number of Normal RAB Releases of HSUPA UEs for Cell (All Scenarios)..............................................1401
1.12.14 InterRAT Handover Measurement per cell(INTRAT.HO.Cell)........................................................................1404
1.12.14.1 Number of Preparations for CS or Enhanced PS Outgoing Inter-RAT Handover for Cell............................1430
1.12.14.2 Number of Outgoing Inter-RAT PS Handover Preparation Attempts Triggered by SRVCC for VoIP Services
for Cell............................................................................................................................................................................1433
1.12.14.3 Number of Successful Preparations for CS or Enhanced PS Outgoing Inter-RAT Handover for Cell..........1434
1.12.14.4 Number of Successful Outgoing Inter-RAT PS Handover Preparations Triggered by SRVCC for VoIP Services
for Cell............................................................................................................................................................................1437
1.12.14.5 Number of CS or Enhanced PS Outgoing Inter-RAT Handover Attempts for Cell.......................................1438
1.12.14.6 Number of Successful CS or Enhanced PS Outgoing Inter-RAT Handovers for Cell...................................1441
1.12.14.7 Number of Successful Outgoing Inter-RAT PS Handovers Triggered by SRVCC for VoIP Services for Cell
........................................................................................................................................................................................1444
1.12.14.8 Number of Failed Preparations for CS or Enhanced PS Outgoing Inter-RAT Handover for Different Causes for
Cell..................................................................................................................................................................................1446
1.12.14.9 Number of Failed CS Outgoing Inter-RAT Handover Preparations (Relocation Command Wait Timeout) for
Cell..................................................................................................................................................................................1451
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxvi

BSC6900 UMTS
1.12.14.10 Number of CS Incoming Inter-RAT Handover Preparation Failures (Iu RELEASE COMMAND Received) for
Cell..................................................................................................................................................................................1453
1.12.14.11 Number of CS Outgoing Inter-RAT Handover Preparation Failures (Iu RELEASE COMMAND Received) for
Cell..................................................................................................................................................................................1454
1.12.14.12 Number of Failed CS or Enhanced PS Outgoing Inter-RAT Handovers for Different Causes for Cell
........................................................................................................................................................................................1455
1.12.14.13 Number of Failed CS Outgoing Inter-RAT Handovers for Cell(Signalling Connection Release Indication)
........................................................................................................................................................................................1458
1.12.14.14 Number of RL Reestablishment Attempts After UEs Failed to Receive the CS Outgoing Inter-RAT Handover
Command for Cell..........................................................................................................................................................1459
1.12.14.15 Number of Times that the Timer Waiting for Iu Release Command Expires in CS or Enhanced PS Outgoing
Inter-RAT Handover for Cell.........................................................................................................................................1461
1.12.14.16 Number of Failed CS Outgoing Inter-RAT Handovers for Cell(Failure in the Radio Interface Procedure)
........................................................................................................................................................................................1463
1.12.14.17 Number of Abnormally Terminated CS Outgoing Inter-RAT Handovers for Cell......................................1464
1.12.14.18 Number of Attempts to Obtain GSM System Information During RIM-based NACCs Triggered by Inter-RAT
PS Handovers.................................................................................................................................................................1466
1.12.14.19 Number of Successful That GSM System Information Is Obtained During RIM-based NACCs Triggered by
Inter-RAT PS Handovers................................................................................................................................................1467
1.12.14.20 Number of Attempts to Obtain GSM System Information During Iur-g-based ENACCs Triggered by Inter-
RAT PS Handovers........................................................................................................................................................1469
1.12.14.21 Number of Successful Times That GSM System Information Is Obtained During Iur-g-based ENACCs
Triggered by Inter-RAT PS Handovers..........................................................................................................................1470
1.12.14.22 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC for Cell...................................1471
1.12.14.23 Counters Related to the Number of PS Outgoing Inter-RAT Handover Attempts......................................1474
1.12.14.24 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by RNC for Cell...............................1477
1.12.14.25 Counters Related to the Number of Successful PS Outgoing Inter-RAT Handovers..................................1479
1.12.14.26 Number of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC for Different Causes for Cell
........................................................................................................................................................................................1482
1.12.14.27 Number of Failed PS Outgoing Inter-RAT Handovers for Cell(Signalling Connection Release Indication)
........................................................................................................................................................................................1484
1.12.14.28 Number of RL Reestablishment Attempts After UEs Failed to Receive the PS Outgoing Inter-RAT Handover
Command for Cell..........................................................................................................................................................1485
1.12.14.29 Number of Failed Outgoing UMTS-to-GSM PS Handovers due to UE Reselection Back to a UTRAN Cell
........................................................................................................................................................................................1488
1.12.14.30 Number of Failed PS Outgoing Inter-RAT Handovers for Cell(No SRNS DATA Forward cmd)..............1489
1.12.14.31 Number of Times that the Timer Waiting for Iu Release Command Expires in PS Outgoing Inter-RAT Handover
Initiated by RNC for Cell...............................................................................................................................................1491
1.12.14.32 Number of Abnormally Terminated PS Outgoing Inter-RAT Handovers for Cell......................................1492
1.12.14.33 Number of Failed PS Outgoing Inter-RAT Handovers for Cell(Failure in the Radio Interface Procedure)
........................................................................................................................................................................................1494
1.12.14.34 Number of PS Outgoing Inter-RAT Handover Requests Initiated by UE for Cell......................................1495
1.12.14.35 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE for Cell..................................1497
1.12.14.36 Number of Preparations for CS or Enhanced PS Incoming Inter-RAT Handover for Cell.........................1498
1.12.14.37 Number of Attempts at Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell..................1500
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxvii

BSC6900 UMTS
1.12.14.38 Number of Preparation Attempts for Incoming LTE-to-UMTS CS+PS Handovers Triggered by SRVCC for
VoIP Services.................................................................................................................................................................1501
1.12.14.39 Number of Successful Preparations for CS or Enhanced PS Incoming Inter-RAT Handover for Cell
........................................................................................................................................................................................1504
1.12.14.40 Number of Successful Preparations for Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell
........................................................................................................................................................................................1505
1.12.14.41 Number of Successful Preparations for Incoming LTE-to-UMTS CS+PS Handovers Triggered by SRVCC for
VoIP Services.................................................................................................................................................................1506
1.12.14.42 Number of CS Incoming Inter-RAT Handover Attempts for Cell...............................................................1509
1.12.14.43 Number of Incoming LTE-to-UMTS CS+PS Handover Attempts Triggered by SRVCC for VoIP Services
........................................................................................................................................................................................1510
1.12.14.44 Number of Successful CS or Enhanced PS Incoming Inter-RAT Handovers for Cell................................1512
1.12.14.45 Number of Successful Incoming PS LTE-to-UMTS Handovers Triggered by CSFB for Cell...................1514
1.12.14.46 Number of Successful Incoming LTE-to-UMTS CS+PS Handovers Triggered by SRVCC for VoIP Services
........................................................................................................................................................................................1515
1.12.14.47 Number of Failed Preparations for CS or Enhanced PS Incoming Inter-RAT Handover for Different Causes
for Cell............................................................................................................................................................................1517
1.12.14.48 Number of Failed CS or Enhanced PS Inter-RAT Incoming Handovers Due to No Response from UE for Cell
........................................................................................................................................................................................1520
1.12.14.49 Counters Related to the Number of Inter-RAT Measurement Expiry for Cell............................................1522
1.12.15 Measurement Related to the Release of Iu Signaling Connections (Without RAB) (Cell)(IU.Sig.Rel.Cell)
........................................................................................................................................................................................1523
1.12.15.1 Number of Iu CS Signaling Connections (Without RAB) Normally Released for Cell................................1525
1.12.15.2 Number of Iu PS Signaling Connections (Without RAB) Normally Released for Cell.................................1526
1.12.15.3 Number of Iu CS Signaling Connections (Without RAB) Abnormally Released for Cell............................1527
1.12.15.4 Number of Iu PS Signaling Connections (Without RAB) Abnormally Released for Cell.............................1529
1.12.15.5 Number of Iu CS Signaling Connections (Without RAB) Normally Released for Cell (Service Reasons)
........................................................................................................................................................................................1530
1.12.15.6 Number of Iu PS Signaling Connections (Without RAB) Normally Released for Cell (Service Reasons)
........................................................................................................................................................................................1532
1.12.15.7 Number of Iu CS Signaling Connections (Without RAB) Abnormally Released for Cell (Service Reasons)
........................................................................................................................................................................................1533
1.12.15.8 Number of Iu PS Signaling Connections (Without RAB) Abnormally Released for Cell (Service Reasons)
........................................................................................................................................................................................1535
1.12.15.9 Number of Iu CS Signaling Connections (Without RAB) Abnormally Released Due to Security Mode Procedure
Failures for Cell (Service Reasons)................................................................................................................................1536
1.12.15.10 Number of Iu PS Signaling Connections (Without RAB) Abnormally Released Due to Security Mode Procedure
Failures for Cell (Service Reasons)................................................................................................................................1538
1.12.16 Iub Interface Measurement per cell(IUB.Cell)..................................................................................................1540
1.12.16.1 Number of RLs with Synchronized Reconfiguration Cancelled on Iub Interface..........................................1543
1.12.16.2 Number of RL Failures on Iub Interface........................................................................................................1544
1.12.16.3 Number of RLs Unsuccessfully Restored on Iub Interface due to No Response...........................................1547
1.12.16.4 Number of RLs Unsuccessfully Added on Iub Interface for Different Causes..............................................1549
1.12.16.5 Number of RLs Unsuccessfully Synchronization Reconfigured on Iub Interface for Different Causes
........................................................................................................................................................................................1551
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxviii

BSC6900 UMTS
1.12.16.6 Number of RLs Unsuccessfully Reconfigured on Iub Interface due to No Response...................................1554

1.12.16.7 Number of RLs Unsuccessfully Established on Iub Interface for Different Causes......................................1555
1.12.16.8 Number of RLs Requested to Reconfigure with Synchronization on Iub Interface.......................................1558
1.12.16.9 Number of RLs Requested to Add on Iub Interface.......................................................................................1559
1.12.16.10 Number of RLs Requested to Delete on Iub Interface.................................................................................1560
1.12.16.11 Number of RLs Requested to Establish on Iub Interface.............................................................................1562
1.12.16.12 Number of RLs Restored on Iub Interface...................................................................................................1563
1.12.16.13 Number of RLs Successfully Added on Iub Interface..................................................................................1564
1.12.16.14 Number of RLs Successfully Deleted on Iub Interface................................................................................1566
1.12.16.15 Number of RLs Successfully Reconfigured with Synchronization on Iub Interface...................................1568
1.12.16.16 Number of RLs Successfully Established on Iub Interface..........................................................................1569
1.12.16.17 Number of RLs Unsuccessfully Established on Iub Interface due to No Response.....................................1571
1.12.17 Measurement related to LCS service per cell(LCS.CELL)...............................................................................1572
1.12.17.1 Number of Positioning Results Beyond Coverage of UE Reference Cell in UE Assisted AGPS Method
........................................................................................................................................................................................1573
1.12.17.2 Number of Positioning Results Beyond Coverage of UE Reference Cell in UE-based AGPS Method........1574
1.12.17.3 Number of Positioning Results Beyond Coverage of UE Reference Cell in OTDOA Method.....................1575
1.12.17.4 Number of Positioning Results Beyond Coverage of UE Reference Cell in CELLID + RTT method.........1576
1.12.18 MBMS Measurement per cell(MBMS.Cell).....................................................................................................1577
1.12.18.1 Number of Releases of PTP MBMS Services because the new best cell is on PTM mode...........................1580
1.12.18.2 Number of Requests for PTP MBMS Setup...................................................................................................1581
1.12.18.3 Number of Successful PTP MBMS Setups....................................................................................................1582
1.12.18.4 Number of Abnormal Releases of PTP MBMS Services for Different Causes.............................................1582
1.12.18.5 Number of Normal Releases of PTP MBMS Services...................................................................................1583
1.12.18.6 Number of Successful Setups of MBMS(PTM) Traffic Channel..................................................................1584
1.12.18.7 Number of Unsuccessful Setups of MBMS(PTM) Traffic Channel..............................................................1585
1.12.18.8 Number of successful PTM to PTP transition in a cell..................................................................................1586
1.12.18.9 Number of Successful Transitions from PTP MBMS Service to PTM MBMS Service................................1587
1.12.18.10 Number of Transitions from PTP MBMS Service to PTM MBMS Service................................................1589
1.12.18.11 Number of RBs in PTM MBMS Service......................................................................................................1589
1.12.18.12 Number of PTM setup request......................................................................................................................1590
1.12.18.13 Number of Successful Setups of PTM MBMS Service...............................................................................1592
1.12.18.14 Mean number of PTP users in a cell of MBMS Channel.............................................................................1592
1.12.18.15 Mean number of PTM users in a cell of MBMS Channel............................................................................1593
1.12.18.16 A PTM Channel Duration in a cell MBMS service Channel.......................................................................1595
1.12.18.17 A PTP Channel Duration in a cell MBMS service Channel.........................................................................1596
1.12.19 RRC Reporting Measurement per cell(MEAR.Report.Cell).............................................................................1597
1.12.19.1 Number of Event 1A Measurement Reports..................................................................................................1599
1.12.19.2 Number of Event 1B Measurement Reports...................................................................................................1600
1.12.19.3 Number of Event 1C Measurement Reports...................................................................................................1601
1.12.19.4 Number of Event 1D Measurement Reports..................................................................................................1603
1.12.19.5 Number of Event 2D Measurement Reports..................................................................................................1604
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxix

BSC6900 UMTS
1.12.19.6 Number of Event 2F Measurement Reports...................................................................................................1605

1.12.19.7 Number of Uplink Event 4A Measurement Reports......................................................................................1607
1.12.19.8 Number of Uplink Event 4B Measurement Reports......................................................................................1608
1.12.19.9 Number of Downlink Event 4A Measurement Reports.................................................................................1610
1.12.19.10 Number of Downlink Event 4B Measurement Reports................................................................................1611
1.12.19.11 Average RSCP for Cell.................................................................................................................................1612
1.12.19.12 Average Ec/No for Cell................................................................................................................................1613
1.12.20 Measurement related to Paging per cell(PAGE.CELL)....................................................................................1615
1.12.20.1 Number of Paging Losses due to PCH Congestion........................................................................................1618
1.12.20.2 Number of Paging Type 1 Messages..............................................................................................................1619
1.12.20.3 Number of Preemptions by CS Paging due to PCH Congestion per Cell......................................................1620
1.12.20.4 Number of Successful Preemptions by CS Paging due to PCH Congestion per Cell....................................1621
1.12.20.5 Number of Level-1 Paging Attempts for UEs Processing Real-Time or Non-Real-Time Services in the
URA_PCH State.............................................................................................................................................................1622
1.12.20.6 Number of Successful Level-1 Paging Attempts for UEs Processing Real-Time or Non-Real-Time Services in
the URA_PCH State.......................................................................................................................................................1624
1.12.20.7 Number of Successful Layered Paging Attempts for UEs Processing Real-Time or Non-Real-Time Services in
the URA_PCH State.......................................................................................................................................................1625
1.12.20.8 Number of PAGING TYPE 1 Messages Sent by the RNC to UEs in the URA_PCH State..........................1627
1.12.20.9 Number of CS PAGING TYPE 1 Messages Sent by the RNC to UEs in the Idle State................................1628
1.12.20.10 Number of PS PAGING TYPE 1 Messages Sent by the RNC to UEs in the Idle State..............................1629
1.12.20.11 Number of Level-1 Paging Attempts for UEs Performing Real-Time or Non-Real-Time Services in Idle Mode
for Cell............................................................................................................................................................................1631
1.12.20.12 Number of Successful Level-1 Paging Attempts for UEs Performing Real-Time or Non-Real-Time Services
in Idle Mode for Cell......................................................................................................................................................1632
1.12.20.13 Number of Times a UE Processing SMS services Attempts to Preempt Resources to Be Allocated to Other UEs
When the PCH Is Congested for Cell.............................................................................................................................1634
1.12.20.14 Number of Successful Preemptions by SMS Paging due to PCH Congestion per Cell...............................1635
1.12.20.15 Number of ETWS-related PAGING TYPE 1 Messages Sent in a Cell.......................................................1636
1.12.21 Measurement by Operator for Cell(PLMN.CELL)...........................................................................................1637
1.12.21.1 Credit Consumption of Operator0..................................................................................................................1641
1.12.21.5 Equivalent Erlangs Consumed by CS Services of Operator0.........................................................................1644
1.12.21.9 Number of Spreading Codes Occupied by Operator0....................................................................................1647
1.12.21.10 Number of Spreading Codes Occupied by Operator1..................................................................................1648
1.12.21.13 Number of Spreading Codes Occupied by Shared Operator for MOCN Cell..............................................1651
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxx

BSC6900 UMTS
1.12.22 Measurements related to PTT(PTT.Cell)..........................................................................................................1653

1.12.22.1 Number of Successful PTT Call Initiation Attempts or Responses During a P2D Procedure for UEs Processing
PTT Services...................................................................................................................................................................1657
1.12.22.2 Number of PTT Call Initiation or Response Attempts of UEs Using Only the PTT Service in the CELL_FACH
State for Cell...................................................................................................................................................................1660
1.12.22.3 Number of Successful PTT Call Initiation Attempts or Responses of UEs Using Only the PTT Service in the
CELL_FACH State for Cell...........................................................................................................................................1662
1.12.22.4 Number of Successful PTT Call Initiation Attempts or Responses of UEs Using the PTT and Other Services in
the CELL_FACH State for Cell.....................................................................................................................................1663
1.12.22.5 Number of Complete PTT Calls for Cell........................................................................................................1665
1.12.22.6 Number of RABs Abnormally Released During PTT Calls for Cell.............................................................1666
1.12.22.7 Number of Successful State Transitions from CELL_PCH/URA_PCH to CELL_DCH After the RNC Sends the
CELL UPDATE CONFIRM Message for Cell..............................................................................................................1669
1.12.22.8 Number of Successful PTT Paging Attempts After the RNC Sends the PAGING TYPE 1 Message for Cell
........................................................................................................................................................................................1673
1.12.22.9 Number of PTT Call Initiation or Response Attempts of UEs Using the PTT and Other Services in the
CELL_FACH State for Cell...........................................................................................................................................1675
1.12.22.10 Number of Failed PTT Call Initiations or Responses Due to Resource Congestion During a P2D Procedure for
UEs Processing PTT Services........................................................................................................................................1677
1.12.22.11 Number of Failed PTT Call Initiation Attempts or Responses of a UE in the CELL_FACH State Processing
Only the PTT Service Due to Congestion for Cell.........................................................................................................1679
1.12.22.12 Number of Failed PTT Call Initiation Attempts or Responses of a UE in the CELL_FACH State Processing
Multiple Services Due to Congestion for Cell................................................................................................................1680
1.12.22.13 Number of PTT Call Initiation Attempts or Responses During a P2D Procedure for UEs Processing PTT
Services...........................................................................................................................................................................1681
1.12.22.14 Uplink Traffic Volume of the PTT Service..................................................................................................1684
1.12.22.15 Downlink Traffic Volume of the PTT Service.............................................................................................1685
1.12.22.16 Number of Successful Serving Cell Changes of PTT Service in Soft Handover Status..............................1686
1.12.22.17 Number of Serving Cell Change Attempts of PTT Service in Soft Handover Status..................................1689
1.12.22.18 Number of Successful Hard Handovers of PTT Service..............................................................................1693
1.12.22.19 Number of Hard Handover Attempts of PTT Service..................................................................................1696
1.12.23 Measurement related to QOS per cell(QOS.Cell).............................................................................................1699
1.12.23.1 Delay of Different Services............................................................................................................................1718
1.12.23.2 Counters Related to the Number of Times that DL Throughput of HSDPA Services Within Each Range
........................................................................................................................................................................................1724
1.12.23.3 Counters Related to the Number of Times that UL Throughput of HSUPA Services Within Each Range
........................................................................................................................................................................................1733
1.12.23.4 Service Setup Duration on an ERACH or EFACH for Cell...........................................................................1740
1.12.24 Measurement of CS RAB assignment setup per cell(RAB.EstabCS.Cell).......................................................1743
1.12.24.1 Number of CS RAB Setup Requests for Different Services..........................................................................1754
1.12.24.2 Number of RAB Setup Attempts for VP Services when VP Call Is Limited................................................1758
1.12.24.3 Number of CS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH
to CELL_FACH for Cell................................................................................................................................................1760
1.12.24.4 Number of Successful CS Service Setups Initiated by UEs During State Transition from CELL_PCH or
URA_PCH to CELL_FACH for Cell.............................................................................................................................1762
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxxi

BSC6900 UMTS
1.12.24.5 Number of Successful CS RAB Establishments in the Cell for Different Services.......................................1764
1.12.24.6 Number of Queuing Attempts Due to Insufficient Resource in the CS RAB Assignment Establishment Procedure
........................................................................................................................................................................................1769
1.12.24.7 Number of CS Over HSPA in a Cell..............................................................................................................1770
1.12.24.8 Average Duration of a CS Queuing in the RAB Establishment Procedure....................................................1771
1.12.24.9 Number of Successful CS Establishment After Queuing...............................................................................1772
1.12.24.10 Number of CS RAB Setup Requests Initiated by Redirection-based CSFB for Cell...................................1773
1.12.24.11 Number of Successful CS RAB Setups Initiated by Redirection-based CSFB for Cell..............................1775
1.12.24.12 Number of CS RAB Setup Requests Initiated by PS-Handover-based CSFB for Cell................................1777
1.12.24.13 Number of Successful CS RAB Setups Initiated by PS-Handover-based CSFB for Cell...........................1779
1.12.25 Measurement of PS RAB assignment setup per cell(RAB.EstabPS.Cell)........................................................1782
1.12.25.1 Number of PS RAB Setup Requests for Different Services...........................................................................1788
1.12.25.2 Number of PS RABs Successfully Set Up in a Cell for Different Services...................................................1790
1.12.25.3 Number of PS RABs Set Up Successfully at 0 Kbit/s....................................................................................1793
1.12.25.4 Number of Queuing Attempts Due to Insufficient Resource in the PS RAB Assignment Establishment Procedure
........................................................................................................................................................................................1796
1.12.25.5 Average Duration of a PS Queuing in the RAB Establishment Procedure....................................................1797
1.12.25.6 Number of Successful PS Establishment After Queuing...............................................................................1799
1.12.25.7 Number of PS Service Setup Attempts Initiated by UEs During State Transition from CELL_PCH or URA_PCH
to CELL_FACH for Cell................................................................................................................................................1800
1.12.25.8 Number of Successful PS Service Setups Initiated by UEs During State Transition from CELL_PCH or
URA_PCH to CELL_FACH for Cell.............................................................................................................................1803
1.12.26 Measurement of CS RAB assignment failure per cell(RAB.EstFailCs.Cell)....................................................1806
1.12.26.1 Number of CS RABs Unsuccessfully Established due to Congestion...........................................................1811
1.12.26.2 Number of Failed CS RABs due to Unsupported Capabilities (Cell)............................................................1814
1.12.26.3 Number of CS RABs Unsuccessfully Established due to Transport Network Layer Cause..........................1816
1.12.26.4 Number of Failed CS RAB Establishments Due to Radio Link Configuration Failure.................................1817
1.12.26.5 Number of CS RABs Unsuccessfully Established due to Different Reasons of UE During the RB Setup Procedure
for Cell............................................................................................................................................................................1820
1.12.26.6 Number of Failed RAB Establishments for Cell (Signaling RLC Reset)......................................................1824
1.12.26.7 Number of Failed CS RAB Establishments for Cell (Concurrent Procedures)..............................................1825
1.12.26.8 Number of Failed CS RABs due to Radio Network Layer Cause..................................................................1827
1.12.27 Measurement of PS RAB assignment failure per cell(RAB.EstFailPs.Cell)....................................................1828
1.12.27.1 Number of PS RABs Unsuccessfully Established due to Congestion............................................................1834
1.12.27.2 Number of Failed PS RABs due to Unsupported Capabilities (Cell).............................................................1837
1.12.27.3 Number of PS Free RAB Setup Failures due to DL Power Resource Congestion for Cell...........................1839
1.12.27.4 Number of PS RABs Unsuccessfully Established due to Transport Network Layer Cause..........................1840
1.12.27.5 Number of Failed PS RAB Establishments Due to Radio Link Configuration Failure.................................1842
1.12.27.6 Number of Failed PS RABs due to different reasons of UE During the RB Setup Procedure for cell..........1845
1.12.27.7 Number of Failed PS RAB Establishments for Cell (Signaling RLC Reset).................................................1848
1.12.27.8 Number of Failed PS RAB Establishments for Cell (Concurrent Procedures)..............................................1849
1.12.27.9 Number of PS RABs Unsuccessfully Established due to Radio Network Layer Cause for Cell...................1851
1.12.28 Measurement of CS RAB assignment modification per cell(RAB.ModCs.Cell).............................................1852
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxxii

BSC6900 UMTS
1.12.28.1 Number of Failed CS RAB Modifications Due to Transport Network Layer Cause.....................................1853
1.12.28.2 Counters Related to the Number of CS RAB Modification Requests............................................................1854
1.12.28.3 Counters Related to the Number of Successful CS RAB Modifications.......................................................1856
1.12.28.4 Number of Failed CS RAB Modifications Due to Radio Network Layer Cause...........................................1857
1.12.29 Measurement of PS RAB assignment modification per cell(RAB.ModPs.Cell)..............................................1859
1.12.29.1 Number of Failed PS RAB Modifications Due to Iu Transport Connection Failure.....................................1861
1.12.29.2 Number of PS RAB Modification Requests...................................................................................................1862
1.12.29.3 Number of Successful PS RAB Modifications...............................................................................................1864
1.12.29.4 Number of Failed PS RAB Modifications Due to Radio Network Fault.......................................................1865
1.12.30 Measurement of multi-RAB service per cell(RAB.MultiRab.Cell)..................................................................1867
1.12.30.1 Mean Number of Single-RAB UEs Occupy the Codes with Different Spreading Factors............................1873
1.12.30.2 Mean Number of Multi-RAB UEs Occupy the Codes with Different Spreading Factors.............................1874
1.12.30.3 Max Count of SF which has been occupied...................................................................................................1876
1.12.30.4 Mean Throughput of a Single HSPA MAC-d Flow in the Case of Multi-RAB Services for Cell.................1877
1.12.30.5 Mean Throughput of a Single PS R99 RB in the Case of Multi-RAB Services for Cell...............................1879
1.12.30.6 Number of CS+PS Combined Service Setup Requests for Cell.....................................................................1880
1.12.30.7 Number of Successful CS+PS Combined Service Setups for Cell................................................................1883
1.12.30.8 Number of Normal Service Releases of Combined Services for Cell............................................................1885
1.12.30.9 Number of Abnormal PS Service Releases of PS+PS Combined Services for Cell......................................1888
1.12.30.10 Number of Abnormal CS Service Releases During PS Service Setup for Cell............................................1892
1.12.30.11 Number of Abnormal CS Service Releases During PS Service Release for Cell........................................1894
1.12.30.12 Number of Normal PS Service Releases of CS+PS Combined Services for Cell........................................1897
1.12.30.13 Number of Abnormal PS Service Releases of CS+PS Combined Services for Cell....................................1900
1.12.30.14 Number of State Transition Attempts from CELL_PCH or URA_PCH to CELL_DCH with the Cause Value
of CS Service for Cell.....................................................................................................................................................1903
1.12.30.15 Number of Successful State Transitions from CELL_PCH or URA_PCH to CELL_DCH with the Cause Value
of CS Service for Cell.....................................................................................................................................................1905
1.12.30.16 Number of Abnormal PS Service Releases in the Case of Multi-RAB Services for Cell during an inter-RAT
handover( PS Resume Timer Expiry).............................................................................................................................1906
1.12.31 Measurement of RAB release per cell(RAB.RelAbnormal.Cell)......................................................................1908
1.12.31.1 Number of CS RABs Abnormally Released for Different Services...............................................................1926
1.12.31.2 Number of CS RABs Abnormally Released Triggered by Different Causes.................................................1930
1.12.31.3 Number of wideband and narrowband AMR services RABs Abnormally Released.....................................1935
1.12.31.4 Number of RABs Abnormally Released Due to Security Mode Procedure Failure......................................1942
1.12.31.5 Number of CS RABs Normally Released for Cell.........................................................................................1944
1.12.31.6 Number of CS RABs Normally Released for Different Services...................................................................1947
1.12.31.7 Number of CS VP RABs Released Due to VP Forbiddance for Cell............................................................1951
1.12.31.8 Number of AMRWB RABs Normally Released for Cell..............................................................................1952
1.12.31.9 Number of CS RABs Normally Released Due to Uplink Signaling Connection Release.............................1957
1.12.31.10 Number of Released RABs due to Network Optimization for Cell.............................................................1958
1.12.31.11 Number of Abnormally Released RABs Triggered by CN for Cell.............................................................1961
1.12.31.12 Number of PS RABs Normally Released for Cell.......................................................................................1963
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxxiii

BSC6900 UMTS
1.12.31.13 Number of PS RABs Normally Released According to Different Services and Different Channel-beared Type
........................................................................................................................................................................................1967
1.12.31.14 Number of PS RABs Normally Released due to UE Signaling Connection Release..................................1970
1.12.31.15 Number of RAB Releases Triggered by the Second RRC CONNECTION REQUEST Message from the Same
UE...................................................................................................................................................................................1971
1.12.31.16 Times of PS RAB of 0kbit/s released for failed to rate up...........................................................................1974
1.12.31.17 Number of PS RABs Abnormally Released for Different Services Type and Channel-beared Type.........1975
1.12.31.18 Number of PS RABs Abnormally Released Due to Different Causes.........................................................1980
1.12.31.19 Number of Abnormally Released PS RABs that Are in CELL_PCH or URA_PCH State for Cell............1986
1.12.31.20 Number of RABs Abnormally Released for PS Services during the Different State Transition.................1989
1.12.31.21 Number of PS BE RABs Beared on HSPA Released due to Cell Congestion or preemption.....................1994
1.12.32 Measurement of CS RAB release per cell(RAB.RelCs.Cell)............................................................................1997
1.12.32.1 Number of CS RABs Released Due to Different Causes in RAB Assignment for Cell................................1998
1.12.32.2 Number of Abnormally Released CS RABs Triggered by CN......................................................................2000
1.12.32.3 Number of CS RABs Released in RAB Assignment for Cell........................................................................2002
1.12.33 Measurement of PS RAB release per cell(RAB.RelPs.Cell).............................................................................2004
1.12.33.1 Number of PS RABs Released by RAB ASSIGNMENT REQUEST for Different Cause...........................2005
1.12.33.2 Number of PS RAB Releases Triggered by CN.............................................................................................2007
1.12.33.3 Number of PS RAB Release Attempts by RAB ASSIGNMENT REQUEST...............................................2009
1.12.34 Measurement of RB Procedure per cell(RB.Cell).............................................................................................2011
1.12.34.1 Number of RB Setup Attempts.......................................................................................................................2031
1.12.34.2 Number of Successful RB Setups...................................................................................................................2032
1.12.34.3 Counters Related to the Number of Failed RB Setups for Different Causes..................................................2033
1.12.34.4 Number of RB Reconfiguration Attempts......................................................................................................2036
1.12.34.5 Number of Successful RB Reconfigurations..................................................................................................2037
1.12.34.6 Counters Related to the Number of Failed RB Reconfigurations for Different Causes.................................2039
1.12.34.7 Number of AMR Users with Different UL and DL Rates for Cell................................................................2042
1.12.34.8 Average Number of CS Conversational or Streaming Service RBs for Cell.................................................2048
1.12.34.9 Number of RBs for PS R99 Services with various Uplink and Downlink Rates for Cell..............................2050
1.12.34.10 Number of RB Setup Attempts for Outgoing Inter-Frequency Directed Retry............................................2058
1.12.34.11 Number of Successful RB Setup for Outgoing Inter-Frequency Directed Retry.........................................2059
1.12.34.12 Number of RB Setup Attempts for Incoming Inter-Frequency Directed Retry...........................................2060
1.12.34.13 Number of Successful RB Setup for Incoming Inter-Frequency Directed Retry.........................................2061
1.12.34.14 Number of RB Reconfiguration Attempts for Outgoing Inter-Frequency Directed Retry...........................2063
1.12.34.15 Number of Successful RB Reconfiguration for Outgoing Inter-Frequency Directed Retry........................2064
1.12.34.16 Number of RB Reconfiguration Attempts for Incoming Inter-Frequency Directed Retry..........................2065
1.12.34.17 Number of Successful RB Reconfiguration for Incoming Inter-Frequency Directed Retry........................2067
1.12.34.18 Number of Outgoing or Incoming DCH-to-HSDPA or DCH-to-HSUPA Directed Retry Attempts...........2068
1.12.34.19 Number of Successful Outgoing or Incoming DCH-to-HSDPA or DCH-to-HSUPA Directed Retry for Cell
........................................................................................................................................................................................2071
1.12.34.20 Number of Successful Directed Retry Attempts Based on Inter-Frequency Measurement for Cell............2073
1.12.34.21 Number of Directed Retry Attempts Based on Inter-Frequency Measurement for Cell..............................2074
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxxiv

BSC6900 UMTS
1.12.34.22 Number of Times that PS Rate Downgrades to 0 Kbit/s..............................................................................2076

1.12.34.23 Average Number of PS Conversation RBs on EDCH or HS-DSCH for Cell..............................................2077
1.12.34.24 Number of Outgoing DRD Attempts through Physical Channel Reconfiguration(Cell).............................2078
1.12.34.25 Number of Successful Outgoing DRDs through Physical Channel Reconfiguration(Cell).........................2079
1.12.34.26 Number of Incoming DRD Attempts through Physical Channel Reconfiguration (Cell)............................2081
1.12.34.27 Number of Successful Incoming DRDs through Physical Channel Reconfiguration (Cell)........................2082
1.12.34.28 Number of RB Setup Attempts After the RB Setup DRD Rollback............................................................2084
1.12.34.29 Number of successful RB Setups After the RB Setup DRD Rollback.........................................................2085
1.12.34.30 Number of RB Reconfiguration Attempts After the RB Reconfiguration DRD Rollback..........................2087
1.12.34.31 Number of Successful RB Reconfigurations After the RB Reconfiguration DRD Rollback......................2088
1.12.34.32 Number of Physical Channel Reconfiguration Attempts After the Physical Channel Reconfiguration DRD
Rollback..........................................................................................................................................................................2090
1.12.34.33 Number of Successful Physical Channel Reconfigurations After the Physical Channel Reconfiguration DRD
Rollback..........................................................................................................................................................................2091
1.12.34.34 Number of Outgoing or Incoming FACH-to-HSDPA or FACH-HSUPA Directed Retry Attempts for Cell
........................................................................................................................................................................................2093
1.12.34.35 Number of Successful Outgoing or Incoming FACH-to-HSDPA or FACH-HSUPA Directed Retry Attempts
for Cell............................................................................................................................................................................2095
1.12.34.36 Number of CELL_FACH to CELL_PCH Transition Attempts by Physical Channel Reconfiguration for Cell
........................................................................................................................................................................................2097
1.12.34.37 Number of SuccessfulCELL_FACH to CELL_PCH Transitions by Physical Channel Reconfiguration for Cell
........................................................................................................................................................................................2098
1.12.34.38 Number of Outgoing or Incoming Inter-Frequency DRD Attempts Triggered by Multiband Directed Retry
Based on UE Location for Cell.......................................................................................................................................2100
1.12.34.39 Number of Successful Incoming Inter-Frequency DRDs Triggered by Multiband Directed Retry Based on UE
Location for a Cell..........................................................................................................................................................2102
1.12.34.40 Number of Periodic Inter-Frequency Ingoing Directed Retry Attempts based on Measurement for Cell
........................................................................................................................................................................................2104
1.12.34.41 Number of Successful Periodic Inter-Frequency Ingoing Directed Retry Attempts based on Measurement for
Cell..................................................................................................................................................................................2107
1.12.35 Reserved counter for cell(RESERVE.Cell).......................................................................................................2109
1.12.35.1 Reserved counters for cell..............................................................................................................................2111
1.12.36 Measurement related to RLC per cell(RLC.Cell)..............................................................................................2113
1.12.36.1 Number of Downlink Service PDUs Retransmitted on AM RLC (L2 Enhancement)...................................2115
1.12.36.2 Number of Downlink Service PDUs Sent on AM RLC.................................................................................2116
1.12.36.3 Number of Downlink Signaling PDUs Sent on AM RLC..............................................................................2117
1.12.36.4 Number of Downlink Service PDUs Retransmitted on AM RLC..................................................................2118
1.12.36.5 Number of Downlink Signaling PDUs Retransmitted on AM RLC..............................................................2119
1.12.36.6 Number of Downlink Service PDUs Discarded on AM RLC........................................................................2120
1.12.36.7 Number of Downlink Signaling PDUs Discarded on AM RLC....................................................................2121
1.12.37 RRC connection release measurement per cell(RRC.Rel.Cell).........................................................................2122
1.12.37.1 Counters Related to the Number of RRC Connection Releases on DCCH due to Different Causes.............2125
1.12.37.2 Counters Related to the Number of RRC Connection Releases on CCCH due to Different Causes.............2127
1.12.37.3 Number of RRC Connection Releases due to Cell Update Failure in the Case of RL Failure......................2130
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxxv

BSC6900 UMTS
1.12.37.4 Number of RRCs Released due to PS Data session end.................................................................................2132

1.12.38 RRC connection setup measurement per cell(RRC.Setup.Cell)........................................................................2133
1.12.38.1 Number of Received RRC CONNECTION REQUESTS for CS Services in a Cell.....................................2162
1.12.38.2 Counters Related to the Number of RRC Connection Requests for Various Reasons...................................2163
1.12.38.3 Counters Related to the Number of Processed RRC Connection Requests...................................................2169
1.12.38.4 Number of RRC Connection Requests sent by the UE for cell......................................................................2171
1.12.38.5 Number of Retransmitted RRC Connection Setup Requests for Cell............................................................2172
1.12.38.6 Number of RRC Connection Setup Requests for Cell (PS Domain).............................................................2178
1.12.38.7 Number of RRC Connection Setup Requests for Cell (CS Domain).............................................................2180
1.12.38.8 Number of RRC Connection Setup Requests that carried System Information Container Stored Indication for
CS services.....................................................................................................................................................................2181
1.12.38.9 Number of RRC Connection Setup Requests that carried System Information Container Stored Indication for
PS services......................................................................................................................................................................2183
1.12.38.10 Number of RRC Connection Setup Requests for Platinum UEs Performing Conversational Services for Cell
........................................................................................................................................................................................2184
1.12.38.11 Number of RRC Connection Setup Requests for Platinum UEs Performing Services for Cell...................2185
1.12.38.12 The average Ec/N0 at each propagation delay range in a cell......................................................................2186
1.12.38.13 Number of RRC Connection Establishment Requests that propagation delay falls into different value ranges
in a cell............................................................................................................................................................................2191
1.12.38.14 Number of RRC Connection Setup Messages Sent from RNC to UE.........................................................2194
1.12.38.15 Counters Related to the Number of Successful RRC Connection Setups....................................................2196
1.12.38.16 Number of Successful RRC Connection Setups with DRD Out..................................................................2198
1.12.38.17 Number of RRC Connection Setup Attempts with DRD in.........................................................................2199
1.12.38.18 Counters Related to Duration of RRC Connection Setup on CELL_DCH..................................................2201
1.12.38.19 Counters Related to the Number of Successful RRC Connection Setups for Various Reasons..................2203
1.12.38.20 Number of Successful RRC Connection Setups with Repeated RRC Connection Request Messages from UE
........................................................................................................................................................................................2209
1.12.38.21 Duration of RRC Establishment Process on FACH for Cell........................................................................2212
1.12.38.22 Number of Successful RRC Connection Setups for CS services (RRC Connection Setup Requests that carried
System Information Container Stored Indication)..........................................................................................................2214
1.12.38.23 Number of Successful RRC Connection Setups for PS services (RRC Connection Setup Requests that carried
System Information Container Stored Indication)..........................................................................................................2215
1.12.38.24 Number of Successful RRC Connection Setups for Platinum UEs Performing Conversational Services for Cell
........................................................................................................................................................................................2217
1.12.38.25 Number of Successful RRC Connection Setups for Platinum UEs for Cell................................................2218
1.12.38.26 Number of RRC Connection Setup Attempts with DRD out.......................................................................2219
1.12.38.27 Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow Control for Cell
........................................................................................................................................................................................2220
1.12.38.28 Number of RRC CONNECTION REQUESTS in a Cell Under Cell Dynamic CAPS Flow Control.........2222
1.12.38.29 Number of RRC CONNECTION REQUESTS for CS Services in a Cell Under Cell Dynamic CAPS Flow
Control............................................................................................................................................................................2223
1.12.38.30 Number of Rejected RRC Connection Setup Requests for CS Voice Services During Flow Control Caused by
Interface-Board CPU Overload for Cell.........................................................................................................................2224
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxxvi

BSC6900 UMTS
1.12.38.31 Number of Rejected RRC Connection Setup Requests During Flow Control Caused by Interface-Board CPU
Overload for Cell............................................................................................................................................................2225
1.12.38.32 Number of Rejected RRC Connection Setup Requests During Flow Control Caused by FACH Congestion for
Cell..................................................................................................................................................................................2226
1.12.38.33 Number of Rejected RRC Connection Setup Requests for CS Voice Services During E2E Flow Control Phase
1 for Cell.........................................................................................................................................................................2227
1.12.38.34 Number of Rejected RRC Connection Setup Requests During E2E Flow Control Phase 1 for Cell..........2228
1.12.38.35 Number of Automatic DSACs Triggered by Congestion on Iu Interface....................................................2229
1.12.38.36 Number of PTT UEs with RRC Connection State of CELL_FACH...........................................................2230
1.12.38.37 Number of PTT UEs with RRC Connection State of CELL_DCH.............................................................2231
1.12.38.38 Number of PTT UEs in CELL_PCH State...................................................................................................2231
1.12.38.39 Number of RRC CONNECTION REQUESTS Under Flow Control for Cell.............................................2232
1.12.38.40 Number of Cell Updates Under Flow Control Triggered by High CPU Usage for Cell..............................2234
1.12.38.41 Number of RRC Connection Setup Requests for CSFB for Cell.................................................................2235
1.12.38.42 Number of Successful RRC Connection Setups for CSFB for Cell.............................................................2236
1.12.39 RRC connection reject measurement per cell(RRC.SetupFail.Cell).................................................................2237
1.12.39.1 Number of RRC Connection Rejects Due to Timeout of RRC CONNECT SETUP COMPLETE...............2243
1.12.39.2 Number of Discarded RRC Connection Requests Due to Various Flow Control Functions.........................2244
1.12.39.3 Number of RRC Connection Requests of Different Priorities Discarded During RAN Integrated Flow Control
for Cell............................................................................................................................................................................2245
1.12.39.4 Number of RRC Connection Rejects Due to Service-based RRC Redirection..............................................2247
1.12.39.5 Number of Distance-Based RRC Redirections for Cell.................................................................................2248
1.12.39.6 Number of Outgoing Macro & Micro Joint Inter-frequency Redirections.....................................................2250
1.12.39.7 Number of RRC Connection Rejects Due to Congestion...............................................................................2252
1.12.39.8 Number of RRC Connection Rejects (Radio Resource Congestion).............................................................2253
1.12.39.9 Number of RRC Connection Rejects Due to Radio Link Setup Failure........................................................2256
1.12.39.10 Number of RRC Connection Rejects Due to NodeB Resource Unavailable...............................................2258
1.12.39.11 Number of RRC Connection Rejects (Transmission Setup Failure on Iub Interface )................................2259
1.12.39.12 Number of RRC Connection Rejects during redirection between inter-RAT cells......................................2260
1.12.39.13 Number of RRC Connection Rejects (RRC Redirection Triggered by Access Failure)..............................2262
1.12.39.14 Number of RRC Connection Rejects............................................................................................................2263
1.12.40 RRC state measurement<Cell>(RRC.State.Cell)..............................................................................................2265
1.12.40.1 Counters Related to the Number of UEs in Different RRC Connection States..............................................2265
1.12.41 UE Capability Measurement per cell(RRC.UECapab.Cell)..............................................................................2267
1.12.41.1 Number of Successful RRC Connection Setups (Including All the HS-DSCH Physical Layer Categories)
........................................................................................................................................................................................2271
1.12.41.2 Number of Successful RRC Connection Setups for Cell (Including All the E-DCH Physical Layer Categories)
........................................................................................................................................................................................2274
1.12.42 Cell TX and RX Power Measurement per cell(RTWPTCP.Cell).....................................................................2277
1.12.42.1 Received Total Wideband Power for cell.......................................................................................................2280
1.12.42.2 Transmitted Power of Carrier for Cell............................................................................................................2281
1.12.42.3 Transmitted Power of Non-HSDPA Carrier for Cell.....................................................................................2283
1.12.42.4 Power Required by HS-DSCH for Cell..........................................................................................................2285
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxxvii

BSC6900 UMTS
1.12.42.5 Received Scheduled E-DCH Power Share in the Measurement Period for Cell............................................2287
1.12.42.6 Average Power Required for Free HSDPA Users for Cell.............................................................................2289
1.12.42.7 Power Required by 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell......................................................2290
1.12.42.8 DL Transmit Power of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell................................................2293
1.12.43 Soft Handover Measurement per cell(SHO.Cell)..............................................................................................2296
1.12.43.1 Number of Soft Handover Decisions for Radio Link Addition Initiated by RNC.........................................2302
1.12.43.2 Number of Soft Handover Attempts for Different Service............................................................................2304
1.12.43.3 Number of Radio Link Addition Attempts in Soft Handover and Softer Handover......................................2306
1.12.43.4 Number of Successful Soft Handovers in Different Service Types...............................................................2308
1.12.43.5 Number of Successful Radio Link Additions in Soft Handover and Softer Handover..................................2310
1.12.43.6 Mean Number of UEs with One to six Radio Link........................................................................................2312
1.12.43.7 Number of Failed Radio Link Additions in Soft and Softer Handover due to Different Causes...................2313
1.12.43.8 Number of Failed Radio Link Additions in Soft and Softer Handover due to UE No Response..................2316
1.12.43.9 Number of Radio Link Deletion Attempts in Soft Handover and Softer Handover......................................2318
1.12.43.10 Number of Successful Radio Link Deletions in Soft Handover and Softer Handover................................2319
1.12.44 Measurement related to SIRTARGET per cell(SIR.Cell).................................................................................2322
1.12.44.1 SIR Target Measurement for Different Services............................................................................................2323
1.12.45 Measurement related to SPI per cell(SPI.Cell)..................................................................................................2328
1.12.45.1 Number of Times of Downlink Throughput of BE Services with SPI Set to 8 with a Certain Range in a
Measurement Period for HSDPA Cell............................................................................................................................2349
1.12.45.4 Number of Times of Uplink Throughput of BE Services with SPI Set to 8 with a Certain Range in a Measurement
Period for HSUPA Cell..................................................................................................................................................2359
1.12.45.7 Number of Bytes Sent on Downlink HSDPA Mac-d flow of BE Services with SPI Setting to Different Values
........................................................................................................................................................................................2368
1.12.45.8 Number of Bytes Received on Uplink HSUPA Mac-d flow of BE Services with SPI Setting to Different Values
........................................................................................................................................................................................2370
1.12.45.9 Mean Downlink Throughput of HSDPA Mac-d flow of BE Services with SPI Setting to Different Values
........................................................................................................................................................................................2372
1.12.45.10 Mean Downlink Throughput of HSUPA Mac-d flow of BE Services with SPI Setting to Different Values
........................................................................................................................................................................................2375
1.12.46 Measurement related to throughput and data rate per cell(THRUPUT.Cell)....................................................2379
1.12.46.1 Average DL Rate of 64 Kbit/s CS Conversational Services..........................................................................2392
1.12.46.2 DL Traffic Volume of 64 Kbit/s CS Conversational Services.......................................................................2393
1.12.46.3 Average DL Rate of 57.6 Kbit/s CS Streaming Services...............................................................................2393
1.12.46.4 DL Traffic Volume of 57.6 Kbit/s CS Streaming Services............................................................................2394
1.12.46.5 Counters Related to the Average DL Rates of Different PS R99 Background Services................................2395
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxxviii

BSC6900 UMTS
1.12.46.6 Counters Related to the DL Traffic Volumes of Different PS R99 Background Services.............................2398
1.12.46.7 Counters Related to the Average DL Rates of Different PS R99 Interactive Services..................................2400
1.12.46.8 Counters Related to the DL Traffic Volumes of Different PS R99 Interactive Services...............................2402
1.12.46.9 Counters Related to the Average DL Rates of Different PS R99 Streaming Services...................................2404
1.12.46.10 Counters Related to the DL Traffic Volumes of Different PS R99 Streaming Services..............................2406
1.12.46.11 Counters Related to the Average UL Rates of Different PS R99 Background Services..............................2408
1.12.46.12 Counters Related to the UL Traffic Volumes of Different PS R99 Background Services...........................2411
1.12.46.13 Counters Related to the Average UL Rates of Different PS R99 Interactive Services................................2412
1.12.46.14 Counters Related to the UL Traffic Volumes of Different PS R99 Interactive Services.............................2415
1.12.46.15 Counters Related to the Average UL Rates of Different PS R99 Streaming Services.................................2417
1.12.46.16 Counters Related to the UL Traffic Volumes of Different PS R99 Streaming Services..............................2419
1.12.46.17 Average UL Rate of Signaling on DCCH....................................................................................................2420
1.12.46.18 UL Traffic Volume of Signaling on DCCH.................................................................................................2421
1.12.46.19 Average DL Rate of Signaling on DCCH....................................................................................................2422
1.12.46.20 DL Traffic Volume of Signaling on DCCH.................................................................................................2423
1.12.46.21 UL Traffic Volume of AMR Services for Best Cell....................................................................................2424
1.12.46.22 DL Traffic Volume of AMR Services for Best Cell....................................................................................2424
1.12.46.23 UL Traffic Volume of VP Services for Best Cell........................................................................................2425
1.12.46.24 DL Traffic Volume of VP Services for Best Cell........................................................................................2426
1.12.46.25 UL Traffic of BE Services with Different PS Data Rates for Best Cell.......................................................2427
1.12.46.26 DL Traffic of BE Services with Different PS Data Rates for Best Cell.......................................................2428
1.12.46.27 Mean Number of AMR service UEs in the best cell....................................................................................2429
1.12.46.28 Mean Number of VP service UEs in the best cell........................................................................................2430
1.12.46.29 Average Throughput of PTM MBMS Services............................................................................................2431
1.12.46.30 Average Throughput of PTP MBMS Services.............................................................................................2431
1.12.46.31 Average DL Bit Rate of PS Conversational Service....................................................................................2432
1.12.46.32 DL Throughput of PS Conversational Service.............................................................................................2433
1.12.46.33 Average UL Bit Rate of PS Conversational Service....................................................................................2434
1.12.46.34 UL Throughput of PS Conversational Service.............................................................................................2435
1.12.46.35 Sum of Sampled Downlink BE Throughput of UEs with PS Services over DCHs.....................................2436
1.12.46.36 Number of Times Downlink BE Throughput of UEs with PS Services over DCHs Is Sampled................2437
1.12.46.37 Sum of Sampled Uplink BE Throughput of UEs with PS Services over DCHs..........................................2437
1.12.46.38 Number of Times Uplink BE Throughput of UEs with PS Services over DCHs Is Sampled.....................2438
1.12.46.39 Number of Erlangs for AMR Services for Cell............................................................................................2439
1.12.47 Traffic Measurement per cell(TRFFIC.Cell).....................................................................................................2440
1.12.47.1 DL Signaling Rate over BCCH on Iub Interface............................................................................................2443
1.12.47.2 DL Signaling Rate over CCCH on Iub Interface............................................................................................2444
1.12.47.3 UL Signaling Rate over CCCH on Iub Interface............................................................................................2445
1.12.47.4 UL Service Traffic over DCH on Iub Interface for DRNC............................................................................2446
1.12.47.5 DL Service Traffic over DCH on Iub Interface for DRNC............................................................................2447
1.12.47.6 UL Signaling Traffic on Iub Interface............................................................................................................2448
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxxix

BSC6900 UMTS
1.12.47.7 DL Signaling Traffic on Iub Interface............................................................................................................2448

1.12.47.8 UL PS R99 Traffic on Iub Interface...............................................................................................................2449
1.12.47.9 DL PS R99 Traffic on Iub Interface...............................................................................................................2450
1.12.47.10 UL CS Traffic on Iub Interface....................................................................................................................2452
1.12.47.11 DL CS Traffic on Iub Interface....................................................................................................................2453
1.12.47.12 Traffic over RACH on Iub Interface............................................................................................................2453
1.12.47.13 Traffic over FACH on Iub Interface.............................................................................................................2454
1.12.47.14 Traffic over PCH on Iub Interface................................................................................................................2455
1.12.47.15 Counters Related to the Bandwidth of Common Channels on Iub Interface for CRNC..............................2456
1.12.47.16 Bandwidth of Channel for MBMS Services.................................................................................................2457
1.12.47.17 PS Traffic over RACH on Iub Interface.......................................................................................................2458
1.12.47.18 PS Traffic over FACH on Iub Interface.......................................................................................................2458
1.12.47.19 DL HSDPA Traffic on Iub Interface............................................................................................................2459
1.12.47.20 UL HSUPA Traffic on Iub Interface............................................................................................................2460
1.12.48 Measurement related to U2L Handover per cell(U2LTE.HO.Cell)..................................................................2461
1.12.48.1 Number of Outgoing UMTS-to-LTE PS Handover Preparation Attempts for Cell.......................................2467
1.12.48.2 Number of Successful Preparations for Outgoing UMTS-to-LTE PS Handovers for Cell............................2469
1.12.48.3 Number of UMTS-to-LTE PS Handover Attempts Triggered by RNC for Cell...........................................2471
1.12.48.4 Number of Successful UMTS-to-LTE PS Handovers for Cell......................................................................2472
1.12.48.5 Number of Failed Preparations for Outgoing UMTS-to-LTE PS Handovers Due to Different Causes........2474
1.12.48.6 Number of Failed UMTS-to-LTE PS Handovers Due to Different Causes for Cell......................................2477
1.12.48.7 Number of Failed UMTS-to-LTE PS Handovers Due to Iu Release Command Timeout for Cell................2479
1.12.48.8 Number of Abnormally Terminated Outgoing UMTS-to-LTE PS Handovers for Cell.................................2481
1.12.48.9 Number of Redirection to LTE Through RRC Connection Release for Cell.................................................2482
1.12.48.10 Number of UMTS to LTE Blind Redirections Through RRC Connection Release for Cell.......................2485
1.12.49 URA Update Measurement per cell(URAUPDATE.Cell)................................................................................2488
1.12.49.1 Number of URA Updates Attempts for Different Causes..............................................................................2488
1.12.49.2 Number of Successful URA Updates for Different Causes............................................................................2490
1.12.50 WLAN Measurement per cell(WLAN.Cell).....................................................................................................2492
1.12.50.1 Number of Wi-Fi Access Attempts for Cell...................................................................................................2492
1.12.50.2 Number of Wi-Fi Access Failures for Cell.....................................................................................................2494
1.13 Measurement between a cell and a neighbour interRAT cell Performance(UCELL_GCELL).............................2495
1.13.1 Measurement between a cell and a intRAT cell(IRATHO.Gcell).......................................................................2496
1.13.1.1 Number of CS Inter-RAT Outgoing Handover Attempts Between Neighboring Cells...................................2498
1.13.1.2 Number of Successful CS Inter-RAT Outgoing Handovers Between Neighboring Cells...............................2500
1.13.1.3 Number of Failed CS Inter-RAT Outgoing Handovers Between Neighboring Cells......................................2501
1.13.1.4 Number of PS Inter-RAT Outgoing Handover Attempts Between Neighboring Cells....................................2502
1.13.1.5 Number of Successful PS Inter-RAT Outgoing Handovers Between Neighboring Cells................................2504
1.13.1.6 Number of Failed PS Inter-RAT Outgoing Handovers Between Neighboring Cells.......................................2505
1.13.1.7 Number of CS Outgoing Inter-RAT Handover Preparation Attempts Between Neighboring Cells................2507
1.13.1.8 Number of CS Outgoing Inter-RAT Handover Preparation Attempts According to Different Causes Between
Neighboring Cells...........................................................................................................................................................2508
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xl

BSC6900 UMTS
1.13.1.9 Number of Successful CS Outgoing Inter-RAT Handover Preparations Between Neighboring Cells............2510
1.13.1.10 Number of Failed CS Outgoing Inter-RAT Handover Preparations According to Different Causes Between
Neighboring Cells...........................................................................................................................................................2511
1.14 Measurement between a cell and a neighbour UMTS cell(UCELL_NCELL).......................................................2513
1.14.1 Measurement between a cell and a UMTS cell(CELL.Ncell).............................................................................2514
1.14.1.1 Number of Successful Soft Handovers Between Neighboring Cells...............................................................2521
1.14.1.2 Number of Soft Handover Attempts Between Neighboring Cells...................................................................2522
1.14.1.3 Number of Failed Soft Handovers Between Neighboring Cells Due to No Response from UE.....................2524
1.14.1.4 Number of Hard Handover Attempts Between Neighboring Cells..................................................................2525
1.14.1.5 Number of Successful Hard Handovers Between Neighboring Cells..............................................................2527
1.14.1.6 Number of Failed Hard Handovers Between Neighboring Cells Due to No Response from UE....................2528
1.14.1.7 Number of RL Addition Attempts in Soft Handover Between Neighboring Cells..........................................2530
1.14.1.8 Number of Successful RL Additions in Soft Handover Between Neighboring Cells......................................2531
1.14.1.9 Number of RL Deletion Attempts in Soft Handover Between Neighboring Cells..........................................2533
1.14.1.10 Number of Successful RL Deletions in Soft Handover Between Neighboring Cells....................................2534
1.14.1.11 Number of Hard Handover Attempts from HS-DSCH to HS-DSCH Between Neighboring Cells...............2536
1.14.1.12 Number of Successful Hard Handovers from HS-DSCH to HS-DSCH Between Neighboring Cells...........2537
1.14.1.13 Number of HSDPA Serving Cell Change Attempts Between Neighboring Cells.........................................2539
1.14.1.14 Number of Successful HSDPA Serving Cell Changes Between Neighboring Cells.....................................2541
1.14.1.15 Number of CS Domain Outgoing Inter-Cell Hard Handover Attempts Between Neighboring Cells............2542
1.14.1.16 Number of Successful CS Domain Outgoing Hard Handovers Between Neighboring Cells........................2545
1.14.1.17 Number of Failed CS Domain Hard Handovers According to Different Causes Between Neighboring Cells
........................................................................................................................................................................................2547
1.14.1.18 Number of PS Domain Outgoing Inter-Cell Hard Handover Attempts Between Neighboring Cells............2551
1.14.1.19 Number of Successful PS Domain Outgoing Hard Handovers Between Neighboring Cells.........................2553
1.14.1.20 Number of Failed PS Domain Hard Handovers According to Different Causes Between Neighboring Cells
........................................................................................................................................................................................2555
1.14.1.21 Number of Outgoing SRNS Relocation Executions with HHO Between Neighboring Cells.......................2559
1.14.1.22 Number of Successful Outgoing SRNS Relocations with HHO Between Neighboring Cells......................2560
1.14.1.23 Number of Failed CS Domain Outgoing SRNS Relocation with HHO Preparations According to Different Causes
Between Neighboring Cells............................................................................................................................................2562
1.14.1.24 Number of Failed PS Domain Outgoing SRNS Relocation with HHO Preparations According to Different Causes
Between Neighboring Cells............................................................................................................................................2563
1.15 Measurement of UMTS DSP Performance(UDSP)...............................................................................................2565
1.15.1 Measurement related to DSP performance(DSP)................................................................................................2565
1.15.1.1 Uplink PS Traffic Handled by the DSP............................................................................................................2566
1.15.1.2 Downlink PS Traffic Handled by the DSP.......................................................................................................2567
1.15.1.3 Measurement of the DSP Usage in a Period.....................................................................................................2568
2 Transport Network Related Measurement.........................................................................2570

2.1 Measurement of AAL2PATH Performance(AAL2PATH)......................................................................................2586
2.1.1 AAL2 Path Measurement(AAL2PATH)...............................................................................................................2586
2.1.1.1 Number of Active AAL2 Connections to an Adjacent Node.............................................................................2587
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xli

BSC6900 UMTS
2.1.1.2 Counters Related to the Number of Congestions on the AAL2 Path.................................................................2588

2.1.1.3 Counters Related to the Duration of Congestions on the AAL2 Path................................................................2589
2.2 Measurement of AAL2PATH ATM Layer Performance(AAL2PATH_PVCLAYER)..........................................2590
2.2.1 AAL2PATH ATM Layer Measurement(AAL2PATH.PVCLAYER)..................................................................2590
2.2.1.1 Counters Related to the Number of Cells Received, Transmitted or Dropped on an AAL2PATH Link ATM Layer
........................................................................................................................................................................................2593
2.2.1.2 Counters Related to the Number of Bytes Received or Transmitted on an AAL2PATH link ATM Layer.......2594
2.3 Measurement of VCL PM on an AAL2 Path(AAL2PATH_VCLPM)....................................................................2596
2.3.1 Measurement Related to VCL PM on an AAL2 Path(AAL2PATH.VCLPM).....................................................2596
2.3.1.1 Number of VCL PM Cells on an AAL2 Path.....................................................................................................2599
2.3.1.2 Maximum Data Rate of VCL PM on an AAL2 Path.........................................................................................2600
2.3.1.3 VCL PM Cell Discard Rate on an AAL2 Path................................................................................................... 2601
2.3.1.4 Rate of Incorrectly Inserted VCL PM Cells on an AAL2 Path..........................................................................2602
2.3.1.5 Number of Error VCL PM Cell Blocks Failed BIP16 Check on an AAL2 Path...............................................2604
2.4 Measurement of IP Transport Adjacent Node Connection Performance(ANI_IP)..................................................2605
2.4.1 IP Transport Adjacent Node Connection Measurement(ANIIPCONN)...............................................................2605
2.4.1.1 Number of IP Connection Setup Requests Received by IP Transport Adjacent Node......................................2606
2.4.1.2 Number of Successful IP Connections for IP Transport Adjacent Node...........................................................2607
2.4.1.3 Number of IP Connection Modifications...........................................................................................................2608
2.4.1.4 Number of Successful IP Connection Modifications for IP Transport Adjacent Node.....................................2609
2.4.2 IP Transport Adjacent Node Resource Operation Measurement(ANIIPTRM)....................................................2610
2.4.2.1 Number of Requests for Resource Allocation on the IP Transport Adjacent Node...........................................2611
2.4.2.2 Number of Successful Resource Allocations on the IP Transport Adjacent Node............................................2612
2.4.2.3 IP Path Forward Bandwidth Allocated to IP Transport Adjacent Node.............................................................2613
2.4.2.4 IP Path Backward Bandwidth Allocated to IP Transport Adjacent Node.......................................................... 2614
2.4.2.5 Number of Failed Resource Allocations Due to Insufficient Bandwidth on the IP Transport Adjacent Node
........................................................................................................................................................................................2615
2.5 Measurement of QAAL2 Adjacent Node Performance(ANI_QAAL2)...................................................................2616
2.5.1 QAAL2 Measurement(QAAL2)............................................................................................................................2616
2.5.1.1 Number of Resource Allocation Requests by QAAL2......................................................................................2621
2.5.1.2 Number of Successful Resource Allocations by QAAL2..................................................................................2622
2.5.1.3 Number of RLC messages received by the QAAL2..........................................................................................2623
2.5.1.4 Number of RLC messages sent by the QAAL2.................................................................................................2624
2.5.1.5 Number of AAL2 Connection Establishment Requests Sent by the QAAL2.................................................... 2626
2.5.1.6 Number of AAL2 Connection Establishment Requests Received by the QAAL2............................................2627
2.5.1.7 Number of AAL2 Connection Establishment Request Rejections Received by the QAAL2............................2629
2.5.1.8 Number of AAL2 Connection Establishment Confirmations Received by the QAAL2....................................2630
2.5.1.9 Number of AAL2 Connection Establishment Confirmations Sent by the QAAL2...........................................2632
2.5.1.10 Number of AAL2 Connection Establishment Rejections Sent by the QAAL2...............................................2633
2.5.1.11 Number of AAL2 Connection Releases Initiated by QAAL2..........................................................................2635
2.5.1.12 Number of AAL2 Connection Releases Received by the QAAL2..................................................................2636
2.5.1.13 Number of AAL2 Connection Confirmations Received by the QAAL2.........................................................2638
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xlii

BSC6900 UMTS
2.5.1.14 Number of AAL2 Connection Releases Confirmation Initiated by the QAAL2.............................................2639

2.5.1.15 Number of AAL2 Connection Modification Request Rejections Received by the QAAL2............................2641
2.5.1.16 Number of AAL2 Connection Modification Rejections Sent by the QAAL2.................................................2642
2.5.1.17 Number of AAL2 Connection Modification Requests Sent by the QAAL2....................................................2644
2.5.1.18 Number of AAL2 Connection Modification Requests Received by the QAAL2............................................2645
2.5.1.19 Average Number of Active AAL2 Connections to an QAAL2 Adjacent Node..............................................2645
2.5.1.20 AAL2 Path Bandwidth Allocated to an Adjacent Node...................................................................................2646
2.6 Measurement of Dual-Stack Transport Adjacent Node Performance(ANI_QAAL2_IP)........................................2647
2.6.1 Dual-Stack Transport Adjacent Node IP Part Measurement(IPPART)................................................................2648
2.6.1.1 Number of IP Connection Setup Requests Received on Dual-Stack Transport Adjacent Node........................2650
2.6.1.2 Number of Successful IP Connection Setups on the Dual-Stack Transport Adjacent Node..............................2650
2.6.1.3 Number of IP Connection Modifications on the Dual-Stack Transport Adjacent Node....................................2651
2.6.1.4 Number of Successful IP Connection Modifications on the Dual-Stack Transport Adjacent Node..................2652
2.6.1.5 Number of IP Connection Releases on the Dual-Stack Transport Adjacent Node............................................2653
2.6.1.6 Number of Active IP Connections on the Dual-Stack Transport Adjacent Node..............................................2654
2.6.1.7 IP Path Forward Bandwidth Allocated to a Dual-Stack Transport Adjacent Node...........................................2655
2.6.1.8 IP Path Backward Bandwidth Allocated to a Dual-Stack Transport Adjacent Node.........................................2655
2.6.2 Dual-Stack Transport Adjacent Node Measurement(QAAL2IP)..........................................................................2656
2.6.2.1 Number of Requests for Resource Allocations by Dual-Stack Transport Adjacent Node.................................2657
2.6.2.2 Number of Successful Resource Allocations to Dual-Stack Transport Adjacent Node.....................................2658
2.6.2.3 Number of Failed Resource Allocations Due to Insufficient Bandwidth on the Dual-Stack Transport Adjacent Node
........................................................................................................................................................................................2659
2.6.3 Dual-Stack Transport Adjacent Node QAAL2 Part Measurement(QAAL2PART).............................................2660
2.6.3.1 Number of RLC messages received by the QAAL2 on Dual-Stack Adjacent Node.........................................2666
2.6.3.2 Number of RLC messages sent by the QAAL2 on Dual-Stack Adjacent Node................................................2668
2.6.3.3 Number of AAL2 Connection Establishment Requests Sent by the QAAL2 on Dual-Stack Adjacent Node
........................................................................................................................................................................................2670
2.6.3.4 Number of AAL2 Connection Establishment Requests Received by the QAAL2 on the Dual-Stack Adjacent Node
........................................................................................................................................................................................2671
2.6.3.5 Number of AAL2 Connection Establishment Request Rejections Received by the QAAL2 on the Dual-Stack
Adjacent Node................................................................................................................................................................2672
2.6.3.6 Number of AAL2 Connection Establishment Confirmations Received by the QAAL2 on Dual-Stack Adjacent
Node................................................................................................................................................................................2674
2.6.3.7 Number of AAL2 Connection Establishment Confirmations Sent by the QAAL2 on Dual-Stack Adjacent Node
........................................................................................................................................................................................2675
2.6.3.8 Number of RLC Messages Sent by QAAL2 on Dual-Stack Adjacent Node after the QAAL2 Receives the
Connection ERQ Message..............................................................................................................................................2676
2.6.3.9 Number of AAL2 Connection Releases Initiated by QAAL2 on Dual-Stack Adjacent Node...........................2677
2.6.3.10 Number of AAL2 Connection Releases Received by the QAAL2 on Dual-Stack Adjacent Node.................2679
2.6.3.11 Number of AAL2 Connection Confirmations Received by the QAAL2 on Dual-Stack Adjacent Node........2680
2.6.3.12 Number of AAL2 Connection Releases Confirmation Initiated by the QAAL2 on the Dual-Stack Adjacent Node
........................................................................................................................................................................................2681
2.6.3.13 Number of AAL2 Connection Modification Request Rejections Received by the QAAL2 on the Dual-Stack
Adjacent Node................................................................................................................................................................2683
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xliii

BSC6900 UMTS
2.6.3.14 Number of AAL2 Connection Modification Rejections Sent by the QAAL2 on Dual-Stack Adjacent Node
........................................................................................................................................................................................2684
2.6.3.15 Number of AAL2 Connection Modification Requests Sent by the QAAL2 on Dual-Stack Adjacent Node
........................................................................................................................................................................................2685
2.6.3.16 Number of AAL2 Connection Modification Requests Received by the QAAL2 on Dual-Stack Adjacent Node
........................................................................................................................................................................................2686
2.6.3.17 Average Number of QAAL2 Connections to Dual-Stack Adjacent Node.......................................................2687
2.6.3.18 Counters Related to Average QAAL2 Bandwidth Allocated to Iub Adjacent Node on Dual-Stack Adjacent Node
........................................................................................................................................................................................2688
2.7 Measurement of ATM Logical Port Performance(ATM_LOGIC_PORT)..............................................................2689
2.7.1 ATM Logical Port Measurement(ATM.LOGIC.PORT).......................................................................................2689
2.7.1.1 Counters Related to the Bandwidth Assigned to an ATM Logical Port............................................................2691
2.7.1.2 Counters Related to the Number of Congestions on the ATM Logical Port......................................................2692
2.7.1.3 Counters Related to the Duration of Congestions on the ATM Logical Port.....................................................2693
2.8 Measurement of Channelized Optical Port Performance(CHANNELIZED_OPTICAL_PORT)...........................2694
2.8.1 Channelized Optical Port Measurement(CHANNELIZED.OPTICAL.PORT)....................................................2695
2.8.1.1 Duration of Faults on the Channelized Optical Port...........................................................................................2695
2.9 Measuement of E1T1 port error code Performance(E1T1_ES)...............................................................................2696
2.9.1 E1T1 Port Bit Error Measurement(E1T1_ES)......................................................................................................2696
2.9.1.1 E1T1 Errored Second.........................................................................................................................................2698
2.9.1.2 E1T1 Severely Errored Second..........................................................................................................................2699
2.9.1.3 E1T1 Unavailable Second..................................................................................................................................2700
2.9.1.4 E1T1 Background Error Block...........................................................................................................................2701
2.9.1.5 E1T1 Errored Second Rate.................................................................................................................................2702
2.9.1.6 E1T1 Severely Errored Second Rate..................................................................................................................2703
2.9.1.7 E1T1 Unavailable Second Rate..........................................................................................................................2704
2.9.1.8 E1T1 Background Block Error Rate..................................................................................................................2705
2.10 Measurement of E1/T1 ELECT Port Performance(ELECT)..................................................................................2706
2.10.1 E1/T1 Electronical Port Measurement(ELECT).................................................................................................2707
2.10.1.1 Counters Related to the Number of Cells with Error Codes in the E1/T1 electronical port............................2708
2.10.1.2 Counters Related to the Rate of Cells in the E1/T1 electronical port...............................................................2710
2.10.1.3 Duration of Faults in the E1/T1 electronical port.............................................................................................2711
2.10.1.4 Number of Multiframes on the E1/T1 electronical port...................................................................................2712
2.10.1.5 Counters Related to the Traffic Received or Transmitted on the E1/T1 electronical port...............................2712
2.10.1.6 Number of Frame Alignment Changes of the E1/T1 electronical port............................................................2713
2.11 Measurement of FEGE Ethernet Port Performance(FEGE)...................................................................................2714
2.11.1 FEGE Ethernet Port Measurement(FEGE)..........................................................................................................2714
2.11.1.1 Counters Related to the Number of Bytes Received or Transmitted on the FEGE Ethernet port....................2717
2.11.1.2 Counters Related to the Number of frames Received, Transmitted or Discarded on the FEGE Ethernet port
........................................................................................................................................................................................2719
2.11.1.3 Duration of Faults in the FEGE Ethernet port..................................................................................................2721
2.11.1.4 Counters related to the Receive Rate or Transmit Rate of the FEGE Ethernet port........................................2722
2.11.1.5 Counters Related to the Number of the PAUSE Control Frames on the FEGE Ethernet port.........................2724
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xliv

BSC6900 UMTS
2.11.1.6 5-Minute Measurement of the Highest Transmit and Receive Rates of the FEGE Ethernet port....................2725
2.12 Measurement of Fractional ATM Link Performance(FRACATMLNK)...............................................................2726
2.12.1 Fractional ATM Link Measurement(FRACATMLNK)......................................................................................2727
2.12.1.1 Counters Related to the Number of Cells Received, Transmitted or Discarded on an Fractional ATM link
........................................................................................................................................................................................2730
2.12.1.2 Counters Related to the Receive Rate or Transmit Rate of an Fractional ATM link.......................................2731
2.12.1.3 Counters Related to the Occupied Forward Bandwidth or Backward Bandwidth of an FRA ATM Link.......2732
2.12.1.4 Counters Related to the Number of Congestions on an FRA ATM Link........................................................2734
2.12.1.5 Counters Related to the Duration of Congestions on an FRA ATM Link.......................................................2735
2.13 Measurement of Fractioanl IMA Link Performance(FRACIMALNK).................................................................2736
2.13.1 Fractional IMA Link Measurement(FRACIMALNK)........................................................................................2736
2.13.1.1 Counters Related to the Number of Cells Received, Transmitted or Discarded on an Fractional IMA Link
........................................................................................................................................................................................2738
2.13.1.2 Counters Related to the Receive Rate or Transmit Rate of an Fractional IMA Link.......................................2740
2.14 Measurement of IMA Group Performance(IMAGRP)...........................................................................................2742
2.14.1 IMA Group Measurement(IMAGRP).................................................................................................................2742
2.14.1.1 Counters Related to the Number of Cells Received or Transmitted on an IMA Group...................................2746
2.14.1.2 Counters Related to the Receive Rate or Transmit Rate of an IMA Group.....................................................2748
2.14.1.3 Counters Related to the Number of Error Cells Received or Transmitted on an IMA Group.........................2750
2.14.1.4 Counters related to the Occupied Forward Bandwidth or Occupied Backward Bandwidth of an IMA Group
........................................................................................................................................................................................2750
2.14.1.5 Counters Related to the Number of Congestions on an IMA Group................................................................2752
2.14.1.6 Counters Related to the Duration of Congestion on an IMA Group................................................................2753
2.15 Measurement of IMA Link Performance(IMALNK).............................................................................................2754
2.15.1 IMA Link Measurement(IMALNK)...................................................................................................................2754
2.15.1.1 Counters Related to the Number of Packets Received or Transmitted on an IMA Link.................................2758
2.15.1.2 Counters Related to the Receive Rate or Transmit Rate of an IMA Link........................................................2760
2.15.1.3 Number of Times That a Fault Occurs in an IMA Link...................................................................................2761
2.15.1.4 Number of Times That a Fault Is Cleared in an IMA Link..............................................................................2762
2.15.1.5 Duration of Faults in an IMA Link...................................................................................................................2763
2.16 Measurement of IPoA Link Performance(IPOALNK)...........................................................................................2764
2.16.1 IPoA Link Measurement(IPOALNK).................................................................................................................2764
2.16.1.1 Counters Related to the Number of Cells Received or Transmitted Correctly on An IPoA Link...................2767
2.16.1.2 Counters Related to the Number of Bytes Received or Transmitted on an IPoA Link....................................2768
2.16.1.3 Counters Related to the Maximum Receive Rate or the Maximum Transmit Rate of an IPoA Link..............2769
2.16.1.4 Counters Related to the Number of Cells Discarded on an IPoA Link............................................................2770
2.17 Measurement of VCL PM on an IPOAPVC link(IPOAPVC_VCLPM)................................................................2771
2.17.1 Measurement Related to VCL PM on an IPOAPVC link(IPOAPVC.VCLPM).................................................2772
2.17.1.1 Number of VCL PM Cells on an IPOAPVC link.............................................................................................2774
2.17.1.2 Maximum Data Rate of VCL PM on an IPOAPVC link.................................................................................2775
2.17.1.3 VCL PM Cell Discard Rate on an IPOAPVC link...........................................................................................2776
2.17.1.4 Rate of Incorrectly Inserted VCL PM Cells on an IPOAPVC link..................................................................2777
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xlv

BSC6900 UMTS
2.17.1.5 Number of Error VCL PM Cell Blocks Failed BIP16 Check on an IPOAPVC link.......................................2778
2.18 Measurement of IP Path Performance(IPPATH)...................................................................................................2780
2.18.1 IP Path Link Measurement(IPPATH)..................................................................................................................2780
2.18.1.1 Number of Active Connections on an IP Path..................................................................................................2782
2.18.1.2 Average IP Path Ping Delay.............................................................................................................................2782
2.18.1.3 Maximum IP Path Ping Delay..........................................................................................................................2783
2.18.1.4 Average IP Path Ping Delay Variation.............................................................................................................2784
2.18.1.5 Maximum IP Path Ping Delay Variation..........................................................................................................2786
2.18.1.6 Average IP Path Ping Packet Loss Rate...........................................................................................................2786
2.18.1.7 Maximum IP Path Ping Packet Loss Rate........................................................................................................2787
2.18.1.8 Counters Related to the Number of Congestions on an IP Path.......................................................................2788
2.18.1.9 Counters Related to the Duration of Congestion on an IP Path.......................................................................2790
2.19 Measurement of IPPATH IP Layer Performance(IPPATH_IPLAYER)...............................................................2791
2.19.1 IPPATH IP Layer Measurement(IPPATH.IPLAYER).......................................................................................2792
2.19.1.1 Counters Related to the Number of Packets Received, Transmitted or Dropped at the IP Layer of an IPPATH
........................................................................................................................................................................................2795
2.19.1.2 Counters Related to the Number of Bytes Received, Transmitted or Discarded at the IP Layer of an IPPATH
........................................................................................................................................................................................2796
2.19.1.3 Counters Related to the Receive Rate or Transmit Rate of an IPPATH at the IP Layer..................................2798
2.19.1.4 5-Minute Measurement of the Highest Transmit and Receive Rates of an IPPATH at the IP Layer..............2800
2.20 Measurement of IPPATH PM Performance(IPPATH_PM)..................................................................................2801
2.20.1 Measurement Related to IPPM(IPPATH.PM)....................................................................................................2801
2.20.1.1 Bit Rate of IPPM..............................................................................................................................................2803
2.20.1.2 Packet TX and RX Rates of IPPM...................................................................................................................2805
2.20.1.3 Forward Packet Loss Rate of IPPM.................................................................................................................2806
2.20.1.4 Jitter Standard Deviation of IPPM....................................................................................................................2807
2.20.1.5 RTT Delay of IPPM.........................................................................................................................................2808
2.21 Measurement of IP-Path-Based RTP Performance(IPPATH_RTP)......................................................................2809
2.21.1 Measurement related to RTP flux in IPPATH(IPPATH.RTP)............................................................................2809
2.21.1.1 Total Number of RTP Packets Transmitted over a Single IP Path...................................................................2810
2.21.1.2 Total Amount of RTP Data in KB Transmitted over a Single IP Path.............................................................2811
2.21.1.3 Total Amount of RTP Data in KB Received over a Single IP Path.................................................................2812
2.21.1.4 Loss Rate of RTP Packets Received over a Single IP Path..............................................................................2813
2.21.1.5 Total Number of RTP Packets Received over a Single IP Path.......................................................................2814
2.21.1.6 Mean Delay Jitter of RTP Packets Received over a Single IP Path.................................................................2814
2.21.1.7 Mean RTT of Packets Received over a Single IP Path....................................................................................2815
2.21.1.8 Local Received Bandwidth of a Single IP Path................................................................................................2816
2.21.1.9 Local Transmitted Bandwidth of a Single IP Path...........................................................................................2817
2.21.1.10 Ratio of Duration of RTP Delay Jitter Exceeding Threshold to Total Active Duration................................2817
2.21.1.11 Ratio of Duration of RTT Exceeding Threshold to Total Active Duration....................................................2818
2.22 Measurement of Transmission Resource Pool Adjacent Node Connection Performance(IPPOOL_ADJNODE)
........................................................................................................................................................................................2819
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xlvi

BSC6900 UMTS
2.22.1 Measurement of IP Layer on User Plane of Transmission Resource Pool Adjacent Node
(IPPOOL.ADJNODE.IPLAYER)..................................................................................................................................2820
2.22.1.1 Counters Related to the Number of Packets Received or Transmitted at the IP Layer on Adjacent Node User Plane
........................................................................................................................................................................................2821
2.22.1.2 Counters Related to the Number of Bytes Received or Transmitted at the IP Layer on Adjacent Node User Plane
........................................................................................................................................................................................2822
2.22.1.3 Counters Related to the Receive Rate or Transmit Rate at the IP Layer on Adjacent Node User Plane.........2823
2.22.2 Measurement of IP Transmission Quality of Transmission Resource Pool Adjacent Node(IPPOOL.ADJNODE)
........................................................................................................................................................................................2825
2.22.2.1 Counters Related to the Number of Congestions of Adjacent Node................................................................2826
2.22.2.2 Counters Related to the Duration of Congestion of Adjacent Node................................................................2827
2.22.2.3 Average Ping Delay of Adjacent Node............................................................................................................2828
2.22.2.4 Maximum Ping Delay of Adjacent Node.........................................................................................................2829
2.22.2.5 Average Ping Delay Variation of Adjacent Node............................................................................................2830
2.22.2.6 Maximum Ping Delay Variation of Adjacent Node.........................................................................................2831
2.22.2.7 Average Ping Packet Loss Rate of Adjacent Node..........................................................................................2832
2.22.2.8 Maximum Ping Packet Loss Rate of Adjacent Node.......................................................................................2833
2.23 Measurement of Transmission Resource Pool IPPM Performance(IPPOOL_PM)...............................................2834
2.23.1 Transmission Resource Pool IPPM Performance Measurement(IPPOOL.PM).................................................2834
2.23.1.1 Bit Rate of Transmission Resource Pool IPPM................................................................................................2837
2.23.1.2 VS.IPPOOL.IPPM.ForwardPkts.MeansTx......................................................................................................2838
2.23.1.3 VS.IPPOOL.IPPM.Forward.DropMeans.........................................................................................................2840
2.23.1.4 Forward Jitter of Transmission Resource Pool IPPM......................................................................................2841
2.23.1.5 RTT Delay of Transmission Resource Pool IPPM...........................................................................................2842
2.24 Measurement of Transmission Resource Pool IP Address RTP Performance(IPPOOL_RTP).............................2843
2.24.1 Measurement of Transmission Resource Pool IP Address RTP Performance(IPPOOL.RTP)...........................2844
2.24.1.1 Number of RTP Packets Sent Between an IP Address Pair.............................................................................2845
2.24.1.2 Number of Bytes in RTP Packets Sent Between an IP Address Pair...............................................................2846
2.24.1.3 Number of Bytes in RTP Packets Received Between an IP Address Pair.......................................................2847
2.24.1.4 Downlink Loss Rate of RTP Packets Between an IP Address Pair..................................................................2848
2.24.1.5 Number of RTP Packets Received Between an IP Address Pair......................................................................2849
2.24.1.6 Mean Delay Jitter for Receiving RTP Packets Between an IP Address Pair...................................................2849
2.24.1.7 Mean RTT for RTP Packets Received Between an IP Address Pair................................................................2850
2.24.1.8 Receive Bandwidth for RTP Packets Received Between an IP Address Pair..................................................2851
2.24.1.9 Transmit Bandwidth for RTP Packets Sent Between an IP Address Pair........................................................2852
2.24.1.10 Percentage of Duration When Delay Jitter of RTP Packets Exceeds the Threshold to Total Activation Duration
........................................................................................................................................................................................2853
2.24.1.11 Percentage of Duration When RTT of RTP Packets Exceeds the Threshold to Total Activation Duration
........................................................................................................................................................................................2854
2.25 Measurement of Transmission Resource Pool Local IP Address Connection Performance(IPPOOL_SIP).........2855
2.25.1 Transmission Resource Pool Local IP Address IP Layer Measurement(IPPOOL.SIP.IPLAYER)....................2855
2.25.1.1 Counters Related to the Number of Packets Received or Transmitted at the IP Layer on Local IP Address
........................................................................................................................................................................................2856
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xlvii

BSC6900 UMTS
2.25.1.2 Counters Related to the Number of Bytes Received or Transmitted at the IP Layer on Local IP Address
........................................................................................................................................................................................2858
2.25.1.3 Counters Related to the Receive Rate or Transmit Rate at the IP Layer on Local IP Address........................2859
2.25.2 Transmission Resource Pool Local IP Address Transmission Quality Measurement(IPPOOL.SIP).................2860
2.25.2.1 Average Ping Packet Loss Rate of Local IP Address.......................................................................................2861
2.26 Measurement of IURP Link Performance(IURPLNK)..........................................................................................2862
2.26.1 IURP Link Measurement(IURPLNK).................................................................................................................2862
2.26.1.1 Number of Packets Sent on the IURP Link......................................................................................................2863
2.26.1.2 Number of Packets Received on the IURP Link..............................................................................................2864
2.26.1.3 Maximum Number of Packets Sent on the IURP Link....................................................................................2865
2.26.1.4 Maximum Number of Packets Received on the IURP Link............................................................................2866
2.26.1.5 Number of IP Bytes Sent on the IURP Link....................................................................................................2866
2.26.1.6 Number of IP Bytes Received on the IURP Link.............................................................................................2867
2.26.1.7 Maximum Number of IP Bytes Sent on the IURP Link...................................................................................2868
2.26.1.8 Maximum Number of IP Bytes Received on the IURP Link...........................................................................2869
2.26.1.9 Service Duration of the IURP Link..................................................................................................................2870
2.26.1.10 Number of Congestions on the IURP Link....................................................................................................2870
2.26.1.11 Congestion Duration of the IURP Link..........................................................................................................2871
2.26.1.12 Number of Overloads on the IURP Link........................................................................................................2872
2.26.1.13 Overload Duration of the IURP Link.............................................................................................................2873
2.26.1.14 Number of Packets Resent on the IURP Link................................................................................................2874
2.27 Measurement of Logic Port Performance(LOGIC_PORT)....................................................................................2874
2.27.1 Logical Port Measurement(LOGIC.PORT)........................................................................................................2875
2.27.1.1 Number of frames transmitted or discarded over a logical port.......................................................................2878
2.27.1.2 Number of bytes of data transmitted or discarded over a logical port..............................................................2879
2.27.1.3 Measurement of the Transmit Rate of the Logic Port......................................................................................2880
2.27.1.4 Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to the Logic Port.....................2881
2.27.1.5 Measurement of the Number of Congestions on the Logic Port......................................................................2882
2.27.1.6 Measurement of Congestion Duration on the Logic Port.................................................................................2883
2.27.1.7 5-Minute Measurement of the Highest Transmit Rates of of the Logic Port...................................................2884
2.28 Measurement of Logic Port Queue Performance(LOGIC_PORT_QUEUE).........................................................2885
2.28.1 Logical Port Queue Measurement(LOGIC.PORT.QUEUE)...............................................................................2885
2.28.1.1 Measurement of the Transmitted and Discarded Packets over a logical port queue........................................2886
2.28.1.2 Measurement of the Transmitted and Discarded Bytes over a logical port queue...........................................2887
2.28.1.3 Measurement of the Transmit Rate of logical port queue................................................................................2888
2.29 Measurement of the M3UA Destination Entities Performance(M3UA_DE).........................................................2889
2.29.1 M3UA Destination Entity Measurement(M3UA.DE).........................................................................................2890
2.29.1.1 Number of M3UA Destination Entity Changes to Unavailable State..............................................................2890
2.29.1.2 Duration of M3UA Destination Entity in Unavailable State............................................................................2891
2.30 Measurement of the M3UA Link Performance(M3UA_LNK)..............................................................................2892
2.30.1 M3UA Link Measurement(M3UA.LNK)...........................................................................................................2892
2.30.1.1 Number of M3UA Link Failures......................................................................................................................2893
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xlviii

BSC6900 UMTS
2.30.1.2 Duration of M3UA Link Failure......................................................................................................................2894

2.30.1.3 Duration of M3UA Link Congestion................................................................................................................2895
2.30.1.4 Counters Related to the Number of Message Units Sent and Received on M3UA Link.................................2895
2.31 Measurement of M3UA Link Set Performance(M3UA_LNK_SET)....................................................................2897
2.31.1 M3UA Link Set Measurement(M3UA.LNKSET)..............................................................................................2897
2.31.1.1 Number of M3UA Link Set Failures................................................................................................................2898
2.31.1.2 Duration of M3UA Link Set Failure................................................................................................................2899
2.32 Measurement of MP Group Performance(MLPPP)...............................................................................................2900
2.32.1 MP Group Measurement(MLPPP)......................................................................................................................2900
2.32.1.1 Counters Related to the Number of frames Received, Transmitted or Discarded on an MP Group................2903
2.32.1.2 Counters Related to the Number of Bytes of Data Received or Transmitted on an MP Group.......................2905
2.32.1.3 Duration of Faults in an MP Group..................................................................................................................2906
2.32.1.4 Counters Related to the Receive Rate or Transmit Rate of an MP Group.......................................................2906
2.32.1.5 Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to an MLPPP Group...............2908
2.32.1.6 Measurement of the Number of Congestions on an MLPPP Group................................................................2909
2.32.1.7 Measurement of the Duration of Congestion on an MLPPP Group.................................................................2910
2.33 Measurement of MP Queue Performance(MLPPP_QUEUE)................................................................................2911
2.33.1 MP Queue Measurement(MLPPP.QUEUE).......................................................................................................2911
2.33.1.1 Counters Related to the Transmitted and Discarded Packets on an MP Queue...............................................2913
2.33.1.2 Counters Related to the Number of Bytes Transmitted or Discarded on an MP Queue..................................2914
2.33.1.3 Measurement Counters Related to the Transmit Rate of an MP Queue...........................................................2915
2.34 Measurement of MTP3 Destination Signaling Point Performance(MTP3_DSP)..................................................2916
2.34.1 MTP3 Destination Signaling Point Measurement(MTP3.DSP)..........................................................................2916
2.34.1.1 Number of MTP3 Destination Signaling Point Failures..................................................................................2917
2.34.1.2 Duration of MTP3 Destination Signaling Point Failure...................................................................................2918
2.35 Measurement of MTP3 Signaling Link performance(MTP3_LNK)......................................................................2919
2.35.1 MTP3 Link Measurement(MTP3.LNK)..............................................................................................................2919
2.35.1.1 Service Duration of MTP3 Link.......................................................................................................................2921
2.35.1.2 Number of MTP3 Link Failures.......................................................................................................................2922
2.35.1.3 Duration of Out-of-Service MTP3 Link...........................................................................................................2923
2.35.1.4 Duration of MTP3 Link Congestion.................................................................................................................2923
2.35.1.5 Number of Local Inhibitions on MTP3 Link....................................................................................................2924
2.35.1.6 Duration of Local Inhibition on MTP3 Link....................................................................................................2925
2.35.1.7 Number of Remote Inhibitions on MTP3 Link................................................................................................2926
2.35.1.8 Duration of Remote Inhibition on MTP3 Link.................................................................................................2926
2.35.1.9 Number of MTP3 Link Changeovers...............................................................................................................2927
2.35.1.10 Number of Message Signal Units Sent by MTP3 Link..................................................................................2928
2.35.1.11 Number of Message Signal Units Received by MTP3 Link..........................................................................2929
2.35.1.12 Number of MTP3 Link Congestions..............................................................................................................2929
2.35.1.13 Number of MSU Bytes Sent by MTP3 Link..................................................................................................2930
2.35.1.14 Number of MSU Bytes Received by MTP3 Link..........................................................................................2931
Issue 06 (2014-01-20) Huawei Proprietary and Confidential xlix

BSC6900 UMTS
2.35.1.15 MTP3 Link Remote Processor Failures..........................................................................................................2932

2.35.1.16 Number of Messages Discarded on MTP3 Link Due to Link Congestion.....................................................2933
2.35.1.17 Number of Transfer-Prohibited Signals Received on MTP3 Link.................................................................2933
2.35.1.18 Number of Messages Discarded on MTP3 Link Due to Route Fail...............................................................2934
2.35.1.19 Number of Transfer-Controlled Signals Received on MTP3 Link................................................................2935
2.35.1.20 Duration of MTP3 Link Remote Processor Fault...........................................................................................2936
2.36 Measurement of MTP3 Link Set Performance(MTP3_LNK_SET).......................................................................2937
2.36.1 MTP3 Link Set Measurement(MTP3.LNKSET)................................................................................................2937
2.36.1.1 Number of MTP3 Link Set Failures.................................................................................................................2938
2.36.1.2 Duration of MTP3 Link Set in Unavailable State............................................................................................2938
2.37 Measurement of Non-Channelized Optical Port Performance(NON_CHANNELIZED_OPTICAL_PORT)......2939
2.37.1 Non Channelized Optical Port Measurement(NON.CHANNELIZED.OPTICAL.PORT).................................2939
2.37.1.1 Counters Related to the Number of Cells Received or Transmitted on the optical port..................................2940
2.37.1.2 Duration of Faults in the optical port................................................................................................................2941
2.37.1.3 Counters Related to the Receive Rate or Transmit Rate over the optical port.................................................2942
2.37.2 Maximum flux of UOI board(UOI.BOARD)......................................................................................................2944
2.37.2.1 Maximum receiving and transmitting rate of UOI board.................................................................................2944
2.38 Measurement of NODEB OAM Flow Performance(OAM_FLOW).....................................................................2945
2.38.1 NODEB OAM FLOW Measurement(OAM.FLOW)..........................................................................................2946
2.38.1.1 Counters Related to the Number of Packets Received or Transmitted in the OAM FLOW............................2948
2.38.1.2 Counters Related to the Number of Bytes Received or Transmitted in the OAM FLOW...............................2950
2.38.1.3 Counters Related to the Receive Rate or Transmit Rate of the OAM FLOW.................................................2951
2.39 Measurement of PPP Link Performance(PPP).......................................................................................................2952
2.39.1 PPP Link Measurement(PPP)..............................................................................................................................2953
2.39.1.1 Number of Frames Received, Transmitted or Discarded on a PPP Link.........................................................2955
2.39.1.2 Number of Bytes Received or Transmitted on a PPP Link..............................................................................2957
2.39.1.3 Duration of Faults on a PPP Link.....................................................................................................................2958
2.39.1.4 Counters Related to the Receive Rate or Transmit Rate of a PPP Link...........................................................2958
2.39.1.5 Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to a PPP Link..........................2960
2.39.1.6 Measurement of the Number of Congestions on a PPP Link...........................................................................2961
2.39.1.7 Measurement of the Duration of Congestion on a PPP Link...........................................................................2962
2.40 Measurement of PPP Queue Performance(PPP_QUEUE).....................................................................................2963
2.40.1 PPP Link Queue Measurement(PPP.QUEUE)....................................................................................................2963
2.40.1.1 Counters Related to the Number of Packets Transmitted in a PPP Link Queue or Discarded in the Transmitting
Direction of a PPP Link Queue......................................................................................................................................2965
2.40.1.2 Counters Related to the Number of Bytes Transmitted in a PPP Link Queue or Discarded in the Transmitting
Direction of a PPP Link Queue......................................................................................................................................2966
2.40.1.3 Counters Related to the Transmit Rate of a PPP Link Queue..........................................................................2967
2.41 Measurement of SAAL Link Performance(SAAL_LNK).....................................................................................2968
2.41.1 SAAL Link Measurement(SAAL.LNK).............................................................................................................2968
2.41.1.1 In-Service Duration of SAAL Link..................................................................................................................2970
2.41.1.2 Number of SAAL Link Failures.......................................................................................................................2971
Issue 06 (2014-01-20) Huawei Proprietary and Confidential l

BSC6900 UMTS
2.41.1.3 Number of Link Failures Due to No Response of SAAL Link........................................................................2971

2.41.1.4 Number of SAAL Link Failures Due to Excessive Errors...............................................................................2973
2.41.1.5 Number of SAAL Link Failures Due to No Credit..........................................................................................2973
2.41.1.6 Number of SAAL Link Location Failures........................................................................................................2974
2.41.1.7 Number of Retransmissions of the downlink Lost Packet on the SAAL Link.................................................2975
2.41.1.8 Number of Unexpected PDUs Received by SAAL Link.................................................................................2976
2.41.1.9 Number of Errors of Other Types on SAAL Link............................................................................................2977
2.41.1.10 Number of Retransmission Failures of Connection Control Message on SAAL Link..................................2978
2.41.1.11 Number of Bytes Received by SAAL Link....................................................................................................2978
2.41.1.12 Number of Bytes Sent by SAAL Link............................................................................................................2979
2.41.1.13 Number of Packets Discarded by SAAL Link Due to Buffer Congestion.....................................................2980
2.41.1.14 Number of Retransmissions of the uplink Lost Packet on the SAAL Link...................................................2981
2.42 Measurement of SAAL Link ATM Layer Performance(SAALLNK_PVCLAYER)............................................2982
2.42.1 SAAL link ATM Layer Measurement(SAALLNK.PVCLAYER).....................................................................2982
2.42.1.1 Counters Related to the Number of Bytes Received or Transmitted on an SAAL link ATM Layer...............2986
2.42.1.2 Counters Related to the Maximum Receive Rate or Maximum Transmit Rate of an SAAL link ATM Layer
........................................................................................................................................................................................2987
2.42.1.3 Counters Related to the Number of Correct Packets Received or Transmitted on an SAAL link ATM Layer
........................................................................................................................................................................................2988
2.42.1.4 Counters Related to the Number of Cells Discarded on an SAAL link ATM Layer.......................................2989
2.43 Measurement of VCL PM on a SAAL link(SAALLNK_VCLPM).......................................................................2990
2.43.1 Measurement Related to VCL PM on a SAAL link(SAALLNK.VCLPM)........................................................2991
2.43.1.1 Number of VCL PM Cells on a SAAL link.....................................................................................................2993
2.43.1.2 Maximum Data Rate of VCL PM on a SAAL link..........................................................................................2994
2.43.1.3 VCL PM Cell Discard Rate on a SAAL link....................................................................................................2995
2.43.1.4 Rate of Incorrectly Inserted VCL PM Cells on a SAAL link...........................................................................2996
2.43.1.5 Number of Error VCL PM Cell Blocks Failed BIP16 Check on a SAAL link................................................2997
2.44 Measurement of SCCP Based on OSP Performance(SCCP).................................................................................2999
2.44.1 SCCP Measurement(SCCP)................................................................................................................................2999
2.44.1.1 Number of SCCP Connection Release Expiry.................................................................................................3003
2.44.1.2 Number of SCCP Connection Releases Due to SCCP Inactivity Test.............................................................3004
2.44.1.3 Number of NSP-initiated SCCP Connection Releases Received by SCCP.....................................................3005
2.44.1.4 Number of SCCP XUDT Segmentation Failures.............................................................................................3006
2.44.1.5 Number of RLSD Messages Received by the SCCP.......................................................................................3006
2.44.1.6 Number of XUDTS Messages Received by the SCCP with the Cause of Transmission Error.......................3008
2.44.1.7 Number of UDTS Messages Received by the SCCP with the Cause of Segmentation Failure.......................3009
2.44.1.8 Number of ERROR PDU Messages Received by the SCCP...........................................................................3010
2.44.1.9 Number of ERROR PDU Messages Sent by the SCCP...................................................................................3011
2.44.1.10 Number of SCCP Routing Failures................................................................................................................3011
2.44.1.11 Counters Related to Number of Messages Sent by the SCCP........................................................................3013
2.44.1.12 Counters Related to Number of Messages Received by the SCCP................................................................3014
2.44.1.13 Number of Messages Handled by the SCCP..................................................................................................3016
Issue 06 (2014-01-20) Huawei Proprietary and Confidential li

BSC6900 UMTS
2.44.1.14 Number of Messages Sent by the SCCP to the Local Subsystem..................................................................3017

2.44.1.15 Number of CR Messages Sent and Received by the SCCP...........................................................................3017
2.44.1.16 Number of CREF Messages Sent and Received by the SCCP.......................................................................3019
2.44.1.17 Ratio of the CREF Messages from the Peer SCCP........................................................................................3020
2.44.1.18 Ratio of the CREF Messages from the Local SCCP......................................................................................3020
2.44.1.19 Number of CC Messages Sent and Received by the SCCP...........................................................................3021
2.44.1.20 Number of RLSD Messages Sent by the SCCP.............................................................................................3022
2.44.1.21 Number of RLC Messages Sent and Received by the SCCP.........................................................................3023
2.45 Measurement of SCTP Link Performance(SCTPLNK).........................................................................................3024
2.45.1 SCTPIP Measurement(SCTPIP)..........................................................................................................................3025
2.45.1.1 Counters Related to Number of Bytes That the SCTP Link Receives from or Transmits to the IP Layer......3026
2.45.1.2 Counters Related to the Number of IP Packets Received or Transmitted on the SCTP Link..........................3028
2.45.1.3 Number of Packets Resent on the SCTP Link..................................................................................................3030
2.45.1.4 Number of Error Packets Received on SCTP Link..........................................................................................3031
2.45.1.5 Number of Retransmit Request Sent on the SCTP Link..................................................................................3032
2.45.2 SCTP Link Measurement(SCTPLNK)................................................................................................................3033
2.45.2.1 Service Duration of the SCTP Link..................................................................................................................3033
2.45.2.2 Congestion Duration of the SCTP Link...........................................................................................................3034
2.45.2.3 Number of Packets Sent on the SCTP Link.....................................................................................................3035
2.45.2.4 Number of Packets Received on SCTP Link....................................................................................................3036
2.46 Measurement of SCTP Link IP Layer Performance(SCTPLNK_IPLAYER).......................................................3037
2.46.1 Measurement related to SCTP link IP layer(SCTPLNK.IPLAYER)..................................................................3037
2.46.1.1 Counters related to the Receive Rate or Transmit Rate of an SCTP link IP layer...........................................3040
2.47 Measurement of SDH Performance(SDH).............................................................................................................3042
2.47.1 SDH Measurement(SDH)....................................................................................................................................3042
2.47.1.1 Counters Related to the Number of SDH Port Switchovers.............................................................................3043
2.47.1.2 Number of SDH Channel Failures....................................................................................................................3044
2.48 Measurement of Trunk Group Performance(Trunk)..............................................................................................3045
2.48.1 Measurement of Trunk Group Performance(Trunk)...........................................................................................3045
2.48.1.1 Number of Bytes That Are Transmitted and Received by Trunk Group.........................................................3049
2.48.1.2 Receive Rate and Transmit Rate of Trunk Group............................................................................................3050
2.48.1.3 BER of Data Transmitted and Received by Trunk Group................................................................................3051
2.48.1.4 Number of Frames That Are Transmitted, Received, or Discarded by the Trunk Group................................3052
2.49 Measurement of UNI Link Performance(UNILNK)..............................................................................................3054
2.49.1 Measurement related to UNI link(UNILNK)......................................................................................................3055
2.49.1.1 Counters Related to the Number of Cells Received or Transmitted on a UNI Link........................................3057
2.49.1.2 Counters Related to the Receive Rate or Transmit Rate of a UNI Link...........................................................3059
2.49.1.3 Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to a UNI Link..........................3060
2.49.1.4 Measurement of the Number of Congestions on a UNI Link...........................................................................3061
2.49.1.5 Measurement of the Duration of Congestion on an UNI Link.........................................................................3062
2.50 Measurement of VC Cross Performance(VCACROSS)........................................................................................3063
Issue 06 (2014-01-20) Huawei Proprietary and Confidential lii

BSC6900 UMTS
2.50.1 VCACROSS Measurement(VCACROSS)..........................................................................................................3063

2.50.1.1 Measurement of the Number of Bytes Received or Transmitted on a VCCROSS Link..................................3067
2.50.1.2 Measurement of the Number of Cells Received or Transmitted on a VCCROSS Link...................................3068
2.50.1.3 Counters Related to the Receive Rate or Transmit Rate of a VC Cross Connection.......................................3070
3 Hardware Platform Related Measurement.........................................................................3072

3.1 Measurement of DPU Performance(DPU)...............................................................................................................3073
3.1.1 DPU Measurement(DPU)......................................................................................................................................3073
3.1.1.1 Maximum CPU Usage of the DPU.....................................................................................................................3074
3.1.1.2 Average CPU Usage of the DPU........................................................................................................................3074
3.1.1.3 Rate of the Period in Which the CPU Usage of the DPU Exceeds the Alarm Threshold..................................3075
3.1.1.4 Rate of the Period in Which the CPU Usage of the DPU Is Lower Than the Alarm Threshold........................3076
3.2 Measurement of Inter-Subrack Traffic Performance(FRAME_FLUX)...................................................................3077
3.2.1 Inter-Subrack Traffic Measurement(FRAME.FLUX)...........................................................................................3077
3.2.1.1 Peak Inter-Subrack Transmitting Traffic............................................................................................................3078
3.2.1.2 Average Inter-Subrack Transmitting Traffic......................................................................................................3078
3.2.1.3 Number of Discarded Inter-Subrack Packets.....................................................................................................3079
3.2.1.4 Number of Sent Inter-Subrack Packets..............................................................................................................3080
3.3 Measurement of GCU Performance(GCU)..............................................................................................................3081
3.3.1 GCU Measurement(GCU).....................................................................................................................................3081
3.3.1.1 Maximum CPU Usage of the GCU....................................................................................................................3082
3.3.1.2 Average CPU Usage of the GCU.......................................................................................................................3083
3.3.1.3 Rate of the Period in Which the CPU Usage of the GCU Exceeds the Alarm Threshold..................................3083
3.3.1.4 Rate of the Period in Which the CPU Usage of the GCU Is Lower Than the Alarm Threshold.......................3084
3.4 Measurement of INT Performance(INT)..................................................................................................................3085
3.4.1 Measurement related to INT(INT).........................................................................................................................3085
3.4.1.1 Maximum CPU usage of the INT.......................................................................................................................3086
3.4.1.2 Average CPU Usage of the INT.........................................................................................................................3087
3.4.1.3 Rate of the Period in Which the CPU Usage of the INT Exceeds the Alarm Threshold...................................3088
3.4.1.4 Rate of the Period in Which the CPU Usage of the INT Is Lower Than the Alarm Threshold.........................3089
3.4.1.5 Maximum Forwarding Ratio of Interface Boards..............................................................................................3090
3.4.1.6 Average Forwarding Ratio of Interface Boards..................................................................................................3090
3.4.1.7 Number of Call Establishment Attempts And Number of Call Establishment Failures on an Interface Board
........................................................................................................................................................................................3091
3.5 Measurement of NIU DSP Performance(NDSP).....................................................................................................3092
3.5.1 Measurement related to NIU DSP performance(NDSP).......................................................................................3093
3.5.1.1 Maximum CPU Usage of the NIU DSP.............................................................................................................3093
3.5.1.2 Average CPU Usage of the NIU DSP................................................................................................................3094
3.6 Measurement of NIU Performance(NIU).................................................................................................................3095
3.6.1 NIU Measurement(NIU)........................................................................................................................................3095
3.6.1.1 Maximum CPU Usage of the NIU.....................................................................................................................3096
3.6.1.2 Average CPU Usage of the NIU.........................................................................................................................3097
Issue 06 (2014-01-20) Huawei Proprietary and Confidential liii

BSC6900 UMTS
3.7 Measurement of SCU Performance(SCU)...............................................................................................................3098

3.7.1 SCU Measurement(SCU)......................................................................................................................................3098
3.7.1.1 Maximum CPU Usage of the SCU.....................................................................................................................3099
3.7.1.2 Average CPU Usage of the SCU........................................................................................................................3099
3.7.1.3 Rate of the Period in Which the CPU Usage of the SCU Exceeds the Alarm Threshold..................................3100
3.7.1.4 Rate of the Period in Which the CPU Usage of the SCU Is Lower Than the Alarm Threshold........................3101
3.8 Measurement of XPU Performance(XPU)...............................................................................................................3102
3.8.1 XPU Measurement(XPU)......................................................................................................................................3102
3.8.1.1 Maximum CPU Usage of the XPU.....................................................................................................................3103
3.8.1.2 Average CPU Usage of the XPU........................................................................................................................3104
3.8.1.3 Rate of the Period in Which the CPU Usage of the XPU Exceeds the Alarm Threshold..................................3104
3.8.1.4 Rate of the Period in Which the CPU Usage of the XPU Is Lower Than the Alarm Threshold........................3105
3.8.1.5 Maximum Packet Usage of the XPU..................................................................................................................3106
3.8.1.6 Average Packet Usage of the XPU.....................................................................................................................3107
Issue 06 (2014-01-20) Huawei Proprietary and Confidential liv

BSC6900 UMTS
Performance Counter Reference 1 UMTS Radio Network Related Measurement
1 UMTS Radio Network Related

Measurement
About This Chapter
The following measurements are UMTS Radio Network Related Measurement.
Issue 06 (2014-01-20) Huawei Proprietary and Confidential 1

BSC6900 UMTS
1.1 Measurement of CNOPERATOR Performance

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

PLMN
RAB.Rel.PLMN.RNC Measurement of RAB assignment release per

PLMN
TRAFF.LOAD.PLMN.RNC Traffic Measurement of CN Operator per

RNC
1.1.1 Measurement of active algorithm per PLMN

(ALGO.PLMN.RNC)
Overview
Measurement is used to measure active algorithm of RNC for each Operator.
Counters
Counter ID Counter Name Counter Original Release
Description
73394050 VS.PI.HSDPA.TR Number of TRBs of V900R012

BNum.PLMN.RNC HSDPA Service on
Which Packet
Inspection (PI) Takes
Effect for RNC
Counter Relationship
None

BSC6900 UMTS
1.1.1.1 Number of TRBs of HSDPA Service on Which Packet Inspection (PI) Takes
Effect for RNC
Counters
Counter ID Counter Name Counter Description
73394050 VS.PI.HSDPA.TRBNum.PL Number of TRBs of HSDPA

MN.RNC Service on Which Packet
Inspection (PI) Takes Effect
for RNC
Description
This counter provides the number of TRBs of the HSDPA service on which the PI takes effect
under the RNC according to telecom operators.
It reflects whether the PI algorithm is used by telecom operators.
Measurement point
This counter provides the number of TRBs of the HSDPA service on which the PI takes effect
under the RNC according to telecom operators.This counter is incremented by one when the PI
takes effect.This counter is measured only once for one HSDPA session.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
VS.PI.HSDPA.TRBNum.PL WRFD-020128 Quality Improvement for

MN.RNC Subscribed Service

BSC6900 UMTS
1.1.2 Measurement of RAB assignment setup per PLMN

(RAB.Estab.PLMN.RNC)
Overview
This function subset provides the number of service setup requests and successful service setups
for different services of different operators. This enables the operators to monitor the RAB setup
conditions.
Counters
Description
67196186 VS.RAB.AttEstab. Number of AMR CS Earlier than

AMR.PLMN.RNC RABs Establishment V900R011
Requests for
Operator
67196187 VS.RAB.SuccEstab Number of AMR CS Earlier than

.AMR.PLMN.RNC RABs Successfully V900R011
Established for
Operator(WB+NB)
67196188 VS.RAB.AttEstab. Number of 64kbit/s Earlier than

CS64.PLMN.RNC CS Conversational V900R011
Service RABs
Establishment
Requests for
Operator
67196189 VS.RAB.SuccEstab Number of 64kbit/s Earlier than

.CS64.PLMN.RNC CS Conversational V900R011
Service RABs
Successfully
Established for
Operator
67196190 VS.RAB.AttEstab. Number of PS RABs Earlier than

PS.PLMN.RNC Establishment V900R011
Requests for
Operator
67196191 VS.RAB.SuccEstab Number of PS RABs Earlier than

.PS.PLMN.RNC Successfully V900R011
Established for
Operator
None

BSC6900 UMTS
1.1.2.1 Number of RABs Requested to Establish for each Operator
Counters
67196186 VS.RAB.AttEstab.AMR.PL Number of AMR CS RABs

MN.RNC Establishment Requests for
Operator
67196188 VS.RAB.AttEstab.CS64.PL Number of 64kbit/s CS

MN.RNC Conversational Service
RABs Establishment
Requests for Operator
67196190 VS.RAB.AttEstab.PS.PLM Number of PS RABs

N.RNC Establishment Requests for
Operator
Description
The measurement items provide the number of RABs requested to establish according to
different types of service for each operator, as shown below.
The following table describes the meaning of each counter.
Counter Name Description
VS.RAB.AttEstab.AMR.PLMN.RNC Number of AMR service RABs requested to

establish for each operator( narrowband and
wideband AMR services)
VS.RAB.AttEstab.CS64.PLMN.RNC Number of CS 64kbits/s conversational

service RABs requested to establish for each
operator
VS.RAB.AttEstab.PS.PLMN.RNC Number of PS RABs requested to establish

for each operator
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.

BSC6900 UMTS
Figure 1-1 RAB setup procedure
Formula
None
Unit
None
Related Features
VS.RAB.AttEstab.AMR.PL WRFD-021311 MOCN Introduction

MN.RNC WRFD-010501 Package
Conversational QoS Class
VS.RAB.AttEstab.CS64.PL WRFD-021311 MOCN Introduction

VS.RAB.AttEstab.PS.PLM WRFD-021311 MOCN Introduction

N.RNC WRFD-010510 Package
3.4/6.8/13.6/27.2Kbps RRC
Connection and Radio
Access Bearer Establishment
and Release

BSC6900 UMTS
1.1.2.2 Number of Successfully Established RABs for each Operator
Counters
67196187 VS.RAB.SuccEstab.AMR.P Number of AMR CS RABs

LMN.RNC Successfully Established for
Operator(WB+NB)
67196189 VS.RAB.SuccEstab.CS64.P Number of 64kbit/s CS

LMN.RNC Conversational Service
RABs Successfully
Established for Operator
67196191 VS.RAB.SuccEstab.PS.PL Number of PS RABs

MN.RNC Successfully Established for
Operator
Description
The measurement items provide the number of RABs successfully established according to
different types of service for each operator, as shown below.
VS.RAB.SuccEstab.AMR.PLMN.RNC Number of AMR service RABs successfully

established for each operator( narrowband
and wideband AMR services)
VS.RAB.SuccEstab.CS64.PLMN.RNC Number of CS 64kbits/s conversational

service RABs successfully established for
each operator
VS.RAB.SuccEstab.PS.PLMN.RNC Number of PS RABs successfully established

for each operator
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SuccEstab.AMR.P WRFD-021311 MOCN Introduction

LMN.RNC WRFD-010501 Package
VS.RAB.SuccEstab.CS64.P WRFD-021311 MOCN Introduction

VS.RAB.SuccEstab.PS.PL WRFD-021311 MOCN Introduction

3.4/6.8/13.6/27.2Kbps RRC
and Release

BSC6900 UMTS
1.1.3 Measurement of RAB assignment release per PLMN

(RAB.Rel.PLMN.RNC)
Overview
This function subset provides the number of normal service releases and abnormal service
releases for different services of different operators. This enables the operators to monitor the
RAB setup conditions.
Counters
Description
67196192 VS.RAB.AbnormR Number of Earlier than

el.AMR.PLMN.RN Abnormally V900R011
C Released AMR CS
RABs for Operator
67196193 VS.RAB.NormRel. Number of Normally Earlier than

AMR.PLMN.RNC Released AMR CS V900R011
RABs for Operator

el.CS64.PLMN.RN Abnormally V900R011
C Released 64kbit/s CS
Conversational
Service RABs for
Operator

CS64.PLMN.RNC Released 64kbit/s CS V900R011
Conversational
Service RABs for
Operator

el.PS.PLMN.RNC Abnormally V900R011
Released PS RABs
for Operator

PS.PLMN.RNC Released PS RABs V900R011
for Operator
None

BSC6900 UMTS
1.1.3.1 Number of Abnormally Released RABs for each Operator
Counters
67196192 VS.RAB.AbnormRel.AMR. Number of Abnormally

PLMN.RNC Released AMR CS RABs for
Operator
67196194 VS.RAB.AbnormRel.CS64. Number of Abnormally

PLMN.RNC Released 64kbit/s CS
Conversational Service
RABs for Operator
67196196 VS.RAB.AbnormRel.PS.PL Number of Abnormally

MN.RNC Released PS RABs for
Operator
Description
The measurement items take statistics of the number of abnormally released RABs of different
type services for each Operator.
VS.RAB.AbnormRel.AMR.PLMN.RNC Number of abnormally released AMR service

RABs for each operator(narrowband and
VS.RAB.AbnormRel.CS64.PLMN.RNC Number of abnormally released CS 64K

Conversational Service RABs for each
operator
VS.RAB.AbnormRel.PS.PLMN.RNC Number of abnormally released PS RABs for

each operator
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.

BSC6900 UMTS
Figure 1-3 RAB release procedure
RAB RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE
COMMAND message(with the cause other than "User Inactivity","Normal

BSC6900 UMTS
Figure 1-4 RAB release IU REL procedure
The measurement is triggered at point A as shown in the figure. The RNC sends to the CN an
IU RELEASE REQUEST message due to exception.If the RNC receives an IU RELEASE

BSC6900 UMTS
Figure 1-5 Iu connection release procedure
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.AMR. WRFD-021311 MOCN Introduction

PLMN.RNC WRFD-010501 Package
VS.RAB.AbnormRel.CS64. WRFD-021311 MOCN Introduction

VS.RAB.AbnormRel.PS.PL WRFD-021311 MOCN Introduction

3.4/6.8/13.6/27.2Kbps RRC
and Release

BSC6900 UMTS
1.1.3.2 Number of Normally Released RABs for each Operator
Counters
67196193 VS.RAB.NormRel.AMR.PL Number of Normally

MN.RNC Released AMR CS RABs for
Operator
67196195 VS.RAB.NormRel.CS64.PL Number of Normally

MN.RNC Released 64kbit/s CS
Conversational Service
RABs for Operator
67196197 VS.RAB.NormRel.PS.PLM Number of Normally

N.RNC Released PS RABs for
Operator
Description
The measurement items take statistics of the number of normally released RABs of different
type services for each Operator.
VS.RAB.NormRel.AMR.PLMN.RNC Number of normally released AMR service

RABs for each operator(narrowband and
VS.RAB.NormRel.CS64.PLMN.RNC Number of normally released CS 64kbit/s

Conversational Service RABs for each
operator
VS.RAB.NormRel.PS.PLMN.RNC Number of normally released PS RABs for

each operator
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.

BSC6900 UMTS
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
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.

BSC6900 UMTS
Figure 1-7 RAB release procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.AMR.PL WRFD-021311 MOCN Introduction

VS.RAB.NormRel.CS64.PL WRFD-021311 MOCN Introduction


BSC6900 UMTS
VS.RAB.NormRel.PS.PLM WRFD-021311 MOCN Introduction

N.RNC WRFD-010510 Package
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.1.4 Traffic Measurement of CN Operator per RNC

(TRAFF.LOAD.PLMN.RNC)
Overview
Traffic Measurement for each Operator is used to measure the traffic of CS domain and PS
domain of RNC for each Operator, and it contains the case of SHO. Where, the traffic of CS
domain is denoted by equivalent Erlang; the traffic of PS domain is expressed in kbit/s.
Counters
Description
67203962 VS.CSLoad.Erlang Equivalent CS Earlier than

.Equiv.PLMN.RNC Erlang for RNC per V900R011
Operator
67192511 VS.CSLoad.MaxEr Maximum Earlier than

lang.Equiv.PLMN. equivalent CS Erlang V900R011
RNC for RNC per
Operator
67204145 VS.R99PSLoad.UL Uplink PS R99 Earlier than

Thruput.PLMN.R Traffic for RNC per V900R011
NC Operator
67193010 VS.R99PSLoad.Ma Maximum Uplink PS Earlier than

xULThruput.PLM R99 Traffic for RNC V900R011
N.RNC per Operator
67204146 VS.R99PSLoad.DL Downlink PS R99 Earlier than

Thruput.PLMN.R Traffic for RNC per V900R011
NC Operator
67193013 VS.R99PSLoad.Ma Maximum Downlink Earlier than

xDLThruput.PLM PS R99 Traffic for V900R011
N.RNC RNC per Operator

BSC6900 UMTS

Description
67204147 VS.HSDPAPSLoad Downlink PS Earlier than

.DLThruput.PLM HSDPA Traffic for V900R011
N.RNC RNC per Operator
67193016 VS.HSDPAPSLoad Maximum Downlink Earlier than

.MaxDLThruput.P PS HSDPA Traffic V900R011
LMN.RNC for RNC per
Operator
67204148 VS.HSUPAPSLoad Uplink PS HSUPA Earlier than

.ULThruput.PLM Traffic for RNC per V900R011
N.RNC Operator
67193019 VS.HSUPAPSLoad Maximum Uplink PS Earlier than

.MaxULThruput.P HSUPA Traffic for V900R011
LMN.RNC RNC per Operator
67204149 VS.MBMSPSLoad. Downlink PS MBMS Earlier than

DLThruput.PLMN Traffic for RNC per V900R011
.RNC Operator
67193022 VS.MBMSPSLoad. Maximum Downlink Earlier than

MaxDLThruput.P PS MBMS Traffic V900R011
LMN.RNC for RNC per
Operator
67204835 VS.AMR.Erlang.E Equivalent Erlang of Earlier than

quiv.PLMN.RNC CS AMR Service for V900R011
RNC per Operator
67204836 VS.VP.Erlang.Equi Equivalent Erlang of Earlier than

v.PLMN.RNC 64kbit/s CS Service V900R011
for RNC per
Operator
67204840 VS.PS.CellDchUEs. Number of Earlier than

PLMN Cell_DCH UEs in PS V900R011
Domain for RNC per
Operator
73394023 VS.PSLoad.MaxTh Maximum Total V900R012

ruput.PLMN.RNC Throughout of UL
and DL PS Services
per Operator for
RNC
73410502 VS.PSLoad.Thrup Average Total V900R012

ut.PLMN.RNC Throughput of UL
and DL PS Services
per Operator for
RNC

BSC6900 UMTS

Description
73440109 VS.PS.CellFachUE Number of V900R012

s.PLMN Cell_FACH UEs in
PS Domain for RNC
per Operator
None
1.1.4.1 Equivalent Erlang of CS Domain of RNC for each Operator
Counters
67203962 VS.CSLoad.Erlang.Equiv.P Equivalent CS Erlang for

LMN.RNC RNC per Operator
Description
This measurement item provides the equivalent Erlang values of all services in the CS domain
of the RNC for each Operator. The item is measured only when the RAN sharing function or
MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the equivalent Erlang values of all services in the
CS domain for each Operator every five seconds. At the end of the measurement period, the
RNC calculates the mean sample (divide the accumulated value by the sampling times), include
the equivalent Erlang of all radio links of Soft Handover.Each time a CS domain service is
admitted, the RNC converts its rate to the equivalent Erlang, and then increases the equivalent
Erlang of the CS domain of the RNC. Each time a CS domain service is released, the RNC
decreases the equivalent Erlang of the CS domain of the RNC.
Formula
None
Unit
Erl

BSC6900 UMTS
Related Features
VS.CSLoad.Erlang.Equiv.P WRFD-021304 RAN Sharing Introduction

WRFD-02130404 MOCN Introduction

Package
Independent License Control
1.1.4.2 Maximum Equivalent Erlang of CS Domain of RNC for each Operator
Counters
67192511 VS.CSLoad.MaxErlang.Equ Maximum equivalent CS

iv.PLMN.RNC Erlang for RNC per Operator
Description
This measurement item provides the maximum equivalent Erlang values of all services in the
CS domain of the RNC for each Operator. The item is measured only when the RAN sharing
function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the equivalent Erlang values of all services in the
CS domain for each Operator every five seconds and calculates the maximum, include the
equivalent Erlang of all radio links of Soft Handover.Each time a CS domain service is admitted,
the RNC converts its rate to the equivalent Erlang, and then increases the equivalent Erlang of
the CS domain of the RNC. Each time a CS domain service is released, the RNC decreases the
equivalent Erlang of the CS domain of the RNC.
Formula
None
Unit
Erl

BSC6900 UMTS
Related Features
VS.CSLoad.MaxErlang.Equ WRFD-021304 RAN Sharing Introduction

iv.PLMN.RNC WRFD-021311 Package

Package
1.1.4.3 Uplink Traffic of R99 PS Domain of RNC for each Operator
Counters
67204145 VS.R99PSLoad.ULThruput. Uplink PS R99 Traffic for

PLMN.RNC RNC per Operator
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

BSC6900 UMTS
Related Features
VS.R99PSLoad.ULThruput. WRFD-021304 RAN Sharing Introduction


Package
1.1.4.4 Maximum Uplink Traffic of R99 PS Domain of RNC for each Operator
Counters
67193010 VS.R99PSLoad.MaxULThr Maximum Uplink PS R99

uput.PLMN.RNC Traffic for RNC per Operator
Description
This measurement item provides the maximum uplink traffic of all the R99 services in the PS
domain of the RNC for each Operator. The item is measured only when the RAN sharing function
or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the uplink traffic values (in kbit/s) of all the R99
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

BSC6900 UMTS
Related Features
VS.R99PSLoad.MaxULThr WRFD-021304 RAN Sharing Introduction

uput.PLMN.RNC WRFD-021311 Package

Package
1.1.4.5 Downlink Traffic of R99 PS Domain of RNC for each Operator
Counters
67204146 VS.R99PSLoad.DLThruput. Downlink PS R99 Traffic for

PLMN.RNC RNC per Operator
Description
This measurement item provides the downlink traffic of all the R99 services in the PS domain
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
times).The mean downlink traffic of all the R99 services in the PS domain is the traffic measured
Formula
None
Unit
kbit/s

BSC6900 UMTS
Related Features
VS.R99PSLoad.DLThruput. WRFD-021304 RAN Sharing Introduction


Package
1.1.4.6 Maximum Downlink Traffic of R99 PS Domain of RNC for each Operator
Counters
67193013 VS.R99PSLoad.MaxDLThr Maximum Downlink PS R99

uput.PLMN.RNC Traffic for RNC per Operator
Description
This measurement item provides the maximum downlink traffic of all the R99 services in the
PS domain of the RNC for each Operator. The item is measured only when the RAN sharing
Measurement point
The RNC periodically takes the samples of the downlink traffic values (in kbit/s) of all the R99
period, the RNC calculates the maximum sample value.The mean downlink traffic of all the R99
Formula
None
Unit
kbit/s

BSC6900 UMTS
Related Features
VS.R99PSLoad.MaxDLThr WRFD-021304 RAN Sharing Introduction

uput.PLMN.RNC WRFD-021311 Package

Package
1.1.4.7 Downlink Traffic of HSDPA PS Domain of RNC for each Operator
Counters
67204147 VS.HSDPAPSLoad.DLThru Downlink PS HSDPA

put.PLMN.RNC Traffic for RNC per Operator
Description
This measurement item provides the downlink traffic of all the HSDPA services in the PS domain
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

BSC6900 UMTS
Related Features
VS.HSDPAPSLoad.DLThru WRFD-021304 RAN Sharing Introduction

put.PLMN.RNC WRFD-021311 Package

Package
1.1.4.8 Maximum Downlink Traffic of HSDPA PS Domain of RNC for each

Operator
Counters
67193016 VS.HSDPAPSLoad.MaxDL Maximum Downlink PS

Thruput.PLMN.RNC HSDPA Traffic for RNC per
Operator
Description
This measurement item provides the maximum downlink traffic of all the HSDPA services in
the PS domain of the RNC for each Operator. The item is measured only when the RAN sharing
Measurement point
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

BSC6900 UMTS
Related Features
VS.HSDPAPSLoad.MaxDL WRFD-021304 RAN Sharing Introduction

Thruput.PLMN.RNC WRFD-021311 Package

Package
1.1.4.9 Uplink Traffic of HSUPA PS Domain of RNC for each Operator
Counters
67204148 VS.HSUPAPSLoad.ULThru Uplink PS HSUPA Traffic

put.PLMN.RNC for RNC per Operator
Description
This measurement item provides the uplink traffic of all the HSUPA services in the PS domain
Measurement point
The RNC periodically takes the samples of the uplink traffic values (in kbit/s) of all the HSUPA
times).The mean uplink traffic of all the HSUPA services in the PS domain is the traffic measured
Formula
None
Unit
kbit/s

BSC6900 UMTS
Related Features
VS.HSUPAPSLoad.ULThru WRFD-021304 RAN Sharing Introduction


Package
1.1.4.10 Maximum Uplink Traffic of HSUPA PS Domain of RNC for each Operator
Counters
67193019 VS.HSUPAPSLoad.MaxUL Maximum Uplink PS

Thruput.PLMN.RNC HSUPA Traffic for RNC per
Operator
Description
This measurement item provides the maximum uplink traffic of all the HSUPA services in the
Measurement point
The RNC periodically takes the samples of the uplink traffic values (in kbit/s) of all the HSUPA
period, the RNC calculates the maximum sample value.The mean uplink traffic of all the HSUPA
Formula
None
Unit
kbit/s

BSC6900 UMTS
Related Features
VS.HSUPAPSLoad.MaxUL WRFD-021304 RAN Sharing Introduction


Package
1.1.4.11 Downlink Traffic of MBMS or IMB PS Domain of RNC for each Operator
Counters
67204149 VS.MBMSPSLoad.DLThru Downlink PS MBMS Traffic

put.PLMN.RNC for RNC per Operator
Description
This measurement item provides the downlink traffic of all the MBMS or IMB services in the
Measurement point
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

BSC6900 UMTS
Related Features
VS.MBMSPSLoad.DLThru WRFD-021304 RAN Sharing Introduction


Package
1.1.4.12 Maximum Downlink Traffic of MBMS or IMB PS Domain of RNC for each
Operator
Counters
67193022 VS.MBMSPSLoad.MaxDL Maximum Downlink PS

Thruput.PLMN.RNC MBMS Traffic for RNC per
Operator
Description
This measurement item provides the maximum downlink traffic of all the MBMS or IMB
services in the PS domain of the RNC for each Operator. The item is measured only when the
RAN sharing function or MOCN function is switched on.
Measurement point
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

BSC6900 UMTS
Related Features
VS.MBMSPSLoad.MaxDL WRFD-021304 RAN Sharing Introduction


Package
WRFD-010616
MBMS Introduction
Package
1.1.4.13 Equivalent Erlang of CS Domain AMR Service of RNC for each Operator
Counters
67204835 VS.AMR.Erlang.Equiv.PL Equivalent Erlang of CS

MN.RNC AMR Service for RNC per
Operator
Description
This measurement item provides the equivalent Erlang values of AMR services(narrowband and
wideband AMR services)in the CS domain of the RNC for each Operator. The item is measured
only when the RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the equivalent Erlang values of AMR services in the
CS domain for each Operator every five seconds. At the end of the measurement period, the
RNC calculates the mean sample (divide the accumulated value by the sampling times), include
the equivalent Erlang of all radio links of Soft Handover. Each time a CS domain AMR service
is admitted, the RNC converts its rate to the equivalent Erlang, and then increases the equivalent
Erlang of the CS domain of the RNC. Each time a CS domain AMR service is released, the RNC
decreases the equivalent Erlang of the CS domain of the RNC.
Formula
None
Unit
Erl

BSC6900 UMTS
Related Features
VS.AMR.Erlang.Equiv.PL WRFD-021304 RAN Sharing Introduction


Package
1.1.4.14 Equivalent Erlang of CS Domain CS 64kbit/s Conversational Service of

RNC for each Operator
Counters
67204836 VS.VP.Erlang.Equiv.PLMN Equivalent Erlang of 64kbit/

.RNC s CS Service for RNC per
Operator
Description
This measurement item provides the equivalent Erlang values of CS 64kbit/s Conversational
Services in the CS domain of the RNC for each Operator. The item is measured only when the
RAN sharing function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the equivalent Erlang values of CS 64kbit/s
Conversational Services in the CS domain for each Operator every five seconds. At the end of
the measurement period, the RNC calculates the mean sample (divide the accumulated value by
the sampling times), include the equivalent Erlang of all radio links of Soft Handover. Each time
a CS domain CS 64kbit/s Conversational Service is admitted, the RNC converts its rate to the
equivalent Erlang, and then increases the equivalent Erlang of the CS domain of the RNC. Each
time a CS domain CS 64kbit/s Conversational Service is released, the RNC decreases the
equivalent Erlang of the CS domain of the RNC.
Formula
None
Unit
Erl

BSC6900 UMTS
Related Features
VS.VP.Erlang.Equiv.PLMN WRFD-021304 RAN Sharing Introduction

.RNC WRFD-021311 Package

Package
1.1.4.15 The Number of Cell_DCH UEs in PS Domain in RNC
Counters
67204840 VS.PS.CellDchUEs.PLMN Number of Cell_DCH UEs in

PS Domain for RNC per
Operator
Description
This measurement item provides the mean number of Cell_DCH UEs in the PS domain of the
RNC for each Operator.
Measurement point
The RNC periodically takes the samples of the number of Cell_DCH UEs in the PS domain for
each Operator every five seconds. At the end of the measurement period, the RNC calculates
the mean sample (divide the accumulated value by the sampling times). When the Cell_DCH
UEs join the PS operation for the first time, add the number of UEs. When all the PS operations
are released, subtract the number of UEs
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.PS.CellDchUEs.PLMN WRFD-021304 RAN Sharing Introduction

WRFD-021311 Package

Package
1.1.4.16 Maximum Total Throughout of UL and DL PS Services per Operator for

RNC
Counters
73394023 VS.PSLoad.MaxThruput.PL Maximum Total Throughout

MN.RNC of UL and DL PS Services
per Operator for RNC
Description
This counter provides the maximum total throughout of UL and DL PS services of an operator
in the RNC. The item is measured only when the RAN sharing function or MOCN function is
switched on.
Measurement point
The total throughput (unit: Kbit/s) of UL and DL PS services of the operator in the RNC is
sampled periodically every five seconds. At the end of the measurement period, the maximum
throughput is obtained. The RLC header is not included and the retransmission data is included
in the counter.
Formula
None
Unit
kbit/s

BSC6900 UMTS
Related Features
VS.PSLoad.MaxThruput.PL WRFD-021304 RAN Sharing Introduction


Package
1.1.4.17 Average Total Throughput of UL and DL PS Services per Operator for RNC
Counters
73410502 VS.PSLoad.Thruput.PLMN. Average Total Throughput of

RNC UL and DL PS Services per
Operator for RNC
Description
This counter provides the average total throughput of UL and DL PS services of an operator in
the RNC. The item is measured only when the RAN sharing function or MOCN function is
switched on.
Measurement point
The total throughput of UL and DL PS services of an operator in the RNC is sampled and
accumulated periodically every five seconds. At the end of the measurement period, the average
throughput is obtained as follows: dividing the accumulated throughput by the sampling times.
The RLC header is not included and the retransmission data is included in the counter.
Formula
None
Unit
kbit/s

BSC6900 UMTS
Related Features
VS.PSLoad.Thruput.PLMN. WRFD-021304 RAN Sharing Introduction

RNC WRFD-021311 Package

Package
1.1.4.18 The Number of Cell_FACH UEs in PS Domain in RNC
Counters
73440109 VS.PS.CellFachUEs.PLMN Number of Cell_FACH UEs

in PS Domain for RNC per
Operator
Description
This measurement item provides the mean number of Cell_FACH UEs in the PS domain of the
RNC for each Operator.
Measurement point
The RNC periodically takes the samples of the number of Cell_FACH UEs in the PS domain
for each Operator every five seconds. At the end of the measurement period, the RNC calculates
the mean sample (divide the accumulated value by the sampling times). When the Cell_FACH
UEs join the PS operation for the first time, add the number of UEs. When all the PS operations
are released, subtract the number of UEs.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.PS.CellFachUEs.PLMN WRFD-021304 RAN Sharing Introduction

WRFD-021311 Package

Package
1.2 Measurement of CPUS Performance(CPUS)

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

BSC6900 UMTS
If the value of a flow control-related counter increases dramatically in a period, check whether
a signaling storm has occurred in the corresponding period.
Counters
Description

.Equiv.CPUS Conversational V900R011
Erlang for CPUS
67193077 VS.RRC.AttConnE Number of RRC Earlier than

stab.CPUS Connection Requests V900R011
for CPUS
67193078 VS.RRC.SuccConn Number of Earlier than

Estab.CPUS Successful RRC V900R011
Connection
Establishments for
CPUS
67193079 VS.RAB.AttEstab. Number of CS AMR Earlier than

AMR.CPUS RAB Establishing V900R011
Requests for CPUS
67193080 VS.RAB.SuccEstab Number of CS AMR Earlier than

.AMR.CPUS RABs Successfully V900R011
Established for
CPUS
67193081 VS.RAB.AttEstab. Number of CS Earlier than

CS64.CPUS 64kbit/s RAB V900R011
Establishing
Requests for CPUS
67193082 VS.RAB.SuccEstab Number of CS Earlier than

.CS64.CPUS 64kbit/s RABs V900R011
Successfully
Established for
CPUS
67193083 VS.HSDPA.RAB.A Number of HSDPA Earlier than

ttEstab.CPUS RAB Establishing V900R011
Requests for CPUS
67193084 VS.HSDPA.RAB.S Number of HSDPA Earlier than

uccEstab.CPUS RABs Successfully V900R011
Established for
CPUS

BSC6900 UMTS

Description
67193085 VS.HSUPA.RAB.A Number of HSUPA Earlier than

ttEstab.CPUS RAB Establishing V900R011
Requests for CPUS
67193086 VS.HSUPA.RAB.S Number of HSUPA Earlier than

uccEstab.CPUS RABs Successfully V900R011
Established for
CPUS
67193087 VS.RAB.AttEstabP Number of PS RAB Earlier than

S.CPUS Establishing V900R011
Requests for CPUS

PS.CPUS Successfully V900R011
Established for
CPUS

el.AMR.CPUS Abnormally V900R011
Released CS AMR
RABs for CPUS

AMR.CPUS Released CS AMR V900R011
RABs for CPUS

el.CS64.CPUS Abnormally V900R011
Released CS 64kbit/s
RABs for CPUS

CS64.CPUS Released CS 64kbit/s V900R011
RABs for CPUS

el.PS.CPUS Abnormally V900R011
Released PS RABs
for CPUS

PS.CPUS Released PS RABs V900R011
for CPUS
73421896 VS.CBS.FC.Disc.N Number of CBS V900R012

um.CPUS Requests Discarded
Due to Flow Control
for CPUS Subsystem

BSC6900 UMTS

Description
73421897 VS.CBS.FC.Disc.Ti Duration of CBS V900R012

me.CPUS Flow Control for
CPUS Subsystem
73421898 VS.Paging.FC.Disc. Number of Paging V900R012

Num.CPUS Messages Discarded
Due to Flow Control
for CPUS Subsystem
73421899 VS.Paging.FC.Disc. Duration of Paging V900R012

Time.CPUS Message Flow
Control for CPUS
Subsystem
73421900 VS.CU.FC.Disc.Nu Number of Cell V900R012

m.CPUS Update Requests
Discarded Due to
Flow Control for
CPUS Subsystem
73421901 VS.CU.FC.Disc.Ti Duration of Cell V900R012

me.CPUS Update Flow Control
for CPUS Subsystem
73423464 VS.RRC.FC.Disc.N Number of V900R013

um.CallShock.CPU Discarded RRC
S Connection Requests
Due to Burst Traffic
for CPUS Subsystem

um.MPU.CPUS Discarded RRC
Connection Requests
Due to MPU
Overload for CPUS
Subsystem

um.RRCQueue.CP Discarded RRC
US Connection Requests
Due to RRC Queue
Overflow for CPUS
Subsystem

um.CPU.CPUS Discarded RRC
Connection Requests
Due to High CPU
Usage for CPUS
Subsystem

BSC6900 UMTS

Description
73421890 VS.LowPriRRC.F Number of Low- V900R012

C.Disc.Num.CPUS Priority RRC
Requests Discarded
Due to Flow Control
for CPUS Subsystem
73421891 VS.NormPriRRC.F Number of Normal- V900R012

Requests Discarded
Due to Flow Control
for CPUS Subsystem
73421892 VS.HighPriRRC.F Number of High- V900R012

Requests Discarded
Due to Flow Control
for CPUS Subsystem
73421893 VS.LowPriRRC.F Duration of V900R012

C.Disc.Time.CPUS Rejection of Low-
Priority RRC
Requests Due to
Flow Control for
CPUS Subsystem
73421894 VS.NormPriRRC.F Duration of V900R012

C.Disc.Time.CPUS Rejection of Normal-
Priority RRC
Requests Due to
Flow Control for
CPUS Subsystem
73421895 VS.HighPriRRC.F Duration of V900R012

C.Disc.Time.CPUS Rejection of High-
Priority RRC
Requests Due to
Flow Control for
CPUS Subsystem
73423921 VS.LowPriCu.FC. Number of Low- V900R014

Disc.Num.CPU Priority CELL
UPDATE Messages
Discarded Because
CPU Usage Exceeds
the Threshold for
CPUS Subsystem

BSC6900 UMTS

Description
73423923 VS.MidPriCu.FC. Number of Medium- V900R014

UPDATE Messages
Discarded Because
CPU Usage Exceeds
the Threshold for
CPUS Subsystem
73423924 VS.HighPriCu.FC. Number of High- V900R014

UPDATE Messages
Discarded Because
CPU Usage Exceeds
the Threshold for
CPUS Subsystem
73423925 VS.LowPriCu.FC. Number of Low- V900R014

Disc.Num.Queue Priority CELL
UPDATE Messages
Discarded Due to
RRC Queue
Overflow for CPUS
Subsystem
73423926 VS.MidPriCu.FC. Number of Medium- V900R014

UPDATE Messages
Discarded Due to
RRC Queue
Overflow for CPUS
Subsystem
73423927 VS.HighPriCu.FC. Number of High- V900R014

UPDATE Messages
Discarded Due to
RRC Queue
Overflow for CPUS
Subsystem
73423928 VS.Traffic.Report4 Number of V900R014

A.CellDch.Disc.Nu Discarded UL Event
m.UpLink.FC 4A Measurement
Reports on PS BE
Traffic in the
CELL_DCH State in
a CPUS

BSC6900 UMTS

Description

A.CellDch.Disc.Nu Discarded DL Event
m.DownLink.FC 4A Measurement
Reports on PS BE
Traffic in the
CELL_DCH State in
a CPUS
73423930 VS.Throughput.Re Number of V900R014

port4A.Disc.Num. Discarded UL Event
UpLink.FC 4A Measurement
Reports on
Throughput for UEs
in the CELL_DCH
State in a CPUS

A.CellFach.Disc.Nu Discarded UL Event
m.UpLink.FC 4A Measurement
Reports on PS BE
Traffic in the
CELL_FACH State
in a CPUS

A.CellFach.Disc.Nu Discarded DL Event
m.DownLink.FC 4A Measurement
Reports on PS BE
Traffic in the
CELL_FACH State
in a CPUS
73424215 VS.RRC.FC.Num. Number of RRC V900R014

CPU.CPUS CONNECTION
REQUESTS Under
Flow Control Due to
High CPU Usage for
CPUS Subsystem

RRCQueue.CPUS CONNECTION
REQUESTS Under
Flow Control Due to
RRC Queue
Overflow for CPUS
Subsystem

BSC6900 UMTS

Description

MPU.CPUS CONNECTION
REQUESTS Under
Flow Control Due to
MPU Overload for
CPUS Subsystem

CallShock.CPUS CONNECTION
REQUESTS Under
Flow Control Due to
Burst Traffic for
CPUS Subsystem
73424219 VS.RRC.CONV.F Number of RRC V900R014

C.Num.CPU.CPUS CONNECTION
REQUESTS for CS
Services Under Flow
Control Due to High
CPU Usage for
CPUS Subsystem

C.Num.RRCQueue CONNECTION
.CPUS REQUESTS for CS
Services Under Flow
Control Due to RRC
Queue Overflow for
CPUS Subsystem

C.Num.MPU.CPU CONNECTION
S REQUESTS for CS
Services Under Flow
Control Due to MPU
Overload for CPUS
Subsystem

C.Num.CallShock. CONNECTION
CPUS REQUESTS for CS
Services Under Flow
Control Due to Burst
Traffic for CPUS
Subsystem

BSC6900 UMTS

Description

C.Num.INT.CPUS CONNECTION
REQUESTS for CS
Services in a CPUS
Subsystem Under
Flow Control
Triggered by
Interface-Board CPU
Overload
73424483 VS.RRC.FC.Num.I Number of RRC V900R014

NT.CPUS CONNECTION
REQUESTS in a
CPUS Subsystem
Under Flow Control
Triggered by
Interface-Board CPU
Overload
73424484 VS.IurUpLinkSig. Number of V900R014

Disc.Num.CPU.CP Discarded Iur-
US Interface Uplink
Signalling Messages
in a CPUS
Subsystem Under
Flow Control
Triggered by CPU
Overload
73424485 VS.IurDownLinkSi Number of V900R014

g.Disc.Num.CPU.C Discarded Iur-
PUS Interface Downlink
Signalling Messages
in a CPUS
Subsystem Under
Flow Control
Triggered by CPU
Overload

BSC6900 UMTS
Counter Sub Counter
VS.CU.FC.Disc.Num.CPUS VS.LowPriCu.FC.Disc.Num.CPU
VS.MidPriCu.FC.Disc.Num.CPU
VS.HighPriCu.FC.Disc.Num.CPU
VS.LowPriCu.FC.Disc.Num.Queue
VS.MidPriCu.FC.Disc.Num.Queue
VS.HighPriCu.FC.Disc.Num.Queue
1.2.1.1 Measurement of CS-Domain Equivalent Erlang of Each Subsystem in the

RNC
Counters
67203413 VS.CSLoad.Erlang.Equiv.C Equivalent CS

PUS Conversational Erlang for
CPUS
Description
This measurement counter provides the equivalent Erlang of all CS-domain services of each
subsystem in the RNC.
Measurement point
The RNC takes samples on the equivalent Erlang of all CS-domain services of each subsystem
in the RNC every five seconds. At the end of the measurement period, the RNC divides the
accumulated value of all sampling data in the measurement period by the number of sampling
times to obtain the equivalent Erlang of all CS-domain services of each subsystem in the RNC,
include the equivalent Erlang of all radio links of Soft Handover.When a CS-domain service
accesses the RNC, the service rate is converted into equivalent Erlang, and then the CS-domain
equivalent Erlang of the corresponding subsystem in the current RNC is increased. When a 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

BSC6900 UMTS
Related Features
VS.CSLoad.Erlang.Equiv.C WRFD-040100 Flow Control

PUS
1.2.1.2 Number of RRC Connection Requests in the CPUS subsystem
Counters
67193077 VS.RRC.AttConnEstab.CP Number of RRC Connection

US Requests for CPUS
Description
This measurement counter provides the number of RRC CONNECTION REQUEST messages
processed by the RNC in the CPUS subsystem, excluding cases that such request is rejected
because of redirection based on specific services, redirection based on inter-RAT and inter-
frequency distance, or redirection based on macro & micro joint inter-frequency.
Measurement point
At point A in Figure, after the RNC receives a RRC CONNECTION REQUEST message from
the UE, if the message is processed by the RNC (that is, the RNC requests a resource and attempts
to set up the RRC connection) and the message is not repeatedly reported by the same UE,
excluding cases that such request is rejected because of redirection based on specific services,
redirection based on inter-RAT and inter-frequency distance, or redirection based on macro &
micro joint inter-frequency, the measurement is triggered in the CPUS subsystem.

BSC6900 UMTS
Figure 1-8 RRC connection setup process
Formula
None
Unit
None
Related Features
VS.RRC.AttConnEstab.CP WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

US Connection and Radio
and Release
1.2.1.3 Number of Successful RRC Connection Setups in the CPUS subsystem

BSC6900 UMTS
Counters
67193078 VS.RRC.SuccConnEstab.C Number of Successful RRC

PUS Connection Establishments
for CPUS
Description
This measurement counter provides the number of RRC CONNECTION SETUP COMPLETE
messages received by the RNC in the CPUS subsystem.
Measurement point
The measurement is triggered at point C, as shown in Figure . After the RNC receives a RRC
CONNECTION SETUP COMPLETE message from an UE, the measurement is triggered in the
corresponding CPUS subsystem.
Figure 1-9 RRC connection setup process
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RRC.SuccConnEstab.C WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

PUS Connection and Radio
and Release
1.2.1.4 Number of CS RAB Requests in the CPUS subsystem
Counters
67193079 VS.RAB.AttEstab.AMR.CP Number of CS AMR RAB

US Establishing Requests for
CPUS
67193081 VS.RAB.AttEstab.CS64.CP Number of CS 64kbit/s RAB

US Establishing Requests for
CPUS
67193083 VS.HSDPA.RAB.AttEstab. Number of HSDPA RAB

CPUS Establishing Requests for
CPUS
67193085 VS.HSUPA.RAB.AttEstab. Number of HSUPA RAB

CPUS Establishing Requests for
CPUS
67193087 VS.RAB.AttEstabPS.CPUS Number of PS RAB

Establishing Requests for
CPUS
Description
These measurement counters provide the number of RAB requests in the CPUS subsystem
according to the service type.
VS.RAB.AttEstab.AMR.CPUS Number of CS AMR RAB Establishing

Requests. Includeing narrowband and
wideband AMR services.

BSC6900 UMTS
VS.RAB.AttEstab.CS64.CPUS Number of CS 64kbit/s RAB Establishing

Requests
VS.HSDPA.RAB.AttEstab.CPUS 1.Number of RABs that are carried over the

HSDPA channel or EFACH in the downlink;
2.The RABs can be CS or PS RABs;
3.The uplink channel carrying the RABs can
be ignored.
VS.HSUPA.RAB.AttEstab.CPUS 1.Number of RABs that are carried over the

HSUPA channel or ERACH in the uplink;
2.The RABs can be CS or PS RABs;
3.The downlink channel carrying the RABs
can be ignored.
VS.RAB.AttEstabPS.CPUS 1.Number of PS RAB Establishing Requests;

2.The uplink or downlink channel carrying
the RABs can be ignored.
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.
Figure 1-10 RAB setup process

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AttEstab.AMR.CP WRFD-010501 Conversational QoS Class

US
VS.RAB.AttEstab.CS64.CP WRFD-010501 Conversational QoS Class

US
VS.HSDPA.RAB.AttEstab. WRFD-01061008 Interactive and Background

CPUS WRFD-010630 Traffic Class on HSDPA
Streaming Traffic Class on
HSDPA
VS.HSUPA.RAB.AttEstab. WRFD-01061206 Interactive and Background

CPUS WRFD-010632 Traffic Class on HSUPA
HSUPA
VS.RAB.AttEstabPS.CPUS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.2.1.5 Number of CS RABs successfully established in the CPUS subsystem
Counters
67193080 VS.RAB.SuccEstab.AMR.C Number of CS AMR RABs

PUS Successfully Established for
CPUS
67193082 VS.RAB.SuccEstab.CS64.C Number of CS 64kbit/s

PUS RABs Successfully
Established for CPUS

BSC6900 UMTS
67193084 VS.HSDPA.RAB.SuccEstab Number of HSDPA RABs

.CPUS Successfully Established for
CPUS
67193086 VS.HSUPA.RAB.SuccEstab Number of HSUPA RABs

.CPUS Successfully Established for
CPUS
67193088 VS.RAB.SuccEstabPS.CPU Number of PS RABs

S Successfully Established for
CPUS
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
Figure 1-11 RAB setup process

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SuccEstab.AMR.C WRFD-010501 Conversational QoS Class

PUS
VS.RAB.SuccEstab.CS64.C WRFD-010501 Conversational QoS Class

PUS
VS.HSDPA.RAB.SuccEstab WRFD-01061008 Interactive and Background

.CPUS WRFD-010630 Traffic Class on HSDPA
HSDPA
VS.HSUPA.RAB.SuccEstab WRFD-01061206 Interactive and Background

.CPUS WRFD-010632 Traffic Class on HSUPA
HSUPA
VS.RAB.SuccEstabPS.CPU WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

S Connection and Radio
and Release
1.2.1.6 Number of RABs Abnormally Released in the CPUS subsystem
Counters

CPUS Released CS AMR RABs for
CPUS
67193091 VS.RAB.AbnormRel.CS64. Number of Abnormally

CPUS Released CS 64kbit/s RABs
for CPUS
67193093 VS.RAB.AbnormRel.PS.CP Number of Abnormally

US Released PS RABs for CPUS

BSC6900 UMTS
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
Connection Release", reference to 3GPP TS 25.413),the RNC measures the items by the service
type in the corresponding CPUS subsystem.

BSC6900 UMTS

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.AMR. WRFD-010501 Conversational QoS Class

CPUS
VS.RAB.AbnormRel.CS64. WRFD-010501 Conversational QoS Class

CPUS
VS.RAB.AbnormRel.PS.CP WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

US Connection and Radio
and Release
1.2.1.7 Number of RABs Normally Released in the CPUS subsystem

BSC6900 UMTS
Counters
67193090 VS.RAB.NormRel.AMR.CP Number of Normally

US Released CS AMR RABs for
CPUS
67193092 VS.RAB.NormRel.CS64.CP Number of Normally

US Released CS 64kbit/s RABs
for CPUS
67193094 VS.RAB.NormRel.PS.CPU Number of Normally

S Released PS RABs for CPUS
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
is "User Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE
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.

BSC6900 UMTS
Figure 1-15 Iu release procedure
If the RAB ASSIGNMENT REQUEST message indicates the reason is "User
Inactivity","Normal Release","Successful Relocation","Network Optimization" or "UE
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.

BSC6900 UMTS
Figure 1-16 RAB assignment release procedure
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.AMR.CP WRFD-010501 Conversational QoS Class

US
VS.RAB.NormRel.CS64.CP WRFD-010501 Conversational QoS Class

US
VS.RAB.NormRel.PS.CPU WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

S Connection and Radio
and Release

BSC6900 UMTS
1.2.1.8 Number of CBS Requests Discarded Due to Flow Control for CPUS
Subsystem
Counters
73421896 VS.CBS.FC.Disc.Num.CPU Number of CBS Requests

S Discarded Due to Flow
Control for CPUS Subsystem
Description
This counter provides the number of times that a cell broadcast service (CBS) request message
is discarded due to flow control.
Measurement point
When receiving a data request from the CBS server, the CPUS subsystem discards the CBS
request if the CPUS subsystem is under the CBS flow control. The measurement is triggered in
the CPUS subsystem when the CBS request is discarded.
Formula
None
Unit
None
Related Features
VS.CBS.FC.Disc.Num.CPU WRFD-040100 Flow Control

S
1.2.1.9 Duration of CBS Flow Control for CPUS Subsystem
Counters
73421897 VS.CBS.FC.Disc.Time.CPU Duration of CBS Flow

S Control for CPUS Subsystem

BSC6900 UMTS
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
VS.CBS.FC.Disc.Time.CPU WRFD-040100 Flow Control

S
1.2.1.10 Number of Paging Messages Discarded Due to Flow Control for CPUS
Subsystem
Counters
73421898 VS.Paging.FC.Disc.Num.C Number of Paging Messages

PUS Discarded Due to Flow
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.Paging.FC.Disc.Num.C WRFD-040100 Flow Control

PUS
1.2.1.11 Duration of Paging Message Flow Control for CPUS Subsystem
Counters
73421899 VS.Paging.FC.Disc.Time.C Duration of Paging Message

PUS Flow Control for CPUS
Subsystem
Description
This counter provides the duration of paging message flow control in the CPUS subsystem.
Measurement point
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

BSC6900 UMTS
Related Features
VS.Paging.FC.Disc.Time.C WRFD-040100 Flow Control

PUS
1.2.1.12 Number of Cell Update Requests Discarded Due to Flow Control for CPUS
Subsystem
Counters
73421900 VS.CU.FC.Disc.Num.CPUS Number of Cell Update

Requests Discarded Due to
Flow Control for CPUS
Subsystem
Description
This counter provides the number of times that a cell update request message is discarded due
to flow control.
Measurement point
When receiving a cell update request from the UE, the CPUS subsystem discards the cell update
request if the CPUS subsystem is under the cell update flow control. The measurement is
triggered in the CPUS subsystem when the cell update request is discarded.
Formula
None
Unit
None
Related Features
VS.CU.FC.Disc.Num.CPUS WRFD-040100 Flow Control
1.2.1.13 Duration of Cell Update Flow Control for CPUS Subsystem

BSC6900 UMTS
Counters
73421901 VS.CU.FC.Disc.Time.CPU Duration of Cell Update

S Flow Control for CPUS
Subsystem
Description
This counter provides the duration of cell update flow control in the CPUS subsystem.
Measurement point
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
VS.CU.FC.Disc.Time.CPU WRFD-040100 Flow Control

S
1.2.1.14 Number of Discarded RRC Connection Requests Due to Various Flow

Control Functions
Counters
73423464 VS.RRC.FC.Disc.Num.Call Number of Discarded RRC

Shock.CPUS Connection Requests Due to
Burst Traffic for CPUS
Subsystem

BSC6900 UMTS
73423465 VS.RRC.FC.Disc.Num.MP Number of Discarded RRC

U.CPUS Connection Requests Due to
MPU Overload for CPUS
Subsystem
73423466 VS.RRC.FC.Disc.Num.RR Number of Discarded RRC

CQueue.CPUS Connection Requests Due to
RRC Queue Overflow for
CPUS Subsystem
73423467 VS.RRC.FC.Disc.Num.CPU Number of Discarded RRC

.CPUS Connection Requests Due to
High CPU Usage for CPUS
Subsystem
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
VS.RRC.FC.Disc.Num.Call WRFD-040100 Flow Control

Shock.CPUS

BSC6900 UMTS
VS.RRC.FC.Disc.Num.MP WRFD-040100 Flow Control

U.CPUS
VS.RRC.FC.Disc.Num.RR WRFD-040100 Flow Control

CQueue.CPUS
VS.RRC.FC.Disc.Num.CPU WRFD-040100 Flow Control

.CPUS
1.2.1.15 Number of Various Priority RRC Requests Discarded Due to Flow Control
for CPUS Subsystem
Counters
73421890 VS.LowPriRRC.FC.Disc.Nu Number of Low-Priority

m.CPUS RRC Requests Discarded
Due to Flow Control for
CPUS Subsystem
73421891 VS.NormPriRRC.FC.Disc.N Number of Normal-Priority

um.CPUS RRC Requests Discarded
CPUS Subsystem
73421892 VS.HighPriRRC.FC.Disc.N Number of High-Priority

um.CPUS RRC Requests Discarded
CPUS Subsystem
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

BSC6900 UMTS
directly and measures the number of discarded RRC connection requests for the corresponding
service priority.
Formula
None
Unit
None
Related Features
VS.LowPriRRC.FC.Disc.Nu WRFD-040100 Flow Control

m.CPUS
VS.NormPriRRC.FC.Disc.N WRFD-040100 Flow Control

um.CPUS
VS.HighPriRRC.FC.Disc.N WRFD-040100 Flow Control

um.CPUS
1.2.1.16 Duration of Rejection of Various Priority RRC Requests Due to Flow

Counters
73421893 VS.LowPriRRC.FC.Disc.Ti Duration of Rejection of

me.CPUS Low-Priority RRC Requests
CPUS Subsystem
73421894 VS.NormPriRRC.FC.Disc.T Duration of Rejection of

ime.CPUS Normal-Priority RRC
Requests Due to Flow
73421895 VS.HighPriRRC.FC.Disc.Ti Duration of Rejection of

me.CPUS High-Priority RRC Requests
CPUS Subsystem

BSC6900 UMTS
Description
These counters provide the duration for which the RRC connection requests of various priorities
are rejected because of flow control.
Measurement point
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
VS.LowPriRRC.FC.Disc.Ti WRFD-040100 Flow Control

me.CPUS
VS.NormPriRRC.FC.Disc.T WRFD-040100 Flow Control

ime.CPUS
VS.HighPriRRC.FC.Disc.Ti WRFD-040100 Flow Control

me.CPUS
1.2.1.17 Number of Various Priority CELL_UPDATE Messages Discarded Because

CPU Usage Exceeds the Threshold in a CPUS
Counters
73423921 VS.LowPriCu.FC.Disc.Num Number of Low-Priority

.CPU CELL UPDATE Messages
Discarded Because CPU
Usage Exceeds the Threshold
for CPUS Subsystem

BSC6900 UMTS
73423923 VS.MidPriCu.FC.Disc.Num Number of Medium-Priority

.CPU CELL UPDATE Messages
for CPUS Subsystem
73423924 VS.HighPriCu.FC.Disc.Nu Number of High-Priority

m.CPU CELL UPDATE Messages
for CPUS Subsystem
Description
These counters provide the number of CELL_UPDATE messages discarded because CPU usage
exceeds the threshold in a CPU subsystem (CPUS). These counters are measured by message
priority.In a later version, this counter is to be replaced by the counters
VS.CU.FC.Num.CPU.OverLoad (ID 73424232) and VS.CU.CONV.FC.Num.CPU.OverLoad
(ID 73424917). In the current version, this counter is reserved but cannot work. Therefore, the
value of this counter is 0 and you are advised to use new counters.
Measurement point
The measurement is triggered when CELL_UPDATE messages are discarded because CPU
usage or the ratio of messages waiting in a queue in the CPUS reaches the corresponding
threshold. The RNC prioritizes the received CELL_UPDATE messages into high, medium, and
low based on the cause value for service setup carried in the extended information element
UU_CELL_UPT_V590EXT_STRU and the cause value for cell update.
Figure 1-17 CPU Usage-based Flow Control on CELL_UPDATE Messages

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.LowPriCu.FC.Disc.Num WRFD-040100 Flow Control

.CPU
VS.MidPriCu.FC.Disc.Num WRFD-040100 Flow Control

.CPU
VS.HighPriCu.FC.Disc.Nu WRFD-040100 Flow Control

m.CPU
1.2.1.18 Number of Various Priority CELL_UPDATE Messages Discarded Due to

Queue-based Shaping in a CPUS
Counters
73423925 VS.LowPriCu.FC.Disc.Num Number of Low-Priority

.Queue CELL UPDATE Messages
Discarded Due to RRC
Queue Overflow for CPUS
Subsystem
73423926 VS.MidPriCu.FC.Disc.Num Number of Medium-Priority

.Queue CELL UPDATE Messages
Subsystem
73423927 VS.HighPriCu.FC.Disc.Nu Number of High-Priority

m.Queue CELL UPDATE Messages
Subsystem

BSC6900 UMTS
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 Flow Control on CELL_UPDATE Messages Due to Queue-based Shaping
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.LowPriCu.FC.Disc.Num WRFD-040100 Flow Control

.Queue
VS.MidPriCu.FC.Disc.Num WRFD-040100 Flow Control

.Queue
VS.HighPriCu.FC.Disc.Nu WRFD-040100 Flow Control

m.Queue
1.2.1.19 Number of Discarded Event 4A Measurement Reports on PS BE Traffic in

the CELL_DCH State
Counters
73423928 VS.Traffic.Report4A.CellD Number of Discarded UL

ch.Disc.Num.UpLink.FC Event 4A Measurement
Reports on PS BE Traffic in
the CELL_DCH State in a
CPUS
73423929 VS.Traffic.Report4A.CellD Number of Discarded DL

ch.Disc.Num.DownLink.FC Event 4A Measurement
the CELL_DCH State in a
CPUS
Description
These counters provide the number of discarded event 4A measurement reports on PS BE traffic
in the CELL_DCH state in a CPU subsystem (CPUS) due to flow control.
Measurement point
Measurement of the counter VS.Traffic.Report4A.CellDch.Disc.Num.UpLink.FC is triggered
when the RNC discards the event 4A measurement report from a UE on PS BE traffic in the
CELL_DCH state. The measurement report is discarded if flow control is performed on the
dynamic channel configuration control (DCCC) procedure.

BSC6900 UMTS
Figure 1-19 Flow Control on Event 4A Measurement Reports on PS BE Traffic of UEs in the
CELL_DCH State
Formula
None
Unit
None
Related Features
VS.Traffic.Report4A.CellD WRFD-040100 Flow Control

ch.Disc.Num.UpLink.FC
VS.Traffic.Report4A.CellD WRFD-040100 Flow Control

ch.Disc.Num.DownLink.FC
1.2.1.20 Number of Discarded UL Event 4A Measurement Reports on Throughput

for UEs in the CELL_DCH State

BSC6900 UMTS
Counters
73423930 VS.Throughput.Report4A.D Number of Discarded UL

isc.Num.UpLink.FC Event 4A Measurement
Reports on Throughput for
UEs in the CELL_DCH State
in a CPUS
Description
This counter provides the number of discarded UL event 4A measurement reports on throughput
for UEs in the CELL_DCH state in a CPU subsystem (CPUS) due to flow control.
Measurement point
The measurement is triggered when the RNC discards an event 4A measurement report on
throughput received from MAC-d. The measurement report is discarded if flow control is
performed on the dynamic channel configuration control (DCCC) procedure.
Figure 1-20 Flow Control on UL Event 4A Measurement Reports on Throughput of UEs in the
CELL_DCH State
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.Throughput.Report4A.D WRFD-040100 Flow Control

isc.Num.UpLink.FC
1.2.1.21 Number of Discarded Event 4A Measurement Reports on PS BE Traffic in

the CELL_FACH State
Counters
73423931 VS.Traffic.Report4A.CellFa Number of Discarded UL

ch.Disc.Num.UpLink.FC Event 4A Measurement
the CELL_FACH State in a
CPUS
73423932 VS.Traffic.Report4A.CellFa Number of Discarded DL

ch.Disc.Num.DownLink.FC Event 4A Measurement
the CELL_FACH State in a
CPUS
Description
These counters provide the number of discarded event 4A measurement reports on PS BE traffic
in the CELL_FACH state in a CPU subsystem (CPUS) due to flow control.
Measurement point
Measurement of the counter VS.Traffic.Report4A.CellFach.Disc.Num.UpLink.FC is triggered
when the RNC discards the event 4A measurement report on traffic received from a UE in the
CELL_FACH state. The measurement report is discarded if flow control is performed on the
dynamic channel configuration control (DCCC) procedure.

BSC6900 UMTS
Figure 1-21 Flow Control on Event 4A Measurement Reports on PS BE Traffic of UEs in the
CELL_FACH State
Formula
None
Unit
None
Related Features
VS.Traffic.Report4A.CellFa WRFD-040100 Flow Control

ch.Disc.Num.UpLink.FC
VS.Traffic.Report4A.CellFa WRFD-040100 Flow Control

ch.Disc.Num.DownLink.FC
1.2.1.22 Number of FlowControl RRC Connection Requests Due to FlowControl

for CPUS Subsystem

BSC6900 UMTS
Counters
73424215 VS.RRC.FC.Num.CPU.CP Number of RRC

US CONNECTION
REQUESTS Under Flow
Control Due to High CPU
Usage for CPUS Subsystem
73424216 VS.RRC.FC.Num.RRCQue Number of RRC

ue.CPUS CONNECTION
REQUESTS Under Flow
Control Due to RRC Queue
Overflow for CPUS
Subsystem
73424217 VS.RRC.FC.Num.MPU.CP Number of RRC

US CONNECTION
REQUESTS Under Flow
Control Due to MPU
Overload for CPUS
Subsystem
73424218 VS.RRC.FC.Num.CallShoc Number of RRC

k.CPUS CONNECTION
REQUESTS Under Flow
Control Due to Burst Traffic
for CPUS Subsystem
Description
These counters provide the number of RRC CONNECTION REQUEST messages in a CPUS
subsystem under flow control.
Measurement point
To be translate.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RRC.FC.Num.CPU.CP WRFD-040100 Flow Control

US
VS.RRC.FC.Num.RRCQue WRFD-040100 Flow Control

ue.CPUS
VS.RRC.FC.Num.MPU.CP WRFD-040100 Flow Control

US
VS.RRC.FC.Num.CallShoc WRFD-040100 Flow Control

k.CPUS
1.2.1.23 Number of FlowControl RT RRC Connection Requests Due to FlowControl

for CPUS Subsystem
Counters
73424219 VS.RRC.CONV.FC.Num.C Number of RRC

PU.CPUS CONNECTION
REQUESTS for CS Services
Under Flow Control Due to
High CPU Usage for CPUS
Subsystem
73424220 VS.RRC.CONV.FC.Num.R Number of RRC

RCQueue.CPUS CONNECTION
RRC Queue Overflow for
CPUS Subsystem
73424221 VS.RRC.CONV.FC.Num.M Number of RRC

PU.CPUS CONNECTION
MPU Overload for CPUS
Subsystem
73424222 VS.RRC.CONV.FC.Num.C Number of RRC

allShock.CPUS CONNECTION
Burst Traffic for CPUS
Subsystem

BSC6900 UMTS
Description
These counters provide the number of RRC CONNECTION REQUEST messages for CS
services in a CPUS subsystem under flow control. If the establishment cause in these requests
is UU_ORIGINATING_CONVERSATIONAL_CALL_ESTAB_CAUSE or
UU_TERMNT_CONVERSATIONAL_CALL_ESTAB_CAUSE, the RNC determines that the
current service is a CS service.
Measurement point
To be translate.
Formula
None
Unit
None
Related Features
VS.RRC.CONV.FC.Num.C WRFD-040100 Flow Control

PU.CPUS
VS.RRC.CONV.FC.Num.R WRFD-040100 Flow Control

RCQueue.CPUS
VS.RRC.CONV.FC.Num.M WRFD-040100 Flow Control

PU.CPUS
VS.RRC.CONV.FC.Num.C WRFD-040100 Flow Control

allShock.CPUS
1.2.1.24 Number of RRC CONNECTION REQUESTS for CS Services in a CPUS

Subsystem Under Flow Control Triggered by Interface-Board CPU Overload

BSC6900 UMTS
Counters
73424482 VS.RRC.CONV.FC.Num.I Number of RRC

NT.CPUS CONNECTION
in a CPUS Subsystem Under
Flow Control Triggered by
Interface-Board CPU
Overload
Description
This counter measures the number of rejected radio resource control (RRC) connection setup
requests for CS voice services during flow control caused by interface-board central processing
unit (CPU) overload in a CPU subsystem (CPUS). If the cause value contained in an RRC
CONNECTION REQUEST message is Originating Conversational Call or Terminating
Conversational Call, the RRC connection setup request is for a CS voice service.
Measurement point
The measurement is triggered when all the following conditions are met: A CPUS receives an
RRC CONNECTION REQUEST message from a UE. The CPUS rejects the UE's request
because of interface-board CPU overload and failures in applying for transmission resources.
This counter measures the number of rejected radio resource control (RRC) connection setup
requests for CS voice services during flow control caused by interface-board central processing
unit (CPU) overload in a CPU subsystem (CPUS).
Formula
None
Unit
None
Related Features
VS.RRC.CONV.FC.Num.I WRFD-040100 Flow Control

NT.CPUS
1.2.1.25 Number of RRC CONNECTION REQUESTS in a CPUS Subsystem Under

Flow Control Triggered by Interface-Board CPU Overload

BSC6900 UMTS
Counters
73424483 VS.RRC.FC.Num.INT.CPU Number of RRC

S CONNECTION
REQUESTS in a CPUS
Subsystem Under Flow
Control Triggered by
Interface-Board CPU
Overload
Description
This counter measures the number of rejected RRC connection setup requests during flow control
caused by interface-board CPU overload in a CPU subsystem (CPUS).
Measurement point
The measurement is triggered when all the following conditions are met: A CPUS receives an
RRC CONNECTION REQUEST message from a UE. The CPUS rejects the UE's request
because of interface-board CPU overload and failures in applying for transmission resources.
This counter measures the number of rejected RRC connection setup requests during flow control
caused by interface-board CPU overload in a CPU subsystem (CPUS).
Formula
None
Unit
None
Related Features
VS.RRC.FC.Num.INT.CPU WRFD-040100 Flow Control

S
1.2.1.26 Number of Discarded Iur-Interface Uplink Signalling Messages in a CPUS

Subsystem Under Flow Control Triggered by CPU Overload

BSC6900 UMTS
Counters
73424484 VS.IurUpLinkSig.Disc.Num Number of Discarded Iur-

.CPU.CPUS Interface Uplink Signalling
Messages in a CPUS
Subsystem Under Flow
Control Triggered by CPU
Overload
Description
This counter measures the number of discarded uplink signalling message during flow control
caused by central processing unit (CPU) overload in a CPU subsystem (CPUS).
Measurement point
This counter measures the number of discarded UPLINK SIGNALLING TRANSFER
INDICATION messages during flow control caused by central processing unit (CPU) overload
in a CPU subsystem (CPUS). The measurement is triggered when a CPUS receives an uplink
signalling message from a neighboring RNC and discards the message due to CPU overload in
the CPUS.
Formula
None
Unit
None
Related Features
VS.IurUpLinkSig.Disc.Num WRFD-040100 Flow Control

.CPU.CPUS
1.2.1.27 Number of Discarded Iur-Interface Downlink Signalling Messages in a

CPUS Subsystem Under Flow Control Triggered by CPU Overload

BSC6900 UMTS
Counters
73424485 VS.IurDownLinkSig.Disc.N Number of Discarded Iur-

um.CPU.CPUS Interface Downlink
Signalling Messages in a
CPUS Subsystem Under
Flow Control Triggered by
CPU Overload
Description
This counter measures the number of discarded downlink signaling messages during flow control
caused by central processing unit (CPU) overload in a CPU subsystem (CPUS).
Measurement point
The measurement is triggered when a CPU subsystem (CPUS) receives any of the following
messages and discards the message due to CPU overload in the CPUS: RADIO LINK SETUP
REQUEST PAGING REQUEST COMMON TRANSPORT CHANNEL RESOURCES
REQUEST This counter measures the number of discarded downlink signaling messages during
flow control caused by central processing unit (CPU) overload in a CPUS.
Formula
None
Unit
None
Related Features
VS.IurDownLinkSig.Disc.N WRFD-040100 Flow Control

um.CPU.CPUS
1.3 Measurement of GTPU Performance(GTPU)

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

BSC6900 UMTS
FunctionSubSets
GTPU Measurement related to GTPU
1.3.1 Measurement related to GTPU(GTPU)
Overview
When the UE is activated in PS domain, the RNC sets up the user plane to the SGSN and allocates
GTP-U tunnels. All the data transmissions of the UE are performed through the GTPU tunnels.
Therefore, it is necessary to calculate the number of messages and the bytes of messages that
are received and transmitted by the GTP-U.
Counters
Description
67178509 VS.GTPU.Pkt.Tx Number of UL Earlier than

Packets Sent by V900R011
GTP-U
67178512 VS.GTPU.Pkt.Rx Number of DL Earlier than

Packets Received by V900R011
GTP-U
67199477 VS.GTPU.BytesPkt Number of UL Bytes Earlier than

.Tx Sent by GTP-U V900R011
67199478 VS.GTPU.BytesPkt Number of DL Bytes Earlier than

.Rx Received by GTP-U V900R011
67204158 VS.GTPU.PktNum Number of UL Earlier than

Conv.Tx Session Service V900R011
Packets Sent by
GTPU
67204159 VS.GTPU.PktNum Number of DL Earlier than

Conv.Rx Session Service V900R011
Packets Received by
GTPU

Str.Tx Streaming Service V900R011
Packets Sent by
GTPU

BSC6900 UMTS

Description

Str.Rx Streaming Service V900R011
Packets Received by
GTPU

Int.Tx Interactive Service V900R011
Packets Sent by
GTPU

Int.Rx Interactive Service V900R011
Packets Received by
GTPU

Bkg.Tx Background Service V900R011
Packets Sent by
GTPU

Bkg.Rx Background Service V900R011
Packets Received by
GTP
67192326 VS.GTPU.BytesMb Number of MBMS Earlier than

ms.Rx Service Bytes V900R011
Received by GTP-U
73424012 VS.GTPU.EchoRsp Number of Echo V900R014

.Tx Response Packets
Sent by the GTP-U
73424013 VS.GTPU.EchoRsp Number of Echo V900R014

.Rx Response Packets
Received by the
GTP-U
73424014 VS.GTPU.EchoRe Number of Echo V900R014

q.Tx Request Packets Sent
by the GTP-U
73424015 VS.GTPU.EchoRe Number of Echo V900R014

q.Rx Request Packets
Received by the
GTP-U
73424016 VS.GTPU.ErrInd. Number of Error V900R014

Tx Indication Packets
Sent by the GTP-U

BSC6900 UMTS

Description
73424017 VS.GTPU.ErrInd. Number of Error V900R014

Rx Indication Packets
Received by the
GTP-U
Counter Sub Counter
VS.GTPU.Pkt.Tx VS.GTPU.PktNumConv.Tx
VS.GTPU.PktNumStr.Tx
VS.GTPU.PktNumInt.Tx
VS.GTPU.PktNumBkg.Tx
VS.GTPU.Pkt.Rx VS.GTPU.PktNumConv.Rx
VS.GTPU.PktNumStr.Rx
VS.GTPU.PktNumInt.Rx
VS.GTPU.PktNumBkg.Rx
1.3.1.1 Number of UL Packets Sent by GTP-U
Counters
67178509 VS.GTPU.Pkt.Tx Number of UL Packets Sent

by GTP-U
Description
This counter provides the number of data packets and control packets sent by the RNC to the
GTP-U at the peer end.
Measurement point
This counter is incremented by one each time the RNC sends a data packet or control packet to
the GTP-U at the peer end.
Formula
None

BSC6900 UMTS
Unit
packet
Related Features
VS.GTPU.Pkt.Tx WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.3.1.2 Number of DL Packets Received by GTP-U
Counters
67178512 VS.GTPU.Pkt.Rx Number of DL Packets

Received by GTP-U
Description
This counter provides the number of data packets and control packets received by the GTP-U
on the RNC side.
Measurement point
This counter is incremented by one each time the RNC receives a data packet or control packet
from the GTP-U at the peer end.
Formula
None
Unit
packet

BSC6900 UMTS
Related Features
VS.GTPU.Pkt.Rx WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.3.1.3 Number of UL Bytes Sent by GTP-U
Counters
67199477 VS.GTPU.BytesPkt.Tx Number of UL Bytes Sent by

GTP-U
Description
This counter provides the number of bytes in the data packets and control packets sent by the
RNC to the GTP-U at the peer end.
Measurement point
This counter is incremented by one each time the RNC sends a data packet or control packet to
Formula
None
Unit
byte
Related Features
VS.GTPU.BytesPkt.Tx WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
1.3.1.4 Number of DL Bytes Received by GTP-U
Counters
67199478 VS.GTPU.BytesPkt.Rx Number of DL Bytes

Received by GTP-U
Description
This counter provides the number of bytes in the data packets and control packets received by
the GTP-U on the RNC side.
Measurement point
This counter is incremented by one each time the RNC receives a data packet or control packet
from the GTP-U at the peer end.
Formula
None
Unit
byte
Related Features
VS.GTPU.BytesPkt.Rx WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.3.1.5 Counters Related to the Number of Service PDUs Sent by GTP-U
Counters
67204158 VS.GTPU.PktNumConv.Tx Number of UL Session

Service Packets Sent by
GTPU

BSC6900 UMTS
67204160 VS.GTPU.PktNumStr.Tx Number of UL Streaming

GTPU
67204162 VS.GTPU.PktNumInt.Tx Number of UL Interactive

GTPU
67204164 VS.GTPU.PktNumBkg.Tx Number of UL Background

GTPU
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
VS.GTPU.PktNumConv.Tx WRFD-010501 Conversational QoS Class
VS.GTPU.PktNumStr.Tx WRFD-010502 Streaming QoS Class
VS.GTPU.PktNumInt.Tx WRFD-010503 Interactive QoS Class
VS.GTPU.PktNumBkg.Tx WRFD-010504 Background QoS Class
1.3.1.6 Counters Related to the Number of Service PDUs Received by GTP-U

BSC6900 UMTS
Counters
67204159 VS.GTPU.PktNumConv.Rx Number of DL Session

Service Packets Received by
GTPU
67204161 VS.GTPU.PktNumStr.Rx Number of DL Streaming

GTPU
67204163 VS.GTPU.PktNumInt.Rx Number of DL Interactive

GTPU
67204165 VS.GTPU.PktNumBkg.Rx Number of DL Background

GTP
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
VS.GTPU.PktNumConv.Rx WRFD-010501 Conversational QoS Class
VS.GTPU.PktNumStr.Rx WRFD-010502 Streaming QoS Class
VS.GTPU.PktNumInt.Rx WRFD-010503 Interactive QoS Class
VS.GTPU.PktNumBkg.Rx WRFD-010504 Background QoS Class
1.3.1.7 Number of MBMS or IMB Service Bytes Received by GTP-U

BSC6900 UMTS
Counters
67192326 VS.GTPU.BytesMbms.Rx Number of MBMS Service

Bytes Received by GTP-U
Description
This counter provides the number of GTP-U PDU bytes of MBMS or IMB services received by
the RNC.
Measurement point
When receiving an MBMS or IMB service PDU from the peer GTP-U, the RNC measures this
counter.
Formula
None
Unit
byte
Related Features
VS.GTPU.BytesMbms.Rx WRFD-010616 MBMS Introduction

Package
1.3.1.8 Number of Echo Response Packets Sent by the GTP-U
Counters
73424012 VS.GTPU.EchoRsp.Tx Number of Echo Response

Packets Sent by the GTP-U
Description
This counter provides the number of Echo Response packets sent by the GTP-U on the RNC
side.

BSC6900 UMTS
Measurement point
This counter is incremented by one each time the RNC sends an Echo Response packet to the
Formula
None
Unit
packet
Related Features
None
1.3.1.9 Number of Echo Response Packets Received by the GTP-U
Counters
73424013 VS.GTPU.EchoRsp.Rx Number of Echo Response

Packets Received by the
GTP-U
Description
This counter provides the number of Echo Response packets received by the GTP-U on the RNC
side.
Measurement point
This counter is incremented by one each time the RNC receives an Echo Response packet from
Formula
None
Unit
packet
Related Features
None

BSC6900 UMTS
1.3.1.10 Number of Echo Request Packets Sent by the GTP-U
Counters
73424014 VS.GTPU.EchoReq.Tx Number of Echo Request

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
Formula
None
Unit
packet
Related Features
None
1.3.1.11 Number of Echo Request Packets Received by the GTP-U
Counters
73424015 VS.GTPU.EchoReq.Rx Number of Echo Request

GTP-U
Description
This counter provides the number of Echo Request packets received by the GTP-U on the RNC
side.

BSC6900 UMTS
Measurement point
This counter is incremented by one each time the RNC receives an Echo Request packet from
Formula
None
Unit
packet
Related Features
None
1.3.1.12 Number of Error Indication Packets Sent by the GTP-U
Counters
73424016 VS.GTPU.ErrInd.Tx Number of Error Indication

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
Formula
None
Unit
packet
Related Features
None

BSC6900 UMTS
1.3.1.13 Number of Error Indication Packets Received by the GTP-U
Counters
73424017 VS.GTPU.ErrInd.Rx Number of Error Indication

GTP-U
Description
This counter provides the number of Error Indication packets received by the GTP-U on the
RNC side.
Measurement point
This counter is incremented by one each time the RNC receives an Error Indication packet from
Formula
None
Unit
packet
Related Features
None
1.4 Measurement of IU Interface Performance(IU)

Overview
The measurement object of Iu Interface Performance Measurement (IU) is used to measure the
overall performance of the basic signaling procedures and traffic flows on the Iu interface.
FunctionSubSets
CS.SIG.IU Measurement related to CS Iu interface

signalling
CS.TRF.IU Measurement related to CS traffic

BSC6900 UMTS
MBMS.IU Measurement related to Iu interface(MBMS)
MOCN.IU Measurement related to Iu interface(MOCN)
NAS.IU Measurement related to NAS signaling
PS.SIG.IU Measurement related to PS Iu interface

signalling
PS.TRF.IU Measurement related to PS traffic
SIG.SCCP.IU Measurement Related to SCCP for Iu

Interface
1.4.1 Measurement related to CS Iu interface signalling(CS.SIG.IU)
Overview
This function subset aims at the connectionless signaling procedure and the signaling connection
setup and release procedures on the Iu interface. In Iu Flex connection mode, the RNC measures
the counters according to the CS CN nodes.
Counters
Description
67176449 VS.IU.ResetCS.Tx Number of RESET Earlier than

Messages Sent by V900R011
RNC to CN in CS
Domain
67176453 VS.IU.ResetCS.Rx Number of RESET Earlier than

Messages Received V900R011
by RNC from CN in
CS Domain
67189920 VS.IU.SIG.AttCon- Number of INITIAL Earlier than

nEstabCS UE MESSAGE V900R011
Messages Sent by
RNC to CN in CS
Domain
67176546 VS.IU.RelReqCS.s Number of IU Earlier than

um RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in CS
Domain

BSC6900 UMTS

Description
67176552 VS.IU.RelCmdCS.s Number of IU Earlier than

um RELEASE V900R011
COMMAND
Messages Received
by RNC from CN in
CS Domain
67176529 VS.IU.ErrInd.CS.T Number of ERROR Earlier than

x INDICATION V900R011
Messages Sent by
RNC to CN in CS
Domain
67176531 VS.IU.ErrInd.CS. Number of ERROR Earlier than

Rx INDICATION V900R011
Messages Received
by RNC from CN in
CS Domain
67176549 VS.IU.RelReqCS.I Number of IU Earlier than

ngChkFail RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in CS
Domain (Repeated
Integrity Checking
Failure)
67176550 VS.IU.RelReqCS.Si Number of IU Earlier than

gConnRel RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in CS
Domain (UE
Signaling
Connection Release)
67176551 VS.IU.RelReqCS.R Number of IU Earlier than

adConnUELost RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in CS
Domain (Radio
Connection With UE
Lost)

BSC6900 UMTS

Description
67176553 VS.IU.RelCmdCS. Number of IU Earlier than

RelocSucc RELEASE V900R011
COMMAND
Messages Received
by RNC from CN in
CS Domain
(Relocation Success)

NormRel RELEASE V900R011
COMMAND
Messages Received
by RNC from CN in
CS Domain (Normal
Release)

UTRANGen RELEASE V900R011
COMMAND
Messages Received
by RNC from CN in
CS Domain
(UTRAN Generated)

RelocCan RELEASE V900R011
COMMAND
Messages Received
by RNC from CN in
CS Domain
(Relocation
Cancelled)

NoRAB RELEASE V900R011
COMMAND
Messages Received
by RNC from CN in
CS Domain (No
Remaining RAB)
67176573 VS.Iu.RelReqCS.R Number of IU Earlier than

IPFail RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in CS
Domain (Failure in
the Radio Interface
Procedure)

BSC6900 UMTS

Description
67190182 VS.IU.RelReqCS.P Number of IU Earlier than

reempt RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in CS
Domain (RAB
Preempted)
67192538 VS.IU.LdBalRtCS. Number of Times Earlier than

IMSI that CS Load V900R011
Balancing is
Performed by IMSI
Users

InValidNRI that CS Load V900R011
Balancing is
Performed by TMSI
Users Due to Invalid
NRI

IMEI that CS Load V900R011
Balancing is
Performed by IMEI
Users
67193095 VS.IU.FlowCtrl.Dis Number of Earlier than

cInitDT.CS Discarded CS Initial V900R011
UE Messages when
Signaling Flow
Control is Triggered
67196234 VS.IU.RelReqCS.N Number of IU Earlier than

etworkOpt RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in CS
Domain (VP
Forbiddance)
73424970 VS.IU.CS.Paging Number of Paging V900R014

Messages Received
by RNC from CN in
CS Domain

BSC6900 UMTS

Description
73425021 VS.IU.RanInfoReq. Number of RAN V900R014

Rx INFORMATION
REQUEST
Messages Received
by RNC from CN
73425022 VS.IU.RanInfo.Tx Number of RAN V900R014

INFORMATION
Messages Sent by
RNC to CN
None
1.4.1.1 Number of RESET Messages Initiated by RNC to CS Domain
Counters
67176449 VS.IU.ResetCS.Tx Number of RESET Messages

Sent by RNC to CN in CS
Domain
Description
This measurement counter takes statistics of the number of RESET messages that the RNC sends
to the CS domain according to respective CN nodes.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends a RESET
message to the CS domain, it measures this counter. If the RNC does not receive the RESET
ACKNOWLEDGE message from the CN before the response timer expires, the RNC sends the
RESET message again and this counter is also measured again.

BSC6900 UMTS
Figure 1-22 CS domain reset procedure initiated by the RNC (successful operation)
Formula
None
Unit
None
Related Features
VS.IU.ResetCS.Tx WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.1.2 Number of RESET Messages Received by RNC from CS Domain

BSC6900 UMTS
Counters
67176453 VS.IU.ResetCS.Rx Number of RESET Messages

Received by RNC from CN
in CS Domain
Description
This counter provides the number of RESET messages that the RNC receives from the CS
domain in the CN based on the corresponding CN node.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives a
RESET message from the CS domain, it measures this counter.
Figure 1-23 CS domain reset procedure initiated by the CN (successful operation)
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.IU.ResetCS.Rx WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.1.3 Number of INITIAL UE MESSAGE Messages from RNC to CS Domain
Counters
67189920 VS.IU.SIG.AttConnEs- Number of INITIAL UE

tabCS MESSAGE Messages Sent
by RNC to CN in CS Domain
Description
This measurement counter takes statistics of the number of INITIAL UE MESSAGE messages
that the RNC sends to the CS domain. The RNC measures this counter according to the CN
nodes.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends an
INITIAL UE MESSAGE message to the CS domain, it measures this counter.
Figure 1-24 Initial UE message procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.SIG.AttConnEs- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

tabCS Connection and Radio
and Release
1.4.1.4 Number of IU RELEASE REQUEST Messages from RNC to CS Domain
Counters
67176546 VS.IU.RelReqCS.sum Number of IU RELEASE

REQUEST Messages Sent
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.

BSC6900 UMTS
Figure 1-25 Iu release procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.IU.RelReqCS.sum WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.1.5 Number of IU RELEASE COMMAND Messages from CS Domain to RNC

BSC6900 UMTS
Counters
67176552 VS.IU.RelCmdCS.sum Number of IU RELEASE

COMMAND Messages
in CS Domain
Description
This counter provides the number of IU RELEASE COMMAND messages that the RNC
receives from the CS domain based on the corresponding CN node. During the Iu release
procedure of the CS domain, the Iu connection and all the UTRAN resources related to the Iu
connection are released.
Measurement point
The measurement is triggered at point B as shown in the figure. In the RNC-initiated Iu release
procedure, when the RNC receives an IU RELEASE COMMAND message from the CS domain,
the RNC measures this counter.
The measurement is triggered at point A as shown in the figure. In the CN-initiated Iu release
the RNC measures this counter.

BSC6900 UMTS
Figure 1-27 Iu release procedure initiated by the CN (successful operation)
Formula
None
Unit
None
Related Features
VS.IU.RelCmdCS.sum WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.1.6 Number of ERROR INDICATION Messages from RNC to CS Domain

BSC6900 UMTS
Counters
67176529 VS.IU.ErrInd.CS.Tx Number of ERROR

INDICATION Messages
Sent by RNC to CN in CS
Domain
Description
This measurement counter takes statistics of the number of ERROR INDICATION messages
that the RNC sends to the CS domain. The RNC measures this counter according to the CN
nodes.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends an ERROR
INDICATION message to the CS domain, it measures this counter.
Figure 1-28 Error indication procedure initiated by the RNC
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IU.ErrInd.CS.Tx WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.1.7 Number of ERROR INDICATION Messages from CS Domain to RNC
Counters
67176531 VS.IU.ErrInd.CS.Rx Number of ERROR

INDICATION Messages
in CS Domain
Description
This counter provides the number of ERROR INDICATION messages that the RNC receives
from the CS domain based on the corresponding CN node.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives an
ERROR INDICATION message from the CS domain, it measures this counter according to the
CN nodes.

BSC6900 UMTS
Figure 1-29 Error indication procedure initiated by the CN
Formula
None
Unit
None
Related Features
VS.IU.ErrInd.CS.Rx WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.1.8 Number of IU RELEASE REQUEST Messages from RNC to CS Domain for

Different Causes

BSC6900 UMTS
Counters
67176549 VS.IU.RelReqCS.In- Number of IU RELEASE

gChkFail REQUEST Messages Sent
(Repeated Integrity
Checking Failure)
67176550 VS.IU.RelReqCS.SigConn- Number of IU RELEASE

Rel REQUEST Messages Sent
(UE Signaling Connection
Release)
67176551 VS.IU.RelReqCS.RadCon- Number of IU RELEASE

nUELost REQUEST Messages Sent
(Radio Connection With UE
Lost)
67176573 VS.Iu.RelReqCS.RIPFail Number of IU RELEASE

(Failure in the Radio
Interface Procedure)
67190182 VS.IU.RelReqCS.Preempt Number of IU RELEASE

(RAB Preempted)
67196234 VS.IU.RelReqCS.Networ- Number of IU RELEASE

kOpt REQUEST Messages Sent
(VP Forbiddance)
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
RELEASE REQUEST message to the CS domain, it measures these counters according to
different causes.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.RelReqCS.In- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

gChkFail Connection and Radio
and Release
VS.IU.RelReqCS.SigConn- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Rel Connection and Radio
and Release
VS.IU.RelReqCS.RadCon- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

nUELost Connection and Radio
and Release

BSC6900 UMTS
VS.Iu.RelReqCS.RIPFail WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IU.RelReqCS.Preempt WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IU.RelReqCS.Networ- WRFD-020130 Videophone Service

kOpt Restriction
1.4.1.9 Number of IU RELEASE COMMAND Messages from CS Domain to RNC

for Different Causes
Counters
67176553 VS.IU.RelCmdCS.Reloc- Number of IU RELEASE

Succ COMMAND Messages
in CS Domain (Relocation
Success)
67176554 VS.IU.RelCmdCS.NormRel Number of IU RELEASE

COMMAND Messages
in CS Domain (Normal
Release)
67176555 VS.IU.RelCmdCS.UTRAN- Number of IU RELEASE

Gen COMMAND Messages
in CS Domain (UTRAN
Generated)
67176556 VS.IU.RelCmdCS.Reloc- Number of IU RELEASE

Can COMMAND Messages
in CS Domain (Relocation
Cancelled)

BSC6900 UMTS
67176557 VS.IU.RelCmdCS.NoRAB Number of IU RELEASE

COMMAND Messages
in CS Domain (No
Remaining RAB)
Description
These counters provide the number of IU RELEASE COMMAND messages with different
release causes that the RNC receives from the CS domain based on the corresponding CN node.
Measurement point
The measurement is triggered at point B, as shown in the figure. In the RNC-initiated Iu release
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
it measures these counters according to different causes.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.RelCmdCS.Reloc- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Succ Connection and Radio
and Release
VS.IU.RelCmdCS.NormRel WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IU.RelCmdCS.UTRAN- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Gen Connection and Radio
and Release

BSC6900 UMTS
VS.IU.RelCmdCS.Reloc- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Can Connection and Radio
and Release
VS.IU.RelCmdCS.NoRAB WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.1.10 Load Balancing of the MSC Pool on the CS Domain
Counters
67192538 VS.IU.LdBalRtCS.IMSI Number of Times that CS

Load Balancing is Performed
by IMSI Users
67192539 VS.IU.LdBalRtCS.InValid- Number of Times that CS

NRI Load Balancing is Performed
by TMSI Users Due to
Invalid NRI
67192540 VS.IU.LdBalRtCS.IMEI Number of Times that CS

Load Balancing is Performed
by IMEI Users
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.
VS.IU.LdBalRtCS.IMSI Number of times that the CS CN is selected

for load balancing by using the IMSI route
parameter.

BSC6900 UMTS
VS.IU.LdBalRtCS.InValidNRI Number of times that load balancing is

triggered due to invalid NRI route parameter,
connection failure to the CN node
corresponding to the route parameter, or the
flow control of the CN node corresponding to
the route parameter.
VS.IU.LdBalRtCS.IMEI Number of times that the CS CN is selected

for load balancing by using the IMEI route
parameter.
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

BSC6900 UMTS
Unit
None
Related Features
VS.IU.LdBalRtCS.IMSI WRFD-021306 Iu Flex Load Distribution

Management
VS.IU.LdBalRtCS.InValid- WRFD-021306 Iu Flex Load Distribution

NRI Management
VS.IU.LdBalRtCS.IMEI WRFD-021306 Iu Flex Load Distribution

Management
1.4.1.11 Number of Discarded Initial UE messages Under Iu Signaling Flow Control

(CS Domain)
Counters
67193095 VS.IU.FlowCtrl.DiscInitDT. Number of Discarded CS

CS Initial UE Messages when
Signaling Flow Control is
Triggered
Description
This measurement counter provides the number of initial UE messages discarded under the flow
control when the RNC receives the CS initial direct transfer messages.
Measurement point
The measurement is triggered when the RNC receives an INITIAL DIRECT TRANSFER
message from a UE and then discards this message because the RNC finds that the Iu-CS
interface is under flow control, as shown by point A in the following figure. After that, the RNC
does not send the INITIAL UE MESSAGE to the CN.

BSC6900 UMTS
Figure 1-34 Process of discarding INITIAL DIRECT TRANSFER message
Formula
None
Unit
None
Related Features
VS.IU.FlowCtrl.DiscInitDT. WRFD-040100 Flow Control

CS
1.4.1.12 Number of Paging Messages Received by RNC from CN in CS Domain
Counters
73424970 VS.IU.CS.Paging Number of Paging Messages

in CS Domain

BSC6900 UMTS
Description
This counter provides the number of PAGING messages that the RNC receives from the CS
domain based on the corresponding CN node.
Measurement point
The measurement is triggered at point A shown in the following figure when both of the
following conditions are met: -The RNC receives a paging message from the CN. -The value of
the CN Domain Indicator IE contained in the message indicates the CS domain.
Figure 1-35 Paging messages sent from the CN to the UE
Formula
None
Unit
None
Related Features
VS.IU.CS.Paging WRFD-010301 Paging UE in Idle,

WRFD-010302 CELL_PCH, URA_PCH
State (Type 1)
Paging UE in CELL_FACH,
CELL_DCH State (Type 2)

BSC6900 UMTS
1.4.1.13 Number of RAN INFORMATION REQUEST Messages Received by RNC

from CN
Counters
73425021 VS.IU.RanInfoReq.Rx Number of RAN

INFORMATION
REQUEST Messages
Description
This counter provides the number of RANAP DERECT INFORMATION TRANSER messages
whose types are RAN INFORMATION REQUEST that the RNC receives from the CN based
on the corresponding CN node.
Measurement point
The measurement is triggered at point A as shown in the figure. This counter is incremented by
one each time the RNC receives a RANAP DERECT INFORMATION TRANSER message
whose type is RAN INFORMATION REQUEST.
Figure 1-36 Procedure for directly sending messages over the Iu interface
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IU.RanInfoReq.Rx WRFD-140224 Fast CS Fallback Based on

RIM
1.4.1.14 Number of RAN INFORMATION Messages Sent by RNC to CN
Counters
73425022 VS.IU.RanInfo.Tx Number of RAN

INFORMATION Messages
Sent by RNC to CN
Description
This counter provides the number of RANAP DERECT INFORMATION TRANSER messages
whose types are RAN INFORMATION that the RNC receives from the CN based on the
corresponding CN node.
Measurement point
The measurement is triggered at point A as shown in the figure. This counter is incremented by
one each time the RNC receives a RANAP DERECT INFORMATION TRANSER message
whose type is RAN INFORMATION.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.RanInfo.Tx WRFD-140224 Fast CS Fallback Based on

RIM
1.4.2 Measurement related to CS traffic(CS.TRF.IU)
Overview
The function subset is used to measure the UL and DL traffic for various services of the CS
domain on the Iu interface.
Counters
Description
67199469 VS.IuCS.BytesPayl Number of DL Bytes Earlier than

dConv.Rx of CS Conversational V900R011
Service on Iu-CS
Interface
67199470 VS.IuCS.BytesPayl Number of DL Bytes Earlier than

dStr.Rx of CS Streaming V900R011
Service on Iu-CS
Interface
67199473 VS.IuCS.BytesPayl Number of UL Bytes Earlier than

dConv.Tx of CS Conversational V900R011
Service on Iu-CS
Interface
67199474 VS.IuCS.BytesPayl Number of UL Bytes Earlier than

dStr.Tx of CS Streaming V900R011
Service on Iu-CS
Interface

BSC6900 UMTS
None
1.4.2.1 Number of DL Bytes of CS Conversational Service on Iu Interface
Counters
67199469 VS.IuCS.BytesPayldConv.R Number of DL Bytes of CS

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

x
1.4.2.2 Number of DL Bytes of CS Streaming Service on Iu Interface

BSC6900 UMTS
Counters
67199470 VS.IuCS.BytesPayldStr.Rx Number of DL Bytes of CS

Streaming Service on Iu-CS
Interface
Description
This counter provides the number of DL payload bytes of CS streaming service data on the Iu-
CS interface received by the RNC.It includes the data at the application layer and excludes the
IuUP header.
Measurement point
When receiving the DL CS streaming service data on the Iu-CS interface, the RNC measures
Formula
None
Unit
byte
Related Features
VS.IuCS.BytesPayldStr.Rx WRFD-010502 Streaming QoS Class
1.4.2.3 Number of UL Bytes of CS Conversational Service on Iu Interface
Counters
67199473 VS.IuCS.BytesPayldConv.T Number of UL Bytes of CS

Iu-CS Interface

BSC6900 UMTS
Description
This counter provides the number of UL payload bytes of CS Conversational service data on the
Iu-CS interface sent by the RNC.It includes the data at the application layer and excludes the
IuUP header.
Measurement point
When receiving the UL CS Conversational service data on the Iu-CS interface, the RNC
measures the counter according to different Iu-CS interfaces.
Formula
None
Unit
byte
Related Features
VS.IuCS.BytesPayldConv.T WRFD-010501 Conversational QoS Class

x
1.4.2.4 Number of UL Bytes of CS Streaming Service on Iu Interface
Counters
67199474 VS.IuCS.BytesPayldStr.Tx Number of UL Bytes of CS

Streaming Service on Iu-CS
Interface
Description
This counter provides the number of UL payload bytes of CS streaming service data on the Iu-
CS interface received by the RNC.It includes the data at the application layer and excludes the
IuUP header.
Measurement point
When receiving the UL CS streaming service data on the Iu-CS interface, the RNC measures

BSC6900 UMTS
Formula
None
Unit
byte
Related Features
VS.IuCS.BytesPayldStr.Tx WRFD-010502 Streaming QoS Class
1.4.3 Measurement related to Iu interface(MBMS)(MBMS.IU)
Overview
This function subset is used to measure the number of MBMS service establishments, including
the total number of MBMS service establishments, the number of successful establishments,
and the number of failed establishments.
Counters
Description
67192077 VS.IU.MBMS.Start Number of MBMS Earlier than

Service V900R011
Establishment
Attempts
67192078 VS.IU.MBMS.Succ Number of Earlier than

Successful MBMS V900R011
Service
Establishments
67192079 VS.IU.MBMS.Fail Number of Failed Earlier than

MBMS Service V900R011
Establishments
67192080 VS.IU.MBMS.Fail. Number of Failed Earlier than

NoRsrc MBMS Service V900R011
Establishments Due
to No Resource

NNSF MBMS Service V900R011
Establishments Due
to NNSF

BSC6900 UMTS

Description

IuUpFail MBMS Service V900R011
Establishments Due
to Iu User Plane
Failure

IuSigFail MBMS Service V900R011
Establishments Due
to Iu Signaling
Connection Failure
None
1.4.3.1 Total Number of MBMS or IMB Service
Counters
67192077 VS.IU.MBMS.Start Number of MBMS Service

Establishment Attempts
Description
This measurement item takes statistics of the number of MBMS or IMB service establishments.
Measurement point
The measurement is triggered at point A, as shown in the figure. The measurement is triggered
when the RNC receives an MBMS SESSION START message from the PS domain.

BSC6900 UMTS
Figure 1-38 MBMS session (success procedure)
Formula
None
Unit
None
Related Features
VS.IU.MBMS.Start WRFD-010616 MBMS Introduction

Package
1.4.3.2 Number of Successful MBMS or IMB Service
Counters
67192078 VS.IU.MBMS.Succ Number of Successful

MBMS Service
Establishments

BSC6900 UMTS
Description
This measurement item takes statistics of the number of successful MBMS or IMB service
establishments.
Measurement point
The measurement is triggered at point B, as shown in the figure. The measurement is triggered
when the RNC successfully establishes the MBMS or IMB service and sends an MBMS
SESSION START RESPONSE message to the PS domain.
Figure 1-39 3-17 MBMS session (success procedure)
Formula
None
Unit
None
Related Features
VS.IU.MBMS.Succ WRFD-010616 MBMS Introduction

Package

BSC6900 UMTS
1.4.3.3 Number of MBMS or IMB Service Setup Failures on the Iu Interface Due to
Different Causes
Counters
67192079 VS.IU.MBMS.Fail Number of Failed MBMS

Service Establishments
67192080 VS.IU.MBMS.Fail.NoRsrc Number of Failed MBMS

Service Establishments Due
to No Resource
67192081 VS.IU.MBMS.Fail.NNSF Number of Failed MBMS

to NNSF
67192082 VS.IU.MBMS.Fail.IuUpFail Number of Failed MBMS

to Iu User Plane Failure
67192083 VS.IU.MBMS.Fail.IuSig- Number of Failed MBMS

Fail Service Establishments Due
to Iu Signaling Connection
Failure
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.

BSC6900 UMTS
Figure 1-40 MBMS session (failure procedure)
Formula
None
Unit
None
Related Features
VS.IU.MBMS.Fail WRFD-010616 MBMS Introduction

Package
VS.IU.MBMS.Fail.NoRsrc WRFD-010616 MBMS Introduction

Package
VS.IU.MBMS.Fail.NNSF WRFD-010616 MBMS Introduction

Package
VS.IU.MBMS.Fail.IuUpFail WRFD-010616 MBMS Introduction

Package
VS.IU.MBMS.Fail.IuSig- WRFD-010616 MBMS Introduction

Fail Package

BSC6900 UMTS
1.4.4 Measurement related to Iu interface(MOCN)(MOCN.IU)
Overview
This function subset of "Iu interface MOCN measurement" is used to measure the number of
Redirect when the RAN supports the multiple operator core network (MOCN).
Counters
Description
67193097 VS.IU.MOCN.CsPs Number of Earlier than

Coordination Redirection V900R011
Requests from CN
(CS/PS Coordination
Required)
67193098 VS.IU.MOCN.Lo- Number of Earlier than

cAreaNotAllowed Redirection V900R011
Requests from CN
(Location Area Not
Allowed)
67193099 VS.IU.MOCN.Plm Number of Earlier than

nNotAllowed Redirection V900R011
Requests from CN
(PLMN Not
Allowed)
67193100 VS.IU.MOCN.Roa Number of Earlier than

mNotAllowed Redirection V900R011
Requests from CN
(Roaming Not
Allowed in this
Location Area)
67193101 VS.IU.MOCN.No- Number of Earlier than

SuitableCell Redirection V900R011
Requests from CN
(No Suitable Cell in
Location Area)
67193102 VS.IU.MOCN.Gpr Number of Earlier than

sServicesNotAl- Redirection V900R011
lowed Requests from CN
(GPRS Services Not
Allowed in this
PLMN)

BSC6900 UMTS
None
1.4.4.1 Number of Redirect for Different Causes
Counters
67193097 VS.IU.MOCN.CsPsCoordi- Number of Redirection

nation Requests from CN (CS/PS
Coordination Required)
67193098 VS.IU.MOCN.LocAreaNo- Number of Redirection

tAllowed Requests from CN (Location
Area Not Allowed)
67193099 VS.IU.MOCN.PlmnNotAl- Number of Redirection

lowed Requests from CN (PLMN
Not Allowed)
67193100 VS.IU.MOCN.RoamNotAl- Number of Redirection

lowed Requests from CN (Roaming
Not Allowed in this Location
Area)
67193101 VS.IU.MOCN.NoSuitable- Number of Redirection

Cell Requests from CN (No
Suitable Cell in Location
Area)
67193102 VS.IU.MOCN.GprsServi- Number of Redirection

cesNotAllowed Requests from CN (GPRS
Services Not Allowed in this
PLMN)
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.

BSC6900 UMTS
Figure 1-41 Process of INIT UE MESSAGE Redirect
Formula
None
Unit
None
Related Features
VS.IU.MOCN.CsPsCoordi- WRFD-021311 MOCN Introduction

nation Package
VS.IU.MOCN.LocAreaNo- WRFD-021311 MOCN Introduction

tAllowed Package
VS.IU.MOCN.PlmnNotAl- WRFD-021311 MOCN Introduction

lowed Package
VS.IU.MOCN.RoamNotAl- WRFD-021311 MOCN Introduction

lowed Package
VS.IU.MOCN.NoSuitable- WRFD-021311 MOCN Introduction

Cell Package

BSC6900 UMTS
VS.IU.MOCN.GprsServi- WRFD-021311 MOCN Introduction

cesNotAllowed Package
1.4.5 Measurement related to NAS signaling(NAS.IU)
Overview
The function subset Non-Access Stratum (NAS) Signaling Measurement on the Iu Interface
measures the number of NAS interactions on the Iu interface. The method of measuring NAS-
related counters on the RNC are different from those on the CN,and the later prevails.
Counters
Description
73423785 VS.IU.MM.LocUp Number of Location V900R014

d.Req Area Update
Requests Forwarded
by the RNC to the CN
73423786 VS.IU.MM.LocUp Number of Accepted V900R014

d.Acc Location Area
Update Requests
Received by the
RNC from the CN
73423788 VS.IU.GMM.RAU. Number of Accepted V900R014

Acc Routing Area Update
Requests Received
by the RNC from the
CN
73423789 VS.IU.GMM.Attac Number of Attach V900R014

h.Req Requests Forwarded
73423790 VS.IU.GMM.Attac Number of Accepted V900R014

h.Acc Attach Requests
Received by the
RNC from the CN
73423791 VS.IU.GMM.PDP Number of PDP V900R014

Act.Req Activation Requests
Forwarded by the
RNC to the CN

BSC6900 UMTS

Description
73423792 VS.IU.GMM.PDP Number of Accepted V900R014

Act.Acc PDP Activation
Requests Received
by the RNC from the
CN
73423793 VS.IU.Sevice.Req Number of Service V900R014

Setup Requests
Forwarded by the
RNC to the CN
73423794 VS.IU.Sevice.Rej Number of Rejected V900R014

Service Setup
Requests Received
by the RNC from the
CN
73423795 VS.IU.Auth.Req Number of V900R014

Authentication
Requests Received
by the RNC from the
CN
73423796 VS.IU.Auth.Rsp Number of V900R014

Authentication
Responses
Forwarded by the
RNC to the CN
73423797 VS.IU.SecModeCm Number of V900R014

d.Num SECURITY MODE
COMMAND
Messages Received
by the RNC from the
CN
73423798 VS.IU.SecModeCm Number of V900R014

p.Num SECURITY MODE
COMPLETE
Messages Forwarded
73423799 VS.IU.GMM.RAU. Number of Routing V900R014

Req Area Update
Requests Forwarded

BSC6900 UMTS
None
1.4.5.1 Number of Messages Forwarded by the RNC to the CN
Counters
73423785 VS.IU.MM.LocUpd.Req Number of Location Area

Update Requests Forwarded
73423789 VS.IU.GMM.Attach.Req Number of Attach Requests

Forwarded by the RNC to the
CN
73423791 VS.IU.GMM.PDPAct.Req Number of PDP Activation

Requests Forwarded by the
RNC to the CN
73423793 VS.IU.Sevice.Req Number of Service Setup

Requests Forwarded by the
RNC to the CN
73423799 VS.IU.GMM.RAU.Req Number of Routing Area

Update Requests Forwarded
Description
These counters provide the number of various types of messages forwarded by the RNC to the
CN.
Measurement point
The measurement is triggered at point A as shown in the figure. The measurement is triggered
when the RNC forwards to the CN an INITIAL UE MESSAGE or DIRECT TRANSFER
message from a UE. The RNC decodes the message, determines the message type based on
decoding result, and increments the number of this type of messages by one in the corresponding
CN node.

BSC6900 UMTS
Figure 1-42 Process of INIT UE MESSAGE Direct TRANSFER
Formula
None
Unit
None
Related Features
VS.IU.MM.LocUpd.Req WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IU.GMM.Attach.Req WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IU.GMM.PDPAct.Req WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
VS.IU.Sevice.Req WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IU.GMM.RAU.Req WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.5.2 Number of Messages Forwarded by the RNC from the CN
Counters
73423786 VS.IU.MM.LocUpd.Acc Number of Accepted

Location Area Update
Requests Received by the
RNC from the CN
73423788 VS.IU.GMM.RAU.Acc Number of Accepted Routing

Area Update Requests
Received by the RNC from
the CN
73423790 VS.IU.GMM.Attach.Acc Number of Accepted Attach

RNC from the CN
73423792 VS.IU.GMM.PDPAct.Acc Number of Accepted PDP

Activation Requests
Received by the RNC from
the CN
73423794 VS.IU.Sevice.Rej Number of Rejected Service

Setup Requests Received by
the RNC from the CN
Description
These counters provide the number of various types of messages forwarded by the RNC from
the CN.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC forwards the
UE a DIRECT TRANSFER message sent by the CN, the RNC decodes the message and

BSC6900 UMTS
determines the message type based on decoding result. This counter is measured in the
corresponding CN node based on the message type.
Formula
None
Unit
None
Related Features
VS.IU.MM.LocUpd.Acc WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IU.GMM.RAU.Acc WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
VS.IU.GMM.Attach.Acc WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IU.GMM.PDPAct.Acc WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IU.Sevice.Rej WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.5.3 Number of Authentication Requests Received by the RNC from the CN
Counters
73423795 VS.IU.Auth.Req Number of Authentication

RNC from the CN
Description
This counter provides the number of authentication requests received by the RNC from the CN.
Measurement point
The measurement is triggered at point B as shown in the figure. The measurement is triggered
when the RNC receives a DIRECT TRANSFER message sent by the CN and determines that
this message is an authentication request based on the message decoding result. In this case, this
counter is incremented by one in the corresponding CN node.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.Auth.Req WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.5.4 Number of Authentication Responses Forwarded by the RNC to the CN

BSC6900 UMTS
Counters
73423796 VS.IU.Auth.Rsp Number of Authentication

Responses Forwarded by the
RNC to the CN
Description
This counter provides the number of authentication responses forwarded by the RNC to the CN.
Measurement point
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

BSC6900 UMTS
Related Features
VS.IU.Auth.Rsp WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.5.5 Number of SECURITY MODE COMMAND Messages Received by the RNC

from the CN
Counters
73423797 VS.IU.SecModeCmd.Num Number of SECURITY

MODE COMMAND
Messages Received by the
RNC from the CN
Description
This counter provides the number of SECURITY MODE COMMAND messages received by
the RNC from the CN.
Measurement point
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.

BSC6900 UMTS
Figure 1-46 Security mode control procedure (CN to RNC)
Formula
None
Unit
None
Related Features
VS.IU.SecModeCmd.Num WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.5.6 Number of SECURITY MODE COMPLETE Messages Forwarded by the

RNC to the CN

BSC6900 UMTS
Counters
73423798 VS.IU.SecModeCmp.Num Number of SECURITY

MODE COMPLETE
Messages Forwarded by the
RNC to the CN
Description
This counter provides the number of SECURITY MODE COMPLETE messages forwarded by
the RNC to the CN.
Measurement point
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

BSC6900 UMTS
Unit
None
Related Features
VS.IU.SecModeCmp.Num WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.6 Measurement related to PS Iu interface signalling(PS.SIG.IU)
Overview
This function subset aims at the connectionless signaling procedure and the signaling connection
setup and release procedures on the Iu interface. In Iu Flex connection mode, the RNC measures
the counters according to the PS CN nodes.
Counters
Description
67176481 VS.IU.ResetPS.Tx Number of RESET Earlier than

Messages Sent by V900R011
RNC to CN in PS
Domain
67176485 VS.IU.ResetPS.Rx Number of RESET Earlier than

Messages Received V900R011
by RNC from CN in
PS Domain
67189921 VS.IU.SIG.AttCon- Number of INITIAL Earlier than

nEstabPS UE MESSAGE V900R011
Messages Sent by
RNC to CN in PS
Domain
67176559 VS.IU.RelReqPS.su Number of IU Earlier than

m RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in PS
Domain

BSC6900 UMTS

Description
67176565 VS.IU.RelCmdPS.s Number of IU Earlier than

um RELEASE V900R011
COMMAND
Messages Received
by RNC from CN in
PS Domain
67176530 VS.IU.ErrInd.PS.T Number of ERROR Earlier than

Messages Sent by
RNC to CN in PS
Domain
67176532 VS.IU.ErrInd.PS.R Number of ERROR Earlier than

Messages Received
by RNC from CN in
PS Domain
67176561 VS.IU.RelReqPS.U Number of IU Earlier than

srInact RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in PS
Domain (User
Inactive)
67176562 VS.IU.RelReqPS.In Number of IU Earlier than

gChkFail RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in PS
Domain (Repeated
Integrity Checking
Failure)
67176563 VS.IU.RelReqPS.Si Number of IU Earlier than

gConnRel RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in PS
Domain (UE
Signaling
Connection Release)

BSC6900 UMTS

Description
67176564 VS.IU.RelReqPS.U Number of IU Earlier than

ELost RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in PS
Domain (RL Out of
Synchronization)
67176566 VS.IU.RelCmdPS. Number of IU Earlier than

RelocSucc RELEASE V900R011
COMMAND
Messages Received
by RNC from CN in
PS Domain
(Relocation Success)

NormRel RELEASE V900R011
COMMAND
Messages Received
by RNC from CN in
PS Domain (Normal
Release)

UTRANGen RELEASE V900R011
COMMAND
Messages Received
by RNC from CN in
PS Domain (UTRAN
Generated)

RelocCanl RELEASE V900R011
COMMAND
Messages Received
by RNC from CN in
PS Domain
(Relocation
Cancelled)

NoRAB RELEASE V900R011
COMMAND
Messages Received
by RNC from CN in
PS Domain (No
Remaining RAB)

BSC6900 UMTS

Description
67176574 VS.Iu.RelReqPS.RI Number of IU Earlier than

PFail RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in PS
Domain (Failure in
the Radio Interface
Procedure)
67190183 VS.IU.RelReqPS.P Number of IU Earlier than

reempt RELEASE V900R011
REQUEST
Messages Sent by
RNC to CN in PS
Domain (RAB
Preempted)
67192541 VS.IU.Load.Route Number of Earlier than

PS.IMSI Performed PS Load V900R011
Balancing by IMSI
Users

PS.NRI Performed PS Load V900R011
Balancing by TMSI
Users Due to Invalid
NRI

PS.IMEI Performed PS Load V900R011
Balancing by IMEI
Users
67193096 VS.IU.FlowCtrl.Dis Number of Earlier than

c.InitDT.PS Discarded PS Initial V900R011
UE Messages when
Signaling Flow
Control is Triggered
73424971 VS.IU.PS.Paging Number of Paging V900R014

Messages Received
by RNC from CN in
PS Domain
73426319 VS.IU.RIM.L2U.SI Number of RIM V900R015

.Req Requests from the
eNodeB to the RNC
(System
Information)

BSC6900 UMTS

Description

.Resp Response Messages
from the RNC to the
eNodeB (System
Information)

.Update Update Messages
from the RNC to the
eNodeB (System
Information)

.Update.ACK acknowledgement
messages from the
eNodeB to the RNC
(System
Information)
73426323 VS.IU.RIM.L2U.L Number of RIM V900R015

oad.Req Requests from the
eNodeB to the RNC
(Load Information)

oad.Resp Response Messages
from the RNC to the
eNodeB (Load
Information)

oad.Update Update Messages
from the RNC to the
eNodeB (Load
Information)

oad.Update.ACK Acknowledgement
Messages from the
eNodeB to the RNC
(Load Information)
None
1.4.6.1 Number of RESET Messages Initiated by RNC to PS Domain

BSC6900 UMTS
Counters
67176481 VS.IU.ResetPS.Tx Number of RESET Messages

Sent by RNC to CN in PS
Domain
Description
This measurement counter takes statistics of the number of RESET messages that the RNC sends
to the PS domain. The RNC measures this counter according to the CN nodes.
Measurement point
The measurement is triggered when the RNC sends a RESET message to the PS domain of the
CN, as shown by point A in the following figure. If the RNC does not receive the RESET
ACKNOWLEDGE message from the CN before the response timer expires, the RNC sends the
RESET message again and this counter is also measured again.
Figure 1-48 PS domain reset procedure initiated by the RNC (successful operation)
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IU.ResetPS.Tx WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.6.2 Number of RESET Messages Received by RNC from PS Domain
Counters
67176485 VS.IU.ResetPS.Rx Number of RESET Messages

in PS Domain
Description
This measurement counter takes statistics of the number of RESET messages that the PS domain
sends to the RNC. The RNC measures this counter according to the CN nodes.
Measurement point
RESET message from the PS domain, it measures this counter.

BSC6900 UMTS
Figure 1-49 PS domain reset procedure initiated by the CN (successful operation)
Formula
None
Unit
None
Related Features
VS.IU.ResetPS.Rx WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.6.3 Number of INITIAL UE MESSAGE Messages from RNC to PS Domain

BSC6900 UMTS
Counters
67189921 VS.IU.SIG.AttConnEstabPS Number of INITIAL UE

MESSAGE Messages Sent
by RNC to CN in PS Domain
Description
This measurement counter takes statistics of the number of INITIAL UE MESSAGE messages
that the RNC sends to the PS domain. The RNC measures this counter according to the CN
nodes.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends an
INITIAL UE MESSAGE to the PS domain, it measures this counter.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.IU.SIG.AttConnEstabPS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.6.4 Number of IU RELEASE REQUEST Messages from RNC to PS Domain
Counters
67176559 VS.IU.RelReqPS.sum Number of IU RELEASE

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
RELEASE REQUEST message to the PS domain, it measures this counter.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.RelReqPS.sum WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.6.5 Number of IU RELEASE COMMAND Messages from PS Domain to RNC

BSC6900 UMTS
Counters
67176565 VS.IU.RelCmdPS.sum Number of IU RELEASE

COMMAND Messages
in PS Domain
Description
This measurement counter takes statistics of the number of IU RELEASE COMMAND
messages that the PS domain sends to the RNC. The RNC measures this counter according to
the CN nodes. The Iu release procedure of the PS domain is a procedure to release the Iu
connection and all the UTRAN resources related to the Iu connection.
Measurement point
The measurement is triggered at point B, as shown in the figure. In the RNC-initiated Iu release
procedure, when the RNC receives an IU RELEASE COMMAND message from the PS domain,
it measures this counter.
The measurement is triggered at point A, as shown in the figure. In the CN-initiated Iu release
it measures this counter.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.RelCmdPS.sum WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.6.6 Number of ERROR INDICATION Messages from RNC to PS Domain

BSC6900 UMTS
Counters
67176530 VS.IU.ErrInd.PS.Tx Number of ERROR

INDICATION Messages
Sent by RNC to CN in PS
Domain
Description
that the RNC sends to the PS domain.
Measurement point
INDICATION message to the PS domain, it measures this counter.
Figure 1-54 Error indication procedure initiated by the RNC
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.IU.ErrInd.PS.Tx WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.6.7 Number of ERROR INDICATION Messages from PS Domain to RNC
Counters
67176532 VS.IU.ErrInd.PS.Rx Number of ERROR

INDICATION Messages
in PS Domain
Description
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.

BSC6900 UMTS
Figure 1-55 Error indication procedure initiated by the CN
Formula
None
Unit
None
Related Features
VS.IU.ErrInd.PS.Rx WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.6.8 Number of IU RELEASE REQUEST Messages from RNC to PS Domain for

Different Causes

BSC6900 UMTS
Counters
67176561 VS.IU.RelReqPS.UsrInact Number of IU RELEASE

(User Inactive)
67176562 VS.IU.RelReqPS.In- Number of IU RELEASE

gChkFail REQUEST Messages Sent
(Repeated Integrity
Checking Failure)
67176563 VS.IU.RelReqPS.SigConn- Number of IU RELEASE

Rel REQUEST Messages Sent
Release)
67176564 VS.IU.RelReqPS.UELost Number of IU RELEASE

(RL Out of Synchronization)
67176574 VS.Iu.RelReqPS.RIPFail Number of IU RELEASE

67190183 VS.IU.RelReqPS.Preempt Number of IU RELEASE

(RAB Preempted)
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
RELEASE REQUEST message to the PS domain, it measures these counters according to
different causes.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.RelReqPS.UsrInact WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IU.RelReqPS.In- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

gChkFail Connection and Radio
and Release
VS.IU.RelReqPS.SigConn- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
VS.IU.RelReqPS.UELost WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.Iu.RelReqPS.RIPFail WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IU.RelReqPS.Preempt WRFD-010505 Queuing and Pre-Emption

WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release
1.4.6.9 Number of IU RELEASE COMMAND Messages from PS Domain to RNC

Counters
67176566 VS.IU.RelCmdPS.Reloc- Number of IU RELEASE

Succ COMMAND Messages
in PS Domain (Relocation
Success)
67176567 VS.IU.RelCmdPS.NormRel Number of IU RELEASE

COMMAND Messages
in PS Domain (Normal
Release)
67176568 VS.IU.RelCmdPS.UTRAN- Number of IU RELEASE

Gen COMMAND Messages
in PS Domain (UTRAN
Generated)
67176569 VS.IU.RelCmdPS.Reloc- Number of IU RELEASE

Canl COMMAND Messages
in PS Domain (Relocation
Cancelled)

BSC6900 UMTS
67176570 VS.IU.RelCmdPS.NoRAB Number of IU RELEASE

COMMAND Messages
in PS Domain (No
Remaining RAB)
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
it measures these counters.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.RelCmdPS.Reloc- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Succ Connection and Radio
and Release
VS.IU.RelCmdPS.NormRel WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IU.RelCmdPS.UTRAN- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
VS.IU.RelCmdPS.Reloc- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Canl Connection and Radio
and Release
VS.IU.RelCmdPS.NoRAB WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.6.10 Load Balancing of the MSC Pool on the PS Domain
Counters
67192541 VS.IU.Load.RoutePS.IMSI Number of Performed PS

Load Balancing by IMSI
Users
67192542 VS.IU.Load.RoutePS.NRI Number of Performed PS

Load Balancing by TMSI
Users Due to Invalid NRI
67192543 VS.IU.Load.RoutePS.IMEI Number of Performed PS

Load Balancing by IMEI
Users
Description
The measurement counters provide the number of times that the UEs perform load balancing on
the PS domain during CN node selection when the RNC processes the initial direct transfer
message.
VS.IU.Load.RoutePS.IMSI Number of times that the PS CN is selected

for load balancing by using the IMSI route
parameter.

BSC6900 UMTS
VS.IU.Load.RoutePS.NRI Number of times that load balancing is

triggered due to invalid NRI route parameter,
connection failure to the CN node
corresponding to the route parameter, or the
flow control of the CN node corresponding to
the route parameter.
VS.IU.Load.RoutePS.IMEI Number of times that the PS CN is selected

for load balancing by using the IMEI route
parameter.
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

BSC6900 UMTS
Unit
None
Related Features
VS.IU.Load.RoutePS.IMSI WRFD-021306 Iu Flex Load Distribution

Management
VS.IU.Load.RoutePS.NRI WRFD-021306 Iu Flex Load Distribution

Management
VS.IU.Load.RoutePS.IMEI WRFD-021306 Iu Flex Load Distribution

Management
1.4.6.11 Number of Discarded Initial UE messages Under Iu Signaling Flow Control

(PS Domain)
Counters
67193096 VS.IU.FlowCtrl.Disc.InitDT Number of Discarded PS

.PS Initial UE Messages when
Signaling Flow Control is
Triggered
Description
This measurement counter provides the number of initial UE messages discarded under the
SCCP flow control when the RNC receives the PS initial direct transfer message.
Measurement point
The measurement is triggered when the RNC receives an INITIAL DIRECT TRANSFER
message from a UE and then discards this message because the RNC finds that the Iu-PS interface
is under flow control. Then, the RNC does not send the INITIAL UE MESSAGE message to
the CN.

BSC6900 UMTS
Figure 1-60 Process of discarding INITIAL DIRECT TRANSFER message
Formula
None
Unit
None
Related Features
VS.IU.FlowCtrl.Disc.InitDT WRFD-040100 Flow Control

.PS
1.4.6.12 Number of Paging Messages Received by RNC from CN in PS Domain
Counters
73424971 VS.IU.PS.Paging Number of Paging Messages

in PS Domain

BSC6900 UMTS
Description
This measurement counter provides the number of PAGING messages that the PS domain sends
to the RNC according to respective CN nodes.
Measurement point
The measurement is triggered at point A shown in the following figure when both of the
following conditions are met: -The RNC receives a paging message from the CN. -The value of
the CN Domain Indicator IE contained in the message indicates the PS domain.
Figure 1-61 Paging messages sent from the CN to the UE
Formula
None
Unit
None
Related Features
VS.IU.PS.Paging WRFD-010301 Paging UE in Idle,

State (Type 1)

BSC6900 UMTS
1.4.6.13 Number of RIM Requests from the eNodeB to the RNC (System
Information)
Counters
73426319 VS.IU.RIM.L2U.SI.Req Number of RIM Requests

from the eNodeB to the RNC
(System Information)
Description
This counter provides the number of RIM requests with system information the RNC receives
from the eNodeB. The RIM requests include RAN-INFORMATION-REQUEST/Single Report
and RAN-INFORMATION-REQUEST/Multiple Report.
Measurement point
The measurement is triggered at point A as shown in Figure 1. This counter is incremented by
1 when the RNC receives the RAN-INFORMATION-REQUEST/Single Report or RAN-
INFORMATION-REQUEST/Multiple Report message with system information from the
eNodeB on the Iu interface.
Figure 1-62 RIM message procedure(single mode)

INFORMATION-REQUEST/Multiple Report message with system information from the
eNodeB on the Iu interface.

BSC6900 UMTS
Figure 1-63 RIM message procedure(Multiple mode)
Formula
None
Unit
None
Related Features
VS.IU.RIM.L2U.SI.Req WRFD-140224 Fast CS Fallback Based on

RIM
1.4.6.14 Number of RIM Response Messages from the RNC to the eNodeB (System
Information)

BSC6900 UMTS
Counters
73426320 VS.IU.RIM.L2U.SI.Resp Number of RIM Response

Messages from the RNC to
the eNodeB (System
Information)
Description
This counter provides the number of RIM response messages with system information the RNC
sends to the eNodeB. The RIM response messages include RAN-INFORMATION/Single
Report and RAN-INFORMATION/Multiple Report-Initial.
Measurement point
The measurement is triggered at point B as shown in Figure 1. This counter is incremented by
1 when the RNC sends to the eNodeB the RAN-INFORMATION/Single Report or RAN-
INFORMATION/Multiple Report-Initial message with system information on the Iu interface.

INFORMATION/Multiple Report-Initial message with system information on the Iu interface.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.RIM.L2U.SI.Resp WRFD-140224 Fast CS Fallback Based on

RIM
1.4.6.15 Number of RIM Update Messages from the RNC to the eNodeB (System
Information)

BSC6900 UMTS
Counters
73426321 VS.IU.RIM.L2U.SI.Update Number of RIM Update

the eNodeB (System
Information)
Description
This counter provides the number of RIM update messages with system information the RNC
sends to the eNodeB. The RAN-INFORMATION/Multiple Report-Initial message is excluded.
Measurement point
The measurement is triggered at point C as shown in Figure 2. This counter is incremented by
1 when the RNC sends to the eNodeB the RAN-INFORMATION/Multiple Report message with
system information on the Iu interface.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IU.RIM.L2U.SI.Update WRFD-140224 Fast CS Fallback Based on

RIM
1.4.6.16 Number of RIM acknowledgement messages from the eNodeB to the RNC
Counters
73426322 VS.IU.RIM.L2U.SI.Update. Number of RIM

ACK acknowledgement messages
Description
This counter provides the number of RIM acknowledgement messages with system information
the RNC receives from the eNodeB.
Measurement point
The measurement is triggered at point D as shown in Figure 2. This counter is incremented by
1 when the RNC receives the RAN-INFORMATION-ACK message with system information
from the eNodeB on the Iu interface.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.RIM.L2U.SI.Update. WRFD-140224 Fast CS Fallback Based on

ACK RIM
1.4.6.17 Number of RIM Requests from the eNodeB to the RNC (Load Information)

BSC6900 UMTS
Counters
73426323 VS.IU.RIM.L2U.Load.Req Number of RIM Requests

(Load Information)
Description
This counter provides the number of RIM requests with load information the RNC receives from
the eNodeB. The RIM requests include RAN-INFORMATION-REQUEST/Single Report and
RAN-INFORMATION-REQUEST/Multiple Report.
Measurement point
INFORMATION-REQUEST/Multiple Report message with load information from the eNodeB
on the Iu interface.

INFORMATION-REQUEST/Multiple Report message with load information from the eNodeB
on the Iu interface.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.RIM.L2U.Load.Req WRFD-150231 RIM Based UMTS Target

Cell Selection for LTE
1.4.6.18 Number of RIM Response Messages from the RNC to the eNodeB (Load
Information)

BSC6900 UMTS
Counters
73426324 VS.IU.RIM.L2U.Load.Resp Number of RIM Response

the eNodeB (Load
Information)
Description
This counter provides the number of RIM response messages with load information the RNC
sends to the eNodeB. The RIM response messages include RAN-INFORMATION/Single
Report and RAN-INFORMATION/Multiple Report-Initial.
Measurement point
INFORMATION/Multiple Report-Initial message with load information on the Iu interface.

INFORMATION/Multiple Report-Initial message with load information on the Iu interface.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.RIM.L2U.Load.Resp WRFD-150231 RIM Based UMTS Target

Cell Selection for LTE
1.4.6.19 Number of RIM Update Messages from the RNC to the eNodeB (Load
Information)

BSC6900 UMTS
Counters
73426325 VS.IU.RIM.L2U.Load.Up- Number of RIM Update

date Messages from the RNC to
the eNodeB (Load
Information)
Description
This counter provides the number of RIM update messages with load information the RNC sends
to the eNodeB. The RAN-INFORMATION/Multiple Report-Initial message is excluded.
Measurement point
The measurement is triggered at point C as shown in Figure 2. This counter is incremented by
1 when the RNC sends to the eNodeB the RAN-INFORMATION/Multiple Report message with
load information on the Iu interface.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IU.RIM.L2U.Load.Up- WRFD-150231 RIM Based UMTS Target

date Cell Selection for LTE
1.4.6.20 Number of RIM Acknowledgement Messages from the eNodeB to the RNC
(Load Information)
Counters
73426326 VS.IU.RIM.L2U.Load.Upda Number of RIM

te.ACK Acknowledgement
Messages from the eNodeB
to the RNC (Load
Information)
Description
This counter provides the number of RIM acknowledgement messages with load information
the RNC receives from the eNodeB.
Measurement point
The measurement is triggered at point D as shown in Figure 2. This counter is incremented by
1 when the RNC receives the RAN-INFORMATION-ACK message with load information from
the eNodeB on the Iu interface.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.RIM.L2U.Load.Upda WRFD-150231 RIM Based UMTS Target

te.ACK Cell Selection for LTE
1.4.7 Measurement related to PS traffic(PS.TRF.IU)
Overview
This function subset is used to measure the UL and DL traffic for various services of the PS
domain on the Iu interface.Without specific instructions,the measurement contains the header
of GTPU.

BSC6900 UMTS
Counters
Description
67203893 VS.IuPS.BytesPayl Number of UL Bytes Earlier than

dConv.Tx of PS Conversational V900R011
Service on Iu-PS
Interface

dStr.Tx of PS Streaming V900R011
Service on Iu-PS
Interface

dIntact.Tx of PS Interactive V900R011
Service on Iu-PS
Interface

dBgrd.Tx of PS Background V900R011
Service on Iu-PS
Interface
67203895 VS.IuPS.BytesPayl Number of DL Bytes Earlier than

dConv.Rx of PS Conversational V900R011
Service on Iu-PS
Interface

dStr.Rx of PS Streaming V900R011
Service on Iu-PS
Interface

dIntact.Rx of PS Interactive V900R011
Service on Iu-PS
Interface

dBgrd.Rx of PS Background V900R011
Service on Iu-PS
Interface
67204829 VS.IuPS.GoldenBE Number of UL Bytes Earlier than

.Bytes.Tx of PS BE Service for V900R011
Golden Subscriber
on Iu-PS Interface
67204830 VS.IuPS.SilverBE. Number of UL Bytes Earlier than

Bytes.Tx of PS BE Service for V900R011
Silver Subscriber on
Iu-PS Interface

BSC6900 UMTS

Description
67204831 VS.IuPS.CopperB Number of UL Bytes Earlier than

E.Bytes.Tx of PS BE Service for V900R011
Copper Subscriber
on Iu-PS Interface
67204832 VS.IuPS.GoldenBE Number of DL Bytes Earlier than

.Bytes.Rx of PS BE Service for V900R011
Golden Subscriber
on Iu-PS Interface
67204833 VS.IuPS.SilverBE. Number of DL Bytes Earlier than

Bytes.Rx of PS BE Service for V900R011
Silver Subscriber on
Iu-PS Interface
67204834 VS.IuPS.CopperB Number of DL Bytes Earlier than

E.Bytes.Rx of PS BE Service for V900R011
Copper Subscriber
on Iu-PS Interface
73441084 VS.IuPS.BytesPayl Total HTTP Traffic V900R013

dHTTP.Rx Volume on the RNC
73441081 VS.IuPS.BytesPayl Total P2P Traffic V900R013

dP2P.Rx Volume on the RNC
73441082 VS.IuPS.BytesPayl Total Traffic Volume V900R013

dSubs.Rx of all Subscribed
Services on the RNC
73441083 VS.IuPS.BytesPayl Total Traffic Volume V900R013

dUndefined.Rx of Undefined
Services on the RNC
73426124 VS.IuPS.BytesPayl Traffic Volume of V900R015

dUnawareness.RX Services Cannot Be
Identified by the
RNC on Downlink
None
1.4.7.1 Number of UL Bytes of PS Conversational Service on Iu Interface

BSC6900 UMTS
Counters
67203893 VS.IuPS.BytesPayldConv.T Number of UL Bytes of PS

Iu-PS Interface
Description
This counter provides the number of UL payload bytes of PS Conversational service data on the
Iu-PS interface sent by the RNC. The value of this counter includes the bytes of application layer
data without GTPU head.
Measurement point
When receiving the UL PS Conversational service data on the Iu-PS interface, the RNC measures
the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
VS.IuPS.BytesPayldConv.T WRFD-010501 Conversational QoS Class

x
1.4.7.2 Number of UL Bytes of PS Streaming Service on Iu Interface
Counters
67203894 VS.IuPS.BytesPayldStr.Tx Number of UL Bytes of PS

Streaming Service on Iu-PS
Interface

BSC6900 UMTS
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
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
VS.IuPS.BytesPayldStr.Tx WRFD-010502 Streaming QoS Class
1.4.7.3 Number of UL Bytes of PS Interactive Service on Iu Interface
Counters
67203897 VS.IuPS.BytesPayldIntact.T Number of UL Bytes of PS

x Interactive Service on Iu-PS
Interface
Description
This counter provides the number of UL payload bytes of PS interactive service data on the Iu-
Measurement point
When receiving the UL PS interactive service data on the Iu-PS interface, the RNC measures

BSC6900 UMTS
Formula
None
Unit
byte
Related Features
VS.IuPS.BytesPayldIntact.T WRFD-010503 Interactive QoS Class

x
1.4.7.4 Number of UL Bytes of PS Background Service on Iu Interface
Counters
67203898 VS.IuPS.BytesPayldBgrd.T Number of UL Bytes of PS

x Background Service on Iu-
PS Interface
Description
This counter provides the number of UL payload bytes of PS background service data on the Iu-
Measurement point
When receiving the UL PS background service data on the Iu-PS interface, the RNC measures
Formula
None
Unit
byte

BSC6900 UMTS
Related Features
VS.IuPS.BytesPayldBgrd.T WRFD-010504 Background QoS Class

x
1.4.7.5 Number of DL Bytes of PS Conversational Service on Iu Interface
Counters
67203895 VS.IuPS.BytesPayldConv.R Number of DL Bytes of PS

Iu-PS Interface
Description
This counter provides the number of DL payload bytes of PS Conversational service data on the
Iu-PS interface received by the RNC. The value of this counter includes the bytes of application
layer data without GTPU head.
Measurement point
When receiving the DL PS Conversational service data on the Iu-PS interface, the RNC measures
Formula
None
Unit
byte
Related Features
VS.IuPS.BytesPayldConv.R WRFD-010501 Conversational QoS Class

x
1.4.7.6 Number of DL Bytes of PS Streaming Service on Iu Interface

BSC6900 UMTS
Counters
67203896 VS.IuPS.BytesPayldStr.Rx Number of DL Bytes of PS

Streaming Service on Iu-PS
Interface
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
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
VS.IuPS.BytesPayldStr.Rx WRFD-010502 Streaming QoS Class
1.4.7.7 Number of DL Bytes of PS Interactive Service on Iu Interface
Counters
67203899 VS.IuPS.BytesPayldIntact.R Number of DL Bytes of PS

x Interactive Service on Iu-PS
Interface

BSC6900 UMTS
Description
This counter provides the number of DL payload bytes of PS interactive service data on the Iu-
Measurement point
When receiving the DL PS interactive service data on the Iu-PS interface, the RNC measures
Formula
None
Unit
byte
Related Features
VS.IuPS.BytesPayldIntact.R WRFD-010503 Interactive QoS Class

x
1.4.7.8 Number of DL Bytes of PS Background Service on Iu Interface
Counters
67203900 VS.IuPS.BytesPayldBgrd.R Number of DL Bytes of PS

x Background Service on Iu-
PS Interface
Description
This counter provides the number of DL payload bytes of PS background service data on the Iu-
Measurement point
When receiving the DL PS background service data on the Iu-PS interface, the RNC measures

BSC6900 UMTS
Formula
None
Unit
byte
Related Features
VS.IuPS.BytesPayldBgrd.R WRFD-010504 Background QoS Class

x
1.4.7.9 Number of UL Bytes of PS BE Service for Golden Subscriber on Iu Interface
Counters
67204829 VS.IuPS.GoldenBE.Bytes.T Number of UL Bytes of PS

x BE Service for Golden
Subscriber on Iu-PS Interface
Description
This counter provides the number of UL payload bytes of PS BE service data for golden
subscriber on the Iu-PS interface sent by the RNC. The value of this counter includes the bytes
of application layer data without GTPU head.
Measurement point
When sending the UL data of PS BE service for golden subscriber on the Iu-PS interface, the
RNC measures the counter according to different Iu-PS interfaces.
Formula
None
Unit
byte

BSC6900 UMTS
Related Features
VS.IuPS.GoldenBE.Bytes.T WRFD-02130403 Mobility Control and Service

x Differentiation
1.4.7.10 Number of UL Bytes of PS BE Service for Silver Subscriber on Iu Interface
Counters
67204830 VS.IuPS.SilverBE.Bytes.Tx Number of UL Bytes of PS

BE Service for Silver
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
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
VS.IuPS.SilverBE.Bytes.Tx WRFD-02130403 Mobility Control and Service

Differentiation
1.4.7.11 Number of UL Bytes of PS BE Service for Copper Subscriber on Iu Interface

BSC6900 UMTS
Counters
67204831 VS.IuPS.CopperBE.Bytes.T Number of UL Bytes of PS

x BE Service for Copper
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
Formula
None
Unit
byte
Related Features
VS.IuPS.CopperBE.Bytes.T WRFD-02130403 Mobility Control and Service

x Differentiation
1.4.7.12 Number of DL Bytes of PS BE Service for Golden Subscriber on Iu Interface
Counters
67204832 VS.IuPS.GoldenBE.Bytes.R Number of DL Bytes of PS

x BE Service for Golden

BSC6900 UMTS
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
Formula
None
Unit
byte
Related Features
VS.IuPS.GoldenBE.Bytes.R WRFD-02130403 Mobility Control and Service

x Differentiation
1.4.7.13 Number of DL Bytes of PS BE Service for Silver Subscriber on Iu Interface
Counters
67204833 VS.IuPS.SilverBE.Bytes.Rx Number of DL Bytes of PS

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

BSC6900 UMTS
Formula
None
Unit
byte
Related Features
VS.IuPS.SilverBE.Bytes.Rx WRFD-02130403 Mobility Control and Service

Differentiation
1.4.7.14 Number of DL Bytes of PS BE Service for Copper Subscriber on Iu Interface
Counters
67204834 VS.IuPS.CopperBE.Bytes.R Number of DL Bytes of PS

x BE Service for Copper
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
Formula
None
Unit
byte

BSC6900 UMTS
Related Features
VS.IuPS.CopperBE.Bytes.R WRFD-02130403 Mobility Control and Service

x Differentiation
1.4.7.15 Total HTTP Traffic Volume on the RNC
Counters
73441084 VS.IuPS.BytesPayldHTTP. Total HTTP Traffic Volume

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

Rx
1.4.7.16 Total P2P Traffic Volume on the RNC

BSC6900 UMTS
Counters
73441081 VS.IuPS.BytesPayldP2P.Rx Total P2P Traffic Volume on

the RNC
Description
This counter provides the number of bytes of downlink P2P services received on the Iu-PS
interface of the RNC. It includes the data at the application layer and excludes the GTP-U header.
The P2P service type is identified by service awareness when the P2P Downloading Rate Control
during Busy Hour feature is enabled.
Measurement point
P2P traffic data on Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
VS.IuPS.BytesPayldP2P.Rx WRFD-020133 P2P Downloading Rate

Control during Busy Hour
1.4.7.17 Total Traffic Volume of all Subscribed Services on the RNC
Counters
73441082 VS.IuPS.BytesPayldSubs.R Total Traffic Volume of all

x Subscribed Services on the
RNC

BSC6900 UMTS
Description
This counter provides the number of bytes of downlink subscribed services received on the Iu-
PS interface of the RNC. It includes the data at the application layer and excludes the GTPU
header. The subscribed service is defined by the Quality Improvement for Subscribed Service
feature.
Measurement point
data of subscribed services on Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
VS.IuPS.BytesPayldSubs.R WRFD-020128 Quality Improvement for

x Subscribed Service
1.4.7.18 Total Traffic Volume of Undefined Services on the RNC
Counters
73441083 VS.IuPS.BytesPayldUndefin Total Traffic Volume of

ed.Rx Undefined Services on the
RNC
Description
This counter provides the number of bytes of downlink undefined services received on the Iu-
PS interface of the RNC. It includes the data at the application layer and excludes the GTP-U
header. Undefined services are services other than the HTTP services, P2P services, subscribed
services, and unidentified services.
Measurement point
data of undefined services on Iu-PS interfaces.

BSC6900 UMTS
Formula
None
Unit
byte
Related Features
VS.IuPS.BytesPayldUndefin WRFD-020132 Web browsing acceleration

ed.Rx WRFD-020133 P2P Downloading Rate
WRFD-020128 Control during Busy Hour
Quality Improvement for
Subscribed Service
1.4.7.19 Traffic Volume of Services Cannot Be Identified by the RNC on Downlink
Counters
73426124 VS.IuPS.BytesPayldUnawar Traffic Volume of Services

eness.RX Cannot Be Identified by the
RNC on Downlink
Description
This counter provides the number of bytes of downlink unidentified services received on the Iu-
PS interface of the RNC. It includes the data at the application layer and excludes the GTPU
header. Unidentified services are those whose service type cannot be identified by service
awareness.
Measurement point
The measurement is triggered when the RNC receives downlink service data on the Iu-PS
interface. The traffic volume is measured on each Iu-PS interface separately.
Formula
None
Unit
byte

BSC6900 UMTS
Related Features
VS.IuPS.BytesPayldUnawar WRFD-020132 Web browsing acceleration

eness.RX WRFD-020133 P2P Downloading Rate
WRFD-020128 Control during Busy Hour
Quality Improvement for
Subscribed Service
1.4.8 Measurement Related to SCCP for Iu Interface(SIG.SCCP.IU)

Overview
Measurement related to SCCP for Iu interface provides the counters related to the numbers of
the RNC-initiated SCCP connection requests, RNC-initiated successful SCCP connection
requests, CN-initiated SCCP connection requests, and CN-initiated successful SCCP connection
requests.
Counters
Description
67195049 VS.IU.SCCP.Tx.Co Number of SCCP Earlier than

n.Req Connection Requests V900R011
Sent to the CN
Through the Iu
Interface
67195050 VS.IU.SCCP.Tx.Co Number of Earlier than

n.Succ Successful SCCP V900R011
Connection Requests
Sent to the CN
Through the Iu
Interface
67195051 VS.IU.SCCP.Rx.C Number of SCCP Earlier than

on.Req Connection Requests V900R011
from the CN
Through the Iu
Interface
67195052 VS.IU.SCCP.Rx.C Number of Earlier than

on.Succ Successful SCCP V900R011
Connection Requests
from the CN
Through the Iu
Interface

BSC6900 UMTS
None
1.4.8.1 Number of SCCP Connection Requests Sent by the RNC to the CN Through
the Iu Interface
Counters
67195049 VS.IU.SCCP.Tx.Con.Req Number of SCCP

Connection Requests Sent to
the CN Through the Iu
Interface
Description
This counter provides the number of SCCP connection requests (CRs) that the RNC sends to
the CN based on the corresponding CN node.
Measurement point
The measurement is triggered at point A as shown in the figure. In the measurement period, the
counter is incremented by one when the RNC RANAP sends a SCCP connection request (CR)
message to the CN.
Figure 1-74 SCCP connection procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.SCCP.Tx.Con.Req WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.8.2 Number of Successful SCCP Connection Requests Sent by the RNC to the
CN Through the Iu Interface
Counters
67195050 VS.IU.SCCP.Tx.Con.Succ Number of Successful SCCP

Interface
Description
This counter provides the number of successful SCCP connection requests sent by the RNC to
the CN based on the corresponding CN node.
Measurement point
The measurement is triggered at point B as shown in the figure. This counter is incremented by
one when the local RNC RANAP receives a Connection Confirm (CC) message from the CN
after sending a Connection Request (CR) message to the CN.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.SCCP.Tx.Con.Succ WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.8.3 Number of SCCP Connection Requests Received by the RNC from the CN
Through the Iu Interface

BSC6900 UMTS
Counters
67195051 VS.IU.SCCP.Rx.Con.Req Number of SCCP

Connection Requests from
Interface
Description
This counter provides the number of SCCP connection requests received by the RNC from the
CN based on the corresponding CN node.
Measurement point
The measurement is triggered at point A as shown in the figure. In the measurement period, the
counter is incremented by one when the RNC RANAP receives a SCCP CR message from the
CN.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IU.SCCP.Rx.Con.Req WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.4.8.4 Number of Successful SCCP Connection Requests Received by the RNC

from the CN Through the Iu Interface
Counters
67195052 VS.IU.SCCP.Rx.Con.Succ Number of Successful SCCP

Interface
Description
This counter provides the number of successful SCCP connection requests received by the RNC
from the CN based on the corresponding CN node.
Measurement point
The measurement is triggered at point B as shown in the figure. This counter is incremented by
one when the local RNC RANAP sends a Connection Confirm (CC) message to the CN after
receiving a Connection Request (CR) message from the CN.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.SCCP.Rx.Con.Succ WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.5 Measurement of IUR Interface Performance(IUR)

Overview
Iur Interface Measurement (IUR) is used to measure the performance of signaling procedures
and traffic flows on the Iur interface.

BSC6900 UMTS
FunctionSubSets
DRNC.IUR Measurement related to DRNC in Iur

interface
RESERVE.IUR Reserved counter for Iur interface
SIG.SCCP.IUR Measurement Related to SCCP for Iur

Interface
SRNC.IUR Measurement related to SRNC in Iur

interface
TRFFIC.IUR Measurement related to traffic for Iur

Interface
1.5.1 Measurement related to DRNC in Iur interface(DRNC.IUR)
Overview
The DRNC Iur Interface Measurement involves measurements of DCH procedures and common
transport channel procedures. The DCH procedures include: RL setup procedures, RL addition
procedures, RL deletion procedures, Synchronized RL reconfiguration procedures, RL failure
procedures, RL restoration procedures; The common transport channel procedures include
common transport channel setup procedures and common transport channel release procedures.
Counters
Description
67179009 VS.SHO.ErrIndIur Number of Error Earlier than

.Rx Indication Messages V900R011
Received on Iur
Interface for DRNC
67179010 VS.SHO.ErrIndIur Number of Error Earlier than

.Tx Indication Messages V900R011
Sent on Iur Interface
for DRNC
67179089 VS.SHO.AttRLSet Number of Radio Earlier than

upIur.Rx Link Setup Requests V900R011
on Iur Interface for
DRNC

BSC6900 UMTS

Description
67179090 VS.SHO.SuccRLSe Number of Earlier than

tupIur.Tx Successful Radio V900R011
Link Setups on Iur
Interface for DRNC
67179092 VS.SHO.FailRLSet Number of Failed Earlier than

upIur.HW.Tx Radio Link Setups on V900R011
Iur Interface for
DRNC (Device
Fault)

upIur.CongTx Radio Link Setups on V900R011
Iur Interface for
DRNC (Congestion)

upIur.CfgUTx Radio Link Setups on V900R011
Iur Interface for
DRNC
(Configuration
Unsupported)
67179096 VS.SHO.AttRLDel Number of Radio Earlier than

Iur.Rx Link Deletion V900R011
Requests on Iur
Interface for DRNC
67179097 VS.SHO.SuccRLD Number of Earlier than

elIur.Tx Successful Radio V900R011
Link Deletions on Iur
Interface for DRNC
67179098 VS.SHO.AttRLAd Number of Radio Earlier than

dIur.Rx Link Addition V900R011
Requests on Iur
Interface for DRNC
67179099 VS.SHO.SuccRLA Number of Earlier than

ddIur.Tx Successful Radio V900R011
Link Additions on
Iur Interface for
DRNC
67179100 VS.SHO.FailRLAd Number of Failed Earlier than

dIur.OM.Tx Radio Link V900R011
Additions on Iur
Interface for DRNC
(OM Intervention)

BSC6900 UMTS

Description

dIur.HW.Tx Radio Link V900R011
Additions on Iur
Interface for DRNC
(Device Fault)

dIur.Cong.Tx Radio Link V900R011
Additions on Iur
Interface for DRNC
(Congestion)

dIur.CfgUnsTx Radio Link V900R011
Additions on Iur
Interface for DRNC
(Configuration
Unsupported)
67179105 VS.SHO.AttRLRec Number of Radio Earlier than

fgIur.Rx Link Synchronous V900R011
Reconfiguration
Requests on Iur
Interface for DRNC
67179106 VS.SHO.SuccRLR Number of Earlier than

ecfgIur.Tx Successful Radio V900R011
Link Synchronous
Reconfigurations on
Iur Interface for
DRNC
67179109 VS.SHO.FailRLRe Number of Failed Earlier than

cfgIur.CongTx Radio Link V900R011
Synchronous
Reconfigurations on
Iur Interface for
DRNC (Congestion)

cfgIur.CfgUTx Radio Link V900R011
Synchronous
Reconfigurations on
Iur Interface for
DRNC
(Configuration
Unsupported)

BSC6900 UMTS

Description

cfgIur.OM.Tx Radio Link V900R011
Synchronous
Reconfigurations on
Iur Interface for
DRNC (OM
Intervention)

cfgIur.HW.Tx Radio Link V900R011
Synchronous
Reconfigurations on
Iur Interface for
DRNC (Device
Fault)

cfgIur.Trans- Radio Link V900R011
CongRx Synchronous
Reconfigurations on
Iur Interface for
DRNC (Transport
Resource
Unavailable)

upIur.Trans- Radio Link Setups on V900R011
CongTx Iur Interface for
DRNC (Transport
Resource
Unavailable)

dIur.TransCong.T Radio Link V900R011
x Additions on Iur
Interface for DRNC
(Transport Resource
Unavailable)
67179112 VS.SHO.CancelRL Number of Radio Earlier than

RecfgIur.Rx Link Synchronous V900R011
Reconfiguration
Cancellations on Iur
Interface for DRNC
67179113 VS.SHO.RLFail.Tx Number of Radio Earlier than

Link Failures on Iur V900R011
Interface for DRNC

BSC6900 UMTS

Description
67179114 VS.SHO.RLFail.O Number of Radio Earlier than

M.Tx Link Failures on Iur V900R011
Interface for DRNC
(OM Intervention)
67179115 VS.SHO.RLFail.H Number of Radio Earlier than

W.Tx Link Failures on Iur V900R011
Interface for DRNC
(Device Fault)
67179116 VS.SHO.RLFail.Sy Number of Radio Earlier than

ncFail.Tx Link Failures on Iur V900R011
Interface for DRNC
(Synchronization
Failure)
67179117 VS.SHO.RLFail.Cf Number of Radio Earlier than

gUnsup.Tx Link Failures on Iur V900R011
Interface for DRNC
(Configuration
Unsupported)
67190048 VS.SHO.RLFail.Ot Number of Radio Earlier than

her.Tx Link Failures on Iur V900R011
Interface for DRNC
(Other Reasons)
67179118 VS.SHO.RLRestor Number of Radio Earlier than

e.Tx Link Restorations on V900R011
Iur Interface for
DRNC
67179119 VS.IUR.AttCom- Number of Common Earlier than

TraChResDRNC Transport Channel V900R011
Resource Requests
DRNC
67179120 VS.IUR.SuccCom- Number of Common Earlier than

TraChResDRNC Transport Channel V900R011
Resource Responses
DRNC

BSC6900 UMTS

Description
67179121 VS.IUR.FailCTCR Number of Common Earlier than

DRNC.NotSupp Transport Channel V900R011
Resource Failures
Due to Transport
Resource
Unavailable on Iur
Interface for DRNC
67179122 VS.IUR.AttRel- Number of Common Earlier than

CoTrChResDRNC Transport Channel V900R011
Resource Release
Requests on Iur
Interface for DRNC
73423641 VS.SHO.FailRLSet Number of Failed V900R014

upIur.NodeBReHo Radio Link Setups on
st.Tx Iur interface for
DRNC (NodeB
Rehoming)
73423642 VS.SHO.FailRLAd Number of Failed V900R014

dIur.NodeBReHost Radio Link
.Tx Additions on Iur
interface for DRNC
(NodeB Rehoming)
Counter Sub Counter
VS.SHO.RLFail.Tx VS.SHO.RLFail.OM.Tx
VS.SHO.RLFail.HW.Tx
VS.SHO.RLFail.SyncFail.Tx
VS.SHO.RLFail.CfgUnsup.Tx
VS.SHO.RLFail.Other.Tx
1.5.1.1 Number of ERROR INDICATION Messages Received by the RNC on Iur

Interface

BSC6900 UMTS
Counters
67179009 VS.SHO.ErrIndIur.Rx Number of Error Indication

Messages Received on Iur
Interface for DRNC
Description
This counter provides the number of ERROR INDICATION messages received on the Iur
interface for the DRNC.
Measurement point
The measurement is triggered at point A, as shown in the figure. When a RNC receives an
ERROR INDICATION message from another RNC, it measures this item.
Figure 1-78 Error indication receiving procedure (successful operation)
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.SHO.ErrIndIur.Rx WRFD-020203 Inter RNC Soft Handover
1.5.1.2 Number of ERROR INDICATION Messages Sent by the RNC on Iur

Interface
Counters
67179010 VS.SHO.ErrIndIur.Tx Number of Error Indication

Messages Sent on Iur
Interface for DRNC
Description
This counter provides the number of ERROR INDICATION messages sent on the Iur interface
for the DRNC.
Measurement point
INDICATION message to another RNC, it measures this item.
Figure 1-79 Error indication sending procedure on the Iur interface

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SHO.ErrIndIur.Tx WRFD-020203 Inter RNC Soft Handover
1.5.1.3 Number of Requests to Establish a Radio Link Received by DRNC on Iur

Interface
Counters
67179089 VS.SHO.AttRLSetupIur.Rx Number of Radio Link Setup

Requests on Iur Interface for
DRNC
Description
This measurement item takes statistics of the number of Radio Links that a DRNC requested to
establish on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC receives a
RADIO LINK SETUP REQUEST message from the SRNC, it measures this item on each Iur
interface.

BSC6900 UMTS
Figure 1-80 Radio Link setup procedure on the Iur interface (successful operation)
Formula
None
Unit
None
Related Features
VS.SHO.AttRLSetupIur.Rx WRFD-020203 Inter RNC Soft Handover
1.5.1.4 Number of Successful Radio Link Establishments by DRNC on Iur Interface
Counters
67179090 VS.SHO.SuccRLSetupIur.T Number of Successful Radio

x Link Setups on Iur Interface
for DRNC

BSC6900 UMTS
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.
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.

BSC6900 UMTS
Figure 1-82 Radio Link setup procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
VS.SHO.SuccRLSetupIur.T WRFD-020203 Inter RNC Soft Handover

x
1.5.1.5 Number of Radio Links Unsuccessfully Established by DRNC on Iur

Interface for Different Causes

BSC6900 UMTS
Counters
67179092 VS.SHO.FailRLSetupIur.H Number of Failed Radio Link

W.Tx Setups on Iur Interface for
DRNC (Device Fault)
67179093 VS.SHO.FailRLSetupIur.Co Number of Failed Radio Link

ngTx Setups on Iur Interface for
DRNC (Congestion)
67179094 VS.SHO.FailRLSetupIur.Cf Number of Failed Radio Link

gUTx Setups on Iur Interface for
DRNC (Configuration
Unsupported)
67192580 VS.SHO.FailRLSetupIur.Tr Number of Failed Radio Link

ansCongTx Setups on Iur Interface for
DRNC (Transport Resource
Unavailable)
73423641 VS.SHO.FailRLSetupIur.No Number of Failed Radio Link

deBReHost.Tx Setups on Iur interface for
DRNC (NodeB Rehoming)
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.
VS.SHO.FailRLSetupIur.HW.Tx Number of radio links unsuccessfully

established by DRNC on Iur interface
because of hardware failure (cause value:
Hardware Failure)
VS.SHO.FailRLSetupIur.CongTx Number of radio links unsuccessfully

because of insufficient RNC capability (cause
value: Cell not Available, UL Scrambling
Code Already in Use, DL Radio Resources
not Available, UL Radio Resources not
Available, Combining Resources not
Available, Measurement Temporarily not
Available, Cell Reserved for Operator Use,
Control Processing Overload, or Not enough
User Plane Processing Resources)

BSC6900 UMTS
VS.SHO.FailRLSetupIur.CfgUTx Number of radio links unsuccessfully

because of improper configurations (cause
value: Combining not Supported, UL
Spreading Factor not Supported, DL
Spreading Factor not Supported, Requested
Tx Diversity Mode not supported, or CM not
Supported)
VS.SHO.FailRLSetupIur.TransCongTx Number of radio links unsuccessfully

because of insufficient RNC transmission
capability (cause value: Transport Resource
Unavailable)
VS.SHO.FailRLSetupIur.NodeBReHost.Tx Number of radio links unsuccessfully

because of NodeB Rehoming (cause value:
NodeB Rehoming)
Measurement point
SRNC a RADIO LINK SETUP FAILURE message with failure causes, the items are measured
on each Iur interface according to different causes.
Figure 1-83 Radio Link setup procedure on the Iur interface (failed operation)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SHO.FailRLSetupIur.H WRFD-020203 Inter RNC Soft Handover

W.Tx
VS.SHO.FailRLSetupIur.Co WRFD-020203 Inter RNC Soft Handover

ngTx
VS.SHO.FailRLSetupIur.Cf WRFD-020203 Inter RNC Soft Handover

gUTx
VS.SHO.FailRLSetupIur.Tr WRFD-020203 Inter RNC Soft Handover

ansCongTx
VS.SHO.FailRLSetupIur.No WRFD-020203 Inter RNC Soft Handover

deBReHost.Tx WRFD-040202 RNC Node Redundancy
1.5.1.6 Number of Radio Links to Be Deleted by DRNC on Iur Interface
Counters
67179096 VS.SHO.AttRLDelIur.Rx Number of Radio Link

Deletion Requests on Iur
Interface for DRNC
Description
This measurement item takes statistics of the number of radio links that the DRNC is requested
to delete on the Iur interface.
Measurement point
RADIO LINK DELETION REQUEST message from the SRNC, this item shall be measured
on each Iur interface.

BSC6900 UMTS
Figure 1-84 Radio Link deletion procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.SHO.AttRLDelIur.Rx WRFD-020203 Inter RNC Soft Handover
1.5.1.7 Number of Successful Radio Link Deletions by DRNC on Iur Interface
Counters
67179097 VS.SHO.SuccRLDelIur.Tx Number of Successful Radio

Link Deletions on Iur
Interface for DRNC

BSC6900 UMTS
Description
This measurement item takes statistics of the number of successful radio link deletions by a
DRNC on the Iur interface.
Measurement point
SRNC a RADIO LINK DELETION RESPONSE message, this item shall be measured on each
Iur interface.
Figure 1-85 RL deletion procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.SHO.SuccRLDelIur.Tx WRFD-020203 Inter RNC Soft Handover

BSC6900 UMTS
1.5.1.8 Number of Radio Link Addition Requests by DRNC on Iur Interface
Counters
67179098 VS.SHO.AttRLAddIur.Rx Number of Radio Link

Addition Requests on Iur
Interface for DRNC
Description
This measurement item takes statistics of the number of radio links that the DRNC is requested
to add on the Iur interface.
Measurement point
RADIO LINK ADDITION REQUEST message from the SRNC, this item shall be measured
Figure 1-86 Radio Link addition procedure (successful operation)
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.SHO.AttRLAddIur.Rx WRFD-020203 Inter RNC Soft Handover
1.5.1.9 Number of Successful Radio Link Additions on DRNC Iur Interface
Counters
67179099 VS.SHO.SuccRLAddIur.Tx Number of Successful Radio

Link Additions on Iur
Interface for DRNC
Description
This measurement item takes statistics of the number of successful radio link additions by a
DRNC on the Iur interface.
Measurement point
The measurement is triggered at point B, as shown in the figure, when the DRNC sends the
SRNC a RADIO LINK ADDITION RESPONSE message, this item shall be measured on each
Iur interface..

BSC6900 UMTS
Figure 1-87 Radio Link addition procedure (successful operation)
The measurement is triggered at point B, as shown in the figure. When the DRNC sends a RADIO
LINK ADDITION FAILURE message to the SRNC and the message indicates that there are
successfully added radio links, this item shall be measured on each Iur interface.
Figure 1-88 Radio Link addition procedure on the Iur interface (failed operation)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SHO.SuccRLAddIur.Tx WRFD-020203 Inter RNC Soft Handover
1.5.1.10 Number of Failed Radio Links Additions by DRNC on Iur Interface for
Different Causes
Counters
67179100 VS.SHO.FailRLAddIur.OM Number of Failed Radio Link

.Tx Additions on Iur Interface for
DRNC (OM Intervention)
67179101 VS.SHO.FailRLAddIur.HW Number of Failed Radio Link

.Tx Additions on Iur Interface for
DRNC (Device Fault)
67179102 VS.SHO.FailRLAddIur.Con Number of Failed Radio Link

g.Tx Additions on Iur Interface for
DRNC (Congestion)
67179103 VS.SHO.FailRLAddIur.Cfg Number of Failed Radio Link

UnsTx Additions on Iur Interface for
DRNC (Configuration
Unsupported)
67192581 VS.SHO.FailRLAddIur.Tra Number of Failed Radio Link

nsCong.Tx Additions on Iur Interface for
DRNC (Transport Resource
Unavailable)
73423642 VS.SHO.FailRLAddIur.Nod Number of Failed Radio Link

eBReHost.Tx Additions on Iur interface for
DRNC (NodeB Rehoming)

BSC6900 UMTS
Description
The measurement items provide the number of failed radio link additions by a DRNC on the Iur
interface according to different causes.
VS.SHO.FailRLAddIur.OM.Tx Number of failed radio link additions by

DRNC on Iur interface because of OM
intervention (cause value: OM Intervention)
VS.SHO.FailRLAddIur.HW.Tx Number of failed radio link additions by

DRNC on Iur interface because of hardware
failure (cause value: Hardware Failure)
VS.SHO.FailRLAddIur.Cong.Tx Number of failed radio link additions by

DRNC on Iur interface because of
insufficient RNC capability (cause value:
Cell not Available, UL Scrambling Code
Already in Use, DL Radio Resources not
Available, UL Radio Resources not
VS.SHO.FailRLAddIur.CfgUnsTx Number of failed radio link additions by

DRNC on Iur interface because of improper
configurations (cause value: Combining not
Supported, UL Spreading Factor not
Supported, DL Spreading Factor not
Supported, Requested Tx Diversity Mode not
supported, or CM not Supported)
VS.SHO.FailRLAddIur.TransCong.Tx Number of failed radio link additions by

DRNC on Iur interface because of
insufficient RNC transmission capability
(cause value: Transport Resource
Unavailable)
VS.SHO.FailRLAddIur.NodeBReHost.Tx Number of failed radio link additions caused

by NodeB Rehoming on Iur interface for
DRNC (cause value: NodeB Rehoming)
Measurement point
SRNC a RADIO LINK ADDITION FAILURE message with different failure causes, these
items shall be measured separately on each Iur interface.

BSC6900 UMTS
Figure 1-89 Radio Link addition procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
VS.SHO.FailRLAddIur.OM WRFD-020203 Inter RNC Soft Handover

.Tx
VS.SHO.FailRLAddIur.HW WRFD-020203 Inter RNC Soft Handover

.Tx
VS.SHO.FailRLAddIur.Con WRFD-020203 Inter RNC Soft Handover

g.Tx
VS.SHO.FailRLAddIur.Cfg WRFD-020203 Inter RNC Soft Handover

UnsTx
VS.SHO.FailRLAddIur.Tra WRFD-020203 Inter RNC Soft Handover

nsCong.Tx

BSC6900 UMTS
VS.SHO.FailRLAddIur.Nod WRFD-020203 Inter RNC Soft Handover

eBReHost.Tx WRFD-040202 RNC Node Redundancy
1.5.1.11 Number of Radio Links to Be Reconfigured by DRNC
Counters
67179105 VS.SHO.AttRLRecfgIur.Rx Number of Radio Link

Synchronous
Reconfiguration Requests on
Iur Interface for DRNC
Description
This measurement item takes statistics of the number of radio links that a DRNC is requested
to reconfigure on the Iur interface.
Measurement point
RADIO LINK RECONFIGURATION PREPARE message, this item shall be measured on each
Iur interface.
Figure 1-90 Radio Link synchronous reconfiguration preparation procedure (successful

operation)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SHO.AttRLRecfgIur.Rx WRFD-020203 Inter RNC Soft Handover
1.5.1.12 Number of Radio Links Successfully Reconfigured by DRNC on Iur

Interface
Counters
67179106 VS.SHO.SuccRLRecfgIur.T Number of Successful Radio

x Link Synchronous
Reconfigurations on Iur
Interface for DRNC
Description
This measurement item takes statistics of the number of successful radio link synchronous
reconfigurations by a DRNC on the Iur interface.
Measurement point
The measurement is triggered at point C, as shown in the figure. When the DRNC receives a
RADIO LINK RECONFIGURATION COMMIT message from the SRNC, this item shall be
measured on each Iur interface.

BSC6900 UMTS
Figure 1-91 Successful radio link synchronous reconfiguration procedure
Formula
None
Unit
None
Related Features
VS.SHO.SuccRLRecfgIur.T WRFD-020203 Inter RNC Soft Handover

x
1.5.1.13 Number of Failed Radio Link Synchronous Reconfigurations by DRNC on

Iur Interface for Different Causes

BSC6900 UMTS
Counters
67179107 VS.SHO.FailRLRecfgIur.O Number of Failed Radio Link

M.Tx Synchronous
Interface for DRNC (OM
Intervention)
67179109 VS.SHO.FailRLRecfgIur.C Number of Failed Radio Link

ongTx Synchronous
Interface for DRNC
(Congestion)
67179110 VS.SHO.FailRLRecfgIur.Cf Number of Failed Radio Link

gUTx Synchronous
Interface for DRNC
(Configuration
Unsupported)
67179108 VS.SHO.FailRLRecfgIur.H Number of Failed Radio Link

W.Tx Synchronous
Interface for DRNC (Device
Fault)
67192579 VS.SHO.FailRLRecfgIur.Tr Number of Failed Radio Link

ansCongRx Synchronous
Interface for DRNC
(Transport Resource
Unavailable)
Description
The measurement items provide the number of failed radio link synchronous reconfigurations
by a DRNC on the Iur interface according to different causes.
VS.SHO.FailRLRecfgIur.OM.Tx Number of failed radio link synchronous

reconfigurations by DRNC on Iur interface
because of OM intervention (cause value:
OM Intervention)

BSC6900 UMTS
VS.SHO.FailRLRecfgIur.CongTx Number of failed radio link synchronous

because of insufficient RNC capability (cause
value: Cell not Available, UL Scrambling
Code Already in Use, DL Radio Resources
not Available, UL Radio Resources not
VS.SHO.FailRLRecfgIur.CfgUTx Number of failed radio link synchronous

because of improper configurations (cause
value: UL SF not supported, DL SF not
supported, Downlink Shared Channel Type
not supported, Uplink Shared Channel Type
not supported, CM not supported, Number of
DL codes not supported, or Number of UL
codes not supported)
VS.SHO.FailRLRecfgIur.HW.Tx Number of failed radio link synchronous

because of hardware failure (cause value:
Hardware Failure)
VS.SHO.FailRLRecfgIur.TransCongRx Number of failed radio link synchronous

because of insufficient RNC transmission
capability (cause value: Transport Resource
Unavailable)
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.

BSC6900 UMTS
Figure 1-92 Synchronized RL reconfiguration procedure (failed operation)
Formula
None
Unit
None
Related Features
VS.SHO.FailRLRecfgIur.O WRFD-020203 Inter RNC Soft Handover

M.Tx
VS.SHO.FailRLRecfgIur.C WRFD-020203 Inter RNC Soft Handover

ongTx
VS.SHO.FailRLRecfgIur.Cf WRFD-020203 Inter RNC Soft Handover

gUTx
VS.SHO.FailRLRecfgIur.H WRFD-020203 Inter RNC Soft Handover

W.Tx
VS.SHO.FailRLRecfgIur.Tr WRFD-020203 Inter RNC Soft Handover

ansCongRx

BSC6900 UMTS
1.5.1.14 Number of Radio Links with Reconfiguration Canceled by the DRNC over
Iur
Counters
67179112 VS.SHO.CancelRLRecfgIur Number of Radio Link

.Rx Synchronous
Reconfiguration
Interface for DRNC
Description
This measurement item takes statistics of the number of radio links whose reconfiguration is
canceled by the SRNC over the Iur interface.
Measurement point
The measurement is triggered at point C as shown in the figure. When the DRNC receives a
RADIO LINK RECONFIGURATION CANCEL message from the SRNC, the DRNC measures
the item for each Iur interface.
Figure 1-93 Radio link reconfiguration cancellation procedure over Iur

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SHO.CancelRLRecfgIur WRFD-020203 Inter RNC Soft Handover

.Rx
1.5.1.15 Number of Radio Link Failures on Iur Interface
Counters
67179113 VS.SHO.RLFail.Tx Number of Radio Link

Failures on Iur Interface for
DRNC
Description
This measurement item takes statistics of the number of failed radio links of a DRNC on the Iur
interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC sends a RADIO
LINK FAILURE INDICATION message to the SRNC, this item shall be measured on each Iur
interface.

BSC6900 UMTS
Figure 1-94 RL failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
VS.SHO.RLFail.Tx WRFD-020203 Inter RNC Soft Handover
1.5.1.16 Number of Failed Radio Links on Iur Interface for Different Causes
Counters
67179114 VS.SHO.RLFail.OM.Tx Number of Radio Link

DRNC (OM Intervention)

BSC6900 UMTS
67179115 VS.SHO.RLFail.HW.Tx Number of Radio Link

DRNC (Device Fault)
67179116 VS.SHO.RLFail.SyncFail.T Number of Radio Link

x Failures on Iur Interface for
DRNC (Synchronization
Failure)
67179117 VS.SHO.RLFail.CfgUnsup. Number of Radio Link

Tx Failures on Iur Interface for
DRNC (Configuration
Unsupported)
67190048 VS.SHO.RLFail.Other.Tx Number of Radio Link

DRNC (Other Reasons)
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.
VS.SHO.RLFail.OM.Tx Number of failed radio links on Iur Interface

Because of OM Intervention (OM
Intervention)
VS.SHO.RLFail.HW.Tx Number of failed radio links on Iur Interface

Because of Hardware Failure (Hardware
Failure)
VS.SHO.RLFail.SyncFail.Tx Number of failed radio links on Iur Interface

Because of Synchronization Failure
(Synchronization Failure)
VS.SHO.RLFail.CfgUnsup.Tx Number of failed radio links on Iur Interface

Because of Improper Configurations (UL SF
not supported, DL SF not supported,
Downlink Shared Channel Type not
supported, Uplink Shared Channel Type not
supported, CM not supported, Number of DL
codes not supported, Number of UL codes not
supported)

BSC6900 UMTS
VS.SHO.RLFail.Other.Tx Number of failed radio links on Iur Interface

Because of Other Cause (cause other than
OM Intervention, Hardware Failure,
Synchronization Failure, and Improper
Configurations)
Measurement point
The measurement is triggered at point A as shown in the figure. When the DRNC sends the
SRNC a RADIO LINK FAILURE INDICATION message with different failure causes as shown
below, these items shall be measured separately on each Iur interface.
Figure 1-95 Radio Link failure procedure on the Iur interface
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.SHO.RLFail.OM.Tx WRFD-020203 Inter RNC Soft Handover
VS.SHO.RLFail.HW.Tx WRFD-020203 Inter RNC Soft Handover
VS.SHO.RLFail.SyncFail.T WRFD-020203 Inter RNC Soft Handover

x
VS.SHO.RLFail.CfgUnsup. WRFD-020203 Inter RNC Soft Handover

Tx
VS.SHO.RLFail.Other.Tx WRFD-020203 Inter RNC Soft Handover
1.5.1.17 Number of RADIO LINK RESTORE INDICATION Messages sent by

DRNC on Iur Interface
Counters
67179118 VS.SHO.RLRestore.Tx Number of Radio Link

Restorations on Iur Interface
for DRNC
Description
These measurement items take statistics of the number of RADIO LINK RESTORE
INDICATION messages sent by a DRNC on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC sends the
SRNC a RADIO LINK RESTORE INDICATION message, this item shall be measured on each
Iur interface.

BSC6900 UMTS
Figure 1-96 Radio Link restoration procedure
Formula
None
Unit
None
Related Features
VS.SHO.RLRestore.Tx WRFD-020203 Inter RNC Soft Handover
1.5.1.18 Number of COMMON TRANSPORT CHANNEL RESOURCES REQUEST

Messages Received by DRNC on Iur Interface

BSC6900 UMTS
Counters
67179119 VS.IUR.AttComTraCh- Number of Common

ResDRNC Transport Channel Resource
Requests on Iur Interface for
DRNC
Description
These measurement items take statistics of the number of COMMON TRANSPORT
CHANNEL RESOURCES REQUEST messages received by a DRNC on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC receives from
the SRNC a COMMON TRANSPORT CHANNEL RESOURCES REQUEST message on the
Iur interface, this item shall be measured on each Iur interface.
Figure 1-97 Common transport channel resources initialization procedure on the Iur interface
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IUR.AttComTraCh- WRFD-010802 Inter RNC Cell Update

ResDRNC
1.5.1.19 Number of COMMON TRANSPORT CHANNEL RESOURCES

RESPONSE Messages Sent by DRNC on Iur Interface
Counters
67179120 VS.IUR.SuccComTraCh- Number of Common

ResDRNC Transport Channel Resource
Responses on Iur Interface
for DRNC
Description
CHANNEL RESOURCES RESPONSE messages sent from DRNC to SRNC on the Iur
interface.
Measurement point
SRNC a COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message on the Iur
interface, this item shall be measured on each Iur interface.

BSC6900 UMTS
Figure 1-98 Common transport channel resources initialization procedure on the Iur interface
Formula
None
Unit
None
Related Features
VS.IUR.SuccComTraCh- WRFD-010802 Inter RNC Cell Update

ResDRNC
1.5.1.20 Number of COMMON TRANSPORT CHANNEL RESOURCES FAILURE

Messages sent by DRNC on the Iur Interface due to Transport Resource
Unavailable

BSC6900 UMTS
Counters
67179121 VS.IUR.FailCTCRDRNC.N Number of Common

otSupp Transport Channel Resource
Failures Due to Transport
Resource Unavailable on Iur
Interface for DRNC
Description
CHANNEL RESOURCES FAILURE messages that the DRNC sends to the SRNC with the
cause of "Common Transport Channel Type Not Supported" on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC sends the
SRNC a COMMON TRANSPORT CHANNEL RESOURCES FAILURE message with the
cause of "Common Transport Channel Type Not Supported" on the Iur interface, this item shall
be measured on each Iur interface.
Figure 1-99 Common transport channel resources failure procedure on the Iur interface
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IUR.FailCTCRDRNC.N WRFD-010802 Inter RNC Cell Update

otSupp
1.5.1.21 Number of COMMON TRANSPORT CHANNEL RESOURCES RELEASE

REQUEST Messages Received by DRNC on Iur Interface
Counters
67179122 VS.IUR.AttRelCoTr- Number of Common

ChResDRNC Transport Channel Resource
Release Requests on Iur
Interface for DRNC
Description
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.

BSC6900 UMTS
Figure 1-100 Common transport channel resources release procedure on the Iur interface
Formula
None
Unit
None
Related Features
VS.IUR.AttRelCoTr- WRFD-010802 Inter RNC Cell Update

ChResDRNC
1.5.2 Reserved counter for Iur interface(RESERVE.IUR)
Overview
Reserved counter for Iur interface.

BSC6900 UMTS
Counters
Description
73423446 VS.Reserve.Counte Reserved counter 1 V900R013

r1.Iur for Iur interface









None
1.5.2.1 Reserved counters for Iur interface
Counters
73423446 VS.Reserve.Counter1.Iur Reserved counter 1 for Iur

interface

interface

BSC6900 UMTS

interface

interface

interface

interface

interface

interface

interface

interface
Description
Reserved counters for Iur interface.
Measurement point
Reserved counters for Iur interface.
Formula
None
Unit
None
Related Features
None

BSC6900 UMTS
1.5.3 Measurement Related to SCCP for Iur Interface

(SIG.SCCP.IUR)
Overview
Measurement related to SCCP for Iur interface provides the counters related to the numbers of
the local-RNC-initiated SCCP connection requests, local-RNC-initiated successful SCCP
connection requests, peer-RNC-initiated SCCP connection requests, and peer-RNC-initiated
successful SCCP connection requests.
Counters
Description
67195053 VS.IUR.SCCP.Tx. Number of SCCP Earlier than

Con.Req Connection Requests V900R011
Sent to Other RNC
Through the Iur
Interface
67195054 VS.IUR.SCCP.Tx. Number of Earlier than

Con.Succ Successful SCCP V900R011
Connection Requests
Sent to Other RNC
Through the Iur
Interface
67195055 VS.IUR.SCCP.Rx. Number of SCCP Earlier than

Con.Req Connection Requests V900R011
from Other RNC
Through the Iur
Interface
67195056 VS.IUR.SCCP.Rx. Number of Earlier than

Con.Succ Successful SCCP V900R011
Connection Requests
from Other RNC
Through the Iur
Interface
None
1.5.3.1 Number of SCCP Connection Requests Sent by the Local RNC to the Peer
RNC Through the Iur Interface

BSC6900 UMTS
Counters
67195053 VS.IUR.SCCP.Tx.Con.Req Number of SCCP

Other RNC Through the Iur
Interface
Description
This counter provides the number of SCCP connection requests sent by the local RNC to the
peer RNC.
Measurement point
The measurement is triggered at point A, as shown in the figure. In the measurement period, the
counter is incremented by one when the local RNC RNSAP sends a SCCP CR message to the
peer RNC.
Figure 1-101 SCCP connection requests sent by the local RNC to the peer RNC
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IUR.SCCP.Tx.Con.Req WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.5.3.2 Number of Successful SCCP Connection Requests Sent by the Local RNC
to the Peer RNC Through the Iur Interface
Counters
67195054 VS.IUR.SCCP.Tx.Con.Succ Number of Successful SCCP

Interface
Description
This counter provides the successful number of SCCP connection requests sent by the local RNC
to the peer RNC.
Measurement point
The measurement is triggered at point B, as shown in the figure. This counter is incremented by
one when the local RNC RNSAP receives a Connection Confirm (CC) message from the peer
RNC after sending a Connection Request (CR) message to the peer RNC.

BSC6900 UMTS
Figure 1-102 Successful SCCP connection requests sent by the local RNC to the peer RNC
Formula
None
Unit
None
Related Features
VS.IUR.SCCP.Tx.Con.Succ WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.5.3.3 Number of SCCP Connection Requests Received by the Local RNC from the
Peer RNC Through the Iur Interface

BSC6900 UMTS
Counters
67195055 VS.IUR.SCCP.Rx.Con.Req Number of SCCP

Interface
Description
This counter provides the number of SCCP connection requests received by the local RNC from
the peer RNC.
Measurement point
The measurement is triggered at point A, as shown in the figure. In the measurement period, the
counter is incremented by one when the local RNC RNSAP receives a SCCP CR message from
the peer RNC.
Figure 1-103 SCCP connection requests received by the local RNC from the peer RNC
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IUR.SCCP.Rx.Con.Req WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.5.3.4 Number of Successful SCCP Connection Requests Received by the Local

RNC from the Peer RNC Through the Iur Interface
Counters
67195056 VS.IUR.SCCP.Rx.Con.Succ Number of Successful SCCP

Interface
Description
This counter provides the number of successful SCCP connection requests received by the local
RNC from the peer RNC.
Measurement point
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.

BSC6900 UMTS
Figure 1-104 Successful SCCP connection requests received by the local RNC from the peer
RNC
Formula
None
Unit
None
Related Features
VS.IUR.SCCP.Rx.Con.Succ WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.5.4 Measurement related to SRNC in Iur interface(SRNC.IUR)
Overview
The SRNC Iur Interface Measurement involves measurements of DCH procedures, common
transport channel procedures, and cross-Iur RAB and RRC connection release procedures. The

BSC6900 UMTS
DCH procedures include: Radio link (RL) setup procedures, RL addition procedures, RL
deletion procedures, Synchronized RL reconfiguration procedures, RL failure procedures, RL
restoration procedures; Common transport channel procedures include common transport
channel setup procedures and common transport channel release procedures.
Counters
Description
67179025 VS.SHO.AttRLSet Number of Radio Earlier than

upIur.Tx Link Setup Requests V900R011
on Iur Interface from
SRNC
67179026 VS.SHO.SuccRLSe Number of Radio Earlier than

tupIur.Rx Links Successfully V900R011
Set Up on the Iur
Interface for SRNC
67179028 VS.SHO.FailRLSet Number of Radio Earlier than

upIur.HW.Rx Link Setup Failures V900R011
SRNC (Device
Fault)

upIur.Cong.Rx Link Setup Failures V900R011
SRNC (Congestion)

upIur.CfgUnsupp. Link Setup Failures V900R011
Rx on Iur Interface for
SRNC
(Configuration
Unsupported)

upIur.TransCong. Link Setup Failures V900R011
Rx on Iur Interface for
SRNC (Transport
Resource
Unavailable)
67192578 VS.SHO.FailRLAd Number of Radio Earlier than

dIur.TransCong.R Link Addition V900R011
x Failures on Iur
Interface for SRNC
(Transport Resource
Unavailable)

BSC6900 UMTS

Description
67179032 VS.SHO.AttRLDel Number of Radio V900R012

Iur.Tx Links Deleted on Iur
Interface for SRNC
67179033 VS.SHO.SuccRLD Number of V900R012

elIur.Rx Successful deleted
Radio Links on Iur
Interface for SRNC
67179035 VS.SHO.AttRLAd Number of Radio Earlier than

dIur.Tx Link Addition V900R011
Requests on Iur
Interface from SRNC
67179036 VS.SHO.SuccRLA Number of Earlier than

ddIur.Rx Successful Radio V900R011
Link Additions on
Iur Interface for
SRNC

dIur.HW.Rx Radio Link V900R011
Additions on Iur
Interface for SRNC
(Device Fault)

dIur.Cong.Rx Radio Link V900R011
Additions on Iur
Interface for SRNC
(Congestion)

dIur.CfgUnsupp.R Radio Link V900R011
x Additions on Iur
Interface for SRNC
(Configuration
Unsupported)
67179042 VS.SHO.AttRLRec Number of Radio Earlier than

fgIur.Tx Link V900R011
Reconfiguration
Requests on Iur
Interface from SRNC

BSC6900 UMTS

Description
67179043 VS.SHO.SuccRLR Number of Earlier than

ecfgIur.Rx Successful Radio V900R011
Link
Reconfigurations on
Iur Interface for
SRNC

cfgIur.HW.Rx Radio Link V900R011
Synchronous
Reconfigurations on
Iur Interface for
SRNC (Device
Fault)

cfgIur.Cong.Rx Radio Link V900R011
Synchronous
Reconfigurations on
Iur Interface for
SRNC (Congestion)

cfgIur.CfgUnsupp. Radio Link V900R011
Rx Synchronous
Reconfigurations on
Iur Interface for
SRNC
(Configuration
Unsupported)

cfgIur.NoReply Radio Link V900R011
Synchronous
Reconfigurations on
Iur Interface for
SRNC (No
Response)
67179051 VS.SHO.RLFailIn Number of Radio Earlier than

dIur.Rx Link Failures on Iur V900R011
Interface for SRNC
67179053 VS.SHO.RLFailIur Number of Radio Earlier than

.HW.Rx Link Failures on Iur V900R011
Interface for SRNC
(Device Fault)

BSC6900 UMTS

Description

.SyncFail.Rx Link Failures on Iur V900R011
Interface for SRNC
(Synchronization
Failure)

.CfgUnsup.Rx Link Failures on Iur V900R011
Interface for SRNC
(Configuration
Unsupported)
67179056 VS.SHO.RLRestor Number of Radio Earlier than

eIur.Rx Link Restorations on V900R011
Iur Interface for
SRNC
67179061 VS.SHO.Att.Iur Number of Soft Earlier than

Handovers Initiated V900R011
by SRNC on Iur
Interface
67179062 VS.SHO.Succ.Iur Number of Earlier than

Successful Soft V900R011
Handovers Initiated
by SRNC on Iur
Interface
67179057 VS.AttCommTrCh Number of Common Earlier than

ResIur.Tx Transport Channel V900R011
Resource Requests
Sent by SRNC on Iur
Interface
67179058 VS.SuccCommTrC Number of Common Earlier than

hResIur.Rx Transport Channel V900R011
Resource Responses
Received by SRNC
on Iur Interface
67179059 VS.FailCommTrC Number of Common Earlier than

hResIur.NotSupp. Transport Channel V900R011
Rx Resource Failures
Due to Transport
Resource
Unavailable on Iur
Interface for SRNC

BSC6900 UMTS

Description
67179060 VS.AttRelCommTr Number of Common Earlier than

ChResIur.Tx Transport Channel V900R011
Resource Release
Requests on Iur
Interface from SRNC
67191845 VS.RAB.NormRel. Number of CS Earlier than

CS64.Iur Conversational V900R011
RABs Normally
Released on the
SRNC Iur Interface
for SRNC
(Conversational with
DL Max Bit Rate as
64kbit/s)
67191850 VS.RAB.NormRel. Number of PS RABs Earlier than

PS.CCH.Iur Normally Released V900R011
SRNC (CCH User
Only)

AMR.Iur Released AMR V900R011
RABs on Iur
Interface for SRNC
(not including WB-
AMR)

el.AMR.Iur Abnormally V900R011
Released AMR
RABs on Iur
Interface for SRNC
(not including WB-
AMR)
67191860 VS.RAB.AbnormR Number of CS Earlier than

el.CS64.Iur Conversational V900R011
RABs Abnormally
Released on the
SRNC Iur Interface
for SRNC
(Conversational with
DL Max Bitrate as
64kbit/s)

BSC6900 UMTS

Description
67191865 VS.RAB.AbnormR Number of PS RABs Earlier than

el.PS.CCH.Iur Abnormally V900R011
Released on Iur
Interface for SRNC
(CCH User Only)

CS.Str.Iur Streaming RABs V900R011
Normally Released
SRNC
67194988 VS.RAB.NormRel. Number of RABs Earlier than

PS.Conv.Iur Normally Released V900R011
for PS
Conversational
Services on Iur
Interface for SRNC

PS.Str.Iur Normally Released V900R011
for PS Streaming
Services on Iur
Interface for SRNC

HSDPA.Iur Released HSDSCH- V900R011
Carried RABs on Iur
Interface for SRNC
67194991 VS.RAB.NormRel. Number of EDCH- Earlier than

HSUPA.Iur Carried RABs V900R011
Normally Released
SRNC

el.CS.Str.Iur Streaming RABs V900R011
Abnormally
Released on Iur
Interface for SRNC
67194998 VS.RAB.AbnormR Number of RABs Earlier than

el.PS.Conv.Iur Abnormally V900R011
Released for PS
Conversational
Services on Iur
Interface for SRNC

BSC6900 UMTS

Description

el.PS.Str.Iur Abnormally V900R011
Released for PS
Streaming Services
SRNC

el.HSDPA.Iur HSDSCH-Carried V900R011
RABs Abnormally
Released on Iur
Interface for SRNC
67195001 VS.RAB.AbnormR Number of EDCH- Earlier than

el.HSUPA.Iur Carried RABs V900R011
Abnormally
Released on Iur
Interface for SRNC
67179050 VS.SHO.CancelRL Number of Radio Earlier than

RecfgIur.Tx Link Synchronous V900R011
Reconfiguration
Interface for SRNC
67196206 VS.RAB.NormRel. Number of HSPA- Earlier than

CS.HSPA.Conv.Iur Carried CS V900R011
Conversational
RABs Normally
Released on Iur
Interface for SRNC
67196207 VS.RAB.AbnormR Number of HSPA- Earlier than

el.CS.HSPA.Conv.I Carried CS V900R011
ur Conversational
RABs Abnormally
Released on Iur
Interface for SRNC
73403815 VS.RAB.AbnormR Number of CS V900R012

el.AMRWB.Iur AMRWB RABs
Abnormally
Released on the
SRNC Iur Interface
for SRNC

BSC6900 UMTS

Description
73403816 VS.RAB.NormRel. Number of CS V900R012

AMRWB.Iur AMRWB RABs
Normally Released
on the SRNC Iur
Interface for SRNC
73393847 VS.RAB.NormRel. Number of PS BE V900R012

PS.BE.Iur RABs Normally
Released on Iur
Interface for SRNC
73393848 VS.RAB.AbnormR Number of PS BE V900R012

el.PS.BE.Iur RABs Abnormally
Released on Iur
Interface for SRNC
73421884 VS.RAB.NormRel. Number of Normally V900R012

PS.PCH.Iur Released PS RABs
that Are in
CELL_PCH or
URA_PCH State on
Iur Interface for
SRNC
73421885 VS.RAB.AbnormR Number of V900R012

el.PS.PCH.Iur Abnormally
Released PS RABs
that Are in
CELL_PCH or
URA_PCH State on
Iur Interface for
SRNC
73423384 VS.RRC.AttConnR Number of RRC V900R013

elCCCH.DSCR.Iur Connection Releases
(CCCH) Sent by the
SRNC over the Iur
Interface due to
DSCR

elDCCH.DSCR.Iur Connection Releases
(DCCH) Sent by the
SRNC over the Iur
Interface due to
DSCR

BSC6900 UMTS

Description
73423639 VS.SHO.FailRLSet Number of Radio V900R014

upIur.NodeBReHo Link Setup Failures
st.Rx on Iur interface for
SRNC (NodeB
Rehoming)
73423640 VS.SHO.FailRLAd Number of Failed V900R014

dIur.NodeBReHost Radio Link
.Rx Additions on Iur
interface for SRNC
(NodeB Rehoming)
Counter Sub Counter
VS.SHO.FailRLSetupIur.Cong.Rx VS.SHO.FailRLSetupIur.TransCong.Rx
VS.SHO.FailRLAddIur.Cong.Rx VS.SHO.FailRLAddIur.TransCong.Rx
VS.SHO.RLFailIndIur.Rx VS.SHO.RLFailIur.HW.Rx
VS.SHO.RLFailIur.SyncFail.Rx
VS.SHO.RLFailIur.CfgUnsup.Rx
VS.RAB.NormRel.PS.CCH.Iur VS.RAB.NormRel.PS.PCH.Iur
VS.RAB.AbnormRel.PS.CCH.Iur VS.RAB.AbnormRel.PS.PCH.Iur
1.5.4.1 Number of Radio Links Requested to Establish by SRNC on Iur Interface
Counters
67179025 VS.SHO.AttRLSetupIur.Tx Number of Radio Link Setup

Requests on Iur Interface
from SRNC
Description
This measurement item takes statistics of the number of radio links that the SRNC requests to
establish on the Iur interface.

BSC6900 UMTS
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.
Formula
None
Unit
None
Related Features
VS.SHO.AttRLSetupIur.Tx WRFD-020203 Inter RNC Soft Handover
1.5.4.2 Number of Radio Links Successfully Established by SRNC on Iur Interface

BSC6900 UMTS
Counters
67179026 VS.SHO.SuccRLSetupIur.R Number of Radio Links

x Successfully Set Up on the
Iur Interface for SRNC
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.
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.

BSC6900 UMTS
Figure 1-107 Radio Link setup failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
VS.SHO.SuccRLSetupIur.R WRFD-020203 Inter RNC Soft Handover

x
1.5.4.3 Number of Failed Radio Link Establishments by SRNC on Iur Interface for
Different Causes

BSC6900 UMTS
Counters
67179028 VS.SHO.FailRLSetupIur.H Number of Radio Link Setup

W.Rx Failures on Iur Interface for
SRNC (Device Fault)
67179029 VS.SHO.FailRLSetupIur.Co Number of Radio Link Setup

ng.Rx Failures on Iur Interface for
SRNC (Congestion)
67179030 VS.SHO.FailRLSetupIur.Cf Number of Radio Link Setup

gUnsupp.Rx Failures on Iur Interface for
SRNC (Configuration
Unsupported)
67192577 VS.SHO.FailRLSetupIur.Tr Number of Radio Link Setup

ansCong.Rx Failures on Iur Interface for
SRNC (Transport Resource
Unavailable)
73423639 VS.SHO.FailRLSetupIur.No Number of Radio Link Setup

deBReHost.Rx Failures on Iur interface for
SRNC (NodeB Rehoming)
Description
The measurement items provide the number of failed radio link establishments by the SRNC on
the Iur interface for different causes.
VS.SHO.FailRLSetupIur.HW.Rx Number of failed radio link establishments

caused by Hardware Failure on Iur interface
for SRNC (cause value: Hardware Failure)
VS.SHO.FailRLSetupIur.Cong.Rx Number of failed radio link establishments

caused by Unavailable RNC Resources on Iur
interface for SRNC (cause value: Cell not
Available, UL Scrambling Code Already in
Use, DL Radio Resources not Available, UL
Radio Resources not Available, Combining
Resources not Available, Measurement
Temporarily not Available, Cell Reserved for
Operator Use, Control Processing Overload,
Not enough User Plane Processing Resources
or Transport Resource Unavailable)

BSC6900 UMTS
VS.SHO.FailRLSetupIur.CfgUnsupp.Rx Number of failed radio link establishments

caused by Improper Configurations on Iur
interface for SRNC (cause value: Combining
not Supported, UL Spreading Factor not
VS.SHO.FailRLSetupIur.TransCong.Rx Number of failed radio link establishments

caused by Transport Resource Unavailable
on Iur interface for SRNC (cause value:
Transport Resource Unavailable)
VS.SHO.FailRLSetupIur.NodeBReHost.Rx Number of failed radio link establishments

caused by NodeB Rehoming on Iur interface
for SRNC (cause value: NodeB Rehoming)
Measurement point
RADIO LINK SETUP FAILURE message from the DRNC, the SRNC measures the item
according to different failure causes on each Iur interface.
Figure 1-108 Radio Link setup failure procedure on the Iur interface

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SHO.FailRLSetupIur.H WRFD-020203 Inter RNC Soft Handover

W.Rx
VS.SHO.FailRLSetupIur.Co WRFD-020203 Inter RNC Soft Handover

ng.Rx
VS.SHO.FailRLSetupIur.Cf WRFD-020203 Inter RNC Soft Handover

gUnsupp.Rx
VS.SHO.FailRLSetupIur.Tr WRFD-020203 Inter RNC Soft Handover

ansCong.Rx
VS.SHO.FailRLSetupIur.No WRFD-020203 Inter RNC Soft Handover

deBReHost.Rx WRFD-040202 RNC Node Redundancy
1.5.4.4 Number of Radio Links Deleted on Iur Interface for SRNC
Counters
67179032 VS.SHO.AttRLDelIur.Tx Number of Radio Links

Deleted on Iur Interface for
SRNC
Description
This measurement item provides the number of radio links deleted on the Iur interface for SRNC.
Measurement point
LINK DELETION REQUEST message to the DRNC, the SRNC measures this item on each
Iur interface.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SHO.AttRLDelIur.Tx WRFD-020203 Inter RNC Soft Handover
1.5.4.5 Number of Successful deleted Radio Links on Iur Interface for SRNC
Counters
67179033 VS.SHO.SuccRLDelIur.Rx Number of Successful

deleted Radio Links on Iur
Interface for SRNC

BSC6900 UMTS
Description
This measurement item provides the number of successful deleted radio links on the Iur interface
for SRNC.
Measurement point
RADIO LINK DELETION RESPONSE message from the DRNC, the SRNC measures this
item on each Iur interface.
Formula
None
Unit
None
Related Features
VS.SHO.SuccRLDelIur.Rx WRFD-020203 Inter RNC Soft Handover

BSC6900 UMTS
1.5.4.6 Number of Radio Links Requested to Add by SRNC on Iur Interface
Counters
67179035 VS.SHO.AttRLAddIur.Tx Number of Radio Link

Addition Requests on Iur
Interface from SRNC
Description
add on the Iur interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the SRNC sends the
DRNC a RADIO LINK ADDITION REQUEST message, the SRNC measures this item on each
Iur interface.
Figure 1-111 Radio Link addition procedure on the Iur interface (successful operation)
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.SHO.AttRLAddIur.Tx WRFD-020203 Inter RNC Soft Handover
1.5.4.7 Number of Radio Links Successfully Added by SRNC on Iur Interface
Counters
67179036 VS.SHO.SuccRLAddIur.Rx Number of Successful Radio

Link Additions on Iur
Interface for SRNC
Description
This measurement item takes statistics of the number of radio links successfully added by the
SRNC on the Iur interface.
Measurement point
RADIO LINK ADDITION RESPONSE message from the DRNC, the SRNC measures the item

BSC6900 UMTS
Figure 1-112 Radio Link addition procedure on the Iur interface (successful operation)
RADIO LINK ADDITION FAILURE message from the DRNC and if there are successfully
added radio links, the SRNC measures this item on each Iur interface.
Figure 1-113 Radio Link addition procedure (failed operation)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SHO.SuccRLAddIur.Rx WRFD-020203 Inter RNC Soft Handover
1.5.4.8 Number of Failed Radio Link Additions for Different Causes on Iur
Interface for SRNC
Counters
67179038 VS.SHO.FailRLAddIur.HW Number of Failed Radio Link

.Rx Additions on Iur Interface for
SRNC (Device Fault)
67192578 VS.SHO.FailRLAddIur.Tra Number of Radio Link

nsCong.Rx Addition Failures on Iur
Interface for SRNC
(Transport Resource
Unavailable)
67179039 VS.SHO.FailRLAddIur.Con Number of Failed Radio Link

g.Rx Additions on Iur Interface for
SRNC (Congestion)
67179040 VS.SHO.FailRLAddIur.Cfg Number of Failed Radio Link

Unsupp.Rx Additions on Iur Interface for
SRNC (Configuration
Unsupported)
73423640 VS.SHO.FailRLAddIur.Nod Number of Failed Radio Link

eBReHost.Rx Additions on Iur interface for
SRNC (NodeB Rehoming)
Description
The measurement items provide the number of failed radio link additions for different causes
on the Iur interface for SRNC.

BSC6900 UMTS
VS.SHO.FailRLAddIur.HW.Rx Number of failed radio link additions caused

by hardware failure on Iur interface for SRNC
(cause value: Hardware Failure)
VS.SHO.FailRLAddIur.TransCong.Rx Number of failed radio link additions caused

by insufficient RNC transmission capability
on Iur interface for SRNC (cause value:
Transport Resource Unavailable)
VS.SHO.FailRLAddIur.Cong.Rx Number of failed radio link additions caused

by insufficient RNC capability on Iur
Operator Use, Control Processing Overload,
Not enough User Plane Processing Resources
or Transport Resource Unavailable)
VS.SHO.FailRLAddIur.CfgUnsupp.Rx Number of failed radio link additions caused

by improper configurations on Iur interface
for SRNC (cause value: Combining not
Supported, UL Spreading Factor not
VS.SHO.FailRLAddIur.NodeBReHost.Rx Number of failed radio link additions caused

by NodeB Rehoming on Iur interface for
SRNC (cause value: NodeB Rehoming)
Measurement point
RADIO LINK ADDITION FAILURE message from the DRNC, the SRNC measures the item

BSC6900 UMTS
Figure 1-114 Radio Link addition procedure (failed operation)
Formula
None
Unit
None
Related Features
VS.SHO.FailRLAddIur.HW WRFD-020203 Inter RNC Soft Handover

.Rx
VS.SHO.FailRLAddIur.Tra WRFD-020203 Inter RNC Soft Handover

nsCong.Rx
VS.SHO.FailRLAddIur.Con WRFD-020203 Inter RNC Soft Handover

g.Rx
VS.SHO.FailRLAddIur.Cfg WRFD-020203 Inter RNC Soft Handover

Unsupp.Rx
VS.SHO.FailRLAddIur.Nod WRFD-040202 RNC Node Redundancy

eBReHost.Rx WRFD-020203 Inter RNC Soft Handover

BSC6900 UMTS
1.5.4.9 Number of Radio Links Requested to Reconfigure by SRNC on Iur Interface
Counters
67179042 VS.SHO.AttRLRecfgIur.Tx Number of Radio Link

Reconfiguration Requests on
Iur Interface from SRNC
Description
reconfigure on the Iur interface.
Measurement point
LINK RECONFIGURATION PREPARE message to the DRNC, the SRNC measures this item
Figure 1-115 Synchronized radio link reconfiguration procedure on the Iur interface
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.SHO.AttRLRecfgIur.Tx WRFD-020203 Inter RNC Soft Handover
1.5.4.10 Number of Radio Links Successfully Reconfigured by SRNC on Iur

Interface
Counters
67179043 VS.SHO.SuccRLRecfgIur.R Number of Successful Radio

x Link Reconfigurations on Iur
Interface for SRNC
Description
This measurement item takes statistics of the number of radio links successfully reconfigured
by the SRNC.
Measurement point
The measurement is triggered at point C, as shown in the figure. When the SRNC sends a RADIO
LINK RECONFIGURATION COMMIT message to the DRNC, if there is an indication of
successfully reconfigured radio links in the message, the SRNC measures this item on each Iur
interface.

BSC6900 UMTS
Figure 1-116 Synchronized radio link reconfiguration commit procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.SHO.SuccRLRecfgIur.R WRFD-020203 Inter RNC Soft Handover

x
1.5.4.11 Number of Radio Links Unsuccessfully Reconfigured by SRNC on Iur


BSC6900 UMTS
Counters
67179045 VS.SHO.FailRLRecfgIur.H Number of Failed Radio Link

W.Rx Synchronous
Interface for SRNC (Device
Fault)
67179046 VS.SHO.FailRLRecfgIur.C Number of Failed Radio Link

ong.Rx Synchronous
Interface for SRNC
(Congestion)
67179047 VS.SHO.FailRLRecfgIur.Cf Number of Failed Radio Link

gUnsupp.Rx Synchronous
Interface for SRNC
(Configuration
Unsupported)
Description
The measurement items provide the number of radio links unsuccessfully reconfigured by the
SRNC on the Iur interface for different causes.
VS.SHO.FailRLRecfgIur.HW.Rx Number of failed radio link reconfigurations

by hardware failure on Iur interface for SRNC
(cause value: Hardware Failure)
VS.SHO.FailRLRecfgIur.Cong.Rx Number of failed radio link reconfigurations

caused by hardware failure on Iur interface
for SRNC (cause value: Cell not Available,
UL Scrambling Code Already in Use, DL
Radio Resources not Available, UL Radio
Resources not Available, Combining
Operator Use, Transport Resource
Unavailable, Control Processing Overload, or
Not enough User Plane Processing
Resources)

BSC6900 UMTS
VS.SHO.FailRLRecfgIur.CfgUnsupp.Rx Number of failed radio link reconfigurations

caused by insufficient RNC capability on Iur
Operator Use, Transport Resource
Unavailable, Control Processing Overload, or
Not enough User Plane Processing
Resources)
Measurement point
RADIO LINK RECONFIGURATION FAILURE message from the DRNC, the SRNC
measures the item according to different failure causes on each Iur interface.
Figure 1-117 Synchronized radio link reconfiguration procedure on the Iur interface (failed
operation)
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.SHO.FailRLRecfgIur.H WRFD-020203 Inter RNC Soft Handover

W.Rx
VS.SHO.FailRLRecfgIur.C WRFD-020203 Inter RNC Soft Handover

ong.Rx
VS.SHO.FailRLRecfgIur.Cf WRFD-020203 Inter RNC Soft Handover

gUnsupp.Rx
1.5.4.12 Number of Radio Links Unsuccessfully Reconfigured by SRNC on Iur

Interface for No Response
Counters
67179048 VS.SHO.FailRLRecfgIur.N Number of Failed Radio Link

oReply Synchronous
Interface for SRNC (No
Response)
Description
This measurement item provides the number of radio links unsuccessfully reconfigured by the
SRNC on the Iur interface due to no response.
Measurement point
The measurement is triggered at point A as shown in the figure. When the SRNC sends a RADIO
LINK RECONFIGURATION PREPARE message to the DRNC, the SRNC starts the timer to
wait for the response message from the DRNC. If the SRNC does not receive a response message
until the timer expires, it triggers the the measurement of this item on each Iur interface.

BSC6900 UMTS
Figure 1-118 Radio Link synchronous reconfiguration preparation procedure (failed operation)
(no reply)
Formula
None
Unit
None
Related Features
VS.SHO.FailRLRecfgIur.N WRFD-020203 Inter RNC Soft Handover

oReply
1.5.4.13 Number of Failed Radio Links of SRNC on Iur Interface

BSC6900 UMTS
Counters
67179051 VS.SHO.RLFailIndIur.Rx Number of Radio Link

SRNC
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

BSC6900 UMTS
Related Features
VS.SHO.RLFailIndIur.Rx WRFD-020203 Inter RNC Soft Handover
1.5.4.14 Number of Failed Radio Links of SRNC on Iur Interface for Different
Causes
Counters
67179053 VS.SHO.RLFailIur.HW.Rx Number of Radio Link

SRNC (Device Fault)
67179054 VS.SHO.RLFailIur.SyncFai Number of Radio Link

l.Rx Failures on Iur Interface for
SRNC (Synchronization
Failure)
67179055 VS.SHO.RLFailIur.CfgUns Number of Radio Link

up.Rx Failures on Iur Interface for
SRNC (Configuration
Unsupported)
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.
VS.SHO.RLFailIur.HW.Rx Number of failed radio links of SRNC on Iur

interface because of hardware failure (cause
value: Hardware Failure)
VS.SHO.RLFailIur.SyncFail.Rx Number of failed radio links of SRNC on Iur

interface because of synchronization failure
(cause value: Synchronization Failure)

BSC6900 UMTS
VS.SHO.RLFailIur.CfgUnsup.Rx Number of failed radio links of SRNC on Iur

interface because of improper configurations
(cause value: UL SF not supported, DL SF not
not supported, CM not supported, Number of
DL codes not supported, or Number of UL
codes not supported)
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
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.SHO.RLFailIur.HW.Rx WRFD-020203 Inter RNC Soft Handover
VS.SHO.RLFailIur.SyncFai WRFD-020203 Inter RNC Soft Handover

l.Rx
VS.SHO.RLFailIur.CfgUns WRFD-020203 Inter RNC Soft Handover

up.Rx
1.5.4.15 Number of Radio Links Restored by SRNC on Iur Interface
Counters
67179056 VS.SHO.RLRestoreIur.Rx Number of Radio Link

Restorations on Iur Interface
for SRNC
Description
This measurement item takes statistics of the number of radio links restored by the SRNC on
the Iur interface.
Measurement point
RADIO LINK RESTORE INDICATION message from the DRNC, the SRNC measures this
item on each Iur interface.

BSC6900 UMTS
Figure 1-121 Radio Link restoration procedure
Formula
None
Unit
None
Related Features
VS.SHO.RLRestoreIur.Rx WRFD-020203 Inter RNC Soft Handover
1.5.4.16 Number of Soft Handovers Initiated by SRNC on Iur Interface
Counters
67179061 VS.SHO.Att.Iur Number of Soft Handovers

Initiated by SRNC on Iur
Interface

BSC6900 UMTS
Description
This measurement item takes statistics of the number of soft handovers initiated by the SRNC
on Iur Interface.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the SRNC sends an UE
an ACTIVE SET UPDATE message on the Iur interface, and when the added or deleted radio
link exists in the DRNC, the SRNC measures this item on each Iur interface.
Figure 1-122 Active set update procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.SHO.Att.Iur WRFD-020203 Inter RNC Soft Handover

BSC6900 UMTS
1.5.4.17 Number of Successful Soft Handovers Initiated by SRNC on Iur Interface
Counters
67179062 VS.SHO.Succ.Iur Number of Successful Soft

Handovers Initiated by
SRNC on Iur Interface
Description
This measurement item takes statistics of the number of successful soft handovers initiated by
the SRNC on Iur Interface.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the SRNC receives from
the UE an ACTIVE SET UPDATE COMPLETE message and detects that the added or deleted
radio link exists in the DRNC, this item shall be measured on each Iur interface.
Figure 1-123 Active set update procedure (successful operation)
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.SHO.Succ.Iur WRFD-020203 Inter RNC Soft Handover
1.5.4.18 Number of COMMON TRANSPORT CHANNEL RESOURCES REQUEST

Messages Sent by SRNC on Iur Interface
Counters
67179057 VS.AttCommTrChResIur.T Number of Common

x Transport Channel Resource
Requests Sent by SRNC on
Iur Interface
Description
This measurement item takes statistics of the number of COMMON TRANSPORT CHANNEL
RESOURCES REQUEST messages sent by the SRNC on the Iur interface.
Measurement point
The measurement is triggered at point A as shown in the figure. During the common channel
setup procedure over the Iur interface, this counter is incremented by one each time the SRNC
sends a COMMON TRANSPORT CHANNEL RESOURCES REQUEST message based on
different Iur interfaces.

BSC6900 UMTS
Figure 1-124 Initialization procedure of common transport channel resources on the Iur interface
Formula
None
Unit
None
Related Features
VS.AttCommTrChResIur.T WRFD-010802 Inter RNC Cell Update

x
1.5.4.19 Number of COMMON TRANSPORT CHANNEL RESOURCES

RESPONSE Messages Received by SRNC on Iur Interface

BSC6900 UMTS
Counters
67179058 VS.SuccCommTrChResIur. Number of Common

Rx Transport Channel Resource
Responses Received by
SRNC on Iur Interface
Description
RESOURCES RESPONSE messages received by the SRNC on the Iur interface.
Measurement point
The measurement is triggered at point B, as shown in the figure. During the common channel
setup procedure over the Iur interface, this counter is incremented by one each time the SRNC
receives a COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message based
on different Iur interfaces.
Figure 1-125 Initialization procedure of common transport channel resources on the Iur interface
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.SuccCommTrChResIur. WRFD-010802 Inter RNC Cell Update

Rx
1.5.4.20 Number of COMMON TRANSPORT CHANNEL RESOURCES FAILURE

Messages Received by SRNC on Iur Interface Due to Transport Resource
Unavailable
Counters
67179059 VS.FailCommTrChResIur.N Number of Common

otSupp.Rx Transport Channel Resource
Failures Due to Transport
Resource Unavailable on Iur
Interface for SRNC
Description
RESOURCES FAILURE messages received by the SRNC on the Iur interface with the cause
of "Common Transport Channel Type Not Supported".
Measurement point
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.

BSC6900 UMTS
Figure 1-126 Common transport channel resource failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
VS.FailCommTrChResIur.N WRFD-010802 Inter RNC Cell Update

otSupp.Rx
1.5.4.21 Number of COMMON TRANSPORT CHANNEL RESOURCES RELEASE

REQUEST Messages of SRNC on Iur Interface

BSC6900 UMTS
Counters
67179060 VS.AttRelCommTrChResIu Number of Common

r.Tx Transport Channel Resource
Release Requests on Iur
Interface from SRNC
Description
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-127 Common transport channel resource release procedure on the Iur interface
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.AttRelCommTrChResIu WRFD-010802 Inter RNC Cell Update

r.Tx
1.5.4.22 Number of PS RABs Normally Released on CCH (FACH or PCH) for SRNC
(Iur Interface)
Counters
67191850 VS.RAB.NormRel.PS.CCH. Number of PS RABs

Iur Normally Released on Iur
Interface for SRNC (CCH
User Only)
Description
When the best cell is under a DRNC, these measurement items take statistics of the number of
RABs normally released on CCH (FACH or PCH) on the SRNC IUR interface.
Measurement point
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.

BSC6900 UMTS
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.PS.CCH. WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Iur Connection and Radio
and Release
1.5.4.23 Number of Normally Released CS RABs According to Different Service on

the IUR interface

BSC6900 UMTS
Counters
67191858 VS.RAB.NormRel.AMR.Iur Number of Normally

Released AMR RABs on Iur
Interface for SRNC(not
including WB-AMR)
67191845 VS.RAB.NormRel.CS64.Iur Number of CS

Conversational RABs
Normally Released on the
SRNC Iur Interface for
SRNC (Conversational with
DL Max Bit Rate as 64kbit/s)
67194987 VS.RAB.NormRel.CS.Str.Iu Number of CS Streaming

r RABs Normally Released on
73403816 VS.RAB.NormRel.AMRW Number of CS AMRWB

B.Iur RABs Normally Released on
the SRNC Iur Interface for
SRNC
Description
RABs normally released by the DRNC according to different service on the SRNC IUR interface.
Measurement point

BSC6900 UMTS

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.AMR.Iur WRFD-010501 Conversational QoS Class
VS.RAB.NormRel.CS64.Iur WRFD-010501 Conversational QoS Class
VS.RAB.NormRel.CS.Str.Iu WRFD-010502 Streaming QoS Class

r
VS.RAB.NormRel.AMRW WRFD-010613 AMR-WB (Adaptive Multi

B.Iur WRFD-010501 Rate Wide Band)

BSC6900 UMTS
1.5.4.24 Number of Abnormally Released CS RABs According to Different Service

on SRNC Iur Interface
Counters

Iur Released AMR RABs on Iur
Interface for SRNC(not
including WB-AMR)
67191860 VS.RAB.AbnormRel.CS64. Number of CS

Iur Conversational RABs
Abnormally Released on the
SRNC Iur Interface for
SRNC (Conversational with
DL Max Bitrate as 64kbit/s)
67194997 VS.RAB.AbnormRel.CS.Str Number of CS Streaming

.Iur RABs Abnormally Released
on Iur Interface for SRNC
73403815 VS.RAB.AbnormRel.AMR Number of CS AMRWB

WB.Iur RABs Abnormally Released
on the SRNC Iur Interface for
SRNC
Description
When the best cell is under a DRNC, the measurement items take statistics of the number of
abnormally released CS RABs 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
Connection Release", reference to 3GPP TS 25.413),the SRNC measures the items by the types
of services on the IUR interface.

BSC6900 UMTS
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

BSC6900 UMTS
The measurement is triggered at point A as shown in the figure. The SRNC sends to the CN an

BSC6900 UMTS
Figure 1-134 Iu connection release procedure triggered by the RNC
Formula
None
Unit
None
Related Features

Iur

Iur
VS.RAB.AbnormRel.CS.Str WRFD-010502 Streaming QoS Class

.Iur
VS.RAB.AbnormRel.AMR WRFD-010613 AMR-WB (Adaptive Multi

WB.Iur WRFD-010501 Rate Wide Band)

BSC6900 UMTS
1.5.4.25 Number of PS RABs Abnormally Released on CCH (FACH or PCH) for

SRNC (Iur Interface)
Counters
67191865 VS.RAB.AbnormRel.PS.CC Number of PS RABs

H.Iur Abnormally Released on Iur
Interface for SRNC (CCH
User Only)
Description
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
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.

BSC6900 UMTS
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
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

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.PS.CC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

H.Iur Connection and Radio
and Release
1.5.4.26 Number of Normally Released PS RABs According to Different Service on

the IUR interface

BSC6900 UMTS
Counters
67194988 VS.RAB.NormRel.PS.Conv Number of RABs Normally

.Iur Released for PS
Conversational Services on
67194989 VS.RAB.NormRel.PS.Str.Iu Number of RABs Normally

r Released for PS Streaming
Services on Iur Interface for
SRNC
73393847 VS.RAB.NormRel.PS.BE.Iu Number of PS BE RABs

r Normally Released on Iur
Interface for SRNC
Description
RABs normally released by the DRNC according to service types in PS domain on the SRNC
IUR interface.
Measurement point
is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or
according to service types in PS domain on Iur Interface.

BSC6900 UMTS
Signalling Connection Release" ,the RNC measures each item according to service types in PS
domain on Iur Interface.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.PS.Conv WRFD-010501 Conversational QoS Class

.Iur
VS.RAB.NormRel.PS.Str.Iu WRFD-010502 Streaming QoS Class

r
VS.RAB.NormRel.PS.BE.Iu WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

r WRFD-010503 Connection and Radio
WRFD-010504 and Release
Interactive QoS Class
Background QoS Class

BSC6900 UMTS
1.5.4.27 Number of Normally Released HSPA RABs on Iur Interface for SRNC
Counters
67194990 VS.RAB.NormRel.HSDPA. Number of Normally

Iur Released HSDSCH-Carried
RABs on Iur Interface for
SRNC
67194991 VS.RAB.NormRel.HSUPA. Number of EDCH-Carried

Iur RABs Normally Released on
Description
When the best cell is under a DRNC, these counters provide the number of RABs normally
released on the Iur interface according to different bearer types.
Measurement point
The measurement can be triggered at point A as shown in the figure. When the RNC receives
from the CN an IU RELEASE COMMAND message, it releases the corresponding RAB, and
then sends to the CN an IU RELEASE COMPLETE message. If the release cause contained in
the IU RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful
Relocation" or "Network Optimization", or if the RNC initiates a release request with the cause
value of "User Inactivity", "Network Optimization", or "UE Generated Signalling Connection
Release" before receiving the IU RELEASE COMMAND message from the CN, then this
counter is measured on the Iur interface according to the bearer types.

BSC6900 UMTS
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
VS.RAB.NormRel.HSDPA. WRFD-010651 HSDPA over Iur

Iur

BSC6900 UMTS
VS.RAB.NormRel.HSUPA. WRFD-010635 HSUPA over Iur

Iur
1.5.4.28 Number of Abnormally Released PS RABs According to Different Service

Type on SRNC Iur Interface
Counters
67194998 VS.RAB.AbnormRel.PS.Co Number of RABs

nv.Iur Abnormally Released for PS
67194999 VS.RAB.AbnormRel.PS.Str Number of RABs

.Iur Abnormally Released for PS
Streaming Services on Iur
Interface for SRNC
73393848 VS.RAB.AbnormRel.PS.BE Number of PS BE RABs

.Iur Abnormally Released on Iur
Interface for SRNC
Description
When the best cell is under a DRNC, these counters provide the number of RABs abnormally
released on the Iur interface according to service types in PS domain.
Measurement point
As shown in point A of the figure, when an exception occurs, the SRNC sends the CN a RAB
RELEASE REQUEST message. If the RNC receives from the CN a RAB ASSIGNMENT
REQUEST message which contains a cause value of abnormal release (a cause value except
"User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE
Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then the SRNC
measures the corresponding counter on the Iur interface according to the service types in PS
domain.

BSC6900 UMTS
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
domain.

BSC6900 UMTS
As shown in point A of the figure, when an exception occurs, the SRNC sends the CN an IU
domain.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.PS.Co WRFD-010501 Conversational QoS Class

nv.Iur
VS.RAB.AbnormRel.PS.Str WRFD-010502 Streaming QoS Class

.Iur
VS.RAB.AbnormRel.PS.BE WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

.Iur WRFD-010503 Connection and Radio

BSC6900 UMTS
1.5.4.29 Number of Abnormally Released HSPA-Carried RABs on SRNC Iur

Interface
Counters
67195000 VS.RAB.AbnormRel.HSDP Number of HSDSCH-

A.Iur Carried RABs Abnormally
Released on Iur Interface for
SRNC
67195001 VS.RAB.AbnormRel.HSUP Number of EDCH-Carried

A.Iur RABs Abnormally Released
Description
abnormally released RABs according to different bearer types on the SRNC IUR interface.
Measurement point
"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.

BSC6900 UMTS

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.HSDP WRFD-010651 HSDPA over Iur

A.Iur
VS.RAB.AbnormRel.HSUP WRFD-010635 HSUPA over Iur

A.Iur
1.5.4.30 Number of RLs with Reconfiguration Canceled by the SRNC over Iur

BSC6900 UMTS
Counters
67179050 VS.SHO.CancelRLRecfgIur Number of Radio Link

.Tx Synchronous
Reconfiguration
Interface for SRNC
Description
This measurement item takes statistics of the number of RLs whose reconfiguration is canceled
by the SRNC over the Iur interface.
Measurement point
The measurement is triggered at point C as shown in the figure. When the SRNC sends a RADIO
LINK RECONFIGURATION CANCEL message to the DRNC, the SRNC measures the item
for each Iur interface.
Figure 1-148 Radio link reconfiguration cancellation procedure over Iur
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.SHO.CancelRLRecfgIur WRFD-020203 Inter RNC Soft Handover

.Tx
1.5.4.31 Number of CS Conversational RABs carried on HSPA Normally Released

Counters
67196206 VS.RAB.NormRel.CS.HSP Number of HSPA-Carried

A.Conv.Iur CS Conversational RABs
Normally Released on Iur
Interface for SRNC
Description
CS Conversational RABs carried on HSPA normally released by the DRNC according to
different service on the SRNC IUR interface.
Measurement point

BSC6900 UMTS

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.CS.HSP WRFD-010619 CS voice over HSPA/HSPA

A.Conv.Iur WRFD-010651 +
WRFD-010635 HSDPA over Iur

HSUPA over Iur
1.5.4.32 Number of CS Conversational RABs carried on HSPA Abnormally

Released on Iur Interface for SRNC

BSC6900 UMTS
Counters
67196207 VS.RAB.AbnormRel.CS.HS Number of HSPA-Carried

PA.Conv.Iur CS Conversational RABs
Abnormally Released on Iur
Interface for SRNC
Description
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
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

BSC6900 UMTS

The measurement is triggered at point A as shown in the figure. The SRNC sends to the CN an

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.CS.HS WRFD-010619 CS voice over HSPA/HSPA

PA.Conv.Iur WRFD-010651 +
WRFD-010635 HSDPA over Iur

HSUPA over Iur
1.5.4.33 Number of Normally Released PS RABs that Are in CELL_PCH or

URA_PCH State on Iur Interface for SRNC

BSC6900 UMTS
Counters
73421884 VS.RAB.NormRel.PS.PCH. Number of Normally

Iur Released PS RABs that Are
in CELL_PCH or URA_PCH
State on Iur Interface for
SRNC
Description
This counter provides the number of normally released PS RABs that are in CELL_PCH or
URA_PCH state on the Iur interface if the UE camps on a cell under the DRNC. The release of
RABs in URA_PCH state is measured in the last cell that the UE camps on before entering the
URA_PCH state.
Measurement point
The measurement is triggered at point A as shown in the following figure. After receiving an
IU RELEASE COMMAND message from the CN, the RNC releases the corresponding RAB
and then sends an IU RELEASE COMPLETE message to the CN. If the release cause in the IU
RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful
Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", or if
the RNC has sent a release request with the cause of "User Inactivity", "Network Optimization",
or "UE Generated Signalling Connection Release" before the RNC receives the IU RELEASE
COMMAND message, then the counter is measured on the Iur interface if the UE camps on a
cell under the DRNC.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.PS.PCH. WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Iur Connection and Radio
and Release
1.5.4.34 Number of Abnormally Released PS RABs that Are in CELL_PCH or

URA_PCH State on Iur Interface for SRNC
Counters
73421885 VS.RAB.AbnormRel.PS.PC Number of Abnormally

H.Iur Released PS RABs that Are
State on Iur Interface for
SRNC
Description
This counter provides the number of abnormally released PS RABs that are in CELL_PCH or
URA_PCH state on the Iur interface if the UE camps on a cell under the DRNC. The release of
RABs in URA_PCH state is measured in the last cell that the UE camps on before entering the
URA_PCH state.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the UE camps
on a cell under the DRNC and a failure occurs, the SRNC sends the CN an RAB RELEASE
REQUEST message. After receiving the message, the CN sends an RAB ASSIGNMENT
REQUEST message to the RNC. If the RAB ASSIGNMENT REQUEST message contains a
cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful
Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), the SNRC measures
a counter on the Iur interface according to the RAB type.

BSC6900 UMTS
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.

BSC6900 UMTS
on a cell under the DRNC and a failure occurs, the SRNC sends the CN an IU RELEASE
or "Network Optimization", for details, see 3GPP TS 25.413), the SNRC measures a counter on
the Iur interface according to the RAB type.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.PS.PC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

H.Iur Connection and Radio
and Release
1.5.4.35 Number of RRC Connection Releases (CCCH) Sent by the SRNC over the
Iur Interface due to DSCR

BSC6900 UMTS
Counters
73423384 VS.RRC.AttConnRelCCCH Number of RRC Connection

.DSCR.Iur Releases (CCCH) Sent by the
SRNC over the Iur Interface
due to DSCR
Description
This counter provides the number of RRC CONNECTION RELEASE (CCCH) messages sent
by the SRNC over the Iur Interface because of Directed Signaling Connection Re-establishment
(DSCR).
Measurement point
The measurement is triggered at point A as shown in the figure, when the SRNC sends the UE
an RRC CONNECTION RELEASE (CCCH) message over the Iur interface because of DSCR.
Figure 1-158 RRC connection release procedure
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RRC.AttConnRelCCCH WRFD-021400 Direct Signaling Connection

.DSCR.Iur WRFD-010510 Re-establishment (DSCR)
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.5.4.36 Number of RRC Connection Releases (DCCH) Sent by the SRNC over the
Iur Interface due to DSCR
Counters
73423385 VS.RRC.AttConnRelDCCH Number of RRC Connection

.DSCR.Iur Releases (DCCH) Sent by the
SRNC over the Iur Interface
due to DSCR
Description
This counter provides the number of RRC CONNECTION RELEASE (DCCH) messages sent
by the SRNC over the Iur interface because of Directed Signaling Connection Re-establishment
(DSCR).
Measurement point
an RRC CONNECTION RELEASE (DCCH) message over the Iur interface because of DSCR.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RRC.AttConnRelDCCH WRFD-021400 Direct Signaling Connection

.DSCR.Iur WRFD-010510 Re-establishment (DSCR)
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.5.5 Measurement related to traffic for Iur Interface(TRFFIC.IUR)
Overview
The Iur interface traffic measurement is used to measure the uplink (UL) and downlink (DL)
signaling flows on the Iur interface and the UL and DL data streams in the CS and PS domains.

BSC6900 UMTS
Counters
Description
67199487 VS.SRNCIurBytes Number of UL Bytes Earlier than

SigDCH.Rx of Signaling Data V900R011
Received by SRNC
on DCH of Iur
Interface
67199488 VS.SRNCIurBytes Number of DL Bytes Earlier than

SigDCH.Tx of Signaling Data V900R011
Sent by SRNC on
DCH of Iur Interface

PSR99Conv.Rx of PS R99 V900R011
Conversational
Service Received by
SRNC on Iur
Interface

PSR99Str.Rx of PS R99 Streaming V900R011
Service Received by
SRNC on Iur
Interface

PSR99Int.Rx of PS R99 Interactive V900R011
Service Received by
SRNC on Iur
Interface

PSR99Bkg.Rx of PS R99 V900R011
Background Service
Received by SRNC
on Iur Interface

PSR99Conv.Tx of PS R99 V900R011
Conversational
Service Sent by
SRNC on Iur
Interface

PSR99Str.Tx of PS R99 Streaming V900R011
Service Sent by
SRNC on Iur
Interface

BSC6900 UMTS

Description

PSR99Int.Tx of PS R99 Interactive V900R011
Service Sent by
SRNC on Iur
Interface

PSR99Bkg.Tx of PS R99 V900R011
Background Service
Sent by SRNC on Iur
Interface

CSConv.Rx of CS Conversational V900R011
Service Received by
SRNC on DCH of Iur
Interface

CSStr.Rx of CS Streaming V900R011
Service Received by
SRNC on DCH of Iur
Interface

CSConv.Tx of CS Conversational V900R011
Service Sent by
SRNC on DCH of Iur
Interface

CSStr.Tx of CS Streaming V900R011
Service Sent by
SRNC on DCH of Iur
Interface
67199505 VS.DRNCIurBytes Number of UL Bytes Earlier than

DCH.Tx Sent by DRNC on V900R011
DCH of Iur Interface
67199506 VS.DRNCIurBytes Number of DL Bytes Earlier than

DCH.Rx Received by DRNC V900R011
Over DCH FP on the
Iur Interface
73410465 VS.SRNCIurBytes Number of bytes of V900R012

PSConvHSUPA.Rx PS HSUPA
conversational
service in SRNC for
IUR

BSC6900 UMTS

Description

PSStrHSUPA.Rx PS HSUPA
streaming service in
SRNC for IUR

PSIntHSUPA.Rx PS HSUPA
interactive service in
SRNC for IUR

PSBkgHSUPA.Rx PS HSUPA
background service
in SRNC for IUR

PSConvHSDPA.Tx PS HSDPA
conversational
service in SRNC for
IUR

PSStrHSDPA.Tx PS HSDPA
streaming service in
SRNC for IUR

PSIntHSDPA.Tx PS HSDPA
interactive service in
SRNC for IUR

PSBkgHSDPA.Tx PS HSDPA
background service
in SRNC for IUR

CSConvHSDPA.Tx CS HSDPA
conversational
service in SRNC for
IUR
73410478 VS.DRNCIurBytes Number of bytes of V900R012

HSDPA.Rx HSDPA services in
DRNC for IUR
73410479 VS.SRNCIurBytes Number of HSDPA V900R012

SigHSDPA.Tx Signaling Bytes on
Iur Interface in
SRNC

BSC6900 UMTS

Description
73410480 VS.SRNCIurBytes Number of HSUPA V900R012

SigHSUPA.Rx Signaling Bytes on
Iur Interface in
SRNC

CSConvHSUPA.Rx CS HSUPA
conversational
service in SRNC for
IUR
None
1.5.5.1 Number of UL Bytes of Signaling Data Received by SRNC on DCH of Iur

Interface
Counters
67199487 VS.SRNCIurBytesSigDCH. Number of UL Bytes of

Rx Signaling Data Received by
SRNC on DCH of Iur
Interface
Description
This counter provides the number of UL bytes of signaling data that the SRNC receives from
the DRNC on the DCH FP of the Iur interface.
Measurement point
When receiving UL signaling data on the signaling bearer DCH FP (excluding the EDCH FP)
of the Iur interface, the SRNC measures this counter. The value of this counter does not include
the number of bytes of FP headers and this counter is measured separately on different Iur
interfaces.
Formula
None

BSC6900 UMTS
Unit
byte
Related Features
VS.SRNCIurBytesSigDCH. WRFD-021000 Transport Channel

Rx Management
1.5.5.2 Number of DL Bytes of Signaling Data Sent by SRNC on DCH of Iur

Interface
Counters
67199488 VS.SRNCIurBytesSigDCH. Number of DL Bytes of

Tx Signaling Data Sent by
SRNC on DCH of Iur
Interface
Description
This counter provides the number of DL bytes of signaling data that the SRNC sends to the
DRNC on the DCH FP of the Iur interface.
Measurement point
When sending DL signaling data to the DRNC on the signaling bearer DCH FP (excluding the
HS-DSCH FP) of the Iur interface, the SRNC measures this counter. The value of this counter
does not include the number of bytes of FP headers and this counter is measured separately on
different Iur interfaces.
Formula
None
Unit
byte

BSC6900 UMTS
Related Features
VS.SRNCIurBytesSigDCH. WRFD-021000 Transport Channel

Tx Management
1.5.5.3 Number of Bytes of UL PS R99 Services Received by SRNC on Iur Interface
Counters
67199497 VS.SRNCIurBytesPSR99Co Number of UL Bytes of PS

nv.Rx R99 Conversational Service
Received by SRNC on Iur
Interface
67199498 VS.SRNCIurBytesPSR99Str Number of UL Bytes of PS

.Rx R99 Streaming Service
Interface
67199499 VS.SRNCIurBytesPSR99Int Number of UL Bytes of PS

.Rx R99 Interactive Service
Interface
67199500 VS.SRNCIurBytesPSR99Bk Number of UL Bytes of PS

g.Rx R99 Background Service
Interface
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

BSC6900 UMTS
Unit
byte
Related Features
VS.SRNCIurBytesPSR99Co WRFD-010501 Conversational QoS Class

nv.Rx
VS.SRNCIurBytesPSR99Str WRFD-010502 Streaming QoS Class

.Rx
VS.SRNCIurBytesPSR99Int WRFD-010503 Interactive QoS Class

.Rx
VS.SRNCIurBytesPSR99Bk WRFD-010504 Background QoS Class

g.Rx
1.5.5.4 Number of Bytes of DL PS R99 Services Sent by SRNC on Iur Interface
Counters
67199501 VS.SRNCIurBytesPSR99Co Number of DL Bytes of PS

nv.Tx R99 Conversational Service
Sent by SRNC on Iur
Interface
67199502 VS.SRNCIurBytesPSR99Str Number of DL Bytes of PS

.Tx R99 Streaming Service Sent
by SRNC on Iur Interface
67199503 VS.SRNCIurBytesPSR99Int Number of DL Bytes of PS

.Tx R99 Interactive Service Sent
by SRNC on Iur Interface
67199504 VS.SRNCIurBytesPSR99Bk Number of DL Bytes of PS

g.Tx R99 Background Service
Sent by SRNC on Iur
Interface
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.

BSC6900 UMTS
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
VS.SRNCIurBytesPSR99Co WRFD-010501 Conversational QoS Class

nv.Tx
VS.SRNCIurBytesPSR99Str WRFD-010502 Streaming QoS Class

.Tx
VS.SRNCIurBytesPSR99Int WRFD-010503 Interactive QoS Class

.Tx
VS.SRNCIurBytesPSR99Bk WRFD-010504 Background QoS Class

g.Tx
1.5.5.5 Number of Bytes of UL CS Services Received by SRNC over DCH on Iur

Interface
Counters
67199489 VS.SRNCIurBytesCSConv. Number of UL Bytes of CS

Rx Conversational Service
Received by SRNC on DCH
of Iur Interface
67199490 VS.SRNCIurBytesCSStr.Rx Number of UL Bytes of CS

Streaming Service Received
by SRNC on DCH of Iur
Interface

BSC6900 UMTS
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
VS.SRNCIurBytesCSConv. WRFD-010501 Conversational QoS Class

Rx
VS.SRNCIurBytesCSStr.Rx WRFD-010502 Streaming QoS Class
1.5.5.6 Number of Bytes of DL CS Services Sent by SRNC over DCH on Iur Interface
Counters
67199493 VS.SRNCIurBytesCSConv. Number of DL Bytes of CS

Tx Conversational Service Sent
by SRNC on DCH of Iur
Interface
67199494 VS.SRNCIurBytesCSStr.Tx Number of DL Bytes of CS

Streaming Service Sent by
SRNC on DCH of Iur
Interface
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.

BSC6900 UMTS
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
VS.SRNCIurBytesCSConv. WRFD-010501 Conversational QoS Class

Tx
VS.SRNCIurBytesCSStr.Tx WRFD-010502 Streaming QoS Class
1.5.5.7 Number of UL Bytes Sent by DRNC on DCH of Iur Interface
Counters
67199505 VS.DRNCIurBytesDCH.Tx Number of UL Bytes Sent by

DRNC on DCH of Iur
Interface
Description
This counter provides the number of UL data bytes that the DRNC sends to the SRNC on the
DCH of the Iur interface.
Measurement point
When sending the UL MAC PDU on the DCH FP of the Iur interface, the DRNC measures this
counter separately on different Iur interfaces (excluding the number of bytes of FP headers).
Formula
None

BSC6900 UMTS
Unit
byte
Related Features
VS.DRNCIurBytesDCH.Tx WRFD-021000 Transport Channel

Management
1.5.5.8 Number of DL Bytes Received by DRNC on DCH of Iur Interface
Counters
67199506 VS.DRNCIurBytesDCH.Rx Number of DL Bytes

Received by DRNC Over
DCH FP on the Iur Interface
Description
This counter provides the number of DL data bytes that the DRNC receives from the SRNC
Over DCH FP on the Iur interface.
Measurement point
When receiving the DL MAC PDU on the DCH FP of the Iur interface, the DRNC measures
this counter separately on different Iur interfaces (excluding the number of bytes of FP headers).
Formula
None
Unit
byte
Related Features
VS.DRNCIurBytesDCH.Rx WRFD-021000 Transport Channel

Management

BSC6900 UMTS
1.5.5.9 Number of Bytes of PS HSUPA Services Received by SRNC on Iur Interface
Counters
73410465 VS.SRNCIurBytesPSConv Number of bytes of PS

HSUPA.Rx HSUPA conversational
service in SRNC for IUR
73410466 VS.SRNCIurBytesPSStrHS Number of bytes of PS

UPA.Rx HSUPA streaming service in
SRNC for IUR
73410467 VS.SRNCIurBytesPSIntHS Number of bytes of PS

UPA.Rx HSUPA interactive service in
SRNC for IUR
73410470 VS.SRNCIurBytesPSBkgH Number of bytes of PS

SUPA.Rx HSUPA background service
in SRNC for IUR
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
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
VS.SRNCIurBytesPSConv WRFD-010617 VoIP over HSPA/HSPA+

HSUPA.Rx WRFD-010501 Conversational QoS Class
VS.SRNCIurBytesPSStrHS WRFD-010635 HSUPA over Iur

UPA.Rx

BSC6900 UMTS
VS.SRNCIurBytesPSIntHS WRFD-010635 HSUPA over Iur

UPA.Rx
VS.SRNCIurBytesPSBkgH WRFD-010635 HSUPA over Iur

SUPA.Rx
1.5.5.10 Number of Bytes of PS HSDPA Services Received by SRNC on Iur Interface
Counters
73410471 VS.SRNCIurBytesPSConv Number of bytes of PS

HSDPA.Tx HSDPA conversational
73410472 VS.SRNCIurBytesPSStrHS Number of bytes of PS

DPA.Tx HSDPA streaming service in
SRNC for IUR
73410473 VS.SRNCIurBytesPSIntHS Number of bytes of PS

DPA.Tx HSDPA interactive service in
SRNC for IUR
73410474 VS.SRNCIurBytesPSBkgH Number of bytes of PS

SDPA.Tx HSDPA background service
in SRNC for IUR
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
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

BSC6900 UMTS
Related Features
VS.SRNCIurBytesPSConv WRFD-010617 VoIP over HSPA/HSPA+

HSDPA.Tx WRFD-010501 Conversational QoS Class
VS.SRNCIurBytesPSStrHS WRFD-010651 HSDPA over Iur

DPA.Tx
VS.SRNCIurBytesPSIntHS WRFD-010651 HSDPA over Iur

DPA.Tx
VS.SRNCIurBytesPSBkgH WRFD-010651 HSDPA over Iur

SDPA.Tx
1.5.5.11 Number of bytes of CS HSDPA conversational service in SRNC for IUR
Counters
73410476 VS.SRNCIurBytesCSConv Number of bytes of CS

HSDPA.Tx HSDPA conversational
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

BSC6900 UMTS
Related Features
VS.SRNCIurBytesCSConv WRFD-010619 CS voice over HSPA/HSPA

HSDPA.Tx +
1.5.5.12 Number of bytes of HSDPA services in DRNC for IUR
Counters
73410478 VS.DRNCIurBytesHSDPA. Number of bytes of HSDPA

Rx services in DRNC for IUR
Description
This counter provides the DL bytes of the DRNC HSDSCH service. The byte are sent by the
SRNC.
Measurement point
The measurement is triggered when the DRNC receives DL MAC PDUs over the HSDSCH FP
on the Iur interface. The FP header is not included. The measurement is performed respectively
on the basis of Iur interfaces.
Formula
None
Unit
byte
Related Features
VS.DRNCIurBytesHSDPA. WRFD-010651 HSDPA over Iur

Rx
1.5.5.13 Number of HSDPA Signaling Bytes on Iur Interface in SRNC

BSC6900 UMTS
Counters
73410479 VS.SRNCIurBytesSigHSDP Number of HSDPA

A.Tx Signaling Bytes on Iur
Interface in SRNC
Description
This counter provides the number of the DL signaling bytes that are sent to the DRNC from the
SRNC over the HSDSCH FP on the Iur interface.
Measurement point
The measurement is triggered when the SRNC sends DL signaling over the HSDSCH FP
carrying the signaling on the Iur interface to the DRNC. The FP header is not included. The
Formula
None
Unit
byte
Related Features
VS.SRNCIurBytesSigHSDP WRFD-010651 HSDPA over Iur

A.Tx WRFD-010652 SRB over HSDPA
1.5.5.14 Number of HSUPA Signaling Bytes on Iur Interface in SRNC
Counters
73410480 VS.SRNCIurBytesSigHSUP Number of HSUPA

A.Rx Signaling Bytes on Iur
Interface in SRNC

BSC6900 UMTS
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
VS.SRNCIurBytesSigHSUP WRFD-010635 HSUPA over Iur

A.Rx WRFD-010636 SRB over HSUPA
1.5.5.15 Number of bytes of CS HSUPA conversational service in SRNC for IUR
Counters
73410481 VS.SRNCIurBytesCSConv Number of bytes of CS

HSUPA.Rx HSUPA conversational
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

BSC6900 UMTS
Formula
None
Unit
byte
Related Features
VS.SRNCIurBytesCSConv WRFD-010619 CS voice over HSPA/HSPA

HSUPA.Rx +
1.6 Measurement of MPU Performance(MPU)

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

BSC6900 UMTS
1.6.1 Measurement related to MPU(MPU)
Overview
The MPU measurement is used to assess the running performance of an MPU subsystem in the
RNC.
Counters
Description
67204521 VS.PSLoad.ULThr Throughput of PS Earlier than

uput.MPU Uplink Data for V900R011
MPU
67204522 VS.PSLoad.DLThr Throughput of PS Earlier than

uput.MPU Downlink Data for V900R011
MPU
None
1.6.1.1 Throughput of PS Uplink Data for MPU
Counters
67204521 VS.PSLoad.ULThruput.MP Throughput of PS Uplink

U Data for MPU
Description
This counter provides the total uplink PS throughput in the MPU subsystem, including
retransmitted data. This counter is measured at the Radio Link Control (RLC) layer, whereas
RLC headers are not measured. During soft handovers, the throughput is measured before the
RNC combines the traffic on each link.
Measurement point
The RNC takes samples on the uplink traffic of all PS services every five seconds in the specified
measurement period. At the end of the measurement period, the RNC divides the accumulated
uplink traffic by the sampling duration to obtain the uplink PS throughput of the MPU in the
measurement period.

BSC6900 UMTS
Formula
None
Unit
kbit/s
Related Features
VS.PSLoad.ULThruput.MP WRFD-040100 Flow Control

U
1.6.1.2 Throughput of PS Downlink Data for MPU
Counters
67204522 VS.PSLoad.DLThruput.MP Throughput of PS Downlink

U Data for MPU
Description
This counter provides the downlink throughput of all PS services in the MPU subsystem,
including retransmitted data. This counter is measured at the Radio Link Control (RLC) layer
and RLC headers are not measured. During soft handovers (not including softer handovers), the
throughput on all links are measured.
Measurement point
The RNC takes samples on the downlink traffic of all PS services every five seconds in the
specified measurement period. At the end of the measurement period, the RNC divides the
accumulated downlink traffic by the sampling duration to obtain the downlink PS throughput
of the MPU in the measurement period.
Formula
None
Unit
kbit/s

BSC6900 UMTS
Related Features
VS.PSLoad.DLThruput.MP WRFD-040100 Flow Control

U
1.7 Measurement of NODEB Performance(NODEB)

Overview
The measurement object type NodeB is used to measure the performance of a NodeB. The NodeB
belongs to the RNC and contains one measurement set NODEB.
FunctionSubSets
ALGO.NODEB Measurement related to Algorithm per

NodeB
1.7.1 Measurement related to Algorithm per NodeB

(ALGO.NODEB)
Overview
The NodeB algorithm measurement involves the Iub congestion measurement, NodeB
unavailability measurement, dynamic spectrum sharing measurement, and uplink NodeB credit
resource consumption for UE admission.
Iub congestion measurement is aimed to check whether the configured Iub bandwidth can meet
the requirements of UEs under the NodeB. Based on this measurement result, operators can
perform fault location or determine whether capacity expansion is required. The RNC
periodically monitors the bandwidth usage of each Iub path under the NodeB. If the remaining
bandwidth is less than a congestion left bandwidth threshold, the RNC determines that
congestion occurs and sends a congestion indication message. After the RNC detects that the
remaining bandwidth is more than the congestion clear clearing threshold, it sends a congestion
elimination message.
NodeB unavailability measurement is aimed to detect the condition that a NodeB becomes
unavailable due to a fault or misoperation. This measurement can be used to analyze the impact
of the fault or misoperation on services.
Dynamic spectrum sharing enables the UMTS network to use some spectrums of the GSM
network when the GSM traffic is light. Dynamic spectrum sharing measurement is used to assess
the performance of this function.

BSC6900 UMTS
These counters measure the NodeB credit usage when CE Overbooking is enabled to determine
whether to perform capacity expansion for CE resources and to locate the fault.
Counters
Description
67192134 VS.IUB.UL.Cong. Number of Iub UL Earlier than

Num Congestions V900R011
67192135 VS.IUB.DL.Cong. Number of Iub DL Earlier than

Num Congestions V900R011
67203854 VS.IUB.UL.Cong.T Duration of Iub UL Earlier than

ime Congestion V900R011
67203855 VS.IUB.DL.Cong.T Duration of Iub DL Earlier than

ime Congestion V900R011
67203853 VS.NodeB.Unavail- Duration of NodeB Earlier than

Time Unavailability V900R011
73441119 VS.DSS.NodeB.Act Total Dynamic V900R013

.Duration Spectrum Sharing
(DSS) Activation
Duration
73423295 VS.DSS.NodeB.Act Number of Received V900R013

.Num Dynamic Spectrum
Sharing (DSS)
73423296 VS.DSS.NodeB.Nor Number of Normal V900R013

malDeAct.Num Spectrum
Withdrawals
73423297 VS.DSS.NodeB.Urg Number of Urgent V900R013

entDeAct.Num Spectrum
Withdrawals
73423298 VS.DSS.NodeB.Ab Number of V900R013

normalDeAct.Num Abnormal Spectrum
Withdrawals
73441218 VS.NodeB.ULCred Average NodeB V900R014

itUsed.Mean Uplink Credit Usage
When CE
Overbooking Is
Enabled for NodeB
73424007 VS.NodeB.ULCred Maximum NodeB V900R014

itUsed.Max Uplink Credit Usage
When CE
Overbooking Is
Enabled for NodeB

BSC6900 UMTS

Description
73424008 VS.NodeB.ULCred Minimum NodeB V900R014

itUsed.Min Uplink Credit Usage
When CE
Overbooking Is
Enabled for NodeB
None
1.7.1.1 Number of UL or DL Congestions on Iub Interface
Counters
67192134 VS.IUB.UL.Cong.Num Number of Iub UL

Congestions
67192135 VS.IUB.DL.Cong.Num Number of Iub DL

Congestions
Description
These counters provide the number of uplink or downlink transmission bandwidth (admission
bandwidth) congestions on the Iub interface of the NodeB. When the residual bandwidth on the
Iub interface is less than the configured congestion bandwidth threshold, congestion occurs on
the Iub interface.
Measurement point
In the measurement period, the RNC measures the corresponding counter when it detects that
the uplink or downlink bandwidth resources of a NodeB change from non-congested state to
congested state.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.IUB.UL.Cong.Num WRFD-020106 Load Reshuffling
VS.IUB.DL.Cong.Num WRFD-020106 Load Reshuffling
1.7.1.2 Time of UL or DL Congestions on Iub Interface
Counters
67203854 VS.IUB.UL.Cong.Time Duration of Iub UL

Congestion
67203855 VS.IUB.DL.Cong.Time Duration of Iub DL

Congestion
Description
These counters provide the duration of uplink or downlink transmission bandwidth (admission
bandwidth) congestions on the Iub interface of a NodeB. When the residual bandwidth on the
Iub interface is less than the configured congestion bandwidth threshold, congestion occurs on
the Iub interface.
Measurement point
In the measurement period, the RNC measures the accumulated duration of uplink or downlink
bandwidth resource congestion for each NodeB.
Formula
None
Unit
s
Related Features
VS.IUB.UL.Cong.Time WRFD-020106 Load Reshuffling
VS.IUB.DL.Cong.Time WRFD-020106 Load Reshuffling

BSC6900 UMTS
1.7.1.3 NodeB Unavailability Time
Counters
67203853 VS.NodeB.UnavailTime Duration of NodeB

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

tion Sharing (DSS) Activation
Duration

BSC6900 UMTS
Description
This counter provides the duration when Dynamic Spectrum Sharing (DSS) is activated for a
NodeB.
Measurement point
The measurement starts when a NodeB receives a spectrum activation command and stops when
the NodeB receives a spectrum deactivation command. At the end of the measurement period,
DSS activation duration is accumulated in this NodeB.
Formula
None
Unit
s
Related Features
VS.DSS.NodeB.Act.Dura- MRFD-221802 GSM and UMTS Dynamic

tion Spectrum Sharing(UMTS)
1.7.1.5 Number of Received Dynamic Spectrum Sharing (DSS)
Counters
73423295 VS.DSS.NodeB.Act.Num Number of Received

Dynamic Spectrum Sharing
(DSS)
Description
This counter provides the number of received commands that instruct a NodeB in Dynamic
Spectrum Sharing (DSS).
Measurement point
In a measurement period, this counter is incremented by one each time the NodeB receives a
spectrum activation command that instructs it in DSS.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DSS.NodeB.Act.Num MRFD-221802 GSM and UMTS Dynamic

Spectrum Sharing(UMTS)
1.7.1.6 Number of Normal Spectrum Withdrawals
Counters
73423296 VS.DSS.NodeB.NormalDe Number of Normal Spectrum

Act.Num Withdrawals
Description
This counter provides the number of received commands that instruct a NodeB in a normal
spectrum withdrawal.
Measurement point
spectrum deactivation command that instructs it in a normal spectrum withdrawal.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.DSS.NodeB.NormalDe MRFD-221802 GSM and UMTS Dynamic

Act.Num Spectrum Sharing(UMTS)
1.7.1.7 Number of Urgent Spectrum Withdrawals
Counters
73423297 VS.DSS.NodeB.UrgentDeA Number of Urgent Spectrum

ct.Num Withdrawals
Description
This counter provides the number of received commands that instruct a NodeB in an urgent
spectrum withdrawal.
Measurement point
spectrum deactivation command that instructs it in an urgent spectrum withdrawal.
Formula
None
Unit
None
Related Features
VS.DSS.NodeB.UrgentDeA MRFD-221802 GSM and UMTS Dynamic

ct.Num Spectrum Sharing(UMTS)
1.7.1.8 Number of Abnormal Spectrum Withdrawals

BSC6900 UMTS
Counters
73423298 VS.DSS.NodeB.AbnormalD Number of Abnormal

eAct.Num Spectrum Withdrawals
Description
This counter provides the number of times that connections between the RNC and the M2000
are abnormally disconnected.
Measurement point
In a measurement period, this counter is incremented by one each time a spectrum is deactivated
for a spectrum withdrawal that is initiated by the RNC and triggered by failed handshakes
between the RNC and the M2000.
Formula
None
Unit
None
Related Features
VS.DSS.NodeB.AbnormalD MRFD-221802 GSM and UMTS Dynamic

eAct.Num Spectrum Sharing(UMTS)
1.7.1.9 NodeB Credit Usage When CE Overbooking Is Enabled
Counters
73441218 VS.NodeB.ULCreditUsed. Average NodeB Uplink

Mean Credit Usage When CE
Overbooking Is Enabled for
NodeB

BSC6900 UMTS
73424007 VS.NodeB.ULCreditUsed. Maximum NodeB Uplink

Max Credit Usage When CE
NodeB
73424008 VS.NodeB.ULCreditUsed. Minimum NodeB Uplink

Min Credit Usage When CE
NodeB
Description
These counters measure the average, maximum, and minimum NodeB credit usage when CE
Overbooking is enabled. When CE Overbooking is disabled, the measurement result is 0.
Measurement point
The RNC takes samples of the NodeB credit usage when CE Overbooking is enabled in a
measurement period of 5s. At the end of the measurement period, the RNC obtains the maximum
and minimum NodeB credit usage, and then divides the accumulated NodeB credit usage by the
number of samples to obtain the average NodeB credit usage in the measurement period.
Formula
None
Unit
None
Related Features
VS.NodeB.ULCreditUsed. WRFD-140212 CE Overbooking

Mean

Max

Min

BSC6900 UMTS
1.8 Measurement of Physical RNC Node(NODESHARE)

Overview
Physical RNC Node
FunctionSubSets
RAB.NODESHARE Radio Access Bearer (RAB) Measurement

for Physical RNC Nodes
RRC.NODESHARE Radio Resource Control (RRC)

Measurement for Physical RNC Nodes
1.8.1 Radio Access Bearer (RAB) Measurement for Physical RNC

Nodes(RAB.NODESHARE)
Overview
This function subset provides RAB measurement for UEs whose load is shared between physical
RNC nodes.
Counters
Description
73426004 VS.RAB.AttEstab Number of CS RAB V900R015

CS.Conv.Node- Assignment
Share Requests for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
(Conversational
Service)

BSC6900 UMTS

Description
73426005 VS.RAB.SuccEstab Number of V900R015

CS.Conv.Node- Successful CS RAB
Share Assignment
Requests for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
(Conversational
Service)
73426006 VS.RAB.AttEstabP Number of PS RAB V900R015

S.Bkg.NodeShare Assignment
Requests for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
(Background
Service)

S.Int.NodeShare Assignment
Requests for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
(Interactive Service)

PS.Bkg.NodeShare Successful PS RAB
Assignment
Requests for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
(Background
Service)

PS.Int.NodeShare Successful PS RAB
assignment Requests
for UEs Whose Load
Is Shared Between
Physical RNC Nodes
(Interactive Service)

BSC6900 UMTS

Description
73426010 VS.RAB.AbnormR Number of CS RABs V900R015

el.CS.RF.Node- Released
Share Abnormally due to
Radio Link Failure
for UEs Whose Load
Is Shared Between
Physical RNC Nodes
73426011 VS.RAB.AbnormR Number of PS RABs V900R015

el.PS.RF.Node- Released
Share Abnormally due to
Radio Link Failure
for UEs Whose Load
Is Shared Between
Physical RNC Nodes

el.CS.NodeShare Released
Abnormally for UEs
Whose Load Is
Shared Between
Physical RNC Nodes

el.PS.NodeShare Released
Abnormally for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
73426014 VS.RAB.NormRel. Number of CS RABs V900R015

CS.NodeShare Released Normally
for UEs Whose Load
Is Shared Between
Physical RNC Nodes
73426015 VS.RAB.NormRel. Number of PS RABs V900R015

PS.NodeShare Released Normally
for UEs Whose Load
Is Shared Between
Physical RNC Nodes
None

BSC6900 UMTS
1.8.1.1 Number of CS RAB Assignment Requests for UEs Whose Load Is Shared
Between Physical RNC Nodes (Conversational Service)
Counters
73426004 VS.RAB.AttEstabCS.Conv. Number of CS RAB

NodeShare Assignment Requests for
UEs Whose Load Is Shared
Between Physical RNC
Nodes (Conversational
Service)
Description
This function subset provides the number of CS RAB assignment requests for UEs whose load
is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point A shown in the figure. When the RNC receives a RAB
ASSIGNMENT REQUEST message from the CN, this counter is measured based on the CS
service type and physical RNC node if the UE load is shared between physical RNC nodes.
Figure 1-160 RAB setup procedure (successful operation)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AttEstabCS.Conv. WRFD-150211 RNC in Pool Load Sharing

NodeShare
1.8.1.2 Number of Successful CS RAB Assignment Requests for UEs Whose Load
Is Shared Between Physical RNC Nodes (Conversational Service)
Counters
73426005 VS.RAB.SuccEstabCS.Con Number of Successful CS

v.NodeShare RAB Assignment Requests
for UEs Whose Load Is
Shared Between Physical
RNC Nodes (Conversational
Service)
Description
This function subset provides the number of successful CS RAB assignment requests for UEs
whose load is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point B shown in the figure. When the RNC receives a RADIO
RESPONSE message to the CN, this counter is measured based on the CS service type and
physical RNC node if the UE load is shared between physical RNC nodes.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SuccEstabCS.Con WRFD-150211 RNC in Pool Load Sharing

v.NodeShare
1.8.1.3 Number of PS RAB Assignment Requests for UEs Whose Load Is Shared
Between Physical RNC Nodes

BSC6900 UMTS
Counters
73426006 VS.RAB.AttEstabPS.Bkg.N Number of PS RAB

odeShare Assignment Requests for
Nodes (Background Service)
73426007 VS.RAB.AttEstabPS.Int.No Number of PS RAB

deShare Assignment Requests for
Nodes (Interactive Service)
Description
This function subset provides the number of PS RAB assignment requests for UEs whose load
is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point A shown in the figure. When the RNC receives a RAB
ASSIGNMENT REQUEST message from the CN, this counter is measured based on the PS
service type and physical RNC node if the UE load is shared between physical RNC nodes.
Figure 1-162 Successful RAB setup procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AttEstabPS.Bkg.N WRFD-150211 RNC in Pool Load Sharing

odeShare
VS.RAB.AttEstabPS.Int.No WRFD-150211 RNC in Pool Load Sharing

deShare
1.8.1.4 Number of Successful PS RAB Assignment Requests for UEs Whose Load
Is Shared Between Physical RNC Nodes
Counters
73426008 VS.RAB.SuccEstabPS.Bkg. Number of Successful PS

NodeShare RAB Assignment Requests
RNC Nodes (Background
Service)
73426009 VS.RAB.SuccEstabPS.Int.N Number of Successful PS

odeShare RAB assignment Requests
RNC Nodes (Interactive
Service)
Description
This function subset provides the number of successful PS RAB assignment requests for UEs
whose load is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point B shown in the figure. When the RNC receives a RADIO

BSC6900 UMTS
RESPONSE message to the CN, these counters are measured based on the PS service type and
physical RNC node if the UE load is shared between physical RNC nodes.
Figure 1-163 PS RAB setup procedure
Formula
None
Unit
None
Related Features
VS.RAB.SuccEstabPS.Bkg. WRFD-150211 RNC in Pool Load Sharing

NodeShare
VS.RAB.SuccEstabPS.Int.N WRFD-150211 RNC in Pool Load Sharing

odeShare
1.8.1.5 Number of RABs Released Abnormally due to Radio Link Failure for UEs
Whose Load Is Shared Between Physical RNC Nodes

BSC6900 UMTS
Counters
73426010 VS.RAB.AbnormRel.CS.RF Number of CS RABs

.NodeShare Released Abnormally due to
Radio Link Failure for UEs
Whose Load Is Shared
Nodes
73426011 VS.RAB.AbnormRel.PS.RF Number of PS RABs

.NodeShare Released Abnormally due to
Radio Link Failure for UEs
Nodes
Description
This counter provides the number of CS RABs released abnormally due to the radio link failure
for UEs whose load is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point A shown in the figure. When radio link failure occurs,
the RNC sends a RAB RELEASE REQUEST message to the CN with the cause value of "Radio
Connection With UE Lost" or "Failure in the Radio Interface Procedure." Then, when the RNC
receives a RAB ASSIGNMENT REQUEST message from the CN with a cause value other than
"User Inactivity," "Normal Release," "Successful Relocation," and "Network Optimization,"
this counter is measured based on the service domain and the physical RNC node if the UE load
is shared between physical RNC nodes. For details on cause values indicating a normal release,
see 3GPP TS 25.413.

BSC6900 UMTS
the RNC sends a RAB RELEASE REQUEST message to the CN with the cause value of "Radio
receives an IU RELEASE COMMAND message from the CN with a cause value other than
see 3GPP TS 25.413.

BSC6900 UMTS
the RNC sends an IU RELEASE REQUEST message to the CN with the cause value of "Radio
receives an IU RELEASE COMMAND message from the CN with a cause value other than
see 3GPP TS 25.413.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.CS.RF WRFD-150211 RNC in Pool Load Sharing

.NodeShare
VS.RAB.AbnormRel.PS.RF WRFD-150211 RNC in Pool Load Sharing

.NodeShare
1.8.1.6 Number of RABs Released Abnormally for UEs Whose Load Is Shared

BSC6900 UMTS
Counters
73426012 VS.RAB.AbnormRel.CS.No Number of CS RABs

deShare Released Abnormally for
Nodes
73426013 VS.RAB.AbnormRel.PS.No Number of PS RABs

deShare Released Abnormally for
Nodes
Description
This counter provides the number of RABs released abnormally for UEs whose load is shared
between physical RNC nodes.
Measurement point
This measurement is triggered at point A shown in the figure. When a failure occurs, the RNC
sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN a RAB
ASSIGNMENT REQUEST message with a cause value other than "User Inactivity," "Normal
Release," "Successful Relocation," and "Network Optimization," this counter is measured based
on the domain of the RAB service and the physical RNC node if the UE load is shared between
physical RNC nodes. For details on cause values indicating a normal release, see 3GPP TS
25.413.

BSC6900 UMTS
sends the CN a RAB RELEASE REQUEST message. If the RNC receives from the CN an IU
RELEASE COMMAND message with a cause value other than "User Inactivity," "Normal
25.413.
sends the CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU
RELEASE COMMAND message with a cause value other than "User Inactivity," "Normal
25.413.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.CS.No WRFD-150211 RNC in Pool Load Sharing

deShare
VS.RAB.AbnormRel.PS.No WRFD-150211 RNC in Pool Load Sharing

deShare
1.8.1.7 Number of RABs Released Normally for UEs Whose Load Is Shared Between
Physical RNC Nodes

BSC6900 UMTS
Counters
73426014 VS.RAB.NormRel.CS.No- Number of CS RABs

deShare Released Normally for UEs
Nodes
73426015 VS.RAB.NormRel.PS.No- Number of PS RABs

deShare Released Normally for UEs
Nodes
Description
This counter provides the number of RABs released normally for UEs whose load is shared
Measurement point
This measurement is triggered at point A shown in the figure. After receiving an IU RELEASE
COMMAND message from the CN, the RNC releases the corresponding RAB and then sends
an IU RELEASE COMPLETE message to the CN. If the release cause in the IU RELEASE
COMMAND message is "User Inactivity," "Normal Release," "Successful Relocation," or
"Network Optimization," or if the RNC has sent a release request with the cause value of "User
Inactivity," "Network Optimization," or "UE Generated Signalling Connection Release" before
the RNC receives the IU RELEASE COMMAND message, then these counters are measured
based on the domain of the RAB service and the physical RNC node if the UE load is shared

BSC6900 UMTS
This measurement is triggered at point A shown in the figure. After receiving a RAB
ASSIGNMENT REQUEST message with a RAB release request from the CN, the RNC releases
the corresponding RAB and then sends a RAB ASSIGNMENT RESPONSE message to the CN.
If the release cause in the RAB ASSIGNMENT REQUEST message is "User Inactivity,"
"Normal Release," "Successful Relocation," or "Network Optimization," or if the RNC has sent
a release request with the cause value of "User Inactivity," "Network Optimization," or "UE
Generated Signalling Connection Release" before the RNC receives the IU RELEASE
COMMAND message, then these counters are measured based on the domain of the RAB service
and the physical RNC node if the UE load is shared between physical RNC nodes.
Figure 1-171 Successful RAB release procedure
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RAB.NormRel.CS.No- WRFD-150211 RNC in Pool Load Sharing

deShare
VS.RAB.NormRel.PS.No- WRFD-150211 RNC in Pool Load Sharing

deShare
1.8.2 Radio Resource Control (RRC) Measurement for Physical

RNC Nodes(RRC.NODESHARE)
Overview
This function subset provides RRC measurement for UEs whose load is shared between physical
RNC nodes.
Counters
Description
73426016 VS.RRC.AttConnE Number of RRC V900R015

stab.NodeShare Connection Requests
Sent by UEs Whose
Load Is Shared
Between Physical
RNC Nodes
73426017 VS.RRC.SuccConn Number of V900R015

Estab.NodeShare Successful RRC
Connection Requests
Sent by UEs Whose
Load Is Shared
Between Physical
RNC Nodes
73426018 VS.RRC.ConnEsta Maximum Delay in V900R015

bTimeMax.CellDC Setting Up RRC
H.NodeShare Connection for UEs
in CELL_DCH State
Whose Load Is
Shared Between
Physical RNC Nodes

BSC6900 UMTS

Description
73426020 VS.RRC.ConnEsta Maximum Delay in V900R015

bTimeMax.CellFA Setting Up RRC
CH.NodeShare Connection for UEs
in CELL_FACH
State Whose Load Is
Shared Between
Physical RNC Nodes
73426019 VS.RRC.ConnEsta Average Delay in V900R015

bTimeMean.CellD Setting Up RRC
CH.NodeShare Connection for UEs
in CELL_DCH State
Whose Load Is
Shared Between
Physical RNC Nodes
73426021 VS.RRC.ConnEsta Average Delay in V900R015

bTimeMean.CellF Setting Up RRC
ACH.NodeShare Connection for UEs
in CELL_FACH
State Whose Load Is
Shared Between
Physical RNC Nodes
73426167 VS.LoadSharedAct Number of UEs V900R015

iveUEs.NodeShare Whose Load Is
Shared Between
Physical RNC Nodes
None
1.8.2.1 Number of RRC Connection Requests Sent by UEs Whose Load Is Shared
Counters
73426016 VS.RRC.AttConnEstab.No- Number of RRC Connection

deShare Requests Sent by UEs Whose
Load Is Shared Between
Physical RNC Nodes

BSC6900 UMTS
Description
This counter provides the number of RRC connection requests sent by UEs whose load is shared
Measurement point
This measurement is triggered at point A shown in the figure. When the RNC receives an RRC
CONNECTION REQUEST message from a UE, this counter is measured for the RNC if the
UE load is shared between physical RNC nodes.
Figure 1-172 Procedure for successful RRC connection setup
Formula
None
Unit
None
Related Features
VS.RRC.AttConnEstab.No- WRFD-150211 RNC in Pool Load Sharing

deShare

BSC6900 UMTS
1.8.2.2 Number of Successful RRC Connection Requests Sent by UEs Whose Load
Is Shared Between Physical RNC Nodes
Counters
73426017 VS.RRC.SuccConnEstab.N Number of Successful RRC

odeShare Connection Requests Sent by
Nodes
Description
This counter provides the number of successful RRC connection requests sent by UEs whose
load is shared between physical RNC nodes.
Measurement point
This measurement is triggered at point C shown in the figure. When the RNC receives an RRC
CONNECTION SETUP COMPLETE message from the UE, this counter is measured based on
the physical RNC node if the UE load is shared between physical RNC nodes.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RRC.SuccConnEstab.N WRFD-150211 RNC in Pool Load Sharing

odeShare
1.8.2.3 Delay in Setting Up RRC Connection for UEs in CELL_DCH State Whose
Load Is Shared Between Physical RNC Nodes
Counters
73426018 VS.RRC.ConnEstabTimeM Maximum Delay in Setting

ax.CellDCH.NodeShare Up RRC Connection for UEs
in CELL_DCH State Whose
Physical RNC Nodes
73426019 VS.RRC.ConnEstabTimeM Average Delay in Setting Up

ean.CellDCH.NodeShare RRC Connection for UEs in
CELL_DCH State Whose
Physical RNC Nodes
The following intermediate counters are used for calculating preceding counters based on
specific formulas.
73426180 VS.RRC.ConnEstabTime.C Cumulative Duration of

ellDCH.NodeShare.Cum Setting Up RRC Connection
for UEs in CELL_DCH State
Nodes

BSC6900 UMTS
73426181 VS.RRC.ConnEstabTime.C Number of Samples in

ellDCH.NodeShare.Sample Setting Up RRC Connection
for UEs in CELL_DCH State
Nodes
Description
This counter provides the maximum delay in setting up RRC connection for UEs in CELL_DCH
state whose load is shared between physical RNC nodes.
Measurement point
When the RNC receives an RRC CONNECTION REQUEST message at point A shown in the
figure, the receiving time T1 is recorded. When the RNC receives an RRC CONNECTION
SETUP COMPLETE message at point C shown in the figure, the receiving time T2 is recorded.
Assume that delta T=T2-T1. If the RRC connection is set up on a dedicated channel and the UE
load is shared between physical RNC nodes, delta T is the delay in setting up the RRC connection
for UEs in CELL_DCH state whose load is shared between physical RNC nodes. This counter
is measured based on the physical RNC node.

BSC6900 UMTS
Formula
VS.RRC.ConnEstabTimeMean.CellDCH.NodeShare =
[VS.RRC.ConnEstabTime.CellDCH.NodeShare.Cum]/
[VS.RRC.ConnEstabTime.CellDCH.NodeShare.Sample]
Unit
ms
Related Features
VS.RRC.ConnEstabTimeM WRFD-150211 RNC in Pool Load Sharing

ax.CellDCH.NodeShare

ean.CellDCH.NodeShare
1.8.2.4 Delay in Setting Up RRC Connection for UEs in CELL_FACH State Whose
Load Is Shared Between Physical RNC Nodes
Counters
73426020 VS.RRC.ConnEstabTimeM Maximum Delay in Setting

ax.CellFACH.NodeShare Up RRC Connection for UEs
in CELL_FACH State
Nodes
73426021 VS.RRC.ConnEstabTimeM Average Delay in Setting Up

ean.CellFACH.NodeShare RRC Connection for UEs in
CELL_FACH State Whose
Physical RNC Nodes
specific formulas.

BSC6900 UMTS
73426182 VS.RRC.ConnEstabTime.C Cumulative Duration of

ellFACH.NodeShare.Cum Setting Up RRC Connection
for UEs in CELL_FACH
State Whose Load Is Shared
Nodes
73426183 VS.RRC.ConnEstabTime.C Number of Samples in

ellFACH.NodeShare.Sam- Setting Up RRC Connection
ple for UEs in CELL_FACH
State Whose Load Is Shared
Nodes
Description
This counter provides the maximum delay in setting up RRC connection for UEs in
CELL_FACH state whose load is shared between physical RNC nodes.
Measurement point
When the RNC receives an RRC CONNECTION REQUEST message at point A shown in the
figure, the receiving time T1 is recorded. When the RNC receives an RRC CONNECTION
SETUP COMPLETE message at point C shown in the figure, the receiving time T2 is recorded.
Assume that delta T=T2-T1. If the RRC connection is set up on the forward access channel
(FACH) and the UE load is shared between physical RNC nodes, delta T is the delay in setting
up RRC connection for UEs in CELL_FACH state whose load is shared between physical RNC
nodes. This counter is measured based on the physical RNC node.

BSC6900 UMTS
Formula
VS.RRC.ConnEstabTimeMean.CellFACH.NodeShare =
[VS.RRC.ConnEstabTime.CellFACH.NodeShare.Cum]/
[VS.RRC.ConnEstabTime.CellFACH.NodeShare.Sample]
Unit
ms
Related Features

ax.CellFACH.NodeShare

ean.CellFACH.NodeShare
1.8.2.5 Number of UEs Whose Load Is Shared Between Physical RNC Nodes

BSC6900 UMTS
Counters
73426167 VS.LoadSharedActiveUEs. Number of UEs Whose Load

NodeShare Is Shared Between Physical
RNC Nodes
Description
This counter provides the number of UEs whose load is shared between physical RNC nodes.
Measurement point
The RNC takes samples of UEs which are in CELL_DCH and CELL_FACH states after the
logic RNC shares the load with the overflow RNC every five seconds. Then, the RNC adds the
numbers of UEs in CELL_DCH and CELL_FACH states. At the end of the measurement period,
the RNC divides the accumulated value on every sampling point in the measurement period by
the number of samples to obtain the number of UEs whose load is shared between physical RNC
nodes. NOTE: This counter is measured only on the master physical RNC corresponding to the
logic RNC.
Formula
None
Unit
None
Related Features
VS.LoadSharedActiveUEs. WRFD-150211 RNC in Pool Load Sharing

NodeShare
1.9 Measurement of Operator Performance at the NodeB

Level(PLMN_NodeB)
Overview
Measurement of Operator per NodeB

BSC6900 UMTS
FunctionSubSets
PLMN.NodeB Measurement Related to Operators at the

NodeB Level
1.9.1 Measurement Related to Operators at the NodeB Level

(PLMN.NodeB)
Overview
On the RNC side, measurements are performed at the NodeB level on a per operator basis.
Counters
Description
73425875 VS.NodeB.LDR.UL Number of UEs With V900R015

.BERateDown.PL Decreased BE
MN Service Rate in the
Case of UL Credit
Resource
Congestion for
Operator
73425876 VS.NodeB.ULCred Average NodeB V900R015

itUsed.Mean.PLM Credit Consumption
N of an Operator in the
Uplink
73425879 VS.NodeB.ULCred Maximum NodeB V900R015

itUsed.Max.PLMN Credit Consumption
of an Operator in the
Uplink
73425880 VS.NodeB.DLCred Average NodeB V900R015

itUsed.Mean.PLM Credit Consumption
N of an Operator in the
Downlink
73425883 VS.NodeB.DLCred Maximum NodeB V900R015

itUsed.Max.PLMN Credit Consumption
of an Operator in the
Downlink

BSC6900 UMTS
None
1.9.1.1 Number of UEs With Decreased BE Service Rate in the Case of UL Credit
Resource Congestion for Operator
Counters
73425875 VS.NodeB.LDR.UL.BERate Number of UEs With

Down.PLMN Decreased BE Service Rate
in the Case of UL Credit
Resource Congestion for
Operator
Description
This counter measures the number of UEs with decreased BE service rate when the uplink credit
resources for the operator of the UE are in basic congestion state and load reshuffling (LDR) is
triggered for the UEs of the operator.
Measurement point
When the uplink credit resources for an operator are in basic congestion state, the RNC decreases
the rates of UEs that belong to the operator and are performing the best effort (BE) service. This
counter is increased by one each time the RNC decreases the rate of a UE performing the BE
service.
Formula
None
Unit
None
Related Features
VS.NodeB.LDR.UL.BERate WRFD-150214 MOCN Independent CE

Down.PLMN Resource Allocation
1.9.1.2 Average NodeB Credit Consumption of an Operator in the Uplink

BSC6900 UMTS
Counters
73425876 VS.NodeB.ULCreditUsed. Average NodeB Credit

Mean.PLMN Consumption of an Operator
in the Uplink
Description
This counter measures the average NodeB credit consumption of an operator in the uplink.
Measurement point
The RNC takes samples of the NodeB credit resources occupied by the UEs of an operator in
the uplink every 5 seconds in a measurement period. At the end of the measurement period, the
RNC obtains the value of this counter by dividing the accumulated NodeB credit consumption
by the number of sampling times.
Formula
None
Unit
None
Related Features
VS.NodeB.ULCreditUsed. WRFD-150214 MOCN Independent CE

Mean.PLMN Resource Allocation
1.9.1.3 Maximum NodeB Credit Consumption of an Operator in the Uplink
Counters
73425879 VS.NodeB.ULCreditUsed. Maximum NodeB Credit

Max.PLMN Consumption of an Operator
in the Uplink

BSC6900 UMTS
Description
This counter measures the maximum NodeB credit consumption of an operator in the uplink.
Measurement point
the uplink every 5 seconds in a measurement period. At the end of the measurement period, the
RNC obtains the maximum NodeB credit consumption of the operator in the uplink.
Formula
None
Unit
None
Related Features
VS.NodeB.ULCreditUsed. WRFD-150214 MOCN Independent CE

Max.PLMN Resource Allocation
1.9.1.4 Average NodeB Credit Consumption of an Operator in the Downlink
Counters
73425880 VS.NodeB.DLCreditUsed. Average NodeB Credit

Mean.PLMN Consumption of an Operator
in the Downlink
Description
This counter measures the average NodeB credit consumption of an operator in the downlink.
Measurement point
the downlink every 5 seconds in a measurement period. At the end of the measurement period,
the RNC obtains the value of this counter by dividing the accumulated NodeB credit
consumption by the number of sampling times.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.NodeB.DLCreditUsed. WRFD-150214 MOCN Independent CE

Mean.PLMN Resource Allocation
1.9.1.5 Maximum NodeB Credit Consumption of an Operator in the Downlinke1
Counters
73425883 VS.NodeB.DLCreditUsed. Maximum NodeB Credit

Max.PLMN Consumption of an Operator
in the Downlink
Description
This counter measures the maximum NodeB credit consumption of an operator in the downlink.
Measurement point
the downlink every 5 seconds in a measurement period. At the end of the measurement period,
the RNC obtains the maximum NodeB credit consumption of the operator in the downlink.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.NodeB.DLCreditUsed. WRFD-150214 MOCN Independent CE

Max.PLMN Resource Allocation
1.10 Measurement of RNC Performance(RNC)

Overview
The RNC performance measurement (RNC) is used to measure the overall performance of the
basic signaling procedures of the RNC. It includes only one measurement set, that is, RNC
performance measurement (RNC).
FunctionSubSets
AMR.RNC Measurement related to AMR service
CBS.RNC Measurement related to CBS per RNC
HHO.RNC Hard Handover Measurement per RNC
IRATHO.Cs.RNC Measurement related to CS Inter-RAT

handover per RNC
IRATHO.PS.RNC Measurement related to PS Inter-RAT

handover per RNC
LCS.RNC Measurement related to LCS service
PAGE.RNC Measurement related to Paging per RNC
PDCPGTPU.RNC Measurement related to PDCP
RAB.EstabCS.RNC Measurement of CS RAB assignment setup

per RNC
RAB.EstabPS.RNC Measurement of PS RAB assignment setup

per RNC
RAB.ModCs.RNC Measurement of CS RAB assignment

modification per RNC
RAB.ModPs.RNC Measurement of PS RAB assignment

modification per RNC
RAB.MultiRab.RNC Measurement of multi-RAB service per RNC
RAB.RelAbnormal.RNC Measurement of RAB release per RNC

BSC6900 UMTS
RAB.RelCs.RNC Measurement of CS RAB release per RNC
RAB.RelPs.RNC Measurement of PS RAB release per RNC
RB.RNC Measurement of RB Procedure per RNC
Relocation.Drnc.RNC Measurement of relocation per DRNC
Relocation.Srnc.RNC Measurement of relocation per SRNC
RLC.RNC RLC measurement per RNC
RNC.IMS Measurement related to IMS
RRC.Rel.RNC RRC connection release measurement per

RNC
RRC.Setup.RNC RRC connection setup measurement per

RNC
RRC.STATE RRC state measurement
SHO.RNC Soft Handover Measurement per RNC
SM.RNC Measurement related to Security mode per

RNC
TRAFF.LOAD.RNC Traffic Measurement per RNC
1.10.1 Measurement related to AMR service(AMR.RNC)
Overview
The purpose of the Adaptive Multi-Rate (AMR) technique is to use the minimal power resources
to meet the Quality of Service (QoS) requirements.
There are eight coding rates for the AMR speech service. During light traffic load, higher bit
rates can be used to provide higher speech quality but they consume more resources. During
heavy traffic load, however, lower bit rates can be used to enlarge the capacity but they provide
lower speech quality.
Counters
Description
67202488 VS.RB.AMR.UL. Average Number of Earlier than

5.9.RNC AMR Service Users V900R011
With UL Rate of 5.9
Kbit/s for RNC

BSC6900 UMTS

Description
67202489 VS.RB.AMR.DL. Average Number of Earlier than

With DL Rate of 10.2
Kbit/s for RNC

Kbit/s for RNC

Kbit/s for RNC

Kbit/s for RNC

With DL Rate of 5.9
Kbit/s for RNC

With DL Rate of 7.4
Kbit/s for RNC

Kbit/s for RNC

With UL Rate of 10.2
Kbit/s for RNC

Kbit/s for RNC

Kbit/s for RNC

BSC6900 UMTS

Description

Kbit/s for RNC

With UL Rate of 7.4
Kbit/s for RNC

Kbit/s for RNC

With UL Rate of 6.7
Kbit/s for RNC

With DL Rate of 6.7
Kbit/s for RNC
73422074 VS.AMR.DLSilent. Number of Times V900R012

Num That Silence Is
Detected in
Downlink for AMR
Calls per RNC
73422075 VS.AMR.ULSilent. Number of Times V900R012

Num That Silence Is
Detected in Uplink
for AMR Calls per
RNC
None
1.10.1.1 The Average Number of AMR Users with Different UL and DL Rates

BSC6900 UMTS
Counters
67202491 VS.RB.AMR.DL.4.75.RNC Average Number of AMR

Service Users With DL Rate
of 4.75 Kbit/s for RNC
67202488 VS.RB.AMR.UL.5.9.RNC Average Number of AMR

Service Users With UL Rate












BSC6900 UMTS



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
VS.RB.AMR.DL.4.75.RNC WRFD-010501 Conversational QoS Class
VS.RB.AMR.UL.5.9.RNC WRFD-010501 Conversational QoS Class

BSC6900 UMTS
1.10.1.2 Number of Times That Silence Is Detected in Downlink for AMR Calls per
RNC
Counters
73422074 VS.AMR.DLSilent.Num Number of Times That

Silence Is Detected in
Downlink for AMR Calls per
RNC
Description
This counter provides the number of times that silence is detected in downlink for AMR calls
(narrowband and wideband AMR services) on an RNC.
Measurement point
The RNC detects the speech frames in downlink at the IUUP layer. It checks whether frame loss
or erroneous frame exists in downlink at the IUUP layer every two seconds. If the ratio of lost
frames or erroneous frames exceeds the threshold for three consecutive measurement periods (a
measurement period lasts two seconds), the RNC considers that silence is detected during the
call. Only one silence can be calculated for a call, regardless of the number of times that silence
is detected during the call.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.AMR.DLSilent.Num WRFD-010501 Conversational QoS Class
1.10.1.3 Number of Times That Silence Is Detected in Uplink for AMR Calls per
RNC
Counters
73422075 VS.AMR.ULSilent.Num Number of Times That

Silence Is Detected in Uplink
for AMR Calls per RNC
Description
This counter provides the number of times that silence is detected in uplink for AMR calls
(narrowband and wideband AMR services) on an RNC.
Measurement point
The RNC detects the speech frames in uplink at the IUUP layer. It checks whether frame loss
or erroneous frame exists in uplink at the IUUP layer every two seconds. If the ratio of lost
frames or erroneous frames exceeds the threshold for three consecutive measurement periods (a
measurement period lasts two seconds), the RNC considers that silence is detected in the call.
Only one silence can be calculated for a call, regardless of the number of times that silence is
detected during the call.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.AMR.ULSilent.Num WRFD-010501 Conversational QoS Class
1.10.2 Measurement related to CBS per RNC(CBS.RNC)
Overview
The Cell Broadcast Service (CBS) is a type of point-to-multipoint multicast service similar to
text broadcast on televisions. It provides the function of broadcasting in unacknowledged mode
a certain number of messages in a specified geographical area. The CBS on the Iu-BC interface
is specified by the Service Area Broadcast Protocol (SABP) in 3GPP 25.419. Cell Broadcast
Service measurement is used to measure the basic cell broadcast procedures from the RNC
perspective.
Counters
Description
73426311 VS.ETWS.WriteRe Number of ETWS- V900R015

place related WRITE-
REPLACE
Messages Received
by the RNC
73426312 VS.ETWS.WriteRe Number of ETWS- V900R015

placeFail related WRITE-
REPLACE
FAILURE Messages
Sent by the RNC
None
1.10.2.1 Number of ETWS-related WRITE-REPLACE Messages Received by the

RNC

BSC6900 UMTS
Counters
73426311 VS.ETWS.WriteReplace Number of ETWS-related

WRITE-REPLACE
Messages Received by the
RNC
Description
This counter provides the number of ETWS-related WRITE-REPLACE messages received by
the RNC that carry the Paging ETWS Indicator information element. ETWS is short for
Earthquake and Tsunami Warning System.
Measurement point
The measurement is triggered at point A as shown in the figure when the RNC receives a WRITE-
REPLACE message carrying the Paging ETWS Indicator information element, which indicates
that the CBC initiates an ETWS warning process. CBC is short for cell broadcast center.
Figure 1-176 Message interactions for a successful ETWS warning process
The measurement is triggered at point A as shown in the figure when the RNC receives a WRITE-
REPLACE message carrying the Paging ETWS Indicator information element, which indicates
that the CBC initiates an ETWS warning process.

BSC6900 UMTS
Figure 1-177 Message interactions for a failed ETWS warning process
Formula
None
Unit
None
Related Features
VS.ETWS.WriteReplace WRFD-150234 Earthquake and Tsunami

Warning System (ETWS)
1.10.2.2 Number of ETWS-related WRITE-REPLACE FAILURE Messages Sent by

the RNC
Counters
73426312 VS.ETWS.WriteReplaceFail Number of ETWS-related

WRITE-REPLACE
FAILURE Messages Sent by
the RNC

BSC6900 UMTS
Description
This counter provides the number of WRITE-REPLACE FAILURE messages sent by the RNC
in response to the WRITE-REPLACE message that carry the Paging ETWS Indicator
information element.
Measurement point
The measurement is triggered at point B as shown in the figure when the RNC sends the CBC
a WRITE-REPLACE FAILURE message in response to the WRITE-REPLACE message
carrying the Paging ETWS Indicator information element. The WRITE-REPLACE FAILURE
message indicates a failed ETWS warning process.
Figure 1-178 Message interactions for a failed ETWS warning process
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.ETWS.WriteReplaceFail WRFD-150234 Earthquake and Tsunami

Warning System (ETWS)
1.10.3 Hard Handover Measurement per RNC(HHO.RNC)
Overview
Hard handover is a handover procedure in which all the existing radio links connected to a UE
are released before a new one is set up. That is, communication on the old radio link is interrupted
and then that on the new radio link is established. Therefore, the performance of hard handover
is not as good as that of soft handover. In normal cases, hard handover is triggered by the
coverage, QoS, HCS, and LDR algorithm.
Hard handovers are mainly classified into the intra-frequency handover and inter-frequency
handover. Intra-frequency hard handover: In this mode, the cells that the UE camps on before
and after the handover use the same frequency. The intra-frequency hard handover can be
performed only when soft handover is not available. The intra-frequency hard handover is
performed through blind handover triggered by event 1D or 1F of intra-frequency measurement
events. Inter-frequency hard handover: In this mode, the cells that the UE camps on before and
after the handover use different frequencies. In addition, the inter-frequency hard handover
involves the inter-band hard handover. Inter-frequency hard handover can balance the loads and
achieve seamless connection between different TRXs. Generally, before an inter-frequency hard
handover, the UE requires compressed mode configurations to perform an inter-frequency
measurement according to its capability. The decision of inter-frequency hard handover is
mainly based on inter-frequency measurement reports.
When deciding to perform a hard handover, the RNC sends the PHYSICAL CHANNEL
RECONFIGURATION message, TRANSPORT CHANNEL RECONFIGURATION message,
RADIO BEARER RECONFIGURATION message, RADIO BEARER SETUP message, or
RADIO BEARER RELEASE message to the UE for response. If the RNC receives the
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message, TRANSPORT
CHANNEL RECONFIGURATION COMPLETE message, RADIO BEARER
RECONFIGURATION COMPLETE message, RADIO BEARER SETUP COMPLETE
message, or RADIO BEARER RELEASE COMPLETE message from the UE in the target cell,
the hard handover succeeds. If the RNC receives the PHYSICAL CHANNEL
RECONFIGURATION FAILURE message, TRANSPORT CHANNEL
RECONFIGURATION FAILURE message, RADIO BEARER RECONFIGURATION
FAILURE message, RADIO BEARER SETUP FAILURE message, or RADIO BEARER
RELEASE FAILURE message in the source cell before the hard handover or the RNC does not
receive the response message from the UE before the timer expires, the hard handover fails.
Hard Handover Measurement per RNC measures the number of intra-frequency and inter-
frequency hard handovers separately at the RNC level. Hard handovers with relocation are not
measured.

BSC6900 UMTS
Counters
Description
67192284 VS.HHO.AttIntraF Number of Intra- Earlier than

req.RNC Frequency Hard V900R011
Handover Requests
for RNC
67175428 VS.HHO.AttInterF Number of Inter- Earlier than

req.RNC Frequency Hard V900R011
Handover Requests
for RNC
67175429 VS.HHO.SuccInter Number of Earlier than

Freq.RNC Successful Inter- V900R011
Frequency Hard
Handovers for RNC
67192285 VS.HHO.SuccIntra Number of Earlier than

Freq.RNC Successful Intra- V900R011
Frequency Hard
Handovers for RNC
None
1.10.3.1 Number of Hard Handover Requests
Counters
67192284 VS.HHO.AttIntraFreq.RNC Number of Intra-Frequency

Hard Handover Requests for
RNC
67175428 VS.HHO.AttInterFreq.RNC Number of Inter-Frequency

Hard Handover Requests for
RNC
Description
This counter provides the number of intra-frequency and inter-frequency hard handover requests
initiated by the RNC.

BSC6900 UMTS
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 and 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.
Figure 1-179 Successful hard handover procedure
Formula
None
Unit
None
Related Features
VS.HHO.AttIntraFreq.RNC WRFD-020301 Intra Frequency Hard

Handover

BSC6900 UMTS
VS.HHO.AttInterFreq.RNC WRFD-020302 Inter Frequency Hard

WRFD-020304 Handover Based on
Coverage
Inter Frequency Hard
Handover Based on DL QoS
1.10.3.2 Number of Successful Hard Handovers
Counters
67192285 VS.HHO.SuccIntraFreq.RN Number of Successful Intra-

C Frequency Hard Handovers
for RNC
67175429 VS.HHO.SuccInterFreq.RN Number of Successful Inter-

C Frequency Hard Handovers
for RNC
Description
This counter provides the number of successful intra-frequency and inter-frequencyhard
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 and
inter-frequency hard handover, when the RNC receives the PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message from the UE, the intra-frequency or inter-
frequencyhard handover succeeds. In this case, the RNC measures the counter.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.SuccIntraFreq.RN WRFD-020301 Intra Frequency Hard

C Handover
VS.HHO.SuccInterFreq.RN WRFD-020302 Inter Frequency Hard

C WRFD-020304 Handover Based on
Coverage

BSC6900 UMTS
1.10.4 Measurement related to CS Inter-RAT handover per RNC

(IRATHO.Cs.RNC)
Overview
This function subset measures the CS inter-RAT handover between WCDMA and GSM at the
RNC level. The CS inter-RAT handover is classified into CS outgoing inter-RAT handover and
CS incoming inter-RAT handover.
The measurement of CS outgoing inter-RAT handover measures the handover from WCDMA
to GSM at the RNC level. CS outgoing inter-RAT handover can be divided into two phases: the
handover preparation phase and the handover execution phase. The handover preparation phase
starts from the time when the RNC makes the decision of CS outgoing inter-RAT handover and
sends a RELOCATION REQUIRED message to the CN, to the time when the RNC receives a
RELOCATION COMMAND message from the CN. If the handover preparation phase is
completed successfully, the outgoing inter-RAT handover execution phase is initiated when the
RNC sends a HANDOVER FROM UTRAN COMMAND message to the UE. The outgoing
inter-RAT handover execution phase lasts until the RNC receives an IU RELEASE COMMAND
message from the CN.
The measurement of CS incoming inter-RAT handover measures the handover from GSM to
WCDMA at the RNC level. CS incoming inter-RAT handover can be divided into two phases:
the handover preparation phase and the handover execution phase. The handover preparation
phase starts from the time when the RNC allocates resources for the UE after receiving a
RELOCATION REQUEST message, to the time when the RNC sends a RELOCATION
REQUEST ACKNOWLEDGE message to the CN. After the handover preparation phase ends,
the handover execution phase starts. If the handover from GSM to WCDMA is completed
successfully, the UE sends a HANDOVER TO UTRAN COMPLETE message to the RNC.
Then the RNC sends a RELOCATION COMPLETE message to the CN, and the handover
execution phase is completed successfully.

BSC6900 UMTS
Figure 1-181 Flow chart of CS outgoing inter-RAT handover
Table 1 describes the measurement points shown in Figure1.
Measurement points Description
A VS.IRATHO.AttRelocPrepOutCS.RNC

BSC6900 UMTS
B VS.IRATHO.SuccRelocPrepOutCS.RNC
C VS.IRATHO.AttOutCS.RNC
D VS.IRATHO.SuccOutCS.RNC
Figure 1-182 Flow chart of CS incoming inter-RAT

BSC6900 UMTS
A VS.IRATHO.AttRelocPrepInCS.RNC
B VS.IRATHO.SuccRelocPrepInCS.RNC
C VS.IRATHO.AttInCS.RNC
D VS.IRATHO.SuccInCS.RNC
Counters
Description
67176008 VS.IRATHO.AttIn Number of CS Earlier than

CS.RNC Incoming Inter-RAT V900R011
Handover Attempts
for RNC
67175945 VS.IRATHO.AttO Number of CS Earlier than

utCS.RNC Outgoing Inter-RAT V900R011
Handover Attempts
for RNC
67190398 VS.IRATHO.AttRe Number of CS Earlier than

locPrepOutCS.RN Outgoing Inter-RAT V900R011
C Handover
Preparation
Attempts for RNC
67190311 VS.IRATHO.AttRe Number of CS Earlier than

locPrepInCS.RNC Incoming Inter-RAT V900R011
Handover
Preparation
Attempts for RNC
67190312 VS.IRATHO.Succ Number of Earlier than

RelocPrepInCS.RN Successful V900R011
C Preparations for CS
Incoming Inter-RAT
Handover for RNC

OutCS.RNC Successful CS V900R011
Outgoing Inter-RAT
Handovers for RNC

BSC6900 UMTS

Description

RelocPrepOutCS.R Successful V900R011
NC Preparations for CS
Outgoing Inter-RAT
Handover for RNC
67190314 VS.IRATHO.SuccI Number of Earlier than

nCS.RNC Successful CS V900R011
Incoming Inter-RAT
Handovers for RNC
None
1.10.4.1 Number of CS Outgoing Inter-RAT Handover Preparation Attempts
Counters
67190398 VS.IRATHO.AttRelocPrep Number of CS Outgoing

OutCS.RNC Inter-RAT Handover
Preparation Attempts for
RNC
Description
This counter provides the number of CS outgoing inter-RAT handover preparation attempts in
the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a
RELOCATION REQUIRED message to the CN during the CS outgoing inter-RAT handover.

BSC6900 UMTS
Figure 1-183 Normal CS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
VS.IRATHO.AttRelocPrep WRFD-020303 Inter-RAT Handover Based

OutCS.RNC WRFD-020305 on Coverage
WRFD-020306 Inter-RAT Handover Based

on Service
Inter-RAT Handover Based
on Load
1.10.4.2 Number of Successful Preparations for CS Outgoing Inter-RAT Handover

BSC6900 UMTS
Counters
67190400 VS.IRATHO.SuccRelocPre Number of Successful

pOutCS.RNC Preparations for CS
Outgoing Inter-RAT
Handover for RNC
Description
This counter provides the number of successful preparations for CS outgoing inter-RAT
handover in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives a
RELOCATION COMMAND message from the CN during the CS outgoing inter-RAT
handover.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IRATHO.SuccRelocPre WRFD-020303 Inter-RAT Handover Based

pOutCS.RNC WRFD-020305 on Coverage

on Service
on Load
1.10.4.3 Number of CS Outgoing Inter-RAT Handover Attempts
Counters
67175945 VS.IRATHO.AttOutCS.RN Number of CS Outgoing

C Inter-RAT Handover
Attempts for RNC
Description
This counter provides the number of CS outgoing inter-RAT handover attempts in the RNC.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends a
HANDOVER FROM UTRAN COMMAND message to the UE during the CS outgoing inter-
RAT handover.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.AttOutCS.RN WRFD-020303 Inter-RAT Handover Based

C WRFD-020305 on Coverage

on Service
on Load
1.10.4.4 Number of Successful CS Outgoing Inter-RAT Handovers

BSC6900 UMTS
Counters
67190399 VS.IRATHO.SuccOutCS.R Number of Successful CS

NC Outgoing Inter-RAT
Handovers for RNC
Description
This counter provides the number of successful CS outgoing inter-RAT handovers in the RNC.
Measurement point
The measurement is triggered at point D as shown in the figure, when the RNC receives an IU
RELEASE COMMAND message with the cause value of "Successful Relocation", "Normal
Release", or "Network Optimization" after sending a HANDOVER FROM UTRAN
COMMAND message during the CS outgoing inter-RAT handover. In this case, the outgoing
handover succeeds and this counter is measured.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IRATHO.SuccOutCS.R WRFD-020303 Inter-RAT Handover Based

NC WRFD-020305 on Coverage

on Service
on Load
1.10.4.5 Number of CS Incoming Inter-RAT Handover Preparation Attempts
Counters
67190311 VS.IRATHO.AttRelocPrepI Number of CS Incoming

nCS.RNC Inter-RAT Handover
RNC
Description
This counter provides the number of CS incoming inter-RAT handover preparation attempts in
the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a
RELOCATION REQUEST message from the CN during the CS incoming inter-RAT handover.

BSC6900 UMTS
Figure 1-187 Normal incoming inter-RAT handover
Formula
None
Unit
None
Related Features
VS.IRATHO.AttRelocPrepI WRFD-020303 Inter-RAT Handover Based

nCS.RNC WRFD-020305 on Coverage

on Service
on Load
1.10.4.6 Number of Successful Preparations for CS Incoming Inter-RAT Handover

BSC6900 UMTS
Counters

pInCS.RNC Preparations for CS
Incoming Inter-RAT
Handover for RNC
Description
This counter provides the number of successful preparations for CS incoming inter-RAT
handover in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends a
RELOCATION REQUEST ACKNOWLEDGE message to the CN during the CS incoming
inter-RAT handover.
Formula
None

BSC6900 UMTS
Unit
None
Related Features

pInCS.RNC WRFD-020305 on Coverage

on Service
on Load
1.10.4.7 Number of CS Incoming Inter-RAT Handover Attempts
Counters
67176008 VS.IRATHO.AttInCS.RNC Number of CS Incoming

Inter-RAT Handover
Attempts for RNC
Description
This counter provides the number of CS incoming inter-RAT handover attempts in the RNC.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC receives a
HANDOVER TO UTRAN COMPLETE message from the UE, or when the RNC receives a
RADIO LINK RESTORE INDICATION message from the Node B after sending a
RELOCATION REQUEST ACKNOWLEDGE message to the CN and finishing the preparation
for CS inter-RAT handover during the CS incoming inter-RAT handover. Only one of the two
messages triggers the measurement. There is no repeated measurement.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.AttInCS.RNC WRFD-020303 Inter-RAT Handover Based

WRFD-020305 on Coverage

on Service
on Load
1.10.4.8 Number of Successful CS Incoming Inter-RAT Handovers

BSC6900 UMTS
Counters
67190314 VS.IRATHO.SuccInCS.RN Number of Successful CS

C Incoming Inter-RAT
Handovers for RNC
Description
This counter provides the number of successful CS incoming inter-RAT handovers in the RNC.
Measurement point
The measurement is triggered at point D as shown in the figure, when the RNC sends a
RELOCATION COMPLETE message to the CN during the CS incoming inter-RAT handover.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.IRATHO.SuccInCS.RN WRFD-020303 Inter-RAT Handover Based

C WRFD-020305 on Coverage

on Service
on Load
1.10.5 Measurement related to PS Inter-RAT handover per RNC

(IRATHO.PS.RNC)
Overview
The measurement of PS inter-RAT handover measures the inter-RAT handover between
WCDMA and GPRS from the perspective of the RNC. According to different initiators, PS
outgoing inter-RAT handover can be classified into two types:
PS inter-RAT handover initiated by the UE and PS inter-RAT handover initiated by the RNC.
After an UE sets up PS services in WCDMA, if the UE is in the state of CELL_FACH,
CELL_PCH, or URA_PCH, and the UE initiates a cell reselection from WCDMA to GPRS, the
handover is called PS inter-RAT handover initiated by the UE. If the UE is in the state of
CELL_DCH, and the RNC initiates CELL CHANGE ORDER FROM UTRAN between
WCDMA and GPRS, the handover is called PS inter-RAT handover initiated by the RNC.
Counters
Description
67176098 VS.IRATHO.AttO Number of PS Earlier than

utPSUTRAN.RNC Outgoing Inter-RAT V900R011
Handover Attempts
Initiated by RNC for
RNC

OutPSUTRAN.RN Successful PS V900R011
C Outgoing Inter-RAT
Handovers Initiated
by RNC for RNC

utPSUE.RNC Outgoing Inter-RAT V900R011
Handover Attempts
Initiated by UE for
RNC

BSC6900 UMTS

Description

OutPSUE.RNC Successful PS V900R011
Outgoing Inter-RAT
Handovers Initiated
by UE for RNC
73424356 VS.L2U.AttRelocP Number of LTE-to- V900R014

repInPS.Emerg.RN UMTS PS Handover
C Attempts Caused by
the CSFB of an LTE
Emergency Call for
RNC
73424357 VS.L2U.SuccReloc Number of V900R014

InPS.Emerg.RNC Successful LTE-to-
UMTS PS
Handovers Caused
by the CSFB of an
LTE Emergency Call
for RNC

PrepInPS.Emerg.R Successful LTE-to-
NC UMTS PS Handover
Preparations Caused
by the CSFB of LTE
Emergency Calls for
RNC
None
1.10.5.1 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC
Counters
67176098 VS.IRATHO.AttOutPSUTR Number of PS Outgoing

AN.RNC Inter-RAT Handover
Attempts Initiated by RNC
for RNC

BSC6900 UMTS
Description
This counter provides the number of attempts of PS outgoing inter-RAT handover initiated by
the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the CELL
CHANGE ORDER FROM UTRAN message during the PS outgoing inter-RAT handover.
Figure 1-191 Successful PS outgoing inter-RAT handover initiated by the RNC
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.IRATHO.AttOutPSUTR WRFD-020303 Inter-RAT Handover Based

AN.RNC WRFD-020305 on Coverage

on Service
on Load
1.10.5.2 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by

RNC
Counters
67176100 VS.IRATHO.SuccOutPSUT Number of Successful PS

RAN.RNC Outgoing Inter-RAT
Handovers Initiated by RNC
for RNC
Description
This counter provides the number of successful PS outgoing inter-RAT handovers initiated by
the RNC.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends the IU
RELEASE COMPLETE message after receiving the IU RELEASE COMMAND message with
the cause value of "Successful Relocation", "Normal Release", or "Network Optimization"
during the PS outgoing inter-RAT handover. In this case, the PS outgoing inter-RAT handover
succeeds and the counter is measured.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.SuccOutPSUT WRFD-020303 Inter-RAT Handover Based

RAN.RNC WRFD-020305 on Coverage

on Service
on Load
1.10.5.3 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by UE

BSC6900 UMTS
Counters
67190316 VS.IRATHO.AttOutPSUE. Number of PS Outgoing

RNC Inter-RAT Handover
Attempts Initiated by UE for
RNC
Description
This counter provides the number of attempts of PS outgoing inter-RAT handover initiated by
the UE in the RNC.
Measurement point
When the UE is the state of CELL_FACH, CELL_PCH, or URA_PCH after PS service setup
in WCDMA, the UE can reselect the GPRS network according to the cell reselection criteria.
After entering the GPRS network through the reselection, the UE re-establishes PS services.
During the re-establishment process, through SRNS CONTEXT REQUEST, the 2.5G SGSN
inquires of the RNC about the context information of the PS RAB set up by the UE in the
WCDMA network. The measurement is triggered at point A as shown in the figure, when the
RNC receives the SRNS CONTEXT REQUEST message.
Figure 1-193 PS outgoing inter-RAT handover initiated by the UE

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.AttOutPSUE. WRFD-020303 Inter-RAT Handover Based

RNC WRFD-020305 on Coverage

on Service
on Load
1.10.5.4 Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE
Counters
67176102 VS.IRATHO.SuccOutPSUE Number of Successful PS

.RNC Outgoing Inter-RAT
Handovers Initiated by UE
for RNC
Description
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.SuccOutPSUE WRFD-020303 Inter-RAT Handover Based

.RNC WRFD-020305 on Coverage

on Service
on Load
1.10.5.5 Number of LTE-to-UMTS PS Handover Attempts Caused by the CSFB of

an LTE Emergency Call for RNC

BSC6900 UMTS
Counters
73424356 VS.L2U.AttRelocPrepInPS. Number of LTE-to-UMTS

Emerg.RNC PS Handover Attempts
Caused by the CSFB of an
LTE Emergency Call for
RNC
Description
This counter measures the number of LTE-to-UMTS PS handover in preparation attempts caused
by the CS fallback (CSFB) of an LTE emergency call at the RNC level.
Measurement point
The measurement is triggered at point A shown in figure 1, when the RNC receives a
RELOCATION REQUEST message in which the information element (IE) Source RNC To
Target RNC Transparent Container contains CSFB High Priority. In this case, this counter is
incremented by one in the RNC.
Figure 1-195 Emergency call signaling procedure on the LTE side
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.L2U.AttRelocPrepInPS. WRFD-140102 CS Fallback Guarantee for

Emerg.RNC LTE Emergency Calls
1.10.5.6 Number of Successful LTE-to-UMTS PS Handovers Caused by the CSFB

of an LTE Emergency Call for RNC
Counters
73424357 VS.L2U.SuccRelocInPS.Em Number of Successful LTE-

erg.RNC to-UMTS PS Handovers
Caused by the CSFB of an
LTE Emergency Call for
RNC
Description
This counter measures the number of successful LTE-to-UMTS PS handovers caused by the CS
fallback (CSFB) of an LTE emergency call at the RNC level.
Measurement point
The measurement is triggered at point D shown in figure 1, when the RNC sends the CN a
RELOCATION COMPLETE message in which the corresponding UE information contains
CSFB High Priority. In this case, this counter is incremented by one in the RNC.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.L2U.SuccRelocInPS.Em WRFD-140102 CS Fallback Guarantee for

erg.RNC LTE Emergency Calls
1.10.5.7 Number of Successful LTE-to-UMTS PS Handover Preparations Caused by

the CSFB of LTE Emergency Calls for RNC

BSC6900 UMTS
Counters
73426204 VS.L2U.SuccRelocPrepInP Number of Successful LTE-

S.Emerg.RNC to-UMTS PS Handover
Preparations Caused by the
CSFB of LTE Emergency
Calls for RNC
Description
This counter measures the number of successful preparations for LTE-to-UMTS PS handovers
caused by the CSFB of LTE emergency calls.
Measurement point
This counter measures the number of successful preparations for LTE-to-UMTS PS handovers
caused by the CSFB of LTE emergency calls. The measurement is triggered at point B shown
in figure 1 when the RNC sends the CN a RELOCATION REQUEST ACKNOWLEDGE
message in which the corresponding UE information contains CSFB High Priority. In this case,
this counter is incremented by one on the RNC.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.L2U.SuccRelocPrepInP WRFD-140102 CS Fallback Guarantee for

S.Emerg.RNC LTE Emergency Calls
1.10.6 Measurement related to LCS service(LCS.RNC)
Overview
When the RNC receives a LOCATION REPORTING CONTROL message from the CN, it
utilizes different positioning methods to determine the position of a UE according to the
combinations of various factors.
The UE positioning methods include:
CELLID method, OTDOA method, Assisted GPS (AGPS) method.
Hybrid positioning method, including AGPS, OTDOA and CELLID methods.
After determining the appropriate positioning method, the RNC shall send positioning
measurement request to the NodeB or UE to obtain the measurement results used for the UE
position calculation. These positioning measurements include:
UE-assisted CELLID measurements, UE-assisted OTDOA measurements, UE-assisted AGPS

measurements, UE-based AGPS measurements, RTT measurements.
When the RNC receives a LOCATION RELATED DATA REQUEST message from the CN,
it determines the location-related assistance data according to the requested data type and sends
the data in the ASSISTANCE DATA DELIVERY message to the UE. If the data transmission
is successful, the RNC indicates the successful delivery to the CN in the LOCATION RELATED
DATA RESPONSE message. If the data delivery fails, the RNC indicates failure to the CN in
the LOCATION RELATED DATA FAILURE message.
Location-related assistance data is mainly used for a UE to determine its own position. The types
of assistance data presently supported by the RNC include:
AGPS assistance data, OTDOA assistance data.

BSC6900 UMTS
Counters
Description
67190216 VS.LCS.AsstGps- Number of Times Earlier than

DataTransDel that RNC V900R011
Successfully Sends
GPS Assistance Data
to CN
67181025 VS.LCS.QoSAccur Number of Location Earlier than

Met Reports with V900R011
Position Estimate
Satisfying the
Requested Accuracy
for RNC
67176209 VS.LCS.Agps.Att Number of the Earlier than

positioning attempt V900R011
of the different
location method
(AGPS) for RNC
67176211 VS.LCS.Otdoa.Att Number of OTDOA Earlier than

Based Positioning V900R011
Procedures for RNC
67176214 VS.LCS.AttCsa Number of Requests Earlier than

for Positioning upon V900R011
Change of Service
Area for RNC
67176213 VS.LCS.AttDir Number of Direct Earlier than

Positioning Requests V900R011
for RNC
67176218 VS.LCS.SuccCsa Number of Earlier than

Successful Location V900R011
Report upon Change
of Service Area for
RNC
67176217 VS.LCS.SuccDir Number of Earlier than

Successful Direct V900R011
Location Reports for
RNC
73404075 VS.LCS.CellIdRtt. Number of the V900R012

Att positioning attempt
of the different
location method
(CELLID + RTT) for
RNC

BSC6900 UMTS

Description
73404076 VS.LCS.CellCenter Number of the V900R012

.Att positioning attempt
of the different
location method
(CELLID CENTER)
for RNC
73404077 VS.LCS.CellCenter Number of the V900R012

.Succ successful
positioning of the
different location
method (CELL
CENTER) for RNC
73404078 VS.LCS.CellIdRtt. Number of the V900R012

Succ successful
positioning of the
different location
method (CELLID +
RTT) for RNC
73404079 VS.LCS.Otdoa.Suc Number of the V900R012

c successful
positioning of the
different location
method (OTDOA)
for RNC
73404080 VS.LCS.Agps.Succ Number of the V900R012

successful
positioning of the
different location
method (AGPS) for
RNC
73394012 VS.LCS.SasMode. Number of the V900R012

Att positioning attempt
of using SAS centric
mode for RNC
73394013 VS.LCS.SasMode.S Number of the V900R012

ucc successful
positioning of using
SAS centric mode for
RNC
73423867 VS.LCS.Utdoa.Att Number of U-TDOA V900R013

Positioning Attempts
for RNC

BSC6900 UMTS

Description
73423868 VS.LCS.Utdoa.Suc Number of V900R013

c Successful U-TDOA
Positionings for
RNC
Counter Sub Counter
VS.LCS.SasMode.Att VS.LCS.Utdoa.Att
VS.LCS.SasMode.Succ VS.LCS.Utdoa.Succ
1.10.6.1 Number of Successful Provisions of GPS Assistance Data
Counters
67190216 VS.LCS.AsstGpsDataTrans- Number of Times that RNC

Del Successfully Sends GPS
Assistance Data to CN
Description
This measurement item takes statistics of the number of times that the RNC successfully provides
the Global Positioning System assistance data after receiving the LOCATION RELATED
DATA REQUEST message from the CN.
Measurement point
The measurement is triggered at point A as shown in figure. When the RNC receives from the
CN a LOCATION RELATED DATA REQUEST message in which the IE "Location Related
Data Request Type" is set to "Dedicated Assistance Data for Assisted GPS", the RNC measures
this item when it responds with a LOCATION RELATED DATA RESPONSE message to the
CN.

BSC6900 UMTS
Figure 1-198 Location related data request procedure
Formula
None
Unit
None
Related Features
VS.LCS.AsstGpsDataTrans- WRFD-020803 A-GPS Based LCS

Del
1.10.6.2 Number of Positioning Reports Meeting Accuracy Requirement

BSC6900 UMTS
Counters
67181025 VS.LCS.QoSAccurMet Number of Location Reports

with Position Estimate
Satisfying the Requested
Accuracy for RNC
Description
This measurement item takes statistics of the number of LOCATION REPORT messages from
the RNC to the CN which meet the positioning accuracy requirement.
Measurement point
The measurement is triggered at point A as shown in figure. When the RNC sends the CN a
LOCATION REPORT message, and if the Accuracy Code is smaller than or equal to that in the
LOCATION REPORTING CONTROL message from the CN, it indicates that the LOCATION
REPORT message meets the positioning accuracy requirement. In this case, the RNC measures
this item.
Figure 1-199 Location reporting procedure
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.LCS.QoSAccurMet WRFD-020801 Cell ID + RTT Function

WRFD-020802 Based LCS
WRFD-020803 OTDOA Based LCS

A-GPS Based LCS
1.10.6.3 Number of Positioning Requests with Different Event Types
Counters
67176213 VS.LCS.AttDir Number of Direct

Positioning Requests for
RNC
67176214 VS.LCS.AttCsa Number of Requests for

Positioning upon Change of
Service Area for RNC
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.
VS.LCS.AttDir Event type is Direct
VS.LCS.AttCsa Event type is Change of service area
Measurement point
The measurement is triggered at point A as shown in figure. When the RNC receives a
LOCATION REPORTING CONTROL message containing one of the event types, the RNC
measures these items.

BSC6900 UMTS
Figure 1-200 Location reporting control procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.LCS.AttDir WRFD-020801 Cell ID + RTT Function


A-GPS Based LCS
VS.LCS.AttCsa WRFD-020801 Cell ID + RTT Function


A-GPS Based LCS
1.10.6.4 Number of Successful Positioning Reports with Different Event Types

BSC6900 UMTS
Counters
67176217 VS.LCS.SuccDir Number of Successful Direct

Location Reports for RNC
67176218 VS.LCS.SuccCsa Number of Successful

Location Report upon
Change of Service Area for
RNC
Description
These measurement items take statistics of the number of successful positioning reports sent by
the RNC to the CN. These reports have different event types.
VS.LCS.SuccDir Event type is Direct
VS.LCS.SuccCsa Event type is Change of service area
Measurement point
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.LCS.SuccDir WRFD-020801 Cell ID + RTT Function


A-GPS Based LCS
VS.LCS.SuccCsa WRFD-020801 Cell ID + RTT Function


A-GPS Based LCS
1.10.6.5 Number of the positioning attempt of the different location method for
RNC
Counters
73404076 VS.LCS.CellCenter.Att Number of the positioning

attempt of the different
location method (CELLID
CENTER) for RNC
67176209 VS.LCS.Agps.Att Number of the positioning

location method (AGPS) for
RNC
67176211 VS.LCS.Otdoa.Att Number of OTDOA Based

Positioning Procedures for
RNC

BSC6900 UMTS
73404075 VS.LCS.CellIdRtt.Att Number of the positioning

location method (CELLID +
RTT) for RNC
Description
The measurement items take statistics of the number of the positioning attempt of the different
location method for RNC
VS.LCS.Agps.Att AGPS
VS.LCS.Otdoa.Att OTDOA
Measurement point
LOCATION REPORTING CONTROL message from the CN and determines a positioning
method.
Figure 1-202 Location reporting control procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.LCS.CellCenter.Att WRFD-020801 Cell ID + RTT Function

Based LCS
VS.LCS.Agps.Att WRFD-020803 A-GPS Based LCS
VS.LCS.Otdoa.Att WRFD-020802 OTDOA Based LCS
VS.LCS.CellIdRtt.Att WRFD-020801 Cell ID + RTT Function

Iupc Interface for LCS
service
1.10.6.6 Number of the successful positioning of the different location method for
RNC
Counters
73404077 VS.LCS.CellCenter.Succ Number of the successful

positioning of the different
location method (CELL
CENTER) for RNC
73404078 VS.LCS.CellIdRtt.Succ Number of the successful

location method (CELLID +
RTT) for RNC
73404079 VS.LCS.Otdoa.Succ Number of the successful

location method (OTDOA)
for RNC

BSC6900 UMTS
73404080 VS.LCS.Agps.Succ Number of the successful

location method (AGPS) for
RNC
Description
The measurement items take statistics of the number of the successful positioning of the different
location method for RNC
Measurement point
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

BSC6900 UMTS
Unit
None
Related Features
VS.LCS.CellCenter.Succ WRFD-020801 Cell ID + RTT Function

Based LCS
VS.LCS.CellIdRtt.Succ WRFD-020801 Cell ID + RTT Function

Iupc Interface for LCS
service
VS.LCS.Otdoa.Succ WRFD-020802 OTDOA Based LCS
VS.LCS.Agps.Succ WRFD-020803 A-GPS Based LCS

WRFD-020807 Iupc Interface for LCS
service
1.10.6.7 Number of the times that the location in SAS centric mode is used in the
RNC
Counters
73394012 VS.LCS.SasMode.Att Number of the positioning

attempt of using SAS centric
mode for RNC
73394013 VS.LCS.SasMode.Succ Number of the successful

positioning of using SAS
centric mode for RNC
Description
These counters provide 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

BSC6900 UMTS
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.
Figure 1-204 SAS location procedure
Formula
None
Unit
None
Related Features
VS.LCS.SasMode.Att WRFD-020807 Iupc Interface for LCS

service
VS.LCS.SasMode.Succ WRFD-020807 Iupc Interface for LCS

service
1.10.6.8 Number of U-TDOA Positioning Attempts

BSC6900 UMTS
Counters
73423867 VS.LCS.Utdoa.Att Number of U-TDOA

Positioning Attempts for
RNC
Description
This counter provides the number of Uplink-Time Difference Of Arrival (U-TDOA) positioning
attempts under an RNC.
Measurement point
In Stand-Alone SMLC (SAS) centric mode, the measurement is triggered at point B as shown
in the figure. This counter is incremented by one when the RNC receives a PCAP POSITION
ACTIVATION REQUEST message that designates the U-TDOA positioning method from the
SAS.
Note: If the SAS retransmits the PCAP POSITION ACTIVATION REQUEST message, only
one is counted.
Figure 1-205 U-TDOA positioning procedure in SAS centric mode
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.LCS.Utdoa.Att WRFD-020802 OTDOA Based LCS
1.10.6.9 Number of Successful U-TDOA Positionings
Counters
73423868 VS.LCS.Utdoa.Succ Number of Successful U-

TDOA Positionings for RNC
Description
This counter provides the number of successful U-TDOA positionings under an RNC.
Measurement point
In SAS centric mode, the measurement is triggered at point D as shown in the figure. This counter
is incremented by one when the RNC receives a PCAP POSITION INITIATION RESPONSE
message and the following conditions are both met:
1. The RNC receives a PCAP POSITION ACTIVATION REQUEST message that designates
the U-TDOA positioning method from the SAS at a point of time between point A when a PCAP
POSITION INITIATION REQUEST message is received and point D when a PCAP POSITION
INITIATION RESPONSE message is received.
2. At point C, the RNC sends the SAS a PCAP POSITION ACTIVATION RESPONSE message
that contains UE's U-TDOA positioning information.

BSC6900 UMTS
Figure 1-206 U-TDOA positioning procedure in SAS centric mode
Formula
None
Unit
None
Related Features
VS.LCS.Utdoa.Succ WRFD-020802 OTDOA Based LCS
1.10.7 Measurement related to Paging per RNC(PAGE.RNC)
Overview
To page an UE, the CN sends a PAGING message to the RNC. Then, the RNC sends a PAGING
TYPE 1 message or a PAGING TYPE 2 message to the UE according to the status of the UE.
If the paged UE is in idle mode, CELL_PCH state or URA_PCH state, the RNC shall send a
PAGING TYPE 1 message on the PCH to the cell in the paged area. If the UE is in CELL_PCH
state and EPCH is supported by the network and the UE, the RNC sends a PAGING TYPE 2
message to the cells in the paging area. If the UE is in CELL_FACH or CELL_DCH state, the
RNC shall send a PAGING TYPE 2 message to the UE on the DCCH.

BSC6900 UMTS
In addition, the UTRAN can send a PAGING TYPE 1 message to an UE in idle mode,
CELL_PCH state or URA_PCH state for system information update. Also, the UTRAN can
send a PAGING TYPE 1 message to an UE in CELL_PCH or URA_PCH state for UE state
transition to support data transmission.
If the paged UE is in idle mode, it will send a RRC CONNECTION REQUEST message to the
RNC after receiving a PAGING TYPE 1 message. If the UE is in CELL_PCH or URA_PCH
state, it will send a CELL UPDATE message with the cell update cause of "paging response" to
the RNC after it receives a PAGING TYPE 1 message.
For more information, refer to 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Description
67174402 VS.RANAP.Paging Number of CN Earlier than

.Att.IdleUE Pagings to Idle UE V900R011
for RNC
67174403 VS.RANAP.Paging Number of Earlier than

.Succ.IdleUE Successful CN V900R011
Pagings to Idle UE
for RNC
67174405 VS.UTRAN.Paging Number of UTRAN- Earlier than

1.Att Originated PAGING V900R011
TYPE 1 Messages
for RNC
67174404 VS.UTRAN.Paging Number of PAGING Earlier than

2.Att TYPE 2 Messages V900R011
for RNC
67174406 VS.UTRAN.Succ- Number of Earlier than

Page1 Successful V900R011
Responses to
PAGING TYPE 1
Messages for RNC
67193711 VS.RANAP.CsPagi Number of CN Earlier than

ng.Att Paging Requests of V900R011
CS Domain for RNC
67193712 VS.RANAP.PsPagi Number of CN Earlier than

ng.Att Paging Requests of V900R011
PS Domain for RNC
67193713 VS.RANAP.CsPagi Number of Earlier than

ng.Loss Unsuccessful CN V900R011
Paging Requests of
CS Domain for RNC

BSC6900 UMTS

Description
67192714 VS.RANAP.PsPagi Number of Earlier than

ng.Loss Unsuccessful CN V900R011
Paging Requests of
PS Domain for RNC
73394071 VS.Paging1.Succ.P Number of V900R012

TT.RNC Successful PAGING
TYPE 1 Message
Responses from PTT
UEs Received by
RNC
73394072 VS.Paging1.Att.PT Number of RNC- V900R012

T.RNC Originated PAGING
TYPE 1 Messages to
PTT UEs
None
1.10.7.1 Number of Paging Messages to UE
Counters
67174402 VS.RANAP.Paging.Att.Idle Number of CN Pagings to

UE Idle UE for RNC
Description
This measurement counter takes statistics of the number of PAGING TYPE 1 messages from
the RNC to the UEs in idle mode after it receives the PAGING messages from the CN.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives a
PAGING message from the CN, and if the paged UE is in idle mode, the RNC sends a PAGING
TYPE 1 message to the cell in the paged area. In this case, the RNC measures this counter.

BSC6900 UMTS
Figure 1-207 Number of Paging Messages to UEs in Idle Mode
Formula
None
Unit
None
Related Features
VS.RANAP.Paging.Att.Idle WRFD-010301 Paging UE in Idle,

UE CELL_PCH, URA_PCH
State (Type 1)
1.10.7.2 Number of Successful Paging Messages to UE
Counters
67174403 VS.RANAP.Paging.Succ.Idl Number of Successful CN

eUE Pagings to Idle UE for RNC

BSC6900 UMTS
Description
This measurement counter takes statistics of the number of RRC CONNECTION REQUEST
messages from the UEs to the RNC that has sent a PAGING TYPE 1 messages to page the UEs
in idle mode.
Measurement point
The measurement is triggered at point C as shown in in the figure. The RNC measures this
counter when it receives a RRC CONNECTION REQUEST message from an UE with one of
the following causes: "Terminating Conversational Call", "Terminating Streaming Call",
"Terminating Interactive Call", "Terminating Background Call", "Terminating High Priority
Signaling", "Terminating Low Priority Signaling, "Terminating cause unknown".
Figure 1-208 Number of Paging Messages to UEs in Idle Mode
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RANAP.Paging.Succ.Idl WRFD-010301 Paging UE in Idle,

eUE CELL_PCH, URA_PCH
State (Type 1)
1.10.7.3 Number of RNC-Originated PAGING TYPE 1 Messages
Counters
67174405 VS.UTRAN.Paging1.Att Number of UTRAN-

Originated PAGING TYPE 1
Messages for RNC
Description
This measurement counter takes statistics of the number of PAGING TYPE 1 messages
originated by the RNC for triggering the state transition of an UE in CELL_PCH or URA_PCH
state. Statistics taken by this item excludes the number of PAGING TYPE 1 messages that the
RNC originates for the modification of system information.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC measures this counter
when it initiates and sends a PAGING TYPE 1 message to an UE in CELL_PCH or URA_PCH
state.

BSC6900 UMTS
Figure 1-209 Response of an UE in CELL_PCH or URA_PCH state to the PAGING TYPE 1

message
Formula
None
Unit
None
Related Features
VS.UTRAN.Paging1.Att WRFD-010301 Paging UE in Idle,

CELL_PCH, URA_PCH
State (Type 1)
1.10.7.4 Number of PAGING TYPE 2 Messages

BSC6900 UMTS
Counters
67174404 VS.UTRAN.Paging2.Att Number of PAGING TYPE 2

Messages for RNC
Description
This measurement counter takes statistics of the number of PAGING TYPE 2 messages from
the RNC to the UE in CELL_FACH or CELL_DCH state. When the RNC receives PAGING
messages from the CN, it sends a PAGING TYPE 2 message to the UE if the paged UE is in
CELL_FACH or CELL_DCH state.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives
PAGING messages from the CN, it sends a PAGING TYPE 2 message to the UE in
CELL_FACH or CELL_DCH state after receiving a PAGING message from the CN. In this
case, the RNC measures this counter.
Figure 1-210 Procedure of CN paging UE in CELL_FACH or CELL_DCH state
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.UTRAN.Paging2.Att WRFD-010302 Paging UE in CELL_FACH,

1.10.7.5 Number of Successful Responses to PAGING TYPE 1 Messages
Counters
67174406 VS.UTRAN.SuccPage1 Number of Successful

Responses to PAGING
TYPE 1 Messages for RNC
Description
This measurement counter takes statistics of the number of CELL UPDATE messages from the
UEs to the RNC. These messages are taken as successful responses to the PAGING TYPE 1
messages sent by the RNC to the UEs in CELL_PCH or URA_PCH state. After receiving the
PAGING TYPE 1 messages, the UEs in CELL_PCH or URA_PCH state send CELL UPDATE
messages with the cause of "paging response" to the RNC. A PAGING TYPE 1 message may
be sent to an UE in CELL_PCH or URA_PCH state for the following reasons: The RNC receives
a PAGING message from the CN. The UTRAN enables the UE to update system information.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives a CELL
UPDATE message with the cause of "paging response", it measures this counter.

BSC6900 UMTS
Figure 1-211 Response of an UE in CELL_PCH or URA_PCH state to the PAGING TYPE 1

message
Formula
None
Unit
None
Related Features
VS.UTRAN.SuccPage1 WRFD-010301 Paging UE in Idle,

CELL_PCH, URA_PCH
State (Type 1)
1.10.7.6 Number of CS-Oriented PAGING Messages from the CN

BSC6900 UMTS
Counters
67193711 VS.RANAP.CsPaging.Att Number of CN Paging

Requests of CS Domain for
RNC
Description
This measurement counter takes statistics of the number of CS-oriented PAGING messages from
the CN to the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a
PAGING message from the CN, the measurement of this counter is triggered if the CN Domain
Indicator IE in the message indicates the CS domain.
Figure 1-212 Procedure of paging from the CN
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RANAP.CsPaging.Att WRFD-010301 Paging UE in Idle,

State (Type 1)
1.10.7.7 Number of PS-Oriented PAGING Messages from the CN
Counters
67193712 VS.RANAP.PsPaging.Att Number of CN Paging

Requests of PS Domain for
RNC
Description
This measurement counter takes statistics of the number of PS-oriented PAGING messages from
the CN to the RNC.
Measurement point
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RANAP.PsPaging.Att WRFD-010301 Paging UE in Idle,

State (Type 1)
1.10.7.8 Number of Failures to Respond to CS-Oriented PAGING Messages from

the CN

BSC6900 UMTS
Counters
67193713 VS.RANAP.CsPaging.Loss Number of Unsuccessful CN

Paging Requests of CS
Domain for RNC
Description
This measurement counter takes statistics of the number of failures to respond to CS-oriented
PAGING messages from the CN to the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives from
the CN a PAGING message in which the CN Domain Indicator IE indicates the CS domain, the
measurement of this counter is triggered if the RNC does not send a Paging type 1 or Paging
type 2 message. The reason why the RNC does not send a Paging type 1 or Paging type 2 message
might be Iu flow control, or high CPU usage. If the RNC does not respond to a paging message
that is consecutively retransmitted, the RNC counts it only once.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.RANAP.CsPaging.Loss WRFD-010301 Paging UE in Idle,

State (Type 1)
1.10.7.9 Number of Failures to Respond to PS-Oriented PAGING Messages from

the CN
Counters
67192714 VS.RANAP.PsPaging.Loss Number of Unsuccessful CN

Paging Requests of PS
Domain for RNC
Description
This measurement item takes statistics of the number of failures to respond to PS-oriented
PAGING messages from the CN to the RNC.
Measurement point
the 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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RANAP.PsPaging.Loss WRFD-010301 Paging UE in Idle,

State (Type 1)
1.10.7.10 Number of CELL UPDATE Messages from PTT UEs as Paging Response
Received by RNC

BSC6900 UMTS
Counters
73394071 VS.Paging1.Succ.PTT.RNC Number of Successful

PAGING TYPE 1 Message
Responses from PTT UEs
Received by RNC
Description
This counter provides the number of times that the RNC receives from the UE a CELL UPDATE
message with a cause value of "paging response" after the RNC sends to the PTT UEs in
CELL_PCH or URA_PCH state a PAGING TYPE 1 message.
Measurement point
This measurement is triggered at point B as shown in the figure, when the RNC receives from
the PTT UE a CELL UPDATE message with a cause value of "paging response".
Figure 1-216 Procedure for UEs in CELL_PCH or URA_PCH state to respond to the PAGING
TYPE 1 message
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.Paging1.Succ.PTT.RNC WRFD-010301 Paging UE in Idle,

State (Type 1)
Push to Talk
1.10.7.11 Number of RNC-Originated PAGING TYPE 1 Messages to PTT UEs in

CELL_PCH or URA_PCH state
Counters
73394072 VS.Paging1.Att.PTT.RNC Number of RNC-Originated

PAGING TYPE 1 Messages
to PTT UEs
Description
This counter provides the number of PAGING TYPE 1 messages sent automatically by the RNC
to PTT UEs.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC automatically
sends a PAGING TYPE 1 message to the PTT UEs in CELL_PCH or URA_PCH state. The
PAGING TYPE 1 message sent by the RNC due to system information change are not measured
in this counter.

BSC6900 UMTS
Figure 1-217 Procedure for UEs in CELL_PCH or URA_PCH state to respond to the PAGING
TYPE 1 message
Formula
None
Unit
None
Related Features
VS.Paging1.Att.PTT.RNC WRFD-010301 Paging UE in Idle,

State (Type 1)
Push to Talk
1.10.8 Measurement related to PDCP(PDCPGTPU.RNC)
Overview
The RNC-based PDCP measurement focuses on the Robust Header Compression (ROHC) of
PDCP headers.

BSC6900 UMTS
Counters
Description
67204484 VS.PDCP.DL.ROH Compression Rate of Earlier than

C.HdrCompressRa DL Packet Header V900R011
tio Through ROHC
Compression
67204485 VS.PDCP.DL.ROH Compression Rate of Earlier than

C.PktCompressRa- DL Packets After V900R011
tio ROHC Compression
67204486 VS.PDCP.UL.ROH Decompression Earlier than

C.FailDecompRa- Failure Rate of UL V900R011
tio Packets Through
ROHC Algorithm
None
1.10.8.1 Compression Ratio of DL Packet Headers Under ROHC
Counters
67204484 VS.PDCP.DL.ROHC.HdrC Compression Rate of DL

ompressRatio Packet Header Through
ROHC Compression
Description
This measurement item takes statistics of the ratio of the packet header size after all downlink
PS packets undergo Robust Header Compression (ROHC) to the header size before the ROHC
during a measurement period in the RNC. This measurement item is valid when the ROHC
algorithm is configured.
Measurement point
When a PDCP entity receives a downlink packet, it judges whether the packet is configured with
ROHC. If the packet is not configured with ROHC, the PDCP entity does not report this
measurement item. If the packet is configured with ROHC, the PDCP entity goes through the
sub-headers of the packet to obtain the chain size before adding the size to the item DL Packet
Header Size before Compression. After the compression, the PDCP entity then adds the new
sub-header chain size to the item DL Packet Header Size after Compression.

BSC6900 UMTS
At the end of the measurement period, the PDCP entity reports the two item values to the
performance function subset and resets the two items. Then the performance function subset
calculates the compression ratio of the downlink packet headers under ROHC based on the
reported values of DL Packet Header Size before Compression and DL Packet Header Size after
Compression.
Formula
None
Unit
%
Related Features
VS.PDCP.DL.ROHC.HdrC WRFD-010617 VoIP over HSPA/HSPA+

ompressRatio
1.10.8.2 Compression Ratio of DL Packets Under ROHC
Counters
67204485 VS.PDCP.DL.ROHC.PktCo Compression Rate of DL

mpressRatio Packets After ROHC
Compression
Description
This measurement item takes statistics of the ratio of the packet size after all downlink PS packets
undergo Robust Header Compression (ROHC) to the packet size before the ROHC during a
measurement period in the RNC. This measurement item is valid when the ROHC algorithm is
configured.
Measurement point
When a PDCP entity receives a downlink packet, it judges whether the packet is configured with
ROHC. If the packet is not configured with ROHC, the PDCP entity does not report this
measurement item. If the packet is configured with ROHC, the number of compressed downlink
packets increases by one. Meanwhile, the PDCP entity adds the initial packet size to the item
DL Packet Size before Compression. After the compression, it adds the packet size to the item
DL Packet Size after Compression. At the end of the measurement period, the PDCP entity
reports the two item values to the performance function subset and resets the two items. Then
the performance function subset calculates the compression ratio of the downlink packets under

BSC6900 UMTS
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
VS.PDCP.DL.ROHC.PktCo WRFD-010617 VoIP over HSPA/HSPA+

mpressRatio
1.10.8.3 Ratio of UL ROHC Decompression Failures to Total UL ROHC

Decompression Operations
Counters
67204486 VS.PDCP.UL.ROHC.Fail- Decompression Failure Rate

DecompRatio of UL Packets Through
ROHC Algorithm
Description
This measurement item takes statistics of the ratio of the number of UL PS packets failing to be
decompressed by Robust Header Compression (ROHC) to the total number of UL packets
undergoing ROHC decompression during a measurement period in the RNC. This measurement
item is valid when the ROHC algorithm is configured.
Measurement point
When a PDCP entity receives an uplink packet, it judges whether the packet is configured with
ROHC. If the packet is configured with ROHC, the value of the item Number of Uplink Packets
to Be Decompressed increases by 1. Then, if the decompression fails, the value of the item
Number of UL Packets Failing to Be Decompressed increases by 1. At the end of the
measurement period, the PDCP entity reports the two item values to the performance function
subset and resets the two items. Then, the performance function subset calculates the ratio of
Number of Uplink Packets Failing to Be Decompressed to Number of UL Packets to Be
Decompressed.

BSC6900 UMTS
Formula
None
Unit
%
Related Features
VS.PDCP.UL.ROHC.Fail- WRFD-010617 VoIP over HSPA/HSPA+

DecompRatio
1.10.9 Measurement of CS RAB assignment setup per RNC

(RAB.EstabCS.RNC)
Overview
The CN in CS domain initiates the radio access bearer setup procedure by sending a RAB
ASSIGNMENT REQUEST message to the RNC.
After receiving the RAB ASSIGNMENT REQUEST message, the RNC selects an appropriate
cell, allocates resources, and performs admission control based on the information in the message
(such as service type, QoS, and priority), the traffic load of the system, and the networking
strategy (such as DRD). The requirements of high-priority users are met preferentially(That is,
when the resources are insufficient and the UEs with low-priority cannot set up the RAB, the
RNC sends to the CN a RAB ASSGNMENT RESPONSE message if the queuing algorithm is
enabled, indicating that the RAB is in the queue to wait for resources).If the admission of the
RAB succeeds, the RNC starts the Iu transport connection setup procedure, the Iub radio bearer
setup procedure, and the Uu radio bearer setup procedure. At last, the RNC sends to the CN a
RAB ASSNMENT RESPONSE, indicating whether the RAB setup is successful.
For details, refer to 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Description
67174721 VS.RAB.AttEstab Number of CS Earlier than

CS.Conv.RNC Conversational RAB V900R011
Establishment
Attempts for RNC

BSC6900 UMTS

Description

CS.Str.RNC Streaming RAB V900R011
Establishment
Attempts for RNC
67199791 VS.RAB.Num.CS. Mean Number of CS Earlier than

Mean RABs for RNC V900R011
67196235 VS.RAB.AttEstab Number of Earlier than

CS.VPLimit.RNC Attempted 64kbit/s V900R011
CS RAB
Establishments in a
Cell Where 64kbit/s
CS Service is
Forbidden for RNC

CS.Conv.RNC Successful RAB
Establishments for
CS Conversational
Services for RNC

CS.Str.RNC Successful CS
Streaming RAB
Establishments for
RNC
None
1.10.9.1 Number of CS RABs Requested to Establish
Counters
67174721 VS.RAB.AttEstabCS.Conv. Number of CS

RNC Conversational RAB
Establishment Attempts for
RNC
67174722 VS.RAB.AttEstabCS.Str.R Number of CS Streaming

NC RAB Establishment
Attempts for RNC

BSC6900 UMTS
Description
This counter provides the number of CS RABs establishment requests in the RNC according to
different services.
Measurement point
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
VS.RAB.AttEstabCS.Conv. WRFD-010501 Conversational QoS Class

RNC

BSC6900 UMTS
VS.RAB.AttEstabCS.Str.R WRFD-010502 Streaming QoS Class

NC
1.10.9.2 Mean Number of CS RABs
Counters
67199791 VS.RAB.Num.CS.Mean Mean Number of CS RABs

for RNC
Description
This counter provides the average number of CS RABs in the RNC within a measurement period.
Measurement point
The RNC periodically samples (sampling periodicity is 5 seconds) the number of CS RABs. At
the end of the measurement period, the RNC divides the total number of CS RABs by the number
of samples to obtain the average number of CS RABs.
Formula
None
Unit
None
Related Features
VS.RAB.Num.CS.Mean WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.10.9.3 Number of CS VP RABs requested to establish in cell where VP is

forbidden

BSC6900 UMTS
Counters
67196235 VS.RAB.AttEstabCS.VPLi Number of Attempted

mit.RNC 64kbit/s CS RAB
Establishments in a Cell
Where 64kbit/s CS Service is
Forbidden for RNC
Description
This counter provides the number of RAB setup requests for VP services when the VP call is
limited.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RAB
ASSIGNMENT REQUEST message from the CN in the CS domain, it measures the counter if
the RAB is for the VP service and it is limited for the best cell.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.RAB.AttEstabCS.VPLi WRFD-020130 Videophone Service

mit.RNC Restriction
1.10.9.4 Number of Successful RAB Establishments for CS Services
Counters
73394064 VS.RAB.SuccEstabCS.Con Number of Successful RAB

v.RNC Establishments for CS
Conversational Services for
RNC
73394065 VS.RAB.SuccEstabCS.Str.R Number of Successful CS

NC Streaming RAB
Establishments for RNC
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SuccEstabCS.Con WRFD-010501 Conversational QoS Class

v.RNC
VS.RAB.SuccEstabCS.Str.R WRFD-010502 Streaming QoS Class

NC
1.10.10 Measurement of PS RAB assignment setup per RNC

(RAB.EstabPS.RNC)
Overview
The CN in PS domain initiates the radio access bearer setup procedure by sending a RAB

BSC6900 UMTS
enabled, indicating that the RAB is in the queue to wait for resources). If the admission of the
For details, refer to 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Description
67174785 VS.RAB.AttEstabP Number of PS Earlier than

S.Bkg.RNC Background RAB V900R011
Establishment
Attempts for RNC

S.Conv.RNC Conversational RAB V900R011
Establishment
Attempts for RNC

S.Int.RNC Interactive RAB V900R011
Establishment
Attempts for RNC

S.Str.RNC Streaming RAB V900R011
Establishment
Attempts for RNC
67174812 VS.RAB.EstabPS. Maximum Duration Earlier than

CellFACH.MaxTi of PS RAB V900R011
me Establishments
Mapped on CCH for
RNC
67199679 VS.RAB.EstabPS. Mean Duration of PS Earlier than

CellFACH.Mean- RAB Establishments V900R011
Time Mapped on CCH for
RNC

BSC6900 UMTS

Description
67174809 VS.RAB.EstabPS. Maximum Duration Earlier than

CellDCH.MaxTime of PS RAB V900R011
Establishments
Mapped on DCH for
RNC
67199427 VS.RAB.EstabPS. Mean Duration of PS Earlier than

CellDCH.MeanTim RAB Establishments V900R011
e Mapped on DCH for
RNC
67174827 VS.RAB.AttEstPS Number of PS Earlier than

Bkg0.32.RNC Background RAB V900R011
Establishment
Attempts for RNC
(Max DL Bit Rate in
[0,32]kbit/s)

S.Bkg. Background RAB V900R011
144.384.RNC Establishment
Attempts for RNC
(Max DL Bit Rate in
(144,384]kbit/s)

S.Bkg.32.64.RNC Background RAB V900R011
Establishment
Attempts for RNC
(Max DL Bit Rate in
(32,64]kbit/s)

S.Bkg.64.144.RNC Background RAB V900R011
Establishment
Attempts for RNC
(Max DL Bit Rate in
(64,144]kbit/s)

S.Bkg.Mor384.RN Background RAB V900R011
C Establishment
Attempts for RNC
(Max DL Bit Rate
More Than 384kbit/
s)

BSC6900 UMTS

Description

S.Conv.0.32.RNC Conversational RAB V900R011
Establishment
Attempts for RNC
(Max DL Bit Rate in
[0,32]kbit/s)

S.Conv.Mor32.RN Conversational RAB V900R011
C Establishment
Attempts for RNC
(Max DL Bit Rate
More Than 32kbit/s)

S.Int.0.32.RNC Interactive RAB V900R011
Establishment
Attempts for RNC
(Max DL Bit Rate in
[0,32]kbit/s)

Establishment
Attempts for RNC
(Max DL Bit Rate in
(144,384]kbit/s)

Establishment
Attempts for RNC
(Max DL Bit Rate in
(32,64]kbit/s)

Establishment
Attempts for RNC
(Max DL Bit Rate in
(64,144]kbit/s)

S.Int.Mor384.RNC Interactive RAB V900R011
Establishment
Attempts for RNC
(Max DL Bit Rate
More Than 384kbit/
s)

BSC6900 UMTS

Description

S.Str.0.32.RNC Streaming RAB V900R011
Establishment
Attempts for RNC
(Max DL Bit Rate in
[0,32]kbit/s)

Establishment
Attempts for RNC
(Max DL Bit Rate in
(32,64]kbit/s)

Establishment
Attempts for RNC
(Max DL Bit Rate in
(144,384]kbit/s)

Establishment
Attempts for RNC
(Max DL Bit Rate in
(64,144]kbit/s)

S.Str.Mor384 Streaming RAB V900R011
Establishment
Attempts for RNC
(Max DL Bit Rate
More Than 384kbit/
s)
67174844 VS.RAB.SuccEstab Number of Earlier than

PS.Bkg.0.32.RNC Successful PS V900R011
Background RAB
Establishments for
RNC (Max DL Bit
Rate in [0,32]kbit/s)

PS.Bkg. Successful PS V900R011
144.384.RNC Background RAB
Establishments for
RNC (Max DL Bit
Rate in (144,384]
kbit/s)

BSC6900 UMTS

Description

PS.Bkg.32.64.RNC Successful PS V900R011
Background RAB
Establishments for
RNC (Max DL Bit
Rate in (32,64]kbit/s)

PS.Bkg. Successful PS V900R011
Establishments for
RNC (Max DL Bit
Rate in (64,144]kbit/
s)

PS.Conv.0.32.RNC Successful PS V900R011
Conversational RAB
Establishments for
RNC (Max DL Bit

PS.Conv.Mor32.R Successful PS V900R011
NC Conversational RAB
Establishments for
RNC (Max DL Bit
Rate More Than
32kbit/s)

PS.Str.Mor384.RN Successful PS V900R011
C Streaming RAB
Establishments for
RNC (Max DL Bit
Rate More Than
384kbit/s)

PS.Int.0.32.RNC Successful PS V900R011
Interactive RAB
Establishments for
RNC (Max DL Bit

BSC6900 UMTS

Description

PS.Int. Successful PS V900R011
144.384.RNC Interactive RAB
Establishments for
RNC (Max DL Bit
Rate in (144,384]
kbit/s)

Interactive RAB
Establishments for
RNC (Max DL Bit

Interactive RAB
Establishments for
RNC (Max DL Bit
s)

PS.Int.Mor384.RN Successful PS V900R011
C Interactive RAB
Establishments for
RNC (Max DL Bit
Rate More Than
384kbit/s)

PS.Bkg.Mor384.R Successful PS V900R011
NC Background RAB
Establishments for
RNC (Max DL Bit
Rate More Than
384kbit/s)

.PS.Str.0.32.RNC Successful PS V900R011
Streaming RAB
Establishments for
RNC (Max DL Bit

BSC6900 UMTS

Description

.PS.Str. Successful PS V900R011
144.384.RNC Streaming RAB
Establishments for
RNC (Max DL Bit
Rate in (144,384]
kbit/s)

Streaming RAB
Establishments for
RNC (Max DL Bit

Streaming RAB
Establishments for
RNC (Max DL Bit
s)
67199790 VS.RAB.Num.PS. Mean Number of PS Earlier than

Mean RABs for RNC V900R011

.PS.0kbps.RNC Established V900R011
Successfully with 0
kbit/s for RNC

PS.Bkg.RNC Successful RAB
Establishments for
PS Background
Services for RNC

PS.Str.RNC Successful RAB
Establishments for
PS Streaming
Services for RNC

PS.Conv.RNC Successful RAB
Establishments for
PS Conversational
Services for RNC

BSC6900 UMTS

Description

PS.Int.RNC Successful RAB
Establishments for
PS Interactive
Services for RNC
Counter Sub Counter
VS.RAB.AttEstabPS.Bkg.RNC VS.RAB.AttEstPSBkg0.32.RNC
VS.RAB.AttEstabPS.Bkg.144.384.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.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.Mor384
VS.RAB.SuccEstabPS.Bkg.RNC VS.RAB.SuccEstabPS.Bkg.0.32.RNC
VS.RAB.SuccEstabPS.Bkg.144.384.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

BSC6900 UMTS
Counter Sub Counter
VS.RAB.SuccEstabPS.Str.RNC VS.RAB.SuccEstabPS.Str.Mor384.RNC
VS.RAB.SuccEstab.PS.Str.0.32.RNC
VS.RAB.SuccEstabPS.Int.RNC VS.RAB.SuccEstabPS.Int.0.32.RNC
VS.RAB.SuccEstabPS.Int.144.384.RNC
VS.RAB.SuccEstabPS.Int.Mor384.RNC
1.10.10.1 Counters Related to the Number of PS RAB Setup Requests for Different
Services
Counters
67174788 VS.RAB.AttEstabPS.Conv. Number of PS

RNC Conversational RAB
RNC
67174785 VS.RAB.AttEstabPS.Bkg.R Number of PS Background

NC RAB Establishment
Attempts for RNC
67174787 VS.RAB.AttEstabPS.Int.RN Number of PS Interactive

C RAB Establishment
Attempts for RNC
67174786 VS.RAB.AttEstabPS.Str.RN Number of PS Streaming

C RAB Establishment
Attempts for RNC
Description
These measurement items take statistics of the number of PS RABs requested to establish in the
RNC according to different types of services.

BSC6900 UMTS
Measurement point
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
VS.RAB.AttEstabPS.Conv. WRFD-010501 Conversational QoS Class

RNC
VS.RAB.AttEstabPS.Bkg.R WRFD-010504 Background QoS Class

NC
VS.RAB.AttEstabPS.Int.RN WRFD-010503 Interactive QoS Class

C

BSC6900 UMTS
VS.RAB.AttEstabPS.Str.RN WRFD-010502 Streaming QoS Class

C
1.10.10.2 Signaling Delay of PS RAB Setup
Counters
67174812 VS.RAB.EstabPS.CellFAC Maximum Duration of PS

H.MaxTime RAB Establishments
Mapped on CCH for RNC
67199679 VS.RAB.EstabPS.CellFAC Mean Duration of PS RAB

H.MeanTime Establishments Mapped on
CCH for RNC
67174809 VS.RAB.EstabPS.CellDCH. Maximum Duration of PS

MaxTime RAB Establishments
Mapped on DCH for RNC
67199427 VS.RAB.EstabPS.CellDCH. Mean Duration of PS RAB

MeanTime Establishments Mapped on
DCH for RNC
specific formulas.
67174810 VS.RAB.EstabPS.CellDCH. Cumulative Duration of PS

Cum RAB Establishments
67174811 VS.RAB.EstabPS.CellDCH. Number of Samples

Sample Recorded for Duration of PS
RAB Establishments
67174813 VS.RAB.EstabPS.CellFAC Cumulative Duration of PS

H.Cum RAB Establishments
Mapped on CCH for RNC

BSC6900 UMTS
67174814 VS.RAB.EstabPS.CellFAC Number of Samples of

H.Sample Duration of PS RAB
Establishments Mapped on
CCH for RNC
Description
These measurement items take statistics of the signaling delay of PS RAB setup from different
angles.
Measurement point
SGSN a RAB ASSIGNMENT REQUEST message for establishing PS RABs. 2)At point B, the
RNC records the time (T2) when it receives a RADIO BEARER SETUP COMPLETE message
and sends a RAB ASSIGNMENT RESPONSE message to the SGSN. Suppose delta T represents
the signaling delay of this PS RAB setup. Then, delta T=T2-T1. Through delta T of each PS
RAB setup in a measurement period, you can obtain the values of previous measurement items.
Figure 1-222 Flow chart of successful RAB setup
Formula
VS.RAB.EstabPS.CellFACH.MeanTime = [VS.RAB.EstabPS.CellFACH.Cum]/
[VS.RAB.EstabPS.CellFACH.Sample]

BSC6900 UMTS
VS.RAB.EstabPS.CellDCH.MeanTime = [VS.RAB.EstabPS.CellDCH.Cum]/
[VS.RAB.EstabPS.CellDCH.Sample]
Unit
ms
Related Features
VS.RAB.EstabPS.CellFAC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

H.MaxTime Connection and Radio
and Release
VS.RAB.EstabPS.CellFAC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

H.MeanTime Connection and Radio
and Release
VS.RAB.EstabPS.CellDCH. WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

MaxTime Connection and Radio
and Release
VS.RAB.EstabPS.CellDCH. WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

MeanTime Connection and Radio
and Release
1.10.10.3 Counters Related to the Number of PS RAB Setup Requests for Different
Maximum Downlink Bit rates
Counters

0.32.RNC Conversational RAB
RNC (Max DL Bit Rate in
[0,32]kbit/s)
67174827 VS.RAB.AttEstPSBkg0.32. Number of PS Background

RNC RAB Establishment
Attempts for RNC (Max DL
Bit Rate in [0,32]kbit/s)

BSC6900 UMTS
67174830 VS.RAB.AttEstabPS.Bkg. Number of PS Background

144.384.RNC RAB Establishment
Bit Rate in (144,384]kbit/s)


67174831 VS.RAB.AttEstabPS.Bkg.M Number of PS Background

or384.RNC RAB Establishment
Bit Rate More Than 384kbit/
s)

Mor32.RNC Conversational RAB
RNC (Max DL Bit Rate More
Than 32kbit/s)
67174822 VS.RAB.AttEstabPS.Int. Number of PS Interactive




67174826 VS.RAB.AttEstabPS.Int.Mo Number of PS Interactive

r384.RNC RAB Establishment
s)

BSC6900 UMTS
67174817 VS.RAB.AttEstabPS.Str. Number of PS Streaming




67174821 VS.RAB.AttEstabPS.Str.Mo Number of PS Streaming

r384 RAB Establishment
s)
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 SGSN a RAB ASSIGNMENT REQUEST message about the PS domain, the RNC measures
these items according to different types of services.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

0.32.RNC
VS.RAB.AttEstPSBkg0.32. WRFD-010504 Background QoS Class

RNC
VS.RAB.AttEstabPS.Bkg. WRFD-010504 Background QoS Class

144.384.RNC

32.64.RNC

64.144.RNC

BSC6900 UMTS
VS.RAB.AttEstabPS.Bkg.M WRFD-010504 Background QoS Class

or384.RNC

Mor32.RNC
VS.RAB.AttEstabPS.Int. WRFD-010503 Interactive QoS Class

0.32.RNC

144.384.RNC

32.64.RNC

64.144.RNC
VS.RAB.AttEstabPS.Int.Mo WRFD-010503 Interactive QoS Class

r384.RNC
VS.RAB.AttEstabPS.Str. WRFD-010502 Streaming QoS Class

0.32.RNC

32.64.RNC

144.384.RNC

64.144.RNC
VS.RAB.AttEstabPS.Str.Mo WRFD-010502 Streaming QoS Class

r384
1.10.10.4 Counters Related to the Number of Successful PS RAB Setups for

Different Maximum Downlink Bit Rates
Counters
67174832 VS.RAB.SuccEstabPS.Conv Number of Successful PS

.0.32.RNC Conversational RAB
(Max DL Bit Rate in [0,32]
kbit/s)

BSC6900 UMTS

kbit/s)

(Max DL Bit Rate in
(144,384]kbit/s)

(Max DL Bit Rate in (32,64]
kbit/s)

kbit/s)

.Mor32.RNC Conversational RAB
(Max DL Bit Rate More Than
32kbit/s)
67174838 VS.RAB.SuccEstabPS.Str. Number of Successful PS

Mor384.RNC Streaming RAB
384kbit/s)
67174839 VS.RAB.SuccEstabPS.Int. Number of Successful PS

kbit/s)

(Max DL Bit Rate in
(144,384]kbit/s)

BSC6900 UMTS

kbit/s)

kbit/s)

Mor384.RNC Interactive RAB
384kbit/s)

Mor384.RNC Background RAB
384kbit/s)
67174834 VS.RAB.SuccEstab.PS.Str. Number of Successful PS

kbit/s)

(Max DL Bit Rate in
(144,384]kbit/s)

kbit/s)

kbit/s)

BSC6900 UMTS
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
VS.RAB.SuccEstabPS.Conv WRFD-010501 Conversational QoS Class

.0.32.RNC

BSC6900 UMTS
VS.RAB.SuccEstabPS.Bkg. WRFD-010504 Background QoS Class

0.32.RNC

144.384.RNC

32.64.RNC

64.144.RNC

.Mor32.RNC
VS.RAB.SuccEstabPS.Str. WRFD-010502 Streaming QoS Class

Mor384.RNC
VS.RAB.SuccEstabPS.Int. WRFD-010503 Interactive QoS Class

0.32.RNC

144.384.RNC

32.64.RNC

64.144.RNC

Mor384.RNC

Mor384.RNC
VS.RAB.SuccEstab.PS.Str. WRFD-010502 Streaming QoS Class

0.32.RNC

144.384.RNC

32.64.RNC

64.144.RNC
1.10.10.5 Mean Number of PS RABs

BSC6900 UMTS
Counters
67199790 VS.RAB.Num.PS.Mean Mean Number of PS RABs

for RNC
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
VS.RAB.Num.PS.Mean WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.10.10.6 Times of PS RAB established successfully with 0kbps for RNC
Counters
67196304 VS.RAB.SuccEstab.PS. Number of PS RABs

0kbps.RNC Established Successfully
with 0 kbit/s for RNC

BSC6900 UMTS
Description
This counter provides the number of times that an UE access the network successfully through
the 0 Kbit/s RAB in the RNC during the procedures of RAB establishment, RAB modification,
Cell update, relocation (UE involved) and hard handover.
Measurement point
The measurement is triggered at point A as shown in the following figure 1. During a RAB setup
procedure, when the RNC receives a RADIO BEARER SETUP COMPLETE message from
UE, it measures this counter in the RNC if the rate of the RAB is 0 Kbit/s.
The measurement is triggered at point A as shown in the following figure 2. During a RAB
modification procedure, when the RNC receives a RADIO BEARER RECONFIGURATION
COMPLETE message from UE, it measures this counter in the RNC if the rate of the RAB is 0
Kbit/s.
Figure 1-226 RAB modification procedure

BSC6900 UMTS
The measurement is triggered at point A as shown in the following figure 3. During a P2D
procedure, when the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE
message from UE, it measures this counter in the RNC if the rate of the RAB is 0 Kbit/s.
Figure 1-227 P2D procedure
The measurement is triggered at point A as shown in the following figure 4. During a relocation
(UE involved) procedure, when the RNC sends a RELOCATION COMPLETE message to CN,
it measures this counter in the RNC if the rate of the RAB is 0 Kbit/s.
Figure 1-228 relocation (UE involved) procedure
The measurement is triggered at point A as shown in the following figure 5. During a hard
handover procedure, when the RNC receives a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from UE, it measures this counter in the RNC if the rate of the RAB is 0
Kbit/s.

BSC6900 UMTS
Figure 1-229 hard handover procedure
Formula
None
Unit
None
Related Features
VS.RAB.SuccEstab.PS. WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

0kbps.RNC Connection and Radio
and Release
1.10.10.7 Number of Successful RAB Establishments for PS Services

BSC6900 UMTS
Counters
73394066 VS.RAB.SuccEstabPS.Bkg. Number of Successful RAB

RNC Establishments for PS
Background Services for
RNC
73394067 VS.RAB.SuccEstabPS.Str.R Number of Successful RAB

NC Establishments for PS
Streaming Services for RNC
73394068 VS.RAB.SuccEstabPS.Conv Number of Successful RAB

.RNC Establishments for PS
RNC
73394069 VS.RAB.SuccEstabPS.Int.R Number of Successful RAB

NC Establishments for PS
Interactive Services for RNC
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.

BSC6900 UMTS
Figure 1-230 PS RAB setup procedure
Formula
None
Unit
None
Related Features

RNC
VS.RAB.SuccEstabPS.Str.R WRFD-010502 Streaming QoS Class

NC

.RNC
VS.RAB.SuccEstabPS.Int.R WRFD-010503 Interactive QoS Class

NC

BSC6900 UMTS
1.10.11 Measurement of CS RAB assignment modification per RNC

(RAB.ModCs.RNC)
Overview
If the parameters, such as QoS, of a CS service are changed after the RAB is set up, the CN
sends to the RNC a RAB ASSIGNMENT REQUEST message. After receiving this message,
the RNC initiates the RAB modification procedure. If the RAB modification succeeds, the RNC
sends to the CN a RAB ASSIGNMENT RESPONSE message indicating that the RAB
modification succeeds. If the RAB modification fails, the RNC sends to the CN a RAB
ASSIGNMENT RESPONSE message indicating that the RAB modification fails.
For details, see 3GPP TS 25.331 and 3GPP TS 25.413.
Counters
Description
67174725 VS.RAB.AttModC Number of RAB Earlier than

S.Conv.RNC Modification V900R011
Requests for CS
Conversational
Services for RNC
67174726 VS.RAB.AttModC Number of RAB Earlier than

S.Str.RNC Modification V900R011
Requests for CS
Streaming Services
for RNC
67174728 VS.RAB.SuccMod Number of Earlier than

CS.Str.RNC Successful RAB V900R011
Modifications for CS
Streaming Services
for RNC
67203800 VS.RAB.ModReqC Number of VP Earlier than

S.VP.Fallback.RN Services Fallen Back V900R011
C to AMR Services for
RNC

CS.Conv.RNC Successful RAB V900R011
Modifications for CS
Conversational
Services for RNC
None

BSC6900 UMTS
1.10.11.1 Number of CS RAB Modification Requests
Counters
67174725 VS.RAB.AttModCS.Conv.R Number of RAB

NC Modification Requests for
CS Conversational Services
for RNC
67174726 VS.RAB.AttModCS.Str.RN Number of RAB

C Modification Requests for
CS Streaming Services for
RNC
Description
These counters provide the number of RAB modification requests for CS services in the RNC
based on the service type.
Measurement point
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AttModCS.Conv.R WRFD-010501 Conversational QoS Class

NC
VS.RAB.AttModCS.Str.RN WRFD-010502 Streaming QoS Class

C
1.10.11.2 Number of VP Services Fallen Back to AMR Services
Counters
67203800 VS.RAB.ModReqCS.VP.Fa Number of VP Services

llback.RNC Fallen Back to AMR
Services for RNC
Description
This counter provides the number of times that the RNC triggers the fallback of the VP service
to the AMR service.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends to the CN
a RAB MODIFICATION REQUEST message to request that the VP services fall back to AMR
services.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.ModReqCS.VP.Fa WRFD-020303 Inter-RAT Handover Based

llback.RNC WRFD-020305 on Coverage

on Service
WRFD-021200
on Load
HCS (Hierarchical Cell
Structure)
1.10.11.3 Number of Successful CS RAB Modifications

BSC6900 UMTS
Counters
67174727 VS.RAB.SuccModCS.Conv. Number of Successful RAB

RNC Modifications for CS
RNC
67174728 VS.RAB.SuccModCS.Str.R Number of Successful RAB

NC Modifications for CS
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SuccModCS.Conv. WRFD-010501 Conversational QoS Class

RNC
VS.RAB.SuccModCS.Str.R WRFD-010502 Streaming QoS Class

NC
1.10.12 Measurement of PS RAB assignment modification per RNC

(RAB.ModPs.RNC)
Overview
If the parameters, such as QoS, of a PS service are changed after the RAB is set up, the CN sends
to the RNC a RAB ASSIGNMENT REQUEST message.
If the RNC determines that the RAB modification is needed (a RAB exists before the RAB
ASSIGNMENT REQUEST message is received) after receiving the message, it sends to the UE
a RADIO BEARER RECONFIGURATION message. If the RAB modification succeeds, the
UE sends to the RNC a RADIO BEARER RECONFIGURATION COMPLETE message. The
RNC then sends to the CN a RAB ASSIGNMENT RESPONSE message indicating that the
RAB modification succeeds.
Counters
Description
67174793 RAB.AttModPS.Co Number of RAB Earlier than

nv.RNC Modification V900R011
Requests for PS
Conversational
Services for RNC

BSC6900 UMTS

Description
67174794 RAB.AttModPS.St Number of RAB Earlier than

r.RNC Modification V900R011
Requests for PS
Streaming Services
for RNC
67174795 RAB.AttModPS.In Number of RAB Earlier than

t.RNC Modification V900R011
Requests for PS
Interactive Services
for RNC
67174796 RAB.AttModPS.Bg Number of RAB Earlier than

rd.RNC Modification V900R011
Requests for PS
Background
Services for RNC

PS.Str.RNC Successful RAB V900R011
Modifications for PS
Streaming Services
for RNC

PS.Conv.RNC Successful RAB V900R011
Conversational
Services for RNC

PS.Int.RNC Successful RAB V900R011
for RNC

PS.Bkg.RNC Successful RAB V900R011
Background
Services for RNC
None
1.10.12.1 Number of PS RAB Modification Requests

BSC6900 UMTS
Counters
67174793 RAB.AttModPS.Conv.RNC Number of RAB

Modification Requests for PS
RNC
67174794 RAB.AttModPS.Str.RNC Number of RAB

67174795 RAB.AttModPS.Int.RNC Number of RAB

67174796 RAB.AttModPS.Bgrd.RNC Number of RAB

RNC
Description
These counters provide the number of RAB modification requests for PS services in the RNC
based on the service type.
Measurement point
the CN a RAB ASSIGNMENT REQUEST message, it measures the corresponding counter
based on the service type if the RAB is for PS services.

BSC6900 UMTS
Figure 1-234 PS RAB modification procedure
Formula
None
Unit
None
Related Features
RAB.AttModPS.Conv.RNC WRFD-010501 Conversational QoS Class
RAB.AttModPS.Str.RNC WRFD-010502 Streaming QoS Class
RAB.AttModPS.Int.RNC WRFD-010503 Interactive QoS Class
RAB.AttModPS.Bgrd.RNC WRFD-010504 Background QoS Class
1.10.12.2 Number of Successful PS RAB Modifications

BSC6900 UMTS
Counters
67174797 VS.RAB.SuccModPS.Conv. Number of Successful RAB

RNC Modifications for PS
RNC
67174798 VS.RAB.SuccModPS.Str.R Number of Successful RAB

NC Modifications for PS
67174799 VS.RAB.SuccModPS.Int.R Number of Successful RAB

NC Modifications for PS
67174800 VS.RAB.SuccModPS.Bkg. Number of Successful RAB

RNC Modifications for PS
RNC
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SuccModPS.Conv. WRFD-010501 Conversational QoS Class

RNC
VS.RAB.SuccModPS.Str.R WRFD-010502 Streaming QoS Class

NC
VS.RAB.SuccModPS.Int.R WRFD-010503 Interactive QoS Class

NC
VS.RAB.SuccModPS.Bkg. WRFD-010504 Background QoS Class

RNC

BSC6900 UMTS
1.10.13 Measurement of multi-RAB service per RNC

(RAB.MultiRab.RNC)
Overview
Multi-RAB measurement includes:
Measurement of the number of UEs with multiple RABs.
Multiple RABs can be multiple CS domain RABs, multiple PS domain RABs or the
combinations of CS domain and PS domain RABs. The combinations of RABs can be denoted
by abbreviations. For example:
1CS+1PS indicates that there are concurrently one CS domain RAB and one PS domain RAB.
1CS+2PS indicates that there are concurrently one CS domain RAB and two PS domain RABs.
2CS indicates that there are concurrently two CS domain RABs.
Counters
Description
67199688 VS.MultRAB.0CS. Number of UEs with Earlier than

2PS.RNC 2PS RABs for RNC V900R011
67199684 VS.MultRAB. Number of UEs with Earlier than

1CS1PS.RNC 1CS+1PS RABs for V900R011
RNC

RNC

RNC

RNC

RNC
None

BSC6900 UMTS
1.10.13.1 Mean Number of UEs with Multi-RABs in RNC
Counters
67199688 VS.MultRAB.0CS. Number of UEs with 2PS

2PS.RNC RABs for RNC
67199684 VS.MultRAB.1CS1PS.RNC Number of UEs with 1CS

+1PS RABs for RNC

+2PS RABs for RNC

+3PS RABs for RNC

+3PS RABs for RNC

+4PS RABs for RNC
Description
The measurement items take 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
VS.MultRAB.0CS. WRFD-01061501 Combination of Two PS

2PS.RNC Services

BSC6900 UMTS
VS.MultRAB.1CS1PS.RNC WRFD-01060902 Combination of One CS

Service and One PS Service

Service and Two PS Services
VS.MultRAB.0CS3PS.RNC WRFD-01061503 Combination of Three PS

Services

Service and Three PS
Services
VS.MultRAB.0CS4PS.RNC WRFD-01061505 Combination of Four PS

Services
1.10.14 Measurement of RAB release per RNC

(RAB.RelAbnormal.RNC)
Overview
The RAB release can be classified into the following types:
1) The RAB release initiated by the RNC. When the RNC detects that the UE has no data to
transmit for a long period or the RNC is faulty (for example, the SRB resets or the AAL2 link
on the Iu interface is faulty), the RNC sends to the CN a RAB RELEASE REQUEST message
to release the RAB or an IU RELEASE REQUEST message to release the Iu connection. If the
cause value is "User Inactivity", "Normal Release", "Successful Relocation", "Network
Optimization", the RAB release is considered as normal release; otherwise, the RAB release is
considered as abnormal release. For details, see the middle of the figure.
2) The RAB release initiated by the CN. The RNC initiates the RAB release by sending the RAB
ASSIGNMENT REQUEST message and initiates the Iu connection release by sending the IU
RELEASE COMMAND message. All the RAB releases initiated by the CN are considered as
normal releases. For details, see the left part of the figure.
3) The RAB release initiated by the UE. The UE initiates the RAB release by sending the
SIGNALING CONNECTION RELEASE INDICATION message. According to the domain
information in the message, the RNC sends an IU RELEASE REQUEST message to the CN
node (SGSN or MSC) to release the Iu connection. After the Iu connection is released, the RNC
initiates the RRC release if no Iu connection exists in another domain. All the RAB releases
initiated by the UE are considered as normal releases. For details, see the right part of the figure.
Note: If the Iu interface is reset, released services will be regarded as being normally released.
The sub procedures mentioned in figure 1 are as following.

BSC6900 UMTS
Figure 1-236 Flow chart of Drop

BSC6900 UMTS
Figure 1-237 Sub flow chart of Drop
A VS.RAB.AbnormRel.CS.RNC,
VS.RAB.AbnormRel.CS.RF.RNC,
VS.RAB.AbnormRel.AMR.RNC,
VS.RAB.AbnormRel.CS64.RNC
B VS.RAB.NormRel.CS.RNC,
VS.RAB.NormRel.CS.UEGen.RNC,
VS.RAB.NormRel.VPLimit.RNC
C VS.RAB.NormRel.PS.RNC,
VS.RAB.NormRel.PS.UEGen.RNC,
VS.RAB.NormRel.PS.0kbps.Timeout.RNC
D VS.RAB.AbnormRel.PS.RNC,
VS.RAB.AbnormRel.PS.RF.RNC

BSC6900 UMTS
Counters
Description
67174954 VS.RAB.AbnormR Number of CS RABs Earlier than

el.CS.RF.RNC Abnormally V900R011
Released due to RF
cause for RNC

el.PS.RF.RNC Abnormally V900R011
Released due to RF
cause for RNC

el.CS.RNC Abnormally V900R011
Released for RNC

el.PS.RNC Abnormally V900R011
Released for RNC
67174965 VS.RAB.NormRel. Number of CS RABs Earlier than

CS.RNC Normally Released V900R011
for RNC

PS.RNC Normally Released V900R011
for RNC

CS.UEGen.RNC Normally Released V900R011
for RNC (UE
Generated Signaling
Connection Release)

PS.UEGen.RNC Normally Released V900R011
for RNC (UE
Generated Signaling
Connection Release)

el.AMR.RNC Abnormally V900R011
Released for RNC
(AMR)

el.CS64.RNC Abnormally V900R011
Released for RNC
(64kbit/s
Conversational
Services)

BSC6900 UMTS

Description
67196236 VS.RAB.NormRel. Number of 64kbit/s Earlier than

VPLimit.RNC CS RABs Normally V900R011
Released for RNC
Due to 64kbit/s CS
Service Forbiddance
in Target Cell

PS. of 0 kbit/s Released V900R011
0kbps.Timeout.RN for Failed to Rate up
C for RNC
Counter Sub Counter
VS.RAB.AbnormRel.PS.RNC VS.RAB.AbnormRel.PS.RF.RNC
VS.RAB.NormRel.CS.RNC VS.RAB.NormRel.CS.UEGen.RNC
VS.RAB.NormRel.VPLimit.RNC
VS.RAB.NormRel.PS.RNC VS.RAB.NormRel.PS.UEGen.RNC
VS.RAB.NormRel.PS.0kbps.Timeout.RNC
VS.RAB.AbnormRel.CS.RNC VS.RAB.AbnormRel.AMR.RNC
VS.RAB.AbnormRel.CS64.RNC
1.10.14.1 Number of RABs Abnormally Released for RNC
Counters
67174963 VS.RAB.AbnormRel.CS.R Number of CS RABs

NC Abnormally Released for
RNC
67174964 VS.RAB.AbnormRel.PS.RN Number of PS RABs

C Abnormally Released for
RNC

BSC6900 UMTS
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
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 a RAB

BSC6900 UMTS
As shown in point A of the figure, when an exception occurs, the RNC sends the CN an IU

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.CS.R WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

NC Connection and Radio
and Release
VS.RAB.AbnormRel.PS.RN WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

C Connection and Radio
and Release
1.10.14.2 Number of Released RABs due to RF cause

BSC6900 UMTS
Counters

.RNC Abnormally Released due to
RF cause for RNC

.RNC Abnormally Released due to
RF cause for RNC
Description
These measurement items provide the number of released RABs triggered by the RNC due to
RF failure.
Measurement point
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
Release","Successful Relocation", "Network Optimization" or "UE Generated Signalling
Connection Release", reference to 3GPP TS 25.413), the RNC measures the items by the CN
domains.

BSC6900 UMTS
RAB RELEASE REQUEST message with cause "Radio Connection With UE Lost" or "Failure
in the Radio Interface Procedure" in the case of RF failure(for example:SRB reset, TRB reset,
radio link synchronous failure or UU interface no reply,etc.).If the RNC receives an IU
RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal
Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling
domains.
IU RELEASE REQUEST message with cause "Radio Connection With UE Lost" or "Failure
in the Radio Interface Procedure" in the case of RF failure (for example:SRB reset, TRB reset,
radio link synchronous failure or UU interface no reply,etc.).If the RNC receives an IU
RELEASE COMMAND message(with the cause other than "User Inactivity", "Normal
Release", "Successful Relocation", "Network Optimization" or "UE Generated Signalling
domains.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.CS.RF WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

.RNC Connection and Radio
and Release
VS.RAB.AbnormRel.PS.RF WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.10.14.3 Number of Abnormally Released CS RABs

BSC6900 UMTS
Counters
67174951 VS.RAB.AbnormRel.AMR. Number of CS RABs

RNC Abnormally Released for
RNC (AMR)
67174952 VS.RAB.AbnormRel.CS64. Number of CS RABs

RNC Abnormally Released for
RNC (64kbit/s
Conversational Services)
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
Connection Release", reference to 3GPP TS 25.413), the RNC measures the items by the types
of services.

BSC6900 UMTS
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.
Release", reference to 3GPP TS 25.413), the RNC measures the items by the types of services.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

RNC

RNC
1.10.14.4 Number of Normally Released RABs

BSC6900 UMTS
Counters
67174965 VS.RAB.NormRel.CS.RNC Number of CS RABs

Normally Released for RNC
67174966 VS.RAB.NormRel.PS.RNC Number of PS RABs

Normally Released for RNC
67196236 VS.RAB.NormRel.VPLimit. Number of 64kbit/s CS

RNC RABs Normally Released for
RNC Due to 64kbit/s CS
Service Forbiddance in
Target Cell
Description
These measurement items take statistics of the number of normally released RABs according to
different domains.
VS.RAB.NormRel.VPLimit.RNC Number of normally released CS VP RABs

triggered by RNC(with cause of "Network
Optimization") because VP is forbidden in
target cell
Measurement point
Optimization" or "UE Generated Signalling Connection Release", the RNC measures these items
by the CN domains.

BSC6900 UMTS
Signalling Connection Release" ,the RNC measures these items by the CN domains.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.CS.RNC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.NormRel.PS.RNC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.NormRel.VPLimit. WRFD-020130 Videophone Service

RNC Restriction

BSC6900 UMTS
1.10.14.5 Number of Released RABs Triggered by RNC Due to UE Signaling

Connection Release
Counters
67190454 VS.RAB.NormRel.CS.UEG Number of CS RABs

en.RNC Normally Released for RNC
(UE Generated Signaling
Connection Release)
67190455 VS.RAB.NormRel.PS.UEG Number of PS RABs

en.RNC Normally Released for RNC
Connection Release)
Description
These measurement items take statistics of the number of released RABs triggered by the RNC
due to UE signaling connection release according to different domains.
Measurement point
The measurement is triggered at point A as shown in the figure. In the case of UE generated
signalling connection release, the RNC sends to the CN an IU RELEASE REQUEST message
(with release cause of "UE Generated Signalling Connection Release", reference to 3GPP TS
25.413),the RNC measures the items by the CN domains.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.CS.UEG WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

en.RNC Connection and Radio
and Release
VS.RAB.NormRel.PS.UEG WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

en.RNC Connection and Radio
and Release
1.10.14.6 Times of PS RAB of 0kbps released for failing to rate up before timer
expiry
Counters
67196305 VS.RAB.NormRel.PS. Number of PS RABs of 0

0kbps.Timeout.RNC kbit/s Released for Failed to
Rate up for RNC
Description
This measurement item provides the times of releasing RAB of 0kbps for failing to rate up before
timer expiry in RNC level.
Measurement point
The measurement is triggered when a PS RAB of 0kbps released by RNC, due to failure of rating
up before the timer of kbit/s expires. The measurement is triggered at point A in the figure. When
the RNC initiates an Iu connection release procedure with the cause "Network Optimization"
and PS services are released due to the failure of 0 kbit/s PS RAB rating up before timer expiry,
it measures the number of times of releasing RAB of 0 kbit/s for failing to rate up before timer
expiry in RNC level.

BSC6900 UMTS
The measurement is triggered at point B in the figure. When the RNC initiates a RAB assignment
release procedure with the cause "Network Optimization" and PS services are released due to
the failure of 0 kbit/s PS RAB rating up before timer expiry, it measures the number of times of
releasing RAB of 0 kbit/s for failing to rate up before timer expiry in RNC level.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.PS. WRFD-021101 Dynamic Channel

0kbps.Timeout.RNC Configuration Control
(DCCC)
1.10.15 Measurement of CS RAB release per RNC(RAB.RelCs.RNC)
Overview
If a CS RAB needs to be released, the CN sends to the RNC a RAB ASSIGNMENT REQUEST
message, indicating the RNC to release the RAB. After receiving this message, the RNC sends
to the CN a RADIO BEARER RELEASE message. If the radio bearer (RB) is released
successfully, the UE sends to the RNC a RADIO BEARER RELEASE COMPLETE. Then the
RNC sends to the CN a RAB ASSIGNMENT RESPONSE message, indicating that the RAB is
released.
Counters
Description
67192101 VS.RAB.AttRelCS. Number of CS RAB V900R012

RNC Release Attempts for
RNC
67192102 VS.RAB.SuccRelC Number of Earlier than

S.RNC Successful CS RAB V900R011
Releases for RNC
None
1.10.15.1 Number of CS RABs Requested to Release

BSC6900 UMTS
Counters
67192101 VS.RAB.AttRelCS.RNC Number of CS RAB Release

Attempts for RNC
Description
This measurement item provides the total number of CS RABs requested to release in the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from
the CN a RAB ASSIGNMENT REQUEST message indicating that a CS RAB needs to be
released. In this case, this counter is measured in the best cell that the UE camps on.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RAB.AttRelCS.RNC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.10.15.2 Number of Successful CS RAB Releases
Counters
67192102 VS.RAB.SuccRelCS.RNC Number of Successful CS

RAB Releases for RNC
Description
This counter provides the number of times that a RAB for CS services is released successfully
in the RNC.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends to the CN
a RAB ASSIGNMENT RESPONSE message indicating that the RAB release succeeds and the
RAB is for CS services.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SuccRelCS.RNC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
1.10.16 Measurement of PS RAB release per RNC(RAB.RelPs.RNC)
Overview
If a PS RAB needs to be released, the CN sends to the RNC a RAB ASSIGNMENT REQUEST
message, indicating the RNC to release the RAB. After receiving this message, the RNC sends
to the CN a RADIO BEARER RELEASE message. If the radio bearer (RB) is released
successfully, the UE sends to the RNC a RADIO BEARER RELEASE COMPLETE. Then the
RNC sends to the CN a RAB ASSIGNMENT RESPONSE message, indicating that the RAB is
released.
Counters
Description
67192104 VS.RAB.SuccRelP Number of Earlier than

S.RNC Successful PS RAB V900R011
Releases for RNC
73394107 VS.RAB.AttRelPS. Number of PS RAB V900R012

RNC Release Attempts for
RNC
None
1.10.16.1 Number of Successful PS RAB Releases
Counters
67192104 VS.RAB.SuccRelPS.RNC Number of Successful PS

RAB Releases for RNC
Description
This counter provides the number of times that a RAB for PS services is released successfully
in the RNC.

BSC6900 UMTS
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
VS.RAB.SuccRelPS.RNC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
1.10.16.2 Number of PS RABs Requested to Release
Counters
73394107 VS.RAB.AttRelPS.RNC Number of PS RAB Release

Attempts for RNC
Description
This measurement item provides the total number of PS RABs requested to release in the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC measures the item, if
the RNC finds that some RABs need to be released after receiving a RAB ASSIGNMENT
REQUEST message about the PS domain from the SGSN.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.RAB.AttRelPS.RNC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.10.17 Measurement of RB Procedure per RNC(RB.RNC)
Overview
The CS domain has four types of services, namely, conversational service, streaming service,
interactive service, and background service. At present, it only supports the first two services.
The PS domain carried on the DCH also has the same four types of services, among which the
conversational service supports eight variable rates, the streaming service supports eight variable
rates, the interactive service supports eight variable rates, and the background service supports
eight variable-rates.
UTRAN can provide different rates according to the resource status and requirement type. If the
RRC state of service switches from CELL_DCH to other states, the measurement item decreases
by one. If the RRC state of service switches from other states to CELL_DCH, the measurement
item increases by one. If the RRC state of service switches from CELL_DCH to CELL_DCH
and the bandwidth is adjusted, the old measurement item decreases by one and the new one
increases by one.
Counters
Description
67202577 VS.RB.PS.Conv.D Average Number of Earlier than

L.8.RNC RBs for PS R99 V900R011
Conversational
Services with DL
Rate of 8 Kbit/s for
RNC

BSC6900 UMTS

Description

Conversational
Services with DL
RNC

Conversational
Services with DL
RNC

Conversational
Services with DL
RNC
67202589 VS.RB.PS.Conv.U Average Number of Earlier than

Conversational
Services with UL
RNC

Conversational
Services with UL
RNC

Conversational
Services with UL
RNC

Conversational
Services with UL
RNC

BSC6900 UMTS

Description
67202604 VS.RB.PS.Str.DL. Average Number of Earlier than

144.RNC RBs for PS R99 V900R011
Streaming Services
with DL Rate of 144
Kbit/s for RNC

Streaming Services
with DL Rate of 128
Kbit/s for RNC

Streaming Services
with DL Rate of 64
Kbit/s for RNC

Streaming Services
with DL Rate of 32
Kbit/s for RNC

Streaming Services
with DL Rate of 16
Kbit/s for RNC

Streaming Services
with DL Rate of 8
Kbit/s for RNC
67202625 VS.RB.PS.Str.UL. Average Number of Earlier than

Streaming Services
with UL Rate of 144
Kbit/s for RNC

Streaming Services
with UL Rate of 128
Kbit/s for RNC

BSC6900 UMTS

Description

Streaming Services
with UL Rate of 64
Kbit/s for RNC

Streaming Services
with UL Rate of 32
Kbit/s for RNC

Streaming Services
with UL Rate of 16
Kbit/s for RNC

Streaming Services
with UL Rate of 8
Kbit/s for RNC
67202643 VS.RB.PS.Int.DL. Average Number of Earlier than

with DL Rate of 384
Kbit/s for RNC

with DL Rate of 256
Kbit/s for RNC

with DL Rate of 144
Kbit/s for RNC

with DL Rate of 128
Kbit/s for RNC

BSC6900 UMTS

Description

with DL Rate of 64
Kbit/s for RNC

with DL Rate of 32
Kbit/s for RNC

with DL Rate of 16
Kbit/s for RNC

with DL Rate of 8
Kbit/s for RNC
67202667 VS.RB.PS.Int.UL. Average Number of Earlier than

with UL Rate of 384
Kbit/s for RNC

with UL Rate of 256
Kbit/s for RNC

with UL Rate of 144
Kbit/s for RNC

with UL Rate of 128
Kbit/s for RNC

BSC6900 UMTS

Description

with UL Rate of 64
Kbit/s for RNC

with UL Rate of 32
Kbit/s for RNC

with UL Rate of 16
Kbit/s for RNC

with UL Rate of 8
Kbit/s for RNC
67202691 VS.RB.PS.Bkg.DL. Average Number of Earlier than

Background
Services with DL
RNC

Background
Services with DL
RNC

Background
Services with DL
RNC

BSC6900 UMTS

Description

Background
Services with DL
RNC

Background
Services with DL
RNC

Background
Services with DL
RNC

Background
Services with DL
RNC

Background
Services with DL
RNC
67202715 VS.RB.PS.Bkg.UL. Average Number of Earlier than

Background
Services with UL
RNC

Background
Services with UL
RNC

BSC6900 UMTS

Description

Background
Services with UL
RNC

Background
Services with UL
RNC

Background
Services with UL
RNC

Background
Services with UL
RNC

Background
Services with UL
RNC

Background
Services with UL
RNC
67202739 VS.RB.CS.Str.DL. Average Number of Earlier than

57.6.RNC RBs for CS V900R011
Streaming Services
with DL Rate of 57.6
Kbit/s for RNC

BSC6900 UMTS

Description
67202748 VS.RB.CS.Str.UL. Average Number of Earlier than

57.6.RNC RBs for CS V900R011
Streaming Services
with UL Rate of 57.6
Kbit/s for RNC
67202766 VS.RB.CS.Conv.D Average Number of Earlier than

L.64.RNC RBs for CS V900R011
Conversational
Services with DL
RNC
67202778 VS.RB.CS.Conv.U Average Number of Earlier than

L.64.RNC RBs for CS V900R011
Conversational
Services with UL
RNC
67192444 VS.DRD.RB.D2H. Number of DCH-to- Earlier than

Att.RNC HSDPA Directed V900R011
Retry Attempts for
RNC
67192445 VS.DRD.RB.D2H.S Number of Earlier than

ucc.RNC Successful DCH-to- V900R011
HSDPA Directed
Retry for RNC

256.384.RNC RBs for PS R99 V900R011
Streaming Services
with DL Rate of 256
Kbit/s or 384 Kbit/s
for RNC

256.384.RNC RBs for PS R99 V900R011
Streaming Services
with UL Rate of 256
Kbit/s or 384 Kbit/s
for RNC

L.38.8.RNC RBs for PS R99 V900R011
Conversational
Services with DL
Rate of 38.8 Kbit/s
for RNC

BSC6900 UMTS

Description

Conversational
Services with DL
Rate of 39.2 Kbit/s
for RNC

Conversational
Services with DL
RNC

Conversational
Services with DL
Rate of 42.8 Kbit/s
for RNC

Conversational
Services with UL
Rate of 38.8 Kbit/s
for RNC

Conversational
Services with UL
Rate of 39.2 Kbit/s
for RNC

Conversational
Services with UL
RNC

Conversational
Services with UL
Rate of 42.8 Kbit/s
for RNC

BSC6900 UMTS
None
1.10.17.1 Counters Related to the Average Number of RBs for PS R99

Conversational Services
Counters
67202577 VS.RB.PS.Conv.DL.8.RNC Average Number of RBs for

PS R99 Conversational
Services with DL Rate of 8
Kbit/s for RNC
67202580 VS.RB.PS.Conv.DL. Average Number of RBs for

16.RNC PS R99 Conversational
Kbit/s for RNC

Kbit/s for RNC

Kbit/s for RNC
67202589 VS.RB.PS.Conv.UL.8.RNC Average Number of RBs for

PS R99 Conversational
Services with UL Rate of 8
Kbit/s for RNC
67202592 VS.RB.PS.Conv.UL. Average Number of RBs for

Kbit/s for RNC

Kbit/s for RNC

Kbit/s for RNC

BSC6900 UMTS

38.8.RNC PS R99 Conversational
Services with DL Rate of
38.8 Kbit/s for RNC

39.2 Kbit/s for RNC

Kbit/s for RNC

42.8 Kbit/s for RNC

Services with UL Rate of
38.8 Kbit/s for RNC

39.2 Kbit/s for RNC

Kbit/s for RNC

42.8 Kbit/s for RNC
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

BSC6900 UMTS
of each counter is obtained as follows: dividing the accumulated value of each sampling point
Formula
None
Unit
None
Related Features
VS.RB.PS.Conv.DL.8.RNC WRFD-010501 Conversational QoS Class
VS.RB.PS.Conv.DL. WRFD-010501 Conversational QoS Class

16.RNC

32.RNC

64.RNC
VS.RB.PS.Conv.UL.8.RNC WRFD-010501 Conversational QoS Class
VS.RB.PS.Conv.UL. WRFD-010501 Conversational QoS Class

16.RNC

32.RNC

64.RNC

38.8.RNC

39.2.RNC

40.RNC

42.8.RNC

38.8.RNC

39.2.RNC

BSC6900 UMTS

40.RNC

42.8.RNC
1.10.17.2 Counters Related to the Average Number of PS R99 Interactive Service

RBs
Counters
67202643 VS.RB.PS.Int.DL.384.RNC Average Number of RBs for

PS R99 Interactive Services
with DL Rate of 384 Kbit/s
for RNC

for RNC

for RNC

for RNC

with DL Rate of 64 Kbit/s for
RNC

RNC

RNC

BSC6900 UMTS

RNC
67202667 VS.RB.PS.Int.UL.384.RNC Average Number of RBs for

with UL Rate of 384 Kbit/s
for RNC

for RNC

for RNC

for RNC

with UL Rate of 64 Kbit/s for
RNC

RNC

RNC

RNC
Description
These counters provide the average number of RBs for PS R99 interactive services in the uplink
or downlink.

BSC6900 UMTS
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
VS.RB.PS.Int.DL.384.RNC WRFD-010503 Interactive QoS Class
VS.RB.PS.Int.UL.384.RNC WRFD-010503 Interactive QoS Class
1.10.17.3 Counters Related to the Average Number of PS R99 Backgroud Service

RBs

BSC6900 UMTS
Counters
67202691 VS.RB.PS.Bkg.DL. Average Number of RBs for

384.RNC PS R99 Background Services
for RNC

for RNC

for RNC

for RNC
67202703 VS.RB.PS.Bkg.DL.64.RNC Average Number of RBs for

PS R99 Background Services
RNC

RNC

RNC

RNC
67202715 VS.RB.PS.Bkg.UL. Average Number of RBs for

for RNC

for RNC

BSC6900 UMTS

for RNC

for RNC
67202727 VS.RB.PS.Bkg.UL.64.RNC Average Number of RBs for

RNC

RNC

RNC

RNC
Description
These counters provide the average number of RBs for PS R99 background services in the uplink
or downlink.
Measurement point
The number of RBs for each type of PS R99 backgroud services is sampled periodically
(sampling periodicity is 5 seconds) in the RNC. At the end of the measurement period, the value
of each counter is obtained as follows: dividing the accumulated value of each sampling point
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RB.PS.Bkg.DL. WRFD-010504 Background QoS Class

384.RNC

256.RNC

144.RNC

128.RNC
VS.RB.PS.Bkg.DL.64.RNC WRFD-010504 Background QoS Class
VS.RB.PS.Bkg.UL. WRFD-010504 Background QoS Class

384.RNC

256.RNC

144.RNC

128.RNC
VS.RB.PS.Bkg.UL.64.RNC WRFD-010504 Background QoS Class
1.10.17.4 Counters Related to the Average Number of CS Streaming Service RBs
Counters
67202739 VS.RB.CS.Str.DL. Average Number of RBs for

57.6.RNC CS Streaming Services with
DL Rate of 57.6 Kbit/s for
RNC

BSC6900 UMTS
67202748 VS.RB.CS.Str.UL. Average Number of RBs for

57.6.RNC CS Streaming Services with
UL Rate of 57.6 Kbit/s for
RNC
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
VS.RB.CS.Str.DL. WRFD-010502 Streaming QoS Class

57.6.RNC
VS.RB.CS.Str.UL. WRFD-010502 Streaming QoS Class

57.6.RNC
1.10.17.5 Counters Related to the Average Number of CS Conversational Service

RBs

BSC6900 UMTS
Counters
67202766 VS.RB.CS.Conv.DL. Average Number of RBs for

64.RNC CS Conversational Services
RNC
67202778 VS.RB.CS.Conv.UL. Average Number of RBs for

64.RNC CS Conversational Services
RNC
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
VS.RB.CS.Conv.DL. WRFD-010501 Conversational QoS Class

64.RNC
VS.RB.CS.Conv.UL. WRFD-010501 Conversational QoS Class

64.RNC
1.10.17.6 Number of DCH-to-HSDPA Directed Retry Attempts

BSC6900 UMTS
Counters
67192444 VS.DRD.RB.D2H.Att.RNC Number of DCH-to-HSDPA

Directed Retry Attempts for
RNC
Description
This counter provides the number of directed retry attempts from DCH to HSDPA in the RNC.
Measurement point
when the RNC sends the UE a RADIO BEARER SETUP message during the RAB assignment
procedure for the directed retry from DCH to HSDPA.
Figure 1-256 RB setup procedure (successful operation)
when the RNC sends the UE a RADIO BEARER RECONFIGURATION message during the
RAB assignment procedure for the directed retry from DCH to HSDPA.

BSC6900 UMTS
Figure 1-257 RB reconfiguration procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.DRD.RB.D2H.Att.RNC WRFD-01061112 HSDPA DRD

WRFD-02040001 Intra System Direct Retry
1.10.17.7 Number of Successful DCH-to-HSDPA Directed Retry
Counters
67192445 VS.DRD.RB.D2H.Succ.RN Number of Successful DCH-

C to-HSDPA Directed Retry
for RNC

BSC6900 UMTS
Description
This counter provides the number of times that the directed retry from DCH to HSDPA succeeds
in the RNC.
Measurement point
when the RNC receives from the UE a RADIO BEARER SETUP COMMPLETE message
during the RAB assignment procedure for the directed retry from DCH to HSDPA.
when the RNC receives from the UE a RADIO BEARER RECONFIGURATION
COMMPLETE message during the RAB assignment procedure for the directed retry from DCH
to HSDPA.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DRD.RB.D2H.Succ.RN WRFD-01061112 HSDPA DRD

C WRFD-02040001 Intra System Direct Retry
1.10.17.8 Counters Related to the Average Number of PS R99 Streaming Service

RBs

BSC6900 UMTS
Counters
67202601 VS.RB.PS.Str.DL. Average Number of RBs for

256.384.RNC PS R99 Streaming Services
with DL Rate of 256 Kbit/s or
384 Kbit/s for RNC
67202604 VS.RB.PS.Str.DL.144.RNC Average Number of RBs for

PS R99 Streaming Services
for RNC

for RNC

RNC

RNC

RNC

RNC
67202625 VS.RB.PS.Str.UL.144.RNC Average Number of RBs for

for RNC

for RNC

RNC

BSC6900 UMTS

RNC

RNC

RNC
67202622 VS.RB.PS.Str.UL. Average Number of RBs for

256.384.RNC PS R99 Streaming Services
with UL Rate of 256 Kbit/s or
384 Kbit/s for RNC
Description
These counters provide the average number of RBs for PS P99 streaming services in the uplink
or downlink.
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
VS.RB.PS.Str.DL. WRFD-010502 Streaming QoS Class

256.384.RNC
VS.RB.PS.Str.DL.144.RNC WRFD-010502 Streaming QoS Class

BSC6900 UMTS
VS.RB.PS.Str.UL.144.RNC WRFD-010502 Streaming QoS Class
VS.RB.PS.Str.UL. WRFD-010502 Streaming QoS Class

256.384.RNC
1.10.18 Measurement of relocation per DRNC

(Relocation.Drnc.RNC)
Overview
TRNC relocation involves two stages: TRNC relocation preparation and TRNC relocation
execution.
The TRNC relocation preparation involves the following messages: RELOCATION

REQUEST , RELOCATION REQUEST ACKNOWLEDGE , and RELOCATION FAILURE .
If the resource allocation for TRNC relocation succeeds, the TRNC sends a RELOCATION
REQUEST ACKNOWLEDGE to the CN. If the resource allocation for TRNC relocation fails,
the TRNC sends a RELOCATION FAILURE with the cause value to the CN.
TRNC relocation execution is a procedure in which the TRNC receives a RELOCATION

COMMIT from the SRNC or receives the reconfiguration response from the UE after successful
relocation preparation.
If the preparation procedure indicates that the relocation is a "UE not Involved" relocation, the
TRNC receives a RELOCATION COMMIT from the SRNC after successful relocation
preparation. If the preparation procedure indicates that the relocation is a "UE Involved"
relocation, the TRNC receives the reconfiguration response from the UE after successful
relocation preparation.
The reconfiguration procedure involves the following messages: RADIO BEARER SETUP
COMPLETE , RADIO BEARER RECONFIGURATION COMPLETE , RADIO BEARER

BSC6900 UMTS
RELEASE COMPLETE , TRANSPORT CHANNEL RECONFIGURATION COMPLETE ,

and PHYSICAL CHANNEL RECONFIGURATION COMPLETE .
Counters
Description
67175893 VS.DRELOC.FailE Number of Failed Earlier than

xec.Cong Relocation V900R011
Executions for
TRNC (Resources
Unavailable)
67175894 VS.DRELOC.FailE Number of Failed Earlier than

xec.Unsp Relocation V900R011
Executions for
TRNC (Protocol
Cause)
67190207 VS.DRELOC.FailP Number of Failed Earlier than

rep.IuRel Relocation V900R011
Preparations Due to
Reception of IU
Release Command
for TRNC

rep.NAS Relocation V900R011
Preparations for
TRNC (NAS Cause)

rep.RNL Relocation V900R011
Preparations for
TRNC (Radio
Network Layer
Cause)

rep.TNL Relocation V900R011
Preparations for
TRNC (Transport
Layer Cause)
67190208 VS.TRELOC.AttE Number of Earlier than

xecUEInvol Relocation V900R011
Execution Attempts
for TRNC (UE
Involved)

BSC6900 UMTS

Description
67190209 VS.TRELOC.AttE Number of Earlier than

xecUENotInvol Relocation V900R011
Execution Attempts
for TRNC (UE Not
Involved)
67190212 VS.TRELOC.Suc- Number of Earlier than

cExecUENotInvol Successful V900R011
Relocation
Executions for
TRNC (UE Not
Involved)
67190213 VS.TRELOC.Suc- Number of Earlier than

cExecUEInvol Successful V900R011
Relocation
Executions for
TRNC (UE
Involved)
67191091 RELOC.AttResAl- Number of PS Earlier than

locUEInvolPS Relocation Resource V900R011
Allocation Attempts
for TRNC (UE
Involved)
67191092 RELOC.AttResAl- Number of PS Earlier than

locUENotInvolPS Relocation Resource V900R011
Allocation Attempts
for TRNC (UE Not
Involved)
67191097 RELOC.SuccResAl Number of Earlier than

locUEInvolPS Successful PS V900R011
Relocation Resource
Allocations for
TRNC (UE
Involved)

locUENotInvolPS Successful PS V900R011
Relocation Resource
Allocations for
TRNC (UE Not
Involved)

BSC6900 UMTS

Description
67191099 RELOC.FailResAll Number of Failed PS Earlier than

ocUEInvolPS.Ci- Relocation V900R011
phUnSupp Preparations for
TRNC (UE
Involved)
(Requested
Ciphering and/or
Integrity Protection
Algorithms Not
Supported)

ocUENotInvolPS.C Relocation V900R011
iphUnSupp Preparations for
TRNC (UE Not
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)

ocUEInvolPS.Re- Relocation V900R011
sUnavail Preparations for
TRNC (UE
Involved) (No
Resources
Available)

ocUENotInvolPS.R Relocation V900R011
esUnavail Preparations for
TRNC (UE Not
Involved) (No
Resources
Available)
67191107 RELOC.AttResAl- Number of CS Earlier than

locUEInvolCS Relocation Resource V900R011
Allocation Attempts
for TRNC (UE
Involved)
67191108 RELOC.AttResAl- Number of CS Earlier than

locUENotInvolCS Relocation Resource V900R011
Allocation Attempts
for TRNC (UE Not
Involved)

BSC6900 UMTS

Description

locUEInvolCS Successful CS V900R011
Relocation Resource
Allocations for
TRNC (UE
Involved)

locUENotInvolCS Successful CS V900R011
Relocation Resource
Allocations for
TRNC (UE Not
Involved)
67191115 RELOC.FailResAll Number of Failed CS Earlier than

ocUEInvolCS.Ci- Relocation V900R011
TRNC (UE
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)

ocUENotInvolCS.C Relocation V900R011
iphUnSupp Preparations for
TRNC (UE Not
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)

ocUENotInvolCS.R Relocation V900R011
esUnavail Preparations for
TRNC (UE Not
Involved) (No
Resources
Available)
73423643 VS.DRELOC.FailP Number of Failed V900R014

rep.NodeBReHost Relocation
Preparations for
TRNC (NodeB
Rehoming)

BSC6900 UMTS

Description
73424478 VS.TRELOC.Suc- Number of V900R014

cExecUEInvolCS Successful CS
Relocations for
TRNC (UE
Involved)

cExecUEInvolPS Successful PS
Relocations for
TRNC (UE
Involved)

cExecUENotIn- Successful CS
volCS Relocations for
TRNC (UE Not
Involved)

cExecUENotIn- Successful PS
volPS Relocations for
TRNC (UE Not
Involved)
None
1.10.18.1 Counters Related to the Number of Failed Relocation Executions for

Different Causes for TRNC
Counters
67175893 VS.DRELOC.FailExec.Con Number of Failed Relocation

g Executions for TRNC
(Resources Unavailable)
67175894 VS.DRELOC.FailExec.Uns Number of Failed Relocation

p Executions for TRNC
(Protocol Cause)

BSC6900 UMTS
Description
These counters provide the number of failed relocation executions in the TRNC according to
different failure causes.
Measurement point
The measurement is triggered at point A as shown in the following figure. Before the relocation
is complete and after the resource allocation for relocation is complete, the TRNC measures the
related counter according to different failure causes when sending a RRC CONNECTION
RELEASE message to the UE.
Figure 1-260 Failed TRNC relocation execution procedure
Formula
None
Unit
None
Related Features
VS.DRELOC.FailExec.Con WRFD-020605 SRNS Relocation

g Introduction Package

BSC6900 UMTS
VS.DRELOC.FailExec.Uns WRFD-020605 SRNS Relocation

p Introduction Package
1.10.18.2 Number of Failed Relocation Resource Allocations Due to Reception of

IU Release Command for TRNC
Counters
67190207 VS.DRELOC.FailPrep.IuR- Number of Failed Relocation

el Preparations Due to
Reception of IU Release
Command for TRNC
Description
This counter provides the number of failed relocation preparations due to the reception of IU
RELEASE COMMAND message from the CN during the relocation.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the TRNC
receives an IU RELEASE COMMAND message from the CN during the relocation preparation,
the relocation preparation fails. In this case, the TRNC measures the counter.
Figure 1-261 Failed resource allocation for TRNC relocation due to reception of IU release
command

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DRELOC.FailPrep.IuR- WRFD-020605 SRNS Relocation

el Introduction Package
1.10.18.3 Number of Failed Relocation Resource Allocations for TRNC
Counters
67175881 VS.DRELOC.FailPrep.NAS Number of Failed Relocation

Preparations for TRNC
(NAS Cause)
67175879 VS.DRELOC.FailPrep.RNL Number of Failed Relocation

(Radio Network Layer
Cause)
67175880 VS.DRELOC.FailPrep.TNL Number of Failed Relocation

(Transport Layer Cause)
67191099 RELOC.FailResAllocUEInv Number of Failed PS

olPS.CiphUnSupp Relocation Preparations for
TRNC (UE Involved)
(Requested Ciphering and/or
Algorithms Not Supported)
67191100 RELOC.FailResAllocUENo Number of Failed PS

tInvolPS.CiphUnSupp Relocation Preparations for
TRNC (UE Not Involved)

BSC6900 UMTS
67191101 RELOC.FailResAllocUEInv Number of Failed PS

olPS.ResUnavail Relocation Preparations for
TRNC (UE Involved) (No
Resources Available)
67191102 RELOC.FailResAllocUENo Number of Failed PS

tInvolPS.ResUnavail Relocation Preparations for
(No Resources Available)
67191115 RELOC.FailResAllocUEInv Number of Failed CS

olCS.CiphUnSupp Relocation Preparations for
TRNC (UE Involved)
67191116 RELOC.FailResAllocUENo Number of Failed CS

tInvolCS.CiphUnSupp Relocation Preparations for
67191117 RELOC.FailResAllocUENo Number of Failed CS

tInvolCS.ResUnavail Relocation Preparations for
73423643 VS.DRELOC.FailPrep.No- Number of Failed Relocation

deBReHost Preparations for TRNC
(NodeB Rehoming)
Description
These counters provide the numbers of failed relocation resource allocations for the TRNC based
on failure causes.
Measurement point
The measurement is triggered at point A as shown in the figure. During a relocation preparation,
when the relocation resource allocation fails, the TRNC sends a RELOCATION FAILURE
message to the CN. In this case, the TRNC measures the related counter based on failure causes.

BSC6900 UMTS
Figure 1-262 Failed resource allocation procedure for TRNC relocation
Formula
None
Unit
None
Related Features
VS.DRELOC.FailPrep.NAS WRFD-020605 SRNS Relocation

Introduction Package
VS.DRELOC.FailPrep.RNL WRFD-020605 SRNS Relocation

VS.DRELOC.FailPrep.TNL WRFD-020605 SRNS Relocation

RELOC.FailResAllocUEInv WRFD-020605 SRNS Relocation

olPS.CiphUnSupp Introduction Package
RELOC.FailResAllocUENo WRFD-020605 SRNS Relocation

tInvolPS.CiphUnSupp Introduction Package

olPS.ResUnavail Introduction Package

BSC6900 UMTS

tInvolPS.ResUnavail Introduction Package

olCS.CiphUnSupp Introduction Package

tInvolCS.CiphUnSupp Introduction Package

tInvolCS.ResUnavail Introduction Package
VS.DRELOC.FailPrep.No- WRFD-040202 RNC Node Redundancy

deBReHost WRFD-020605 SRNS Relocation
1.10.18.4 Number of Reconfiguration Completions During Relocation for TRNC

(UE Involved)
Counters
67190208 VS.TRELOC.AttExecUEIn- Number of Relocation

vol Execution Attempts for
TRNC (UE Involved)
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.

BSC6900 UMTS
Figure 1-263 Reconfiguration procedure during the TRNC relocation (UE involved)
Formula
None
Unit
None
Related Features
VS.TRELOC.AttExecUEIn- WRFD-020605 SRNS Relocation

vol Introduction Package
1.10.18.5 Number of Relocation Execution Attempts for TRNC (UE Not Involved)
Counters
67190209 VS.TRELOC.AttExecUE- Number of Relocation

NotInvol Execution Attempts for

BSC6900 UMTS
Description
This counter provides the number of TRNC relocation execution attempts during the relocation
(UE not involved).
Measurement point
The measurement is triggered at point A as shown in the following figure. During the relocation
(UE not involved), the TRNC measures this counter when receiving a RELOCATION COMMIT
message from the SRNC.
Figure 1-264 TRNC relocation execution procedure (UE not involved)
Formula
None
Unit
None
Related Features
VS.TRELOC.AttExecUE- WRFD-020605 SRNS Relocation

NotInvol Introduction Package

BSC6900 UMTS
1.10.18.6 Number of Successful Relocation Executions for TRNC (UE Not Involved)
Counters
67190212 VS.TRELOC.SuccExecUE- Number of Successful

NotInvol Relocation Executions for
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.TRELOC.SuccExecUE- WRFD-020605 SRNS Relocation

NotInvol Introduction Package
1.10.18.7 Number of Successful Relocation Executions for TRNC (UE Involved)
Counters
67190213 VS.TRELOC.SuccExe- Number of Successful

cUEInvol Relocation Executions for
TRNC (UE Involved)
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.

BSC6900 UMTS
Figure 1-266 Reconfiguration procedure during the TRNC relocation (UE involved)
Formula
None
Unit
None
Related Features
VS.TRELOC.SuccExe- WRFD-020605 SRNS Relocation

cUEInvol Introduction Package
1.10.18.8 Number of Relocation Resource Allocation Attempts for TRNC

BSC6900 UMTS
Counters
67191091 RELOC.AttResAllocUEIn- Number of PS Relocation

volPS Resource Allocation
Attempts for TRNC (UE
Involved)
67191092 RELOC.AttResAllocUENo- Number of PS Relocation

tInvolPS Resource Allocation
Attempts for TRNC (UE Not
Involved)
67191107 RELOC.AttResAllocUEIn- Number of CS Relocation

volCS Resource Allocation
Attempts for TRNC (UE
Involved)
67191108 RELOC.AttResAllocUENo- Number of CS Relocation

tInvolCS Resource Allocation
Attempts for TRNC (UE Not
Involved)
Description
These counters provide the numbers of CS or PS relocation resource allocations initiated by the
TRNC based on the relocation type.
Measurement point
The measurement is triggered at point A as shown in the figure. When the TRNC receives a
RELOCATION REQUEST message from the CS domain or PS domain in the CN, the TRNC
measures the related counter based on relocation types.

BSC6900 UMTS
Figure 1-267 TRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
RELOC.AttResAllocUEIn- WRFD-020605 SRNS Relocation

volPS Introduction Package
RELOC.AttResAllocUENo- WRFD-020605 SRNS Relocation

tInvolPS Introduction Package
RELOC.AttResAllocUEIn- WRFD-020605 SRNS Relocation

volCS Introduction Package
RELOC.AttResAllocUENo- WRFD-020605 SRNS Relocation

tInvolCS Introduction Package
1.10.18.9 Number of Successful Relocation Resource Allocations for TRNC

BSC6900 UMTS
Counters
67191097 RELOC.SuccResAllo- Number of Successful PS

cUEInvolPS Relocation Resource
Allocations for TRNC (UE
Involved)
67191098 RELOC.SuccResAllocUE- Number of Successful PS

NotInvolPS Relocation Resource
Not Involved)
67191113 RELOC.SuccResAllo- Number of Successful CS

cUEInvolCS Relocation Resource
Involved)
67191114 RELOC.SuccResAllocUE- Number of Successful CS

NotInvolCS Relocation Resource
Not Involved)
Description
These counters provide the numbers of successful CS or PS relocation resource allocations
initiated by the TRNC based on the relocation type.
Measurement point
The measurement is triggered at point B as shown in the figure. When the relocation resource
allocation is complete, the TRNC sends a RELOCATION REQUEST ACKNOWLEDGE
message to the CS domain or PS domain in the CN. In this case, the TRNC measures the related
counter based on relocation types.

BSC6900 UMTS
Figure 1-268 TRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
RELOC.SuccResAllo- WRFD-020605 SRNS Relocation

cUEInvolPS Introduction Package
RELOC.SuccResAllocUE- WRFD-020605 SRNS Relocation

NotInvolPS Introduction Package
RELOC.SuccResAllo- WRFD-020605 SRNS Relocation

cUEInvolCS Introduction Package
RELOC.SuccResAllocUE- WRFD-020605 SRNS Relocation

NotInvolCS Introduction Package

BSC6900 UMTS
1.10.18.10 Number of Successful TRNC Relocations in the CS Domain and PS

Domain (UE Involved)
Counters
73424478 VS.TRELOC.SuccExe- Number of Successful CS

cUEInvolCS Relocations for TRNC (UE
Involved)
73424479 VS.TRELOC.SuccExe- Number of Successful PS

cUEInvolPS Relocations for TRNC (UE
Involved)
Description
These counters measure the number of successful target RNC (TRNC) relocations.
Measurement point
The measurement is triggered at point B shown in figure 1 when the TRNC sends a
RELOCATION COMPLETE message to the CN upon completing a relocation. In this case,
these counters are measured based on the service type.
Figure 1-269 Reconfiguration during a TRNC relocation (UE Involved)

BSC6900 UMTS
Formula
None
Unit
None
Related Features


1.10.18.11 Number of Successful TRNC Relocations in the CS Domain and PS

Domain (UE Not Involved)
Counters
73424480 VS.TRELOC.SuccExecUE- Number of Successful CS

NotInvolCS Relocations for TRNC (UE
Not Involved)
73424481 VS.TRELOC.SuccExecUE- Number of Successful PS

NotInvolPS Relocations for TRNC (UE
Not Involved)
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features


1.10.19 Measurement of relocation per SRNC

(Relocation.Srnc.RNC)
Overview
SRNC relocation involves two stages: SRNC relocation preparation and SRNC relocation
execution.

BSC6900 UMTS
SRNC relocation preparation involves the following messages: RELOCATION REQUIRED

message, RELOCATION COMMAND message, and RELOCATION FAILURE message.
When the relocation conditions are satisfied, the SRNC sends a RELOCATION REQUIRED
message to the CN. If the SRNC then receives a RELOCATION COMMAND message from
the CN, the relocation preparation succeeds. If the SRNC receives from the CN a RELOCATION
FAILURE message with the failure cause, the relocation preparation fails.
SRNC relocation execution is a procedure in which the SRNC sends a RELOCATION COMMIT
message to the TRNC or initiates a reconfiguration procedure to the UE after successful
preparation. If the preparation procedure indicates that the relocation is a "UE not Involved"
relocation, the SRNC sends a RELOCATION COMMIT message to the TRNC after successful
preparation. If the preparation procedure indicates that the relocation is a "UE Involved"
relocation, the SRNC initiates a reconfiguration procedure to the UE after successful preparation.
The reconfiguration procedure involves the following messages: RADIO BEARER SETUP
message, RADIO BEARER RECONFIGURATION message, RADIO BEARER RELEASE
message, TRANSPORT CHANNEL RECONFIGURATION message, and PHYSICAL
CHANNEL RECONFIGURATION message. If the SRNC receives a RADIO BEARER
SETUP FAILURE message, RADIO BEARER RECONFIGURATION FAILURE message,
RADIO BEARER RELEASE FAILURE message, TRANSPORT CHANNEL
RECONFIGURATION FAILURE message, or PHYSICAL CHANNEL
RECONFIGURATION FAILURE message, the reconfiguration fails.
During the relocation execution, if the SRNC receives an IU RELEASE COMMAND message
with the cause value of "Successful Relocation", "Normal Release", or "Network Optimization",
the relocation execution succeeds.
Counters
Description
67190184 VS.RELOC.AttPre Number of CS Earlier than

pUEInvolCS.Time- Relocation V900R011
Crit Preparation
Attempts for SRNC
(UE Involved) (Time
Critical Relocation)

pUEInvolCS.RF Relocation V900R011
Preparation
Attempts for SRNC
(UE Involved)
(Relocation
Desirable for Radio
Reasons)
67190186 RELOC.AttPre- Number of CS Earlier than

pUEInvolCS Relocation V900R011
Preparation
Attempts for SRNC
(UE Involved)

BSC6900 UMTS

Description
67190187 VS.RELOC.SuccPr Number of Earlier than

epUEInvolCS.Time Successful CS V900R011
Crit Relocation
Preparations for
SRNC (UE
Involved) (Time

epUEInvolCS.RF Successful CS V900R011
Relocation
Preparations for
SRNC (UE
Involved)
(Relocation
Desirable for Radio
Reasons)
67190189 RELOC.SuccPre- Number of Earlier than

pUEInvolCS Successful CS V900R011
Relocation
Preparations for
SRNC (UE
Involved)
67190192 RELOC.FailPrepU Number of Failed CS Earlier than

EInvolCS.CiphUn- Relocation V900R011
Supp Preparations for
SRNC (UE
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)

EInvolCS.Treloc- Relocation V900R011
prepExp Preparations for
SRNC (UE
Involved)
(Trelocprep Expiry)

BSC6900 UMTS

Description

EInvolCS.TgtSy- Relocation V900R011
sUnsupp Preparations for
SRNC (UE
Involved)
(Relocation Not
Supported in Target
RNC or Target
System)

EInvolCS.TgtNo- Relocation V900R011
tAllow Preparations for
SRNC (UE
Involved)
(Relocation Target
Not Allowed)

EInvolCS.ResUna- Relocation V900R011
vail Preparations for
SRNC (UE
Involved) (No
Resources
Available)

EInvolCS.Unsp Relocation V900R011
Preparations for
SRNC (UE
Involved)
(Unspecified
Failure)
67175799 VS.SRELOC.FailE Number of Failed Earlier than

xec.CfgUnsupp Relocation V900R011
Executions During
Reconfiguration for
SRNC
(Configuration
Unsupported)

xec.PhyChFail Relocation V900R011
Executions During
Reconfiguration for
SRNC (Physical
Channel Failure)

BSC6900 UMTS

Description

xec.InvCfg Relocation V900R011
Executions During
Reconfiguration for
SRNC (Invalid
Configuration)

xec.CfgIncomp Relocation V900R011
Executions During
Reconfiguration for
SRNC
(Configuration
Incomplete)

xecPS.Expire SRNC Relocation V900R011
Executions Due to
Timer Expiry for IU
Release Command
for SRNC (PS
Domain)

xecCS.Expire SRNC Relocation V900R011
Executions Due to
Timer Expiry for IU
Release Command
for SRNC (CS
Domain)
67192142 VS.SRELOC.AttE Number of PS Earlier than

xecUENotInvolPS Relocation V900R011
Execution Attempts
for SRNC (UE Not
Involved)
67192143 VS.SRELOC.AttE Number of CS Earlier than

xecUENotInvolCS Relocation V900R011
Execution Attempts
for SRNC (UE Not
Involved)

xec.IuRel Relocation V900R011
Executions Due to
Reception of IU
Release Command
for SRNC

BSC6900 UMTS

Description

pUENotInvolCS.Ti Relocation V900R011
meCrit Preparation
Attempts for SRNC
(UE Not Involved)
(Time Critical
Relocation)

pUENotInvolCS.R Relocation V900R011
F Preparation
Attempts for SRNC
(UE Not Involved)
(Relocation
Desirable for Radio
Reasons)
67191049 RELOC.AttPrepU Number of CS Earlier than

ENotInvolCS Relocation V900R011
Preparation
Attempts for SRNC
(UE Not Involved)

epUENotInvolCS.T Successful CS V900R011
imeCrit Relocation
Preparations for
SRNC (UE Not
Involved) (Time

epUENotInvolCS.R Successful CS V900R011
F Relocation
Preparations for
SRNC (UE Not
Involved)
(Relocation
Desirable for Radio
Reasons)

pUENotInvolCS Successful CS V900R011
Relocation
Preparations for
SRNC (UE Not
Involved)

BSC6900 UMTS

Description

ENotInvolCS.Ci- Relocation V900R011
SRNC (UE Not
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)

ENotInvolCS.Tre- Relocation V900R011
locprepExp Preparations for
SRNC (UE Not
Involved)
(Trelocprep Expiry)

ENotInvolCS.TgtS Relocation V900R011
ysUnsupp Preparations for
SRNC (UE Not
Involved)
(Relocation Not
Supported in Target
RNC or Target
System)

ENotInvolCS.TgtN Relocation V900R011
otAllow Preparations for
SRNC (UE Not
Involved)
(Relocation Target
Not Allowed)

ENotInvolCS.Re- Relocation V900R011
SRNC (UE Not
Involved) (No
Resources
Available)

BSC6900 UMTS

Description

ENotInvolCS.Unsp Relocation V900R011
Preparations for
SRNC (UE Not
Involved)
(Unspecified
Failure)
67191060 VS.RELOC.AttPre Number of PS Earlier than

pUEInvolPS.Time- Relocation V900R011
Crit Preparation
Attempts for SRNC
(UE Involved) (Time

pUENotInvolPS.Ti Relocation V900R011
meCrit Preparation
Attempts for SRNC
(UE Not Involved)
(Time Critical
Relocation)

pUEInvolPS.RF Relocation V900R011
Preparation
Attempts for SRNC
(UE Involved)
(Relocation
Desirable for Radio
Reasons)

pUENotInvolPS.R Relocation V900R011
F Preparation
Attempts for SRNC
(UE Not Involved)
(Relocation
Desirable for Radio
Reasons)
67191064 RELOC.AttPre- Number of PS Earlier than

pUEInvolPS Relocation V900R011
Preparation
Attempts for SRNC
(UE Involved)

BSC6900 UMTS

Description
67191065 RELOC.AttPrepU Number of PS Earlier than

ENotInvolPS Relocation V900R011
Preparation
Attempts for SRNC
(UE Not Involved)

epUEInvolPS.Time Successful PS V900R011
Crit Relocation
Preparations for
SRNC (UE
Involved) (Time

epUENotInvolPS.T Successful PS V900R011
imeCrit Relocation
Preparations for
SRNC (UE Not
Involved) (Time

epUEInvolPS.RF Successful PS V900R011
Relocation
Preparations for
SRNC (UE
Involved)
(Relocation
Desirable for Radio
Reasons)

epUENotInvolPS.R Successful PS V900R011
F Relocation
Preparations for
SRNC (UE Not
Involved)
(Relocation
Desirable for Radio
Reasons)

pUEInvolPS Successful PS V900R011
Relocation
Preparations for
SRNC (UE
Involved)

BSC6900 UMTS

Description

pUENotInvolPS Successful PS V900R011
Relocation
Preparations for
SRNC (UE Not
Involved)
67191072 RELOC.FailPrepU Number of Failed PS Earlier than

EInvolPS.CiphUn- Relocation V900R011
Supp Preparations for
SRNC (UE
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)

ENotInvolPS.Ci- Relocation V900R011
SRNC (UE Not
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)

EInvolPS.Treloc- Relocation V900R011
prepExp Preparations for
SRNC (UE
Involved)
(Trelocprep Expiry)

ENotInvolPS.Tre- Relocation V900R011
locprepExp Preparations for
SRNC (UE Not
Involved)
(Trelocprep Expiry)

BSC6900 UMTS

Description

EInvolPS.TgtSy- Relocation V900R011
SRNC (UE
Involved)
(Relocation Not
Supported in Target
RNC or Target
System)

ENotInvolPS.TgtSy Relocation V900R011
SRNC (UE Not
Involved)
(Relocation Not
Supported in Target
RNC or Target
System)

EInvolPS.TgtNo- Relocation V900R011
tAllow Preparations for
SRNC (UE
Involved)
(Relocation Target
Not Allowed)

ENotInvolPS.TgtN Relocation V900R011
otAllow Preparations for
SRNC (UE Not
Involved)
(Relocation Target
Not Allowed)

EInvolPS.ResUna- Relocation V900R011
vail Preparations for
SRNC (UE
Involved) (No
Resources
Available)

BSC6900 UMTS

Description

ENotInvolPS.Re- Relocation V900R011
SRNC (UE Not
Involved) (No
Resources
Available)

EInvolPS.Unsp Relocation V900R011
Preparations for
SRNC (UE
Involved)
(Unspecified
Failure)

ENotInvolPS.Unsp Relocation V900R011
Preparations for
SRNC (UE Not
Involved)
(Unspecified
Failure)
67192683 VS.SRELOC.AttE Number of CS Earlier than

xecUEInvolCS Relocation V900R011
Execution Attempts
for SRNC (UE
Involved)
67192684 VS.SRELOC.AttE Number of PS Earlier than

xecUEInvolPS Relocation V900R011
Execution Attempts
for SRNC (UE
Involved)
67192685 VS.SRELOC.Suc- Number of Earlier than

cExecUEInvolCS Successful CS V900R011
Relocation
Executions for
SRNC (UE
Involved)

cExecUEInvolPS Successful PS V900R011
Relocation
Executions for
SRNC (UE
Involved)

BSC6900 UMTS

Description

cExecUENonIn- Successful CS V900R011
volCS Relocation
Executions for
SRNC (UE Not
Involved)

cExecUENonIn- Successful PS V900R011
volPS Relocation
Executions for
SRNC (UE Not
Involved)
73423644 RELOC.FailPrepU Number of Failed CS V900R014

EInvolCS.Node- Relocation
BReHost Preparations for
SRNC (UE
Involved) (NodeB
Rehoming)
73423645 RELOC.FailPrepU Number of Failed PS V900R014

EInvolPS.Node- Relocation
BReHost Preparations for
SRNC (UE
Involved) (NodeB
Rehoming)
None
1.10.19.1 Number of Relocation Preparation Attempts Due to Different Causes for

SRNC
Counters
67190184 VS.RELOC.AttPrepUEInvo Number of CS Relocation

lCS.TimeCrit Preparation Attempts for
SRNC (UE Involved) (Time

BSC6900 UMTS
67190185 VS.RELOC.AttPrepUEInvo Number of CS Relocation

lCS.RF Preparation Attempts for
SRNC (UE Involved)
(Relocation Desirable for
Radio Reasons)
67191047 VS.RELOC.AttPrepUENotI Number of CS Relocation

nvolCS.TimeCrit Preparation Attempts for
SRNC (UE Not Involved)
(Time Critical Relocation)
67191048 VS.RELOC.AttPrepUENotI Number of CS Relocation

nvolCS.RF Preparation Attempts for
Radio Reasons)
67191060 VS.RELOC.AttPrepUEInvo Number of PS Relocation

lPS.TimeCrit Preparation Attempts for
67191061 VS.RELOC.AttPrepUENotI Number of PS Relocation

nvolPS.TimeCrit Preparation Attempts for
67191062 VS.RELOC.AttPrepUEInvo Number of PS Relocation

lPS.RF Preparation Attempts for
SRNC (UE Involved)
Radio Reasons)
67191063 VS.RELOC.AttPrepUENotI Number of PS Relocation

nvolPS.RF Preparation Attempts for
Radio Reasons)
Description
These counters provide the numbers of CS or PS relocation preparation attempts (UE involved
or UE not involved) initiated by the SRNC based on different causes.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the SRNC
sends a RELOCATION REQUIRED message to the CN in the CS or PS domain, the SRNC
measures the related counters based on different causes if the relocation request type is "UE
involved" or "UE not involved."

BSC6900 UMTS
Figure 1-271 SRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
VS.RELOC.AttPrepUEInvo WRFD-020605 SRNS Relocation

lCS.TimeCrit Introduction Package

lCS.RF Introduction Package
VS.RELOC.AttPrepUENotI WRFD-020605 SRNS Relocation

nvolCS.TimeCrit Introduction Package

nvolCS.RF Introduction Package

lPS.TimeCrit Introduction Package

nvolPS.TimeCrit Introduction Package

BSC6900 UMTS

lPS.RF Introduction Package

nvolPS.RF Introduction Package
1.10.19.2 Number of Relocation Preparation Attempts for SRNC
Counters
67190186 RELOC.AttPrepUEInvolCS Number of CS Relocation

SRNC (UE Involved)
67191049 RELOC.AttPrepUENotIn- Number of CS Relocation

volCS Preparation Attempts for
67191064 RELOC.AttPrepUEInvolPS Number of PS Relocation

SRNC (UE Involved)
67191065 RELOC.AttPrepUENotIn- Number of PS Relocation

volPS Preparation Attempts for
Description
These counters provide the numbers of CS or PS relocation preparation attempts initiated by the
SRNC based on the relocation type.
Measurement point
The measurement is triggered at point A as shown in the figure. When the SRNC sends a
RELOCATION REQUIRED message to the CS domain or PS domain in the CN, the SRNC
measures the related counter based on relocation types and CN domains.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
RELOC.AttPrepUEInvolCS WRFD-020605 SRNS Relocation

RELOC.AttPrepUENotIn- WRFD-020605 SRNS Relocation

RELOC.AttPrepUEInvolPS WRFD-020605 SRNS Relocation

RELOC.AttPrepUENotIn- WRFD-020605 SRNS Relocation

1.10.19.3 Number of Successful Relocation Preparations Due to Different Causes

for SRNC

BSC6900 UMTS
Counters
67190187 VS.RELOC.SuccPrepUEInv Number of Successful CS

olCS.TimeCrit Relocation Preparations for
67190188 VS.RELOC.SuccPrepUEInv Number of Successful CS

olCS.RF Relocation Preparations for
SRNC (UE Involved)
Radio Reasons)
67191050 VS.RELOC.SuccPrepUENo Number of Successful CS

tInvolCS.TimeCrit Relocation Preparations for
67191051 VS.RELOC.SuccPrepUENo Number of Successful CS

tInvolCS.RF Relocation Preparations for
Radio Reasons)
67191066 VS.RELOC.SuccPrepUEInv Number of Successful PS

olPS.TimeCrit Relocation Preparations for
67191067 VS.RELOC.SuccPrepUENo Number of Successful PS

tInvolPS.TimeCrit Relocation Preparations for
67191068 VS.RELOC.SuccPrepUEInv Number of Successful PS

olPS.RF Relocation Preparations for
SRNC (UE Involved)
Radio Reasons)
67191069 VS.RELOC.SuccPrepUENo Number of Successful PS

tInvolPS.RF Relocation Preparations for
Radio Reasons)
Description
These counters provide the numbers of successful CS or PS relocation preparations (UE involved
or UE not involved) initiated by the SRNC based on different causes.

BSC6900 UMTS
Measurement point
The measurement is triggered at point B as shown in the figure. After the SRNC initiates a
relocation procedure (UE involved or UE not involved), the outgoing relocation preparation
succeeds if the SRNC receives a RELOCATION COMMAND message from the CS domain or
PS domain in the CN. In this case, the SRNC measures the related counter based on relocation
causes, CN domains, and whether the UE is involved.
Formula
None
Unit
None
Related Features
VS.RELOC.SuccPrepUEInv WRFD-020605 SRNS Relocation

olCS.TimeCrit Introduction Package

olCS.RF Introduction Package
VS.RELOC.SuccPrepUENo WRFD-020605 SRNS Relocation

tInvolCS.TimeCrit Introduction Package

BSC6900 UMTS

tInvolCS.RF Introduction Package

olPS.TimeCrit Introduction Package

tInvolPS.TimeCrit Introduction Package

olPS.RF Introduction Package

tInvolPS.RF Introduction Package
1.10.19.4 Number of Successful Relocation Preparations for SRNC
Counters
67190189 RELOC.SuccPrepUEIn- Number of Successful CS

volCS Relocation Preparations for
SRNC (UE Involved)
67191052 RELOC.SuccPrepUENotIn- Number of Successful CS

volCS Relocation Preparations for
67191070 RELOC.SuccPrepUEIn- Number of Successful PS

volPS Relocation Preparations for
SRNC (UE Involved)
67191071 RELOC.SuccPrepUENotIn- Number of Successful PS

volPS Relocation Preparations for
Description
These counters provide the numbers of successful CS or PS relocation preparations initiated by
the SRNC based on the relocation type.
Measurement point
The measurement is triggered at point B as shown in the figure. After the SRNC initiates a
relocation procedure, the outgoing relocation preparation succeeds if the SRNC receives a
RELOCATION COMMAND message from the CS domain or PS domain in the CN. In this
case, the SRNC measures the related counter based on relocation types and CN domains.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
RELOC.SuccPrepUEIn- WRFD-020605 SRNS Relocation

RELOC.SuccPrepUENotIn- WRFD-020605 SRNS Relocation

RELOC.SuccPrepUEIn- WRFD-020605 SRNS Relocation

RELOC.SuccPrepUENotIn- WRFD-020605 SRNS Relocation

1.10.19.5 Number of Failed Relocation Preparations Due to Different Causes for

SRNC

BSC6900 UMTS
Counters
67190192 RELOC.FailPrepUEInvolC Number of Failed CS

S.CiphUnSupp Relocation Preparations for
SRNC (UE Involved)

S.TrelocprepExp Relocation Preparations for
SRNC (UE Involved)
(Trelocprep Expiry)

S.TgtSysUnsupp Relocation Preparations for
SRNC (UE Involved)
(Relocation Not Supported in
Target RNC or Target
System)

S.TgtNotAllow Relocation Preparations for
SRNC (UE Involved)
(Relocation Target Not
Allowed)

S.ResUnavail Relocation Preparations for
SRNC (UE Involved) (No

S.Unsp Relocation Preparations for
SRNC (UE Involved)
(Unspecified Failure)
67191053 RELOC.FailPrepUENotInv Number of Failed CS

olCS.CiphUnSupp Relocation Preparations for

olCS.TrelocprepExp Relocation Preparations for
(Trelocprep Expiry)

BSC6900 UMTS

olCS.TgtSysUnsupp Relocation Preparations for
System)

olCS.TgtNotAllow Relocation Preparations for
Allowed)

olCS.ResUnavail Relocation Preparations for

olCS.Unsp Relocation Preparations for
67191072 RELOC.FailPrepUEInvolPS Number of Failed PS

.CiphUnSupp Relocation Preparations for
SRNC (UE Involved)
67191073 RELOC.FailPrepUENotInv Number of Failed PS

olPS.CiphUnSupp Relocation Preparations for

.TrelocprepExp Relocation Preparations for
SRNC (UE Involved)
(Trelocprep Expiry)

olPS.TrelocprepExp Relocation Preparations for
(Trelocprep Expiry)

BSC6900 UMTS

.TgtSysUnsupp Relocation Preparations for
SRNC (UE Involved)
System)

olPS.TgtSysUnsupp Relocation Preparations for
System)

.TgtNotAllow Relocation Preparations for
SRNC (UE Involved)
Allowed)

olPS.TgtNotAllow Relocation Preparations for
Allowed)

.ResUnavail Relocation Preparations for
SRNC (UE Involved) (No

olPS.ResUnavail Relocation Preparations for

.Unsp Relocation Preparations for
SRNC (UE Involved)

olPS.Unsp Relocation Preparations for

S.NodeBReHost Relocation Preparations for
SRNC (UE Involved)
(NodeB Rehoming)

BSC6900 UMTS

.NodeBReHost Relocation Preparations for
SRNC (UE Involved)
(NodeB Rehoming)
Description
These counters provide the numbers of failed CS or PS relocation preparations (UE involved or
UE not involved) initiated by the SRNC based on different causes.
Measurement point
The measurement is triggered at point A as shown in the figure. After the SRNC initiates a
relocation procedure (UE involved or UE not involved), the outgoing relocation preparation fails
if the SRNC receives a RELOCATION PREPARATION FAILURE message from the CS
domain or PS domain in the CN. In this case, the SRNC measures the related counter based on
failure causes, CN domains, and whether the UE is involved.
Figure 1-275 Failed SRNC relocation preparation procedure
Formula
None

BSC6900 UMTS
Unit
None
Related Features
RELOC.FailPrepUEInvolC WRFD-020605 SRNS Relocation

S.CiphUnSupp Introduction Package

S.TrelocprepExp Introduction Package

S.TgtSysUnsupp Introduction Package

S.TgtNotAllow Introduction Package

S.ResUnavail Introduction Package

S.Unsp Introduction Package
RELOC.FailPrepUENotInv WRFD-020605 SRNS Relocation

olCS.CiphUnSupp Introduction Package

olCS.TrelocprepExp Introduction Package

olCS.TgtSysUnsupp Introduction Package

olCS.TgtNotAllow Introduction Package

olCS.ResUnavail Introduction Package

olCS.Unsp Introduction Package
RELOC.FailPrepUEInvolPS WRFD-020605 SRNS Relocation

.CiphUnSupp Introduction Package

olPS.CiphUnSupp Introduction Package

.TrelocprepExp Introduction Package

olPS.TrelocprepExp Introduction Package

BSC6900 UMTS

.TgtSysUnsupp Introduction Package

olPS.TgtSysUnsupp Introduction Package

.TgtNotAllow Introduction Package

olPS.TgtNotAllow Introduction Package

.ResUnavail Introduction Package

olPS.ResUnavail Introduction Package

.Unsp Introduction Package

olPS.Unsp Introduction Package
RELOC.FailPrepUEInvolC WRFD-040202 RNC Node Redundancy

S.NodeBReHost WRFD-020605 SRNS Relocation
RELOC.FailPrepUEInvolPS WRFD-040202 RNC Node Redundancy

.NodeBReHost WRFD-020605 SRNS Relocation
1.10.19.6 Counters Related to the Number of Failed Relocation Executions During

Reconfiguration for Different Causes for SRNC
Counters
67175799 VS.SRELOC.FailExec.Cfg Number of Failed Relocation

Unsupp Executions During
Reconfiguration for SRNC
(Configuration
Unsupported)
67175800 VS.SRELOC.FailExec.Phy Number of Failed Relocation

ChFail Executions During
(Physical Channel Failure)

BSC6900 UMTS
67175802 VS.SRELOC.FailExec.InvC Number of Failed Relocation

fg Executions During
(Invalid Configuration)
67175803 VS.SRELOC.FailExec.CfgI Number of Failed Relocation

ncomp Executions During
(Configuration Incomplete)
Description
These counters provide the number of failed relocation (UE involved) executions during the
reconfiguration according to different failure causes.
Measurement point
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-276 Failed SRNC relocation procedure during the reconfiguration (UE involved)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SRELOC.FailExec.Cfg WRFD-020605 SRNS Relocation

Unsupp Introduction Package
VS.SRELOC.FailExec.Phy WRFD-020605 SRNS Relocation

ChFail Introduction Package
VS.SRELOC.FailExec.InvC WRFD-020605 SRNS Relocation

fg Introduction Package
VS.SRELOC.FailExec.CfgI WRFD-020605 SRNS Relocation

ncomp Introduction Package
1.10.19.7 Counters Related to the Number of Failed SRNC Relocation Executions

Due to Timer Expiry for IU Release Command for SRNC
Counters
67192140 VS.SRELOC.FailExecPS.E Number of Failed SRNC

xpire Relocation Executions Due
to Timer Expiry for IU
Release Command for SRNC
(PS Domain)
67192141 VS.SRELOC.FailExecCS.E Number of Failed SRNC

xpire Relocation Executions Due
to Timer Expiry for IU
Release Command for SRNC
(CS Domain)
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.

BSC6900 UMTS
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-277 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.

BSC6900 UMTS
Figure 1-278 Failed SRNC relocation execution procedure due to timer expiry for IU release
command (UE involved)
Formula
None
Unit
None
Related Features
VS.SRELOC.FailExecPS.E WRFD-020605 SRNS Relocation

xpire Introduction Package
VS.SRELOC.FailExecCS.E WRFD-020605 SRNS Relocation

xpire Introduction Package
1.10.19.8 Counters Related to the Number of Relocation Execution Attempts for


BSC6900 UMTS
Counters
67192142 VS.SRELOC.AttExecUE- Number of PS Relocation

NotInvolPS Execution Attempts for
67192143 VS.SRELOC.AttExecUE- Number of CS Relocation

NotInvolCS Execution Attempts for
Description
These counters provide the number of relocation execution attempts initiated by the SRNC
during the relocation according to different domain types.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the SRNC
sends a RELOCATION COMMIT message to the TRNC, if the relocation request type is "UE
Not Involved", the SRNC measures the related counter according to different domain types.
Figure 1-279 SRNC relocation execution procedure (UE not involved)
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.SRELOC.AttExecUE- WRFD-020605 SRNS Relocation

VS.SRELOC.AttExecUE- WRFD-020605 SRNS Relocation

1.10.19.9 Number of Failed Relocation Executions Due to Reception of IU Release

Command for SRNC
Counters
67175805 VS.SRELOC.FailExec.IuR- Number of Failed Relocation

el Executions Due to Reception
of IU Release Command for
SRNC
Description
This counter provides the number of failed relocation executions when the SRNC receives an
IU RELEASE COMMAND message from the CN and the cause value contained in the message
is not "Successful Relocation", "Normal Release", or "Network Optimization."
Measurement point
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."

BSC6900 UMTS
Figure 1-280 Failed SRNC relocation execution procedure (reception of IU release command)
Formula
None
Unit
None
Related Features
VS.SRELOC.FailExec.IuR- WRFD-020605 SRNS Relocation

el Introduction Package
1.10.19.10 Counters Related to the Number of Reconfiguration Attempts During

Relocation Execution for SRNC ( UE Involved)

BSC6900 UMTS
Counters
67192683 VS.SRELOC.AttExecUEIn- Number of CS Relocation

volCS Execution Attempts for
SRNC (UE Involved)
67192684 VS.SRELOC.AttExecUEIn- Number of PS Relocation

volPS Execution Attempts for
SRNC (UE Involved)
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
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-281 Reconfiguration procedure during the SRNC relocation (UE involved)
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.SRELOC.AttExecUEIn- WRFD-020605 SRNS Relocation

VS.SRELOC.AttExecUEIn- WRFD-020605 SRNS Relocation

1.10.19.11 Number of Successful Relocation Executions for SRNC
Counters
67192685 VS.SRELOC.SuccExe- Number of Successful CS

cUEInvolCS Relocation Executions for
SRNC (UE Involved)
67192686 VS.SRELOC.SuccExe- Number of Successful PS

cUEInvolPS Relocation Executions for
SRNC (UE Involved)
67192687 VS.SRELOC.SuccExecUE- Number of Successful CS

NonInvolCS Relocation Executions for
67192688 VS.SRELOC.SuccExecUE- Number of Successful PS

NonInvolPS Relocation Executions for
Description
These counters provide the numbers of successful relocation executions (UE involved or UE
not involved) initiated by the SRNC based on different CN domains.
Measurement point
The measurement is triggered at point A as shown in the figure. During the relocation (UE
involved or UE not involved), when the SRNC receives an IU RELEASE COMMAND message
with the cause value "Successful Relocation", "Normal Release", or "Network Optimization",
the relocation succeeds. In this case, the SRNC measures the related counter based on CN
domains and whether the UE is involved.

BSC6900 UMTS
Figure 1-282 Successful SRNC relocation procedure
Formula
None
Unit
None
Related Features
VS.SRELOC.SuccExe- WRFD-020605 SRNS Relocation

VS.SRELOC.SuccExe- WRFD-020605 SRNS Relocation

VS.SRELOC.SuccExecUE- WRFD-020605 SRNS Relocation

NonInvolCS Introduction Package
VS.SRELOC.SuccExecUE- WRFD-020605 SRNS Relocation

NonInvolPS Introduction Package

BSC6900 UMTS
1.10.20 RLC measurement per RNC(RLC.RNC)
Overview
This function subset measures the number of packets sent, received, discarded, and retransmitted
at the RLC layer.
Counters
Description
67202533 RLC.NbrBlocksSe Number of PDUs Earlier than

nt.TM Sent by TM RLCs for V900R011
RNC

nt.AM Sent by AM RLCs V900R011
for RNC

nt.UM Sent by UM RLCs V900R011
for RNC
67202536 RLC.NbrBlocksRe Number of PDUs Earlier than

ceived.TM Received by TM V900R011
RLCs for RNC

ceived.AM Received by AM V900R011
RLCs for RNC

ceived.UM Received by UM V900R011
RLCs for RNC
67202539 RLC.Discarded- Number of PDUs Earlier than

BlocksByRNC Discarded by RLCs V900R011
for RNC
67202540 RLC.Retransmit- Number of PDUs Earlier than

tedBlocksToUE Retransmitted by V900R011
RLCs for RNC
67204246 RLC.NbrBlocksRe Number of PDUs V900R012

ceived.AM.1 with the Size Smaller
than 336 bit
Received by RLCs In
Acknowledged
Mode Carried by
TRB

BSC6900 UMTS

Description
67204247 RLC.NbrBlocksRe Number of PDUs V900R012

ceived.AM.2 with the Size Greater
than or Equal to 336
bit Received by
RLCs In
Acknowledged
Mode Carried by
TRB
None
1.10.20.1 Number of Packets Sent at the RLC Layer
Counters
67202533 RLC.NbrBlocksSent.TM Number of PDUs Sent by TM

RLCs for RNC
67202534 RLC.NbrBlocksSent.AM Number of PDUs Sent by

AM RLCs for RNC
67202535 RLC.NbrBlocksSent.UM Number of PDUs Sent by

UM RLCs for RNC
Description
These counters provide the number of packets sent in TM, AM, and UM modes at the RLC layer
in the RNC.
Measurement point
These counters are incremented by one each time the RLC layer on the RNC side sends a packet.
Formula
None
Unit
packet

BSC6900 UMTS
Related Features
RLC.NbrBlocksSent.TM WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
RLC.NbrBlocksSent.AM WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
RLC.NbrBlocksSent.UM WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.10.20.2 Number of Packets Received at the RLC Layer
Counters
67202536 RLC.NbrBlocksReceived.T Number of PDUs Received

M by TM RLCs for RNC
67202537 RLC.NbrBlocksReceived.A Number of PDUs Received

M by AM RLCs for RNC
67202538 RLC.NbrBlocksReceived.U Number of PDUs Received

M by UM RLCs for RNC
Description
These counters provide the number of packets received by the RLC layers in TM, AM, and UM
modes on the RNC side.
Measurement point
These counters are incremented by one each time the RLC layer on the RNC receives a packet.
Formula
None

BSC6900 UMTS
Unit
packet
Related Features
RLC.NbrBlocksReceived.T WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

M Connection and Radio
and Release
RLC.NbrBlocksReceived.A WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
RLC.NbrBlocksReceived.U WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.10.20.3 Number of Packets Discarded by All RLCs in RNC
Counters
67202539 RLC.DiscardedBlocks- Number of PDUs Discarded

ByRNC by RLCs for RNC
Description
This measurement item takes statistics of the number of packets discarded by all the RLCs in
the RNC.
Measurement point
The measurement is triggered when an RLC discards a packet.
Formula
None
Unit
packet

BSC6900 UMTS
Related Features
RLC.DiscardedBlocks- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

ByRNC Connection and Radio
and Release
1.10.20.4 Number of Packets Retransmitted by All RLCs in AM Mode in RNC
Counters
67202540 RLC.RetransmittedBlock- Number of PDUs

sToUE Retransmitted by RLCs for
RNC
Description
This counter provides the number of PDUs that are retransmitted by the RLC in AM mode in
the RNC. It excludes the number of PDUs that are automatically retransmitted by the RLC.
Measurement point
The measurement is triggered when an RLC in AM mode retransmits a packet.
Formula
None
Unit
packet
Related Features
RLC.RetransmittedBlock- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

sToUE Connection and Radio
and Release

BSC6900 UMTS
1.10.20.5 Number of PDUs with the Size Smaller than 336 bit Received by RLCs In
Acknowledged Mode Carried by TRB
Counters
67204246 RLC.NbrBlocksReceived.A Number of PDUs with the

M.1 Size Smaller than 336 bit
Received by RLCs In
Acknowledged Mode
Carried by TRB
Description
This counter provides the number of PDUs with the size smaller than 336 bit received by RLCs
in acknowledged mode carried by the traffic radio bearer (TRB).
Measurement point
This counter is measured at the RNC when RLCs in acknowledge mode carried by the TRB
receive a PDU with the size smaller than 336 bit.
Formula
None
Unit
packet
Related Features
RLC.NbrBlocksReceived.A WRFD-010695 UL Layer 2 Improvement

M.1
1.10.20.6 Number of PDUs with the Size Greater than or Equal to 336 bit Received
by RLCs In Acknowledged Mode Carried by TRB

BSC6900 UMTS
Counters
67204247 RLC.NbrBlocksReceived.A Number of PDUs with the

M.2 Size Greater than or Equal to
336 bit Received by RLCs In
Acknowledged Mode
Carried by TRB
Description
This counter provides the number of PDUs with the size greater than or equal to 336 bit received
by RLCs in acknowledged mode carried by the traffic radio bearer (TRB).
Measurement point
This counter is measured at the RNC when RLCs in acknowledge mode carried by the TRB
receive a PDU with the size greater than or equal to 336 bit.
Formula
None
Unit
packet
Related Features
RLC.NbrBlocksReceived.A WRFD-010695 UL Layer 2 Improvement

M.2
1.10.21 Measurement related to IMS(RNC.IMS)

Overview
A new CN domain, known as IMS domain, is introduced into the system architecture of 3GPP
R5.
With the UTRAN PS features and PS CN, the IMS domain provides various standard services,
such as packet call and IP multimedia conference. In addition, it can also provide real time or
approximate real time voice, data and video communications, such as PTT service.
Seen from the access network, the IMS service is carried by two PS RABs. One carries the
Session Initiation Protocol (SIP) of the IMS signaling, and the other carries IMS application.
Both RABs have their own service features.

BSC6900 UMTS
Counters
Description
67202541 VS.RABCmb.Num Number of IMS_PoC Earlier than

IMS.Str8.8 Users in the Statistic V900R011
Period for RNC
67202542 VS.RABCmb.Num Number of Earlier than

IMS.Con8.8 IMS_VoIP Users in V900R011
the Statistic Period
for RNC
67202546 VS.IMS.NumSigUs Number of IMS Earlier than

er Users in the Statistic V900R011
Period for RNC
67203417 VS.RABCmb.IM- Number of IMS Earlier than

SSigCon16.42.8 Users in the Statistic V900R011
Period for RNC
(Signaling at 16kbit/s
and Services at
42.8kbit/s)

SSigCon16.32 Users in the Statistic V900R011
Period for RNC
and Services at
32kbit/s)

Period for RNC
and Services at
64kbit/s)

Period for RNC
and Services at
16kbit/s)

Period for RNC
and Services at
32kbit/s)

BSC6900 UMTS

Description

Period for RNC
and Services at
16kbit/s)
None
1.10.21.1 Mean Number of UEs Setting Up Different IMS Services
Counters
67202541 VS.RABCmb.NumIMS.Str8 Number of IMS_PoC Users

.8 in the Statistic Period for
RNC
67202542 VS.RABCmb.NumIMS.Con Number of IMS_VoIP Users

8.8 in the Statistic Period for
RNC
67203417 VS.RABCmb.IMSSig- Number of IMS Users in the

Con16.42.8 Statistic Period for RNC
(Signaling at 16kbit/s and
Services at 42.8kbit/s)

Con16.32 Statistic Period for RNC
Services at 32kbit/s)



BSC6900 UMTS


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
VS.RABCmb.NumIMS.Str8 WRFD-010617 VoIP over HSPA/HSPA+

.8
VS.RABCmb.NumIMS.Con WRFD-010617 VoIP over HSPA/HSPA+

8.8
VS.RABCmb.IMSSig- WRFD-010617 VoIP over HSPA/HSPA+

Con16.42.8

Con16.32

Con16.64

BSC6900 UMTS

Con8.16

Con8.32

Con16.16
1.10.21.2 Number of UEs Setting Up IMS Services
Counters
67202546 VS.IMS.NumSigUser Number of IMS Users in the

Statistic Period for RNC
Description
This measurement item provides the number of UEs setting up IMS services in the RNC.
Measurement point
The RNC periodically takes samples from the number of UEs that setting up IMS services every
five seconds. At the end of the measurement period, the RNC divides the accumulated number
by the number of samples to obtain the mean number of UEs setting up IMS services.
Formula
None
Unit
None
Related Features
VS.IMS.NumSigUser WRFD-010617 VoIP over HSPA/HSPA+

BSC6900 UMTS
1.10.22 RRC connection release measurement per RNC

(RRC.Rel.RNC)
Overview
When the RNC release a RRC connection, it sends a RRC CONNECTION RELEASE message
to the UE to release the resources related to the UE. The RRC connection release measurement
counts the RRC connection release messages of the entire RNC by the RRC connection release
cause.
Counters
Description
67174454 VS.RRC.AttConnR Number of RRC Earlier than

el.RNC Connection Releases V900R011
for RNC

el.Norm.RNC Connection Releases V900R011
due to Normal Event
for RNC

el.Cong.RNC Connection Releases V900R011
due to Congestion for
RNC

el.Preempt.RNC Connection Releases V900R011
due to Preemption
for RNC

el.UsrInact.RNC Connection Releases V900R011
due to User Inactivity
for RNC

el.ReEstRej.RNC Connection Releases V900R011
due to Re-
establishment Reject
for RNC

el.DSCR.RNC Connection Releases V900R011
due to Directed
Signaling
Connection Re-
establishment for
RNC

BSC6900 UMTS

Description

el.Unspec.RNC Connection Releases V900R011
due to Unspecified
Causes for RNC
73421937 VS.RRC.AttConRe Number of RRC V900R012

l.SCRI.DF2P.NoRe Releases Due to
ply.RNC Failure in the UE
State Transition to
CELL_PCH
Triggered by
Signaling
Connection Release
Indication

el.DSCR.SRNC Connection Releases
Triggered by SRNC
Due to DSCR

el.DSCR.DRNC Connection Releases
Triggered by DRNC
Due to DSCR
None
1.10.22.1 Number of RRC Connection Releases
Counters
67174454 VS.RRC.AttConnRel.RNC Number of RRC Connection

Releases for RNC
Description
When the network side needs to release a RRC connection because of a certain cause, for
example, the call ends, the RRC connection sends a RRC CONNECTION RELEASE message
to the UE. This counter provides the number of RRC CONNECTION RELEASE messages sent
by the RNC to the UE.

BSC6900 UMTS
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
VS.RRC.AttConnRel.RNC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.10.22.2 Counters Related to the Number of RRC Connection Releases due to

Different Causes

BSC6900 UMTS
Counters
67174641 VS.RRC.AttConnRel.Norm. Number of RRC Connection

RNC Releases due to Normal
Event for RNC
67190072 VS.RRC.AttConnRel.Cong. Number of RRC Connection

RNC Releases due to Congestion
for RNC
67190073 VS.RRC.AttConnRel.Preem Number of RRC Connection

pt.RNC Releases due to Preemption
for RNC
67190074 VS.RRC.AttConnRel.UsrIn Number of RRC Connection

act.RNC Releases due to User
Inactivity for RNC
67190075 VS.RRC.AttConnRel.ReEst Number of RRC Connection

Rej.RNC Releases due to Re-
establishment Reject for
RNC
67190076 VS.RRC.AttConnRel.DSCR Number of RRC Connection

.RNC Releases due to Directed
Signaling Connection Re-
establishment for RNC
67174647 VS.RRC.AttConnRel.Unspe Number of RRC Connection

c.RNC Releases due to Unspecified
Causes for RNC
Description
These counters provide the number of RRC CONNECTION RELEASE messages with certain
causes sent by the RNC to the UE.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC initiates the
RRC connection release procedure, the RNC sends a RRC CONNECTION RELEASE message
to the UE. These counters are measured on the RNC side when a RRN CONNECTION
RELEASE message with the corresponding cause is sent to the UE. For details, see section
10.3.3.32 in 3GPP TS 25.331.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RRC.AttConnRel.Norm. WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

RNC Connection and Radio
and Release
VS.RRC.AttConnRel.Cong. WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

RNC Connection and Radio
and Release
VS.RRC.AttConnRel.Preem WRFD-010505 Queuing and Pre-Emption

pt.RNC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release

BSC6900 UMTS
VS.RRC.AttConnRel.UsrIn WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

act.RNC Connection and Radio
and Release
VS.RRC.AttConnRel.ReEst WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Rej.RNC Connection and Radio
and Release
VS.RRC.AttConnRel.DSCR WRFD-021400 Direct Signaling Connection

.RNC WRFD-010510 Re-establishment (DSCR)
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RRC.AttConnRel.Unspe WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

c.RNC Connection and Radio
and Release
1.10.22.3 Number of RRC Releases Due to Failure in the UE State Transition to

CELL_PCH Triggered by Signaling Connection Release Indication
Counters
73421937 VS.RRC.AttConRel.SCRI.D Number of RRC Releases

F2P.NoReply.RNC Due to Failure in the UE State
Transition to CELL_PCH
Triggered by Signaling
Connection Release
Indication
Description
This counter provides the number of times that an RRC connection is released because no UE
response is received after the RNC sends a RADIO BEAR RECONFIGURATION or
PHYSICAL CHANNEL RECONFIGURATION message to the UE, instructing the UE to
transfer to the CELL_PCH state.
Measurement point
The measurement is triggered at point A as shown in the figure. After receiving the
SIGNALLING CONNECTION RELEASE INDICATION message from the UE, the RNC

BSC6900 UMTS
sends a RADIO BEAR RECONFIGURATION or PHYSICAL CHANNEL

RECONFIGURATION message to the UE, instructing the UE to transfer to the CELL_PCH
state. If no response from the UE is received before the timer expires, the RNC releases the RRC
connection and measure this counter.
Figure 1-285 RB reconfiguration or Physical Channel reconfiguration failure procedure (UE no

response)
Formula
None
Unit
None
Related Features
VS.RRC.AttConRel.SCRI.D WRFD-020500 Enhanced Fast Dormancy

F2P.NoReply.RNC
1.10.22.4 Number of RRC Connection Releases Triggered by SRNC Due to DSCR

BSC6900 UMTS
Counters

.SRNC Releases Triggered by SRNC
Due to DSCR
Description
This counter provides the number of RRC CONNECTION RELEASE messages sent by the
SRNC to the UE because of Directed Signaling Connection Re-establishment (DSCR).
Measurement point
an RRC CONNECTION RELEASE message because of DSCR.
Formula
None
Unit
None

BSC6900 UMTS
Related Features

.SRNC WRFD-010510 Re-establishment (DSCR)
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.10.22.5 Number of RRC Connection Releases Triggered by DRNC Due to DSCR
Counters

.DRNC Releases Triggered by
DRNC Due to DSCR
Description
This counter provides the number of RRC CONNECTION RELEASE messages sent by the
DRNC to the UE because of Directed Signaling Connection Re-establishment (DSCR).
Measurement point
The measurement is triggered at point A as shown in the figure, when the DRNC sends the UE
an RRC CONNECTION RELEASE message because of DSCR.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

.DRNC WRFD-010510 Re-establishment (DSCR)
3.4/6.8/13.6/27.2Kbps RRC
and Release

BSC6900 UMTS
1.10.23 RRC connection setup measurement per RNC

(RRC.Setup.RNC)
Overview
When an UE needs to access the network, setting up the RRC connection is the first step. From
the cell where the UE is located, the UE sends a RRC CONNECTION REQUEST message to
request network access.
After receiving the RRC CONNECTION REQUEST message, the RNC initiates the admission
procedure and allocates relevant resources to the UE. Following successful allocation of
resources, the RNC sends a RRC CONNECTION SETUP message to the UE and waits for a
RRC CONNECTION SETUP COMPLETE message, a response message from the UE. When
the RNC receives a RRC CONNECTION SETUP COMPLETE message, the procedure for RRC
connection setup is finished. For more details, see 3GPP TS 25.331.
The number of RRC connection setup attempts and rejects does not include service-based
redirections, inter-RAT and inter-frequency distance-based redirections, and macro & micro
joint inter-frequency redirections.
During the resource admission and radio link setup process, if DRD is configured when resource
admission and radio link setup fail and the configured DRD succeeds, the measurement is
triggered in the target cell for the UE. If the configured DRD fails, the measurement is triggered
in the source cell for the UE.
Note that the measurement is not triggered for RRC CONNECTION REQUEST messages
retransmitted by the UE.
The following figure shows the measurement points of the counters.

BSC6900 UMTS
Figure 1-288 Flow chart of RRC connection setup

BSC6900 UMTS
A VS.RRC.AttConnEstab.RNC,
VS.RRC.AttConnEstab.Msg.RNC,
VS.RRC.AttConnEstab.CellDCH.RNC,
VS.RRC.AttConnEstab.CellFACH.RNC
B See:RRC.Setup.Cell
C VS.RRC.SuccConnEstab.RNC,
VS.RRC.SuccConnEstab.CellFACH.RNC,
VS.RRC.SuccConnEstab.CellDCH.RNC
D See:RRC.Setup.Cell
E~L See:RRC.SetupFail.Cell
Counters
Description

stab.RNC Connection Requests V900R011
Processed by RNC
67174449 VS.RRC.AttConnE Total Number of Earlier than

stab.Msg.RNC RRC Connection V900R011
Requests Received
by RNC

stab.CellDCH.RNC Connection Requests V900R011
for RNC (UE Target
State of
CELL_DCH)

stab.CellFACH.RN Connection Requests V900R011
C for RNC (UE Target
State of
CELL_FACH)

Estab.RNC Successful RRC V900R011
Connection
Establishments for
RNC

BSC6900 UMTS

Description

Estab.CellFACH.R Successful RRC V900R011
NC Connection
Establishments on
CELL_FACH

Estab.CellDCH.RN Successful RRC V900R011
C Connection
Establishments on
CELL_DCH
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
1.10.23.1 Counters Related to the Number of RRC Connection Requests Processed

by RNC
Counters
67174450 VS.RRC.AttConnEstab.RN Number of RRC Connection

C Requests Processed by RNC
67174689 VS.RRC.AttConnEstab.Cell Number of RRC Connection

DCH.RNC Requests for RNC (UE
Target State of CELL_DCH)
67174705 VS.RRC.AttConnEstab.Cell Number of RRC Connection

FACH.RNC Requests for RNC (UE
Target State of
CELL_FACH)

BSC6900 UMTS
Description
These counters provide the number of RRC CONNECTION REQUEST messages actually
processed by the RNC after the RNC receives the messages from the UE. These counters exclude
the number of rejected RRC connection requests caused by service-based redirection, inter-RAT
and inter-frequency distance-based redirection, or macro & micro joint inter-frequency
redirection.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a RRC
CONNECTION REQUEST message from the UE. These counters exclude the number of
rejected RRC connection requests caused by service-based redirection, inter-RAT and inter-
frequency distance-based redirection, or macro & micro joint inter-frequency redirection. Note
that the measurement is not triggered for a RRC CONNECTION REQUEST message that is
retransmitted by the UE.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RRC.AttConnEstab.RN WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

C Connection and Radio
and Release
VS.RRC.AttConnEstab.Cell WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

DCH.RNC Connection and Radio
and Release
VS.RRC.AttConnEstab.Cell WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

FACH.RNC Connection and Radio
and Release
1.10.23.2 Total Number of RRC Connection Requests Received by RNC
Counters
67174449 VS.RRC.AttConnEstab.Msg Total Number of RRC

.RNC Connection Requests
Received by RNC
Description
This counter provides the total number of RRC CONNECTION REQUEST messages received
by the RNC from the UE, including the retransmitted ones.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a RRC
CONNECTION REQUEST message from the UE. Note that the UE may send a RRC
CONNECTION REQUEST message for several times to increase the access rate. The
retransmitted RRC CONNECTION REQUEST messages from the UE are all measured by the
RNC.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RRC.AttConnEstab.Msg WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.10.23.3 Counters Related to the Number of Successful RRC Connection

Establishments

BSC6900 UMTS
Counters
67174452 VS.RRC.SuccConnEstab.R Number of Successful RRC

NC Connection Establishments
for RNC
67174706 VS.RRC.SuccConnEstab.Ce Number of Successful RRC

llFACH.RNC Connection Establishments
on CELL_FACH
67174691 VS.RRC.SuccConnEstab.Ce Number of Successful RRC

llDCH.RNC Connection Establishments
on CELL_DCH
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RRC.SuccConnEstab.R WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

NC Connection and Radio
and Release
VS.RRC.SuccConnEstab.Ce WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

llFACH.RNC Connection and Radio
and Release
VS.RRC.SuccConnEstab.Ce WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

llDCH.RNC Connection and Radio
and Release
1.10.24 RRC state measurement(RRC.STATE)
Overview
This function subset provides the average number of UEs in different RRC connection states in
the RNC.
Counters
Description
67199465 VS.CellDCHUEs.R Number of UEs in Earlier than

NC CELL_DCH State V900R011
for RNC
67199466 VS.CellFACHUEs. Number of UEs in Earlier than

RNC CELL_FACH State V900R011
for RNC
67199467 VS.CellPCHUEs.R Number of UEs in Earlier than

NC CELL_PCH State for V900R011
RNC

BSC6900 UMTS

Description
67199468 VS.UraPCHUEs.R Number of UEs in Earlier than

NC URA_PCH State for V900R011
RNC
73410506 VS.UraPCHUEs.P Average Number of V900R012

TT.RNC PTT UEs with RRC
Connection State of
URA_PCH for RNC
73441130 VS.UraEPCHUEs. Average Number of V900R013

RNC UEs in the
URA_PCH State and
Carried on the EPCH
for RNC
None
1.10.24.1 Counters Related to the Number of UEs in Different RRC Connection

States for RNC
Counters
67199465 VS.CellDCHUEs.RNC Number of UEs in

CELL_DCH State for RNC
67199466 VS.CellFACHUEs.RNC Number of UEs in

CELL_FACH State for RNC
67199467 VS.CellPCHUEs.RNC Number of UEs in

CELL_PCH State for RNC
67199468 VS.UraPCHUEs.RNC Number of UEs in

URA_PCH State for RNC
Description
These counters provide the number of UEs in different RRC connection states in the RNC.
Measurement point
The system periodically takes samples of the number of UEs in each RRC connection state every
five seconds. At the end of the measurement period, by dividing the accumulated value of sample

BSC6900 UMTS
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
VS.CellDCHUEs.RNC WRFD-010202 UE State in Connected Mode

(CELL-DCH, CELL-PCH,
URA-PCH, CELL-FACH)
VS.CellFACHUEs.RNC WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
VS.CellPCHUEs.RNC WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
VS.UraPCHUEs.RNC WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.10.24.2 Number of PTT UEs in URA_PCH State for RNC
Counters
73410506 VS.UraPCHUEs.PTT.RNC Average Number of PTT

UEs with RRC Connection
State of URA_PCH for RNC
Description
This counter provides the numbers of PTT UEs in URA_PCH state in the RNC.

BSC6900 UMTS
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
VS.UraPCHUEs.PTT.RNC WRFD-010202 UE State in Connected Mode

WRFD-020134 (CELL-DCH, CELL-PCH,
URA-PCH, CELL-FACH)
Push to Talk
1.10.24.3 Average Number of UEs in the URA_PCH State and Carried on the EPCH
for RNC
Counters
73441130 VS.UraEPCHUEs.RNC Average Number of UEs in

the URA_PCH State and
Carried on the EPCH for
RNC
Description
This counter provides the average number of UEs that are in the URA_PCH state and use the
EPCH function under an RNC.
Measurement point
UEs that are in the URA_PCH state and use the EPCH function are sampled at a certain interval
every five seconds. At the end of a measurement period, this counter measured at each sampling
site is calculated by dividing the accumulated number of the UEs by the number of samples.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.UraEPCHUEs.RNC WRFD-020134 Push to Talk
1.10.25 Soft Handover Measurement per RNC(SHO.RNC)
Overview
Soft handover is the procedure during which a radio link is added to or deleted from the active
set. When an UE moves or the radio link quality fluctuates, the RNC adds a radio link to the
active set if the RNC detects that the cell of the radio link is of good signal quality. If the quality
of a radio link in a cell in the active set becomes lower than the predefined threshold, the RNC
deletes this radio link from the active set.
A soft handover is considered as a softer handover if the two radio links of the UE connection
are established with cells belonging to the same NodeB. The RNC determines whether to perform
soft handover based on the intra-frequency measurement of the UE. When the RNC receives a
measurement report (MR) from the UE and determines that a soft handover is required, it sends
an ACTIVE SET UPDATE message to the UE, and starts a timer to wait for the response from
the UE. If the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE
before the timer expires, the soft handover is considered successful. If the RNC receives an
ACTIVE SET UPDATE FAILURE message from the UE or does not receive any message from
the UE before the timer expires, the soft handover is considered as a failure.
Counters
Description
67175268 VS.SoHO.Att.RNC Number of Softer Earlier than

by RNC for RNC
67175266 VS.SHO.Att.RNC Number of Soft Earlier than

by RNC for RNC

BSC6900 UMTS

Description
67175267 VS.SHO.Succ.RNC Number of Earlier than

Successful Soft V900R011
Handovers Initiated
by RNC for RNC
67175269 VS.SoHO.Succ.RN Number of Earlier than

C Successful Softer V900R011
Handovers Initiated
by RNC for RNC
67199432 VS.SHO.AS.1.RNC Mean Number of Earlier than

UEs with One Radio V900R011
Link for RNC
67199434 VS.SHO.AS. Mean Number of Earlier than

2Soft.RNC UEs with Two V900R011
Uncombined Radio
Links for RNC

3Soft2Softer.RNC UEs with Three V900R011
Radio Links and Two
Combined for RNC

3Soft.RNC UEs with Three V900R011
Uncombined Radio
Links for RNC

2Softer.RNC UEs with Two V900R011
Combined Radio
Links for RNC

3Softer.RNC UEs with Three V900R011
Combined Radio
Links for RNC

UEs with Four Radio V900R011
Links for RNC

UEs with Five Radio V900R011
Links for RNC

UEs with Six Radio V900R011
Links for RNC

BSC6900 UMTS

Description
67175283 VS.SHO.Drop.RN Number of Call Earlier than

C Drops Due to Soft V900R011
Handover Failures
for RNC
Counter Sub Counter
VS.SHO.Att.RNC VS.SoHO.Att.RNC
VS.SHO.Succ.RNC VS.SoHO.Succ.RNC
1.10.25.1 Number of Soft and Softer Handover Attempts
Counters
67175266 VS.SHO.Att.RNC Number of Soft Handovers

Initiated by RNC for RNC
67175268 VS.SoHO.Att.RNC Number of Softer Handovers

Initiated by RNC for RNC
Description
These counters provide the number of soft handover attempts in the RNC.
VS.SHO.Att.RNC Soft handover attempts in the RNC
VS.SoHO.Att.RNC Softer handover attempts in the RNC
Measurement point
one each time the RNC sends an ACTIVE SET UPDATE message to the UE during the soft
handover (including the softer handover) procedure.

BSC6900 UMTS
Figure 1-292 Successful soft handover procedure
Formula
None
Unit
None
Related Features
VS.SHO.Att.RNC WRFD-020202 Intra RNC Soft Handover

WRFD-020203 Inter RNC Soft Handover
VS.SoHO.Att.RNC WRFD-020201 Intra Node B Softer

WRFD-020202 Handover
Intra RNC Soft Handover
1.10.25.2 Number of Successful Soft Handovers

BSC6900 UMTS
Counters
67175267 VS.SHO.Succ.RNC Number of Successful Soft

for RNC
67175269 VS.SoHO.Succ.RNC Number of Successful Softer

for RNC
Description
This counter provides the number of successful soft handovers in the RNC.
VS.SHO.Succ.RNC Number of successful soft handovers in the

RNC
VS.SoHO.Succ.RNC 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 soft handover
(including the softer handover) procedure, the soft handover is considered as successful, and the
RNC measures the item.

BSC6900 UMTS
Figure 1-293 Successful soft handover procedure
Formula
None
Unit
None
Related Features
VS.SHO.Succ.RNC WRFD-020202 Intra RNC Soft Handover

VS.SoHO.Succ.RNC WRFD-020201 Intra Node B Softer

Intra RNC Soft Handover
1.10.25.3 Mean Number of UEs with One to Six Radio Link

BSC6900 UMTS
Counters
67199432 VS.SHO.AS.1.RNC Mean Number of UEs with

One Radio Link for RNC
67199434 VS.SHO.AS.2Soft.RNC Mean Number of UEs with

Two Uncombined Radio
Links for RNC
67199437 VS.SHO.AS. Mean Number of UEs with

3Soft2Softer.RNC Three Radio Links and Two
Combined for RNC
67199436 VS.SHO.AS.3Soft.RNC Mean Number of UEs with

Three Uncombined Radio
Links for RNC
67199433 VS.SHO.AS.2Softer.RNC Mean Number of UEs with

Two Combined Radio Links
for RNC
67199435 VS.SHO.AS.3Softer.RNC Mean Number of UEs with

Three Combined Radio
Links for RNC

Four Radio Links for RNC

Five Radio Links for RNC

Six Radio Links for RNC
Description
These counters provide the mean number of UEs with one to six radio links (RLs) in an RNC.
The mean number of UEs with two or three RLs is measured with consideration of the number
of combined RLs at the NodeB.
Measurement point
The RNC takes samples of the number of UEs with one to six radio links every five seconds in
a measurement period. At the end of the measurement period, the RNC divides the accumulated
numbers by the number of samples to obtain the mean number of UEs with one to six RLs in
the measurement period in the RNC.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.SHO.AS.1.RNC WRFD-020202 Intra RNC Soft Handover

VS.SHO.AS.2Soft.RNC WRFD-020202 Intra RNC Soft Handover

VS.SHO.AS. WRFD-020202 Intra RNC Soft Handover

3Soft2Softer.RNC WRFD-020203 Inter RNC Soft Handover
VS.SHO.AS.3Soft.RNC WRFD-020202 Intra RNC Soft Handover

VS.SHO.AS.2Softer.RNC WRFD-020202 Intra RNC Soft Handover

VS.SHO.AS.3Softer.RNC WRFD-020202 Intra RNC Soft Handover




1.10.25.4 Number of Call Drops due to Soft Handover Failures
Counters
67175283 VS.SHO.Drop.RNC Number of Call Drops Due to

Soft Handover Failures for
RNC
Description
This counter provides the number of call drops caused by soft handover failures in the RNC.

BSC6900 UMTS
Measurement point
The measurement is triggered at point A, as shown in the figure. During the soft handover
(including the softer handover), when the RNC sends an ACTIVE SET UPDATE message to
the UE, it starts a timer to wait for the response from the UE. If the RNC does not receive the
response before the timer expires, it releases the corresponding RRC connection, which results
in a call drop. In this case, this counter is incremented by one.
Figure 1-294 A failed soft handover (timer expiry)
Formula
None
Unit
None
Related Features
VS.SHO.Drop.RNC WRFD-020202 Intra RNC Soft Handover

WRFD-020201 Intra Node B Softer
Inter RNC Soft Handover

BSC6900 UMTS
1.10.26 Measurement related to Security mode per RNC(SM.RNC)
Overview
The security mode control procedure is to send encryption and integrity protection information
to the UTRAN. With the information, the UTRAN can encrypt user data and signaling data, and
provide integrity protection for signaling data.
Counters
Description
67190317 VS.IU.AttSecMode Number of Earlier than

SECURITY MODE V900R011
COMMAND
Messages Received
by RNC from CN
67190318 VS.IU.SuccSec- Number of Earlier than

Mode SECURITY MODE V900R011
COMPLETE
Messages Sent by
RNC to CN
67190319 VS.IU.RejSecMd.R Number of Earlier than

nl SECURITY MODE V900R011
REJECT Messages
Sent by RNC to CN
(Radio Network
Layer Cause)
67190320 VS.IU.RejSecMd.T Number of Earlier than

nl SECURITY MODE V900R011
REJECT Messages
Sent by RNC to CN
(Transport Layer
Cause)
67190321 VS.IU.RejSecMd.N Number of Earlier than

AS SECURITY MODE V900R011
REJECT Messages
Sent by RNC to CN
(NAS Cause)
67190323 VS.IU.RejSecMd.U Number of Earlier than

nsp SECURITY MODE V900R011
REJECT Messages
Sent by RNC to CN
(Unspecified
Failure)

BSC6900 UMTS

Description
67190324 VS.UU.AttSecMod Number of Earlier than

e SECURITY MODE V900R011
COMMAND
Messages Sent by
RNC to UE
67190325 VS.UU.SuccSec- Number of Earlier than

Mode SECURITY MODE V900R011
COMPLETE
Messages Received
by RNC from UE
None
1.10.26.1 Number of SECURITY MODE COMMAND Messages Received by RNC

from CN
Counters
67190317 VS.IU.AttSecMode Number of SECURITY

MODE COMMAND
Messages Received by RNC
from CN
Description
This measurement item takes statistics of the number of SECURITY MODE COMMAND
messages that the RNC receives from the CN.
Measurement point
SECURITY MODE COMMAND message from the CN, the RNC measures this item.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.AttSecMode WRFD-011401 Integrity Protection
1.10.26.2 Number of SECURITY MODE COMPLETE Messages Sent from RNC to

CN

BSC6900 UMTS
Counters
67190318 VS.IU.SuccSecMode Number of SECURITY

MODE COMPLETE
Messages Sent by RNC to
CN
Description
This measurement item takes statistics of the number of SECURITY MODE COMPLETE
messages that the RNC sends to the CN.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends a
SECURITY MODE COMPLETE message to the CN, the RNC measures this item.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.IU.SuccSecMode WRFD-011401 Integrity Protection
1.10.26.3 Number of SECURITY MODE REJECT Messages Sent from RNC to CN

Counters
67190319 VS.IU.RejSecMd.Rnl Number of SECURITY

MODE REJECT Messages
Sent by RNC to CN (Radio
Network Layer Cause)
67190320 VS.IU.RejSecMd.Tnl Number of SECURITY

Sent by RNC to CN
(Transport Layer Cause)
67190321 VS.IU.RejSecMd.NAS Number of SECURITY

Sent by RNC to CN (NAS
Cause)
67190323 VS.IU.RejSecMd.Unsp Number of SECURITY

Sent by RNC to CN
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.

BSC6900 UMTS
Figure 1-297 Security mode rejection procedure
Formula
None
Unit
None
Related Features
VS.IU.RejSecMd.Rnl WRFD-011401 Integrity Protection
VS.IU.RejSecMd.Tnl WRFD-011401 Integrity Protection
VS.IU.RejSecMd.NAS WRFD-011401 Integrity Protection
VS.IU.RejSecMd.Unsp WRFD-011401 Integrity Protection
1.10.26.4 Number of SECURITY MODE COMMAND Messages Sent from RNC to

UE

BSC6900 UMTS
Counters
67190324 VS.UU.AttSecMode Number of SECURITY

MODE COMMAND
Messages Sent by RNC to
UE
Description
This measurement item takes statistics of the number of SECURITY MODE COMMAND
messages that the RNC sends to the UE.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends a
SECURITY MODE COMMAND message to the UE, the RNC measures this item.
Figure 1-298 Security mode control procedure (RNC to UE)
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.UU.AttSecMode WRFD-011401 Integrity Protection
1.10.26.5 Number of SECURITY MODE COMPLETE Messages Received by RNC

from UE
Counters
67190325 VS.UU.SuccSecMode Number of SECURITY

MODE COMPLETE
Messages Received by RNC
from UE
Description
This measurement item takes statistics of the number of SECURITY MODE COMPLETE
messages that the RNC receives from the UE.
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC receives a
SECURITY MODE COMPLETE message from the UE, the RNC measures this item.
Figure 1-299 Security mode control procedure (RNC to UE)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.UU.SuccSecMode WRFD-011401 Integrity Protection
1.10.27 Traffic Measurement per RNC(TRAFF.LOAD.RNC)
Overview
The RNC traffic measurement is used to measure the traffic of the CS domain and PS domain
in the RNC. Here, the traffic of the CS domain is indicated by equivalent Erlang while the traffic
of the PS domain by kbit per second.
Counters
Description

.Equiv.RNC Conversational V900R011
Erlang for RNC
67192086 VS.CSLoad.MaxEr Maximum Earlier than

lang.Equiv.RNC equivalent CS V900R011
Conversational
Erlang for RNC
67204135 VS.R99PSLoad.UL Throughput of Earlier than

Thruput.RNC Uplink PS R99 V900R011
Traffic for RNC
67192985 VS.R99PSLoad.Ma Maximum Earlier than

xULThruput.RNC Throughput of V900R011
Uplink PS R99
Traffic for RNC
67204136 VS.R99PSLoad.DL Throughput of Earlier than

Thruput.RNC Downlink PS R99 V900R011
Traffic for RNC

BSC6900 UMTS

Description
67192988 VS.R99PSLoad.Ma Maximum Earlier than

xDLThruput.RNC Throughput of V900R011
Downlink PS R99
Traffic for RNC
67204137 VS.HSDPAPSLoad Throughput of PS Earlier than

.DLThruput.RNC HSDPA Traffic for V900R011
RNC
67192991 VS.HSDPAPSLoad Maximum Earlier than

.MaxDLThruput.R Throughput of PS V900R011
NC HSDPA Traffic for
RNC
67204138 VS.HSUPAPSLoad Throughput of PS Earlier than

.ULThruput.RNC HSUPA Traffic for V900R011
RNC
67192994 VS.HSUPAPSLoad Maximum Earlier than

.MaxULThruput.R Throughput of PS V900R011
NC HSUPA Traffic for
RNC
67204139 VS.MBMSPSLoad. Throughput of PS Earlier than

DLThruput.RNC MBMS Traffic for V900R011
RNC
67192997 VS.MBMSPSLoad. Maximum Earlier than

MaxDLThruput.R Throughput of PS V900R011
NC MBMS Traffic for
RNC
73410501 VS.PSLoad.Thrup Average Total V900R012

ut.RNC Throughout of UL
and DL PS Services
for RNC
73394059 VS.PSLoad.MaxTh Maximum Total V900R012

ruput.RNC Throughout of UL
and DL PS Services
for RNC
73394070 VS.CS.Erlang.RNC Erlang of CS V900R012

Services for RNC
None

BSC6900 UMTS
1.10.27.1 Equivalent Erlang of CS Domain in RNC
Counters
67202970 VS.CSLoad.Erlang.Equiv.R Equivalent CS

NC Conversational Erlang for
RNC
Description
This measurement item provides the equivalent Erlang values of all the services in the CS domain
in the RNC. The item is measured only when the RAN sharing function and MOCN function
are switched off.
Measurement point
The RNC periodically takes the samples from the equivalent Erlang values of all the services in
the CS domain every five seconds. At the end of the measurement period, the RNC divides the
accumulated equivalent Erlang values by the number of samples to obtain the mean equivalent
Erlang values of all the services in the CS domain, include the equivalent Erlang of all radio
links of Soft Handover.Each time a CS domain service is established, the RNC converts its rate
to the equivalent Erlang, and then increases the equivalent Erlang of the CS domain in the current
RNC. Each time a CS domain service is released, the RNC converts its rate to the equivalent
Erlang and decreases the equivalent Erlang of the CS domain in the current RNC.
Formula
None
Unit
Erl
Related Features
VS.CSLoad.Erlang.Equiv.R MRFD-210403 License Management

NC
1.10.27.2 Maximum Equivalent Erlang of CS Domain in RNC

BSC6900 UMTS
Counters
67192086 VS.CSLoad.MaxErlang.Equ Maximum equivalent CS

iv.RNC Conversational Erlang for
RNC
Description
This measurement item provides the maximum equivalent Erlang values of all the services in
the CS domain within the RNC. The item is measured only when the RAN sharing function and
MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the equivalent Erlang values of all the services in
the CS domain every five seconds. At the end of the period, the RNC calculates the maximum
equivalent Erlang of all the services in the CS domain within the RNC, include the equivalent
Erlang of all radio links of Soft Handover.Each time a CS domain service is established, the
RNC converts its rate to the equivalent Erlang, and then increases the equivalent Erlang of the
CS domain in the current RNC. Each time a CS domain service is released, the RNC decreases
the equivalent Erlang of the CS domain in the current RNC.
Formula
None
Unit
Erl
Related Features
VS.CSLoad.MaxErlang.Equ MRFD-210403 License Management

iv.RNC
1.10.27.3 UL Traffic of R99 PS Domain in RNC
Counters
67204135 VS.R99PSLoad.ULThruput. Throughput of Uplink PS

RNC R99 Traffic for RNC

BSC6900 UMTS
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
VS.R99PSLoad.ULThruput. MRFD-210403 License Management

RNC
1.10.27.4 Maximum UL Traffic of R99 PS Domain in RNC
Counters
67192985 VS.R99PSLoad.MaxULThr Maximum Throughput of

uput.RNC Uplink PS R99 Traffic for
RNC
Description
This measurement item provides the maximum uplink traffic of all the R99 services in the PS
domain within the RNC. The item is measured only when the RAN sharing function and MOCN
function are switched off.

BSC6900 UMTS
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
VS.R99PSLoad.MaxULThr MRFD-210403 License Management

uput.RNC
1.10.27.5 DL Traffic of R99 PS Domain in RNC
Counters
67204136 VS.R99PSLoad.DLThruput. Throughput of Downlink PS

RNC R99 Traffic for RNC
Description
This measurement item provides the downlink traffic of all the R99 services in the PS domain
within the RNC. The item is measured only when the RAN sharing function and MOCN function
are switched off.
Measurement point
The RNC periodically takes a sample from the downlink traffic values of all the R99 services
in the PS domain every five seconds. At the end of the measurement period, the RNC divides
the accumulated traffic values by the number of samples to obtain the mean downlink traffic of
all the R99 services in the PS domain.The mean downlink traffic of all the R99 services in the
PS domain is the traffic measured at the RLC layer. The RLC header data is not included and
the soft handover traffic is included.

BSC6900 UMTS
Formula
None
Unit
kbit/s
Related Features
VS.R99PSLoad.DLThruput. MRFD-210403 License Management

RNC
1.10.27.6 Maximum DL Traffic of R99 PS Domain in RNC
Counters
67192988 VS.R99PSLoad.MaxDLThr Maximum Throughput of

uput.RNC Downlink PS R99 Traffic for
RNC
Description
This measurement item provides the maximum downlink traffic of all the R99 services in the
PS domain within the RNC. The item is measured only when the RAN sharing function and
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

BSC6900 UMTS
Related Features
VS.R99PSLoad.MaxDLThr MRFD-210403 License Management

uput.RNC
1.10.27.7 DL Traffic of HSDPA PS Domain in RNC
Counters
67204137 VS.HSDPAPSLoad.DLThru Throughput of PS HSDPA

put.RNC Traffic for RNC
Description
This measurement item provides the downlink traffic of all the HSDPA services in the PS domain
are switched off.
Measurement point
The RNC periodically takes a sample from the downlink traffic values of all the HSDPA services
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
VS.HSDPAPSLoad.DLThru WRFD-010610 HSDPA Introduction

put.RNC Package

BSC6900 UMTS
1.10.27.8 Maximum DL Traffic of HSDPA PS Domain in RNC
Counters
67192991 VS.HSDPAPSLoad.MaxDL Maximum Throughput of PS

Thruput.RNC HSDPA Traffic for RNC
Description
This measurement item provides the maximum downlink traffic of all the HSDPA services in
the PS domain within the RNC. The item is measured only when the RAN sharing function and
Measurement point
The RNC periodically takes a sample from the downlink traffic values of all the HSDPA services
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
VS.HSDPAPSLoad.MaxDL WRFD-010610 HSDPA Introduction

Thruput.RNC Package
1.10.27.9 UL Traffic of HSUPA PS Domain in RNC
Counters
67204138 VS.HSUPAPSLoad.ULThru Throughput of PS HSUPA


BSC6900 UMTS
Description
This measurement item provides the uplink traffic of all the HSUPA services in the PS domain
are switched off.
Measurement point
The RNC periodically takes a sample from the uplink traffic values of all the HSUPA services
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
VS.HSUPAPSLoad.ULThru WRFD-010612 HSUPA Introduction

put.RNC Package
1.10.27.10 Maximum UL Traffic of HSUPA PS Domain in RNC
Counters
67192994 VS.HSUPAPSLoad.MaxUL Maximum Throughput of PS

Thruput.RNC HSUPA Traffic for RNC
Description
This measurement item provides the maximum uplink traffic of all the HSUPA services in the
Measurement point
The RNC periodically takes a sample from the uplink traffic values of all the HSUPA services

BSC6900 UMTS
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
VS.HSUPAPSLoad.MaxUL WRFD-010612 HSUPA Introduction

Thruput.RNC Package
1.10.27.11 DL Traffic of MBMS or IMB PS Domain in RNC
Counters
67204139 VS.MBMSPSLoad.DLThru Throughput of PS MBMS

Description
This measurement item provides the downlink traffic of all the MBMS or IMB services in the
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

BSC6900 UMTS
Unit
kbit/s
Related Features
VS.MBMSPSLoad.DLThru WRFD-010616 MBMS Introduction

put.RNC Package
1.10.27.12 Maximum DL Traffic of MBMS or IMB PS Domain in RNC
Counters
67192997 VS.MBMSPSLoad.MaxDL Maximum Throughput of PS

Thruput.RNC MBMS Traffic for RNC
Description
This measurement item provides the maximum downlink traffic of all the MBMS or IMB
services in the PS domain within the RNC. The item is measured only when the RAN sharing
function and MOCN function are switched off.
Measurement point
The RNC periodically takes a sample from the downlink traffic values of all the MBMS or IMB
services in the PS domain every five seconds. At the end of the measurement period, the RNC
calculates the maximum downlink traffic of all the MBMS or IMB services in PS domain within
the RNC.The downlink traffic of all MBMS or IMB services in the PS domain refers to the
traffic obtained at the RLC layer. The data does not include the RLC head data.
Formula
None
Unit
kbit/s

BSC6900 UMTS
Related Features
VS.MBMSPSLoad.MaxDL WRFD-010616 MBMS Introduction

Thruput.RNC Package
1.10.27.13 Average Total Throughout of UL and DL PS Services for RNC
Counters
73410501 VS.PSLoad.Thruput.RNC Average Total Throughout of

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

BSC6900 UMTS
Counters
73394059 VS.PSLoad.MaxThruput.R Maximum Total Throughout

NC of UL and DL PS Services for
RNC
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
VS.PSLoad.MaxThruput.R MRFD-210403 License Management

NC
1.10.27.15 Erlang of CS Services for RNC
Counters
73394070 VS.CS.Erlang.RNC Erlang of CS Services for

RNC

BSC6900 UMTS
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
VS.CS.Erlang.RNC MRFD-210403 License Management
1.11 Measurement of ROAMCNOPERATOR Performance

(ROAM_CNOPERATOR)
Overview
Roaming UE registration measurement indicates the registration of roaming UEs by the RNC.
FunctionSubSets
MOCN.ROAM_CNOPERATOR Roaming UE Registration Measurement

Under MOCN

BSC6900 UMTS
1.11.1 Roaming UE Registration Measurement Under MOCN

(MOCN.ROAM.CNOPERATOR)
Overview
Roaming UE registration measurement under MOCN provides the number of times that a
roaming UE is registered in an operator under the MOCN after the roaming UE starts the CS or
PS registration.
Counters
Description
73423374 VS.Roam.Cnoperat Number of Roaming V900R013

or.MOCN.Num UEs that Is
Registered In Local
Operator Under
MOCN for the First
Time
None
1.11.1.1 Number of Roaming UEs that Is Registered In Local Operator Under

MOCN for the First Time
Counters
73423374 VS.Roam.Cnoperator.MOC Number of Roaming UEs

N.Num that Is Registered In Local
Operator Under MOCN for
the First Time
Description
This counter provides the number of times that a roaming UE is registered in the local operator
under the MOCN to indicate that when the operator of the roaming UE has signed the roaming
contract with multiple operators under the MOCN, the RNC routes the roaming UEs to different
operators according to the preset proportion.

BSC6900 UMTS
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.
Figure 1-300 INIT UE MESSAGE Redirect procedure
Formula
None
Unit
None
Related Features
VS.Roam.Cnoperator.MOC WRFD-02131106 Routing Roaming UEs in

N.Num Proportion

BSC6900 UMTS
1.12 Measurement of Radio Cell Performance(UCELL)

Overview
The measurement object type CELL is used to measure the performance of a cell. The cell
belongs to the RNC and contains one measurement set: CELL.
FunctionSubSets
ALGO.Cell Measurement related to Algorithm per cell
ALGO2.Cell Algorithm Measurement2 for Cell
BLER.Cell Measurement related to BLER per cell
BOOST.CELL Cell Measurement on BOOST
CCH.Cell Common Channel Measurement per Cell
CELLUPDATE.Cell Cell Update Measurement per cell
CM.Cell Measurement of Compressed Mode per cell
EFACH.Cell EFACH Measurement per cell
EPCH.Cell EPCH Measurement per cell
ERACH.Cell ERACH Measurement per cell
HHO.Cell Hard Handover Measurement per cell
HSDPA.Cell HSDPA Measurement per cell
HSUPA.Cell HSUPA Measurement per cell
INTRAT.HO.Cell InterRAT Handover Measurement per cell
IU.Sig.Rel.Cell Measurement Related to the Release of Iu

Signaling Connections (Without RAB) (Cell)
IUB.Cell Iub Interface Measurement per cell
LCS.CELL Measurement related to LCS service per cell
MBMS.Cell MBMS Measurement per cell
MEAR.Report.Cell RRC Reporting Measurement per cell
PAGE.CELL Measurement related to Paging per cell
PLMN.CELL Measurement by Operator for Cell
PTT.Cell Measurements related to PTT

BSC6900 UMTS
QOS.Cell Measurement related to QOS per cell
RAB.EstabCS.Cell Measurement of CS RAB assignment setup

per cell
RAB.EstabPS.Cell Measurement of PS RAB assignment setup

per cell
RAB.EstFailCs.Cell Measurement of CS RAB assignment failure

per cell
RAB.EstFailPs.Cell Measurement of PS RAB assignment failure

per cell
RAB.ModCs.Cell Measurement of CS RAB assignment

modification per cell
RAB.ModPs.Cell Measurement of PS RAB assignment

modification per cell
RAB.MultiRab.Cell Measurement of multi-RAB service per cell
RAB.RelAbnormal.Cell Measurement of RAB release per cell
RAB.RelCs.Cell Measurement of CS RAB release per cell
RAB.RelPs.Cell Measurement of PS RAB release per cell
RB.Cell Measurement of RB Procedure per cell
RESERVE.Cell Reserved counter for cell
RLC.Cell Measurement related to RLC per cell
RRC.Rel.Cell RRC connection release measurement per

cell
RRC.Setup.Cell RRC connection setup measurement per cell
RRC.SetupFail.Cell RRC connection reject measurement per cell
RRC.State.Cell RRC state measurement<Cell>
RRC.UECapab.Cell UE Capability Measurement per cell
RTWPTCP.Cell Cell TX and RX Power Measurement per cell
SHO.Cell Soft Handover Measurement per cell
SIR.Cell Measurement related to SIRTARGET per

cell
SPI.Cell Measurement related to SPI per cell
THRUPUT.Cell Measurement related to throughput and data

rate per cell

BSC6900 UMTS
TRFFIC.Cell Traffic Measurement per cell
U2LTE.HO.Cell Measurement related to U2L Handover per

cell
URAUPDATE.Cell URA Update Measurement per cell
WLAN.Cell WLAN Measurement per cell
1.12.1 Measurement related to Algorithm per cell(ALGO.Cell)
Overview
Radio Resource Management (RRC) algorithm is an important function of the WCDMA system.
It is used to manage cell resources effectively and to increase resource utilization. This function
subset provides measurements related to the radio resource management algorithm.
Counters
Description
67180678 VS.AMR.DL.Rate Number of DL Rate Earlier than

Up Increases for AMR V900R011
Services for Cell
67190519 VS.AMR.DL.Rate- Number of DL Rate Earlier than

Down Decreases for AMR V900R011
Services for Cell
67190520 VS.AMR.UL.Rate Number of UL Rate Earlier than

Up Increases for AMR V900R011
Services for Cell
67180677 VS.AMR.UL.Rate- Number of UL Rate Earlier than

Down Decreases for AMR V900R011
Services for Cell
67180675 VS.DCCC.Succ.F2 Number of Earlier than

D Successful Channel V900R011
Conversions from
FACH to DCH for
Cell
67180676 VS.DCCC.Succ.D2 Number of Earlier than

F Successful Channel V900R011
Conversions from
DCHs to FACHs for
Cell

BSC6900 UMTS

Description
67192583 VS.DCCC.Att.F2P Number of State Earlier than

Transfer Attempts V900R011
from CELL_FACH
to CELL_PCH for
Cell
67192584 VS.DCCC.Succ.F2 Number of Earlier than

P Successful State V900R011
Transfers from
CELL_FACH to
CELL_PCH for Cell
67192587 VS.DCCC.AttDow Number of Downlink Earlier than

nsizing.DL.Thr DCH DCCC V900R011
Downsizing
Attempts Based on
Throughput or RLC
BO for Cell
67192588 VS.DCCC.SuccDo Number of Earlier than

wnsizing.DL.Thr Successful DL DCH V900R011
DCCC Downsizings
Based on
Throughput or RLC
BO for Cell

nsizing.DL.Cov DCH DCCC V900R011
Downsizing
Attempts Based on
Coverage (QoS) for
Cell

wnsizing.DL.Cov Successful DL DCH V900R011
DCCC Downsizings
Based on Coverage
(QoS) for Cell

nsizing.DL.Cong DCH DCCC V900R011
Downsizing
Attempts Based on
Resource
Congestion
Algorithm for Cell

BSC6900 UMTS

Description

wnsizing.DL.Cong Successful DL DCH V900R011
DCCC Downsizings
Based on Resource
Congestion
Algorithm for Cell
67189852 VS.LCC.OLC.UL. Number of UL Earlier than

Num Overload V900R011
Congestions for Cell
67189853 VS.LCC.OLC.DL. Number of DL Earlier than

Num Overload V900R011
67203402 VS.LCC.OLC.UL. Duration of UL Earlier than

Time Overload V900R011
Congestion for Cell
67203403 VS.LCC.OLC.DL. Duration of DL Earlier than

Time Overload V900R011
Congestion for Cell
67191150 VS.LCC.OLC.HSD Number of HSDPA Earlier than

PA.UserRel UEs Released Due to V900R011
Overload
Congestion for Cell
67192549 VS.LCC.OLC.D2C Number of UEs Earlier than

Transferring BE V900R011
Service to Common
Channel in Overload
Congestion for Cell
67203991 VS.LCC.LDR.Tim Duration of Cell in Earlier than

e.ULPower LDR State Due to UL V900R011
Power Congestion
for Cell

e.DLPower LDR State Due to DL V900R011
Power Congestion
for Cell

e.DLCode LDR State Due to DL V900R011
Code Resource
Congestion for Cell

BSC6900 UMTS

Description

e.ULCE LDR State Due to UL V900R011
CE Resource
Congestion

e.DLCE LDR State Due to DL V900R011
CE Resource
Congestion

e.ULIub LDR State Due to UL V900R011
Iub Transmission
Resource
Congestion for Cell

e.DLIub LDR State Due to DL V900R011
Iub Transmission
Resource
Congestion for Cell
67192637 VS.LCC.LDR.Num Number of Times a Earlier than

.ULPower Cell Is in LDR State V900R011
Due to UL Power
Congestion for Cell

.DLPower Cell Is in LDR State V900R011
Due to DL Power
Congestion for Cell

.DLCode Cell Is in LDR State V900R011
Due to DL Code
Resource
Congestion for Cell

.ULCE Cell Is in LDR State V900R011
Due to UL CE
Resource
Congestion for Cell

.DLCE Cell Is in LDR State V900R011
Due to DL CE
Resource
Congestion for Cell

BSC6900 UMTS

Description

.ULIub Cell Is in LDR State V900R011
Due to UL Iub
Transmission
Resource
Congestion for Cell

.DLIub Cell Is in LDR State V900R011
Due to DL Iub
Transmission
Resource
Congestion for Cell
67192644 VS.LCC.LDR.HSU Number of HSUPA Earlier than

PA.InterFreq UEs Performing V900R011
Inter-Frequency
Load Handovers in
Basic Congestion for
Cell

PA.InterRATPS UEs Performing PS V900R011
Inter-RAT Handover
in Basic Congestion
for Cell
67192646 VS.LCC.OLC.UL. Number of UEs Earlier than

TF Performing BE V900R011
Service TF Control
in UL Overload
Congestion for Cell
67192647 VS.LCC.OLC.UL. Number of UEs Earlier than

UserRel Released Due to UL V900R011
Overload
Congestion for Cell
67192648 VS.LCC.OLC.HSU Number of HSUPA Earlier than

PA.UserRel UEs Released during V900R011
Overload
Congestion for Cell
67192649 VS.LCC.OLC.DL. Number of UEs Earlier than

TF Performing BE V900R011
Service TF Control
in DL Overload
Congestion for Cell

BSC6900 UMTS

Description
67192650 VS.LCC.OLC.DL. Number of UEs Earlier than

UserRel Released Due to DL V900R011
Overload
Congestion for Cell
67192916 VS.RAC.NewCallR Number of Failed Earlier than

eq.Fail.HSDPANu Admissions Due to V900R011
m.Cong HSDPA User
Number Exceeding
Threshold During
RAB Establishment
for Cell

eq.Fail.HSUPANu Admissions Due to V900R011
m.Cong HSUPA User
Number Exceeding
Threshold During
RAB Establishment
for Cell
67192937 VS.RAC.NewCallR Number of Earlier than

eq.Preempt.Cong Preemptions During V900R011
RAB Establishment
for Cell
67192939 VS.RAC.SHO.Fail. Number of Failed Earlier than

ULPower.Cong Requests for UL V900R011
Power Resources
During SHO for Cell

DLPower.Cong Requests for DL V900R011
Power Resources
During SHO for Cell

Code.Cong Requests for Code V900R011
Resources During
SHO for Cell

ULIUBBand.Cong Requests for UL Iub V900R011
Transmission
Resources During
SHO for Cell

BSC6900 UMTS

Description

DLIUBBand.Cong Requests for DL Iub V900R011
Transmission
Resources During
SHO for Cell

HSUPANum.Cong Admissions Due to V900R011
HSUPA User
Number Exceeding
Threshold During
SHO for Cell
67192943 VS.RAC.DCCC.Fa Number of Failed Earlier than

il.ULPower.Cong Requests for UL V900R011
Power Resources
During DCCC for
Cell

il.DLPower.Cong Requests for DL V900R011
Power Resources
During DCCC for
Cell

il.Code.Cong Requests for DL V900R011
Code Resources
During DCCC for
Cell
67192923 VS.RAC.TrChSwit Number of Failed Earlier than

ch.Fail.ULCE.Con Requests for UL CE V900R011
g Resources During
Channel Type
Switch for Cell

ch.Fail.DLCE.Con Requests for DL CE V900R011
g Resources During
Channel Type
Switch for Cell

ch.Fail.ULPower.C Requests for UL V900R011
ong Power Resources
During Channel
Type Switch for Cell

BSC6900 UMTS

Description

ch.Fail.DLPower.C Requests for DL V900R011
ong Power Resources
During Channel

ch.Fail.Code.Cong Requests for Code V900R011
Resources During
Channel Type
Switch for Cell

ch.Fail.ULIUBBan Requests for UL Iub V900R011
d.Cong Transmission
Resources During
Channel Type
Switch for Cell

ch.Fail.DLIUBBan Requests for DL Iub V900R011
d.Cong Transmission
Resources During
Channel Type
Switch for Cell

ch.Fail.HSDPANu Admissions Due to V900R011
m.Cong HSDPA User
Number Exceeding
Threshold During
Channel Type
Switch for Cell

ch.Fail.HSUPANu Admissions Due to V900R011
m.Cong HSUPA User
Number Exceeding
Threshold During
Channel Type
Switch for Cell
67192941 VS.RAC.HHO.Fail Number of Failed Earlier than

.ULPower.Cong Requests for UL V900R011
Power Resources
During HHO for Cell

BSC6900 UMTS

Description

.DLPower.Cong Requests for DL V900R011
Power Resources
During HHO for Cell

.ULIUBBand.Cong Requests for UL Iub V900R011
Transmission
Resources During
HHO for Cell

.DLIUBBand.Cong Requests for DL Iub V900R011
Transmission
Resources During
HHO for Cell

.HSDPANum.Cong Admissions Due to V900R011
HSDPA User
Number Exceeding
Threshold During
HHO for Cell

.HSUPANum.Cong Admissions Due to V900R011
HSUPA User
Number Exceeding
Threshold During
HHO for Cell
67192938 VS.RAC.HHO.Pre Number of Earlier than

empt.Cong Preemptions During V900R011
HHO for Cell
67194970 VS.LCC.OLC.MB Number of MBMS Earlier than

MS.PTM.RBRel PTM Service V900R011
Releases in Overload
Congestion for Cell
67194971 VS.LCC.OLC.MB Number of MBMS Earlier than

MS.PTP.RBRel PTP Service V900R011
Releases in Overload
Congestion for Cell
67190435 VS.LCC.LDR.In- Number of UEs Earlier than

terFreq Performing Inter- V900R011
Frequency Load
Handovers in Basic
Congestion for Cell

BSC6900 UMTS

Description
67191151 VS.LCC.LDR.HSD Number of HSDPA Earlier than

PA.InterFreq UEs Performing V900R011
Inter-Frequency
Load Handovers in
Cell
67190436 VS.LCC.LDR.UL. Number of UEs Earlier than

BERateDown Performing BE V900R011
Service Downsizing
in UL Basic
Congestion
67190437 VS.LCC.LDR.DL. Number of UEs Earlier than

BERateDown Performing BE V900R011
Service Downsizing
in DL Basic
Congestion
67190438 VS.LCC.LDR.UL. Number of UEs Earlier than

QosReNego Performing V900R011
Uncontrollable Real-
Time Service QoS
Renegotiation in UL
Cell
67190439 VS.LCC.LDR.DL. Number of UEs Earlier than

QosReNego Performing V900R011
Uncontrollable Real-
Time Service QoS
Renegotiation in DL
Cell

terRATCS Performing CS Inter- V900R011
RAT Handovers in
Cell

terRATPS Performing PS Inter- V900R011
RAT Handovers in
Cell

BSC6900 UMTS

Description

PA.InterRATPS UEs Performing PS V900R011
Inter-RAT
Handovers in Basic
Congestion for Cell
67192426 VS.LCC.LDR.AM Number of UEs Earlier than

RRateUL Performing AMR V900R011
Rate Decrease in UL
Cell
67192427 VS.LCC.LDR.AM Number of UEs Earlier than

RRateDL Performing AMR V900R011
Rate Decrease in DL
Cell
67192397 VS.LCC.LDR.Cod Number of UEs Earlier than

eAdj.Att Performing Code V900R011
Adjustment
Attempts in DL
Cell
67192398 VS.LCC.LDR.Mb Number of MBMS Earlier than

msPowerDec Services Performing V900R011
Power Decreasing in
Cell
67189856 VS.PUC.High.Offs Number of Qoffset Earlier than

et.Updt Updates Due to V900R011
Heavy Load for Cell
67189857 VS.PUC.Light.Offs Number of Qoffset Earlier than

et.Updt Updates Due to Light V900R011
Load for Cell
67189858 VS.PUC.Norm.Offs Number of Qoffset Earlier than

et.Updt Updates Due to V900R011
Normal Load for Cell
67190442 VS.PUC.Light.IntS Number of Earlier than

rch.Updt Sintersearch Updates V900R011
Due to Light Load
for Cell

BSC6900 UMTS

Description
67190443 VS.PUC.Norm.IntS Number of Earlier than

Due to Normal Load
for Cell
67190444 VS.PUC.High.IntS Number of Earlier than

Due to Heavy Load
for Cell

.Code.Cong Requests for Code V900R011
Resources During
HHO for Cell
67181079 VS.RAC.HHOCal- Number of Earlier than

lAcc Successful Cell V900R011
Resource Requests
During HHO for Cell
67181074 VS.RAC.HHOCall- Number of Cell Earlier than

Req Resource Requests V900R011
During HHO for Cell
67181076 VS.RAC.NewCal- Number of Earlier than

Resource Requests
During RAB
Establishment for
Cell
67181071 VS.RAC.NewCall- Number of Cell Earlier than

During RAB
Establishment for
Cell
67181078 VS.RAC.Reconfig- Number of Earlier than

CallAcc Successful Cell V900R011
Resource Requests
Due to UE RAB
Reconfiguration for
Cell
67181073 VS.RAC.Reconfig- Number of Cell Earlier than

CallReq Resource Requests V900R011
Due to UE RAB
Reconfiguration for
Cell

BSC6900 UMTS

Description
67181077 VS.RAC.SHOCal- Number of Earlier than

Resource Requests
During SHO for Cell
67181072 VS.RAC.SHOCall- Number of Cell Earlier than

During SHO for Cell
67181080 VS.RAC.TrChSwit Number of Earlier than

chCallAcc Successful Cell V900R011
Resource Requests
During Channel
67181075 VS.RAC.TrChSwit Number of Cell Earlier than

chCallReq Resource Requests V900R011
During Channel
67199664 VS.RAC.DL.EqvU- Mean Number of DL Earlier than

serNum Equivalent Voice V900R011
UEs in CEL_DCH
State for Cell
67199663 VS.RAC.UL.EqvU- Mean Number of UL Earlier than

serNum Equivalent Voice V900R011
UEs in CEL_DCH
State for Cell
67204134 VS.Cell.DynShutD Duration of Cell V900R012

own.Time Dynamic Shutdown
Due to Automatic
Shutdown for Cell
67199736 VS.Cell.Unavail- Cell Unavailability Earlier than

Time Duration V900R011
67202567 VS.LC.ULCreditU Mean Usage of UL Earlier than

sed.Mean Credit for Cell V900R011
67191165 VS.LC.ULCreditU Maximum Usage of Earlier than

sed.Max UL Credit for Cell V900R011
67191166 VS.LC.ULCreditU Minimum Usage of Earlier than

sed.Min UL Credit for Cell V900R011
67202570 VS.LC.DLCreditU Mean Usage of DL Earlier than

sed.Mean Credit for Cell V900R011
67191167 VS.LC.DLCreditU Maximum Usage of Earlier than

sed.Max DL Credit for Cell V900R011

BSC6900 UMTS

Description
67191168 VS.LC.DLCreditU Minimum Usage of Earlier than

sed.Min DL Credit for Cell V900R011
67202917 VS.CellBreath.CPI Duration of Earlier than

CHMin.Time Minimum Values of V900R011
CPICH Power Due to
Cell Breathing for
Cell
67202918 VS.CellBreath.CPI Duration of Earlier than

CHMax.Time Maximum Values of V900R011
CPICH Power Due to
Cell Breathing for
Cell
67190846 VS.CellBreath.CPI Number of Upward Earlier than

CHUp CPICH Power V900R011
Adjustments Due to
Cell Breathing for
Cell
67190847 VS.CellBreath.CPI Number of Earlier than

CHDown Downward CPICH V900R011
Power Adjustments
Due to Cell
Breathing for Cell
67202919 VS.CellBreath.TC Duration of TCP Earlier than

PUnder.Time Smaller Than Cell V900R011
Breathing Lower
Threshold for Cell
67202920 VS.CellBreath.TC Duration of TCP Earlier than

POver.Time Greater Than Cell V900R011
Breathing Upper
Threshold for Cell
67202921 VS.CPICH.MeanP Average CPICH V900R013

wr Power for Cell
67190706 VS.DCCC.D2C.Att Number of Dynamic Earlier than

Channel Conversion V900R011
Attempts from DCHs
to FACHs for Cell
67190707 VS.DCCC.C2D.Att Number of Dynamic Earlier than

Channel Conversion V900R011
Attempts from
FACHs to DCHs for
Cell

BSC6900 UMTS

Description
67192001 VS.AMRWB.DLR Number of Increases Earlier than

ateUp of DL Rate for AMR V900R011
WB Speech Service
67192002 VS.AMRWB.DLR Number of Earlier than

ateDown Decreases of DL V900R011
Rate for AMR WB
Speech Service
67192003 VS.AMRWB.ULR Number of Increases Earlier than

ateUp of UL Rate for AMR V900R011
WB Speech Service
67192004 VS.AMRWB.ULR Number of Earlier than

ateDown Decreases of UL V900R011
Rate for AMR WB
Speech Service

il.ULCE.Cong Requests for UL CE V900R011
Resources During
DCCC for Cell

il.DLCE.Cong Requests for DL CE V900R011
Resources During
DCCC for Cell

ULCE.Cong Requests for UL CE V900R011
Resources During
SHO for Cell

DLCE.Cong Requests for DL CE V900R011
Resources During
SHO for Cell

.ULCE.Cong Requests for UL CE V900R011
Resources During
HHO for Cell

.DLCE.Cong Requests for DL CE V900R011
Resources During
HHO for Cell

BSC6900 UMTS

Description

eq.Fail.ULCE.Con Requests for Uplink V900R011
g CE Resources
During RAB
Establishment for
Cell

eq.Fail.DLCE.Con Requests for V900R011
g Downlink CE
Resources During
RAB Establishment
for Cell
67184359 VS.DCCC.AttUpsi Number of UL Earlier than

zing.E2E.Thr EDCH-EDCH V900R011
DCCC Upsizing
Attempts Based on
the Throughput or
RLC BO for Cell
67196026 VS.DCCC.AttDow Number of UL Earlier than

nsizing.E2E.Thr EDCH-EDCH V900R011
DCCC Downsizing
Attempts Based on
the Throughput or
RLC BO for Cell
67196027 VS.DCCC.SuccUps Number of Earlier than

izing.E2E.Thr Successful UL V900R011
EDCH-EDCH
DCCC Upsizings
Based on the
Throughput or RLC
BO for Cell

wnsizing.E2E.Thr Successful UL V900R011
EDCH-EDCH
DCCC Downsizings
Based on the
Throughput or RLC
BO for Cell
67195992 VS.LCC.HSDPA.C Number of UEs V900R012

odeAdj.Att Performing Code
Adjustment Based on
HSDPA for Cell

BSC6900 UMTS

Description

PA.InterRATCS UEs Performing CS V900R011
Inter-RAT
Handovers in Basic
Congestion for Cell

PA.InterRATCS UEs Performing CS V900R011
Inter-RAT
Handovers in Basic
Congestion for Cell
67192585 VS.DCCC.AttUpsi Number of DL DCH Earlier than

zing.DL.Thr DCCC Upsizing V900R011
Attempts Based on
Throughput or RLC
BO for Cell

izing.DL.Thr Successful DL DCH V900R011
DCCC Upsizings
Based on
Throughput or RLC
BO for Cell
67192593 VS.DCCC.AttUpsi Number of UL DCH Earlier than

zing.UL.Thr DCCC Upsizing V900R011
Attempts Based on
Throughput or RLC
BO for Cell

izing.UL.Thr Successful UL DCH V900R011
DCCC Upsizings
Based on
Throughput or RLC
BO for Cell
67192595 VS.DCCC.AttDow Number of UL DCH Earlier than

nsizing.UL.Thr DCCC Downsizing V900R011
Attempts Based on
the Throughput or
RLC BO for Cell

wnsizing.UL.Thr Successful UL DCH V900R011
DCCC Downsizings
Based on
Throughput or RLC
BO for Cell

BSC6900 UMTS

Description

nsizing.UL.Cov DCCC Downsizing V900R011
Attempts Based on
the Coverage (QoS)
for Cell

wnsizing.UL.Cov Successful UL DCH V900R011
DCCC Downsizings
Based on Coverage
(QoS) for Cell

nsizing.UL.Cong DCCC Downsizing V900R011
Attempts Based on
the Resource
Congestion
Algorithm for Cell

wnsizing.UL.Cong Successful UL DCH V900R011
DCCC Downsizings
Based on Resource
Congestion
Algorithm for Cell
67193409 VS.LCC.LDR.Cod Number of UEs Earlier than

eAdj.Succ Performing V900R011
Successful Code
Adjustment in DL
Cell
67193410 VS.LCC.HSDPA.C Number of UEs Earlier than

odeAdj.Succ Performing V900R011
Successful Code
Adjustment Based on
HSDPA for Cell
67204837 VS.Cell.UnavailTi Duration of Cell Earlier than

me.Sys Unavailability Due V900R011
to System Faults for
Cell
67204838 VS.Cell.HSDPA.Un Duration of HSDPA Earlier than

availTime Service V900R011
Unavailability Due
to System Fault for
Cell

BSC6900 UMTS

Description
67204839 VS.Cell.HSUPA.Un Duration of HSUPA V900R012

availTime Service
Unavailability Due
to System Fault for
Cell
73403799 VS.DCCC.P2F.Att Number of Attempts V900R012

to transfer state from
CELL_PCH to
CELL_FACH for
cell
73403800 VS.DCCC.P2F.Suc Number of V900R012

c Successful state
transfer from
CELL_PCH to
CELL_FACH for
cell
73403801 VS.DCCC.P2URA Number of state V900R012

P transfer from
CELL_PCH to
URA_PCH for cell
73403802 VS.DCCC.URAP2 Number of Attempts V900R012

F.Att to transfer state from
URA_PCH to
CELL_FACH for
cell
73403803 VS.DCCC.URAP2 Number of V900R012

F.Succ successful state
transfer from
URA_PCH to
CELL_FACH in the
best cell.
73393802 VS.DynClose.Cell- Number of Cell V900R012

Del Deletions Due to
Dynamic Cell
Shutdown
73393803 VS.DynOpen.Cell- Number of Cell V900R012

Setup Setup Due to
Dynamic Cell
Shutdown

BSC6900 UMTS

Description
73393961 VS.RAC.NewCallR Number of Failed V900R012

eq.Fail.ULPower.C Requests for Uplink
ong Power Resources in
the RAB Setup
Procedure for Cell

eq.Fail.DLPower.C Requests for
ong Downlink Power
Resources in the
RAB Setup
Procedure for Cell

eq.Fail.Code.Cong Requests for Code
Resources in the
RAB Setup
Procedure for Cell

eq.Fail.ULIUBBan Requests for Uplink
d.Cong Iub Bandwidth
Resources in the
RAB Setup
Procedure for Cell

eq.Fail.DLIUBBan Requests for
d.Cong Downlink Iub
Bandwidth
Resources in the
RAB Setup
Procedure for Cell
73421765 VS.DCCC.D2P.Att Number of State V900R012

Transfer Attempts
from CELL_DCH to
CELL_PCH for Cell
73421766 VS.DCCC.D2P.Suc Number of V900R012

c Successful State
Transfers from
CELL_DCH to
CELL_PCH for Cell

BSC6900 UMTS

Description
73421767 VS.DCCC.FastDor Number of State V900R012

mUe.DF2P.Att Transfer Attempts
from CELL_DCH or
CELL_FACH to
CELL_PCH for
FAST
DORMANCY user
for Cell
73421768 VS.DCCC.FastDor Number of V900R012

mUe.DF2P.Succ Successful State
Transfers from
CELL_DCH or
CELL_FACH to
CELL_PCH for
FAST
DORMANCY user
for Cell
73439971 VS.FACH.DTCH. Congestion Duration V900R012

CONG.TIME of DTCHs Carried
over FACHs for Cell
73421933 VS.DCCC.P2D.Att Number of Attempts V900R012

to transfer state from
CELL_PCH to
CELL_DCH for cell
73421934 VS.DCCC.P2D.Suc Number of V900R012

c Successful state
transfer from
CELL_PCH to
CELL_DCH for cell
73421935 VS.DCCC.URAP2 Number of Attempts V900R012

D.Att to transfer state from
URA_PCH to
CELL_DCH for cell
73421936 VS.DCCC.URAP2 Number of V900R012

D.Succ successful state
transfer from
URA_PCH to
CELL_DCH in the
best cell.

BSC6900 UMTS

Description
73422068 VS.DCCC.P2D.DR Number of Attempts V900R012

D.Att of CELL_PCH/
URA_PCH-to-
CELL_DCH State
Transition Together
with DRD for Cell
73422069 VS.DCCC.P2D.DR Number of V900R012

D.Succ Successful
CELL_PCH/
URA_PCH-to-
CELL_DCH State
Transitions Together
with DRDs for Cell
73423313 VS.ULB.CPICH.A Number of CPICH V900R013

djustNum Power Adjustments
Based on RTWP for
Cell
73441123 VS.ULB.CPICHMi Duration of PCPICH V900R013

n.Time Power Under
Minimum RTWP
Threshold
73422160 VS.HSDPA.H2P.At Number of State V900R012

t Transfer Attempts
from CELL_DCH to
CELL_PCH or
URA_PCH for Cell
for HSDPA service
73422161 VS.HSDPA.H2P.Su Number of V900R012

cc Successful Times
That a UE
Performing HSDPA
Services Transits to
CELL_PCH or
URA_PCH State for
cell
73422162 VS.HSUPA.E2P.At Number of Attempts V900R012

t for a UE Performing
HSUPA Services to
Transit to
CELL_PCH or
URA_PCH State for
Cell

BSC6900 UMTS

Description
73422163 VS.HSUPA.E2P.Su Number of V900R012

cc Successful Times
That a UE
Performing HSUPA
CELL_PCH or
URA_PCH State for
cell
73422164 VS.PSR99.D2P.Att Number of Attempts V900R012

for a UE Performing
PS R99 Services to
Transit to
CELL_PCH or
URA_PCH State for
Cell
73422165 VS.PSR99.D2P.Suc Number of V900R012

c Successful Times
That a UE
Performing PS R99
CELL_PCH or
URA_PCH State for
cell
73423357 VS.HSUPAR99.Un Number of Times V900R013

fairness That PS R99 Service
Rate Is Found to Be
Higher than HSUPA
Service Rate
73423358 VS.HSUPAR99.Un Number of PS R99 V900R013

fairness.R99BERa- BE Rate Reduction
teDown Requests Triggered
by Unfairness
Between PS R99
Service Rate and
HSUPA Service Rate
73411191 VS.NodeB.CPU.Co Duration of CPU V900R013

ng.Dur Resource
Insufficiency
Reported by NodeB
for Cell
73439970 VS.FACH.DCCH. Congestion Duration V900R012

CONG.TIME of DCCHs Carried
over FACHs for Cell

BSC6900 UMTS

Description
73424009 VS.FACH.CCCH. Congestion Duration V900R014

CONG.TIME of CCCHs Carried
over FACHs for Cell
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
1.12.1.1 Number of DL Rate Adjustments for AMR Services
Counters
67180678 VS.AMR.DL.RateUp Number of DL Rate

Increases for AMR Services
for Cell
67190519 VS.AMR.DL.RateDown Number of DL Rate

Decreases for AMR Services
for Cell
67192001 VS.AMRWB.DLRateUp Number of Increases of DL

Rate for AMR WB Speech
Service
67192002 VS.AMRWB.DLRateDown Number of Decreases of DL

Service
Description
These counters provide the number of times the DL rate of narrowband or wideband AMR
services is adjusted upward and downward. VS.AMRWB.DLRateUp and
VS.AMRWB.DLRateDown are used for wideband AMR services, VS.AMR.DL.RateUp and
VS.AMR.DL.RateDown are used for narrowband AMR services.

BSC6900 UMTS
Measurement point
The measurement is triggered at point B as shown in the following figure. The RNC sends the
RATE CONTROL control frame to the CN through the IUUP layer to request an increase or
decrease in the DL rate of narrowband or wideband AMR services. If the RNC receives the
RATE CONTROL ACK control frame from the CN, the DL rate of AMR services successfully
increases or decreases. In this case, the RNC measures the counters in the best cell where the
UE camps on.
Figure 1-301 DL AMR rate adjustment procedure
Formula
None
Unit
None
Related Features
VS.AMR.DL.RateUp WRFD-020701 AMR/WB-AMR Speech

Rates Control
VS.AMR.DL.RateDown WRFD-020701 AMR/WB-AMR Speech

Rates Control
VS.AMRWB.DLRateUp WRFD-020701 AMR/WB-AMR Speech

Rates Control
VS.AMRWB.DLRateDown WRFD-020701 AMR/WB-AMR Speech

Rates Control

BSC6900 UMTS
1.12.1.2 Counters Related to the Number of Successful Dynamic Channel

Conversions Between DCH and FACH
Counters
67180675 VS.DCCC.Succ.F2D Number of Successful

Channel Conversions from
FACH to DCH for Cell
67180676 VS.DCCC.Succ.D2F Number of Successful

DCHs to FACHs for Cell
Description
These counters provide the number of successful conversions from the DCH to FACH or from
the FACH to DCH. When a UE in the CELL_DCH state performs a soft handover or softer
handover, the RNC measures counters related to DCH to FACH state transitions in the best cell
before state transition.
Measurement point
The measurement is triggered at point B as shown in the following figure. In the process of state
transition, when the RNC receives the RADIO BEARER RECONFIGURATION COMPLETE
message from the UE, the RNC measures the related counter in the best cell where the UE camps
on before the state transition if the DCH is converted to the FACH. If the FACH is converted to
the DCH, the RNC measures the related counter in the cell where the UE in the CELL_FACH
state camps on after the state transition.
Figure 1-302 Dynamic channel conversion procedure (RB reconfiguration)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.Succ.F2D WRFD-021101 Dynamic Channel

Configuration Control
(DCCC)
VS.DCCC.Succ.D2F WRFD-021101 Dynamic Channel

(DCCC)
1.12.1.3 Number of State Transfer Attempts from CELL_FACH to CELL_PCH
Counters
67192583 VS.DCCC.Att.F2P Number of State Transfer

Attempts from
CELL_FACH to
CELL_PCH for Cell
Description
This counter provides the number of state transition attempts from CELL_FACH to CELL_PCH
in a cell.
Measurement point
The measurement is triggered at point A, as shown in the following figure. When the RNC sends
a RADIO BEARER RECONFIGURATION or PHYSICAL CHANNEL
RECONFIGURATION message to a UE, instructing the UE to transfer from the CELL_FACH
state to the CELL_PCH state, this counter is incremented by one in the cell where the UE is
camping.

BSC6900 UMTS
Figure 1-303 RB reconfiguration and physical channel reconfiguration procedure
Formula
None
Unit
None
Related Features
VS.DCCC.Att.F2P WRFD-021101 Dynamic Channel

(DCCC)
1.12.1.4 Number of Successful State Transfers from CELL_FACH to CELL_PCH
Counters
67192584 VS.DCCC.Succ.F2P Number of Successful State

Transfers from
CELL_FACH to
CELL_PCH for Cell

BSC6900 UMTS
Description
This counter provides the number of successful state transitions from CELL_FACH to
CELL_PCH in a cell.
Measurement point
The measurement is triggered at point B, as shown in the following figure. When the RNC
receives a RADIO BEARER RECONFIGURATION COMPLETE or a PHYSICAL
CHANNEL RECONFIGURATION COMPLETE message from a UE, indicating that the UE
has transfered from the CELL_FACH state to the CELL_PCH state, this counter is incremented
by one in the cell where the UE is camping.
Figure 1-304 RB reconfiguration and physical channel reconfiguration procedure
Formula
None
Unit
None
Related Features
VS.DCCC.Succ.F2P WRFD-021101 Dynamic Channel

(DCCC)

BSC6900 UMTS
1.12.1.5 Counters Related to the Number of Downlink DCH DCCC Downsizing

Attempts Based on Different Strategies
Counters
67192587 VS.DCCC.AttDownsizing. Number of Downlink DCH

DL.Thr DCCC Downsizing Attempts
Based on Throughput or RLC
BO for Cell

DL.Cov DCCC Downsizing Attempts
Based on Coverage (QoS) for
Cell

DL.Cong DCCC Downsizing Attempts
Based on Resource
Congestion Algorithm for
Cell
Description
These counters provide the number of downlink DCH DCCC downsizing attempts based on
different strategies in the best cell where the UE camps on.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending the
RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the related
counter based on different DCCC strategies in the best cell where the UE camps on if downlink
services are carried on the DCH before and after the reconfiguration.

BSC6900 UMTS
Figure 1-305 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
VS.DCCC.AttDownsizing. WRFD-021101 Dynamic Channel

DL.Thr Configuration Control
(DCCC)

DL.Cov Configuration Control
(DCCC)

DL.Cong Configuration Control
(DCCC)

BSC6900 UMTS
1.12.1.6 Counters Related to the Number of Successful DL DCH DCCC

Downsizings Based on Different DCCC Strategies
Counters
67192588 VS.DCCC.SuccDownsizing. Number of Successful DL

DL.Thr DCH DCCC Downsizings
BO for Cell

DL.Cov DCH DCCC Downsizings
Cell

DL.Cong DCH DCCC Downsizings
Based on Resource
Cell
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
counter based on different DCCC strategies in the best cell where the UE camps on if downlink

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.SuccDownsizing. WRFD-021101 Dynamic Channel

DL.Thr Configuration Control
(DCCC)

DL.Cov Configuration Control
(DCCC)

DL.Cong Configuration Control
(DCCC)
1.12.1.7 Counters Related to the Number of UL or DL Overload Congestion

BSC6900 UMTS
Counters
67189852 VS.LCC.OLC.UL.Num Number of UL Overload

67189853 VS.LCC.OLC.DL.Num Number of DL Overload

Description
These counters provide the number of UL or DL overload congestion in a cell. A cell enters the
congestion state when the uplink power or downlink power exceeds the preset Overload Control
(OLC) threshold.
Measurement point
The measurement is triggered at point A as shown in the following figure. After receiving the
COMMON MEASUREMENT REPORT message from the NodeB, the RNC measures the
related counter in the cell where the overload congestion occurs at UL or DL. If a cell is detected
as being in the overload congestion state for two consecutive times, the counter is not increased
by one for the second instance.
Figure 1-307 Common measurement report procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.LCC.OLC.UL.Num WRFD-020107 Overload Control
VS.LCC.OLC.DL.Num WRFD-020107 Overload Control
1.12.1.8 Counters Related to the Duration of UL or DL Overload Congestion
Counters
67203402 VS.LCC.OLC.UL.Time Duration of UL Overload

Congestion for Cell
67203403 VS.LCC.OLC.DL.Time Duration of DL Overload

Congestion for Cell
Description
These counters provide the duration of UL or DL overload congestion in a cell.
Measurement point
After a cell is set up, the RNC measures and accumulates the durations of UL or DL overload
congestion in the cell to obtain the value of these counters in a measurement period.
Formula
None
Unit
s

BSC6900 UMTS
Related Features
VS.LCC.OLC.UL.Time WRFD-020107 Overload Control
VS.LCC.OLC.DL.Time WRFD-020107 Overload Control
1.12.1.9 Number of UEs Transferring BE Service to Common Channel in Overload

Congestion
Counters
67192549 VS.LCC.OLC.D2C Number of UEs Transferring

BE Service to Common
Channel in Overload
Congestion for Cell
Description
When the cell is in overload congestion, the RNC transfer certain UEs performing BE services
to common channels (CCHs) to decrease the throughput of interactive and background services,
thus reducing the cell load. This counter provides the number of UEs performing BE services
that are transferred to CCHs.
Measurement point
When the cell is in overload congestion, the RNC measures the counter in the best cell where
the UE camps on every time a UE performing BE services is transited from the DCH to the
CCH.
Formula
None
Unit
None
Related Features
VS.LCC.OLC.D2C WRFD-020107 Overload Control

BSC6900 UMTS
1.12.1.10 Counters Related to the Duration of Cell in LDR State Due to Congestion
of Various Resources
Counters
67203991 VS.LCC.LDR.Time.UL- Duration of Cell in LDR

Power State Due to UL Power
Congestion for Cell
67203992 VS.LCC.LDR.Time.DLPow Duration of Cell in LDR

er State Due to DL Power
Congestion for Cell
67203993 VS.LCC.LDR.Time.DLCod Duration of Cell in LDR

e State Due to DL Code
Resource Congestion for Cell
67203994 VS.LCC.LDR.Time.ULCE Duration of Cell in LDR

State Due to UL CE Resource
Congestion
67203995 VS.LCC.LDR.Time.DLCE Duration of Cell in LDR

State Due to DL CE Resource
Congestion
67203996 VS.LCC.LDR.Time.ULIub Duration of Cell in LDR

State Due to UL Iub
Transmission Resource
Congestion for Cell
67203997 VS.LCC.LDR.Time.DLIub Duration of Cell in LDR

State Due to DL Iub
Congestion for Cell
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

BSC6900 UMTS
Unit
s
Related Features
VS.LCC.LDR.Time.UL- WRFD-020106 Load Reshuffling

Power
VS.LCC.LDR.Time.DLPow WRFD-020106 Load Reshuffling

er
VS.LCC.LDR.Time.DLCod WRFD-020106 Load Reshuffling

e
VS.LCC.LDR.Time.ULCE WRFD-020106 Load Reshuffling
VS.LCC.LDR.Time.DLCE WRFD-020106 Load Reshuffling
VS.LCC.LDR.Time.ULIub WRFD-020106 Load Reshuffling
VS.LCC.LDR.Time.DLIub WRFD-020106 Load Reshuffling
1.12.1.11 Counters Related to the Number of Times a Cell Is in LDR State Due to
Congestion of Various Resources
Counters
67192637 VS.LCC.LDR.Num.UL- Number of Times a Cell Is in

Power LDR State Due to UL Power
Congestion for Cell
67192638 VS.LCC.LDR.Num.DLPow Number of Times a Cell Is in

er LDR State Due to DL Power
Congestion for Cell
67192639 VS.LCC.LDR.Num.DLCod Number of Times a Cell Is in

e LDR State Due to DL Code
67192640 VS.LCC.LDR.Num.ULCE Number of Times a Cell Is in

LDR State Due to UL CE
67192641 VS.LCC.LDR.Num.DLCE Number of Times a Cell Is in

LDR State Due to DL CE

BSC6900 UMTS
67192642 VS.LCC.LDR.Num.ULIub Number of Times a Cell Is in

LDR State Due to UL Iub
Congestion for Cell
67192643 VS.LCC.LDR.Num.DLIub Number of Times a Cell Is in

LDR State Due to DL Iub
Congestion for Cell
Description
These counters provide the number of times that a cell is in LDR state due to congestion of
various resources.
Measurement point
If the cell is in LDR state due to congestion of various resources, in a measurement period the
RNC measures the number of times that the cell is in LDR state due to uplink or downlink
congestion of various resources.
Formula
None
Unit
None
Related Features
VS.LCC.LDR.Num.UL- WRFD-020106 Load Reshuffling

Power
VS.LCC.LDR.Num.DLPow WRFD-020106 Load Reshuffling

er
VS.LCC.LDR.Num.DLCod WRFD-020106 Load Reshuffling

e
VS.LCC.LDR.Num.ULCE WRFD-020106 Load Reshuffling
VS.LCC.LDR.Num.DLCE WRFD-020106 Load Reshuffling
VS.LCC.LDR.Num.ULIub WRFD-020106 Load Reshuffling
VS.LCC.LDR.Num.DLIub WRFD-020106 Load Reshuffling

BSC6900 UMTS
1.12.1.12 Counters Related to the Number of UEs Performing BE Service TF Control

in Overload Congestion
Counters
67192646 VS.LCC.OLC.UL.TF Number of UEs Performing

BE Service TF Control in UL
Overload Congestion for Cell
67192649 VS.LCC.OLC.DL.TF Number of UEs Performing

BE Service TF Control in DL
Overload Congestion for Cell
Description
When the cell is in overload congestion, the RNC selects certain UEs performing BE services
to implement TF control, that is, reduce the BE throughput based on the MAC control though
the TFC selection process. VS.LCC.OLC.UL.TF and VS.LCC.OLC.DL.TF provide the number
of UEs performing BE service TF control in UL and DL respectively.
Measurement point
When the cell is in overload congestion, every time the RNC selects a UE to perform BE service
TF control, the RNC measures the related counters in the best cell where the UE camps on
according to the UL or DL overload congestion.
Formula
None
Unit
None
Related Features
VS.LCC.OLC.UL.TF WRFD-020107 Overload Control
VS.LCC.OLC.DL.TF WRFD-020107 Overload Control
1.12.1.13 Counters Related to the Number of UEs Released Due to Overload

Congestion

BSC6900 UMTS
Counters
67192647 VS.LCC.OLC.UL.UserRel Number of UEs Released

Due to UL Overload
Congestion for Cell
67191150 VS.LCC.OLC.HSDPA.User Number of HSDPA UEs

Rel Released Due to Overload
Congestion for Cell
67192648 VS.LCC.OLC.HSUPA.User Number of HSUPA UEs

Rel Released during Overload
Congestion for Cell
67192650 VS.LCC.OLC.DL.UserRel Number of UEs Released

Due to DL Overload
Congestion for Cell
Description
When the cell is in overload congestion, the RNC shall release certain UEs if the overload
congestion in the cell cannot be relieved through the following operations: (1) Performing TF
control through BE services. (2) Transferring BE services to CCHs. (3) Decreasing the power
of FACHs. VS.LCC.OLC.UL.UserRel and VS.LCC.OLC.DL.UserRel are used to measure the
number of UEs released due to the UL and DL overload congestions in the cell respectively.
VS.LCC.OLC.HSDPA.UserRel and VS.LCC.OLC.HSUPA.UserRel are used to measure the
number of HSDPA and HSUPA UEs released due to the overload congestion in the cell
respectively.For DC-HSDPA or DC-HSUPA users, this counter is measured only in the cell with
the primary carrier.
Measurement point
When the cell is in overload congestion, every time a UE is released, as shown of point A in
Figure1,the RNC measures VS.LCC.OLC.UL.UserRel and VS.LCC.OLC.DL.UserRel in the
cell where the UE camps on according to the uplink or downlink overload congestion. If a
HSDPA UE is released, the RNC measures VS.LCC.OLC.HSDPA.UserRel in the cell where
the UE camps on. If a HSUPA is released, the RNC measures VS.LCC.OLC.HSUPA.UserRel
in the cell where the UE camps on.

BSC6900 UMTS
Figure 1-308 User release procedure for Cell in congestion state
Formula
None
Unit
None
Related Features
VS.LCC.OLC.UL.UserRel WRFD-020107 Overload Control
VS.LCC.OLC.HSDPA.User WRFD-020107 Overload Control

Rel
VS.LCC.OLC.HSUPA.User WRFD-020107 Overload Control

Rel
VS.LCC.OLC.DL.UserRel WRFD-020107 Overload Control
1.12.1.14 Number of Failed Admissions Due to HSPA User Number Exceeding

Threshold During RAB Establishment for Cell

BSC6900 UMTS
Counters
67192916 VS.RAC.NewCallReq.Fail. Number of Failed

HSDPANum.Cong Admissions Due to HSDPA
User Number Exceeding
Threshold During RAB
Establishment for Cell
67192917 VS.RAC.NewCallReq.Fail. Number of Failed

HSUPANum.Cong Admissions Due to HSUPA
Threshold During RAB
67191843 VS.RAC.NewCallReq.Fail. Number of Failed Requests

ULCE.Cong for Uplink CE Resources
During RAB Establishment
for Cell

DLCE.Cong for Downlink CE Resources
During RAB Establishment
for Cell

ULPower.Cong for Uplink Power Resources
in the RAB Setup Procedure
for Cell

DLPower.Cong for Downlink Power
Resources in the RAB Setup
Procedure for Cell

Code.Cong for Code Resources in the
RAB Setup Procedure for
Cell

ULIUBBand.Cong for Uplink Iub Bandwidth
Procedure for Cell

DLIUBBand.Cong for Downlink Iub Bandwidth
Procedure for Cell

BSC6900 UMTS
Description
These counters provide the number of failed resource requests due to insufficient resources of
different types, such as CE resources, power resources, Iub bandwidth resources, code resources,
number of HSDPA users, and number of HSUPA users, in a cell in the RAB setup procedure.
For DC-HSDPA users, VS.RAC.NewCallReq.Fail.HSDPANum.Cong is measured only in the

cell with the primary carrier. For DC-HSUPA users,
VS.RAC.NewCallReq.Fail.HSUPANum.Cong is measured only in the cell with the primary
carrier.
VS.RAC.NewCallReq.Fail.HSUPANum.Co This counter measure the number of failed

ng admissions due to HSUPA user number
exceeding threshold during RAB
establishment for cell.
Measurement point
The measurement is triggered at point A as shown in Figure 1. After receiving the RAB
ASSIGNMENT REQUEST message from the CN, the RNC initiates the admission procedure
to request different resources. If the resource request fails, the RNC measures these counters in
the cell where the admission fails according to the limited resource type.
Figure 1-309 RAB assignment request admission failure
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.RAC.NewCallReq.Fail. WRFD-01061003 HSDPA Admission Control

HSDPANum.Cong
VS.RAC.NewCallReq.Fail. WRFD-01061202 HSUPA Admission Control

HSUPANum.Cong
VS.RAC.NewCallReq.Fail. WRFD-020101 Admission Control

ULCE.Cong

DLCE.Cong

ULPower.Cong

DLPower.Cong

Code.Cong

ULIUBBand.Cong

DLIUBBand.Cong
1.12.1.15 Number of Preemptions During RAB Establishment
Counters
67192937 VS.RAC.NewCallReq.Pree Number of Preemptions

mpt.Cong During RAB Establishment
for Cell
Description
This counter provides the number of service preemptions in a cell during the RAB establishment.

BSC6900 UMTS
Measurement point
During the RAB establishment, services with high priorities may preempt the resources that are
occupied by services with low priorities. If the resource request fails, the RNC measures the
counter in the cell where the resource request fails The measurement is triggered at point A as
shown in Figure 1. After receiving the RAB ASSIGNMENT REQUEST message from the CN,
the RNC initiates the admission procedure to request different resources. If the resource request
fails, the RNC initiates a procedure of preempting the resources occupied by low-priority
services by high-priority services. This counter is measured in the cell that fails to request the
resources.
Figure 1-310 RAB assignment admission failure
Formula
None
Unit
None
Related Features
VS.RAC.NewCallReq.Pree WRFD-010505 Queuing and Pre-Emption

mpt.Cong
1.12.1.16 Number of Failed Requests for various Resources During SHO for Cell

BSC6900 UMTS
Counters
67192939 VS.RAC.SHO.Fail.ULPowe Number of Failed Requests

r.Cong for UL Power Resources
During SHO for Cell
67192940 VS.RAC.SHO.Fail.DLPowe Number of Failed Requests

r.Cong for DL Power Resources
During SHO for Cell
67192918 VS.RAC.SHO.Fail.Code.Co Number of Failed Requests

ng for Code Resources During
SHO for Cell
67192919 VS.RAC.SHO.Fail.ULIUB Number of Failed Requests

Band.Cong for UL Iub Transmission
Resources During SHO for
Cell
67192920 VS.RAC.SHO.Fail.DLIUB Number of Failed Requests

Band.Cong for DL Iub Transmission
Resources During SHO for
Cell
67192921 VS.RAC.SHO.Fail.HSUPA Number of Failed

Num.Cong Admissions Due to HSUPA
Threshold During SHO for
Cell
67191841 VS.RAC.SHO.Fail.ULCE.C Number of Failed Requests

ong for UL CE Resources During
SHO for Cell
67191842 VS.RAC.SHO.Fail.DLCE.C Number of Failed Requests

ong for DL CE Resources During
SHO for Cell
Description
different types, such as CE resources, power resources, Iub bandwidth resources, and number
of HSUPA users, in a cell in the soft handover procedure.
For DC-HSDPA users, VS.RAC.SHO.Fail.HSUPANum.Cong is measured only in the cell with
Measurement point
The measurement is triggered at point A as shown in Figure 1. After receiving the
MEASUREMENT REPORT message from the UE, the RNC initiates the admission procedure

BSC6900 UMTS
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.
Figure 1-311 admission failure in soft handover
Formula
None
Unit
None
Related Features
VS.RAC.SHO.Fail.ULPowe WRFD-020101 Admission Control

r.Cong
VS.RAC.SHO.Fail.DLPowe WRFD-020101 Admission Control

r.Cong
VS.RAC.SHO.Fail.Code.Co WRFD-020101 Admission Control

ng
VS.RAC.SHO.Fail.ULIUB WRFD-020101 Admission Control

Band.Cong
VS.RAC.SHO.Fail.DLIUB WRFD-020101 Admission Control

Band.Cong
VS.RAC.SHO.Fail.HSUPA WRFD-01061202 HSUPA Admission Control

Num.Cong

BSC6900 UMTS
VS.RAC.SHO.Fail.ULCE.C WRFD-020101 Admission Control

ong
VS.RAC.SHO.Fail.DLCE.C WRFD-020101 Admission Control

ong
1.12.1.17 Number of Failed Requests for various Resources During DCCC for Cell
Counters
67192943 VS.RAC.DCCC.Fail.ULPo Number of Failed Requests

wer.Cong for UL Power Resources
During DCCC for Cell
67192944 VS.RAC.DCCC.Fail.DLPo Number of Failed Requests

wer.Cong for DL Power Resources
67192922 VS.RAC.DCCC.Fail.Code. Number of Failed Requests

Cong for DL Code Resources
67191839 VS.RAC.DCCC.Fail.ULCE. Number of Failed Requests

Cong for UL CE Resources During
DCCC for Cell
67191840 VS.RAC.DCCC.Fail.DLCE. Number of Failed Requests

Cong for DL CE Resources During
DCCC for Cell
Description
different types such as CE resources, power resources, and code resources in a cell in the DCCC
procedure.
Measurement point
The measurement is triggered at point A as shown in the following figure. The admission fails
because of certain limited resources in the DCCC procedure. In this case, the RNC measures the
related counters in the cells where certain resources are limited according to the limited resource
type.

BSC6900 UMTS
Figure 1-312 admisson failure in DCCC procedure
Formula
None
Unit
None
Related Features
VS.RAC.DCCC.Fail.ULPo WRFD-020101 Admission Control

wer.Cong
VS.RAC.DCCC.Fail.DLPo WRFD-020101 Admission Control

wer.Cong
VS.RAC.DCCC.Fail.Code. WRFD-020101 Admission Control

Cong
VS.RAC.DCCC.Fail.ULCE. WRFD-020101 Admission Control

Cong
VS.RAC.DCCC.Fail.DLCE. WRFD-020101 Admission Control

Cong
1.12.1.18 Counters Related to the Number of Failed Requests for Different

Resources During Channel Type Switch

BSC6900 UMTS
Counters
67192923 VS.RAC.TrChSwitch.Fail.U Number of Failed Requests

LCE.Cong for UL CE Resources During
Channel Type Switch for
Cell
67192924 VS.RAC.TrChSwitch.Fail.D Number of Failed Requests

LCE.Cong for DL CE Resources During
Cell

LPower.Cong for UL Power Resources
During Channel Type Switch
for Cell

LPower.Cong for DL Power Resources
During Channel Type Switch
for Cell
67192925 VS.RAC.TrChSwitch.Fail.C Number of Failed Requests

ode.Cong for Code Resources During
Cell

LIUBBand.Cong for UL Iub Transmission
Resources During Channel

LIUBBand.Cong for DL Iub Transmission
Resources During Channel
67192928 VS.RAC.TrChSwitch.Fail.H Number of Failed

SDPANum.Cong Admissions Due to HSDPA
Threshold During Channel
67192929 VS.RAC.TrChSwitch.Fail.H Number of Failed

SUPANum.Cong Admissions Due to HSUPA
Threshold During Channel

BSC6900 UMTS
Description
These counters provide the number of failed resources requests because of limited resources of
different types in a cell during the channel type switch. The resources include CE resources,
power resources, Iub bandwidth resources, code resources, number of HSDPA users, and number
of HSUPA users.
For DC-HSDPA users, VS.RAC.TrChSwitch.Fail.HSDPANum.Cong is measured only in the

cell with the primary carrier.For DC-HSUPA users,
VS.RAC.TrChSwitch.Fail.HSUPANum.Cong is measured only in the cell with the primary
carrier.
Measurement point
The measurement is triggered at point A as shown in Figure 1. During the channel type change,
the RNC initiates the admission procedure to request resources. If the resource request fails, the
RNC measures these counters in the cell where the admission fails according to the limited
resource type. In addition, only the number of failed requests for different resources in a cell
during the channel type change is measured.
Figure 1-313 admission control failure
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RAC.TrChSwitch.Fail.U WRFD-020101 Admission Control

LCE.Cong
VS.RAC.TrChSwitch.Fail.D WRFD-020101 Admission Control

LCE.Cong

LPower.Cong

LPower.Cong
VS.RAC.TrChSwitch.Fail.C WRFD-020101 Admission Control

ode.Cong

LIUBBand.Cong

LIUBBand.Cong
VS.RAC.TrChSwitch.Fail.H WRFD-01061003 HSDPA Admission Control

SDPANum.Cong
VS.RAC.TrChSwitch.Fail.H WRFD-01061202 HSUPA Admission Control

SUPANum.Cong
1.12.1.19 Number of Failed Requests for various Resources During HHO for Cell
Counters
67192941 VS.RAC.HHO.Fail.ULPow Number of Failed Requests

er.Cong for UL Power Resources
During HHO for Cell
67192942 VS.RAC.HHO.Fail.DLPow Number of Failed Requests

er.Cong for DL Power Resources
During HHO for Cell
67192930 VS.RAC.HHO.Fail.ULIUB Number of Failed Requests

Band.Cong for UL Iub Transmission
Resources During HHO for
Cell

BSC6900 UMTS
67192931 VS.RAC.HHO.Fail.DLIUB Number of Failed Requests

Band.Cong for DL Iub Transmission
Resources During HHO for
Cell
67192932 VS.RAC.HHO.Fail.HSDPA Number of Failed

Num.Cong Admissions Due to HSDPA
Threshold During HHO for
Cell
67192933 VS.RAC.HHO.Fail.HSUPA Number of Failed

Num.Cong Admissions Due to HSUPA
Threshold During HHO for
Cell
67189859 VS.RAC.HHO.Fail.Code.C Number of Failed Requests

ong for Code Resources During
HHO for Cell
67192492 VS.RAC.HHO.Fail.ULCE. Number of Failed Requests

Cong for UL CE Resources During
HHO for Cell
67192493 VS.RAC.HHO.Fail.DLCE. Number of Failed Requests

Cong for DL CE Resources During
HHO for Cell
Description
These counters provide the number of failed resources requests due to insufficient resources of
different types, such as CE resources, power resources, Iub bandwidth resources, code resources,
number of HSDPA users, and number of HSUPA users, in a cell during the hard handover. For
DC-HSDPA users, VS.RAC.HHO.Fail.HSDPANum.Cong is measured only in the cell with the
primary carrier. For DC-HSUPA users, VS.RAC.HHO.Fail.HSUPANum.Cong is measured
only in the cell with the primary carrier.
Measurement point
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.

BSC6900 UMTS
Figure 1-314 admission control failure in hard handover
Formula
None
Unit
None
Related Features
VS.RAC.HHO.Fail.ULPow WRFD-020101 Admission Control

er.Cong
VS.RAC.HHO.Fail.DLPow WRFD-020101 Admission Control

er.Cong
VS.RAC.HHO.Fail.ULIUB WRFD-020101 Admission Control

Band.Cong
VS.RAC.HHO.Fail.DLIUB WRFD-020101 Admission Control

Band.Cong
VS.RAC.HHO.Fail.HSDPA WRFD-01061003 HSDPA Admission Control

Num.Cong
VS.RAC.HHO.Fail.HSUPA WRFD-01061202 HSUPA Admission Control

Num.Cong
VS.RAC.HHO.Fail.Code.C WRFD-020101 Admission Control

ong
VS.RAC.HHO.Fail.ULCE. WRFD-020101 Admission Control

Cong

BSC6900 UMTS
VS.RAC.HHO.Fail.DLCE. WRFD-020101 Admission Control

Cong
1.12.1.20 Number of Preemptions During HHO
Counters
67192938 VS.RAC.HHO.Preempt.Con Number of Preemptions

g During HHO for Cell
Description
This counter provides the number of service preemptions in a cell during the hard handover.
Measurement point
measurement report, the RNC initiates the admission procedure to request resources if the RNC
decides to perform a hard handover. If the resource request fails, the RNC initiates a procedure
of preempting the resources occupied by low-priority services by high-priority services and
measures the counter in the cell that performs preemption.
Figure 1-315 admission control failure in hard handover
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.RAC.HHO.Preempt.Con WRFD-010505 Queuing and Pre-Emption

g
1.12.1.21 Number of MBMS PTM Service Releases in Overload Congestion
Counters
67194970 VS.LCC.OLC.MBMS.PTM. Number of MBMS PTM

RBRel Service Releases in Overload
Congestion for Cell
Description
This counter provides the number of times the MBMS PTM service is released when the cell is
in overload congestion.
Measurement point
When the cell is in overload congestion and the MBMS PTM service releases, the RNC measures
the counter.
Formula
None
Unit
None
Related Features
VS.LCC.OLC.MBMS.PTM. WRFD-020107 Overload Control

RBRel

BSC6900 UMTS
1.12.1.22 Number of MBMS PTP Service Releases in Overload Congestion
Counters
67194971 VS.LCC.OLC.MBMS.PTP. Number of MBMS PTP

RBRel Service Releases in Overload
Congestion for Cell
Description
This counter provides the number of the times the RB is released due to the MBMS PTP services
when the cell is in overload congestion.
Measurement point
When the cell is in overload congestion and the MBMS PTP services trigger the RB release, the
RNC measures the counter.
Formula
None
Unit
None
Related Features
VS.LCC.OLC.MBMS.PTP. WRFD-020107 Overload Control

RBRel
1.12.1.23 Counters Related to the Number of UEs Performing Inter-Frequency Load

Handovers in Basic Congestion
Counters
67190435 VS.LCC.LDR.InterFreq Number of UEs Performing

Inter-Frequency Load
Handovers in Basic
Congestion for Cell

BSC6900 UMTS
67192644 VS.LCC.LDR.HSUPA.In- Number of HSUPA UEs

terFreq Performing Inter-Frequency
Load Handovers in Basic
Congestion for Cell
67191151 VS.LCC.LDR.HSDPA.In- Number of HSDPA UEs

terFreq Performing Inter-Frequency
Load Handovers in Basic
Congestion for Cell
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. For DC-HSDPA users, this counter is
measured only in the cell with the primary carrier. VS.LCC.LDR.HSUPA.InterFreq is used to
measure the number of HSUPA UEs performing inter-frequency handovers.For DC-HSUPA
users, this counter is measured only in the cell with the primary carrier.
Measurement point
When the cell is in basic congestion, VS.LCC.LDR.InterFreq is measured in the cell where the
UE camps on every time the RNC selects a UE to perform inter-frequency handover. If the RNC
selects an HSDPA UE, VS.LCC.LDR.HSDPA.InterFreq is measured in the cell where the UE
camps on. If the RNC selects an HSUPA UE, VS.LCC.LDR.HSUPA.InterFreq is measured in
the cell where the UE camps on.
Formula
None
Unit
None
Related Features
VS.LCC.LDR.InterFreq WRFD-020103 Inter Frequency Load

Balance
VS.LCC.LDR.HSUPA.In- WRFD-020103 Inter Frequency Load

terFreq Balance
VS.LCC.LDR.HSDPA.In- WRFD-020103 Inter Frequency Load

terFreq Balance

BSC6900 UMTS
1.12.1.24 Counters Related to the Number of UEs Performing BE Service

Downsizing in Basic Congestion
Counters
67190436 VS.LCC.LDR.UL.BERate- Number of UEs Performing

Down BE Service Downsizing in
UL Basic Congestion
67190437 VS.LCC.LDR.DL.BERate- Number of UEs Performing

Down BE Service Downsizing in
DL Basic Congestion
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.LCC.LDR.UL.BERate- WRFD-020106 Load Reshuffling

Down
VS.LCC.LDR.DL.BERate- WRFD-020106 Load Reshuffling

Down
1.12.1.25 Counters Related to the Number of UEs Performing Uncontrollable Real-

Time Service QoS Renegotiation in Basic Congestion
Counters
67190438 VS.LCC.LDR.UL.QosRe- Number of UEs Performing

Nego Uncontrollable Real-Time
Service QoS Renegotiation
in UL Basic Congestion for
Cell
67190439 VS.LCC.LDR.DL.QosRe- Number of UEs Performing

Nego Uncontrollable Real-Time
Service QoS Renegotiation
in DL Basic Congestion for
Cell
Description
When the cell is in basic congestion, the RNC decreases the service QoS of certain UEs
performing uncontrollable real-time service to relieve congestion.
VS.LCC.LDR.UL.QosReNego and VS.LCC.LDR.DL.QosReNego provide the number of UEs
performing uncontrollable real-time service QoS renegotiation according to the UL or DL
congestion respectively.
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,

BSC6900 UMTS
the RNC sends the RAB MODIFY REQUEST message to the CN. In this case, the RNC
measures the related counter in the cell where the UE camps on according to the UL or DL
congestion.
Figure 1-317 Uncontrollable real-time service QoS renegotiation procedure
Formula
None
Unit
None
Related Features
VS.LCC.LDR.UL.QosRe- WRFD-020106 Load Reshuffling

Nego
VS.LCC.LDR.DL.QosRe- WRFD-020106 Load Reshuffling

Nego
1.12.1.26 Counters Related to the Number of UEs Performing CS Inter-RAT


BSC6900 UMTS
Counters
67190440 VS.LCC.LDR.InterRATCS Number of UEs Performing

CS Inter-RAT Handovers in
Basic Congestion for Cell

terRATCS Performing CS Inter-RAT
Handovers in Basic
Congestion for Cell

terRATCS Performing CS Inter-RAT
Handovers in Basic
Congestion for Cell
Description
When the cell is in basic congestion, the RNC selects certain UEs to perform CS inter-RAT load
handover. VS.LCC.LDR.InterRATCS is used to measure the number of UEs performing CS
inter-RAT handovers. VS.LCC.LDR.HSDPA.InterRATCS is used to measure the number of
HSDPA UEs performing CS inter-RAT handovers. For DC-HSDPA users, this counter is
measured only in the cell with the primary carrier. VS.LCC.LDR.HSUPA.InterRATCS is used
to measure the number of HSUPA UEs performing CS inter-RAT handovers.For DC-HSUPA
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
VS.LCC.LDR.InterRATCS WRFD-020306 Inter-RAT Handover Based

on Load

BSC6900 UMTS
VS.LCC.LDR.HSUPA.In- WRFD-020306 Inter-RAT Handover Based

terRATCS on Load
VS.LCC.LDR.HSDPA.In- WRFD-020306 Inter-RAT Handover Based

terRATCS on Load
1.12.1.27 Counters Related to the Number of UEs Performing PS Inter-RAT

Counters
67190441 VS.LCC.LDR.InterRATPS Number of UEs Performing

PS Inter-RAT Handovers in

terRATPS Performing PS Inter-RAT
Handover in Basic
Congestion for Cell

terRATPS Performing PS Inter-RAT
Handovers in Basic
Congestion for Cell
Description
When the cell is in basic congestion, the RNC selects certain UEs to perform PS inter-RAT load
handovers. VS.LCC.LDR.InterRATPS is used to measure the number of UEs performing PS
inter-RAT handovers. VS.HSDPA.LDR.InterRATPS is used to measure the number of HSDPA
UEs performing PS inter-RAT handovers. For DC-HSDPA users, this counter is measured only
in the cell with the primary carrier. VS.LCC.LDR.HSUPA.InterRATPS is used to measure the
number of HSUPA UEs performing PS inter-RAT handovers. For DC-HSDPA users, this
counter is measured only in the cell with the primary carrier.
Measurement point
When the cell is in basic congestion, VS.LCC.LDR.InterRATPS is measured in the cell where
the UE camps on every time the RNC selects a UE to perform PS inter-RAT handover. If the
RNC selects an HSDPA UE, VS.HSDPA.LDR.InterRATPS is measured in the cell where the
UE camps on. If the RNC selects an HSUPA UE, VS.LCC.LDR.HSUPA.InterRATPS is
measured in the cell where the UE camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.LCC.LDR.InterRATPS WRFD-020306 Inter-RAT Handover Based

on Load
VS.LCC.LDR.HSUPA.In- WRFD-020306 Inter-RAT Handover Based

terRATPS on Load
VS.LCC.LDR.HSDPA.In- WRFD-020306 Inter-RAT Handover Based

terRATPS on Load
1.12.1.28 Counters Related to the Number of UEs Performing AMR Rate Decrease
in Basic Congestion
Counters
67192426 VS.LCC.LDR.AMRRateUL Number of UEs Performing

AMR Rate Decrease in UL
67192427 VS.LCC.LDR.AMRRateDL Number of UEs Performing

AMR Rate Decrease in DL
Description
When the cell is in basic congestion, the RNC selects certain UEs to perform narrowband and
wideband AMR services rate decrease. VS.LCC.LDR.AMRRateUL and
VS.LCC.LDR.AMRRateDL provide the number of UEs performing AMR rate decrease
according to the UL or DL congestion respectively.
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.LCC.LDR.AMRRateUL WRFD-020106 Load Reshuffling
VS.LCC.LDR.AMRRateDL WRFD-020106 Load Reshuffling
1.12.1.29 Number of UEs Performing Code Adjustment Attempts in DL Basic

Congestion for Cell
Counters
67192397 VS.LCC.LDR.CodeAdj.Att Number of UEs Performing

Code Adjustment Attempts
Cell
Description
When the cell is in basic congestion, the RNC selects certain UEs to perform code adjustment
attempts. The counter provides the number of UEs performing code adjustment attempts in a
cell. When a cell is in basic congestion of downlink code resources, the RNC selects certain UEs
in the cell to perform code adjustment so that some idle codes are combined to meet the
requirement of a higher rate.
Measurement point
When the cell is in basic congestion, the RNC measures the counter in the cell where the UE
camps on every time the RNC selects a UE to perform code adjustment attempt.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.LCC.LDR.CodeAdj.Att WRFD-020106 Load Reshuffling
1.12.1.30 Number of MBMS Services Performing Power Decreasing in Basic

Congestion
Counters
67192398 VS.LCC.LDR.MbmsPower- Number of MBMS Services

Dec Performing Power
Decreasing in Basic
Congestion for Cell
Description
When the cell is in basic congestion, the RNC selects certain MBMS services to perform power
decreasing. This counter provides the number of MBMS services performing power decreasing
in a cell.
Measurement point
When the cell is in basic congestion, the RNC measures the counter in the cell where the MBMS
service is processed every time the RNC selects an MBMS service to perform power decreasing.
Formula
None
Unit
None
Related Features
VS.LCC.LDR.MbmsPower- WRFD-020106 Load Reshuffling

Dec

BSC6900 UMTS
1.12.1.31 Counters Related to the Number of Qoffset Updates Due to Load Level
Change
Counters
67189856 VS.PUC.High.Offset.Updt Number of Qoffset Updates

Due to Heavy Load for Cell
67189857 VS.PUC.Light.Offset.Updt Number of Qoffset Updates

Due to Light Load for Cell
67189858 VS.PUC.Norm.Offset.Updt Number of Qoffset Updates

Due to Normal Load for Cell
Description
These counters provide the number of Qoffset updates by the PUC (Potential User Control)
algorithm when the load of the current cell becomes light, normal, or heavy. Qoffset, the
selection/reselection parameter in system information block (SIB) 11, defines the selection/
reselection offset between two cells. The network can instruct a UE to camp on either of the two
cells based on the value for Qoffset. For details about this parameter, see 3GPP TS 25.304. PUC
algorithm: When the load of the serving cell is light, the RNC sets the Qoffset between the
serving cell and the neighboring cells to a larger value by updating system information.
Therefore, the UE in idle mode is not apt to reselect another heavily-loaded cell. When the load
of the serving cell is heavy, the RNC sets the Qoffset between the serving cell and the neighboring
cells to a smaller value by updating system information. Therefore, the UE in idle mode is apt
to reselect another lightly-loaded cell, which reduces the potential load of the current cell.
Measurement point
The measurement is triggered at point A shown in the following figure. The RNC measures the
related counter when updating Qoffset in SIB 11 according to the change in the cell load level
in the common measurement report.

BSC6900 UMTS
Figure 1-318 Qoffset update procedure (based on load)
Formula
None
Unit
None
Related Features
VS.PUC.High.Offset.Updt WRFD-020105 Potential User Control
VS.PUC.Light.Offset.Updt WRFD-020105 Potential User Control
VS.PUC.Norm.Offset.Updt WRFD-020105 Potential User Control
1.12.1.32 Counters Related to the Number of Sintersearch Updates Due to Cell Load
Change

BSC6900 UMTS
Counters
67190444 VS.PUC.High.IntSrch.Updt Number of Sintersearch

Updates Due to Heavy Load
for Cell
67190442 VS.PUC.Light.IntSrch.Updt Number of Sintersearch

Updates Due to Light Load
for Cell
67190443 VS.PUC.Norm.IntSrch.Updt Number of Sintersearch

Updates Due to Normal Load
for Cell
Description
These counters provide the number of Sintersearch updates by the PUC (Potential User Control)
algorithm when the load of the current cell becomes light, normal, or heavy. Sintersearch, the
selection/reselection parameter in system information block (SIB) 3, defines the quality
requirement of starting a measurement for inter-frequency cell reselection. If the UE finds that
the quality of the serving cell is worse than the value for Sintersearch, it starts the inter-frequency
measurement so that UE can reselect to another cell. PUC algorithm: When the load of the
serving cell is light, the RNC can set a smaller value for Sintersearch by updating system
information. Therefore, the UE in idle mode is not apt to start cell reselection. When the load of
the serving cell is heavy, the RNC can set a larger value for Sintersearch by updating system
information. Therefore, the UE in idle mode is apt to start cell reselection, which reduces the
potential load of the current cell.
Measurement point
The measurement is triggered at point A shown in the following figure. The RNC measures the
related counter when updating Sintersearch in SIB 3 according to the change in the cell load
level in the common measurement report.

BSC6900 UMTS
Figure 1-319 Sintersearch update procedure (based on load)
Formula
None
Unit
None
Related Features
VS.PUC.High.IntSrch.Updt WRFD-020105 Potential User Control
VS.PUC.Light.IntSrch.Updt WRFD-020105 Potential User Control
VS.PUC.Norm.IntSrch.Updt WRFD-020105 Potential User Control
1.12.1.33 Number of Successful Cell Resource Requests During HHO

BSC6900 UMTS
Counters
67181079 VS.RAC.HHOCallAcc Number of Successful Cell

Resource Requests During
HHO for Cell
Description
After receiving a measurement report from the UE, the RNC requests cell resources for a
successful hard handover to a new cell. This counter provides the number of successful cell
resource requests in the target cell during a hard handover.
Measurement point
The measurement is triggered at point B as shown in the following figure. After receiving the
MEASUREMENT REPORT message from the UE, the RNC requests cell resources for hard
handover to a new cell. If the request succeeds, the RNC measures the counter in the target cell
for handover.
Figure 1-320 Successful handover admission
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RAC.HHOCallAcc WRFD-020101 Admission Control
1.12.1.34 Number of Cell Resource Requests During HHO
Counters
67181074 VS.RAC.HHOCallReq Number of Cell Resource

Requests During HHO for
Cell
Description
After receiving a measurement report from the UE, the RNC requests cell resource for hard
handover to a new cell. This counter provides the number of cell resource requests for hard
handover in the target cell.
Measurement point
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

BSC6900 UMTS
Unit
None
Related Features
VS.RAC.HHOCallReq WRFD-020101 Admission Control
1.12.1.35 Number of Successful Cell Resource Requests During RAB Establishment
Counters
67181076 VS.RAC.NewCallAcc Number of Successful Cell

RAB Establishment for Cell
Description
This counter provides the number of successful cell resource requests during the RAB
establishment.
Measurement point
The measurement is triggered at point B as shown in the Figure1. After receiving the RAB
ASSIGNMENT REQUEST message from the CN, the RNC requests cell resources for the UE.
In this case, the counter will be measured in the cell in which the resources(E.g. Iub bandwidth,
CE, power, code, user number etc.) are assigned successfully. If the assignments succeed in
more than one cell(E.g. in SHO or DRD case.), the RNC measures the counter in every cell in
which the assignments succeed.

BSC6900 UMTS
Figure 1-322 Successful admission during the RAB establishment
Formula
None
Unit
None
Related Features
VS.RAC.NewCallAcc WRFD-020101 Admission Control
1.12.1.36 Number of Cell Resource Requests During RAB Establishment

BSC6900 UMTS
Counters
67181071 VS.RAC.NewCallReq Number of Cell Resource

Requests During RAB
Description
This counter provides the number of cell resource requests during the RAB establishment.
Measurement point
The measurement is triggered at point A as shown in the Figure1. After receiving the RAB
ASSIGNMENT REQUEST message from the CN, the RNC requests cell resources for the UE.
In this case, the counter will be measured in the cell in which the resources(E.g. Iub bandwidth,
CE, power, code, user number etc.) are requested. If the resources are requested in more than
one cell(E.g. in SHO or DRD case.), the RNC measures the counter in every cell in which the
resources are requested.
Figure 1-323 Successful admission during the RAB establishment
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RAC.NewCallReq WRFD-020101 Admission Control
1.12.1.37 Number of Successful Cell Resource Requests due to UE Service

Reconfiguration (Cell)
Counters
67181078 VS.RAC.ReconfigCallAcc Number of Successful Cell

Resource Requests Due to
UE RAB Reconfiguration for
Cell
Description
This counter provides the number of successful cell resource requests during the RAB
modification process.
Measurement point
When the RNC receives a RAB ASSIGNMENT REQUEST message with the cause of "RABs
To Be Modified", it shall request cell resource again for this UE. If the request succeeds, as
shown of point B in Figure1, the RNC measures this item in the cell that the UE camps on.
Figure 1-324 RAB reconfiguration procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAC.ReconfigCallAcc WRFD-020101 Admission Control
1.12.1.38 Number of Cell Resource Requests due to UE Service Reconfiguration

(Cell)
Counters
67181073 VS.RAC.ReconfigCallReq Number of Cell Resource

Requests Due to UE RAB
Reconfiguration for Cell
Description
This counter provides the number of cell resource requests during the RAB modification process.
Measurement point
The measurement is triggered at point A as shown in Figure1. When receiving a RAB
ASSIGNMENT REQUEST message with the cause value of "RABs To Be Modified", the RNC
requests cell resources again for this UE. In this case, the RNC measures this item in the cell
that the UE camps on.
Figure 1-325 RAB reconfiguration procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAC.ReconfigCallReq WRFD-020101 Admission Control
1.12.1.39 Number of Successful Cell Resource Requests During SHO
Counters
67181077 VS.RAC.SHOCallAcc Number of Successful Cell

SHO for Cell
Description
After receiving an intra-frequency measurement report from the UE, the RNC requests cell
resources for a successful soft handover to a new cell. This counter provides the number of
successful cell resource requests in the target cell where the UE is handed over during a soft
handover.
Measurement point
The measurement is triggered at point B as shown in the following figure. After receiving the
MEASUREMENT REPORT message from the UE, the RNC requests cell resources for soft
handover to a new cell. If the request succeeds, the RNC measures the counter in the target cell
for handover. If the request for multiple cells' resources succeeds, the RNC measures the counter
in each cell.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAC.SHOCallAcc WRFD-020101 Admission Control
1.12.1.40 Number of Cell Resource Requests During SHO
Counters
67181072 VS.RAC.SHOCallReq Number of Cell Resource

Requests During SHO for
Cell
Description
After receiving an intra-frequency measurement report from the UE, the RNC requests cell
resource for soft handover to a new cell. This counter provides the number of cell resource
requests for soft handover in the target cell for handover.

BSC6900 UMTS
Measurement point
MEASUREMENT REPORT message from the UE, the RNC requests cell resources for soft
handover to a new cell. In this case, the RNC measures the counter in the target cell for handover.
If the request for multiple cells' resources succeeds, the RNC measures the counter in each cell.
Formula
None
Unit
None
Related Features
VS.RAC.SHOCallReq WRFD-020101 Admission Control
1.12.1.41 Number of Successful Cell Resource Requests During Channel Type

Switch

BSC6900 UMTS
Counters
67181080 VS.RAC.TrChSwitchCal- Number of Successful Cell

lAcc Resource Requests During
Cell
Description
When a UE experiences a channel type change, such as from the FACH to the DCH or from the
DCH to the FACH, the RNC requests cell resources for the UE again. This counter provides the
number of successful cell resource requests in a cell during the channel type change. Only the
number of successful cell resource requests in a cell during the channel type change is measured.
Measurement point
The measurement is triggered at point B as shown in the following figure. During a channel type
change, the RNC requests related resources. If the resource request succeeds, the RNC measures
the counter in the cell where the UE camps on.
Figure 1-328 admission success
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RAC.TrChSwitchCal- WRFD-020101 Admission Control

lAcc
1.12.1.42 Number of Cell Resource Requests During Channel Type Switch
Counters
67181075 VS.RAC.TrChSwitchCall- Number of Cell Resource

Req Requests During Channel
Description
The measurement is triggered at point A as shown in the following figure. When the type of
channel where the UE occupies in a cell switches, the RNC requests related resources and
measures the counter in the cell where the UE camps on.
Measurement point
When the type of channel where the UE occupies in a cell switches, the RNC requests cell
resources for the UE. In this case, the RNC measures the counter in the cell where the UE camps
on.
Figure 1-329 admission control in channel type switch

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAC.TrChSwitchCall- WRFD-020101 Admission Control

Req
1.12.1.43 Counters Related to the Mean Number of Equivalent Voice UEs in

CEL_DCH State
Counters
67199663 VS.RAC.UL.EqvUserNum Mean Number of UL

Equivalent Voice UEs in
CEL_DCH State for Cell
67199664 VS.RAC.DL.EqvUserNum Mean Number of DL

Equivalent Voice UEs in
CEL_DCH State for Cell
Description
These counters provide the mean number of UL and DL equivalent UEs in CELL_DCH state
in a cell within a measurement period.
Measurement point
In a measurement period, the RNC samples the number of equivalent UEs in the CELL_DCH
state in the UL and DL every 5 seconds. At the end of the measurement period, the RNC divides
the accumulated data from all the sampling points by the number of samples to obtain the values
of the related counters.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.RAC.UL.EqvUserNum WRFD-020101 Admission Control
VS.RAC.DL.EqvUserNum WRFD-020101 Admission Control
1.12.1.44 Duration of Cell Dynamic Shutdown Due to Automatic Shutdown
Counters
67204134 VS.Cell.DynShutDown.Tim Duration of Cell Dynamic

e Shutdown Due to Automatic
Shutdown for Cell
Description
This counter provides the duration of cell dynamic shutdown when the cell dynamic shutdown
algorithm takes effect.
Measurement point
After a cell is set up, the RNC measures the accumulated duration of cell dynamic shutdown in
the measurement period.
Formula
None
Unit
s

BSC6900 UMTS
Related Features
VS.Cell.DynShutDown.Tim WRFD-020117 Multi-Carrier Switch off

e WRFD-020122 Based on Traffic Load
Multi-Carrier Switch off
Based on QoS
1.12.1.45 Cell Unavailability Duration caused by O&M (Cell)
Counters
67199736 VS.Cell.UnavailTime Cell Unavailability Duration
Description
This counter provides the duration of cell unavailability due to cell maintenance and operation.
Measurement point
After a cell is set up, all services may become unavailable in the cell if the cell is blocked on the
LMT. In this case, the RNC measures the duration of service unavailability to obtain the value
of this counter in a measurement period.
Formula
None
Unit
s
Related Features
VS.Cell.UnavailTime WRFD-031000 Intelligently Out of Service
1.12.1.46 Counters Related to the Cell Credit Usage

BSC6900 UMTS
Counters
67202567 VS.LC.ULCreditUsed.Mean Mean Usage of UL Credit for

Cell
67191165 VS.LC.ULCreditUsed.Max Maximum Usage of UL

Credit for Cell
67191166 VS.LC.ULCreditUsed.Min Minimum Usage of UL

Credit for Cell
67202570 VS.LC.DLCreditUsed.Mean Mean Usage of DL Credit for

Cell
67191167 VS.LC.DLCreditUsed.Max Maximum Usage of DL

Credit for Cell
67191168 VS.LC.DLCreditUsed.Min Minimum Usage of DL

Credit for Cell
Description
These counters provide uplink or downlink credit usage on the RNC side in a cell. Note: Credit
resources on the RNC side are equivalent to CE resources on the NodeB side. The uplink credit
number is twice the number of uplink CEs, and the downlink credit number is equal to the number
of downlink CEs. The CE-related counters measured at the RNC have different values from
these measured at the NodeB. CE-related counters measured at the RNC are mainly used to
estimate the access capability and are measured based on the number of CEs consumed in the
access strategy. CE-related counters measured at the NodeB are mainly used to calculate the
CEs that are actually used. In addition, the sampling period of the CE-related counters measured
at the RNC is 5s, which is different from that of the CE-related counters measured at the NodeB
(2 ms). Therefore, the counter values are not comparable, extremely when the NodeB dynamic
CE function is enabled.
Measurement point
The RNC takes samples from the UL and DL credit usage in the cell every 5s. At the end of the
measurement period, the RNC calculates the maximum and minimum credit usage, and divides
the accumulated credit usage by the number of samples to obtain the mean usage of both UL
and DL credit resources in the measurement period.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.LC.ULCreditUsed.Mean WRFD-020101 Admission Control
VS.LC.ULCreditUsed.Max WRFD-020101 Admission Control
VS.LC.ULCreditUsed.Min WRFD-020101 Admission Control
VS.LC.DLCreditUsed.Mean WRFD-020101 Admission Control
VS.LC.DLCreditUsed.Max WRFD-020101 Admission Control
VS.LC.DLCreditUsed.Min WRFD-020101 Admission Control
1.12.1.47 Counters Related to the Duration of Max and Min Values of CPICH Power
Due to Cell Breathing
Counters
67202917 VS.CellBreath.CPICHMin. Duration of Minimum

Time Values of CPICH Power Due
to Cell Breathing for Cell
67202918 VS.CellBreath.CPICHMax. Duration of Maximum

Time Values of CPICH Power Due
to Cell Breathing for Cell
Description
These counters provide the duration of maximum or minimum value of P-CPICH power due to
the downlink load-based dynamic adjustment of P-CPICH algorithm in a cell. Note: 1. The
downlink load-based dynamic adjustment of P-CPICH algorithm refers to the TCP-based intra-
frequency load balancing algorithm or load-based dynamic adjustment of P-CPICH algorithm.
2. The preceding two algorithms mutually exclude each other. When the two algorithms are
enabled at the same time, the load-based dynamic adjustment of P-CPICH algorithm takes
precedence. 3. If the two algorithms are disabled in the measurement period, the value of this
counter is zero.
Measurement point
When the downlink cell power load in a cell is heavy according to the load level specified by
the dynamic adjustment of P-CPICH algorithm, the RNC needs to reduce the power of P-CPICH.
However, if the power of P-CPICH reaches the minimum value, the P-CPICH power cannot be
reduced. The controlling RNC (CRNC) measures the accumulated duration of the maximum
value of P-CPICH power for a cell in the measurement period. When the downlink cell power
load in a cell is light according to the load level specified by the dynamic adjustment of P-CPICH

BSC6900 UMTS
algorithm, the RNC needs to increase the power of P-CPICH. However, if the power of P-CPICH
reaches the maximum value, P-CPICH power cannot be increased. The CRNC measures the
accumulated duration of the minimum value of P-CPICH power for a cell in the measurement
period.
Formula
None
Unit
s
Related Features
VS.CellBreath.CPICHMin. WRFD-020104 Intra Frequency Load

Time Balance
VS.CellBreath.CPICHMax. WRFD-020104 Intra Frequency Load

Time Balance
1.12.1.48 Counters Related to the Number of CPICH Power Adjustments Due to

Cell Breathing
Counters
67190846 VS.CellBreath.CPICHUp Number of Upward CPICH

Power Adjustments Due to
Cell Breathing for Cell
67190847 VS.CellBreath.CPICHDown Number of Downward

CPICH Power Adjustments
Due to Cell Breathing for
Cell
Description
These counters provide the number of P-CPICH power adjustments due to the downlink load-
based dynamic adjustment of P-CPICH algorithm in a cell.
Measurement point
When the downlink cell power load in a cell is heavy according to the load level specified by
the dynamic adjustment of P-CPICH algorithm, the RNC needs to reduce the power of P-CPICH.

BSC6900 UMTS
When the downlink cell power load in a cell is light according to the load level specified by the
dynamic adjustment of P-CPICH algorithm, the RNC needs to increase the power of P-CPICH.
The CRNC measures the number of P-CPICH power adjustments for a cell in the measurement
period. Note: 1. The downlink load-based dynamic adjustment of P-CPICH algorithm refers to
the TCP-based intra-frequency load balancing algorithm or load-based dynamic adjustment of
P-CPICH algorithm. If the former algorithm is used, downlink power refers to transmitted carrier
power (TCP). If the latter is used, downlink power refers to non-HSDPA transmit power
(NonHSTCP). 2. The preceding two algorithms mutually exclude each other. When the two
algorithms are enabled at the same time, the load-based dynamic adjustment of P-CPICH
algorithm takes precedence. 3. If the two algorithms are disabled in the measurement period, the
value of this counter is zero.
Formula
None
Unit
None
Related Features
VS.CellBreath.CPICHUp WRFD-020104 Intra Frequency Load

Balance
VS.CellBreath.CPICHDown WRFD-020104 Intra Frequency Load

Balance
1.12.1.49 Counters Related to the Duration of TCP Underload and Overload
Counters
67202919 VS.CellBreath.TCPUnder.T Duration of TCP Smaller

ime Than Cell Breathing Lower
Threshold for Cell
67202920 VS.CellBreath.TCPOver.Ti Duration of TCP Greater

me Than Cell Breathing Upper
Threshold for Cell
Description
These counters provide the overloaded or underloaded duration of transmit carrier power (TCP)
specified by the TCP-based intra-frequency load balancing algorithm in a cell. When the cell

BSC6900 UMTS
TCP load is lower than a specified threshold, the cell is in the underloaded state. When the cell
TCP load is higher than a specified threshold, the cell is in overloaded state.
Measurement point
The CRNC measures the accumulated duration in which the TCP is higher than the overloaded
threshold or the accumulated duration in which the TCP is lower than the underloaded threshold
in the measurement period for a cell. Note: The values of these counters are not affected by
whether the TCP-based intra-frequency load balancing algorithm is enabled or not in the
measurement period.
Formula
None
Unit
s
Related Features
VS.CellBreath.TCPUnder.T WRFD-020104 Intra Frequency Load

ime Balance
VS.CellBreath.TCPOver.Ti WRFD-020104 Intra Frequency Load

me Balance
1.12.1.50 Average CPICH Power for Cell
Counters
67202921 VS.CPICH.MeanPwr Average CPICH Power for

Cell
Description
This counter provides the average P-CPICH power in a cell. Note: When the dynamic adjustment
of P-CPICH algorithm (including the RTWP/TCP-based intra-frequency load balancing
algorithm and load-based dynamic adjustment of P-CPICH algorithm) is enabled, the RNC
adjusts P-CPICH power based on cell load. This counter is measured based on the adjusted P-
CPICH power.

BSC6900 UMTS
Measurement point
The RNC takes samples P-CPICH power in a cell every 5s. At the end of the measurement
period, the average P-CPICH power is obtained by dividing the accumulated P-CPICH power
by the number of samples.
Formula
None
Unit
dBm
Related Features
VS.CPICH.MeanPwr WRFD-020101 Admission Control
1.12.1.51 Counters Related to the Number of Dynamic Channel Conversion

Attempts Between DCHs and FACHs
Counters
67190707 VS.DCCC.C2D.Att Number of Dynamic Channel

Conversion Attempts from
FACHs to DCHs for Cell
67190706 VS.DCCC.D2C.Att Number of Dynamic Channel

DCHs to FACHs for Cell
Description
These counters provide the number of conversion attempts from the DCH to the FACH or from
FACH to DCH. When a UE in the CELL_DCH state performs a soft handover or softer handover,
the number of successful conversions from the DCH to the FACH is measured in the best cell
where the UE camps on before state transition.
Measurement point
The measurement is triggered at point A as shown in the following figure. In the process of state
transition, when the RNC receives the RADIO BEARER RECONFIGURATION COMPLETE
message from the UE, the RNC measures the related counter in the best cell where the UE camps
on before the state transition if the DCH is converted to the FACH. If the FACH is converted to

BSC6900 UMTS
the DCH, the RNC measures the related counter in the cell where the UE in the CELL_FACH
state camps on after the state transition.
Formula
None
Unit
None
Related Features
VS.DCCC.C2D.Att WRFD-021101 Dynamic Channel

(DCCC)
VS.DCCC.D2C.Att WRFD-021101 Dynamic Channel

(DCCC)
1.12.1.52 Number of UL Rate Adjustments for AMR Services
Counters
67192003 VS.AMRWB.ULRateUp Number of Increases of UL

Service

BSC6900 UMTS
67190520 VS.AMR.UL.RateUp Number of UL Rate

Increases for AMR Services
for Cell
67180677 VS.AMR.UL.RateDown Number of UL Rate

Decreases for AMR Services
for Cell
67192004 VS.AMRWB.ULRateDown Number of Decreases of UL

Service
Description
These counters provide the number of times the UL rate of narrowband or wideband AMR
services is adjusted upward and downward. VS.AMRWB.ULRateUp and
VS.AMRWB.ULRateDown are used for wideband AMR services, VS.AMR.UL.RateUp and
VS.AMR.UL.RateDown are used for narrowband AMR services.
Measurement point
The measurement is triggered at point A as shown in the following figure. The RNC sends
TRANSPORT FORMAT COMBINATION CONTROL messages to UEs to request an increase
or decrease in the UL rate of narrowband or wideband AMR services. If the RNC does not
receive TRANSPORT FORMAT COMBINATION CONTROL FAILURE messages from
UEs, the UL rate of AMR services successfully increases or decreases. In this case, the RNC
measures the counters in the best cell where the UE camps on.
Figure 1-331 UL AMR rate adjustment procedure
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.AMRWB.ULRateUp WRFD-020701 AMR/WB-AMR Speech

Rates Control
VS.AMR.UL.RateUp WRFD-020701 AMR/WB-AMR Speech

Rates Control
VS.AMR.UL.RateDown WRFD-020701 AMR/WB-AMR Speech

Rates Control
VS.AMRWB.ULRateDown WRFD-020701 AMR/WB-AMR Speech

Rates Control
1.12.1.53 Counters Related to the Number of UL EDCH DCCC Attempts Based on

Throughput or RLC BO
Counters
67184359 VS.DCCC.AttUpsizing.E2E Number of UL EDCH-

.Thr EDCH DCCC Upsizing
Attempts Based on the
Throughput or RLC BO for
Cell
67196026 VS.DCCC.AttDownsizing.E Number of UL EDCH-

2E.Thr EDCH DCCC Downsizing
Attempts Based on the
Cell
Description
These counters provide the number of rate increase and decrease attempts for uplink E-DCH BE
services according to DCCC strategies, DCCC based on traffic volume and DCCC based on
throughput, in the HSUPA serving cell.
Measurement point
RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the counters

BSC6900 UMTS
based on decreases and increases in BE services due to different DCCC strategies in HSUPA
serving cell if uplink services are carried on the E-DCH before and after the reconfiguration.
Formula
None
Unit
None
Related Features
VS.DCCC.AttUpsizing.E2E WRFD-01061208 HSUPA DCCC

.Thr
VS.DCCC.AttDownsizing.E WRFD-01061208 HSUPA DCCC

2E.Thr
1.12.1.54 Counters Related to the Number of Successful UL EDCH DCCC

Operations Based on Throughput or RLC BO

BSC6900 UMTS
Counters
67196027 VS.DCCC.SuccUpsizing.E2 Number of Successful UL

E.Thr EDCH-EDCH DCCC
Upsizings Based on the
Cell
67196028 VS.DCCC.SuccDownsizing. Number of Successful UL

E2E.Thr EDCH-EDCH DCCC
Downsizings Based on the
Cell
Description
These counters provide the number of successful times the RNC increases and decreases uplink
E-DCH BE services according to DCCC strategies, DCCC based on traffic volume and DCCC
based on throughput, in the HSUPA serving cell.
Measurement point
The measurement is triggered at point B as shown in the following figure. When receiving the
RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the RNC
measures the counters based on decreases and increases in BE services due to different DCCC
strategies in HSUPA serving cell if uplink services are carried on the E-DCH before and after
the reconfiguration.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.SuccUpsizing.E2 WRFD-01061208 HSUPA DCCC

E.Thr
VS.DCCC.SuccDownsizing. WRFD-01061208 HSUPA DCCC

E2E.Thr
1.12.1.55 Number of UEs Performing Code Adjustment Based on HSDPA
Counters
67195992 VS.LCC.HSDPA.CodeAdj. Number of UEs Performing

Att Code Adjustment Based on
HSDPA for Cell
Description
In order to get more available HSDPA codes, the RNC shall select certain UEs to perform code
adjustments. This counter provides the number of UEs that perform code adjustment attempts
based on the HSDPA in a cell. For DC-HSDPA users, this counter is measured only in the cell
with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in the following figure. The RNC measures
the counter in the best cell where the UE camps on every time the RNC selects a UE to perform
code adjustment attempt and sends a PHYSICAL CHANNEL RECONFIGURATION message
to the UE.

BSC6900 UMTS
Figure 1-334 Physical channel reconfiguration
Formula
None
Unit
None
Related Features
VS.LCC.HSDPA.CodeAdj. WRFD-020108 Code Resource Management

Att
1.12.1.56 Number of DL DCH DCCC Upsizing Attempts Based on Throughput or

RLC BO
Counters
67192585 VS.DCCC.AttUpsizing.DL. Number of DL DCH DCCC

Thr Upsizing Attempts Based on
Cell

BSC6900 UMTS
Description
This counter provides the number of rate increase attempts for downlink DCH BE services on
the UE according to DCCC strategies, DCCC based on traffic volume and DCCC based on
throughput, in the best cell where the UE camps on.
Measurement point
RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the counter
based on different DCCC strategies in the best cell where the UE camps on if downlink services
are carried on the DCH before and after the reconfiguration.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.DCCC.AttUpsizing.DL. WRFD-021101 Dynamic Channel

Thr Configuration Control
(DCCC)
1.12.1.57 Number of Successful DL DCH DCCC Upsizings Based on Throughput

or RLC BO
Counters
67192586 VS.DCCC.SuccUpsizing.D Number of Successful DL

L.Thr DCH DCCC Upsizings
BO for Cell
Description
This counter provides the number of successful times the RNC increases downlink DCH BE
services on the UE according to DCCC strategies, DCCC based on traffic volume and DCCC
based on throughput, in the best cell where the UE camps on.
Measurement point
measures the counter based on different DCCC strategies in the best cell where the UE camps
on if downlink services are carried on the DCH before and after the reconfiguration.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.SuccUpsizing.D WRFD-021101 Dynamic Channel

L.Thr Configuration Control
(DCCC)
1.12.1.58 Number of UL DCH DCCC Upsizing Attempts Based on Throughput or

RLC BO

BSC6900 UMTS
Counters
67192593 VS.DCCC.AttUpsizing.UL. Number of UL DCH DCCC

Thr Upsizing Attempts Based on
Cell
Description
This counter provides the number of rate increase attempts for uplink DCH BE services on the
UE according to DCCC strategies, DCCC based on traffic volume and DCCC based on
throughput, in the best cell where the UE camps on.
Measurement point
based on different DCCC strategies in the best cell where the UE camps on if uplink services
are carried on the DCH before and after the reconfiguration.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.DCCC.AttUpsizing.UL. WRFD-021101 Dynamic Channel

Thr Configuration Control
(DCCC)
1.12.1.59 Number of Successful UL DCH DCCC Upsizings Based on Throughput

or RLC BO
Counters
67192594 VS.DCCC.SuccUpsizing.U Number of Successful UL

L.Thr DCH DCCC Upsizings
BO for Cell
Description
This counter provides the number of successful times the RNC increases uplink DCH BE
services on the UE according to DCCC strategies, DCCC based on traffic volume and DCCC
based on throughput, in the best cell where the UE camps on.
Measurement point
measures the counter based on different DCCC strategies in the best cell where the UE camps
on if uplink services are carried on the DCH before and after the reconfiguration.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.SuccUpsizing.U WRFD-021101 Dynamic Channel

L.Thr Configuration Control
(DCCC)
1.12.1.60 Counters Related to the Number of UL DCH DCCC Downsizing Attempts

Based on Different Strategies

BSC6900 UMTS
Counters
67192595 VS.DCCC.AttDownsizing. Number of UL DCH DCCC

UL.Thr Downsizing Attempts Based
on the Throughput or RLC
BO for Cell

UL.Cov Downsizing Attempts Based
on the Coverage (QoS) for
Cell

UL.Cong Downsizing Attempts Based
on the Resource Congestion
Algorithm for Cell
Description
These counters provide the number of rate decrease attempts for uplink DCH BE services on
the UE according to DCCC strategies in the best cell where the UE camps on.
Measurement point
counter based on different DCCC strategies in the best cell where the UE camps on if uplink

BSC6900 UMTS
Formula
None
Unit
None
Related Features

UL.Thr Configuration Control
(DCCC)

UL.Cov Configuration Control
(DCCC)

UL.Cong Configuration Control
(DCCC)
1.12.1.61 Counters Related to the Number of Successful UL DCH DCCC

Downsizings Based on Different Strategies
Counters

UL.Thr DCH DCCC Downsizings
BO for Cell

UL.Cov DCH DCCC Downsizings
Cell

UL.Cong DCH DCCC Downsizings
Based on Resource
Cell

BSC6900 UMTS
Description
These counters provide the number of successful times the RNC decreases uplink DCH BE
services on the UE based on different strategies in the best cell where the UE camps on.
Measurement point
counter based on different DCCC strategies in the best cell where the UE camps on if uplink
Formula
None
Unit
None

BSC6900 UMTS
Related Features

UL.Thr Configuration Control
(DCCC)

UL.Cov Configuration Control
(DCCC)

UL.Cong Configuration Control
(DCCC)
1.12.1.62 Number of UEs Performing Successful Code Adjustment in DL Basic

Congestion
Counters
67193409 VS.LCC.LDR.CodeAdj.Suc Number of UEs Performing

c Successful Code Adjustment
Cell
Description
When the cell is in basic congestion, the counter provides the number of UEs that has performed
code adjustment successfully in a cell. When a cell is in basic congestion of downlink code
resources, the RNC selects certain UEs in the cell to perform code adjustment so that some idle
codes are combined to meet the requirement of a higher rate.
Measurement point
When a cell is in basic congestion, the RNC selects certain UEs in the cell to perform code
adjustment. Upon receiving the PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message from the UEs, the RNC determines that code adjustment is successful. In this case, this
counter is measured in the cell where the selected UEs camp on.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.LCC.LDR.CodeAdj.Suc WRFD-020108 Code Resource Management

c
1.12.1.63 Number of UEs Performing Successful Code Adjustment Based on

HSDPA
Counters
67193410 VS.LCC.HSDPA.CodeAdj. Number of UEs Performing

Succ Successful Code Adjustment
Based on HSDPA for Cell
Description
In order to get more available HSDPA codes, the RNC shall select certain UEs to perform code
adjustments. This counter provides the number of UEs that perform successful code adjustments
based on the HSDPA in a cell. For DC-HSDPA users, this counter is measured only in the cell
with the primary carrier. This counter reflects the success rate of code adjustments.
Measurement point
The measurement is triggered at point B as shown in the following figure. The RNC measures
the counter in the best cell where the UE camps on every time the RNC selects a UE to perform
code adjustment attempt and receives a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from the UE.

BSC6900 UMTS
Figure 1-341 Physical channel reconfiguration
Formula
None
Unit
None
Related Features
VS.LCC.HSDPA.CodeAdj. WRFD-020108 Code Resource Management

Succ
1.12.1.64 Duration of Cell Unavailability Due to System Faults
Counters
67204837 VS.Cell.UnavailTime.Sys Duration of Cell

Unavailability Due to System
Faults for Cell

BSC6900 UMTS
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
VS.Cell.UnavailTime.Sys WRFD-031000 Intelligently Out of Service
1.12.1.65 Duration of HSDPA Service Unavailability Due to System Fault
Counters
67204838 VS.Cell.HSDPA.Unavail- Duration of HSDPA Service

Time Unavailability Due to System
Fault for Cell
Description
This counter provides the duration of HSDPA service unavailability due to system faults of the
RNC in a cell. The counter is not measured when the whole cell is unavailable. For DC-HSDPA
users, this counter is measured only in the primary cell. System faults are caused by various
reasons, such as the HSDPA channel fails to be set up or the state of the HSDPA channel changes
from available to unavailable.

BSC6900 UMTS
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
VS.Cell.HSDPA.Unavail- WRFD-031000 Intelligently Out of Service

Time
1.12.1.66 Duration of HSUPA Service Unavailability Due to System Fault
Counters
67204839 VS.Cell.HSUPA.Unavail- Duration of HSUPA Service

Time Unavailability Due to System
Fault for Cell
Description
This counter provides the duration of HSUPA service unavailability due to system faults of the
RNC in a cell. The counter is not measured when the whole cell is unavailable. For DC-HSUPA
users, this counter is measured only in the primary cell.
Measurement point
In a measurement period, after a cell is set up, the RNC measures the duration of HSUPA service
unavailability in a cell provided that the HSUPA service is not barred through the LMT.
Formula
None
Unit
s

BSC6900 UMTS
Related Features
VS.Cell.HSUPA.Unavail- WRFD-031000 Intelligently Out of Service

Time
1.12.1.67 Number of Attempts to transfer state from CELL_PCH to CELL_FACH for

cell
Counters
73403799 VS.DCCC.P2F.Att Number of Attempts to

transfer state from
CELL_PCH to
CELL_FACH for cell
Description
This counter provides the number of state transition attempts from CELL_PCH to CELL_FACH
in the cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends the UE a
CELL UPDATE CONFIRM message, the RNC measures the counter in the best cell that the
UE camps on if the UE tries to transit from CELL_PCH to CELL_FACH.
Figure 1-342 cell update

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.P2F.Att WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
Dynamic Channel
(DCCC)
1.12.1.68 Number of Successful state transfer from CELL_PCH to CELL_FACH for

cell
Counters
73403800 VS.DCCC.P2F.Succ Number of Successful state

transfer from CELL_PCH to
CELL_FACH for cell
Description
This counter provides the number of successful state transitions from CELL_PCH to
CELL_FACH in the best cell.
Measurement point
The measurement is triggered at point C as shown in the figure. When the RNC received from
the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message after sending
a CELL UPDATE CONFIRM message to the UE, the RNC measures the counter in the best
cell that the UE camps on, if the UE transits from CELL_PCH to CELL_FACH.

BSC6900 UMTS
Figure 1-343 CELL UPDATE
the UE a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message after
sending a CELL UPDATE CONFIRM message to the UE, the RNC measures the counter in the
best cell that the UE camps on, if the UE transits from CELL_PCH to CELL_FACH.
sending a CELL UPDATE CONFIRM message to the UE, the RNC measures the counter in the
best cell that the UE camps on, if the UE transits from CELL_PCH to CELL_FACH.

BSC6900 UMTS
the UE a RADIO BEARER RECONFIGURATION COMPLETE message after sending a
CELL UPDATE CONFIRM message to the UE, the RNC measures the counter in the best cell
that the UE camps on, if the UE transits from CELL_PCH to CELL_FACH.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.DCCC.P2F.Succ WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
Dynamic Channel
(DCCC)
1.12.1.69 Number of state transfer from CELL_PCH to URA_PCH for cell
Counters
73403801 VS.DCCC.P2URAP Number of state transfer from

CELL_PCH to URA_PCH
for cell
Description
This counter provides the number of state transition attempts from CELL_PCH to URA_PCH
in the cell.
Measurement point
CELL UPDATE CONFIRM message after receiving a CELL UPDATE message from the UE,
the RNC measures the counter in the best cell that the UE camps on, if the UE tries to transit
from CELL_PCH to URA_PCH.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.P2URAP WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
Dynamic Channel
(DCCC)
1.12.1.70 Number of Attempts to transfer state from URA_PCH to CELL_FACH for

cell

BSC6900 UMTS
Counters
73403802 VS.DCCC.URAP2F.Att Number of Attempts to

transfer state from
URA_PCH to CELL_FACH
for cell
Description
This counter provides the number of state transition attempts from URA_PCH to CELL_FACH
in the cell.
Measurement point
CELL UPDATE CONFIRM message after receiving a CELL UPDATE message from the UE,
the RNC measures the counter in the best cell that the UE camps on, if the UE tries to transit
from URA_PCH to CELL_FACH.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.DCCC.URAP2F.Att WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
Dynamic Channel
(DCCC)
1.12.1.71 Number of successful state transfer from URA_PCH to CELL_FACH in

the best cell
Counters
73403803 VS.DCCC.URAP2F.Succ Number of successful state

transfer from URA_PCH to
Description
This counter provides the number of successful state transitions from URA_PCH to
Measurement point
The measurement is triggered at point C as shown in the figure. When the RNC receives from
the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to a UE, the
RNC measures the counter in the best cell that the UE camps on, if the UE transits from
URA_PCH to CELL_FACH.

BSC6900 UMTS
sending a CELL UPDATE CONFIRM message to a UE, the RNC measures the counter in the
best cell that the UE camps on, if the UE transits from URA_PCH to CELL_FACH.
the UE a UTRAN MOBILITY INFORMATION CONFIRM message after sending a CELL
UPDATE CONFIRM message to a UE, the RNC measures the counter in the best cell that the
UE camps on, if the UE transits from URA_PCH to CELL_FACH.

BSC6900 UMTS
the UE a RADIO BEARER RECONFIGURATION COMPLETE message after sending a
CELL UPDATE CONFIRM message to a UE, the RNC measures the counter in the best cell
that the UE camps on, if the UE transits from URA_PCH to CELL_FACH.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.DCCC.URAP2F.Succ WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
Dynamic Channel
(DCCC)
1.12.1.72 Number of Cell Deletions or Establishments Due to Dynamic Cell

Shutdown
Counters
73393802 VS.DynClose.CellDel Number of Cell Deletions

Due to Dynamic Cell
Shutdown
73393803 VS.DynOpen.CellSetup Number of Cell Setup Due to

Dynamic Cell Shutdown
Description
These counters provide the number of cell deletions or establishments due to dynamic cell
shutdown in a cell.
Measurement point
After dynamic cell shutdown takes effect, if the conditions of dynamic cell shutdown are met
and the action of shutdown or power-on is triggered, this counter is increased by one when the
cell is deleted or set up. The accumulated number of cell deletions or establishments is the value
of this counter.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.DynClose.CellDel WRFD-020117 Multi-Carrier Switch off

WRFD-020122 Based on Traffic Load
Based on QoS
VS.DynOpen.CellSetup WRFD-020117 Multi-Carrier Switch off

WRFD-020122 Based on Traffic Load
Based on QoS
1.12.1.73 Number of State Transfer Attempts from CELL_DCH to CELL_PCH for

Cell
Counters
73421765 VS.DCCC.D2P.Att Number of State Transfer

Attempts from CELL_DCH
to CELL_PCH for Cell
Description
This counter provides the number of state transition attempts from CELL_DCH to CELL_FACH
or URA_PCH in the cell. When a UE in the CELL_DCH state performs a soft handover or softer
handover, the counter is measured in the best cell in the active set for soft handovers. The best
cell is obtained before the state transition.
Measurement point
in the best cell where the UE camps on if the state is transited from CELL_DCH to CELL_PCH
or URA_PCH.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.D2P.Att WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.1.74 Number of Successful State Transfers from CELL_DCH to CELL_PCH for

Cell

BSC6900 UMTS
Counters
73421766 VS.DCCC.D2P.Succ Number of Successful State

Transfers from CELL_DCH
to CELL_PCH for Cell
Description
This counter provides the number of successful state transitions from CELL_DCH to
CELL_FACH or URA_PCH in the cell. When a UE in the CELL_DCH state performs a soft
handover or softer handover, the counter is measured in the best cell in the active set for soft
handovers. The best cell is obtained before the state transition.
Measurement point
measures the counter in the best cell where the UE camps on if the state is transferred from
CELL_DCH to CELL_PCH.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.DCCC.D2P.Succ WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.1.75 Number of State Transfer Attempts from CELL_DCH or CELL_FACH to

CELL_PCH for FAST DORMANCY user for Cell
Counters
73421767 VS.DCCC.FastDormUe.DF Number of State Transfer

2P.Att Attempts from CELL_DCH
or CELL_FACH to
CELL_PCH for FAST
DORMANCY user for Cell
Description
This counter provides the number of state transition attempts from CELL_DCH or CELL_FACH
to CELL_PCH or URA_PCH for Fast Dormancy user in a cell. When a UE in the CELL_DCH
state performs a soft handover or softer handover, the counter is measured in the best cell in the
active set for soft handovers. The best cell is obtained before the state transition. In case of the
state transition from CELL_FACH to CELL_PCH or UAR_PCH, the counter is measured in
the cell where the UE in the CELL_FACH state camps on.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC sends
a PHYSICAL CHANNEL RECONFIGURATION message to a UE supporting the fast
dormancy function, instructing the UE to transit from the CELL_FACH or CELL_DCH state
to the CELL_PCH or URA_PCH state, this counter is incremented by one in the cell where the
UE is camping. When a UE in the CELL_DCH state performs a soft handover or softer handover,
the counter is measured in the best cell in the active set for soft handovers. The best cell is
obtained before the state transition.

BSC6900 UMTS
Figure 1-355 physical channel reconfiguration procedure
a RADIO BEARER RECONFIGURATION message to a UE supporting the fast dormancy
function, instructing the UE to transit from the CELL_FACH or CELL_DCH state to the
CELL_PCH or URA_PCH state, this counter is incremented by one in the cell where the UE is
camping. When a UE in the CELL_DCH state performs a soft handover or softer handover, the
counter is measured in the best cell in the active set for soft handovers. The best cell is obtained
before the state transition.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.DCCC.FastDormUe.DF WRFD-020500 Enhanced Fast Dormancy

2P.Att
1.12.1.76 Number of Successful State Transfers from CELL_DCH or CELL_FACH

to CELL_PCH for FAST DORMANCY user
Counters
73421768 VS.DCCC.FastDormUe.DF Number of Successful State

2P.Succ Transfers from CELL_DCH
or CELL_FACH to
CELL_PCH for FAST
DORMANCY user for Cell
Description
This counter provides the number of successful state transitions from CELL_DCH or
CELL_FACH to CELL_PCH or URA_PCH for Fast Dormancy user in a cell. When a UE in
the CELL_DCH state performs a soft handover or softer handover, the counter is measured in
the best cell in the active set for soft handovers. The best cell is obtained before the state
transition. In case of the state transition from CELL_FACH to CELL_PCH or UAR_PCH, the
counter is measured in the cell where the UE in the CELL_FACH state camps on.
Measurement point
The measurement is triggered at point B as shown in the following figure. When the RNC
receives a message from a UE supporting the fast dormancy feature, indicating that the UE has
transited from the CELL_FACH or CELL_DCH state to the CELL_PCH state, this counter is
incremented by one in the cell where the UE is camping. When a UE in the CELL_DCH state
performs a soft handover or softer handover, the counter is measured in the best cell in the active
set for soft handovers. The best cell is obtained before the state transition.

BSC6900 UMTS
receives a RADIO BEARER RECONFIGURATION COMPLETE message from a UE
supporting the fast dormancy feature, indicating that the UE has transited from the CELL_FACH
or CELL_DCH state to the CELL_PCH state, this counter is incremented by one in the cell
where the UE is camping. When a UE in the CELL_DCH state performs a soft handover or
softer handover, the counter is measured in the best cell in the active set for soft handovers. The
best cell is obtained before the state transition.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.DCCC.FastDormUe.DF WRFD-020500 Enhanced Fast Dormancy

2P.Succ
1.12.1.77 Number of Attempts to transfer state from CELL_PCH to CELL_DCH for

cell
Counters
73421933 VS.DCCC.P2D.Att Number of Attempts to

transfer state from
CELL_PCH to CELL_DCH
for cell
Description
This counter provides the number of state transition attempts from CELL_PCH to CELL_DCH
in the cell.
Measurement point
CELL UPDATE CONFIRM message, the RNC measures the counter in the cell where the UE
camps on before the state transition, if the UE tries to transit from CELL_PCH to CELL_DCH.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.P2D.Att WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.1.78 Number of Successful state transfer from CELL_PCH to CELL_DCH for

cell

BSC6900 UMTS
Counters
73421934 VS.DCCC.P2D.Succ Number of Successful state

transfer from CELL_PCH to
CELL_DCH for cell
Description
This counter provides the number of successful state transitions from CELL_PCH to
CELL_DCH in the cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives the UE
a RADIO BEARER RECONFIGURATION COMPLETE message, the RNC measures the
counter in the cell where the UE camps on before the state transition, if the UE transits from
CELL_PCH to CELL_DCH.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.DCCC.P2D.Succ WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.1.79 Number of Attempts to transfer state from URA_PCH to CELL_DCH for

cell
Counters
73421935 VS.DCCC.URAP2D.Att Number of Attempts to

transfer state from
URA_PCH to CELL_DCH
for cell
Description
This counter provides the number of state transition attempts from URA_PCH to CELL_DCH
in the cell.
Measurement point
CELL UPDATE CONFIRM message, the RNC measures the counter in the cell where the UE
camps on before the state transition, if the UE tries to transit from URA_PCH to CELL_DCH.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.URAP2D.Att WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.1.80 Number of successful state transfer from URA_PCH to CELL_DCH in the

best cell

BSC6900 UMTS
Counters
73421936 VS.DCCC.URAP2D.Succ Number of successful state

transfer from URA_PCH to
CELL_DCH in the best cell.
Description
This counter provides the number of successful state transitions from URA_PCH to CELL_DCH
in the cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives the UE
a RADIO BEARER RECONFIGURATION COMPLETE message, the RNC measures the
counter in the cell where the UE camps on before the state transition, if the UE transits from
URA_PCH to CELL_DCH.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.DCCC.URAP2D.Succ WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.1.81 Number of Attempts of CELL_PCH/URA_PCH-to-CELL_DCH State

Transition Together with DRD for Cell
Counters
73422068 VS.DCCC.P2D.DRD.Att Number of Attempts of

CELL_PCH/URA_PCH-to-
CELL_DCH State Transition
Together with DRD for Cell
Description
This counter provides the number of times the RNC attempts to trigger the state transition from
CELL_PCH or URA_PCH to CELL_DCH together with DRD in a cell.
Measurement point
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.P2D.DRD.Att WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.1.82 Number of Successful CELL_PCH/URA_PCH-to-CELL_DCH State

Transitions Together with DRDs for Cell

BSC6900 UMTS
Counters
73422069 VS.DCCC.P2D.DRD.Succ Number of Successful

CELL_PCH/URA_PCH-to-
CELL_DCH State
Transitions Together with
DRDs for Cell
Description
This counter provides the number of times a UE successfully transit its state from CELL_PCH
or URA_PCH to CELL_DCH together with DRDs in a cell.
Measurement point
The measurement is triggered at point C as shown in the figure. When the RNC received RADIO
BEARER RECONFIGURATION COMPLETE message from the UE after the UE transfers its
state from CELL_PCH or URA_PCH to CELL_DCH and the DRD is performed, this counter
is measured in the cell that the UE camps on when sending the CELL UPDATE message.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.DCCC.P2D.DRD.Succ WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.1.83 Number of CPICH Power Adjustments Based on RTWP for Cell
Counters
73423313 VS.ULB.CPICH.Adjust- Number of CPICH Power

Num Adjustments Based on
RTWP for Cell
Description
This counter provides the number of power adjustments of the Common Pilot Channel (CPICH)
triggered by the RTWP-based uplink intra-frequency load balancing algorithm. RTWP is short
for Received Total Wideband Power (RTWP).
Measurement point
At point A as shown in the figure, When RTWP is higher than a certain threshold, the RNC
needs to decrease CPICH power. When RTWP is lower than a certain threshold, the RNC needs
to increase CPICH power. This counter provides the accumulated number of CPICH power
adjustments in a measurement period in a cell.

BSC6900 UMTS
Figure 1-365 Cell reconfiguration procedure
Formula
None
Unit
None
Related Features
VS.ULB.CPICH.Adjust- WRFD-020104 Intra Frequency Load

Num Balance
1.12.1.84 Duration of PCPICH Power Under Minimum RTWP Threshold
Counters
73441123 VS.ULB.CPICHMin.Time Duration of PCPICH Power

Under Minimum RTWP
Threshold

BSC6900 UMTS
Description
This counter provides the duration of CPICH power being lower than Min Transmit Power of
P-CPICH when the CPICH power is adjusted by the RTWP-based uplink intra-frequency load
balancing algorithm.
Measurement point
The measurement starts when CPICH power is adjusted to be lower than Min Transmit Power
of P-CPICH and stops when CPICH power is adjusted to be higher than Min Transmit Power
of PCPICH. This counter is the accumulated value of such durations in the measurement period.
Formula
None
Unit
s
Related Features
VS.ULB.CPICHMin.Time WRFD-020104 Intra Frequency Load

Balance
1.12.1.85 Number of State Transfer Attempts from CELL_DCH to CELL_PCH or

URA_PCH for Cell for HSDPA service
Counters
73422160 VS.HSDPA.H2P.Att Number of State Transfer

Attempts from CELL_DCH
to CELL_PCH or URA_PCH
for Cell for HSDPA service
Description
This counter provides the number of times a UE performing HSDPA services attempts to transit
from the CELL_DCH state to the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the UE a
RADIO BEARER RECONFIGURATION message, instructing the UE performing HSDPA

BSC6900 UMTS
services to transit from the CELL_DCH state to the CELL_PCH or URA_PCH state, this counter
is measured at the serving cell where the UE camps on. For DC-HSDPA users, this counter is
measured only in the cell with the primary carrier.
Formula
None
Unit
None
Related Features
VS.HSDPA.H2P.Att WRFD-01061111 HSDPA State Transition
1.12.1.86 Number of Successful Times That a UE Performing HSDPA Services

Transits to CELL_PCH or URA_PCH State for cell

BSC6900 UMTS
Counters
73422161 VS.HSDPA.H2P.Succ Number of Successful Times

That a UE Performing
HSDPA Services Transits to
CELL_PCH or URA_PCH
State for cell
Description
This counter provides the number of times a UE performing HSDPA services successfully
transits from the CELL_DCH state to the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives a RADIO
BEARER RECONFIGURATION COMPLETE message from the UE, indicating that the UE
performing HSDPA services successfully transits from the CELL_DCH state to the CELL_PCH
or URA_PCH state, this counter is measured at the serving cell where the UE camps on. For
DC-HSDPA users, this counter is measured only in the cell with the primary carrier.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.HSDPA.H2P.Succ WRFD-01061111 HSDPA State Transition
1.12.1.87 Number of Attempts for a UE Performing HSUPA Services to Transit to

CELL_PCH or URA_PCH State for Cell
Counters
73422162 VS.HSUPA.E2P.Att Number of Attempts for a UE

Performing HSUPA Services
to Transit to CELL_PCH or
URA_PCH State for Cell
Description
This counter provides the number of times a UE performing HSUPA services attempts to transit
Measurement point
RADIO BEARER RECONFIGURATION message, instructing the UE performing HSUPA
services to transit from the CELL_DCH state to the CELL_PCH or URA_PCH state, this counter
is measured at the serving cell where the UE camps on. For DC-HSUPA users, this counter is

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.E2P.Att WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.1.88 Number of Successful Times That a UE Performing HSUPA Services


BSC6900 UMTS
Counters
73422163 VS.HSUPA.E2P.Succ Number of Successful Times

That a UE Performing
HSUPA Services Transits to
CELL_PCH or URA_PCH
State for cell
Description
This counter provides the number of times a UE performing HSUPA services successfully
transits from the CELL_DCH state to the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives a RADIO
performing HSUPA services successfully transits from the CELL_DCH state to the CELL_PCH
or URA_PCH state, this counter is measured at the serving cell where the UE camps on. For
DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.HSUPA.E2P.Succ WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.1.89 Number of Attempts for a UE Performing PS R99 Services to Transit to

CELL_PCH or URA_PCH State for Cell
Counters
73422164 VS.PSR99.D2P.Att Number of Attempts for a UE

Performing PS R99 Services
to Transit to CELL_PCH or
Description
This counter provides the number of times a UE performing PS R99 services attempts to transit
Measurement point
RADIO BEARER RECONFIGURATION message to the UE, instructing the UE performing
PS R99 services to transit from the CELL_DCH state to the CELL_PCH or URA_PCH state,
this counter is measured at the serving cell that the UE camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.PSR99.D2P.Att WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.1.90 Number of Successful Times That a UE Performing PS R99 Services


BSC6900 UMTS
Counters
73422165 VS.PSR99.D2P.Succ Number of Successful Times

That a UE Performing PS
R99 Services Transits to
CELL_PCH or URA_PCH
State for cell
Description
This counter provides the number of times a UE performing PS R99 services successfully transits
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives RADIO
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

BSC6900 UMTS
Unit
None
Related Features
VS.PSR99.D2P.Succ WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.1.91 Number of Times That PS R99 Service Rate Is Found to Be Higher than
HSUPA Service Rate
Counters
73423357 VS.HSUPAR99.Unfairness Number of Times That PS

R99 Service Rate Is Found to
Be Higher than HSUPA
Service Rate
Description
This counter provides the number of times that the PS R99 service rate is found to be higher
than the HSUPA service rate in an HSUPA cell in the case that the cell fairness switch is set to
ON.
Measurement point
This counter is increased by one each time the PS R99 service rate is found to be higher than
the HSUPA service rate in the period of time specified by the fairness period timer length
parameter.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.HSUPAR99.Unfairness WRFD-020131 Optimization of R99 and

HSUPA Users Fairness
1.12.1.92 Number of PS R99 BE Rate Reduction Requests Triggered by Unfairness

Between PS R99 Service Rate and HSUPA Service Rate
Counters
73423358 VS.HSUPAR99.Unfairness. Number of PS R99 BE Rate

R99BERateDown Reduction Requests
Triggered by Unfairness
Between PS R99 Service
Rate and HSUPA Service
Rate
Description
This counter provides the number of times that PS R99 BE users are selected for rate reduction
in the cell in the case that the PS R99 BE service rate is found to be higher than the HSUPA
service rate.
Measurement point
The measurement is triggered at point A shown in figure 1. When the RNC determines that the
PS R99 service rate is higher than the HSUPA service rate in an HSUPA cell, the RNC reduces
the rate of certain R99 BE users. The measurement is triggered in the best HSUPA cell when
the RNC sends a RADIO BERER RECONFIGURATION message to the UE.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPAR99.Unfairness. WRFD-020131 Optimization of R99 and

R99BERateDown HSUPA Users Fairness
1.12.1.93 Duration of CPU Resource Insufficiency Reported by NodeB
Counters
73411191 VS.NodeB.CPU.Cong.Dur Duration of CPU Resource

Insufficiency Reported by
NodeB for Cell

BSC6900 UMTS
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
VS.NodeB.CPU.Cong.Dur WRFD-040100 Flow Control
1.12.1.94 Congestion Duration of DCCHs, DTCHs and CCCHs Carried over FACHs
for Cell
Counters
73439970 VS.FACH.DCCH.CONG.TI Congestion Duration of

ME DCCHs Carried over FACHs
for Cell
73439971 VS.FACH.DTCH.CONG.TI Congestion Duration of

ME DTCHs Carried over FACHs
for Cell
73424009 VS.FACH.CCCH.CONG.TI Congestion Duration of

ME CCCHs Carried over FACHs
for Cell
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

BSC6900 UMTS
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
VS.FACH.DCCH.CONG.TI WRFD-010202 UE State in Connected Mode

ME (CELL-DCH, CELL-PCH,
URA-PCH, CELL-FACH)
VS.FACH.DTCH.CONG.TI WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
VS.FACH.CCCH.CONG.TI WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
1.12.2 Algorithm Measurement2 for Cell(ALGO2.Cell)
Overview
Radio Resource Management (RRC) algorithm is an important function of the WCDMA system.
It is used to manage cell resources effectively and to increase resource utilization. This function
subset(ALGO2.Cell) provides measurements related to the radio resource management
algorithm.

BSC6900 UMTS
Counters
Description
73441210 VS.SirDist.OLPC. Number of UEs V900R013

User Using OLPC
Enhancement Based
on SIRerror
Distribution for Cell
73441212 VS.BackGroundNo Average Uplink V900R014

ise.Mean Background Noise in
a Cell
73423948 VS.BackGroundNo Number of V900R014

ise.Update Automatic Uplink
Background Noise
Updates in a Cell
73441215 VS.BackGroundNo Maximum Uplink V900R014

ise.Max Background Noise in
a Cell
73423955 VS.RAC.TrChSwit Counters Related to V900R014

ch.Fail.DCCH.Con the Failed Number of
g.F2D F2D Process
Triggered by DCCH
Congestion

ch.Fail.DCCH.Con the Failed Number of
g.D2F D2F Process
Triggered by DCCH
Congestion

ch.Fail.DSP.Overlo the Failed Number of
ad.D2F D2F Process
Triggered by DSP
Overload
73423994 VS.HSUPA.TgtRo- Number of times the V900R014

TInc RoT value is
increased
73423995 VS.HSUPA.TgtRo Number of times the V900R014

TDec RoT value is
decreased

BSC6900 UMTS

Description
73424209 VS.HSUPA.TTI2to Number of V900R014

10.ADMCE.Succ Successful TTI
Switchovers Based
on Admitted CEs
During RB
Reconfiguration in a
Cell(2ms to 10ms)

10.COVER.Succ Successful TTI
Switchovers Based
on Coverage During
RB Reconfiguration
in a Cell(2ms to
10ms)

10.ResRTWP.Succ Successful TTI
Switchovers Based
on RTWP During RB
Cell(2ms to 10ms)

10.ResUsedCE.Suc Successful TTI
c Switchovers Based
on Number of
Occupied CEs
During RB
Cell(2ms to 10ms)
73424214 VS.RABEstabE2D. Number of Times V900R014

COVER.Succ HSUPA UEs
Processing BE
Services Succeed in
Setting Up RABs
over the DCH in
Case of Weak
Coverage
73441241 VS.AC.CongCtl.M Mean Number of PS V900R014

eanAcBarNum.Abo Access Classes
veR6.PS Restricted Due to
Cell Resource
Congestion (R6 or
Later)

BSC6900 UMTS

Description
73441243 VS.AC.CongCtl.M Mean Number of V900R014

eanAcBarNum.Un- Access Classes
derR5 Restricted Due to
Cell Resource
Congestion (R5 or
Earlier)
73441244 VS.AC.CongCtl.M Mean Number of CS V900R014

eanAcBarNum.Abo Access Classes
veR6.CS Restricted Due to
Cell Resource
Congestion (R6 or
Later)
73441245 VS.AC.CongCtl.Ti Duration of Access V900R014

me Class Restriction
Triggered by Cell
Resource
Congestion
73441246 VS.LCC.CLB.CS.I Number of CS UEs V900R014

nterFreq Involved in Inter-
Frequency Load-
based Handovers in a
CS CLB Cell
73441247 VS.LCC.CLB.PS.I Number of PS UEs V900R014

nterFreq Involved in Inter-
Frequency Load-
based Handovers in a
PS CLB Cell

10.ResIUB.Succ Successful TTI
Switchovers Based
on Iub Resources
During RB
Cell(2ms to 10ms)
73424472 VS.HSDPA.DynCf Number of Attempts V900R014

gAtt.LongCQI to Configure a Long
CQI Feedback
Period for a Cell
73424473 VS.HSDPA.DynCf Number of Attempts V900R014

gAtt.ShortCQI to Configure a Short
CQI Feedback
Period for a Cell

BSC6900 UMTS

Description
73424474 VS.ULBler.BE.Lar Number of Attempts V900R014

ge to Configure BLER
in a Congested Cell
73424475 VS.ULBler.BE.Sm Number of Attempts V900R014

all to Configure BLER
in a Normal Cell
73424760 VS.RAB.SpecialUs Number of CS RABs V900R014

er.AbnormRel.CS Abnormally
Released for Special
UEs for Cell
73424761 VS.RAB.SpecialUs Number of CS RABs V900R014

er.NormRel.CS Normally Released
for Special UEs for
Cell
73441505 VS.MeanULActual Mean Uplink Actual V900R014

PowerLoad Cell Load
73424787 VS.MaxULActual- Max Uplink Actual V900R014

PowerLoad Cell Load
73424788 VS.MinULActual- Min Uplink Actual V900R014

PowerLoad Cell Load
73424896 VS.DCCC.Att.F2U Number of V900R014

CELL_FACH to
URA_PCH State
Transition Attempts
for Cell
73424897 VS.DCCC.Succ.F2 Number of V900R014

U Successful
CELL_FACH to
URA_PCH State
Transitions for Cell
73424898 VS.DCCC.Att.D2U Number of V900R014

CELL_DCH to
URA_PCH State
Transition Attempts
for Cell
73424899 VS.DCCC.Succ.D2 Number of V900R014

U Successful
CELL_DCH to
URA_PCH State

BSC6900 UMTS

Description
73425824 VS.DL.DPCH.Opti Number of Pilot PO V900R015

PilotPOAttNum Optimization
Attempts in the DL
DPCH for Cell
73425825 VS.DL.DPCH.Nor- Number of Normal V900R015

malPilotPOAttNu Pilot PO Attempts in
m the DL DPCH for
Cell
73426173 VS.TotalDesense.N Total number of V900R015

um times a micro cell
transits to the total
desensitization state
73426176 VS.TotalDesense.Ti Total time periods of V900R015

me the total
for a micro cell
73426179 VS.MeanDesen- Average V900R015

sePwr desensitization
intensity for a micro
cell
73426283 VS.LCG.ULCredit Average Uplink V900R015

Usage.Mean Credit Usage of LCG
for Cell
73426284 VS.LCG.ULCredit Maximum Uplink V900R015

Usage.Max Credit Usage of LCG
for Cell
73426333 VS.DCCC.Att.F2D. Number of State V900R015

AfterP2F Transition Attempts
from CELL_PCH or
URA_PCH to
CELL_FACH and
then to CELL_DCH
Due to Data
Transmission
Requirements for
Cell

BSC6900 UMTS

Description
73426334 VS.DCCC.Succ.F2 Number of V900R015

D.AfterP2F Successful State
Transitions from
CELL_PCH or
URA_PCH to
CELL_FACH and
then to CELL_DCH
Due to Data
Transmission
Requirements for
Cell
None
1.12.2.1 Average Number of UEs Using OLPC Enhancement Based on SIRerror

Distribution
Counters
73441210 VS.SirDist.OLPC.User Number of UEs Using OLPC

Enhancement Based on
SIRerror Distribution for
Cell
Description
This counter provides the average number of UEs using the algorithm OLPC Enhancement
Based on SIRerror Distribution in a cell that is their best cell.
Measurement point
The RNC takes samples of UEs using the algorithm OLPC Enhancement Based on SIRerror
Distribution in a cell that is their best cell. The samples are taken every five seconds. At the end
of a measurement period, the RNC accumulates the values obtained at each sampling point and
divides the accumulated value by the number of samples for the average value. A UE is
considered to be using this algorithm if the DEDICATED MEASUREMENT INITIATION
procedure related to this algorithm is successfully started in all cells in the active set for the UE.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SirDist.OLPC.User WRFD-020503 Outer Loop Power Control
1.12.2.2 Average and Maximum Uplink Background Noise
Counters
73441212 VS.BackGroundNoise.Mean Average Uplink Background

Noise in a Cell
73441215 VS.BackGroundNoise.Max Maximum Uplink

Background Noise in a Cell
specific formulas.
73423946 VS.BackGroundNoise.CUM Accumulated Totally

Background Noise for Cell
73423947 VS.BackGroundNoise.SAM Number of the Background

PLE Noise for Cell
Description
These counters provide the average and maximum uplink background noise, respectively, in a
cell.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of the cell background
noise after the RNC updates. At the end of a measurement period, the average uplink background

BSC6900 UMTS
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
VS.BackGroundNoise.Mean = ([VS.BackGroundNoise.CUM]/
[VS.BackGroundNoise.SAMPLE]-{1121})/{10}
Unit
dBm
Related Features
VS.BackGroundNoise.Mean WRFD-020102 Load Measurement
VS.BackGroundNoise.Max WRFD-020102 Load Measurement
1.12.2.3 Number of Automatic Uplink Background Noise Updates
Counters
73423948 VS.BackGroundNoise.Up- Number of Automatic Uplink

date Background Noise Updates
in a Cell
Description
This counter provides the number of automatic uplink background noise updates in a cell.
Measurement point
The measurement is triggered when the RNC makes a decision on a cell background noise update
during the period when the algorithm for automatic uplink background noise updates takes effect.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.BackGroundNoise.Up- WRFD-020102 Load Measurement

date
1.12.2.4 Counters Related to the Number of Failed in Channal Transfering Process
Counters
73423955 VS.RAC.TrChSwitch.Fail.D Counters Related to the

CCH.Cong.F2D Failed Number of F2D
Process Triggered by DCCH
Congestion

CCH.Cong.D2F Failed Number of D2F
Process Triggered by DCCH
Congestion

SP.Overload.D2F Failed Number of D2F
Process Triggered by DSP
Overload
Description
These counters measure the number of failed resource applications during a channel conversion.
Measurement point
UEs must apply for resources before state transitions. When a UE fails to apply for resources
due to resource congestion, these counters are measured in the cell that the UE fails to access
based on the causes of resource congestion.
Formula
None
Unit
None

BSC6900 UMTS
Related Features

CCH.Cong.F2D

CCH.Cong.D2F

SP.Overload.D2F
1.12.2.5 Number of RoT adjustments in an HSUPA cell
Counters
73423994 VS.HSUPA.TgtRoTInc Number of times the RoT

value is increased
73423995 VS.HSUPA.TgtRoTDec Number of times the RoT

value is decreased
Description
This counter provides the number of Rise over Thermal (RoT) adjustments in an HSUPA cell.
Measurement point
The RNC decides whether to adjust the RoT value based on the UL Timeslot ISCP value reported
by the NodeB and transmit power of R99 users in an HSUPA cell. Once the RNC decides to
adjust the RoT value, this counter is increased by one.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.HSUPA.TgtRoTInc WRFD-140211 Dynamic Target ROT

Adjustment
VS.HSUPA.TgtRoTDec WRFD-140211 Dynamic Target ROT

Adjustment
1.12.2.6 Number of Successful TTI Switchovers with Various Causes During RB

Reconfiguration in a Cell(2ms to 10ms)
Counters
73424209 VS.HSUPA.TTI2to10.ADM Number of Successful TTI

CE.Succ Switchovers Based on
Admitted CEs During RB
Reconfiguration in a Cell
(2ms to 10ms)
73424210 VS.HSUPA.TTI2to10.COV Number of Successful TTI

ER.Succ Switchovers Based on
Coverage During RB
(2ms to 10ms)
73424211 VS.HSUPA.TTI2to10.ResR Number of Successful TTI

TWP.Succ Switchovers Based on
RTWP During RB
(2ms to 10ms)
73424212 VS.HSUPA.TTI2to10.ResU Number of Successful TTI

sedCE.Succ Switchovers Based on
Number of Occupied CEs
During RB Reconfiguration
in a Cell(2ms to 10ms)
73424471 VS.HSUPA.TTI2to10.ResI Number of Successful TTI

UB.Succ Switchovers Based on Iub
Resources During RB
(2ms to 10ms)

BSC6900 UMTS
Description
These counters provide the number of successful TTI switchovers from 2 ms to 10 ms during
RB reconfiguration in a cell. For DC-HSUPA UEs, these counters are measured only in the
primary cell. TTI is short for transmission time interval.
Measurement point
The measurement is triggered at point B shown in the following figure. When the UE sends the
RNC a RADIO BEARER RECONFIGURATION COMPLETE message, a specific counter is
increased by one if the UE performs a successful TTI switchover from 2 ms to 10 ms in its
HSUPA serving cell. This counter is determined based on the specific TTI switchover cause. At
the end of the measurement period, the RNC calculates the accumulated times of successful TTI
handovers caused by different reasons.
Figure 1-373 RB reconfig procedure
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.HSUPA.TTI2to10.ADM WRFD-01061404 HSUPA 2ms/10ms TTI

CE.Succ Handover
VS.HSUPA.TTI2to10.COV WRFD-010690 TTI Switch for BE Services

ER.Succ WRFD-01061404 Based on Coverage
HSUPA 2ms/10ms TTI
Handover
VS.HSUPA.TTI2to10.ResR WRFD-01061404 HSUPA 2ms/10ms TTI

TWP.Succ Handover
VS.HSUPA.TTI2to10.ResU WRFD-01061404 HSUPA 2ms/10ms TTI

sedCE.Succ Handover
VS.HSUPA.TTI2to10.ResI WRFD-01061404 HSUPA 2ms/10ms TTI

UB.Succ Handover
1.12.2.7 Number of Times HSUPA UEs Processing BE Services Succeed in Setting

Up RABs over the DCH in Case of Weak Coverage
Counters
73424214 VS.RABEstabE2D.COVER. Number of Times HSUPA

Succ UEs Processing BE Services
Succeed in Setting Up RABs
over the DCH in Case of
Weak Coverage
Description
This counter provides the number of times HSUPA UEs processing BE services succeed in
setting up RABs over the DCH in case of weak coverage.
Measurement point
At measure point B shown in the following figure, the RNC receives a RADIO BEARER SETUP
COMPLETE message from the UE and sends an RAB ASSIGNMENT RESPONSE message
to the CN. The UEs eventually succeed in setting up the RABs over the DCH due to a small Ec/
N0 even through conditions for setting up the RABs over the E-DCH has been met. In such a
case, this counter in the serving cell is increased by one.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RABEstabE2D.COVER. WRFD-01061208 HSUPA DCCC

Succ
1.12.2.8 Mean Number of Access Classes Restricted Due to Cell Resource

Congestion

BSC6900 UMTS
Counters
73441241 VS.AC.CongCtl.MeanAcBa Mean Number of PS Access

rNum.AboveR6.PS Classes Restricted Due to
Cell Resource Congestion
(R6 or Later)
73441243 VS.AC.CongCtl.MeanAcBa Mean Number of Access

rNum.UnderR5 Classes Restricted Due to
(R5 or Earlier)
73441244 VS.AC.CongCtl.MeanAcBa Mean Number of CS Access

rNum.AboveR6.CS Classes Restricted Due to
(R6 or Later)
Description
These counters provide the mean number of PS access classes restricted due to cell resource
congestion for UEs of Release 6 or later, mean number of access classes restricted due to cell
resource congestion for UEs of Release 5 or earlier, and mean number of CS access classes
restricted due to cell resource congestion for UEs of Release 6 or later, respectively. Note: AC
restrictions for UEs of Release 6 or later can be performed for the PS or CS domain, respectively.
AC restrictions for UEs of Release 5 or earlier cannot be performed for the PS or CS domain,
respectively.
Measurement point
The RNC takes samples every time it attempts to restrict access classes due to congested cell
resources. At the end of each measurement period, the RNC sums sample results and divides
the sum by the number of samples. The division result is the mean number of restricted access
classes within a specific measurement period.
Formula
None
Unit
None
Related Features
VS.AC.CongCtl.MeanAcBa WRFD-140213 Intelligent Access Class

rNum.AboveR6.PS Control

BSC6900 UMTS

rNum.UnderR5 Control

rNum.AboveR6.CS Control
1.12.2.9 Duration of Access Class Restriction Triggered by Cell Resource

Congestion
Counters
73441245 VS.AC.CongCtl.Time Duration of Access Class

Restriction Triggered by Cell
Resource Congestion
Description
This counter provides the duration of access class restriction triggered by cell resource
congestion.
Measurement point
When cell resources become congested, the RNC calculates the duration of access class
restriction for the cell. Access class restriction: At least one of the AC number restricted for PS
UEs of Release 6 or later, CS UEs of Release 5 or earlier and Release 6 or later is not zero. This
counter is calculated by the accumulated duration of access class restriction in the measurement
period.
Formula
None
Unit
s
Related Features
VS.AC.CongCtl.Time WRFD-140213 Intelligent Access Class

Control

BSC6900 UMTS
1.12.2.10 Number of UEs Involved in Inter-Frequency Load-based Handovers in a

CLB Cell
Counters
73441246 VS.LCC.CLB.CS.InterFreq Number of CS UEs Involved

in Inter-Frequency Load-
based Handovers in a CS
CLB Cell
73441247 VS.LCC.CLB.PS.InterFreq Number of PS UEs Involved

in Inter-Frequency Load-
based Handovers in a PS
CLB Cell
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
VS.LCC.CLB.CS.InterFreq WRFD-140217 Inter-Frequency Load

Balancing Based on
Configurable Load
Threshold

BSC6900 UMTS
VS.LCC.CLB.PS.InterFreq WRFD-140217 Inter-Frequency Load

Balancing Based on
Configurable Load
Threshold
1.12.2.11 Number of Attempts to Configure CQI Feedback Period for a Cell
Counters
73424472 VS.HSDPA.DynCfgAtt.Lon Number of Attempts to

gCQI Configure a Long CQI
Feedback Period for a Cell
73424473 VS.HSDPA.DynCfgAtt.Sho Number of Attempts to

rtCQI Configure a Short CQI
Feedback Period for a Cell
Description
These counters provide the number of attempts to configure a short or long CQI feedback period
for an HSDPA serving cell. The RNC prolongs the CQI feedback period if the uplink cell load
is heavy, UEs move to areas with poor signal quality, or UEs process CS and PS combined
services. A short CQI feedback period is the period configured by the RNC before Dynamic
Configuration of HSDPA CQI Feedback Period is introduced.
Measurement point
During each measurement period, the RNC takes samples during the procedures involved when
settings of physical-layer parameters are changed, including RB reconfiguration, RB setup, cell
update, DRD, soft handover, and hard handover.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.HSDPA.DynCfgAtt.Lon WRFD-140215 Dynamic Configuration of

gCQI HSDPA CQI Feedback
Period
VS.HSDPA.DynCfgAtt.Sho WRFD-140215 Dynamic Configuration of

rtCQI HSDPA CQI Feedback
Period
1.12.2.12 Number of Attempts to Configure BLER in a Congested or Normal Cell
Counters
73424474 VS.ULBler.BE.Large Number of Attempts to

Configure BLER in a
Congested Cell
73424475 VS.ULBler.BE.Small Number of Attempts to

Configure BLER in a Normal
Cell
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

BSC6900 UMTS
Related Features
VS.ULBler.BE.Large WRFD-140216 Load-based Uplink Target

BLER Configuration
VS.ULBler.BE.Small WRFD-140216 Load-based Uplink Target

BLER Configuration
1.12.2.13 Number of CS RABs Abnormally Released for Special UEs for Cell
Counters
73424760 VS.RAB.SpecialUser.Abnor Number of CS RABs

mRel.CS Abnormally Released for
Special UEs for Cell
Description
This counter measures the number of CS radio access bearers (RABs) abnormally released for
special UEs in the best cell. Special UEs are UEs that are configured with weak reception.
Measurement point
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.

BSC6900 UMTS
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.

BSC6900 UMTS
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SpecialUser.Abnor WRFD-140205 Voice Service Experience

mRel.CS Improvement for Weak
Reception UEs
1.12.2.14 Number of CS RABs Normally Released for Special UEs for Cell

BSC6900 UMTS
Counters
73424761 VS.RAB.SpecialUser.Norm Number of CS RABs

Rel.CS Normally Released for
Special UEs for Cell
Description
This counter measures the number of CS RABs normally released for special UEs in the best
cell.
Measurement point
COMPLETE message to the CN. If the IU RELEASE COMMAND message indicates the reason
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.
If the IU RELEASE COMMAND message indicates the reason is "User Inactivity","Normal

BSC6900 UMTS

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
VS.RAB.SpecialUser.Norm WRFD-140205 Voice Service Experience

Rel.CS Improvement for Weak
Reception UEs
1.12.2.15 Uplink Actual Cell Load

BSC6900 UMTS
Counters
73441505 VS.MeanULActualPower- Mean Uplink Actual Cell

Load Load
73424787 VS.MaxULActualPower- Max Uplink Actual Cell

Load Load
73424788 VS.MinULActualPower- Min Uplink Actual Cell Load

Load
Description
These counters measure the average, maximum, and minimum uplink actual cell load in a cell.
These counters indicate the percentage of the uplink actual cell load in the received total
wideband power (RTWP).
Measurement point
The measurement is triggered at point A shown in figure 1 when the RNC receives a COMMON
MEASUREMENT REPORT message containing the RTWP for a cell. In this case, this counter
is calculated based on the measurement results contained in the message and the measurement
period is 5s. At the end of the measurement period, the RNC measures the maximum and
minimum uplink actual cell load and divides the accumulated value by the number of samples
to obtain the average uplink actual cell load.
Figure 1-380 Common measurement report procedure

BSC6900 UMTS
Formula
None
Unit
%
Related Features
VS.MeanULActualPower- WRFD-020102 Load Measurement

Load
VS.MaxULActualPower- WRFD-020102 Load Measurement

Load
VS.MinULActualPower- WRFD-020102 Load Measurement

Load
1.12.2.16 Number of CELL_FACH to URA_PCH State Transition Attempts
Counters
73424896 VS.DCCC.Att.F2U Number of CELL_FACH to

URA_PCH State Transition
Attempts for Cell
Description
This counter provides the number of state transition attempts from CELL_FACH to URA_PCH
in the cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending a
RADIO BEARER RECONFIGURATION message, instructing the UE to transit from the
CELL_FACH state to the URA_PCH state, the RNC measures the counter in the best cell where
the UE camps on before the state transition.

BSC6900 UMTS
Figure 1-381 RB Reconfiguration Procedure
The measurement is triggered at point A as shown in the following figure. When sending a
PHYSICAL CHANNEL RECONFIGURATION message, instructing the UE to transit from
the CELL_FACH state to the URA_PCH state, the RNC measures the counter in the best cell
where the UE camps on before the state transition.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.Att.F2U WRFD-021101 Dynamic Channel

(DCCC)
1.12.2.17 Number of Successful CELL_FACH to URA_PCH State Transitions
Counters
73424897 VS.DCCC.Succ.F2U Number of Successful

CELL_FACH to URA_PCH
State Transitions for Cell
Description
This counter provides the number of successful state transitions from CELL_FACH to
URA_PCH in the cell.
Measurement point
The measurement is triggered at point B as shown in the following figure. When receiving a
RADIO BEARER RECONFIGURATION COMPLETE message, indicating that the UE has
transited from the CELL_FACH state to the URA_PCH state, the RNC measures the counter in
the best cell where the UE camps on before the state transition.

BSC6900 UMTS
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message, indicating that the UE
has transited from the CELL_FACH state to the URA_PCH state, the RNC measures the counter
in the best cell where the UE camps on before the state transition.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.Succ.F2U WRFD-021101 Dynamic Channel

(DCCC)
1.12.2.18 Number of CELL_DCH to URA_PCH State Transition Attempts
Counters
73424898 VS.DCCC.Att.D2U Number of CELL_DCH to

URA_PCH State Transition
Attempts for Cell
Description
This counter provides the number of state transition attempts from CELL_DCH to URA_PCH
in the cell.
Measurement point
RADIO BEARER RECONFIGURATION message to the UE, instructing the UE to transit from
the CELL_DCH state to the URA_PCH state, the RNC measures the counter in the best cell
where the UE camps on before the state transition.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.DCCC.Att.D2U WRFD-021101 Dynamic Channel

(DCCC)
1.12.2.19 Number of Successful CELL_DCH to URA_PCH State Transitions

BSC6900 UMTS
Counters
73424899 VS.DCCC.Succ.D2U Number of Successful

CELL_DCH to URA_PCH
State Transitions for Cell
Description
This counter provides the number of successful state transitions from CELL_DCH to URA_PCH
in the cell.
Measurement point
RADIO BEARER RECONFIGURATION COMPLETE message, indicating that the UE has
transited from the CELL_DCH state to the URA_PCH state, the RNC measures the counter in
the best cell where the UE camps on before the state transition.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.DCCC.Succ.D2U WRFD-021101 Dynamic Channel

(DCCC)
1.12.2.20 Number of Pilot PO Optimization Attempts in the DL DPCH for Cell
Counters
73425824 VS.DL.DPCH.OptiPilot- Number of Pilot PO

POAttNum Optimization Attempts in the
DL DPCH for Cell
Description
This counter measures the number of the attempts to optimize the pilot PO in the best cell in a
measurement period.
Measurement point
This counter measures the number of the attempts to optimize the pilot PO in the downlink
DPCH in the best cell in a measurement period. The optimization attempt occurs during physical
parameter change procedures at the physical layer, including radio bearer (RB) setups, RB
reconfigurations, cell updates, and hard handovers.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.DL.DPCH.OptiPilot- WRFD-150230 DPCH Pilot Power

POAttNum Adjustment
1.12.2.21 Number of Normal Pilot PO Attempts in the DL DPCH for Cell
Counters
73425825 VS.DL.DPCH.NormalPilot- Number of Normal Pilot PO

POAttNum Attempts in the DL DPCH
for Cell
Description
This counter measures the number of the attempts to configure a normal pilot PO in the best cell
in a measurement period.
Measurement point
This counter measures the number of attempts to configure a normal pilot PO in the best cell in
the measurement period. The optimization attempt occurs during RRC connection setup, hard
handover H2D fallback, hard handover with relocation, inter-RAT incoming handover, P2D
state transition, DCCC F2D state transition, F2D state transition due to service establishment,
DRD procedure for HSPA retry, or RAB establishment for DRD to other cells.
Formula
None
Unit
None
Related Features
VS.DL.DPCH.NormalPilot- WRFD-150230 DPCH Pilot Power

POAttNum Adjustment

BSC6900 UMTS
1.12.2.22 Total number of times a micro cell transits to the total desensitization state
Counters
73426173 VS.TotalDesense.Num Total number of times a

micro cell transits to the total
Description
This counter indicates the total number of times a micro cell transits to the total desensitization
state.
Measurement point
This counter increases by increments of 1 each time the micro cell transits from partial
desensitization to total desensitization.
Formula
None
Unit
None
Related Features
VS.TotalDesense.Num WRFD-150201 Macro & Micro Co-carrier

WRFD-15020103 Uplink Interference Control
Micro Cell Dynamic Rx
Sensitivity Control
1.12.2.23 Total time periods of the total desensitization state for a micro cell
Counters
73426176 VS.TotalDesense.Time Total time periods of the total

desensitization state for a
micro cell

BSC6900 UMTS
Description
This counter indicates the total time periods of the total desensitization state for a micro cell.
Measurement point
This counter starts to measure the time period of the total desensitization state when the micro
cell transits from partial desensitization to total desensitization and stops the measurement when
the micro cell transits from total desensitization to partial desensitization. This counter is equal
to the sum of the time periods of the total desensitization state.
Formula
None
Unit
s
Related Features
VS.TotalDesense.Time WRFD-150201 Macro & Micro Co-carrier

Sensitivity Control
1.12.2.24 Average desensitization intensity for a micro cell
Counters
73426179 VS.MeanDesensePwr Average desensitization

intensity for a micro cell
Description
This counter indicates the average desensitization intensity for a micro cell. (Note: This counter
measures the intensity of desensitization on the NodeB, which is configured on the RNC. It does
not measure the intensity of static desensitization on the NodeB.)
Measurement point
When sending the physical sharing channel reconfiguration message to the NodeB, the RNC
reports the latest desensitization intensity to the platform if the desensitization intensity is

BSC6900 UMTS
changed. In addition, the RNC reports the current desensitization intensity to the platform every
minute. The average desensitization intensity is equal to the sum of reported desensitization
intensity values divided by the number of reports in a measurement period.
Formula
None
Unit
dBm
Related Features
VS.MeanDesensePwr WRFD-150201 Macro & Micro Co-carrier

Sensitivity Control
1.12.2.25 Average and Maximum Uplink Credit Usage of LCG for Cell
Counters
73426283 VS.LCG.ULCreditUsage.M Average Uplink Credit

ean Usage of LCG for Cell
73426284 VS.LCG.ULCreditUsage.M Maximum Uplink Credit

ax Usage of LCG for Cell
Description
These counters provide the average and maximum uplink credit usage of the local cell group
(LCG) where the cell belongs. Note: The CE-related counters measured at the RNC have
different values from these measured at the NodeB. CE-related counters measured at the RNC
are mainly used to estimate the access capability and are measured based on the number of CEs
consumed in the access strategy. CE-related counters measured at the NodeB are mainly used
to calculate the CEs that are actually used. In addition, the sampling period of the CE-related
counters measured at the RNC is 5s, which is different from that of the CE-related counters
measured at the NodeB (2 ms). Therefore, the counter values are not comparable, extremely
when the NodeB dynamic CE function is enabled.
Measurement point
The system samples the uplink credit usage of the logical cell group (LCG) every 5s. At the end
of the measurement period, the maximum uplink credit usage of the LCG for the cell is obtained.

BSC6900 UMTS
The average uplink credit usage of the LCG for the cell equals to accumulated value of the credit
usage at the sampling points divided by the number of sampling times.Counters related to CE
resource measurement by the RNC are different from those related to CE resource measurement
by the NodeB in that:? The counters related to CE resource measurement by the RNC estimate
the access capabilities based on the CE resources consumed by the admission policy, while the
counters related to CE resource measurement by the NodeB estimate the actual CE usage and
indicate the CE resources available for connected UEs. When the dynamic CE function is enabled
on the NodeB, the values of the counters related to CE resource measurement by the RNC are
quite different from the counters related to CE resource measurement by the NodeB.The RNC
measures the related counters every 5 s, while the NodeB measures the related counters every
2 ms TTI.
Formula
None
Unit
per mill
Related Features
VS.LCG.ULCreditUsage.M WRFD-140212 CE Overbooking

ean
VS.LCG.ULCreditUsage.M WRFD-140212 CE Overbooking

ax
1.12.2.26 Number of State Transition Attempts from CELL_PCH or URA_PCH to

CELL_FACH and then to CELL_DCH Due to Data Transmission Requirements for
Cell
Counters
73426333 VS.DCCC.Att.F2D.AfterP2 Number of State Transition

F Attempts from CELL_PCH
or URA_PCH to
CELL_FACH and then to
CELL_DCH Due to Data
Transmission Requirements
for Cell

BSC6900 UMTS
Description
This counter measures the number of state transition attempts from CELL_PCH or URA_PCH
or CELL_FACH and then to CELL_DCH due to data transmission requirements in a cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives a CELL
UPDATE message with cause value "uplink data transmission" or "paging response" from a UE
in the CELL_PCH or URA_PCH state and the cell update procedure is successful. The RNC
then instructs the UE to transition from the CELL_FACH state to the CELL_DCH state. When
the RNC sends a RADIO BEARER RECONFIGURATION message to the UE, this counter is
measured in the cell that the UE camps on.
Figure 1-387 RB Reconfiguration procedure after cell update procedure
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.DCCC.Att.F2D.AfterP2 WRFD-021101 Dynamic Channel

F Configuration Control
(DCCC)
1.12.2.27 Number of Successful State Transitions from CELL_PCH or URA_PCH to

CELL_FACH and then to CELL_DCH Due to Data Transmission Requirements for
Cell
Counters
73426334 VS.DCCC.Succ.F2D.AfterP Number of Successful State

2F Transitions from
CELL_PCH or URA_PCH to
CELL_FACH and then to
CELL_DCH Due to Data
Transmission Requirements
for Cell
Description
This counter measures the number of successful state transitions from CELL_PCH or URA_PCH
or CELL_FACH and then to CELL_DCH due to data transmission requirements in a cell.
Measurement point
The measurement is triggered at point B, as shown in the figure. The RNC receives a CELL
UPDATE message with cause value "uplink data transmission" or "paging response" from a UE
in the CELL_PCH or URA_PCH state and the cell update procedure is successful. The RNC
then instructs the UE to transition from the CELL_FACH state to the CELL_DCH state. When
the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from the
UE, this counter is measured in the cell that the UE camps on.

BSC6900 UMTS
Figure 1-388 RB Reconfiguration procedure after cell update procedure
Formula
None
Unit
None
Related Features
VS.DCCC.Succ.F2D.AfterP WRFD-021101 Dynamic Channel

2F Configuration Control
(DCCC)
1.12.3 Measurement related to BLER per cell(BLER.Cell)
Overview
Cell UL BLER Measurement is used to measure the BLER of the uplink data transmission of
all UEs in a cell according to different service classes and traffic rates.

BSC6900 UMTS
Counters
Description
67199797 VS.ULBler.AMR UL BLER of AMR Earlier than

Services for Cell V900R011
67184402 VS.ULBler.AMR.E Number of TBs with Earlier than

rrTB UL CRCI Error for V900R011
AMR Services for
Cell
67184403 VS.ULBler.AMR.S Number of BLER Earlier than

ample Samplings for AMR V900R011
Services for Cell
73394082 VS.ULBler.CS64 UL BLER of CS 64 V900R012

Kbit/s
Conversational
Services on DCH for
Cell
73394083 VS.ULBler.CS64.E Number of TBs with V900R012

rrTB UL CRCI Error for
CS 64 Kbit/s
Conversational
Services for Cell
73394084 VS.ULBler.CS64.S Number of BLER V900R012

ample Samplings for CS 64
Kbit/s
Conversational
Services for Cell
67199806 VS.ULBler.PS.BE. UL BLER of PS 8 Earlier than

DCH.8 Kbit/s BE Services V900R011
on DCH for Cell
67184420 VS.ULBler.PS.BE. Number of TBs with Earlier than

DCH.8.ErrTB UL CRCI Error for V900R011
PS 8 Kbit/s BE
Services for Cell
67184421 VS.ULBler.PS.BE. Sampling Times of Earlier than

DCH.8.Sample BLER for PS 8 Kbit/ V900R011
s BE Services for
Cell

on DCH for Cell

BSC6900 UMTS

Description

PS 16 Kbit/s BE
Services for Cell

DCH.16.Sample BLER for PS 16 V900R011
Kbit/s BE Services
for Cell

on DCH for Cell

PS 32 Kbit/s BE
Services for Cell

Kbit/s BE Services
for Cell

on DCH for Cell

PS 64 Kbit/s BE
Services for Cell

Kbit/s BE Services
for Cell

on DCH for Cell

PS 128 Kbit/s BE
Services for Cell

Kbit/s BE Services
for Cell

BSC6900 UMTS

Description

on DCH for Cell

PS 144 Kbit/s BE
Services for Cell

Kbit/s BE Services
for Cell

on DCH for Cell

PS 256 Kbit/s BE
Services for Cell

Kbit/s BE Services
for Cell

on DCH for Cell

PS 384 Kbit/s BE
Services for Cell

Kbit/s BE Services
for Cell
67202429 VS.ULBLer.Out.A Rate of Duration that Earlier than

MR UL BLER of AMR V900R011
Services Exceeds
Target Value for Cell

BSC6900 UMTS

Description
73394085 VS.ULBler.Out.CS Rate of Duration that V900R012

64 UL BLER of CS 64
Kbit/s
Conversational
Services on DCH
Exceeds Target
Value for Cell
67202439 VS.ULBler.Out.PS. Rate of Duration that Earlier than

BE.DCH.8 UL BLER of PS 8 V900R011
Kbit/s BE Services
on DCH Exceeds

Kbit/s BE Services
on DCH Exceeds

Kbit/s BE Services
on DCH Exceeds

Kbit/s BE Services
on DCH Exceeds

Kbit/s BE Services
on DCH Exceeds

Kbit/s BE Services
on DCH Exceeds

Kbit/s BE Services
on DCH Exceeds

BSC6900 UMTS

Description

Kbit/s BE Services
on DCH Exceeds

RACH Kbit/s BE Service on V900R011
RACH for Cell
67189898 VS.ULBler.PS.BE. Number of Error V900R012

RACH.ErrTB Blocks of PS 8 kbit/s
BE Services on
RACH for Cell
67189899 VS.ULBler.PS.BE. Number of PS 8 kbit/ V900R012

RACH.Sample s BE Service
Samplings on RACH
for Cell
67204479 VS.Voice.VQI.Goo Rate of Duration that Earlier than

d.TimeRate AMR Speech V900R011
Quality is GOOD for
Cell
67204480 VS.Voice.VQI.Acce Rate of Duration that Earlier than

pt.TimeRate AMR Speech V900R011
Quality is ACCEPT
for Cell
67204481 VS.Voice.VQI.Bad. Rate of Duration that Earlier than

TimeRate AMR Speech V900R011
Quality is BAD for
Cell
73410495 VS.ULBler.PS.Con UL BLER of PS V900R012

v Conversational
Services on DCH for
Cell
73394040 VS.ULBler.PS.Con Number of TBs with V900R012

v.ErrTB UL CRCI Error for
PS Conversational
Services for Cell
73394041 VS.ULBler.PS.Con Sampling Times of V900R012

v.Sample BLER for PS
Conversational
Services for Cell

BSC6900 UMTS

Description
73410496 VS.ULBler.PS.Str UL BLER of PS V900R012

Streaming Services
on DCH for Cell
73394042 VS.ULBler.PS.Str. Number of TBs with V900R012

ErrTB UL CRCI Error for
PS Streaming
Services for Cell
73394043 VS.ULBler.PS.Str. Sampling Times of V900R012

Sample BLER for PS
Streaming Services
for Cell
73410497 VS.ULBler.Out.PS. Rate of Duration that V900R012

Conv UL BLER of PS
Conversational
Services on DCH
Exceeds Target
Value for Cell
73410498 VS.ULBler.Out.PS. Rate of Duration that V900R012

Str UL BLER of PS
Streaming Services
on DCH Exceeds
73441535 VS.Voice.VQI.Poor Rate of Duration that V900R014

.TimeRate AMR Speech
Quality is POOR for
Cell
73441536 VS.Voice.VQI.Exce Rate of Duration that V900R014

llent.TimeRate AMR Speech
Quality is
EXCELLENT for
Cell
73442310 VS.Voice.VQI.Aver Average VQI for V900R015

age AMR Services
None
1.12.3.1 Percentage of Duration When UL BLER on DCH Exceeds Target Value for
Cell

BSC6900 UMTS
Counters
67202429 VS.ULBLer.Out.AMR Rate of Duration that UL

BLER of AMR Services
Exceeds Target Value for
Cell
73394085 VS.ULBler.Out.CS64 Rate of Duration that UL

BLER of CS 64 Kbit/s
DCH Exceeds Target Value
for Cell
67202439 VS.ULBler.Out.PS.BE.DC Rate of Duration that UL

H.8 BLER of PS 8 Kbit/s BE
Services on DCH Exceeds








BSC6900 UMTS
73410497 VS.ULBler.Out.PS.Conv Rate of Duration that UL

BLER of PS Conversational
73410498 VS.ULBler.Out.PS.Str Rate of Duration that UL

BLER of PS Streaming
specific formulas.
67189862 VS.ULBler.Out.AMR.Out- Duration that UL BLER of

Time AMR Speech Services
Reaches Target Value for
Cell
67189870 VS.ULBler.Out.CSRT. Duration that UL BLER of

64.OutTime CS 64 kbit/s Real-Time
Services Reaches Target
Value for Cell
67189890 VS.ULBler.Out.PSNrt.DCH Duration that UL BLER of

.128.OutTime PS 128 kbit/s Non-Real-
Time Services on DCH
Cell

Cell

.16.OutTime PS 16 kbit/s Non-Real-Time
Value for Cell

Cell

BSC6900 UMTS

Services on DCH Reaches

Cell

Services on DCH Reaches

Value for Cell
73394044 VS.ULBler.PS.Conv.Out- Duration that UL BLER of

Time PS Conversational Services
Cell
73394045 VS.ULBler.PS.Str.OutTime Duration that UL BLER of

PS Streaming Services
Cell
Description
These counters provide the percentage of the duration when the uplink block error rate (BLER)
on the DCH exceeds target value for services in the best cell. The measured services include the
adaptive multirate (AMR) service, CS 64 kbit/s conversational service, PS conversational
service, PS streaming service, and PS BE service. The VS.ULBLer.Out.AMR counter measures
only the narrowband AMR service.
Measurement point
The measurement is triggered in the best cell when the number of uplink TBs carrying services
on the DCH reaches the defined sampling window (500 TBs). The measured services include
the AMR service, CS 64 kbit/s conversational service, PS conversational service, PS streaming
service, and PS BE service. At the end of the measurement period, this counter is calculated by
dividing the number of times that the measured BLER exceeds the target value by the total
number of sampling times.

BSC6900 UMTS
Formula
VS.ULBLer.Out.AMR = {100}*[VS.ULBler.Out.AMR.OutTime]/
[VS.ULBler.AMR.Sample]
VS.ULBler.Out.CS64 = {100}*[VS.ULBler.Out.CSRT.64.OutTime]/
[VS.ULBler.CS64.Sample]
VS.ULBler.Out.PS.BE.DCH.8 = {100}*[VS.ULBler.Out.PSNrt.DCH.8.OutTime]/
[VS.ULBler.PS.BE.DCH.8.Sample]
VS.ULBler.Out.PS.Conv = {100}*[VS.ULBler.PS.Conv.OutTime]/
[VS.ULBler.PS.Conv.Sample]
VS.ULBler.Out.PS.Str = {100}*[VS.ULBler.PS.Str.OutTime]/[VS.ULBler.PS.Str.Sample]
Unit
%
Related Features
VS.ULBLer.Out.AMR WRFD-020503 Outer Loop Power Control
VS.ULBler.Out.CS64 WRFD-020503 Outer Loop Power Control
VS.ULBler.Out.PS.BE.DC WRFD-020503 Outer Loop Power Control

H.8

H.16

H.32

BSC6900 UMTS

H.64

H.128

H.144

H.256

H.384
VS.ULBler.Out.PS.Conv WRFD-020503 Outer Loop Power Control
VS.ULBler.Out.PS.Str WRFD-020503 Outer Loop Power Control
1.12.3.2 UL BLER of Services on RACH or DCH for Cell
Counters
67202447 VS.ULBler.PS.BE.RACH UL BLER of PS 8 Kbit/s BE

Service on RACH for Cell
67199797 VS.ULBler.AMR UL BLER of AMR Services

for Cell
73394082 VS.ULBler.CS64 UL BLER of CS 64 Kbit/s

DCH for Cell
67199806 VS.ULBler.PS.BE.DCH.8 UL BLER of PS 8 Kbit/s BE

Services on DCH for Cell



67199810 VS.ULBler.PS.BE.DCH. UL BLER of PS 128 Kbit/s

128 BE Services on DCH for Cell

BSC6900 UMTS



73410495 VS.ULBler.PS.Conv UL BLER of PS

DCH for Cell
73410496 VS.ULBler.PS.Str UL BLER of PS Streaming

Description
These counters provide the uplink block error rate (BLER) of services on the RACH or DCH in
the best cell. The measured services include the adaptive multirate (AMR) service, CS 64 kbit/
s conversational service, PS conversational service, PS streaming service, and PS BE service.
The VS.ULBler.AMR counter applies only to the narrowband AMR service.
Measurement point
on the RACH or DCH reaches the defined sampling window (500 TBs). The measured services
include the AMR service, CS 64 kbit/s conversational service, PS conversational service, PS
streaming service, and PS BE service.
Formula
VS.ULBler.PS.BE.RACH = [VS.ULBler.PS.BE.RACH.ErrTB]/
([VS.ULBler.PS.BE.RACH.Sample]*{5})
VS.ULBler.AMR = [VS.ULBler.AMR.ErrTB]/([VS.ULBler.AMR.Sample]*{5})
VS.ULBler.CS64 = [VS.ULBler.CS64.ErrTB]/([VS.ULBler.CS64.Sample]*{5})
VS.ULBler.PS.BE.DCH.8 = [VS.ULBler.PS.BE.DCH.8.ErrTB]/([VS.ULBler.PS.BE.DCH.
8.Sample]*{5})
VS.ULBler.PS.BE.DCH.16 = [VS.ULBler.PS.BE.DCH.16.ErrTB]/
([VS.ULBler.PS.BE.DCH.16.Sample]*{5})

BSC6900 UMTS
VS.ULBler.PS.Conv = [VS.ULBler.PS.Conv.ErrTB]/([VS.ULBler.PS.Conv.Sample]*{5})
VS.ULBler.PS.Str = [VS.ULBler.PS.Str.ErrTB]/([VS.ULBler.PS.Str.Sample]*{5})
Unit
%
Related Features
VS.ULBler.PS.BE.RACH WRFD-020503 Outer Loop Power Control
VS.ULBler.AMR WRFD-020503 Outer Loop Power Control
VS.ULBler.CS64 WRFD-020503 Outer Loop Power Control
VS.ULBler.PS.BE.DCH.8 WRFD-020503 Outer Loop Power Control
VS.ULBler.PS.BE.DCH. WRFD-020503 Outer Loop Power Control

128

144

256

384
VS.ULBler.PS.Conv WRFD-020503 Outer Loop Power Control
VS.ULBler.PS.Str WRFD-020503 Outer Loop Power Control

BSC6900 UMTS
1.12.3.3 Number of TBs with UL CRCI Errors for Services on RACH or DCH for
Cell
Counters
67189898 VS.ULBler.PS.BE.RACH.E Number of Error Blocks of

rrTB PS 8 kbit/s BE Services on
RACH for Cell
67184402 VS.ULBler.AMR.ErrTB Number of TBs with UL

CRCI Error for AMR
Services for Cell
73394083 VS.ULBler.CS64.ErrTB Number of TBs with UL

CRCI Error for CS 64 Kbit/s
Cell
67184420 VS.ULBler.PS.BE.DCH. Number of TBs with UL

8.ErrTB CRCI Error for PS 8 Kbit/s
BE Services for Cell




128.ErrTB CRCI Error for PS 128 Kbit/
s BE Services for Cell




BSC6900 UMTS
73394040 VS.ULBler.PS.Conv.ErrTB Number of TBs with UL

CRCI Error for PS
Cell
73394042 VS.ULBler.PS.Str.ErrTB Number of TBs with UL

CRCI Error for PS Streaming
Services for Cell
Description
These counters provide the number of TBs with uplink cyclic redundancy check indicator
(CRCI) errors for services on the RACH or DCH in the best cell. The measured services include
the adaptive multirate (AMR) service, CS 64 kbit/s conversational service, PS conversational
service, PS streaming service, and PS BE service. The VS.ULBler.AMR.ErrTB counter applies
only to the narrowband AMR service. Counters VS.ULBler.AMR.ErrTB,
VS.ULBler.CS64.ErrTB, VS.ULBler.PS.Conv.ErrTB, and VS.ULBler.PS.Str.ErrTB measure
TBs with uplink CRCI errors on the DCH.
Measurement point
Formula
None
Unit
None
Related Features
VS.ULBler.PS.BE.RACH.E WRFD-020503 Outer Loop Power Control

rrTB
VS.ULBler.AMR.ErrTB WRFD-020503 Outer Loop Power Control
VS.ULBler.CS64.ErrTB WRFD-020503 Outer Loop Power Control

8.ErrTB

BSC6900 UMTS

16.ErrTB

32.ErrTB

64.ErrTB

128.ErrTB

144.ErrTB

256.ErrTB

384.ErrTB
VS.ULBler.PS.Conv.ErrTB WRFD-020503 Outer Loop Power Control
VS.ULBler.PS.Str.ErrTB WRFD-020503 Outer Loop Power Control
1.12.3.4 Number of UL BLER Samplings for Services on the RACH or DCH for Cell
Counters
67189899 VS.ULBler.PS.BE.RACH.S Number of PS 8 kbit/s BE

ample Service Samplings on RACH
for Cell
67184403 VS.ULBler.AMR.Sample Number of BLER Samplings

for AMR Services for Cell
73394084 VS.ULBler.CS64.Sample Number of BLER Samplings

for CS 64 Kbit/s
Cell
67184421 VS.ULBler.PS.BE.DCH. Sampling Times of BLER for

8.Sample PS 8 Kbit/s BE Services for
Cell

Cell

BSC6900 UMTS

Cell

Cell

128.Sample PS 128 Kbit/s BE Services
for Cell

for Cell

for Cell

for Cell
73394041 VS.ULBler.PS.Conv.Sam- Sampling Times of BLER for

ple PS Conversational Services
for Cell
73394043 VS.ULBler.PS.Str.Sample Sampling Times of BLER for

PS Streaming Services for
Cell
Description
These counters provide the number of uplink block error rate (BLER) samplings for services on
the RACH or DCH in the best cell. The measured services include the adaptive multirate (AMR)
service, CS 64 kbit/s conversational service, PS conversational service, PS streaming service,
and PS BE service. The VS.ULBler.AMR.Sample counter applies only to the narrowband AMR
service. Counters VS.ULBler.AMR.Sample, VS.ULBler.CS64.Sample,
VS.ULBler.PS.Conv.Sample, and VS.ULBler.PS.Str.Sample measure the number of uplink
BLER samplings on the DCH.
Measurement point

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.ULBler.PS.BE.RACH.S WRFD-020503 Outer Loop Power Control

ample
VS.ULBler.AMR.Sample WRFD-020503 Outer Loop Power Control
VS.ULBler.CS64.Sample WRFD-020503 Outer Loop Power Control

8.Sample

16.Sample

32.Sample

64.Sample

128.Sample

144.Sample

256.Sample

384.Sample
VS.ULBler.PS.Conv.Sam- WRFD-020503 Outer Loop Power Control

ple
VS.ULBler.PS.Str.Sample WRFD-020503 Outer Loop Power Control
1.12.3.5 Percentage of Duration for AMR Voice Quality Being at A Level to Total
Call Duration for Cell

BSC6900 UMTS
Counters
73441536 VS.Voice.VQI.Excellent.Ti Rate of Duration that AMR

meRate Speech Quality is
EXCELLENT for Cell
67204479 VS.Voice.VQI.Good.Time- Rate of Duration that AMR

Rate Speech Quality is GOOD for
Cell
67204480 VS.Voice.VQI.Accept.Time Rate of Duration that AMR

Rate Speech Quality is ACCEPT
for Cell
67204481 VS.Voice.VQI.Bad.Time- Rate of Duration that AMR

Rate Speech Quality is BAD for
Cell
73441535 VS.Voice.VQI.Poor.Time- Rate of Duration that AMR

Rate Speech Quality is POOR for
Cell
Description
These counters provide the percentage of duration when the broadband or narrowband adaptive
multirate (AMR) voice quality is assessed as EXCELLENT, GOOD, ACCEPT, BAD, or POOR
to the total call duration. The mapping between the AMR voice quality level and the voice quality
indicator (VQI) are as follows:
EXCELLENT: VQI > 4
GOOD: VQI > 3 and VQI <= 4
ACCEPT: VQI > 2 and VQI <= 3
BAD: VQI > 1 and VQI <= 2
POOR: VQI <= 1
Measurement point
In a measurement period, the duration when the AMR voice quality is assessed as EXCELLENT,
GOOD, ACCEPT, BAD, or POOR is sampled every 2.4s. At the end of the measurement period,
these counters are calculated by dividing the corresponding accumulated duration by the total
call duration in the best cell.
Formula
None

BSC6900 UMTS
Unit
%
Related Features
VS.Voice.VQI.Excellent.Ti WRFD-010501 Conversational QoS Class

meRate
VS.Voice.VQI.Good.Time- WRFD-010501 Conversational QoS Class

Rate
VS.Voice.VQI.Accept.Time WRFD-010501 Conversational QoS Class

Rate
VS.Voice.VQI.Bad.Time- WRFD-010501 Conversational QoS Class

Rate
VS.Voice.VQI.Poor.Time- WRFD-010501 Conversational QoS Class

Rate
1.12.3.6 Average VQI for AMR Services
Counters
73442310 VS.Voice.VQI.Average Average VQI for AMR

Services
Description
This counter provides the average uplink VQI for narrowband and broadband AMR services in
the best cell.
Measurement point
The system calculates the total uplink VQI for narrowband and broadband AMR services in the
best cell. Within each measurement period, this counter divides the total uplink VQI by the
sampling times.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.Voice.VQI.Average WRFD-010501 Conversational QoS Class
1.12.4 Cell Measurement on BOOST(BOOST.CELL)
Overview
The BOOST.CELL function subset includes the numbers of UU BOOST service establishments
and releases for UMTS-UMTS dual terminal in the downlink, and indicators related to UU
BOOST traffic. This function subset is effective only when the UMTS-UMTS Dual Terminal
Downlink BOOST feature is enabled.
Counters
Description
73424977 VS.BOOST.UU.An Number of R99 V900R014

chor.DL.R99.Bytes Downlink Bytes of
UU BOOST Anchor
for Cell
73441547 VS.BOOST.UU.An Mean Throughput of V900R014

chor.DL.R99.Mean R99 Downlink of UU
Throughput BOOST Anchor for
Cell
73424979 VS.BOOST.UU.An Number of HSDPA V900R014

chor.DL.HSDPA.B Downlink Bytes of
ytes UU BOOST Anchor
for Cell

chor.DL.HSDPA.M HSDPA Downlink of
eanThroughput UU BOOST Anchor
for Cell
73424981 VS.BOOST.UU.An Number of R99 V900R014

chor.UL.R99.Bytes Uplink Bytes of UU
BOOST Anchor for
Cell

BSC6900 UMTS

Description

chor.UL.R99.Mean R99 Uplink of UU
Throughput BOOST Anchor for
Cell
73424983 VS.BOOST.UU.An Number of HSUPA V900R014

chor.UL.HSUPA.B Uplink Bytes of UU
ytes BOOST Anchor for
Cell

chor.UL.HSUPA.M HSUPA Uplink of
eanThroughput UU BOOST Anchor
for Cell
73424985 VS.BOOST.UU.Br Number of R99 V900R014

anch.DL.R99.Bytes Downlink Bytes of
UU BOOST Branch
for Cell
73441551 VS.BOOST.UU.Br Mean Throughput of V900R014

anch.DL.R99.Mean R99 Downlink of UU
Throughput BOOST Branch for
Cell
73424987 VS.BOOST.UU.Br Number of HSDPA V900R014

anch.DL.HSDPA.B Downlink Bytes of
ytes UU BOOST Branch
for Cell

anch.DL.HSDPA. HSDPA Downlink of
MeanThroughput UU BOOST Branch
for Cell
73424989 VS.BOOST.UU.Br Number of R99 V900R014

anch.UL.R99.Bytes Uplink Bytes of UU
BOOST Branch for
Cell

anch.UL.R99.Mean R99 Uplink of UU
Throughput BOOST Branch for
Cell
73424991 VS.BOOST.UU.Br Number of HSUPA V900R014

anch.UL.HSUPA.B Uplink Bytes of UU
ytes BOOST Branch for
Cell

BSC6900 UMTS

Description

anch.UL.HSUPA. HSUPA Uplink of
MeanThroughput UU BOOST Branch
for Cell
73424993 VS.BOOST.UU.BP Number of UU V900R014

LCapRprtInd BOOST BPL
Capability Indication
Messages Received
for Cell
73424994 VS.BOOST.UU.BP Number of V900R014

LCapRsp.Succ Successful
Responses to UU
BOOST BPL
Capability Indication
Messages
Transmitted for Cell

LInfoRprtInd BOOST BPL User
Information
Indication Messages
Received for Cell
73424996 VS.BOOST.UU.BP Number of V900R014

LInfoRsp.Succ Successful
Responses to UU
BOOST BPL User
Information
Indication Messages

LRel BOOST BPL
Release Messages
73424998 VS.BOOST.UU.Su Number of V900R014

ccEstab Successful UU
BOOST Setups for
Cell
73424999 VS.BOOST.UU.An Number of Normal V900R014

chor.NormRel UU BOOST Anchor
Releases for Cell
73425000 VS.BOOST.UU.Br Number of Normal V900R014

anch.NormRel UU BOOST Branch
Releases for Cell

BSC6900 UMTS

Description
73441555 VS.BOOST.UU.An Average Number of V900R014

chorUEs.Mean UU BOOST Anchor
UEs for Cell
73441556 VS.BOOST.UU.Br Average Number of V900R014

anchUEs.Mean UU BOOST Branch
UEs for Cell
None
1.12.4.1 Number of R99 Downlink Bytes of UU BOOST Anchor for Cell
Counters
73424977 VS.BOOST.UU.Anchor.DL Number of R99 Downlink

.R99.Bytes Bytes of UU BOOST Anchor
for Cell
Description
This counter provides the total RLC traffic volume transmitted by PS services of UU BOOST
anchor UEs on downlink R99 channels in cells in the active set. RLC headers and retransmitted
data are not included.
Measurement point
When downlink PS RABs of UU BOOST anchor UEs are carried over R99 channels (including
the DCH and FACH) and there is downlink data transmission, the RNC measures the number
of all bytes (data of all service types) transmitted on the downlink RLC layer of cells in the active
set. RLC headers and retransmitted data are not included.
Formula
None
Unit
byte

BSC6900 UMTS
Related Features
None
1.12.4.2 Mean Throughput of R99 Downlink of UU BOOST Anchor for Cell
Counters
73441547 VS.BOOST.UU.Anchor.DL Mean Throughput of R99

.R99.MeanThroughput Downlink of UU BOOST
Anchor for Cell
specific formulas.
73424978 VS.BOOST.UU.Anchor.DL Duration of R99 Downlink

.R99.Time Sending Data of UU BOOST
Anchor for Cell
Description
This counter provides the mean throughput rate of PS services of UU BOOST anchor UEs
transmitted on downlink R99 channels of cells in the active set.
Measurement point
When downlink PS RABs of UU BOOST anchor UEs are carried over R99 channels (including
the DCH and FACH) and there is downlink data transmission, the RNC measures the total actual
data transmission time and number of all transmitted bytes of cells in the active set. At the end
of a measurement period, the RNC measures this item by dividing the number of all transmitted
bytes by the total actual data transmission time. In soft handover scenarios, the RNC measures
this item of each cell in the active set separately.
Formula
VS.BOOST.UU.Anchor.DL.R99.MeanThroughput =
[VS.BOOST.UU.Anchor.DL.R99.Bytes]*{8}/[VS.BOOST.UU.Anchor.DL.R99.Time]
Unit
kbit/s

BSC6900 UMTS
Related Features
None
1.12.4.3 Number of HSDPA Downlink Bytes of UU BOOST Anchor for Cell
Counters
73424979 VS.BOOST.UU.Anchor.DL Number of HSDPA

.HSDPA.Bytes Downlink Bytes of UU
BOOST Anchor for Cell
Description
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
Formula
None
Unit
byte
Related Features
None
1.12.4.4 Mean Throughput of HSDPA Downlink of UU BOOST Anchor for Cell
Counters
73441548 VS.BOOST.UU.Anchor.DL Mean Throughput of HSDPA

.HSDPA.MeanThroughput Downlink of UU BOOST
Anchor for Cell

BSC6900 UMTS
specific formulas.
73424980 VS.BOOST.UU.Anchor.DL Duration of HSDPA

.HSDPA.Time Downlink Sending Data of
UU BOOST Anchor for Cell
Description
transmitted on downlink HSDPA channels in the HSDPA serving cell.
Measurement point
When downlink PS RABs of UU BOOST anchor UEs are carried over HSDPA channels and
there is downlink data transmission, the RNC measures the total actual data transmission time
and number of all transmitted bytes in the HSDPA serving cell. At the end of a measurement
period, the RNC measures this item by dividing the number of all transmitted bytes by the total
actual data transmission time.
Formula
VS.BOOST.UU.Anchor.DL.HSDPA.MeanThroughput =
[VS.BOOST.UU.Anchor.DL.HSDPA.Bytes]*{8}/
[VS.BOOST.UU.Anchor.DL.HSDPA.Time]
Unit
kbit/s
Related Features
None
1.12.4.5 Number of R99 Uplink Bytes of UU BOOST Anchor for Cell
Counters
73424981 VS.BOOST.UU.Anchor.UL Number of R99 Uplink Bytes

.R99.Bytes of UU BOOST Anchor for
Cell

BSC6900 UMTS
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
Measurement point
When uplink PS RABs of UU BOOST anchor UEs are carried over R99 channels (including the
DCH and RACH) and there is uplink data reception, the RNC measures the number of all bytes
(data of all service types) received on the uplink RLC layer of cells in the active set. RLC headers
and retransmitted data are not included.
Formula
None
Unit
byte
Related Features
None
1.12.4.6 Mean Throughput of R99 Uplink of UU BOOST Anchor for Cell
Counters
73441549 VS.BOOST.UU.Anchor.UL Mean Throughput of R99

.R99.MeanThroughput Uplink of UU BOOST
Anchor for Cell
specific formulas.
73424982 VS.BOOST.UU.Anchor.UL Duration of R99 Uplink

.R99.Time Receiving Data of UU
Description
received on uplink R99 channels of cells in the active set.

BSC6900 UMTS
Measurement point
When uplink PS RABs of UU BOOST anchor UEs are carried over R99 channels (including the
DCH and RACH) and there is uplink data reception, the RNC measures the total actual data
reception time and number of all received bytes of cells in the active set. At the end of a
measurement period, the RNC measures this item by dividing the number of all received bytes
by the total actual data reception time. In soft handover scenarios, the RNC measures this item
of each cell in the active set separately after combination.
Formula
VS.BOOST.UU.Anchor.UL.R99.MeanThroughput =
[VS.BOOST.UU.Anchor.UL.R99.Bytes]*{8}/[VS.BOOST.UU.Anchor.UL.R99.Time]
Unit
kbit/s
Related Features
None
1.12.4.7 Number of HSUPA Uplink Bytes of UU BOOST Anchor for Cell
Counters
73424983 VS.BOOST.UU.Anchor.UL Number of HSUPA Uplink

.HSUPA.Bytes Bytes of UU BOOST Anchor
for Cell
Description
anchor UEs on uplink HSUPA channels in cells in the HSUPA active set. RLC headers and
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

BSC6900 UMTS
Unit
byte
Related Features
None
1.12.4.8 Mean Throughput of HSUPA Uplink of UU BOOST Anchor for Cell
Counters
73441550 VS.BOOST.UU.Anchor.UL Mean Throughput of HSUPA

.HSUPA.MeanThroughput Uplink of UU BOOST
Anchor for Cell
specific formulas.
73424984 VS.BOOST.UU.Anchor.UL Duration of HSUPA Uplink

.HSUPA.Time Receiving Data of UU
Description
received on uplink HSUPA channels of cells in the HSUPA active set.
Measurement point
When uplink PS RABs of UU BOOST anchor UEs are carried over HSUPA channels and there
is uplink data reception, the RNC measures the total actual data reception time and number of
all received bytes of cells in the HSUPA active set. At the end of a measurement period, the
RNC measures this item by dividing the number of all received bytes by the total actual data
reception time. In soft handover scenarios, the RNC measures this item of each cell in the HSUPA
active set separately after combination.
Formula
VS.BOOST.UU.Anchor.UL.HSUPA.MeanThroughput =
[VS.BOOST.UU.Anchor.UL.HSUPA.Bytes]*{8}/
[VS.BOOST.UU.Anchor.UL.HSUPA.Time]

BSC6900 UMTS
Unit
kbit/s
Related Features
None
1.12.4.9 Number of R99 Downlink Bytes of UU BOOST Branch for Cell
Counters
73424985 VS.BOOST.UU.Branch.DL. Number of R99 Downlink

R99.Bytes Bytes of UU BOOST Branch
for Cell
Description
branch UEs on downlink R99 channels in cells in the active set. RLC headers and retransmitted
Measurement point
When downlink PS RABs of UU BOOST branch UEs are carried over R99 channels (including
the DCH and FACH) and there is downlink data transmission, the RNC measures the number
of all bytes (data of all service types) transmitted on the downlink RLC layer of cells in the active
set. RLC headers and retransmitted data are not included.
Formula
None
Unit
byte
Related Features
None
1.12.4.10 Mean Throughput of R99 Downlink of UU BOOST Branch for Cell

BSC6900 UMTS
Counters
73441551 VS.BOOST.UU.Branch.DL. Mean Throughput of R99

R99.MeanThroughput Downlink of UU BOOST
Branch for Cell
specific formulas.
73424986 VS.BOOST.UU.Branch.DL. Duration of R99 Downlink

R99.Time Sending Data of UU BOOST
Branch for Cell
Description
This counter provides the mean throughput rate of PS services of UU BOOST branch UEs
transmitted on downlink R99 channels of cells in the active set.
Measurement point
When downlink PS RABs of UU BOOST branch UEs are carried over R99 channels (including
the DCH and FACH) and there is downlink data transmission, the RNC measures the total actual
data transmission time and number of all transmitted bytes of cells in the active set. At the end
of a measurement period, the RNC measures this item by dividing the number of all transmitted
bytes by the total actual data transmission time. In soft handover scenarios, the RNC measures
this item of each cell in the active set separately.
Formula
VS.BOOST.UU.Branch.DL.R99.MeanThroughput =
[VS.BOOST.UU.Branch.DL.R99.Bytes]*{8}/[VS.BOOST.UU.Branch.DL.R99.Time]
Unit
kbit/s
Related Features
None
1.12.4.11 Number of HSDPA Downlink Bytes of UU BOOST Branch for Cell

BSC6900 UMTS
Counters
73424987 VS.BOOST.UU.Branch.DL. Number of HSDPA

HSDPA.Bytes Downlink Bytes of UU
BOOST Branch for Cell
Description
branch UEs on downlink HSDPA channels in the HSDPA serving cell. RLC headers and
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
Formula
None
Unit
byte
Related Features
None
1.12.4.12 Mean Throughput of HSDPA Downlink of UU BOOST Branch for Cell
Counters
73441552 VS.BOOST.UU.Branch.DL. Mean Throughput of HSDPA

HSDPA.MeanThroughput Downlink of UU BOOST
Branch for Cell
specific formulas.

BSC6900 UMTS
73424988 VS.BOOST.UU.Branch.DL. Duration of HSDPA

HSDPA.Time Downlink Sending Data of
UU BOOST Branch for Cell
Description
transmitted on downlink HSDPA channels in the HSDPA serving cell.
Measurement point
When downlink PS RABs of UU BOOST branch UEs are carried over HSDPA channels and
there is downlink data transmission, the RNC measures the total actual data transmission time
and number of all transmitted bytes in the HSDPA serving cell. At the end of a measurement
period, the RNC measures this item by dividing the number of all transmitted bytes by the total
actual data transmission time.
Formula
VS.BOOST.UU.Branch.DL.HSDPA.MeanThroughput =
[VS.BOOST.UU.Branch.DL.HSDPA.Bytes]*{8}/
[VS.BOOST.UU.Branch.DL.HSDPA.Time]
Unit
kbit/s
Related Features
None
1.12.4.13 Number of R99 Uplink Bytes of UU BOOST Branch for Cell
Counters
73424989 VS.BOOST.UU.Branch.UL. Number of R99 Uplink Bytes

R99.Bytes of UU BOOST Branch for
Cell
Description
branch UEs on uplink R99 channels in cells in the active set. RLC headers and retransmitted

BSC6900 UMTS
Measurement point
When uplink PS RABs of UU BOOST branch UEs are carried over R99 channels (including the
DCH and RACH) and there is uplink data reception, the RNC measures the number of all bytes
(data of all service types) received on the uplink RLC layer of cells in the active set. RLC headers
and retransmitted data are not included.
Formula
None
Unit
byte
Related Features
None
1.12.4.14 Mean Throughput of R99 Uplink of UU BOOST Branch for Cell
Counters
73441553 VS.BOOST.UU.Branch.UL. Mean Throughput of R99

R99.MeanThroughput Uplink of UU BOOST
Branch for Cell
specific formulas.
73424990 VS.BOOST.UU.Branch.UL. Duration of R99 Uplink

R99.Time Receiving Data of UU
Description
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

BSC6900 UMTS
measurement period, the RNC measures this item by dividing the number of all received bytes
by the total actual data reception time. In soft handover scenarios, the RNC measures this item
of each cell in the active set separately after combination.
Formula
VS.BOOST.UU.Branch.UL.R99.MeanThroughput =
[VS.BOOST.UU.Branch.UL.R99.Bytes]*{8}/[VS.BOOST.UU.Branch.UL.R99.Time]
Unit
kbit/s
Related Features
None
1.12.4.15 Number of HSUPA Uplink Bytes of UU BOOST Branch for Cell
Counters
73424991 VS.BOOST.UU.Branch.UL. Number of HSUPA Uplink

HSUPA.Bytes Bytes of UU BOOST Branch
for Cell
Description
branch UEs on uplink HSUPA channels in cells in the HSUPA active set. RLC headers and
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

BSC6900 UMTS
Related Features
None
1.12.4.16 Mean Throughput of HSUPA Uplink of UU BOOST Branch for Cell
Counters
73441554 VS.BOOST.UU.Branch.UL. Mean Throughput of HSUPA

HSUPA.MeanThroughput Uplink of UU BOOST
Branch for Cell
specific formulas.
73424992 VS.BOOST.UU.Branch.UL. Duration of HSUPA Uplink

HSUPA.Time Receiving Data of UU
Description
received on uplink HSUPA channels of cells in the HSUPA active set.
Measurement point
When uplink PS RABs of UU BOOST branch UEs are carried over HSUPA channels and there
is uplink data reception, the RNC measures the total actual data reception time and number of
all received bytes of cells in the HSUPA active set. At the end of a measurement period, the
RNC measures this item by dividing the number of all received bytes by the total actual data
reception time. In soft handover scenarios, the RNC measures this item of each cell in the HSUPA
active set separately after combination.
Formula
VS.BOOST.UU.Branch.UL.HSUPA.MeanThroughput =
[VS.BOOST.UU.Branch.UL.HSUPA.Bytes]*{8}/
[VS.BOOST.UU.Branch.UL.HSUPA.Time]
Unit
kbit/s

BSC6900 UMTS
Related Features
None
1.12.4.17 Number of UU BOOST BPL Capability Indication Messages Received for

Cell
Counters
73424993 VS.BOOST.UU.BPLCapRp Number of UU BOOST BPL

rtInd Capability Indication
Messages Received for Cell
Description
This counter provides the number of UU BOOST BPL capability indication messages received
in the best cell.
Measurement point
This measurement is triggered at point A as shown in the figure. When the RNC receives a UU
BOOST BPL capability indication message after PS RAB establishment, the RNC measures this
item in the best cell of the UE.
Figure 1-389 BPL Message Interaction
Formula
None

BSC6900 UMTS
Unit
None
Related Features
None
1.12.4.18 Number of Successful Responses to UU BOOST BPL Capability

Indication Messages Transmitted for Cell
Counters
73424994 VS.BOOST.UU.BPLCapRs Number of Successful

p.Succ Responses to UU BOOST
BPL Capability Indication
Messages Transmitted for
Cell
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
1.12.4.19 Number of UU BOOST BPL User Information Indication Messages

Received for Cell
Counters
73424995 VS.BOOST.UU.BPLIn- Number of UU BOOST BPL

foRprtInd User Information Indication
Messages Received for Cell
Description
This counter provides the number of UU BOOST BPL user information indication messages
received in the best cell.
Measurement point
This measurement is triggered at point C as shown in the figure. When the RNC receives a UU
BOOST BPL user information indication message after PS RAB establishment, the RNC
measures this item in the best cell of the UE.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
1.12.4.20 Number of Successful Responses to UU BOOST BPL User Information

Indication Messages Transmitted for Cell
Counters
73424996 VS.BOOST.UU.BPLInfoRs Number of Successful

p.Succ Responses to UU BOOST
BPL User Information
Indication Messages
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
1.12.4.21 Number of UU BOOST BPL Release Messages Transmitted for Cell
Counters
73424997 VS.BOOST.UU.BPLRel Number of UU BOOST BPL

Release Messages
Description
This counter provides the number of UU BOOST BPL release messages transmitted in the best
cell.

BSC6900 UMTS
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
1.12.4.22 Number of Successful UU BOOST Setups for Cell
Counters
73424998 VS.BOOST.UU.SuccEstab Number of Successful UU

BOOST Setups for Cell
Description
This counter provides the number of successful UU BOOST setups in the best cell.

BSC6900 UMTS
Measurement point
The measurement is triggered at point D as shown in the figure. When the RNC successfully
responds to a UU BOOST BPL user information indication message and anchor and branch UEs
complete UU BOOST configuration after PS RAB establishment, the RNC measures this item
in the best cell of the anchor UE.
Formula
None
Unit
None
Related Features
None
1.12.4.23 Number of Normal UU BOOST Anchor Releases for Cell
Counters
73424999 VS.BOOST.UU.Anchor.Nor Number of Normal UU

mRel BOOST Anchor Releases for
Cell

BSC6900 UMTS
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".
Figure 1-395 Iu release
Formula
None
Unit
None
Related Features
None
1.12.4.24 Number of Normal UU BOOST Branch Releases for Cell

BSC6900 UMTS
Counters
73425000 VS.BOOST.UU.Branch.Nor Number of Normal UU

mRel BOOST Branch Releases for
Cell
Description
This counter provides the number of normal UU BOOST branch UE releases in the best cell.
Measurement point
This measurement is triggered at point A as shown in the figure. When the RNC receives an IU
RELEASE COMMAND message from the CN, the RNC releases related RAB resources and
responds with an IU RELEASE COMPLETE message. The RNC measures this item in the best
cell of the UE if the following conditions are met: The UE is the UU BOOST branch UE and
has PS services to be released. The release cause in the IU RELEASE COMMAND message is
"User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization". OR
The RNC initiates a release request with the release cause of "User Inactivity", "Network
Optimization", or "UE Generated Signalling Connection Release".
Figure 1-396 IU
Formula
None

BSC6900 UMTS
Unit
None
Related Features
None
1.12.4.25 Average Number of UU BOOST Anchor UEs for Cell
Counters
73441555 VS.BOOST.UU.AnchorUEs Average Number of UU

.Mean BOOST Anchor UEs for Cell
Description
This counter provides the average number of UU BOOST anchor UEs in the best cell.
Measurement point
In the best cell of the anchor UEs, the RNC periodically samples the number of UU BOOST
anchor UEs. The sample period is 5s. At the end of a measurement period, the RNC measures
this item by calculating the sum of UEs at all sample points and dividing the sum by the times
of sampling.
Formula
None
Unit
None
Related Features
None
1.12.4.26 Average Number of UU BOOST Branch UEs for Cell
Counters
73441556 VS.BOOST.UU.BranchUEs Average Number of UU

.Mean BOOST Branch UEs for Cell

BSC6900 UMTS
Description
This counter provides the average number of UU BOOST branch UEs in the best cell.
Measurement point
In the best cell of the branch UEs, the RNC periodically samples the number of UU BOOST
branch UEs. The sample period is 5s. At the end of a measurement period, the RNC measures
this item by calculating the sum of UEs at all sample points and dividing the sum by the times
of sampling.
Formula
None
Unit
None
Related Features
None
1.12.5 Common Channel Measurement per Cell(CCH.Cell)
Overview
This function subset measures the amount of traffic in the uplink and downlink of a common
transport channel such as a PCH, RACH, and FACH in a cell.
Counters
Description
73423941 VS.IndepTRBNum Number of TBs That V900R014

.FACH Contain only TRB
Data on FACHs
73423942 VS.SRBNum.FAC Number of TBs That V900R014

H Contain SRB Data on
FACHs
73423943 VS.OneSRBTTINu Number of TTIs V900R014

m.FACH During Which One
SRB TB Is
Transmitted on
FACHs

BSC6900 UMTS

Description
73423944 VS.TRBNum.RAC Number of TRB TBs V900R014

H Received on RACHs
None
1.12.5.1 Number of TBs That Contain only TRB Data on FACHs
Counters
73423941 VS.IndepTRBNum.FACH Number of TBs That Contain

only TRB Data on FACHs
Description
This counter measures the number of TBs that contain only TRB data on FACHs in a cell. It
indicates the amount of user plane traffic transmitted on FACHs in a cell.
Measurement point
This counter is measured at MAC-c according to the type of data transmitted on FACHs during
each transmission time interval (TTI).
Formula
None
Unit
None
Related Features
VS.IndepTRBNum.FACH WRFD-021000 Transport Channel

Management

BSC6900 UMTS
1.12.5.2 Number of TBs That Contain SRB Data on FACHs
Counters
73423942 VS.SRBNum.FACH Number of TBs That Contain

SRB Data on FACHs
Description
This counter measures the number of TBs that contain SRB data on FACHs in a cell. It indicates
the amount of control plane traffic transmitted on FACHs in a cell.
Measurement point
each transmission time interval (TTI).
Formula
None
Unit
None
Related Features
VS.SRBNum.FACH WRFD-021000 Transport Channel

Management
1.12.5.3 Number of TTIs During Which One SRB TB Is Transmitted on FACHs
Counters
73423943 VS.OneSRBTTINum.FACH Number of TTIs During

Which One SRB TB Is
Transmitted on FACHs

BSC6900 UMTS
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
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
VS.OneSRBTTINum.FACH WRFD-021000 Transport Channel

Management
1.12.5.4 Number of TRB TBs Received on RACHs
Counters
73423944 VS.TRBNum.RACH Number of TRB TBs

Received on RACHs
Description
This counter measures the number of TRB TBs received on RACHs in a cell.
Measurement point
This counter is measured at MAC-c.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.TRBNum.RACH WRFD-021000 Transport Channel

Management
1.12.6 Cell Update Measurement per cell(CELLUPDATE.Cell)
Overview
An UE may send a CELL UPDATE message to the RNC for different causes, such as uplink
data transmission, paging response, radio link failure, re-entering service area, RLC
unrecoverable error, cell reselection, and periodical cell update.
This function subset is used to assess the cell update procedure by measuring the number of cell
updates triggered by different causes, and the number of successful or failed cell updates
triggered by each cause.
Counters
Description
67180378 VS.AttCellUpdt.R Number of Cell Earlier than

LFail Updates Due to V900R011
Radio Link Failure
for Cell
67189767 VS.SuccCellUpdt.R Number of Earlier than

LFail Successful Cell V900R011
Updates Due to
Radio Link Failure
for Cell
67189768 VS.FailCellUpdt.R Number of Failed Earlier than

LFail.NoReply Cell Updates Due to V900R011
No Response from
UE for Cell (Cell
Update Caused by
RL Failure)

BSC6900 UMTS

Description
67180370 VS.CellUpdt.Con- Number of CELL Earlier than

firm UPDATE V900R011
CONFIRM
Messages from
SRNC for Cell
67192569 VS.AttCellUpdt Number of Cell Earlier than

Updates for Cell V900R011
67192570 VS.AttCellUpdt.Er Number of Cell Earlier than

rSRB Updates Due to SRB V900R011
RLC Unrecoverable
Error for Cell
67192571 VS.AttCellUpdt.Er Number of Cell Earlier than

rTRB Updates Due to TRB V900R011
RLC Unrecoverable
Error for Cell
67192572 VS.SuccCellUpdt.E Number of Earlier than

rrTRB Successful Cell V900R011
Updates Due to TRB
RLC Unrecoverable
Error for Cell
67192573 VS.AttCellUpdt.M Number of Cell Earlier than

bmsRecv Updates Due to V900R011
MBMS Reception
for Cell
67192574 VS.SuccCellUpdt. Number of Earlier than

MbmsRecv Successful Cell V900R011
Updates Due to
MBMS Reception
for Cell
67192575 VS.AttCellUpdt.M Number of Cell Earlier than

bmsPtpRbReq Updates Due to V900R011
MBMS PtP RB
Request for Cell
67192576 VS.SuccCellUpdt. Number of Earlier than

MbmsPtpRbReq Successful Cell V900R011
Updates Due to
MBMS PtP RB
Request for Cell
67180372 VS.AttCellUpdt.Pr Number of Earlier than

d Periodical Cell V900R011
Updates for Cell

BSC6900 UMTS

Description
67180373 VS.AttCellUpdt.Re Number of Cell Earlier than

sel Updates Due to Cell V900R011
Reselection for Cell
67180374 VS.AttCellUpdt.RS Number of Cell Earlier than

A Updates Due to Re- V900R011
Entering Service
Area for Cell
67180375 VS.AttCellUpdt.Pa Number of Cell Earlier than

geRsp Updates Due to V900R011
Paging Response for
Cell
67180376 VS.AttCellUpdt.U Number of Cell Earlier than

LDataTrans Updates Due to V900R011
Uplink Data
Transmission for
Cell
67180379 VS.SuccCellUpdt.P Number of Earlier than

rd Successful V900R011
Periodical Cell
Updates for Cell

esel Successful Cell V900R011
Updates Due to Cell

sa Successful Cell V900R011
Updates Due to Re-
Entering Service
Area for Cell
67180382 VS.SuccCellUpdt.P Number of Earlier than

ageRsp Successful Cell V900R011
Updates Due to
Paging Response for
Cell
67180383 VS.SuccCellUpdt.U Number of Earlier than

LDataTrans Successful Cell V900R011
Updates Due to
Uplink Data
Transmission for
Cell

BSC6900 UMTS

Description
67180371 VS.SuccCellUpdt Number of Earlier than

Successful Cell V900R011
Updates for Cell
67180386 VS.CellUpdt.RRC Number of RRC Earlier than

Rel Connection Releases V900R011
Due to Cell Update
Failure for Cell
73423781 VS.SuccCellUpdt.E Number of V900R013

rrSRB Successful Cell
Updates Due to SRB
RLC Unrecoverable
Error for Cell
73424125 VS.FailCellUpdt.E Number of Cell V900R014

rrSRB.NoReply.FA Update Failures due
CH to No Response from
UEs in the
CELL_FACH State
(SRB RLC ERROR)
for Cell
73424126 VS.FailCellUpdt.E Number of Cell V900R014

rrTRB.NoReply.F Update Failures due
ACH to No Response from
UEs in the
CELL_FACH State
(TRB RLC ERROR)
for Cell
73424915 VS.AttCellUpdt.Ms Number of Cell V900R014

g Updates in a Cell
73424916 VS.AttCellUpdt.Ms Number of Cell V900R014

g.Conv Updates Triggered
by CS Service
Establishments in a
Cell
73424917 VS.CU.CONV.FC. Number of Cell V900R014

Num.CPU.OverLo Updates that Are
ad Under CPU Usage-
Based Flow Control
and Are Triggered by
CS Service
Establishments in a
Cell

BSC6900 UMTS

Description
73424918 VS.CU.CONV.FC. Number of Cell V900R014

Num.RRCQueue Updates that Are
Under RRC
Queuing-Based
Flow Control and
Are Triggered by CS
Service
Establishments in a
Cell
73424919 VS.CU.FC.Num.R Number of Cell V900R014

RCQueue Updates that Are
Under RRC
Queuing-Based
Flow Control in a
Cell
73426327 VS.AttCellUpdt.Or Number of Cell V900R015

gConvCall.PCH Update Attempts for
Cell (Originating
Conversational Call)
73426328 VS.AttCellUpdt.T Number of Cell V900R015

mConvCall.PCH Update Attempts for
Cell (Terminating
73426329 VS.AttCellUpdt.E Number of Cell V900R015

mgCall.PCH Update Attempts for
Cell (Emergency
Call)
73426330 VS.SuccCellUpdt. Number of V900R015

OrgConvCall.PCH Successful Cell
Updates for Cell
(Originating
73426331 VS.SuccCellUpdt.T Number of V900R015

mConvCall.PCH Successful Cell
Updates for Cell
(Terminating
73426332 VS.SuccCellUpdt.E Number of V900R015

mgCall.PCH Successful Cell
Updates for Cell
(Emergency Call)

BSC6900 UMTS

Description
73426363 VS.P2F.Redir.Out Number of Outgoing V900R015

P2F Redirections for
Cell
73426364 VS.P2F.Redir.In.U Number of Incoming V900R015

seNewCU P2F Redirections for
Cell (Cell Update)
73426365 VS.P2F.Redir.Fail Number of P2F V900R015

Out.NonTargetFC Redirection Failures
N Caused by UE Not
Accessing the Target
Frequency for Cell
73426366 VS.P2F.Redir.Fail Number of P2F V900R015

Out.NoReply Redirection Failures
Caused by UE No
Response for Cell
None
1.12.6.1 Number of Unsuccessful Cell Updates due to RL Failure (No Response)
Counters
67189768 VS.FailCellUpdt.RLFail.No Number of Failed Cell

Reply Updates Due to No Response
from UE for Cell (Cell
Update Caused by RL
Failure)
Description
This counter provides the number of times that a cell update triggered by "radio link failure"
fails due to UE no response.
Measurement point
The measurement is triggered at point A in Figure 1. After receiving a CELL UPDATE message
carrying a cause value of "radio link failure" from the UE, the RNC sends a CELL UPDATE
CONFIRM message to the UE and starts a timer to wait for a response message from the UE

BSC6900 UMTS
(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-397 Cell update procedure (failed operation due to timer expiry)
Formula
None
Unit
None
Related Features
VS.FailCellUpdt.RLFail.No WRFD-010801 Intra RNC Cell Update

Reply WRFD-010802 Inter RNC Cell Update
1.12.6.2 Number of Confirmation Messages from SRNC

BSC6900 UMTS
Counters
67180370 VS.CellUpdt.Confirm Number of CELL UPDATE

CONFIRM Messages from
SRNC for Cell
Description
This measurement item provides the number of CELL UPDATE CONFIRM messages sent from
the SRNC to the UE in a cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the SRNC sends a CELL
UPDATE CONFIRM message to the UE. In this case, the RNC measures the item in the cell
that the UE has selected during the cell update procedure. Note that the measurement is not
triggered for a CELL UPDATE CONFIRM message that is retransmitted by the RNC.
Figure 1-398 Cell update procedure
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.CellUpdt.Confirm WRFD-010801 Intra RNC Cell Update

WRFD-010802 Inter RNC Cell Update
1.12.6.3 Number of Cell Update Attempts for Different Causes
Counters
67180372 VS.AttCellUpdt.Prd Number of Periodical Cell

Updates for Cell
67180378 VS.AttCellUpdt.RLFail Number of Cell Updates Due

to Radio Link Failure for Cell
67192569 VS.AttCellUpdt Number of Cell Updates for

Cell
67192570 VS.AttCellUpdt.ErrSRB Number of Cell Updates Due

to SRB RLC Unrecoverable
Error for Cell
67192571 VS.AttCellUpdt.ErrTRB Number of Cell Updates Due

to TRB RLC Unrecoverable
Error for Cell
67192573 VS.AttCellUpdt.MbmsRecv Number of Cell Updates Due

to MBMS Reception for Cell
67192575 VS.AttCellUpdt.MbmsPtpR Number of Cell Updates Due

bReq to MBMS PtP RB Request
for Cell
67180373 VS.AttCellUpdt.Resel Number of Cell Updates Due

to Cell Reselection for Cell
67180374 VS.AttCellUpdt.RSA Number of Cell Updates Due

to Re-Entering Service Area
for Cell
67180375 VS.AttCellUpdt.PageRsp Number of Cell Updates Due

to Paging Response for Cell

BSC6900 UMTS
67180376 VS.AttCellUpdt.ULData- Number of Cell Updates Due

Trans to Uplink Data Transmission
for Cell
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

BSC6900 UMTS
Unit
None
Related Features
VS.AttCellUpdt.Prd WRFD-010801 Intra RNC Cell Update

VS.AttCellUpdt.RLFail WRFD-010801 Intra RNC Cell Update

VS.AttCellUpdt WRFD-010801 Intra RNC Cell Update

VS.AttCellUpdt.ErrSRB WRFD-010801 Intra RNC Cell Update

VS.AttCellUpdt.ErrTRB WRFD-010801 Intra RNC Cell Update

VS.AttCellUpdt.MbmsRecv WRFD-010801 Intra RNC Cell Update

WRFD-010616 MBMS Introduction
Package
VS.AttCellUpdt.MbmsPtpR WRFD-010801 Intra RNC Cell Update

bReq WRFD-010802 Inter RNC Cell Update
Package
VS.AttCellUpdt.Resel WRFD-010801 Intra RNC Cell Update

VS.AttCellUpdt.RSA WRFD-010801 Intra RNC Cell Update

VS.AttCellUpdt.PageRsp WRFD-010801 Intra RNC Cell Update

VS.AttCellUpdt.ULData- WRFD-010801 Intra RNC Cell Update

Trans WRFD-010802 Inter RNC Cell Update
1.12.6.4 Number of Successful Cell Updates for Different Causes

BSC6900 UMTS
Counters
67180371 VS.SuccCellUpdt Number of Successful Cell

Updates for Cell
67189767 VS.SuccCellUpdt.RLFail Number of Successful Cell

Updates Due to Radio Link
Failure for Cell
67192572 VS.SuccCellUpdt.ErrTRB Number of Successful Cell

Updates Due to TRB RLC
Unrecoverable Error for Cell
67192574 VS.SuccCellUpdt.MbmsRec Number of Successful Cell

v Updates Due to MBMS
Reception for Cell
67192576 VS.SuccCellUpdt.MbmsPtp Number of Successful Cell

RbReq Updates Due to MBMS PtP
RB Request for Cell
67180379 VS.SuccCellUpdt.Prd Number of Successful

Periodical Cell Updates for
Cell
67180380 VS.SuccCellUpdt.Resel Number of Successful Cell

Updates Due to Cell
67180381 VS.SuccCellUpdt.Rsa Number of Successful Cell

Updates Due to Re-Entering
Service Area for Cell
67180382 VS.SuccCellUpdt.PageRsp Number of Successful Cell

Updates Due to Paging
Response for Cell
67180383 VS.SuccCellUpdt.ULData- Number of Successful Cell

Trans Updates Due to Uplink Data
Transmission for Cell
73423781 VS.SuccCellUpdt.ErrSRB Number of Successful Cell

Updates Due to SRB RLC
Unrecoverable Error for Cell
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.

BSC6900 UMTS
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.
Figure 1-400 Basic cell update procedure
In a cell update requiring UE response, the RNC determines that the cell update is successful
upon receiving the response message from the UE after sending a CELL UPDATE CONFIRM
message to the UE. In this procedure, the measurement is triggered after the RNC receives a
response message (such as the PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message) from the UE based on the cause value, as shown by point C in the following figure.
The corresponding counter is measured in the cell that is selected by the UE for cell update.
The UE may respond with one of the following messages after receiving a CELL UPDATE
CONFIRM message:
UTRAN MOBILITY INFORMATION CONFIRM
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RELEASE COMPLETE.

BSC6900 UMTS
Figure 1-401 Cell update procedure with physical channel reconfiguration
After the RNC receives a cell update message, if the RNC directly performs the RRC connection
release procedure rather than performs a cell update, the counter is measured at point B, as shown
in the following figure. For example, for cell updates due to SRB RLC unrecoverable errors,
when the SRB reestablishment algorithm is disabled, the counter is measured after the RNC
performs the RRC connection release procedure.
Figure 1-402 Basic cell update procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SuccCellUpdt WRFD-010801 Intra RNC Cell Update

VS.SuccCellUpdt.RLFail WRFD-010801 Intra RNC Cell Update

VS.SuccCellUpdt.ErrTRB WRFD-010801 Intra RNC Cell Update

VS.SuccCellUpdt.MbmsRec WRFD-010801 Intra RNC Cell Update

v WRFD-010802 Inter RNC Cell Update
Package
VS.SuccCellUpdt.MbmsPtp WRFD-010801 Intra RNC Cell Update

RbReq WRFD-010802 Inter RNC Cell Update
Package
VS.SuccCellUpdt.Prd WRFD-010801 Intra RNC Cell Update

VS.SuccCellUpdt.Resel WRFD-010801 Intra RNC Cell Update

VS.SuccCellUpdt.Rsa WRFD-010801 Intra RNC Cell Update

VS.SuccCellUpdt.PageRsp WRFD-010801 Intra RNC Cell Update

VS.SuccCellUpdt.ULData- WRFD-010801 Intra RNC Cell Update

Trans WRFD-010802 Inter RNC Cell Update
VS.SuccCellUpdt.ErrSRB WRFD-010801 Intra RNC Cell Update


BSC6900 UMTS
1.12.6.5 Number of RRC Connection Releases due to Cell Update Failure
Counters
67180386 VS.CellUpdt.RRCRel Number of RRC Connection

Releases Due to Cell Update
Failure for Cell
Description
This counter provides the number of RRC connection releases due to cell update failures.
Measurement point
The measurement is triggered at point A in the following figure. If the cell update fails and
therefore the RRC connection needs to be released, the RNC sends an RRC CONNECTION
RELEASE message to the UE and measures this counter in the cell that is selected by the UE
for cell update.
Figure 1-403 RRC connection release procedure triggered by cell update
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.CellUpdt.RRCRel WRFD-010801 Intra RNC Cell Update

WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release
1.12.6.6 Number of Cell Update Failures due to No Response from UEs in the
CELL_FACH State for Cell
Counters
73424125 VS.FailCellUpdt.ErrSRB.N Number of Cell Update

oReply.FACH Failures due to No Response
from UEs in the
CELL_FACH State (SRB
RLC ERROR) for Cell
73424126 VS.FailCellUpdt.ErrTRB.N Number of Cell Update

oReply.FACH Failures due to No Response
from UEs in the
CELL_FACH State (TRB
RLC ERROR)for Cell
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

BSC6900 UMTS
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-404 Cell update procedure (failed operation due to timer expiry)
Formula
None
Unit
None
Related Features
VS.FailCellUpdt.ErrSRB.N WRFD-010801 Intra RNC Cell Update

oReply.FACH WRFD-010802 Inter RNC Cell Update
VS.FailCellUpdt.ErrTRB.N WRFD-010801 Intra RNC Cell Update

oReply.FACH WRFD-010802 Inter RNC Cell Update
1.12.6.7 Number of Cell Updates in a Cell

BSC6900 UMTS
Counters
73424915 VS.AttCellUpdt.Msg Number of Cell Updates in a

Cell
Description
This counter provides the total number of CELL UPDATE messages received in a cell. In
addition, This counter also include those CELL UPDATE messages that are re-sent by UE.
Measurement point
This counter provides the total number of CELL UPDATE messages received in a cell. This
counter is counted When the RNC receives a CELL UPDATE message which UE is in
CELL_PCH/URA_PCH state.
Formula
None
Unit
None
Related Features
VS.AttCellUpdt.Msg WRFD-040100 Flow Control
1.12.6.8 Number of Cell Updates Triggered by CS Service Establishments in a Cell
Counters
73424916 VS.AttCellUpdt.Msg.Conv Number of Cell Updates

Triggered by CS Service
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

BSC6900 UMTS
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
VS.AttCellUpdt.Msg.Conv WRFD-040100 Flow Control
1.12.6.9 Number of Cell Updates that Are Under CPU Usage-Based Flow Control
and Are Triggered by CS Service Establishments in a Cell
Counters
73424917 VS.CU.CONV.FC.Num.CP Number of Cell Updates that

U.OverLoad Are Under CPU Usage-
Based Flow Control and Are
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

BSC6900 UMTS
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
VS.CU.CONV.FC.Num.CP WRFD-040100 Flow Control

U.OverLoad
1.12.6.10 Number of Cell Updates that Are Under RRC Queuing-Based Flow
Control and Are Triggered by CS Service Establishments in a Cell
Counters
73424918 VS.CU.CONV.FC.Num.RR Number of Cell Updates that

CQueue Are Under RRC Queuing-
Based Flow Control and Are
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
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.CU.CONV.FC.Num.RR WRFD-040100 Flow Control

CQueue
1.12.6.11 Number of Cell Updates that Are Under RRC Queuing-Based Flow
Control in a Cell
Counters
73424919 VS.CU.FC.Num.RRCQueue Number of Cell Updates that

Are Under RRC Queuing-
Based Flow Control in a Cell
Description
This counter provides the number of CELL UPDATE messages received in a cell which is Under
Flow Control Triggered by RRC Queue. The CELL UPDATE or URA UPDATE messages are
Flow Controled when the UE is in CELL_PCH/URA_PCH state. In addition, The counter also
include those CELL UPDATE or URA UPDATE messages that are re-sent by UE.
Measurement point
This counter provides the number of CELL UPDATE or URA UPDATE messages received in
a cell which is Under Flow Control Triggered by RRC Queue. (1)If the cell is Under Flow Control
Triggered by RRC Queue, This counter will be counted When this cell receives a CELL
UPDATE message from the UE in CELL_PCH/URA_PCH state. (2)If the cell is Under Flow
Control Triggered by RRC Queue, This counter will be counted When this cell receives a URA
UPDATE message from the UE in URA_PCH state.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.CU.FC.Num.RRCQueue WRFD-040100 Flow Control
1.12.6.12 Number of Cell Update Attempts for Cell (Originating Conversational

Call)
Counters
73426327 VS.AttCellUpdt.OrgConvCa Number of Cell Update

ll.PCH Attempts for Cell
(Originating Conversational
Call)
73426328 VS.AttCellUpdt.TmConvCa Number of Cell Update

ll.PCH Attempts for Cell
(Terminating Conversational
Call)
73426329 VS.AttCellUpdt.EmgCall.P Number of Cell Update

CH Attempts for Cell
(Emergency Call)
Description
These counters measure the number of cell update attempts made by UEs in the CELL_PCH or
URA_PCH state to establish new services in a cell. These counters are measured based on the
specific causes of cell update attempts.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives a CELL
UPDATE message with the cause value "uplink data transmission" or "paging response" from
a UE in the CELL_PCH or URA_PCH state, the RNC calculates the numbers of cell update
attempts based on the cause values. The retransmitted CELL UPDATE messages are not
calculated into these counters.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.AttCellUpdt.OrgConvCa WRFD-010801 Intra RNC Cell Update

ll.PCH WRFD-010802 Inter RNC Cell Update
VS.AttCellUpdt.TmConvCa WRFD-010801 Intra RNC Cell Update

ll.PCH WRFD-010802 Inter RNC Cell Update
VS.AttCellUpdt.EmgCall.P WRFD-010801 Intra RNC Cell Update

CH WRFD-010802 Inter RNC Cell Update
1.12.6.13 Number of Successful Cell Updates for Cell (Originating Conversational

Call)

BSC6900 UMTS
Counters
73426330 VS.SuccCellUpdt.OrgConv Number of Successful Cell

Call.PCH Updates for Cell (Originating
73426331 VS.SuccCellUpdt.TmConv Number of Successful Cell

Call.PCH Updates for Cell
(Terminating Conversational
Call)
73426332 VS.SuccCellUpdt.EmgCall. Number of Successful Cell

PCH Updates for Cell (Emergency
Call)
Description
These counters measure the number of cell update attempts made by UEs in the CELL_PCH or
URA_PCH state to establish new services in a cell. These counters are measured based on the
specific causes of cell update attempts.
Measurement point
When receiving a CELL UPDATE message with the cause value "uplink data transmission" or
"paging response" from a UE in the CELL_PCH or URA_PCH state, the RNC returns a CELL
UPDATE CONFIRM message. If the RNC receives a response from the UE, the RNC considers
the cell update procedure successful. The measurement is triggered at point C, as shown in the
figure (The PHYSICAL CHANNEL RECONFIGURATION COMPLETE message in the
figure is used as an example). On receiving the response from the UE, the RNC calculates the
number of successful cell updates based on the cause values in the CELL UPDATE message.
On receiving the CELL UPDATE CONFIRM message, the UE returns one of the following
messages based on the IE carried in the CELL UPDATE CONFIRM message: UTRAN
MOBILITY INFORMATION CONFIRM PHYSICAL CHANNEL RECONFIGURATION
COMPLETE TRANSPORT CHANNEL RECONFIGURATION COMPLETE RADIO
BEARER RECONFIGURATION COMPLETE RADIO BEARER RELEASE COMPLETE

BSC6900 UMTS
Figure 1-406 Cell update procedure with physical channel reconfiguration
Formula
None
Unit
None
Related Features
VS.SuccCellUpdt.OrgConv WRFD-010801 Intra RNC Cell Update

Call.PCH WRFD-010802 Inter RNC Cell Update
VS.SuccCellUpdt.TmConv WRFD-010801 Intra RNC Cell Update

Call.PCH WRFD-010802 Inter RNC Cell Update
VS.SuccCellUpdt.EmgCall. WRFD-010801 Intra RNC Cell Update

PCH WRFD-010802 Inter RNC Cell Update
1.12.6.14 Number of Outgoing P2F Redirections for Cell

BSC6900 UMTS
Counters
73426363 VS.P2F.Redir.Out Number of Outgoing P2F

Redirections for Cell
Description
This counter measures the number of outgoing redirections triggered by state transitions from
CELL_PCH or URA_PCH to CELL_FACH in a cell. This counter is measured in the source
cell and excludes the CELL UPDATE CONFIRM messages retransmitted by the RNC.
Measurement point
The measurement is triggered at point A, as shown in figure. The RNC receives a CELL
a UE in the CELL_PCH or URA_PCH state, and sends a CELL UPDATE CONFIRM message
to the UE, instructing the UE to perform a P2F redirection. In this case, this counter is increased
by one in the source cell. The retransmitted CELL UPDATE CONFIRM messages are not
calculated into this counter.
Figure 1-407 Cell update P2F redirection procedure
The measurement is triggered at point A, as shown in figure. The RNC receives a CELL
to the UE, instructing the UE to perform a P2F redirection. In this case, this counter is increased
by one in the source cell. The retransmitted CELL UPDATE CONFIRM messages are not
calculated into this counter.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.P2F.Redir.Out WRFD-150246 Service Steering and Load

Sharing in CELL_FACH
State
1.12.6.15 Number of Incoming P2F Redirections for Cell (Cell Update)

BSC6900 UMTS
Counters
73426364 VS.P2F.Redir.In.UseNew- Number of Incoming P2F

CU Redirections for Cell (Cell
Update)
Description
This counter measures the number of incoming redirections triggered by state transitions from
CELL_PCH or URA_PCH to CELL_FACH in the target cell for the redirection.
Measurement point
The measurement is triggered at point B, as shown in figure. The RNC receives a CELL
to the UE, instructing the UE to perform a P2F redirection. If the RNC receives a cell update
request on the target frequency for the redirection, this counter is increased by one in the target
cell.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.P2F.Redir.In.UseNew- WRFD-150246 Service Steering and Load

CU Sharing in CELL_FACH
State
1.12.6.16 Number of P2F Redirection Failures Caused by UE Not Accessing the

Target Frequency for Cell
Counters
73426365 VS.P2F.Redir.FailOut.Non- Number of P2F Redirection

TargetFCN Failures Caused by UE Not
Accessing the Target
Frequency for Cell
Description
This counter measures the number of redirection failures caused by UE not accessing the target
frequency for the redirection. The redirection must be triggered by state transitions from
CELL_PCH or URA_PCH to CELL_FACH. This counter is measured in the source cell.
Measurement point
to the UE, instructing the UE to perform a P2F redirection. If the RNC receives a cell update
request on a frequency other than the target frequency for the redirection, this counter is increased
by one in the source cell.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.P2F.Redir.FailOut.Non- WRFD-150246 Service Steering and Load

TargetFCN Sharing in CELL_FACH
State
1.12.6.17 Number of P2F Redirection Failures Caused by UE No Response for Cell

BSC6900 UMTS
Counters
73426366 VS.P2F.Redir.FailOut.NoRe Number of P2F Redirection

ply Failures Caused by UE No
Response for Cell
Description
This counter measures the number of redirection failures caused by UE no response. The
redirection must be triggered by state transitions from CELL_PCH or URA_PCH to
CELL_FACH. This counter is measured in the source cell.
Measurement point
to the UE, instructing the UE to perform a P2F redirection. If the RNC does not receive a
PHYSICAL CHANNEL RECONFIGURATION COMPLETE or CELL UPDATE message
from the UE before the timer expires, this counter is increased by one in the source cell.

BSC6900 UMTS
to the UE, instructing the UE to perform a P2F redirection. If the RNC does not receive a
PHYSICAL CHANNEL RECONFIGURATION COMPLETE or CELL UPDATE message
from the UE before the timer expires, this counter is increased by one in the source cell.
Formula
None
Unit
None
Related Features
VS.P2F.Redir.FailOut.NoRe WRFD-150246 Service Steering and Load

ply Sharing in CELL_FACH
State

BSC6900 UMTS
1.12.7 Measurement of Compressed Mode per cell(CM.Cell)
Overview
This function subset is used to measure the number of Compressed Mode Activation Attempts
and the number of Compressed Mode Activation fails.
Counters
Description
67194881 VS.CM.ULSF2.Act Number of Uplink Earlier than

.Att SF-2 Compression V900R011
Mode Activation
Requests for Cell
67194882 VS.CM.ULHLS.Ac Number of Uplink Earlier than

t.Att HLS Compression V900R011
Mode Activation
Requests for Cell
67194883 VS.CM.ULSF2.Act Number of Uplink Earlier than

.Fail SF-2 Compression V900R011
Mode Activation
Failures for Cell
67194884 VS.CM.ULHLS.Ac Number of Uplink Earlier than

t.Fail HLS Compression V900R011
Mode Activation
Failures for Cell
67194885 VS.CM.DLSF2.Act Number of Downlink Earlier than

.Att SF-2 Compression V900R011
Mode Activation
Requests for Cell
67194886 VS.CM.DLHLS.Ac Number of Downlink Earlier than

t.Att HLS Compression V900R011
Mode Activation
Requests for Cell
67194887 VS.CM.DLSF2.Act Number of Downlink Earlier than

.Fail SF-2 Compression V900R011
Mode Activation
Failures for Cell
67194888 VS.CM.DLHLS.Ac Number of Downlink Earlier than

t.Fail HLS Compression V900R011
Mode Activation
Failures for Cell

BSC6900 UMTS
None
1.12.7.1 Number of Up Link SF-2 Compressed Mode Activation Attempts
Counters
67194881 VS.CM.ULSF2.Act.Att Number of Uplink SF-2

Compression Mode
Activation Requests for Cell
Description
This measurement item provides the number of Up Link SF-2 Compressed Mode Activation
Attempts in a cell.
Measurement point
the UE a MEASUREMENT CONTROL message, the RNC measures the counter if the SF/2
compressed mode is used in the uplink.
Figure 1-413 Flow chart of Measurement of Compressed Mode
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.CM.ULSF2.Act.Att WRFD-020302 Inter Frequency Hard

Coverage
1.12.7.2 Number of Up Link HLS Compressed Mode Activation Attempts
Counters
67194882 VS.CM.ULHLS.Act.Att Number of Uplink HLS

Compression Mode
Description
This measurement item provides the number of Up Link HLS Compressed Mode Activation
Attempts in a cell.
Measurement point
the UE a MEASUREMENT CONTROL message, the RNC measures the counter if the high
layer scheduling (HLS) compressed mode is used in the uplink.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.CM.ULHLS.Act.Att WRFD-020302 Inter Frequency Hard

Coverage
1.12.7.3 Number of Up Link SF-2 Compressed Mode Activation Fails
Counters
67194883 VS.CM.ULSF2.Act.Fail Number of Uplink SF-2

Compression Mode
Activation Failures for Cell
Description
This measurement item provides the number of Up Link SF-2 Compressed Mode Activation
Fails in a cell.
Measurement point
The measurement is triggered at point C as shown in the following figure. When the RNC
receives a MEASUREMENT CONTROL FAILURE message related to the Up Link SF/2
compressed mode from the UE or does not receive the ACK message for MEASUREMENT
CONTROL, it measures the counter.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.CM.ULSF2.Act.Fail WRFD-020302 Inter Frequency Hard

Coverage
1.12.7.4 Number of Up Link HLS Compressed Mode Activation Fails
Counters
67194884 VS.CM.ULHLS.Act.Fail Number of Uplink HLS

Compression Mode

BSC6900 UMTS
Description
This measurement item provides the number of Up Link HLS Compressed Mode Activation
Fails in a cell.
Measurement point
receives a MEASUREMENT CONTROL FAILURE message related to the Up Link HLS
Formula
None
Unit
None
Related Features
VS.CM.ULHLS.Act.Fail WRFD-020302 Inter Frequency Hard

Coverage
1.12.7.5 Number of Down Link SF-2 Compressed Mode Activation Attempts

BSC6900 UMTS
Counters
67194885 VS.CM.DLSF2.Act.Att Number of Downlink SF-2

Compression Mode
Description
This measurement item provides the number of Down Link SF-2 Compressed Mode Activation
Attempts in a cell.
Measurement point
the UE a MEASUREMENT CONTROL message, the RNC measures the counter if the SF/2
compressed mode is used in the downlink.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.CM.DLSF2.Act.Att WRFD-020302 Inter Frequency Hard

Coverage
1.12.7.6 Number of Down Link HLS Compressed Mode Activation Attempts
Counters
67194886 VS.CM.DLHLS.Act.Att Number of Downlink HLS

Compression Mode
Description
This measurement item provides the number of Down Link HLS Compressed Mode Activation
Attempts in a cell.
Measurement point
the UE a MEASUREMENT CONTROL message, the RNC measures the counter if the HLS
compressed mode is used in the downlink.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.CM.DLHLS.Act.Att WRFD-020302 Inter Frequency Hard

Coverage
1.12.7.7 Number of Down Link SF-2 Compressed Mode Activation Fails
Counters
67194887 VS.CM.DLSF2.Act.Fail Number of Downlink SF-2

Compression Mode
Description
This measurement item provides the number of Down Link SF-2 Compressed Mode Activation
Fails in a cell.
Measurement point
receives a MEASUREMENT CONTROL FAILURE message related to the Down Link SF/2

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.CM.DLSF2.Act.Fail WRFD-020302 Inter Frequency Hard

Coverage
1.12.7.8 Number of Down Link HLS Compressed Mode Activation Fails
Counters
67194888 VS.CM.DLHLS.Act.Fail Number of Downlink HLS

Compression Mode

BSC6900 UMTS
Description
This measurement item provides the number of Down Link HLS Compressed Mode Activation
Fails in a cell.
Measurement point
receives a MEASUREMENT CONTROL FAILURE message related to the Down Link HLS
Formula
None
Unit
None
Related Features
VS.CM.DLHLS.Act.Fail WRFD-020302 Inter Frequency Hard

Coverage

BSC6900 UMTS
1.12.8 EFACH Measurement per cell(EFACH.Cell)
Overview
UEs in the E-FACH state are those in the CELL_FACH state and use the HS-DSCH for downlink
transmission.
EFACH refers to the status that the UE uplink is established on the RACH and the UE downlink
is established on the HSDSCH. This technology can increase CELL_FACH user downlink data
peak rate and shorten state transfer delay time. The function subset EFACH Measurement (Cell)
is used to measure this technology related services on the basis of Cell.
Counters
Description

stab.EFACH Establishment V900R011
Requests on EFACH
for Cell

Estab.EFACH Successful RRC V900R011
Establishments on
EFACH for Cell
67193119 VS.RAB.AttEstPS. Number of PS RAB Earlier than

EFACH Establishment V900R011
Requests on EFACH
for Cell
67193120 VS.RAB.SuccEstP Number of Earlier than

S.EFACH Successful PS RAB V900R011
Establishments on
EFACH for Cell
67193121 VS.RAB.Estab.PS. Maximum Duration Earlier than

CellFACH.MaxTi of PS RAB V900R011
me Establishment
Process on FACH for
Cell
67204169 VS.RAB.Estab.PS. Mean Duration of PS Earlier than

CellFACH.Mean- RAB Establishment V900R011
Time Process on FACH for
Cell

el.PS.EFACH Abnormal RAB V900R011
Releases on EFACH
for Cell

BSC6900 UMTS

Description
67193128 VS.RAB.NormRel. Number of Normal Earlier than

PS.EFACH PS RAB Release on V900R011
EFACH for Cell
67204778 VS.CRNCIubBytes Number of Bytes of Earlier than

EFACH.Tx MAC PDUs Sent on V900R011
IUB EFACH FP for
Cell
73410512 VS.EFACHUEs Number of UEs Earlier than

carried on EFACH V900R011
for Cell
73421757 VS.RRC.ConnEsta Maximum Duration V900R012

bTimeMax.CellFA of RRC
CH.EFACH Establishment
Process on EFACH
for Cell
73439900 VS.RRC.ConnEsta Mean Duration of V900R012

bTimeMean.CellF RRC Establishment
ACH.EFACH Process on EFACH
for Cell
73441122 VS.EDRXUEs Number of UEs V900R013

Carried on the
EFACH and Using
E-DRX
73426149 VS.EFACH.F2D.At Number of Attempts V900R015

t at State Transitions
from Enhanced
CELL_FACH to
CELL_DCH (DCH)
for Cell
73426150 VS.EFACH.D2F.At Number of Attempts V900R015

from CELL_DCH
(DCH) to Enhanced
CELL_FACH for
Cell
73426151 VS.EFACH.F2D.S Number of V900R015

ucc Successful State
Transitions from
Enhanced
CELL_FACH to
CELL_DCH (DCH)
for Cell

BSC6900 UMTS

Description
73426152 VS.EFACH.D2F.S Number of V900R015

Transitions from
CELL_DCH (DCH)
to Enhanced
CELL_FACH for
Cell
73426153 VS.EFACH.H2F.S Number of V900R015

Transitions from
CELL_DCH (HS-
DSCH) to Enhanced
CELL_FACH for
Cell
73426154 VS.EFACH.F2H.S Number of V900R015

Transitions from
Enhanced
CELL_FACH to
CELL_DCH (HS-
DSCH) for Cell
73426155 VS.EFACH.F2H.A Number of Attempts V900R015

tt at State Transitions
from Enhanced
CELL_FACH to
CELL_DCH (HS-
DSCH) for Cell
73426156 VS.EFACH.H2F.A Number of Attempts V900R015

from CELL_DCH
(HS-DSCH) to
Enhanced
CELL_FACH for
Cell
73426160 VS.EFACH.P2F.Su Number of V900R015

cc Successful State
Transitions from
CELL_PCH or
URA_PCH to
Enhanced
CELL_FACH for
Cell

BSC6900 UMTS

Description
73426159 VS.EFACH.P2F.At Number of Attempts V900R015

from CELL_PCH or
URA_PCH to
Enhanced
CELL_FACH for
Cell
73426158 VS.EFACH.F2P.Su Number of V900R015

cc Successful State
Transitions from
Enhanced
CELL_FACH to
CELL_PCH or
URA_PCH for Cell
73426157 VS.EFACH.F2P.At Number of Attempts V900R015

from Enhanced
CELL_FACH to
CELL_PCH or
URA_PCH for Cell
73426171 VS.EFACHUEs.M Maximum Number V900R015

ax of UEs on E_FACH
for Cell
Counter Sub Counter
VS.EFACHUEs VS.EDRXUEs
1.12.8.1 Number of RRC Connection Requests in a Cell (EFACH)
Counters
67193111 VS.RRC.AttConnEstab.EF Number of RRC

ACH Establishment Requests on
EFACH for Cell

BSC6900 UMTS
Description
This measurement item provides the number of requests for the RRC connection that the RNC
decides to set up on the EFACH in a cell after the RNC receives a RRC CONNECTION
REQUEST message from the UE.
Measurement point
The measurement is triggered at point A, as shown in the figure. After the RNC receives a RRC
CONNECTION REQUEST message from the UE, it assigns the basic channel resources for the
UE. If the RNC decides that the RRC signaling is established on the EFACH, it measures the
item in the cell on which the UE camps. The measurement is triggered for only once if the RNC
repeatedly receives the RRC CONNECTION REQUEST message from the UE.
Figure 1-421 RRC connection setup success flow
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RRC.AttConnEstab.EF WRFD-010688 Downlink Enhanced

ACH CELL_FACH
1.12.8.2 Number of Successful RRC Connection Setups in a Cell (EFACH)
Counters
67193112 VS.RRC.SuccConnEstab.EF Number of Successful RRC

ACH Establishments on EFACH
for Cell
Description
This counter provides the number of successful RRC connection setups on the EFACH.
Success rate of RRC connection setups on the EFACH = VS.RRC.SuccConnEstab.EFACH/
VS.RRC.AttConnEstab.EFACH
Measurement point
The measurement is triggered at point C, as shown in the figure. After the RNC receives a RRC
CONNECTION SETUP COMPLETE message from the UE, it measures the item in the cell on
which the UE camps if the RRC signaling is established on the EFACH.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RRC.SuccConnEstab.EF WRFD-010688 Downlink Enhanced

ACH CELL_FACH
1.12.8.3 Number of PS RAB Setup Attempts on EFACH in a Cell
Counters
67193119 VS.RAB.AttEstPS.EFACH Number of PS RAB

Establishment Requests on
EFACH for Cell
Description
This counter provides the number of PS RAB setup attempts on the EFACH.
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives a RAB
ASSIGNMENT REQUEST message from the SGSN, it measures the item in the best cell on
which the UE camps when the PS service is established on the EFACH.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AttEstPS.EFACH WRFD-010688 Downlink Enhanced

CELL_FACH
1.12.8.4 Number of Successful PS RAB Setup on EFACH in a Cell
Counters
67193120 VS.RAB.SuccEstPS.EFAC Number of Successful PS

H RAB Establishments on
EFACH for Cell

BSC6900 UMTS
Description
This counter provides the number of successful PS RAB setups on the EFACH.
Success rate of PS RAB setups on the EFACH = VS.RAB.SuccEstPS.EFACH/

VS.RAB.AttEstPS.EFACH
Measurement point
The measurement is triggered at point B, as shown in Figure. When the RNC receives a RADIO
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

BSC6900 UMTS
Related Features
VS.RAB.SuccEstPS.EFAC WRFD-010688 Downlink Enhanced

H CELL_FACH
1.12.8.5 Signaling Delay of PS RAB Established on CCH in a Cell
Counters
67193121 VS.RAB.Estab.PS.CellFAC Maximum Duration of PS

H.MaxTime RAB Establishment Process
on FACH for Cell
67204169 VS.RAB.Estab.PS.CellFAC Mean Duration of PS RAB

H.MeanTime Establishment Process on
FACH for Cell
specific formulas.
67193123 VS.RAB.Estab.PS.CellFAC Accumulative Duration of PS

H.Cum RAB Establishment Process
on FACH for Cell
67193124 VS.RAB.Estab.PS.CellFAC Number of Samples of

H.Sample Accumulative Duration of PS
RAB Establishment Process
on FACH for Cell
Description
These counters provide the signaling delay of PS RAB setup of the UE in CELL_FACH status.
Measurement point
The measurement is triggered at points A and B, as shown in Figure: At point A, the RNC records
the time (T1) when it receives a RAB ASSIGNMENT REQUEST message and decides the PS
RAB is set up on the CCH. At point B, the RNC records the time (T2) when it sends a RAB
ASSIGNMENT RESPONSE message to the CN after receiving a RADIO BEARER SETUP
COMPLETE message. Suppose delta T represents the signaling delay of the RAB connection
setup. Then, delta T = T2 - T1 when the RRC connection is set up on the CCH.

BSC6900 UMTS
Formula
VS.RAB.Estab.PS.CellFACH.MeanTime = [VS.RAB.Estab.PS.CellFACH.Cum]/
[VS.RAB.Estab.PS.CellFACH.Sample]
Unit
ms
Related Features
VS.RAB.Estab.PS.CellFAC WRFD-010688 Downlink Enhanced

H.MaxTime CELL_FACH
VS.RAB.Estab.PS.CellFAC WRFD-010688 Downlink Enhanced

H.MeanTime CELL_FACH
1.12.8.6 Number of Abnormally Released PS RABs on the EFACH in a Cell

BSC6900 UMTS
Counters
67193127 VS.RAB.AbnormRel.PS.EF Number of Abnormal RAB

ACH Releases on EFACH for Cell
Description
This counter provides the number of abnormally released PS RABs on the EFACH.
Success rate of abnormally released RABs on EFACH = VS.RAB.AbnormRel.PS.EFACH/

VS.RAB.NormRel.PS.EFACH
Measurement point
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.

BSC6900 UMTS


BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.PS.EF WRFD-010688 Downlink Enhanced

ACH CELL_FACH
1.12.8.7 Number of Normal Released PS RABs on the EFACH in a Cell
Counters
67193128 VS.RAB.NormRel.PS.EFA Number of Normal PS RAB

CH Release on EFACH for Cell

BSC6900 UMTS
Description
This measurement item provides the number of normally released PS RABs on the EFACH in
the cell.
Measurement point
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.
Release" or "Successful Relocation","Network Optimization", or the RNC initiates the release
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.PS.EFA WRFD-010688 Downlink Enhanced

CH CELL_FACH
1.12.8.8 Number of Downlink MAC PDU Bytes on the EFACH over the Iub
Interface

BSC6900 UMTS
Counters
67204778 VS.CRNCIubBytesEFACH. Number of Bytes of MAC

Tx PDUs Sent on IUB EFACH
FP for Cell
Description
This measurement counter provides the number of downlink MAC PDU bytes sent by the CRNC
on the EFACH over the Iub interface in a cell (including signaling and service data but excluding
FP headers).
Measurement point
This counter is measured when the CRNC sends data on the EFACH over the Iub interface. In
a measurement period, the bytes of uplink MAC PDUs (including the signaling and service data
but not including the FP header) that are received by the CRNC on the EFACH over the Iub
interface are accumulated in a cell.
Formula
None
Unit
byte
Related Features
VS.CRNCIubBytesEFACH. WRFD-010688 Downlink Enhanced

Tx CELL_FACH
1.12.8.9 Signaling Delay of RRC Established on EFACH in a Cell
Counters
73421757 VS.RRC.ConnEstabTimeM Maximum Duration of RRC

ax.CellFACH.EFACH Establishment Process on
EFACH for Cell

BSC6900 UMTS
73439900 VS.RRC.ConnEstabTimeM Mean Duration of RRC

ean.CellFACH.EFACH Establishment Process on
EFACH for Cell
specific formulas.
73421758 VS.RRC.ConnEstabTime.C Accumulative Duration of

CH.HSDSCH.Cum RRC Establishment Process
on EFACH for Cell
73421759 VS.RRC.ConnEstabTime.C Number of Samples of

CH.HSDSCH.Sample Cumulative Duration of RRC
Establishment Process on
EFACH for Cell
Description
These counters provide the average and maximum durations of RRC signaling setups on the
EFACH in a cell.
Measurement point
As shown in the figure, when the RNC receives an RRC CONNECTION REQUEST message
at point A, it records the time T1. When the RNC receives an RRC CONNECTION SETUP
COMPLETE message at point C, it records the time T2. Assume that delta T is the duration of
RRC signaling setup on the EFACH in a cell, delta T = T2-T1. The RNC takes samples of the
durations of RRC signaling setups on the EFACH every 5 seconds. At the end of a measurement
period, the RNC obtains the average duration by dividing the accumulated number by the
sampling times. The maximum number in a measurement period is the maximum duration.

BSC6900 UMTS
Formula
VS.RRC.ConnEstabTimeMean.CellFACH.EFACH =
[VS.RRC.ConnEstabTime.CCH.HSDSCH.Cum]/
[VS.RRC.ConnEstabTime.CCH.HSDSCH.Sample]
Unit
ms
Related Features
VS.RRC.ConnEstabTimeM WRFD-010688 Downlink Enhanced

ax.CellFACH.EFACH CELL_FACH
VS.RRC.ConnEstabTimeM WRFD-010688 Downlink Enhanced

ean.CellFACH.EFACH CELL_FACH
1.12.8.10 Number of UEs Carried on the EFACH or Those Carried on the EFACH
and Using E-DRX

BSC6900 UMTS
Counters
73441122 VS.EDRXUEs Number of UEs Carried on

the EFACH and Using E-
DRX
73410512 VS.EFACHUEs Number of UEs carried on

EFACH for Cell
73426171 VS.EFACHUEs.Max Maximum Number of UEs

on E_FACH for Cell
Description
These counters provide the average number or maximum number of UEs that are carried on the
EFACH, and the average number of UEs that are carried on the EFACH and enabled with the
Enhanced Discontinuous Reception (E-DRX) function in a cell.
Measurement point
The number of UEs carried on the EFACH in a cell is sampled every 5 seconds. At the end of
a measurement period, the average number of UEs that are carried on the EFACH is calculated
by dividing the accumulated number of the UEs measured at each sampling point by the number
of samples. The maximum number of UEs that are carried on the EFACH measured at each
sampling point is the maximum value obtained in a measurement period. The number of UEs
carried on the EFACH and using the E-DRX function in a cell is sampled every 5 seconds. At
the end of a measurement period, the average number of UEs that are carried on the EFACH
and use the E-DRX function is calculated by dividing the accumulated number of the UEs
measured at each sampling point by the number of samples.
Formula
None
Unit
None
Related Features
VS.EDRXUEs WRFD-010702 Enhanced DRX
VS.EFACHUEs WRFD-010688 Downlink Enhanced

CELL_FACH
VS.EFACHUEs.Max WRFD-010688 Downlink Enhanced

CELL_FACH

BSC6900 UMTS
1.12.8.11 Number of Attempts at State Transitions from Enhanced CELL_FACH to

CELL_DCH (DCH) for Cell
Counters
73426149 VS.EFACH.F2D.Att Number of Attempts at State

Transitions from Enhanced
CELL_FACH to
73426150 VS.EFACH.D2F.Att Number of Attempts at State

Transitions from
CELL_DCH (DCH) to
Enhanced CELL_FACH for
Cell
Description
These counters provide the number of UE state transition attempts from enhanced CELL_FACH
(E-DCH) to CELL_DCH (DCH) and from CELL_DCH (DCH) to enhanced CELL_FACH (E-
DCH) in a cell. Enhanced CELL_FACH refers to that a UE in the CELL_FACH state uses the
HS-DSCH in the downlink.
Measurement point
RADIO BEARER RECONFIGURATION message during a state transition from CELL_DCH
(DCH) to enhanced CELL_FACH, this counter is measured in the best cell that the UE camps
on before the state transition. When the RNC sends the UE a RADIO BEARER
RECONFIGURATION message during a state transition from enhanced CELL_FACH to
CELL_DCH (DCH), this counter is measured in the cell that the UE currently camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.EFACH.F2D.Att WRFD-021101 Dynamic Channel

WRFD-010688 Configuration Control
(DCCC)
Downlink Enhanced
CELL_FACH
VS.EFACH.D2F.Att WRFD-021101 Dynamic Channel

(DCCC)
Downlink Enhanced
CELL_FACH
1.12.8.12 Number of Successful State Transitions from Enhanced CELL_FACH to

Counters
73426151 VS.EFACH.F2D.Succ Number of Successful State

CELL_FACH to
73426152 VS.EFACH.D2F.Succ Number of Successful State

Transitions from
CELL_DCH (DCH) to
Cell
Description
These counters provide the number of UE successful state transitions from enhanced
CELL_FACH to CELL_DCH (DCH) and state transitions from CELL_DCH (DCH) to

BSC6900 UMTS
enhanced CELL_FACH in a cell. Enhanced CELL_FACH refers to the state in which UEs stay
in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
the UE a RADIO BEARER RECONFIGURATION COMPLETE message during a state
transition from CELL_DCH (DCH) to enhanced CELL_FACH, this counter is measured in the
best cell that the UE camps on before the state transition. When the RNC receives the UE a
RADIO BEARER RECONFIGURATION COMPLETE message during a state transition from
enhanced CELL_FACH to CELL_DCH (DCH), this counter is measured in the cell that the UE
currently camps on.
Formula
None
Unit
None
Related Features
VS.EFACH.F2D.Succ WRFD-021101 Dynamic Channel

(DCCC)
Downlink Enhanced
CELL_FACH

BSC6900 UMTS
VS.EFACH.D2F.Succ WRFD-021101 Dynamic Channel

(DCCC)
Downlink Enhanced
CELL_FACH

CELL_DCH (HS-DSCH) for Cell
Counters
73426154 VS.EFACH.F2H.Succ Number of Successful State

CELL_FACH to
CELL_DCH (HS-DSCH) for
Cell
73426153 VS.EFACH.H2F.Succ Number of Successful State

Transitions from
CELL_DCH (HS-DSCH) to
Cell
Description
These counters provide the number of UE successful state transitions from enhanced
CELL_FACH to CELL_DCH (HS-DSCH) and state transitions from CELL_DCH (HS-DSCH)
to enhanced CELL_FACH in a cell. Enhanced CELL_FACH refers to the state in which UEs
stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
the UE a RADIO BEARER RECONFIGURATION COMPLETE message during a state
transition from CELL_DCH (HS-DSCH) to enhanced CELL_FACH, this counter is measured
in the best cell that the UE camps on before the state transition. When the RNC receives the UE
a RADIO BEARER RECONFIGURATION COMPLETE message during a state transition
from enhanced CELL_FACH to CELL_DCH (HS-DSCH), this counter is measured in the cell
that the UE currently camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.EFACH.F2H.Succ WRFD-01061111 HSDPA State Transition

WRFD-010688 Downlink Enhanced
CELL_FACH
VS.EFACH.H2F.Succ WRFD-01061111 HSDPA State Transition

CELL_FACH

CELL_DCH (HS-DSCH) for Cell

BSC6900 UMTS
Counters
73426155 VS.EFACH.F2H.Att Number of Attempts at State

CELL_FACH to
CELL_DCH (HS-DSCH) for
Cell
73426156 VS.EFACH.H2F.Att Number of Attempts at State

Transitions from
CELL_DCH (HS-DSCH) to
Cell
Description
These counters provide the number of UE attempts at state transitions from enhanced
CELL_FACH to CELL_DCH (HS-DSCH) and state transitions from CELL_DCH (HS-DSCH)
to enhanced CELL_FACH in a cell. Enhanced CELL_FACH refers to the state in which UEs
stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
RADIO BEARER RECONFIGURATION message during a state transition from CELL_DCH
(HS-DSCH) to enhanced CELL_FACH, this counter is measured in the best cell that the UE
camps on before the state transition. When the RNC sends the UE a RADIO BEARER
RECONFIGURATION message during a state transition from enhanced CELL_FACH to
CELL_DCH (HS-DSCH), this counter is measured in the cell that the UE currently camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.EFACH.F2H.Att WRFD-01061111 HSDPA State Transition

CELL_FACH
VS.EFACH.H2F.Att WRFD-01061111 HSDPA State Transition

CELL_FACH
1.12.8.15 Number of Successful State Transitions from CELL_PCH or URA_PCH to

Enhanced CELL_FACH for Cell
Counters
73426160 VS.EFACH.P2F.Succ Number of Successful State

Transitions from
Cell
Description
This counter provides the number of UE successful state transitions from CELL_PCH or
URA_PCH to enhanced CELL_FACH in a cell. Enhanced CELL_FACH refers to the state in
which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
When the RNC receives any of the following messages from a UE during a state transition from
CELL_PCH or URA_PCH to CELL_FACH, this counter is increased by one in the cell where
the UE sends the RNC a CELL UPDATE message: ? UTRAN MOBILITY INFORMATION
CONFIRM ? PHYSICAL CHANNEL RECONFIGURATION COMPLETE ? TRANSPORT
CHANNEL RECONFIGURATION COMPLETE ? RADIO BEARER RECONFIGURATION
COMPLETE The measurement is triggered at point C, as shown in the following figure.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.EFACH.P2F.Succ WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
Downlink Enhanced
CELL_FACH
1.12.8.16 Number of Attempts at State Transitions from CELL_PCH or URA_PCH

to Enhanced CELL_FACH for Cell

BSC6900 UMTS
Counters
73426159 VS.EFACH.P2F.Att Number of Attempts at State

Transitions from
Cell
Description
This counter provides the number of UE attempts at state transitions from CELL_PCH or
URA_PCH to enhanced CELL_FACH in a cell. Enhanced CELL_FACH refers to the state in
which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
When the RNC sends a UE a CELL UPDATE CONFIRM message during a state transition from
CELL_PCH or URA_PCH to enhanced CELL_FACH, this counter is increased by one in the
cell where the UE sends the RNC a CELL UPDATE message. The measurement is triggered at
point B, as shown in the following figure.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.EFACH.P2F.Att WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
Downlink Enhanced
CELL_FACH

CELL_PCH or URA_PCH for Cell
Counters
73426158 VS.EFACH.F2P.Succ Number of Successful State

CELL_FACH to
CELL_PCH or URA_PCH
for Cell
Description
This counter provides the number of UE successful state transitions from enhanced
CELL_FACH to CELL_PCH or URA_PCH in a cell. Enhanced CELL_FACH refers to the state
in which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
When the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message
from a UE during a state transition from enhanced CELL_FACH to CELL_PCH or URA_PCH,
this counter is increased by one in the serving cell where the UE camps. The measurement is
triggered at point B, as shown in the following figure.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.EFACH.F2P.Succ WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
Downlink Enhanced
CELL_FACH

CELL_PCH or URA_PCH for Cell
Counters
73426157 VS.EFACH.F2P.Att Number of Attempts at State

CELL_FACH to
CELL_PCH or URA_PCH
for Cell

BSC6900 UMTS
Description
This counter provides the number of UE attempts at state transitions from enhanced
CELL_FACH to CELL_PCH or URA_PCH in a cell. Enhanced CELL_FACH refers to the state
in which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink.
Measurement point
When the RNC sends a UE a RADIO BEARER RECONFIGURATION message during a state
transition from enhanced CELL_FACH to CELL_PCH or URA_PCH, this counter is increased
by one in the best cell where the UE camps. The measurement is triggered at point A, as shown
in the following figure.
Formula
None
Unit
None
Related Features
VS.EFACH.F2P.Att WRFD-010202 UE State in Connected Mode

URA-PCH, CELL-FACH)
Downlink Enhanced
CELL_FACH

BSC6900 UMTS
1.12.9 EPCH Measurement per cell(EPCH.Cell)
Overview
UEs in the E-PCH state are those in the CELL_PCH or URA_PCH state and use the HS-DSCH
for downlink transmission.
The EPCH feature is introduced in 3GPP R7. It allows the PCCH to be mapped to the HS-DSCH
for UEs in the CELL_PCH or URA_PCH state and therefore enables transmission on the 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.
Counters
Description
73441131 VS.EPCHUEs Average Number of V900R013

UEs Carried on the
EPCH for Cell
73441132 VS.EPCHUEs.DH Average Number of V900R013

RNTI UEs Carried on the
EPCH and Allocated
Dedicated H-RNTI
for Cell
Counter Sub Counter
VS.EPCHUEs VS.EPCHUEs.DHRNTI
1.12.9.1 Average Number of UEs Carried on the EPCH or Those Carried on the
EPCH and Allocated Dedicated H-RNTI for Cell
Counters
73441131 VS.EPCHUEs Average Number of UEs

Carried on the EPCH for Cell

BSC6900 UMTS
73441132 VS.EPCHUEs.DHRNTI Average Number of UEs

Carried on the EPCH and
Allocated Dedicated H-
RNTI for Cell
Description
These counters provide the average number of UEs in the CELL_PCH state and carried on E-
PCH and the average number of those carried on the E-PCH and allocated dedicated HS-DSCH
Radio Network Temporary Identifier (H-RNTI) in a cell.
Measurement point
The number of UEs in the CELL_PCH state and carried on the E-PCH is sampled every 5
seconds. At the end of a measurement period, this counter is calculated by dividing the
accumulated number of the UEs measured at each sampling point by the number of samples.
The number of UEs in the CELL_PCH state and carried on the E-PCH and allocated dedicated
H-RNTI are sampled every 5 seconds. At the end of a measurement period, this counter is
calculated by dividing the accumulated number of the UEs measured at each sampling point by
the number of samples.
Formula
None
Unit
None
Related Features
VS.EPCHUEs WRFD-020134 Push to Talk
VS.EPCHUEs.DHRNTI WRFD-020134 Push to Talk
1.12.10 ERACH Measurement per cell(ERACH.Cell)

Overview
In ERACH mode, UEs in CELL_FACH state use the E-DCH as the uplink transport channel
and use the HS-DSCH as the downlink transport channel.
The ERACH feature is introduced in R8. The E-DCH carries message data, replacing the
traditional RACH for a higher uplink peak rate. In this way, delay of UEs in the IDLE mode or

BSC6900 UMTS
in the CELL_FACH, CELL_PCH, or URA_PCH state on the user plane and control plane is
reduced and delay in transition from the CELL_FACH, CELL_PCH, or URA_PCH state to the
CELL_DCH state is reduced.
Counters
Description
73441118 VS.ERACHUEs Number of UEs V900R013

Carried on ERACH
for Cell
73423340 VS.RRC.AttConnE Number of Requests V900R013

stab.ERACH for Setting Up RRC
Connections on an
ERACH for Cell
73423341 VS.RRC.SuccConn Number of V900R013

Estab.ERACH Successful RRC
Connection Setups
on an ERACH for
Cell

S.ERACH Setup Requests on an
ERACH for Cell

PS.ERACH Successful PS RAB
Setups on an
ERACH for Cell
73423344 VS.RAB.NormRel. Number of PS RABs V900R013

PS.ERACH Normally Released
on an ERACH for
Cell

el.PS.ERACH Abnormally
Released on an
ERACH for Cell
73423346 VS.RRC.ConnEsta Maximum RRC V900R013

bTimeMax.ERAC Connection Setup
H Duration on an
ERACH for Cell
73441135 VS.RRC.ConnEsta Average RRC V900R013

bTimeMean.ERAC Connection Setup
H Duration on an
ERACH for Cell

BSC6900 UMTS

Description
73441170 VS.CRNCIubBytes Number of Bytes V900R013

ERACH.Rx over Iub ERACH for
Cell
73426161 VS.ERACH.E2F.S Number of V900R015

Transitions from
CELL_DCH (E-
DCH) to Enhanced
CELL_FACH (E-
DCH) for Cell
73426162 VS.ERACH.F2E.S Number of V900R015

Transitions from
Enhanced
CELL_FACH (E-
DCH) to
CELL_DCH (E-
DCH) for Cell
73426163 VS.ERACH.E2F.A Number of Attempts V900R015

from CELL_DCH
(E-DCH) to
Enhanced
CELL_FACH (E-
DCH) for Cell
73426164 VS.ERACH.F2E.A Number of Attempts V900R015

tt at State Transition
from Enhanced
CELL_FACH (E-
DCH) to
CELL_DCH (E-
DCH) for Cell
73426172 VS.ERACHUEs.M Maximum Number V900R015

ax of UEs on E_RACH
for Cell
None
1.12.10.1 Number of UEs Carried on ERACH for Cell

BSC6900 UMTS
Counters
73441118 VS.ERACHUEs Number of UEs Carried on

ERACH for Cell
73426172 VS.ERACHUEs.Max Maximum Number of UEs

on E_RACH for Cell
Description
These counters provide the average and maximum numbers of UEs that are carried on the
ERACH in a cell.
Measurement point
The RNC takes a sample from the number of UEs carried on the ERACH in a cell every 5s. At
the end of the measurement period, the RNC obtains the value of VS.ERACHUEs in the
measurement period by dividing the accumulated number of the UEs by the number of samples
and the RNC takes the maximum sampling number as the value of VS.ERACHUEs.Max.
Formula
None
Unit
None
Related Features
VS.ERACHUEs WRFD-010701 Uplink Enhanced

CELL_FACH
VS.ERACHUEs.Max WRFD-010701 Uplink Enhanced

CELL_FACH
1.12.10.2 Number of Requests for Setting Up RRC Connections on an ERACH for

Cell

BSC6900 UMTS
Counters
73423340 VS.RRC.AttConnEstab.ER Number of Requests for

ACH Setting Up RRC Connections
on an ERACH for Cell
Description
This counter provides the number of requests for setting up an RRC connection on the ERACH.
Measurement point
The measurement is triggered at point A shown in the following figure. After receiving an RRC
CONNECTION REQUEST message from a UE, the RNC allocates channel resources to the
RRC connection. If the RNC determines that the RRC signaling be setup on an ERACH, this
counter is measured in the cell where the UE camps. This counter is measured only once if the
RNC receives multiple RRC CONNECTION REQUEST messages repeatedly from a UE.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.RRC.AttConnEstab.ER WRFD-010701 Uplink Enhanced

ACH CELL_FACH
1.12.10.3 Number of Successful RRC Connection Setups on an ERACH for Cell
Counters
73423341 VS.RRC.SuccConnEstab.E Number of Successful RRC

RACH Connection Setups on an
ERACH for Cell
Description
This counter provides the number of times that an RRC connection is set up successfully on the
ERACH. Together with "Number of Requests for Setting Up RRC Connections on ERACHs
for Cell", this counter reflects the RRC setup success rate on the ERACH. The formula is as
follows: RRC setup success rate on the ERACH = VS.RRC.SuccConnEstab.ERACH/
VS.RRC.AttConnEstab.ERACH.
Measurement point
The measurement is triggered at point C shown in the following figure. After receiving an RRC
CONNECTION SETUP COMPLETE message from an UE, the RNC measures this counter if
the RRC connection is set up on an ERACH.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RRC.SuccConnEstab.E WRFD-010701 Uplink Enhanced

RACH CELL_FACH
1.12.10.4 Number of PS RAB Setup Requests on an ERACH for Cell
Counters
73423342 VS.RAB.AttEstabPS.ERAC Number of PS RAB Setup

H Requests on an ERACH for
Cell

BSC6900 UMTS
Description
This counter provides the number of requests for setting up a PS RAB on the ERACH in a cell.
Measurement point
The measurement is triggered at point A shown in the following figure. When the RNC receives
from the CN an RAB ASSIGNMENT REQUEST message, the counter is measured in the cell
that the UE camps on if the request is for setting up a PS RAB on an ERACH.
Formula
None
Unit
None
Related Features
VS.RAB.AttEstabPS.ERAC WRFD-010701 Uplink Enhanced

H CELL_FACH

BSC6900 UMTS
1.12.10.5 Number of Successful PS RAB Setups on an ERACH for Cell
Counters
73423343 VS.RAB.SuccEstabPS.ERA Number of Successful PS

CH RAB Setups on an ERACH
for Cell
Description
This counter provides the number of times that a PS RAB is successfully set up on the ERACH
in a cell. Together with "Number of PS RAB Setup Requests on ERACH for Cell", this counter
reflects the PS RAB setup success rate on the ERACH. The formula is as follows: PS RAB setup
success rate = VS.RAB.SuccEstabPS.ERACH/VS.RAB.AttEstabPS.ERACH .
Measurement point
The measurement is triggered at point B shown in the following figure. When the RNC sends
the CN an RAB ASSIGNMENT RESPONSE message after receiving from the UE a RADIO
BEARER SETUP COMPLETE message, it measures the counter in the cell that the UE camps
on if the PS RAB is set up on an ERACH.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SuccEstabPS.ERA WRFD-010701 Uplink Enhanced

CH CELL_FACH
1.12.10.6 Number of PS RABs Normally Released on an ERACH for Cell
Counters
73423344 VS.RAB.NormRel.PS.ERA Number of PS RABs

CH Normally Released on an
ERACH for Cell
Description
This counter provides the number of times that a PS RAB is normally released on the ERACH
in a cell.
Measurement point
The measurement is triggered at point A in the figure. After receiving from the CN an IU
RELEASE COMMAND message, the RNC releases the corresponding RAB, and then sends
the CN an IU RELEASE COMPLETE message. If the release cause in the IU RELEASE
COMMAND message is "User Inactivity", "Normal Release", "Successful Relocation", or
"Network Optimization", or if the RNC has sent a release request with the cause of "User
Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before
the RNC receives the IU RELEASE COMMAND message and the RAB to be released is a PS
RAB carried on an ERACH, then the counter is measured in the cell that the UE camps on.

BSC6900 UMTS
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.PS.ERA WRFD-010701 Uplink Enhanced

CH CELL_FACH
1.12.10.7 Number of PS RABs Abnormally Released on an ERACH for Cell

BSC6900 UMTS
Counters
73423345 VS.RAB.AbnormRel.PS.ER Number of PS RABs

ACH Abnormally Released on an
ERACH for Cell
Description
This counter provides the number of times that a PS RAB is abnormally released on the ERACH
in a cell. Together with "Number of PS RABs Normally Released on the ERACH for Cell", this
counter reflects the ratio of abnormal PS RAB releases on ERACHs. The formula is as follows:
Ratio of abnormal PS RAB releases on the ERACH = VS.RAB.AbnormRel.PS.ERACH/
VS.RAB.NormRel.PS.ERACH .
Measurement point
As shown by point A in the following figure, when an abnormal release occurs, the RNC sends
the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an RAB
ASSIGNMENT REQUEST message which contains a cause value of the abnormal release
(causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network
Optimization", for details, see 3GPP TS 25.413) and the RAB to be released is a PS RAB carried
on an ERACH, then this counter is measured in the cell that the UE camps on.
the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an IU

BSC6900 UMTS
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.
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.PS.ER WRFD-010701 Uplink Enhanced

ACH CELL_FACH
1.12.10.8 RRC Connection Setup Duration on an ERACH for Cell
Counters
73423346 VS.RRC.ConnEstabTimeM Maximum RRC Connection

ax.ERACH Setup Duration on an
ERACH for Cell

BSC6900 UMTS
73441135 VS.RRC.ConnEstabTimeM Average RRC Connection

ean.ERACH Setup Duration on an
ERACH for Cell
specific formulas.
73423347 VS.RRC.ConnEstabTime.C Accumulative Duration of

CH.ERACH.Cum RRC Establishment Process
on ERACH for Cell
73423348 VS.RRC.ConnEstabTime.C Number of Samples of

CH.ERACH.Sample Cumulative Duration of RRC
Establishment Process on
ERACH for Cell
Description
These counters provide the maximum and average durations taken by an RRC connection setup
on the ERACH in a cell.
Measurement point
As shown in the figure, when the RNC receives an RRC CONNECTION REQUEST message
at point A, the time is recorded as T1. When the RNC receives an RRC CONNECTION SETUP
COMPLETE message at point C, the time is recorded as T2. The RNC uses delta T = T2-T1 as
the RRC connection setup duration on the ERACH if the RRC connection is set up on the
ERACH. The RNC takes a sample from durations taken by an RRC connection setup on the
ERACH every 5s. At the end of the measurement period, the RNC obtains the value of
VS.RRC.ConnEstabTimeMean.ERACH for Cell by dividing the accumulated numbers by the
number of samples. In addition, the RNC takes the maximum sampling number as the value of
VS.RRC.ConnEstabTimeMax.ERACH.

BSC6900 UMTS
Formula
VS.RRC.ConnEstabTimeMean.ERACH = [VS.RRC.ConnEstabTime.CCH.ERACH.Cum]/
[VS.RRC.ConnEstabTime.CCH.ERACH.Sample]
Unit
ms
Related Features
VS.RRC.ConnEstabTimeM WRFD-010701 Uplink Enhanced

ax.ERACH CELL_FACH
VS.RRC.ConnEstabTimeM WRFD-010701 Uplink Enhanced

ean.ERACH CELL_FACH
1.12.10.9 Traffic over ERACH on Iub Interface

BSC6900 UMTS
Counters
73441170 VS.CRNCIubBytesERACH. Number of Bytes over Iub

Rx ERACH for Cell
Description
This counter provides the bytes of UL MAC PDUs (including the signaling data and the service
data, not including the FP header) received by the CRNC over the ERACH FP on the Iub
interface.
Measurement point
The measurement is triggered when the CRNC sends UL data over the ERACH FP on the Iub
interface. At the end of the measurement period, the bytes of UL data over the ERACH FP are
accumulated to obtain the bytes of UL MAC PDUs (including the signaling data and the service
data, not including the FP header) received by the CRNC over the ERACH FP on the Iub
interface.
Formula
None
Unit
byte
Related Features
VS.CRNCIubBytesERACH. WRFD-010701 Uplink Enhanced

Rx CELL_FACH
1.12.10.10 Number of Successful State Transitions from CELL_DCH (E-DCH) to

Enhanced CELL_FACH (E-DCH) for Cell

BSC6900 UMTS
Counters
73426161 VS.ERACH.E2F.Succ Number of Successful State

Transitions from
CELL_DCH (E-DCH) to
Enhanced CELL_FACH (E-
DCH) for Cell
73426162 VS.ERACH.F2E.Succ Number of Successful State

CELL_FACH (E-DCH) to
CELL_DCH (E-DCH) for
Cell
Description
These counters provide the number of successful state transitions from enhanced CELL_FACH
(E-DCH) to CELL_DCH (E-DCH) and state transitions from CELL_DCH (E-DCH) to enhanced
CELL_FACH (E-DCH). Enhanced CELL_FACH (E-DCH) refers to the state in which UEs stay
in the CELL_FACH state but use HS-DSCHs in the downlink and E-DCHs in the uplink.
Measurement point
When the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message
from a UE during a state transition from CELL_DCH (E-DCH) to enhanced CELL_FACH (E-
DCH), VS.ERACH.E2F.Succ is increased by one in the serving cell where the UE camps before
the state transition. If the state transition is from enhanced CELL_FACH (E-DCH) to
CELL_DCH (E-DCH), VS.ERACH.F2E.Succ is increased by one in the cell where the UE now
camps. The measurement is triggered at point B, as shown in the following figure.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.ERACH.E2F.Succ WRFD-01061208 HSUPA DCCC

WRFD-010701 Uplink Enhanced
CELL_FACH
VS.ERACH.F2E.Succ WRFD-01061208 HSUPA DCCC

CELL_FACH
1.12.10.11 Number of Attempts at State Transitions from CELL_DCH (E-DCH) to

Enhanced CELL_FACH (E-DCH) for Cell
Counters
73426163 VS.ERACH.E2F.Att Number of Attempts at State

Transitions from
CELL_DCH (E-DCH) to
Enhanced CELL_FACH (E-
DCH) for Cell
73426164 VS.ERACH.F2E.Att Number of Attempts at State

Transition from Enhanced
CELL_FACH (E-DCH) to
CELL_DCH (E-DCH) for
Cell
Description
These counters provide the number of attempts at state transitions from enhanced CELL_FACH
(E-DCH) to CELL_DCH (E-DCH) and state transitions from CELL_DCH (E-DCH) to enhanced
CELL_FACH (E-DCH). Enhanced CELL_FACH (E-DCH) refers to the state in which UEs stay
in the CELL_FACH state but use HS-DSCHs in the downlink and E-DCHs in the uplink.

BSC6900 UMTS
Measurement point
When the RNC sends a UE a RADIO BEARER RECONFIGURATION message during a state
transition from CELL_DCH (E-DCH) to enhanced CELL_FACH (E-DCH),
VS.ERACH.E2F.Att is increased by one in the serving cell where the UE camps before the state
transition. If the state transition is from enhanced CELL_FACH (E-DCH) to CELL_DCH (E-
DCH), VS.ERACH.F2E.Att is increased by one in the cell where the UE now camps. The
measurement is triggered at point A, as shown in the following figure.
Formula
None
Unit
None
Related Features
VS.ERACH.E2F.Att WRFD-01061208 HSUPA DCCC

CELL_FACH
VS.ERACH.F2E.Att WRFD-01061208 HSUPA DCCC

CELL_FACH

BSC6900 UMTS
1.12.11 Hard Handover Measurement per cell(HHO.Cell)

Overview
This function subset provides measurements on messages involved in hard handovers on a cell
basis. Hard handover is a handover procedure in which all the existing radio links connected to
a UE are released before a new one is set up. That is, communications on the existing radio links
are interrupted, and then communications on the new radio link are established. Therefore, the
performance of hard handover is not as good as that of soft handover. In most cases, hard
handover is triggered by coverage, QoS, HCS, LDR, and CLB algorithm. Hard handover can
be classified into intra-frequency hard handover and inter-frequency hard handover.
Intra-frequency hard handover: In this mode, the cells that the UE camps on before and after the
handover use the same frequency. The intra-frequency hard handover can be performed only
when soft handover is not available.
Inter-frequency hard handover: In this mode, the cells that the UE camps on before and after the
handover use different frequencies. In addition, the inter-band hard handover are included in the
inter-frequency hard handover. Inter-frequency hard handover can balance the loads and
implement seamless connection between different TRXs. Generally, before an inter-frequency
hard handover, the UE requires compressed mode configurations to perform an inter-frequency
measurement according to its capability. The decision of inter-frequency hard handover is
mainly based on inter-frequency measurement reports.
When deciding to perform a hard handover, the RNC sends the PHYSICAL CHANNEL
RECONFIGURATION message, TRANSPORT CHANNEL RECONFIGURATION message,
RADIO BEARER RECONFIGURATION message, RADIO BEARER SETUP message, or
RADIO BEARER RELEASE message to the UE for response. If the RNC receives the
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message, TRANSPORT
CHANNEL RECONFIGURATION COMPLETE message, RADIO BEARER
RECONFIGURATION COMPLETE message, RADIO BEARER SETUP COMPLETE
message, or RADIO BEARER RELEASE COMPLETE message from the UE in the target cell,
the hard handover succeeds. If the RNC receives the PHYSICAL CHANNEL
RECONFIGURATION FAILURE message, TRANSPORT CHANNEL
RECONFIGURATION FAILURE message, RADIO BEARER RECONFIGURATION
FAILURE message, RADIO BEARER SETUP FAILURE message, or RADIO BEARER
RELEASE FAILURE message in the source cell during the hard handover or the RNC does not
receive the response message from the UE before the timer expires, the hard handover fails. The
relocation with hard handover has the same procedure. The following figure shows the related
procedure.
Hard Handover Measurement per cell(HHO Cell) provides measurements on the messages
involved in hard handovers from the view of cell. This function subset consists of measurements
on incoming hard handovers and outgoing hard handovers. The measurement of incoming hard
handover is triggered in the target cell, whereas the measurement of outgoing hard handover is
triggered in the best cell before hard handover.
If the RNC triggers hard handovers for UEs processing combined services, the measurement is
triggered by counters that do not differentiate services. The measurement is also triggered by
counters that differentiate services based on the RAB numbers for each type of services. For
example, if the RNC triggers inter-RNC inter-frequency hard handovers for UEs processing
combined services, the measurement is triggered by the VS.HHO.SuccInterFreqOut.InterRNC
counter. The measurement is also triggered by the VS.HHO.SuccInterFreqOut.CS and

BSC6900 UMTS
VS.HHO.SuccInterFreqOut.PS counters based on the RB numbers occupied by CS and PS

services, respectively.
Figure 1-452 Flow chart of hard handover and hard handover with relocation
A VS.HHO.EvalOut, VS.HHO.EvalIn,
VS.HHO.InterFreqOut.Eval.CM,
VS.HHO.InterFreqIn.Eval.CM

BSC6900 UMTS
B VS.HHO.AttInterFreqIn , VS.HHO.AttInter-
FreqOut, VS.HHO.AttIn,
VS.HHO.AttMultiBandOut.CS,
VS.HHO.AttInterCellLB.SingleRL,
VS.HHO.AttInterCellLB.MultiRL,
VS.HHO.AttBlindHO,
VS.HHO.AttInterFreqIn.CS,
VS.HHO.AttInterFreqIn.PS,
VS.HHO.AttInterFreqOut.CS,
VS.HHO.AttInterFreqOut.PS,
VS.HHO.AttInterFreqOut.Sig,
VS.HHO.AttInterFreqOut.CS.TrigRscp,
VS.HHO.AttInterFreqOut.CS.TrigEcNo,
VS.HHO.AttInterFreqOut.PS.TrigRscp,
VS.HHO.AttInterFreqOut.PS.TrigEcNo,
VS.HHO.AttInterFreqOut.PS.UlBler,
VS.HHO.AttInterFreqOut.CS.UeTxPwr,
VS.HHO.AttInterFreqOut.PS.UeTxPwr,
VS.HHO.AttInterFreqOut.CS.Tcp,
VS.HHO.AttInterFreqOut.PS.Tcp,
VS.HHO.AttInterFreqOut.CS.TotalTxPwr,
VS.HHO.AttInterFreqOut.PS.TotalTxPwr,
VS.HHO.AttInterFreqOut.CS.TotalRxPwr,
VS.HHO.AttInterFreqOut.PS.TotalRxPwr,
VS.HHO.AttInterFreqOut.CS.Code,
VS.HHO.AttInterFreqOut.PS.Code,
VS.HHO.AttInterFreqOut.PS.UlCE,
VS.HHO.AttInterFreqOut.PS.DlCE,
VS.HHO.AttInterFreqOut.CS.DlCE,
VS.HHO.AttInterFreqOut.CS.UlCE,
VS.HHO.AttInterFreqOut.PS.CoMacroMi-
cro
C VS.HHO.AttIntraFreqOut.IntraNodeB,
VS.HHO.AttInterFreqOut.IntraNodeB
D VS.HHO.SuccIntraFreqOut.IntraNodeB,
VS.HHO.SuccInterFreqOut.IntraNodeB
E VS.HHO.AttIntraFreqOut.InterNodeBIn-
traRNC, VS.HHO.AttInterFreqOut.InterNo-
deBIntraRNC
F VS.HHO.SuccIntraFreqOut.InterNodeBIn-
traRNC, VS.HHO.SuccInterFreqOut.Inter-
NodeBIntraRNC
G VS.HHO.AttIntraFreqOut.InterRNC,
VS.HHO.AttInterFreqOut.InterRNC

BSC6900 UMTS
H VS.HHO.SuccIntraFreqOut.InterRNC,
VS.HHO.SuccInterFreqOut.InterRNC
I VS.HHO.SuccInterFreqOut,
VS.HHO.SuccInterFreqIn,
VS.HHO.SuccInterCellLB.SingleRL,
VS.HHO.SuccMultiBandOut.PS,
VS.HHO.SuccMultiBandOut.CS,
VS.HHO.SuccInterCellLB.MultiRL,
VS.HHO.SuccInterFreqOut, VS.HHO.Succ-
BlindHO, VS.HHO.SuccInterFreqIn.CS,
VS.HHO.SuccInterFreqIn.PS,
VS.HHO.SuccInterFreqOut.PS,
VS.HHO.SuccInterFreqOut.Sig,
VS.HHO.SuccInterFreqOut.CS.Rscp,
VS.HHO.SuccInterFreqOut.CS.EcNo,
VS.HHO.SuccInterFreqOut.PS.Rscp,
VS.HHO.SuccInterFreqOut.PS.EcNo,
VS.HHO.SuccInterFreqOut.PS.UlBler,
VS.HHO.SuccInterFreqOut.CS.UeTxPwr,
VS.HHO.SuccInterFreqOut.PS.UeTxPwr,
VS.HHO.SuccInterFreqOut.CS.Tcp,
VS.HHO.SuccInterFreqOut.PS.Tcp,
VS.HHO.SuccInterFreqOut.CS.To-
talTxPwr,
VS.HHO.SuccInterFreqOut.PS.TotalTxPwr,
VS.HHO.SuccInterFreqOut.CS.To-
talRxPwr,
VS.HHO.SuccInterFreqOut.PS.TotalRxPwr,
VS.HHO.SuccInterFreqOut.CS.Code,
VS.HHO.SuccInterFreqOut.PS.Code,
VS.HHO.SuccInterFreqOut.PS.UlCE,
VS.HHO.SuccInterFreqOut.PS.DlCE,
VS.HHO.SuccInterFreqOut.CS.UlCE,
VS.HHO.SuccInterFreqOut.CS.DlCE,
VS.HHO.SuccInterFreqOut.PS.CoMacro-
Micro, VS.HHO.SuccIn

BSC6900 UMTS
J VS.HHO.FailIntraFreqOut.InterRNC.CfgU
nsupp ,
VS.HHO.FailInterFreqOut.InterRNC.CfgU
nsupp ,
VS.HHO.FailIntraFreqOut.InterRNC.NoRe-
ply,
VS.HHO.FailInterFreqOut.InterRNC.NoRe-
ply,
VS.HHO.FailIntraFreqOut.InterRNC.Cel-
lUpdt,
VS.HHO.FailInterFreqOut.InterRNC.PhyC
hFail,
VS.HHO.FailInterFreqOut.InterRNC.ISR,
VS.HHO.FailInterFreqOut.InterRNC.InvCf
g, VS.HHO.FailInterFreqOut.InterRNC.Cel-
lUpdt
K VS.HHO.FailIntraFreqOut.CfgUnsupp,
VS.HHO.FailInterFreqOut.CfgUnsupp,
VS.HHO.FailIntraFreqOut.NoReply,
VS.HHO.FailInterFreqOut.NoReply,
VS.HHO.FailIntraFreqOut.InvCfg,
VS.HHO.FailIntraFreqOut.PyhChFail,
VS.HHO.FailIntraFreqOut.ISR,
VS.HHO.FailIntraFreqOut.CellUpdt,
VS.HHO.FailIntraFreqOut.InterRNC.PhyC
hFail,
VS.HHO.FailIntraFreqOut.InterRNC.ISR,
VS.HHO.FailIntraFreqOut.InterRNC.InvCf
g, VS.HHO.FailInterFreqOut.PyhChFail,
VS.HHO.FailInterFreqOut.ISR,
VS.HHO.FailInterFreqOut.CellUpdt,
VS.HHO.FailInterFreqOut.InvCfg,
VS.HHO.IntraFreqOut.Drop,
VS.HHO.InterFreqOut.CS.Drop,
VS.HHO.InterFreqOut.PS.Drop
L VS.HHO.FailIntraFreqOut.RLSetupFail,
VS.HHO.FailInterFreqOut.RLSetupFail
M VS.HHO.FailIntraFreqOut.PrepFail,
VS.HHO.FailInterFreqOut.PrepFail
N VS.HHO.AttIntraFreqRelocPrep,
VS.HHO.AttInterFreqRelocPrep
O VS.HHO.SuccIntraFreqRelocPrep,
VS.HHO.SuccInterFreqRelocPrep
P VS.HHO.AttIntraFreqRelocExec,
VS.HHO.AttInterFreqRelocExec

BSC6900 UMTS
Q VS.HHO.SuccIntraFreqRelocExec,
VS.HHO.SuccInterFreqRelocExec
R HHO.FailRelocPrepOut.NoResAvail,
HHO.FailRelocPrepOut.Texp,
HHO.FailRelocPrepOut.TgtFail,
HHO.FailRelocPrepOut.RelocUnsupp,
HHO.FailRelocPrepOut.TgtNotAllow,
HHO.FailRelocPrepOut.OM,
HHO.FailRelocPrepOut.ResUnavail,
HHO.FailRelocPrepOut.Unspec
* The RL establishment consists of the RL

establishment on the Iub interface and RL
establishment on the Iur interface.
** In the reconfiguration procedure, the RNC

sends the PHYSICAL CHANNEL
RECONFIGURATION, TRANSPORT
CHANNEL RECONFIGURATION,
RADIO BEARER RECONFIGURATION,
RADIO BEARER SETUP, or RADIO
BEARER RELEASE message to the UE. The
procedure shown in the figure takes the
PHYSICAL CHANNEL
RECONFIGURATION message as an
example.
*** The cause value of normal releases is

"Successful Relocation", "Normal Release",
or "Network Optimization."
Counters
Description
67180565 VS.HHO.AttIn Number of Incoming Earlier than

Hard Handover V900R011
Attempts for Cell
67180566 VS.HHO.SuccIn Number of Earlier than

Successful Incoming V900R011
Hard Handovers in
the RNC for Cell

BSC6900 UMTS

Description
67193708 VS.HHO.AttIntra- Number of Earlier than

FreqRelocPrep Relocation V900R011
Preparation
Attempts with
Outgoing Intra-
Frequency Hard
Handovers for Cell
67192770 VS.HHO.SuccIn- Number of Earlier than

traFreqRelocPrep Successful V900R011
Relocation
Preparations with
Outgoing Intra-
Frequency Hard
Handovers for Cell
67192551 VS.HHO.AttInter- Number of Earlier than

FreqRelocPrep Relocation V900R011
Preparation
Attempts with
Outgoing Inter-
Frequency Hard
Handovers for Cell

terFreqRelocPrep Successful V900R011
Relocation
Preparations with
Outgoing Inter-
Frequency Hard
Handovers for Cell
67192553 VS.HHO.FailIntra Number of Failed Earlier than

FreqOut.NoReply Outgoing Intra- V900R011
Frequency Hard
Handovers Due to
No Response from
the UE for Cell

FreqOut.PrepFail Preparations for V900R011
Outgoing Intra-
Frequency Hard
Handovers for Cell
67192555 VS.HHO.FailInter Number of Failed Earlier than

FreqOut.PrepFail Preparations for V900R011
Outgoing Inter-
Frequency Hard
Handovers for Cell

BSC6900 UMTS

Description

FreqOut.RLSetup- Preparations for V900R011
Fail Outgoing Intra-
Frequency Hard
Handovers Due to
Radio Link
Establishment
Failure for Cell

FreqOut.RLSetup- Preparations for V900R011
Fail Outgoing Inter-
Frequency Hard
Handovers Due to
Radio Link
Establishment
Failure for Cell

FreqOut.InvCfg Outgoing Intra- V900R011
Frequency Hard
Handovers for Cell
(Invalid
Configuration)

FreqOut.CfgUn- Outgoing Intra- V900R011
supp Frequency Hard
Handovers for Cell
(Configuration
Unsupported)

FreqOut.PyhCh- Outgoing Intra- V900R011
Fail Frequency Hard
Handovers for Cell
(Physical Channel
Failure)

FreqOut.ISR Outgoing Intra- V900R011
Frequency Hard
Handovers for Cell
(Incompatible
Simultaneous
Reconfiguration)

BSC6900 UMTS

Description

FreqOut.CellUpdt Outgoing Intra- V900R011
Frequency Hard
Handovers for Cell
(Cell Update
Occurred)
67193565 VS.HHO.AttMulti Number of CS Earlier than

BandOut.CS Outgoing Inter-Band V900R011
Hard Handover
Attempts for Cell
67193566 VS.HHO.SuccMult Number of Earlier than

iBandOut.CS Successful CS V900R011
Outgoing Inter-Band
Hard Handovers for
Cell
67192567 VS.HHO.AttMulti Number of PS Earlier than

BandOut.PS Outgoing Inter-Band V900R011
Hard Handover
Attempts for Cell
67192568 VS.HHO.SuccMult Number of Earlier than

iBandOut.PS Successful PS V900R011
Outgoing Inter-Band
Hard Handovers for
Cell
67180585 VS.HHO.AttIntraF Number of Outgoing Earlier than

reqOut.IntraNo- Intra-Frequency V900R011
deB Hard Handover
Attempts in NodeB
for Cell

FreqOut.IntraNo- Successful Outgoing V900R011
deB Intra-Frequency
Hard Handovers in
NodeB for Cell

reqOut.InterNode- Intra-Frequency V900R011
BIntraRNC Hard Handover
Attempts Between
Different NodeBs of
RNC for Cell

BSC6900 UMTS

Description

FreqOut.InterNo- Successful Outgoing V900R011
deBIntraRNC Intra-Frequency
Hard Handovers
Between Different
NodeBs of RNC for
Cell

reqOut.InterRNC Intra-Frequency V900R011
Hard Handover
Attempts Between
RNCs for Cell

FreqOut.InterRNC Successful Outgoing V900R011
Intra-Frequency
Hard Handovers
Between RNCs for
Cell

FreqOut.InterRNC Outgoing Intra- V900R011
.CfgUnsupp Frequency Hard
Handovers Between
RNCs for Cell
(Configuration
Unsupported)

.PhyChFail Frequency Hard
Handovers Between
RNCs for Cell
(Physical Channel
Failure)

.ISR Frequency Hard
Handovers Between
RNCs for Cell
(Incompatible
Simultaneous
Reconfiguration)

BSC6900 UMTS

Description

.InvCfg Frequency Hard
Handovers Between
RNCs for Cell
(Invalid
Configuration)
67189708 HHO.FailRelocPre Number of Failed Earlier than

pOut.NoResAvail Relocation V900R011
Preparations with
Outgoing Hard
Handovers for Cell
(No Radio Resources
Available in Target
Cell)

pOut.Texp Relocation V900R011
Preparations with
Outgoing Hard
Handovers for Cell
(TRELOCalloc
Expiry)

pOut.TgtFail Relocation V900R011
Preparations with
Outgoing Hard
Handovers for Cell
(Relocation Failure
in Target CN/RNC or
Target System)

pOut.RelocUnsupp Relocation V900R011
Preparations with
Outgoing Hard
Handovers for Cell
(Relocation Not
Supported in Target
RNC or Target
System)

BSC6900 UMTS

Description

pOut.TgtNotAllow Relocation V900R011
Preparations with
Outgoing Hard
Handovers for Cell
(Relocation Target
Not Allowed)

pOut.OM Relocation V900R011
Preparations with
Outgoing Hard
Handovers for Cell
(O&M Intervention)

pOut.ResUnavail Relocation V900R011
Preparations with
Outgoing Hard
Handovers for Cell
(No Resource
Available)

pOut.Unspec Relocation V900R011
Preparations with
Outgoing Hard
Handovers for Cell
(Unspecified
Failure)
67189716 VS.HHO.AttIntra- Number of Earlier than

FreqRelocExec Relocation V900R011
Execution Attempts
with Outgoing Intra-
Frequency Hard
Handovers for Cell

traFreqRelocExec Successful V900R011
Relocation
Executions with
Outgoing Intra-
Frequency Hard
Handovers for Cell
67189722 VS.HHO.EvalOut Number of Decisions Earlier than

for Outgoing Hard V900R011
Handovers for Cell

BSC6900 UMTS

Description
67189723 VS.HHO.EvalIn Number of Decisions Earlier than

for Incoming Hard V900R011
Handovers for Cell
67180551 VS.HHO.InterFreq Number of Decisions Earlier than

Out.Eval.CM for Outgoing Inter- V900R011
Frequency Hard
Handovers in
Compressed Mode
for Cell
67180570 VS.HHO.InterFreq Number of Decisions Earlier than

In.Eval.CM for Incoming Inter- V900R011
Frequency Hard
Handovers in
Compressed Mode
for Cell
67180549 VS.HHO.AttInterC Number of Outgoing Earlier than

ellLB.SingleRL Inter-Frequency V900R011
Hard Handover
Attempts Due to
Load Balancing for
Cell (Single RL)

CellLB.SingleRL Successful Outgoing V900R011
Inter-Frequency
Hard Handovers Due
to Load Balancing
for Cell (Single RL)
67193709 VS.HHO.AttInterC Number of Outgoing Earlier than

ellLB.MultiRL Inter-Frequency V900R011
Hard Handover
Attempts Due to
Load Balancing for
Cell (Multiple RLs)

CellLB.MultiRL Successful Outgoing V900R011
Inter-Frequency
Hard Handovers Due
to Load Balancing
for Cell (Multiple
RLs)

BSC6900 UMTS

Description
67183900 VS.HHO.AttInter- Number of Outgoing Earlier than

FreqOut Inter-Frequency V900R011
Hard Handover
Attempts for Cell

terFreqOut Successful Outgoing V900R011
Inter-Frequency
Hard Handovers for
Cell

FreqOut.CfgUn- Outgoing Inter- V900R011
supp Frequency Hard
Handovers for Cell
(Configuration
Unsupported)

FreqOut.PyhCh- Outgoing Inter- V900R011
Fail Frequency Hard
Handovers for Cell
(Physical Channel
Failure)

FreqOut.ISR Outgoing Inter- V900R011
Frequency Hard
Handovers for Cell
(Incompatible
Simultaneous
Reconfiguration)

FreqOut.CellUpdt Outgoing Inter- V900R011
Frequency Hard
Handovers for Cell
(Cell Update
Occurred)

FreqOut.InvCfg Outgoing Inter- V900R011
Frequency Hard
Handovers for Cell
(Invalid
Configuration)

BSC6900 UMTS

Description

FreqOut.NoReply Outgoing Inter- V900R011
Frequency Hard
Handovers Due to
No Response from
the UE for Cell
67183912 VS.HHO.AttInter- Number of Incoming Earlier than

FreqIn Inter-Frequency V900R011
Hard Handover
Attempts for Cell

terFreqIn Successful Incoming V900R011
Inter-Frequency
Hard Handovers for
Cell
67183926 VS.HHO.IntraFreq Number of Call Earlier than

Out.Drop Drops Due to Failed V900R011
Outgoing Intra-
Frequency Hard
Handovers for Cell
67190877 VS.HHO.AttInterF Number of Outgoing Earlier than

reqOut.IntraNo- Inter-Frequency V900R011
deB Hard Handover
Attempts in NodeB
for Cell

FreqOut.IntraNo- Successful Outgoing V900R011
deB Inter-Frequency
Hard Handovers in
NodeB for Cell

reqOut.InterNode- Inter-Frequency V900R011
BIntraRNC Hard Handovers
Attempts Between
Different NodeBs of
RNC for Cell

FreqOut.InterNo- Successful Outgoing V900R011
deBIntraRNC Inter-Frequency
Hard Handovers
Between Different
NodeBs of RNC for
Cell

BSC6900 UMTS

Description

reqOut.InterRNC Inter-Frequency V900R011
Hard Handovers
Attempts Between
RNCs for Cell

FreqOut.InterRNC Successful Outgoing V900R011
Inter-Frequency
Hard Handovers
Between RNCs for
Cell
67190898 VS.HHO.AttInter- Number of Earlier than

FreqRelocExec Relocation V900R011
Execution Attempts
with Outgoing Inter-
Frequency Hard
Handovers for Cell

terFreqRelocExec Successful V900R011
Relocation
Executions with
Outgoing Inter-
Frequency Hard
Handovers for Cell
67191694 VS.HHO.AttBlind- Number of Outgoing Earlier than

HO Emergency Blind V900R011
Handover Attempts
for Cell
67191695 VS.HHO.Succ- Number of Earlier than

BlindHO Successful Outgoing V900R011
Emergency Blind
Hard Handovers for
Cell
67193397 VS.HHO.InterFreq Number of Earlier than

Out.CS.MeasTime- Handovers Not V900R011
Out Performed Due to CS
Inter-Frequency
Measurement Expiry
for Cell

BSC6900 UMTS

Description
67193398 VS.HHO.InterFreq Number of Earlier than

Out.PS.MeasTime- Handovers Not V900R011
Out Performed Due to PS
Inter-Frequency
Measurement Expiry
for Cell
67193401 VS.HHO.AttInterF Number of CS Inter- Earlier than

reqOut.CS.TrigRsc Frequency Hard V900R011
p Handover Attempts
Based on RSCP for
Cell
67193402 VS.HHO.AttInterF Number of CS Inter- Earlier than

reqOut.CS.TrigEc- Frequency Hard V900R011
No Handover Attempts
Based on EcNo for
Cell
67193403 VS.HHO.AttInterF Number of PS Inter- Earlier than

reqOut.PS.TrigRsc Frequency Hard V900R011
p Handover Attempts
Based on RSCP for
Cell
67193404 VS.HHO.AttInterF Number of PS Inter- Earlier than

reqOut.PS.TrigEc- Frequency Hard V900R011
No Handover Attempts
Based on EcNo for
Cell
73403768 VS.HHO.AttInterF Number of Requests V900R012

reqIn.CS for CS Incoming
Inter-Frequency
Hard Handovers for
Cell

reqIn.PS for PS Incoming
Inter-Frequency
Hard Handovers for
Cell

reqOut.CS for CS Outgoing
Inter-Frequency
Hard Handovers for
Cell

BSC6900 UMTS

Description

reqOut.PS for PS Outgoing
Inter-Frequency
Hard Handovers for
Cell
73403772 VS.HHO.SuccInter Number of V900R012

FreqIn.CS Successful for CS
Incoming Inter-
Frequency Hard
Handovers for Cell

FreqIn.PS Successful for PS
Incoming Inter-
Frequency Hard
Handovers for Cell

FreqOut.CS Successful for CS
Outgoing Inter-
Frequency Hard
Handovers for Cell

FreqOut.PS Successful for PS
Outgoing Inter-
Frequency Hard
Handovers for Cell
73403776 VS.HHO.InterFreq Number of CS Call V900R012

Out.CS.Drop Drops due to
Unsuccessful
Outgoing Inter-
Frequency Hard
Handovers for cell
73403777 VS.HHO.InterFreq Number of PS Call V900R012

Out.PS.Drop Drops due to
Unsuccessful
Outgoing Inter-
Frequency Hard
Handovers for cell

FreqOut.CS.Rscp Successful CS Inter-
Frequency Hard
Handovers Based on
RSCP for Cell

BSC6900 UMTS

Description

FreqOut.CS.EcNo Successful CS Inter-
Frequency Hard
Handovers Based on
EcNo for Cell

FreqOut.PS.Rscp Successful PS Inter-
Frequency Hard
Handovers Based on
RSCP for Cell

FreqOut.PS.EcNo Successful PS Inter-
Frequency Hard
Handovers Based on
EcNo for Cell
73393851 VS.HHO.FailIntra Number of Failed V900R012

FreqOut.InterRNC Outgoing Intra-
.CellUpdt Frequency Hard
Handovers Between
RNCs for Cell (Cell
update occurred)
73393852 VS.HHO.FailIntra Number of Failed V900R012

FreqOut.InterRNC Outgoing Intra-
.NoReply Frequency Hard
Handovers Between
the RNCs Due to No
Response from the
UE for Cell
73393853 VS.HHO.FailInter Number of Failed V900R012

FreqOut.InterRNC Outgoing Inter-
.CfgUnsupp Frequency Hard
Handovers Between
the RNCs for Cell
(Configuration
Unsupported)

.PhyChFail Frequency Hard
Handovers Between
the RNCs for Cell
(Physical Channel
Failure)

BSC6900 UMTS

Description

.ISR Frequency Hard
Handovers Between
the RNCs for Cell
(Incompatible
Simultaneous
Reconfiguration)

.InvCfg Frequency Hard
Handovers Between
the RNCs for Cell
(Invalid
Configuration)

.CellUpdt Frequency Hard
Handovers Between
the RNCs for Cell
(Cell Update
Occurred)

.NoReply Frequency Hard
Handovers Between
the RNCs Due to No
Response from the
UE for Cell
73393934 VS.HHO.AttInterF Number of PS Inter- V900R012

reqOut.PS.UlBler Frequency Hard
Handover Attempts
Based on UL BLER
for Cell
73393935 VS.HHO.AttInterF Number of CS Inter- V900R012

reqOut.CS.UeTxP Frequency Hard
wr Handover Attempts
Based on UE
Transmit Power for
Cell

BSC6900 UMTS

Description

reqOut.PS.UeTxP Frequency Hard
wr Handover Attempts
Based on UE
Transmit Power for
Cell

reqOut.CS.Tcp Frequency Hard
Handover Attempts
Based on DL
Transmit Power for
Cell

reqOut.PS.Tcp Frequency Hard
Handover Attempts
Based on DL
Transmit Power for
Cell

reqOut.CS.To- Frequency Hard
talTxPwr Handover Attempts
Based on Cell Total
Transmit Power for
Cell

reqOut.PS.To- Frequency Hard
talTxPwr Handover Attempts
Based on Cell Total
Transmit Power for
Cell

reqOut.CS.To- Frequency Hard
talRxPwr Handover Attempts
Based on Cell Total
Receive Power for
Cell

reqOut.PS.To- Frequency Hard
talRxPwr Handover Attempts
Based on Cell Total
Receive Power for
Cell

BSC6900 UMTS

Description

reqOut.CS.Code Frequency Hard
Handover Attempts
Based on Code
Resources for Cell

reqOut.PS.Code Frequency Hard
Handover Attempts
Based on Code
Resources for Cell

FreqOut.PS.UlBler Successful PS Inter-
Frequency Hard
Handovers Based on
UL BLER for Cell

FreqOut.CS.UeTx Successful CS Inter-
Pwr Frequency Hard
Handovers Based on
UE Transmit Power
for Cell

FreqOut.PS.UeTxP Successful PS Inter-
wr Frequency Hard
Handovers Based on
UE Transmit Power
for Cell

FreqOut.CS.Tcp Successful CS Inter-
Frequency Hard
Handovers Based on
DL Transmit Power
for Cell

FreqOut.PS.Tcp Successful PS Inter-
Frequency Hard
Handovers Based on
DL Transmit Power
for Cell

BSC6900 UMTS

Description

FreqOut.CS.To- Successful CS Inter-
talTxPwr Frequency Hard
Handovers Based on
Cell Total Transmit
Power for Cell

FreqOut.PS.To- Successful PS Inter-
talTxPwr Frequency Hard
Handovers Based on
Cell Total Transmit
Power for Cell

FreqOut.CS.To- Successful CS Inter-
talRxPwr Frequency Hard
Handovers Based on
Cell Total Receive
Power for Cell

FreqOut.PS.To- Successful PS Inter-
talRxPwr Frequency Hard
Handovers Based on
Cell Total Receive
Power for Cell

FreqOut.CS.Code Successful CS Inter-
Frequency Hard
Handovers Based on
Code Resources for
Cell

FreqOut.PS.Code Successful PS Inter-
Frequency Hard
Handovers Based on
Code Resources for
Cell

reqOut.PS.UlCE Frequency Hard
Handover Attempts
Based on UL CE for
Cell

BSC6900 UMTS

Description

FreqOut.PS.UlCE Successful PS Inter-
Frequency Hard
Handovers Based on
UL CE for Cell

reqOut.PS.DlCE Frequency Hard
Handover Attempts
Based on DL CE for
Cell

FreqOut.PS.DlCE Successful PS Inter-
Frequency Hard
Handovers Based on
DL CE for Cell

reqOut.CS.DlCE Frequency Hard
Handover Attempts
Based on DL CE for
Cell

reqOut.CS.UlCE Frequency Hard
Handover Attempts
Based on UL CE for
Cell

FreqOut.CS.UlCE Successful CS Inter-
Frequency Hard
Handovers Based on
UL CE for Cell

FreqOut.CS.DlCE Successful CS Inter-
Frequency Hard
Handovers Based on
DL CE for Cell
73425014 VS.HHO.AttInterF Number of Inter- V900R014

reqOut.Sig Frequency Hard
Handover Attempts
When only Signaling
Exists for Cell

BSC6900 UMTS

Description

FreqOut.Sig Successful Inter-
Frequency Hard
Handover Attempts
When only Signaling
Exists for Cell
73425831 VS.HHO.AttInterF Number of Outgoing V900R015

reqOut.PS.CoMa- Macro & Micro Joint
croMicro Inter-frequency
Handover Attempts
in PS Domain for
Cell

FreqOut.PS.CoMa- Successful Outgoing
croMicro Macro & Micro Joint
Inter-frequency
Handovers in PS
Domain for Cell
Counter Sub Counter
VS.HHO.FailIntraFreqOut.PrepFail VS.HHO.FailIntraFreqOut.RLSetupFail
VS.HHO.FailInterFreqOut.PrepFail VS.HHO.FailInterFreqOut.RLSetupFail
VS.HHO.AttInterFreqOut VS.HHO.AttInterFreqOut.IntraNodeB
VS.HHO.AttInterFreqOut.InterNodeBIn-
traRNC
VS.HHO.AttInterFreqOut.InterRNC
VS.HHO.SuccInterFreqOut VS.HHO.SuccInterFreqOut.IntraNodeB
VS.HHO.SuccInterFreqOut.InterNodeBIn-
traRNC
VS.HHO.SuccInterFreqOut.InterRNC
VS.HHO.AttInterFreqIn VS.HHO.AttInterFreqIn.CS
VS.HHO.AttInterFreqIn.PS
VS.HHO.SuccInterFreqIn VS.HHO.SuccInterFreqIn.CS
VS.HHO.SuccInterFreqIn.PS

BSC6900 UMTS
1.12.11.1 Number of Decisions for Outgoing Hard Handovers
Counters
67189722 VS.HHO.EvalOut Number of Decisions for

Outgoing Hard Handovers
for Cell
67180551 VS.HHO.InterFreqOut.Eval. Number of Decisions for

CM Outgoing Inter-Frequency
Hard Handovers in
Compressed Mode for Cell
Description
These counters provide 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.
VS.HHO.EvalOut Number of decisions for outgoing intra-

frequency and inter-frequency hard
handovers
VS.HHO.InterFreqOut.Eval.CM Number of decisions for outgoing inter-

frequency hard handovers in compressed
mode
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.EvalOut WRFD-020301 Intra Frequency Hard

WRFD-020304 Inter Frequency Hard

Handover Based on
Coverage

BSC6900 UMTS
VS.HHO.InterFreqOut.Eval. WRFD-020302 Inter Frequency Hard

CM WRFD-020304 Handover Based on
Coverage
1.12.11.2 Number of Decisions for Incoming Hard Handovers
Counters
67189723 VS.HHO.EvalIn Number of Decisions for

Incoming Hard Handovers
for Cell
67180570 VS.HHO.InterFreqIn.Eval.C Number of Decisions for

M Incoming Inter-Frequency
Hard Handovers in
Compressed Mode for Cell
Description
These counters provide the number of incoming hard handover decisions initiated by the RNC.
The measurement is performed in the target cell when handover conditions are met.
VS.HHO.EvalIn Number of decisions for incoming intra-

frequency and inter-frequency hard
handovers
VS.HHO.InterFreqIn.Eval.CM Number of decisions for incoming inter-

frequency hard handovers in compressed
mode
Measurement point
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.EvalIn WRFD-020301 Intra Frequency Hard


Handover Based on
Coverage

BSC6900 UMTS
VS.HHO.InterFreqIn.Eval.C WRFD-020302 Inter Frequency Hard

M WRFD-020304 Handover Based on
Coverage
1.12.11.3 Number of Outgoing Inter-Frequency Hard Handover Attempts
Counters
67183900 VS.HHO.AttInterFreqOut Number of Outgoing Inter-

Frequency Hard Handover
Attempts for Cell
67180549 VS.HHO.AttInterCellLB.Si Number of Outgoing Inter-

ngleRL Frequency Hard Handover
Attempts Due to Load
Balancing for Cell (Single
RL)
67193709 VS.HHO.AttInterCellLB.M Number of Outgoing Inter-

ultiRL Frequency Hard Handover
Attempts Due to Load
Balancing for Cell (Multiple
RLs)
73403770 VS.HHO.AttInterFreqOut.C Number of Requests for CS

S Outgoing Inter-Frequency
Hard Handovers for Cell
73403771 VS.HHO.AttInterFreqOut.P Number of Requests for PS

S Outgoing Inter-Frequency
73425014 VS.HHO.AttInterFreqOut.Si Number of Inter-Frequency

g Hard Handover Attempts
When only Signaling Exists
for Cell
Description
These counters provide 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.

BSC6900 UMTS
VS.HHO.AttInterFreqOut Number of outgoing inter-frequency hard

handover attempts
VS.HHO.AttInterCellLB.SingleRL Number of Outgoing Inter-Frequency Hard

Handover Attempts Due to Load Balancing
in Single RL
VS.HHO.AttInterCellLB.MultiRL Number of Outgoing Inter-Frequency Hard

Handover Attempts Due to Load Balancing
in Multiple RLs
VS.HHO.AttInterFreqOut.CS Number of requests for CS Outgoing inter-

frequency hard handovers
VS.HHO.AttInterFreqOut.PS Number of requests for PS Outgoing inter-

VS.HHO.AttInterFreqOut.Sig Number of outgoing inter-frequency hard

handover attempts when the UE has only
signalling
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
according to service types and the number of RL in the best cell where the UE camps on before
the inter-frequency hard handover.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.AttInterFreqOut WRFD-020302 Inter Frequency Hard

Coverage
WRFD-020106
Load Reshuffling
VS.HHO.AttInterCellLB.Si WRFD-020103 Inter Frequency Load

ngleRL Balance
VS.HHO.AttInterCellLB.M WRFD-020103 Inter Frequency Load

ultiRL Balance

BSC6900 UMTS
VS.HHO.AttInterFreqOut.C WRFD-020302 Inter Frequency Hard

S WRFD-020304 Handover Based on
Coverage
VS.HHO.AttInterFreqOut.P WRFD-020302 Inter Frequency Hard

Coverage
VS.HHO.AttInterFreqOut.Si WRFD-020302 Inter Frequency Hard

g WRFD-020304 Handover Based on
Coverage
1.12.11.4 Number of Incoming Hard Handover Attempts
Counters
67180565 VS.HHO.AttIn Number of Incoming Hard

Handover Attempts for Cell
67183912 VS.HHO.AttInterFreqIn Number of Incoming Inter-

Attempts for Cell
73403768 VS.HHO.AttInterFreqIn.CS Number of Requests for CS

Incoming Inter-Frequency
73403769 VS.HHO.AttInterFreqIn.PS Number of Requests for PS

Description
These counters provide the number of incoming hard handover attempts. The measurement is
performed in the target cell in the RNC.

BSC6900 UMTS
VS.HHO.AttIn Number of incoming intra-frequency and

inter-frequency hard handover attempts
(including CS and PS)
VS.HHO.AttInterFreqIn Number of incoming inter-frequency hard

handover attempts(including CS and PS)
VS.HHO.AttInterFreqIn.CS Number of Requests for CS Incoming Inter-

Frequency Hard Handovers
VS.HHO.AttInterFreqIn.PS Number of Requests for PS Incoming Inter-

Measurement point
The measurement is triggered at point B as shown in the figure, taking the PHYSICAL
CHANNEL RECONFIGURATION message as an example. When the hard handover decision
conditions are met, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION
message to the UE and measures the counter in the target cell of the hard handover.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.AttIn WRFD-020301 Intra Frequency Hard


Handover Based on
Coverage
VS.HHO.AttInterFreqIn WRFD-020302 Inter Frequency Hard

Coverage
VS.HHO.AttInterFreqIn.CS WRFD-020302 Inter Frequency Hard

Coverage
VS.HHO.AttInterFreqIn.PS WRFD-020302 Inter Frequency Hard

Coverage
1.12.11.5 Number of Outgoing Inter-Band Hard Handover Attempts for Different

Services
Counters
67193565 VS.HHO.AttMultiBandOut. Number of CS Outgoing

CS Inter-Band Hard Handover
Attempts for Cell

BSC6900 UMTS
67192567 VS.HHO.AttMultiBandOut. Number of PS Outgoing

PS Inter-Band Hard Handover
Attempts for Cell
Description
These counters provide the number of CS and PS services 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
CHANNEL RECONFIGURATION message as an example. The RNC performs hard handover
for 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 according to the
service types in the best cell where the UE camps on before the hard handover.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.HHO.AttMultiBandOut. WRFD-020110 Multi Frequency Band

CS Networking Management
VS.HHO.AttMultiBandOut. WRFD-020110 Multi Frequency Band

PS Networking Management
1.12.11.6 Number of Outgoing Emergency Blind Handover Attempts
Counters
67191694 VS.HHO.AttBlindHO Number of Outgoing

Emergency Blind Handover
Attempts for Cell
Description
This counter provides the number of outgoing emergency blind handover attempts initiated by
the RNC. The measurement is performed in the best cell where the UE camps on before the
handover.
Measurement point
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.AttBlindHO WRFD-020302 Inter Frequency Hard

Handover Based on
Coverage
1.12.11.7 Counters Related to the Number of Outgoing Inter-Frequency Hard

Handover Attempts

BSC6900 UMTS
Counters
73393934 VS.HHO.AttInterFreqOut.P Number of PS Inter-

S.UlBler Frequency Hard Handover
Attempts Based on UL
BLER for Cell
67193401 VS.HHO.AttInterFreqOut.C Number of CS Inter-

S.TrigRscp Frequency Hard Handover
Attempts Based on RSCP for
Cell

S.TrigEcNo Frequency Hard Handover
Attempts Based on EcNo for
Cell

S.TrigRscp Frequency Hard Handover
Attempts Based on RSCP for
Cell

S.TrigEcNo Frequency Hard Handover
Attempts Based on EcNo for
Cell

S.UeTxPwr Frequency Hard Handover
Attempts Based on UE
Transmit Power for Cell

S.UeTxPwr Frequency Hard Handover
Attempts Based on UE

S.Tcp Frequency Hard Handover
Attempts Based on DL

S.Tcp Frequency Hard Handover
Attempts Based on DL

S.TotalTxPwr Frequency Hard Handover
Attempts Based on Cell Total

BSC6900 UMTS

S.TotalTxPwr Frequency Hard Handover

S.TotalRxPwr Frequency Hard Handover
Receive Power for Cell

S.TotalRxPwr Frequency Hard Handover
Receive Power for Cell

S.Code Frequency Hard Handover
Attempts Based on Code
Resources for Cell

S.Code Frequency Hard Handover
Attempts Based on Code
Resources for Cell

S.UlCE Frequency Hard Handover
Attempts Based on UL CE
for Cell

S.DlCE Frequency Hard Handover
Attempts Based on DL CE
for Cell

S.DlCE Frequency Hard Handover
Attempts Based on DL CE
for Cell

S.UlCE Frequency Hard Handover
Attempts Based on UL CE
for Cell
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.

BSC6900 UMTS
Measurement point
The measurements can be triggered at point A as shown in the figure, taking the PHYSICAL
CHANNEL RECONFIGURATION message as an example. When the RNC sends the UE a
PHYSICAL CHANNEL RECONFIGURATION message, the corresponding counter is
measured in the best cell that the UE camps on before the handover based on the handover cause
and the service type. Note: 1. If an inter-frequency hard handover is triggered due to high BLER,
and the transmit power of the UE is also limited. In this case, both the counter related to the
number of inter-frequency hard handover attempts based on UL BLER and the counter related
to the number of inter-frequency hard handover attempts based on transmit power are measured.
2. The UL and DL power-triggered LDR inter-frequency hard handovers include the UL and
DL inter-frequency hard handovers triggered based on the equivalent user number respectively.
Figure 1-459 Handover Indication
Formula
None
Unit
None
Related Features

S.UlBler Handover Based on DL QoS

S.TrigRscp Handover Based on
Coverage

BSC6900 UMTS

S.TrigEcNo Handover Based on
Coverage

S.TrigRscp Handover Based on
Coverage

S.TrigEcNo Handover Based on
Coverage

S.UeTxPwr Handover Based on DL QoS

S.UeTxPwr Handover Based on DL QoS

S.Tcp Handover Based on DL QoS

S.Tcp Handover Based on DL QoS
VS.HHO.AttInterFreqOut.C WRFD-020106 Load Reshuffling

S.TotalTxPwr WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold
VS.HHO.AttInterFreqOut.P WRFD-020106 Load Reshuffling

S.TotalTxPwr WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold

S.TotalRxPwr WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold

S.TotalRxPwr WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold

BSC6900 UMTS

S.Code WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold

S.Code WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold

S.UlCE WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold
VS.HHO.AttInterFreqOut.P WRFD-140217 Inter-Frequency Load

S.DlCE Balancing Based on
Configurable Load
Threshold
VS.HHO.AttInterFreqOut.C WRFD-140217 Inter-Frequency Load

S.DlCE Balancing Based on
Configurable Load
Threshold
VS.HHO.AttInterFreqOut.C WRFD-140217 Inter-Frequency Load

S.UlCE Balancing Based on
Configurable Load
Threshold
1.12.11.8 Number of Outgoing Macro & Micro Joint Inter-frequency Handover

Attempts in PS Domain for Cell
Counters
73425831 VS.HHO.AttInterFreqOut.P Number of Outgoing Macro

S.CoMacroMicro & Micro Joint Inter-
frequency Handover
Attempts in PS Domain for
Cell

BSC6900 UMTS
Description
This counter measures the number of outgoing macro & micro joint inter-frequency handover
attempts in the PS domain in a cell.
Measurement point
In the figure 1, Both SHO and Non-SHO areas are macro & micro joint inter-frequency handover
area.
Figure 1-460 Macro and micro joint inter-frequency handover area
The measurement is triggered at point A as shown in Figure 2. When the RNC determines that
a UE is in the Macro & Micro joint inter-frequency handover area, it triggers a Macro & Micro
joint inter-frequency handover and sends the UE a PHYSICAL CHANNEL
RECONFIGURATION message. In this case, the counter is measured in the best cell where the
UE camps on before the hard handover.
Figure 1-461 Successful physical channel reconfiguration procedure

BSC6900 UMTS
This measurement is triggered at point A in figure 3. The RNC determines that a UE is in the
macro & micro joint inter-frequency handover area and triggers a macro & micro joint inter-
frequency handover. This counter is increased by one in the serving cell where the UE camps
each time the RNC sends a TRANSPORT CHANNEL RECONFIGURATION message to the
UE.
Figure 1-462 Successful transport channel reconfiguration procedure
This measurement is triggered at point A in figure 4. The RNC determines that a UE is in the
each time the RNC sends a RADIO BEARER RECONFIGURATION message to the UE.
Figure 1-463 Successful radio bearer reconfiguration procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.AttInterFreqOut.P WRFD-150201 Macro & Micro Co-carrier

S.CoMacroMicro WRFD-15020102 Uplink Interference Control
Macro & Micro Joint Inter-
frequency Handover
1.12.11.9 Number of Outgoing Hard Handover Attempts in NodeB
Counters
67180585 VS.HHO.AttIntraFreqOut.In Number of Outgoing Intra-

traNodeB Frequency Hard Handover
Attempts in NodeB for Cell
67190877 VS.HHO.AttInterFreqOut.In Number of Outgoing Inter-

traNodeB Frequency Hard Handover
Attempts in NodeB for Cell
Description
These counter provides the number of outgoing intra-frequency and 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 intra-frequency hard handover in the NodeB, the best source cell and the target
cell must belong to the same NodeB and use the same frequency.
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 and use the different frequency.
Measurement point
CHANNEL RECONFIGURATION message as an example. The RNC performs intra-
frequency or inter-frequency hard handover if the criteria of the decision to perform the hard
handover are fulfilled, and then sends the PHYSICAL CHANNEL RECONFIGURATION

BSC6900 UMTS
message to the UE. If the best cell before the hard handover and target cell belong to the same
NodeB, the RNC measures this counter in the best cell where the UE camps on before the hard
handover according to whether the source best cell and target cell in the same frequency.
Formula
None
Unit
None
Related Features
VS.HHO.AttIntraFreqOut.In WRFD-020301 Intra Frequency Hard

traNodeB Handover
VS.HHO.AttInterFreqOut.In WRFD-020302 Inter Frequency Hard

traNodeB WRFD-020304 Handover Based on
Coverage

BSC6900 UMTS
1.12.11.10 Number of Successful Outgoing Hard Handovers in NodeB
Counters
67180586 VS.HHO.SuccIntraFreqOut. Number of Successful

IntraNodeB Outgoing Intra-Frequency
Hard Handovers in NodeB
for Cell
67190878 VS.HHO.SuccInterFreqOut. Number of Successful

IntraNodeB Outgoing Inter-Frequency
Hard Handovers in NodeB
for Cell
Description
These counter provides the number of successful outgoing intra-frequency and inter-frequency
hard handover 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 and use the same frequency.
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 and use the different frequency.
Measurement point
frequency or inter-frequency hard handover if the criteria of the decision to perform hard
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, the RNC measures
this counter in the best cell where the UE camps on before the hard handover according to
whether the source best cell and target cell in the same frequency.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.SuccIntraFreqOut. WRFD-020301 Intra Frequency Hard

IntraNodeB Handover
VS.HHO.SuccInterFreqOut. WRFD-020302 Inter Frequency Hard

IntraNodeB WRFD-020304 Handover Based on
Coverage

BSC6900 UMTS
1.12.11.11 Number of Outgoing Hard Handover Attempts Between Different

NodeBs of RNC
Counters

terNodeBIntraRNC Frequency Hard Handover
Attempts Between Different
NodeBs of RNC for Cell

terNodeBIntraRNC Frequency Hard Handovers
Attempts Between Different
NodeBs of RNC for Cell
Description
These counters provide the number of outgoing intra-frequency and 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 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
and use the different frequency.
In the case of intra-frequency hard handover attempts between different NodeBs of the same
and use the same frequency.
Measurement point
message to the UE. If the best cell before the hard handover and target cell belong to different
NodeBs of the same RNC, the RNC measures this counter in the best cell where the UE camps
on before the hard handover according to whether the source best cell and target cell in the same
frequency.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

terNodeBIntraRNC Handover

terNodeBIntraRNC WRFD-020304 Handover Based on
Coverage

BSC6900 UMTS
1.12.11.12 Number of Successful Outgoing Hard Handovers Between Different

NodeBs of RNC
Counters

InterNodeBIntraRNC Outgoing Intra-Frequency
Hard Handovers Between
Different NodeBs of RNC for
Cell

InterNodeBIntraRNC Outgoing Inter-Frequency
Different NodeBs of RNC for
Cell
Description
These counters provide the number of successful outgoing intra-frequency and 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 attempts between different NodeBs of the same
and use the different frequency.
In the case of intra-frequency hard handover attempts between different NodeBs of the same
and use the same frequency.
Measurement point
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,
the RNC measures this counter in the best cell where the UE camps on before the hard handover
according to whether the source best cell and target cell in the same frequency.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

InterNodeBIntraRNC Handover

InterNodeBIntraRNC WRFD-020304 Handover Based on
Coverage
1.12.11.13 Number of Outgoing Hard Handover Attempts Between RNCs

BSC6900 UMTS
Counters

terRNC Frequency Hard Handover
Attempts Between RNCs for
Cell

terRNC Frequency Hard Handovers
Attempts Between RNCs for
Cell
Description
These counters provide the number of outgoing intra-frequency and inter-frequency hard
handover attempts between the RNCs. The measurement is performed in the best cell where the
In the case of intra-frequency hard handover between the RNCs, the source cell and the target
cell must belong to different RNCs and use the same frequency, the handover is performed
through the Iur interface between the RNCs.
In the case of inter-frequency hard handover between the RNCs, the source cell and the target
cell must belong to different RNCs and use the different frequency, the handover is performed
Measurement point
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, the SRNC measures this counter in the best cell where
the UE camps on before the hard handover according to whether the source best cell and target
cell in the same frequency.

BSC6900 UMTS
Figure 1-468 Hard handover procedure (between different RNCs)
Formula
None
Unit
None
Related Features

terRNC Handover

terRNC WRFD-020304 Handover Based on
Coverage
1.12.11.14 Number of Successful Outgoing Hard Handovers Between RNCs

BSC6900 UMTS
Counters

InterRNC Outgoing Intra-Frequency
RNCs for Cell

InterRNC Outgoing Inter-Frequency
RNCs for Cell
Description
These counters provide the number of successful outgoing intra-frequency and inter-frequency
hard handovers between the RNCs. The measurement is performed in the best cell where the
In the case of intra-frequency hard handover between the RNCs, the source cell and the target
cell must belong to different RNCs and use the same frequency, the handover is performed
In the case of inter-frequency hard handover between the RNCs, the source cell and the target
cell must belong to different RNCs and use the different frequency, the handover is performed
Measurement point
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, the SRNC measures this counter
in the best cell where the UE camps on before the hard handover according to whether the source
best cell and target cell in the same frequency.

BSC6900 UMTS
Figure 1-469 Hard handover procedure (between different RNCs)
Formula
None
Unit
None
Related Features

InterRNC Handover

InterRNC WRFD-020304 Handover Based on
Coverage
1.12.11.15 Number of Successful Outgoing Inter-Frequency Hard Handovers

BSC6900 UMTS
Counters
67183901 VS.HHO.SuccInterFreqOut Number of Successful

Outgoing Inter-Frequency
67180550 VS.HHO.SuccInterCellLB.S Number of Successful

ingleRL Outgoing Inter-Frequency
Hard Handovers Due to Load
Balancing for Cell (Single
RL)
67193710 VS.HHO.SuccInterCellLB. Number of Successful

MultiRL Outgoing Inter-Frequency
Hard Handovers Due to Load
Balancing for Cell (Multiple
RLs)
73403774 VS.HHO.SuccInterFreqOut. Number of Successful for CS

CS Outgoing Inter-Frequency
73403775 VS.HHO.SuccInterFreqOut. Number of Successful for PS

PS Outgoing Inter-Frequency
73425015 VS.HHO.SuccInterFreqOut. Number of Successful Inter-

Sig Frequency Hard Handover
Attempts When only
Signaling Exists for Cell
Description
These counters provide 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.
VS.HHO.SuccInterFreqOut Number of successful outgoing inter-

VS.HHO.SuccInterCellLB.SingleRL Number of successful outgoing inter-

frequency hard handovers due to the load
balancing in single RL
VS.HHO.SuccInterCellLB.MultiRL Number of successful outgoing inter-

frequency hard handovers due to the load
balancing in Multiple RLs

BSC6900 UMTS
VS.HHO.SuccInterFreqOut.CS Number of successful for CS Outgoing inter-

VS.HHO.SuccInterFreqOut.PS Number of successful for PS Outgoing inter-

VS.HHO.SuccInterFreqOut.Sig Number of successful outgoing inter-

frequency hard handover when the UE has
only signalling
Measurement point
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 according to service types and the number of RL in the best cell where the UE camps

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.SuccInterFreqOut WRFD-020302 Inter Frequency Hard

Coverage
WRFD-020106
Load Reshuffling
VS.HHO.SuccInterCellLB.S WRFD-020103 Inter Frequency Load

ingleRL Balance
VS.HHO.SuccInterCellLB. WRFD-020103 Inter Frequency Load

MultiRL Balance

CS WRFD-020304 Handover Based on
Coverage

PS WRFD-020304 Handover Based on
Coverage

Sig WRFD-020304 Handover Based on
Coverage
1.12.11.16 Number of Successful Outgoing Inter-Band Hard Handovers for

Different Services

BSC6900 UMTS
Counters
67193566 VS.HHO.SuccMultiBandOu Number of Successful CS

t.CS Outgoing Inter-Band Hard
Handovers for Cell
67192568 VS.HHO.SuccMultiBandOu Number of Successful PS

t.PS Outgoing Inter-Band Hard
Handovers for Cell
Description
These counters provide the number of successful CS and PS services outgoing inter-band hard
handovers. The measurement is performed in the best cell where the UE camps on before the
hard handover.
Measurement point
CHANNEL RECONFIGURATION message as an example. The RNC performs hard handover
for 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 according to service types in the best cell where the UE
camps on before the hard handover.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.SuccMultiBandOu WRFD-020110 Multi Frequency Band

t.CS Networking Management
VS.HHO.SuccMultiBandOu WRFD-020110 Multi Frequency Band

t.PS Networking Management
1.12.11.17 Number of Successful Outgoing Emergency Blind Hard Handovers
Counters
67191695 VS.HHO.SuccBlindHO Number of Successful

Outgoing Emergency Blind
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
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.SuccBlindHO WRFD-020302 Inter Frequency Hard

Handover Based on
Coverage
1.12.11.18 Counters Related to the Number of Successful Outgoing Inter-Frequency

Hard Handovers

BSC6900 UMTS
Counters
73393945 VS.HHO.SuccInterFreqOut. Number of Successful PS

PS.UlBler Inter-Frequency Hard
Handovers Based on UL
BLER for Cell
73404081 VS.HHO.SuccInterFreqOut. Number of Successful CS

CS.Rscp Inter-Frequency Hard
Handovers Based on RSCP
for Cell

CS.EcNo Inter-Frequency Hard
Handovers Based on EcNo
for Cell

PS.Rscp Inter-Frequency Hard
Handovers Based on RSCP
for Cell

PS.EcNo Inter-Frequency Hard
Handovers Based on EcNo
for Cell

CS.UeTxPwr Inter-Frequency Hard
Handovers Based on UE

PS.UeTxPwr Inter-Frequency Hard
Handovers Based on UE

CS.Tcp Inter-Frequency Hard
Handovers Based on DL

PS.Tcp Inter-Frequency Hard
Handovers Based on DL

CS.TotalTxPwr Inter-Frequency Hard
Handovers Based on Cell
Total Transmit Power for
Cell

BSC6900 UMTS

PS.TotalTxPwr Inter-Frequency Hard
Total Transmit Power for
Cell

CS.TotalRxPwr Inter-Frequency Hard
Total Receive Power for Cell

PS.TotalRxPwr Inter-Frequency Hard
Total Receive Power for Cell

CS.Code Inter-Frequency Hard
Handovers Based on Code
Resources for Cell

PS.Code Inter-Frequency Hard
Handovers Based on Code
Resources for Cell

PS.UlCE Inter-Frequency Hard
Handovers Based on UL CE
for Cell

PS.DlCE Inter-Frequency Hard
Handovers Based on DL CE
for Cell

CS.UlCE Inter-Frequency Hard
Handovers Based on UL CE
for Cell

CS.DlCE Inter-Frequency Hard
Handovers Based on DL CE
for Cell
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.

BSC6900 UMTS
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.
Figure 1-473 Handover Indication
Formula
None
Unit
None

BSC6900 UMTS
Related Features

PS.UlBler Handover Based on DL QoS

CS.Rscp Handover Based on
Coverage

CS.EcNo Handover Based on
Coverage

PS.Rscp Handover Based on
Coverage

PS.EcNo Handover Based on
Coverage

CS.UeTxPwr Handover Based on DL QoS

PS.UeTxPwr Handover Based on DL QoS

CS.Tcp Handover Based on DL QoS

PS.Tcp Handover Based on DL QoS
VS.HHO.SuccInterFreqOut. WRFD-020106 Load Reshuffling

CS.TotalTxPwr WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold

PS.TotalTxPwr WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold

CS.TotalRxPwr WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold

BSC6900 UMTS

PS.TotalRxPwr WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold

CS.Code WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold

PS.Code WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold

PS.UlCE WRFD-140217 Inter-Frequency Load
Balancing Based on
Configurable Load
Threshold
VS.HHO.SuccInterFreqOut. WRFD-140217 Inter-Frequency Load

PS.DlCE Balancing Based on
Configurable Load
Threshold

CS.UlCE Balancing Based on
Configurable Load
Threshold

CS.DlCE Balancing Based on
Configurable Load
Threshold
1.12.11.19 Number of Successful Outgoing Macro & Micro Joint Inter-frequency

Handovers in PS Domain for Cell

BSC6900 UMTS
Counters

PS.CoMacroMicro Outgoing Macro & Micro
Joint Inter-frequency
Handovers in PS Domain for
Cell
Description
This counter measures the number of successful outgoing macro & micro joint inter-frequency
handovers in the PS domain in a cell.
Measurement point
In the figure 1, Both SHO and Non-SHO areas are macro & micro joint inter-frequency handover
area.
Figure 1-474 Macro and micro joint inter-frequency handover area
This measurement is triggered at point B in figure 2. The RNC determines that a UE is in the
each time the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE
in the target cell after sending a PHYSICAL CHANNEL RECONFIGURATION message to
the UE.

BSC6900 UMTS
Figure 1-475 Successful physical channel reconfiguration procedure
before the handover each time the RNC receives a TRANSPORT CHANNEL
RECONFIGURATION COMPLETE in the target cell after sending a TRANSPORT
CHANNEL RECONFIGURATION message to the UE.
Figure 1-476 Successful transport channel reconfiguration procedure
before the handover each time the RNC receives a RADIO BEARER RECONFIGURATION

BSC6900 UMTS
COMPLETE in the target cell after sending a RADIO BEARER RECONFIGURATION

message to the UE.
Figure 1-477 Successful radio bearer reconfiguration procedure
Formula
None
Unit
None
Related Features
VS.HHO.SuccInterFreqOut. WRFD-150201 Macro & Micro Co-carrier

PS.CoMacroMicro WRFD-15020102 Uplink Interference Control
Macro & Micro Joint Inter-
frequency Handover
1.12.11.20 Number of Successful Incoming Hard Handovers

BSC6900 UMTS
Counters
67180566 VS.HHO.SuccIn Number of Successful

Incoming Hard Handovers in
the RNC for Cell
67183913 VS.HHO.SuccInterFreqIn Number of Successful

73403772 VS.HHO.SuccInterFreqIn.C Number of Successful for CS

S Incoming Inter-Frequency
73403773 VS.HHO.SuccInterFreqIn.P Number of Successful for PS

S Incoming Inter-Frequency
Description
These counters provide the number of successful incoming hard handovers. The measurement
is performed in the target cell in the RNC.
VS.HHO.SuccIn Number of successful incoming intra-

frequency and inter-frequency hard handover
(including CS and PS)
VS.HHO.SuccInterFreqIn Number of successful incoming inter-

frequency hard handovers(including CS and
PS)
VS.HHO.SuccInterFreqIn.CS Number of successful CS incoming inter-

VS.HHO.SuccInterFreqIn.PS Number of successful PS incoming inter-

Measurement point
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.SuccIn WRFD-020301 Intra Frequency Hard


Handover Based on
Coverage

BSC6900 UMTS
VS.HHO.SuccInterFreqIn WRFD-020302 Inter Frequency Hard

Coverage
VS.HHO.SuccInterFreqIn.C WRFD-020302 Inter Frequency Hard

Coverage
VS.HHO.SuccInterFreqIn.P WRFD-020302 Inter Frequency Hard

Coverage
1.12.11.21 Number of Failed Outgoing Hard Handovers Between RNCs for

Different Causes
Counters
67189701 VS.HHO.FailIntraFreqOut.I Number of Failed Outgoing

nterRNC.CfgUnsupp Intra-Frequency Hard
Handovers Between RNCs
for Cell (Configuration
Unsupported)

nterRNC.PhyChFail Intra-Frequency Hard
for Cell (Physical Channel
Failure)

nterRNC.ISR Intra-Frequency Hard
for Cell (Incompatible
Simultaneous
Reconfiguration)

BSC6900 UMTS

nterRNC.InvCfg Intra-Frequency Hard
for Cell (Invalid
Configuration)
73393853 VS.HHO.FailInterFreqOut.I Number of Failed Outgoing

nterRNC.CfgUnsupp Inter-Frequency Hard
Handovers Between the
RNCs for Cell
(Configuration
Unsupported)

nterRNC.PhyChFail Inter-Frequency Hard
RNCs for Cell (Physical
Channel Failure)

nterRNC.ISR Inter-Frequency Hard
RNCs for Cell (Incompatible
Simultaneous
Reconfiguration)

nterRNC.InvCfg Inter-Frequency Hard
RNCs for Cell (Invalid
Configuration)
Description
These counters provide the number of failed outgoing intra-frequency and inter-frequency hard
handovers between the RNCs due to different failure causes. The measurements are performed
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 and 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 intra-frequency or inter-
frequency 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.

BSC6900 UMTS
Figure 1-479 Failed hard handover procedure
Formula
None
Unit
None
Related Features
VS.HHO.FailIntraFreqOut.I WRFD-020301 Intra Frequency Hard

nterRNC.CfgUnsupp Handover

nterRNC.PhyChFail Handover

nterRNC.ISR Handover

nterRNC.InvCfg Handover
VS.HHO.FailInterFreqOut.I WRFD-020302 Inter Frequency Hard

nterRNC.CfgUnsupp WRFD-020304 Handover Based on
Coverage

BSC6900 UMTS

nterRNC.PhyChFail WRFD-020304 Handover Based on
Coverage

nterRNC.ISR WRFD-020304 Handover Based on
Coverage

nterRNC.InvCfg WRFD-020304 Handover Based on
Coverage
1.12.11.22 Number of Failed Outgoing Hard Handovers Between the RNCs Due to
No Response from the UE
Counters

nterRNC.NoReply Intra-Frequency Hard
RNCs Due to No Response
from the UE for Cell

nterRNC.NoReply Inter-Frequency Hard
RNCs Due to No Response
from the UE for Cell
Description
handovers between the RNCs due to no response from the UE. The measurement is performed

BSC6900 UMTS
Measurement point
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, the SRNC measures this counter
in the best cell where the UE camps on before the intra-frequency or inter-frequency hard
handover.
Figure 1-480 Failed hard handover procedure (UE no response)
Formula
None
Unit
None
Related Features

nterRNC.NoReply Handover

BSC6900 UMTS

nterRNC.NoReply WRFD-020304 Handover Based on
Coverage
1.12.11.23 Number of Failed Outgoing Inter-RNC Hard Handovers for Cell

(Concurrent Procedures)
Counters

nterRNC.CellUpdt Intra-Frequency Hard
for Cell (Cell update
occurred)

nterRNC.CellUpdt Inter-Frequency Hard
RNCs for Cell (Cell Update
Occurred)
Description
These counters provide the number of failed outgoing hard handovers due to concurrence of the
inter-RNC outgoing intra-frequency and inter-frequency hard handover procedure with cell
update procedure.
Measurement point
The measurements are triggered at point A as shown in the following figure, which uses the
PHYSICAL CHANNEL RECONFIGURATION message as an example. During an inter-RNC
intra-frequency or inter-frequency hard handover, when the RNC receives a PHYSICAL
CHANNEL RECONFIGURATION FAILURE message from the UE, the intra-frequency or
inter-frequency hard handover procedure and cell update procedure are performed concurrently.
As a result, the hard handover fails. In this case, If the best cell before the hard handover and
the target cell are controlled by the SRNC and the DRNC respectively, the SRNC measures this
counter in the best cell where the UE camps on before the intra-frequency or inter-frequency
hard handover.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

nterRNC.CellUpdt Handover

nterRNC.CellUpdt WRFD-020304 Handover Based on
Coverage
1.12.11.24 Number of Failed Outgoing Hard Handovers in RNC for Different

Causes

BSC6900 UMTS
Counters
67192558 VS.HHO.FailIntraFreqOut. Number of Failed Outgoing

CfgUnsupp Intra-Frequency Hard
Handovers for Cell
(Configuration
Unsupported)

nvCfg Intra-Frequency Hard
Handovers for Cell (Invalid
Configuration)
67192559 VS.HHO.FailIntraFreqOut.P Number of Failed Outgoing

yhChFail Intra-Frequency Hard
Handovers for Cell (Physical
Channel Failure)

SR Intra-Frequency Hard
Handovers for Cell
(Incompatible Simultaneous
Reconfiguration)
67183902 VS.HHO.FailInterFreqOut. Number of Failed Outgoing

CfgUnsupp Inter-Frequency Hard
Handovers for Cell
(Configuration
Unsupported)
67183903 VS.HHO.FailInterFreqOut.P Number of Failed Outgoing

yhChFail Inter-Frequency Hard
Channel Failure)

SR Inter-Frequency Hard
Handovers for Cell
(Incompatible Simultaneous
Reconfiguration)

nvCfg Inter-Frequency Hard
Handovers for Cell (Invalid
Configuration)
Description
handovers in RNC due to different failure causes. The measurements are performed in the best
cell where the UE camps on before the hard handover.

BSC6900 UMTS
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 and inter-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 or inter-
frequencyhard handover according to the failure cause contained in the message.
Formula
None
Unit
None
Related Features
VS.HHO.FailIntraFreqOut. WRFD-020301 Intra Frequency Hard

CfgUnsupp Handover

nvCfg Handover
VS.HHO.FailIntraFreqOut.P WRFD-020301 Intra Frequency Hard

yhChFail Handover

SR Handover

BSC6900 UMTS
VS.HHO.FailInterFreqOut. WRFD-020302 Inter Frequency Hard

CfgUnsupp WRFD-020304 Handover Based on
Coverage
VS.HHO.FailInterFreqOut.P WRFD-020302 Inter Frequency Hard

yhChFail WRFD-020304 Handover Based on
Coverage

SR WRFD-020304 Handover Based on
Coverage

nvCfg WRFD-020304 Handover Based on
Coverage
1.12.11.25 Number of Failed Outgoing Hard Handovers in RNC Due to No

Response from the UE
Counters

NoReply Intra-Frequency Hard
Handovers Due to No
Response from the UE for
Cell

NoReply Inter-Frequency Hard
Handovers Due to No
Response from the UE for
Cell

BSC6900 UMTS
Description
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
inter-frequencyhard 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 or inter-frequency hard handover.
Figure 1-483 Failed hard handover procedure (UE no response)
Formula
None
Unit
None
Related Features

NoReply Handover

BSC6900 UMTS

NoReply WRFD-020304 Handover Based on
Coverage
1.12.11.26 Number of Failed Outgoing Intra-RNC Hard Handovers for Cell

Counters

CellUpdt Intra-Frequency Hard
Handovers for Cell (Cell
Update Occurred)

CellUpdt Inter-Frequency Hard
Handovers for Cell (Cell
Update Occurred)
Description
These counters provide the number of failed outgoin hard handovers due to concurrence of the
intra-RNC outgoing intra-frequency and inter-frequency hard handover procedure with cell
update procedure.
Measurement point
The measurements are triggered at point A as shown in the following figure, which uses the
PHYSICAL CHANNEL RECONFIGURATION message as an example. During an inter-RNC
intra-frequency or inter-frequency hard handover, when the RNC receives a PHYSICAL
CHANNEL RECONFIGURATION FAILURE message from the UE, the intra-frequency or
inter-frequency hard handover procedure and cell update procedure are performed concurrently.
As a result, the hard handover fails. In this case, the RNC measures the related counters in the
best cell where the UE camps on before the intra-frequency or inter-frequency hard handover.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

CellUpdt Handover

CellUpdt WRFD-020304 Handover Based on
Coverage
1.12.11.27 Number of Call Drops due to Unsuccessful Outgoing Hard Handovers

for cell

BSC6900 UMTS
Counters
73403776 VS.HHO.InterFreqOut.CS. Number of CS Call Drops

Drop due to Unsuccessful
Hard Handovers for cell
67183926 VS.HHO.IntraFreqOut.Drop Number of Call Drops Due to

Failed Outgoing Intra-
for Cell
73403777 VS.HHO.InterFreqOut.PS.D Number of PS Call Drops due

rop to Unsuccessful Outgoing
Inter-Frequency Hard
Handovers for cell
Description
The measurement items take statistics of call drops due to unsuccessful intra-frequency and
inter-frequency hard handovers.
VS.HHO.IntraFreqOut.Drop number of call drops due to failed outgoing

intra-frequency hard handovers(including CS
and PS)
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 and
intra-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 hard handover.

BSC6900 UMTS
Figure 1-485 Hard handover procedure (failed operation)
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 and
intra-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
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 or intra-frequency hard handover.
Figure 1-486 Hard handover procedure (failed operation for timer expiry)
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.HHO.InterFreqOut.CS. WRFD-020302 Inter Frequency Hard

Drop WRFD-020304 Handover Based on
Coverage
VS.HHO.IntraFreqOut.Drop WRFD-020301 Intra Frequency Hard

Handover
VS.HHO.InterFreqOut.PS.D WRFD-020302 Inter Frequency Hard

rop WRFD-020304 Handover Based on
Coverage
1.12.11.28 Number of Failed Preparations for Outgoing Hard Handovers Due to

Radio Link Establishment Failure
Counters
67192556 VS.HHO.FailIntraFreqOut. Number of Failed

RLSetupFail Preparations for Outgoing
Intra-Frequency Hard
Handovers Due to Radio
Link Establishment Failure
for Cell
67192557 VS.HHO.FailInterFreqOut. Number of Failed

RLSetupFail Preparations for Outgoing
Handovers Due to Radio
Link Establishment Failure
for Cell

BSC6900 UMTS
Description
These counters provide the number of failed preparations for outgoing intra-frequency and 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
CHANNEL RECONFIGURATION message as an example. The RNC initiates the request for
an intra-frequency or inter-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-487 Failed hard handover procedure (failure in the RL establishment on the Iub
interface)
CHANNEL RECONFIGURATION message as an example. The RNC initiates the request for
an intra-frequency or inter-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.

BSC6900 UMTS
Figure 1-488 Failed hard handover procedure (failure in the RL establishment on the Iur
interface)
Formula
None
Unit
None
Related Features

RLSetupFail Handover

RLSetupFail WRFD-020304 Handover Based on
Coverage
1.12.11.29 Number of Failed Preparations for Outgoing Hard Handovers

BSC6900 UMTS
Counters
67192554 VS.HHO.FailIntraFreqOut.P Number of Failed

repFail Preparations for Outgoing
Handovers for Cell
67192555 VS.HHO.FailInterFreqOut.P Number of Failed

repFail Preparations for Outgoing
Handovers for Cell
Description
These counters provide the number of failed preparations for outgoing intra-frequency and inter-
frequency hard handovers. The measurement is performed in the best cell where the UE camps
Measurement point
The measurement is triggered at point A as shown in the figure, where the PHYSICAL
CHANNEL RECONFIGURATION message is used as an example. The RNC initiates a request
for an intra-frequency or inter-frequency hard handover if the criteria of the decision to perform
the handover are fulfilled. If the admission fails, this counter is increased by one in the best cell
that the UE camps on before the hard handover.
Figure 1-489 Failed hard handover procedure (admission fails)

BSC6900 UMTS
The measurement is triggered at point B as shown in the figure, where the PHYSICAL
CHANNEL RECONFIGURATION message is used as an example. The RNC initiates a request
for an intra-frequency or inter-frequency hard handover if the criteria of the decision to perform
the handover are fulfilled. If the preparation for the intra-frequency hard handover fails before
the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE, including
the failure in the RL establishment on the Iub and Iur interfaces, this counter is increased by one
in the best cell that the UE camps on before the hard handover.
Figure 1-490 Failed hard handover procedure (failure in the RL establishment on the Iur
interface)
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.HHO.FailIntraFreqOut.P WRFD-020301 Intra Frequency Hard

repFail Handover
VS.HHO.FailInterFreqOut.P WRFD-020302 Inter Frequency Hard

repFail WRFD-020304 Handover Based on
Coverage
1.12.11.30 Number of Relocation Preparation Attempts with Outgoing Hard

Handovers
Counters
67193708 VS.HHO.AttIntraFreqRe- Number of Relocation

locPrep Preparation Attempts with
Outgoing Intra-Frequency
67192551 VS.HHO.AttInterFreqRe- Number of Relocation

locPrep Preparation Attempts with
Description
These counters provide the number of relocation preparation attempts with outgoing intra-
frequency and inter-frequency hard handovers. The measurement is performed in the best cell
of the SRNC where the UE camps on.
Measurement point
preparation with outgoing intra-frequency or 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 the RELOCATION REQUIRED
message to both domains. In this case, the RNC measures the counter once only.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.AttIntraFreqRe- WRFD-02060502 SRNS Relocation with Hard

locPrep Handover
VS.HHO.AttInterFreqRe- WRFD-02060502 SRNS Relocation with Hard

locPrep Handover
1.12.11.31 Number of Successful Relocation Preparations with Outgoing Hard

Handovers
Counters
67192770 VS.HHO.SuccIntraFreqRe- Number of Successful

locPrep Relocation Preparations with

BSC6900 UMTS
67192552 VS.HHO.SuccInterFreqRe- Number of Successful

locPrep Relocation Preparations with
Description
These counters provide the number of successful relocation preparations with outgoing intra-
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 or 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

BSC6900 UMTS
Related Features
VS.HHO.SuccIntraFreqRe- WRFD-02060502 SRNS Relocation with Hard

locPrep Handover
VS.HHO.SuccInterFreqRe- WRFD-02060502 SRNS Relocation with Hard

locPrep Handover
1.12.11.32 Number of Relocation Execution Attempts with Outgoing Hard

Handovers
Counters
67189716 VS.HHO.AttIntraFreqRelo- Number of Relocation

cExec Execution Attempts with
67190898 VS.HHO.AttInterFreqRelo- Number of Relocation

cExec Execution Attempts with
Description
These counters provide the number of relocation execution attempts with outgoing intra-
controlled by the SRNC. In terms of relocation with outgoing intra-frequency or 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 hard handover must be controlled by different RNCs.
Measurement point
CHANNEL RECONFIGURATION message as an example. During the relocation with intra-
frequency or 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 according to whether the source best cell and target
cell in the same frequency. In this case, the best cell before the relocation and the target cell must
be controlled by the SRNC and the TRNC respectively.

BSC6900 UMTS
Figure 1-493 Reconfiguration procedure during SRNC relocation with hard handover
Formula
None
Unit
None
Related Features
VS.HHO.AttIntraFreqRelo- WRFD-02060502 SRNS Relocation with Hard

cExec Handover
VS.HHO.AttInterFreqRelo- WRFD-02060502 SRNS Relocation with Hard

cExec Handover
1.12.11.33 Number of Successful Relocation Executions with Outgoing Hard

Handovers

BSC6900 UMTS
Counters
67189717 VS.HHO.SuccIntraFreqRe- Number of Successful

locExec Relocation Executions with
67190899 VS.HHO.SuccInterFreqRe- Number of Successful

locExec Relocation Executions with
Description
These counters provide the number of successful relocation executions with outgoing intra-
controlled by the SRNC.
Measurement point
with intra-frequency or 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 according to whether
the source best cell and target cell in the same frequency. 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-494 Successful SRNC relocation procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HHO.SuccIntraFreqRe- WRFD-02060502 SRNS Relocation with Hard

locExec Handover
VS.HHO.SuccInterFreqRe- WRFD-02060502 SRNS Relocation with Hard

locExec Handover
1.12.11.34 Counters Related to the Number of Failed Relocation Preparations with

Outgoing Hard Handovers for Different Causes
Counters
67189708 HHO.FailRelocPrepOut.No Number of Failed Relocation

ResAvail Preparations with Outgoing
Hard Handovers for Cell (No
Radio Resources Available
in Target Cell)
67189709 HHO.FailRelocPrepOut.Tex Number of Failed Relocation

p Preparations with Outgoing
(TRELOCalloc Expiry)
67189710 HHO.FailRelocPrepOut.Tgt Number of Failed Relocation

Fail Preparations with Outgoing
(Relocation Failure in Target
CN/RNC or Target System)
67189711 HHO.FailRelocPrepOut.Re- Number of Failed Relocation

locUnsupp Preparations with Outgoing
System)

BSC6900 UMTS
67189712 HHO.FailRelocPrepOut.Tgt Number of Failed Relocation

NotAllow Preparations with Outgoing
Allowed)
67189713 HHO.FailRelocPrepOut.OM Number of Failed Relocation

Preparations with Outgoing
(O&M Intervention)
67189714 HHO.FailRelocPrepOut.Re- Number of Failed Relocation

sUnavail Preparations with Outgoing
Hard Handovers for Cell (No
Resource Available)
67189715 HHO.FailRelocPrepOut.Un- Number of Failed Relocation

spec Preparations with Outgoing
Description
These counters provide the number of failed relocation preparations with outgoing hard
handovers. The measurements are performed in the best cell where the UE camps on before the
hard handover.
Measurement point
The measurements are triggered at point A as shown in the following figure. During the
relocation preparation with outgoing hard handover, after receiving the RELOCATION
PREPARATION FAILURE message from the CN, the SRNC measures the related counters in
the best cell where the UE camps on before the hard handover according to the failure cause
contained in the message. In this case, the best cell must be controlled by the SRNC.
Figure 1-495 Failed SRNC relocation preparation procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
HHO.FailRelocPrepOut.No WRFD-02060502 SRNS Relocation with Hard

ResAvail Handover
HHO.FailRelocPrepOut.Tex WRFD-02060502 SRNS Relocation with Hard

p Handover
HHO.FailRelocPrepOut.Tgt WRFD-02060502 SRNS Relocation with Hard

Fail Handover
HHO.FailRelocPrepOut.Re- WRFD-02060502 SRNS Relocation with Hard

locUnsupp Handover
HHO.FailRelocPrepOut.Tgt WRFD-02060502 SRNS Relocation with Hard

NotAllow Handover
HHO.FailRelocPrepOut.OM WRFD-02060502 SRNS Relocation with Hard

Handover
HHO.FailRelocPrepOut.Re- WRFD-02060502 SRNS Relocation with Hard

sUnavail Handover
HHO.FailRelocPrepOut.Un- WRFD-02060502 SRNS Relocation with Hard

spec Handover
1.12.11.35 Counters Related to the Number of Handovers Not Performed Due to

Inter-Frequency Measurement Expiry
Counters
67193397 VS.HHO.InterFreqOut.CS. Number of Handovers Not

MeasTimeOut Performed Due to CS Inter-
Frequency Measurement
Expiry for Cell

BSC6900 UMTS
67193398 VS.HHO.InterFreqOut.PS. Number of Handovers Not

MeasTimeOut Performed Due to PS Inter-
Frequency Measurement
Expiry for Cell
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
None
Related Features
VS.HHO.InterFreqOut.CS. WRFD-020302 Inter Frequency Hard

MeasTimeOut WRFD-020304 Handover Based on
Coverage
VS.HHO.InterFreqOut.PS. WRFD-020302 Inter Frequency Hard

MeasTimeOut WRFD-020304 Handover Based on
Coverage

BSC6900 UMTS
1.12.12 HSDPA Measurement per cell(HSDPA.Cell)
Overview
High Speed Downlink Packet Access (HSDPA) is a DL high speed data solution of WCDMA.
The HSDPA system has the following features: Adopting 2 ms short frame, Adopting link
adaptive technologies such as HARQ and AMC on physical layer, Introducing high-order
modulation to increase spectrum utilization, Scheduling between UEs by code division and time
division. The above technologies can implement the following: Increasing DL peak data rate
and shortening service delay, Increasing DL throughput of such services as receiving Email and
browsing on WEB and Increasing DL capacity by effectively using DL code resource and power
resource. The function subset HSDPA Measurement(Cell) is used to measure the related HSDPA
service on the basis of Cell. This function subset contains counters related to the number of
successful or RRC connection setups, normal or abnormal RRC connection release, handovers,
and state transitions for HSDPA users of different capability levels, service delay, and
throughput.
Counters
Description
67189830 VS.HSDPA.D2H.S Number of Earlier than

ucc Successful Channel V900R011
Conversions from
DCH to HS-DSCH
for HSDPA Service
for Cell
67189831 VS.HSDPA.F2H.Su Number of Earlier than

cc Successful Channel V900R011
Conversions from
FACH to HS-DSCH
for HSDPA Service
for Cell
67189832 VS.HSDPA.H2D.S Number of Earlier than

ucc Successful Channel V900R011
Conversions from
HS-DSCH to DCH
for HSDPA Service
for Cell
67189833 VS.HSDPA.H2F.Su Number of Earlier than

Conversions from
HS-DSCH to FACH
for HSDPA Service
for Cell

BSC6900 UMTS

Description
67189834 VS.HSDPA.MACD Number of Earlier than

.SuccSetup Successful HSDPA V900R011
MAC-d Flow
Establishments for
Cell
67202932 VS.HSDPA.UE.Me Average Number of Earlier than

an.Cell HSDPA UEs in a V900R011
Cell
67202941 VS.HSDPA.MACD Average Number of Earlier than

.Mean.Cell MAC-d Flows in a V900R011
Cell
67202894 VS.HSDPA.Mean- Mean Downlink Earlier than

ChThroughput Throughput of single V900R011
HSDPA MAC-d
Flows for Cell
67189840 VS.HSDPA.MeanC Number of Total Earlier than

hThroughput.To- Bytes Sent in V900R011
talBytes Downlink of HSDPA
MAC-d Flow for
Cell

GoldenBeCh- Throughput of V900R011
Throughput HSDPA MAC-d
Flow of BE Service
for Golden
Subscriber for Cell
67194867 VS.HSDPA.MeanG Number of Total Earlier than

oldenBeChThroug Bytes Sent in V900R011
hput.TotalBytes Downlink of HSDPA
MAC-d Flow of BE
Service for Golden
Subscriber for Cell

SilverBeCh- Throughput of V900R011
Flow of BE Service
for Silver Subscriber
for Cell

BSC6900 UMTS

Description
67194869 VS.HSDPA.MeanS Number of Total Earlier than

ilverBeChThrough Bytes Sent in V900R011
put.TotalBytes Downlink of HSDPA
MAC-d Flow of BE
Service for Silver
Subscriber for Cell

CopperBeCh- Throughput of V900R011
Flow of BE Service
for Copper
Subscriber for Cell
67194871 VS.HSDPA.MeanC Number of Total Earlier than

opperBeChThroug Bytes Sent in V900R011
hput.TotalBytes Downlink of HSDPA
MAC-d Flow of BE
Service for Copper
Subscriber for Cell
67190690 VS.HSDPA.H2D.A Number of Channel Earlier than

tt Conversion V900R011
Attempts from HS-
DSCH to DCH for
HSDPA Service for
Cell
67190693 VS.HSDPA.D2H.A Number of Channel Earlier than

tt Conversion V900R011
Attempts from DCH
to HS-DSCH for
HSDPA Service for
Cell
67190696 VS.HSDPA.F2H.At Number of Channel Earlier than

t Conversion V900R011
Attempts from
FACH to HS-DSCH
for HSDPA Service
for Cell
67190697 VS.HSDPA.H2F.At Number of Channel Earlier than

Attempts from HS-
DSCH to FACH for
HSDPA Service for
Cell

BSC6900 UMTS

Description
67190698 VS.HSDPA.SHO.S Number of Intra- Earlier than

ervCellChg.AttOut RNC HSDPA V900R011
Serving Cell Change
Attempts for Cell
67190699 VS.HSDPA.SHO.S Number of Intra- Earlier than

ervCellChg.Suc- RNC HSDPA V900R011
cOut Serving Cell Change
Success in RNC for
Cell
67195481 VS.HSDPA.SHO.S Number of Inter- Earlier than

ervCellChg.AttOu- RNC HSDPA V900R011
tIur Serving Cell Change
Attempts for Cell
67195482 VS.HSDPA.SHO.S Number of Inter- Earlier than

ervCellChg.Suc- RNC HSDPA V900R011
cOutIur Serving Cell Change
Success for Cell
67195483 VS.HSDPA.HHO. Number of Inter- Earlier than

H2H.AttOutIur RNC HSDPA Hard V900R011
Handover Attempts
Without Channel
Change for Cell
67195484 VS.HSDPA.HHO. Number of Earlier than

H2H.SuccOutIur Successful Inter- V900R011
RNC HSDPA Hard
Handovers Without
Channel Change for
Cell
67190700 VS.HSDPA.HHO. Number of Intra- Earlier than

H2H.AttOutIntra- Frequency HSDPA V900R011
Freq Hard Handover
Attempts Without
Channel Change for
Cell

H2H.SuccOutIn- Successful Intra- V900R011
traFreq Frequency HSDPA
Hard Handovers
Without Channel
Change for Cell

BSC6900 UMTS

Description

H2H.AttOutInter- Frequency HSDPA V900R011
Freq Hard Handover
Attempts Without
Channel Change for
Cell

H2H.SuccOutIn- Successful Inter- V900R011
terFreq Frequency HSDPA
Hard Handovers
Without Channel
Change for Cell
67191157 VS.HSDPA.HHO. Number of Intra- Earlier than

H2D.AttOutIntra- Frequency H2D V900R011
Freq Hard Handover
Attempts for Cell

H2D.SuccOutIn- Successful Intra- V900R011
traFreq Frequency H2D
Hard Handovers for
Cell

H2D.AttOutInter- Frequency H2D V900R011
Freq Hard Handover
Attempts for Cell

H2D.SuccOutInter- Successful Inter- V900R011
Freq Frequency H2D
Hard Handovers for
Cell

ttEstab RAB Establishment V900R011
Attempts for Cell

ttEstab.BE.Golden RAB Establishment V900R011
Attempts of BE
Service for Golden
Level User for Cell

BSC6900 UMTS

Description

ttEstab.BE.Silver RAB Establishment V900R011
Attempts of BE
Service for Silver
Level User for Cell

ttEstab.BE.Copper RAB Establishment V900R011
Attempts of BE
Service for Copper
Level User for Cell
67190705 VS.HSDPA.RAB.S Number of Earlier than

uccEstab Successful HSDPA V900R011
RAB Establishments
for Cell

uccEstab.BE.Gold- Successful HSDPA V900R011
en RAB Establishments
of BE Service for
Golden Level User
for Cell

uccEstab.BE.Silver Successful HSDPA V900R011
RAB Establishments
of BE Service for
Silver Level User for
Cell

uccEstab.BE.Cop- Successful HSDPA V900R011
per RAB Establishments
of BE Service for
Copper Level User
for Cell
67191161 VS.HSDPA.RAB.N Number of HSDPA Earlier than

ormRel.UsrInact RAB Releases Due V900R011
to User Inactivity for
Cell

bnormRel RABs Abnormal V900R011
Released for Cell

BSC6900 UMTS

Description

bnormRel.RF RABs Abnormal V900R011
Released Due to RF
Cause for Cell
67191164 VS.HSDPA.RAB.N Number of HSDPA Earlier than

ormRel RABs Normal V900R011
Released for Cell
73403763 VS.HSDPA.UE.Ma Maximum Number V900R012

x.Cell of HSDPA UEs in a
Cell
73403764 VS.HSDPA.HHO. number of Inter- V900R012

H2D.AttOutIur RNC H2D Hard
Handover Attempts
for Cell
73403765 VS.HSDPA.HHO. Number of V900R012

H2D.SuccOutIur Successful Inter-
RNC H2D Hard
Handovers for Cell
73403817 VS.HSDPA.RAB. Number of HSDPA V900R012

64QAM.AttEstab 64QAM RAB Setup
Requests for cell

64QAM.SuccEstab 64QAM RABs Setup
Successfully for cell
73403819 VS.HSDPA.RAB.A Number of HSDPA V900R012

bnormRel.64QAM 64QAM RABs
Abnormal Released
for cell
73403820 VS.HSDPA.RAB.N Number of HSDPA V900R012

ormRel.64QAM 64QAM RABs
Normal Released for
Cell

MIMO.AttEstab MIMO RABs Setup
Request for Cell

MIMO.SuccEstab MIMO RABs Setup

BSC6900 UMTS

Description

ormRel.MIMO MIMO RABs
Normal Released for
cell

MIMO64QAM.Att MIMO+64QAM
Estab RABs Setup Request
for cell

MIMO64QAM.Suc MIMO+64QAM
cEstab RABs Setup

bnormRel.MIMO6 MIMO+64QAM
4QAM RABs Abnormal
Released for cell

ormRel.MIMO64Q MIMO+64QAM
AM RABs Normal
Released for cell
73403828 VS.HSDPA.RAB.D Number of DC- V900R012

C.AttEstab HSDPA RAB Setup
Requests in the
primary carrier of
DC-HSDPA counted
for cell

C.SuccEstab HSDPA RABs Setup
Successfully in the
primary carrier of
DC-HSDPA counted
for cell
73403830 VS.HSDPA.RAB.A Number of DC- V900R012

bnormRel.DC HSDPA RABs
Abnormal Released
in the primary carrier
of DC counted for
Cell(including RF
Cause)

BSC6900 UMTS

Description
73403831 VS.HSDPA.RAB.N Number of DC- V900R012

ormRel.DC HSDPA RABs
Normal Released in
the primary carrier of
DC counted for Cell

bnormRel.MIMO MIMO RABs
Abnormal Released
for cell(Including RF
Cause)
67204259 VS.HSDPA.UE.Me Average Number of V900R012

an.CAT1.6 HSDPA UEs with
Category 1-6 in a
Cell

x.CAT1.6 of HSDPA UEs with
Category 1-6 in a
Cell

Category 7-10 in a
Cell

Category 7-10 in a
Cell

Category 11-12 in a
Cell

Category 11-12 in a
Cell

Category 13-14 in a
Cell

Category 13-14 in a
Cell

BSC6900 UMTS

Description

Category 15-16 in a
Cell

Category 15-16 in a
Cell

Category 17-20 in a
Cell

Category 17-20 in a
Cell

Category 21-24 in a
Cell

Category 21-24 in a
Cell
73393828 VS.HSDPA.MACD Number of HSDPA V900R012

.AttSetup MAC-d Flow
Establishment
Requests for Cell
73393830 VS.HSDPA.RAB.F Number of Failed V900R012

ailEstab.DLPower. HSDPA Service
Cong Establishments Due
to DL Power
Insufficiency for Cell
73393831 VS.HSDPA.RAB.F Number of Failed V900R012

ailEstab.DLIUBBa HSDPA Service
nd.Cong Establishments Due
to DL Iub Bandwidth

BSC6900 UMTS

Description
73410484 VS.PS.Conv.Kbps. Average downlink V900R012

HSDSCH throughput of the
Traffic PS
Conversational
beared on HSDSCH
for cell
73393912 VS.PS.Conv.Traffi Number of downlink V900R012

c.HSDSCH bytes of Transport
Blocks of Traffic PS
Conversational
beared on HSDSCH
for cell
73410491 VS.HSDPA. Average Number of V900R012

64QAM.UE.Mean. 64QAM UEs in a
Cell Cell
73410492 VS.HSDPA.MIMO Average Number of V900R012

.UE.Mean.Cell MIMO UEs in a Cell
73410493 VS.HSDPA.MIMO Average Number of V900R012

64QAM.UE.Mean. MIMO+64QAM
Cell UEs in a Cell
73410508 VS.HSDPA.DC.PR Average number of V900R012

IM.UE.Mean.Cell DC-HSDPA UEs in
anchor carrier in a
Cell
73410509 VS.HSDPA.DC.SE Average number of V900R012

C.UE.Mean.Cell DC-HSDPA UEs in
supplementary
carrier in a Cell
73421686 VS.HSDPA.DRD.A Number of Outgoing V900R012

ttOut.Intelligence DRD Attempts for
HSDPA Users
Through Intelligent
User Recognition for
Cell
73421687 VS.HSDPA.DRD.S Number of V900R012

uccOut.Intelligence Successful Outgoing
DRDs for HSDPA
Users Through
Intelligent User
Recognition for Cell

BSC6900 UMTS

Description
73421688 VS.HSDPA.DRD.A Number of Incoming V900R012

ttIn.Intelligence DRD Attempts for
HSDPA Users
Through Intelligent
User Recognition for
Cell
73421689 VS.HSDPA.DRD.S Number of V900R012

uccIn.Intelligence Successful Incoming
DRDs for HSDPA
Users Through
Intelligent User
73422167 VS.HSDPA.RAB.A Number of RABs V900R012

bnormRel.H2P Abnormally
Released for PS
HSDPA Services
during the State
Transition from
CELL_DCH to
CELL_PCH or
URA_PCH for Cell

Category 25-28 in a
Cell

Category 25-28 in a
Cell

CMIMO.AttEstab HSDPA+MIMO
RAB Setup Requests
in the Primary
Carrier of DC-
HSDPA for Cell
73423379 VS.HSDPA.RAB.D Number of V900R013

CMIMO.SuccEsta Successful DC-
b HSDPA+MIMO
RAB Setups in the
Primary Carrier of
DC-HSDPA for cell

BSC6900 UMTS

Description
73423380 VS.HSDPA.RAB.D Number of Normal V900R013

CMIMO.NormRel DC-HSDPA+MIMO
RAB Releases in the
Primary Carrier of
DC-HSDPA for cell

CMIMO.AbnormR Abnormal DC-
el HSDPA+MIMO
RAB Releases in the
Primary Carrier of
DC-HSDPA for cell
73441141 VS.HSDPA.MeanC Mean Throughput on V900R013

hThrouput.High- HSDPA MAC-d
Load Flow for Cell
(Excluding the Data
of Low-Traffic
Users)
73423462 VS.HSDPA.Traffic. Number of Bytes V900R013

HighLoad Sent on HSDPA
MAC-d Flow for
Cell (Excluding the
Bytes of Low-Traffic
Users)

an.Cell.Free Free HSDPA Users
in a Cell

x.Cell.Free of Free HSDPA
Users in a Cell
73423900 VS.HSDPA.SHO.I Number of Serving V900R013

ubBasedServCellC Cell Change
hg.AttOut Attempts Triggered
by Unbalanced Iub
Resources for Cell
73423901 VS.HSDPA.SHO.I Number of V900R013

ubBasedServCellC Successful Serving
hg.SuccOut Cell Changes
Triggered by
Unbalanced Iub
Resources for Cell

BSC6900 UMTS

Description

4C.PRIM.UE.Mea 4C-HSDPA UEs
n.Cell Using This Cell as
the Primary Carrier
Cell

3C.PRIM.UE.Mea 3C-HSDPA UEs
n.Cell Using This Cell as
the Primary Carrier
Cell
73425890 VS.HSDPA.MC.SE Average Number of V900R015

C.UE.Mean.Cell 4C-HSDPA/DB-
HSDPA/DC-
HSDPA UEs Using
This Cell as the
Secondary Carrier
Cell
73425893 VS.HSDPA.DB.PR Average Number of V900R015

IM.UE.Mean.Cell DB-HSDPA UEs
Using This Cell as
the Primary Carrier
Cell
73425928 VS.HSDPA.RAB.A Number of V900R015

bnormRel.DC2P Abnormal RAB
Releases for Cell
During State
Transition of DC-
HSDPA UEs to
CELL/URA_PCH

bnormRel. Abnormal RAB
64QAM2P Releases for Cell
During State
Transition of
HSDPA+64QAM
UEs to CELL/
URA_PCH

bnormRel.MIMO2 Abnormal RAB
P Releases for Cell
During State
Transition of MIMO
UEs to CELL/
URA_PCH

BSC6900 UMTS

Description

bnormRel.DCMIM Abnormal RAB
O2P Releases for Cell
During State
Transition of DC-
HSDPA+MIMO
UEs to CELL/
URA_PCH

bnormRel.MIMO6 Abnormal RAB
During State
Transition of MIMO
+64QAM UEs to
CELL/URA_PCH

bnormRel.3C2P Abnormal RAB
Releases for Cell
During State
Transition of 3C-
HSDPA UEs to
CELL/URA_PCH

3CMIMO2P Releases for Cell
During State
Transition of 3C-
HSDPA+MIMO
UEs to CELL/
URA_PCH

bnormRel.4C2P Abnormal RAB
Releases for Cell
During State
Transition of 4C-
HSDPA UEs to
CELL/URA_PCH

BSC6900 UMTS

Description

4CMIMO2P Releases for Cell
During State
Transition of 4C-
HSDPA+MIMO
UEs to CELL/
URA_PCH

bnormRel.DB2P Abnormal RAB
Releases for Cell
During State
Transition of DB-
HSDPA UEs to
CELL/URA_PCH

bnormRel.DBMIM Abnormal RAB
O2P Releases for Cell
During State
Transition of DB-
HSDPA+MIMO
UEs to CELL/
URA_PCH
73425939 VS.HSDPA.RAB.N Number of Normal V900R015

ormRel.DC.All RAB Releases of
DC-HSDPA UEs for
Cell (All Scenarios)

ormRel. RAB Releases of
64QAM.All HSDPA+64QAM
UEs for Cell (All
Scenarios)

ormRel.MIMO.All RAB Releases of
HSDPA+MIMO
UEs for Cell (All
Scenarios)

ormRel.DCMIMO. RAB Releases of
All DC-HSDPA+MIMO
UEs for Cell (All
Scenarios)

BSC6900 UMTS

Description

ormRel.MIMO64Q RAB Releases of
AM.All HSDPA MIMO
+64QAM UEs for

ormRel.3C.All RAB Releases of 3C-
HSDPA UEs for Cell
(All Scenarios)

ormRel. RAB Releases of 3C-
3CMIMO.All HSDPA+MIMO
UEs for Cell (All
Scenarios)

ormRel.4C.All RAB Releases of 4C-
HSDPA UEs for Cell
(All Scenarios)

ormRel. RAB Releases of 4C-
4CMIMO.All HSDPA+MIMO
UEs for Cell (All
Scenarios)

ormRel.DB.All RAB Releases of
DB-HSDPA UEs for

ormRel.DBMIMO. RAB Releases of
All DB-HSDPA+MIMO
UEs for Cell (All
Scenarios)
73426132 VS.HSDPA.UE.Me Average number of V900R015

an.CAT29 Category 29 HSDPA
users in a cell
73426133 VS.HSDPA.UE.Ma Maximum number of V900R015

x.CAT29 Category 29 HSDPA
users in a cell

users in a cell

BSC6900 UMTS

Description

users in a cell

users in a cell

users in a cell

users in a cell

users in a cell
73426170 VS.HSDPA.SRBoH Average number of V900R015

.UE.Mean.Cell users capable of the
SRB over HSDPA
feature in a cell
73426094 VS.HSDPA.RAB. Number of RAB V900R015

3CMIMO.AttEstab Setup Attempts for
Cell When 3C-
HSDPA with MIMO
Applied
73426095 VS.HSDPA.RAB. Number of V900R015

3CMIMO.SuccEsta Successful RAB
b Setups for Cell When
3C-HSDPA with
MIMO Applied

bnormRel. Abnormally
3CMIMO Released RABs for
Cell When 3C-
HSDPA with MIMO
Applied (RF
Exceptions
Considered)
73426097 VS.HSDPA.RAB.N Number of Normally V900R015

ormRel.3CMIMO Released RABs for
Cell When 3C-
HSDPA with MIMO
Applied

BSC6900 UMTS

Description

3C.AttEstab Setup Attempts for
Cell When 3C-
HSDPA Applied

3C.SuccEstab Successful RAB
Setups for Cell When
3C-HSDPA Applied

bnormRel.3C Abnormally
Released RABs for
Cell When 3C-
HSDPA Applied (RF
Exceptions
Considered)

ormRel.3C Released RABs for
Cell When 3C-
HSDPA Applied

4CMIMO.AttEstab Setup Attempts for
Cell Where 4C-
HSDPA with MIMO
Applied

4CMIMO.SuccEsta Successful RAB
b Setups for Cell When
4C-HSDPA with
MIMO Applied

bnormRel. Abnormally
4CMIMO Released RABs for
Cell When 4C-
HSDPA with MIMO
Applied (RF
Exceptions
Considered)

ormRel.4CMIMO Released RABs for
Cell When 4C-
HSDPA with MIMO
Applied

BSC6900 UMTS

Description
73426106 VS.HSDPA.RAB.D Number of RAB V900R015

BMIMO.AttEstab Setup Attempts for
Cell When DB-
HSDPA with MIMO
Applied

BMIMO.SuccEstab Successful RAB
DB-HSDPA with
MIMO Applied

bnormRel.DBMIM Abnormal Released
O RABs for Cell When
DB-HSDPA with
MIMO Applied (RF
Exceptions
Considered)

ormRel.DBMIMO Released RABs for
Cell When DB-
HSDPA with MIMO
Applied

4C.AttEstab Setup Attempts for
Cell When 4C-
HSDPA Applied

4C.SuccEstab Successful RAB
4C-HSDPA Applied

bnormRel.4C Abnormal Released
RABs for Cell When
4C-HSDPA Applied
(RF Exceptions
Considered)

ormRel.4C Released RABs for
Cell When 4C-
HSDPA Applied

BSC6900 UMTS

Description
73426114 VS.HSDPA.RAB.D Number of RAB V900R015

B.AttEstab Setup Attempts for
Cell When DB-
HSDPA Applied

B.SuccEstab Successful RAB
DB-HSDPA Applied

bnormRel.DB Abnormally
Released RABs for
Cell When DB-
HSDPA Applied (RF
Exceptions
Considered)

ormRel.DB Released RABs for
Cell When DB-
HSDPA Applied

bnormRel.SRBoH. Abnormally
H2P Released RABs
During State
Transition of SRB
over HSDPA Users
to CELL_PCH or
URA_PCH for Cell

bnormRel.SRBoH Abnormally
Released RABs of
SRB over HSDPA
Users for Cell

ormRel.SRBoH.All Released RABs of
SRB over HSDPA
Users for Cell (All
Scenarios)

BSC6900 UMTS
Counter Sub Counter
VS.HSDPA.MeanChThroughput.TotalBytes VS.HSDPA.MeanGoldenBeChThroughput.
TotalBytes
VS.HSDPA.MeanSilverBeChThroughput.T
otalBytes
VS.HSDPA.MeanCopperBeChThroughput.
TotalBytes
VS.PS.Conv.Traffic.HSDSCH
VS.HSDPA.Traffic.HighLoad
VS.HSDPA.SHO.ServCellChg.AttOut VS.HSDPA.SHO.ServCellChg.AttOutIur
VS.HSDPA.SHO.IubBasedServCellChg.Att
Out
VS.HSDPA.SHO.ServCellChg.SuccOut VS.HSDPA.SHO.ServCellChg.SuccOutIur
VS.HSDPA.SHO.IubBasedServCellChg.Su
ccOut
VS.HSDPA.HHO.H2H.AttOutIur VS.HSDPA.HHO.H2H.AttOutIntraFreq
VS.HSDPA.HHO.H2H.AttOutInterFreq
VS.HSDPA.HHO.H2H.SuccOutIur VS.HSDPA.HHO.H2H.SuccOutIntraFreq
VS.HSDPA.HHO.H2H.SuccOutInterFreq
VS.HSDPA.HHO.H2D.AttOutIur VS.HSDPA.HHO.H2D.AttOutIntraFreq
VS.HSDPA.HHO.H2D.AttOutInterFreq
VS.HSDPA.HHO.H2D.SuccOutIur VS.HSDPA.HHO.H2D.SuccOutIntraFreq
VS.HSDPA.HHO.H2D.SuccOutInterFreq

BSC6900 UMTS
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.64QAM.AttEstab
VS.HSDPA.RAB.MIMO.AttEstab
VS.HSDPA.RAB.MIMO64QAM.AttEstab
VS.HSDPA.RAB.DC.AttEstab
VS.HSDPA.RAB.DCMIMO.AttEstab
VS.HSDPA.RAB.3CMIMO.AttEstab
VS.HSDPA.RAB.3C.AttEstab
VS.HSDPA.RAB.4CMIMO.AttEstab
VS.HSDPA.RAB.DBMIMO.AttEstab
VS.HSDPA.RAB.4C.AttEstab
VS.HSDPA.RAB.DB.AttEstab
VS.HSDPA.RAB.SuccEstab VS.HSDPA.RAB.SuccEstab.BE.Golden
VS.HSDPA.RAB.SuccEstab.BE.Silver
VS.HSDPA.RAB.SuccEstab.BE.Copper
VS.HSDPA.RAB.64QAM.SuccEstab
VS.HSDPA.RAB.MIMO.SuccEstab
VS.HSDPA.RAB.MIMO64QAM.SuccEs-
tab
VS.HSDPA.RAB.DC.SuccEstab
VS.HSDPA.RAB.DCMIMO.SuccEstab
VS.HSDPA.RAB.3CMIMO.SuccEstab
VS.HSDPA.RAB.3C.SuccEstab
VS.HSDPA.RAB.4CMIMO.SuccEstab
VS.HSDPA.RAB.DBMIMO.SuccEstab
VS.HSDPA.RAB.4C.SuccEstab
VS.HSDPA.RAB.DB.SuccEstab

BSC6900 UMTS
Counter Sub Counter
VS.HSDPA.RAB.AbnormRel VS.HSDPA.RAB.AbnormRel.RF
VS.HSDPA.RAB.AbnormRel.64QAM
VS.HSDPA.RAB.AbnormRel.MIMO64QA
M
VS.HSDPA.RAB.AbnormRel.DC
VS.HSDPA.RAB.AbnormRel.MIMO
VS.HSDPA.RAB.AbnormRel.H2P
VS.HSDPA.RAB.DCMIMO.AbnormRel
VS.HSDPA.RAB.AbnormRel.3CMIMO
VS.HSDPA.RAB.AbnormRel.3C
VS.HSDPA.RAB.AbnormRel.4CMIMO
VS.HSDPA.RAB.AbnormRel.DBMIMO
VS.HSDPA.RAB.AbnormRel.4C
VS.HSDPA.RAB.AbnormRel.DB
VS.HSDPA.RAB.AbnormRel.SRBoH
VS.HSDPA.RAB.NormRel VS.HSDPA.RAB.NormRel.64QAM
VS.HSDPA.RAB.NormRel.MIMO
VS.HSDPA.RAB.NormRel.MIMO64QAM
VS.HSDPA.RAB.NormRel.DC
VS.HSDPA.RAB.DCMIMO.NormRel
VS.HSDPA.RAB.NormRel.3CMIMO
VS.HSDPA.RAB.NormRel.3C
VS.HSDPA.RAB.NormRel.4CMIMO
VS.HSDPA.RAB.NormRel.DBMIMO
VS.HSDPA.RAB.NormRel.4C
VS.HSDPA.RAB.NormRel.DB

BSC6900 UMTS
Counter Sub Counter
VS.HSDPA.UE.Mean.Cell VS.HSDPA.UE.Mean.CAT1.6
VS.HSDPA.UE.Mean.CAT7.10
VS.HSDPA.64QAM.UE.Mean.Cell
VS.HSDPA.MIMO.UE.Mean.Cell
VS.HSDPA.MIMO64QAM.UE.Mean.Cell
VS.HSDPA.DC.PRIM.UE.Mean.Cell
VS.HSDPA.UE.Mean.Cell.Free
VS.HSDPA.4C.PRIM.UE.Mean.Cell
VS.HSDPA.3C.PRIM.UE.Mean.Cell
VS.HSDPA.DB.PRIM.UE.Mean.Cell
VS.HSDPA.UE.Mean.CAT29
VS.HSDPA.SRBoH.UE.Mean.Cell
VS.HSDPA.UE.Max.Cell VS.HSDPA.UE.Max.CAT1.6
VS.HSDPA.UE.Max.CAT7.10
VS.HSDPA.UE.Max.Cell.Free
VS.HSDPA.UE.Max.CAT29

BSC6900 UMTS
Counter Sub Counter
VS.HSDPA.RAB.AbnormRel.H2P VS.HSDPA.RAB.AbnormRel.DC2P
VS.HSDPA.RAB.AbnormRel.64QAM2P
VS.HSDPA.RAB.AbnormRel.MIMO2P
VS.HSDPA.RAB.AbnormRel.DCMIMO2P
VS.HSDPA.RAB.AbnormRel.MIMO64QA
M2P
VS.HSDPA.RAB.AbnormRel.3C2P
VS.HSDPA.RAB.AbnormRel.3CMIMO2P
VS.HSDPA.RAB.AbnormRel.4C2P
VS.HSDPA.RAB.AbnormRel.4CMIMO2P
VS.HSDPA.RAB.AbnormRel.DB2P
VS.HSDPA.RAB.AbnormRel.DBMIMO2P
VS.HSDPA.RAB.AbnormRel.SRBoH.H2P
1.12.12.1 Number of Successful Channel Reconfigurations
Counters
67189831 VS.HSDPA.F2H.Succ Number of Successful

FACH to HS-DSCH for
HSDPA Service for Cell
67189830 VS.HSDPA.D2H.Succ Number of Successful

DCH to HS-DSCH for
67189832 VS.HSDPA.H2D.Succ Number of Successful

HS-DSCH to DCH for
67189833 VS.HSDPA.H2F.Succ Number of Successful

HS-DSCH to FACH for

BSC6900 UMTS
Description
These counters provide the number of successful channel reconfigurations by channel
reconfiguration type in the HSDPA serving cell. For multi-carrier HSDPA users, this counter is
VS.HSDPA.F2H.Succ VS.HSDPA.F2H.Succ provides the number

of successful channel conversions from the
FACH to the HS-DSCH in a cell.
VS.HSDPA.D2H.Succ VS.HSDPA.D2H.Succ provides the number

DCH to the HS-DSCH in a cell.
VS.HSDPA.H2D.Succ VS.HSDPA.H2D.Succ provides the number

HS-DSCH to the DCH in a cell.
VS.HSDPA.H2F.Succ VS.HSDPA.H2F.Succ provides the number

HS-DSCH to the FACH in a cell.
Measurement point
The measurement is triggered at point B as shown in the following figure. The RNC receives
from a UE a RADIO BEARER RECONFIGURATION COMPLETE message indicating a
channel reconfiguration in the DCCC or RAB MODIFY procedure. If a channel conversion
occurs, the RNC measures this counter in the HSDPA serving cell according to the channel status
before and after the reconfiguration.
Figure 1-496 Dynamic channel configuration procedure (RB reconfiguration)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSDPA.F2H.Succ WRFD-01061111 HSDPA State Transition
VS.HSDPA.D2H.Succ WRFD-01061111 HSDPA State Transition
VS.HSDPA.H2D.Succ WRFD-01061111 HSDPA State Transition
VS.HSDPA.H2F.Succ WRFD-01061111 HSDPA State Transition
1.12.12.2 Number of Successful HSDPA MAC-d Flow Establishments for Cell
Counters
67189834 VS.HSDPA.MACD.Succ- Number of Successful

Setup HSDPA MAC-d Flow
Establishments for Cell
Description
This measurement item provides the number of successful HSDPA MAC-d flow establishments
in a cell.For DC-HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
During the RL reconfiguration, if the RADIO LINK RECONFIGURATION PREPARE
message contains an IE "HSDSCH FDD Information" or "HS-DSCH MAC-d Flows To Add",
it indicates that the RL is set up for HSDPA service. The measurement is triggered at point C
as shown in the following figure. When the RNC sends the NodeB a RADIO LINK
RECONFIGURATION COMMIT message, this counter is measured in the cell in which the
RL is set up.

BSC6900 UMTS
Figure 1-497 Synchronized RL reconfiguration commit procedure
During the RL reconfiguration, if the RADIO LINK SETUP REQUEST message contains an
IE "HSDSCH FDD Information", it indicates that the RL is set up for HSDPA service in the
serving cell. The measurement is triggered at point B as shown in the following figure. When
the RNC receives a RADIO LINK SETUP RESPONSE message from the NodeB, this counter
is measured in the cell in which the RL is set up.
Figure 1-498 Radio link setup procedure (successful operation)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSDPA.MACD.Succ- WRFD-010610 HSDPA Introduction

Setup Package
1.12.12.3 Number of HSDPA UEs in a Cell
Counters
67202932 VS.HSDPA.UE.Mean.Cell Average Number of HSDPA

UEs in a Cell
73403763 VS.HSDPA.UE.Max.Cell Maximum Number of

HSDPA UEs in a Cell
73410491 VS.HSDPA. Average Number of 64QAM

64QAM.UE.Mean.Cell UEs in a Cell
73410493 VS.HSDPA.MIMO64QAM. Average Number of MIMO

UE.Mean.Cell +64QAM UEs in a Cell
73410508 VS.HSDPA.DC.PRIM.UE. Average number of DC-

Mean.Cell HSDPA UEs in anchor
carrier in a Cell
73410509 VS.HSDPA.DC.SEC.UE.M Average number of DC-

ean.Cell HSDPA UEs in
supplementary carrier in a
Cell
73441142 VS.HSDPA.UE.Mean.Cell. Average Number of Free

Free HSDPA Users in a Cell
73423469 VS.HSDPA.UE.Max.Cell.Fr Maximum Number of Free

ee HSDPA Users in a Cell

BSC6900 UMTS
73425884 VS.HSDPA. Average Number of 4C-

4C.PRIM.UE.Mean.Cell HSDPA UEs Using This Cell
as the Primary Carrier Cell
73425887 VS.HSDPA. Average Number of 3C-

3C.PRIM.UE.Mean.Cell HSDPA UEs Using This Cell
73425890 VS.HSDPA.MC.SEC.UE.M Average Number of 4C-

ean.Cell HSDPA/DB-HSDPA/DC-
HSDPA UEs Using This Cell
as the Secondary Carrier Cell
73425893 VS.HSDPA.DB.PRIM.UE. Average Number of DB-

Mean.Cell HSDPA UEs Using This Cell
73426170 VS.HSDPA.SRBoH.UE.Me Average number of users

an.Cell capable of the SRB over
HSDPA feature in a cell
specific formulas.

64QAM.UE.Mean.Cell.DE- UEs in a Cell(Denominator)
NO

64QAM.UE.Mean.Cell.NU UEs in a Cell(Numerator)
M

UE.Mean.Cell.DENO +64QAM UEs in a Cell
(Denominator)

UE.Mean.Cell.NUM +64QAM UEs in a Cell
(Numerator)
73423471 VS.HSDPA.UE.Mean.Cell. VS.HSDPA.UE.Mean.Cell.

Free.DENO Free.DENO
73423470 VS.HSDPA.UE.Mean.Cell. VS.HSDPA.UE.Mean.Cell.

Free.NUM Free.NUM

BSC6900 UMTS
Description
These counters provide the average number and maximum number of HSDPA UEs in a serving
cell when different technologies are used.
For DC-HSDPA, 3C-HSDPA, 4C-HSDPA, or DB-HSDPA users, these counters, excluding

VS.HSDPA.DC.SEC.UE.Mean.Cell and VS.HSDPA.MC.SEC.UE.Mean.Cell, are measured
only in the cell with the primary carrier for once.
VS.HSDPA.UE.Mean.Cell provides the average number of HSDPA UEs in a serving cell.
VS.HSDPA.UE.MaX.Cell provides the maximum number of HSDPA UEs in a serving cell.
The other counters provide the average or maximum number of UEs when different features are
used in a serving cell.
VS.HSDPA.DC.SEC.UE.Mean.Cell provides the average number of DC-HSDPA UEs whose

secondary carrier is the current cell in a serving cell.
VS.HSDPA.MC.SEC.UE.Mean.Cell provides the average number of 4C-HSDPA, 3C-HSDPA,

DB-HSDPA, and DC-HSDPA UEs (including UEs using both multi-carrier HSDPA and MIMO)
whose secondary carrier is the current cell in a serving cell.
Measurement point
The system samples the number of HSDPA UEs using various technologies every 5s. Assume
that the total number of samples is N within a measurement period. At the end of the measurement
period, the system divides N by the accumulated value of sampled data to obtain the average
number of UEs using various features. The maximum sampled value is used as the maximum
number of UEs using various technologies.
Formula
VS.HSDPA.64QAM.UE.Mean.Cell = [VS.HSDPA.64QAM.UE.Mean.Cell.NUM]/
[VS.HSDPA.64QAM.UE.Mean.Cell.DENO]
VS.HSDPA.MIMO64QAM.UE.Mean.Cell =
[VS.HSDPA.MIMO64QAM.UE.Mean.Cell.NUM]/
[VS.HSDPA.MIMO64QAM.UE.Mean.Cell.DENO]
VS.HSDPA.UE.Mean.Cell.Free = [VS.HSDPA.UE.Mean.Cell.Free.NUM]/
[VS.HSDPA.UE.Mean.Cell.Free.DENO]
Unit
None
Related Features
VS.HSDPA.UE.Mean.Cell WRFD-01061016 16 HSDPA Users per Cell

WRFD-010622 32 HSDPA Users per Cell

BSC6900 UMTS
VS.HSDPA.UE.Max.Cell WRFD-01061003 HSDPA Admission Control

WRFD-020101 Admission Control
VS.HSDPA. WRFD-010683 Downlink 64QAM

64QAM.UE.Mean.Cell
VS.HSDPA.MIMO64QAM. WRFD-010693 DL 64QAM+MIMO

UE.Mean.Cell
VS.HSDPA.DC.PRIM.UE. WRFD-010696 DC-HSDPA

Mean.Cell
VS.HSDPA.DC.SEC.UE.M WRFD-010696 DC-HSDPA

ean.Cell
VS.HSDPA.UE.Mean.Cell. WRFD-01061003 HSDPA Admission Control

Free
VS.HSDPA.UE.Max.Cell.Fr WRFD-01061003 HSDPA Admission Control

ee
VS.HSDPA. WRFD-150207 4C-HSDPA

4C.PRIM.UE.Mean.Cell WRFD-150223 MC-HSDPA+MIMO
VS.HSDPA. WRFD-150250 3C-HSDPA

3C.PRIM.UE.Mean.Cell WRFD-150223 MC-HSDPA+MIMO
VS.HSDPA.MC.SEC.UE.M WRFD-150250 3C-HSDPA

ean.Cell WRFD-150207 4C-HSDPA
WRFD-150208 Flexible Dual Carrier
WRFD-150209 HSDPA
WRFD-010699 DB-HSDPA
WRFD-010696 DC-HSDPA+MIMO
DC-HSDPA
VS.HSDPA.DB.PRIM.UE. WRFD-150209 DB-HSDPA

Mean.Cell WRFD-150227 DB-HSDPA+MIMO
VS.HSDPA.SRBoH.UE.Me WRFD-010652 SRB over HSDPA

an.Cell
1.12.12.4 Number of MAC-d Flows in a Cell

BSC6900 UMTS
Counters
67202941 VS.HSDPA.MACD.Mean.C Average Number of MAC-d

ell Flows in a Cell
Description
This counter provides the average number of MAC-d flows in a serving cell.For DC-HSDPA
Measurement point
The system samples the number of MAC-d flows every 5s. Assume that the total number of
samples within a measurement period is N. at the end of a measurement period, the RNC divides
N by the accumulated value of sampled data to obtain the average number of MAC-d flows.
Formula
None
Unit
None
Related Features
VS.HSDPA.MACD.Mean.C WRFD-01061016 16 HSDPA Users per Cell

ell WRFD-010622 32 HSDPA Users per Cell
1.12.12.5 Mean Downlink Throughput of single HSDPA MAC-d Flows
Counters
67202894 VS.HSDPA.Mean- Mean Downlink Throughput

ChThroughput of single HSDPA MAC-d
Flows for Cell

BSC6900 UMTS
67204510 VS.HSDPA.MeanGolden- Mean Downlink Throughput

BeChThroughput of HSDPA MAC-d Flow of
BE Service for Golden
Subscriber for Cell
67204511 VS.HSDPA.MeanSilver- Mean Downlink Throughput

Subscriber for Cell
67204512 VS.HSDPA.MeanCopper- Mean Downlink Throughput

BE Service for Copper
Subscriber for Cell
73410484 VS.PS.Conv.Kbps.HSDSC Average downlink

H throughput of the Traffic PS
Conversational beared on
HSDSCH for cell
specific formulas.
67190567 VS.HSDPA.MeanChThroug Duration of HSDPA MAC-D

hput.Times Flow Sending Data for Cell
67194872 VS.HSDPA.MeanCopperBe Duration of Copper BE

ChThroughput.Times HSDPA MAC-D Flow
Sending Data for Cell
67194868 VS.HSDPA.MeanGoldenBe Duration of Golden BE

ChThroughput.Times HSDPA MAC-D Flow
67194870 VS.HSDPA.MeanSilverBeC Duration of Silver BE

hThroughput.Times HSDPA MAC-D Flow
73393913 VS.PS.Conv.Times.HSDSC Duration of PS

H Conversational HSDPA
MAC-D Flow Sending Data
for Cell
Description
These counters provide the mean downlink throughput of single HSDPA MAC-d flows in a
serving cell according to user priorities or service types. For multi-carrier HSDPA users, this

BSC6900 UMTS
counter is measured only in the primary cell based on the total throughput on the primary and
secondary carriers.
VS.HSDPA.MeanChThroughput VS.HSDPA.MeanChThroughput provides

the mean downlink throughput of all single
HSDPA MAC-d flows in a cell.
VS.HSDPA.MeanGoldenBeChThroughput VS.HSDPA.MeanGoldenBeChThroughput,
VS.HSDPA.MeanSilverBeChThroughput,
and VS.HSDPA.MeanCopperBeCh-
Throughput provide the mean downlink
throughput of HSDPA MAC-d flows of BE
services for golden subscribers, silver
subscribers, and copper subscribers in a cell,
respectively.
VS.HSDPA.MeanSilverBeChThroughput VS.HSDPA.MeanGoldenBeChThroughput,
respectively.
VS.HSDPA.MeanCopperBeChThroughput VS.HSDPA.MeanGoldenBeChThroughput,
respectively.
VS.PS.Conv.Kbps.HSDSCH VS.PS.Conv.Kbps.HSDSCH provides the

average downlink throughput of single MAC-
d flows of PS conversational services carried
on HSDSCH.
Measurement point
When data is sent in an HSDPA serving cell, the RNC measures the total data transmission time
of the MAC-d flows in the serving cell and the total bytes sent in the HSDPA serving cell. When
data of BE services for golden/silver/copper subscribers or data of PS conversational services
carried on the HS-DSCH is sent in the serving cell, the RNC measures the total data transmission
time of MAC-d flows for these services and the total bits sent in the HSDPA serving cell. At the
end of the measurement period, the RNC divides the total data transmission time by the total
number of bits to obtain the mean downlink throughput of MAC-d flows at the RLC layer in the

BSC6900 UMTS
cell. The total bits do not include the RLC header and the retransmitted data in the unit of bit.
The total number of bits is calculated by converting the total number of bytes. The total data
transmission time is measured in the unit of ms.
Formula
VS.HSDPA.MeanChThroughput = {8}*[VS.HSDPA.MeanChThroughput.TotalBytes]/
[VS.HSDPA.MeanChThroughput.Times]
VS.HSDPA.MeanGoldenBeChThroughput = {8}*
[VS.HSDPA.MeanGoldenBeChThroughput.TotalBytes]/
[VS.HSDPA.MeanGoldenBeChThroughput.Times]
VS.HSDPA.MeanSilverBeChThroughput = {8}*
[VS.HSDPA.MeanSilverBeChThroughput.TotalBytes]/
[VS.HSDPA.MeanSilverBeChThroughput.Times]
VS.HSDPA.MeanCopperBeChThroughput = {8}*
[VS.HSDPA.MeanCopperBeChThroughput.TotalBytes]/
[VS.HSDPA.MeanCopperBeChThroughput.Times]
VS.PS.Conv.Kbps.HSDSCH = {8}*[VS.PS.Conv.Traffic.HSDSCH]/
[VS.PS.Conv.Times.HSDSCH]
Unit
kbit/s
Related Features
VS.HSDPA.Mean- WRFD-010610 HSDPA Introduction

ChThroughput Package
VS.HSDPA.MeanGolden- WRFD-01061008 Interactive and Background

BeChThroughput WRFD-020806 Traffic Class on HSDPA
Differentiated Service Based
on SPI Weight
VS.HSDPA.MeanSilver- WRFD-01061008 Interactive and Background

on SPI Weight
VS.HSDPA.MeanCopper- WRFD-01061008 Interactive and Background

on SPI Weight
VS.PS.Conv.Kbps.HSDSC WRFD-010617 VoIP over HSPA/HSPA+

H WRFD-010501 Conversational QoS Class

BSC6900 UMTS
1.12.12.6 Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow
Counters
67189840 VS.HSDPA.MeanChThroug Number of Total Bytes Sent

hput.TotalBytes in Downlink of HSDPA
MAC-d Flow for Cell
67194867 VS.HSDPA.MeanGoldenBe Number of Total Bytes Sent

ChThroughput.TotalBytes in Downlink of HSDPA
MAC-d Flow of BE Service
for Golden Subscriber for
Cell
67194869 VS.HSDPA.MeanSilverBeC Number of Total Bytes Sent

hThroughput.TotalBytes in Downlink of HSDPA
for Silver Subscriber for Cell
67194871 VS.HSDPA.MeanCopperBe Number of Total Bytes Sent

ChThroughput.TotalBytes in Downlink of HSDPA
for Copper Subscriber for
Cell
73393912 VS.PS.Conv.Traffic.HSDSC Number of downlink bytes of

H Transport Blocks of Traffic
PS Conversational beared on
HSDSCH for cell
Description
These counters provide the number of bytes sent in the downlink for a single HSDPA MAC-d
flow according to user priorities or service types in a serving cell.
For multi-carrier HSDPA users, this counter is measured only in the primary cell based on the
total number of bytes sent on the primary and secondary carriers.
VS.HSDPA.MeanChThroughput provides total number of bytes sent in the downlink on all

HSDPA Mac-d flows.
VS.HSDPA.MeanGoldenBeChThroughput, VS.HSDPA.MeanSilverBeChThroughput, and

VS.HSDPA.MeanCopperBeChThroughput provide the number of bytes sent in the downlink
on the HSDPA MAC-d flows of BE services for golden subscribers, silver subscribers, and
copper subscribers in a cell, respectively.
VS.PS.Conv.Kbps.HSDSCH provides the number of bytes sent in the downlink on the MAC-d
flows of PS conversational services carried on HS-DSCH.

BSC6900 UMTS
Measurement point
The RNC measures the number of total bytes (including all types of service data) sent in the
downlink at the RLC layer of the MAC-d flow in the serving cell. When data of BE services for
golden/silver/copper subscribers or data of PS conversational services carried on the HS-DSCH
is sent in the serving cell, the RNC measures the total number of bytes sent in the downlink at
the RLC layer of the MAC-d flow HSDPA serving cell. The total bytes do not include the RLC
header and the retransmitted data.
Formula
None
Unit
byte
Related Features
VS.HSDPA.MeanChThroug WRFD-010610 HSDPA Introduction

hput.TotalBytes Package
VS.HSDPA.MeanGoldenBe WRFD-01061008 Interactive and Background

ChThroughput.TotalBytes WRFD-020806 Traffic Class on HSDPA
on SPI Weight
VS.HSDPA.MeanSilverBeC WRFD-01061008 Interactive and Background

hThroughput.TotalBytes WRFD-020806 Traffic Class on HSDPA
on SPI Weight
VS.HSDPA.MeanCopperBe WRFD-01061008 Interactive and Background

on SPI Weight
VS.PS.Conv.Traffic.HSDSC WRFD-010617 VoIP over HSPA/HSPA+

H WRFD-010501 Conversational QoS Class
1.12.12.7 Number of Handover Attempts Between Channels of Different Types

BSC6900 UMTS
Counters
67190690 VS.HSDPA.H2D.Att Number of Channel

HS-DSCH to DCH for
67190693 VS.HSDPA.D2H.Att Number of Channel

DCH to HS-DSCH for
67190696 VS.HSDPA.F2H.Att Number of Channel

FACH to HS-DSCH for
67190697 VS.HSDPA.H2F.Att Number of Channel

HS-DSCH to FACH for
Description
These counters provide the number of handover attempts between channels of different types in
a cell. For multi-carrier HSDPA users, this counter is measured only in the cell with the primary
carrier.
VS.HSDPA.H2D.Att VS.HSDPA.H2D.Att provides the number of

channel conversion attempts from the HS-
DSCH to the DCH in a cell.
VS.HSDPA.D2H.Att VS.HSDPA.D2H.Att provides the number of

channel conversion attempts from the DCH
to the HS-DSCH in a cell.
VS.HSDPA.F2H.Att VS.HSDPA.F2H.Att provides the number of

channel conversion attempts from the FACH
to the HS-DSCH in a cell.
VS.HSDPA.H2F.Att VS.HSDPA.H2F.Att provides the number of

channel conversion attempts from the HS-
DSCH to the FACH in a cell.

BSC6900 UMTS
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC decides
to perform a channel handover, it sends a RADIO BEARER RECONFIGURATION message
to a UE during the DCCC or RAB MODIFY procedure. The RNC measures these counters in
the HSDPA serving cell according to the channel status before and after the reconfiguration.
Formula
None
Unit
None
Related Features
VS.HSDPA.H2D.Att WRFD-01061111 HSDPA State Transition
VS.HSDPA.D2H.Att WRFD-01061111 HSDPA State Transition
VS.HSDPA.F2H.Att WRFD-01061111 HSDPA State Transition
VS.HSDPA.H2F.Att WRFD-01061111 HSDPA State Transition
1.12.12.8 Number of HSDPA Serving Cell Change Attempts for Cell

BSC6900 UMTS
Counters
67190698 VS.HSDPA.SHO.ServCellC Number of Intra-RNC

hg.AttOut HSDPA Serving Cell Change
Attempts for Cell
67195481 VS.HSDPA.SHO.ServCellC Number of Inter-RNC

hg.AttOutIur HSDPA Serving Cell Change
Attempts for Cell
73423900 VS.HSDPA.SHO.IubBased Number of Serving Cell

ServCellChg.AttOut Change Attempts Triggered
by Unbalanced Iub
Resources for Cell
Description
These counters provide the number of serving cell change attempts for cell. For multi-carrier
HSDPA users, this counter is measured only in the cell with the primary carrier.
VS.HSDPA.SHO.ServCellChg.AttOut VS.HSDPA.SHO.ServCellChg.AttOut
provides the number of HSDPA serving cell
change attempts in a cell.
VS.HSDPA.SHO.ServCellChg.AttOutIur VS.HSDPA.SHO.ServCellChg.AttOutIur
provides the number of inter-RNC HSDPA
serving cell change attempts in a cell.
VS.HSDPA.SHO.IubBasedServCellChg.Att VS.HSDPA.SHO.IubBasedServCellChg.Att
Out Out provides the number of HSDPA serving
cell change attempts that are triggered by
unbalanced Iub resources between NodeBs.
Measurement point
During an HSDPA serving cell change when a soft handover occurs, the RNC may send the UE
the following messages:
(1)PHYSICAL CHANNEL RECONFIGURATION,
(2)TRANSPORT CHANNEL RECONFIGURATION,
(3)RADIO BEARER RECONFIGURATION,
(4)ACTIVE SET UPDATE.

BSC6900 UMTS
The measurement is triggered at point A as shown in the following figure. Assume that the RNC
sends the UE a PHYSICAL CHANNEL RECONFIGURATION message, the RNC measures
these counters in the original serving cell based on the type of serving cell change.
Figure 1-500 HSDPA Serving cell change procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.HSDPA.SHO.ServCellC WRFD-01061006 HSDPA Mobility

hg.AttOut Management

hg.AttOutIur Management
1.12.12.9 Number of Successful HSDPA Serving Cell Changes for Cell

BSC6900 UMTS
Counters
67190699 VS.HSDPA.SHO.ServCellC Number of Intra-RNC

hg.SuccOut HSDPA Serving Cell Change
Success in RNC for Cell
67195482 VS.HSDPA.SHO.ServCellC Number of Inter-RNC

hg.SuccOutIur HSDPA Serving Cell Change
Success for Cell
73423901 VS.HSDPA.SHO.IubBased Number of Successful

ServCellChg.SuccOut Serving Cell Changes
Triggered by Unbalanced Iub
Resources for Cell
Description
These counters provide the number of successful serving cell changes of different types only
during a soft handover. For multi-carrier HSDPA users, this counter is measured only in the cell
VS.HSDPA.SHO.ServCellChg.SuccOut VS.HSDPA.SHO.ServCellChg.SuccOut
provides the number of successful HSDPA
serving cell changes in a cell.
VS.HSDPA.SHO.ServCellChg.SuccOutIur VS.HSDPA.SHO.ServCellChg.SuccOutIur
provides the number of successful inter-RNC
HSDPA serving cell changes in a cell.
VS.HSDPA.SHO.IubBasedServCellChg.Su VS.HSDPA.SHO.IubBasedServCellChg.Su
ccOut ccOut provides the number of successful
HSDPA serving cell changes that are
triggered by unbalanced Iub resources
between NodeBs.
Measurement point
During an HSDPA serving cell change when a soft handover occurs, the RNC may send the UE
the following messages:
(1)PHYSICAL CHANNEL RECONFIGURATION,
(2)TRANSPORT CHANNEL RECONFIGURATION,
(3)RADIO BEARER RECONFIGURATION,

BSC6900 UMTS
(4)ACTIVE SET UPDATE.
The measurement is triggered at point B as shown in the following figure. Assume that the RNC
sends the UE a PHYSICAL CHANNEL RECONFIGURATION message, the RNC measures
these counters in the original serving cell based on the type of serving cell change.
Formula
None
Unit
None
Related Features

hg.SuccOut Management

hg.SuccOutIur Management
1.12.12.10 Number of Inter-RNC HSDPA Hard Handover Attempts Without

Channel Change for Cell

BSC6900 UMTS
Counters
67195483 VS.HSDPA.HHO.H2H.At- Number of Inter-RNC

tOutIur HSDPA Hard Handover
Attempts Without Channel
Change for Cell
67190700 VS.HSDPA.HHO.H2H.At- Number of Intra-Frequency

tOutIntraFreq HSDPA Hard Handover
Change for Cell
67190702 VS.HSDPA.HHO.H2H.At- Number of Inter-Frequency

tOutInterFreq HSDPA Hard Handover
Change for Cell
Description
These counters provide the number of attempts for outgoing hard handovers of different types
on the HSDPA channel in a serving cell. For multi-carrier HSDPA users, this counter is measured
VS.HSDPA.HHO.H2H.AttOutIur VS.HSDPA.HHO.H2H.AttOutIur provides

the number of inter-RNC HSDPA hard
handover attempts without channel change in
the serving cell.
VS.HSDPA.HHO.H2H.AttOutIntraFreq VS.HSDPA.HHO.H2H.AttOutIntraFreq
provides the number of intra-frequency
HSDPA hard handover attempts without
channel change in a cell.
VS.HSDPA.HHO.H2H.AttOutInterFreq VS.HSDPA.HHO.H2H.AttOutInterFreq
provides the number of inter-frequency
channel change in a cell.
Measurement point
During the hard handover on the HSDPA channel, the RNC may send the UE the following
messages:
(1) PHYSICAL CHANNEL RECONFIGURATION,

BSC6900 UMTS
(2) TRANSPORT CHANNEL RECONFIGURATION,
(3) RADIO BEARER RECONFIGURATION,
(4) RADIO BEARER SETUP,
(5) RADIO BEARER RELEASE.
sends the UE a PHYSICAL CHANNEL RECONFIGRATION message, the RNC measures
these counters in the best cell before the hard handover according to the hard handover type.
Formula
None
Unit
None
Related Features
VS.HSDPA.HHO.H2H.At- WRFD-01061006 HSDPA Mobility

tOutIur Management

tOutIntraFreq Management

tOutInterFreq Management

BSC6900 UMTS
1.12.12.11 Number of Successful Inter-RNC HSDPA Hard Handovers Without

Counters
67195484 VS.HSDPA.HHO.H2H.Suc- Number of Successful Inter-

cOutIur RNC HSDPA Hard
Handovers Without Channel
Change for Cell
67190701 VS.HSDPA.HHO.H2H.Suc- Number of Successful Intra-

cOutIntraFreq Frequency HSDPA Hard
Change for Cell
Description
These counters provide the number of successful outgoing hard handovers of different types on
the HSDPA channel in a serving cell. For multi-carrier HSDPA users, this counter is measured
VS.HSDPA.HHO.H2H.SuccOutIur VS .HSDPA.HHO.H2H.SuccOutIur
provides the number of successful inter-RNC
channel change in the serving cell.
VS.HSDPA.HHO.H2H.SuccOutIntraFreq VS.HSDPA.HHO.H2H.SuccOutIntraFreq
provides the number of successful intra-
frequency HSDPA hard handover attempts
without channel change in a cell.
Measurement point
During the hard handover on the HSDPA channel, the RNC may send the UE the following
messages:
(1) PHYSICAL CHANNEL RECONFIGURATION,
(2) TRANSPORT CHANNEL RECONFIGURATION,

BSC6900 UMTS
sends the UE a PHYSICAL CHANNEL RECONFIGURATIO COMPLETE message, the RNC
measures these counters in the best cell before the hard handover according to the hard handover
type.
Formula
None
Unit
None
Related Features
VS.HSDPA.HHO.H2H.Suc- WRFD-01061006 HSDPA Mobility

cOutIur Management

cOutIntraFreq Management
1.12.12.12 Number of Successful Inter-Frequency HSDPA Hard Handovers

Without Channel Change for Cell

BSC6900 UMTS
Counters
67190703 VS.HSDPA.HHO.H2H.Suc- Number of Successful Inter-

cOutInterFreq Frequency HSDPA Hard
Change for Cell
Description
This measurement item provides the number of successful inter-frequency hard handovers from
the HSDPA to the HSDPA in a cell. The hard handover procedure can be triggered with the
following messages:[1]PHYSICAL CHANNEL RECONFIGURATION,[2]TRANSPORT
CHANNEL RECONFIGURATION,[3]RADIO BEARER RECONFIGURATION,[4]RADIO
BEARER SETUP,[5]RADIO BEARER RELEASE message. Accordingly, UE may send [1]
PHYSICAL CHANNEL RECONFIGURATION COMPLETE,[2]PHYSICAL CHANNEL
RECONFIGURATION FAILURE,[3]TRANSPORT CHANNEL RECONFIGURATION
COMPLETE,[4]TRANSPORT CHANNEL RECONFIGURATION FAILURE,[5]RADIO
BEARER RECONFIGURATION COMPLETE,[6]RADIO BEARER RECONFIGURATION
FAILURE,[7]RADIO BEARER SETUP COMPLETE,[8]RADIO BEARER SETUP
FAILURE,[9]RADIO BEARER RELEASE COMPLETE,[10]RADIO BEARER RELEASE
FAILURE message to RNC as a response.For DC-HSDPA users, this counter is measured only
in the cell with the primary carrier.
VS.HSDPA.HHO.H2H.SuccOutInterFreq VS.HSDPA.HHO.H2H.SuccOutInterFreq
provides the number of successful inter-
frequency HSDPA hard handover attempts
without channel change in a cell.
Measurement point
The measurement is triggered at point B as shown in the figure, the procedure shown in the
figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an exampl, when
receiving from a UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message,the RNC measures this item in best the cell from which the UE is handed over if an
inter-frequency HSDPA hard handover without channel change is performed.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

cOutInterFreq Management
1.12.12.13 Number of HSDPA RAB Establishment Attempts for Cell
Counters
67190704 VS.HSDPA.RAB.AttEstab Number of HSDPA RAB

Cell

BSC6900 UMTS

BE.Golden Establishment Attempts of
BE Service for Golden Level
User for Cell

BE.Silver Establishment Attempts of
BE Service for Silver Level
User for Cell

BE.Copper Establishment Attempts of
BE Service for Copper Level
User for Cell
73403817 VS.HSDPA.RAB. Number of HSDPA 64QAM

64QAM.AttEstab RAB Setup Requests for cell
73403821 VS.HSDPA.RAB.MIMO.At Number of HSDPA MIMO

tEstab RABs Setup Request for Cell
73403824 VS.HSDPA.RAB.MIMO64 Number of HSDPA MIMO

QAM.AttEstab +64QAM RABs Setup
Request for cell
73403828 VS.HSDPA.RAB.DC.At- Number of DC-HSDPA

tEstab RAB Setup Requests in the
primary carrier of DC-
HSDPA counted for cell
73423378 VS.HSDPA.RAB.DCMIM Number of DC-HSDPA

O.AttEstab +MIMO RAB Setup
Requests in the Primary
Carrier of DC-HSDPA for
Cell
73426094 VS.HSDPA.RAB. Number of RAB Setup

3CMIMO.AttEstab Attempts for Cell When 3C-
HSDPA with MIMO Applied

3C.AttEstab Attempts for Cell When 3C-
HSDPA Applied

4CMIMO.AttEstab Attempts for Cell Where 4C-
73426106 VS.HSDPA.RAB.DBMIM Number of RAB Setup

O.AttEstab Attempts for Cell When DB-

BSC6900 UMTS

4C.AttEstab Attempts for Cell When 4C-
HSDPA Applied
73426114 VS.HSDPA.RAB.DB.At- Number of RAB Setup

tEstab Attempts for Cell When DB-
HSDPA Applied
Description
These counters provide the number of HSDPA RAB establishment attempts for different priority
level users (including gold, silver, and copper) when different features (such as 64QAM, MIMO,
and DC) are enabled in a cell.
For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC
receives a RAB ASSIGNMENT REQUEST message from the CN for setting up HSDPA
services, the RNC measures the measurement items by the priority level or used technology in
the serving cell.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSDPA.RAB.AttEstab WRFD-01061008 Interactive and Background

WRFD-010630 Traffic Class on HSDPA
HSDPA

BE.Golden Traffic Class on HSDPA

BE.Silver Traffic Class on HSDPA

BE.Copper Traffic Class on HSDPA
VS.HSDPA.RAB. WRFD-010683 Downlink 64QAM

64QAM.AttEstab
VS.HSDPA.RAB.MIMO.At WRFD-010684 2 x 2 MIMO

tEstab
VS.HSDPA.RAB.MIMO64 WRFD-010693 DL 64QAM+MIMO

QAM.AttEstab
VS.HSDPA.RAB.DC.At- WRFD-010696 DC-HSDPA

tEstab
VS.HSDPA.RAB.DCMIM WRFD-010699 DC-HSDPA+MIMO

O.AttEstab
VS.HSDPA.RAB. WRFD-150223 MC-HSDPA+MIMO

3CMIMO.AttEstab
VS.HSDPA.RAB. WRFD-150250 3C-HSDPA

3C.AttEstab

4CMIMO.AttEstab
VS.HSDPA.RAB.DBMIM WRFD-150227 DB-HSDPA+MIMO

O.AttEstab

4C.AttEstab

BSC6900 UMTS
VS.HSDPA.RAB.DB.At- WRFD-150209 DB-HSDPA

tEstab
1.12.12.14 Number of Successful HSDPA RAB Establishments for Cell
Counters
67190705 VS.HSDPA.RAB.SuccEstab Number of Successful

HSDPA RAB

.BE.Golden HSDPA RAB
Establishments of BE
Service for Golden Level
User for Cell

.BE.Silver HSDPA RAB
Service for Silver Level User
for Cell

.BE.Copper HSDPA RAB
Service for Copper Level
User for Cell
73403818 VS.HSDPA.RAB. Number of HSDPA 64QAM

64QAM.SuccEstab RABs Setup Successfully for
cell
73403822 VS.HSDPA.RAB.MIMO.Su Number of HSDPA MIMO

ccEstab RABs Setup Successfully for
cell
73403825 VS.HSDPA.RAB.MIMO64 Number of HSDPA MIMO

QAM.SuccEstab +64QAM RABs Setup
73403829 VS.HSDPA.RAB.DC.Suc- Number of DC-HSDPA

cEstab RABs Setup Successfully in
the primary carrier of DC-
HSDPA counted for cell

BSC6900 UMTS
73423379 VS.HSDPA.RAB.DCMIM Number of Successful DC-

O.SuccEstab HSDPA+MIMO RAB
Setups in the Primary Carrier
of DC-HSDPA for cell
73426095 VS.HSDPA.RAB. Number of Successful RAB

3CMIMO.SuccEstab Setups for Cell When 3C-

3C.SuccEstab Setups for Cell When 3C-
HSDPA Applied

4CMIMO.SuccEstab Setups for Cell When 4C-
73426107 VS.HSDPA.RAB.DBMIM Number of Successful RAB

O.SuccEstab Setups for Cell When DB-

4C.SuccEstab Setups for Cell When 4C-
HSDPA Applied
73426115 VS.HSDPA.RAB.DB.Suc- Number of Successful RAB

cEstab Setups for Cell When DB-
HSDPA Applied
Description
These counters provide the number of HSDPA RAB establishment attempts for different priority
level users (including gold, silver, and copper) when different features (such as 64QAM, MIMO,
and DC) are enabled in a cell.
For DC-HSDPA, 3C-HSDPA, 4C-HSDPA, or DB-HSDPA users, this counter is measured only
in the cell with the primary carrier.
Measurement point
The measurement is triggered at point B as shown in the following figure. After receiving a
RADIO BEARER SETUP COMPLETE message from the UE, the RNC sends the CN a RAB
ASSIGNMENT RESPONSE message. If the assignment is for setting up HSDPA services, the
RNC measures the measurement items by the priority level or used technology in the serving
cell.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

HSDPA

.BE.Golden Traffic Class on HSDPA

.BE.Silver Traffic Class on HSDPA

.BE.Copper Traffic Class on HSDPA

BSC6900 UMTS
VS.HSDPA.RAB. WRFD-010683 Downlink 64QAM

64QAM.SuccEstab
VS.HSDPA.RAB.MIMO.Su WRFD-010684 2 x 2 MIMO

ccEstab
VS.HSDPA.RAB.MIMO64 WRFD-010693 DL 64QAM+MIMO

QAM.SuccEstab
VS.HSDPA.RAB.DC.Suc- WRFD-010696 DC-HSDPA

cEstab

O.SuccEstab

3CMIMO.SuccEstab

3C.SuccEstab

4CMIMO.SuccEstab
VS.HSDPA.RAB.DBMIM WRFD-150227 DB-HSDPA+MIMO

O.SuccEstab

4C.SuccEstab
VS.HSDPA.RAB.DB.Suc- WRFD-150209 DB-HSDPA

cEstab
1.12.12.15 Number of HSDPA RABs Abnormal Released for Cell
Counters
67191162 VS.HSDPA.RAB.Abnorm- Number of HSDPA RABs

Rel Abnormal Released for Cell
67191163 VS.HSDPA.RAB.AbnormR Number of HSDPA RABs

el.RF Abnormal Released Due to
RF Cause for Cell
73403819 VS.HSDPA.RAB.Abnorm- Number of HSDPA 64QAM

Rel.64QAM RABs Abnormal Released
for cell

BSC6900 UMTS
73403826 VS.HSDPA.RAB.AbnormR Number of HSDPA MIMO

el.MIMO64QAM +64QAM RABs Abnormal
Released for cell
73403830 VS.HSDPA.RAB.AbnormR Number of DC-HSDPA

el.DC RABs Abnormal Released in
the primary carrier of DC
counted for Cell(including
RF Cause)
73403832 VS.HSDPA.RAB.AbnormR Number of HSDPA MIMO

el.MIMO RABs Abnormal Released
for cell(Including RF Cause)
73423381 VS.HSDPA.RAB.DCMIM Number of Abnormal DC-

O.AbnormRel HSDPA+MIMO RAB
Releases in the Primary
cell
73426096 VS.HSDPA.RAB.Abnorm- Number of Abnormally

Rel.3CMIMO Released RABs for Cell
When 3C-HSDPA with
MIMO Applied (RF
Exceptions Considered)

Rel.3C Released RABs for Cell
When 3C-HSDPA Applied
(RF Exceptions Considered)

Rel.4CMIMO Released RABs for Cell
When 4C-HSDPA with
MIMO Applied (RF
73426112 VS.HSDPA.RAB.Abnorm- Number of Abnormal

Rel.4C Released RABs for Cell
73426116 VS.HSDPA.RAB.AbnormR Number of Abnormally

el.DB Released RABs for Cell
When DB-HSDPA Applied

el.SRBoH Released RABs of SRB over
HSDPA Users for Cell

BSC6900 UMTS
Description
These counters provide the number of times RABs are abnormally released when different
technologies such as 64QAM, MIMO, and DC are used due to different factors including the
RF failures in a serving cell.
Note: Unless otherwise specified, SRB over HSDPA users are in the CELL_DCH state, and
their SRBs are carried on the HSDPA channel.
VS.HSDPA.RAB.AbnormRel VS.HSDPA.RAB.AbnormRel provides the

number of abnormal HSDPA RAB releases
in a cell.
VS.HSDPA.RAB.AbnormRel.RF VS.HSDPA.RAB.AbnormRel.RF provides

the number of times HSDPA RABs are
abnormally released due to RF failures in a
cell. RF failures are indicated by the IEs
"Radio Connection With UE Lost" and
"Failure in the Radio Interface Procedure."
Measurement point
As shown in point A of the following figure, when an exception occurs, the RNC sends the CN
a RAB RELEASE REQUEST message. If the RNC receives from the CN a RAB
ASSIGNMENT REQUEST message which contains a cause value of abnormal release, the
counters related to abnormal release when different technologies are used are measured.

BSC6900 UMTS
a RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE
COMMAND message which contains a cause value of abnormal release, the counters related
to abnormal release when different technologies are used are measured.

BSC6900 UMTS
an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE
COMMAND message which contains a cause value of abnormal release, the counters related
to abnormal release when different technologies are used are measured.
The cause values for normal release include "User Inactivity", "Normal Release", "Successful
Relocation", and "Network Optimization". For details, see 3GPP TS 25.413.
Formula
None
Unit
None
Related Features
VS.HSDPA.RAB.Abnorm- WRFD-01061008 Interactive and Background

Rel WRFD-010630 Traffic Class on HSDPA
HSDPA

BSC6900 UMTS
VS.HSDPA.RAB.AbnormR WRFD-01061008 Interactive and Background

el.RF WRFD-010630 Traffic Class on HSDPA
HSDPA
VS.HSDPA.RAB.Abnorm- WRFD-010683 Downlink 64QAM

Rel.64QAM
VS.HSDPA.RAB.AbnormR WRFD-010693 DL 64QAM+MIMO

el.MIMO64QAM
VS.HSDPA.RAB.AbnormR WRFD-010696 DC-HSDPA

el.DC
VS.HSDPA.RAB.AbnormR WRFD-010684 2 x 2 MIMO

el.MIMO

O.AbnormRel
VS.HSDPA.RAB.Abnorm- WRFD-150223 MC-HSDPA+MIMO

Rel.3CMIMO
VS.HSDPA.RAB.Abnorm- WRFD-150250 3C-HSDPA

Rel.3C
VS.HSDPA.RAB.Abnorm- WRFD-150223 MC-HSDPA+MIMO

Rel.4CMIMO

Rel.4C
VS.HSDPA.RAB.AbnormR WRFD-150209 DB-HSDPA

el.DB
VS.HSDPA.RAB.AbnormR WRFD-010652 SRB over HSDPA

el.SRBoH
1.12.12.16 Number of HSDPA RABs Normal Released for Cell
Counters
67191164 VS.HSDPA.RAB.NormRel Number of HSDPA RABs

Normal Released for Cell
67191161 VS.HSDPA.RAB.NormRel. Number of HSDPA RAB

UsrInact Releases Due to User
Inactivity for Cell

BSC6900 UMTS
73403820 VS.HSDPA.RAB.NormRel. Number of HSDPA 64QAM

64QAM RABs Normal Released for
Cell
73403823 VS.HSDPA.RAB.NormRel. Number of HSDPA MIMO

MIMO RABs Normal Released for
cell
73403827 VS.HSDPA.RAB.NormRel. Number of HSDPA MIMO

MIMO64QAM +64QAM RABs Normal
Released for cell
73403831 VS.HSDPA.RAB.NormRel. Number of DC-HSDPA

DC RABs Normal Released in
the primary carrier of DC
counted for Cell
73423380 VS.HSDPA.RAB.DCMIM Number of Normal DC-

O.NormRel HSDPA+MIMO RAB
Releases in the Primary
cell
73426097 VS.HSDPA.RAB.NormRel. Number of Normally

3CMIMO Released RABs for Cell
When 3C-HSDPA with
MIMO Applied

3C Released RABs for Cell

4CMIMO Released RABs for Cell
When 4C-HSDPA with
MIMO Applied

DBMIMO Released RABs for Cell
When DB-HSDPA with
MIMO Applied

4C Released RABs for Cell

DB Released RABs for Cell
When DB-HSDPA Applied

BSC6900 UMTS
Description
technologies such as 64QAM, MIMO, and DC are used in a serving cell.
VS.HSDPA.RAB.NormRel VS.HSDPA.RAB.NormRel provides the

number of normal HSDPA RAB releases in a
cell.
VS.HSDPA.RAB.NormRel.UsrInact VS.HSDPA.RAB.NormRel.UsrInact
provides the number of normal HSDPA RAB
releases due to user inactivity in a cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. Upon receiving an
IU RELEASE COMMAND message from the CN, the RNC releases related RABs and then
sends the CN an IU RELEASE COMPLETE message. If the IU RELEASE COMPLETE
message carries a cause value of normal release and HSDPA services are performed, the RNC
measures the related counter in the serving cell according to the used technology.
The measurement is triggered at point B as shown in the following figure. Upon receiving a
RAB ASSIGNMENT REQUEST message that carries the RABs to be released, the RNC

BSC6900 UMTS
releases the related RABs and then sends the CN a RAB ASSIGNMENT RESPONSE message.
If the RAB ASSIGNMENT REQUEST message carries a cause value of normal release, HSDPA
services are performed, and 4C-HSDPA is enabled, the RNC measures the related counter in
the serving cell according to the used technology.
The cause values for normal release include "User Inactivity", "Normal Release", "Successful
Relocation", and "Network Optimization". For details, see 3GPP TS 25.413.
Formula
None
Unit
None
Related Features
VS.HSDPA.RAB.NormRel WRFD-01061008 Interactive and Background

HSDPA

BSC6900 UMTS
VS.HSDPA.RAB.NormRel. WRFD-01061008 Interactive and Background

UsrInact WRFD-010630 Traffic Class on HSDPA
HSDPA
VS.HSDPA.RAB.NormRel. WRFD-010683 Downlink 64QAM

64QAM
VS.HSDPA.RAB.NormRel. WRFD-010684 2 x 2 MIMO

MIMO
VS.HSDPA.RAB.NormRel. WRFD-010693 DL 64QAM+MIMO

MIMO64QAM
VS.HSDPA.RAB.NormRel. WRFD-010696 DC-HSDPA

DC

O.NormRel
VS.HSDPA.RAB.NormRel. WRFD-150223 MC-HSDPA+MIMO

3CMIMO
VS.HSDPA.RAB.NormRel. WRFD-150250 3C-HSDPA

3C
VS.HSDPA.RAB.NormRel. WRFD-150223 MC-HSDPA+MIMO

4CMIMO
VS.HSDPA.RAB.NormRel. WRFD-150227 DB-HSDPA+MIMO

DBMIMO

4C
VS.HSDPA.RAB.NormRel. WRFD-150209 DB-HSDPA

DB
1.12.12.17 Number of Inter-RNC HSDPA Hard Handover Attempts for Cell

(HSDPA to DCH)
Counters
73403764 VS.HSDPA.HHO.H2D.At- number of Inter-RNC H2D

tOutIur Hard Handover Attempts for
Cell

BSC6900 UMTS
67191157 VS.HSDPA.HHO.H2D.At- Number of Intra-Frequency

tOutIntraFreq H2D Hard Handover
Attempts for Cell
67191159 VS.HSDPA.HHO.H2D.At- Number of Inter-Frequency

tOutInterFreq H2D Hard Handover
Attempts for Cell
Description
These counters provide the number of successful outgoing DCH hard handovers of different
types on the HSDPA channel in a serving cell. For multi-carrier HSDPA users, this counter is
VS.HSDPA.HHO.H2D.AttOutIur VS.HSDPA.HHO.H2D.AttOutIur provides

the number of inter-RNC hard handover from
HSDPA to DCH attempts in the serving cell.
VS.HSDPA.HHO.H2D.AttOutIntraFreq VS.HSDPA.HHO.H2D.AttOutIntraFreq
provides the number of intra-frequency hard
handover from HSDPA to DCH attempts in a
cell.
VS.HSDPA.HHO.H2D.AttOutInterFreq VS.HSDPA.HHO.H2D.AttOutInterFreq
provides the number of inter-frequency hard
handover from HSDPA to DCH attempts in a
cell.
Measurement point
During the hard handover from the HSDPA channel to the DCH, the RNC may send the UE the
following messages:
sends the UE a RADIO BEARER RECONFIGURATION message, the RNC measures these
counters in the best cell before the hard handover according to the hard handover type.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSDPA.HHO.H2D.At- WRFD-01061006 HSDPA Mobility

tOutIur Management


1.12.12.18 Number of Successful inter-RNC HSDPA Hard Handovers for Cell

(HSDPA to DCH)

BSC6900 UMTS
Counters
73403765 VS.HSDPA.HHO.H2D.Suc- Number of Successful Inter-

cOutIur RNC H2D Hard Handovers
for Cell
67191158 VS.HSDPA.HHO.H2D.Suc- Number of Successful Intra-

cOutIntraFreq Frequency H2D Hard
Handovers for Cell
67191160 VS.HSDPA.HHO.H2D.Suc- Number of Successful Inter-

cOutInterFreq Frequency H2D Hard
Handovers for Cell
Description
These counters provide the number of successful outgoing hard handovers of different types
from the HSDPA channel to the DCH in a serving cell.
VS.HSDPA.HHO.H2D.SuccOutIur VS.HSDPA.HHO.H2D.SuccOutIur provides

the number of successful inter-RNC hard
handovers from HSDPA to DCH in a cell.
VS.HSDPA.HHO.H2D.SuccOutIntraFreq VS.HSDPA.HHO.H2D.SuccOutIntraFreq
provides the number of successful intra-
frequency hard handovers from HSDPA to
DCH in a cell.
VS.HSDPA.HHO.H2D.SuccOutInterFreq VS.HSDPA.HHO.H2D.SuccOutInterFreq
provides the number of successful inter-
frequency hard handovers from HSDPA to
DCH in a cell.
Measurement point
During the hard handover from the HSDPA channel to the DCH, the RNC may send the UE the
following messages:

BSC6900 UMTS
sends the UE a RADIO BEARER RECONFIGURATION COMPLETE message, the RNC
measures these counters in the best cell before the hard handover according to the hard handover
type.
Formula
None
Unit
None
Related Features
VS.HSDPA.HHO.H2D.Suc- WRFD-01061006 HSDPA Mobility

cOutIur Management


1.12.12.19 Number of HSDPA UEs with Various Categories in a Cell

BSC6900 UMTS
Counters
67204259 VS.HSDPA.UE.Mean.CAT Average Number of HSDPA

1.6 UEs with Category 1-6 in a
Cell
67193578 VS.HSDPA.UE.Max.CAT1. Maximum Number of

6 HSDPA UEs with Category
1-6 in a Cell

Cell
67193581 VS.HSDPA.UE.Max.CAT7. Maximum Number of

10 HSDPA UEs with Category
7-10 in a Cell

11.12 UEs with Category 11-12 in
a Cell
67193584 VS.HSDPA.UE.Max.CAT1 Maximum Number of

1.12 HSDPA UEs with Category
11-12 in a Cell

a Cell

13-14 in a Cell

a Cell

15-16 in a Cell

a Cell

17-20 in a Cell

a Cell

BSC6900 UMTS

21-24 in a Cell

25-28 in a Cell

a Cell
73426132 VS.HSDPA.UE.Mean.CAT Average number of Category

29 29 HSDPA users in a cell
73426133 VS.HSDPA.UE.Max.CAT2 Maximum number of

9 Category 29 HSDPA users in
a cell


a cell


a cell


a cell
specific formulas.

11.12.DENO UEs with Category 11-12 in
a Cell(Denominator)

BSC6900 UMTS

11.12.NUM UEs with Category 11-12 in
a Cell(Numerator)

a Cell(Denominator)

a Cell(Numerator)

a Cell(Denominator)

a Cell(Numerator)

a Cell(Denominator)

a Cell(Numerator)
67193577 VS.HSDPA.UE.Mean.CAT Average num of CAT1-6

1.6.DENO HSDPA UEs (Denominator)

1.6.NUM UEs with Category 1-6 in a
Cell(Numerator)

a Cell(Denominator)

a Cell(Numerator)

a Cell(Denominator)

a Cell(Numerator)

BSC6900 UMTS

7.10.DENO UEs with Category 7-10 in a
Cell(Denominator)

Cell(Numerator)
Description
These counters provide the average and maximum number of HSDPA UEs with various
categories in a serving cell. The HSDPA UE category used for the measurement depends on the
actual CAT capability of HSDPA UEs and the capability required for service setup. The HSDPA
UEs with categories 21-28 using the multi-carrier HSDPA feature are only sampled in the cells
with primary carriers.
Measurement point
The system takes samples of the number of HSDPA UEs with various categories every 5s. At
the end of the measurement period, by dividing the accumulated value of sample data in the
period by the number of samples, the average number of HSDPA UEs with various categories
in the measurement period is obtained; by selecting the maximum value of sample data in the
period, the maximum number of HSDPA UEs with various categories in the measurement period
is obtained.
Formula
VS.HSDPA.UE.Mean.CAT1.6 = [VS.HSDPA.UE.Mean.CAT1.6.NUM]/
[VS.HSDPA.UE.Mean.CAT1.6.DENO]

BSC6900 UMTS
Unit
None
Related Features
VS.HSDPA.UE.Mean.CAT WRFD-01061002 HSDPA UE Category 1 to 28

1.6
VS.HSDPA.UE.Max.CAT1. WRFD-01061002 HSDPA UE Category 1 to 28

6

7.10
VS.HSDPA.UE.Max.CAT7. WRFD-01061002 HSDPA UE Category 1 to 28

10

11.12
VS.HSDPA.UE.Max.CAT1 WRFD-01061002 HSDPA UE Category 1 to 28

1.12

13.14

3.14

15.16

5.16

17.20

7.20

21.24

1.24
VS.HSDPA.UE.Max.CAT2 WRFD-010699 DC-HSDPA+MIMO

5.28
VS.HSDPA.UE.Mean.CAT WRFD-010699 DC-HSDPA+MIMO

25.28

BSC6900 UMTS
VS.HSDPA.UE.Mean.CAT WRFD-150250 3C-HSDPA

29
VS.HSDPA.UE.Max.CAT2 WRFD-150250 3C-HSDPA

9

30

0

31

1

32

2
1.12.12.20 Number of HSDPA MAC-d Flow Establishment Requests for Cell
Counters
73393828 VS.HSDPA.MACD.AttSet- Number of HSDPA MAC-d

up Flow Establishment
Requests for Cell
Description
This counter provides the number of HSDPA MAC-d flow establishment requests in the cell.For
DC-HSDPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
The measurement can be triggered at point A as shown in the figure. When the RNC sends the
NodeB a RADIO LINK SETUP REQUEST message, this counter is measured in the HSDPA
serving cell if the message contains the "HSDSCH FDD Information" IE.

BSC6900 UMTS
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSDPA.MACD.AttSet- WRFD-010610 HSDPA Introduction

up Package
1.12.12.21 Number of Failed HSDPA Service Establishments Due to Insufficiency

of Different Resources
Counters
73393830 VS.HSDPA.RAB.FailEstab. Number of Failed HSDPA

DLPower.Cong Service Establishments Due
to DL Power Insufficiency
for Cell
73393831 VS.HSDPA.RAB.FailEstab. Number of Failed HSDPA

DLIUBBand.Cong Service Establishments Due
to DL Iub Bandwidth
Description
These counters provide the number of HSDPA RABs failed to be established due to insufficiency
of different resources in the HSDPA serving cell. For multi-carrier HSDPA users, this counter
is measured only in the cell with the primary carrier.
VS.HSDPA.RAB.FailEstab.DLPower.Cong provides the number of HSDPA RABs failed to be
established due to insufficient downlink power resources.
VS.HSDPA.RAB.FailEstab.DLIUBBand.Cong provides the number of HSDPA RABs failed to
be established due to insufficient downlink Iub bandwidth resources.
Measurement point
the CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request,

BSC6900 UMTS
it requests related radio resources. This counter is measured in the HSDPA serving cell when
the RAB is for a HSDPA service and the resource request fails.
Figure 1-516 Failed RAB establishments due to resource insufficiency
Formula
None
Unit
None
Related Features
VS.HSDPA.RAB.FailEstab. WRFD-01061003 HSDPA Admission Control

DLPower.Cong
VS.HSDPA.RAB.FailEstab. WRFD-01061003 HSDPA Admission Control

DLIUBBand.Cong
1.12.12.22 Number of MIMO UEs in a Cell

BSC6900 UMTS
Counters
73410492 VS.HSDPA.MIMO.UE.Mea Average Number of MIMO

n.Cell UEs in a Cell
specific formulas.

n.Cell.DENO UEs in a Cell(Denominator)

n.Cell.NUM UEs in a Cell(Numerator)
Description
This counter provides the average number of MIMO UEs in a serving cell.For DC-HSDPA users,
this counter is measured only in the cell with the primary carrier.
Measurement point
The system periodically takes samples(sampling periodicity is 5 seconds) of the number of
MIMO UEs. At the end of the measurement period, by dividing the accumulated value of sample
data in the period by the number of samples, the average number of MIMO UEs in the
measurement period is obtained.
Formula
VS.HSDPA.MIMO.UE.Mean.Cell = [VS.HSDPA.MIMO.UE.Mean.Cell.NUM]/
[VS.HSDPA.MIMO.UE.Mean.Cell.DENO]
Unit
None
Related Features
VS.HSDPA.MIMO.UE.Mea WRFD-010684 2 x 2 MIMO

n.Cell

BSC6900 UMTS
1.12.12.23 Number of Outgoing DRD Attempts for HSDPA Users Through

Intelligent User Recognition for Cell
Counters
73421686 VS.HSDPA.DRD.AttOut.Int Number of Outgoing DRD

elligence Attempts for HSDPA Users
Through Intelligent User
73421688 VS.HSDPA.DRD.AttIn.In- Number of Incoming DRD

telligence Attempts for HSDPA Users
Through Intelligent User
Description
These counters provide the number of times the RNC attempts to switch HSDPA users in
connected mode into or out of the serving cell through the DRD procedure according to the
intelligent user recognition algorithm in the HSDPA serving cell. For multi-carrier HSDPA
VS.HSDPA.DRD.AttOut.Intelligence VS.HSDPA.DRD.AttOut.Intelligence
provides the number of times the RNC
attempts to switch HSDPA users in connected
mode out of the serving cell through the DRD
procedure according to the intelligent user
recognition algorithm.
VS.HSDPA.DRD.AttIn.Intelligence VS.HSDPA.DRD.AttIn.Intelligence
attempts to switch HSDPA users in connected
mode into the serving cell through the DRD
procedure according to the intelligent user
recognition algorithm.
Measurement point
The measurement is triggered at point A as shown in the following figure. According to the
intelligent user recognition algorithm, after the RNC receives a Channel Quality Indicator (CQI)
measurement report from the NodeB, the RNC selects a proper target cell and then initiates an
inter-frequency handover. Before the handover, the RNC takes statistics of the number of times
that the RNC attempts to switch HSDPA users in connected mode out of the serving cell through

BSC6900 UMTS
the DRD procedure. The RNC takes statistics of the number of times that the RNC attempts to
switch HSDPA users in connected mode into the target cell through the DRD procedure.
Figure 1-517 The DRD Process triggered by Intelligent User Recognition
Formula
None
Unit
None
Related Features
VS.HSDPA.DRD.AttOut.Int WRFD-01061004 HSDPA Power Control

elligence
VS.HSDPA.DRD.AttIn.In- WRFD-01061004 HSDPA Power Control

telligence

BSC6900 UMTS
1.12.12.24 Number of Successful Outgoing DRDs for HSDPA Users Through

Intelligent User Recognition for Cell
Counters
73421687 VS.HSDPA.DRD.SuccOut.I Number of Successful

ntelligence Outgoing DRDs for HSDPA
Users Through Intelligent
User Recognition for Cell
73421689 VS.HSDPA.DRD.SuccIn.Int Number of Successful

elligence Incoming DRDs for HSDPA
Users Through Intelligent
User Recognition for Cell
Description
These counters provide the number of times the RNC successfully switches HSDPA users in
connected mode into or out of the serving cell through the DRD procedure according to the
intelligent user recognition algorithm in the HSDPA serving cell. For multi-carrier HSDPA
VS.HSDPA.DRD.SuccOut.Intelligence VS.HSDPA.DRD.SuccOut.Intelligence
successfully switches HSDPA users in
connected mode out of the serving cell
through the DRD procedure according to the
intelligent user recognition algorithm.
VS.HSDPA.DRD.SuccIn.Intelligence VS.HSDPA.DRD.SuccIn.Intelligence
successfully switches HSDPA users in
connected mode into the serving cell through
the DRD procedure according to the
intelligent user recognition algorithm.
Measurement point
receives a PHYSICAL CHANNEL RECONFIG COMPLETE message from the UE, the RNC
measures the number of times HSDPA users in connected mode are successfully switched out
of the serving cell before the DRD procedure if an inter-frequency handover is to be performed
on HSDPA users using the intelligent user recognition algorithm. The RNC measures the number

BSC6900 UMTS
of times HSDPA users are successfully switched into the target cell through the DRD procedure
in the target cell for DRD. Note that this counter is measured for only HSDPA users in connected
mode.
Figure 1-518 The DRD Process triggered by Intelligent User Recognition
Formula
None
Unit
None
Related Features
VS.HSDPA.DRD.SuccOut.I WRFD-01061004 HSDPA Power Control

ntelligence
VS.HSDPA.DRD.SuccIn.Int WRFD-01061004 HSDPA Power Control

elligence

BSC6900 UMTS
1.12.12.25 Number of RABs Abnormally Released for PS HSDPA Services during

the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell
Counters
73422167 VS.HSDPA.RAB.AbnormR Number of RABs

el.H2P Abnormally Released for PS
HSDPA Services during the
State Transition from
CELL_DCH to CELL_PCH
or URA_PCH for Cell
73425928 VS.HSDPA.RAB.AbnormR Number of Abnormal RAB

el.DC2P Releases for Cell During
State Transition of DC-
HSDPA UEs to CELL/
URA_PCH
73425929 VS.HSDPA.RAB.Abnorm- Number of Abnormal RAB

Rel.64QAM2P Releases for Cell During
State Transition of HSDPA
+64QAM UEs to CELL/
URA_PCH

el.MIMO2P Releases for Cell During
State Transition of MIMO
UEs to CELL/URA_PCH

el.DCMIMO2P Releases for Cell During
HSDPA+MIMO UEs to
CELL/URA_PCH

el.MIMO64QAM2P Releases for Cell During
State Transition of MIMO
+64QAM UEs to CELL/
URA_PCH

Rel.3C2P Releases for Cell During
State Transition of 3C-
HSDPA UEs to CELL/
URA_PCH

BSC6900 UMTS

Rel.3CMIMO2P Releases for Cell During
HSDPA+MIMO UEs to
CELL/URA_PCH

Rel.4C2P Releases for Cell During
HSDPA UEs to CELL/
URA_PCH

Rel.4CMIMO2P Releases for Cell During
HSDPA+MIMO UEs to
CELL/URA_PCH

el.DB2P Releases for Cell During
State Transition of DB-
HSDPA UEs to CELL/
URA_PCH

el.DBMIMO2P Releases for Cell During
State Transition of DB-
HSDPA+MIMO UEs to
CELL/URA_PCH

el.SRBoH.H2P Released RABs During State
Transition of SRB over
HSDPA Users to
CELL_PCH or URA_PCH
for Cell
Description
technologies such as 64QAM, MIMO, and DC are used due to different factors including the
RF failures in a serving cell. For multi-carrier HSDPA users, this counter is measured only in
the cell with the primary carrier. Note: Unless otherwise specified, SRB over HSDPA users are
in the CELL_DCH state, and their SRBs are carried on the HSDPA channel.
Measurement point
As shown in point A of the following figure. When the UE fails to transit to CELL_PCH or
URA_PCH, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives

BSC6900 UMTS
from the CN a RAB ASSIGNMENT REQUEST message which contains a cause value of
abnormal release, the counters related to abnormal release when different technologies are used
are measured.
URA_PCH, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives
from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal
release, the counters related to abnormal release when different technologies are used are
measured.

BSC6900 UMTS
URA_PCH, the RNC sends the CN an IU RELEASE REQUEST message. If the RNC receives
from the CN an IU RELEASE COMMAND message which contains a cause value of abnormal
release, the counters related to abnormal release when different technologies are used are
measured. The cause values for normal release include "User Inactivity", "Normal Release",
"Successful Relocation", and "Network Optimization". For details, see 3GPP TS 25.413.

BSC6900 UMTS
Figure 1-521 IU release procedure triggered by the RNC
Formula
None
Unit
None
Related Features
VS.HSDPA.RAB.AbnormR WRFD-010202 UE State in Connected Mode

el.H2P WRFD-010610 (CELL-DCH, CELL-PCH,
URA-PCH, CELL-FACH)
HSDPA Introduction
Package
VS.HSDPA.RAB.AbnormR WRFD-010696 DC-HSDPA

el.DC2P
VS.HSDPA.RAB.Abnorm- WRFD-010683 Downlink 64QAM

Rel.64QAM2P
VS.HSDPA.RAB.AbnormR WRFD-010684 2 x 2 MIMO

el.MIMO2P

BSC6900 UMTS
VS.HSDPA.RAB.AbnormR WRFD-010699 DC-HSDPA+MIMO

el.DCMIMO2P
VS.HSDPA.RAB.AbnormR WRFD-010693 DL 64QAM+MIMO

el.MIMO64QAM2P

Rel.3C2P

Rel.3CMIMO2P

Rel.4C2P

Rel.4CMIMO2P
VS.HSDPA.RAB.AbnormR WRFD-150209 DB-HSDPA

el.DB2P
VS.HSDPA.RAB.AbnormR WRFD-150227 DB-HSDPA+MIMO

el.DBMIMO2P
VS.HSDPA.RAB.AbnormR WRFD-010652 SRB over HSDPA

el.SRBoH.H2P
1.12.12.26 Average Throughput on HSDPA MAC-d Flow for Cell (Excluding the
Data of Low-Traffic Users)
Counters
73441141 VS.HSDPA.MeanChThroup Mean Throughput on

ut.HighLoad HSDPA MAC-d Flow for
Cell (Excluding the Data of
Low-Traffic Users)
specific formulas.

BSC6900 UMTS
73423463 VS.HSDPA.Times.High- Duration of Data Sending on

Load HSDPA MAC-d flow for
Cell (Excluding the Duration
of Data Sending by Low-
Traffic Users)
Description
This counter provides the mean downlink throughput on HSDPA Single MAC-d flow in a cell.
It excludes the data sent by low-traffic users.For DC-HSDPA users, this counter is measured
only in the primary cell based on the total throughput on the primary and secondary carriers.
Measurement point
The amount of data that is sent in downlink on HSDPA MAC-d flow at the RLC layer (excluding
the retransmitted RLC data and RLC headers) is measured every second in the serving cell.
The amount of data that is measured in one second is considered as valid only when the amount
of data received on the Iu interface within that second is greater than or equal to 80 KB and the
amount of data in the RLC buffer within that second is greater than or equal to 80 KB.
At the end of the measurement period, the mean throughput on HSDPA MAC-d flow is
calculated by dividing the total amount of data that is considered as valid by the total period of
valid time. Note that the total amount of data excludes the data sent by low-traffic users.
Formula
VS.HSDPA.MeanChThrouput.HighLoad = {8}*[VS.HSDPA.Traffic.HighLoad]/
[VS.HSDPA.Times.HighLoad]
Unit
kbit/s
Related Features
VS.HSDPA.MeanChThroup WRFD-010610 HSDPA Introduction

ut.HighLoad WRFD-01061008 Package
Interactive and Background
Traffic Class on HSDPA
1.12.12.27 Number of Bytes Sent on HSDPA MAC-d Flow for Cell (Excluding the
Bytes of Low-Traffic Users)

BSC6900 UMTS
Counters
73423462 VS.HSDPA.Traffic.High- Number of Bytes Sent on

Load HSDPA MAC-d Flow for
Cell (Excluding the Bytes of
Low-Traffic Users)
Description
This counter provides the number of bytes that are sent in downlink on HSDPA MAC-d flow
in a cell. It excludes the number of bytes that are sent by low-traffic users.For DC-HSDPA users,
this counter is measured only in the primary cell based on the total number of bytes sent on the
primary and secondary carriers.
Measurement point
The number of bytes that are sent in downlink on HSDPA MAC-d flow at the RLC layer
(excluding the retransmitted RLC data and RLC headers) is measured every second in the serving
cell.
The number of bytes that is measured in one second is calculated into the counter only when the
amount of data received on the Iu interface within that second is greater than or equal to 80 KB
and the amount of data in the RLC buffer within that second is greater than or equal to 80 KB.
At the end of the measurement period, the number of bytes that can be calculated into the counter
is accumulated. Note that the total number of bytes excludes the number of bytes sent by low-
traffic users at the RLC layer.
Formula
None
Unit
byte
Related Features
VS.HSDPA.Traffic.High- WRFD-010610 HSDPA Introduction

Load WRFD-01061008 Package
Interactive and Background
Traffic Class on HSDPA
1.12.12.28 Number of Normal RAB Releases of HSDPA UEs for Cell (All Scenarios)

BSC6900 UMTS
Counters
73425939 VS.HSDPA.RAB.NormRel. Number of Normal RAB

DC.All Releases of DC-HSDPA UEs
for Cell (All Scenarios)

64QAM.All Releases of HSDPA
+64QAM UEs for Cell (All
Scenarios)

MIMO.All Releases of HSDPA+MIMO
UEs for Cell (All Scenarios)

DCMIMO.All Releases of DC-HSDPA
+MIMO UEs for Cell (All
Scenarios)

MIMO64QAM.All Releases of HSDPA MIMO
Scenarios)

3C.All Releases of 3C-HSDPA UEs

3CMIMO.All Releases of 3C-HSDPA
Scenarios)

4C.All Releases of 4C-HSDPA UEs

4CMIMO.All Releases of 4C-HSDPA
Scenarios)

DB.All Releases of DB-HSDPA UEs

DBMIMO.All Releases of DB-HSDPA
Scenarios)

BSC6900 UMTS

SRBoH.All Released RABs of SRB over
HSDPA Users for Cell (All
Scenarios)
Description
These counters provide the number of normal RAB releases in a cell where HSDPA is applied.
For multi-carrier HSDPA UEs, these counters are measured only in the primary carrier cell.
Note: The normal RAB releases on HSDPA channels include the RAB releases over the Iu
interface and the switchover of the RAB from a technique to another one.
The following uses DC-HSDPA as an example to describe a normal RAB release.
(1)The DC-HSDPA RAB has been released over the Iu interface.
(2)The RAB successfully falls back from DC-HSDPA to SC-HSDPA or R99 through a channel
switchover procedure. In R99, the UE can be in the CELL_DCH, CELL_FACH, CELL_PCH,
or URA_PCH state.
(3)The RAB successfully falls back from DC-HSDPA to SC-HSDPA or to R99 in CELL_DCH
state through an inter-cell hard handover procedure.
Note: Unless otherwise specified, SRB over HSDPA users are in the CELL_DCH state, and
their SRBs are carried on the HSDPA channel.
Measurement point
As shown by point A in figure 1 (HSDPA UEs enter the idle state), after receiving an IU
RELEASE COMMAND message from the CN, the RNC releases the corresponding RAB and
then sends an IU RELEASE COMPLETE message to the CN. This counter is increased by one
in the serving cell where the UE camps when either of the following condition is met: The cause
value in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release",
"Successful Relocation", or "Network Optimization." Alternatively, the RNC has initiated a
release request with the cause value "User Inactivity", "Network Optimization", or "UE
Generated Signalling Connection Release" before receiving the IU RELEASE COMMAND
message.

BSC6900 UMTS
As shown by point B in figure 2 (HSDPA UEs enter the idle state), after receiving an RAB
to the CN. This counter is increased by one in the serving cell where the UE camps when either
of the following condition is met: The cause value in the RAB ASSIGNMENT REQUEST
message is "User Inactivity", "Normal Release", "Successful Relocation", or "Network
Optimization." Alternatively, the RNC has initiated a release request with the cause value "User
receiving the RAB ASSIGNMENT REQUEST message.
As shown by point B in figure 3 (all types of hard handovers for HSDPA UEs), the RNC receives
a RADIO BEARER RECONFIGURATION COMPLETE message from a UE. If the UE is
performing a hard handover on the RAB from a HSDPA channel to channels of other types, this
counter is increased by one in the serving cell of the UE. As shown by point B in figure 3 (all
types of channel switchovers for HSDPA UEs), the RNC receives a RADIO BEARER
RECONFIGURATION COMPLETE message from a UE. If the UE is performing a switchover
on the RAB from a HSDPA channel to channels of other types, this counter is increased by one
in the serving cell of the UE.

BSC6900 UMTS
As shown by point B in figure 4 (all types of hard handovers for HSDPA UEs), the RNC receives
a RADIO BEARER SETUP COMPLETE message from a UE. If the UE is performing a
switchover of SRB from a HSDPA channel to channels of other types, this counter is increased
by one in the serving cell of the UE.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.HSDPA.RAB.NormRel. WRFD-010696 DC-HSDPA

DC.All
VS.HSDPA.RAB.NormRel. WRFD-010683 Downlink 64QAM

64QAM.All
VS.HSDPA.RAB.NormRel. WRFD-010684 2 x 2 MIMO

MIMO.All
VS.HSDPA.RAB.NormRel. WRFD-010699 DC-HSDPA+MIMO

DCMIMO.All
VS.HSDPA.RAB.NormRel. WRFD-010693 DL 64QAM+MIMO

MIMO64QAM.All

3C.All

3CMIMO.All

4C.All

4CMIMO.All
VS.HSDPA.RAB.NormRel. WRFD-150209 DB-HSDPA

DB.All
VS.HSDPA.RAB.NormRel. WRFD-150227 DB-HSDPA+MIMO

DBMIMO.All
VS.HSDPA.RAB.NormRel. WRFD-010652 SRB over HSDPA

SRBoH.All
1.12.12.29 Number of Abnormal Released RABs for Cell When DB-HSDPA with
MIMO Applied (RF Exceptions Considered)
Counters
73426108 VS.HSDPA.RAB.AbnormR Number of Abnormal

el.DBMIMO Released RABs for Cell
When DB-HSDPA with
MIMO Applied (RF

BSC6900 UMTS
Description
This counter provides the number of abnormally released RABs in a cell when DB-HSDPA with
MIMO is applied. The instances are calculated in the cell with the primary carrier and RF
exceptions are considered.
Measurement point
As shown by point A in the following figure, when an exception occurs, the RNC sends the CN
an RAB RELEASE REQUEST message. When the RNC receives from the CN an RAB
ASSIGNMENT REQUEST message with the cause value not being "User Inactivity", "Normal
Release", "Successful Relocation", or "Network Optimization", this counter is increased by one
in the serving cell where the UE in question camps if the UE is processing HSDPA services and
DB-HSDPA with MIMO is applied. For details on cause values indicating abnormal RAB
releases, see 3GPP TS 25.413.
an RAB RELEASE REQUEST message. When the RNC receives from the CN an IU RELEASE
COMMAND message with the cause value not being "User Inactivity", "Normal Release",
"Successful Relocation", or "Network Optimization", this counter is increased by one in the
serving cell where the UE in question camps if the UE is processing HSDPA services and DB-
HSDPA with MIMO is applied. For details on cause values indicating abnormal RAB releases,
see 3GPP TS 25.413.

BSC6900 UMTS
an IU RELEASE REQUEST message. When the RNC receives from the CN an IU RELEASE
COMMAND message with the cause value not being "User Inactivity", "Normal Release",
serving cell where the UE in question camps if the UE is processing HSDPA services and DB-
HSDPA with MIMO is applied. For details on cause values indicating abnormal RAB releases,
see 3GPP TS 25.413.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSDPA.RAB.AbnormR WRFD-150227 DB-HSDPA+MIMO

el.DBMIMO
1.12.13 HSUPA Measurement per cell(HSUPA.Cell)
Overview
This function subset is used to measure the number of attempts to set up and release the HSUPA
RABs, and the number of attempts to switch the EDCH channels for the HSUPA service.

BSC6900 UMTS
Counters
Description
67203850 VS.HSUPA.UE.Me Average Number of Earlier than

an.Cell HSUPA UEs in a V900R011
Cell
67192110 VS.HSUPA.MACD Number of Earlier than

.SuccSetup Successful EDCH V900R011
MAC-d Flow
Establishments for
Cell

ttEstab RAB Establishment V900R011
Attempts for Cell
67192115 VS.HSUPA.RAB.S Number of Earlier than

uccEstab Successful HSUPA V900R011
RAB Establishments
for Cell

ttEstab.BE.Golden RAB Establishment V900R011
Attempts of BE
Service for Golden
Level User for Cell

ttEstab.BE.Silver RAB Establishment V900R011
Attempts of BE
Service for Silver
Level User for Cell

ttEstab.BE.Copper RAB Establishment V900R011
Attempts of BE
Service for Copper
Level User for Cell

uccEstab.BE.Gold- Successful HSUPA V900R011
en RAB Establishments
of BE Service for
Golden Level User
for Cell

BSC6900 UMTS

Description

uccEstab.BE.Silver Successful HSUPA V900R011
RAB Establishments
of BE Service for
Silver Level User for
Cell

uccEstab.BE.Cop- Successful HSUPA V900R011
per RAB Establishments
of BE Service for
Copper Level User
for Cell

bnormRel RABs Abnormal V900R011
Releases for Cell
67192365 VS.HSUPA.RAB.N Number of HSUPA Earlier than

ormRel RABs Normal V900R011
Released for Cell
67192366 VS.HSUPA.RAB.N Number of HSUPA Earlier than

ormRel.UEGen RAB Releases Due V900R011
to UE Signal
Connection Release
for Cell
67192367 VS.HSUPA.SHO.A Number of EDCH Earlier than

ttOut RL Addition and V900R011
Deletion Attempts by
Soft Handover for
Cell
67192368 VS.HSUPA.SHO.S Number of Earlier than

uccOut Successful EDCH V900R011
RL Additions and
Deletions by Soft
Handover for Cell

ervCellChg.Suc- Successful HSUPA V900R011
cOut Serving Cell
Changes in Soft
Handover Status for
Cell

BSC6900 UMTS

Description
67192370 VS.HSUPA.SHO.S Number of HSUPA Earlier than

ervCellChg.AttOut Serving Cell Change V900R011
Attempts in Soft
Handover Status for
Cell
67195485 VS.HSUPA.SHO.S Number of inter- Earlier than

ervCellChg.AttOu- RNC HSUPA V900R011
tIur Serving Cell Change
Attempts in Soft
Handover Status for
Cell

ervCellChg.Suc- Successful inter- V900R011
cOutIur RNC HSUPA
Serving Cell
Changes in Soft
Handover Status for
Cell
67195487 VS.HSUPA.HHO.E Number of Earlier than

2E.SuccOutIur Successful HSUPA V900R011
Serving Cell
Changes Due to
inter-RNC Hard
Handover without
Channel Change for
Cell
67195488 VS.HSUPA.HHO.E Number of HSUPA Earlier than

2E.AttOutIur Serving Cell Change V900R011
Attempts Due to
inter-RNC Hard
Handover without
Channel Change for
Cell

2E.SuccOutIntra- Successful HSUPA V900R011
Freq Serving Cell
Changes Due to
Intra-Frequency
Hard Handover
without Channel
Change for Cell

BSC6900 UMTS

Description

2E.AttOutIntra- Serving Cell Change V900R011
Freq Attempts Due to
Intra-Frequency
Hard Handover
without Channel
Change for Cell

2E.SuccOutInter- Successful HSUPA V900R011
Freq Serving Cell
Changes Due to
Inter-Frequency
Hard Handover
without Channel
Change for Cell

2E.AttOutInter- Serving Cell Change V900R011
Freq Attempts Due to
Inter-Frequency
Hard Handover
without Channel
Change for Cell
67192470 VS.HSUPA.E2D.Su Number of Earlier than

Conversions from
EDCH to DCH for
HSUPA Service for
Cell
67192471 VS.HSUPA.E2D.At Number of Channel Earlier than

Attempts from
EDCH to DCH for
HSUPA Service for
Cell

2D.SuccOutIntra- Successful HSUPA V900R011
Freq Intra-Frequency
Hard Handovers for
Cell(EDCH to DCH)

2D.AttOutIntra- Intra-Frequency V900R011
Freq Hard Handover
Attempts for Cell
(EDCH to DCH)

BSC6900 UMTS

Description

2D.SuccOutInter- Successful HSUPA V900R011
Freq Inter-Frequency
Hard Handovers for
Cell(EDCH to DCH)

2D.AttOutInter- Inter-Frequency V900R011
Freq Hard Handover
Attempts for Cell
(EDCH to DCH)
67192476 VS.HSUPA.D2E.Su Number of Earlier than

Conversions from
DCH to EDCH for
HSUPA Service for
Cell
67192477 VS.HSUPA.D2E.At Number of Channel Earlier than

Attempts from DCH
to EDCH for HSUPA
Service for Cell
67192480 VS.HSUPA.E2F.At Number of Channel Earlier than

Attempts from
EDCH to FACH for
HSUPA Service for
Cell
67192481 VS.HSUPA.E2F.Su Number of Earlier than

Conversions from
EDCH to FACH for
HSUPA Service for
Cell
67192482 VS.HSUPA.F2E.At Number of Channel Earlier than

Attempts from
FACH to EDCH for
HSUPA Service for
Cell

BSC6900 UMTS

Description
67192483 VS.HSUPA.F2E.Su Number of Earlier than

Conversions from
FACH to EDCH for
HSUPA Service for
Cell
67203932 VS.HSUPA.Mean- Mean Uplink Earlier than

ChThroughput Throughput of single V900R011
HSUPA MAC-d
Flow for Cell
67192486 VS.HSUPA.MeanC Number of Total Earlier than

hThroughput.To- Bytes Received in V900R011
talBytes Uplink of HSUPA
MAC-d Flow for
Cell
67204513 VS.HSUPA.Golden Mean Uplink Earlier than

BeMeanChThroug Throughput of V900R011
hput HSUPA MAC-d
Flow of BE Service
for Golden
Subscriber for Cell
67194873 VS.HSUPA.Golden Number of Total Earlier than

BeMeanChThroug Bytes Received in V900R011
hput.TotalBytes Uplink of HSUPA
MAC-d Flow of BE
Service for Golden
Subscriber for Cell
67204514 VS.HSUPA.Silver- Mean Uplink Earlier than

hput HSUPA MAC-d
Flow of BE Service
for Silver Subscriber
for Cell
67194875 VS.HSUPA.SilverB Number of Total Earlier than

eMeanChThrough Bytes Received in V900R011
put.TotalBytes Uplink of HSUPA
MAC-d Flow of BE
Service for Silver
Subscriber for Cell

BSC6900 UMTS

Description
67204515 VS.HSUPA.Copper Mean Uplink Earlier than

hput HSUPA MAC-d
Flow of BE Service
for Copper
Subscriber for Cell
67194889 VS.HSUPA.Copper Number of Total Earlier than

BeMeanChThroug Bytes Received in V900R011
hput.TotalBytes Uplink of HSUPA
MAC-d Flow of BE
Service for Copper
Subscriber for Cell
73403761 VS.HSUPA.UE.Ma Maximum Number V900R012

x.Cell of HSUPA UEs in a
Cell
73403766 VS.HSUPA.HHO.E Number of inter- V900R012

2D.AttOutIur RNC HSUPA Hard
Handover Attempts
for Cell(EDCH to
DCH)
73403767 VS.HSUPA.HHO.E Number of V900R012

2D.SuccOutIur Successful inter-
RNC HSUPA Hard
Handovers for Cell
(EDCH to DCH)
73403795 VS.HSUPA.RAB. Number of V900R012

16QAM.SuccEstab Successful HSUPA
16QAM RAB
Establishments for
cell
73403796 VS.HSUPA.RAB.A Number of HSUPA V900R012

bnormRel.16QAM 16QAM RABs
Abnormal Released
Including RF Cause
for cell
73403797 VS.HSUPA.RAB.N Number of HSUPA V900R012

ormRel.16QAM 16QAM RABs
Normal Released for
cell
73403794 VS.HSUPA.RAB. Number of HSUPA V900R012

16QAM.AttEstab 16QAM RAB Setup
Attempts for cell

BSC6900 UMTS

Description
73391136 VS.HSUPA.RAB.A Number of HSUPA V900R012

bnormRel.RF RABs Abnormal
Released due to RF
Failures for Cell
67204266 VS.HSUPA.UE.Me Average Number of V900R012

an.CAT1.4 HSUPA UEs with
Category 1-4 in a
Cell

an.CAT5 HSUPA UEs with
Category 5 in a Cell



x.CAT1.4 of HSUPA UEs with
Category1-4 in a Cell

x.CAT5 of HSUPA UEs with


73393829 VS.HSUPA.MACD Number of EDCH V900R012

.AttSetup MAC-d Flow Setup
Requests for Cell
73393832 VS.HSUPA.RAB.F Number of Failed V900R012

ailEstab.ULPower. HSUPA Service
Cong Establishments Due
to UL Power

BSC6900 UMTS

Description

ailEstab.ULIUBBa HSUPA Service
nd.Cong Establishments Due
to UL Iub Bandwidth

ailEstab.ULCE.Co HSUPA Service
ng Establishments Due
to UL CE
73410485 VS.PS.Conv.Kbps. Average uplink V900R012

EDCH throughput of the
Traffic PS
Conversational
beared on E-DCH for
cell
73393914 VS.PS.Conv.Traffi Number of uplink V900R012

c.EDCH bytes of Transport
Blocks of Traffic PS
Conversational
beared on E-DCH for
cell
73393956 VS.HSUPA.RsnSm Number of Times V900R012

all2Large.TTI2ms that HSUPA 2ms
TTI Users Transfer
from Small
Retransmission to
Large
Retransmission for
Cell
73393957 VS.HSUPA.RsnSm Number of Times V900R012

all2Large.TTI10ms that HSUPA 10ms
TTI Users Transfer
from Small
Retransmission to
Large
Retransmission for
Cell

BSC6900 UMTS

Description
73393958 VS.HSUPA.RsnLa Number of Times V900R012

rge2Small.TTI2ms that HSUPA 2ms
TTI Users Transfer
from Large
Retransmission to
Small
Retransmission for
Cell
73393959 VS.HSUPA.RsnLa Number of Times V900R012

rge2Small.TTI10m that HSUPA 10ms
s TTI Users Transfer
from Large
Retransmission to
Small
Retransmission for
Cell
73393984 VS.HSUPA.TTI2to Number of TTI V900R012

10.Att Switch Attempts
During RB
Reconfiguration for
Cell(2ms to 10ms)

10.Succ Successful TTI
Switches During RB
Reconfiguration for
Cell(2ms to 10ms)
73393986 VS.HSUPA.TTI10t Number of TTI V900R012

o2.Att Switch Attempts
During RB
Reconfiguration for
Cell(10ms to 2ms)
73393987 VS.HSUPA.TTI10t Number of V900R012

o2.Succ Successful TTI
Switches During RB
Reconfiguration for
Cell(10ms to 2ms)
73410507 VS.HSUPA. Average Number of V900R012

16QAM.UE.Mean. HSUPA 16QAM
Cell UEs in a Cell
73441120 VS.HSUPA.Boostin Number of UEs V900R013

g.UE.Mean.Cell Supporting E-
DPCCH Boosting for
Cell

BSC6900 UMTS

Description
73441121 VS.HSUPA.Boostin Number of UEs V900R013

gCPC.UE.Mean.Ce Supporting E-
ll DPCCH Boosting
and CPC for Cell
73422168 VS.HSUPA.RAB.A Number of RABs V900R012

bnormRel.E2P Abnormally
Released for PS
HSUPA Services
during the State
Transition from
CELL_DCH to
CELL_PCH or
URA_PCH for Cell
73423359 VS.HSUPA.RAB.B Number of HSUPA V900R013

oosting.AttEstab Boosting RAB Setup
Attempts for Cell
73423360 VS.HSUPA.RAB.B Number of V900R013

oosting.SuccEstab Successful HSUPA
Boosting RAB
Setups for Cell
73423361 VS.HSUPA.RAB.A Number of V900R013

bnormRel.Boosting Abnormally
Released HSUPA
Boosting RABs for
Cell
73423362 VS.HSUPA.RAB.N Number of Normally V900R013

ormRel.Boosting Released HSUPA
Boosting RABs for
Cell
73423567 VS.HSUPA.HARQ. Number of HARQ V900R013

POReCfgAtt.TTI1 PO Reconfiguration
0ms Attempts of HSUPA
Users with 10 ms TTI
for Cell
73423568 VS.HSUPA.HARQ. Number of V900R013

POReCfgSucc.TTI Successful HARQ
10ms PO Reconfigurations
of HSUPA Users
with 10 ms TTI for
Cell

BSC6900 UMTS

Description
73424115 VS.HSUPA.RAB.D Number of DC- V900R014

C.AttEstab HSUPA RAB Setup
Attempts for Cell
73424116 VS.HSUPA.RAB.D Number of V900R014

C.SuccEstab Successful DC-
HSUPA RAB Setups
for Cell

C.NormRel HSUPA RABs
Normally Released
for Cell

C.AbnormRel HSUPA RABs
Abnormally
Released for Cell




73424192 VS.HSUPA.DC.PR Mean Number of V900R014

IM.UE.Mean.Cell DC-HSUPA Users in
the Cell with the
Primary Carrier
73441238 VS.HSUPA.DC.SE Mean Number of V900R014

C.UE.Mean.Cell DC-HSUPA Users in
the Cell with the
Secondary Carrier

an.TTI2ms HSUPA 2 ms TTI
UEs in a Cell

BSC6900 UMTS

Description

x.TTI2ms of HSUPA 2 ms TTI
UEs in a Cell
73441240 VS.HSUPA.UE.Me Average number of V900R014

an.TTI10ms HSUPA 10 ms TTI
UEs in a Cell

x.TTI10ms of HSUPA 10 ms
TTI UEs in a Cell
73424205 VS.HSUPA.RABEs Number of V900R014

tabTTI10ms.AdmC Successful RAB
E.Succ Establishments
Initiated by HSUPA
2 ms UEs with a 10
ms TTI Due to
Congestion of
Admitted CEs in a
Cell

tabTTI10ms.ResR Successful RAB
TWP.Succ Establishments
Initiated by HSUPA
2 ms UEs with a 10
ms TTI Due to
RTWP Congestion in
a Cell

tabTTI10ms.ResUs Successful RAB
edCE.Succ Establishments
Initiated by HSUPA
2 ms UEs with a 10
ms TTI Due to
Congestion of
Occupied CEs in a
Cell

tabTTI10ms.ResIU Successful RAB
B.Succ Establishments
Initiated by HSUPA
2 ms UEs with a 10
ms TTI Due to Iub
Resource
Congestion in a Cell

BSC6900 UMTS

Description

tabTTI10ms.Cover Successful RAB
.Succ Establishments
Initiated by HSUPA
2 ms UEs with a 10
ms TTI Due to
Limited Uplink
Coverage

During State
Transition of
HSUPA+16QAM
UEs to CELL/
URA_PCH

bnormRel.DC2P Abnormal RAB
Releases for Cell
During State
Transition of DC-
HSUPA UEs to
CELL/URA_PCH
73425952 VS.HSUPA.RAB.N Number of Normal V900R015

ormRel. RAB Releases of
16QAM.All HSUPA+16QAM
UEs for Cell (All
Scenarios)
73425953 VS.HSUPA.RAB.N Number of Normal V900R015

ormRel.DC.All RAB Releases of
DC-HSUPA UEs for
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

BSC6900 UMTS
Counter Sub Counter
VS.HSUPA.RAB.SuccEstab VS.HSUPA.RAB.SuccEstab.BE.Golden
VS.HSUPA.RAB.SuccEstab.BE.Silver
VS.HSUPA.RAB.SuccEstab.BE.Copper
1.12.13.1 Average Number of HSUPA UEs in a Cell
Counters
67203850 VS.HSUPA.UE.Mean.Cell Average Number of HSUPA

UEs in a Cell
73403761 VS.HSUPA.UE.Max.Cell Maximum Number of

HSUPA UEs in a Cell
Description
These counters provide the average and maximum number of HSUPA UEs in active set cells.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of the number of
HSUPA UEs. At the end of the measurement period, by dividing the accumulated value of
sample data in the period by the number of samples, the average number of HSUPA UEs in the
measurement period is obtained; by selecting the maximum value of sample data in the period,
the maximum number of HSUPA UEs in the measurement period is obtained.
Formula
None
Unit
None
Related Features
VS.HSUPA.UE.Mean.Cell WRFD-01061211 20 HSUPA Users per Cell

WRFD-010634 60 HSUPA Users per Cell
WRFD-010639 96 HSUPA Users per Cell

BSC6900 UMTS
VS.HSUPA.UE.Max.Cell WRFD-01061202 HSUPA Admission Control

WRFD-020101 Admission Control
1.12.13.2 Number of Successful EDCH MAC-d Flow Establishments for Cell
Counters
67192110 VS.HSUPA.MACD.Succ- Number of Successful EDCH

Setup MAC-d Flow Establishments
for Cell
Description
This measurement item takes statistics of the number of successful EDCH MAC-d flow
establishments for UE by RNC in a cell.For DC-HSUPA users, this counter is measured only in
the cell with the primary carrier.
Measurement point
This measurement is triggered at point C as shown in Figure. When the RNC sends a RADIO
LINK RECONFIGURATION COMMIT message to the NodeB, the RNC measures this item
in the cell where the radio link exists if the HSUPA RABs are setup. During the reconfiguration
of the radio link, the HSUPA RABs are set up if the message RADIO LINK
RECONFIGURATION PREPARE contains the newly added EDCH MACD FLOW.

BSC6900 UMTS
This measurement is triggered at point B as shown in Figure. When the RNC sends a RADIO
LINK SETUP REQUEST/RADIO LINK ADDITION REQUEST message to the NodeB, the
RNC measures this item in the cell where the radio link is successfully set up for the HSUPA
service if the RNC receives a RADIO LINK SETUP RESPONSE/RADIO LINK ADDITION
RESPONSE message from the NodeB.
During the setup of the radio link, the radio link for the HSUPA cell will be established if the
RADIO LINK SETUP REQUEST/RADIO LINK ADDITION REQUEST message contains the
EDCH FDD Information.
Figure 1-530 RL setup procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.HSUPA.MACD.Succ- WRFD-010612 HSUPA Introduction

Setup Package

BSC6900 UMTS
1.12.13.3 Number of HSUPA RAB Establishment Attempts for Cell
Counters
67192114 VS.HSUPA.RAB.AttEstab Number of HSUPA RAB

Cell
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
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

BSC6900 UMTS
Unit
None
Related Features
VS.HSUPA.RAB.AttEstab WRFD-01061206 Interactive and Background

WRFD-010632 Traffic Class on HSUPA
HSUPA
1.12.13.4 Number of Successful HSUPA RAB Establishments for Cell
Counters
67192115 VS.HSUPA.RAB.SuccEstab Number of Successful

HSUPA RAB
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

HSUPA
1.12.13.5 Number of HSUPA RAB establish attempts of BE Service for different

prior Level Users (Cell)

BSC6900 UMTS
Counters

BE.Golden Establishment Attempts of
BE Service for Golden Level
User for Cell

BE.Silver Establishment Attempts of
BE Service for Silver Level
User for Cell

BE.Copper Establishment Attempts of
BE Service for Copper Level
User for Cell
Description
These counters provide the number of HSUPA RAB establishment attempts of BE service for
different prior level users (golden, silver, and copper users) in the HSUPA serving cell. For DC-
HSUPA users, these counters are measured only in the cell with the primary carrier.
Measurement point
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

BE.Golden Traffic Class on HSUPA

BE.Silver Traffic Class on HSUPA

BE.Copper Traffic Class on HSUPA
1.12.13.6 Number of Successful HSUPA RAB Establishments of BE Service for

different prior Level Users (Cell)
Counters

.BE.Golden HSUPA RAB
Service for Golden Level
User for Cell

.BE.Silver HSUPA RAB
Service for Silver Level User
for Cell

.BE.Copper HSUPA RAB
Service for Copper Level
User for Cell

BSC6900 UMTS
Description
These counters provide the number of successful HSUPA RAB establishments of BE service
for different prior level users (golden, silver, and copper users) in the HSUPA serving cell. For
DC-HSUPA users, these counters are measured only in the cell with the primary carrier.
Measurement point
The measurement is triggered at point B as shown in the figure. After receiving a RADIO
BEARER SETUP COMPLETE message from a UE, the RNC sends a RAB ASSIGNMENT
RESPONSE message to the CN. If the assignment is for setting up the HSUPA service, the RNC
measures the items by the prior lever in the HSUPA serving cell.
Formula
None
Unit
None

BSC6900 UMTS
Related Features

.BE.Golden Traffic Class on HSUPA

.BE.Silver Traffic Class on HSUPA

.BE.Copper Traffic Class on HSUPA
1.12.13.7 Number of HSUPA RABs Abnormal Released for Cell
Counters
67192364 VS.HSUPA.RAB.Abnorm- Number of HSUPA RABs

Rel Abnormal Releases for Cell
Description
This measurement item takes statistics of the number of HSUPA RABs abnormal released by
the RNC in a cell.For DC-HSUPA users, this counter is measured only in the cell with the primary
carrier.
Measurement point
RNC measures the items in the HSUPA serving cell if the released RAB is a HSUPA service.

BSC6900 UMTS

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.Abnorm- WRFD-01061206 Interactive and Background

Rel WRFD-010632 Traffic Class on HSUPA
HSUPA

BSC6900 UMTS
1.12.13.8 Number of HSUPA RABs Normal Released for Cell
Counters
67192365 VS.HSUPA.RAB.NormRel Number of HSUPA RABs

Normal Released for Cell
Description
This measurement item takes statistics of the number of HSUPA RABs normally released in the
HSUPA serving cell.For DC-HSUPA users, this counter is measured only in the cell with the
primary carrier.
Measurement point
in the HSUPA serving cell if it is a HSUPA service.

BSC6900 UMTS
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
VS.HSUPA.RAB.NormRel WRFD-01061206 Interactive and Background

HSUPA

BSC6900 UMTS
1.12.13.9 Number of HSUPA RAB Released due to UE Signaling Connection failure

for Cell
Counters
67192366 VS.HSUPA.RAB.NormRel. Number of HSUPA RAB

UEGen Releases Due to UE Signal
Connection Release for Cell
Description
This measurement item takes statistics of the number of HSUPA RABs released by the RNC
due to UE Signal Connection Release.For DC-HSUPA users, this counter is measured only in
Measurement point
This measurement is triggered at point A shown in the figure. When the RNC received a
SIGNALLING CONNECTION RELEASE INDICATION message from UE, it sends an IU
RELEASE REQUEST message to the CN. And the RNC will releases corresponding RABs
after it receives an IU RELEASE COMMAND message from the CN. When the RNC sends an
IU RELEASE COMPLETE message to the CN, the RNC measures the item in the HSUPA
serving cell if the released RAB is HSUPA service.
Figure 1-540 UL SIG connection release procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.NormRel. WRFD-01061206 Interactive and Background

UEGen WRFD-010632 Traffic Class on HSUPA
HSUPA
1.12.13.10 Number of EDCH RL Addition and Deletion Attempts by Soft Handover

for Cell
Counters
67192367 VS.HSUPA.SHO.AttOut Number of EDCH RL

Addition and Deletion
Attempts by Soft Handover
for Cell
Description
This measurement item takes statistics of the number of EDCH RL addition and deletion attempts
by soft handover in a cell.For DC-HSUPA users, this counter is measured only in the cell with
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.

BSC6900 UMTS
Figure 1-541 Soft handover procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.HSUPA.SHO.AttOut WRFD-01061204 HSUPA Mobility

Management
1.12.13.11 Number of Successful EDCH RL Additions and Deletions by Soft

Handover for Cell

BSC6900 UMTS
Counters
67192368 VS.HSUPA.SHO.SuccOut Number of Successful EDCH

RL Additions and Deletions
by Soft Handover for Cell
Description
This measurement item takes statistics of the number of successful EDCH RL additions and
deletions due to soft handover in a cell.For DC-HSUPA users, this counter is measured only in
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

BSC6900 UMTS
Unit
None
Related Features
VS.HSUPA.SHO.SuccOut WRFD-01061204 HSUPA Mobility

Management
1.12.13.12 Number of Successful HSUPA Serving Cell Changes in Soft Handover

Status for Cell
Counters
67192369 VS.HSUPA.SHO.ServCellC Number of Successful

hg.SuccOut HSUPA Serving Cell
Changes in Soft Handover
Status for Cell
Description
This measurement item takes statistics of the number of successful HSUPA serving cell changes
in soft handover status for cell.For DC-HSUPA users, this counter is measured only in the cell
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.

BSC6900 UMTS
Figure 1-543 Serving cell change procedure (successful operation)
This measurement triggered at point C as shown in Figure , when the RNC receives an ACTIVE
SET UPDATE COMPLETE message from the UE. If the HSUPA serving cell changes during
the soft handover, the RNC measures this item in the original HSUPA serving cell.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.SHO.ServCellC WRFD-01061204 HSUPA Mobility

hg.SuccOut Management
1.12.13.13 Number of HSUPA Serving Cell Change Attempts in Soft Handover

Status for Cell
Counters
67192370 VS.HSUPA.SHO.ServCellC Number of HSUPA Serving

hg.AttOut Cell Change Attempts in Soft
Handover Status for Cell
Description
This measurement item takes statistics of the number of HSUPA serving cell change attempts
in soft handover status for cell.For DC-HSUPA users, this counter is measured only in the cell
Measurement point
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

BSC6900 UMTS
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

hg.AttOut Management
1.12.13.14 Number of inter-RNC HSUPA Serving Cell Change Attempts in Soft


BSC6900 UMTS
Counters
67195485 VS.HSUPA.SHO.ServCellC Number of inter-RNC

hg.AttOutIur HSUPA Serving Cell Change
Attempts in Soft Handover
Status for Cell
Description
This measurement counter takes statistics of the number of inter-RNC HSUPA serving cell
change attempts in soft handover status for cell. It is measured in a serving cell.For DC-HSUPA
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.

BSC6900 UMTS
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

hg.AttOutIur Management
1.12.13.15 Number of Successful inter-RNC HSUPA Serving Cell Changes in Soft

Counters
67195486 VS.HSUPA.SHO.ServCellC Number of Successful inter-

hg.SuccOutIur RNC HSUPA Serving Cell
Changes in Soft Handover
Status for Cell
Description
This measurement counter takes statistics of the number of successful HSUPA serving cell
changes in soft handover status for cell. It is measured in a serving cell.For DC-HSUPA users,
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,

BSC6900 UMTS
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

hg.SuccOutIur Management
1.12.13.16 Number of Successful HSUPA Serving Cell Changes Due to inter-RNC

Hard Handover without Channel Change for Cell

BSC6900 UMTS
Counters
67195487 VS.HSUPA.HHO.E2E.Suc- Number of Successful

cOutIur HSUPA Serving Cell
Changes Due to inter-RNC
Hard Handover without
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 message to RNC as a response.
Measurement point
This measurement is triggered at point B as shown in Figure. The procedure shown in the figure
takes a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message as an example.
When the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message from the UE, the RNC measures the item in the HSUPA serving cell before the hard
handover on condition that the hard handover is performed over the Iur interface from EDCH
to EDCH.

BSC6900 UMTS
Figure 1-551 HSUPA Serving cell change procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.HSUPA.HHO.E2E.Suc- WRFD-01061204 HSUPA Mobility

cOutIur Management
1.12.13.17 Number of HSUPA Serving Cell Change Attempts Due to inter-RNC

Hard Handover without Channel Change for Cell

BSC6900 UMTS
Counters
67195488 VS.HSUPA.HHO.E2E.At- Number of HSUPA Serving

tOutIur Cell Change Attempts Due to
inter-RNC Hard Handover
without Channel Change for
Cell
Description
This measurement counter takes statistics of the number of HSUPA serving cell change attempts
due to inter-RNC hard handover.It is measured in a serving cell.For DC-HSUPA users, this
counter is measured only in the cell with the primary carrier.The hard handover procedure can
be triggered with the following messages:[1]PHYSICAL CHANNEL RECONFIGURATION,
[2]TRANSPORT CHANNEL RECONFIGURATION,[3]RADIO BEARER
RECONFIGURATION,[4]RADIO BEARER SETUP,[5]RADIO BEARER RELEASE
message. Accordingly, UE may send [1]PHYSICAL CHANNEL RECONFIGURATION
COMPLETE,[2]PHYSICAL CHANNEL RECONFIGURATION FAILURE,[3]TRANSPORT
CHANNEL RECONFIGURATION COMPLETE,[4]TRANSPORT CHANNEL
RECONFIGURATION FAILURE,[5]RADIO BEARER RECONFIGURATION
COMPLETE,[6]RADIO BEARER RECONFIGURATION FAILURE,[7]RADIO BEARER
SETUP COMPLETE,[8]RADIO BEARER SETUP FAILURE,[9]RADIO BEARER
RELEASE COMPLETE,[10]RADIO BEARER RELEASE FAILURE message to RNC as a
response.
Measurement point
This measurement is triggered at point A as shown in Figure. The procedure shown in the figure
takes a PHYSICAL CHANNEL RECONFIGURATION message as an example. When the RNC
sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC measure
the item in the serving cell before hard handover on condition that this hard handover is
performed over the Iur interface from EDCH to EDCH.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.HHO.E2E.At- WRFD-01061204 HSUPA Mobility

tOutIur Management
1.12.13.18 Number of Successful HSUPA Serving Cell Changes Due to Intra-

Frequency Hard Handover without Channel Change for Cell

BSC6900 UMTS
Counters

cOutIntraFreq HSUPA Serving Cell
Changes Due to Intra-
Cell

cOutInterFreq HSUPA Serving Cell
Changes Due to Inter-
Cell
Description
These counters provide the number of successful HSUPA serving cell changes due to E-DCH-
to-E-DCH intra-frequency and inter-frequency hard handover. For DC-HSUPA users, these
counters are measured only in the cell with the primary carrier.
Measurement point
These measurements are triggered at point B shown in the figure. When receiving a message
PHYSICAL CHANNEL RECONFIGURATION COMPLETE or TRANSPORT CHANNEL
RECONFIGURATION COMPLETE or RADIO BEARER RECONFIGURATION
COMPLETE or RADIO BEARER SETUP COMPLETE or RADIO BEARER RELEASE
COMPLETE message from the UE, the RNC measures
VS.HSUPA.HHO.E2E.SuccOutIntraFreq in the HSUPA serving cell before the hard handover
if an E-DCH-to-E-DCH intra-frequency hard handover is performed, or measures
VS.HSUPA.HHO.E2E.SuccOutInterFreq in the HSUPA serving cell before the hard handover
if an E-DCH-to-E-DCH inter-frequency hard handover is performed.

BSC6900 UMTS
Formula
None
Unit
None
Related Features


1.12.13.19 Number of HSUPA Serving Cell Change Attempts Due to Intra-


BSC6900 UMTS
Counters

tOutIntraFreq Cell Change Attempts Due to
Handover without Channel
Change for Cell
Description
These counters provide the number of HSUPA serving cell change attempts due to E-DCH-to-
E-DCH intra-frequency and inter-frequency hard handover. For DC-HSUPA users, these
Measurement point
These measurements are triggered at point A shown in the figure. When sending the UE a
message PHYSICAL CHANNEL RECONFIGRATION, TRANSPORT CHANNEL
RECONFIGURATION, RADIO BEARER RECONFIGURATION, RADIO BEARER SETUP
message, or RADIO BEARER RELEASE, the RNC measures
VS.HSUPA.HHO.E2E.AttOutIntraFreq in the HSUPA serving cell before the hard handover if
an E-DCH-to-EDCH intra-frequency hard handover is performed, or measures
VS.HSUPA.HHO.E2E.AttOutInterFreq in the HSUPA serving cell before the hard handover if
an E-DCH-to-E-DCH inter-frequency hard handover is performed.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

1.12.13.20 Number of HSUPA Serving Cell Change Attempts Due to Inter-

Counters

tOutInterFreq Cell Change Attempts Due to
Handover without Channel
Change for Cell
Description
due to inter-frequency hard handover without channel change for cell.For DC-HSUPA users,
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

1.12.13.21 Number of Successful HSUPA Intra-Frequency Hard Handovers for Cell

(EDCH to DCH)

BSC6900 UMTS
Counters
67192472 VS.HSUPA.HHO.E2D.Suc- Number of Successful

cOutIntraFreq HSUPA Intra-Frequency
(EDCH to DCH)
67192474 VS.HSUPA.HHO.E2D.Suc- Number of Successful

cOutInterFreq HSUPA Inter-Frequency
(EDCH to DCH)
Description
These counters provide the number of successful HSUPA intra-frequency/inter-frequency hard
handovers from EDCH to DCH in a cell. For DC-HSUPA users, these counters are measured
Measurement point
These measurements are triggered at point B shown in the figure. When receiving a RADIO
BEARER RECONFIGURATION COMPLETE message from the UE, the RNC measures
VS.HSUPA.HHO.E2D.SuccOutIntraFreq in the HSUPA serving cell before the hard handover
if an EDCH-to-DCH intra-frequency hard handover is performed or measures
VS.HSUPA.HHO.E2D.SuccOutInterFreq in the HSUPA serving cell before the hard handover
if an EDCH-to-DCH inter-frequency hard handover is performed.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.HSUPA.HHO.E2D.Suc- WRFD-01061204 HSUPA Mobility


1.12.13.22 Number of HSUPA Hard Handover Attempts for Cell(EDCH to DCH)
Counters
67192473 VS.HSUPA.HHO.E2D.At- Number of HSUPA Intra-

tOutIntraFreq Frequency Hard Handover
Attempts for Cell(EDCH to
DCH)
67192475 VS.HSUPA.HHO.E2D.At- Number of HSUPA Inter-

tOutInterFreq Frequency Hard Handover
DCH)
Description
These counters provide the number of attempts to switch the channel type from E-DCH to DCH
due to intra-frequency/inter-frequency hard handover in a cell. For DC-HSUPA users, these
Measurement point
These measurements are triggered at point A shown in the figure. When sending the UE a
message RADIO BEARER RECONFIGURATION, the RNC measures
VS.HSUPA.HHO.E2D.AttOutIntraFreq in the HSUPA serving cell before the hard handover if
an EDCH-to-DCH intra-frequency hard handover is performed, or measures
VS.HSUPA.HHO.E2D.AttOutInterFreq in the HSUPA serving cell before the hard handover if
an EDCH-to-DCH inter-frequency hard handover is performed.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.HHO.E2D.At- WRFD-01061204 HSUPA Mobility


1.12.13.23 Number of Channel Conversion Attempts According to Different

Channel Switch Type for Cell
Counters
67192480 VS.HSUPA.E2F.Att Number of Channel

EDCH to FACH for HSUPA
Service for Cell

BSC6900 UMTS
67192471 VS.HSUPA.E2D.Att Number of Channel

EDCH to DCH for HSUPA
Service for Cell
67192477 VS.HSUPA.D2E.Att Number of Channel

DCH to EDCH for HSUPA
Service for Cell
67192482 VS.HSUPA.F2E.Att Number of Channel

FACH to EDCH for HSUPA
Service for Cell
Description
These counters provide the number of channel conversion attempts according to different
channel switch type in the same cell of the RNC for HSUPA service. For DC-HSUPA users,
these counters are measured only in the cell with the primary carrier.
Measurement point
This measurement is performed at point A shown in the figure. The RNC sends a RADIO BEAR
RECONFIGURE message to the UE during the DCCC or RAB ASSIGN procedure. If the UE
camps on the same cell after reconfigurations, the RNC measures the items in the HSUPA serving
cell by the channel switch type.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.HSUPA.E2F.Att WRFD-01061208 HSUPA DCCC
VS.HSUPA.E2D.Att WRFD-01061208 HSUPA DCCC
VS.HSUPA.D2E.Att WRFD-01061208 HSUPA DCCC
VS.HSUPA.F2E.Att WRFD-01061208 HSUPA DCCC
1.12.13.24 Number of Successful Handovers Between Different Channel Types for

Cell
Counters
67192481 VS.HSUPA.E2F.Succ Number of Successful

EDCH to FACH for HSUPA
Service for Cell
67192470 VS.HSUPA.E2D.Succ Number of Successful

EDCH to DCH for HSUPA
Service for Cell
67192476 VS.HSUPA.D2E.Succ Number of Successful

DCH to EDCH for HSUPA
Service for Cell
67192483 VS.HSUPA.F2E.Succ Number of Successful

FACH to EDCH for HSUPA
Service for Cell
Description
These counters provide the number of times that the handover between different channels
succeeds in the cell. For DC-HSUPA users, these counters are measured only in the cell with

BSC6900 UMTS
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
VS.HSUPA.E2F.Succ WRFD-01061208 HSUPA DCCC
VS.HSUPA.E2D.Succ WRFD-01061208 HSUPA DCCC
VS.HSUPA.D2E.Succ WRFD-01061208 HSUPA DCCC
VS.HSUPA.F2E.Succ WRFD-01061208 HSUPA DCCC
1.12.13.25 Mean Uplink Throughput of single HSUPA MAC-d Flow

BSC6900 UMTS
Counters
67203932 VS.HSUPA.Mean- Mean Uplink Throughput of

ChThroughput single HSUPA MAC-d Flow
for Cell
specific formulas.
67192487 VS.HSUPA.MeanChThroug Duration of HSUPA MAC-D

hput.Times Flow Receiving Data for Cell
Description
This counter provides the mean uplink throughput of single HSUPA MAC-d flows in HSUPA
cells in active set.For DC-HSUPA users, this counter is measured only in the primary cell based
on the total throughput on the primary and secondary carriers.
Measurement point
When data is received in HSUPA active cells, the RNC measures the total data transfer time of
all the UEs and the total number of bits received in the cell. At the end of the measurement
period, the RNC divides the total number of bits by the total data transfer time to obtain the mean
uplink throughput of MAC-d flows at the RLC layer. Note that the total number of bits measured
excludes RLC headers and retransmitted data. In the case of a soft handover, the RNC measures
the number of bits received after combining in all cells of the active set.
Formula
VS.HSUPA.MeanChThroughput = {8}*[VS.HSUPA.MeanChThroughput.TotalBytes]/
[VS.HSUPA.MeanChThroughput.Times]
Unit
kbit/s
Related Features
VS.HSUPA.Mean- WRFD-010612 HSUPA Introduction

ChThroughput Package

BSC6900 UMTS
1.12.13.26 Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow
Counters
67192486 VS.HSUPA.MeanChThroug Number of Total Bytes

hput.TotalBytes Received in Uplink of
HSUPA MAC-d Flow for
Cell
Description
This counter provides the number of total bytes received in uplink of all the HSUPA MAC-d
flows in a cell.For DC-HSUPA users, this counter is measured only in the primary cell based
on the total number of bytes received on the primary and secondary carriers.
Measurement point
When data is received in HSUPA active cells, the RNC measures the number of total bytes
received in the uplink (including data of different services) at the RLC layer for the MAC-d flow
in the cell. The RLC header and the retransmitted data are excluded.In the case of a soft handover,
the RNC measures the number of bits received after combining in all cells of the active set.
Formula
None
Unit
byte
Related Features
VS.HSUPA.MeanChThroug WRFD-010612 HSUPA Introduction

hput.TotalBytes Package
1.12.13.27 Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for

Golden Subscriber

BSC6900 UMTS
Counters
67204513 VS.HSUPA.GoldenBe- Mean Uplink Throughput of

MeanChThroughput HSUPA MAC-d Flow of BE
Service for Golden
Subscriber for Cell
67204514 VS.HSUPA.SilverBe- Mean Uplink Throughput of

Service for Silver Subscriber
for Cell
67204515 VS.HSUPA.CopperBe- Mean Uplink Throughput of

Service for Copper
Subscriber for Cell
specific formulas.
67194890 VS.HSUPA.CopperBeMean Duration of Copper BE

ChThroughput.Times HSUPA MAC-D Flow
Receiving Data for Cell
67194874 VS.HSUPA.GoldenBeMean Duration of Golden BE

ChThroughput.Times HSUPA MAC-D Flow
67194876 VS.HSUPA.SilverBeMeanC Duration of Silver BE

hThroughput.Times HSUPA MAC-D Flow
Description
These counters provide the average UL throughput of all the HSUPA MAC-d flows of different-
priority BE services in an HSUPA serving cell. For DC-HSUPA users, these counters are
measured only in the primary cell based on the total number of bytes received on the primary
and secondary carriers.
Measurement point
When BE services for golden, silver, and copper users are carried in an HSUPA serving cell,
the RNC measures the number of total bytes received in the uplink of the MAC-d flow of the
BE service at the RLC layer and the time for data transmission for different users. At the end of
the measurement period, the average throughput of users of a priority, (for example, golden

BSC6900 UMTS
users) is obtained by dividing the number of total bytes for the golden users by the total
transmission time for the golden users. RLC headers and retransmitted data are not considered.
Formula
VS.HSUPA.GoldenBeMeanChThroughput = {8}*
[VS.HSUPA.GoldenBeMeanChThroughput.TotalBytes]/
[VS.HSUPA.GoldenBeMeanChThroughput.Times]
VS.HSUPA.SilverBeMeanChThroughput = {8}*
[VS.HSUPA.SilverBeMeanChThroughput.TotalBytes]/
[VS.HSUPA.SilverBeMeanChThroughput.Times]
VS.HSUPA.CopperBeMeanChThroughput = {8}*
[VS.HSUPA.CopperBeMeanChThroughput.TotalBytes]/
[VS.HSUPA.CopperBeMeanChThroughput.Times]
Unit
kbit/s
Related Features
VS.HSUPA.GoldenBe- WRFD-01061008 Interactive and Background

MeanChThroughput WRFD-020806 Traffic Class on HSDPA
on SPI Weight
VS.HSUPA.SilverBe- WRFD-01061008 Interactive and Background

on SPI Weight
VS.HSUPA.CopperBe- WRFD-01061008 Interactive and Background

on SPI Weight
1.12.13.28 Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of

BE Service for Golden Subscriber

BSC6900 UMTS
Counters
67194873 VS.HSUPA.GoldenBeMean Number of Total Bytes

ChThroughput.TotalBytes Received in Uplink of
HSUPA MAC-d Flow of BE
Service for Golden
Subscriber for Cell
67194875 VS.HSUPA.SilverBeMeanC Number of Total Bytes

hThroughput.TotalBytes Received in Uplink of
Service for Silver Subscriber
for Cell
67194889 VS.HSUPA.CopperBeMean Number of Total Bytes

ChThroughput.TotalBytes Received in Uplink of
Service for Copper
Subscriber for Cell
Description
These counters provide the number of total bytes received in the uplink of all the HSUPA MAC-
d flows of different-priority BE services in an HSUPA serving cell. For DC-HSUPA users, these
counters are measured only in the primary cell based on the total number of bytes received on
the primary and secondary carriers.
Measurement point
When BE services for golden, silver, and copper users are carried in an HSUPA serving cell,
the RNC separately measures the number of total bytes received in the uplink of the MAC-d
flow of different-priority BE service at the RLC layer. RLC headers and retransmitted data are
not considered.
Formula
None
Unit
byte

BSC6900 UMTS
Related Features
VS.HSUPA.GoldenBeMean WRFD-01061008 Interactive and Background

on SPI Weight
VS.HSUPA.SilverBeMeanC WRFD-01061008 Interactive and Background

hThroughput.TotalBytes WRFD-020806 Traffic Class on HSDPA
on SPI Weight
VS.HSUPA.CopperBeMean WRFD-01061008 Interactive and Background

on SPI Weight
1.12.13.29 Number of inter-RNC HSUPA Hard Handover Attempts for Cell(EDCH

to DCH)
Counters
73403766 VS.HSUPA.HHO.E2D.At- Number of inter-RNC

tOutIur HSUPA Hard Handover
DCH)
Description
This measurement item takes statistics of the number of requests for inter RNC hard handovers
from the EDCH to the DCH in a cell. For DC-HSUPA users, this counter is measured only in
the cell with the primary carrier.The hard handover procedure can be triggered with the following
messages:[1]RADIO BEARER RECONFIGURATION,[2]RADIO BEARER SETUP,[3]
RADIO BEARER RELEASE message. Accordingly, UE may send [1]RADIO BEARER
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

BSC6900 UMTS
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

tOutIur Management
1.12.13.30 Number of Successful inter-RNC HSUPA Hard Handovers for Cell

(EDCH to DCH)
Counters
73403767 VS.HSUPA.HHO.E2D.Suc- Number of Successful inter-

cOutIur RNC HSUPA Hard
Handovers for Cell(EDCH to
DCH)

BSC6900 UMTS
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
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

cOutIur Management

BSC6900 UMTS
1.12.13.31 Number of Successful HSUPA 16QAM RAB Establishments for cell
Counters
73403795 VS.HSUPA.RAB. Number of Successful

16QAM.SuccEstab HSUPA 16QAM RAB
Establishments for cell
Description
This measurement item takes statistics of the number of successful HSUPA 16QAM RAB
establishments for cell. For DC-HSUPA users, this counter is measured only in the cell with the
primary carrier.
Measurement point
This measurement is triggered at point B as shown in the figure, when the RNC receives a RADIO
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB. WRFD-010694 UL 16QAM

16QAM.SuccEstab
1.12.13.32 Number of HSUPA 16QAM RABs Abnormal Released for cell
Counters
73403796 VS.HSUPA.RAB.Abnorm- Number of HSUPA 16QAM

Rel.16QAM RABs Abnormal Released
Including RF Cause for cell
Description
This measurement item takes statistics of the number of HSUPA 16QAM RABs Abnormal
Released including RF causes for cell. For DC-HSUPA users, this counter is measured only in
Measurement point
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.

BSC6900 UMTS
16QAM.

BSC6900 UMTS
16QAM.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.Abnorm- WRFD-010694 UL 16QAM

Rel.16QAM
1.12.13.33 Number of HSUPA 16QAM RABs Normal Released for cell
Counters
73403797 VS.HSUPA.RAB.NormRel. Number of HSUPA 16QAM

16QAM RABs Normal Released for
cell

BSC6900 UMTS
Description
This measurement item takes statistics of the number of HSUPA 16QAM Release due to normal
cause for cell. For DC-HSUPA users, this counter is measured only in the cell with the primary
carrier.
Measurement point
in the HSUPA serving cell if it is a HSUPA service using 16QAM.
Release","Successful Relocation" or "Network Optimization" , or the RNC initiates the release
Signalling Connection Release" ,the RNC measures the item in the HSUPA serving cell if it is
a HSUPA service using 16QAM.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.NormRel. WRFD-010694 UL 16QAM

16QAM
1.12.13.34 Number of HSUPA 16QAM RAB Setup Attempts for cell
Counters
73403794 VS.HSUPA.RAB. Number of HSUPA 16QAM

16QAM.AttEstab RAB Setup Attempts for cell

BSC6900 UMTS
Description
This measurement item takes statistics of the number of HSUPA 16QAM RAB Setup Attempts
for cell. For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Measurement point
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

BSC6900 UMTS
Related Features
VS.HSUPA.RAB. WRFD-010694 UL 16QAM

16QAM.AttEstab
1.12.13.35 Number of HSUPA RABs Abnormal Released due to RF Failures for Cell
Counters
73391136 VS.HSUPA.RAB.AbnormR Number of HSUPA RABs

el.RF Abnormal Released due to
RF Failures for Cell
Description
This measurement item takes statistics of the number of abnormally released HSUPA services
due to RF cause in a cell.For DC-HSUPA users, this counter is measured only in the cell with
the primary carrier. The cause value for RF exceptions on the Iu interface is "Radio Connection
With UE Lost" or "Failure in the Radio Interface Procedure".
Measurement point
The measurement is triggered at point A as shown in the following figure. When an RF exception
occurs (including SRB reset, TRB reset, radio link synchronization failures, or air interface
process failures), the RNC sends the CN a RAB RELEASE REQUEST message with the cause
value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure." If the
RNC receives from the CN a RAB ASSIGNMENT REQUEST message with a cause value other
than "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization",
this counter is measured in the HSUPA serving cell if HSUPA services are enabled. For details
about the preceding cause values, see 3GPP TS 25.413.

BSC6900 UMTS
process failures), the RNC sends the CN a RAB RELEASE REQUEST message with the cause
value of "Radio Connection With UE Lost", or "Failure in the Radio Interface Procedure." If
the RNC receives from the CN an IU RELEASE COMMAND message with a cause value other

BSC6900 UMTS
process failures), the RNC sends the CN an IU RELEASE REQUEST message with the cause
value of "Radio Connection With UE Lost" or "Failure in the Radio Interface Procedure." If the
RNC receives from the CN a RAB ASSIGNMENT REQUEST message with a cause value other
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.AbnormR WRFD-01061206 Interactive and Background

el.RF WRFD-010632 Traffic Class on HSUPA
HSUPA

BSC6900 UMTS
1.12.13.36 Number of HSUPA UEs with Various Categories in a Cell
Counters
67204266 VS.HSUPA.UE.Mean.CAT Average Number of HSUPA

Cell

5 UEs with Category 5 in a Cell


67193599 VS.HSUPA.UE.Max.CAT1. Maximum Number of

4 HSUPA UEs with
Category1-4 in a Cell
67193602 VS.HSUPA.UE.Max.CAT5 Maximum Number of

HSUPA UEs with Category 5
in a Cell

in a Cell

in a Cell


in a Cell


in a Cell
specific formulas.

BSC6900 UMTS

1.4.DENO UEs with Category 1-4 in a
Cell(Denominator)

Cell(Numerator)

5.DENO UEs with Category 5 in a Cell
(Denominator)

5.NUM UEs with Category 5 in a Cell
(Numerator)

(Denominator)

(Numerator)

(Denominator)

(Numerator)

(Denominator)

(Numerator)

(Denominator)

(Numerator)
Description
These counters provide the average and maximum number of HSUPA UEs with various
categories in a serving cell. The actual CAT capability of HSUPA UEs is used for the

BSC6900 UMTS
measurement. The RNC calculates the mean and maximum numbers of HSUPA users of
category 8 or 9 only for the cell with the primary carrier.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of the number of
HSUPA UEs with various categories. At the end of the measurement period, by dividing the
accumulated value of sample data in the period by the number of samples, the average number
of HSUPA UEs with various categories in the measurement period is obtained; by selecting the
maximum value of sample data in the period, the maximum number of HSUPA UEs with various
categories in the measurement period is obtained.
Formula
VS.HSUPA.UE.Mean.CAT1.4 = [VS.HSUPA.UE.Mean.CAT1.4.NUM]/
[VS.HSUPA.UE.Mean.CAT1.4.DENO]
VS.HSUPA.UE.Mean.CAT5 = [VS.HSUPA.UE.Mean.CAT5.NUM]/
[VS.HSUPA.UE.Mean.CAT5.DENO]
Unit
None
Related Features
VS.HSUPA.UE.Mean.CAT WRFD-01061201 HSUPA UE Category

1.4 Support

5 Support

6 Support

7 Support
VS.HSUPA.UE.Max.CAT1. WRFD-01061201 HSUPA UE Category

4 Support

BSC6900 UMTS
VS.HSUPA.UE.Max.CAT5 WRFD-01061201 HSUPA UE Category

Support

Support

Support

8 Support

Support

9 Support

Support
1.12.13.37 Number of EDCH MAC-d Flow Setup Requests for Cell
Counters
73393829 VS.HSUPA.MACD.AttSet- Number of EDCH MAC-d

up Flow Setup Requests for Cell
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
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.

BSC6900 UMTS
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.

BSC6900 UMTS
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.
Figure 1-574 Radio link add procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.HSUPA.MACD.AttSet- WRFD-010612 HSUPA Introduction

up Package
1.12.13.38 Number of Failed HSUPA Service Establishments Due to Insufficiency

of Different Resources

BSC6900 UMTS
Counters
73393832 VS.HSUPA.RAB.FailEstab. Number of Failed HSUPA

ULPower.Cong Service Establishments Due
to UL Power Insufficiency
for Cell

ULIUBBand.Cong Service Establishments Due
to UL Iub Bandwidth

ULCE.Cong Service Establishments Due
to UL CE Insufficiency for
Cell
Description
These counters provide 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 CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request,
it requests related radio resources. This counter is measured in the HSUPA serving cell when
the RAB is for a HSUPA service and the resource request fails.
Figure 1-575 Failed RAB establishments due to resource insufficiency

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.FailEstab. WRFD-01061206 Interactive and Background

ULPower.Cong WRFD-010632 Traffic Class on HSUPA
HSUPA

ULIUBBand.Cong WRFD-010632 Traffic Class on HSUPA
HSUPA

ULCE.Cong WRFD-010632 Traffic Class on HSUPA
HSUPA
1.12.13.39 Average uplink throughput of the Traffic PS Conversational beared on

E-DCH for cell
Counters
73410485 VS.PS.Conv.Kbps.EDCH Average uplink throughput

of the Traffic PS
Conversational beared on E-
DCH for cell
specific formulas.

BSC6900 UMTS
73393915 VS.PS.Conv.Times.EDCH Duration of PS

Conversational HSUPA
MAC-D Flow Receiving
Data for Cell
Description
This measurement item takes statistics of the average uplink throughput of the Traffic PS
Conversational beared on E-DCH in the cell.
Measurement point
The RNC measures all UL traffic volume (the RLC headers and retransmitted data are not
included) (unit: bit) and duration (unit: ms) of the PS conversational service beared on EDCH
in the cell of the RLC layer. At the end of the measurement period, the RNC calculates average
bit rate.
Formula
VS.PS.Conv.Kbps.EDCH = {8}*[VS.PS.Conv.Traffic.EDCH]/[VS.PS.Conv.Times.EDCH]
Unit
kbit/s
Related Features
VS.PS.Conv.Kbps.EDCH WRFD-010617 VoIP over HSPA/HSPA+

WRFD-010501 Conversational QoS Class
1.12.13.40 Number of uplink bytes of Transport Blocks of Traffic PS Conversational

beared on E-DCH for cell
Counters
73393914 VS.PS.Conv.Traffic.EDCH Number of uplink bytes of

Transport Blocks of Traffic
PS Conversational beared on
E-DCH for cell

BSC6900 UMTS
Description
This measurement item takes statistics of the number of uplink bytes of Transport Blocks of
traffic PS conversational beared on E-DCH in the cell.
Measurement point
The RNC measures the total UL volume of PS conversational service beared on EDCH in the
cell of the RLC layer. Note that the RLC headers and retransmitted data are not included.
Formula
None
Unit
byte
Related Features
VS.PS.Conv.Traffic.EDCH WRFD-010617 VoIP over HSPA/HSPA+

WRFD-010501 Conversational QoS Class
1.12.13.41 Counters Related to the Number of Transfers Between Small

Retransmission and Large Retransmission for HSUPA 2ms TTI Users or HSUPA
10ms TTI Users
Counters
73393956 VS.HSUPA.RsnSmall2Larg Number of Times that

e.TTI2ms HSUPA 2ms TTI Users
Transfer from Small
Retransmission to Large
Retransmission for Cell
73393957 VS.HSUPA.RsnSmall2Larg Number of Times that

e.TTI10ms HSUPA 10ms TTI Users
Transfer from Small
Retransmission to Large

BSC6900 UMTS
73393958 VS.HSUPA.RsnLarge2Smal Number of Times that

l.TTI2ms HSUPA 2ms TTI Users
Transfer from Large
Retransmission to Small
73393959 VS.HSUPA.RsnLarge2Smal Number of Times that

l.TTI10ms HSUPA 10ms TTI Users
Transfer from Large
Retransmission to Small
Description
These counters provide the number of times that HSUPA 2ms TTI Users or HSUPA 10ms TTI
Users transfer between small retransmission and large retransmission in the serving cell. The
RNC calculates the number of DC-HSUPA users for the cell with the primary carrier and that
for the cell with the secondary carrier separately. HSUPA users allocated a 10-ms TTI do not
support DC-HSUPA.
Measurement point
The measurement can be triggered at point A as shown in the figure. The NodeB informs the
RNC of its retransmission state through the E-DCH UL DATA FRAME. After receiving the
frame, the RNC L2 checks whether the retransmission state changes. If yes, the RNC L2 sends
the inner message CMACD_EDCH_PDU_RETRANS_TAR_NUM_MODIFY to the RNC L3.
The RNC L3 then measures the corresponding counter based on the TTI of the user.
Figure 1-576 Adaptive retransmission procedure
The measurement can also be triggered at point B as shown in the figure. In the OLPC_MODIFY
scenario, only small retransmission can be used. In this case, the corresponding counter is
measured based on the TTI of the user when the user in large retransmission mode receives an
OLPC_MODIFY message.

BSC6900 UMTS
Figure 1-577 Retransmission of OLPC procedure
Formula
None
Unit
None
Related Features
VS.HSUPA.RsnSmall2Larg WRFD-010641 HSUPA Adaptive

e.TTI2ms Transmission
VS.HSUPA.RsnSmall2Larg WRFD-010641 HSUPA Adaptive

e.TTI10ms Transmission
VS.HSUPA.RsnLarge2Smal WRFD-010641 HSUPA Adaptive

l.TTI2ms Transmission
VS.HSUPA.RsnLarge2Smal WRFD-010641 HSUPA Adaptive

l.TTI10ms Transmission
1.12.13.42 Number of TTI Switch Attempts During RB Reconfiguration for Cell

BSC6900 UMTS
Counters
73393984 VS.HSUPA.TTI2to10.Att Number of TTI Switch

Attempts During RB
(2ms to 10ms)
73393986 VS.HSUPA.TTI10to2.Att Number of TTI Switch

Attempts During RB
(10ms to 2ms)
Description
These counters provide the number TTI switch attempts in the HSUPA serving cell. The
measurement is triggered by the RADIO BEAR RECONFIGURATION message.For DC-
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.TTI2to10.Att WRFD-010690 TTI Switch for BE Services

WRFD-01061404 Based on Coverage
HSUPA 2ms/10ms TTI
Handover
VS.HSUPA.TTI10to2.Att WRFD-010690 TTI Switch for BE Services

HSUPA 2ms/10ms TTI
Handover
1.12.13.43 Number of Successful TTI Switches During RB Reconfiguration for Cell
Counters
73393985 VS.HSUPA.TTI2to10.Succ Number of Successful TTI

Switches During RB
(2ms to 10ms)
73393987 VS.HSUPA.TTI10to2.Succ Number of Successful TTI

Switches During RB
(10ms to 2ms)
Description
These counters provide 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.

BSC6900 UMTS
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives from
the UE a RADIO BEARER RECONFIGURATION COMPLETE message from the UE. In this
case, this counter is measured in the best cell that the UE camps on.
Figure 1-579 RB reconfig procedure
Formula
None
Unit
None
Related Features
VS.HSUPA.TTI2to10.Succ WRFD-010690 TTI Switch for BE Services

HSUPA 2ms/10ms TTI
Handover

BSC6900 UMTS
VS.HSUPA.TTI10to2.Succ WRFD-010690 TTI Switch for BE Services

HSUPA 2ms/10ms TTI
Handover
1.12.13.44 Number of HSUPA 16QAM UEs in a Cell
Counters
73410507 VS.HSUPA. Average Number of HSUPA

16QAM.UE.Mean.Cell 16QAM UEs in a Cell
specific formulas.

16QAM.UE.Mean.Cell.DE- 16QAM UEs in a Cell
NO (Denominator)

16QAM.UE.Mean.Cell.NU 16QAM UEs in a Cell
M (Numerator)
Description
This counter provides the average number of HSUPA 16QAM UEs in a serving cell.
Measurement point
The system periodically (the measurement period is 5 second) takes samples of the number of
HSUPA 16QAM UEs. At the end of the measurement period, by dividing the accumulated value
of sample data in the period by the number of samples, the average number of HSUPA 16QAM
UEs in the measurement period is obtained. Intermediate counters: VS.HSUPA.
16QAM.UE.Mean.Cell.DENO: Sampling times in the measurement period (denominator)
VS.HSUPA.16QAM.UE.Mean.Cell.NUM: Accumulated number of HSUPA 16QAM UEs at
the sampling points in a cell in the measurement period (numerator)

BSC6900 UMTS
Formula
VS.HSUPA.16QAM.UE.Mean.Cell = [VS.HSUPA.16QAM.UE.Mean.Cell.NUM]/
[VS.HSUPA.16QAM.UE.Mean.Cell.DENO]
Unit
None
Related Features
VS.HSUPA. WRFD-010694 UL 16QAM

16QAM.UE.Mean.Cell
1.12.13.45 Number of HSUPA Boosting UEs in a Cell
Counters
73441120 VS.HSUPA.Boosting.UE.M Number of UEs Supporting

ean.Cell E-DPCCH Boosting for Cell
Description
This counter provides the average number of UEs in an active set of HSUPA E-DCH cells that
support E-DPCCH boosting.
Measurement point
UEs supporting E-DPCCH boosting in an HSUPA cell are sampled (sampling periodicity is 5
seconds) at a certain interval. At the end of a measurement period, this counter measured at each
sampling site is obtained by dividing the accumulated number of the UEs by the number of
samples.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.HSUPA.Boosting.UE.M WRFD-010697 E-DPCCH Boosting

ean.Cell
1.12.13.46 Number of UEs Supporting E-DPCCH Boosting and CPC for Cell
Counters
73441121 VS.HSUPA.BoostingCPC.U Number of UEs Supporting

E.Mean.Cell E-DPCCH Boosting and
CPC for Cell
Description
This counter provides the average number of UEs in an active set of HSUPA E-DCH cells that
support E-DPCCH boosting 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
VS.HSUPA.BoostingCPC.U WRFD-010697 E-DPCCH Boosting

E.Mean.Cell

BSC6900 UMTS
1.12.13.47 Number of RABs Abnormally Released for PS HSUPA Services during

the State Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell
Counters
73422168 VS.HSUPA.RAB.AbnormR Number of RABs

el.E2P Abnormally Released for PS
HSUPA Services during the
CELL_DCH to CELL_PCH
or URA_PCH for Cell
Description
This counter provides the number of RABs Abnormally Released for PS HSUPA Services during
the State Transition from CELL_DCH to CELL_PCH or URA_PCH in the serving cell.For DC-
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.

BSC6900 UMTS
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",

BSC6900 UMTS
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",

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.AbnormR WRFD-010202 UE State in Connected Mode

el.E2P WRFD-010612 (CELL-DCH, CELL-PCH,
URA-PCH, CELL-FACH)
HSUPA Introduction
Package
1.12.13.48 Number of HSUPA Boosting RAB Setup Attempts for Cell

BSC6900 UMTS
Counters
73423359 VS.HSUPA.RAB.Boosting. Number of HSUPA Boosting

AttEstab RAB Setup Attempts for Cell
Description
This counter provides the number of setup attempts for HSUPA RABs with the E-DPCCH
Boosting feature enabled in the serving cell.
Measurement point
the 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

BSC6900 UMTS
Related Features
VS.HSUPA.RAB.Boosting. WRFD-010697 E-DPCCH Boosting

AttEstab
1.12.13.49 Number of Successful HSUPA Boosting RAB Setups for Cell
Counters
73423360 VS.HSUPA.RAB.Boosting. Number of Successful

SuccEstab HSUPA Boosting RAB
Setups for Cell
Description
This counter provides the number of times that an HSUPA RAB with the E-DPCCH Boosting
feature enabled is set up successfully in the serving cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends the CN
an RAB ASSIGNMENT RESPONSE message after receiving from the UE a RADIO BEARER
SETUP COMPLETE message, this counter is measured in the serving cell that the UE camps
on if the RAB is intended for HSUPA services and the E-DPCCH Boosting feature is enabled.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.Boosting. WRFD-010697 E-DPCCH Boosting

SuccEstab
1.12.13.50 Number of Abnormally Released HSUPA Boosting RABs for Cell
Counters
73423361 VS.HSUPA.RAB.AbnormR Number of Abnormally

el.Boosting Released HSUPA Boosting
RABs for Cell
Description
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.

BSC6900 UMTS
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.

BSC6900 UMTS
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.AbnormR WRFD-010697 E-DPCCH Boosting

el.Boosting
1.12.13.51 Number of Normally Released HSUPA Boosting RABs for Cell
Counters
73423362 VS.HSUPA.RAB.NormRel. Number of Normally

Boosting Released HSUPA Boosting
RABs for Cell

BSC6900 UMTS
Description
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
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
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.NormRel. WRFD-010697 E-DPCCH Boosting

Boosting
1.12.13.52 Number of HARQ PO Reconfiguration Attempts of HSUPA Users with

10 ms TTI for Cell
Counters
73423567 VS.HSUPA.HARQ.POReCf Number of HARQ PO

gAtt.TTI10ms Reconfiguration Attempts of
HSUPA Users with 10 ms
TTI for Cell

BSC6900 UMTS
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

BSC6900 UMTS
Related Features
VS.HSUPA.HARQ.POReCf WRFD-010712 Adaptive Configuration of

gAtt.TTI10ms Traffic Channel Power offset
for HSUPA
1.12.13.53 Number of Successful HARQ PO Reconfigurations of HSUPA Users

with 10 ms TTI for Cell
Counters
73423568 VS.HSUPA.HARQ.POReCf Number of Successful

gSucc.TTI10ms HARQ PO Reconfigurations
of HSUPA Users with 10 ms
TTI for Cell
Description
This counter provides the number of successful HARQ PO reconfigurations of HSUPA users
with 10 ms TTI in a cell.
The counter is used to evaluate the application of the Adaptive Configuration of Traffic Channel
Power offset for HSUPA feature in a network.
Measurement point
At point B shown in the figure, when the RNC receives a RADIO BEAR RECONFIGURATION
COMPLETE message during the HARQ PO reconfiguration, the measurement is triggered in
the serving cell of HSUPA users.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.HARQ.POReCf WRFD-010712 Adaptive Configuration of

gSucc.TTI10ms Traffic Channel Power offset
for HSUPA
1.12.13.54 Number of DC-HSUPA RAB Setup Attempts for Cell
Counters
73424115 VS.HSUPA.RAB.DC.At- Number of DC-HSUPA

tEstab RAB Setup Attempts for Cell

BSC6900 UMTS
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

BSC6900 UMTS
Related Features
VS.HSUPA.RAB.DC.At- WRFD-140204 DC-HSUPA

tEstab
1.12.13.55 Number of Successful DC-HSUPA RAB Setups for Cell
Counters
73424116 VS.HSUPA.RAB.DC.Suc- Number of Successful DC-

cEstab HSUPA RAB Setups for Cell
Description
This counter provides the number of successful DC-HSUPA RAB setups in the serving cell
where the DC-HSUPA feature is enabled. This counter is measured only in the cell with the
primary carrier.
Measurement point
This measurement is triggered at point B, as shown in the following figure. When the RNC sends
the CN an RAB ASSIGNMENT RESPONSE message after receiving from the UE a RADIO
BEARER SETUP COMPLETE message, this counter is incremented by one in the cell with the
primary carrier, if the RAB is intended for HSUPA services and the DC-HSUPA feature is
enabled.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.DC.Suc- WRFD-140204 DC-HSUPA

cEstab
1.12.13.56 Number of DC-HSUPA RABs Normally Released for Cell
Counters
73424117 VS.HSUPA.RAB.DC.Norm Number of DC-HSUPA

Rel RABs Normally Released for
Cell
Description
This counter provides the number of DC-HSUPA RABs normally released by the RNC in the
serving cell where the DC-HSUPA feature is enabled. This counter is measured only in the cell
Measurement point
This measurement is triggered at point A, as shown in the following figure. After receiving an
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.

BSC6900 UMTS
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
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.DC.Norm WRFD-140204 DC-HSUPA

Rel
1.12.13.57 Number of DC-HSUPA RABs Abnormally Released for Cell
Counters
73424118 VS.HSUPA.RAB.DC.Ab- Number of DC-HSUPA

normRel RABs Abnormally Released
for Cell
Description
This counter provides the number of DC-HSUPA RABs abnormally released by the RNC in the
serving cell where the DC-HSUPA feature is enabled. This counter is measured only in the cell
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.

BSC6900 UMTS
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.

BSC6900 UMTS
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.DC.Ab- WRFD-140204 DC-HSUPA

normRel
1.12.13.58 Mean Number of DC-HSUPA Users in the Cell with the Primary Carrier
Counters
73424192 VS.HSUPA.DC.PRIM.UE. Mean Number of DC-

Mean.Cell HSUPA Users in the Cell
with the Primary Carrier

BSC6900 UMTS
73441238 VS.HSUPA.DC.SEC.UE.M Mean Number of DC-

ean.Cell HSUPA Users in the Cell
with the Secondary Carrier
specific formulas.
73424194 VS.HSUPA.DC.PRIM.UE. Average Number of HSUPA

Mean.Cell.DENO UEs in a primary Cell
(Denominator)
73424193 VS.HSUPA.DC.PRIM.UE. Average Number of HSUPA

Mean.Cell.NUM UEs in a primary Cell
(Numerator)
73424196 VS.HSUPA.DC.SEC.UE.M Average Number of HSUPA

ean.Cell.DENO UEs in supplementary carrier
Cell(Denominator)
73424195 VS.HSUPA.DC.SEC.UE.M Average Number of HSUPA

ean.Cell.NUM UEs in supplementary carrier
Cell(Numerator)
Description
These counters provide the mean number of DC-HSUPA users in the cell with the primary carrier
and the mean number of DC-HSUPA users in the cell with the secondary carrier, respectively.
Measurement point
The RNC takes samples every 5 seconds at each measurement point. At the end of each
measurement period, the RNC divides the sum of sampling results by the number of samples.
Intermediate counters: VS.HSUPA.DC.PRIM.UE.Mean.Cell.DENO: Sampling times in the
measurement period (denominator) VS.HSUPA.DC.PRIM.UE.Mean.Cell.NUM: Accumulated
Number of DC-HSUPA Users in the Cell with the Primary Carrier at the sampling points in the
measurement period (numerator) VS.HSUPA.DC.SEC.UE.Mean.Cell.DENO: Sampling times
in the measurement period (denominator) VS.HSUPA.DC.SEC.UE.Mean.Cell.NUM:
Accumulated Number of DC-HSUPA Users in the Cell with the Secondary Carrier at the
sampling points in the measurement period (numerator)
Formula
VS.HSUPA.DC.PRIM.UE.Mean.Cell = [VS.HSUPA.DC.PRIM.UE.Mean.Cell.NUM]/
[VS.HSUPA.DC.PRIM.UE.Mean.Cell.DENO]

BSC6900 UMTS
VS.HSUPA.DC.SEC.UE.Mean.Cell = [VS.HSUPA.DC.SEC.UE.Mean.Cell.NUM]/
[VS.HSUPA.DC.SEC.UE.Mean.Cell.DENO]
Unit
None
Related Features
VS.HSUPA.DC.PRIM.UE. WRFD-140204 DC-HSUPA

Mean.Cell
VS.HSUPA.DC.SEC.UE.M WRFD-140204 DC-HSUPA

ean.Cell
1.12.13.59 Number of HSUPA 2 ms TTI UEs in a Cell
Counters
73441239 VS.HSUPA.UE.Mean.TTI2 Average Number of HSUPA

ms 2 ms TTI UEs in a Cell
73424199 VS.HSUPA.UE.Max.TTI2m Maximum Number of

s HSUPA 2 ms TTI UEs in a
Cell
specific formulas.

ms.DENO 2 ms TTI UEs in a Cell
(Denominator)

ms.NUM 2 ms TTI UEs in a Cell
(Numerator)
Description
These counters provide the average and maximum numbers of HSUPA 2 ms TTI UEs in a cell.
For DC-HSUPA users, these counters are measured only in the cell with the primary carrier.

BSC6900 UMTS
Measurement point
measurement period, the RNC sums sample results and divides the sum by the number of
samples. The division result is the mean number of HSUPA 2 ms TTI UEs in a cell. Of the
sample results, the maximum value is the maximum number of HSUPA 2 ms TTI UEs in the
cell. Intermediate counters: VS.HSUPA.UE.Mean.TTI2ms.DENO: Sampling times in the
measurement period (denominator) VS.HSUPA.UE.Mean.TTI2ms.NUM: Accumulated
number of HSUPA 2 ms TTI UEs at the sampling points in a cell in the measurement period
(numerator)
Formula
VS.HSUPA.UE.Mean.TTI2ms = [VS.HSUPA.UE.Mean.TTI2ms.NUM]/
[VS.HSUPA.UE.Mean.TTI2ms.DENO]
Unit
None
Related Features
VS.HSUPA.UE.Mean.TTI2 WRFD-010612 HSUPA Introduction

ms WRFD-01061403 Package
HSUPA 2ms TTI
VS.HSUPA.UE.Max.TTI2m WRFD-010612 HSUPA Introduction

s WRFD-01061403 Package
HSUPA 2ms TTI
1.12.13.60 Number of HSUPA 10 ms TTI UEs in a Cell
Counters
73441240 VS.HSUPA.UE.Mean.TTI1 Average number of HSUPA

0ms 10 ms TTI UEs in a Cell
73424202 VS.HSUPA.UE.Max.TTI10 Maximum Number of

ms HSUPA 10 ms TTI UEs in a
Cell
specific formulas.

BSC6900 UMTS

0ms.DENO 10 ms TTI UEs in a Cell
(Denominator)

0ms.NUM 10 ms TTI UEs in a Cell
(Numerator)
Description
These counters provide the average and maximum numbers of HSUPA 10 ms TTI UEs in a cell.
Measurement point
measurement period, the RNC sums sample results and divides the sum by the number of
samples. The division result is the mean number of HSUPA 10 ms TTI UEs in a cell. Of the
sample results, the maximum value is the maximum number of HSUPA 10 ms TTI UEs in the
cell. Intermediate counters: VS.HSUPA.UE.Mean.TTI10ms.DENO: Sampling times in the
measurement period (denominator) VS.HSUPA.UE.Mean.TTI10ms.NUM: Accumulated
number of HSUPA 10 ms TTI UEs at the sampling points in a cell in the measurement period
(numerator)
Formula
VS.HSUPA.UE.Mean.TTI10ms = [VS.HSUPA.UE.Mean.TTI10ms.NUM]/
[VS.HSUPA.UE.Mean.TTI10ms.DENO]
Unit
None
Related Features
VS.HSUPA.UE.Mean.TTI1 WRFD-010612 HSUPA Introduction

0ms Package
VS.HSUPA.UE.Max.TTI10 WRFD-010612 HSUPA Introduction

ms Package
1.12.13.61 Number of Successful RAB Establishments Initiated by HSUPA 2 ms

UEs with a 10 ms TTI in a Cell with Various Causes

BSC6900 UMTS
Counters
73424205 VS.HSUPA.RABEstabTTI1 Number of Successful RAB

0ms.AdmCE.Succ Establishments Initiated by
HSUPA 2 ms UEs with a 10
ms TTI Due to Congestion of
Admitted CEs in a Cell

0ms.ResRTWP.Succ Establishments Initiated by
ms TTI Due to RTWP

0ms.ResUsedCE.Succ Establishments Initiated by
ms TTI Due to Congestion of
Occupied CEs in a Cell

0ms.ResIUB.Succ Establishments Initiated by
ms TTI Due to Iub Resource

0ms.Cover.Succ Establishments Initiated by
ms TTI Due to Limited
Uplink Coverage
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
1.12.13.62 Number of Abnormal RAB Releases for Cell During State Transition of
HSUPA UEs to CELL/URA_PCH
Counters
73425950 VS.HSUPA.RAB.Abnorm- Number of Abnormal RAB

Rel.16QAM2P Releases for Cell During
State Transition of HSUPA
+16QAM UEs to CELL/
URA_PCH

BSC6900 UMTS
73425951 VS.HSUPA.RAB.AbnormR Number of Abnormal RAB

el.DC2P Releases for Cell During
HSUPA UEs to CELL/
URA_PCH
Description
These counters provide the number of abnormal RAB releases during the state transition of
HSUPA UEs to CELL_PCH or URA_PCH in the serving cell. For DC-HSUPA UEs, this counter
is measured only in the primary carrier cell.
Measurement point
As shown by point A in figure 1, when an exception occurs, the RNC sends the CN an RAB
RELEASE REQUEST message. When the RNC receives from the CN an RAB ASSIGNMENT
REQUEST message with the cause value being other than "User Inactivity", "Normal Release",
serving cell where the UE camps. For details on cause values indicating RAB releases, see 3GPP
TS 25.413.
Figure 1-600 The release process of RAB
As shown by point A in figure 2, when an exception occurs, the RNC sends the CN a RAB
RELEASE REQUEST message. When the RNC receives from the CN an IU RELEASE

BSC6900 UMTS
COMMAND message with the cause value being other than "User Inactivity", "Normal
in the serving cell where the UE camps. For details on cause values indicating RAB releases,
see 3GPP TS 25.413.
Figure 1-601 The IU release process of RAB
As shown by point A in figure 3, when an exception occurs, the RNC sends the CN an IU
RELEASE REQUEST message. When the RNC receives from the CN an IU RELEASE
COMMAND message with the cause value being other than "User Inactivity", "Normal
in the serving cell where the UE camps. For details on cause values indicating RAB releases,
see 3GPP TS 25.413.

BSC6900 UMTS
Figure 1-602 The IU release process launched by RNC
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.Abnorm- WRFD-010694 UL 16QAM

Rel.16QAM2P
VS.HSUPA.RAB.AbnormR WRFD-140204 DC-HSUPA

el.DC2P
1.12.13.63 Number of Normal RAB Releases of HSUPA UEs for Cell (All Scenarios)

BSC6900 UMTS
Counters
73425952 VS.HSUPA.RAB.NormRel. Number of Normal RAB

16QAM.All Releases of HSUPA
Scenarios)
73425953 VS.HSUPA.RAB.NormRel. Number of Normal RAB

DC.All Releases of DC-HSUPA UEs
Description
These counters provide the number of normal RAB releases in a serving cell when HSUPA is
applied. For DC-HSUPA users, this counter is measured only in the cell with the primary carrier.
Note: The normal RAB releases on HSUPA channels include the RAB releases over the Iu
interface and the switchover of the RAB from a technique to another one. The following uses
DC-HSUPA as an example to describe a normal RAB release. (1) The DC-HSUPA RAB has
been released over the Iu interface. (2) The RAB successfully falls back from DC-HSUPA to
SC-HSUPA or R99 through a channel switchover procedure. In R99, the UE can be in the
CELL_DCH, CELL_FACH, CELL_PCH, or URA_PCH state. (3) The RAB successfully falls
back from DC-HSUPA to SC-HSUPA or to R99 in CELL_DCH state through an inter-cell hard
handover procedure. The two cells can operate in either the same or different frequencies.
Measurement point
As shown by point A in figure 1 (HSUPA UEs enter the idle state), after receiving an IU
RELEASE COMMAND message from the CN, the RNC releases the corresponding RAB and
then sends an IU RELEASE COMPLETE message to the CN. This counter is increased by one
in the serving cell where the UE camps when either of the following condition is met: The cause
value in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release",
"Successful Relocation", or "Network Optimization." Alternatively, the RNC has initiated a
release request with the cause value "User Inactivity", "Network Optimization", or "UE
Generated Signalling Connection Release" before receiving the IU RELEASE COMMAND
message.

BSC6900 UMTS
As shown by point B in figure 2 (HSUPA UEs enter the idle state), after receiving an RAB
to the CN. This counter is increased by one in the serving cell where the UE camps when either
of the following condition is met: The cause value in the RAB ASSIGNMENT REQUEST
Optimization." Alternatively, the RNC has initiated a release request with the cause value "User
receiving the RAB ASSIGNMENT REQUEST message.
As shown by point B in figure 3 (all types of hard handovers for HSUPA UEs), the RNC receives
a RADIO BEARER RECONFIGURATION COMPLETE message from a UE. If the UE is
performing a hard handover on the RAB from HSUPA channel to channels of other types, this
counter is increased by one in the serving cell of the UE. As shown by point B in figure 3 (all
types of channel switchovers for HSUPA UEs), the RNC receives a RADIO BEARER
RECONFIGURATION COMPLETE message from a UE. If the UE is performing a switchover
on the RAB from HSUPA channel to channels of other types, this counter is increased by one
in the serving cell of the UE.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.HSUPA.RAB.NormRel. WRFD-010694 UL 16QAM

16QAM.All
VS.HSUPA.RAB.NormRel. WRFD-140204 DC-HSUPA

DC.All
1.12.14 InterRAT Handover Measurement per cell

(INTRAT.HO.Cell)
Overview
Inter-RAT handover is classified into CS inter-RAT handover and PS inter-RAT handover. PS
inter-RAT handover is further classified into normal PS inter-RAT handover and enhanced PS
inter-RAT handover, where the procedure of the enhanced PS inter-RAT handover is the same
as that of the CS inter-RAT handover. For the detailed inter-RAT handover procedure, see the
function subset IRATHO.Cs.RNC or IRATHO.PS.RNC. The counters related to the number of
failed handovers during different phases of outgoing handovers and incoming handovers are
measured based on different handover causes.

BSC6900 UMTS
The causes for outgoing inter-RAT handover can be load, RF (coverage, QoS, or HCS), inter-
RAT DRD, or service type. The cause inter-RAT DRD only exists in the inter-RAT CS handover.
The following figure shows the measurement points in the inter-RAT CS handover measuremnt.
Figure 1-606 Flow chart of outgoing inter-RAT handover measurement procedure

BSC6900 UMTS
A VS.IRATHO.AttRelocPrepOutCS.DR,
VS.IRATHO.AttRelocPrepOutCS.RF,
VS.IRATHO.AttRelocPrepOutCS.Load,
IRATHO.AttRelocPrepOutCS,
VS.IRATHO.AttRelocPrepOutCS.Service,
VS.IRATHO.AttRelocPrepOutCS.Sig,
VS.IRATHO.AttRelocPrepOutPS,
VS.IRATHO.AttOutCS.MBDR,
VS.SRVCC.U2GERAN.AttRelocPre-
pOutPS
B VS.IRATHO.SuccRelocPrepOutCS.RF,
VS.IRATHO.SuccRelocPrepOutCS.DR,
VS.IRATHO.SuccRelocPrepOutCS.Load,
IRATHO.SuccRelocPrepOutCS,
VS.IRATHO.SuccRelocPrepOutCS.Serv-
ice, VS.IRATHO.SuccRelocPrepOutCS.Sig,
VS.IRATHO.SuccRelocPrepOutPS,
VS.SRVCC.U2GERAN.SuccRelocPre-
pOutPS
C IRATHO.AttOutCS,
VS.IRATHO.AttOutCS.Sig,
VS.IRATHO.AttRelocOutPS,
VS.IRATHO.AttOutCS.TrigRscp,
VS.IRATHO.AttOutCS.TrigEcNo,
VS.IRATHO.AttOutCS.TrigULTxp,
VS.IRATHO.AttOutCS.TrigDLTxp
D IRATHO.SuccOutCS,
VS.IRATHO.SuccOutCS.DR,
VS.IRATHO.SuccOutCS.Load,
VS.IRATHO.SuccOutCS.RF,
VS.IRATHO.SuccOutCS.Service,
VS.IRATHO.SuccOutCS.Sig,
VS.IRATHO.SuccRelocOutPS,
VS.IRATHO.SuccOutCS.MBDR,
VS.SRVCC.U2GERAN.SuccRelocOutPS,
VS.IRATHO.SuccOutCS.TrigRscp,
VS.IRATHO.SuccOutCS.TrigEcNo,
VS.IRATHO.SuccOutCS.TrigULTxp,
VS.IRATHO.SuccOutCS.TrigDLTxp

BSC6900 UMTS
E IRATHO.FailRelocPrepOutCS.UKnowRN
C, IRATHO.FailRelocPrepOutCS.NoResA-
vail,
IRATHO.FailRelocPrepOutCS.TAlExp,
IRATHO.FailRelocPrepOutCS.TgtFail,
IRATHO.FailRelocPrepOutCS.ReloNoSup,
IRATHO.FailRelocPrepOutCS.HigherTraf-
ficLod,
VS.IRATHO.FailRelocPrepOutPS.TAlExp,
VS.IRATHO.FailRelocPrepOutPS.TgtFail,
VS.IRATHO.FailRelocPrepOutPS.ReloUn-
Supp,
VS.IRATHO.FailRelocPrepOutPS.TgtHigh-
Load,
VS.IRATHO.FailRelocPrepOutPS.NoRe-
sAvail,
VS.IRATHO.FailRelocPrepOutPS.Un-
KnowRNC,
VS.IRATHO.FailRelocPrepOutCS.Cancel,
VS.IRATHO.FailRelocPrepOutCS.ReqInfo-
NotAvail,
VS.IRATHO.FailRelocPrepOutCS.CNNoR
eply,
VS.IRATHO.FailRelocPrepInCS.Abort,
VS.IRATHO.FailRelocPrepOutCS.Abort
F IRATHO.FailOutCS.CfgUnsupp,
IRATHO.FailOutCS.PhyChFail,
VS.IRATHO.FailRelocOutPS.CfgUnSupp,
VS.IRATHO.FailRelocOutPS.PhyChFail,
VS.IRATHO.FailOutCS.SCRI,
VS.IRATHOCS.Cancel.ReEstab
G VS.IRATHO.FailOutCS.NoReply,
VS.IRATHO.FailOutCS.InterRatRF,
VS.IRATHO.FailRelocOutPS.NoReply,
VS.IRATHO.FailOutCS.NoReply,
VS.IRATHO.FailOutCS.Abort
H VS.IRATHO.AttNACC, VS.IRATHO.Succ-
NACC, VS.IRATHO.AttENACC,
VS.IRATHO.SuccENACC

BSC6900 UMTS
I IRATHO.AttOutPSUTRAN,
VS.IRATHO.AttOutPSUTRAN.Load,
VS.IRATHO.AttOutPSUTRAN.RF,
VS.IRATHO.AttOutPSUTRAN.Service,
VS.IRATHO.HSDPA.AttOutPSUTRAN,
VS.IRATHO.HSUPA.AttOutPSUTRAN,
VS.IRATHO.AttOutPSUTRAN.Sig,
VS.IRATHO.AttOutPS.TrigRscp,
VS.IRATHO.AttOutPS.TrigEcNo,
VS.IRATHO.AttOutPS.TrigULTxp,
VS.IRATHO.AttOutPS.TrigDLTxp
J IRATHO.SuccOutPSUTRAN,
VS.IRATHO.SuccOutPSUTRAN.Load,
VS.IRATHO.SuccOutPSUTRAN.RF,
VS.IRATHO.SuccOutPSUTRAN.Service,
VS.IRATHO.HSDPA.SuccOutPSUTRAN,
VS.IRATHO.HSUPA.SuccOutPSUTRAN,
VS.IRATHO.SuccOutPSUTRAN.Sig,
VS.IRATHO.SuccOutPS.TrigRscp,
VS.IRATHO.SuccOutPS.TrigEcNo,
VS.IRATHO.SuccOutPS.TrigULTxp,
VS.IRATHO.SuccOutPS.TrigDLTxp
K IRATHO.FailOutPSUTRAN.CfgUnsupp,
IRATHO.FailOutPSUTRAN.PhyChFail,
VS.IRATHO.FailOutPS,
VS.IRATHO.FailOutPSUTRAN.SCRI,
VS.IRATHOPS.Cancel.ReEstab,
VS.IRATHO.FailOutPS.UEGen,
VS.IRATHO.FailOutPSUTRAN.NoSRNS-
DataForwardCmd
L VS.IRATHO.FailOutPSUTRAN.NoReply,
VS.IRATHO.FailOutPS.Abort,
VS.IRATHO.FailOutPSUTRAN.Inter-
RatRF, VS.IRATHO.FailOutPS.UEGen
M VS.IRATHO.AttOutPSUE,
VS.IRATHO.AttOutPS.TrigRscp,
VS.IRATHO.AttOutPS.TrigEcNo,
VS.IRATHO.AttOutPS.TrigULTxp,
VS.IRATHO.AttOutPS.TrigDLTxp
N IRATHO.SuccOutPSUE,
VS.IRATHO.SuccOutPS.TrigRscp,
VS.IRATHO.SuccOutPS.TrigEcNo,
VS.IRATHO.SuccOutPS.TrigULTxp,
VS.IRATHO.SuccOutPS.TrigDLTxp

BSC6900 UMTS
Figure 1-607 Flow chart of incoming inter-RAT handover measurement procedure
A VS.IRATHO.AttRelocPrepInCS,
VS.IRATHO.AttRelocPrepInPS,
VS.L2U.AttRelocPrepInPS.CS.CELL,
VS.SRVCC.L2U.AttRelocPrepInCSPS

BSC6900 UMTS
B VS.IRATHO.SuccRelocPrepInCS,
VS.IRATHO.SuccRelocPrepInPS,
VS.L2U.SuccRelocPrepInPS.CS.CELL,
VS.SRVCC.L2U.SuccRelocPrepInCSPS
C VS.IRATHO.AttInCS, VS.SRVCC.L2U.At-
tInCSPS
D VS.IRATHO.SuccInCS, VS.IRATHO.Suc-
cRelocInPS,
VS.L2U.SuccRelocInPS.CS.CELL,
VS.SRVCC.L2U.SuccInCSPS
E VS.IRATHO.FailRelocPrepInCS.ResUna-
vail,
VS.IRATHO.FailRelocPrepInCS.TgtHigh-
Load,
VS.IRATHO.FailRelocPrepInCS.TRNCSys
FailReloc,
VS.IRATHO.FailRelocPrepInCS.TRNCSys
RelocUnsupp,
VS.IRATHO.FailRelocPrepInPS.TgtFail,
VS.IRATHO.FailRelocPrepInPS.ReloUn-
Supp, VS.IRATHO.FailRelocPrepInPS.Re-
sUnavail,
VS.IRATHO.FailRelocPrepInPS.TgtHigh-
Load
F VS.IRATHO.FailInCS.NoReply,
VS.IRATHO.FailRelocInPS.NoReply
G See counter "RRC.AttConnEstab.IRAT-

CelRes" in function subset "RRC.Setup.Cell"
H See counter "RRC.SuccConnEstab.IRAT-

CelRes" in function subset "RRC.Setup.Cell"
I See counter "RRC.AttConnEstab.IRATC-

CO" in function subset "RRC.Setup.Cell"
J See counter "RRC.SuccConnEstab.IRATC-

CO" in function subset "RRC.Setup.Cell"

BSC6900 UMTS
Counters
Description

OutCS.DR Successful CS V900R011
Outgoing Inter-RAT
Handovers Based on
Directed Retry for
Cell
67189730 VS.IRATHO.AttRe Number of Earlier than

locPrepOutCS.DR Preparation V900R011
Attempts for CS
Outgoing Inter-RAT
Handover Based on
Directed Retry for
Cell

RelocPrepOutCS.D Successful V900R011
R Preparations for CS
Outgoing Inter-RAT
Handover Based on
Directed Retry for
Cell

locPrepOutCS.Loa Preparation V900R011
d Attempts for CS
Outgoing Inter-RAT
Handover Initiated
by UTRAN Based on
Load for Cell

RelocPrepOutCS.L Successful V900R011
oad Preparations for CS
Outgoing Inter-RAT
Handover Initiated
by UTRAN Based on
Load for Cell

OutCS.Load Successful CS V900R011
Outgoing Inter-RAT
Handovers Based on
Load for Cell

BSC6900 UMTS

Description

utPSUTRAN.Load Outgoing Inter-RAT V900R011
Handover Attempts
Initiated by UTRAN
Based on Load for
Cell

OutPSUTRAN.Loa Successful PS V900R011
d Outgoing Inter-RAT
Handovers Initiated
by UTRAN Based on
Load for Cell

locPrepOutCS.RF Preparation V900R011
Attempts for CS
Outgoing Inter-RAT
Handover Based on
RF (Coverage, QoS,
or HCS) for Cell

RelocPrepOutCS.R Successful V900R011
F Preparations for CS
Outgoing Inter-RAT
Handover Based on
RF (Coverage, QoS,
or HCS) for Cell

OutCS.RF Successful CS V900R011
Outgoing Inter-RAT
Handovers Based on
RF (Coverage, QoS,
or HCS) for Cell

utPSUTRAN.RF Outgoing Inter-RAT V900R011
Handover Attempts
Initiated by the RNC
Based on RF
(Coverage, QoS, or
HCS) for Cell

BSC6900 UMTS

Description

OutPSUTRAN.RF Successful PS V900R011
Outgoing Inter-RAT
Handovers Initiated
by the RNC Based on
RF (Coverage, QoS,
or HCS) for Cell
67189749 IRATHO.AttReloc- Number of Earlier than

PrepOutCS Preparation V900R011
Attempts for CS
Outgoing Inter-RAT
Handover for Cell
67189750 IRATHO.SuccRe- Number of Earlier than

locPrepOutCS Successful V900R011
Preparations for CS
Outgoing Inter-RAT
Handover for Cell
67189751 IRATHO.FailReloc Number of Failed Earlier than

PrepOutCS.TAlEx Preparations for CS V900R011
p Outgoing Inter-RAT
Handover for Cell
(TRELOCalloc
expiry)

PrepOutCS.TgtFail Preparations for CS V900R011
Outgoing Inter-RAT
Handover for Cell
(Relocation Failure
in Target CN/RNC or
Target System)

PrepOutCS.Relo- Preparations for CS V900R011
NoSup Outgoing Inter-RAT
Handover for Cell
(Relocation not
supported in Target
RNC or Target
system)
67189754 IRATHO.AttOutC Number of CS Earlier than

S Outgoing Inter-RAT V900R011
Handover Attempts

BSC6900 UMTS

Description
67189755 IRATHO.SuccOut Number of Earlier than

CS Successful CS V900R011
Outgoing Inter-RAT
Handovers for Cell
67189756 IRATHO.FailOutC Number of Failed CS Earlier than

S.CfgUnsupp Outgoing Inter-RAT V900R011
Handovers for Cell
(Configuration
Unsupported)
67189757 IRATHO.FailOutC Number of Failed CS Earlier than

S.PhyChFail Outgoing Inter-RAT V900R011
Handovers for Cell
(Physical Channel
Failure)

locPrepInCS Preparations for CS V900R011
Incoming Inter-RAT
Handover for Cell
67189759 VS.IRATHO.Suc- Number of Earlier than

cInCS Successful CS V900R011
Incoming Inter-RAT
Handovers for Cell
67189760 VS.IRATHO.FailR Number of Failed Earlier than

elocPrepInCS.TRN Preparations for CS V900R011
CSysFailReloc Incoming Inter-RAT
Handover
(Relocation failure in
target CN/RNC or
target system)

elocPrepInCS.TRN Preparations for CS V900R011
CSysRelocUnsupp Incoming Inter-RAT
Handover
(Relocation not
supported in target
RNC or target
system)

elocPrepInCS.Re- Preparations for CS V900R011
sUnavail Incoming Inter-RAT
Handover (No
resource available)

BSC6900 UMTS

Description
67189763 IRATHO.SuccOut- Number of Earlier than

PSUE Successful PS V900R011
Outgoing Inter-RAT
Handovers Initiated
by UE for Cell
67190410 VS.IRATHO.FailI Number of Failed CS Earlier than

nCS.NoReply Inter-RAT Incoming V900R011
Handovers Due to
No Response from
UE for Cell
67190411 IRATHO.AttOut- Number of PS Earlier than

PSUTRAN Outgoing Inter-RAT V900R011
Handover Attempts
Initiated by RNC for
Cell
67190412 IRATHO.SuccOut- Number of Earlier than

PSUTRAN Successful PS V900R011
Outgoing Inter-RAT
Handovers Initiated
by RNC for Cell
67190476 IRATHO.FailOutP Number of Failed PS Earlier than

SUTRAN.CfgUnsu Outgoing Inter-RAT V900R011
pp Handovers Initiated
by RNC
(Configuration
unsupported)
67190477 IRATHO.FailOutP Number of Failed PS Earlier than

SUTRAN.PhyChFa Outgoing Inter-RAT V900R011
il Handovers Initiated
by RNC (Physical
Channel Failure)
67190413 VS.IRATHO.At- Number of PS Inter- Earlier than

tOutPSUE RAT Outgoing Inter- V900R011
RAT Handover
Requests Initiated by
UE for Cell

cRelocPrepInCS Successful V900R011
preparations for CS
Incoming Inter-RAT
Handovers for Cell

BSC6900 UMTS

Description

locPrepOutCS.Serv Preparation V900R011
ice Attempts for CS
Outgoing Inter-RAT
Handover Based on
Service Type for Cell

RelocPrepOutCS.S Successful V900R011
ervice Preparations for CS
Outgoing Inter-RAT
Handover Based on

OutCS.Service Successful CS V900R011
Outgoing Inter-RAT
Handovers Based on

utPSUTRAN.Serv- Outgoing Inter-RAT V900R011
ice Handover Attempts
Initiated by the RNC
Based on Service
Type for Cell

OutPSUTRAN.Ser Successful PS V900R011
vice Outgoing Inter-RAT
Handovers Initiated
by the RNC Based on
67191155 VS.IRATHO.HSD Number of PS Inter- Earlier than

PA.AttOutPSUTR RAT Outgoing V900R011
AN Handover Attempts
for HSDPA Services
for Cell
67191156 VS.IRATHO.HSD Number of Earlier than

PA.SuccOutPSU- Successful PS V900R011
TRAN Outgoing Inter-RAT
Handovers for
HSDPA Services for
Cell

BSC6900 UMTS

Description
67192506 VS.IRATHO.HSU Number of Earlier than

PA.SuccOutPSU- Successful PS V900R011
Handovers for
HSUPA Services for
Cell
67192507 VS.IRATHO.HSU Number of PS Earlier than

PA.AttOutPSUTR Outgoing Inter-RAT V900R011
AN Handover Attempts
for HSUPA Services
for Cell

PrepOutCS.High- Preparations for CS V900R011
erTrafficLod Outgoing Inter-RAT
Handover for Cell
(Traffic Load In The
Target Cell Higher
Than In The Source
Cell)

elocPrepInCS.Tgt Preparations for CS V900R011
HighLoad Incoming Inter-RAT
Handover (Traffic
Load In The Target
Cell Higher Than In
The Source Cell)

locPrepOutCS.Sig Preparations for CS V900R011
Outgoing Inter-RAT
Handover When only
Signaling Exists for
Cell

RelocPrepOutCS.S Successful V900R011
ig Preparations for CS
Outgoing Inter-RAT
Handover When only
Signaling Exists for
Cell

utCS.Sig Outgoing Inter-RAT V900R011
Handover Attempts
When only Signaling
Exists for Cell

BSC6900 UMTS

Description

OutCS.Sig Successful CS V900R011
Outgoing Inter-RAT
Handovers When
only Signaling Exists
for Cell

PrepOutCS.NoRe- Preparations for CS V900R011
sAvail Outgoing Inter-RAT
Handover for Cell
(No Resource
Available)

PrepOutCS.UKno Preparations for CS V900R011
wRNC Outgoing Inter-RAT
Handover for Cell
(Unknown Target
RNC)
67192660 VS.IRATHO.FailO Number of Times Earlier than

utCS.NoReply that the Timer V900R011
Waiting for Iu
Release Command
Expires in CS
Outgoing Inter-RAT
Handover for Cell
67192661 VS.IRATHO.FailO Number of Times Earlier than

utPSUTRAN.NoRe that the Timer V900R011
ply Waiting for Iu
Release Command
Expires in PS
Outgoing Inter-RAT
Handover Initiated
by RNC for Cell

locPrepOutPS Preparations for V900R011
Enhanced PS
Outgoing Inter-RAT
Handover for Cell

cRelocPrepOutPS Successful V900R011
Preparations for
Enhanced PS
Outgoing Inter-RAT
Handover for Cell

BSC6900 UMTS

Description
67192664 VS.IRATHO.AttRe Number of Enhanced Earlier than

locOutPS PS Outgoing Inter- V900R011
RAT Handover
Attempts for Cell

cRelocOutPS Successful Enhanced V900R011
PS Outgoing Inter-
RAT Handovers for
Cell

elocPrepOutPS.TA Preparations for V900R011
lExp Enhanced PS
Outgoing Inter-RAT
Handover for Cell
(TRELOCalloc
expiry)

elocPrepOutPS.Tgt Preparations for V900R011
Fail Enhanced PS
Outgoing Inter-RAT
Handover for Cell
(Relocation Failure
in Target CN/RNC or
Target System)

elocPrepOutPS.Re- Preparations for V900R011
loUnSupp Enhanced PS
Outgoing Inter-RAT
Handover for Cell
(Relocation not
supported in Target
RNC or Target
system)

elocPrepOutPS.Tgt Preparations for V900R011
HighLoad Enhanced PS
Outgoing Inter-RAT
Handover for Cell
Target Cell Higher
Than In The Source
Cell)

BSC6900 UMTS

Description

elocPrepOutPS.No Preparations for V900R011
ResAvail Enhanced PS
Outgoing Inter-RAT
Handover for Cell
(No Resource
Available)

elocPrepOutPS.Un- Preparations for V900R011
KnowRNC Enhanced PS
Outgoing Inter-RAT
Handover for Cell
(Unknown Target
RNC)

elocOutPS.CfgUn- Enhanced PS V900R011
Supp Outgoing Inter-RAT
Handovers for Cell
(Configuration
Unsupported)

elocOutPS.PhyCh- Enhanced PS V900R011
Fail Outgoing Inter-RAT
Handovers for Cell
(Physical Channel
Failure)
67192674 VS.IRATHO.FailR Number of Times Earlier than

elocOutPS.NoRe- that the Timer V900R011
ply Waiting for Iu
Release Command
Expires in Enhanced
PS Outgoing Inter-
RAT Handover for
Cell

locPrepInPS Preparations for V900R011
Enhanced PS
Incoming Inter-RAT
Handover for Cell

BSC6900 UMTS

Description

cRelocPrepInPS Successful V900R011
Preparations for
Enhanced PS
Incoming Inter-RAT
Handover for Cell

cRelocInPS Successful Enhanced V900R011
PS Incoming Inter-
RAT Handovers for
Cell

elocPrepInPS.TgtF Preparations for V900R011
ail Enhanced PS
Incoming Inter-RAT
Handover for cell
(Relocation failure in
target CN/RNC or
target system)

elocPrepInPS.Re- Preparations for V900R011
loUnSupp Enhanced PS
Incoming Inter-RAT
Handover for cell
(Relocation not
supported in target
RNC or target
system)

elocPrepInPS.Re- Preparations for V900R011
sUnavail Enhanced PS
Incoming Inter-RAT
Handover for cell
(No resource
available)

elocPrepInPS.TgtH Preparations for V900R011
ighLoad Enhanced PS
Incoming Inter-RAT
Handover for cell
Target Cell Higher
Than In The Source
Cell)

BSC6900 UMTS

Description

elocInPS.NoReply Enhanced PS V900R011
Incoming Inter-RAT
Handovers Due to
UE Response
Timeout for Cell
67193399 VS.IRATHO.OutC Number of CS Inter- Earlier than

S.MeasTimeOut RAT Measurement V900R011
Expiry for Cell
67193400 VS.IRATHO.OutP Number of PS Inter- Earlier than

S.MeasTimeOut RAT Measurement V900R011
Expiry for Cell
67193405 VS.IRATHO.AttO Number of CS Inter- Earlier than

utCS.TrigRscp RAT Handover V900R011
Attempts Based on
RSCP for Cell
67193406 VS.IRATHO.AttO Number of CS Inter- Earlier than

utCS.TrigEcNo RAT Handover V900R011
Attempts Based on
EcNo for Cell
67193407 VS.IRATHO.AttO Number of PS Inter- Earlier than

utPS.TrigRscp RAT Handover V900R011
Attempts Based on
RSCP for Cell
67193408 VS.IRATHO.AttO Number of PS Inter- Earlier than

utPS.TrigEcNo RAT Handover V900R011
Attempts Based on
EcNo for Cell

utCS.MBDR Outgoing Inter-RAT V900R011
Handover Attempts
Based on
Measurement for
Cell

OutCS.MBDR Successful CS V900R011
Outgoing Inter-RAT
Handovers Based on
Measurement for
Cell

BSC6900 UMTS

Description
73393922 VS.IRATHO.AttO Number of CS Inter- V900R012

utCS.TrigULTxp RAT Handover
Attempts Based on
UL Transmit Power
of UE for Cell
73393923 VS.IRATHO.AttO Number of CS Inter- V900R012

utCS.TrigDLTxp RAT Handover
Attempts Based on
DL Code Power for
Cell
73393924 VS.IRATHO.AttO Number of PS Inter- V900R012

utPS.TrigULTxp RAT Handover
Attempts Based on
UL Transmit Power
of UE for Cell
73393925 VS.IRATHO.AttO Number of PS Inter- V900R012

utPS.TrigDLTxp RAT Handover
Attempts Based on
DL Code Power for
Cell
73393926 VS.IRATHO.Succ Number of V900R012

OutCS.TrigRscp Successful CS Inter-
RAT Handovers
Based on RSCP for
Cell

OutCS.TrigEcNo Successful CS Inter-
RAT Handovers
Based on EcNo for
Cell

OutCS.TrigULTxp Successful CS Inter-
RAT Handovers
Based on UL
Transmit Power of
UE for Cell

OutCS.TrigDLTxp Successful CS Inter-
RAT Handovers
Based on DL Code
Power for Cell

BSC6900 UMTS

Description

OutPS.TrigRscp Successful PS Inter-
RAT Handovers
Based on RSCP for
Cell

OutPS.TrigEcNo Successful PS Inter-
RAT Handovers
Based on EcNo for
Cell

OutPS.TrigULTxp Successful PS Inter-
RAT Handovers
Based on UL
Transmit Power of
UE for Cell

OutPS.TrigDLTxp Successful PS Inter-
RAT Handovers
Based on DL Code
Power for Cell
73394014 VS.IRATHO.At- Number of CS V900R012

tInCS Incoming Inter-RAT
Handover Attempts
for Cell
73394015 VS.IRATHO.FailR Number of Failed CS V900R012

elocPrepOutCS.Ca Outgoing Inter-RAT
ncel Handover
Preparations for Cell
(Relocation
Cancelled)

elocPrepOutCS.CN Outgoing Inter-RAT
NoReply Handover
(Relocation
Command Wait
Timeout)

BSC6900 UMTS

Description
73394017 VS.IRATHO.FailR Number of CS V900R012

elocPrepInCS.Abor Incoming Inter-RAT
t Handover
Preparation Failures
for Cell (Iu
RELEASE
COMMAND
Received)
73394018 VS.IRATHO.FailO Number of V900R012

utCS.Abort Abnormally
Terminated CS
Outgoing Inter-RAT
Handovers for Cell
73394019 VS.IRATHO.FailR Number of CS V900R012

elocPrepOutCS.Ab Outgoing Inter-RAT
ort Handover
Preparation Failures
for Cell (Iu
RELEASE
COMMAND
Received)

elocPrepOutCS.Re- Outgoing Inter-RAT
qInfoNotAvail Handover
(Requested
Information Not
Available)
73394021 VS.IRATHO.Fail- Number of Failed PS V900R012

OutPS Outgoing Inter-RAT
Handovers Initiated
by the RNC for Cell
73394022 VS.IRATHO.FailO Number of V900R012

utPS.Abort Abnormally
Terminated PS
Outgoing Inter-RAT
Handovers for Cell
73423107 VS.IRATHO.FailO Number of Failed V900R013

utPS.UEGen Outgoing UMTS-to-
GSM PS Handovers
due to UE
Reselection Back to a
UTRAN Cell

BSC6900 UMTS

Description
73423288 VS.SRVCC.U2GE Number of Outgoing V900R013

RAN.AttRelocPre- Inter-RAT PS
pOutPS Handover
Preparation
Attempts Triggered
by SRVCC for VoIP
Services for Cell
73423289 VS.SRVCC.U2GE Number of V900R013

RAN.SuccReloc- Successful Outgoing
PrepOutPS Inter-RAT PS
Handover
Preparations
Triggered by
SRVCC for VoIP
Services for Cell
73423290 VS.SRVCC.U2GE Number of V900R013

RAN.SuccRelo- Successful Outgoing
cOutPS Inter-RAT PS
Handovers Triggered
by SRVCC for VoIP
Services for Cell
73425007 VS.IRATHO.FailO Number of Failed CS V900R014

utCS.SCRI Outgoing Inter-RAT
Handovers for Cell
(Signalling
Connection Release
Indication)
73425008 VS.IRATHO.FailO Number of Failed PS V900R014

utPSUTRAN.SCRI Outgoing Inter-RAT
Handovers for Cell
(Signalling
Connection Release
Indication)

utPSUTRAN.NoSR Outgoing Inter-RAT
NSDataForwardC Handovers for Cell
md (No SRNS DATA
Forward cmd)
73425010 VS.IRATHO.AttO Number of PS V900R014

utPSUTRAN.Sig Outgoing Inter-RAT
Handover Attempts
When only Signaling
Exists for Cell

BSC6900 UMTS

Description

OutPSUTRAN.Sig Successful PS
Outgoing Inter-RAT
Handovers When
only Signaling Exists
for Cell
73425012 VS.IRATHO.FailO Number of Failed CS V900R014

utCS.InterRatRF Outgoing Inter-RAT
Handovers for Cell

utPSUTRAN.Inter- Outgoing Inter-RAT
RatRF Handovers for Cell
73425926 VS.IRATHOCS.Ca Number of RL V900R015

ncel.ReEstab Reestablishment
Attempts After UEs
Failed to Receive the
CS Outgoing Inter-
RAT Handover
Command for Cell
73425927 VS.IRATHOPS.Ca Number of RL V900R015

ncel.ReEstab Reestablishment
Attempts After UEs
Failed to Receive the
PS Outgoing Inter-
RAT Handover
Command for Cell
73425954 VS.IRATHO.Att- Number of Attempts V900R015

NACC to Obtain GSM
System Information
during RIM-based
NACCs Triggered by
Inter-RAT PS
Handovers for Cell

BSC6900 UMTS

Description
73425955 VS.IRATHO.Succ- Number of V900R015

NACC Successful That
GSM System
Information Is
Obtained during
RIM-based NACCs
Triggered by Inter-
RAT PS Handovers
for Cell
73425956 VS.IRATHO.AttE- Number of Attempts V900R015

NACC to Obtain GSM
System Information
During Iur-g-based
ENACCs Triggered
by Inter-RAT PS
Handovers for Cell

ENACC Successful Times
That GSM System
Information is
Obtained During Iur-
g-based ENACCs
Triggered by Inter-
RAT PS Handovers
for Cell
73426146 VS.L2U.AttRelocP Number of Attempts V900R015

repInPS.CS.CELL at Incoming PS LTE-
to-UMTS Handovers
Triggered by CSFB
for Cell

InPS.CS.CELL Successful Incoming
PS LTE-to-UMTS
Handovers Triggered
by CSFB for Cell

PrepInPS.CS.CEL Successful
L Preparations for
Incoming PS LTE-
to-UMTS Handovers
Triggered by CSFB
for Cell

BSC6900 UMTS

Description
73425820 VS.SRVCC.L2U.At Number of V900R015

tRelocPrepInCSPS Preparation
Attempts for
Incoming LTE-to-
UMTS CS+PS
Handovers Triggered
by SRVCC for VoIP
Services for Cell
73425821 VS.SRVCC.L2U.S Number of V900R015

uccRelocPre- Successful
pInCSPS Preparations for
Incoming LTE-to-
UMTS CS+PS
Handovers Triggered
by SRVCC for VoIP
Services for Cell
73425822 VS.SRVCC.L2U.At Number of Incoming V900R015

tInCSPS LTE-to-UMTS CS
+PS Handover
Attempts Triggered
by SRVCC for VoIP
Services for Cell
73425823 VS.SRVCC.L2U.S Number of V900R015

uccInCSPS Successful Incoming
LTE-to-UMTS CS
+PS Handovers
Triggered by
SRVCC for VoIP
Services for Cell
Counter Sub Counter
IRATHO.SuccOutCS VS.IRATHO.SuccOutCS.DR
VS.IRATHO.SuccOutCS.Load
VS.IRATHO.SuccOutCS.RF
VS.IRATHO.SuccOutCS.Service
VS.IRATHO.SuccOutCS.MBDR

BSC6900 UMTS
Counter Sub Counter
IRATHO.AttRelocPrepOutCS VS.IRATHO.AttRelocPrepOutCS.DR
VS.IRATHO.AttRelocPrepOutCS.Load
VS.IRATHO.AttRelocPrepOutCS.RF
VS.IRATHO.AttRelocPrepOutCS.Service
IRATHO.SuccRelocPrepOutCS VS.IRATHO.SuccRelocPrepOutCS.DR
VS.IRATHO.SuccRelocPrepOutCS.Load
VS.IRATHO.SuccRelocPrepOutCS.RF
VS.IRATHO.SuccRelocPrepOutCS.Service
IRATHO.AttOutPSUTRAN VS.IRATHO.AttOutPSUTRAN.Load
VS.IRATHO.AttOutPSUTRAN.RF
VS.IRATHO.AttOutPSUTRAN.Service
IRATHO.SuccOutPSUTRAN VS.IRATHO.SuccOutPSUTRAN.Load
VS.IRATHO.SuccOutPSUTRAN.RF
VS.IRATHO.SuccOutPSUTRAN.Service
VS.IRATHO.AttRelocPrepOutPS VS.SRVCC.U2GERAN.AttRelocPre-
pOutPS
VS.IRATHO.SuccRelocPrepOutPS VS.SRVCC.U2GERAN.SuccRelocPre-
pOutPS
VS.IRATHO.SuccRelocOutPS VS.SRVCC.U2GERAN.SuccRelocOutPS
1.12.14.1 Number of Preparations for CS or Enhanced PS Outgoing Inter-RAT

Handover for Cell
Counters
67189730 VS.IRATHO.AttRelocPrep Number of Preparation

OutCS.DR Attempts for CS Outgoing
on Directed Retry for Cell

OutCS.Load Attempts for CS Outgoing
Inter-RAT Handover
Initiated by UTRAN Based
on Load for Cell

BSC6900 UMTS

OutCS.RF Attempts for CS Outgoing
on RF (Coverage, QoS, or
HCS) for Cell
67189749 IRATHO.AttRelocPre- Number of Preparation

pOutCS Attempts for CS Outgoing
Inter-RAT Handover for Cell

OutCS.Service Attempts for CS Outgoing
on Service Type for Cell
67192654 VS.IRATHO.AttRelocPrep Number of Preparations for

OutCS.Sig CS Outgoing Inter-RAT
Handover When only
67192662 VS.IRATHO.AttRelocPre- Number of Preparations for

pOutPS Enhanced PS Outgoing Inter-
RAT Handover for Cell
67196299 VS.IRATHO.AttOutCS.MB Number of CS Outgoing

DR Inter-RAT Handover
Attempts Based on
Measurement for Cell
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 .

BSC6900 UMTS
Figure 1-608 Normal CS or Enhanced PS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
VS.IRATHO.AttRelocPrep WRFD-02040002 Inter System Direct Retry

OutCS.DR

OutCS.Load on Load

OutCS.RF on Coverage

BSC6900 UMTS
IRATHO.AttRelocPre- WRFD-02040002 Inter System Direct Retry

pOutCS WRFD-020303 Inter-RAT Handover Based

on Service
on Load

OutCS.Service on Service

OutCS.Sig WRFD-020305 on Coverage

on Service
on Load
VS.IRATHO.AttRelocPre- WRFD-02030802 PS Handover Between

pOutPS UMTS and GPRS
VS.IRATHO.AttOutCS.MB WRFD-02040002 Inter System Direct Retry

DR WRFD-020402 Measurement Based Direct
Retry
1.12.14.2 Number of Outgoing Inter-RAT PS Handover Preparation Attempts

Triggered by SRVCC for VoIP Services for Cell
Counters
73423288 VS.SRVCC.U2GERAN.At- Number of Outgoing Inter-

tRelocPrepOutPS RAT PS Handover
Preparation Attempts
Triggered by SRVCC for
VoIP Services for Cell
Description
This counter provides the number of outgoing inter-RAT PS handover preparation attempts
triggered by Single Radio Voice Call Continuity (SRVCC) for VoIP services in the best cell that
the UE camps on. After SRVCC is enabled, a VoIP service carried on HSPA is processed as a
PS service at the UTRAN and as a CS service at the GERAN during the UTRAN-to-GERAN
handover to ensure the speech continuity.

BSC6900 UMTS
Measurement point
The measurement is triggered at point A shown in the figure. When the RNC sends the CN a
RELOCATION REQUIRED message during the SRVCC-triggered inter-RAT PS handover for
a VoIP service, this counter is measured in the best cell that the UE camps on.
Figure 1-609 VS.SRVCC.U2GERAN.AttRelocPrepOutPS
Formula
None
Unit
None
Related Features
VS.SRVCC.U2GERAN.At- WRFD-02030802 PS Handover Between

tRelocPrepOutPS UMTS and GPRS
1.12.14.3 Number of Successful Preparations for CS or Enhanced PS Outgoing Inter-


BSC6900 UMTS
Counters

pOutCS.DR Preparations for CS
Outgoing Inter-RAT
Handover Based on Directed
Retry for Cell

pOutCS.Load Preparations for CS
Outgoing Inter-RAT
Handover Initiated by
UTRAN Based on Load for
Cell

pOutCS.RF Preparations for CS
Outgoing Inter-RAT
Handover Based on RF
(Coverage, QoS, or HCS) for
Cell
67189750 IRATHO.SuccRelocPre- Number of Successful

pOutCS Preparations for CS
Outgoing Inter-RAT
Handover for Cell

pOutCS.Service Preparations for CS
Outgoing Inter-RAT
Handover Based on Service
Type for Cell

pOutCS.Sig Preparations for CS
Outgoing Inter-RAT
Handover When only
67192663 VS.IRATHO.SuccRelocPre- Number of Successful

pOutPS Preparations for Enhanced
PS Outgoing Inter-RAT
Handover for Cell
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.

BSC6900 UMTS
Measurement point
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
VS.IRATHO.SuccRelocPre WRFD-02040002 Inter System Direct Retry

pOutCS.DR

pOutCS.Load on Load

pOutCS.RF on Coverage

BSC6900 UMTS
IRATHO.SuccRelocPre- WRFD-02040002 Inter System Direct Retry

pOutCS WRFD-020303 Inter-RAT Handover Based

on Service
on Load

pOutCS.Service on Service

pOutCS.Sig WRFD-020305 on Coverage

on Service
on Load
VS.IRATHO.SuccRelocPre- WRFD-02030802 PS Handover Between

pOutPS UMTS and GPRS
1.12.14.4 Number of Successful Outgoing Inter-RAT PS Handover Preparations

Triggered by SRVCC for VoIP Services for Cell
Counters
73423289 VS.SRVCC.U2GERAN.Suc Number of Successful

cRelocPrepOutPS Outgoing Inter-RAT PS
Handover Preparations
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.

BSC6900 UMTS
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.
Figure 1-611 VS.SRVCC.U2GERAN.SuccRelocPrepOutPS
Formula
None
Unit
None
Related Features
VS.SRVCC.U2GERAN.Suc WRFD-02030802 PS Handover Between

cRelocPrepOutPS UMTS and GPRS
1.12.14.5 Number of CS or Enhanced PS Outgoing Inter-RAT Handover Attempts

for Cell

BSC6900 UMTS
Counters
67189754 IRATHO.AttOutCS Number of CS Outgoing

Inter-RAT Handover
Attempts
67192656 VS.IRATHO.AttOutCS.Sig Number of CS Outgoing

Inter-RAT Handover
Attempts When only
67192664 VS.IRATHO.AttRelo- Number of Enhanced PS

cOutPS Outgoing Inter-RAT
Handover Attempts for Cell
67193405 VS.IRATHO.AttOutCS.Trig Number of CS Inter-RAT

Rscp Handover Attempts Based on
RSCP for Cell
67193406 VS.IRATHO.AttOutCS.Tri- Number of CS Inter-RAT

gEcNo Handover Attempts Based on
EcNo for Cell
73393922 VS.IRATHO.AttOutCS.Tri- Number of CS Inter-RAT

gULTxp Handover Attempts Based on
UL Transmit Power of UE
for Cell
73393923 VS.IRATHO.AttOutCS.Trig Number of CS Inter-RAT

DLTxp Handover Attempts Based on
DL Code Power for Cell
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
IRATHO.AttOutCS WRFD-02040002 Inter System Direct Retry


on Service
on Load

BSC6900 UMTS
VS.IRATHO.AttOutCS.Sig WRFD-020303 Inter-RAT Handover Based


on Service
on Load
VS.IRATHO.AttRelo- WRFD-02030802 PS Handover Between

cOutPS UMTS and GPRS
VS.IRATHO.AttOutCS.Trig WRFD-020303 Inter-RAT Handover Based

Rscp on Coverage
VS.IRATHO.AttOutCS.Tri- WRFD-020303 Inter-RAT Handover Based

gEcNo on Coverage
VS.IRATHO.AttOutCS.Tri- WRFD-020309 Inter-RAT Handover Based

gULTxp on DL QoS
VS.IRATHO.AttOutCS.Trig WRFD-020309 Inter-RAT Handover Based

DLTxp on DL QoS
1.12.14.6 Number of Successful CS or Enhanced PS Outgoing Inter-RAT Handovers

for Cell
Counters
67189729 VS.IRATHO.SuccOutCS.D Number of Successful CS

R Outgoing Inter-RAT
Handovers Based on
Directed Retry for Cell
67189741 VS.IRATHO.SuccOutCS.L Number of Successful CS

oad Outgoing Inter-RAT
Handovers Based on Load
for Cell
67189746 VS.IRATHO.SuccOutCS.R Number of Successful CS

F Outgoing Inter-RAT
Handovers Based on RF
Cell
67189755 IRATHO.SuccOutCS Number of Successful CS

Outgoing Inter-RAT
Handovers for Cell

BSC6900 UMTS
67190857 VS.IRATHO.SuccOutCS.Se Number of Successful CS

rvice Outgoing Inter-RAT
Handovers Based on Service
Type for Cell
67192657 VS.IRATHO.SuccOutCS.Si Number of Successful CS

g Outgoing Inter-RAT
Handovers When only
67192665 VS.IRATHO.SuccRelo- Number of Successful

cOutPS Enhanced PS Outgoing Inter-
RAT Handovers for Cell
67196300 VS.IRATHO.SuccOutCS.M Number of Successful CS

BDR Outgoing Inter-RAT
Handovers Based on
Measurement for Cell
73393926 VS.IRATHO.SuccOutCS.Tr Number of Successful CS

igRscp Inter-RAT Handovers Based
on RSCP for Cell

igEcNo Inter-RAT Handovers Based
on EcNo for Cell

igULTxp Inter-RAT Handovers Based
on UL Transmit Power of UE
for Cell

igDLTxp Inter-RAT Handovers Based
on DL Code Power for Cell
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
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.

BSC6900 UMTS
Figure 1-613 Normal CS or the Enhanced PS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
VS.IRATHO.SuccOutCS.D WRFD-02040002 Inter System Direct Retry

R
VS.IRATHO.SuccOutCS.L WRFD-020306 Inter-RAT Handover Based

oad on Load
VS.IRATHO.SuccOutCS.R WRFD-020303 Inter-RAT Handover Based

F on Coverage

BSC6900 UMTS
IRATHO.SuccOutCS WRFD-02040002 Inter System Direct Retry


on Service
on Load
VS.IRATHO.SuccOutCS.Se WRFD-020305 Inter-RAT Handover Based

rvice on Service
VS.IRATHO.SuccOutCS.Si WRFD-020303 Inter-RAT Handover Based

g WRFD-020305 on Coverage

on Service
on Load
VS.IRATHO.SuccRelo- WRFD-02030802 PS Handover Between

cOutPS UMTS and GPRS
VS.IRATHO.SuccOutCS.M WRFD-02040002 Inter System Direct Retry

BDR WRFD-020402 Measurement Based Direct
Retry
VS.IRATHO.SuccOutCS.Tr WRFD-020303 Inter-RAT Handover Based

igRscp on Coverage

igEcNo on Coverage

igULTxp on DL QoS

igDLTxp on DL QoS
1.12.14.7 Number of Successful Outgoing Inter-RAT PS Handovers Triggered by

SRVCC for VoIP Services for Cell

BSC6900 UMTS
Counters
73423290 VS.SRVCC.U2GERAN.Suc Number of Successful

cRelocOutPS Outgoing Inter-RAT PS
Handovers Triggered by
SRVCC for VoIP Services
for Cell
Description
This counter provides the number of successful outgoing inter-RAT PS handovers triggered by
Single Radio Voice Call Continuity (SRVCC) for VoIP services in the best cell that the UE
camps on. After SRVCC is enabled, a VoIP service carried on HSPA is processed as a PS service
at the UTRAN and as a CS service at the GERAN during the UTRAN-to-GERAN handover to
ensure the speech continuity.
Measurement point
The measurement is triggered at point D shown in the figure. When the RNC receives an IU
COMMAND message during the SRVCC-triggered inter-RAT PS handover for a VoIP service,
the handover succeeds and this counter is measured in the best cell that the UE camps on under
the SRNC before the handover.
Figure 1-614 VS.SRVCC.U2GERAN.SuccRelocOutPS

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SRVCC.U2GERAN.Suc WRFD-02030802 PS Handover Between

cRelocOutPS UMTS and GPRS
1.12.14.8 Number of Failed Preparations for CS or Enhanced PS Outgoing Inter-

RAT Handover for Different Causes for Cell
Counters
67189751 IRATHO.FailRelocPrepOut Number of Failed

CS.TAlExp Preparations for CS
Outgoing Inter-RAT
Handover for Cell
(TRELOCalloc expiry)

CS.TgtFail Preparations for CS
Outgoing Inter-RAT
Handover for Cell

CS.ReloNoSup Preparations for CS
Outgoing Inter-RAT
Handover for Cell
(Relocation not supported in
system)

BSC6900 UMTS

CS.HigherTrafficLod Preparations for CS
Outgoing Inter-RAT
Handover for Cell (Traffic
Load In The Target Cell
Higher Than In The Source
Cell)

CS.NoResAvail Preparations for CS
Outgoing Inter-RAT
Handover for Cell (No
Resource Available)

CS.UKnowRNC Preparations for CS
Outgoing Inter-RAT
Handover for Cell (Unknown
Target RNC)
67192666 VS.IRATHO.FailRelocPrep Number of Failed

OutPS.TAlExp Preparations for Enhanced
Handover for Cell
(TRELOCalloc expiry)

OutPS.TgtFail Preparations for Enhanced
Handover for Cell

OutPS.ReloUnSupp Preparations for Enhanced
Handover for Cell
system)

OutPS.TgtHighLoad Preparations for Enhanced
Handover for Cell (Traffic
Cell)

BSC6900 UMTS

OutPS.NoResAvail Preparations for Enhanced
Handover for Cell (No
Resource Available)

OutPS.UnKnowRNC Preparations for Enhanced
Handover for Cell (Unknown
Target RNC)
73394015 VS.IRATHO.FailRelocPrep Number of Failed CS

OutCS.Cancel Outgoing Inter-RAT
Handover Preparations for
Cell (Relocation Cancelled)

OutCS.ReqInfoNotAvail Outgoing Inter-RAT
Cell (Requested Information
Not Available)
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 CN a RELOCATION PREPARATION FAILURE message after sending the CN a
RELOCATION REQUIRED message during the CS or the Enhanced PS outgoing inter-RAT
camps on based on the cause value.

BSC6900 UMTS
Figure 1-615 Failed relocation preparation for SRNC
Formula
None
Unit
None
Related Features
IRATHO.FailRelocPrepOut WRFD-02040002 Inter System Direct Retry

CS.TAlExp WRFD-020303 Inter-RAT Handover Based

on Service
on Load

BSC6900 UMTS

CS.TgtFail WRFD-020303 Inter-RAT Handover Based

on Service
on Load

CS.ReloNoSup WRFD-020303 Inter-RAT Handover Based

on Service
on Load

CS.HigherTrafficLod WRFD-020303 Inter-RAT Handover Based

on Service
on Load

CS.NoResAvail WRFD-020303 Inter-RAT Handover Based

on Service
on Load

CS.UKnowRNC WRFD-020303 Inter-RAT Handover Based

on Service
on Load
VS.IRATHO.FailRelocPrep WRFD-02030802 PS Handover Between

OutPS.TAlExp UMTS and GPRS

OutPS.TgtFail UMTS and GPRS

BSC6900 UMTS

OutPS.ReloUnSupp UMTS and GPRS

OutPS.TgtHighLoad UMTS and GPRS

OutPS.NoResAvail UMTS and GPRS

OutPS.UnKnowRNC UMTS and GPRS
VS.IRATHO.FailRelocPrep WRFD-020303 Inter-RAT Handover Based

OutCS.Cancel WRFD-020305 on Coverage

on Service
on Load

OutCS.ReqInfoNotAvail WRFD-020305 on Coverage

on Service
on Load
1.12.14.9 Number of Failed CS Outgoing Inter-RAT Handover Preparations

(Relocation Command Wait Timeout) for Cell
Counters

OutCS.CNNoReply Outgoing Inter-RAT
Cell (Relocation Command
Wait Timeout)
Description
This counter provides the number of times that the CS outgoing inter-RAT handover preparation
fails in the best cell because the timer waiting for the relocation command expires.

BSC6900 UMTS
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-616 SRNC relocation preparation failure due to expiry of relocation command
Formula
None
Unit
None
Related Features

OutCS.CNNoReply WRFD-020305 on Coverage

on Service
on Load

BSC6900 UMTS
1.12.14.10 Number of CS Incoming Inter-RAT Handover Preparation Failures (Iu

RELEASE COMMAND Received) for Cell
Counters
73394017 VS.IRATHO.FailRelocPrep Number of CS Incoming

InCS.Abort Inter-RAT Handover
Preparation Failures for Cell
(Iu RELEASE COMMAND
Received)
Description
This counter provides the number of times that the CS incoming inter-RAT handover preparation
fails because an IU RELEASE COMMAND message is received according to the target cell ID
in the relocation request.
Measurement point
The measurement is triggered at point A as shown in the figure. After the CN sends a
RELOCATION REQUEST message to the RNC during the CS incoming inter-RAT handover,
this counter is measured according to the value of TargetCellId in the RELOCATION
REQUEST message if the RNC receives an IU RELEASE COMMAND message.
Figure 1-617 CS domain inter-RAT incoming handover preparation

BSC6900 UMTS
Formula
None
Unit
None
Related Features

InCS.Abort WRFD-020305 on Coverage

on Service
on Load
1.12.14.11 Number of CS Outgoing Inter-RAT Handover Preparation Failures (Iu

RELEASE COMMAND Received) for Cell
Counters
73394019 VS.IRATHO.FailRelocPrep Number of CS Outgoing

OutCS.Abort Inter-RAT Handover
Preparation Failures for Cell
(Iu RELEASE COMMAND
Received)
Description
This counter provides the number of times that the CS outgoing inter-RAT handover preparation
fails in the best cell because an IU RELEASE COMMAND message is received.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives an IU
RELEASE COMMAND command after sending the CN a RELOCATION REQUIRED
message during the CS outgoing inter-RAT handover.

BSC6900 UMTS
Figure 1-618 RNC-initiated CS domain inter-RAT outgoing handover procedure (failed

operation due to termination)
Formula
None
Unit
None
Related Features

OutCS.Abort WRFD-020305 on Coverage

on Service
on Load
1.12.14.12 Number of Failed CS or Enhanced PS Outgoing Inter-RAT Handovers

for Different Causes for Cell

BSC6900 UMTS
Counters
67189756 IRATHO.FailOutCS.CfgUn Number of Failed CS

supp Outgoing Inter-RAT
Handovers for Cell
(Configuration
Unsupported)
67189757 IRATHO.FailOutCS.PhyCh Number of Failed CS

Fail Outgoing Inter-RAT
Channel Failure)
67192672 VS.IRATHO.FailRelocOutP Number of Failed Enhanced

S.CfgUnSupp PS Outgoing Inter-RAT
Handovers for Cell
(Configuration
Unsupported)
67192673 VS.IRATHO.FailRelocOutP Number of Failed Enhanced

S.PhyChFail PS Outgoing Inter-RAT
Channel Failure)
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 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.

BSC6900 UMTS
Figure 1-619 Failed CS or the Enhanced PS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
IRATHO.FailOutCS.CfgUn WRFD-02040002 Inter System Direct Retry

supp WRFD-020303 Inter-RAT Handover Based

on Service
on Load

BSC6900 UMTS
IRATHO.FailOutCS.PhyCh WRFD-02040002 Inter System Direct Retry

Fail WRFD-020303 Inter-RAT Handover Based

on Service
on Load
VS.IRATHO.FailRelocOutP WRFD-02030802 PS Handover Between

S.CfgUnSupp UMTS and GPRS

S.PhyChFail UMTS and GPRS
1.12.14.13 Number of Failed CS Outgoing Inter-RAT Handovers for Cell(Signalling

Connection Release Indication)
Counters
73425007 VS.IRATHO.FailOutCS.SC Number of Failed CS

RI Outgoing Inter-RAT
Handovers for Cell
(Signalling Connection
Release Indication)
Description
This counter provides the number of the CS outgoing inter-RAT handover fails in the best cell
because the RNC receives SIGNALLING CONNECTION RELEASE INDICATION from the
UE.
Measurement point
The measurement is triggered at point A as shown in the figure.During the CS outgoing 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.

BSC6900 UMTS
Figure 1-620 Procedure for a failed outgoing inter-RAT handover in the CS domain
Formula
None
Unit
None
Related Features
VS.IRATHO.FailOutCS.SC WRFD-020303 Inter-RAT Handover Based

RI WRFD-020305 on Coverage

on Service
on Load
1.12.14.14 Number of RL Reestablishment Attempts After UEs Failed to Receive

the CS Outgoing Inter-RAT Handover Command for Cell

BSC6900 UMTS
Counters
73425926 VS.IRATHOCS.Cancel.Re- Number of RL

Estab Reestablishment Attempts
After UEs Failed to Receive
the CS Outgoing Inter-RAT
Handover Command for Cell
Description
This counter measures the number of radio link (RL) reestablishment attempts in the best cell
when a UE fails to receive a HANDOVER FROM UTRAN COMMAND message from the
RNC during a CS outgoing inter-RAT handover.
Measurement point
The measurement is triggered at point A shown in the figure when both of the following
conditions are met:
The RNC has sent a HANDOVER FROM UTRAN COMMAND message to the UE, but fails
to receive an ACK message from the UE.
The RNC receives a CELL UPDATE message from the UE and attempts to reestablish the RL
for the UE.
In this case, the counter is measured in the best cell that the UE camps on under the SRNC.
Figure 1-621 RL reestablishment during a CS or enhanced PS outgoing inter-RAT handover

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHOCS.Cancel.Re- WRFD-020303 Inter-RAT Handover Based

Estab WRFD-020306 on Coverage

on Load
on Service
1.12.14.15 Number of Times that the Timer Waiting for Iu Release Command
Expires in CS or Enhanced PS Outgoing Inter-RAT Handover for Cell
Counters
67192660 VS.IRATHO.FailOutCS.No Number of Times that the

Reply Timer Waiting for Iu Release
Command Expires in CS
Outgoing Inter-RAT
Handover for Cell
67192674 VS.IRATHO.FailRelocOutP Number of Times that the

S.NoReply Timer Waiting for Iu Release
Command Expires in
Enhanced PS Outgoing Inter-
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

BSC6900 UMTS
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-622 Timeout Waiting for Iu Release Command in CS or the Enhanced PS Outgoing
Inter-RAT Handover
Formula
None
Unit
None
Related Features
VS.IRATHO.FailOutCS.No WRFD-02040002 Inter System Direct Retry

Reply WRFD-020303 Inter-RAT Handover Based

on Service
on Load

BSC6900 UMTS

S.NoReply UMTS and GPRS
1.12.14.16 Number of Failed CS Outgoing Inter-RAT Handovers for Cell(Failure in

the Radio Interface Procedure)
Counters
73425012 VS.IRATHO.FailOutCS.In- Number of Failed CS

terRatRF Outgoing Inter-RAT
Handovers for Cell(Failure in
the Radio Interface
Procedure)
Description
This counter provides the number of IU RELEASE COMMAND messages that are received by
the RNC from the CN after the RNC sends HANDOVER FROM UTRAN COMMAND
messages to the UE and that contain the reason value "Failure in the Radio Interface Procedure."
This counter is measured in a CS inter-RAT handover and in the best cell before the handover.
Measurement point
The measurement is triggered at point D as shown in the figure.When the RNC receives a IU
RELEASE COMMAND message,If the IU RELEASE COMMAND message indicate the
reason"Failure in the Radio Interface Procedure",this counter is increased by one in the best cell
that the UE camps on before the handover.

BSC6900 UMTS
Figure 1-623 Procedure for an outgoing inter-RAT handover in the CS domain
Formula
None
Unit
None
Related Features
VS.IRATHO.FailOutCS.In- WRFD-020303 Inter-RAT Handover Based

terRatRF WRFD-020305 on Coverage

on Service
on Load
1.12.14.17 Number of Abnormally Terminated CS Outgoing Inter-RAT Handovers

for Cell

BSC6900 UMTS
Counters
73394018 VS.IRATHO.FailOutCS.Ab Number of Abnormally

ort Terminated CS Outgoing
Inter-RAT Handovers for
Cell
Description
This counter provides the number of times that the CS outgoing inter-RAT handover fails in the
best cell because an IU RELEASE COMMAND message with a cause value of abnormal release,
that is, a cause value except "Successful Relocation", "Normal Release", or "Network
Optimization", is received.
Measurement point
RELEASE COMMAND message with the cause value except "Successful Relocation", "Normal
COMMAND message. In this case, this counter is measured in the SRNC best cell that the UE
camps on before the handover.
Figure 1-624 CS domain inter-RAT outgoing handover procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.FailOutCS.Ab WRFD-020303 Inter-RAT Handover Based

ort WRFD-020305 on Coverage

on Service
on Load
1.12.14.18 Number of Attempts to Obtain GSM System Information During RIM-

based NACCs Triggered by Inter-RAT PS Handovers
Counters
73425954 VS.IRATHO.AttNACC Number of Attempts to

Obtain GSM System
Information during RIM-
based NACCs Triggered by
Inter-RAT PS Handovers for
Cell
Description
This counter provides the number of attempts to obtain GSM system information during RIM-
based NACCs triggered by Inter-RAT PS handovers in the best cell where the UE camps. RIM
is short for RAN information management and NACC is short for network assisted cell change.
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC sends the
CN a DIRECT INFORMATION TRANSFER message which contains RAN INFORMATION
REQUEST to initiate inter-RAT PS handovers. This counter is measured in the best cell under
the SRNC where the UE is currently served.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.AttNACC WRFD-02030801 NACC(Network Assisted

Cell Change)
1.12.14.19 Number of Successful That GSM System Information Is Obtained

During RIM-based NACCs Triggered by Inter-RAT PS Handovers
Counters
73425955 VS.IRATHO.SuccNACC Number of Successful That

GSM System Information Is
Obtained during RIM-based
NACCs Triggered by Inter-
RAT PS Handovers for Cell

BSC6900 UMTS
Description
This counter provides the number of times that GSM system information is successfully obtained
during RIM-based NACCs triggered by Inter-RAT PS handovers to obtain GSM system
information in the best cell where the UE camps. RIM is short for RAN information management
and NACC is short for network assisted cell change.
Measurement point
The measurement is triggered at point B shown in the following figure. After receiving a
DIRECT INFORMATION TRANSFER message containing RAN INFORMATION from the
CN, the RNC initiates inter-RAT PS handovers. This counter is measured in the best cell under
the SRNC where the UE is currently served.
Formula
None
Unit
None
Related Features
VS.IRATHO.SuccNACC WRFD-02030801 NACC(Network Assisted

Cell Change)

BSC6900 UMTS
1.12.14.20 Number of Attempts to Obtain GSM System Information During Iur-g-

based ENACCs Triggered by Inter-RAT PS Handovers
Counters
73425956 VS.IRATHO.AttENACC Number of Attempts to

Obtain GSM System
Information During Iur-g-
based ENACCs Triggered by
Inter-RAT PS Handovers for
Cell
Description
This counter provides the number of attempts to obtain GSM system information during Iur-g-
based ENACCs triggered by Inter-RAT PS handovers in the best cell where the UE camps.
ENACC is short for evolved network assisted cell change.
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC sends the
BSC an INFORMATION EXCHANGE INITIATION REQUEST message which contains
NACC Related Data. This counter is measured in the best cell under the SRNC where the UE
is served.
Figure 1-627 Information exchange procedure between the RNC and BSC
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IRATHO.AttENACC WRFD-070005 NACC Procedure

Optimization Based on Iur-g
1.12.14.21 Number of Successful Times That GSM System Information Is Obtained

During Iur-g-based ENACCs Triggered by Inter-RAT PS Handovers
Counters
73425957 VS.IRATHO.SuccENACC Number of Successful Times

That GSM System
Information is Obtained
During Iur-g-based ENACCs
Triggered by Inter-RAT PS
Handovers for Cell
Description
This counter provides the number of successful times that GSM system information is obtained
during Iur-g-based ENACCs triggered by Inter-RAT PS handovers in the best cell where the
UE camps. ENACC is short for evolved network assisted cell change.
Measurement point
The measurement is triggered at point B shown in the following figure when the RNC receives
an INFORMATION EXCHANGE INITIATION REQUEST message which contains NACC
Related Data from the BSC. This counter is measured in the best cell under the SRNC where
the UE is served.

BSC6900 UMTS
Figure 1-628 Information exchange procedure between the RNC and BSC
Formula
None
Unit
None
Related Features
VS.IRATHO.SuccENACC WRFD-070005 NACC Procedure

Optimization Based on Iur-g
1.12.14.22 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC

for Cell
Counters

AN.Load Inter-RAT Handover
Attempts Initiated by
Cell

BSC6900 UMTS

AN.RF Inter-RAT Handover
Attempts Initiated by the
RNC Based on RF
Cell
67190411 IRATHO.AttOutPSUTRAN Number of PS Outgoing

Inter-RAT Handover
Attempts Initiated by RNC
for Cell

AN.Service Inter-RAT Handover
Attempts Initiated by the
RNC Based on Service Type
for Cell
67191155 VS.IRATHO.HSDPA.At- Number of PS Inter-RAT

tOutPSUTRAN Outgoing Handover
Attempts for HSDPA
Services for Cell
67192507 VS.IRATHO.HSUPA.At- Number of PS Outgoing

tOutPSUTRAN Inter-RAT Handover
Attempts for HSUPA
Services for Cell

AN.Sig Inter-RAT Handover
Attempts When only
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
camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

AN.Load on Load

AN.RF on Coverage
IRATHO.AttOutPSUTRAN WRFD-020303 Inter-RAT Handover Based


on Service
on Load

AN.Service on Service

BSC6900 UMTS
VS.IRATHO.HSDPA.At- WRFD-01061006 HSDPA Mobility

tOutPSUTRAN Management
VS.IRATHO.HSUPA.At- WRFD-01061204 HSUPA Mobility

tOutPSUTRAN Management

AN.Sig WRFD-020305 on Coverage

on Service
on Load
1.12.14.23 Counters Related to the Number of PS Outgoing Inter-RAT Handover

Attempts
Counters
67193407 VS.IRATHO.AttOutPS.Trig Number of PS Inter-RAT

Rscp Handover Attempts Based on
RSCP for Cell
67193408 VS.IRATHO.AttOutPS.Tri- Number of PS Inter-RAT

gEcNo Handover Attempts Based on
EcNo for Cell
73393924 VS.IRATHO.AttOutPS.Tri- Number of PS Inter-RAT

gULTxp Handover Attempts Based on
UL Transmit Power of UE
for Cell
73393925 VS.IRATHO.AttOutPS.Trig Number of PS Inter-RAT

DLTxp Handover Attempts Based on
DL Code Power for Cell
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

BSC6900 UMTS
handover. In this case, the corresponding counter is measured in the best cell that the UE camps
on under the SRNC, based on the handover cause.
Figure 1-630 Handover instruction
The measurement can also be triggered at point C as shown in the figure, when the RNC sends
the UE a HANDOVER FROM UTRAN COMMAND message during the enhanced PS outgoing
inter-RAT handover. In this case, the corresponding counter is measured in the best cell that the
UE camps on under the SRNC, based on the handover cause.

BSC6900 UMTS
Figure 1-631 Handover instruction
Formula
None
Unit
None
Related Features
VS.IRATHO.AttOutPS.Trig WRFD-020303 Inter-RAT Handover Based

Rscp on Coverage
VS.IRATHO.AttOutPS.Tri- WRFD-020303 Inter-RAT Handover Based

gEcNo on Coverage
VS.IRATHO.AttOutPS.Tri- WRFD-020309 Inter-RAT Handover Based

gULTxp on DL QoS
VS.IRATHO.AttOutPS.Trig WRFD-020309 Inter-RAT Handover Based

DLTxp on DL QoS

BSC6900 UMTS

RNC for Cell
Counters

RAN.Load Outgoing Inter-RAT
Handovers Initiated by
Cell

RAN.RF Outgoing Inter-RAT
Handovers Initiated by the
RNC Based on RF
Cell
67190412 IRATHO.SuccOutPSU- Number of Successful PS

for Cell

RAN.Service Outgoing Inter-RAT
RNC Based on Service Type
for Cell
67191156 VS.IRATHO.HSDPA.Suc- Number of Successful PS

cOutPSUTRAN Outgoing Inter-RAT
Handovers for HSDPA
Services for Cell
67192506 VS.IRATHO.HSUPA.Suc- Number of Successful PS

cOutPSUTRAN Outgoing Inter-RAT
Handovers for HSUPA
Services for Cell

RAN.Sig Outgoing Inter-RAT
Handovers When only
Description
These counters provide the number of successful PS outgoing inter-RAT handovers in the best
cell initiated by the RNC due to different causes.

BSC6900 UMTS
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC receives from
the CN an IU RELEASE COMMAND message with the cause value of "Successful Relocation,"
"Normal Release," or "Network Optimization," after sending a CELL CHANGE ORDER
FROM UTRAN message to the UE during an outgoing inter-RAT PS handover. In this case,
the corresponding counter is measured in the best cell that the UE camps on in the SRNC before
the handover based on the cause value.
Formula
None
Unit
None
Related Features

RAN.Load on Load

RAN.RF on Coverage

BSC6900 UMTS
IRATHO.SuccOutPSU- WRFD-020303 Inter-RAT Handover Based

TRAN WRFD-020305 on Coverage

on Service
on Load

RAN.Service on Service
VS.IRATHO.HSDPA.Suc- WRFD-01061006 HSDPA Mobility

cOutPSUTRAN Management
VS.IRATHO.HSUPA.Suc- WRFD-01061204 HSUPA Mobility

cOutPSUTRAN Management

RAN.Sig WRFD-020305 on Coverage

on Service
on Load
1.12.14.25 Counters Related to the Number of Successful PS Outgoing Inter-RAT

Handovers
Counters
73393930 VS.IRATHO.SuccOutPS.Tr Number of Successful PS

igRscp Inter-RAT Handovers Based
on RSCP for Cell

igEcNo Inter-RAT Handovers Based
on EcNo for Cell

igULTxp Inter-RAT Handovers Based
on UL Transmit Power of UE
for Cell

igDLTxp Inter-RAT Handovers Based
on DL Code Power for Cell

BSC6900 UMTS
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.
Figure 1-633 Handover Indication 1
The measurement can also be triggered at point D as shown in the figure, when the RNC receives
from the CN an IU RELEASE COMMAND message with the cause value of "Successful
Relocation", "Normal Release", or "Network Optimization" during the PS outgoing inter-RAT
handover. In this case, the handover succeeds and the corresponding counter is measured in the
best cell that the UE camps on under the SRNC, based on the cause value.

BSC6900 UMTS
Figure 1-634 Handover Indication 2
Formula
None
Unit
None
Related Features
VS.IRATHO.SuccOutPS.Tr WRFD-020303 Inter-RAT Handover Based

igRscp on Coverage

igEcNo on Coverage

igULTxp on DL QoS

igDLTxp on DL QoS

BSC6900 UMTS
1.12.14.26 Number of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC

for Different Causes for Cell
Counters
67190476 IRATHO.FailOutPSUTRA Number of Failed PS

N.CfgUnsupp Outgoing Inter-RAT
(Configuration unsupported)
67190477 IRATHO.FailOutPSUTRA Number of Failed PS

N.PhyChFail Outgoing Inter-RAT
(Physical Channel Failure)
73394021 VS.IRATHO.FailOutPS Number of Failed PS

Outgoing Inter-RAT
RNC for Cell
Description
These counters provide the number of failed PS outgoing inter-RAT handovers in the best cell
due to different causes.
Measurement point
the UE a CELL CHANGE ORDER FROM UTRAN FAILURE message after sending the CELL
CHANGE ORDER FROM UTRAN message to the UE during the PS outgoing inter-RAT
handover. In this case, the corresponding counter is measured in the best cell that the UE camps
on based on the handover cause.

BSC6900 UMTS
Figure 1-635 Failed PS outgoing inter-RAT handover initiated by the RNC
Formula
None
Unit
None
Related Features
IRATHO.FailOutPSUTRA WRFD-020303 Inter-RAT Handover Based

N.CfgUnsupp WRFD-020305 on Coverage

on Service
on Load
IRATHO.FailOutPSUTRA WRFD-020303 Inter-RAT Handover Based

N.PhyChFail WRFD-020305 on Coverage

on Service
on Load

BSC6900 UMTS
VS.IRATHO.FailOutPS WRFD-020303 Inter-RAT Handover Based


on Service
on Load
1.12.14.27 Number of Failed PS Outgoing Inter-RAT Handovers for Cell(Signalling

Connection Release Indication)
Counters
73425008 VS.IRATHO.FailOutPSUT Number of Failed PS

RAN.SCRI Outgoing Inter-RAT
Handovers for Cell
(Signalling Connection
Release Indication)
Description
This counter provides the number of the CS outgoing inter-RAT handover fails in the best cell
because the RNC receives SIGNALLING CONNECTION RELEASE INDICATION from the
UE.
Measurement point
The measurement is triggered at point A as shown in the figure.During the PS outgoing 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.

BSC6900 UMTS
Figure 1-636 Procedure for a failed outgoing inter-RAT handover in the PS domain
Formula
None
Unit
None
Related Features
VS.IRATHO.FailOutPSUT WRFD-020303 Inter-RAT Handover Based

RAN.SCRI WRFD-020305 on Coverage

on Service
on Load
1.12.14.28 Number of RL Reestablishment Attempts After UEs Failed to Receive

the PS Outgoing Inter-RAT Handover Command for Cell

BSC6900 UMTS
Counters
73425927 VS.IRATHOPS.Cancel.Re- Number of RL

Estab Reestablishment Attempts
After UEs Failed to Receive
the PS Outgoing Inter-RAT
Handover Command for Cell
Description
This counter measures the number of RL reestablishment attempts in the best cell after a UE
fails to receive a CELL CHANGE ORDER FROM UTRAN message or a HANDOVER FROM
UTRAN COMMAND message from the RNC during a PS outgoing inter-RAT handover.
Measurement point
conditions are met:
The RNC has sent a CELL CHANGE ORDER FROM UTRAN message to the UE, but fails to
receive an ACK message from the UE.
for the UE.
Figure 1-637 RL reestablishment during a PS outgoing inter-RAT handover

BSC6900 UMTS
conditions are met:
The RNC has sent a HANDOVER FROM UTRAN COMMAND message to the UE, but fails
to receive an ACK message from the UE.
for the UE.
Figure 1-638 RL reestablishment during a CS or enhanced PS outgoing inter-RAT handover
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.IRATHOPS.Cancel.Re- WRFD-020303 Inter-RAT Handover Based

Estab WRFD-020306 on Coverage

on Load
on Service
1.12.14.29 Number of Failed Outgoing UMTS-to-GSM PS Handovers due to UE

Reselection Back to a UTRAN Cell
Counters
73423107 VS.IRATHO.FailOutPS.UE Number of Failed Outgoing

Gen UMTS-to-GSM PS
Handovers due to UE
Reselection Back to a
UTRAN Cell
Description
This counter provides the number of times that a UE reselects a 3G cell and sends an RRC
connection setup request or receive IU RELEASE COMMAND with cause of Release due to
UE generated signalling connection release during the UMTS-to-GSM PS handover. This
counter indicates that the UE accesses the UTRAN again during the UMTS-to-GSM PS
handover. If a large proportion of inter-RAT handovers fail due to this reason, view the 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 following figure. After the RNC sends
the UE a CELL CHANGE ORDER FROM UTRAN message, instructing the UE to hand over
to a 2G cell, this counter is measured in the best cell that the UE camps on before the handover
if the UE reselects a 3G cell and sends an RRC connection setup request before the RNC receives
from the CN an IU RELEASE COMMAND message or if the RNC receives from the CN an
IU RELEASE COMMAND message with the cause value of "UE generated signaling
connection release".

BSC6900 UMTS
Figure 1-639 inter-RAT handovers abnormal procedure
Formula
None
Unit
None
Related Features
VS.IRATHO.FailOutPS.UE WRFD-020303 Inter-RAT Handover Based

Gen WRFD-020305 on Coverage

on Service
on Load
1.12.14.30 Number of Failed PS Outgoing Inter-RAT Handovers for Cell(No SRNS

DATA Forward cmd)

BSC6900 UMTS
Counters

RAN.NoSRNSDataFor- Outgoing Inter-RAT
wardCmd Handovers for Cell(No
SRNS DATA Forward cmd)
Description
This counter provides the number of the PS outgoing inter-RAT handover fails in the best cell
because the timer waiting for the SRNS DATA FORWARD COMMAND message from CN
expires.
Measurement point
The measurement is triggered at point A as shown in the figure.If an SRNS context forwarding
procedure is triggered in a PS inter-RAT handover and no SRNS DATA FORWARD
COMMAND message is received, this counter is increased by one in the best cell before the
handover.
Figure 1-640 Procedure for a failed outgoing inter-RAT handover in the PS domain
Formula
None

BSC6900 UMTS
Unit
None
Related Features

RAN.NoSRNSDataFor- WRFD-020305 on Coverage
wardCmd Inter-RAT Handover Based
WRFD-020306
on Service
on Load
1.12.14.31 Number of Times that the Timer Waiting for Iu Release Command
Expires in PS Outgoing Inter-RAT Handover Initiated by RNC for Cell
Counters
67192661 VS.IRATHO.FailOutPSUT Number of Times that the

RAN.NoReply Timer Waiting for Iu Release
Command Expires in PS
Outgoing Inter-RAT
Handover Initiated by RNC
for Cell
Description
This counter provides the number of times that the timer waiting for the IU RELEASE
COMMAND message expires in the PS outgoing inter-RAT handover initiated by the RNC.
Measurement point
The measurement is triggered at point A as shown in the figure. During the PS outgoing 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.

BSC6900 UMTS
Figure 1-641 Timeout waiting for Iu Release Command in PS Outgoing Inter-RAT Handover
Initiated by RNC
Formula
None
Unit
None
Related Features

RAN.NoReply WRFD-020305 on Coverage

on Service
on Load
1.12.14.32 Number of Abnormally Terminated PS Outgoing Inter-RAT Handovers

for Cell

BSC6900 UMTS
Counters
73394022 VS.IRATHO.FailOutPS.Ab Number of Abnormally

ort Terminated PS Outgoing
Inter-RAT Handovers for
Cell
Description
This counter provides the number of times that the PS outgoing inter-RAT handover fails in the
best cell because an IU RELEASE COMMON message with a cause value of abnormal release,
that is, a cause value except "Successful Relocation", "Normal Release", or "Network
Optimization", is received.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC receives an IU
RELEASE COMMAND message in the PS domain with the cause value except "Successful
Relocation", "Normal Release" or "Network Optimization" after sending a CELL CHANGE
ORDER FORM UTRAN message. In this case, this counter is measured in the SRNC best cell
Figure 1-642 PS domain inter-RAT outgoing handover procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.FailOutPS.Ab WRFD-020303 Inter-RAT Handover Based

ort WRFD-020305 on Coverage

on Service
on Load
1.12.14.33 Number of Failed PS Outgoing Inter-RAT Handovers for Cell(Failure in

Counters

RAN.InterRatRF Outgoing Inter-RAT
Handovers for Cell(Failure in
the Radio Interface
Procedure)
Description
This counter provides the number of IU RELEASE COMMAND messages that are received by
the RNC from the CN after the RNC sends CELL CHANGE ORDER FROM UTRAN messages
to the UE and that contain the reason value "Failure in the Radio Interface Procedure." This
counter is measured in a PS inter-RAT handover and in the best cell before the handover.
Measurement point
The measurement is triggered at point C as shown in the figure.When the RNC receives a IU
RELEASE COMMAND message,If the IU RELEASE COMMAND message indicate the
reason"Failure in the Radio Interface Procedure",this counter is increased by one in the best cell

BSC6900 UMTS
Figure 1-643 Procedure for an outgoing inter-RAT handover in the PS domain
Formula
None
Unit
None
Related Features

RAN.InterRatRF WRFD-020305 on Coverage

on Service
on Load
1.12.14.34 Number of PS Outgoing Inter-RAT Handover Requests Initiated by UE

for Cell

BSC6900 UMTS
Counters
67190413 VS.IRATHO.AttOutPSUE Number of PS Inter-RAT

Outgoing Inter-RAT
Handover Requests Initiated
by UE for Cell
Description
This counter provides the number of PS outgoing inter-RAT handover requests initiated by the
UE. If the UE is in CELL_FACH, CELL_PCH, or URA_PCH state after setting up PS services
in the WCDMA system, it can reselect a GPRS network based on the cell reselection criteria.
After the UE reselects the GPRS network, it sets up PS services again. During the PS service
setup, the 2.5G SGSN try to obtain from the RNC the context of the PS RAB set up by the UE
in the WCDMA system by sending the SRNS CONTEXT REQUEST message to the SRNC.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives the
SRNS CONTEXT REQUEST message from the CN during a PS inter-RAT outgoing handover,
the counter is measured in the best cell that the UE camps on before the handover.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.AttOutPSUE WRFD-02030802 PS Handover Between

UMTS and GPRS

UE for Cell
Counters
67189763 IRATHO.SuccOutPSUE Number of Successful PS

Outgoing Inter-RAT
Handovers Initiated by UE
for Cell
Description
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 CN an IU RELEASE COMMAND message with the cause value of "Normal Release",
"Successful Relocation" or "Network Optimization",during a PS inter-RAT outgoing handover.
In this case, this counter is measured in the cell that the UE camps on before handover.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
IRATHO.SuccOutPSUE WRFD-02030802 PS Handover Between

UMTS and GPRS
1.12.14.36 Number of Preparations for CS or Enhanced PS Incoming Inter-RAT

Handover for Cell

BSC6900 UMTS
Counters

pInCS CS Incoming Inter-RAT
Handover for Cell

pInPS Enhanced PS Incoming Inter-
Description
These counters provide the number of preparation attempts for CS or Enhanced PS incoming
inter-RAT handovers according to the target cell ID in the relocation request.
Measurement point
the 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.
Figure 1-646 Normal CS or the Enhanced PS incoming inter-RAT handover

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.AttRelocPre- WRFD-02040002 Inter System Direct Retry

pInCS WRFD-020303 Inter-RAT Handover Based

on Service
on Load
VS.IRATHO.AttRelocPre- WRFD-02030802 PS Handover Between

pInPS UMTS and GPRS
1.12.14.37 Number of Attempts at Incoming PS LTE-to-UMTS Handovers Triggered

by CSFB for Cell
Counters
73426146 VS.L2U.AttRelocPrepInPS. Number of Attempts at

CS.CELL Incoming PS LTE-to-UMTS
CSFB for Cell
Description
This counter provides the number of attempts at incoming PS L2U handovers triggered by CSFB
in the cell that is specified by the related RELOCATION REQUEST message.
Measurement point
When the RNC receives a RELOCATION REQUEST message from the CN, this counter is
increased by one in the cell that is specified by the TargetCellId IE in the message if the "Source
RNC To Target RNC Transparent Container" IE in the RELOCATION REQUEST message
carries a CSFB flag or the Cause IE in the message is set to "CS Fallback triggered." The
measurement is triggered at point A, as shown in the following figure.

BSC6900 UMTS
Figure 1-647 CSFB signaling procedure initiated on the LTE side
Formula
None
Unit
None
Related Features
VS.L2U.AttRelocPrepInPS. WRFD-140102 CS Fallback Guarantee for

CS.CELL LTE Emergency Calls
1.12.14.38 Number of Preparation Attempts for Incoming LTE-to-UMTS CS+PS

Handovers Triggered by SRVCC for VoIP Services

BSC6900 UMTS
Counters
73425820 VS.SRVCC.L2U.AttReloc- Number of Preparation

PrepInCSPS Attempts for Incoming LTE-
to-UMTS CS+PS Handovers
Description
This counter provides the number of preparation attempts for incoming L2U CS+PS handovers
triggered by Single Radio Voice Call Continuity (SRVCC) with PS Handover for VoIP services.
This counter is measured according to the target cell ID in the RELOCATION REQUEST
message. L2U refers to handovers from the LTE network to the UMTS network. With the
SRVCC with PS Handover feature, the VoIP and PS services in an LTE network are handed
over to the CS and PS domains of the UMTS network, respectively. As a result, speech continuity
is ensured during the handover. On the RNC side, this process is an incoming inter-RAT CS+PS
handover. RAT is short for radio access technology.
Measurement point
The measurement is triggered at point A shown in the following figure. After confirming that
the two RELOCATION REQUEST messages from the CN are incoming CS+PS handover
requests from an LTE cell, the RNC triggers the incoming inter-RAT CS+PS handover
preparation procedure. This counter is measured according to the target cell ID in the two
RELOCATION REQUEST messages.

BSC6900 UMTS
Figure 1-648 Procedure of SRVCC inter-RAT handover
Formula
None
Unit
None
Related Features
VS.SRVCC.L2U.AttReloc- WRFD-150215 SRVCC from LTE to UMTS

PrepInCSPS with PS Handover

BSC6900 UMTS
1.12.14.39 Number of Successful Preparations for CS or Enhanced PS Incoming

Inter-RAT Handover for Cell
Counters

pInCS preparations for CS
Incoming Inter-RAT
Handovers for Cell

pInPS Preparations for Enhanced
PS Incoming Inter-RAT
Handover for Cell
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.SuccRelocPre- WRFD-02040002 Inter System Direct Retry

pInCS WRFD-020303 Inter-RAT Handover Based

on Service
on Load
VS.IRATHO.SuccRelocPre- WRFD-02030802 PS Handover Between

pInPS UMTS and GPRS
1.12.14.40 Number of Successful Preparations for Incoming PS LTE-to-UMTS

Handovers Triggered by CSFB for Cell
Counters
73426148 VS.L2U.SuccRelocPrepInP Number of Successful

S.CS.CELL Preparations for Incoming PS
LTE-to-UMTS Handovers
Triggered by CSFB for Cell
Description
This counter provides the number of successful preparations for incoming PS L2U handovers
triggered by CSFB in the cell that is specified in the related RELOCATION REQUEST message.
Measurement point
When the RNC sends the CN a RELOCATION REQUEST ACKNOWLEDGE message, this
counter is increased by one in the cell that is specified by the TargetCellId IE in the corresponding
RELOCATION REQUEST message if the "Source RNC To Target RNC Transparent

BSC6900 UMTS
Container" IE in the RELOCATION REQUEST message carries a CSFB flag or the Cause IE
in the message is set to "CS Fallback triggered." The measurement is triggered at point B, as
shown in the following figure.
Formula
None
Unit
None
Related Features
VS.L2U.SuccRelocPrepInP WRFD-140102 CS Fallback Guarantee for

S.CS.CELL LTE Emergency Calls
1.12.14.41 Number of Successful Preparations for Incoming LTE-to-UMTS CS+PS

Handovers Triggered by SRVCC for VoIP Services

BSC6900 UMTS
Counters
73425821 VS.SRVCC.L2U.SuccRe- Number of Successful

locPrepInCSPS Preparations for Incoming
LTE-to-UMTS CS+PS
for Cell
Description
This counter provides the number of successful preparations for incoming L2U CS+PS
handovers triggered by Single Radio Voice Call Continuity (SRVCC) with PS Handover for
VoIP services. This counter is measured according to the target cell ID in the RELOCATION
REQUEST message. L2U refers to handovers from the LTE network to the UMTS network.
With the SRVCC with PS Handover feature, the VoIP and PS services in an LTE network are
handed over to the CS and PS domains of the UMTS network, respectively. As a result, speech
continuity is ensured during the handover. On the RNC side, this process is an incoming inter-
RAT CS+PS handover. RAT is short for radio access technology.
Measurement point
The measurement is triggered at point B shown in the following figure. When the RNC sends
two RELOCATION REQUEST ACKNOWLEDGE messages to the CN, this counter is
measured according to the target cell ID in the two RELOCATION REQUEST messages.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SRVCC.L2U.SuccRe- WRFD-150215 SRVCC from LTE to UMTS

locPrepInCSPS with PS Handover

BSC6900 UMTS
1.12.14.42 Number of CS Incoming Inter-RAT Handover Attempts for Cell
Counters
73394014 VS.IRATHO.AttInCS Number of CS Incoming

Inter-RAT Handover
Attempts for Cell
Description
This counter provides the number of CS incoming inter-RAT handover attempts according to
the target cell ID in the relocation request.
Measurement point
The measurement is triggered at point C as shown in the figure. After the RNC sends to the CN
a RELOCATION REQUEST ACKNOWLEDGE message indicating that the CS inter-RAT
handover preparation succeeds, this counter is measured according to the value of TargetCellId
in the RELOCATION REQUEST message if the RNC receives a HANDOVER TO UTRAN
COMPLETE message from the UE or a RADIO LINK RESTORE INDICATION message from
the NodeB during the CS incoming inter-RAT handover. The measurement is triggered only
once if both the messages are received.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.AttInCS WRFD-02040002 Inter System Direct Retry


on Service
on Load
1.12.14.43 Number of Incoming LTE-to-UMTS CS+PS Handover Attempts

Triggered by SRVCC for VoIP Services
Counters
73425822 VS.SRVCC.L2U.At- Number of Incoming LTE-

tInCSPS to-UMTS CS+PS Handover
Attempts Triggered by
for Cell
Description
This counter provides the number of incoming L2U CS+PS handover attempts triggered by
Single Radio Voice Call Continuity (SRVCC) with PS Handover for VoIP services. This counter
is measured according to the target cell ID in the RELOCATION REQUEST message. L2U
refers to handovers from the LTE network to the UMTS network. With the SRVCC with PS
Handover feature, the VoIP and PS services in an LTE network are handed over to the CS and
PS domains of the UMTS network, respectively. As a result, speech continuity is ensured during
the handover. On the RNC side, this process is an incoming inter-RAT CS+PS handover. RAT
is short for radio access technology.

BSC6900 UMTS
Measurement point
The measurement is triggered at point C shown in the following figure. After the RNC sends
the CN two RELOCATION REQUEST ACKNOWLEDGE messages indicating that the
handover preparation process is completed, if the RNC receives a HANDOVER TO UTRAN
COMPLETE message from the UE, this counter is measured according to the target cell ID in
the RELOCATION REQUEST message.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.SRVCC.L2U.At- WRFD-150215 SRVCC from LTE to UMTS

tInCSPS with PS Handover
1.12.14.44 Number of Successful CS or Enhanced PS Incoming Inter-RAT

Handovers for Cell
Counters
67189759 VS.IRATHO.SuccInCS Number of Successful CS

Incoming Inter-RAT
Handovers for Cell
67192677 VS.IRATHO.SuccRelo- Number of Successful

cInPS Enhanced PS Incoming Inter-
RAT Handovers for Cell
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.

BSC6900 UMTS
Figure 1-654 Normal CS or the Enhanced PS incoming inter-RAT handover
Formula
None
Unit
None
Related Features
VS.IRATHO.SuccInCS WRFD-02040002 Inter System Direct Retry


on Service
on Load
VS.IRATHO.SuccRelo- WRFD-02030802 PS Handover Between

cInPS UMTS and GPRS

BSC6900 UMTS
1.12.14.45 Number of Successful Incoming PS LTE-to-UMTS Handovers Triggered

by CSFB for Cell
Counters
73426147 VS.L2U.SuccRelocInPS.CS. Number of Successful

CELL Incoming PS LTE-to-UMTS
CSFB for Cell
Description
This counter provides the number of successful incoming PS L2U handovers triggered by CSFB
in the cell that is specified by the related RELOCATION REQUEST message.
Measurement point
When the RNC sends the CN a RELOCATION COMPLETE message, this counter is increased
by one in the cell that is specified by the TargetCellId IE in the corresponding RELOCATION
REQUEST message if the "Source RNC To Target RNC Transparent Container" IE in the
RELOCATION REQUEST message carries a CSFB flag or the Cause IE in the message is set
to "CS Fallback triggered." The measurement is triggered at point D, as shown in the following
figure.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.L2U.SuccRelocInPS.CS. WRFD-140102 CS Fallback Guarantee for

CELL LTE Emergency Calls
1.12.14.46 Number of Successful Incoming LTE-to-UMTS CS+PS Handovers

Triggered by SRVCC for VoIP Services
Counters
73425823 VS.SRVCC.L2U.Suc- Number of Successful

cInCSPS Incoming LTE-to-UMTS CS
+PS Handovers Triggered by
for Cell
Description
This counter provides the number of successful incoming L2U CS+PS handovers triggered by
Single Radio Voice Call Continuity (SRVCC) with PS Handover for VoIP services. This counter
is measured according to the target cell ID in the RELOCATION REQUEST message. L2U
refers to handovers from the LTE network to the UMTS network. With the SRVCC with PS
Handover feature, the VoIP and PS services in an LTE network are handed over to the CS and
PS domains of the UMTS network, respectively. As a result, speech continuity is ensured during
the handover. On the RNC side, this process is an incoming inter-RAT CS+PS handover. RAT
is short for radio access technology.
Measurement point
The measurement is triggered at point D shown in the following figure. When the RNC sends
two RELOCATION COMPLETE messages to the CN, this counter is measured according to
the target cell ID in the two RELOCATION REQUEST messages.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SRVCC.L2U.Suc- WRFD-150215 SRVCC from LTE to UMTS

cInCSPS with PS Handover

BSC6900 UMTS
1.12.14.47 Number of Failed Preparations for CS or Enhanced PS Incoming Inter-

RAT Handover for Different Causes for Cell
Counters

InCS.TRNCSysFailReloc Preparations for CS
Incoming Inter-RAT
Handover (Relocation failure
in target CN/RNC or target
system)

InCS.TRNCSysRelocUn- Preparations for CS
supp Incoming Inter-RAT
Handover (Relocation not
supported in target RNC or
target system)

InCS.ResUnavail Preparations for CS
Incoming Inter-RAT
Handover (No resource
available)

InCS.TgtHighLoad Preparations for CS
Incoming Inter-RAT
Handover (Traffic Load In
The Target Cell Higher Than
In The Source Cell)

InPS.TgtFail Preparations for Enhanced
Handover for cell
(Relocation failure in target
CN/RNC or target system)

InPS.ReloUnSupp Preparations for Enhanced
Handover for cell
target RNC or target system)

BSC6900 UMTS

InPS.ResUnavail Preparations for Enhanced
Handover for cell (No
resource available)

InPS.TgtHighLoad Preparations for Enhanced
Handover for cell (Traffic
Cell)
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 counter is measured according to the value of
TargetCellId in the RELOCATION REQUEST message.
Figure 1-657 Failed incoming inter-RAT handover

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IRATHO.FailRelocPrep WRFD-02040002 Inter System Direct Retry

InCS.TRNCSysFailReloc WRFD-020303 Inter-RAT Handover Based

on Service
on Load

InCS.TRNCSysRelocUn- WRFD-020303 Inter-RAT Handover Based
supp on Coverage
WRFD-020305
on Service
on Load

InCS.ResUnavail WRFD-020303 Inter-RAT Handover Based

on Service
on Load

InCS.TgtHighLoad WRFD-020303 Inter-RAT Handover Based

on Service
on Load

InPS.TgtFail UMTS and GPRS

BSC6900 UMTS

InPS.ReloUnSupp UMTS and GPRS

InPS.ResUnavail UMTS and GPRS

InPS.TgtHighLoad UMTS and GPRS
1.12.14.48 Number of Failed CS or Enhanced PS Inter-RAT Incoming Handovers

Due to No Response from UE for Cell
Counters
67190410 VS.IRATHO.FailInCS.NoR Number of Failed CS Inter-

eply RAT Incoming Handovers
Due to No Response from UE
for Cell
67192682 VS.IRATHO.FailRelocInPS Number of Failed Enhanced

.NoReply PS Incoming Inter-RAT
Handovers Due to UE
Response Timeout for Cell
Description
These counters provide the number of failed CS or Enhanced PS incoming inter-RAT handovers
due to no response from the UE according to the target cell ID in the relocation request.
Measurement point
The measurement is triggered at point A as shown in the figure. During the CS or the Enhanced
PS inter-RAT handover, after sending the RELOCATION REQUEST ACKNOWLEDGE
message, the TRNC starts the timer waiting for the response message. If no response is received
from the UE before the timer expires, the incoming inter-RAT handover fails and the
corresponding counter is measured according to the value of TargetCellId in the RELOCATION
REQUEST message.

BSC6900 UMTS
Figure 1-658 Failed CS Inter-RAT Incoming Handovers
Formula
None
Unit
None
Related Features
VS.IRATHO.FailInCS.NoR WRFD-02040002 Inter System Direct Retry

eply WRFD-020303 Inter-RAT Handover Based

on Service
on Load
VS.IRATHO.FailRelocInPS WRFD-02030802 PS Handover Between

.NoReply UMTS and GPRS

BSC6900 UMTS
1.12.14.49 Counters Related to the Number of Inter-RAT Measurement Expiry for

Cell
Counters
67193399 VS.IRATHO.OutCS.Meas- Number of CS Inter-RAT

TimeOut Measurement Expiry for Cell
67193400 VS.IRATHO.OutPS.Meas- Number of PS Inter-RAT

TimeOut Measurement Expiry for Cell
Description
These counters provide the number of times that the timer for inter-RAT measurement expires
before which no inter-RAT cell is detected and inter-RAT handover fails to start.
Measurement point
After the inter-RAT measurement is started, if no inter-RAT handover is performed before the
timer for inter-RAT measurement expires, the inter-RAT measurement and compressed mode
(if activated) are stopped. In this case, this counter is measured in the best cell.
Formula
None
Unit
None
Related Features
VS.IRATHO.OutCS.Meas- WRFD-020303 Inter-RAT Handover Based

TimeOut WRFD-020309 on Coverage
on DL QoS
VS.IRATHO.OutPS.Meas- WRFD-020303 Inter-RAT Handover Based

TimeOut WRFD-020309 on Coverage
on DL QoS

BSC6900 UMTS
1.12.15 Measurement Related to the Release of Iu Signaling

Connections (Without RAB) (Cell)(IU.Sig.Rel.Cell)
Overview
The RNC receives an RRC Connection Setup Complete message and returns an INITIAL UE
MESSAGE to the CN. The signaling connection (without RAB) is released over the Iu interface.
This function subset measures the number of Iu signaling connection releases in a cell based on
the domain.
Counters
Description
73426353 VS.IU.Sig.Normal Number of Iu CS V900R015

Rel.CS Signaling
Connections
(Without RAB)
Normally Released
for Cell
73426354 VS.IU.Sig.Normal Number of Iu PS V900R015

Rel.PS Signaling
Connections
(Without RAB)
Normally Released
for Cell
73426355 VS.IU.Sig.Abnorm Number of Iu CS V900R015

alRel.CS Signaling
Connections
(Without RAB)
Abnormally
Released for Cell
73426356 VS.IU.Sig.Abnorm Number of Iu PS V900R015

alRel.PS Signaling
Connections
(Without RAB)
Abnormally
Released for Cell
73426357 VS.IU.Sig.Normal Number of Iu CS V900R015

Rel.CS.Service Signaling
Connections
(Without RAB)
Normally Released
for Cell (Service
Reasons)

BSC6900 UMTS

Description
73426358 VS.IU.Sig.Normal Number of Iu PS V900R015

Rel.PS.Service Signaling
Connections
(Without RAB)
Normally Released
for Cell (Service
Reasons)

alRel.CS.Service Signaling
Connections
(Without RAB)
Abnormally
Released for Cell
(Service Reasons)

alRel.PS.Service Signaling
Connections
(Without RAB)
Abnormally
Released for Cell
(Service Reasons)

alRel.CS.Service.Se Signaling
cModeFail Connections
(Without RAB)
Abnormally
Released Due to
Security Mode
Procedure Failures
for Cell (Service
Reasons)

alRel.PS.Service.Se Signaling
cModeFail Connections
(Without RAB)
Abnormally
Released Due to
Security Mode
Procedure Failures
for Cell (Service
Reasons)

BSC6900 UMTS
None
1.12.15.1 Number of Iu CS Signaling Connections (Without RAB) Normally

Released for Cell
Counters
73426353 VS.IU.Sig.NormalRel.CS Number of Iu CS Signaling

Connections (Without RAB)
Normally Released for Cell
Description
This counter measures the number of Iu CS signaling connections (without RAB) normally
released in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives an RRC
Connection Setup Complete message from a UE and sends an INITIAL UE MESSAGE to the
CN. Then, the signaling connection (without RAB) for the UE is released over the Iu interface.
If the latest IU RELEASE COMMAND message received by the RNC carries the cause value
"User Inactivity", "Normal Release", "Successful Relocation" or "Network Optimization", or
the RNC initiates the release procedure by sending an IU RELEASE REQUEST message with
the causes of "User Inactivity", "Network Optimization" or "UE Generated Signalling
Connection Release", this counter is increased by one in the best cell of the UE based on the
domain of the released signaling connection.
Figure 1-659 Iu signaling connections normally released procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.Sig.NormalRel.CS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.15.2 Number of Iu PS Signaling Connections (Without RAB) Normally

Released for Cell
Counters
73426354 VS.IU.Sig.NormalRel.PS Number of Iu PS Signaling

Description
This counter measures the number of Iu PS signaling connections (without RAB) normally
Measurement point
Connection Release", this counter is increased by one in the best cell of the UE based on the
domain of the released signaling connection. For details about the cause values indicating a
normal release.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.Sig.NormalRel.PS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.15.3 Number of Iu CS Signaling Connections (Without RAB) Abnormally

Released for Cell

BSC6900 UMTS
Counters
73426355 VS.IU.Sig.AbnormalRel.CS Number of Iu CS Signaling

Abnormally Released for
Cell
Description
This counter measures the number of Iu CS signaling connections (without RAB) abnormally
Measurement point
CN. Then, the RNC sends an IU RELEASE REQUEST message to the CN. The signaling
connection (without RAB) for the UE is released over the Iu interface. If the latest IU RELEASE
COMMAND message received by the RNC carries a cause value other than "User Inactivity",
"Normal Release", "Successful Relocation", "Network Optimization" or "UE Generated
Signalling Connection Release", this counter is increased by one in the best cell of the UE based
on the domain of the released signaling connection. For details about the cause values indicating
an abnormal release, see 3GPP TS 25.413.
Figure 1-661 Iu signaling connections abnormally released procedure
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IU.Sig.AbnormalRel.CS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.15.4 Number of Iu PS Signaling Connections (Without RAB) Abnormally

Released for Cell
Counters
73426356 VS.IU.Sig.AbnormalRel.PS Number of Iu PS Signaling

Cell
Description
This counter measures the number of Iu PS signaling connections (without RAB) abnormally
Measurement point
Signalling Connection Release", this counter is increased by one in the best cell of the UE based
on the domain of the released signaling connection. For details about the cause values indicating
an abnormal release, see 3GPP TS 25.413.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.Sig.AbnormalRel.PS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.15.5 Number of Iu CS Signaling Connections (Without RAB) Normally

Released for Cell (Service Reasons)

BSC6900 UMTS
Counters
73426357 VS.IU.Sig.NormalRel.CS.S Number of Iu CS Signaling

ervice Connections (Without RAB)
(Service Reasons)
Description
This counter measures the number of Iu CS signaling connections (without RAB) that are
normally released due to service reasons. This counter is measured in the best cell.
Measurement point
Connection Release", and if the RRC connection is set up due to originating conversational call,
terminating conversational call, or emergency call, this counter is increased by one in the best
cell of the UE based on the domain of the released signaling connection. For details about the
cause values indicating a normal release .

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.Sig.NormalRel.CS.S WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

ervice Connection and Radio
and Release
1.12.15.6 Number of Iu PS Signaling Connections (Without RAB) Normally

Counters
73426358 VS.IU.Sig.NormalRel.PS.Se Number of Iu PS Signaling

rvice Connections (Without RAB)
(Service Reasons)
Description
This counter measures the number of Iu PS signaling connections (without RAB) that are
normally released due to service reasons. This counter is measured in the best cell.
Measurement point
Connection Release", and if the RRC connection is set up due to originating interactive call,
terminating interactive call, originating background call, or terminating background call, this
counter is increased by one in the best cell of the UE based on the domain of the released signaling
connection. For details about the cause values indicating a normal release, see 3GPP TS 25.413.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.Sig.NormalRel.PS.Se WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

rvice Connection and Radio
and Release


BSC6900 UMTS
Counters

.Service Connections (Without RAB)
Cell (Service Reasons)
Description
This counter measures the number of Iu CS signaling connections (without RAB) that are
abnormally released due to service reasons. This counter is measured in the best cell.
Measurement point
CN. Then, the RNC sends the last IU RELEASE REQUEST message to the CN. The signaling
connection (without RAB) for the UE is released over the Iu interface. If the IU RELEASE
Signalling Connection Release", and if the RRC connection is set up due to originating
conversational call, terminating conversational call, or emergency call, this counter is increased
by one in the best cell of the UE based on the domain of the released signaling connection. For
details about the cause values indicating an abnormal release, see 3GPP TS 25.413.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

.Service Connection and Radio
and Release

Counters
73426360 VS.IU.Sig.AbnormalRel.PS. Number of Iu PS Signaling

Service Connections (Without RAB)
Cell (Service Reasons)
Description
This counter measures the number of Iu PS signaling connections (without RAB) that are
abnormally released due to service reasons. This counter is measured in the best cell.
Measurement point
Signalling Connection Release", and if the RRC connection is set up due to originating
interactive call, terminating interactive call, originating background call, or terminating
background call, this counter is increased by one in the best cell of the UE based on the domain
of the released signaling connection. For details about the cause values indicating an abnormal
release, see 3GPP TS 25.413.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IU.Sig.AbnormalRel.PS. WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Service Connection and Radio
and Release

Released Due to Security Mode Procedure Failures for Cell (Service Reasons)

BSC6900 UMTS
Counters

.Service.SecModeFail Connections (Without RAB)
Abnormally Released Due to
Security Mode Procedure
Failures for Cell (Service
Reasons)
Description
This counter measures the number of Iu CS signaling connections (established because of service
reasons; without RAB) that are abnormally released due to service reasons in the case of security
mode procedure failures. This counter is measured in the best cell.
Measurement point
CN. Then, the security mode procedure fails, and the RNC sends an IU RELEASE REQUEST
message to the CN. The signaling connection (without RAB) for the UE is released over the Iu
interface. If the latest IU RELEASE COMMAND message received by the RNC carries a cause
value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network
Optimization" or "UE Generated Signalling Connection Release", and if the RRC connection is
set up due to originating conversational call, terminating conversational call, or emergency call,
this counter is increased by one in the best cell of the UE based on the domain of the released
signaling connection. For details about the cause values indicating an abnormal release, see
3GPP TS 25.413.
Figure 1-667 Iu signaling connections abnormally released due to security mode procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features

.Service.SecModeFail Connection and Radio
and Release

Released Due to Security Mode Procedure Failures for Cell (Service Reasons)
Counters
73426362 VS.IU.Sig.AbnormalRel.PS. Number of Iu PS Signaling

Service.SecModeFail Connections (Without RAB)
Failures for Cell (Service
Reasons)
Description
This counter measures the number of Iu PS signaling connections (established because of service
reasons; without RAB) that are abnormally released due to security mode procedure failures.
This counter is measured in the best cell.
Measurement point
CN. Then, the security mode procedure fails, and the RNC sends an IU RELEASE REQUEST
message to the CN. The signaling connection (without RAB) for the UE is released over the Iu
interface. If the latest IU RELEASE COMMAND message received by the RNC carries a cause
value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network

BSC6900 UMTS
Optimization" or "UE Generated Signalling Connection Release", and if the RRC connection is
set up due to originating interactive call, terminating interactive call, originating background
call, or terminating background call, this counter is increased by one in the best cell of the UE
based on the domain of the released signaling connection. For details about the cause values
indicating an abnormal release, see 3GPP TS 25.413.
Figure 1-668 Iu signaling connections abnormally released due to security mode procedure
Formula
None
Unit
None
Related Features
VS.IU.Sig.AbnormalRel.PS. WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Service.SecModeFail Connection and Radio
and Release

BSC6900 UMTS
1.12.16 Iub Interface Measurement per cell(IUB.Cell)
Overview
Iub Interface radio link (RL) procedures on the Iub interface are as follows: RL setup procedure,
RL deletion procedure, Synchronized RL reconfiguration procedure, RL failure procedure, RL
restoration procedure.
Counters
Description
67180826 VS.IUB.CancelRL- Number of Iub Earlier than

Recfg Interface RLs Whose V900R011
Synchronized
Reconfiguration Is
Cancelled for Cell
67180827 VS.IUB.RLFailInd Number of Iub Earlier than

Interface RL Failures V900R011
for Cell
67180831 VS.IUB.RLFailInd. Number of Iub Earlier than

CfgUnsupp Interface Radio Link V900R011
Failures for Cell
(Configuration
Unsupported)

HW Interface Radio Link V900R011
Failures for Cell
(Device Fault)

SyncFail Interface Radio Link V900R011
Synchronization
Failures for Cell
67180830 VS.IUB.RLFail- Number of Iub Earlier than

NoRestore Interface Radio Link V900R011
Failures for Cell
(Synchronization
Failure)
67180813 RLM.FailRLAddIu Number of Iub Earlier than

b.CfgUnsup Interface Radio Link V900R011
Addition Failures for
Cell (Configuration
Unsupported)

BSC6900 UMTS

Description
67180812 RLM.FailRLAddIu Number of Iub Earlier than

b.Cong Interface Radio Link V900R011
Cell (Congestion)
67180811 VS.SHO.FailRLAd Number of Iub Earlier than

dIub.HW Interface Radio Link V900R011
Cell (Device Fault)
67180823 VS.IUB.FailRLRec Number of Iub Earlier than

fg.CfgUnsupp Interface Radio Link V900R011
Synchronous
Reconfiguration
Failures for Cell
(Configuration
Unsupported)

fg.Cong Interface Radio Link V900R011
Synchronous
Reconfiguration
Failures for Cell
(Congestion)

fg.HW Interface Radio Link V900R011
Synchronous
Reconfiguration
Failures for Cell
(Device Fault)

fg.NoReply Interface RLs V900R011
Unsuccessfully
Reconfigured Due to
No Response for Cell
67180806 RLM.FailRLSetup Number of Iub Earlier than

Iub.CfgUnsup Interface Radio Link V900R011
Setup Failures for
Cell (Configuration
Unsupported)
67180805 RLM.FailRLSetup Number of Iub Earlier than

Iub.Cong Interface Radio Link V900R011
Setup Failures for
Cell (Congestion)

BSC6900 UMTS

Description
67180804 VS.IUB.FailRLSet Number of Iub Earlier than

up.HW Interface Radio Link V900R011
Setup Failures for
Cell (Device Fault)
67189775 VS.IUB.At- Number of Iub Earlier than

tRLRecfg Interface RL V900R011
Reconfiguration
Attempts for Cell
67180808 VS.IUB.AttRLAdd Number of Iub Earlier than

Interface RL V900R011
Addition Requests
for Cell
67180815 VS.IUB.AttRLDel Number of Iub V900R012

Interface RL
Deletion Requests
for Cell
67180801 VS.IUB.AttRLSet- Number of Iub Earlier than

up Interface RL V900R011
Establishment
Requests for Cell
67180832 VS.IUB.RLRestore Number of Iub Earlier than

Interface RL V900R011
Restorations for Cell
67180809 VS.IUB.SuccRLAd Number of Iub Earlier than

d Interface RLs V900R011
Successfully Added
for Cell
67180816 VS.IUB.SuccRLDel Number of Iub V900R012

Interface RLs
Successfully Deleted
for Cell
67180819 VS.IUB.SuccRL- Number of Iub Earlier than

Recfg Interface RLs V900R011
Successfully
Synchronization
Reconfigured for
Cell
67180802 VS.IUB.SuccRL- Number of Iub Earlier than

Setup Interface RLs V900R011
Successfully
Established for Cell

BSC6900 UMTS

Description
67180838 VS.IUB.FailRLSet Number of Iub Earlier than

up.NoReply Interface RLs V900R011
Unsuccessfully
Established Due to
No Response for Cell
None
1.12.16.1 Number of RLs with Synchronized Reconfiguration Cancelled on Iub

Interface
Counters
67180826 VS.IUB.CancelRLRecfg Number of Iub Interface RLs

Whose Synchronized
Reconfiguration Is Cancelled
for Cell
Description
This measurement counter takes statistics of the number of RLs whose synchronized
reconfiguration is cancelled on the Iub interface in a cell.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends a RADIO
LINK RECONFIGURATION CANCEL message to the NodeB. In this case, the RNC measures
the counter in the cell of the RL whose reconfiguration is cancelled on the Iub interface.

BSC6900 UMTS
Figure 1-669 RL reconfiguration cancel procedure
Formula
None
Unit
None
Related Features
VS.IUB.CancelRLRecfg WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.16.2 Number of RL Failures on Iub Interface
Counters
67180827 VS.IUB.RLFailInd Number of Iub Interface RL

Failures for Cell

BSC6900 UMTS
67180831 VS.IUB.RLFailInd.CfgUn- Number of Iub Interface

supp Radio Link Failures for Cell
(Configuration
Unsupported)
67180829 VS.IUB.RLFailInd.HW Number of Iub Interface

Radio Link Failures for Cell
(Device Fault)
67189772 VS.IUB.RLFailInd.SyncFail Number of Iub Interface

Radio Link Synchronization
Failures for Cell
Description
These counters provide the number of the RADIO LINK FAILURE INDICATION messages
that the RNC receives from the NodeB on the Iub interface in a cell.
VS.IUB.RLFailInd.CfgUnsupp Number of RL failures on Iub interface due

to configuration unsupported (cause value:
Power level not supported, Measurement not
supported for the object, SIB Origination in
Node B not Supported, Requested Tx
Diversity Mode not supported, Number of DL
codes not supported, S-CPICH not supported,
Combining not supported, UL SF not
supported, DL SF not supported, Common
Transport Channel Type not supported,
Dedicated Transport Channel Type not
not supported, CM not supported, Tx
diversity no longer supported, or Number of
UL codes not supported)
VS.IUB.RLFailInd.HW Number of RL failures on Iub interface due

to hardware failure (cause value: Hardware
failure)
VS.IUB.RLFailInd.SyncFail Number of RL failures on Iub interface due

to synchronization failure (cause value:
Synchronization failure)

BSC6900 UMTS
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a RADIO
LINK FAILURE INDICATION message from the NodeB, indicating that one or more radio
links (RLs) are not available due to a synchronization failure or unsupported configurations. In
this case, this counter is increased by one in the cell where the RL is unavailable.
Figure 1-670 RL failure procedure
Formula
None
Unit
None
Related Features
VS.IUB.RLFailInd WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
VS.IUB.RLFailInd.CfgUn- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

supp Connection and Radio
and Release
VS.IUB.RLFailInd.HW WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IUB.RLFailInd.SyncFail WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.16.3 Number of RLs Unsuccessfully Restored on Iub Interface due to No

Response
Counters
67180830 VS.IUB.RLFailNoRestore Number of Iub Interface

Radio Link Failures for Cell
(Synchronization Failure)
Description
This counter provides the number of radio links (RLs) that cannot be restored on the Iub interface
in a cell because the NodeB fails to send the RADIO LINK RESTORE INDICATION message.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC allocates
resources to a new RL and initiates an RL setup procedure, the RNC starts a timer to wait for
the RADIO LINK RESTORE INDICATION message from the NodeB. If the RNC does not
receive this message before the timer expires, this counter is increased by one in the cell where
the RL is to be restored.

BSC6900 UMTS
Figure 1-671 RL restore time out procedure
RADIO LINK FAILURE INDICATION message from the NodeB, the RNC starts a timer to
wait for the RADIO LINK RESTORE INDICATION message from the NodeB. If the RNC
does not receive the RADIO LINK RESTORE INDICATION message before the timer expires,
this counter is increased by one in the cell where the RL is to be restored.
Figure 1-672 RL restore time out procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IUB.RLFailNoRestore WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.16.4 Number of RLs Unsuccessfully Added on Iub Interface for Different

Causes
Counters
67180813 RLM.FailRLAddIub.CfgUn Number of Iub Interface

sup Radio Link Addition Failures
for Cell (Configuration
Unsupported)
67180812 RLM.FailRLAddIub.Cong Number of Iub Interface

Radio Link Addition Failures
for Cell (Congestion)
67180811 VS.SHO.FailRLAddIub.H Number of Iub Interface

W Radio Link Addition Failures
for Cell (Device Fault)
Description
The measurement counters provide the number of RLs unsuccessfully added on the Iub interface
in a cell for different causes.

BSC6900 UMTS
RLM.FailRLAddIub.CfgUnsup Number of RLs unsuccessfully added on Iub

interface due to configuration unsupported
(cause value: Combining not supported,
Requested Tx Diversity Mode not supported,
UL SF not supported, DL SF not supported,
or CM not supported)
RLM.FailRLAddIub.Cong Number of RLs unsuccessfully added on Iub

interface due to resources not available (cause
value: Cell not available, DL radio resources
not available, UL radio resources not
available, RL Already Activated/allocated,
Node B Resources Unavailable, Combining
Resources not available, Transport resource
unavailable, or Control processing overload)
VS.SHO.FailRLAddIub.HW Number of RLs unsuccessfully added on Iub

Interface due to hardware failure (cause
value: Hardware failure)
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends a RADIO
LINK ADDITION REQUEST message to the NodeB and waits for the response. If the RNC
receives a RADIO LINK ADDITION FAILURE message from the NodeB, it measures the
counters in the cell where the RL are unsuccessfully added for different causes.
Figure 1-673 RL addition procedure (failed operation)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
RLM.FailRLAddIub.CfgUn WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

sup Connection and Radio
and Release
RLM.FailRLAddIub.Cong WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.SHO.FailRLAddIub.H WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

W Connection and Radio
and Release
1.12.16.5 Number of RLs Unsuccessfully Synchronization Reconfigured on Iub

Counters
67180823 VS.IUB.FailRLRecfg.CfgU Number of Iub Interface

nsupp Radio Link Synchronous
Reconfiguration Failures for
Cell (Configuration
Unsupported)
67180822 VS.IUB.FailRLRecfg.Cong Number of Iub Interface

Radio Link Synchronous
Cell (Congestion)
67180821 VS.IUB.FailRLRecfg.HW Number of Iub Interface

Radio Link Synchronous
Cell (Device Fault)

BSC6900 UMTS
Description
The measurement counters provide the number of RLs unsuccessfully reconfigured on the Iub
interface in a cell for different causes.
VS.IUB.FailRLRecfg.CfgUnsupp Number of RLs unsuccessfully reconfigured

on Iub interface due to configuration
unsupported (cause value: UL SF not
supported, DL SF not supported, Downlink
Shared Channel Type not supported, Uplink
Shared Channel Type not supported, CM not
supported, Number of DL codes not
supported, or Number of UL codes not
supported)
VS.IUB.FailRLRecfg.Cong Number of RLs unsuccessfully reconfigured

on Iub interface due to resources not available
(cause value: Cell not available, DL radio
resources not available, UL radio resources
not available, RL Already Activated/
allocated, Node B Resources Unavailable,
Combining Resources not available,
Transport resource unavailable, or Control
processing overload)
VS.IUB.FailRLRecfg.HW Number of RLs unsuccessfully reconfigured

on Iub Interface due to hardware failure
(cause value: Hardware failure)
Measurement point
The measurement is triggered at point B as shown in the figure. The RNC sends a RADIO LINK
RECONFIGURATION PREPARE message to the NodeB and waits for the response. If the
RNC receives a RADIO LINK RECONFIGURATION FAILURE message from the NodeB, it
measures the counters in the cell according to different causes.

BSC6900 UMTS
Figure 1-674 Synchronized RL reconfiguration procedure (failed operation)
Formula
None
Unit
None
Related Features
VS.IUB.FailRLRecfg.CfgU WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

nsupp Connection and Radio
and Release
VS.IUB.FailRLRecfg.Cong WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IUB.FailRLRecfg.HW WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
1.12.16.6 Number of RLs Unsuccessfully Reconfigured on Iub Interface due to No

Response
Counters
67180824 VS.IUB.FailRLRecfg.NoRe Number of Iub Interface RLs

ply Unsuccessfully
Reconfigured Due to No
Response for Cell
Description
This measurement counter takes statistics of the number of RLs unsuccessfully reconfigured on
the Iub interface due to no response from the NodeB.
Measurement point
The measurement is triggered at point A as shown in the figure. The RNC sends a RADIO LINK
RECONFIGURATION PREPARE message to a NodeB and starts a timer to wait for the
response. If the RNC does not receive any response message from the NodeB upon expiry of
the timer, it measures the counter in the cell where the RL is requested to reconfigure.
Figure 1-675 Sync RL reconfiguration procedure (NoReply)
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IUB.FailRLRecfg.NoRe WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

ply Connection and Radio
and Release
1.12.16.7 Number of RLs Unsuccessfully Established on Iub Interface for Different

Causes
Counters
67180806 RLM.FailRLSetupIub.CfgU Number of Iub Interface

nsup Radio Link Setup Failures for
Cell (Configuration
Unsupported)
67180805 RLM.FailRLSetupIub.Cong Number of Iub Interface

Radio Link Setup Failures for
Cell (Congestion)
67180804 VS.IUB.FailRLSetup.HW Number of Iub Interface

Radio Link Setup Failures for
Cell (Device Fault)
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.

BSC6900 UMTS
RLM.FailRLSetupIub.CfgUnsup Number of RLs unsuccessfully established on

Iub Interface due to configuration
unsupported (cause value: Combining not
supported, Requested Tx Diversity Mode not
supported, Number of DL codes not
supported, Number of UL codes not
supported, UL SF not supported, DL SF not
supported, Dedicated Transport Channel
Type not supported, Downlink Shared
Channel Type not supported, Uplink Shared
Channel Type not supported, or CM not
supported)
RLM.FailRLSetupIub.Cong Number of RLs unsuccessfully established on

Iub Interface due to no resource available
(cause value: Cell not available, DL radio
resources not available, UL radio resources
not available, RL Already Activated/
allocated, Node B Resources Unavailable,
Combining Resources not available,
Transport resource unavailable, or Control
processing overload)
VS.IUB.FailRLSetup.HW Number of RLs unsuccessfully established on

Iub Interface due to hardware failure (cause
value: Hardware failure)
Measurement point
The measurement is triggered at point B as shown in the figure, 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.

BSC6900 UMTS
Figure 1-676 RL setup procedure (failed operation)
Formula
None
Unit
None
Related Features
RLM.FailRLSetupIub.CfgU WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

nsup Connection and Radio
and Release
RLM.FailRLSetupIub.Cong WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.IUB.FailRLSetup.HW WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
1.12.16.8 Number of RLs Requested to Reconfigure with Synchronization on Iub

Interface
Counters
67189775 VS.IUB.AttRLRecfg Number of Iub Interface RL

Reconfiguration Attempts
for Cell
Description
This measurement counter takes statistics of the number of RLs requested to reconfigure with
synchronization on the Iub interface in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a RADIO
LINK RECONFIGURATION PREPARE message to the NodeB. In this case, the RNC
measures the counter in the cell where the RLs are requested to reconfigure.
Figure 1-677 Synchronized RL reconfiguration procedure (successful operation)
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IUB.AttRLRecfg WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.16.9 Number of RLs Requested to Add on Iub Interface
Counters
67180808 VS.IUB.AttRLAdd Number of Iub Interface RL

Addition Requests for Cell
Description
The measurement counters provide the number of RLs requested to add on the Iub interface in
a cell.
Measurement point
The measurement is triggered at point A as shown in the figure. To add one or more RLs for a
NodeB communication context, the RNC shall initiate a RL addition procedure by sending a
RADIO LINK ADDITION REQUEST message to the NodeB. In this case, the RNC measures
the counter in the cell where the RLs are requested to add.

BSC6900 UMTS
Figure 1-678 RL addition procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.IUB.AttRLAdd WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.16.10 Number of RLs Requested to Delete on Iub Interface
Counters
67180815 VS.IUB.AttRLDel Number of Iub Interface RL

Deletion Requests for Cell

BSC6900 UMTS
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
VS.IUB.AttRLDel WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
1.12.16.11 Number of RLs Requested to Establish on Iub Interface
Counters
67180801 VS.IUB.AttRLSetup Number of Iub Interface RL

Establishment Requests for
Cell
Description
This measurement counter takes statistics of the number of RLs requested to establish on the
Iub interface in a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC needs to establish
mandatory resources for a new communication context in the NodeB and initiates a RL setup
procedure to the NodeB by sending a RADIO LINK SETUP REQUEST message. In this case,
the RNC measures the counter in the cell where the RLs are requested to establish.
Figure 1-680 RL setup procedure (successful operation)
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.IUB.AttRLSetup WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.16.12 Number of RLs Restored on Iub Interface
Counters
67180832 VS.IUB.RLRestore Number of Iub Interface RL

Restorations for Cell
Description
This measurement counter takes statistics of the number of RLs restored on the Iub interface in
a cell.
Measurement point
The measurement is triggered at point A as shown in the figure, when the Node B sends a RADIO
LINK RESTORE INDICATION message to the RNC, notifying that the RNC has obtained or
restored the synchronization of one or more uplinks on the Uu interface. In this case, the RNC
measures the counter in the cell where the RLs are restored.

BSC6900 UMTS
Figure 1-681 RL restoration procedure
Formula
None
Unit
None
Related Features
VS.IUB.RLRestore WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.16.13 Number of RLs Successfully Added on Iub Interface

BSC6900 UMTS
Counters
67180809 VS.IUB.SuccRLAdd Number of Iub Interface RLs

Successfully Added for Cell
Description
The measurement counters provide the number of RLs successfully added on the Iub interface
in a cell.
Measurement point
At point B as shown in the figure, the RNC sends a RADIO LINK ADDITION REQUEST
message to the NodeB and starts a timer to wait for a response. After receiving a RADIO LINK
ADDITION RESPONSE message from the NodeB, the RNC measures the counter in the cell
where the RLs are successfully added.
Figure 1-682 RL addition procedure (successful operation)
At point B as shown in the figure, the RNC sends the NodeB a RADIO LINK ADDITION
REQUEST message and starts a timer to wait for a response. If there are successfully added RLs
when the RNC receives a RADIO LINK ADDITION FAILURE message from the NodeB, the
RNC measures the counter in the cell where the RLs are successfully added.

BSC6900 UMTS
Figure 1-683 RL addition procedure (failed operation)
Formula
None
Unit
None
Related Features
VS.IUB.SuccRLAdd WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.16.14 Number of RLs Successfully Deleted on Iub Interface
Counters
67180816 VS.IUB.SuccRLDel Number of Iub Interface RLs

Successfully Deleted for Cell

BSC6900 UMTS
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
VS.IUB.SuccRLDel WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
1.12.16.15 Number of RLs Successfully Reconfigured with Synchronization on Iub

Interface
Counters
67180819 VS.IUB.SuccRLRecfg Number of Iub Interface RLs

Successfully
Synchronization
Reconfigured for Cell
Description
This measurement counter takes statistics of the number of RLs successfully reconfigured on
the Iub interface in a cell.
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends a RADIO
LINK RECONFIGURATION COMMIT message to the NodeB. In this case, the RNC measures
the counter in the cell where the RLs are successfully reconfigured.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IUB.SuccRLRecfg WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.16.16 Number of RLs Successfully Established on Iub Interface
Counters
67180802 VS.IUB.SuccRLSetup Number of Iub Interface RLs

Successfully Established for
Cell
Description
This measurement counter takes statistics of the number of RLs successfully established on Iub
interface in a cell.
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives a RADIO
LINK SETUP RESPONSE message from the NodeB after sending a RADIO LINK SETUP
REQUEST message to the NodeB. In this case, the RNC measures the counter in the cell where
the RLs are successfully established.

BSC6900 UMTS
Figure 1-686 Figure 7-33 RL setup procedure (successful operation)
The measurement is triggered at point A as shown in the figure, when the RNC sends a RADIO
LINK SETUP REQUEST message to the NodeB and starts a timer to wait for a response. If
there are successfully established RLs when the RNC receives a RADIO LINK SETUP
FAILURE message from the NodeB, the RNC measures the counter in the cell where the RLs
are successfully established.
Figure 1-687 RL setup procedure (failed operation)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.IUB.SuccRLSetup WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.16.17 Number of RLs Unsuccessfully Established on Iub Interface due to No

Response
Counters
67180838 VS.IUB.FailRLSetup.NoRe- Number of Iub Interface RLs

ply Unsuccessfully Established
Due to No Response for Cell
Description
The measurement counter provides the number of RLs unsuccessfully established on the Iub
interface due to no response from the NodeB.
Measurement point
The RNC sends a RADIO LINK SETUP REQUEST or RADIO LINK ADDITION REQUEST
message to the NodeB and starts a timer to wait for the response. If the RNC does not receive a
response upon expiry of the timer, it measures the counter in the cell where the RLs are
unsuccessfully established.

BSC6900 UMTS
Figure 1-688 RL setup procedure (failed operation)(no reply)
Formula
None
Unit
None
Related Features
VS.IUB.FailRLSetup.NoRe- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

ply Connection and Radio
and Release
1.12.17 Measurement related to LCS service per cell(LCS.CELL)
Overview
This function subset mainly measures the number of positioning results that exceeds the coverage
of UE reference cell through the UE ASSISTED AGPS, UE BASED AGPS, OTDOA, CELLID
+ RTT positioning methods.

BSC6900 UMTS
Counters
Description
67190670 VS.LCS.OutCellCo Number of Earlier than

ver.AgpsAss Positioning Results V900R011
Out of the Reference
Cell's Coverage in
Case of UE
ASSISTED AGPS
Method for Cell

ver.AgpsBas Positioning Results V900R011
Cell's Coverage in
Case of UE Based
AGPS Method for
Cell

ver.Otdoa Positioning Results V900R011
Cell's Coverage in
Case of OTDOA
Method for Cell

ver.CellIdRtt Positioning Results V900R011
Cell's Coverage in
Case of CELLID +
RTT Method for Cell
None
1.12.17.1 Number of Positioning Results Beyond Coverage of UE Reference Cell in

UE Assisted AGPS Method

BSC6900 UMTS
Counters
67190670 VS.LCS.OutCellCover.Ag- Number of Positioning

psAss Results Out of the Reference
Cell's Coverage in Case of
UE ASSISTED AGPS
Method for Cell
Description
This measurement item provides the number of positioning results that exceed the coverage of
UE reference cell through the UE 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
VS.LCS.OutCellCover.Ag- WRFD-020803 A-GPS Based LCS

psAss

UE-based AGPS Method
Counters
67190671 VS.LCS.OutCellCover.Agp Number of Positioning

sBas Results Out of the Reference
UE Based AGPS Method for
Cell

BSC6900 UMTS
Description
UE reference cell through the UE BASED AGPS method in a cell.
Measurement point
the coverage of UE reference cell and the current positioning method is UE BASED AGPS.
Formula
None
Unit
None
Related Features
VS.LCS.OutCellCover.Agp WRFD-020803 A-GPS Based LCS

sBas

OTDOA Method
Counters
67190672 VS.LCS.OutCellCover.Ot- Number of Positioning

doa Results Out of the Reference
OTDOA Method for Cell
Description
UE reference cell through the OTDOA method in a cell.

BSC6900 UMTS
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
VS.LCS.OutCellCover.Ot- WRFD-020802 OTDOA Based LCS

doa

CELLID + RTT method
Counters
67190673 VS.LCS.OutCellCover.Cel- Number of Positioning

lIdRtt Results Out of the Reference
CELLID + RTT Method for
Cell
Description
This measurement item provides the number of positioning results that exceeds the coverage of
UE reference cell through the CELLID + RTT method in a cell.
Measurement point
the coverage of UE reference cell and the current positioning method is CELLID + RTT.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.LCS.OutCellCover.Cel- WRFD-020801 Cell ID + RTT Function

lIdRtt Based LCS
1.12.18 MBMS Measurement per cell(MBMS.Cell)
Overview
This function subset is used to measure the number of setups and releases of the MBMS traffic.
Counters
Description
67194980 VS.MBMS.InterCe Number of Handover Earlier than

ll.PTPtoPTM.Att Requests from PTP V900R011
Cell to PTM Cell
67194981 VS.MBMS.RB.PTP Number of MBMS Earlier than

.AttEstab Service PTP Setup V900R011
Requests for Cell
67194982 VS.MBMS.RB.PTP Number of Earlier than

.SuccEstab Successful MBMS V900R011
Service PTP Setups
for Cell
67194983 VS.MBMS.RB.PTP Number of Earlier than

.Loss.Abnorm Abnormal MBMS V900R011
Service Releases in
PTP Mode for Cell
67194984 VS.MBMS.RB.PTP Number of Normal Earlier than

.Loss.Norm MBMS Service V900R011
Releases in PTP
Mode for Cell
67192130 VS.MBMS.MTCH Number of Earlier than

SetupSucc.Cell Successful MTCH V900R011
Setups for Cell

BSC6900 UMTS

Description
67192131 VS.MBMS.MTCH Number of MTCH Earlier than

SetupFail.Cell Setup Failures for V900R011
Cell
67192615 VS.MBMS.PTMto Number of Earlier than

PTP.Succ Successful V900R011
Transitions from
PTM to PTP for Cell
67192616 VS.MBMS.PTPtoP Number of Earlier than

TM.Succ Successful V900R011
Transitions from
PTP to PTM for Cell
67192617 VS.MBMS.PTPtoP Number of PTP to Earlier than

TM.Att PTM Transitions for V900R011
Cell
67204014 VS.MBMS.PTM.R Mean Number of Earlier than

B.Mean.Cell PTM RBs for Cell V900R011
67192620 VS.MBMS.PTM.R Maximum Number Earlier than

B.Max.Cell of PTM RBs for Cell V900R011
67192621 VS.MBMS.RB.PT Number of PTM Earlier than

M.AttEstab Setup Requests for V900R011
Cell
67192622 VS.MBMS.RB.PT Number of Earlier than

M.SuccEstab Successful PTM V900R011
Setups for Cell
67204225 VS.MBMS.PTP.UE Mean Number of Earlier than

.Channel0.Mean.C PTP Users of MBMS V900R011
ell Channel 0 for Cell
67204226 VS.MBMS.PTM.U Mean Number of Earlier than

E.Channel0.Mean. PTM Users of V900R011
Cell MBMS Channel 0
for Cell


Cell MBMS Channel 1
for Cell

BSC6900 UMTS

Description


Cell MBMS Channel 2
for Cell


Cell MBMS Channel 3
for Cell


Cell MBMS Channel 4
for Cell
67204235 VS.MBMS.PTM.C Duration of MBMS Earlier than

hannel0.Dur.Cell Channel 0 in PTM V900R011
Mode for Cell
67204236 VS.MBMS.PTP.Ch Duration of MBMS Earlier than

annel0.Dur.Cell Channel 0 in PTP V900R011
Mode for Cell

Mode for Cell

Mode for Cell

Mode for Cell

Mode for Cell

BSC6900 UMTS

Description

Mode for Cell

Mode for Cell

Mode for Cell

Mode for Cell
None
1.12.18.1 Number of Releases of PTP MBMS Services because the new best cell is
on PTM mode
Counters
67194980 VS.MBMS.InterCell.PTPto Number of Handover

PTM.Att Requests from PTP Cell to
PTM Cell
Description
This measurement item provides the number of releases of PTP MBMS Services because the
new best cell is on PTM mode.
Measurement point
After a PTP RB is set up and there are several cells in the active set for UE, the release of the
RB might be triggered if the best cell changes and the new best cell is on PTM mode. At that
time, the RNC measures the item.
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.MBMS.InterCell.PTPto WRFD-010660 MBMS Phase 2

PTM.Att
1.12.18.2 Number of Requests for PTP MBMS Setup
Counters
67194981 VS.MBMS.RB.PTP.AttEs- Number of MBMS Service

tab PTP Setup Requests for Cell
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
VS.MBMS.RB.PTP.AttEs- WRFD-010660 MBMS Phase 2

tab

BSC6900 UMTS
1.12.18.3 Number of Successful PTP MBMS Setups
Counters
67194982 VS.MBMS.RB.PTP.Suc- Number of Successful

cEstab MBMS Service PTP Setups
for Cell
Description
This measurement item provides the number of successful setups of Point-to-Point (PTP) MBMS
services in a cell.
Measurement point
After the UE initiates an MBMS setup request, the RNC initiates PTP RB setup based on the
request of the UE. When the PTP RB is successfully set up, the RNC measures the item. If the
UE applies for more than one service, the RNC measures the item once for each service.
Formula
None
Unit
None
Related Features
VS.MBMS.RB.PTP.Suc- WRFD-010660 MBMS Phase 2

cEstab
1.12.18.4 Number of Abnormal Releases of PTP MBMS Services for Different

Causes
Counters
67194983 VS.MBMS.RB.PTP.Loss.A Number of Abnormal

bnorm MBMS Service Releases in
PTP Mode for Cell

BSC6900 UMTS
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
VS.MBMS.RB.PTP.Loss.A WRFD-010660 MBMS Phase 2

bnorm
1.12.18.5 Number of Normal Releases of PTP MBMS Services
Counters
67194984 VS.MBMS.RB.PTP.Loss.N Number of Normal MBMS

orm Service Releases in PTP
Mode for Cell
Description
This measurement item provides the number of normal releases of PTP MBMS services in a
cell.
Measurement point
After a PTP RB is set up, the RNC measures this item in the following conditions: the UE initiates
the RB release, the RNC initiates the RB release for transition from PTP to PTM, the RB release
is performed because the SGSN initiates MBMS SESSION STOP, and the RNC initiates the
RB release because of relocation.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.MBMS.RB.PTP.Loss.N WRFD-010660 MBMS Phase 2

orm
1.12.18.6 Number of Successful Setups of MBMS(PTM) Traffic Channel
Counters
67192130 VS.MBMS.MTCHSetupSuc Number of Successful

c.Cell MTCH Setups for Cell
Description
This measurement item provides the number of successful attempts to set up the MBMS traffic
channel in a cell.
Measurement point
As shown in Figure1,the RNC measures this item when a MBMS traffic channel of the cell is
successfully set up.

BSC6900 UMTS
Figure 1-689 MBMS traffic channel set up procedure
Formula
None
Unit
None
Related Features
VS.MBMS.MTCHSetupSuc WRFD-010616 MBMS Introduction

c.Cell Package
1.12.18.7 Number of Unsuccessful Setups of MBMS(PTM) Traffic Channel
Counters
67192131 VS.MBMS.MTCHSetupFail Number of MTCH Setup

.Cell Failures for Cell

BSC6900 UMTS
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
VS.MBMS.MTCHSetupFail WRFD-010616 MBMS Introduction

.Cell Package
1.12.18.8 Number of successful PTM to PTP transition in a cell
Counters
67192615 VS.MBMS.PTMtoPTP.Succ Number of Successful

Transitions from PTM to
PTP for Cell
Description
This measurement item provides the number of successful transition from PTM MBMS service
to PTP MBMS service in a cell.
Measurement point
After a MBMS service is transited from PTM mode to PTP mode and a PTP MBMS RB is
successful set up, the RNC measures the item.

BSC6900 UMTS
Figure 1-690 transmission of MBMS service from PTM to PTP
Formula
None
Unit
None
Related Features
VS.MBMS.PTMtoPTP.Succ WRFD-01066001 MBMS Enhanced Broadcast

Mode
1.12.18.9 Number of Successful Transitions from PTP MBMS Service to PTM

MBMS Service

BSC6900 UMTS
Counters
67192616 VS.MBMS.PTPtoPTM.Succ Number of Successful

Transitions from PTP to
PTM for Cell
Description
This measurement item provides the number of successful transition from PTP MBMS service
to PTM MBMS service in a cell.
Measurement point
After a MBMS service is transited from PTP mode to PTM mode and a PTM MBMS RB is
successful set up, the RNC measures the item.
Figure 1-691 Transmission of MBMS service from PTP to PTM
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.MBMS.PTPtoPTM.Succ WRFD-01066001 MBMS Enhanced Broadcast

Mode
1.12.18.10 Number of Transitions from PTP MBMS Service to PTM MBMS Service
Counters
67192617 VS.MBMS.PTPtoPTM.Att Number of PTP to PTM

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
VS.MBMS.PTPtoPTM.Att WRFD-01066001 MBMS Enhanced Broadcast

Mode
1.12.18.11 Number of RBs in PTM MBMS Service

BSC6900 UMTS
Counters
67204014 VS.MBMS.PTM.RB.Mean. Mean Number of PTM RBs

Cell for Cell
67192620 VS.MBMS.PTM.RB.Max.C Maximum Number of PTM

ell RBs for Cell
Description
These counters provide the mean number and maximum number of PTM MBMS RBs in a cell.
Measurement point
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
VS.MBMS.PTM.RB.Mean. WRFD-01061601 MBMS Broadcast Mode

Cell
VS.MBMS.PTM.RB.Max.C WRFD-01061601 MBMS Broadcast Mode

ell
1.12.18.12 Number of PTM setup request
Counters
67192621 VS.MBMS.RB.PTM.AttEs- Number of PTM Setup

tab Requests for Cell

BSC6900 UMTS
Description
This measurement item provides the number of setups of PTM MBMS service in a cell.
Measurement point
When the RNC initiates the setup of PTM MBMS service ,the RNC measures the item.
Figure 1-692 PTM MBMS service setup procedure
Formula
None
Unit
None
Related Features
VS.MBMS.RB.PTM.AttEs- WRFD-01061601 MBMS Broadcast Mode

tab

BSC6900 UMTS
1.12.18.13 Number of Successful Setups of PTM MBMS Service
Counters
67192622 VS.MBMS.RB.PTM.Suc- Number of Successful PTM

cEstab Setups for Cell
Description
This measurement item provides the number of successful setups of PTM MBMS RB in a cell.
Measurement point
When the RB of PTM MBMS service is successful set up ,the RNC measures the item.
Formula
None
Unit
None
Related Features
VS.MBMS.RB.PTM.Suc- WRFD-01061601 MBMS Broadcast Mode

cEstab
1.12.18.14 Mean number of PTP users in a cell of MBMS Channel
Counters
67204225 VS.MBMS.PTP.UE.Channe Mean Number of PTP Users

l0.Mean.Cell of MBMS Channel 0 for Cell



BSC6900 UMTS


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
VS.MBMS.PTP.UE.Channe WRFD-010665 MBMS Channel Audience

l0.Mean.Cell Rating Statistics




1.12.18.15 Mean number of PTM users in a cell of MBMS Channel

BSC6900 UMTS
Counters
67204226 VS.MBMS.PTM.UE.Chann Mean Number of PTM Users

el0.Mean.Cell of MBMS Channel 0 for Cell




Description
The previous measurement counter provides the mean number of UEs that subscribe to MBMS
channel in PTM mode in a cell.
Measurement point
If the MBMS channel is in PTM mode, the number of cell_MBMS UEs is reported when a
connected UE orders or releases the MBMS program in the cell. When the MBMS channel
switches from PTP to PTM, the number of connected UEs that currently order the program in
the cell is reported. When the MBMS channel switches from PTM to PTP, the number of UEs
that order the program in PTM mode is reported as 0.
Formula
None
Unit
None
Related Features
VS.MBMS.PTM.UE.Chann WRFD-010665 MBMS Channel Audience

el0.Mean.Cell Rating Statistics


BSC6900 UMTS



1.12.18.16 A PTM Channel Duration in a cell MBMS service Channel
Counters
67204235 VS.MBMS.PTM.Channel0. Duration of MBMS Channel

Dur.Cell 0 in PTM Mode for Cell




Description
The previous measurement counter provides the duration in which MBMS channel is in PTM
mode.
Measurement point
When the MBMS channel is initially decided to be in PTM mode or switches from PTP to PTM,
the system records the time as T1. When the MBMS channel stops or switches to PTP, the system
records the time as T2. The difference between T1 and T2 indicates a duration in which the
MBMS channel is in PTM mode. Assume that T is the difference between T1 and T2. The sum
of all the Ts in the measurement period equals the total duration in which the MBMS channel
is in PTM mode in the measurement period.
Formula
None

BSC6900 UMTS
Unit
s
Related Features
VS.MBMS.PTM.Channel0. WRFD-010665 MBMS Channel Audience

Dur.Cell Rating Statistics




1.12.18.17 A PTP Channel Duration in a cell MBMS service Channel
Counters
67204236 VS.MBMS.PTP.Channel0.D Duration of MBMS Channel

ur.Cell 0 in PTP Mode for Cell




Description
The previous measurement counter provides the duration in which MBMS channel is in PTP
mode.

BSC6900 UMTS
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
VS.MBMS.PTP.Channel0.D WRFD-010665 MBMS Channel Audience

ur.Cell Rating Statistics




1.12.19 RRC Reporting Measurement per cell(MEAR.Report.Cell)
Overview
The RRC measurement reports include the following events: Events 1A, 1B, 1C, 1D related to
intra-frequency measurement. Events 2D and 2F related to active set measurement. Events 4A
and 4B related to traffic measurement.

BSC6900 UMTS
Counters
Description
67180609 VS.RRC.MrRpt.1A Number of Event 1A Earlier than

Measurement V900R011
Reports for Cell
67180610 VS.RRC.MrRpt.1B Number of Event 1B Earlier than

Reports for Cell
67180611 VS.RRC.MrRpt.1C Number of Event 1C Earlier than

Reports for Cell
67180612 VS.RRC.MrRpt.1D Number of Event 1D Earlier than

Reports for Cell
67180613 VS.RRC.MrRpt.2D Number of Event 2D Earlier than

Reports for Cell
67180614 VS.RRC.MrRpt.2F Number of Event 2F Earlier than

Reports for Cell
67180615 VS.RRC.MrRpt.4A Number of Uplink Earlier than

Event 4A V900R011
Measurement
Reports for Cell
67180616 VS.RRC.MrRpt.4B Number of Uplink Earlier than

Event 4B V900R011
Measurement
Reports for Cell
67192652 VS.Utran.MrRpt. Number of Downlink Earlier than

4A Event 4A V900R011
Measurement
Reports for Cell
67192653 VS.Utran.MrRpt. Number of Downlink Earlier than

4B Event 4B V900R011
Measurement
Reports for Cell
73440131 VS.RRC.MrRpt.S Average RSCP for V900R012

HO.RSCP Cell
73440132 VS.RRC.MrRpt.S Average Ec/No for V900R012

HO.EcNo Cell

BSC6900 UMTS
None
1.12.19.1 Number of Event 1A Measurement Reports
Counters
67180609 VS.RRC.MrRpt.1A Number of Event 1A

Measurement Reports for
Cell
Description
This measurement item provides the number of event 1A measurement reports about neighboring
cells from UEs to the RNC in a cell.
Measurement point
MEASUREMENT REPORT message from the UE with the event type as 1A and the
measurement object as neighboring cells. In this case, the RNC measures the item in the best
cell that the UE camps on.
Figure 1-693 Measurement reporting procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RRC.MrRpt.1A WRFD-020202 Intra RNC Soft Handover

1.12.19.2 Number of Event 1B Measurement Reports
Counters
67180610 VS.RRC.MrRpt.1B Number of Event 1B

Cell
Description
This measurement item provides the number of event 1B measurement reports about neighboring
Measurement point
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RRC.MrRpt.1B WRFD-020202 Intra RNC Soft Handover

1.12.19.3 Number of Event 1C Measurement Reports
Counters
67180611 VS.RRC.MrRpt.1C Number of Event 1C

Cell

BSC6900 UMTS
Description
This measurement item provide the number of event 1C measurement reports about neighboring
Measurement point
MEASUREMENT REPORT message from the UE with the event type as 1C and the
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RRC.MrRpt.1C WRFD-020202 Intra RNC Soft Handover

1.12.19.4 Number of Event 1D Measurement Reports
Counters
67180612 VS.RRC.MrRpt.1D Number of Event 1D

Cell
Description
This measurement item provides the number of event 1D measurement reports about neighboring
Measurement point
MEASUREMENT REPORT message from the UE with the event type as 1D and the

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RRC.MrRpt.1D WRFD-020202 Intra RNC Soft Handover

1.12.19.5 Number of Event 2D Measurement Reports
Counters
67180613 VS.RRC.MrRpt.2D Number of Event 2D

Cell
Description
This measurement item provides the number of event 2D measurement reports about cells in the
active set from UEs to the RNC in a cell.
Measurement point
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

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RRC.MrRpt.2D WRFD-020302 Inter Frequency Hard

Coverage
1.12.19.6 Number of Event 2F Measurement Reports

BSC6900 UMTS
Counters
67180614 VS.RRC.MrRpt.2F Number of Event 2F

Cell
Description
This measurement item provides the number of event 2F measurement reports about cells in the
Measurement point
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
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.RRC.MrRpt.2F WRFD-020302 Inter Frequency Hard

Coverage
1.12.19.7 Number of Uplink Event 4A Measurement Reports
Counters
67180615 VS.RRC.MrRpt.4A Number of Uplink Event 4A

Cell
Description
This measurement item provides the number of event 4A measurement reports about cells in the
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RRC.MrRpt.4A WRFD-021101 Dynamic Channel

(DCCC)
1.12.19.8 Number of Uplink Event 4B Measurement Reports

BSC6900 UMTS
Counters
67180616 VS.RRC.MrRpt.4B Number of Uplink Event 4B

Cell
Description
This measurement item provides the number of event 4B measurement reports about cells in the
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

BSC6900 UMTS
Unit
None
Related Features
VS.RRC.MrRpt.4B WRFD-021101 Dynamic Channel

(DCCC)
1.12.19.9 Number of Downlink Event 4A Measurement Reports
Counters
67192652 VS.Utran.MrRpt.4A Number of Downlink Event

4A Measurement Reports for
Cell
Description
This measurement item provides the number of event 4A measurement reports about DL traffic
of the UE from the MACD to the RNC in a cell.
Measurement point
When the RNC receives a Measurement Report message from L2 to L3, if the event type of the
message is 4A and the measurement object is DL traffic of the UE, the RNC measures the item
in the best cell that the UE camps on.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.Utran.MrRpt.4A WRFD-021101 Dynamic Channel

(DCCC)
1.12.19.10 Number of Downlink Event 4B Measurement Reports
Counters
67192653 VS.Utran.MrRpt.4B Number of Downlink Event

4B Measurement Reports for
Cell
Description
This measurement item provides the number of event 4B measurement reports about DL traffic
of the UE from the MACD to the RNC in a cell.
Measurement point
When the RNC receives a Measurement Report message from L2 to L3, if the event type of the
message is 4B and the measurement object is the DL traffic of the UE, the RNC measures the
item in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
VS.Utran.MrRpt.4B WRFD-021101 Dynamic Channel

(DCCC)

BSC6900 UMTS
1.12.19.11 Average RSCP for Cell
Counters
73440131 VS.RRC.MrRpt.SHO.RSCP Average RSCP for Cell
specific formulas.
73422195 VS.MrRpt.Cum.SHO Number of 1A, 1B and 1C

Measure Report from UE
73422194 VS.RSCP.Cum.SHO RSCPCum
Description
This counter provides the average received signal code power (RSCP) of the common pilot
channel (CPICH) reported by UEs in a cell in measurement reports triggered by event 1A, 1B,
or 1C.
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC receives
from a UE a MEASUREMENT REPORT message with the event type being 1A, 1B, or 1C.
The RNC measures the total number of event 1A, 1B, or 1C measurement reports and the total
CPICH RSCP of the cell with the best signal quality in the active set of the UEs. At the end of
each measurement period, this counter is calculated by dividing the total CPICH RSCP by the
total number. Note that this counter is measured in the cell in the active set.

BSC6900 UMTS
Figure 1-701 UE sends an event 1A, 1B, or 1C measurement report
Formula
VS.RRC.MrRpt.SHO.RSCP = [VS.RSCP.Cum.SHO]/[VS.MrRpt.Cum.SHO]
Unit
None
Related Features
VS.RRC.MrRpt.SHO.RSCP WRFD-020201 Intra Node B Softer

WRFD-020203 Intra RNC Soft Handover

1.12.19.12 Average Ec/No for Cell

BSC6900 UMTS
Counters
73440132 VS.RRC.MrRpt.SHO.EcNo Average Ec/No for Cell
specific formulas.
73422196 VS.EcNo.Cum.SHO EcNoCum
73422197 VS.EcNo.MrRpt.Cum.SHO VS.EcNo.MrRpt.Cum.SHO
Description
This counter provides the average Ec/No of the common pilot channel (CPICH) reported by UEs
in a cell in measurement reports triggered by event 1A, 1B, or 1C. Ec/No refers to the ratio of
received energy per chip to noise spectral density
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC receives
from a UE a MEASUREMENT REPORT message with the event type being 1A, 1B, or 1C.
The RNC measures the total number of event 1A, 1B, or 1C measurement reports and the total
CPICH Ec/No of the cell with the best signal quality in the active set of the UEs. At the end of
each measurement period, this counter is calculated by dividing the total CPICH Ec/No by the
total number. Note that this counter is measured in the cell in the active set.
Figure 1-702 UE sends an event 1A, 1B, or 1C measurement report

BSC6900 UMTS
Formula
VS.RRC.MrRpt.SHO.EcNo = [VS.EcNo.Cum.SHO]/[VS.EcNo.MrRpt.Cum.SHO]
Unit
dB
Related Features
VS.RRC.MrRpt.SHO.EcNo WRFD-020201 Intra Node B Softer

WRFD-020203 Intra RNC Soft Handover

1.12.20 Measurement related to Paging per cell(PAGE.CELL)
Overview
This function subset mainly measures the number of paging losses due to congestion and the
number of paging times in a cell.
If the paged UE is in idle mode, the CELL_PCH state, or URA_PCH state, the RNC sends a
PAGING TYPE 1 message on the Paging Control Channel (PCCH) to the cells in the paging
area. If the UE is in the CELL_PCH state and both the network and the UE support EPCH, the
RNC sends a PAGING TYPE 2 message to the cells in the paging area.
Counters
Description
67190472 VS.RRC.Paging1.L Number of Paging Earlier than

oss.PCHCong.Cell Messages Discarded V900R011
Due to PCH
Congestion for Cell
67190473 VS.UTRAN.AttPag Number of Paging Earlier than

ing1 Messages Sent by V900R011
RNC for Cell
73422072 VS.RRC.Paging1.P Number of V900R012

CHCong.CSPreem Preemptions by CS
ptAtt Paging due to PCH
Congestion per Cell

BSC6900 UMTS

Description

CHCong.CSPreem Successful
ptSucc Preemptions by CS
Paging due to PCH
Congestion per Cell
73424293 VS.Paging1.Att1.U Number of Level-1 V900R014

RA.RealTime.Cell Paging Attempts for
UEs Processing
Real-Time Services
in the URA_PCH
State for Cell
73424294 VS.Paging1.Succ1. Number of V900R014

URA.RealTime.Cel Successful Level-1
l Paging Attempts for
UEs Processing
Real-Time Services
in the URA_PCH
State for Cell
73424295 VS.Paging1.Att1.U Number of Level-1 V900R014

RA.NoneRealTime. Paging Attempts for
Cell UEs Processing Non-
Real-Time Services
in the URA_PCH
State for Cell
73424296 VS.Paging1.Succ1. Number of V900R014

URA.NoneRealTim Successful Level-1
e.Cell Paging Attempts for
UEs Processing Non-
Real-Time Services
in the URA_PCH
State for Cell
73424297 VS.Paging1.TotalS Number of V900R014

ucc.URA.RealTime Successful Layered
.Cell Paging Attempts for
UEs Processing
Real-Time Services
in the URA_PCH
State for Cell

BSC6900 UMTS

Description
73424298 VS.Paging1.TotalS Number of V900R014

ucc.URA.NoneReal Successful Layered
Time.Cell Paging Attempts for
UEs Processing Non-
Real-Time Services
in the URA_PCH
State for Cell
73394912 VS.UTRAN.Paging Number of PAGING V900R014

1.Att.UraPCH TYPE 1 Messages
Sent by the RNC to
UEs in the
URA_PCH State for
Cell
73394913 VS.UTRAN.Paging Number of CS V900R014

1.Att.Idle.CS PAGING TYPE 1
Messages Sent by the
RNC to UEs in the
Idle State for Cell
73394914 VS.UTRAN.Paging Number of PS V900R014

1.Att.Idle.PS PAGING TYPE 1
Messages Sent by the
RNC to UEs in the
Idle State for Cell
73425838 VS.Paging1.Att1.Id Number of Level-1 V900R015

le.RealTime.Cell Paging Attempts for
UEs Performing
Real-Time Services
in Idle Mode for Cell
73425839 VS.Paging1.Succ1.I Number of V900R015

dle.RealTime.Cell Successful Level-1
Paging Attempts for
UEs Performing
Real-Time Services
in Idle Mode for Cell
73425840 VS.Paging1.Att1.Id Number of Level-1 V900R015

le.NoneRealTime.C Paging Attempts for
ell UEs Performing
Non-Real-Time
Services in Idle
Mode for Cell

BSC6900 UMTS

Description
73425841 VS.Paging1.Succ1.I Number of V900R015

dle.NoneRealTime. Successful Level-1
Cell Paging Attempts for
UEs Performing
Non-Real-Time
Services in Idle
Mode for Cell
73426165 VS.RRC.Paging1.P Number of Times a V900R015

CHCong.SMSPree UE Processing SMS
mptAtt services Attempts to
Preempt Resources
to Be Allocated to
Other UEs When the
PCH Is Congested
for Cell

CHCong.SMSPree Successful
mptSucc Preemptions by SMS
Paging due to PCH
Congestion per Cell
73426313 VS.UTRAN.Paging Number of ETWS- V900R015

1.Att.Etws related PAGING
TYPE 1 Messages
Sent in a Cell
None
1.12.20.1 Number of Paging Losses due to PCH Congestion
Counters
67190472 VS.RRC.Paging1.Loss.PCH Number of Paging Messages

Cong.Cell Discarded Due to PCH
Congestion for Cell
Description
This counter provides the number of losses of PAGING TYPE 1 message due to PCH congestion
in a cell.

BSC6900 UMTS
Measurement point
The measurement is triggered when the RNC discards a paging message due to PCH congestion.
Formula
None
Unit
None
Related Features
VS.RRC.Paging1.Loss.PCH WRFD-010301 Paging UE in Idle,

Cong.Cell CELL_PCH, URA_PCH
State (Type 1)
1.12.20.2 Number of Paging Type 1 Messages
Counters
67190473 VS.UTRAN.AttPaging1 Number of Paging Messages

Sent by RNC for Cell
Description
This counter provides the number of paging messages of PAGING TYPE 1 sent by the RNC in
a cell. However, the scenario where the RNC sends such paging messages due to a modification
in the system information is not counted.
Measurement point
The measurement is triggered at point B as shown in the figure when the RNC sends a message
of PAGING TYPE 1. This counter also includes the number of PAGING TYPE 1 messages
retransmitted by the RNC.

BSC6900 UMTS
Figure 1-703 Sending Procedure of PAGING TYPE 1
Formula
None
Unit
None
Related Features
VS.UTRAN.AttPaging1 WRFD-010301 Paging UE in Idle,

CELL_PCH, URA_PCH
State (Type 1)
1.12.20.3 Number of Preemptions by CS Paging due to PCH Congestion per Cell
Counters
73422072 VS.RRC.Paging1.PCHCong Number of Preemptions by

.CSPreemptAtt CS Paging due to PCH
Congestion per Cell
Description
This counter provides the number of times that CS conversational paging preempts the resources
of other paging due to PCH congestion in a cell.

BSC6900 UMTS
Measurement point
This counter is incremented by one at point A as shown in the figure each time the CS
conversational paging preempts the resources of other paging (including CN originated
streaming, interactive, background and SMS paging), due to PCH congestion.
Formula
None
Unit
None
Related Features
VS.RRC.Paging1.PCHCong WRFD-010301 Paging UE in Idle,

.CSPreemptAtt CELL_PCH, URA_PCH
State (Type 1)
1.12.20.4 Number of Successful Preemptions by CS Paging due to PCH Congestion

per Cell
Counters
73422073 VS.RRC.Paging1.PCHCong Number of Successful

.CSPreemptSucc Preemptions by CS Paging
due to PCH Congestion per
Cell

BSC6900 UMTS
Description
This counter provides the number of times that CS conversational paging successfully preempts
the resources of other paging due to PCH congestion in a cell.
Measurement point
This counter is incremented by one at point B as shown in the figure each time the CS
conversational paging successfully preempts the resources of other paging (including CN
originated streaming, interactive, background and SMS paging) due to PCH congestion and is
successfully sent.
Formula
None
Unit
None
Related Features

.CSPreemptSucc CELL_PCH, URA_PCH
State (Type 1)
1.12.20.5 Number of Level-1 Paging Attempts for UEs Processing Real-Time or Non-
Real-Time Services in the URA_PCH State

BSC6900 UMTS
Counters
73424293 VS.Paging1.Att1.URA.Real Number of Level-1 Paging

Time.Cell Attempts for UEs Processing
Real-Time Services in the
73424295 VS.Paging1.Att1.URA.Non Number of Level-1 Paging

eRealTime.Cell Attempts for UEs Processing
Non-Real-Time Services in
the URA_PCH State for Cell
Description
These counters measure the number of level-1 paging attempts for UEs processing real-time or
non-real-time services in the URA_PCH state in the cells on which the UEs camped recently.
These counters does not measure the number of PAGING TYPE 1 messages that the RNC sent
due to system information modifications or the number of retransmitted paging messages.
NOTE:Real-time services are classified into CS conversational services, PS conversational
services, and streaming services, without including push to talk (PTT) services. Non-real-time
services are classified into PS interactive services, PS background services, and signaling radio
bearer (SRB) services.
Measurement point
The measurement is triggered at point A as shown in the figure when the RNC sends PAGING
TYPE 1 messages to the cells on which the UEs in the URA_PCH state camped recently and to
their neighboring cells (level-1 paging).
Figure 1-706 Procedure of PAGING TYPE 1

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.Paging1.Att1.URA.Real WRFD-140206 Layered Paging in

Time.Cell URA_PCH
VS.Paging1.Att1.URA.Non WRFD-140206 Layered Paging in

eRealTime.Cell URA_PCH
1.12.20.6 Number of Successful Level-1 Paging Attempts for UEs Processing Real-
Time or Non-Real-Time Services in the URA_PCH State
Counters
73424294 VS.Paging1.Succ1.URA.Re Number of Successful

alTime.Cell Level-1 Paging Attempts for
UEs Processing Real-Time
Services in the URA_PCH
State for Cell
73424296 VS.Paging1.Succ1.URA.No Number of Successful

neRealTime.Cell Level-1 Paging Attempts for
UEs Processing Non-Real-
Time Services in the
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

BSC6900 UMTS
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
VS.Paging1.Succ1.URA.Re WRFD-140206 Layered Paging in

alTime.Cell URA_PCH
VS.Paging1.Succ1.URA.No WRFD-140206 Layered Paging in

neRealTime.Cell URA_PCH
1.12.20.7 Number of Successful Layered Paging Attempts for UEs Processing Real-
Time or Non-Real-Time Services in the URA_PCH State

BSC6900 UMTS
Counters
73424297 VS.Paging1.TotalSucc.URA Number of Successful

.RealTime.Cell Layered Paging Attempts for
UEs Processing Real-Time
Services in the URA_PCH
State for Cell
73424298 VS.Paging1.TotalSucc.URA Number of Successful

.NoneRealTime.Cell Layered Paging Attempts for
UEs Processing Non-Real-
Time Services in the
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.Paging1.TotalSucc.URA WRFD-140206 Layered Paging in

.RealTime.Cell URA_PCH
VS.Paging1.TotalSucc.URA WRFD-140206 Layered Paging in

.NoneRealTime.Cell URA_PCH
1.12.20.8 Number of PAGING TYPE 1 Messages Sent by the RNC to UEs in the
URA_PCH State
Counters
73394912 VS.UTRAN.Paging1.Att.Ur Number of PAGING TYPE 1

aPCH Messages Sent by the RNC to
UEs in the URA_PCH State
for Cell
Description
This counter measures the number of PAGING TYPE 1 messages sent by the RNC to UEs in
the URA_PCH state in a cell.
Measurement point
This counter is incremented at point B as shown in the figure by one each time the RNC sends
a PAGING TYPE 1 message to a UE in the URA_PCH state in the cell. This counter also includes
the retransmitted PAGING TYPE 1 messages.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.UTRAN.Paging1.Att.Ur WRFD-010301 Paging UE in Idle,

aPCH CELL_PCH, URA_PCH
State (Type 1)
1.12.20.9 Number of CS PAGING TYPE 1 Messages Sent by the RNC to UEs in the
Idle State
Counters
73394913 VS.UTRAN.Paging1.Att.Idl Number of CS PAGING

e.CS TYPE 1 Messages Sent by
the RNC to UEs in the Idle
State for Cell

BSC6900 UMTS
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
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
VS.UTRAN.Paging1.Att.Idl WRFD-010301 Paging UE in Idle,

e.CS CELL_PCH, URA_PCH
State (Type 1)
1.12.20.10 Number of PS PAGING TYPE 1 Messages Sent by the RNC to UEs in the
Idle State

BSC6900 UMTS
Counters
73394914 VS.UTRAN.Paging1.Att.Idl Number of PS PAGING

e.PS TYPE 1 Messages Sent by
the RNC to UEs in the Idle
State for Cell
Description
This counter measures the number of PAGING TYPE 1 messages sent by the RNC in the PS
domain to UEs in the idle state in a cell.
Measurement point
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

BSC6900 UMTS
Related Features
VS.UTRAN.Paging1.Att.Idl WRFD-010301 Paging UE in Idle,

e.PS CELL_PCH, URA_PCH
State (Type 1)
1.12.20.11 Number of Level-1 Paging Attempts for UEs Performing Real-Time or

Non-Real-Time Services in Idle Mode for Cell
Counters
73425838 VS.Paging1.Att1.Idle.RealT Number of Level-1 Paging

ime.Cell Attempts for UEs Performing
Real-Time Services in Idle
Mode for Cell
73425840 VS.Paging1.Att1.Idle.None Number of Level-1 Paging

RealTime.Cell Attempts for UEs Performing
Non-Real-Time Services in
Idle Mode for Cell
Description
These counters measure the number of level-1 paging attempts for UEs performing real-time or
non-real-time services in idle mode in the last camped-on cell.They do not measure the number
of PAGING TYPE 1 messages that the RNC sent due to system information modifications or
the number of retransmitted paging messages. Note that real-time services are classified into CS
conversational services, PS conversational services, and streaming services. Push to talk (PTT)
services are not included. Non-real-time services are classified into PS interactive services, PS
background services, and signaling radio bearer (SRB) services.
Measurement point
The measurement is triggered at point A shown in the figure when the RNC sends PAGING
TYPE 1 messages to the last cell that a UE is camped on and to its neighboring cells. If the UE
is performing real-time services, the VS.Paging1.Att1.Idle.RealTime.Cell counter is measured
in the last camped-on cell. If the UE is performing non-real-time services, the
VS.Paging1.Att1.Idle.NoneRealTime.Cell counter is measured in the last camped-on cell.

BSC6900 UMTS
Figure 1-712 How a UE in idle mode responds to the PAGING TYPE 1 message
Formula
None
Unit
None
Related Features
VS.Paging1.Att1.Idle.RealT WRFD-150205 Layered Paging in Idle Mode

ime.Cell
VS.Paging1.Att1.Idle.None WRFD-150205 Layered Paging in Idle Mode

RealTime.Cell
1.12.20.12 Number of Successful Level-1 Paging Attempts for UEs Performing Real-
Time or Non-Real-Time Services in Idle Mode for Cell
Counters
73425839 VS.Paging1.Succ1.Idle.Real Number of Successful

Time.Cell Level-1 Paging Attempts for
UEs Performing Real-Time
Services in Idle Mode for
Cell

BSC6900 UMTS
73425841 VS.Paging1.Succ1.Idle.Non Number of Successful

eRealTime.Cell Level-1 Paging Attempts for
UEs Performing Non-Real-
Time Services in Idle Mode
for Cell
Description
These counters measure the number of successful level-1 paging attempts for UEs performing
real-time or non-real-time services in idle mode in the last camped-on cell.
Measurement point
The measurement is triggered at point B shown in the figure when all the following conditions
are met: -The RNC has sent a PAGING TYPE 1 message to the last cell that a UE is camped on
and to its neighboring cells. -The RNC receives an RRC Connection Request message from the
UE before the layered paging response timer expires. -The RRC Connection Request message
contains any of the following cause values: Terminating Conversational Call, Terminating
Streaming Call, Terminating Interactive Call, Terminating Background Call, Terminating High
Priority Signalling, Terminating Low Priority Signalling, and Terminating - cause unknown. If
the UE is performing real-time services, the VS.Paging1.Succ1.Idle.RealTime. Cell counter is
measured in the last camped-on cell. If the UE is performing non-real-time services, the
VS.Paging1.Succ1.Idle.NoneRealTime.Cell counter is measured in the last camped-on cell.
Figure 1-713 How a UE in idle mode responds to the PAGING TYPE 1 message
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.Paging1.Succ1.Idle.Real WRFD-150205 Layered Paging in Idle Mode

Time.Cell
VS.Paging1.Succ1.Idle.Non WRFD-150205 Layered Paging in Idle Mode

eRealTime.Cell
1.12.20.13 Number of Times a UE Processing SMS services Attempts to Preempt

Resources to Be Allocated to Other UEs When the PCH Is Congested for Cell
Counters
73426165 VS.RRC.Paging1.PCHCong Number of Times a UE

.SMSPreemptAtt Processing SMS services
Attempts to Preempt
Resources to Be Allocated to
Other UEs When the PCH Is
Congested for Cell
Description
This counter provides the number of times that SMS paging preempts the resources of the other
paging due to PCH congestion in a cell.
Measurement point
This counter is incremented by one at point A as shown in the figure each time the SMS paging
preempts the resources of other paging (including CN originated streaming, interactive and
background paging), due to PCH congestion.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

.SMSPreemptAtt CELL_PCH, URA_PCH
State (Type 1)
1.12.20.14 Number of Successful Preemptions by SMS Paging due to PCH

Congestion per Cell
Counters
73426166 VS.RRC.Paging1.PCHCong Number of Successful

.SMSPreemptSucc Preemptions by SMS Paging
due to PCH Congestion per
Cell
Description
This counter provides the number of times that SMS paging successfully preempts the resources
of other paging due to PCH congestion in a cell.
Measurement point
This counter is incremented by one at point B as shown in the figure each time the SMS paging
successfully preempts the resources of other paging (including CN originated streaming,
interactive, and background paging) due to PCH congestion and is successfully sent.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

.SMSPreemptSucc CELL_PCH, URA_PCH
State (Type 1)
1.12.20.15 Number of ETWS-related PAGING TYPE 1 Messages Sent in a Cell
Counters
73426313 VS.UTRAN.Paging1.Att.Et Number of ETWS-related

ws PAGING TYPE 1 Messages
Sent in a Cell
Description
This counter provides the number of PAGING TYPE 1 messages sent in a cell that carry ETWS-
related information.
Measurement point
The measurement is triggered at point A as shown in the figure when the RNC sends PAGING
TYPE 1 messages that carry ETWS-related information to UEs in the specified cell. The
information indicates that the paging is initiated by an ETWS warning process.

BSC6900 UMTS
Figure 1-716 Message interactions for paging type 1
Formula
None
Unit
None
Related Features
VS.UTRAN.Paging1.Att.Et WRFD-150234 Earthquake and Tsunami

ws Warning System (ETWS)
1.12.21 Measurement by Operator for Cell(PLMN.CELL)
Overview
This function subset provides counters measured by operator in a cell.
Counters
Description
73441192 VS.LC.ULCreditU Average Uplink V900R013

sed.Mean.PLMN0 Credit Consumption
of Operator0 for Cell

BSC6900 UMTS

Description



73423831 VS.LC.ULCreditU Minimum Uplink V900R013

sed.Min.PLMN0 Credit Consumption



73423835 VS.LC.ULCreditU Maximum Uplink V900R013

sed.Max.PLMN0 Credit Consumption



73441196 VS.CSLoad.Erlang Average Equivalent V900R013

.Equiv.PLMN0 Erlangs Consumed
by CS Services of
Operator0 for Cell

BSC6900 UMTS

Description

by CS Services of
Operator1 for Cell

by CS Services of
Operator2 for Cell

by CS Services of
Operator3 for Cell
73441200 VS.RAB.SFOccupy Average Number of V900R013

.PLMN0 Spreading Codes
Occupied by
Operator0 for Cell

Occupied by
Operator1 for Cell

Occupied by
Operator2 for Cell

Occupied by
Operator3 for Cell
73423839 VS.RAB.SFOccupy Maximum Number V900R013

.MAX.PLMN0 of Spreading Codes
Occupied by
Operator0 for Cell

Occupied by
Operator1 for Cell

Occupied by
Operator2 for Cell

BSC6900 UMTS

Description

Occupied by
Operator3 for Cell

.MAX.SharedOper of Spreading Codes
ator0 Occupied by Shared
Operator0 for
MOCN Cell

.SharedOperator0 Spreading Codes
Occupied by Shared
Operator0 for
MOCN Cell

Operator1 for
MOCN Cell

Occupied by Shared
Operator1 for
MOCN Cell

Operator2 for
MOCN Cell

Occupied by Shared
Operator2 for
MOCN Cell

Operator3 for
MOCN Cell

BSC6900 UMTS

Description

Occupied by Shared
Operator3 for
MOCN Cell
None
1.12.21.1 Credit Consumption of Operator0
Counters
73441192 VS.LC.ULCreditUsed.Mean Average Uplink Credit

.PLMN0 Consumption of Operator0
for Cell
73423831 VS.LC.ULCreditUsed.Min. Minimum Uplink Credit

PLMN0 Consumption of Operator0
for Cell
73423835 VS.LC.ULCreditUsed.Max. Maximum Uplink Credit

for Cell
Description
These counters provide the average, minimum, and maximum uplink credit consumption of
operator0 in 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

BSC6900 UMTS
Unit
None
Related Features
None
Counters

for Cell

for Cell

for Cell
Description
Measurement point
Formula
None
Unit
None
Related Features
None

BSC6900 UMTS
Counters

for Cell

for Cell

for Cell
Description
Measurement point
Formula
None
Unit
None
Related Features
None

BSC6900 UMTS
Counters

for Cell

for Cell

for Cell
Description
Measurement point
Formula
None
Unit
None
Related Features
None
1.12.21.5 Equivalent Erlangs Consumed by CS Services of Operator0
Counters
73441196 VS.CSLoad.Erlang.Equiv.P Average Equivalent Erlangs

LMN0 Consumed by CS Services of
Operator0 for Cell

BSC6900 UMTS
Description
This counter provides the average equivalent Erlangs consumed by all CS services of operator0
in 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
Counters

Operator1 for Cell
Description
in a cell.
Measurement point

BSC6900 UMTS
Formula
None
Unit
Erl
Related Features
None
Counters

Operator2 for Cell
Description
in a cell.
Measurement point
Formula
None
Unit
Erl

BSC6900 UMTS
Related Features
None
Counters

Operator3 for Cell
Description
in a cell.
Measurement point
Formula
None
Unit
Erl
Related Features
None
1.12.21.9 Number of Spreading Codes Occupied by Operator0

BSC6900 UMTS
Counters
73441200 VS.RAB.SFOccupy.PLMN Average Number of

0 Spreading Codes Occupied
by Operator0 for Cell
73423839 VS.RAB.SFOccupy.MAX.P Maximum Number of

LMN0 Spreading Codes Occupied
Description
These counters provide the average and maximum number of spreading codes occupied by
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
Formula
None
Unit
None
Related Features
None
Counters


BSC6900 UMTS

Description
Measurement point
Formula
None
Unit
None
Related Features
None
Counters



BSC6900 UMTS
Description
Measurement point
Formula
None
Unit
None
Related Features
None
Counters


Description
Measurement point

BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
1.12.21.13 Number of Spreading Codes Occupied by Shared Operator for MOCN

Cell
Counters
73424840 VS.RAB.SFOccupy.MAX.S Maximum Number of

haredOperator0 Spreading Codes Occupied
by Shared Operator0 for
MOCN Cell
73441525 VS.RAB.SFOccupy.Share- Average Number of

dOperator0 Spreading Codes Occupied
MOCN Cell

MOCN Cell

MOCN Cell

MOCN Cell

BSC6900 UMTS

MOCN Cell

MOCN Cell

MOCN Cell
Description
These counters provide the R99 code resource usage for operators in an MOCN cell.
Measurement point
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
VS.RAB.SFOccupy.MAX.S WRFD-021311 MOCN Introduction

haredOperator0 Package
VS.RAB.SFOccupy.Share- WRFD-021311 MOCN Introduction

dOperator0 Package

BSC6900 UMTS


dOperator1 Package


dOperator2 Package


dOperator3 Package
1.12.22 Measurements related to PTT(PTT.Cell)
Overview
This function subset includes the counters for push to talk (PTT) service establishment, complete
calls, handover, and traffic. The PTT service uses half-duplex mode to provide private calls
(point-to-point) and group calls (point-to-multipoint). A PTT connection is set up instantly
without ringing after a subscriber simply presses a key.
Counters
Description
73423555 VS.PTT.PCH.Singl Number of V900R013

eRAB.CallReq.Suc Successful PTT Call
c Initiation Attempts
or Responses of UEs
Using Only the PTT
Service in the
CELL_PCH or
URA_PCH State
During the State
Transition from
CELL_PCH/
URA_PCH to
CELL_DCH for Cell

BSC6900 UMTS

Description
73423556 VS.PTT.FACH.Sin Number of PTT Call V900R013

gleRAB.CallReq.At Initiation or
t Response Attempts
of UEs Using Only
the PTT Service in
the CELL_FACH
State for Cell
73423557 VS.PTT.FACH.Sin Number of V900R013

gleRAB.CallReq.S Successful PTT Call
ucc Initiation Attempts
or Responses of UEs
Using Only the PTT
Service in the
CELL_FACH State
for Cell
73423558 VS.PTT.FACH.Mu Number of V900R013

ltRAB.CallReq.Suc Successful PTT Call
c Initiation Attempts
or Responses of UEs
Using the PTT and
Other Services in the
CELL_FACH State
for Cell
73423559 VS.PTT.NormalRe Number of Complete V900R013

l PTT Calls for Cell
73423560 VS.PTT.RAB.Abno Number of RABs V900R013

rmRel.DCH Abnormally
Released During
PTT Calls for Cell
73423561 VS.PTT.SuccP2D.F Number of V900R013

irst Successful State
Transitions from
CELL_PCH/
URA_PCH to
CELL_DCH After
the RNC Sends a
CELL UPDATE
CONFIRM Message
for Cell

BSC6900 UMTS

Description
73423562 VS.PTT.SuccP2D.S Number of V900R013

econd Successful State
Transitions from
CELL_PCH/
URA_PCH to
CELL_DCH After
the RNC Sends Two
CELL UPDATE
CONFIRM
Messages for Cell
73423563 VS.PTT.SuccP2D. Number of V900R013

Third Successful State
Transitions from
CELL_PCH/
URA_PCH to
CELL_DCH After
the RNC Sends
Three CELL
UPDATE
CONFIRM
Messages for Cell
73423564 VS.PTT.SuccPagin Number of V900R013

g.First Successful PTT
Paging Attempts
After the RNC Sends
a PAGING TYPE 1
Message for Cell

g.Second Successful PTT
Paging Attempts
After the RNC Sends
Two PAGING TYPE
1 Messages for Cell

g.Third Successful PTT
Paging Attempts
After the RNC Sends
Three PAGING
TYPE 1 Messages
for Cell

BSC6900 UMTS

Description
73423609 VS.PTT.FACH.Mu Number of PTT Call V900R013

ltRAB.CallReq.Att Initiation or
Responses Attempts
of UEs Using the
PTT and Other
Services in the
CELL_FACH State
for Cell
73423610 VS.PTT.PCH.Singl Number of Failed V900R013

eRAB.CallReq.Fail PTT Call Initiation
.Cong Attempts or
Responses of a UE in
the CELL_PCH or
URA_PCH State
Processing Only the
PTT Service During
P2D Due to
Congestion for Cell
73423611 VS.PTT.FACH.Sin Number of Failed V900R013

gleRAB.CallReq.F PTT Call Initiation
ail.Cong Attempts or
the CELL_FACH
State Processing
Only the PTT
Service Due to
Congestion for Cell
73423612 VS.PTT.FACH.Mu Number of Failed V900R013

ltRAB.CallReq.Fail PTT Call Initiation
.Cong Attempts or
the CELL_FACH
State Processing
Multiple Services
Due to Congestion
for Cell
73423619 VS.PTT.PCH.Singl Number of PTT Call V900R013

eRAB.CallReq.Att Initiation or
Response Attempts
of UEs Using Only
the PTT Service in
the CELL_PCH
State for Cell

BSC6900 UMTS

Description
73441168 VS.PTT.UL.Traffic Uplink Traffic V900R013

Volume of the PTT
Service
73441169 VS.PTT.DL.Traffic Downlink Traffic V900R013

Volume of the PTT
Service
73424828 VS.PTT.SHO.Serv Number of V900R014

CellChg.SuccOut Successful Serving
Cell Changes of PTT
Service in Soft
Handover Status for
Cell
73424829 VS.PTT.SHO.Serv Number of Serving V900R014

CellChg.AttOut Cell Change
Attempts of PTT
Service in Soft
Handover Status for
Cell
73424830 VS.PTT.HHO.Suc- Number of V900R014

cOut Successful Hard
Handovers of PTT
Service for Cell
73424831 VS.PTT.HHO.Att- Number of Hard V900R014

Out Handover Attempts
of PTT Service for
Cell
None
1.12.22.1 Number of Successful PTT Call Initiation Attempts or Responses During

a P2D Procedure for UEs Processing PTT Services

BSC6900 UMTS
Counters
73423555 VS.PTT.PCH.SingleRAB.C Number of Successful PTT

allReq.Succ Call Initiation Attempts or
Responses of UEs Using
Only the PTT Service in the
CELL_PCH or URA_PCH
State During the State
Transition from
CELL_PCH/URA_PCH to
CELL_DCH for Cell
Description
This counter provides the number of successful state transitions from CELL_PCH or URA_PCH
to CELL_DCH, which indicates the successful PTT call initiations or responses of the UE in
the CELL_PCH or URA_PCH state. The state transition is triggered by PTT data transmission.
This counter is measured on a per cell basis. The counter is used with the
VS.PTT.PCH.SingleRAB.CallReq.Att counter to assess the success rate of PTT call initiations
or responses of a UE in the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point B as shown in Figure 1 when the RNC receives from the
UE a RADIO BEARER RECONFIGURATION COMPLETE message that transfers from the
CELL_PCH or URA_PCH state to the CELL_DCH state to initiate to a PTT call.
A calling UE transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to
initiate a PTT call if the following conditions are met: The UE has set up a PTT service. The
values of the IEs "Cell update cause", "Establishment cause", and "Traffic volume indicator"
contained in the CELL UPDATE message are "Uplink Data Transmission", "Originating
Conversational Call", and "True", respectively. The "CS Call Type" IE is not contained in this
message.

BSC6900 UMTS
Figure 1-717 PTT call normal procedure(P2D)
The measurement is triggered at point B as shown in Figure 2 when the RNC receives from the
UE a RADIO BEARER RECONFIGURATION COMPLETE message that transfers from the
CELL_PCH or URA_PCH state to the CELL_DCH state to respond to a PTT call.
A called UE transfers from the CELL_PCH or URA_PCH state to the CELL_DCH state to
respond a PTT call if the following conditions are met: The UE has set up a PTT service. PTT
has data to be transmitted in the downlink. The value of the "Cell update cause" IE contained in
the CELL UPDATE message is "paging response."

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.PTT.PCH.SingleRAB.C WRFD-020134 Push to Talk

allReq.Succ
1.12.22.2 Number of PTT Call Initiation or Response Attempts of UEs Using Only
the PTT Service in the CELL_FACH State for Cell

BSC6900 UMTS
Counters
73423556 VS.PTT.FACH.SingleRAB. Number of PTT Call

CallReq.Att Initiation or Response
Attempts of UEs Using Only
the PTT Service in the
Description
This counter provides the number of UE state transition attempts from the CELL_FACH to
CELL_DCH triggered by PTT data transmission of a UE processing only the PTT service, which
indicates the number of PTT call initiation or response attempts of the UE in the CELL_FACH
state.
VS.PTT.FACH.SingleRAB.CallReq.Succ counter to assess the success rate of PTT call
initiations or responses of a UE processing only the PTT service in the CELL_FACH state.
Measurement point
The measurement is triggered at point A as shown in Figure 1, when a UE processing only the
PTT service in the CELL_FACH state transfers to CELL_DCH state triggered by an event 4A
measurement report.
Figure 1-719 PTT call normal procedure(F2D)

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.PTT.FACH.SingleRAB. WRFD-020134 Push to Talk

CallReq.Att
1.12.22.3 Number of Successful PTT Call Initiation Attempts or Responses of UEs

Using Only the PTT Service in the CELL_FACH State for Cell
Counters
73423557 VS.PTT.FACH.SingleRAB. Number of Successful PTT

CallReq.Succ Call Initiation Attempts or
Responses of UEs Using
Only the PTT Service in the
Description
This counter provides the number of successful UE state transitions from CELL_FACH to
CELL_DCH triggered by PTT data transmission of a UE processing only the PTT service, which
indicates the number of successful PTT call initiations or responses of the UE in the
CELL_FACH state.
VS.PTT.PCH.SingleRAB.CallReq.Att counter to assess the success rate of PTT call initiations
or responses of a UE processing only the PTT service in the CELL_FACH state.
Measurement point
The measurement is triggered at point B as shown in Figure 1, when the RNC receives a RADIO
BEARER RECONFIGURATION COMPLETE message during the UE state transition from
CELL_FACH to CELL_DCH. The UE processes only the PTT service in the CELL_FACH
state. The state transition is triggered by PTT data transmission.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

CallReq.Succ
1.12.22.4 Number of Successful PTT Call Initiation Attempts or Responses of UEs

Using the PTT and Other Services in the CELL_FACH State for Cell

BSC6900 UMTS
Counters
73423558 VS.PTT.FACH.MultRAB.C Number of Successful PTT

allReq.Succ Call Initiation Attempts or
Responses of UEs Using the
PTT and Other Services in
the CELL_FACH State for
Cell
Description
This counter provides the number of successful UE state transitions from CELL_FACH to
CELL_DCH triggered by PTT data transmission of a UE processing PTT and other services,
which indicates the number of successful PTT call initiations or responses of the UE in the
CELL_FACH state.
VS.PTT.FACH.MultRAB.CallReq.Att counter to assess the success rate of PTT call initiations
or responses of a UE processing PTT and other services in the CELL_FACH state.
Measurement point
The measurement is triggered at point B as shown in Figure 1, when the RNC receives a RADIO
BEARER RECONFIGURATION COMPLETE message during the UE state transition from
CELL_FACH to CELL_DCH. The UE processes PTT and other services in the CELL_FACH
state. The state transition is triggered by PTT data transmission.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.PTT.FACH.MultRAB.C WRFD-020134 Push to Talk

allReq.Succ
1.12.22.5 Number of Complete PTT Calls for Cell
Counters
73423559 VS.PTT.NormalRel Number of Complete PTT

Calls for Cell
Description
This counter provides number of UE state transitions from CELL_DCH to another RRC
connection state of a UE when data transmission ends only if the UE state transition to
CELL_DCH is triggered by PTT data transmission.
VS.PTT.RAB.AbnormRel.DCH counter to assess the PTT call drop rate.
Measurement point
The measurement is triggered at point A as shown in Figure 1. When a PTT call ends, the RNC
sends the UE a RADIO BEARER RECONFIGURATION message to trigger the UE state
transition from CELL_DCH to another RRC connection state. When the RNC receives from the
UE a RADIO BEARER RECONFIGURATION COMPLETE message, the measurement is
triggered in the cell that the UE camps on if RBs are reconfigured to transfer the UE to an RRC
connection state other than CELL_DCH and the current the UE state transition to CELL_DCH
is initiated by a PTT call.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.PTT.NormalRel WRFD-020134 Push to Talk
1.12.22.6 Number of RABs Abnormally Released During PTT Calls for Cell
Counters
73423560 VS.PTT.RAB.AbnormRel.D Number of RABs

CH Abnormally Released
During PTT Calls for Cell
Description
This counter provides the number of times that RABs are abnormally released after a UE state
transition to CELL_DCH due to PTT data transmission, which indicates the number of PTT call
drops.

BSC6900 UMTS
This counter is measured on a per cell basis. The counter is used with the VS.PTT.NormalRel
counter to access the PTT call drop rate.
Measurement point
At point A shown in the following figure, when a failure occurs, the RNC sends a RAB
RELEASE REQUEST message to the CN. After the RNC receives from the CN a RAB
ASSIGNMENT REQUEST message containing a cause value other than normal release values
(such as "User Inactivity", "Normal Release", "Successful Relocation", and "Network
Optimization", for details, see 3GPP TS 25.413), the RNC sends a RAB ASSIGNMENT
RESPONSE message. When this happens, this counter is measured in the best cell that the UE
camps on if the UE transfers to the current CELL_DCH state due to a PTT call.
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.

BSC6900 UMTS
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

BSC6900 UMTS
Unit
None
Related Features
VS.PTT.RAB.AbnormRel.D WRFD-020134 Push to Talk

CH
1.12.22.7 Number of Successful State Transitions from CELL_PCH/URA_PCH to

CELL_DCH After the RNC Sends the CELL UPDATE CONFIRM Message for Cell
Counters
73423561 VS.PTT.SuccP2D.First Number of Successful State

Transitions from
CELL_PCH/URA_PCH to
CELL_DCH After the RNC
Sends a CELL UPDATE
CONFIRM Message for Cell
73423562 VS.PTT.SuccP2D.Second Number of Successful State

Transitions from
CELL_PCH/URA_PCH to
Sends Two CELL UPDATE
CONFIRM Messages for
Cell
73423563 VS.PTT.SuccP2D.Third Number of Successful State

Transitions from
CELL_PCH/URA_PCH to
Sends Three CELL
UPDATE CONFIRM
Messages for Cell
Description
These counters provide the number of RADIO BEARER RECONFIGURATION COMPLETE
messages received by the RNC during the UE state transition from CELL_PCH or URA_PCH
to CELL_DCH triggered by a PTT call. The counters are measured based on the number of
CELL UPDATE CONFIRM messages sent by the RNC.
These counters are measured on a per cell basis. The counters are used to analyze the impact on
PTT call setup duration caused by the UE state transition from CELL_PCH or URA_PCH to

BSC6900 UMTS
CELL_DCH. If the value of the VS.PTT.SuccP2D.Second or VS.PTT.SuccP2D.Third counter

is larger than that of the VS.PTT.SuccP2D.First counter, more UEs undergo a long duration
during the UE state transition. In this case, check whether the UE fails to receive the downlink
signaling in time due to Uu interface abnormality.
Measurement point
The VS.PTT.SuccP2D.First counter is measured at point B as shown in Figure 1. During the UE
state transition from CELL_PCH or URA_PCH to CELL_DCH triggered by a PTT call, if the
RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message
after the RNC sends the UE a first CELL UPDATE CONFIRM message, the counter is measured
in the cell that the UE camps on.
Figure 1-726 VS.PTT.SuccP2D.First
The VS.PTT.SuccP2D.Second counter is measured at point B as shown in Figure 2. During the

UE state transition from CELL_PCH or URA_PCH to CELL_DCH triggered by a PTT call, if
the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE
message after the RNC sends the UE a second CELL UPDATE CONFIRM message, the counter
is measured in the cell that the UE camps on.

BSC6900 UMTS
Figure 1-727 VS.PTT.SuccP2D.Second
The VS.PTT.SuccP2D.Third counter is measured at point B as shown in Figure 3. During the

UE state transition from CELL_PCH or URA_PCH to CELL_DCH triggered by a PTT call, if
the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE
message after the RNC sends the UE a third CELL UPDATE CONFIRM message, the counter
is measured in the cell that the UE camps on.

BSC6900 UMTS
Figure 1-728 VS.PTT.SuccP2D.Third
Formula
None
Unit
None
Related Features
VS.PTT.SuccP2D.First WRFD-020134 Push to Talk
VS.PTT.SuccP2D.Second WRFD-020134 Push to Talk
VS.PTT.SuccP2D.Third WRFD-020134 Push to Talk

BSC6900 UMTS
1.12.22.8 Number of Successful PTT Paging Attempts After the RNC Sends the
PAGING TYPE 1 Message for Cell
Counters
73423564 VS.PTT.SuccPaging.First Number of Successful PTT

Paging Attempts After the
RNC Sends a PAGING
TYPE 1 Message for Cell
73423565 VS.PTT.SuccPaging.Second Number of Successful PTT

RNC Sends Two PAGING
TYPE 1 Messages for Cell
73423566 VS.PTT.SuccPaging.Third Number of Successful PTT

RNC Sends Three PAGING
TYPE 1 Messages for Cell
Description
These counters provide the number of CELL UPDATE messages with the cause value of "paging
response" sent by the UE due to PTT paging. The counters are measured based on the number
of PAGING TYPE 1 messages sent by the RNC.
These counters are measured on a per cell basis. The counters are used to analyze the impact on
end-to-end duration caused by paging over the Uu interface of the called UE during the PTT
call setup. If the value of the VS.PTT.SuccPaging.Second or VS.PTT.SuccPaging.Third counter
is larger than that of the VS.PTT.SuccPaging.First counter, more UEs undergo a long paging
duration. In this case, check whether the UE fails to receive the downlink signaling in time due
to Uu interface abnormality.
Measurement point
The measurement is triggered at point A as shown in Figure 1. When the RNC detects downlink
PTT data transmission, it sends the UE a first PAGING TYPE 1 message. When the RNC
receives a CELL UPDATE message that carries the "Cell update cause" IE with the value of
"paging response", the VS.PTT.SuccPaging.First counter is measured in the cell that the UE
camps on.

BSC6900 UMTS
Figure 1-729 Paging procedure trigged by RNC
PTT data transmission, it sends the UE a second PAGING TYPE 1 message. When the RNC
"paging response", the VS.PTT.SuccPaging.Second counter is measured in the cell that the UE
camps on.
PTT data transmission, it sends the UE a third PAGING TYPE 1 message. When the RNC
"paging response", the VS.PTT.SuccPaging.Third counter is measured in the cell that the UE
camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.PTT.SuccPaging.First WRFD-020134 Push to Talk
VS.PTT.SuccPaging.Second WRFD-020134 Push to Talk
VS.PTT.SuccPaging.Third WRFD-020134 Push to Talk
1.12.22.9 Number of PTT Call Initiation or Response Attempts of UEs Using the
PTT and Other Services in the CELL_FACH State for Cell

BSC6900 UMTS
Counters
73423609 VS.PTT.FACH.MultRAB.C Number of PTT Call

allReq.Att Initiation or Responses
Attempts of UEs Using the
PTT and Other Services in
the CELL_FACH State for
Cell
Description
This counter provides the number of UE state transition attempts from the CELL_FACH to
CELL_DCH that is triggered by PTT data transmission of a UE processing PTT and other
services, which indicates the number of initiation or response attempts of a UE in the
CELL_FACH state. This counter is measured on a per cell basis. The counter is used with the
VS.PTT.FACH.MultRAB.CallReq.Succ counter to assess the success rate of PTT call initiations
or responses of a UE processing PTT and other services in the CELL_FACH state.
Measurement point
The measurement is triggered at point A as shown in Figure 1 in the cell that a UE camps on,
when the UE setting up multiple RABs in the CELL_FACH state transfers to CELL_DCH state.
The state transition is triggered when the RNC receives an event 4A measurement report from
the UE processing PTT data transmission.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

allReq.Att
1.12.22.10 Number of Failed PTT Call Initiations or Responses Due to Resource

Congestion During a P2D Procedure for UEs Processing PTT Services
Counters
73423610 VS.PTT.PCH.SingleRAB.C Number of Failed PTT Call

allReq.Fail.Cong Initiation Attempts or
Responses of a UE in the
CELL_PCH or URA_PCH
State Processing Only the
PTT Service During P2D
Due to Congestion for Cell
Description
This counter provides the number of times the UE fails to transit from the CELL_PCH or
URA_PCH state to the CELL_DCH state due to admission failures during PTT data
transmission, which indicates the failed PTT call initiations or responses of a UE in the
CELL_PCH or URA_PCH state due to resource congestion.
This counter is measured on a per cell basis. Failed PTT calls increased due to cell resource
congestion affect user experience, which can be improved by resource utilization optimization
or capacity expansion.
Measurement point
The measurement is triggered at point A as shown in Figure 1. If the UE transmits from the
CELL_PCH or URA_PCH state to the CELL_DCH state to initiate a PTT call, the counter is

BSC6900 UMTS
measured in the cell that the UE camps on when the UE fails to be transited to the CELL_DCH
state due to admission failures.
contained in the CELL UPDATE message are "uplink data transmission", "Originating
Conversational Call", and "True", respectively. The "CS Call Type" IE is not contained in this
message.
Figure 1-733 VS.PTT.PCH.SingleRAB.CallReq.Fail.Cong
The measurement is triggered at point A as shown in Figure 2. If the UE transits from the
CELL_PCH or URA_PCH state to the CELL_DCH state to respond a PTT call, the counter is
measured in the cell that the UE camps on when the UE fails to be transited to the CELL_DCH
state due to admission failures.

BSC6900 UMTS
Figure 1-734 VS.PTT.PCH.SingleRAB.CallReq.Fail.Cong
Formula
None
Unit
None
Related Features

allReq.Fail.Cong
1.12.22.11 Number of Failed PTT Call Initiation Attempts or Responses of a UE in

the CELL_FACH State Processing Only the PTT Service Due to Congestion for Cell

BSC6900 UMTS
Counters
73423611 VS.PTT.FACH.SingleRAB. Number of Failed PTT Call

CallReq.Fail.Cong Initiation Attempts or
CELL_FACH State
Processing Only the PTT
Service Due to Congestion
for Cell
Description
This counter provides the number of times the UE fails to transit from the CELL_FACH state
to the CELL_DCH state due to admission failures during PTT data transmission with only PTT
RABs established, which indicates the number of failed PTT call initiations or responses of the
UE in the CELL_FACH state due to resource congestion.
Measurement point
If the UE state transition from CELL_FACH to CELL_DCH is triggered by PTT data
transmission and only the PTT service is established, when the UE access fails during the state
transition, the counter is measured in the cell that the UE camps on.
Formula
None
Unit
None
Related Features

CallReq.Fail.Cong
1.12.22.12 Number of Failed PTT Call Initiation Attempts or Responses of a UE in

the CELL_FACH State Processing Multiple Services Due to Congestion for Cell

BSC6900 UMTS
Counters
73423612 VS.PTT.FACH.MultRAB.C Number of Failed PTT Call

allReq.Fail.Cong Initiation Attempts or
CELL_FACH State
Processing Multiple Services
Due to Congestion for Cell
Description
This counter provides the number of times the UE fails to transit from the CELL_FACH state
to the CELL_DCH state due to admission failures during PTT data transmission with multiple
RABs established, which indicates the number of failed PTT call initiations or responses of the
UE in the CELL_FACH state due to resource congestion.
Measurement point
If the UE state transition from CELL_FACH to CELL_DCH is triggered by PTT data
transmission and PTT and other services are established, when the UE access fails during the
state transition, the counter is measured in the cell that the UE camps on.
Formula
None
Unit
None
Related Features

allReq.Fail.Cong
1.12.22.13 Number of PTT Call Initiation Attempts or Responses During a P2D

Procedure for UEs Processing PTT Services

BSC6900 UMTS
Counters
73423619 VS.PTT.PCH.SingleRAB.C Number of PTT Call

allReq.Att Initiation or Response
Attempts of UEs Using Only
the PTT Service in the
CELL_PCH State for Cell
Description
This counter provides the number of state transition attempts from CELL_PCH or URA_PCH
to CELL_DCH triggered by PTT data transmission, which indicates the number of initiation or
response attempts of a UE.
VS.PTT.PCH.SingleRAB.CallReq.Succ counter to assess the success rate of PTT call initiations
or responses of the UE in the CELL_PCH or URA_PCH state.
Measurement point
The measurement is triggered at point B as shown in Figure 1. If the UE transfers from the
CELL_PCH or URA_PCH state to the CELL_DCH state to respond a PTT call, when the RNC
receives from the UE a CELL UPDATE message, the counter is measured in the cell that the
UE camps on.
contained in the CELL UPDATE message are "uplink data transmission", "Originating
Conversational Call", and "True", respectively. The "CS Call Type" IE is not contained in the
CELL UPDATE message.

BSC6900 UMTS
The measurement is triggered at point B as shown in Figure 2. If the UE transfers from the
CELL_PCH or URA_PCH state to the CELL_DCH state to respond a PTT call, when the RNC
receives from the UE a CELL UPDATE message, the counter is measured in the cell that the
UE camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

allReq.Att
1.12.22.14 Uplink Traffic Volume of the PTT Service

BSC6900 UMTS
Counters
73441168 VS.PTT.UL.Traffic Uplink Traffic Volume of the

PTT Service
Description
This counter provides the uplink PTT traffic volume (not including the RLC header) at the RLC
layer of cells in the active set. This counter is measured on a per cell basis.
This counter can be used to assess the proportion of the PTT traffic volume for all services in a
cell. To obtain the total call duration, divide the value of this counter by the uplink PTT data
rate.
Measurement point
In a measurement period, the accumulated uplink PTT traffic volume (not including the RLC
header) at the RLC layer in a cell is the total uplink PTT traffic volume at the RLC layer in the
cell.
Formula
None
Unit
bit
Related Features
VS.PTT.UL.Traffic WRFD-020134 Push to Talk
1.12.22.15 Downlink Traffic Volume of the PTT Service
Counters
73441169 VS.PTT.DL.Traffic Downlink Traffic Volume of

the PTT Service

BSC6900 UMTS
Description
This counter provides the downlink traffic volume of PTT services at the RLC layer of cells in
the active set. This counter is measured on a per cell basis.
This counter can be used to assess the proportion of PTT services for all services in a cell. To
obtain the total call duration, divide the value of this counter by the downlink PTT data rate.
Measurement point
In a measurement period, the accumulated downlink PTT traffic volume (not including the RLC
header) at the RLC layer in a cell is the total downlink PTT traffic volume at the RLC layer in
the cell.
Formula
None
Unit
bit
Related Features
VS.PTT.DL.Traffic WRFD-020134 Push to Talk
1.12.22.16 Number of Successful Serving Cell Changes of PTT Service in Soft

Handover Status
Counters
73424828 VS.PTT.SHO.ServCellChg. Number of Successful

SuccOut Serving Cell Changes of PTT
Service in Soft Handover
Status for Cell
Description
This counter provides the number of successful serving cell changes of a PTT UE performing a
soft handover.
VS.PTT.SHO.ServCellChg.AttOut counter to assess the success rate of serving cell changes of
a PTT UE.

BSC6900 UMTS
Measurement point
This counter is measured when the RNC receives from a PTT UE a message indicating that an
HSDPA or HSUPA serving cell change has completed.
The measurement is triggered at point B as shown in Figure 1. The counter is measured in the
original serving cell of the UE when the following conditions are met: The UE has set up PTT
services and is performing a soft handover. The RNC receives from the UE a PHYSICAL
CHANNEL RECONFIGURATION COMPLETE message in responding to the PHYSICAL
CHANNEL RECONFIGURATION message sent from the RNC. The RNC sends the UE a
PHYSICAL CHANNEL RECONFIGURATION message to initiate an HSDPA or HSUPA
serving cell (intra- or inter-RNC) change.
Figure 1-737 Physical Channel Reconfiguration Procedure
services and is performing a soft handover. The RNC receives from the UE a TRANSPORT
CHANNEL RECONFIGURATION COMPLETE message in responding to the TRANSPORT
CHANNEL RECONFIGURATION message sent from the RNC. The RNC sends the UE a
TRANSPORT CHANNEL RECONFIGURATION message to initiate an HSDPA or HSUPA
serving cell (intra- or inter-RNC) change.

BSC6900 UMTS
Figure 1-738 Transport Channel Reconfiguration Procedure
services and is performing a soft handover. The RNC receives from the UE a RADIO BEARER
RECONFIGURATION COMPLETE message in responding to the RADIO BEARER
RECONFIGURATION message sent from the RNC. The RNC sends the UE a RADIO
BEARER RECONFIGURATION message to initiate an HSDPA or HSUPA serving cell (intra-
or inter-RNC) change.
Figure 1-739 Radio Bearer Reconfiguration Procedure

BSC6900 UMTS
services and is performing a soft handover. The RNC receives from the UE an ACTIVE SET
UPDATE COMPLETE message in responding to the ACTIVE SET UPDATE message sent
from the RNC. The RNC sends the UE an ACTIVE SET UPDATE message to initiate an HSDPA
or HSUPA serving cell (intra- or inter-RNC) change.
Figure 1-740 Active Set Update Procedure
Formula
None
Unit
None
Related Features
VS.PTT.SHO.ServCellChg. WRFD-020134 Push to Talk

SuccOut
1.12.22.17 Number of Serving Cell Change Attempts of PTT Service in Soft

Handover Status

BSC6900 UMTS
Counters
73424829 VS.PTT.SHO.ServCellChg. Number of Serving Cell

AttOut Change Attempts of PTT
Service in Soft Handover
Status for Cell
Description
This counter provides the number of cell change attempts of a PTT UE performing a soft
handover.
VS.PTT.SHO.ServCellChg.SuccOut counter to assess the success rate of serving cell changes
of a PTT UE.
Measurement point
This counter is measured when the RNC sends the PTT UE a message to initiate an HSDPA or
HSUPA serving cell change.
The measurement is triggered at point A as shown in Figure 1. The counter is measured in the
services and is performing a soft handover. The RNC sends the UE a PHYSICAL CHANNEL
RECONFIGURATION message to initiate an HSDPA or HSUPA serving cell (intra- or inter-
RNC) change.
Figure 1-741 Physical Channel Reconfiguration Procedure

BSC6900 UMTS
services and is performing a soft handover. The RNC sends the UE a TRANSPORT CHANNEL
RNC) change.
Figure 1-742 Transport Channel Reconfiguration Procedure
services and is performing a soft handover. The RNC sends the UE a RADIO BEARER
RNC) change.

BSC6900 UMTS
Figure 1-743 Radio Bearer Reconfiguration Procedure
services and is performing a soft handover. The RNC sends the UE an ACTIVE SET UPDATE
message to initiate an HSDPA or HSUPA serving cell (intra- or inter-RNC) change.
Figure 1-744 Active Set Update Procedure
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.PTT.SHO.ServCellChg. WRFD-020134 Push to Talk

AttOut
1.12.22.18 Number of Successful Hard Handovers of PTT Service
Counters
73424830 VS.PTT.HHO.SuccOut Number of Successful Hard

Handovers of PTT Service
for Cell
Description
This counter provides the number of successful hard handovers of a PTT UE, including intra-
frequency, inter-frequency, intra-RNC, and inter-RNC hard handovers.
This counter is measured on a per cell basis. The counter is used with the VS.PTT.HHO.AttOut
counter to assess the success rate of hard handovers of a PTT UE.
Measurement point
This counter is measured when the RNC receives from the PTT UE a message indicating that a
hard handover has completed.
best cell before the hard handover when the following conditions are met: The UE has set up
PTT services. The RNC receives from the UE a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message in responding to the PHYSICAL CHANNEL
RECONFIGURATION message sent from the RNC. The RNC sends the UE a PHYSICAL
CHANNEL RECONFIGURATION message to initiate a hard handover (including intra- and
inter-frequency and intra- and inter-RNC hard handovers).

BSC6900 UMTS
Figure 1-745 Physical Channel reconfiguration procedure
PTT services. The RNC receives from the UE a TRANSPORT CHANNEL
RECONFIGURATION COMPLETE message in responding to the TRANSPORT CHANNEL
RECONFIGURATION message sent from the RNC. The RNC sends the UE a TRANSPORT
CHANNEL RECONFIGURATION message to initiate a hard handover (including intra- and
inter-frequency and intra- and inter-RNC hard handovers).
Figure 1-746 Transport Channel Reconfiguration procedure

BSC6900 UMTS
PTT services. The RNC receives from the UE a RADIO BEARER RECONFIGURATION
COMPLETE message in responding to the RADIO BEARER RECONFIGURATION message
sent from the RNC. The RNC sends the UE a RADIO BEARER RECONFIGURATION
message to initiate a hard handover (including intra- and inter-frequency and intra- and inter-
RNC hard handovers).
PTT services. The RNC receives from the UE a RADIO BEARER SETUP COMPLETE
message in responding to the RADIO BEARER SETUP message sent from the RNC. The RNC
sends the UE a RADIO BEARER SETUP message to initiate a hard handover (including intra-
and inter-frequency and intra- and inter-RNC hard handovers).

BSC6900 UMTS
Figure 1-748 Radio Bearer Setup procedure
Formula
None
Unit
None
Related Features
VS.PTT.HHO.SuccOut WRFD-020134 Push to Talk
1.12.22.19 Number of Hard Handover Attempts of PTT Service
Counters
73424831 VS.PTT.HHO.AttOut Number of Hard Handover

Attempts of PTT Service for
Cell

BSC6900 UMTS
Description
This counter provides the number of hard handover attempts of a PTT UE, including intra- and
inter-frequency and intra- and inter-RNC hard handovers.
This counter is measured on a per cell basis. The counter is used with the VS.PTT.HHO.SuccOut
counter to assess the success rate of hard handovers of a PTT UE.
Measurement point
This counter is measured when the RNC sends the PTT UE a message to initiate a hard handover.
PTT services. The RNC receives from the UE a PHYSICAL CHANNEL
RECONFIGURATION message to initiate a hard handover (including intra- and inter-frequency
and intra- and inter-RNC hard handovers).
Figure 1-749 Physical Channel reconfiguration procedure
PTT services. The RNC receives from the UE a TRANSPORT CHANNEL
RECONFIGURATION message to initiate a hard handover (including intra- and inter-frequency
and intra- and inter-RNC hard handovers).

BSC6900 UMTS
Figure 1-750 Transport Channel Reconfiguration procedure
PTT services. The RNC receives from the UE a RADIO BEARER RECONFIGURATION
message to initiate a hard handover (including intra- and inter-frequency and intra- and inter-
RNC hard handovers).

BSC6900 UMTS
PTT services. The RNC receives from the UE a RADIO BEARER SETUP message to initiate
a hard handover (including intra- and inter-frequency and intra- and inter-RNC hard handovers).
Figure 1-752 Radio Bearer Setup procedure
Formula
None
Unit
None
Related Features
VS.PTT.HHO.AttOut WRFD-020134 Push to Talk
1.12.23 Measurement related to QOS per cell(QOS.Cell)
Overview
This function subset contains the following contents:1)Delay from RRC establishment to
completion of RAB establishment.2)Delay of service establishment by service types and CN
domains.3)Mean throughput count by user class and HSDPA download throughput.4)Mean
throughput count by user class and HSUPA upload throughput.

BSC6900 UMTS
Counters
Description
67195972 VS.AMR.Estab.Ma Maximum Delay Earlier than

xTime Between RRC V900R011
Connection
Establishment and
AMR RAB
Establishment
Completion for Cell
67204785 VS.AMR.Estab.Me Mean Delay Earlier than

anTime Between RRC V900R011
Connection
Establishment and
AMR RAB
Establishment
Completion for Cell
67195973 VS.AMR.Estab.Mi Minimum Delay Earlier than

nTime Between RRC V900R011
Connection
Establishment and
AMR RAB
Establishment
Completion for Cell
67195976 VS.CS64.Estab.Ma Maximum Delay Earlier than

xTime Between RRC V900R011
Connection
Establishment and
64kbit/s CS RAB
Establishment
Completion for Cell
67204786 VS.CS64.Estab.Me Mean Delay Earlier than

anTime Between RRC V900R011
Connection
Establishment and
64kbit/s CS RAB
Establishment
Completion for Cell
67195977 VS.CS64.Estab.Mi Minimum Delay Earlier than

nTime Between RRC V900R011
Connection
Establishment and
64kbit/s CS RAB
Establishment
Completion for Cell

BSC6900 UMTS

Description
67195980 VS.PSR99.Estab.M Maximum Delay Earlier than

axTime Between RRC V900R011
Connection
Establishment and
PS R99 RAB
Establishment
Completion for Cell
67204787 VS.PSR99.Estab.M Mean Delay Earlier than

eanTime Between RRC V900R011
Connection
Establishment and
PS R99 RAB
Establishment
Completion for Cell
67195981 VS.PSR99.Estab.M Minimum Delay Earlier than

inTime Between RRC V900R011
Connection
Establishment and
PS R99 RAB
Establishment
Completion for Cell
67195984 VS.HSDPA.Estab. Maximum Delay Earlier than

MaxTime Between RRC V900R011
Connection
Establishment and
HSDPA RAB
Establishment
Completion for Cell
67204788 VS.HSDPA.Estab. Mean Delay Earlier than

MeanTime Between RRC V900R011
Connection
Establishment and
HSDPA RAB
Establishment
Completion for Cell
67195985 VS.HSDPA.Estab. Minimum Delay Earlier than

MinTime Between RRC V900R011
Connection
Establishment and
HSDPA RAB
Establishment
Completion for Cell

BSC6900 UMTS

Description
67195988 VS.HSUPA.Estab. Maximum Delay Earlier than

MaxTime Between RRC V900R011
Connection
Establishment and
HSUPA RAB
Establishment
Completion for Cell
67204789 VS.HSUPA.Estab. Mean Delay Earlier than

MeanTime Between RRC V900R011
Connection
Establishment and
HSUPA RAB
Establishment
Completion for Cell
67195989 VS.HSUPA.Estab. Minimum Delay Earlier than

MinTime Between RRC V900R011
Connection
Establishment and
HSUPA RAB
Establishment
Completion for Cell
67196050 VS.HSDPA.Golden Number of Times Earlier than

BeChThroughput.0 that Average DL V900R011
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between 0
Kbit/s and 32 Kbit/s
for Cell

Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between 32
for Cell

BSC6900 UMTS

Description

Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between 64
for Cell

Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
256 Kbit/s and 512
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
512 Kbit/s and 768
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
768 Kbit/s and 1024
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
1024 Kbit/s and 1536
Kbit/s for Cell

BSC6900 UMTS

Description

Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
Kbit/s for Cell

BeChThroughput. that Average DL V900R011
10 Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
Kbit/s for Cell

11 Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
Kbit/s for Cell

BSC6900 UMTS

Description

12 Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
8192 Kbit/s and
12288 Kbit/s for Cell

13 Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Greater
Than 12288 Kbit/s
for Cell
67196064 VS.HSDPA.Silver- Number of Times Earlier than

Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between 0
for Cell

Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between 32
for Cell

Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between 64
for Cell

BSC6900 UMTS

Description

Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
256 Kbit/s and 512
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
512 Kbit/s and 768
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
768 Kbit/s and 1024
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
Kbit/s for Cell

BSC6900 UMTS

Description

Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
Kbit/s for Cell

10 Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
Kbit/s for Cell

11 Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
Kbit/s for Cell

12 Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
8192 Kbit/s and

BSC6900 UMTS

Description

13 Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Greater
Than 12288 Kbit/s
for Cell
67196078 VS.HSDPA.Copper Number of Times Earlier than

Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between 0
for Cell

Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between 32
for Cell

Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between 64
for Cell

Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
256 Kbit/s and 512
Kbit/s for Cell

BSC6900 UMTS

Description

Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
512 Kbit/s and 768
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
768 Kbit/s and 1024
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
Kbit/s for Cell

BSC6900 UMTS

Description

Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
Kbit/s for Cell

10 Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
Kbit/s for Cell

11 Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
Kbit/s for Cell

12 Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
8192 Kbit/s and

13 Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Greater
Than 12288 Kbit/s
for Cell

BSC6900 UMTS

Description
67196092 VS.HSUPA.Golden Number of Times Earlier than

BeChThroughput.0 that Average UL V900R011
Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between 0
for Cell

Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between 32
for Cell

Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between 64
for Cell

Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
256 Kbit/s and 512
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
512 Kbit/s and 768
Kbit/s for Cell

BSC6900 UMTS

Description

Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
768 Kbit/s and 1024
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
Kbit/s for Cell

BSC6900 UMTS

Description

BeChThroughput. that Average UL V900R011
10 Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Greater
Than 4096 Kbit/s for
Cell
67196103 VS.HSUPA.Silver- Number of Times Earlier than

Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between 0
for Cell

Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between 32
for Cell

Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between 64
for Cell

Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
256 Kbit/s and 512
Kbit/s for Cell

BSC6900 UMTS

Description

Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
512 Kbit/s and 768
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
768 Kbit/s and 1024
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
Kbit/s for Cell

BSC6900 UMTS

Description

Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
Kbit/s for Cell

10 Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Greater
Cell
67196114 VS.HSUPA.Copper Number of Times Earlier than

Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between 0
for Cell

Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between 32
for Cell

Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between 64
for Cell

BSC6900 UMTS

Description

Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
256 Kbit/s and 512
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
512 Kbit/s and 768
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
768 Kbit/s and 1024
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
Kbit/s for Cell

BSC6900 UMTS

Description

Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
Kbit/s for Cell

Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
Kbit/s for Cell

10 Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Greater
Cell
73423349 VS.ERACH.Estab. Maximum Service V900R013

MaxTime Setup Duration on an
ERACH for Cell
73441136 VS.ERACH.Estab. Average Service V900R013

MeanTime Setup Duration on an
ERACH for Cell
73423352 VS.ERACH.Estab. Minimum Service V900R013

MinTime Setup Duration on an
ERACH for Cell
73423353 VS.EFACH.Estab. Maximum Service V900R013

MaxTime Setup Duration on an
EFACH for Cell
73441137 VS.EFACH.Estab. Average Service V900R013

MeanTime Setup Duration on an
EFACH for Cell
73423356 VS.EFACH.Estab. Minimum Service V900R013

MinTime Setup Duration on an
EFACH for Cell

BSC6900 UMTS
None
1.12.23.1 Delay of Different Services
Counters
67204785 VS.AMR.Estab.MeanTime Mean Delay Between RRC

Connection Establishment
and AMR RAB
Establishment Completion
for Cell
67195972 VS.AMR.Estab.MaxTime Maximum Delay Between

RRC Connection
Establishment and AMR
RAB Establishment
Completion for Cell
67195973 VS.AMR.Estab.MinTime Minimum Delay Between

RRC Connection
RAB Establishment
Completion for Cell
67195976 VS.CS64.Estab.MaxTime Maximum Delay Between

RRC Connection
Establishment and 64kbit/s
CS RAB Establishment
Completion for Cell
67204786 VS.CS64.Estab.MeanTime Mean Delay Between RRC

and 64kbit/s CS RAB
for Cell
67195977 VS.CS64.Estab.MinTime Minimum Delay Between

RRC Connection
Completion for Cell

BSC6900 UMTS
67195980 VS.PSR99.Estab.MaxTime Maximum Delay Between

RRC Connection
Establishment and PS R99
RAB Establishment
Completion for Cell
67204787 VS.PSR99.Estab.MeanTime Mean Delay Between RRC

and PS R99 RAB
for Cell
67195981 VS.PSR99.Estab.MinTime Minimum Delay Between

RRC Connection
RAB Establishment
Completion for Cell
67195984 VS.HSDPA.Estab.MaxTime Maximum Delay Between

RRC Connection
Establishment and HSDPA
RAB Establishment
Completion for Cell
67204788 VS.HSDPA.Estab.Mean- Mean Delay Between RRC

Time Connection Establishment
and HSDPA RAB
for Cell
67195985 VS.HSDPA.Estab.MinTime Minimum Delay Between

RRC Connection
RAB Establishment
Completion for Cell
67195988 VS.HSUPA.Estab.MaxTime Maximum Delay Between

RRC Connection
Establishment and HSUPA
RAB Establishment
Completion for Cell
67204789 VS.HSUPA.Estab.Mean- Mean Delay Between RRC

Time Connection Establishment
and HSUPA RAB
for Cell

BSC6900 UMTS
67195989 VS.HSUPA.Estab.MinTime Minimum Delay Between

RRC Connection
RAB Establishment
Completion for Cell
specific formulas.
67195974 VS.AMR.Estab.Cum Cumulative Delay Between

RRC Connection
RAB Establishment
Completion for Cell
67195975 VS.AMR.Estab.Sample Number of Samples of

Accumulative Delay
Between RRC Connection
RAB Establishment
Completion for Cell
67195978 VS.CS64.Estab.Cum Cumulative Delay Between

RRC Connection
Completion for Cell
67195979 VS.CS64.Estab.Sample Number of Samples of

Accumulative Delay
Completion for Cell
67195986 VS.HSDPA.Estab.Cum Cumulative Delay Between

RRC Connection
RAB Establishment
Completion for Cell
67195987 VS.HSDPA.Estab.Sample Number of Samples of

Accumulative Delay
RAB Establishment
Completion for Cell

BSC6900 UMTS
67195990 VS.HSUPA.Estab.Cum Cumulative Delay Between

RRC Connection
RAB Establishment
Completion for Cell
67195991 VS.HSUPA.Estab.Sample Number of Samples of

Cumulative Delay Between
RRC Connection
RAB Establishment
Completion for Cell
67195982 VS.PSR99.Estab.Cum Cumulative Delay Between

RRC Connection
RAB Establishment
Completion for Cell
67195983 VS.PSR99.Estab.Sample Number of Samples of

Accumulative Delay
RAB Establishment
Completion for Cell
Description
These counters provide the maximum, average, and minimum durations when services are
established in the best cell based on the CN domain and service type. The durations cover the
time starting from the RRC CONNECTION REQUEST message to the first RAB
ASSIGNMENT RESPONSE message.These counters are not measured when a second or more
RAB are established. For DC-HSUPA users, the corresponding counter is measured only in the
primary cell. The counters VS.AMR.Estab.MeanTime, VS.AMR.Estab.MaxTime and
VS.AMR.Estab.MinTime are measured for narrowband and wideband AMR services.
Measurement point
The measurement is triggered at point A 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.These counters are not
measured when a second or more RAB are established.

BSC6900 UMTS
Figure 1-753 RAB establishment flow
Formula
VS.AMR.Estab.MeanTime = [VS.AMR.Estab.Cum]/[VS.AMR.Estab.Sample]
VS.CS64.Estab.MeanTime = [VS.CS64.Estab.Cum]/[VS.CS64.Estab.Sample]
VS.PSR99.Estab.MeanTime = [VS.PSR99.Estab.Cum]/[VS.PSR99.Estab.Sample]
VS.HSDPA.Estab.MeanTime = [VS.HSDPA.Estab.Cum]/[VS.HSDPA.Estab.Sample]
VS.HSUPA.Estab.MeanTime = [VS.HSUPA.Estab.Cum]/[VS.HSUPA.Estab.Sample]
Unit
ms
Related Features
VS.AMR.Estab.MeanTime WRFD-010501 Conversational QoS Class
VS.AMR.Estab.MaxTime WRFD-010501 Conversational QoS Class
VS.AMR.Estab.MinTime WRFD-010501 Conversational QoS Class
VS.CS64.Estab.MaxTime WRFD-010501 Conversational QoS Class
VS.CS64.Estab.MeanTime WRFD-010501 Conversational QoS Class

BSC6900 UMTS
VS.CS64.Estab.MinTime WRFD-010501 Conversational QoS Class
VS.PSR99.Estab.MaxTime WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.PSR99.Estab.MeanTime WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.PSR99.Estab.MinTime WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.HSDPA.Estab.MaxTime WRFD-01061008 Interactive and Background

HSDPA
VS.HSDPA.Estab.Mean- WRFD-01061008 Interactive and Background

Time WRFD-010630 Traffic Class on HSDPA
HSDPA
VS.HSDPA.Estab.MinTime WRFD-01061008 Interactive and Background

HSDPA
VS.HSUPA.Estab.MaxTime WRFD-01061206 Interactive and Background

HSUPA
VS.HSUPA.Estab.Mean- WRFD-01061206 Interactive and Background

Time WRFD-010632 Traffic Class on HSUPA
HSUPA
VS.HSUPA.Estab.MinTime WRFD-01061206 Interactive and Background

HSUPA

BSC6900 UMTS
1.12.23.2 Counters Related to the Number of Times that DL Throughput of HSDPA

Services Within Each Range
Counters
67196050 VS.HSDPA.GoldenBeCh- Number of Times that

Throughput.0 Average DL Throughput of
MAC-d Flow of HSDPA
Golden BE Services Between
0 Kbit/s and 32 Kbit/s for Cell

MAC-d Flow of HSDPA
32 Kbit/s and 64 Kbit/s for
Cell

MAC-d Flow of HSDPA
Cell

MAC-d Flow of HSDPA
Cell

MAC-d Flow of HSDPA
Cell

MAC-d Flow of HSDPA
768 Kbit/s and 1024 Kbit/s
for Cell

BSC6900 UMTS

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
8192 Kbit/s and 12288 Kbit/
s for Cell

BSC6900 UMTS

MAC-d Flow of HSDPA
Golden BE Services Greater
Than 12288 Kbit/s for Cell
67196064 VS.HSDPA.SilverBeCh- Number of Times that

MAC-d Flow of HSDPA
Silver BE Services Between

MAC-d Flow of HSDPA
Cell

MAC-d Flow of HSDPA
Cell

MAC-d Flow of HSDPA
Cell

MAC-d Flow of HSDPA
Cell

MAC-d Flow of HSDPA
for Cell

BSC6900 UMTS

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
s for Cell

BSC6900 UMTS

MAC-d Flow of HSDPA
Silver BE Services Greater
67196078 VS.HSDPA.CopperBeCh- Number of Times that

MAC-d Flow of HSDPA
Bronze BE Services Between

MAC-d Flow of HSDPA
Cell

MAC-d Flow of HSDPA
Cell

MAC-d Flow of HSDPA
Cell

MAC-d Flow of HSDPA
Cell

MAC-d Flow of HSDPA
for Cell

BSC6900 UMTS

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
for Cell

MAC-d Flow of HSDPA
s for Cell

BSC6900 UMTS

MAC-d Flow of HSDPA
Bronze BE Services Greater
Description
These counters provide the number of times that the average downlink throughput of the MAC-
d flow carrying BE services at the RCL layer falls in the corresponding range based on the level
of the service in an HSDPA serving cell. For DC-HSDPA users, these counters are measured
only in the primary cell based on the total throughput on the primary and secondary carriers.
These counters are measured only when the SPI measure function is activated using the SET
UDPUCFGDATA command with CellCountersMeasOBJCtrlSwitch set to Qos or QosAndSpi.
Measurement point
In an HSDPA serving cell, the RNC takes samples of the average downlink throughput (the RLC
header and retransmitted data are not measured) of the MAC-d flow carrying BE services at the
RLC layer for gold, silver, and copper users every 20 seconds. When the throughput falls in a
predefined range, the corresponding counter is incremented by one. At the end of a measurement
period, the value of each counter is obtained.
Formula
None
Unit
None
Related Features
VS.HSDPA.GoldenBeCh- WRFD-01061008 Interactive and Background

Throughput.0 Traffic Class on HSDPA




BSC6900 UMTS










VS.HSDPA.SilverBeCh- WRFD-01061008 Interactive and Background









BSC6900 UMTS






VS.HSDPA.CopperBeCh- WRFD-01061008 Interactive and Background













BSC6900 UMTS


1.12.23.3 Counters Related to the Number of Times that UL Throughput of HSUPA

Services Within Each Range
Counters
67196092 VS.HSUPA.GoldenBeCh- Number of Times that

Throughput.0 Average UL Throughput of
MAC-d Flow of HSUPA

MAC-d Flow of HSUPA
Cell

MAC-d Flow of HSUPA
Cell

MAC-d Flow of HSUPA
Cell

MAC-d Flow of HSUPA
Cell

BSC6900 UMTS

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
Golden BE Services Greater
67196103 VS.HSUPA.SilverBeCh- Number of Times that

MAC-d Flow of HSUPA

BSC6900 UMTS

MAC-d Flow of HSUPA
Cell

MAC-d Flow of HSUPA
Cell

MAC-d Flow of HSUPA
Cell

MAC-d Flow of HSUPA
Cell

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
for Cell

BSC6900 UMTS

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
Silver BE Services Greater
67196114 VS.HSUPA.CopperBeCh- Number of Times that

MAC-d Flow of HSUPA

MAC-d Flow of HSUPA
Cell

MAC-d Flow of HSUPA
Cell

MAC-d Flow of HSUPA
Cell

BSC6900 UMTS

MAC-d Flow of HSUPA
Cell

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
for Cell

MAC-d Flow of HSUPA
Bronze BE Services Greater

BSC6900 UMTS
Description
These counters provide the number of times that the average UL throughput of the MAC-d flow
of BE services is in each range based on the level of the service in the HSUPA cells in the active
set. The average throughput is reported by the DSP every 20 seconds.For DC-HSUPA users,
this counter is measured only in the primary cell based on the total throughput on the primary
and secondary carriers.The measurement item is measured only when the SPI measure function
is activated using the SET UDPUCFGDATA command with CellCountersMeasOBJCtrlSwitch
set to Qos or QosAndSpi.
Measurement point
In an HSUPA serving cell, the RNC takes samples of the average uplink throughput (the RLC
header and retransmitted data are not measured) of the MAC-d flow carrying BE services at the
RLC layer for gold, silver, and copper users every 20 seconds. When the throughput falls in a
predefined range, the corresponding counter is incremented by one. At the end of a measurement
period, the value of each counter is obtained.
Formula
None
Unit
None
Related Features
VS.HSUPA.GoldenBeCh- WRFD-01061206 Interactive and Background

Throughput.0 Traffic Class on HSUPA








BSC6900 UMTS



VS.HSUPA.SilverBeCh- WRFD-01061206 Interactive and Background











VS.HSUPA.CopperBeCh- WRFD-01061206 Interactive and Background





BSC6900 UMTS







1.12.23.4 Service Setup Duration on an ERACH or EFACH for Cell
Counters
73423349 VS.ERACH.Estab.Max- Maximum Service Setup

Time Duration on an ERACH for
Cell
73441136 VS.ERACH.Estab.Mean- Average Service Setup

Time Duration on an ERACH for
Cell
73423352 VS.ERACH.Estab.MinTime Minimum Service Setup

Duration on an ERACH for
Cell
73423353 VS.EFACH.Estab.MaxTime Maximum Service Setup

Duration on an EFACH for
Cell
73441137 VS.EFACH.Estab.Mean- Average Service Setup

Time Duration on an EFACH for
Cell
73423356 VS.EFACH.Estab.MinTime Minimum Service Setup

Duration on an EFACH for
Cell

BSC6900 UMTS
specific formulas.
73423354 VS.EFACH.Estab.Cum Cumulative Delay Between

RRC Connection
Establishment and EFACH
RAB Establishment
Completion for Cell
73423355 VS.EFACH.Estab.Sample Number of Samples of

RRC Connection
Establishment and EFACH
RAB Establishment
Completion for Cell
73423350 VS.ERACH.Estab.Cum Cumulative Delay Between

RRC Connection
Establishment and ERACH
RAB Establishment
Completion for Cell
73423351 VS.ERACH.Estab.Sample Number of Samples of

RRC Connection
Establishment and ERACH
RAB Establishment
Completion for Cell
Description
These counters provide the durations from the RRC connection setup to the first service setup
on an ERACH or EFACH in the best cell.These counters are not measured when a second or
more RAB are established.
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an RRC
CONNECTION REQUEST message, the RNC records the time T1 at point A. When the RNC
receives from the UE a RADIO BEARER SETUP COMPLETE message and sends a RAB
ASSIGNMENT RESPONSE message to the CN, the RNC records the time T2 at point B.
Assume that delta T is the duration of this service establishment, it is calculated as follows: delta
T = T2-T1. The RNC takes samples of service establishment durations every 5 seconds in a
measurement period. At the end of a measurement period, the RNC obtains the average duration
by dividing the accumulated number by the sampling times. The maximum and minimum
numbers among all sampling points in a measurement period are the maximum and minimum
durations for establishing a service, respectively.

BSC6900 UMTS
Figure 1-754 RAB establishment flow
Formula
VS.ERACH.Estab.MeanTime = [VS.ERACH.Estab.Cum]/[VS.ERACH.Estab.Sample]
VS.EFACH.Estab.MeanTime = [VS.EFACH.Estab.Cum]/[VS.EFACH.Estab.Sample]
Unit
ms
Related Features
VS.ERACH.Estab.Max- WRFD-010701 Uplink Enhanced

Time CELL_FACH
VS.ERACH.Estab.Mean- WRFD-010701 Uplink Enhanced

Time CELL_FACH
VS.ERACH.Estab.MinTime WRFD-010701 Uplink Enhanced

CELL_FACH
VS.EFACH.Estab.MaxTime WRFD-010688 Downlink Enhanced

CELL_FACH
VS.EFACH.Estab.Mean- WRFD-010688 Downlink Enhanced

Time CELL_FACH

BSC6900 UMTS
VS.EFACH.Estab.MinTime WRFD-010688 Downlink Enhanced

CELL_FACH
1.12.24 Measurement of CS RAB assignment setup per cell

(RAB.EstabCS.Cell)
Overview
If DRD is enabled during the RAB setup, the RAB setup measurement is performed on the cell
of RAB setup success.Otherwise,if DRD is enabled after the RAB setup, the RAB setup
measurement is performed on the target cell of DRD first attempt.
The RAB setup procedure is as follows:

BSC6900 UMTS
Figure 1-755 Flow chart of RAB setup

BSC6900 UMTS
A VS.RAB.AttEstabCS.Conv,
VS.RAB.AttEstabCS.Str,
VS.RAB.AttEstabCS.AMR.12.2,
VS.RAB.AttEstCS.AMR.7.95,
VS.RAB.AttEstCS.AMR.4.75,
VS.RAB.AttEstab.AMR,
VS.RAB.AttEstabCS.AMRWB,
VS.RAB.AttEstCS.Conv.64,
VS.HSPA.RAB.AttEstab.CS.Conv,
VS.RAB.AttEstabCS.AMRWB23.85,
VS.RAB.AttEstabCS.Platinum,
VS.RAB.AttEstabCS.Conv.Platinum,
VS.RAB.AttEstabCS.VPLimit,
VS.AttEstabCS.AfterP2F,
VS.AttEstabCS.AfterP2D,
VS.SuccEstabCS.AfterP2F,
VS.SuccEstabCS.AfterP2D,
VS.AttEstabPS.AfterP2F,
VS.AttEstabPS.AfterP2D,
VS.SuccEstabPS.AfterP2F,
VS.SuccEstabPS.AfterP2D

BSC6900 UMTS
B VS.RAB.SuccEstabCS.Conv,
VS.RAB.SuccEstabCS.Str,
VS.RAB.SuccEstabCS.AMR.12.2,
VS.RAB.SuccEstCS.AMR.7.95,
VS.RAB.SuccEstCS.AMR.4.75,
VS.RAB.SuccEstabCS.AMR,
VS.RAB.SuccEstabCS.AMRWB,
VS.RAB.SuccEstCS.Conv.64,
VS.HSPA.RAB.SuccEstab.CS.Conv,
VS.RAB.SuccEstabCS.AMRWB23.85,
VS.RAB.SuccEstabCS.Platinum,
VS.RAB.SuccEstabCS.Conv.Platinum
C VS.RAB.AttEstabCS.Queue
D~G Other counters refer to RAB.EstFailCs.Cell
Counters
Description

CS.Conv Conversational RAB V900R011
Establishment
Requests for Cell

CS.Str Streaming RAB V900R011
Establishment
Requests for Cell

CS.Conv Successful CS V900R011
Conversational RAB
Establishments for
Cell

BSC6900 UMTS

Description

CS.Str Successful CS V900R011
Streaming RAB
Establishments for
Cell

CS.AMR.12.2 12.2kbit/s AMR V900R011
Service RAB
Establishment
Attempts for Cell
67190458 VS.RAB.AttEstCS. Number of CS Earlier than

AMR.7.95 7.95kbit/s AMR V900R011
Service RAB
Establishment
Attempts for Cell

AMR.4.75 4.75kbit/s AMR V900R011
Service RAB
Establishment
Attempts for Cell

CS.AMR.12.2 Successful CS V900R011
12.2kbit/s AMR
Service RAB
Establishments for
Cell
67190462 VS.RAB.SuccEstC Number of Earlier than

S.AMR.7.95 Successful CS V900R011
7.95kbit/s AMR
Service RAB
Establishments for
Cell

S.AMR.4.75 Successful CS V900R011
4.75kbit/s AMR
Service RAB
Establishments for
Cell
67179858 VS.RAB.AttEstab. Number of CS AMR Earlier than

AMR Service RAB V900R011
Establishment
Attempts for Cell

BSC6900 UMTS

Description

CS.AMRWB Wideband AMR V900R011
Service RAB
Establishment
Attempts for Cell

Conv.64 Conversational RAB V900R011
Establishment
Attempts for Cell
(Max DL Bit Rate is
64 kbit/s)

CS.AMR Successful CS AMR V900R011
RAB Establishments
for Cell

CS.AMRWB Successful CS V900R011
Wideband AMR
RAB Establishments
for Cell

S.Conv.64 Successful CS RAB V900R011
Establishments for
Cell (Max DL Bit
Rate is 64 kbit/s)
67196202 VS.HSPA.RAB.Att Number of CS over Earlier than

Estab.CS.Conv HSPA RAB V900R011
Establishment
Attempts for Cell
67196203 VS.HSPA.RAB.Suc Number of Earlier than

cEstab.CS.Conv Successful CS over V900R011
HSPA RAB
Establishments for
Cell
67196232 VS.RAB.AttEstab Number of 64kbit/s Earlier than

CS.VPLimit CS RAB Attempts V900R011
Initiated in Cell
Where 64kbit/s CS
Conversational
Service is Forbidden
for Cell

BSC6900 UMTS

Description
67204853 VS.HSPA.UE.Mea Number of CS over Earlier than

n.CS.Conv.Cell HSPA Users for Cell V900R011
73393916 VS.RAB.AttEstab Number of Queuing V900R012

CS.Queue Attempts Due to
Insufficient
Resource in the CS
RAB Assignment
Establishment
Procedure for Cell
73393918 VS.RAB.Estab.Que Average Duration of V900R012

ueTime.CS a CS Queuing in the
RAB Establishment
Procedure for Cell

CS.Queue Successful CS
Establishment After
Queuing for Cell
73394277 VS.RAB.AttEstab Number of CS V900R012

CS.AMRWB23.85 23.85kbit/s
AMRWB service
RAB establishment
Attempts for cell

AMRWB service
RAB establishment
Attempts for cell

AMRWB service
RAB establishment
Attempts for cell

AMRWB service
RAB establishment
Attempts for cell

AMRWB service
RAB establishment
Attempts for cell

BSC6900 UMTS

Description

AMRWB service
RAB establishment
Attempts for cell

AMRWB service
RAB establishment
Attempts for cell

CS.AMRWB8.85 8.85kbit/s AMRWB
service RAB
establishment
Attempts for cell

service RAB
establishment
Attempts for cell
73394286 VS.RAB.SuccEstab Number of CS V900R012

AMRWB service
RAB successfully
established for cell

AMRWB service
RAB successfully

AMRWB service
RAB successfully

AMRWB service
RAB successfully

BSC6900 UMTS

Description

AMRWB service
RAB successfully

AMRWB service
RAB successfully

AMRWB service
RAB successfully

service RAB
successfully

service RAB
successfully

CS.Platinum Setup Requests for
Platinum UEs for
Cell

CS.Platinum Successful CS RAB
Setups for Platinum
UEs for Cell

CS.Conv.Platinum Setup Requests for
Platinum UEs
Performing
Conversational
Services for Cell

BSC6900 UMTS

Description

CS.Conv.Platinum Successful CS RAB
Setups for Platinum
UEs Performing
Conversational
Services for Cell
73426335 VS.AttEstabCS.Aft Number of CS V900R015

erP2F Service Setup
UEs During State
Transition from
CELL_PCH or
URA_PCH to
CELL_FACH for
Cell
73426336 VS.AttEstabCS.Aft Number of CS V900R015

erP2D Service Setup
UEs During State
Transition from
CELL_PCH or
URA_PCH to
CELL_DCH for Cell
73426337 VS.SuccEstabCS.A Number of V900R015

fterP2F Successful CS
Service Setups
Initiated by UEs
During State
Transition from
CELL_PCH or
URA_PCH to
CELL_FACH for
Cell
73426338 VS.SuccEstabCS.A Number of V900R015

fterP2D Successful CS
Service Setups
Initiated by UEs
During State
Transition from
CELL_PCH or
URA_PCH to
CELL_DCH for Cell

BSC6900 UMTS

Description

CS.CSFB.Redir Setup Requests
Initiated by
Redirection-based
CSFB for Cell

CS.CSFB.Redir Successful CS RAB
Setups Initiated by
Redirection-based
CSFB for Cell

CS.CSFB.PSHO Setup Requests
Initiated by PS-
Handover-based
CSFB for Cell

CS.CSFB.PSHO Successful CS RAB
Setups Initiated by
PS-Handover-based
CSFB for Cell
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

BSC6900 UMTS
Counter Sub Counter
VS.RAB.AttEstabCS.AMRWB VS.RAB.AttEstabCS.AMRWB23.85
VS.RAB.AttEstabCS.AMRWB23.05
VS.RAB.SuccEstabCS.AMRWB VS.RAB.SuccEstabCS.AMRWB23.85
VS.RAB.SuccEstabCS.AMRWB23.05
VS.RAB.AttEstabCS.Platinum VS.RAB.AttEstabCS.Conv.Platinum
VS.RAB.SuccEstabCS.Platinum VS.RAB.SuccEstabCS.Conv.Platinum
1.12.24.1 Number of CS RAB Setup Requests for Different Services
Counters
67179825 VS.RAB.AttEstabCS.Conv Number of CS

Conversational RAB
Establishment Requests for
Cell
67179826 VS.RAB.AttEstabCS.Str Number of CS Streaming

RAB Establishment
Requests for Cell
67190457 VS.RAB.AttEstabCS.AMR. Number of CS 12.2kbit/s

12.2 AMR Service RAB
Cell

BSC6900 UMTS
67190458 VS.RAB.AttEstCS.AMR. Number of CS 7.95kbit/s

Cell
67190460 VS.RAB.AttEstCS.AMR. Number of CS 4.75kbit/s

Cell
67179858 VS.RAB.AttEstab.AMR Number of CS AMR Service

RAB Establishment
Attempts for Cell
67192120 VS.RAB.AttEstabCS.AMR Number of CS Wideband

WB AMR Service RAB
Cell
67179859 VS.RAB.AttEstCS.Conv.64 Number of CS

Conversational RAB
Cell (Max DL Bit Rate is 64
kbit/s)
67196202 VS.HSPA.RAB.AttEstab.C Number of CS over HSPA

S.Conv RAB Establishment
Attempts for Cell
73394277 VS.RAB.AttEstabCS.AMR Number of CS 23.85kbit/s

WB23.85 AMRWB service RAB
establishment Attempts for
cell

cell

cell

cell

BSC6900 UMTS

cell

cell

cell

cell

cell
73425918 VS.RAB.AttEstabCS.Plati- Number of CS RAB Setup

num Requests for Platinum UEs
for Cell
73425920 VS.RAB.AttEstabCS.Conv. Number of CS RAB Setup

Platinum Requests for Platinum UEs
Performing Conversational
Services for Cell
Description
These counters provide the number of CS RABs establishment requests in the best cell according
to the service type or user grade.
Measurement point
RAB ASSIGNMENT REQUEST message from the CN in the CS domain, it measures the
corresponding counter in the best cell according to the type of the service to be set up, user grade,
maximum rate, or channel carrying. The number of CS RAB setup requests for platinum UEs
in the best cells is provided by the VS.RAB.AttEstabCS.Platinum counter.The number of setup
requests for CS conversational service carried on an HSPA channel is provided by the
VS.HSPA.RAB.AttEstab.CS.Conv.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AttEstabCS.Conv WRFD-010501 Conversational QoS Class
VS.RAB.AttEstabCS.Str WRFD-010502 Streaming QoS Class
VS.RAB.AttEstabCS.AMR. WRFD-010501 Conversational QoS Class

12.2
VS.RAB.AttEstCS.AMR. WRFD-010501 Conversational QoS Class

7.95
VS.RAB.AttEstCS.AMR. WRFD-010501 Conversational QoS Class

4.75
VS.RAB.AttEstab.AMR WRFD-010501 Conversational QoS Class

BSC6900 UMTS
VS.RAB.AttEstabCS.AMR WRFD-010613 AMR-WB (Adaptive Multi

WB Rate Wide Band)
VS.RAB.AttEstCS.Conv.64 WRFD-010501 Conversational QoS Class
VS.HSPA.RAB.AttEstab.C WRFD-010619 CS voice over HSPA/HSPA

S.Conv +

WB23.85 Rate Wide Band)








VS.RAB.AttEstabCS.Plati- WRFD-150204 Platinum User Prioritizing

num
VS.RAB.AttEstabCS.Conv. WRFD-150204 Platinum User Prioritizing

Platinum
1.12.24.2 Number of RAB Setup Attempts for VP Services when VP Call Is Limited

BSC6900 UMTS
Counters
67196232 VS.RAB.AttEstabCS.VPLi- Number of 64kbit/s CS RAB

mit Attempts Initiated in Cell
Where 64kbit/s CS
Conversational Service is
Forbidden for Cell
Description
This counter provides the number of RAB setup requests for VP services when the VP call is
limited in the best cell.
Measurement point
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

BSC6900 UMTS
Unit
None
Related Features
VS.RAB.AttEstabCS.VPLi- WRFD-020130 Videophone Service

mit Restriction
1.12.24.3 Number of CS Service Setup Attempts Initiated by UEs During State

Transition from CELL_PCH or URA_PCH to CELL_FACH for Cell
Counters
73426335 VS.AttEstabCS.AfterP2F Number of CS Service Setup

Attempts Initiated by UEs
During State Transition from
CELL_FACH for Cell
73426336 VS.AttEstabCS.AfterP2D Number of CS Service Setup

CELL_DCH for Cell
Description
These counters measure the number of CS service setups initiated by UEs in the CELL_PCH or
URA_PCH state in the best cell.
Measurement point
The measurement is triggered at point A, as shown in the figure. A UE in the CELL_PCH or
URA_PCH state initiates CS services and transitions to another state. After the RNC receives a
RAB ASSIGNMENT REQUEST message from the CS domain of the CN, the RNC calculates
the number of CS service setup attempts in the best cell of the UE based on the UE state.

BSC6900 UMTS
Figure 1-758 RAB setup procedure initiated by UEs in the CELL_PCH or URA_PCH state

RAB ASSIGNMENT REQUEST message from the CS domain of the CN, the RNC calculates
the number of CS service setup attempts in the best cell of the UE based on the UE state.
Figure 1-759 RAB setup procedure initiated by CN RAB assignment requests for UEs in the

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.AttEstabCS.AfterP2F WRFD-010501 Conversational QoS Class

WRFD-010502 Streaming QoS Class
VS.AttEstabCS.AfterP2D WRFD-010501 Conversational QoS Class

1.12.24.4 Number of Successful CS Service Setups Initiated by UEs During State

Counters
73426337 VS.SuccEstabCS.AfterP2F Number of Successful CS

Service Setups Initiated by
UEs During State Transition
from CELL_PCH or
for Cell
73426338 VS.SuccEstabCS.AfterP2D Number of Successful CS

from CELL_PCH or
URA_PCH to CELL_DCH
for Cell
Description
These counters measure the number of CS service setups initiated by UEs in the CELL_PCH or

BSC6900 UMTS
Measurement point
The measurement is triggered at point B, as shown in the figure. A UE in the CELL_PCH or
RAB ASSIGNMENT REQUEST message from the CS domain of the CN and return a RAB
ASSIGNMENT RESPONSE message, the RNC calculates the number of successful CS service
setups in the best cell of the UE based on the UE state.

RAB ASSIGNMENT REQUEST message from the CS domain of the CN and return a RAB
ASSIGNMENT RESPONSE message, the RNC calculates the number of successful CS service

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SuccEstabCS.AfterP2F WRFD-010501 Conversational QoS Class

VS.SuccEstabCS.AfterP2D WRFD-010501 Conversational QoS Class

1.12.24.5 Number of Successful CS RAB Establishments in the Cell for Different

Services

BSC6900 UMTS
Counters

v Conversational RAB
67179828 VS.RAB.SuccEstabCS.Str Number of Successful CS

Streaming RAB
67190461 VS.RAB.SuccEstabCS.AM Number of Successful CS

R.12.2 12.2kbit/s AMR Service
RAB Establishments for Cell
67190462 VS.RAB.SuccEstCS.AMR. Number of Successful CS

7.95 7.95kbit/s AMR Service
67190464 VS.RAB.SuccEstCS.AMR. Number of Successful CS

4.75 4.75kbit/s AMR Service

R AMR RAB Establishments
for Cell

RWB Wideband AMR RAB
67179861 VS.RAB.SuccEstCS.Conv. Number of Successful CS

64 RAB Establishments for Cell
(Max DL Bit Rate is 64 kbit/
s)
67196203 VS.HSPA.RAB.SuccEstab. Number of Successful CS

CS.Conv over HSPA RAB
73394286 VS.RAB.SuccEstabCS.AM Number of CS 23.85kbit/s

RWB23.85 AMRWB service RAB
successfully established for
cell

cell

cell

BSC6900 UMTS

cell

cell

cell

cell

cell

cell
73425919 VS.RAB.SuccEstabCS.Plat- Number of Successful CS

inum RAB Setups for Platinum
UEs for Cell

v.Platinum RAB Setups for Platinum
UEs Performing
Cell
Description
These counters provide the number of CS RABs that are successfully established in the best cell
according to the service type or user grade.
Measurement point
COMPLETE message from the UE, it measures the corresponding counter in the best cell where

BSC6900 UMTS
the UE camps on according to the service type of the RAB, user grade, or maximum rate if the
RAB is for the CS service. The number of successful CS RAB setups for platinum UEs in the
best cells is provided by the VS.RAB.SuccEstabCS.Platinum counter.The number of successful
CS conversational service carried on an HSPA channel is provided by the
VS.HSPA.RAB.SuccEstab.CS.Conv.
Formula
None
Unit
None
Related Features
VS.RAB.SuccEstabCS.Con WRFD-010501 Conversational QoS Class

v
VS.RAB.SuccEstabCS.Str WRFD-010502 Streaming QoS Class
VS.RAB.SuccEstabCS.AM WRFD-010501 Conversational QoS Class

R.12.2

BSC6900 UMTS
VS.RAB.SuccEstCS.AMR. WRFD-010501 Conversational QoS Class

7.95
VS.RAB.SuccEstCS.AMR. WRFD-010501 Conversational QoS Class

4.75
VS.RAB.SuccEstabCS.AM WRFD-010501 Conversational QoS Class

R
VS.RAB.SuccEstabCS.AM WRFD-010613 AMR-WB (Adaptive Multi

RWB Rate Wide Band)
VS.RAB.SuccEstCS.Conv. WRFD-010501 Conversational QoS Class

64
VS.HSPA.RAB.SuccEstab. WRFD-010619 CS voice over HSPA/HSPA

CS.Conv +

RWB23.85 Rate Wide Band)








VS.RAB.SuccEstabCS.Plat- WRFD-150204 Platinum User Prioritizing

inum
VS.RAB.SuccEstabCS.Con WRFD-150204 Platinum User Prioritizing

v.Platinum

BSC6900 UMTS
1.12.24.6 Number of Queuing Attempts Due to Insufficient Resource in the CS RAB

Assignment Establishment Procedure
Counters
73393916 VS.RAB.AttEstabCS.Queue Number of Queuing

Attempts Due to Insufficient
Resource in the CS RAB
Assignment Establishment
Procedure for Cell
Description
This counter provides the queuing attempts initiated by the RNC for the CS service that fails to
be set up due to insufficient cell resources.
Measurement point
During the RAB establishment procedure, the RNC initiates queuing for the CS service if the
cell has insufficient resources for the service. After a period of time, the RNC tries to assign
resources to the service again. The measurement is triggered when the service enters the queue,as
shown of point A in Figure1. The counter is measured in the queued cells.
Figure 1-763 Queue procedure for admission failure during the RAB establishment

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AttEstabCS.Queue WRFD-010505 Queuing and Pre-Emption
1.12.24.7 Number of CS Over HSPA in a Cell
Counters
67204853 VS.HSPA.UE.Mean.CS.Co Number of CS over HSPA

nv.Cell Users for Cell
Description
This counter provides the average number of CS over HSPA users in the serving cell.
Measurement point
The system periodically samples (sampling periodicity is 5 seconds) the number of CS Over
HSPA users. At the end of a statistical period, the system divides the sampling number by the
sum at each sampling point to obtain the average number of CS Over HSPA users during the
period.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.HSPA.UE.Mean.CS.Co WRFD-010619 CS voice over HSPA/HSPA

nv.Cell +
1.12.24.8 Average Duration of a CS Queuing in the RAB Establishment Procedure
Counters
73393918 VS.RAB.Estab.QueueTime. Average Duration of a CS

CS Queuing in the RAB
Establishment Procedure for
Cell
specific formulas.
73393966 VS.RAB.Estab.QueueTime. Duration of RAB queuing in

CS.CUM CS domain during the RAB
assignment in a cell
(Numerator)

CS.SAMPLE CS domain during the RAB
(Denominator)
Description
This counter provides the queuing duration for the queued cells.
Measurement point
During the RAB establishment, the RNC initiates queuing for the CS service if the target cell
does not have sufficient resources. After a certain period of time, the RNC attempts to allocate
resources to the service again. If the service is allocated resources before the related timer expires,
this counter measures the queuing duration of this service in the cell where the corresponding
UE currently camps.

BSC6900 UMTS
Formula
VS.RAB.Estab.QueueTime.CS = [VS.RAB.Estab.QueueTime.CS.CUM]/
[VS.RAB.Estab.QueueTime.CS.SAMPLE]
Unit
s
Related Features
VS.RAB.Estab.QueueTime. WRFD-010505 Queuing and Pre-Emption

CS
1.12.24.9 Number of Successful CS Establishment After Queuing
Counters
73393920 VS.RAB.SuccEstabCS.Que Number of Successful CS

ue Establishment After Queuing
for Cell
Description
This counter provides the number of successful establishment of the CS service after the service
is queued when the RNC initiates queuing for the CS service that fails to be set up due to
insufficient cell resources.
Measurement point
During the RAB establishment procedure, the RNC initiates queuing for the CS service if the
resources to the service again. The measurement is triggered when the service is successfully
set up after it is queued,as shown of point C in Figure1. The counter is measured in the queued
cells.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SuccEstabCS.Que WRFD-010505 Queuing and Pre-Emption

ue
1.12.24.10 Number of CS RAB Setup Requests Initiated by Redirection-based CSFB

for Cell

BSC6900 UMTS
Counters
73426417 VS.RAB.AttEstabCS.CSFB. Number of CS RAB Setup

Redir Requests Initiated by
Redirection-based CSFB for
Cell
Description
This counter measures the number of CS RAB setup requests initiated by redirection-based
CSFB to UMTS from LTE in the best cell. This counter includes the CS RAB setup requests
initiated by the redirection-based CSFB in combined service scenarios. This counter together
with the VS.RAB.SuccEstabCS.CSFB.Redir counter evaluates the RAB setup success rate of
CSFB services on the UMTS network.
Measurement point
The measurement is triggered at point D, as shown in the figure. When the RNC receives from
the CS domain of the CN a RAB ASSIGNMENT REQUEST message, requesting the
establishment of a conversational service, this counter is increased by one in the best cell of the
UE if the RRC CONNECTION REQUEST message sent by the same UE carries the CSFB
Indication IE. This counter calculates only the first CS RAB setup in the CSFB procedure.

BSC6900 UMTS
Figure 1-765 RAB assignment setup procedure
Formula
None
Unit
None
Related Features
None
1.12.24.11 Number of Successful CS RAB Setups Initiated by Redirection-based

CSFB for Cell

BSC6900 UMTS
Counters
73426418 VS.RAB.SuccEstabCS.CSF Number of Successful CS

B.Redir RAB Setups Initiated by
Redirection-based CSFB for
Cell
Description
This counter measures the number of successful CS RAB setups initiated by redirection-based
CSFB to UMTS from LTE in the best cell. This counter includes the CS RAB setups initiated
by the redirection-based CSFB in combined service scenarios. This counter together with the
VS.RAB.AttEstabCS.CSFB.Redir counter evaluates the RAB setup success rate of CSFB
services on the UMTS network.
Measurement point
The measurement is triggered at point E, as shown in the figure. When the RNC receives a
RADIO BEARER SETUP COMPLETE message from a UE and sends a RAB ASSIGNMENT
RESPONSE message to the CN, this counter is increased by one in the best cell of the UE if a
CS conversational service is established and the RRC CONNECTION REQUEST message sent
by the UE carries the CSFB Indication IE. This counter calculates only the first CS RAB setup
in the CSFB procedure.

BSC6900 UMTS
Figure 1-766 RAB assignment setup procedure
Formula
None
Unit
None
Related Features
None
1.12.24.12 Number of CS RAB Setup Requests Initiated by PS-Handover-based

CSFB for Cell

BSC6900 UMTS
Counters
73426419 VS.RAB.AttEstabCS.CSFB. Number of CS RAB Setup

PSHO Requests Initiated by PS-
Handover-based CSFB for
Cell
Description
This counter measures the number of CS RAB setup requests initiated by PS-handover-based
CSFB to UMTS from LTE in the best cell. This counter applies only to combined services.
This counter calculates only the first CS RAB setup in the CSFB procedure.
Measurement point
The measurement is triggered at point E, as shown in the figure. When the RNC receives from
the CS domain of the CN a RAB ASSIGNMENT REQUEST message, requesting the
establishment of a conversational service, this counter is increased by one in the best cell of the
UE if the CSFB Information IE contained in the Source RNC to Target RNC Transparent
Container IE or Cause IE is "CS Fallback triggered (268)" in the RELOCATION REQUEST
message.This counter calculates only the first CS RAB setup in the CSFB procedure.

BSC6900 UMTS
Figure 1-767 CS RAB setup procedure initiated by PS-handover-based CSFB
Formula
None
Unit
None
Related Features
None
1.12.24.13 Number of Successful CS RAB Setups Initiated by PS-Handover-based

CSFB for Cell

BSC6900 UMTS
Counters
73426420 VS.RAB.SuccEstabCS.CSF Number of Successful CS

B.PSHO RAB Setups Initiated by PS-
Handover-based CSFB for
Cell
Description
This counter measures the number of successful CS RAB setups initiated by PS-handover-based
CSFB to UMTS from LTE in the best cell. This counter applies only to combined services.
This counter calculates only the first CS RAB setup in the CSFB procedure.
Measurement point
The measurement is triggered at point F, as shown in the figure. When the RNC receives a
RADIO BEARER SETUP COMPLETE message from a UE and sends a RAB ASSIGNMENT
RESPONSE message to the CN, this counter is increased by one in the best cell of the UE if a
CS conversational service is established and the CSFB Information IE contained in the Source
RNC to Target RNC Transparent Container IE or Cause IE is "CS Fallback triggered (268)" in
the RELOCATION REQUEST. This counter calculates only the first CS RAB setup in the CSFB
procedure.

BSC6900 UMTS
Figure 1-768 CS RAB setup procedure initiated by PS-handover-based CSFB
Formula
None
Unit
None
Related Features
None

BSC6900 UMTS
1.12.25 Measurement of PS RAB assignment setup per cell

(RAB.EstabPS.Cell)
Overview
The RAB setup procedure is as follows.

BSC6900 UMTS

BSC6900 UMTS
A VS.RAB.AttEstabPS.Conv,
VS.RAB.AttEstabPS.Str,
VS.RAB.AttEstabPS.Int,
VS.RAB.AttEstabPS.Bkg,
VS.RAB.AttEstab.PSR99,
VS.RAB.AttEstabPS.PTT,
VS.RAB.AttEstabPS.Free,
VS.RAB.AttEstabPS.Conv.Platinum,
VS.RAB.AttEstabPS.Platinum
B VS.RAB.SuccEstabPS.Conv,
VS.RAB.SuccEstabPS.Str,
VS.RAB.SuccEstabPS.Int,
VS.RAB.SuccEstabPS.Bkg,
VS.RAB.SuccEstab.PSR99,
VS.RAB.SuccEstabPS.PTT,
VS.RAB.SuccEstabPS.Free,
VS.RAB.SuccEstabPS.Platinum,
VS.RAB.SuccEstabPS.Conv.Platinum,
VS.RAB.SuccEstabPS.0kbps
C VS.RAB.AttEstabPS.Queue
D~G See:RAB.EstFailPs.Cell
Counters
Description

S.Bkg Background RAB V900R011
Establishment
Attempts for Cell

S.Conv Conversational RAB V900R011
Establishment
Attempts for Cell

S.Int Interactive RAB V900R011
Establishment
Attempts for Cell

BSC6900 UMTS

Description

S.Str Streaming RAB V900R011
Establishment
Attempts for Cell

PS.Bkg Successful PS V900R011
Background RAB
Establishments for
Cell

PS.Conv Successful PS V900R011
Conversational RAB
Establishments for
Cell

PS.Int Successful PS V900R011
Interactive RAB
Establishments for
Cell

PS.Str Successful PS V900R011
Streaming RAB
Establishments for
Cell
67196301 VS.RAB.SuccEs- Number of PS RABs Earlier than

tabPS.0kbps Established V900R011
Successfully at 0
kbit/s in the Best Cell
73403808 VS.RAB.SuccEstab Number of PS R99 V900R012

.PSR99 RAB successfully
73403809 VS.RAB.AttEstab. Number of PS R99 V900R012

PSR99 RAB establishment
Attempts for cell
73393917 VS.RAB.AttEstabP Number of Queuing V900R012

S.Queue Attempts Due to
Insufficient
Resource in the PS
RAB Assignment
Establishment
Procedure for Cell

BSC6900 UMTS

Description
73393919 VS.RAB.Estab.Que Average Duration of V900R012

ueTime.PS a PS Queuing in the
RAB Establishment
Procedure for Cell

PS.Queue Successful PS
Establishment After
Queuing for Cell

PS.PTT Successful PTT
Service
Establishments for
Cell
73394076 VS.RAB.AttEstabP Number of PTT V900R012

S.PTT Service
Establishment
Attempts for Cell
73423517 VS.RAB.AttEstabP Number of PS Free V900R013

S.Free RAB Setup Attempts
for Cell

PS.Free Successful PS Free
RAB Setups for Cell

PS.Platinum Successful PS RAB
Setups for Platinum
UEs for Cell

S.Conv.Platinum Setup Requests for
Platinum UEs
Performing
Conversational
Services for Cell

PS.Conv.Platinum Successful PS RAB
Setups for Platinum
UEs Performing
Conversational
Services for Cell

BSC6900 UMTS

Description

S.Platinum Setup Requests for
Platinum UEs for
Cell
73426339 VS.AttEstabPS.Aft Number of PS V900R015

erP2F Service Setup
UEs During State
Transition from
CELL_PCH or
URA_PCH to
CELL_FACH for
Cell
73426340 VS.AttEstabPS.Aft Number of PS V900R015

erP2D Service Setup
UEs During State
Transition from
CELL_PCH or
URA_PCH to
CELL_DCH for Cell
73426341 VS.SuccEstabPS.A Number of V900R015

fterP2F Successful PS
Service Setups
Initiated by UEs
During State
Transition from
CELL_PCH or
URA_PCH to
CELL_FACH for
Cell
73426342 VS.SuccEstabPS.A Number of V900R015

fterP2D Successful PS
Service Setups
Initiated by UEs
During State
Transition from
CELL_PCH or
URA_PCH to
CELL_DCH for Cell

BSC6900 UMTS
Counter Sub Counter
VS.RAB.AttEstabPS.Platinum VS.RAB.AttEstabPS.Conv.Platinum
VS.RAB.SuccEstabPS.Platinum VS.RAB.SuccEstabPS.Conv.Platinum
1.12.25.1 Number of PS RAB Setup Requests for Different Services
Counters
67179921 VS.RAB.AttEstabPS.Conv Number of PS

Conversational RAB
Cell
67179924 VS.RAB.AttEstabPS.Bkg Number of PS Background

RAB Establishment
Attempts for Cell
67179923 VS.RAB.AttEstabPS.Int Number of PS Interactive

RAB Establishment
Attempts for Cell
67179922 VS.RAB.AttEstabPS.Str Number of PS Streaming

RAB Establishment
Attempts for Cell
73403809 VS.RAB.AttEstab.PSR99 Number of PS R99 RAB

cell
73394076 VS.RAB.AttEstabPS.PTT Number of PTT Service

Cell
73423517 VS.RAB.AttEstabPS.Free Number of PS Free RAB

Setup Attempts for Cell
73425924 VS.RAB.AttEstabPS.Conv. Number of PS RAB Setup

Platinum Requests for Platinum UEs
Performing Conversational
Services for Cell
73425922 VS.RAB.AttEstabPS.Plati- Number of PS RAB Setup

num Requests for Platinum UEs
for Cell

BSC6900 UMTS
Description
These counters provide the number of PS RABs that are requested to be set up in the best cell
according to the service type, user grade, or traffic channel type.
Measurement point
ASSIGNMENT REQUEST message from the CN in the PS domain, it measures the
corresponding counter in the best cell that the UE camps on based on the service type, user grade,
or traffic channel type. The number of PS RABs that are requested to be set up for platinum UEs
in the best cells is provided by the VS.RAB.AttEstabPS.Platinum. The number of RABs that
are requested to be set up for PS R99 services carried by a specific traffic channel in the best
cell is provided by the VS.RAB.AttEstab.PSR99 counter. The number of PS free RABs that are
requested to be set up in the best cell is provided by the VS.RAB.AttEstabPS.Free counter. This
counter is measured only when the special handling for free access user algorithm is enabled.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RAB.AttEstabPS.Conv WRFD-010501 Conversational QoS Class
VS.RAB.AttEstabPS.Bkg WRFD-010504 Background QoS Class
VS.RAB.AttEstabPS.Int WRFD-010503 Interactive QoS Class
VS.RAB.AttEstabPS.Str WRFD-010502 Streaming QoS Class
VS.RAB.AttEstab.PSR99 WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AttEstabPS.PTT WRFD-020134 Push to Talk
VS.RAB.AttEstabPS.Free WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AttEstabPS.Conv. WRFD-150204 Platinum User Prioritizing

Platinum
VS.RAB.AttEstabPS.Plati- WRFD-150204 Platinum User Prioritizing

num
1.12.25.2 Number of PS RABs Successfully Set Up in a Cell for Different Services
Counters

Conversational RAB
67179928 VS.RAB.SuccEstabPS.Bkg Number of Successful PS

Background RAB
67179927 VS.RAB.SuccEstabPS.Int Number of Successful PS

Interactive RAB
67179926 VS.RAB.SuccEstabPS.Str Number of Successful PS

Streaming RAB

BSC6900 UMTS
73403808 VS.RAB.SuccEstab.PSR99 Number of PS R99 RAB

cell
73394075 VS.RAB.SuccEstabPS.PTT Number of Successful PTT

Service Establishments for
Cell
73423518 VS.RAB.SuccEstabPS.Free Number of Successful PS

Free RAB Setups for Cell
73425923 VS.RAB.SuccEstabPS.Plati- Number of Successful PS

num RAB Setups for Platinum
UEs for Cell

.Platinum RAB Setups for Platinum
UEs Performing
Cell
Description
These counters provide the number of PS RABs that are successfully established in the best cell
according to the service type, user grade, and traffic channel type.
Measurement point
COMPLETE message from the UE, it measures the corresponding counter based on the service
type of the RAB, user grade, or traffic channel carrying the RAB in the best cell where the UE
camps on if the RAB is for the PS service. The number of PS RABs that are successfully set up
for platinum UEs in the best cells is provided by the VS.RAB.SuccEstabPS.Platinum counter.
The number of successful RABs that are successfully set up for PS R99 services in a specific
traffic channel in the best cells is provided by the VS.RAB.SuccEstab.PSR99 counter. The
number of PS free RABs that are successfully set up in the best cells is provided by the
VS.RAB.AttEstabPS.Free counter. This counter is measured only when the special handling for
free access user algorithm is enabled.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SuccEstabPS.Bkg WRFD-010504 Background QoS Class
VS.RAB.SuccEstabPS.Int WRFD-010503 Interactive QoS Class
VS.RAB.SuccEstabPS.Str WRFD-010502 Streaming QoS Class
VS.RAB.SuccEstab.PSR99 WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.SuccEstabPS.PTT WRFD-020134 Push to Talk

BSC6900 UMTS
VS.RAB.SuccEstabPS.Free WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.SuccEstabPS.Plati- WRFD-150204 Platinum User Prioritizing

num
VS.RAB.SuccEstabPS.Conv WRFD-150204 Platinum User Prioritizing

.Platinum
1.12.25.3 Number of PS RABs Set Up Successfully at 0 Kbit/s
Counters
67196301 VS.RAB.SuccEstabPS. Number of PS RABs

0kbps Established Successfully at 0
kbit/s in the Best Cell
Description
This counter provides the number of times that an UE access the network successfully through
the 0 Kbit/s RAB in the best cell during the procedures of RAB establishment, RAB
modification, cell update, relocation (UE involved) and hard handover.
Measurement point
The measurement is triggered at point A as shown in the following figure 1. During a RAB setup
procedure, when the RNC receives a RADIO BEARER SETUP COMPLETE message from
UE, it measures this counter in the best cell if any of the following conditions is met: 1.The rate
of the RAB is 0 Kbit/s. 2.The existing PS service rate is reconfigured as 0 kbit/s because the UE
establishes a CS service.

BSC6900 UMTS
The measurement is triggered at point A as shown in the following figure 2. During a RAB
modification procedure, when the RNC receives a RADIO BEARER RECONFIGURATION
COMPLETE message from UE, it measures this counter in the best cell if the rate of the RAB
is 0 Kbit/s.
The measurement is triggered at point A as shown in the following figure 3. During a P2D
procedure, when the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE
message from UE, it measures this counter in the best cell if the rate of the RAB is 0 Kbit/s.
Figure 1-774 P2D procedure
The measurement is triggered at point A as shown in the following figure 4. During a relocation
(UE involved) procedure, when the RNC sends a RELOCATION COMPLETE message to CN,
it measures this counter in the best cell if the rate of the RAB is 0 Kbit/s.

BSC6900 UMTS
Figure 1-775 relocation (UE involved) procedure
The measurement is triggered at point A as shown in the following figure 5. During a hard
handover procedure, when the RNC receives a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from UE, it measures this counter in the best cell if the rate of the RAB
is 0 Kbit/s.
Figure 1-776 hard handover procedure
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.RAB.SuccEstabPS. WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

0kbps Connection and Radio
and Release
1.12.25.4 Number of Queuing Attempts Due to Insufficient Resource in the PS RAB

Assignment Establishment Procedure
Counters
73393917 VS.RAB.AttEstabPS.Queue Number of Queuing

Attempts Due to Insufficient
Resource in the PS RAB
Assignment Establishment
Procedure for Cell
Description
This counter provides the queuing attempts initiated by the RNC for the PS service that fails to
be set up due to insufficient cell resources.
Measurement point
During the RAB establishment procedure, the RNC initiates queuing for the PS service if the
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AttEstabPS.Queue WRFD-010505 Queuing and Pre-Emption
1.12.25.5 Average Duration of a PS Queuing in the RAB Establishment Procedure

BSC6900 UMTS
Counters
73393919 VS.RAB.Estab.QueueTime. Average Duration of a PS

PS Queuing in the RAB
Establishment Procedure for
Cell
specific formulas.

PS.CUM PS domain during the RAB
(Numerator)

PS.SAMPLE PS domain during the RAB
(Denominator)
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
resources to the service again. If the service is allocated resources before the related timer expires,
this counter measures the queuing duration of this service in the cell where the corresponding
UE currently camps.
Formula
VS.RAB.Estab.QueueTime.PS = [VS.RAB.Estab.QueueTime.PS.CUM]/
[VS.RAB.Estab.QueueTime.PS.SAMPLE]
Unit
s

BSC6900 UMTS
Related Features
VS.RAB.Estab.QueueTime. WRFD-010505 Queuing and Pre-Emption

PS
1.12.25.6 Number of Successful PS Establishment After Queuing
Counters
73393921 VS.RAB.SuccEstabPS.Queu Number of Successful PS

e Establishment After Queuing
for Cell
Description
This counter provides the number of successful establishment of the PS service after the service
is queued when the RNC initiates queuing for the PS service that fails to be set up due to
insufficient cell resources.
Measurement point
resources to the service again. The measurement is triggered when the service is successfully
set up after it is queued,as shown of point C in Figure1. The counter is measured in the queued
cells.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SuccEstabPS.Queu WRFD-010505 Queuing and Pre-Emption

e
1.12.25.7 Number of PS Service Setup Attempts Initiated by UEs During State


BSC6900 UMTS
Counters
73426339 VS.AttEstabPS.AfterP2F Number of PS Service Setup

CELL_FACH for Cell
73426340 VS.AttEstabPS.AfterP2D Number of PS Service Setup

CELL_DCH for Cell
Description
These counters measure the number of PS service setups initiated by UEs in the CELL_PCH or
Measurement point
URA_PCH state initiates PS services and transitions to another state. After the RNC receives a
RAB ASSIGNMENT REQUEST message from the PS domain of the CN, the RNC calculates
the number of PS service setups in the best cell of the UE based on the UE state.

BSC6900 UMTS

RAB ASSIGNMENT REQUEST message from the PS domain of the CN, the RNC calculates
the number of PS service setups in the best cell of the UE based on the UE state.
Formula
None
Unit
None
Related Features
VS.AttEstabPS.AfterP2F WRFD-010501 Conversational QoS Class

VS.AttEstabPS.AfterP2D WRFD-010501 Conversational QoS Class


BSC6900 UMTS
1.12.25.8 Number of Successful PS Service Setups Initiated by UEs During State

Counters
73426341 VS.SuccEstabPS.AfterP2F Number of Successful PS

from CELL_PCH or
for Cell
73426342 VS.SuccEstabPS.AfterP2D Number of Successful PS

from CELL_PCH or
URA_PCH to CELL_DCH
for Cell
Description
These counters measure the number of successful PS service setups initiated by UEs in the
CELL_PCH or URA_PCH state in the best cell.
Measurement point
RAB ASSIGNMENT REQUEST message from the PS domain of the CN and return a RAB
ASSIGNMENT RESPONSE message, the RNC calculates the number of successful PS service

BSC6900 UMTS

RAB ASSIGNMENT REQUEST message from the PS domain of the CN and return a RAB
ASSIGNMENT RESPONSE message, the RNC calculates the number of successful PS service

BSC6900 UMTS
Figure 1-782 RAB setup procedure initiated by CN RAB assignment request for UEs in the
Formula
None
Unit
None
Related Features
VS.SuccEstabPS.AfterP2F WRFD-010501 Conversational QoS Class

WRFD-010503 Interactive QoS Class
WRFD-010504 Background QoS Class
VS.SuccEstabPS.AfterP2D WRFD-010501 Conversational QoS Class

WRFD-010503 Interactive QoS Class
WRFD-010504 Background QoS Class

BSC6900 UMTS
1.12.26 Measurement of CS RAB assignment failure per cell

(RAB.EstFailCs.Cell)
Overview
The RAB setup procedure is as follows:

BSC6900 UMTS

BSC6900 UMTS
A~B See:RAB.EstabCS.Cell
C 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.Unsp
D VS.RAB.FailEstabCS.TNL
E VS.RAB.FailEstabCS.IubFail
F VS.RAB.FailEstabCS.UuFail,
VS.RAB.FailEstabCS.RBIncCfg,
VS.RAB.FailEstabCS.RBCfgUnsup,
VS.RAB.FailEstabCS.UuNoReply,
VS.RAB.FailEstabCS.PhyChFail,
VS.RAB.FailEstabCS.SRBReset,
VS.RAB.FailEstabCS.CellUpd
G VS.RAB.FailEstabCS.RNL
Counters
Description
67189494 VS.RAB.FailEstab Number of Failed CS Earlier than

CS.Cong RAB Establishments V900R011

CS.RNL RAB Establishments V900R011
for Cell (Radio
Network Layer
Cause)

BSC6900 UMTS

Description

CS.TNL RAB Establishments V900R011
for Cell
(Transmission
Network Layer
Cause)

CS.DLIUBBand.C RAB Establishments V900R011
ong for Cell (DL Iub
Bandwidth
Congestion)

CS.ULIUBBand.C RAB Establishments V900R011
ong for Cell (UL Iub
Bandwidth
Congestion)

CS.ULCE.Cong RAB Establishments V900R011
for Cell (UL CE
Congestion)

CS.DLCE.Cong RAB Establishments V900R011
for Cell (DL CE
Congestion)

CS.Code.Cong RAB Establishments V900R011
for Cell (Code
Congestion)
67193536 VS.RAB.FailEstab Number of Failed CS V900R012

CS.RBIncCfg RAB Establishments
for Cell(Invalid
configuration of UE
during the RB setup
procedure)

CS.RBCfgUnsup RAB Establishments
for Cell
(Configuration
unsupported of UE
during the RB setup
procedure)

BSC6900 UMTS

Description

CS.UuNoReply RAB Establishments
for Cell(No reply of
UE during the RB
setup procedure)

CS.PhyChFail RAB Establishments
for Cell(Physical
channel failure of UE
during the RB setup
procedure)

CS.ULPower.Cong RAB Establishments
for Cell (UL Power
Congestion)

CS.DLPower.Cong RAB Establishments
for Cell (DL Power
Congestion)

CS.IubFail RAB Establishments
for cell (Radio Link
Configuration
Failure)

CS.UuFail RAB Establishments
for cell (Uu Interface
Configuration
Failure)

CS.Unsp RAB Establishments V900R011
for Cell
(Unsupported
Capabilities)

CS.SRBReset RAB Establishments
for Cell (Signaling
RLC Reset)

CS.CellUpd RAB Establishments
for Cell (Concurrent
Procedures)

BSC6900 UMTS
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.UuFail
VS.RAB.FailEstabCS.SRBReset
VS.RAB.FailEstabCS.CellUpd
VS.RAB.FailEstabCS.UuFail VS.RAB.FailEstabCS.RBIncCfg
VS.RAB.FailEstabCS.RBCfgUnsup
VS.RAB.FailEstabCS.UuNoReply
VS.RAB.FailEstabCS.PhyChFail
1.12.26.1 Number of CS RABs Unsuccessfully Established due to Congestion
Counters
67189494 VS.RAB.FailEstabCS.Cong Number of Failed CS RAB

(Congestion)

BSC6900 UMTS
67192610 VS.RAB.FailEstabCS.DLIU Number of Failed CS RAB

BBand.Cong Establishments for Cell (DL
Iub Bandwidth Congestion)
67192611 VS.RAB.FailEstabCS.ULIU Number of Failed CS RAB

BBand.Cong Establishments for Cell (UL
67190406 VS.RAB.FailEstabCS.ULC Number of Failed CS RAB

E.Cong Establishments for Cell (UL
CE Congestion)
67190407 VS.RAB.FailEstabCS.DLC Number of Failed CS RAB

E.Cong Establishments for Cell (DL
CE Congestion)
67179864 VS.RAB.FailEstabCS.Code. Number of Failed CS RAB

Cong Establishments for Cell
(Code Congestion)
67193611 VS.RAB.FailEstabCS.ULPo Number of Failed CS RAB

wer.Cong Establishments for Cell (UL
Power Congestion)
67193612 VS.RAB.FailEstabCS.DLPo Number of Failed CS RAB

wer.Cong Establishments for Cell (DL
Power Congestion)
Description
These counters provide the number of failed CS RAB establishments due to congestion in the
best cell according to the congestion cause. If congestion occurs both in the uplink and downlink,
the counter is measured only in the downlink. For example, when CS RABs fail to be set up due
to congestion in both the uplink and downlink power resources, the RNC measures only the
VS.RAB.FailEstabCS.DLPower.Cong counter. For example, if CS RABs fail to be set up due
to congestion in Iub uplink and downlink bandwidth (admission bandwidth), the RNC measures
only the VS.RAB.FailEstabCS.DLIUBBand.Cong counter.
Measurement point
The measurement is triggered at point B as shown in the figure. After receiving from the CN an
RAB ASSIGNMENT REQUEST message that contains the RAB to be set up, the RNC applies
for corresponding radio resources. If the application fails, the RAB setup fails and the RNC
sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails
and the failure cause is any of the following: "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 this counter based on the
specific cause in the best cell that the UE camps on.

BSC6900 UMTS
Figure 1-784 RAB setup procedure (failed operation)
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabCS.Cong WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.FailEstabCS.DLIU WRFD-020101 Admission Control

BBand.Cong WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release

BSC6900 UMTS
VS.RAB.FailEstabCS.ULIU WRFD-020101 Admission Control

and Release
VS.RAB.FailEstabCS.ULC WRFD-020101 Admission Control

E.Cong WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabCS.DLC WRFD-020101 Admission Control

and Release
VS.RAB.FailEstabCS.Code. WRFD-020101 Admission Control

Cong WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabCS.ULPo WRFD-020101 Admission Control

wer.Cong WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabCS.DLPo WRFD-020101 Admission Control

and Release
1.12.26.2 Number of Failed CS RABs due to Unsupported Capabilities (Cell)
Counters
67179830 VS.RAB.FailEstabCS.Unsp Number of Failed CS RAB

(Unsupported Capabilities)

BSC6900 UMTS
Description
This measurement item provides the number of failed CS RABs due to unsupported capabilities
in the best cell.
Measurement point
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
Rate for UL not Available","Requested Guaranteed Bit Rate not Available","Requested
Guaranteed Bit Rate for DL not Available","Requested Guaranteed Bit Rate for UL not
Available","No Radio Resources Available in Target cell","Requested Transfer Delay not
Achievable","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

BSC6900 UMTS
Related Features
VS.RAB.FailEstabCS.Unsp WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.26.3 Number of CS RABs Unsuccessfully Established due to Transport

Network Layer Cause
Counters
67189496 VS.RAB.FailEstabCS.TNL Number of Failed CS RAB

(Transmission Network
Layer Cause)
Description
This measurement item provides the number of CS RABs unsuccessfully established due to
transport connection setup failure on the Iu-CS interface in the best cell.
Measurement point
a RAB ASSIGNMENT RESPONSE message with the failure cause of "Signalling Transport
Resource Failure" or "Iu-CS Interface Transport Connection Failed to Establish", indicating that
the RAB unsuccessfully established, this counter is measured in the best cell that the UE camps
on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabCS.TNL WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.26.4 Number of Failed CS RAB Establishments Due to Radio Link

Configuration Failure

BSC6900 UMTS
Counters
73393835 VS.RAB.FailEstabCS.Iub- Number of Failed CS RAB

Fail Establishments for cell
(Radio Link Configuration
Failure)
Description
This counter provides the number of times RAB assignment fails in the CS domain when radio
link configuration fails (because a timeout occurs in the wait for the NodeB to respond or the
NodeB responds with a radio link configuration failure message) in the best cell or when a
timeout occurs in the wait for a RADIO LINK RESTORE INDICATION message after a
RADIO LINK FAIL INDICATION message is received from the NodeB.
Measurement point
Using 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 SSIGNMENT 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 if the
RNC receives from the NodeB a RADIO LINK RECONFIGURATION FAILURE message
(see section 9.2.1.6 in 3GPP TS 25.433 for the failure cause). Note that if the radio link
configuration fails due to CE resource insufficiency, this counter is not measured in the cell,
instead, a congestion counter is measured.
Figure 1-787 Failed RAB establishments due to radio link configuration failure


BSC6900 UMTS
CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request, it

timer for the RNC to wait for a RADIO LINK RECONFIGURATION READY message from
the NodeB expires.
Take the RADIO LINK RECONFIGURATION PREPARE message as an example, the

CN a RAB ASSIGNMENT REQUEST message that contains a RAB establishment request, it
requests related radio resources and triggers a radio link reconfiguration procedure (or radio link
establishment procedure). After the RNC sends the NodeB a RADIO LINK
RECONFIGURATION COMMIT message and then receives a RADIO LINK FAILURE
INDICATION message from the NodeB, the RNC starts a timer to wait for a RADIO LINK
RESTORE INDICATION message from the NodeB. This counter is measured in the best cell
that the UE camps on when a RADIO LINK RESTORE INDICATION message is not received
before the timer expires.

BSC6900 UMTS
Figure 1-789 Timeout for a RADIO LINK RESTORE INDICATION message after receiving
a RADIO LINK FAILURE INDICATION message
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabCS.Iub- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Fail Connection and Radio
and Release
1.12.26.5 Number of CS RABs Unsuccessfully Established due to Different Reasons

of UE During the RB Setup Procedure for Cell

BSC6900 UMTS
Counters
67193536 VS.RAB.FailEstabCS.RBIn Number of Failed CS RAB

cCfg Establishments for Cell
(Invalid configuration of UE
during the RB setup
procedure)
67193537 VS.RAB.FailEstabCS.RBCf Number of Failed CS RAB

gUnsup Establishments for Cell
(Configuration unsupported
of UE during the RB setup
procedure)
67193539 VS.RAB.FailEstabCS.Uu- Number of Failed CS RAB

NoReply Establishments for Cell(No
reply of UE during the RB
setup procedure)
67193538 VS.RAB.FailEstabCS.PhyC Number of Failed CS RAB

hFail Establishments for Cell
(Physical channel failure of
UE during the RB setup
procedure)
73393836 VS.RAB.FailEstabCS.Uu- Number of Failed CS RAB

Fail Establishments for cell (Uu
Interface Configuration
Failure)
Description
The messurement items provide the number of CS RABs unsuccessfully established due to
different reason of UE during the RB setup procedure in the best cell.
VS.RAB.FailEstabCS.RBIncCfg Number of CS RABs Unsuccessfully

Established due to invalid configuration of
UE during the RB Setup Procedure
VS.RAB.FailEstabCS.RBCfgUnsup Number of CS RABs Unsuccessfully

Established due to configuration unsupported
of UE During the RB Setup Procedure
VS.RAB.FailEstabCS.UuNoReply Number of CS RABs Unsuccessfully

Established due to no reply during the RB
Setup Procedure

BSC6900 UMTS
VS.RAB.FailEstabCS.PhyChFail Number of CS RABs Unsuccessfully

Established due to physical channel failure of
VS.RAB.FailEstabCS.UuFail Number of CS RABs Unsuccessfully

Established due to UE configuration failures
(no response is received from the UE or the
UE sends a RADIO BEARER SETUP
FAILURE message) on the Uu interface
during the RB setup procedure
For details about the failure causes for the
message, see section 10.3.3.14 in 3GPP TS
25.331.
Measurement point
RAB ASSIGNMENT RESPONSE message indicating that the operation fails, the RNC
measures the VS.RAB.FailEstabCS.RBIncCfg, VS.RAB.FailEstabCS.RBCfgUnsupp,
VS.RAB.FailEstabCS.PhyChFail, and VS.RAB.FailEstabCS.UuFail counters in the best cell
that the UE camps on based on the failure causes contained in the RADIO BEARER SETUP
FAILURE message.

BSC6900 UMTS
measures the VS.RAB.FailEstabCS.UuNoReply and VS.RAB.FailEstabCS.UuFail counters in
the best cell that the UE camps on in the scenarios where the RAB setup fails because the timer
for the RNC to wait for the RADIO BEARER SETUP COMPLETE message from the UE
expires during the RB setup procedure.
Figure 1-791 RAB setup procedure (UE response timeouts)
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabCS.RBIn WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

cCfg Connection and Radio
and Release

BSC6900 UMTS
VS.RAB.FailEstabCS.RBCf WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

gUnsup Connection and Radio
and Release
VS.RAB.FailEstabCS.Uu- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

NoReply Connection and Radio
and Release
VS.RAB.FailEstabCS.PhyC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

hFail Connection and Radio
and Release
VS.RAB.FailEstabCS.Uu- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.26.6 Number of Failed RAB Establishments for Cell (Signaling RLC Reset)
Counters
73424884 VS.RAB.FailEstabCS.SRB Number of Failed CS RAB

Reset Establishments for Cell
(Signaling RLC Reset)
Description
This counter provides the number of times that a PS RAB establishment fails due to signaling
RLC reset.
Measurement point
RAB ASSIGNMENT RESPONSE message indicating that the operation fails. If RAB setup
fails when the RB setup procedure is concurrent with cell update, the RNC measures this counter

BSC6900 UMTS
Figure 1-792 RAB setup procedure(Signaling RLC Reset)
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabCS.SRB WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Reset Connection and Radio
and Release
1.12.26.7 Number of Failed CS RAB Establishments for Cell (Concurrent

Procedures)
Counters
73424885 VS.RAB.FailEstabCS.Cel- Number of Failed CS RAB

lUpd Establishments for Cell

BSC6900 UMTS
Description
This counter provides the number of times that a CS RAB establishment fails due to RB Setup
and Cell Update Overlap.
Measurement point
The measurement is triggered at point B shown in the following figure. When the RAB setup
fails due to the overlap of RB setup and cell update procedures, the RNC sends the CN a RAB
ASSIGNMENT RESPONSE message with a cause value of "Failure in the Radio Interface
Procedure". In this case, this counter is measured in the best cell that the UE camps on.
Figure 1-793 RAB setup procedure(RB Setup and Cell Update Overlap)
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabCS.Cel- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

lUpd Connection and Radio
and Release

BSC6900 UMTS
1.12.26.8 Number of Failed CS RABs due to Radio Network Layer Cause
Counters
67189495 VS.RAB.FailEstabCS.RNL Number of Failed CS RAB

Cause)
Description
This measurement item provies the number of failed CS RABs due to the radio network layer
cause in the best cell.
Measurement point
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

BSC6900 UMTS
Related Features
VS.RAB.FailEstabCS.RNL WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.27 Measurement of PS RAB assignment failure per cell

(RAB.EstFailPs.Cell)
Overview
The RAB setup procedure is as follows.

BSC6900 UMTS

BSC6900 UMTS
A~B See:RAB.EstabPS.Cell
C 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.Unsp,
VS.RAB.FailEstabPS.DLPower.Cong.Free
D VS.RAB.FailEstabPS.TNL
E VS.RAB.FailEstabPS.IubFail
F VS.RAB.FailEstabPS.UuFail,
VS.RAB.FailEstabPS.UuNoReply,
VS.RAB.FailEstabPS.RBIncCfg,
VS.RAB.FailEstabPS.RBCfgUnsupp,
VS.RAB.FailEstabPS.PhyChFail,
VS.RAB.FailEstabPS.SRBReset,
VS.RAB.FailEstabPS.CellUpd
G VS.RAB.FailEstabPS.RNL
Counters
Description
67192612 VS.RAB.FailEstab Number of Failed PS Earlier than

PS.DLIUBBand.Co RAB Establishments V900R011
ng for Cell (DL Iub
Bandwidth
Congestion)

PS.ULIUBBand.Co RAB Establishments V900R011
ng for Cell (UL Iub
Bandwidth
Congestion)

BSC6900 UMTS

Description

PS.RNL RAB Establishments V900R011
for Cell (Radio
Network Layer
Cause)

PS.TNL RAB Establishments V900R011
for Cell (Transport
Network Layer
Cause)

PS.ULCE.Cong RAB Establishments V900R011
for Cell (UL CE
Congestion)

PS.DLCE.Cong RAB Establishments V900R011
for Cell (DL CE
Congestion)

PS.Code.Cong RAB Establishments V900R011
for Cell (Code
Congestion)
67193540 VS.RAB.FailEstab Number of Failed PS V900R012

PS.RBIncCfg RAB Establishments
for Cell (UU
interface invalid
configuration)

PS.RBCfgUnsupp RAB Establishments
for Cell
(Configuration
unsupported of UE
during the RB setup
procedure)

PS.UuNoReply RAB Establishments
for Cell (No reply of
UE during the RB
setup procedure)

BSC6900 UMTS

Description

PS.PhyChFail RAB Establishments
for Cell (Physical
channel failure of UE
during the RB setup
procedure)

PS.ULPower.Cong RAB Establishments
for Cell (UL Power
Congestion)

PS.DLPower.Cong RAB Establishments
for Cell (DL Power
Congestion)

PS.IubFail RAB Establishments
Due to Radio Link
Configuration
Failure for Cell

PS.UuFail RAB Establishments
Due to Uu Interface
Configuration
Failure for Cell

PS.Unsp RAB Establishments V900R011
for Cell
(Unsupported
Capabilities)

PS.Cong RAB Establishments
73423519 VS.RAB.FailEstab Number of PS Free V900R013

PS.DLPower.Cong. RAB Setup Failures
Free due to DL Power
Resource
Congestion for Cell

PS.SRBReset RAB Establishments
for Cell (Signaling
RLC Reset)

BSC6900 UMTS

Description

PS.CellUpd RAB Establishments
for Cell (Concurrent
Procedures)

PS.HSUPAUser.Co RAB Establishments
ng for Cell (New RAB
Setup Failures When
the Maximum
Number of HSUPA
UEs Is Reached)

PS.HSDPAUser.Co RAB Establishments
ng for Cell (New RAB
Setup Failures When
the Maximum
Number of HSDPA
UEs Is Reached)
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

BSC6900 UMTS
Counter Sub Counter
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.UuFail
VS.RAB.FailEstabPS.SRBReset
VS.RAB.FailEstabPS.CellUpd
VS.RAB.FailEstabPS.HSUPAUser.Cong
VS.RAB.FailEstabPS.HSDPAUser.Cong
VS.RAB.FailEstabPS.UuFail VS.RAB.FailEstabPS.RBIncCfg
VS.RAB.FailEstabPS.RBCfgUnsupp
VS.RAB.FailEstabPS.UuNoReply
VS.RAB.FailEstabPS.PhyChFail
VS.RAB.FailEstabPS.Unsp VS.RAB.FailEstabPS.Cong
1.12.27.1 Number of PS RABs Unsuccessfully Established due to Congestion
Counters
73394298 VS.RAB.FailEstabPS.Cong Number of Failed PS RAB

(Congestion)
67192612 VS.RAB.FailEstabPS.DLIU Number of Failed PS RAB

BBand.Cong Establishments for Cell (DL
67192613 VS.RAB.FailEstabPS.ULIU Number of Failed PS RAB

BBand.Cong Establishments for Cell (UL
67190408 VS.RAB.FailEstabPS.ULC Number of Failed PS RAB

E.Cong Establishments for Cell (UL
CE Congestion)

BSC6900 UMTS
67190409 VS.RAB.FailEstabPS.DLC Number of Failed PS RAB

E.Cong Establishments for Cell (DL
CE Congestion)
67179967 VS.RAB.FailEstabPS.Code. Number of Failed PS RAB

Cong Establishments for Cell
(Code Congestion)
67193613 VS.RAB.FailEstabPS.ULPo Number of Failed PS RAB

wer.Cong Establishments for Cell (UL
Power Congestion)
67193614 VS.RAB.FailEstabPS.DLPo Number of Failed PS RAB

wer.Cong Establishments for Cell (DL
Power Congestion)
73424888 VS.RAB.FailEstabPS.HSUP Number of Failed PS RAB

AUser.Cong Establishments for Cell (New
RAB Setup Failures When
the Maximum Number of
HSUPA UEs Is Reached)
73424889 VS.RAB.FailEstabPS.HSDP Number of Failed PS RAB

AUser.Cong Establishments for Cell (New
RAB Setup Failures When
the Maximum Number of
HSDPA UEs Is Reached)
Description
These counters provide the number of failed PS RAB establishments due to congestion caused
by different reasons in the best cell. If congestion occurs both in the uplink and downlink, the
counter is measured only in the downlink. For example, when PS RABs fail to be set up due to
congestion in both the uplink and downlink power resources, the RNC measures only the
VS.RAB.FailEstabPS.DLPower.Cong counter. For example, if PS RABs fail to be set up due
to congestion in Iub uplink and downlink bandwidth (admission bandwidth), the RNC measures
only the VS.RAB.FailEstabPS.DLIUBBand.Cong counter.
Measurement point
The measurement is triggered at point B as shown in the figure. After receiving from the CN an
RAB ASSIGNMENT REQUEST message that contains the RAB to be set up, the RNC applies
for corresponding radio resources. If the application fails, the RAB setup fails and the RNC
sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails
and the failure cause is any of the following: "Requested Maximum Bit Rate not
Rate for UL not Available","No Radio Resources Available in Target cell","No resource
available", or "TQUEUING Expiry". In this case, the RNC measures this counter based on the
specific cause in the best cell that the UE camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabPS.Cong WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.FailEstabPS.DLIU WRFD-020101 Admission Control

and Release

BSC6900 UMTS
VS.RAB.FailEstabPS.ULIU WRFD-020101 Admission Control

and Release
VS.RAB.FailEstabPS.ULC WRFD-020101 Admission Control

and Release
VS.RAB.FailEstabPS.DLC WRFD-020101 Admission Control

and Release
VS.RAB.FailEstabPS.Code. WRFD-020101 Admission Control

Cong WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabPS.ULPo WRFD-020101 Admission Control

and Release
VS.RAB.FailEstabPS.DLPo WRFD-020101 Admission Control

and Release
VS.RAB.FailEstabPS.HSUP WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

AUser.Cong Connection and Radio
and Release
VS.RAB.FailEstabPS.HSDP WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

AUser.Cong Connection and Radio
and Release
1.12.27.2 Number of Failed PS RABs due to Unsupported Capabilities (Cell)

BSC6900 UMTS
Counters
67179930 VS.RAB.FailEstabPS.Unsp Number of Failed PS RAB

(Unsupported Capabilities)
Description
This measurement item provides the number of failed PS RABs due to insufficient abilities in
the best cell.
Measurement point
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
Rate for UL not Available","Requested Guaranteed Bit Rate not Available","Requested
Guaranteed Bit Rate for DL not Available","Requested Guaranteed Bit Rate for UL not
Available","No Radio Resources Available in Target cell","Requested Transfer Delay not
Achievable","No Resource Available"or "TQUEUING Expiry".In this case, the RNC measures
each item in the best cell that the UE camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabPS.Unsp WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.27.3 Number of PS Free RAB Setup Failures due to DL Power Resource

Congestion for Cell
Counters
73423519 VS.RAB.FailEstabPS.DLPo Number of PS Free RAB

wer.Cong.Free Setup Failures due to DL
Power Resource Congestion
for Cell
Description
This counter provides the number of PS free RAB setup failures in the best cell due to DL power
resource congestion.
Measurement point
This measurement is triggered at point B as shown in the following figure. When the RNC sends
to the CN a RAB ASSIGNMENT RESPONSE message indicating a RAB setup failure, it
measures this counter in the best cell on which the UE camps if the PS free RAB setup fails due
to DL power resource congestion.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabPS.DLPo WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

wer.Cong.Free Connection and Radio
and Release
1.12.27.4 Number of PS RABs Unsuccessfully Established due to Transport

Network Layer Cause

BSC6900 UMTS
Counters
67189557 VS.RAB.FailEstabPS.TNL Number of Failed PS RAB

(Transport Network Layer
Cause)
Description
This counter provides the number of PS RAB setup failures due to failed transport network on
the Iu-PS interface in the best cell that the UE camps on.
Measurement point
a RAB ASSIGNMENT RESPONSE message with the failure cause of "Iu-PS Interface
Transport Connection Failed to Establish", indicating that the RAB unsuccessfully established,
this counter is measured in the best cell that the UE camps on.
Figure 1-799 PS RAB setup procedure (failed operation)
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RAB.FailEstabPS.TNL WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.27.5 Number of Failed PS RAB Establishments Due to Radio Link

Configuration Failure
Counters
73393837 VS.RAB.FailEstabPS.Iub- Number of Failed PS RAB

Fail Establishments Due to Radio
Link Configuration Failure
for Cell
Description
This counter provides the number of times RAB assignment fails in the PS domain when radio
link configuration fails (because a timeout occurs in the wait for the NodeB to respond or the
NodeB responds with a radio link configuration failure message) in the best cell or when a
timeout occurs in the wait for a RADIO LINK RESTORE INDICATION message after a
RADIO LINK FAIL INDICATION message is received from the NodeB.
Measurement point
CN a RAB SSIGNMENT REQUEST message which contains a RAB establishing request, it
RNC receives from the NodeB a RADIO LINK RECONFIGURATION FAILURE message
(see section 9.2.1.6 in 3GPP TS 25.433 for the failure cause). Note that if the radio link
configuration fails due to CE resource insufficiency, this counter is not measured in the cell,
instead, a congestion counter is measured.

BSC6900 UMTS

CN a RAB ASSIGNMENT REQUEST message which contains a RAB establishing request, it
timer for the RNC to wait for a RADIO LINK RECONFIGURATION READY message from
the NodeB expires.
Take the RADIO LINK RECONFIGURATION PREPARE message as an example, the

CN a RAB ASSIGNMENT REQUEST message that contains a RAB establishment request, it
requests related radio resources and triggers a radio link reconfiguration procedure (or radio link
establishment procedure). After the RNC sends the NodeB a RADIO LINK

BSC6900 UMTS
RECONFIGURATION COMMIT message and then receives a RADIO LINK FAILURE

INDICATION message from the NodeB, the RNC starts a timer to wait for a RADIO LINK
RESTORE INDICATION message from the NodeB. This counter is measured in the best cell
that the UE camps on when a RADIO LINK RESTORE INDICATION message is not received
before the timer expires.
Figure 1-802 Timeout for a RADIO LINK RESTORE INDICATION message after receiving
a RADIO LINK FAILURE INDICATION message
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabPS.Iub- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
1.12.27.6 Number of Failed PS RABs due to different reasons of UE During the RB

Setup Procedure for cell
Counters
67193540 VS.RAB.FailEstabPS.RBIn Number of Failed PS RAB

cCfg Establishments for Cell (UU
interface invalid
configuration)
67193541 VS.RAB.FailEstabPS.RBCf Number of Failed PS RAB

gUnsupp Establishments for Cell
(Configuration unsupported
of UE during the RB setup
procedure)
67193543 VS.RAB.FailEstabPS.Uu- Number of Failed PS RAB

NoReply Establishments for Cell (No
reply of UE during the RB
setup procedure)
67193542 VS.RAB.FailEstabPS.PhyC Number of Failed PS RAB

hFail Establishments for Cell
(Physical channel failure of
UE during the RB setup
procedure)
73393838 VS.RAB.FailEstabPS.Uu- Number of Failed PS RAB

Fail Establishments Due to Uu
Interface Configuration
Failure for Cell
Description
The messurement items provide the number of failed PS RABs due to different reasons of UE
in the best cell.
VS.RAB.FailEstabPS.RBIncCfg Number of PS RABs Unsuccessfully

Established due to invalid configuration of
VS.RAB.FailEstabPS.RBCfgUnsupp Number of PS RABs Unsuccessfully

Established due to configuration unsupported
of UE during the RB Setup Procedure

BSC6900 UMTS
VS.RAB.FailEstabPS.UuNoReply Number of PS RABs Unsuccessfully

Established due to no reply during the RB
Setup Procedure
VS.RAB.FailEstabPS.PhyChFail Number of PS RABs Unsuccessfully

Established due to physical channel failure of
VS.RAB.FailEstabPS.UuFail Number of PS RABs Unsuccessfully

Established due to UE configuration failures
(no response is received from the UE or the
UE sends a RADIO BEARER SETUP
FAILURE message) on the Uu interface
during the RB setup procedure
For details about the failure causes for the
message, see section 10.3.3.14 in 3GPP TS
25.331.
Measurement point
measures the VS.RAB.FailEstabPS.RBIncCfg, VS.RAB.FailEstabPS.RBCfgUnsupp,
VS.RAB.FailEstabPS.PhyChFail, and VS.RAB.FailEstabPS.UuFail counters in the best cell
that the UE camps on based on the failure causes contained in the RADIO BEARER SETUP
FAILURE message.

BSC6900 UMTS
measures the VS.RAB.FailEstabPS.UuNoReply and VS.RAB.FailEstabPS.UuFail counters in
the best cell that the UE camps on in the scenarios where the RAB setup fails because the timer
for the RNC to wait for the RADIO BEARER SETUP COMPLETE message from the UE
expires during the RB setup procedure.
Figure 1-804 RAB setup procedure (UE response timeouts)
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabPS.RBIn WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

cCfg Connection and Radio
and Release

BSC6900 UMTS
VS.RAB.FailEstabPS.RBCf WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

gUnsupp Connection and Radio
and Release
VS.RAB.FailEstabPS.Uu- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

NoReply Connection and Radio
and Release
VS.RAB.FailEstabPS.PhyC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

hFail Connection and Radio
and Release
VS.RAB.FailEstabPS.Uu- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.27.7 Number of Failed PS RAB Establishments for Cell (Signaling RLC Reset)
Counters
73424886 VS.RAB.FailEstabPS.SRBR Number of Failed PS RAB

eset Establishments for Cell
(Signaling RLC Reset)
Description
This counter provides the number of times that a PS RAB establishment fails due to signaling
RLC reset.
Measurement point
The measurement is triggered at point B as shown in the figure. The RNC measures this counter
in the best cell that the UE camps on when the RNC sends the CN a RAB ASSIGNMENT
RESPONSE message indicating that the operation fails due to the reset of the RLC that carries
the RADIO BEARER SETUP message.

BSC6900 UMTS
Figure 1-805 RAB setup procedure(Signaling RLC Reset)
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabPS.SRBR WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

eset Connection and Radio
and Release
1.12.27.8 Number of Failed PS RAB Establishments for Cell (Concurrent

Procedures)
Counters
73424887 VS.RAB.FailEstabPS.Cel- Number of Failed PS RAB

lUpd Establishments for Cell

BSC6900 UMTS
Description
This counter provides the number of times that a PS RAB establishment fails due to RB Setup
and Cell Update Overlap.
Measurement point
The measurement is triggered at point B shown in the following figure. When the RAB setup
fails due to the overlap of RB setup and cell update procedures, the RNC sends the CN a RAB
ASSIGNMENT RESPONSE message with a cause value of "Failure in the Radio Interface
Procedure". In this case, this counter is measured in the best cell that the UE camps on.
Figure 1-806 RAB setup procedure(RB Setup and Cell Update Overlap)
Formula
None
Unit
None
Related Features
VS.RAB.FailEstabPS.Cel- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

lUpd Connection and Radio
and Release

BSC6900 UMTS
1.12.27.9 Number of PS RABs Unsuccessfully Established due to Radio Network

Layer Cause for Cell
Counters
67189556 VS.RAB.FailEstabPS.RNL Number of Failed PS RAB

Cause)
Description
The measurement items provide the number of PS RABs unsuccessfully established in the best
cell due to radio network layer cause.
Measurement point
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
Figure 1-807 PS RAB setup procedure (failed operation)
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.RAB.FailEstabPS.RNL WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.28 Measurement of CS RAB assignment modification per cell

(RAB.ModCs.Cell)
Overview
If the parameters, such as QoS, of a CS service are changed after the RAB is set up, the CN
sends to the RNC a RAB ASSIGNMENT REQUEST message. After receiving this message,
the RNC initiates the RAB modification procedure. If the RAB modification succeeds, the RNC
sends to the CN a RAB ASSIGNMENT RESPONSE message indicating that the RAB
modification succeeds. If the RAB modification fails, the RNC sends to the CN a RAB
ASSIGNMENT RESPONSE message indicating that the RAB modification fails.
Counters
Description
67179840 VS.RAB.FailModC Number of Failed CS Earlier than

S.TNL RAB Modifications V900R011
Due to Iu Transport
Connection Setup
Failure for Cell
67179835 VS.RAB.AttEstMo Number of RAB Earlier than

dCS.Conv Modification V900R011
Requests for CS
Conversational
Services for Cell

dCS.Str Modification V900R011
Requests for CS
Streaming Services
for Cell

BSC6900 UMTS

Description

CS.Conv Successful CS RAB V900R011
Modifications for
Conversational
Services for Cell

CS.Str Successful CS RAB V900R011
Modifications for
Streaming Services
for Cell
73393839 VS.RAB.FailModC Number of Failed CS V900R012

S.RNL RAB Modifications
Due to Radio
Network Layer
Cause for Cell
None
1.12.28.1 Number of Failed CS RAB Modifications Due to Transport Network Layer

Cause
Counters
67179840 VS.RAB.FailModCS.TNL Number of Failed CS RAB

Modifications Due to Iu
Transport Connection Setup
Failure for Cell
Description
This counter provides the number of times that the modification of the CS RAB fails due to
transport connection setup failure on the Iu interface in the best cell.
Measurement point
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.

BSC6900 UMTS
Figure 1-808 CS RAB modification procedure
Formula
None
Unit
None
Related Features
VS.RAB.FailModCS.TNL WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.28.2 Counters Related to the Number of CS RAB Modification Requests

BSC6900 UMTS
Counters
67179835 VS.RAB.AttEstModCS.Con Number of RAB

v Modification Requests for
CS Conversational Services
for Cell
67179836 VS.RAB.AttEstModCS.Str Number of RAB

Modification Requests for
CS Streaming Services for
Cell
Description
These counters provide the number of RAB modification requests for CS services in the best
cell based on the service type.
Measurement point
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.
Figure 1-809 CS RAB modification procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AttEstModCS.Con WRFD-010501 Conversational QoS Class

v
VS.RAB.AttEstModCS.Str WRFD-010502 Streaming QoS Class
1.12.28.3 Counters Related to the Number of Successful CS RAB Modifications
Counters
67179837 VS.RAB.SuccModCS.Conv Number of Successful CS

RAB Modifications for
Cell
67179838 VS.RAB.SuccModCS.Str Number of Successful CS

RAB Modifications for
Streaming Services for Cell
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.

BSC6900 UMTS
Figure 1-810 RAB modification procedure (successful operation)
Formula
None
Unit
None
Related Features
VS.RAB.SuccModCS.Conv WRFD-010501 Conversational QoS Class
VS.RAB.SuccModCS.Str WRFD-010502 Streaming QoS Class
1.12.28.4 Number of Failed CS RAB Modifications Due to Radio Network Layer

Cause

BSC6900 UMTS
Counters
73393839 VS.RAB.FailModCS.RNL Number of Failed CS RAB

Modifications Due to Radio
Network Layer Cause for
Cell
Description
This counter provides the number of times that a CS RAB modifications fails due to radio
network fault. The radio network fault can be Requested Maximum Bit Rate not Available,
Requested Maximum Bit Rate for DL not Available, Requested Maximum Bit Rate for UL not
Available, No Radio Resources Available in Target cell, No resource available or TQUEUING
Expiry.
Measurement point
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.
Figure 1-811 RAB assignment failure procedure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.FailModCS.RNL WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.29 Measurement of PS RAB assignment modification per cell

(RAB.ModPs.Cell)
Overview
If the parameters, such as QoS, of a PS service are changed after the RAB is set up, the CN sends
to the RNC a RAB ASSIGNMENT REQUEST message. After receiving this message, the RNC
initiates the RAB modification procedure. If the RAB modification succeeds, the RNC sends to
the CN a RAB ASSIGNMENT RESPONSE message indicating that the RAB modification
succeeds. If the RAB modification fails, the RNC sends to the CN a RAB ASSIGNMENT
RESPONSE message indicating that the RAB modification fails.
For details, see 3GPP TS 25.413.
Counters
Description
67179943 VS.RAB.FailModP Number of Failed PS Earlier than

S.TNL RAB Modifications V900R011
Due to Iu Transport
Connection Failure
for Cell

dPS.Bkg Modification V900R011
Requests for PS
Background
Services for Cell

BSC6900 UMTS

Description

dPS.Conv Modification V900R011
Requests for PS
Conversational
Services for Cell

dPS.Inter Modification V900R011
Requests for PS
for Cell

dPS.Str Modification V900R011
Requests for PS
Streaming Services
for Cell

PS.Bkg Successful RAB V900R011
Background
Services for Cell

PS.Conv Successful RAB V900R011
Conversational
Services for Cell

PS.Inter Successful RAB V900R011
for Cell

PS.Str Successful RAB V900R011
Streaming Services
for Cell
73393840 VS.RAB.FailModP Number of Failed PS V900R012

S.RNL RAB Modifications
Due to Radio
Network Fault for
Cell

BSC6900 UMTS
None
1.12.29.1 Number of Failed PS RAB Modifications Due to Iu Transport Connection

Failure
Counters
67179943 VS.RAB.FailModPS.TNL Number of Failed PS RAB

Modifications Due to Iu
Transport Connection
Failure for Cell
Description
This counter provides the number of times that the modification of the PS RAB fails due to
transport connection setup failure on the Iu interface in the best cell.
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends to the
SGSN a RAB ASSIGNMENT RESPONSE message with the failure cause of "Signalling
Transport Resource Failure" or "Iu Transport Connection Failed to Establish", indicating that
the RAB modification fails, this counter is measured in the best cell that the UE camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.FailModPS.TNL WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.29.2 Number of PS RAB Modification Requests
Counters
67179934 VS.RAB.AttEstModPS.Con Number of RAB

v Modification Requests for PS
Cell
67179937 VS.RAB.AttEstModPS.Bkg Number of RAB

Background Services for Cell
67179936 VS.RAB.AttEstModPS.Inter Number of RAB

Interactive Services for Cell
67179935 VS.RAB.AttEstModPS.Str Number of RAB

Description
These counters provide the number of RAB modification requests for PS services in the best
cell based on the service type.

BSC6900 UMTS
Measurement point
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
VS.RAB.AttEstModPS.Con WRFD-010501 Conversational QoS Class

v
VS.RAB.AttEstModPS.Bkg WRFD-010504 Background QoS Class
VS.RAB.AttEstModPS.Inter WRFD-010503 Interactive QoS Class
VS.RAB.AttEstModPS.Str WRFD-010502 Streaming QoS Class

BSC6900 UMTS
1.12.29.3 Number of Successful PS RAB Modifications
Counters
67179938 VS.RAB.SuccModPS.Conv Number of Successful RAB

Cell
67179941 VS.RAB.SuccModPS.Bkg Number of Successful RAB

Background Services for Cell
67179940 VS.RAB.SuccModPS.Inter Number of Successful RAB

Interactive Services for Cell
67179939 VS.RAB.SuccModPS.Str Number of Successful RAB

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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.SuccModPS.Conv WRFD-010501 Conversational QoS Class
VS.RAB.SuccModPS.Bkg WRFD-010504 Background QoS Class
VS.RAB.SuccModPS.Inter WRFD-010503 Interactive QoS Class
VS.RAB.SuccModPS.Str WRFD-010502 Streaming QoS Class
1.12.29.4 Number of Failed PS RAB Modifications Due to Radio Network Fault

BSC6900 UMTS
Counters
73393840 VS.RAB.FailModPS.RNL Number of Failed PS RAB

Modifications Due to Radio
Network Fault for Cell
Description
This counter provides the number of times that a PS RAB modifications fails due to radio network
fault. The radio network fault can be Requested Maximum Bit Rate not Available, Requested
Maximum Bit Rate for DL not Available, Requested Maximum Bit Rate for UL not Available,
No Radio Resources Available in Target cell, No resource available or TQUEUING Expiry.
Measurement point
RAB ASSIGNMENT RESPONSE message indicating that the operation fails due to
transmission network connection failure (typical cause: radio resource admission failure). In this
Figure 1-815 RAB assignment failure procedure
Formula
None

BSC6900 UMTS
Unit
None
Related Features
VS.RAB.FailModPS.RNL WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.30 Measurement of multi-RAB service per cell

(RAB.MultiRab.Cell)
Overview
These counters provide the number of UEs that occupy different types of spreading factors and
times that combined services are set up and released.
Counters
Description
67199698 VS.SingleRAB.SF4 Number of single- Earlier than

RAB UEs that V900R011
Occupy the DL R99
Codes with
Spreading Factor
(SF) of 4 for Cell

Occupy the DL R99
Codes with
Spreading Factor
(SF) of 8 for Cell

6 RAB UEs that V900R011
Occupy the DL R99
Codes with
Spreading Factor
(SF) of 16 for Cell

BSC6900 UMTS

Description

Occupy the DL R99
Codes with
Spreading Factor
(SF) of 32 for Cell

Occupy the DL R99
Codes with
Spreading Factor
(SF) of 64 for Cell

Occupy the DL R99
Codes with
Spreading Factor
(SF) of 128 for Cell

Occupy the DL R99
Codes with
Spreading Factor
67202942 VS.MultRAB.SF4 Number of multi- Earlier than

Occupy the DL R99
Codes with the
Spreading Factor
(SF) of 4 for Cell

Occupy the DL R99
Codes with the
Spreading Factor
(SF) of 8 for Cell

Occupy the DL R99
Codes with the
Spreading Factor
(SF) of 16 for Cell

BSC6900 UMTS

Description

Occupy the DL R99
Codes with the
Spreading Factor
(SF) of 32 for Cell

Occupy the DL R99
Codes with the
Spreading Factor
(SF) of 64 for Cell

Occupy the DL R99
Codes with the
Spreading Factor

Occupy the DL R99
Codes with the
Spreading Factor
67191657 VS.RAB.SFOccupy Maximum Number Earlier than

.MAX of SFs that Have V900R011
Been Occupied (Let
the SFs that Have
Been Occupied a
Unitary SF of 256)
for Cell
67203416 VS.RAB.SFOccupy Mean Number of SFs Earlier than

that Have Been V900R011
Occupied (Let the
SFs that Have Been
Occupied a Unitary
SF of 256) for Cell
73439942 VS.MultiRAB.Mea Mean Throughput of V900R012

nThroughput.HSD a Single HSDPA
PA MAC-d Flow in the
Case of Multi-RAB
Services for Cell

BSC6900 UMTS

Description
73439943 VS.MultiRAB.Mea Mean Throughput of V900R012

nThroughput.HSU- a Single HSUPA
PA MAC-d Flow in the
Case of Multi-RAB
Services for Cell
73439944 VS.MultiRAB.Mea Mean Downlink V900R012

nThroughput.PSR9 Throughput of a
9DL Single PS R99 RB in
the Case of Multi-
RAB Services for
Cell
73439945 VS.MultiRAB.Mea Mean Uplink V900R012

nThroughput.PSR9 Throughput of a
9UL Single PS R99 RB in
the Case of Multi-
RAB Services for
Cell
73421828 VS.MultiRAB.AttE Number of CS+PS V900R012

stab.CSPS Combined Service
Setup Requests for
Cell
73421829 VS.MultiRAB.Succ Number of V900R012

Estab.CSPS Successful CS+PS
Combined Service
Setups for Cell
73421830 VS.MultiRAB.AttE Number of PS+PS V900R012

stab.PSPS Combined Service
Setup Requests for
Cell
73421831 VS.MultiRAB.Succ Number of V900R012

Estab.PSPS Successful PS+PS
Combined Service
Setups for Cell
73421832 VS.MultiRAB.CSN Number of Normal V900R012

ormRel.CSPS CS Service Releases
of CS+PS Combined
Services for Cell
73421834 VS.MultiRAB.PSN Number of Normal V900R012

ormRel.PSPS PS Service Releases
of PS+PS Combined
Services for Cell

BSC6900 UMTS

Description
73421835 VS.MultiRAB.CSA Number of V900R012

bnormRel.CSPS Abnormal CS
Service Releases of
CS+PS Combined
Services for Cell
73421837 VS.MultiRAB.PSA Number of V900R012

bnormRel.PSPS Abnormal PS
Service Releases of
PS+PS Combined
Services for Cell

bnormRel.PSAtt Abnormal CS
Service Releases
During PS Service
Setup for Cell

bnormRel.PSRel Abnormal CS
Service Releases
During PS Service
Release for Cell
73421840 VS.MultiRAB.PSN Number of Normal V900R012

ormRel.CSPS PS Service Releases
of CS+PS Combined
Services for Cell

bnormRel.CSPS Abnormal PS
Service Releases of
CS+PS Combined
Services for Cell
73424024 VS.AttEstabCS.PSi Number of CS V900R014

nDCH Service Setup
Attempts of UEs
with an Ongoing PS
Service in the
CELL_DCH state for
Cell
73424025 VS.SuccEstabCS.P Number of V900R014

SinDCH Successful CS
Service Setups of
UEs with an Ongoing
PS Service in the
CELL_DCH state for
Cell

BSC6900 UMTS

Description
73424026 VS.AttEstabCS.PSi Number of CS V900R014

nFACH Service Setup
Attempts of UEs
with an Ongoing PS
Service in the
CELL_FACH state
for Cell
73424027 VS.SuccEstabCS.P Number of V900R014

SinFACH Successful CS
Service Setups of
UEs with an Ongoing
PS Service in the
CELL_FACH state
for Cell
73424028 VS.AttPSP2D.CSC Number of State V900R014

onv Transition Attempts
from CELL_PCH or
URA_PCH to
CELL_DCH with the
Cause Value of CS
Service for Cell
73424029 VS.SuccPSP2D.CS Number of V900R014

Conv Successful State
Transitions from
CELL_PCH or
URA_PCH to
CELL_DCH with the
Cause Value of CS
Service for Cell

bnormRel.Resu- Abnormal PS
meExp Service Releases in
the Case of Multi-
RAB Services for
Cell during an inter-
RAT handover( PS
Resume Timer
Expiry)
73425977 VS.MultiRAB.CSP Number of Normally V900R015

SNormRel.CSPS Released CS and PS
Services in CS+PS
Combined Services

BSC6900 UMTS

Description
73425978 VS.MultiRAB.CSP Number of V900R015

SAbnormRel.CSPS Abnormally
Released CS and PS
Services in CS+PS
Combined Services
None
1.12.30.1 Mean Number of Single-RAB UEs Occupy the Codes with Different
Spreading Factors
Counters
67199698 VS.SingleRAB.SF4 Number of single-RAB UEs

that Occupy the DL R99
Codes with Spreading Factor
(SF) of 4 for Cell

(SF) of 8 for Cell

(SF) of 16 for Cell

(SF) of 32 for Cell

(SF) of 64 for Cell


BSC6900 UMTS

Description
These counters provide the average number of single-RAB or multi-RAB UEs that use the
spreading factor (SF) of 4/8/16/32/64/128/256 in a cell.
Measurement point
single-RAB and multi-RAT UEs that use the SF of 4/8/16/32/64/128/256 in a cell. At the end
of the measurement period, the RNC divides the accumulated number of single-RAB UEs by
the number of samples to get the average number of single-RAB and multi-RAT UEs that use
the SF of 4/8/16/32/64/128/256 in a cell.
Formula
None
Unit
None
Related Features
VS.SingleRAB.SF4 WRFD-020108 Code Resource Management
1.12.30.2 Mean Number of Multi-RAB UEs Occupy the Codes with Different
Spreading Factors

BSC6900 UMTS
Counters
67202942 VS.MultRAB.SF4 Number of multi-RAB UEs

Codes with the Spreading
Factor (SF) of 4 for Cell






Description
These counters provide the average number of single-RAB or multi-RAB UEs that use the
spreading factor (SF) of 4/8/16/32/64/128/256 in a cell.
Measurement point
single-RAB and multi-RAT UEs that use the SF of 4/8/16/32/64/128/256 in a cell. At the end
of the measurement period, the RNC divides the accumulated number of single-RAB UEs by
the number of samples to get the average number of single-RAB and multi-RAT UEs that use
the SF of 4/8/16/32/64/128/256 in a cell.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.MultRAB.SF4 WRFD-020108 Code Resource Management
1.12.30.3 Max Count of SF which has been occupied
Counters
67191657 VS.RAB.SFOccupy.MAX Maximum Number of SFs

that Have Been Occupied
(Let the SFs that Have Been
Occupied a Unitary SF of
256) for Cell
67203416 VS.RAB.SFOccupy Mean Number of SFs that

Have Been Occupied (Let the
SFs that Have Been
Occupied a Unitary SF of
256) for Cell
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

BSC6900 UMTS
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
VS.RAB.SFOccupy.MAX WRFD-020108 Code Resource Management
VS.RAB.SFOccupy WRFD-020108 Code Resource Management
1.12.30.4 Mean Throughput of a Single HSPA MAC-d Flow in the Case of Multi-
RAB Services for Cell
Counters
73439942 VS.MultiRAB.MeanThroug Mean Throughput of a Single

hput.HSDPA HSDPA MAC-d Flow in the
Case of Multi-RAB Services
for Cell
73439943 VS.MultiRAB.MeanThroug Mean Throughput of a Single

hput.HSUPA HSUPA MAC-d Flow in the
for Cell
specific formulas.

BSC6900 UMTS
73421821 VS.MultiRAB.MeanThroug VS.MultiRAB.MeanThroug

hput.HSDPA.Times hput.HSDPA.Times

hput.HSDPA.Traffic hput.HSDPA.Traffic

hput.HSUPA.Times hput.HSUPA.Times

hput.HSUPA.Traffic hput.HSUPA.Traffic
Description
This counter provides the mean throughput of a single HSPA MAC-d flow in the case of Multi-
RAB services in the HSPA cell. For DC-HSPA 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 HSPA cell and there is data transmission in the
HSPA cell, the total period of time used for transmitting data and the total number of bits
transmitted in the HSPA cell are calculated. At the end of the measurement period, the mean
throughput of a single MAC-d flow at the RLC layer in a cell is calculated by dividing the total
number of bits by the total period of time. Note that the total number of measured bits excludes
RLC headers and retransmitted data.
Formula
VS.MultiRAB.MeanThroughput.HSDPA = {8}*
[VS.MultiRAB.MeanThroughput.HSDPA.Traffic]/
[VS.MultiRAB.MeanThroughput.HSDPA.Times]
VS.MultiRAB.MeanThroughput.HSUPA = {8}*
[VS.MultiRAB.MeanThroughput.HSUPA.Traffic]/
[VS.MultiRAB.MeanThroughput.HSUPA.Times]
Unit
kbit/s

BSC6900 UMTS
Related Features
VS.MultiRAB.MeanThroug WRFD-010609 Multiple RAB Introduction

hput.HSDPA WRFD-01061505 Package (PS RAB < 2)
Combination of Four PS
Services

hput.HSUPA WRFD-01061505 Package (PS RAB < 2)
Services
1.12.30.5 Mean Throughput of a Single PS R99 RB in the Case of Multi-RAB

Services for Cell
Counters
73439944 VS.MultiRAB.MeanThroug Mean Downlink Throughput

hput.PSR99DL of a Single PS R99 RB in the
for Cell
73439945 VS.MultiRAB.MeanThroug Mean Uplink Throughput of

hput.PSR99UL a Single PS R99 RB in the
for Cell
specific formulas.

hput.PSR99DL.Times hput.PSR99DL.Times

hput.PSR99DL.Traffic hput.PSR99DL.Traffic

hput.PSR99UL.Times hput.PSR99UL.Times

hput.PSR99UL.Traffic hput.PSR99UL.Traffic

BSC6900 UMTS
Description
This counter provides the mean 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 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 throughput of a single PS R99 RB at the RLC layer in a cell is calculated by dividing
the total number of bits by the total period of time. Note that the total number of measured bits
excludes RLC headers and retransmitted data.
Formula
VS.MultiRAB.MeanThroughput.PSR99DL = {8}*
[VS.MultiRAB.MeanThroughput.PSR99DL.Traffic]/
[VS.MultiRAB.MeanThroughput.PSR99DL.Times]
VS.MultiRAB.MeanThroughput.PSR99UL = {8}*
[VS.MultiRAB.MeanThroughput.PSR99UL.Traffic]/
[VS.MultiRAB.MeanThroughput.PSR99UL.Times]
Unit
kbit/s
Related Features

hput.PSR99DL WRFD-01061505 Package (PS RAB < 2)
Services

hput.PSR99UL WRFD-01061505 Package (PS RAB < 2)
Services
1.12.30.6 Number of CS+PS Combined Service Setup Requests for Cell

BSC6900 UMTS
Counters
73421828 VS.MultiRAB.AttEstab.CS Number of CS+PS

PS Combined Service Setup
Requests for Cell
73421830 VS.MultiRAB.AttEstab.PSP Number of PS+PS Combined

S Service Setup Requests for
Cell
73424024 VS.AttEstabCS.PSinDCH Number of CS Service Setup

Attempts of UEs with an
Ongoing PS Service in the
CELL_DCH state for Cell
73424026 VS.AttEstabCS.PSinFACH Number of CS Service Setup

Attempts of UEs with an
Ongoing PS Service in the
CELL_FACH state for Cell
Description
This counter provides the number of RAB setup requests for combined services in the best cell.
Measurement point
The measurement is triggered at point A as shown in the following figure if one or more RABs
of a UE already exists in the cell. When receiving from the CN an RAB ASSIGNMENT
REQUEST message, the RNC checks the RAB type carried in the message and determines the
combined service type based on the existing RAB type of the UE. The counter is measured in
the best cell that the UE camps on if the combined service type is CS+PS. For the combined
service type of CS+PS, CS+2PS, or CS+3PS, the counter of CS+PS combined service is
measured. For the combined service type of 2PS, 3PS, or 4PS, the counter of PS+PS combined
service is measured. VS.MultiRAB.AttEstab.CSPS and VS.MultiRAB.AttEstab.PSPS are
measured in scenarios where service setup sequence is not considered.
VS.AttEstabCS.PSinDCH and VS.AttEstabCS.PSinFACH are measured in scenarios where PS
services are established before CS services.

BSC6900 UMTS
Figure 1-816 RAB setup for combined services
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.MultiRAB.AttEstab.CS WRFD-010609 Multiple RAB Introduction

PS WRFD-01061505 Package (PS RAB < 2)
Services
VS.MultiRAB.AttEstab.PSP WRFD-010609 Multiple RAB Introduction

S WRFD-01061505 Package (PS RAB < 2)
Services
VS.AttEstabCS.PSinDCH WRFD-010609 Multiple RAB Introduction

WRFD-01061505 Package (PS RAB < 2)
Services
VS.AttEstabCS.PSinFACH WRFD-010609 Multiple RAB Introduction

Services
1.12.30.7 Number of Successful CS+PS Combined Service Setups for Cell
Counters
73421829 VS.MultiRAB.SuccEstab.C Number of Successful CS

SPS +PS Combined Service
Setups for Cell
73421831 VS.MultiRAB.SuccEstab.P Number of Successful PS

SPS +PS Combined Service
Setups for Cell
73424025 VS.SuccEstabCS.PSinDCH Number of Successful CS

Service Setups of UEs with
an Ongoing PS Service in the
CELL_DCH state for Cell
73424027 VS.SuccEstabCS.PSin- Number of Successful CS

FACH Service Setups of UEs with
an Ongoing PS Service in the
CELL_FACH state for Cell

BSC6900 UMTS
Description
This counter provides the number of successful RAB setup requests for combined services in
the best cell.
Measurement point
The measurement is triggered at point B as shown in the following figure if one or more RABs
of a UE already exists in the cell. When sending an RAB ASSIGNMENT RESPONSE message
to the CN after receiving an RADIO BEARER SETUP COMPLETE message from the UE, the
RNC checks the RAB type and determines the combined service type based on the existing RAB
type of the UE. The counter is measured in the best cell that the UE camps on if the combined
service type is CS+PS. For the combined service type of CS+PS, CS+2PS, or CS+3PS, the
counter of CS+PS combined service is measured. For the combined service type of 2PS, 3PS,
or 4PS, the counter of PS+PS combined service is measured. VS.MultiRAB.SuccEstab.CSPS
and VS.MultiRAB.SuccEstab.PSPS are measured in scenarios where service setup sequence is
not considered. VS.SuccEstabCS.PSinDCH and VS.SuccEstabCS.PSinFACH are measured in
scenarios where PS services are established before CS services.
Figure 1-817 RAB setup for combined services

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.MultiRAB.SuccEstab.C WRFD-010609 Multiple RAB Introduction

SPS WRFD-01061505 Package (PS RAB < 2)
Services
VS.MultiRAB.SuccEstab.P WRFD-010609 Multiple RAB Introduction

SPS WRFD-01061505 Package (PS RAB < 2)
Services
VS.SuccEstabCS.PSinDCH WRFD-010609 Multiple RAB Introduction

Services
VS.SuccEstabCS.PSin- WRFD-010609 Multiple RAB Introduction

FACH WRFD-01061505 Package (PS RAB < 2)
Services
1.12.30.8 Number of Normal Service Releases of Combined Services for Cell
Counters
73421832 VS.MultiRAB.CSNormRel. Number of Normal CS

CSPS Service Releases of CS+PS
Combined Services for Cell
73421834 VS.MultiRAB.PSNormRel. Number of Normal PS

PSPS Service Releases of PS+PS

BSC6900 UMTS
73425977 VS.MultiRAB.CSPSNormR Number of Normally

el.CSPS Released CS and PS Services
in CS+PS Combined
Services
Description
This counter provides the number of normal combined service releases in the best cell.
Measurement point
RELEASE COMMAND message is User Inactivity, Normal Release, Successful Relocation,
or Network Optimization, or if the RNC has sent a release request with the cause of User
Inactivity, Network Optimization, or UE Generated Signalling Connection Release before the
RNC receives the IU RELEASE COMMAND message, then the counter is measured in the best
cell that the UE camps on according to the combined service type and the released service type.
Figure 1-818 RAB release procedure for combined services
The measurement is also triggered at point B as shown in the following figure. After receiving
an RAB ASSIGNMENT REQUEST message with an RAB release request from the CN, the
RNC releases the corresponding RAB and then sends an RAB ASSIGNMENT RESPONSE
message to the CN. If the release cause in the RAB ASSIGNMENT REQUEST message is User
Inactivity, Normal Release, Successful Relocation, or Network Optimization, or if the RNC has
sent a release request with the cause of User Inactivity, Network Optimization, or UE Generated

BSC6900 UMTS
Signalling Connection Release before the RNC receives the RAB ASSIGNMENT REQUEST
message, then the counter is measured in the best cell that the UE camps on according to the
combined service type and the released service type.
Figure 1-819 Successful RAB release procedure for combined services
Formula
None
Unit
None
Related Features
VS.MultiRAB.CSNormRel. WRFD-010609 Multiple RAB Introduction

CSPS WRFD-01061505 Package (PS RAB < 2)
Services
VS.MultiRAB.PSNormRel. WRFD-01061505 Combination of Four PS

PSPS Services

BSC6900 UMTS
VS.MultiRAB.CSPSNormR WRFD-010609 Multiple RAB Introduction

el.CSPS WRFD-01061505 Package (PS RAB < 2)
Services
1.12.30.9 Number of Abnormal PS Service Releases of PS+PS Combined Services

for Cell
Counters
73421837 VS.MultiRAB.PSAbnormR Number of Abnormal PS

el.PSPS Service Releases of PS+PS
73421835 VS.MultiRAB.CSAbnormR Number of Abnormal CS

el.CSPS Service Releases of CS+PS
73425978 VS.MultiRAB.CSPSAbnor Number of Abnormally

mRel.CSPS Released CS and PS Services
in CS+PS Combined
Services
Description
This counter provides the number of abnormal combined service releases in the best cell.
Measurement point
As shown in point A of the figure, when a failure occurs, the RNC sends the CN an IU RELEASE
"Network Optimization", or "UE Generated Signalling Connection Release", 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.

BSC6900 UMTS
As shown in point A of the figure, when a failure occurs, the RNC sends the CN an RAB
COMMAND message which 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 the counter
is measured in the best cell that the UE camps on according to the types of the combined service
and released service.

BSC6900 UMTS
Figure 1-821 RAB release IU REL procedure for combined services
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

BSC6900 UMTS
Figure 1-822 Iu connection release procedure for combined services
Formula
None
Unit
None
Related Features
VS.MultiRAB.PSAbnormR WRFD-010609 Multiple RAB Introduction

el.PSPS WRFD-01061505 Package (PS RAB < 2)
Services
VS.MultiRAB.CSAbnormR WRFD-010609 Multiple RAB Introduction

Services
VS.MultiRAB.CSPSAbnor WRFD-010609 Multiple RAB Introduction

mRel.CSPS WRFD-01061505 Package (PS RAB < 2)
Services

BSC6900 UMTS
1.12.30.10 Number of Abnormal CS Service Releases During PS Service Setup for

Cell
Counters

el.PSAtt Service Releases During PS
Service Setup for Cell
Description
This counter provides the number of times that a CS service is released abnormally during the
PS RAB setup in the best cell.
Measurement point
As shown in point A of the figure, when a CS RAB is released abnormally during PS RAB setup,
the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives from the
CN an RAB ASSIGNMENT REQUEST message which contains a cause value of abnormal
release (causes except "User Inactivity", "Normal Release", "Successful Relocation", "Network
Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS
25.413), then the counter is measured in the best cell that the UE camps on.

BSC6900 UMTS
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", "Network
25.413), then the counter is measured in the best cell that the UE camps on.
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 the counter is measured in the best

BSC6900 UMTS
Formula
None
Unit
None
Related Features

el.PSAtt WRFD-01061505 Package (PS RAB < 2)
Services
1.12.30.11 Number of Abnormal CS Service Releases During PS Service Release for

Cell

BSC6900 UMTS
Counters

el.PSRel Service Releases During PS
Service Release for Cell
Description
This counter provides the number of times that a CS service in the combined service is released
due to PS service release in the best cell.
Measurement point
As shown in point A of the figure, when a CS RAB is released abnormally during PS RAB
release, the RNC sends the CN an RAB RELEASE REQUEST message. If the RNC receives
from the CN an RAB ASSIGNMENT REQUEST message which contains a cause value of
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

BSC6900 UMTS

Connection Release", for details, see 3GPP TS 25.413), then the counter is measured in the best
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
3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

el.PSRel WRFD-01061505 Package (PS RAB < 2)
Services
1.12.30.12 Number of Normal PS Service Releases of CS+PS Combined Services for

Cell

BSC6900 UMTS
Counters
73421840 VS.MultiRAB.PSNormRel. Number of Normal PS

CSPS Service Releases of CS+PS
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
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

BSC6900 UMTS
RNC releases the corresponding RAB and then sends an RAB ASSIGNMENT RESPONSE
message to the CN. If the release cause in the RAB ASSIGNMENT REQUEST message is User
Inactivity, Normal Release, Successful Relocation, or Network Optimization, or if the RNC has
sent a release request with the cause of User Inactivity, Network Optimization, or UE Generated
Signalling Connection Release before the RNC receives the RAB ASSIGNMENT REQUEST
message, then the counter is measured in the best cell that the UE camps on according to the
combined service type and the released service type.
Figure 1-830 Successful RAB release procedure for combined services
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.MultiRAB.PSNormRel. WRFD-010609 Multiple RAB Introduction

CSPS WRFD-01061505 Package (PS RAB < 2)
Services
1.12.30.13 Number of Abnormal PS Service Releases of CS+PS Combined Services

for Cell
Counters

el.CSPS Service Releases of CS+PS
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
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.

BSC6900 UMTS
COMMAND message which contains a cause value of abnormal release (causes except "User

BSC6900 UMTS
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

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.MultiRAB.PSAbnormR WRFD-010609 Multiple RAB Introduction

Services
1.12.30.14 Number of State Transition Attempts from CELL_PCH or URA_PCH to

CELL_DCH with the Cause Value of CS Service for Cell

BSC6900 UMTS
Counters
73424028 VS.AttPSP2D.CSConv Number of State Transition

Attempts from CELL_PCH
or URA_PCH to
CELL_DCH with the Cause
Value of CS Service for Cell
Description
This counter measures the number of attempts to transit a UE from the CELL_PCH or
URA_PCH to CELL_DCH state with the cause value of CS service in a cell.
Measurement point
The measurement is triggered at point B shown in the figure. When the RNC sends a CELL
UPDATE CONFIRM message to a UE, this counter is incremented by one in the cell that the
UE camps on when all the following conditions are met: 1. The UE attempts to transit from the
CELL_PCH or URA_PCH to CELL_DCH state. 2. The CELL UPDATE message from UE
contains the cause value of Originating Conversational Call, Terminating Conversational Call
and Emergency Call in Establishment cause(IE).

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.AttPSP2D.CSConv WRFD-010609 Multiple RAB Introduction

WRFD-010202 Combination of Four PS

Services
UE State in Connected Mode
URA-PCH, CELL-FACH)
1.12.30.15 Number of Successful State Transitions from CELL_PCH or URA_PCH

to CELL_DCH with the Cause Value of CS Service for Cell
Counters
73424029 VS.SuccPSP2D.CSConv Number of Successful State

Transitions from
CELL_DCH with the Cause
Value of CS Service for Cell
Description
This counter measures the number of successful UE state transitions from CELL_PCH or
URA_PCH to CELL_DCH with the cause value of CS service in a cell.
Measurement point
The measurement is triggered at point C shown in the figure. When the RNC receives a RADIO
BEARER RECONFIGURATION COMPLETE message from the UE, this counter is
incremented by one in the cell that the UE camps on when all the following conditions are met:
1. The UE transits from the CELL_PCH or URA_PCH to CELL_DCH state. 2. The CELL
UPDATE message from UE contains the cause value of Originating Conversational Call,
Terminating Conversational Call and Emergency Call in Establishment cause(IE).

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.SuccPSP2D.CSConv WRFD-010609 Multiple RAB Introduction

WRFD-010202 Combination of Four PS

Services
UE State in Connected Mode
URA-PCH, CELL-FACH)
1.12.30.16 Number of Abnormal PS Service Releases in the Case of Multi-RAB

Services for Cell during an inter-RAT handover( PS Resume Timer Expiry)

BSC6900 UMTS
Counters

el.ResumeExp Service Releases in the Case
of Multi-RAB Services for
Cell during an inter-RAT
handover( PS Resume Timer
Expiry)
Description
This counter provides the number of PS releases that a UE initiates on the RAN side in the best
cell when it does not receive an IU RELEASE COMMAND message from the PS domain in
the CN after the related timer expires. After the CS service in the Multi-RAB Services is
successfully handed over to a cell which uses another RAT, the related timer starts and then this
UE is supposed to receive this message from the PS domain in the CN before the timer expires.
Measurement point
The measurement is triggered at point A as shown in the figure. After the CS service of the UE
is successfully handed over to a cell which uses another RAT, if the UE does not receive an IU
RELEASE COMMAND message from the PS domain in the CN after the related timer expires,
the RAN side sends the UE an IU RELEASE REQUEST message for PS release. This counter
is increased by one in the best cell where the UE camps before the inter-RAT handover.
Figure 1-836 Procedure for an outgoing inter-RAT handover

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.MultiRAB.PSAbnormR WRFD-020303 Inter-RAT Handover Based

el.ResumeExp WRFD-020305 on Coverage

on Service
on Load
1.12.31 Measurement of RAB release per cell

(RAB.RelAbnormal.Cell)
Overview
The RAB release can be classified into the following types:
1) The RAB release initiated by the RNC. When the RNC detects that the UE has no data to
transmit for a long period or the RNC is faulty (for example, the SRB resets or the AAL2 link
on the Iu interface is faulty), the RNC sends to the CN a RAB RELEASE REQUEST message
to release the RAB or an IU RELEASE REQUEST message to release the Iu connection. If the
cause value is "User Inactivity", "Normal Release", "Successful Relocation", "Network
Optimization", or "UE Generated Signalling Connection Release", the RAB release is
considered as normal release; otherwise, the RAB release is considered as abnormal release. For
details, see the middle of the figure.
2) The RAB release initiated by the CN. The RNC initiates the RAB release by sending the RAB
ASSIGNMENT REQUEST message and initiates the Iu connection release by sending the IU
RELEASE COMMAND message. All the RAB releases initiated by the CN are considered as
normal releases. For details, see the left part of the figure.
3) The RAB release initiated by the UE. The UE initiates the RAB release by sending the
SIGNALING CONNECTION RELEASE INDICATION message. According to the domain
information in the message, the RNC sends an IU RELEASE REQUEST message to the CN
node (SGSN or MSC) to release the Iu connection. After the Iu connection is released, the RNC
initiates the RRC release if no Iu connection exists in another domain. All the RAB releases
initiated by the UE are considered as normal releases. For details, see the right part of the figure.
Note: If the Iu interface is reset, released services will be regarded as being normally released.

BSC6900 UMTS
Figure 1-837 Flow chart of call drop

BSC6900 UMTS
Figure 1-838 Sub flow chart of call drop

BSC6900 UMTS
A VS.RAB.AbnormRel.CS,
VS.RAB.AbnormRel.CS.Str,
VS.RAB.AbnormRel.CS64,
VS.RAB.AbnormRel.CS.HSPA.Conv,
VS.RAB.AbnormRel.CS.IuAAL2,
VS.RAB.AbnormRel.CS.RF.ULSync,
VS.RAB.AbnormRel.CS.RF.UuNoReply,
VS.RAB.AbnormRel.CS.RF,
VS.RAB.AbnormRel.CS.OM,
VS.RAB.AbnormRel.CS.Preempt,
VS.RAB.AbnormRel.CS.UTRANgen,
VS.RAB.AbnormRel.CS.RF.SRBReset,
VS.RAB.AbnormRel.AMR,
VS.RAB.AbnormRel.AMR.12.2,
VS.RAB.AbnormRel.AMRWB.23.85,
VS.RAB.AbnormRel.AMRWB,
VS.RAB.AbnormRel.AMR.RF,
VS.RAB.AbnormRel.CS64.RF,
VS.RAB.AbnormRel.CS.Security,
VS.RAB.AbnormRel.CS.OLC

BSC6900 UMTS
B VS.RAB.NormRel.CS,
VS.RAB.NormRel.CS.Str,
VS.RAB.NormRel.AMR,
VS.RAB.NormRel.CS64,
VS.RAB.NormRel.CS.HSPA.Conv,
VS.RAB.NormRel.VPLimit,
VS.RAB.NormRel.AMRWB.23.85,
VS.RAB.NormRel.AMRWB,
VS.RAB.NormRel.CS.UEGen,
VS.RAB.NormRel.CS.UEReEst,
VS.RAB.NormRel.CS.NetOpt,
VS.RAB.AbnormRel.CS.CN
C VS.RAB.NormRel.PS,
VS.RAB.NormRel.PS.Conv,
VS.RAB.NormRel.PS.Str,
VS.RAB.NormRel.PS.CCH,
VS.RAB.NormRel.PS.BE,
VS.RAB.NormRelPS.PTT,
VS.RAB.NormRel.PSR99,
VS.RAB.NormRel.PS.PCH,
VS.RAB.NormRel.PS.UEGen,
VS.RAB.NormRel.PS.UEReEst,
VS.RAB.NormRel.PS.UEReEst.CCHRela-
ted, VS.RAB.NormRel.PS.NetOpt,
VS.RAB.AbnormRel.PS.CN,
VS.RAB.NormRel.PS.0kbps.Timeout

BSC6900 UMTS
D VS.RAB.AbnormRel.PS,
VS.RAB.AbnormRel.PS.Conv,
VS.RAB.AbnormRel.PS.Str,
VS.RAB.AbnormRel.PS.CCH,
VS.RAB.AbnormRel.PS.BE,
VS.RAB.AbnormRelPS.PTT,
VS.RAB.AbnormRel.PSR99,
VS.RAB.AbnormRel.PS.RF.ULSync,
VS.RAB.AbnormRel.PS.GTPULoss,
VS.RAB.AbnormRel.PS.RF.UuNoReply,
VS.RAB.AbnormRel.PS.RF,
VS.RAB.AbnormRel.PS.OM,
VS.RAB.AbnormRel.PS.Preempt,
VS.RAB.AbnormRel.PS.RF.SRBReset,
VS.RAB.AbnormRel.PS.RF.TRBReset,
VS.RAB.AbnormRel.PSR99.RF,
VS.RAB.AbnormRel.PS.UTRANgen,
VS.RAB.AbnormRel.PS.F2P,
VS.RAB.AbnormRel.PS.PCH,
VS.RAB.AbnormRel.PS.D2P,
VS.RAB.AbnormRel.PS.R99D2P,
VS.RAB.AbnormRel.PS.Security,
VS.RAB.AbnormRel.PS.OLC,
VS.RAB.RelReqPS.BE.HSDPA.Cong.Gold
en,
VS.RAB.RelReqPS.BE.HSDPA.Cong.Sil-
ver,
VS.RAB.RelReqPS.BE.HSDPA.Cong.Cop-
per,
VS.RAB.RelReqPS.BE.HSUPA.Cong.Gold
en,
VS.RAB.RelReqPS.BE.HSUPA.Cong.Sil-
ver,
VS.RAB.RelReqPS.BE.HSUPA.Cong.Cop-
per
Counters
Description

el.CS.RF.ULSync Abnormally V900R011
Released Due to RF
for Cell (Uplink
Synchronization
Fail)

BSC6900 UMTS

Description

el.CS.Str Streaming RABs V900R011
Abnormally
Released for Cell

el.PS.Conv Abnormally V900R011
Released for PS
Conversational
Services for Cell

el.PS.Str Abnormally V900R011
Released for PS
Streaming Services
for Cell

CS.Str Streaming RABs V900R011
Normally Released
for Cell

PS.Conv Normally Released V900R011
for PS
Conversational
Services for Cell

PS.Str Normally Released V900R011
for PS Streaming
Services for Cell

el.PS.RF.ULSync Abnormally V900R011
Released for Cell
(Uplink
Synchronization
Failure)

el.CS.RF.UuNoRe- Abnormally V900R011
ply Released Due to RF
for Cell (Failure in
the Radio Interface
Procedure)

BSC6900 UMTS

Description

el.PS.RF.UuNoRe- Abnormally V900R011
ply Released Due to RF
for Cell (Failure in
the Radio Interface
Procedure)

el.CS Abnormally V900R011
Released for Cell

el.CS.RF Abnormally V900R011
Released Due to RF
for Cell

CS Normally Released V900R011
for Cell

el.PS Abnormally V900R011
Released for Cell

PS Normally Released V900R011
for Cell

el.PS.RF Abnormally V900R011
Released Due to RF
for Cell
67180067 VS.RAB.AbnormR Number of CS RAB Earlier than

el.CS.OM Release Requests for V900R011
Cell (O&M
Intervention)

el.CS.Preempt Release Attempts for V900R011
Cell (RAB
Preemption)

el.CS.UTRANgen Abnormal Releases V900R011
Triggered by RNC
for Cell (UTRAN
Cause)

BSC6900 UMTS

Description
67180074 VS.RAB.AbnormR Number of PS RAB Earlier than

el.PS.OM Abnormal Released V900R011
Due to O&M
Intervention for Cell
67180076 VS.RAB.AbnormR Number of PS RAB Earlier than

el.PS.Preempt Abnormal Released V900R011
Due to RAB
Preemption for Cell

el.AMR.12.2 12.2kbit/s AMR V900R011
RABs Abnormally
Released for Cell

RABs Abnormally
Released for Cell

RABs Abnormally
Released for Cell

RABs Abnormally
Released for Cell

el.AMRWB.23.85 23.85kbit/s WB
AMR RABs
Abnormally
Released for Cell

AMR RABs
Abnormally
Released for Cell

AMR RABs
Abnormally
Released for Cell

BSC6900 UMTS

Description

AMR RABs
Abnormally
Released for Cell

AMR RABs
Abnormally
Released for Cell

AMR RABs
Abnormally
Released for Cell

el.AMRWB.12.65 12.65kbit/s WB V900R011
AMR RABs
Abnormally
Released for Cell

el.AMRWB.8.85 8.85kbit/s WB AMR V900R011
RABs Abnormally
Released for Cell

el.AMRWB.6.6 6.6kbit/s WB AMR
RABs Abnormally
Released for Cell

el.CS.RF.SRBReset Abnormally V900R011
Released for Cell
(Signaling RLC
Reset)

el.CS.IuAAL2 Abnormally V900R011
Released for Cell (Iu
Interface AAL2 Link
Failure)
67180082 VS.RAB.AbnormR Number of CS AMR Earlier than

el.AMR RABs Abnormally V900R011
Released for Cell

BSC6900 UMTS

Description
67190518 VS.RAB.NormRel. Number of CS AMR Earlier than

AMR RABs Normally V900R011
Released for Cell(not
including WB-
AMR)

el.PS.RF.SRBReset Abnormally V900R011
Released Due to
Signaling RLC Reset
for Cell

el.PS.RF.TRBReset Abnormally V900R011
Released for Cell
(Traffic RLC Reset)

el.PS.GTPULoss Abnormally V900R011
Released Due to
GTPU Failure for
Cell
67190840 VS.RAB.AbnormR Number of PS Earlier than

el.PS.OLC Domain RABs V900R011
Released Due to
Congestion for Cell

el.CS.OLC Domain RABs V900R011
Released Due to
Congestion for Cell
67192975 VS.RAB.RelReqPS Number of HSDPA Earlier than

.BE.HSDPA.Cong. RABs Carrying V900R011
Golden Golden Users BE
Traffic Released Due
to Congestion for
Cell

Silver Silver Users BE
to Congestion for
Cell

BSC6900 UMTS

Description

Copper Copper Users BE
to Congestion for
Cell
67192978 VS.RAB.RelReqPS Number of HSUPA Earlier than

.BE.HSUPA.Cong. RABs Carrying V900R011
Golden Golden Users BE
to Congestion for
Cell

Silver Silver Users BE
to Congestion for
Cell

Copper Copper Users BE
to Congestion for
Cell
67191786 VS.RAB.NormRel. Number of CS 64 Earlier than

CS64 kbit/s V900R011
Conversational
RABs Normally
Released for Cell

PS.CCH Mapped on CCH V900R011
Normally Released
for Cell

el.PS.CCH Mapped on CCH V900R011
Abnormally
Released for Cell

PS.UEGen Normally Released V900R011
for Cell (UE
Signaling
Connection Release)

BSC6900 UMTS

Description

el.CS64 Conversational V900R011
64kbit/s RABs
Abnormally
Released for Cell
67196204 VS.RAB.AbnormR Number of CS over Earlier than

el.CS.HSPA.Conv HSPA RABs V900R011
Abnormally
Released for Cell
67196205 VS.RAB.NormRel. Number of CS over Earlier than

CS.HSPA.Conv HSPA RABs Normal V900R011
Released for Cell
67196233 VS.RAB.NormRel. Number of CS VP Earlier than

VPLimit RABs Released Due V900R011
to VP Forbiddance
for Cell

PS.0kbps.Timeout at 0 kbit/s Released V900R011
for Failure to Rate up
in the Best Cell

AMRWB.23.85 23.85kbps AMRWB
RABs Normally
Released for cell

RABs Normally
Released for cell

RABs Normally
Released for cell

RABs Normally
Released for cell

RABs Normally
Released for cell

BSC6900 UMTS

Description

RABs Normally
Released for cell

RABs Normally
Released for cell

RABs Normally
Released for cell

RABs Normally
Released for cell

el.AMRWB AMRWB RABs
Abnormally
Released for cell

AMRWB AMRWB RABs
Normally Released
for cell
73393843 VS.RAB.NormRel. Number of CS RABs V900R012

CS.UEGen Normally Released
for Cell (UE
Generated Signaling
Connection Release)
73393845 VS.RAB.NormRel. Number of RABs V900R012

PS.BE Normally Released
for PS BE Services
for Cell
73393846 VS.RAB.AbnormR Number of RABs V900R012

el.PS.BE Abnormally
Released for PS BE
Services for Cell
73394051 VS.RAB.AbnormR Number of CS AMR V900R012

el.AMR.RF RABs abnormal
release Due to RF
Failure for cell

BSC6900 UMTS

Description

el.CS64.RF Conversational
64kbit/s RABs
abnormal released
due to RF failure for
cell

elPS.PTT Abnormally
Released for PTT
Services for Cell
73394074 VS.RAB.NormRel Number of RABs V900R012

PS.PTT Normally Released
for PTT Services for
Cell
73403805 VS.RAB.AbnormR Number of PS R99 V900R012

el.PSR99.RF RABs abnormally
released Due to RF
Failure for cell
73403806 VS.RAB.AbnormR Number of PS R99 V900R012

el.PSR99 RABs abnormally
released for cell
(Including RF
Failure)
73403807 VS.RAB.NormRel. Number of PS R99 V900R012

PSR99 RAB successfully
released for cell
73421882 VS.RAB.NormRel. Number of Normally V900R012

PS.PCH Released PS RABs
that Are in
CELL_PCH or
URA_PCH State for
Cell
73421886 VS.RAB.AbnormR Number of call drops V900R012

el.PS.F2P During the F2P State
Transition for Cell

el.PS.PCH Abnormally
Released PS RABs
that Are in
CELL_PCH or
URA_PCH State for
Cell

BSC6900 UMTS

Description

el.PS.D2P Abnormally
Released for PS
Services during the
CELL_DCH to
CELL_PCH or
URA_PCH for Cell

el.PS.R99D2P Abnormally
Released for PS R99
Services during the
CELL_DCH to
CELL_PCH or
URA_PCH for Cell

el.CS.Security Abnormally
Released Due to
Security Mode
Procedure Failure for
Cell

el.PS.Security Abnormally
Released Due to
Security Mode
Procedure Failure for
Cell
73425979 VS.RAB.NormRel. Number of Released V900R015

CS.UEReEst RABs Triggered by
the Second RRC
CONNECTION
REQUEST Message
from the Same UE in
the CS Domain for
Cell
73425980 VS.RAB.NormRel. Number of RAB V900R015

PS.UEReEst Releases Triggered
by the Second RRC
CONNECTION
REQUEST Message
from the Same UE in
the PS Domain for
Cell

BSC6900 UMTS

Description
73425981 VS.RAB.NormRel. Number of RAB V900R015

PS.UEReEst.CCH Releases Triggered
Related by the Second RRC
CONNECTION
REQUEST Message
from the Same UE in
the PS Domain in
Common Channel-
related Scenarios for
Cell

PS.NetOpt PS RABs due to
Network
Optimization for Cell

el.PS.CN Abnormally
Released PS RABs
Triggered by CN for
Cell

CS.NetOpt CS RABs due to
Network

el.PS.UTRANgen Abnormally
Released PS RABs
Triggered by RNC
for Cell

el.CS.CN Abnormally
Released CS RABs
Triggered by CN for
Cell
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

BSC6900 UMTS
Counter Sub Counter
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.CS.Security
VS.RAB.AbnormRel.PS VS.RAB.AbnormRel.PS.RF
VS.RAB.AbnormRel.PS.OM
VS.RAB.AbnormRel.PS.Preempt
VS.RAB.AbnormRel.PS.GTPULoss
VS.RAB.AbnormRel.PS.OLC
VS.RAB.AbnormRel.PS.Security
VS.RAB.AbnormRel.PS.UTRANgen
VS.RAB.AbnormRel.AMR VS.RAB.AbnormRel.AMR.12.2
VS.RAB.AbnormRel.AMR.7.95
VS.RAB.AbnormRel.AMRWB VS.RAB.AbnormRel.AMRWB.23.85
VS.RAB.AbnormRel.AMRWB.23.05
VS.RAB.NormRel.PSR99 VS.RAB.NormRel.PS.CCH
VS.RAB.NormRel.PS VS.RAB.NormRel.PS.UEGen
VS.RAB.NormRel.PS.UEReEst
VS.RAB.NormRel.PS.NetOpt
VS.RAB.AbnormRel.PS.CN

BSC6900 UMTS
Counter Sub Counter
VS.RAB.NormRel.AMRWB VS.RAB.NormRel.AMRWB.23.85
VS.RAB.NormRel.AMRWB.23.05
VS.RAB.NormRel.CS VS.RAB.NormRel.CS.UEGen
VS.RAB.NormRel.CS.UEReEst
VS.RAB.NormRel.CS.NetOpt
VS.RAB.AbnormRel.CS.CN
VS.RAB.NormRel.PS.UEReEst VS.RAB.NormRel.PS.UEReEst.CCHRela-
ted
1.12.31.1 Number of CS RABs Abnormally Released for Different Services
Counters
67192597 VS.RAB.AbnormRel.CS.Str Number of CS Streaming

RABs Abnormally Released
for Cell
67179778 VS.RAB.AbnormRel.CS Number of CS RABs

Cell
67180083 VS.RAB.AbnormRel.CS64 Number of CS

Conversational 64kbit/s
RABs Abnormally Released
for Cell
67196204 VS.RAB.AbnormRel.CS.HS Number of CS over HSPA

PA.Conv RABs Abnormally Released
for Cell

BSC6900 UMTS
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
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.
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.

BSC6900 UMTS
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.CS.Str WRFD-010502 Streaming QoS Class

WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.AbnormRel.CS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AbnormRel.CS64 WRFD-010501 Conversational QoS Class
VS.RAB.AbnormRel.CS.HS WRFD-010619 CS voice over HSPA/HSPA

PA.Conv +

BSC6900 UMTS
1.12.31.2 Number of CS RABs Abnormally Released Triggered by Different Causes
Counters
67180080 VS.RAB.AbnormRel.CS.Iu Number of CS RABs

AAL2 Abnormally Released for
Cell (Iu Interface AAL2 Link
Failure)

.ULSync Abnormally Released Due to
RF for Cell (Uplink
Synchronization Fail)

.UuNoReply Abnormally Released Due to
RF for Cell (Failure in the
Radio Interface Procedure)

RF for Cell
67180067 VS.RAB.AbnormRel.CS.O Number of CS RAB Release

M Requests for Cell (O&M
Intervention)
67180069 VS.RAB.AbnormRel.CS.Pr Number of CS RAB Release

eempt Attempts for Cell (RAB
Preemption)
67180068 VS.RAB.AbnormRel.CS.U Number of CS RAB

TRANgen Abnormal Releases
Triggered by RNC for Cell
(UTRAN Cause)

.SRBReset Abnormally Released for
Cell (Signaling RLC Reset)
67190841 VS.RAB.AbnormRel.CS.O Number of CS Domain

LC RABs Released Due to
Congestion for Cell
73394051 VS.RAB.AbnormRel.AMR. Number of CS AMR RABs

RF abnormal release Due to RF
Failure for cell

BSC6900 UMTS
73394052 VS.RAB.AbnormRel.CS64. Number of CS

RF Conversational 64kbit/s
RABs abnormal released due
to RF failure for cell
Description
The messurement items provide the number of CS RABs abnormally released triggered by
different causes in the best cell.
VS.RAB.AbnormRel.CS.IuAAL2 Number of CS RABs Abnormally Released

Due to Iu Interface AAL2 Link Failure for
Cell(Fault over Iu:Signalling Transport
Resource Failure)
VS.RAB.AbnormRel.CS.RF.ULSync Number of CS RABs abnormally released

due to Uplink Synchronization Fail(Fault
over Iu:Radio Connection With UE Lost)
VS.RAB.AbnormRel.CS.RF.UuNoReply Number of CS RABs abnormally released

due to UU interface Fail(Fault over Iu:Failure
in the Radio Interface Procedure)
VS.RAB.AbnormRel.CS.RF Number of CS RABs Abnormally Released

Due to RF for Cell(The RF failure includes
Radio Connection With UE Lost and Failure
VS.RAB.AbnormRel.CS.OM Number of CS RAB Abnormal Released Due

to OM Intervention for Cell(Fault over
Iu:O&M Intervention)
VS.RAB.AbnormRel.CS.Preempt Number of CS RAB Abnormal Released Due

to RAB Preemption for Cell(Fault over
Iu:RAB pre-empted)
VS.RAB.AbnormRel.CS.UTRANgen Number of CS RABs Abnormally Released

Due to causes on the UTRAN side for Cell
(Fault over Iu:Release due to UTRAN
Generated Reason)
VS.RAB.AbnormRel.CS.RF.SRBReset Number of CS RABs abnormally released

due to signaling RLC reset(Fault over
Iu:Radio Connection With UE Lost)

BSC6900 UMTS
VS.RAB.AbnormRel.CS.OLC Number of CS RAB Release Attempts Due to

Congestion for Cell
VS.RAB.AbnormRel.AMR.RF Number of wideband and narrowband AMR

services Abnormally Released Due to RF for
Cell(The RF failure includes Radio
Connection With UE Lost and Failure in the
VS.RAB.AbnormRel.CS64.RF Number of 64kbit/s Coversational RAB

Abnormally Released Due to RF for Cell(The
RF failure includes Radio Connection With
UE Lost and Failure in the Radio Interface
Procedure)
Measurement point
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.

BSC6900 UMTS

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.CS.Iu WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

AAL2 Connection and Radio
and Release

.ULSync Connection and Radio
and Release

.UuNoReply Connection and Radio
and Release

BSC6900 UMTS

and Release
VS.RAB.AbnormRel.CS.O WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AbnormRel.CS.Pr WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

eempt WRFD-010505 Connection and Radio
and Release
Queuing and Pre-Emption
VS.RAB.AbnormRel.CS.U WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

TRANgen Connection and Radio
and Release

.SRBReset Connection and Radio
and Release
VS.RAB.AbnormRel.CS.O WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

LC WRFD-020107 Connection and Radio
and Release
Overload Control

RF WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release

RF WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release
1.12.31.3 Number of wideband and narrowband AMR services RABs Abnormally

Released

BSC6900 UMTS
Counters
67180082 VS.RAB.AbnormRel.AMR Number of CS AMR RABs

Cell
67190467 VS.RAB.AbnormRel.AMR. Number of CS 12.2kbit/s

12.2 AMR RABs Abnormally
Released for Cell

Released for Cell

Released for Cell

Released for Cell
67192201 VS.RAB.AbnormRel.AMR Number of CS 23.85kbit/s

WB.23.85 WB AMR RABs
Cell

Cell

Cell

Cell

Cell

Cell

BSC6900 UMTS

Cell
67192208 VS.RAB.AbnormRel.AMR Number of CS 8.85kbit/s WB

WB.8.85 AMR RABs Abnormally
Released for Cell
67192209 VS.RAB.AbnormRel.AMR Number of CS 6.6kbit/s WB

WB.6.6 AMR RABs Abnormally
Released for Cell
73403842 VS.RAB.AbnormRel.AMR Number of CS AMRWB

WB RABs Abnormally Released
for cell
Description
These counters provide the number of abnormally released WB and NB AMR services based
on the maximum downlink bit rate in the best cell. AMR-related counters measure the number
of released NB AMR services. AMRWB-related counters measure the number of released WB
AMR services.
Measurement point
Connection Release", reference to 3GPP TS 25.413),the RNC measures the items based on the
service type and maximum downlink bit rate in the best cells that the UE camps on.

BSC6900 UMTS
Release", reference to 3GPP TS 25.413), the RNC measures the items based on the service type
and maximum downlink bit rate in the best cell that the UE camps on.

BSC6900 UMTS
Release", reference to 3GPP TS 25.413), the RNC measures the items based on the service type
and maximum downlink bit rate in the best cell that the UE camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.AMR WRFD-010501 Conversational QoS Class

12.2 WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release

7.95 WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release

BSC6900 UMTS

5.9 WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release

4.75 WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release

WB.23.85 WRFD-010510 Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

BSC6900 UMTS

3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

WB WRFD-010510 Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.12.31.4 Number of RABs Abnormally Released Due to Security Mode Procedure

Failure
Counters
73423939 VS.RAB.AbnormRel.CS.Se Number of CS RABs

curity Abnormally Released Due to
Failure for Cell

BSC6900 UMTS
73423940 VS.RAB.AbnormRel.PS.Se- Number of PS RABs

curity Abnormally Released Due to
Failure for Cell
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 one RAB is successfully
set up in one domain, another domain Security Mode procedure failure then the RNC sends the
CN an IU RELEASE REQUEST message. 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.
Figure 1-848 Release procedure due to security mode failure

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.CS.Se WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

curity Connection and Radio
and Release
VS.RAB.AbnormRel.PS.Se- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

curity Connection and Radio
and Release
1.12.31.5 Number of CS RABs Normally Released for Cell
Counters
67179779 VS.RAB.NormRel.CS Number of CS RABs

Description
The measurement items provide the number of CS RABs normally released in the best cell.
Measurement point
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.

BSC6900 UMTS
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.

BSC6900 UMTS
The measurement is triggered at point B shown in figure 3 when both of the following conditions
are met: The RNC receives a RAB ASSIGNMENT REQUEST message from the CS CN, and
the cause value in it is not Normal Release, Successful Relocation, User Inactivity, or Network
Optimization. The CN does not receive a RAB RELEASE REQUEST message from the RNC.
In this case, this counter is incremented by one in the best cell that the UE camps on.

BSC6900 UMTS
The measurement is triggered at point A shown in figure 4 when both of the following conditions
are met: The RNC receives an IU RELEASE COMMAND message from the CS CN, and the
cause value in it is not Normal Release, Successful Relocation, User Inactivity, or Network
Optimization. The CN does not receive an IU RELEASE REQUEST or RAB RELEASE
REQUEST message from the RNC. In this case, this counter is incremented by one in the best
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.CS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.31.6 Number of CS RABs Normally Released for Different Services

BSC6900 UMTS
Counters
67192600 VS.RAB.NormRel.CS.Str Number of CS Streaming

RABs Normally Released for
Cell
67190518 VS.RAB.NormRel.AMR Number of CS AMR RABs

(not including WB-AMR)
67191786 VS.RAB.NormRel.CS64 Number of CS 64 kbit/s

Conversational RABs
67196205 VS.RAB.NormRel.CS.HSP Number of CS over HSPA

A.Conv RABs Normal Released for
Cell
Description
The measurement items provide the number of RABs normally released according to different
CS service type in the best cell.
Measurement point
in the best cell which the UE camps on if the released RAB belongs to CS domain.

BSC6900 UMTS
on if the released RAB belongs to CS domain.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.CS.Str WRFD-010502 Streaming QoS Class

WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.AMR WRFD-010501 Conversational QoS Class
VS.RAB.NormRel.CS64 WRFD-010501 Conversational QoS Class
VS.RAB.NormRel.CS.HSP WRFD-010619 CS voice over HSPA/HSPA

A.Conv +

BSC6900 UMTS
1.12.31.7 Number of CS VP RABs Released Due to VP Forbiddance for Cell
Counters
67196233 VS.RAB.NormRel.VPLimit Number of CS VP RABs

Released Due to VP
Forbiddance for Cell
Description
The measurement items provide the number of RABs normally released Due to VP Forbiddance
in the best cell.
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC
initiates an Iu connection release procedure with the cause value of "Network Optimization" and
CS VP RABs are released due to VP forbiddance, this counter is measured in the best cell that
the UE camps on.
initiates a RAB release procedure with the cause value of "Network Optimization" and CS VP
RABs are released due to VP forbiddance, this counter is measured in the best cell that the UE
camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.VPLimit WRFD-020130 Videophone Service

Restriction
1.12.31.8 Number of AMRWB RABs Normally Released for Cell

BSC6900 UMTS
Counters
73403833 VS.RAB.NormRel.AMRW Number of CS 23.85kbps

B.23.85 AMRWB RABs Normally
Released for cell

Released for cell

Released for cell

Released for cell

Released for cell

Released for cell

Released for cell

Released for cell

Released for cell
73403843 VS.RAB.NormRel.AMRW Number of CS AMRWB

B RABs Normally Released for
cell
Description
The measurement item provides the number of CS AMRWB RABs of different rates normally
Measurement point

BSC6900 UMTS
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.
Signalling Connection Release",the RNC measures the items by the service type in the best cell
which the UE camps on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features

B.23.85 WRFD-010510 Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

BSC6900 UMTS

3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

3.4/6.8/13.6/27.2Kbps RRC
and Release

BSC6900 UMTS

B WRFD-010510 Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.12.31.9 Number of CS RABs Normally Released Due to Uplink Signaling

Connection Release
Counters
73393843 VS.RAB.NormRel.CS.UE- Number of CS RABs

Gen Normally Released for Cell
Connection Release)
Description
The measurement items provide the number of CS RABs normally released for uplink signaling
connection release in the best cell which the UE camps on.
Measurement point
SIGNALING CONNECTION RELEASE INDICATION message from the UE. the RNC sends
an IU RELEASE REQUEST message to the CN. After receiving this message, the CN sends
IU RELEASE COMMAND to the RNC. After receiving this command, the RNC releases the
corresponding RAB and sends an IU RELEASE COMPLETE message to the CN. At this time,
the RNC measures this item in the best cell that the UE camps on.

BSC6900 UMTS
Figure 1-859 UL signalling connection release procedure
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.CS.UE- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.31.10 Number of Released RABs due to Network Optimization for Cell

BSC6900 UMTS
Counters
73426207 VS.RAB.NormRel.CS.Ne- Number of Released CS

tOpt RABs due to Network
73426205 VS.RAB.NormRel.PS.Ne- Number of Released PS

tOpt RABs due to Network
Description
This counter measures the number of released RABs due to network optimization according to
the domain types.
Measurement point
The measurement is triggered at point A shown in figure 1 when the RNC sends a RAB
RELEASE REQUEST message to the CN and receives from the CN a RAB ASSIGNMENT
REQUEST message containing the cause value Network Optimization. If the RAB to be released
is for CS services, these counters are measured according to the domain types in the best cell
The measurement is triggered at point A shown in figure 2 when the RNC sends a RAB
RELEASE REQUEST message to the CN and receives from the CN a IU RELEASE

BSC6900 UMTS
COMMAND message containing the cause value Network Optimization. If the RAB to be
released is for CS services, these counters are measured according to the domain types in the
The measurement is triggered at point A shown in figure 3 when the RNC sends an IU RELEASE
REQUEST message to the CN and receives from the CN an IU RELEASE COMMAND message
containing the cause value Network Optimization. If the RAB to be released is for CS services,
these counters are measured according to the domain types in the best cell that the UE camps
on.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.CS.Ne- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

tOpt Connection and Radio
and Release
VS.RAB.NormRel.PS.Ne- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

tOpt Connection and Radio
and Release
1.12.31.11 Number of Abnormally Released RABs Triggered by CN for Cell

BSC6900 UMTS
Counters
73426208 VS.RAB.AbnormRel.CS.C Number of Abnormally

N Released CS RABs
Triggered by CN for Cell
73426206 VS.RAB.AbnormRel.PS.CN Number of Abnormally

Released PS RABs Triggered
by CN for Cell
Description
These counters measure the number of released RABs with abnormal cause values triggered by
the CN in the best cell. All the RAB releases initiated by the CN according to the domain types
are considered as normal releases by RNC.
Measurement point
are met: The RNC receives a RAB ASSIGNMENT REQUEST message from the CS or PS.and
the cause value in it is not Normal Release, Successful Relocation, User Inactivity, Network
Optimization or UE Generated Signalling Connection Release. The CN does not receive a RAB
RELEASE REQUEST message from the RNC. These counters provide the number of released
RABs triggered by the CN according to the domain types.
are met: The RNC receives an IU RELEASE COMMAND message from the CS or PS.and the

BSC6900 UMTS
cause value in it is not Normal Release, Successful Relocation, User Inactivity, Network
Optimization or UE Generated Signalling Connection Release. The CN does not receive an IU
RELEASE REQUEST or RAB RELEASE REQUEST message from the RNC. These counters
provide the number of released RABs triggered by the CN according to the domain types.
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.CS.C WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

N Connection and Radio
and Release
VS.RAB.AbnormRel.PS.CN WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.31.12 Number of PS RABs Normally Released for Cell

BSC6900 UMTS
Counters
67179782 VS.RAB.NormRel.PS Number of PS RABs

Description
The measurement items provide the number of PS RABs normally released in the best cell.
Measurement point
in the best cell which the UE camps on if the released RAB belongs to PS domain.

BSC6900 UMTS

on if the released RAB belongs to PS domain.
are met: The RNC receives from the PS CN a RAB ASSIGNMENT REQUEST message in
which the cause value is not Normal Release, Successful Relocation, User Inactivity, Network
Optimization or UE Generated Signalling Connection Release. The CN does not receive a RAB
RELEASE REQUEST message from the RNC. In this case, this counter is incremented by one

BSC6900 UMTS
are met: The RNC receives an IU RELEASE COMMAND message from the PS CN, and the
cause value in it is not Normal Release, Successful Relocation, User Inactivity, Network
Optimization or UE Generated Signalling Connection Release. The CN does not receive an IU
RELEASE REQUEST or RAB RELEASE REQUEST message from the RNC. In this case, this
counter is incremented by one in the best cell that the UE camps on.
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RAB.NormRel.PS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.31.13 Number of PS RABs Normally Released According to Different Services

and Different Channel-beared Type
Counters
67192601 VS.RAB.NormRel.PS.Conv Number of RABs Normally

Released for PS
Cell
67192602 VS.RAB.NormRel.PS.Str Number of RABs Normally

Released for PS Streaming
Services for Cell
67191791 VS.RAB.NormRel.PS.CCH Number of PS RABs Mapped

on CCH Normally Released
for Cell
73393845 VS.RAB.NormRel.PS.BE Number of RABs Normally

Released for PS BE Services
for Cell
73394074 VS.RAB.NormRelPS.PTT Number of RABs Normally

Released for PTT Services
for Cell
73403807 VS.RAB.NormRel.PSR99 Number of PS R99 RAB

successfully released for cell
73421882 VS.RAB.NormRel.PS.PCH Number of Normally

Released PS RABs that Are
State for Cell
Description
The measurement items provide the number of RABs normally released according to different
services and different channel-beared type in the best cell that the UE camps on.

BSC6900 UMTS
Measurement point
in the best cell which the UE camps on if the released RAB belongs to PS domain.
on if the released RAB belongs to PS domain.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.PS.Conv WRFD-010501 Conversational QoS Class

WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.PS.Str WRFD-010502 Streaming QoS Class

WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release

BSC6900 UMTS
VS.RAB.NormRel.PS.CCH WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.NormRel.PS.BE WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

WRFD-010504 Connection and Radio
VS.RAB.NormRelPS.PTT WRFD-020134 Push to Talk
VS.RAB.NormRel.PSR99 WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.NormRel.PS.PCH WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.31.14 Number of PS RABs Normally Released due to UE Signaling Connection

Release
Counters
67191835 VS.RAB.NormRel.PS.UE- Number of PS RABs

Gen Normally Released for Cell
Release)
Description
This measurement item provides the number of PS RABs normally released due to UE signaling
connection release in the best cell that the UE camps on.
Measurement point
SIGNALING CONNECTION RELEASE INDICATION message from the UE. the RNC sends
an IU RELEASE REQUEST message to the CN. After receiving this message, the CN sends

BSC6900 UMTS
IU RELEASE COMMAND to the RNC. After receiving this command, the RNC releases the
corresponding RAB and sends an IU RELEASE COMPLETE message to the CN. At this time,
the RNC measures this item in the best cell that the UE camps on.
Figure 1-871 UL signalling connection release procedure
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.PS.UE- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.31.15 Number of RAB Releases Triggered by the Second RRC CONNECTION

REQUEST Message from the Same UE

BSC6900 UMTS
Counters
73425980 VS.RAB.NormRel.PS.UER Number of RAB Releases

eEst Triggered by the Second
RRC CONNECTION
REQUEST Message from
the Same UE in the PS
Domain for Cell
73425979 VS.RAB.NormRel.CS.UER Number of Released RABs

eEst Triggered by the Second
RRC CONNECTION
the Same UE in the CS
Domain for Cell
73425981 VS.RAB.NormRel.PS.UER Number of RAB Releases

eEst.CCHRelated Triggered by the Second
RRC CONNECTION
the Same UE in the PS
Domain in Common
Channel-related Scenarios
for Cell
Description
These counters provide the number of times that RABs are released because a UE initiates a
second RRC CONNECTION REQUEST message in a cell when one RRC connection is still in
progress. RAB is short for radio access bearer and RRC is short for radio resource control.
Measurement point
The measurement is triggered at point A shown in the following figure. After receiving the
second RRC CONNECTION REQUEST message, the RNC determines based on the
RANAP_COMMON_ID message that this RRC CONNECTION REQUEST message is sent
by the same UE. Although the RABs requested by the first RRC CONNECTION REQUEST
message are not released yet, the RNC still sends an IU RELEASE REQUEST message with a
cause value of UE Generated Signaling Connection Release to the PS domain. Upon receiving
this message, the CN responds with an IU RELEASE COMMAND message to instruct the RNC
to release the corresponding RABs. After releasing the corresponding RABs, the RNC returns
an IU RELEASE COMPLETE message to the CN. This counter of
VS.RAB.NormRel.PS.UEReEst or VS.RAB.NormRel.CS.UEReEst is measured in the best cell
where the UE camps according to service types.
If the RNC returns an IU RELEASE COMPLETE message to the CN,the UE is experiencing a

D2F or D2P transition, or if the UE is in CELL_FACH or CELL_PCH state (including
CELL_PCH and URA_PCH), this counter of VS.RAB.NormRel.PS.UEReEst.CCHRelated is
measured in the best cell where the UE camps. D2F refers to the process when a UE moves from

BSC6900 UMTS
the CELL_DCH state to the CELL_FACH state. D2P refers to the process when a UE moves
from the CELL_DCH state to the CELL_PCH state.
Figure 1-872 Iu connection release procedure initiated by the RNC upon UEs' RRC connection
reestablishment
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.PS.UER WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

eEst Connection and Radio
and Release
VS.RAB.NormRel.CS.UER WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

eEst Connection and Radio
and Release
VS.RAB.NormRel.PS.UER WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

eEst.CCHRelated Connection and Radio
and Release

BSC6900 UMTS
1.12.31.16 Times of PS RAB of 0kbit/s released for failed to rate up
Counters
67196302 VS.RAB.NormRel.PS. Number of PS RABs at 0

0kbps.Timeout kbit/s Released for Failure to
Rate up in the Best Cell
Description
This measurement item provides the times of releasing RAB of 0kbit/s for failing to rate up
before timer expiry in the best cell.
Measurement point
The measurement is triggered when a RAB of 0kbit/s released by RNC, due to failure of rating
up before the timer of 0kbit/s expires. The measurement is triggered at point A in the figure.
When the RNC initiates an Iu connection release procedure with the cause "Network
Optimization" and PS services are released due to the failure of 0 kbit/s PS RAB rating up before
timer expiry, it measures the number of times of releasing RAB of 0 kbit/s for failing to rate up
before timer expiry in the best cell.
The measurement is triggered at point B in the figure. When the RNC initiates a RAB assignment
release procedure with the cause "Network Optimization" and PS services are released due to

BSC6900 UMTS
the failure of 0 kbit/s PS RAB rating up before timer expiry, it measures the number of times of
releasing RAB of 0 kbit/s for failing to rate up before timer expiry in the best cell.
Formula
None
Unit
None
Related Features
VS.RAB.NormRel.PS. WRFD-021101 Dynamic Channel

0kbps.Timeout Configuration Control
(DCCC)
1.12.31.17 Number of PS RABs Abnormally Released for Different Services Type

and Channel-beared Type

BSC6900 UMTS
Counters
67192598 VS.RAB.AbnormRel.PS.Co Number of RABs

nv Abnormally Released for PS
Cell
67192599 VS.RAB.AbnormRel.PS.Str Number of RABs

Abnormally Released for PS
67179781 VS.RAB.AbnormRel.PS Number of PS RABs

Cell
67191818 VS.RAB.AbnormRel.PS.CC Number of PS RABs Mapped

H on CCH Abnormally
Released for Cell
73393846 VS.RAB.AbnormRel.PS.BE Number of RABs

Abnormally Released for PS
73394073 VS.RAB.AbnormRelPS.PT Number of RABs

T Abnormally Released for
PTT Services for Cell
73403806 VS.RAB.AbnormRel.PSR9 Number of PS R99 RABs

9 abnormally released for cell
(Including RF Failure)
Description
These measurement items take statistics of the number of PS RABs abnormally released
according to different types of service and different Channel-beared Type in the best cell.
Measurement point
Connection Release", reference to 3GPP TS 25.413), the RNC measures the items according to
different service types and Channel-beared Type in the best cell that the UE camps on if the
released RABs belong to PS domain.

BSC6900 UMTS
Release", reference to 3GPP TS 25.413), the RNC measures the items according to according
to different service types and Channel-beared Type in the best cell that the UE camps on if the

BSC6900 UMTS
Release", reference to 3GPP TS 25.413), the RNC measures the items according to according
to different service types and Channel-beared Type in the best cell that the UE camps on if the

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.PS.Co WRFD-010501 Conversational QoS Class

nv WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.AbnormRel.PS.Str WRFD-010502 Streaming QoS Class

WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release

BSC6900 UMTS
VS.RAB.AbnormRel.PS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AbnormRel.PS.CC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

H Connection and Radio
and Release
VS.RAB.AbnormRel.PS.BE WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

WRFD-010503 Connection and Radio
VS.RAB.AbnormRelPS.PT WRFD-020134 Push to Talk

T
VS.RAB.AbnormRel.PSR9 WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

9 Connection and Radio
and Release
1.12.31.18 Number of PS RABs Abnormally Released Due to Different Causes
Counters
67180081 VS.RAB.AbnormRel.PS.GT Number of PS RABs

PULoss Abnormally Released Due to
GTPU Failure for Cell

.ULSync Abnormally Released for
Cell (Uplink
Synchronization Failure)

.UuNoReply Abnormally Released Due to
RF for Cell (Failure in the

RF for Cell

BSC6900 UMTS
67180074 VS.RAB.AbnormRel.PS.O Number of PS RAB

M Abnormal Released Due to
O&M Intervention for Cell
67180076 VS.RAB.AbnormRel.PS.Pre Number of PS RAB

empt Abnormal Released Due to
RAB Preemption for Cell

.SRBReset Abnormally Released Due to
Signaling RLC Reset for Cell

.TRBReset Abnormally Released for
Cell (Traffic RLC Reset)
67190840 VS.RAB.AbnormRel.PS.OL Number of PS Domain RABs

C Released Due to Congestion
for Cell
73403805 VS.RAB.AbnormRel.PSR9 Number of PS R99 RABs

9.RF abnormally released Due to
RF Failure for cell
73426209 VS.RAB.AbnormRel.PS.UT Number of Abnormally

RANgen Released PS RABs Triggered
by RNC for Cell
Description
The messurement items provide the number of PS RABs abnormally released due to different
causes in the best cell.
VS.RAB.AbnormRel.PS.GTPULoss Number of PS RABs Abnormally Released

Due to GTPU Failure for Cell
VS.RAB.AbnormRel.PS.RF.ULSync Number of PS RABs abnormally released due

to Uplink Synchronization Fail(Fault over
Iu:Radio Connection With UE Lost)
VS.RAB.AbnormRel.PS.RF.UuNoReply Number of PS RABs abnormally released due

to UU interface Fail(Fault over Iu:Failure in

BSC6900 UMTS
VS.RAB.AbnormRel.PS.RF Number of PS RABs Abnormally Released

Due to RF for Cell(The RF failure includes
Radio Connection With UE Lost and Failure
VS.RAB.AbnormRel.PS.OM Number of PS RAB Abnormal Released Due

to OM Intervention for Cell(Fault over
Iu:O&M Intervention)
VS.RAB.AbnormRel.PS.Preempt Number of PS RAB Abnormal Released Due

to RAB Preemption for Cell(Fault over
Iu:RAB pre-empted)
VS.RAB.AbnormRel.PS.RF.SRBReset Number of PS RABs abnormally released due

to signaling RLC reset(Fault over Iu:Radio
Connection With UE Lost)
VS.RAB.AbnormRel.PS.RF.TRBReset Number of PS RABs abnormally released due

to traffic RLC reset(Fault over Iu:Radio
Connection With UE Lost)
VS.RAB.AbnormRel.PS.OLC Number of PS Domain RABs Released Due

to Congestion for Cell
VS.RAB.AbnormRel.PSR99.RF Number of PS R99 RABs Abnormally

Released Due to RF for Cell(The RF failure
includes Radio Connection With UE Lost and
Failure in the Radio Interface Procedure)
VS.RAB.AbnormRel.PS.UTRANgen Number of PS RABs Abnormally Released

Due to causes on the UTRAN side for Cell
(Fault over Iu:Release due to UTRAN
Generated Reason)
Measurement point
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

BSC6900 UMTS
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
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.

BSC6900 UMTS
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
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.PS.GT WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

PULoss Connection and Radio
and Release

.ULSync Connection and Radio
and Release

.UuNoReply Connection and Radio
and Release

BSC6900 UMTS

and Release
VS.RAB.AbnormRel.PS.O WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AbnormRel.PS.Pre WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

empt WRFD-010505 Connection and Radio
and Release

.SRBReset Connection and Radio
and Release

.TRBReset Connection and Radio
and Release
VS.RAB.AbnormRel.PS.OL WRFD-020107 Overload Control

C
VS.RAB.AbnormRel.PSR9 WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

9.RF Connection and Radio
and Release
VS.RAB.AbnormRel.PS.UT WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

RANgen Connection and Radio
and Release
1.12.31.19 Number of Abnormally Released PS RABs that Are in CELL_PCH or


BSC6900 UMTS
Counters
73421883 VS.RAB.AbnormRel.PS.PC Number of Abnormally

H Released PS RABs that Are
State for Cell
Description
This counter provides the number of abnormally released PS RABs that are in CELL_PCH or
URA_PCH state. The release of RABs in URA_PCH state is measured in the last cell that the
UE camps on before entering the URA_PCH state.
Measurement point
The measurement is triggered at point A as shown in the following figure. When a failure occurs,
the RNC sends the CN an IU RELEASE REQUEST message. After receiving the message, the
CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE COMMAND
message contains a cause value of abnormal release (causes except "User Inactivity", "Normal
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 RNC sends the CN an RAB RELEASE REQUEST message. After receiving the message,

BSC6900 UMTS
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 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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.PS.PC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

H Connection and Radio
and Release
1.12.31.20 Number of RABs Abnormally Released for PS Services during the

Different State Transition

BSC6900 UMTS
Counters
73422166 VS.RAB.AbnormRel.PS.D2 Number of RABs

P Abnormally Released for PS
Services during the State
Transition from CELL_DCH
for Cell
73421886 VS.RAB.AbnormRel.PS.F2 Number of call drops During

P the F2P State Transition for
Cell
73422169 VS.RAB.AbnormRel.PS.R9 Number of RABs

9D2P Abnormally Released for PS
R99 Services during the State
Transition from CELL_DCH
for Cell
Description
These counters provide the number of RABs Abnormally Released for PS Services during the
different State Transition in the best cell.
VS.RAB.AbnormRel.PS.D2P Number of RABs Abnormally Released for

PS Services during the State Transition from
CELL_DCH to CELL_PCH or URA_PCH
VS.RAB.AbnormRel.PS.F2P Number of RABs Abnormally Released for

PS Services during the State Transition from
CELL_FACH to CELL_PCH or URA_PCH
VS.RAB.AbnormRel.PS.R99D2P Number of RABs Abnormally Released for

PS R99 Services during the State Transition
from CELL_DCH to CELL_PCH or
URA_PCH
Measurement point
Bear Reconfiguration Message to UE during the different State Transition), 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

BSC6900 UMTS
value except "User Inactivity", "Normal Release", "Successful Relocation", "Network

25.413), then this counter is measured in the best cell that the UE camps on according to different
State Transition if the RAB is for a PS service.
CN a RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE
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 according to different State Transition if the
RAB is for a PS service.

BSC6900 UMTS
CN an IU RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE
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 according to different State Transition if the
RAB is for a PS service.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AbnormRel.PS.D2 WRFD-010202 UE State in Connected Mode

P (CELL-DCH, CELL-PCH,
URA-PCH, CELL-FACH)
VS.RAB.AbnormRel.PS.F2 WRFD-010202 UE State in Connected Mode

P (CELL-DCH, CELL-PCH,
URA-PCH, CELL-FACH)
VS.RAB.AbnormRel.PS.R9 WRFD-010202 UE State in Connected Mode

9D2P (CELL-DCH, CELL-PCH,
URA-PCH, CELL-FACH)

BSC6900 UMTS
1.12.31.21 Number of PS BE RABs Beared on HSPA Released due to Cell

Congestion or preemption
Counters
67192975 VS.RAB.RelReqPS.BE.HS Number of HSDPA RABs

DPA.Cong.Golden Carrying Golden Users BE
Traffic Released Due to
Congestion for Cell

DPA.Cong.Silver Carrying Silver Users BE
Congestion for Cell

DPA.Cong.Copper Carrying Copper Users BE
Congestion for Cell
67192978 VS.RAB.RelReqPS.BE.HS Number of HSUPA RABs

UPA.Cong.Golden Carrying Golden Users BE
Congestion for Cell

UPA.Cong.Silver Carrying Silver Users BE
Congestion for Cell

UPA.Cong.Copper Carrying Copper Users BE
Congestion for Cell
Description
The measurement items provide the number of released PS BE RABs beared on HSPA triggered
by the RNC in the best cell due to CELL congestion or preemption.For DC-HSUPA or DC-
HSDPA users, this counter is measured only in the cell with the primary carrier.
VS.RAB.RelReqPS.BE.HSDPA.Cong.Sil- Number of released silver PS BE RABs

ver beared on HSDPA triggered by the RNC due
to CELL congestion

BSC6900 UMTS
VS.RAB.RelReqPS.BE.HSDPA.Cong.Cop- Number of released copper users PS BE

per RABs beared on HSDPA triggered by the
RNC due to CELL congestion
VS.RAB.RelReqPS.BE.HSUPA.Cong.Gold Number of released golden users PS BE

en RABs beared on HSUPA triggered by the
VS.RAB.RelReqPS.BE.HSUPA.Cong.Sil- Number of released silver users PS BE RABs

ver beared on HSUPA triggered by the RNC due
to CELL congestion
VS.RAB.RelReqPS.BE.HSUPA.Cong.Cop- Number of released copper users PS BE

per RABs beared on HSUPA triggered by the
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.
Figure 1-887 RAB release request procedure
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.

BSC6900 UMTS
Figure 1-888 IU connection release procedure
Formula
None
Unit
None
Related Features
VS.RAB.RelReqPS.BE.HS WRFD-010610 HSDPA Introduction

DPA.Cong.Golden WRFD-020107 Package
Overload Control

DPA.Cong.Silver WRFD-020107 Package
Overload Control

DPA.Cong.Copper WRFD-020107 Package
Overload Control

BSC6900 UMTS
VS.RAB.RelReqPS.BE.HS WRFD-010612 HSUPA Introduction

UPA.Cong.Golden WRFD-020107 Package
Overload Control

UPA.Cong.Silver WRFD-020107 Package
Overload Control

UPA.Cong.Copper WRFD-020107 Package
Overload Control
1.12.32 Measurement of CS RAB release per cell(RAB.RelCs.Cell)
Overview
This function subset measures the number of released CS RABs. If a CS RAB is not needed or
an abnormal release occurs after a successful RAB setup, the CN sends a RAB ASSIGNMENT
REQUEST message to the RNC, instructing the RNC to release the RAB. After receiving this
message, the RNC releases the corresponding RAB and then sends a RADIO BEARER
RELEASE message to the UE. If the RB release succeeds, the UE sends a RADIO BEARER
RELEASE COMPLETE message to the RNC. The RNC sends a RAB ASSIGNMENT
RESPONSE message to the CN regardless of whether it receives a RADIO BEARER RELEASE
COMPLETE message from the UE.
Counters
Description
67179850 VS.RAB.AttRelCS. Number of CS RAB Earlier than

NetOpt Release Requests for V900R011
Cell (Network
Optimization)

NormRel Release Requests for V900R011
Cell (Normal
Release)

OM Release Requests for V900R011
Cell (OM
Intervention)

BSC6900 UMTS

Description

Preempt Release Requests for V900R011
Cell (RAB
Preempted)

UEInact Release Requests for V900R011
Cell (User Inactivity)

UTRANGen Release Requests for V900R011
Cell (Release due to
UTRAN Generated
Reason)
67190745 VS.CN.RAB.Loss. Number of CS RAB Earlier than

CS Releases Triggered V900R011
by CN for Cell
73393841 VS.RAB.AttRelCS Number of CS RABs V900R012

Released in RAB
Assignment for Cell
None
1.12.32.1 Number of CS RABs Released Due to Different Causes in RAB

Assignment for Cell
Counters
67179850 VS.RAB.AttRelCS.NetOpt Number of CS RAB Release

Requests for Cell (Network
Optimization)
67179845 VS.RAB.AttRelCS.Norm- Number of CS RAB Release

Rel Requests for Cell (Normal
Release)
67179849 VS.RAB.AttRelCS.OM Number of CS RAB Release

Requests for Cell (OM
Intervention)

BSC6900 UMTS
67179848 VS.RAB.AttRelCS.Preempt Number of CS RAB Release

Requests for Cell (RAB
Preempted)
67179847 VS.RAB.AttRelCS.UEInact Number of CS RAB Release

Requests for Cell (User
Inactivity)
67189500 VS.RAB.AttRelCS.UTRAN Number of CS RAB Release

Gen Requests for Cell (Release
due to UTRAN Generated
Reason)
Description
These counters provide the number of RAB release requests for CS services in the best cell based
on the release cause.
Disuse Statement:This counter will be deleted in later versions. In the current version, the value
of this counter is properly reported.
Measurement point
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.RAB.AttRelCS.NetOpt WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AttRelCS.Norm- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AttRelCS.OM WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AttRelCS.Preempt WRFD-010505 Queuing and Pre-Emption

WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.AttRelCS.UEInact WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AttRelCS.UTRAN WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.32.2 Number of Abnormally Released CS RABs Triggered by CN

BSC6900 UMTS
Counters
67190745 VS.CN.RAB.Loss.CS Number of CS RAB Releases

Description
This measurement item provides the number of CS RABs for the release triggered by the CN in
the best cell only if the release cause is any other Iu interface cause except the following causes:
Successful Relocation, User Inactivity, Normal Release.
Disuse Statement:Counter VS.CN.RAB.Loss.CS will be replaced by counter
VS.RAB.AbnormRel.CS.CN in later versions. In the current version, counters
VS.CN.RAB.Loss.CS and VS.RAB.AbnormRel.CS.CN are both valid, and the value of counter
VS.CN.RAB.Loss.CS is properly reported. Counter VS.CN.RAB.Loss.CS will be deleted in
later versions. Using counter VS.CN.RAB.Loss.CS is not recommended.
Measurement point
The measurement is triggered at point A as shown in Figure 1. When the RNC from the CN
receives a RAB ASSIGNMENT REQUEST message about the CS domain, if the RAB release
cause value is not "Normal Release", "Successful Relocation", "User Inactivity", "Network
Optimization" or "UE Generated Signalling Connection Release", and the RNC had not sent any
RAB RELEASE REQUEST message about the CS domain before, the RNC measures this
counter according to the number of RABs released.
The measurement is triggered at point A as shown in Figure 2. When the RNC receives from
the CN an IU RELEASE COMMAND message about the CS domain, if the RAB release cause

BSC6900 UMTS
value 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 message about the CS domain before, the RNC measures this counter
according to the number of RABs released.
Formula
None
Unit
None
Related Features
VS.CN.RAB.Loss.CS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.32.3 Number of CS RABs Released in RAB Assignment for Cell
Counters
73393841 VS.RAB.AttRelCS Number of CS RABs

Released in RAB
Assignment for Cell

BSC6900 UMTS
Description
This counter provides the number of CS RABs released in RAB assignment in the best cell.
Measurement point
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
VS.RAB.AttRelCS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
1.12.33 Measurement of PS RAB release per cell(RAB.RelPs.Cell)
Overview
If an PS RAB is not needed or an abnormal release occurs after the RAB setup, the CN sends
to the RNC a RAB ASSIGNMENT REQUEST message, indicating the RNC to release the RAB.
After receiving this message, the RNC release the corresponding RAB and then sends to the CN
a RAB ASSIGNMENT RESPONSE message.
Counters
Description
67179955 VS.RAB.AttRelPS. Number of PS RAB Earlier than

NetOptm Release Requests for V900R011
Cell (Network
Optimization)

NormRel Release Requests for V900R011
Cell (Normal
Release)

OM Release Requests for V900R011
Cell (OM
Intervention)

RABPreempt Release Requests for V900R011
Cell (RAB
Preempted)

UeInact Release Requests for V900R011
Cell (User Inactivity)

Unsp Release Requests for V900R011
Cell (Unspecified)

UtranGen Release Requests for V900R011
Cell (Release due to
UTRAN Generated
Reason)

BSC6900 UMTS

Description
67190755 VS.CN.RAB.Loss.P Number of PS RAB Earlier than

S Releases Triggered V900R011
by CN for Cell
73393842 VS.RAB.AttRelPS Number of PS RABs V900R012

Release Attempts for
Cell
None
1.12.33.1 Number of PS RABs Released by RAB ASSIGNMENT REQUEST for

Different Cause
Counters
67179955 VS.RAB.AttRelPS.Ne- Number of PS RAB Release

tOptm Requests for Cell (Network
Optimization)
67179950 VS.RAB.AttRelPS.Norm- Number of PS RAB Release

Rel Requests for Cell (Normal
Release)
67179954 VS.RAB.AttRelPS.OM Number of PS RAB Release

Requests for Cell (OM
Intervention)
67179953 VS.RAB.AttRelPS.RAB- Number of PS RAB Release

Preempt Requests for Cell (RAB
Preempted)
67179952 VS.RAB.AttRelPS.UeInact Number of PS RAB Release

Requests for Cell (User
Inactivity)
67189561 VS.RAB.AttRelPS.Unsp Number of PS RAB Release

Requests for Cell
(Unspecified)
67179951 VS.RAB.AttRelPS.Utran- Number of PS RAB Release

Gen Requests for Cell (Release
due to UTRAN Generated
Reason)

BSC6900 UMTS
Description
These counters provide the number of RAB release requests for PS services in the best cell
according to different release causes.
Measurement point
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.
Figure 1-893 PS RAB release procedure
Formula
None
Unit
None

BSC6900 UMTS
Related Features
VS.RAB.AttRelPS.Ne- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

tOptm Connection and Radio
and Release
VS.RAB.AttRelPS.Norm- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AttRelPS.OM WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AttRelPS.RAB- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

Preempt WRFD-010505 Connection and Radio
and Release
VS.RAB.AttRelPS.UeInact WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AttRelPS.Unsp WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
VS.RAB.AttRelPS.Utran- WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.33.2 Number of PS RAB Releases Triggered by CN
Counters
67190755 VS.CN.RAB.Loss.PS Number of PS RAB Releases


BSC6900 UMTS
Description
This measurement item provides the number of PS RAB releases triggered by the CN in the best
cell.
Disuse Statement:Counter VS.CN.RAB.Loss.PS will be replaced by counter

VS.RAB.AbnormRel.PS.CN in later versions. In the current version, counters
VS.CN.RAB.Loss.PS and VS.RAB.AbnormRel.PS.CN are both valid, and the value of counter
VS.CN.RAB.Loss.PS is properly reported. Counter VS.CN.RAB.Loss.PS will be deleted in later
versions. Using counter VS.CN.RAB.Loss.PS is not recommended.
Measurement point
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.
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.

BSC6900 UMTS
Formula
None
Unit
None
Related Features
VS.CN.RAB.Loss.PS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release
1.12.33.3 Number of PS RAB Release Attempts by RAB ASSIGNMENT REQUEST
Counters
73393842 VS.RAB.AttRelPS Number of PS RABs Release

Attempts for Cell
Description
The measurement item provides the number of PS RAB release attempts by RAB
ASSIGNMENT REQUEST message in the best cell.

BSC6900 UMTS
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
VS.RAB.AttRelPS WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC

and Release

BSC6900 UMTS
1.12.34 Measurement of RB Procedure per cell(RB.Cell)
Overview
Radio Bearer (RB) is the service provided by Layer 2 for transfer of user data between UE and
UTRAN. The RB procedures include:RB setup procedures, RB reconfiguration procedures, RB
release procedures, Transport channel reconfiguration procedures and Physical channel
reconfiguration procedure.
Counters
Description
67180113 VS.AttRBSetup Number of RB Setup Earlier than

Attempts for Cell V900R011
67180114 VS.SuccRBSetup Number of Earlier than

Successful RB V900R011
Setups for Cell
67180115 VS.FailRBSetup.Cf Number of Failed RB Earlier than

gUnsup Setups for Cell V900R011
(configuration
unsupported)
67180116 VS.FailRBSetup.P Number of Failed RB Earlier than

hyChFail Setups for Cell V900R011
(physical channel
failure)
67180119 VS.FailRBSetup.C Number of Failed RB Earlier than

ellUpd Setups for Cell (cell V900R011
update occurred)
67180120 VS.FailRBSetup.In Number of Failed RB Earlier than

cCfg Setups for Cell V900R011
(invalid
configuration)
67180121 VS.FailRBSetup.N Number of Failed RB Earlier than

oReply Setups for Cell (no V900R011
reply)
67180122 VS.AttRBRecfg Number of RB Earlier than

Reconfiguration V900R011
Attempts for Cell
67180123 VS.SuccRBRecfg Number of Earlier than

Successful RB V900R011
Reconfigurations for
Cell

BSC6900 UMTS

Description
67180124 VS.FailRBRecfg.Cf Number of Failed RB Earlier than

gUnsup Reconfigurations for V900R011
Cell (configuration
unsupported)
67180125 VS.FailRBRecfg.P Number of Failed RB Earlier than

hyChFail Reconfigurations for V900R011
Cell (physical
channel failure)
67180128 VS.FailRBRecfg.C Number of Failed RB Earlier than

ellUpd Reconfigurations for V900R011
Cell (cell update
occurred)
67180129 VS.FailRBRecfg.In Number of Failed RB Earlier than

cCfg Reconfigurations for V900R011
Cell (invalid
configuration)
67180130 VS.FailRBRecfg.N Number of Failed RB Earlier than

oReply Reconfigurations for V900R011
Cell (no reply)
67199619 VS.RB.AMR.DL. Number of AMR Earlier than

10.2 Users with DL rate of V900R011
10.2 Kbit/s for Cell



7.4 Kbit/s for Cell

6.7 Kbit/s for Cell

5.9 Kbit/s for Cell


BSC6900 UMTS

Description

67199626 VS.RB.AMR.UL. Number of AMR Earlier than

10.2 Users with UL rate of V900R011



7.4 Kbit/s for Cell

6.7 Kbit/s for Cell

5.9 Kbit/s for Cell


67203430 VS.RB.PS.Conv.D Average Number of V900R012

L.64 RBs for PS R99
Conversational
Services with DL
Cell
67203434 VS.RB.PS.Conv.U Average Number of V900R012

L.64 RBs for PS R99
Conversational
Services with UL
Cell

BSC6900 UMTS

Description

128 RBs for PS R99 V900R011
Background
Services with DL
Cell

Background
Services with DL
Cell

Background
Services with DL
Cell

Background
Services with DL
Cell

Background
Services with DL
Cell

Background
Services with DL
Cell

Background
Services with DL
Cell

BSC6900 UMTS

Description

Background
Services with DL
Cell
67199556 VS.RB.CS.Conv.D Average Number of Earlier than

L.64 RBs for CS V900R011
Conversational
Services with DL
Cell
67203438 VS.RB.CS.Conv.U Average Number of Earlier than

L.64 RBs for CS V900R011
Conversational
Services with UL
Cell

with DL Rate of 128
Kbit/s for Cell

with DL Rate of 144
Kbit/s for Cell

with DL Rate of 16
Kbit/s for Cell

with DL Rate of 256
Kbit/s for Cell

with DL Rate of 32
Kbit/s for Cell

BSC6900 UMTS

Description

with DL Rate of 384
Kbit/s for Cell

with DL Rate of 64
Kbit/s for Cell
67199574 VS.RB.PS.Int.DL.8 Average Number of Earlier than

RBs for PS R99 V900R011
with DL Rate of 8
Kbit/s for Cell
67199560 VS.RB.CS.Str.DL. Average Number of Earlier than

57.6 RBs for CS V900R011
Streaming Services
with DL Rate of 57.6
Kbit/s for Cell

Streaming Services
with DL Rate of 128
Kbit/s for Cell

Streaming Services
with DL Rate of 144
Kbit/s for Cell

Streaming Services
with DL Rate of 32
Kbit/s for Cell

Streaming Services
with DL Rate of 64
Kbit/s for Cell

BSC6900 UMTS

Description
67203439 VS.RB.PS.Str.DL.8 Average Number of Earlier than

Streaming Services
with DL Rate of 8
Kbit/s for Cell

Streaming Services
with DL Rate of 16
Kbit/s for Cell

Background
Services with UL
Cell

Background
Services with UL
Cell

Background
Services with UL
Cell

Background
Services with UL
Cell

Background
Services with UL
Cell

BSC6900 UMTS

Description

Background
Services with UL
Cell

Background
Services with UL
Cell

Background
Services with UL
Cell

with UL Rate of 128
Kbit/s for Cell

with UL Rate of 144
Kbit/s for Cell

with UL Rate of 16
Kbit/s for Cell

with UL Rate of 256
Kbit/s for Cell

with UL Rate of 32
Kbit/s for Cell

BSC6900 UMTS

Description

with UL Rate of 384
Kbit/s for Cell

with UL Rate of 64
Kbit/s for Cell
67199582 VS.RB.PS.Int.UL.8 Average Number of Earlier than

with UL Rate of 8
Kbit/s for Cell
67203442 VS.RB.CS.Str.UL. Average Number of Earlier than

57.6 RBs for CS V900R011
Streaming Services
with UL Rate of 57.6
Kbit/s for Cell

Streaming Services
with UL Rate of 16
Kbit/s for Cell

Streaming Services
with UL Rate of 32
Kbit/s for Cell

Streaming Services
with UL Rate of 64
Kbit/s for Cell
67203445 VS.RB.PS.Str.UL.8 Average Number of Earlier than

Streaming Services
with UL Rate of 8
Kbit/s for Cell

BSC6900 UMTS

Description

Streaming Services
with UL Rate of 128
Kbit/s for Cell

Streaming Services
with UL Rate of 144
Kbit/s for Cell
67192389 VS.DRD.RBSetup. Number of RB Setup Earlier than

AttOut Attempts for V900R011
Outgoing Inter-
Frequency Directed
Retry for Cell
67192390 VS.DRD.RBSetup. Number of Earlier than

SuccOut Successful RB Setup V900R011
for Outgoing Inter-
Frequency Directed
Retry for Cell
67192391 VS.DRD.RBSetup. Number of RB Setup Earlier than

AttIn Attempts for V900R011
Incoming Inter-
Frequency Directed
Retry for Cell
67192392 VS.DRD.RBSetup. Number of Earlier than

SuccIn Successful RB Setup V900R011
for Incoming Inter-
Frequency Directed
Retry for Cell
67192393 VS.DRD.RBRecfg. Number of RB Earlier than

AttOut Reconfiguration V900R011
Attempts for
Outgoing Inter-
Frequency Directed
Retry for Cell
67192394 VS.DRD.RBRecfg. Number of Earlier than

SuccOut Successful RB V900R011
Reconfiguration for
Outgoing Inter-
Frequency Directed
Retry for Cell

BSC6900 UMTS

Description
67192395 VS.DRD.RBRecfg. Number of RB Earlier than

AttIn Reconfiguration V900R011
Attempts for
Incoming Inter-
Frequency Directed
Retry for Cell
67192396 VS.DRD.RBRecfg. Number of Earlier than

SuccIn Successful RB V900R011
Reconfiguration for
Incoming Inter-
Frequency Directed
Retry for Cell
67192440 VS.DRD.RB.D2H. Number of Outgoing Earlier than

AttOut DCH-to-HSDPA V900R011
Directed Retry
Attempts for Cell

uccOut Successful Outgoing V900R011
DCH-to-HSDPA
Directed Retry for
Cell
67192442 VS.DRD.RB.D2H. Number of Incoming Earlier than

AttIn DCH-to-HSDPA V900R011
Directed Retry
Attempts for Cell

uccIn Successful Incoming V900R011
DCH-to-HSDPA
Directed Retry for

BSC6900 UMTS V900R015C00SPC529 Performance Counter Reference

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BSC6900 UMTS V900R015C00SPC529 Performance Counter Reference

Hochgeladen von

Copyright:

Verfügbare Formate

BSC6900 UMTS

Performance Counter Reference

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 06 (2014-01-20) Huawei Proprietary and Confidential i

About This Document

Product Name Product Version

Issue 06 (2014-01-20) Huawei Proprietary and Confidential ii

Figure 1 Document structure

Table 1 explains the terms shown in Figure 1.

Object type Object types are located at the second level of

Function Subset Function Subsets are located at the third level

Counter Counters are located at the fourth level of the

Counter Item Description

Table 2 Description of each counter item

Obj Overvi Definition and function of a object type.

Issue 06 (2014-01-20) Huawei Proprietary and Confidential iii

Functio Function subsets contained in a object type.

Fun Functio Name of the function set.

Co Counte A string of digits that uniquely Related intermediate counters are

Descri Detailed description about a counter.

Measur Condition for triggering counter measurement.

Formul Relationship among counters.

Unit Unit of a counter.

Issue 06 (2014-01-20) Huawei Proprietary and Confidential iv

About This Document.....................................................................................................................ii

Issue 06 (2014-01-20) Huawei Proprietary and Confidential v

1.2.1.1 Measurement of CS-Domain Equivalent Erlang of Each Subsystem in the RNC.................................................46

Issue 06 (2014-01-20) Huawei Proprietary and Confidential vi

1.3.1.8 Number of Echo Response Packets Sent by the GTP-U........................................................................................93

Issue 06 (2014-01-20) Huawei Proprietary and Confidential vii

1.4.6.1 Number of RESET Messages Initiated by RNC to PS Domain...........................................................................154

Issue 06 (2014-01-20) Huawei Proprietary and Confidential viii

Issue 06 (2014-01-20) Huawei Proprietary and Confidential ix

1.5.4 Measurement related to SRNC in Iur interface(SRNC.IUR)..................................................................................264

Issue 06 (2014-01-20) Huawei Proprietary and Confidential x

1.5.5 Measurement related to traffic for Iur Interface(TRFFIC.IUR)..............................................................................347

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xi

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xii

1.10.5.3 Number of PS Outgoing Inter-RAT Handover Attempts Initiated by UE.........................................................448

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xiii

1.10.10.2 Signaling Delay of PS RAB Setup...................................................................................................................512

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xiv

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xv

1.10.22.4 Number of RRC Connection Releases Triggered by SRNC Due to DSCR.....................................................673

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xvi

1.12.1 Measurement related to Algorithm per cell(ALGO.Cell)......................................................................................725

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xvii

1.12.1.35 Number of Successful Cell Resource Requests During RAB Establishment..................................................798

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xviii

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xix

1.12.2.10 Number of UEs Involved in Inter-Frequency Load-based Handovers in a CLB Cell......................................897

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xx

1.12.4.15 Number of HSUPA Uplink Bytes of UU BOOST Branch for Cell.................................................................958

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxi

1.12.7.3 Number of Up Link SF-2 Compressed Mode Activation Fails........................................................................1010

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxii

1.12.10.8 RRC Connection Setup Duration on an ERACH for Cell..............................................................................1065

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxiii

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxiv

1.12.13.4 Number of Successful HSUPA RAB Establishments for Cell.......................................................................1294

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxv

Issue 06 (2014-01-20) Huawei Proprietary and Confidential xxvi